CUA - IDOCS - DISTRIBUTION UNCONFIRMED STATUS

[Former Member]

Hi,

I have seen the strange issue in CUA IDOCs with respective of a child system...

That is, If i do the user maintenance with respective of the child system in the central system and save it.

1) then the system is generating the IDOC's for central and the respective child systems.

2) The changes are getting reflected to the respective child system.

But when i check SCUL in CUA, still it is showing as DISTRIBUTION UNCONFIRMED STATUS

I have verified the below things

A) OUTBOUND and INBOUND jobs in central and Child are working fine.

B) IDOCS are getting posted in child system with status 53

C) RFC connection is fine

D) Partner profiles are fine

E) SCUA - showing green

NOTE:

The issue is happening only for one system -client and all other systems and clients were working fine without any issue

Kindly let me know your opinion

Sv

[sdipanjan]

>

> NOTE:
> 
> The issue is happening only for one system -client and all other systems and clients were working fine without any issue

Hi,

Please follow the [SAP Note 169538 - CUA: Too many unconfirmed users in the log|https://websmp230.sap-ag.de/sap%28bD1lbiZjPTAwMQ==%29/bc/bsp/spn/sapnotes/index2.htm?numm=169538].

Is the RFC from that Child system to Central system is working properly?

Basically this kind of Unconfirmed status happens when the IDoc processing get stuck due to too many IDoc generation. You can schedule a job in that child system for the report RDBPROCESS to process the unprocessed IDocs in a certain interval of times.

You may also want to check the changes happened in SCUL by [SAP Note 632486 - Improvements to transaction SCUL|https://websmp230.sap-ag.de/sap%28bD1lbiZjPTAwMQ==%29/bc/bsp/spn/sapnotes/index2.htm?numm=632486].

Regards,

Dipanjan

[Former Member]

Hi Dipanjan,

Sorry for the late reply.

basically IDOC is geeting processed in the child systems and the required changes are getting updated in the user profile.

As per the SAP NOTE 169538

Since changes do not need to be distributed in the central system via ALE (they were made directly in the central system), a confirmation message, which reconverts the status, does not take place

Where should i check this return confirmation to the central system from source or child system.?

Kindly help me on this...

[Bernhard_SAP]

Hi,

the confirmation from the child system is sent to the central system by direct rfc (no idoc!). So I think you can check the sending of confirmation in SM58. If you don't get the confirmation in the central system (scul stays grey), normally the rfc connectionf rom child to central is not defined correctly, or the assigned rfc-user does not have sufficient rights (in this case switch on st01 authorty-trace for the rfc-user and/or check st22 dumps reg. auth.-issues).

b.rgds, Bernhard

[Former Member]

Hi Sukumar,

This thread is almost 3 years old but did you find a fix for this issue? I am also facing the same issue with 2 child systems.One of the system was working fine, was sending the acknowledgements to CUA system but today somehow the acknowledgements are not reaching and hence getting stuck in SCUL.

Would really appreciate if you can share the fix.

Thanks,

Manisha

[Former Member]

Hello Folks,

I encountered the same issue and raised an OSS with SAP. SAP got back saying that this issue occurs when the IDocs are stuck in the "Transaction Recorded" status in SM58 due to processing of large amounts of tRFC calls. Please refer to note 1548446 to fix this issue. On a high Level, Make sure the Registration for the child system is active for both tRFC and qRFC in Output Scheduler (SMQS)

Hope this helps!

Thanks

Surakshith

[Former Member]

This message was moderated.