cancel
Showing results for 
Search instead for 
Did you mean: 

Non-updated Idocs found in Source System

Former Member
0 Kudos

Hi All,

Our Process chains are regularly failing at infopackage level with Non-updated Idocs found in Source System issue. But when we Repeat the process type, the job completes successfully.

Please let me know how we can resolve this issue to have our process chains running smooth.

Points will be assigned

Rgds

AP

Accepted Solutions (1)

Accepted Solutions (1)

former_member181964
Active Contributor
0 Kudos

Dear AP

chech the following link.

Thanks

reddy

Answers (3)

Answers (3)

Former Member
0 Kudos

You may not have enough Dialogue processes set up in R/3 to handle your infopackage requests.

See OSS Note 561880.

desgallagher
Contributor
0 Kudos

Hi,

Please check if the note 901878 is relevant for the problem you have.

Best Regards,

Des.

Former Member
0 Kudos

Hi

When your load fails.

Check that both the Extraction & the Processing sections in the request monitor are green. If so, then:

1. Right-click on the yellow Info IDoc message and select "Manual update" from the popup menu

2. Confirm the 'IDOC in staus 64' message

3. Hit F8

4. Return to the monitor

This works for both yellow and red loads as well as for both transaction and master data loads

Also check

Hope this helps

Regards

Shilpa

Former Member
0 Kudos

thanks for your responses Reddy & Shilpa.

But I am looking for a permanent resolution for the issue. When we get this issue we don't even need to update IDOCS manually; just by repeating the process type the InfoPack is getting completed.

Moreover the issue is not just with one infopack but several of them. Manually updating IDOCS for each and every infopack would take lot of time.

I want to know what might be the root cause of such an issue. Any Ideas?

Rgds

AP