Username Change in Incoming IDOC

[venkatasunil16]

Hello SAP Experts ,

For incoming IDOC from CPI , the username is not  getting changed from custom user name  (R_xxxx) to WF-BATCH at status 62 (IDOC passed to application) with the processing program SAPLBD20 . Due to that  custom user ID ( System User type ),  Authorization is failing to create the document . This is happening all of sudden.

Expectation is that it should have WF-BATCH as user .

I have checked all the possibilities but couldn't find what could be the cause of this issue . Please let me know if this can be  due to any enhancement or IDOC configuration for that Partner profile/ message type. 

[Sandra_Rossi]

This user is the one which has generated the message. How do you run the integration of the IDoc? (job with program RBDAPP01?) Change the user running this integration.

[venkatasunil16]

IDOC is triggered immediately . I already checked, there is no batch job running to process the incoming IDOC with the custom USER ID .

[venkatasunil16]

Sorry for the late response . We got the root cause why this was happening . In transcation OYEA , Start without event linkage option was checked by some project team in quality server . We unchecked this option and IDOC's are routing through WF-BATCH user and getting success .

[Sandra_Rossi]

Anyway, in your case, there's an ABAP process with user R_XXXXXX which integrates the IDoc and runs it because of your WE20 settings). So, look in CPI customizing about the integration of the IDoc (adapter and so on).

[venkatasunil16]

IDOC is triggered immediately . I already checked, there is  no  batch job  running to process the incoming IDOC  with the custom USER ID .

Deleted this message as i already responded same earlier. 

[Sandra_Rossi]

To delete this answer, you may edit and indicate "deleted" or something like that.

[raymond_giuseppi]

Did you check (WE20) the Partner Profile Inbound Parameters

• e.g. trigger by background program, user of the (SM36) scheduled job

[venkatasunil16]

Hi Raymond,

It is trigger immediately  . Not through RBDAPP01 program.