IDOC's status Distribution Unconfirmed

[Former Member]

Hi,

whatever the changes we are performing in Central system and the changes are getting reflected in the child system.

But the problem is when we check in SCUL transaction the IDOC's are showing as unconfirmed status.

As per my knowledge if the changes get reflect in child system then the IDOC will not be display in SCUL.

But this is a strange problem which is showing as Unconfirmed status...

Please provide me the solution for it...

SV

[Former Member]

What are the IDoc error messages in the target system?

What are the messages in SCUL in the CUA master?

[Former Member]

If the IDOC status is unconfirmed, I am sure it means there is something which is not getting updated. Are you sure everything in all the tabs of SU01 is getting updated in the child system.

I am sure it cannot be user group or Printer because if the user is group is not there in the child system or the printer is not there then it will give you error.

I remember vaguely I faced this issue, when everything looked okay ( atleast things that mattered like roles and profiles ) looked okay but the status was unconfirmed. Check if all the parameters in SU01 parameter tab are passing to child system and other smaller things.

Did you checked the unconfirmed idocs in BD87.

Also check SAP note 333441 for Tips for Problem analysis.

[Former Member]

Sourabh,

Thanks for your valuable inputs.....And your answer was very realistic to my problem....

U have provided the route case of it and can I know what is the solution for it...

As when there is no user group or account number I mean blank in child system in that case it is showing as unconfirmed status but the changes get reflected to the child system...

Then can I know is there a specific solution for it...

if so please help me out...

SV

[Former Member]

....see you have exactly same user groups (SUGR ) in all systems..central and child. similarly for Account # ...if there is uniformity in child systems with central systems....these issues fade away mostly

[Bernhard_SAP]

Hi Sukumar,

if the idocs are processed successfully in the target system and only the SCUL-status is 'unconfirmed' this can have some causes:

a)Most common: the RFC-connection form Target system to CUA central system does not work correctly, for instance wrong client,wrong system,user cannot log in, etc. Please test the connection in SM59. Perform also a remote login attempt (you need a diealog user for that) to see, where the conenction points to (is it really the central system?). Check also if the user used in the connection can log on to the central system.

b) missing authorization of the RFC user from the connection child->central system

For a test simpyl assign sap_all temporarily and check if it works then.

If not, use ST01 for analyzing, which authorization is missing for the RFC-user.

In most cases these 2 steps solve such issues you face.

b.rgds,

Bernhard

[Former Member]

> Please test the connection in SM59. Perform also a remote login attempt (you need a diealog user for that) to see, where the conenction points to (is it really the central system?).

A small comment: A SERVICE type user would be a better temporary match for this, otherwise you might be forced to change the password in the target and the authority-checks are very slightly different.

Cheers,

Julius

[Former Member]

that happens to me often when i use mass update using SU10. so i go to SCUL, select user id and the distribute. it sends idoc again. i keep doing it until they are all successful unless if there are specific errors occured. i think this happens because of not enough resources available. or in lament term i would say "clogged up".

Edited by: Friend on Feb 5, 2009 6:27 PM