Scenario specific configuration and Commit fault: ASJ.ejb.005043

[Former Member]

Hi All,

I have noticed a strange issue w.r.t few outbound idocs. The Idocs fail with Commit fault: ASJ.ejb.005043 (Failed in component:sap.com/com.sap.aii.ad error even though the configuration is perfectly fine in ECC and PI.

However it works perfectly fine the moment we use the below Advanced settings instead of Global Configuration:

Assuming we have 50 different outbound Idoc/Message types, everything works perfectly for 49 but fails only for 1 idoc type. Can someone explain the reason behind this?

Regards,

Vishal

[former_member201275]

Hi Vishal,

Please would you be so kind as to let me know if you managed to solve this problem in the end, and if so how?

I have exactly the same problem and have been struggling for 2 weeks now to try and fix this!

Thank you kindly in advance and regards

Warren

[Former Member]

Hi,

you have this kind of error in sm58 when the IDoc sent has no matching condition in the ICO or RD (if you have a dual stack system but you are using a AAE port).

You can face the same issue also if the metadata of the IDoc in PI/PO system are not update.

Please check the rules on your receiver and upload again the metadata using this page: http://host:port /webdynpro/dispatcher/sap.com/tc~lm~itsam~ui~mainframe~wd/FloorPlanApp?applicationID=com.sap.itsam.mon.xi.idoc

BR

Nicholas

[PRAGSMATIC]

This worked for us

[iaki_vila]

Hi Vishal,

Check this note

1952406 - "Commit fault" error in SM58 transaction when sending IDOC from backend system to PI sender Java IDOC adapter

Regards.

[former_member182412]

I don't think it is adapter specific identifiers because when he resent the IDoc with scenario specific configuration and IDoc received successfully, i think there was temporary connection problem but when he check in log viewer he will get exact error why it failed in the first place.

[former_member182412]

Hi Vishal,

Then check in the log viewer for exact error in NWA. Filter by application and the time. (filter the time when you the error in SM58)

I think it is temporary error.

Regards,

Praveen.

[former_member182412]

Hi Vishal,

• Global configuration is the message will be stored in the database after receiver determination which is staging MS step.
• Your case the message failed before mapping which means receiver determination step like cant find the receiver or between ECC and PI connectivity.
• If the message failed before mapping then the transaction will be roll back and the error is shown in SM58 transaction.
• This is what happened when you using global configuration.
• When you apply scenario specific configuration and when you store the message at staging step BI which means you are store the message version immediately when message enters into PI.
• That is why the message was successfully reached to PI but it will fail in PI at receiver determination step, you can check this in message monitor.

Regards,

Praveen.

[Former Member]

Hi Praveen,

I forgot to mention that the messages were processed successfully in PI as well 🙂 That's why I am finding it strange

Regards,

Vishal