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

Error in inbound IDOC

Former Member
0 Likes
881

hi gurus,

i am trying to send material master data from IDES to ECC. From IDES data sent perfectly. but in ECC the inbound IDOC showing a error message as 'STATUS 56'. What does it mean and how to solve this eror. pls help me .thanks in advance,

santosh.

1 ACCEPTED SOLUTION
Read only

Former Member
0 Likes
862

Status 56 means that the IDOC could not be processed in ECC. To be able to correct the issue you need to find out what caused the error.

Go to transaction 'WE02', select the IDOC in question and look at the status records. Most of the time you'll find a long text that describes what caused the error.

If that doesn't help your last resort would be to debug the IDOC while it runs in and setting a breakpoint at statement 'message' to see what caused that error.

Hope that helps,

Michael

Status 56 means that the IDOC could not be processed in ECC. To be able to correct the issue you need to find out what caused the error.

Go to transaction 'WE02', select the IDOC in question and look at the status records. Most of the time you'll find a long text that describes what caused the error.

If that doesn't help your last resort would be to debug the IDOC while it runs in and setting a breakpoint at statement 'message' to see what caused that error.

Hope that helps,

Michael

6 REPLIES 6
Read only

Former Member
0 Likes
862

Is there a specific error message in the idoc status record?

Read only

Former Member
0 Likes
863

Status 56 means that the IDOC could not be processed in ECC. To be able to correct the issue you need to find out what caused the error.

Go to transaction 'WE02', select the IDOC in question and look at the status records. Most of the time you'll find a long text that describes what caused the error.

If that doesn't help your last resort would be to debug the IDOC while it runs in and setting a breakpoint at statement 'message' to see what caused that error.

Hope that helps,

Michael

Read only

0 Likes
862

Hi,

I saw the error message. i got where the mistake went.

actually in IDES there is extension to basic idoctype MATMAS04 and this is not there in ECC, so the maping has not been done coreclty. Now what to do, how to rectify this error.

thanks,

santosh.

Read only

0 Likes
862

Basically you have three options:

(1) use MATMAS04 to publish the data from IDES instead of the extension (only feaseable if you don't need the data in the added extension)

(2) create the same extension in ECC (you would have to add code in the userexit to handle the infos coming in in the extension)

(3) hook into a user exit right at the beginning of the IDOC input function module and remove the segments that were added by the extension.

Regards,

Michael

Read only

0 Likes
862

Hi Michael,

Thanks for your answer,

but actually i am sending material from BD10. There just i am giving message type as MATMAS. so its automatically taking the added segement also. what to do if i dont watn that extra segment, and if i only want to send basic MATMAS04 data. where should i do the configuration for that one.

thanks,

santosh.

Read only

0 Likes
862

The settings which extension is to be used when sending an IDOC is done in your output control customizing.

You might want to check with your functional team, because that type of customizing is usually done by them.

Regards,

Michael