lsmw using bapi

[Former Member]

WHILE DOING A CONVERSION using lsmw FOR TRANSACTION PA30 USING BAPI- BAPI_HRMASTER_SAVE_REPL_MULT IN THE STEP OF create idoc overview I am getting error for each of the five segments what I am using.

error says like "No entry in HR_INFOTYPE_HEADER for infotype for object ,P ,92000021"

where errors are same for all segements.

Kindly suggest how to go on.

i tried adding header and giving object type and plan_ver.

please give some solution for this isuue.

Thank You

Regards

Rendeep

[abdul_hakim]

Hi,

Check whether you have passed the correct values for the header detls.

Check whether mapping has done correctly and other idoc settings..

Regards,

Abdul

[Former Member]

Hi,

Pass values to the BAPI as below:

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 an Accounting System, you are advised for technical reasons not to use the BAPI because synchronous validation would lead to a COMMIT. This would prevent 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 by SAP and must not be modified. It is used to create personnel numbers. Infotype 0000 (Actions) is then overwritten without validation in accordance with the transferred parameters.

Infotype 1000 is also created by the BAPI without validation. Infotype 0003 (Payroll Status) is recreated in accordance with the logic for creating HR master data.

If infotypes have time constraint 1, you must ensure that the data records do not contain gaps.

The 'Changed on' and 'Last changed by' fields in all of the infotypes contain the date on which the BAPI was accessed, and the user used to access the BAPI in the target system (RFC user).

Infotypes must not be related to dynamic actions in the system to which data is imported.

To ensure that actions are displayed consistently, you must deactivate the 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 the error, you can import data to the R/3 System using the 'HRMaster_Save_Repl_Mult' function module instead of the BAPI. The data records for error analysis are displayed online using report 'RHALEBAPIPROOF'.

The data is validated before it is imported, which can lead to runtime problems, especially if large amounts of data are imported. One way of avoiding this problem, for example, is by reducing the size of the dataset for each BAPI access.

Hope this helps....

Lokesh

Pls. reward appropriate points