Application Development and Automation Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
cancel
Showing results for 
Search instead for 
Did you mean: 
Read only

Inbound Idoc errors

Former Member
0 Likes
1,608

Hi,

Inbound Idocs (custom idoc type) , I am getting Idoc status '51' with custom message Material Number 111133 not exists in system,however segment in the Idoc contains different Material Number 233325 it should not display this error message as per code it should validate for segment material number .Nearly 12000 idocs are failed with same error message "Material Number 111133 not exists in system".

We are using custom class to update the status record(Static attributes) for the Idocs.

When I reprocess the single Idoc which contains error in t.code BD87, the document posted successfully with status '53'

Whether it is possible that same memory space(Static attributes)is used for all the Idocs and why the same error message is

displayed in all Idocs.

Kindly help.

Thanks,

Venkat

1 ACCEPTED SOLUTION
Read only

nabheetscn
SAP Champion
SAP Champion
0 Likes
865

Please make sure you have refreshed and cleared the respective tables,..

Nabheet

5 REPLIES 5
Read only

nabheetscn
SAP Champion
SAP Champion
0 Likes
866

Please make sure you have refreshed and cleared the respective tables,..

Nabheet

Read only

Former Member
0 Likes
865

Hi Nabheet,

Thanks for your reply.

We reprocessed 3 Idocs at same time in BD87 in different session , all the 3 idocs posted successfully.

Sap will allocated different memory space for each execution then how it possible display the same error in the idoc?

Thanks,

Venkat

Read only

0 Likes
865

You need to refresh the internal table that goes to create the status records after posting each IDoc. This clearly looks like a carry over bug.

The moment you put a error record in status table, SAP considers the IDoc to be in error.

That is why you are not getting this error when you are processing individual IDocs through BD87. In fact you should be even able to post those IDocs in 51 status by reprocessing them in BD87. This goes to show that the status internal table got the error message on one of the IDocs, but since it was not refreshed the error got carried over to IDocs that otherwise are error free.

Read only

Former Member
0 Likes
865

As per my understandin you are using a custom process code to update the entries fro IDOC

Please check in debugging if your code is passing this function module for processing.

Lalit.

Read only

Jelena_Perfiljeva
Active Contributor
0 Likes
865

The wording 'Material Number ... not exists in system' doesn't sound like a standard SAP message, so my guess is it's a custom message coming from a user exit and such. Double-click on the message and you'll see the message class and number. You can use 'where used' in SE91 or debugger watchpoint to see where the message occurs exactly.

P.S. When posting the IDoc questions you might want to share at least the IDoc/message type.