Skip to Content
0

Commit fault: ASJ.ejb.005043

Jun 02, 2017 at 11:33 PM

364

avatar image

Hello Expert

I am doing testing my IDOC to JDBC interface .I am triggering the Delivery.Delivery03 idoc from my SAP ECC system . If i trigger around 30 order one time , only 18 order comes in SAP PI and rest 22 order stuck in ECC system , I checked SM58 in ECC system it is showing some error :Commit fault: ASJ.ejb.005043 (Failed in component:sap.com/com.sap.aii.ad)

Can you please help me why all order are not process in SAP PI system.

Regards

P.Singh

10 |10000 characters needed characters left characters exceeded
* Please Login or Register to Answer, Follow or Comment.

5 Answers

avatar image
Former Member Jun 03, 2017 at 12:26 AM
0
Share
10 |10000 characters needed characters left characters exceeded
Priyanka Anagani Jun 05, 2017 at 06:29 AM
0

Hi Pankaj,

Few IDocs are reaching to PI and few are not means, its not an issue with PI configuration. It could be either Data or connectivity issue.

Try to reprocess the failed tRFC message after sometime and if it got processed successfully then it should be a connectivity issue and if its not reprocessed after multiple retries then its a data issue.

Case1 - Connectivity Issue: Check if there is any issue with the tRFC resources. When you reprocess the failed message from tRFC, you'll get the actual error in IDoc sender channel and in NWA Log viewer. Also, taking help from Basis Admin to collet the tRFC trace would help in fixing the issue.

Case2 - Data Issue: Check if you've enabled any inbound validation or conditional receiver determination. Compare the IDoc payload of successful and failed IDdocs and see what's missing.

---Priyanka

Share
10 |10000 characters needed characters left characters exceeded
pankaj yadav Jun 05, 2017 at 08:04 PM
0

Thanks Priyanka for response .

I want to you more explain my issue as per your answer:

case 1:Connectivity Issue :I think there is no connectivity because when i reprocess stuck Order from SM58 via Excute LUW , They process successful from ECC side and received successful in PI system. So i think no issue in Connectivity .

Case2 - Data Issue : Same as per above if they process second time manually from ECC side so no data issue from there side .

I am not sure why not process or filed all message at a time

Please help me if you have any idea.

Regards

P .Singh

Show 3 Share
10 |10000 characters needed characters left characters exceeded

Hi Pankaj!

Did you search NWA logs for any additional details about these errors?

Regards, Evgeniy.

0

HI Evgniy

I have checked in NWA there is no error log for this issue .

0

Hi Pankaj,

You are able to reprocess the IDocs after sometime means its a temporary connectivity issue at the time all Idocs were triggered. It could be because of load or because of lack of system resources. You need to work with system Admin team to collect tRFC trace and analyze.

Till you identify the issue, just to avoid the impact of Idocs getting blocked in tRFC, you can schedule a job to automatically reprocess the tRFc failures. Create a job to execute the standard report "RSARFCEX" which reprocess the SM58 failures and schedule the job frequency as per your business criticality.

--Priyanka

0
avatar image
Former Member Jun 06, 2017 at 10:10 AM
0

Pankaj,

Did you refresh ASI in the IDOC sender BS. In your case the BS of your ECC system. Try it once.

Try to refresh full cache refresh as well- Delta and CPA both.

Thanks,
Apu

Show 2 Share
10 |10000 characters needed characters left characters exceeded

HI Apu

I have refreshed the full cache as well Delta .But still same problem .

Please any one share the response for this issue .

Regards

Pankaj

1
Former Member
pankaj yadav

Did you checked Adapter specific identifier in orresponding BS so that it can update the logical system name as mentioned in SLD.

Thanks,

Apu

0
Anurag Gupta Jan 26 at 05:16 PM
0

This worked for us


Share
10 |10000 characters needed characters left characters exceeded