Functionality This method determines how data from Organizational Management and HRmaster data is replicated, and stores the replications of objects. The BAPI is used in the 'HR-ONLY' ALE scenario, which requires HR datato be validated and imported in a non-HR system. The number ofinfotypes supported by 'HR-ONLY' is preset, which means that the BAPIis less suitable for complete legacy data transfers. The header data of objects to be replicated is transferred using the'HR_Object_Header' parameter. In addition to the object key, whichconsists of the plan version, object type, and object ID, there is a'proof flag' that must be set to 'X', and the 'Operator' field. Thisfield determines the mode in which the object in question is imported.You must decide whether to use the insert or update mode. Insert mode: The data records for the object are transferred in full. If an objectyou want to transfer already exists, it is replaced in full. In otherwords, it is deleted in full and then recreated using the transferreddata records. Update mode: In the target system, the records that are completely within the perioddetermined by the 'HR_Infotype_Header' parameter are deleted in full,and then recreated using the transferred infotype data for theinfotypes for the object. If you want to create an object, you must ensure that the followinginfotypes are transferred: infotypes 0000, 0001, and 0002 for persons,and infotype 1000 (object) for objects in Personnel Planning andOrganizational Management. The 'HR_Infotype_Header' parameter is used for each object to determinethe infotypes that are transferred for a particular period. All of theinfotype records that are completely within this period for theinfotype in question are transferred to another corresponding infotypetable.
Example Importing an organizational unit in insert mode (existence infotype 1000): BAPIHROBJ[1]-PLAN_VER = '01'. BAPIHROBJ[1]-OBJ_TYPE = 'O '. BAPIHROBJ[1]-OBJ_ID = '12345678'. BAPIHROBJ[1]-PROOF = 'X'. BAPIHROBJ[1]-OPERATOR = 'I'. BAPIHRINF[1]-PLAN_VER = '01'. BAPIHRINF[1]-OBJ_TYPE = 'O '. BAPIHRINF[1]-OBJ_ID = '12345678'. BAPIHRINF[1]-INFOTYPE = '1000'. BAPIHRINF[1]-SUBTYPE = ' '. BAPIHRINF[1]-FROM_DATE = '19980101'. BAPIHRINF[1]-TO_DATE = '99991231'. PD_OBJECT[1]-CLIENT = '000'. PD_OBJECT[1]-PLAN_VER = '01'. PD_OBJECT[1]-OBJ_TYPE = 'O '. PD_OBJECT[1]-OBJ_ID = '12345678'. PD_OBJECT[1]-INFOTYPE = '1000'. PD_OBJECT[1]-SUBTYPE = ' '. PD_OBJECT[1]-PL_STATUS = '1'. PD_OBJECT[1]-PRIORITY = ' '. PD_OBJECT[1]-FROM_DATE = '19980101'. PD_OBJECT[1]-TO_DATE = '99991231'. PD_OBJECT[1]-CHANGED_ON = '19980101'. PD_OBJECT[1]-CHANGED_BY = 'MODEL USER'. PD_OBJECT[1]-OBJ_ABB = 'ORG_EH_A'. PD_OBJECT[1]-OBJ_NAME = 'organizational unit A'. PD_OBJECT[1]-LANGU_ISO = 'DE'. Importing infotype 0006 with subtypes 1 and 2 for a person in update mode: BAPIHROBJ[1]-PLAN_VER = '01'. BAPIHROBJ[1]-OBJ_TYPE = 'P '. BAPIHROBJ[1]-OBJ_ID = '00112233'. BAPIHROBJ[1]-PROOF = 'X'. BAPIHROBJ[1]-OPERATOR = 'U'. BAPIHRINF[1]-PLAN_VER = '01'. BAPIHRINF[1]-OBJ_TYPE = 'P '. BAPIHRINF[1]-OBJ_ID = '00112233'. BAPIHRINF[1]-INFOTYPE = '0006'. BAPIHRINF[1]-SUBTYPE = '1 '. BAPIHRINF[1]-FROM_DATE = '19980205'. BAPIHRINF[1]-TO_DATE = '99991231'. BAPIHRINF[2]-PLAN_VER = '01'. BAPIHRINF[2]-OBJ_TYPE = 'P '. BAPIHRINF[2]-OBJ_ID = '00112233'. BAPIHRINF[2]-INFOTYPE = '0006'. BAPIHRINF[2]-SUBTYPE = '2 '. BAPIHRINF[2]-FROM_DATE = '19980304'. BAPIHRINF[2]-TO_DATE = '19991231'. EMPLOYEE_PRIVATE_ADDRESS[1]-OBJ_ID = '00112233'. EMPLOYEE_PRIVATE_ADDRESS[1]-INFOTYPE = '0006'. EMPLOYEE_PRIVATE_ADDRESS[1]-SUBTYPE = '1 '. EMPLOYEE_PRIVATE_ADDRESS[1]-TO_DATE = '19980630'. EMPLOYEE_PRIVATE_ADDRESS[1]-FROM_DATE = '19980205'. EMPLOYEE_PRIVATE_ADDRESS[1]-CHANGED_ON = '19980701'. EMPLOYEE_PRIVATE_ADDRESS[1]-CHANGED_BY = 'MODEL USER'. EMPLOYEE_PRIVATE_ADDRESS[1]-STREET = 'Main Street'. EMPLOYEE_PRIVATE_ADDRESS[1]-CITY = 'Heidelberg'. ... EMPLOYEE_PRIVATE_ADDRESS[2]-OBJ_ID = '00112233'. EMPLOYEE_PRIVATE_ADDRESS[2]-INFOTYPE = '0006'. EMPLOYEE_PRIVATE_ADDRESS[2]-SUBTYPE = '1 '. EMPLOYEE_PRIVATE_ADDRESS[2]-TO_DATE = '99991231'. EMPLOYEE_PRIVATE_ADDRESS[2]-FROM_DATE = '19980701'. EMPLOYEE_PRIVATE_ADDRESS[2]-CHANGED_ON = '19980701'. EMPLOYEE_PRIVATE_ADDRESS[2]-CHANGED_BY = 'MODEL USER'. EMPLOYEE_PRIVATE_ADDRESS[2]-STREET = 'Fisherman Road'. EMPLOYEE_PRIVATE_ADDRESS[2]-CITY = 'Heidelberg'. ... EMPLOYEE_PRIVATE_ADDRESS[3]-OBJ_ID = '00112233'. EMPLOYEE_PRIVATE_ADDRESS[3]-INFOTYPE = '0006'. EMPLOYEE_PRIVATE_ADDRESS[3]-SUBTYPE = '2 '. EMPLOYEE_PRIVATE_ADDRESS[3]-TO_DATE = '19991231'. EMPLOYEE_PRIVATE_ADDRESS[3]-FROM_DATE = '19980304'. EMPLOYEE_PRIVATE_ADDRESS[3]-CHANGED_ON = '19980304'. EMPLOYEE_PRIVATE_ADDRESS[3]-CHANGED_BY = 'MODEL USER'. EMPLOYEE_PRIVATE_ADDRESS[3]-STREET = 'Broadway'. EMPLOYEE_PRIVATE_ADDRESS[3]-CITY = 'Walldorf'. Restrictions> If your Human Resources Management System is linked by ALE to anAccounting System, you are advised for technical reasons not to use theBAPI because synchronous validation would lead to a COMMIT. This wouldprevent a ROLLBACK if a posting error occurs. If data is posted using the BAPI, ALE change pointers are not written. Action 'AL', which consists of infotypes 0001 and 0002, is supplied bySAP and must not be modified. It is used to create personnel numbers.Infotype 0000 (Actions) is then overwritten without validation inaccordance with the transferred parameters. Infotype 1000 is also created by the BAPI without validation. Infotype0003 (Payroll Status) is recreated in accordance with the logic forcreating HR master data. If infotypes have time constraint 1, you must ensure that the datarecords do not contain gaps. The 'Changed on' and 'Last changed by' fields in all of the infotypescontain the date on which the BAPI was accessed, and the user used toaccess the BAPI in the target system (RFC user). Infotypes must not be related to dynamic actions in the system to whichdata is imported. To ensure that actions are displayed consistently, you must deactivatethe additional actions (switch 'ADMIN EVSUB' in T77S0 = 0). The method is not used in the scenario for distributed HR master data. Notes If the error messages are not precise enough for you to localize theerror, you can import data to the R/3 System using the'HRMaster_Save_Repl_Mult' function module instead of the BAPI. The datarecords for error analysis are displayed online using report'RHALEBAPIPROOF'. The data is validated before it is imported, which can lead to runtimeproblems, especially if large amounts of data are imported. One way ofavoiding this problem, for example, is by reducing the size of thedataset for each BAPI access. Description This parameter contains records for infotype 0283. Its structure is thesame as that of P0283. Description This parameter contains records for infotype 0009. Its structure is thesame as that of P0009. Description This parameter contains records for infotype 0315. Its structure is thesame as that of P0315. Description This parameter contains records for infotype 0105. Its structure is thesame as that of P0105. Description This parameter contains records for infotype 0222. Its structure is thesame as that of P0222. Description This parameter contains records for infotype 0001. Its structure is thesame as that of P0001. Description This parameter contains records for infotype 0003. Its structure is thesame as that of P0003. Description This parameter contains records for infotype 0002. Its structure is thesame as that of P0002. Description This parameter contains records for infotype 0000. Its structure is thesame as that of P0000. Description This parameter contains records for infotype 0006. Its structure is thesame as that of P0006. Description This parameter contains records for infotype 0900. Its structure is thesame as that of P0900. Description This parameter contains records for infotype 0050. Its structure is thesame as that of P0050. Description This parameter contains records for infotype 0017. Its structure is thesame as that of P0017. Description This parameter contains header data for infotypes to be reproduced. Description This parameter contains header data for HR objects to be reproduced. Description This parameter contains records for infotype 1000. Its structure is thesame as that of P1000. Description This parameter contains records for infotype 1028. Its structure is thesame as that of P1028. Description This parameter contains records for infotype 1043. Its structure is thesame as that of P1043. Description This parameter contains records for infotype 1044. Its structure is thesame as that of P1044. Description This parameter contains records for infotype 1010. Its structure is thesame as that of P1010. Description This parameter contains records from infotype 1062. Its structurecorresponds to structure P1062_EXP. Description This parameter contains records for infotype 1023. Its structure is thesame as that of P1023. Description This parameter contains records for infotype 1041. Its structure is thesame as that of P1041. Description This parameter contains records for infotype 1024. Its structure is thesame as that of P1024. Description This parameter contains records for infotype 1036. Its structure is thesame as that of P1036. Description This parameter contains records for infotype 1060. Its structure is thesame as that of P1060. Description This parameter contains records for infotype 1026. Its structure is thesame as that of P1026. Description This parameter contains records for infotype 1034. Its structure is thesame as that of P1034. Description This parameter contains records for infotype 1021. Its structure is thesame as that of P1021. Description This parameter contains records for infotype 1030. Its structure is thesame as that of P1030. Description This parameter contains records for infotype 1035. Its structure is thesame as that of P1035. Description This parameter contains records for infotype 1042. Its structure is thesame as that of P1042. Description This parameter contains records for infotype 1029. Its structure is thesame as that of P1029. Description This parameter contains records for infotype 1037. Its structure is thesame as that of P1037. Description This parameter contains records for infotype 1018. Its structure is thesame as that of P1018. Description This parameter contains records for infotype 1015. Its structure is thesame as that of P1015. Description This parameter contains records for infotype 1003. Its structure is thesame as that of P1003. Description This parameter contains records for infotype 1002. Its structure is thesame as that of P1002. Description This parameter contains records for infotype 1013. Its structure is thesame as that of P1013. Description This parameter contains records for infotype 1038. Its structure is thesame as that of P1038. Description This parameter contains records for infotype 1019. Its structure is thesame as that of P1019. Description This parameter contains records for infotype 1009. Its structure is thesame as that of P1009. Description This parameter contains records for infotype 1051. Its structure is thesame as that of P1051. Description This parameter contains records for infotype 1032. Its structure is thesame as that of P1032. Description This parameter contains records for infotype 1014. Its structure is thesame as that of P1014. Description This parameter contains records for infotype 1040. Its structure is thesame as that of P1040. Description This parameter contains records for infotype 1017. Its structure is thesame as that of P1017. Description This parameter contains records for infotype 1005. Its structure is thesame as that of P1005. Description This parameter contains records for infotype 1008. Its structure is thesame as that of P1008. Description This parameter contains records for infotype 1047. Its structure is thesame as that of P1047. Description This parameter contains records for infotype 1048. Its structure is thesame as that of P1048. Description This parameter contains records for infotype 1001. Its structure is thesame as that of P1001. Description This parameter contains records for infotype 1006. Its structure is thesame as that of P1006. Description This parameter contains records for infotype 1031. Its structure is thesame as that of P1031. Description This parameter contains records for infotype 1039. Its structure is thesame as that of P1039. Description This parameter contains records for infotype 1027. Its structure is thesame as that of P1027. Description This parameter contains records for infotype 1016. Its structure is thesame as that of P1016. Description This parameter contains records for infotype 1004. Its structure is thesame as that of P1004. Description This parameter contains records for infotype 1007. Its structure is thesame as that of P1007. Description This parameter contains records for infotype 1025. Its structure is thesame as that of P1025. Description This parameter contains records for infotype 1045. Its structure is thesame as that of P1045. Description This parameter contains records for infotype 1050. Its structure is thesame as that of P1050. Description This parameter contains records for infotype 1033. Its structure is thesame as that of P1033. Description This parameter contains records for infotype 1011. Its structure is thesame as that of P1011. Description This parameter contains records for infotype 1001 with additional dataPAD48. Its structure is the same as that of P1001 with substructurePAD48 in the additional data field. Description This parameter contains records for infotype 1001 with additional dataPAD47. Its structure is the same as that of P1001 with substructurePAD47 in the additional data field. Description This parameter contains records for infotype 1001 with additional dataPAD50. Its structure is the same as that of P1001 with substructurePAD50 in the additional data field. Description This parameter contains records for infotype 1001 with additional dataPAD44. Its structure is the same as that of P1001 with substructurePAD44 in the additional data field. Description This parameter contains records for infotype 1001 with additional dataPAD21. Its structure is the same as that of P1001 with substructurePAD21 in the additional data field. Description This parameter contains records for infotype 1001 with additional dataPAD27. Its structure is the same as that of P1001 with substructurePAD27 in the additional data field. Description This parameter contains records for infotype 1001 with additional dataPAD63. Its structure is the same as that of P1001 with substructurePAD63 in the additional data field. Description This parameter contains records for infotype 1001 with additional dataPADXN. Its structure is the same as that of P1001 with substructurePADXN in the additional data field. Description This parameter contains records for infotype 1001 with additional dataPAD31. Its structure is the same as that of P1001 with substructurePAD31 in the additional data field. Description This parameter contains records for infotype 1001 with additional dataPAD22. Its structure is the same as that of P1001 with substructurePAD22 in the additional data field. Description This parameter contains records for infotype 1001 with additional dataPAD23. Its structure is the same as that of P1001 with substructurePAD23 in the additional data field. Description This parameter contains records for infotype 1001 with additional dataPAD51. Its structure is the same as that of P1001 with substructurePAD51 in the additional data field. Description This parameter contains records for infotype 1001 with additional dataPADD2. Its structure is the same as that of P1001 with substructurePADD2 in the additional data field. Description This parameter contains records for infotype 1001 with additional dataPAD53. Its structure is the same as that of P1001 with substructurePAD53 in the additional data field. Description This parameter contains records for infotype 1001 with additional dataPAD25. Its structure is the same as that of P1001 with substructurePAD25 in the additional data field. Description Information on the message type is included in the data elementdocumentation: Message type> This table contains the messages that are returned when the method isaccessed.Value range Type,,ID,,,,Number,,,,Message,,,, E,,,,B1,,,,536,,,,,,Currency amount & & in field & could not ,,,,,,,,,,,,,,be converted E,,,,B1,,,,537,,,,,,& initial, currency amount & in & was ,,,,,,,,,,,,,,transferred without currency A,,,,B1,,,,546,,,,,,No country key found for ISO code & in ,,,,,,,,,,,,,,field & A,,,,B1,,,,547,,,,,,No currency key found for ISO code & in ,,,,,,,,,,,,,,field & A,,,,B1,,,,548,,,,,,No unit of measure found for ISO code & ,,,,,,,,,,,,,,in field & A,,,,B1,,,,549,,,,,,No language key found for ISO code & in ,,,,,,,,,,,,,,field & E,,,,5-,,,,010,,,,,,Allowed operators: I(nsert), U(pdate), ,,,,,,,,,,,,,,D(elete) E,,,,5-,,,,101,,,,,,Object is locked ,,,,,,,,,,,,,,(plan version &, obj.type &, obj.ID &) I,,,,5-,,,,102,,,,,,Object is locked by T77TR (segment &) I,,,,5-,,,,103,,,,,,Object/infotype/subtype is locked ,,,,,,,,,,,,,,by T77TR (segment &) E,,,,5-,,,,104,,,,,,No authorization for object E,,,,5-,,,,105,,,,,,Object &, &, & does not exist: infotype ,,,,,,,,,,,,,,cannot be created W,,,,5-,,,,105,,,,,,See above E,,,,5-,,,,106,,,,,,Database update not possible, ,,,,,,,,,,,,,,data record &, RC & I,,,,5-,,,,107,,,,,,Relationship starting from & not possible, ,,,,,,,,,,,,,,because & does not exist E,,,,5-,,,,108,,,,,,Infotype & cannot be updated on database E,,,,5-,,,,110,,,,,,No entry in HR_INFOTYPE_HEADER for ,,,,,,,,,,,,,,infotype & for object &, &, & E,,,,5-,,,,111,,,,,,No entry in HR_OBJECT_HEADER for ,,,,,,,,,,,,,,object &, &, & E,,,,5-,,,,112,,,,,,Object &, &, & not created; not all ,,,,,,,,,,,,,,parent infotypes exist E,,,,5-,,,,113,,,,,,No data available for creating/changing ,,,,,,,,,,,,,,object &, &, & E,,,,5-,,,,120,,,,,,In infotype &, required field & ,,,,,,,,,,,,,,does not contain an entry (&) Other messages> This list does not include messages that can be displayed when data isvalidated before data records are created for HR master data andorganizational management. |