Error message by IDOC not descriptive during posting failure

[Former Member]

Hi team,

I am trying to load material master using MATMAS03. However, during failure , the error just indicates - "Application document not posted; Messages were triggered when processing material master data". I have to go to TCode SLG1 to check the details behind the failure. Is there any way to get the detailed error message.

Regards,

Binu Pillai

[Former Member]

Hi team,

I am trying to load material master using MATMAS03. However, during failure , the error just indicates - "Application document not posted; Messages were triggered when processing material master data". I have to go to TCode SLG1 to check the details behind the failure. Is there any way to get the detailed error message.

Regards,

Binu Pillai

[Former Member]

I dont think so. This is design. If you look at the standard code you will see that after the main FM call to create/update material master, the logs are simply written to SLG1.

Personally I think this is correct in this case as there will be a lot of messages raised. Each of these messages cannot/should not be written as a status record to the idoc.

You could write a separate program that can read the status record of the idoc to find the corresponding SLG1 transaction id and read data from the same and display as report output if required.

V.

[prakashsaurav]

You have just given basic type and expecting answer on this.

Anyhow as Vikram mentioned above standard works as it  is.

So please check if you are using standard message type and call ,then try to find exit and see if you can get the desired error message in there and if yes then you can update error message for yourself. 

And if you are hitting custom code for processing then you are the king do whatever your requirement ask.

But again as Vikram pointed out there is no need update multiple  message and make it more confusing.

You can decide based on your need.

[Former Member]

Basically, I am quite new to IDOC. Now, I checked STATXT field in EDIDS table. It actually contains the message as I have mentioned in the post. However, when i check the below thread, I can see it is possible to have the STATXT field to have descriptive error message.

What I am trying to understand is, if this is related to authorization settings?

[atul_mohanty]

Check the details in WE02 transaction or go to EDIDS table put the IDOc number and status as '51'

and check field STATXT, STAPA1, STAPA2, STAPA3, STAPA4

[Former Member]

Hi Atul,

As I have mentioned, I have already checked the field STATXT in the EDIDS table. It just has the message "Messages were triggered when processing material master data" for status code 51. This does not reveal anything regarding the failure. The only way I have is to go to SLG1 T-Code to get it. What i am trying to understand is, is it the limitation of standard IDOC?

[Former Member]

It depends on how you see it. In my personal opinion this is not a limitation but the design as its is intended to be.

In any case if this does not satisfy your requirement you should see if there are any exits available once the logs are written. If you re able to find one, you should be able to use the same. However the difficulty would be to to filter the right message to be added to the status record. If there are multiple 'E' messages, how would you determine which of the message describes the problem with the material creation?

V.

[atul_mohanty]

Hi Binu - If the message you are seeing as a general message, then the IDoc processing do not capture the exact message rather the general message.

In that case if you want to see the exact message / error, if you are in development system ( if not replicate the issue to dev system) and use WE19 transaction and put the break point in the associated inbound function module and check further.

Also try to post the same data through MM01 transaction and see the errors.

[Jelena_Perfiljeva]

In a way - yes, it's a limitation of IDoc status records. You get only one entry with error status and a generic error message. I'm guessing in this case the system might actually be doing you a favor because application log is normally used when there are multiple messages possible. I.e. instead of stopping the whole process at the first error, it might run a bit further to check if there are more issues. That's just my guess though. In other scenarios there is a more descriptive message, although not always it gives you a clue to the actual issue. IDoc status messages are somewhat of enigma in SAP, from what I find.