Enabling Principal Propagation for ABAP Messaging Components 

The context of the user to be propagated is impersonated again after a message restart or during batch processing only if principal propagation is enabled for the involved messaging component.

The ABAP messaging components are the Integration Server and the Integration Engines of the sender and receiver systems executing ABAP proxies. To enable principal propagation on these messaging components, perform the following steps on each component:

...

...

       1.      Install the ABAP kernel patch level 76.

       2.      From your SAP Easy Access user menu, choose Exchange Infrastructure ® Administration ® Integration Engine – Administration ® Configure Principal Propagation and activate principal propagation.

This executes the report RSXMB_CONFIG_PP. This report creates the type 3 RFC destination SAPXIPP<clnt>, where <clnt> represents the three-digit client of the respective messaging component. In addition, it generates the system user XIPPUSER with a random password and the role SAP_XI_APPL_SERV_USER.

If you use a central user administration, you must create this RFC destination and user manually. For the RFC destination, specify the following values:

■       Name: SAPXIPP<clnt>

■       Connection type: 3

■       Client: <clnt>

■       User: XIPPUSER

■       Password: <password of XIPPUSER>

Leave the technical settings Target Host and System Number empty.