Roles not replicated from CUA

[Former Member]

Hello,

We are facing problem, that roles are not replicated from CUA to system. because is the Idocs were not processed from CUA to child system.

So we have to launch SCUL transaction manually .

Is there any suggestion to solve this problem ?

[Former Member]

What was the error message for the unsuccessful IDOCS? Check if some one changed the system user password that is used for Idoc processing. Is there any system refresh that happened recently?

[Former Member]

Hi,

We didn't get any idoc transfered to child system, that is why we run SCUL transaction.We get that problem only with SRM child system, for ECC we have not this issu

Cordialy

[Former Member]

Hi Mou,

If changes are getting reflected automatically in child system (SRM) after some delay or re-distributing them from SCUL, it does not seem to be CUA configuration issue. You can try to run BDM5 t-code for SRM once and see if there is any improvement.

If this does not help, you can reach out to basis team for delayed distribution/processing of idocs.

Thanks

[Bernhard_SAP]

1. step for a structured approach: check idoc status in central system.

depending on that findings further steps:

check outbound processing settings (dialog/batch), batchjob settings, ale setup.

(un der the precondition, that resending in scul works fine.

b.rgds, Bernhard

[Colleen]

what IDOC status do you  have in SCUL? You need to track your CUA configuration down to see if it's still yet to be sent out of CUA, received/processed in SRM and finally confirmation sent back to CUA to switch the IDOC to yellow/red/green instead of white

For CUA, I usually sit in BD87 checking IDOCs. How you investigate this will depend on your configuration (ALE Model, WE02 (?) Partners and if IDOCs are processed immeidately or in batch). Is the RFC a trusted connection for named user or is it under a system user (and does the user have authorisation and is valid)

if you have checked all potential then you can attempt to use SCUL to reprocess some IDOCs. If not, you can then look at using program RSCCUSND to resend users

Regards

Colleen

[jinesh_jayan]

Hi,

Can you check the logical system name of the child system in SCC4?

It should be <SID>CLNTXXX for CUA to work.

Regards,

Jinesh Jayan

[radhakrishnan_r]

Hello,

Check your partner profile is properly distributed and all the changes are replicated in child system otherwise you would face this kind of issue

Regards,

RK

[Former Member]

Hi Mou,

Is this issue solved? If not, you can try to manually process the inbound idocs from child system using BD87 t-code.

Thanks,

Santosh