Start of Content Area

Procedure documentation Generating Partner Profiles of the OM Distribution Model  Locate the document in its SAP Library structure

Use

Perform these procedures both in the HR system and in the receiving system of the organizational management distribution model (OM distribution model).

Caution

Choose serial background processing for the incoming processing. In this way, you can avoid two background jobs being run in parallel, which can easily cause update problems.

If the system displays an error message in transaction WE02, saying that the object was locked, check the background processing of the IDocs.

Procedure

...

       1.      Choose Environment Generate Partner Profile in transaction BD64.

The system displays the Generating  Partner Profile screen.

       2.      Specify the model view and the receiving system.

       3.      Under inbound parameters, choose the option Trigger by Background Program.

Note

To be able to use background processing, you must then schedule the report RBDAPP01 for the message type HRMD_ABA in all receiving systems. The IDocs of the OM model are updated sequentially by the background processing. This avoids lock problems.

       4.      Check the result log for the partner profile generation in the sending and receiving systems.

     If message type HRMD_ABA was not generated correctly in the sending system, adjust the outbound processing in transaction WE20.

                                                  i.       On the Partner Profiles screen (transaction WE20), choose the partner profile of the sending system under Partner type LS.

                                                ii.       Check whether message type HRMD_ABA is listed under Outbound parameters.

If not, add it with Create Outbound Parameter. On the Partner Profiles: Outbound Parameters screen, you can specify the following data:

      Outbound Options tab page: Message type: HRMD_ABA, process code: HRMD, syntax check, triggered by background program

      Postprocessing tab page: Allowed Processor: Type: US, Processor: User name of the administrator, Language: EN

     If message type HRMD_ABA was not generated correctly in the receiving system, adjust the inbound processing in transaction WE20.

...

                                                  i.       On the Partner Profiles screen (transaction WE20), choose the partner profile of the sending system under Partner type LS.

                                                ii.       Check whether message type HRMD_ABA is listed under Inbound parameters.

If not, add it with Create Inbound Parameter. On the Partner Profiles: Inbound Parameters screen, you can specify the following data:

      Inbound Options tab page: Message type: HRMD_ABA, process code: HRMD, syntax check, triggered by background program

      Postprocessing tab page: Allowed Processor: Type: US, Processor: User name of the administrator, Language: EN

 

 

End of Content Area