cancel
Showing results for 
Search instead for 
Did you mean: 

IDOC_AAE sender channel shows Commit fault: ASJ:ejb 005043 [Failed in component error]

Former Member
0 Kudos

Hello All.

We have a scenario IDOC to JDBC [ async-sync] scenario. And we have used Async/sync bridge using request response bean module.

Now the issue is that when IDOC is triggered from ECC it shows Commit fault:ASJ:ejb 005043[failed in component] error in SM58.

And if we click on "execute LUW" option the IDOC message reaches PI and gets processed successfully.

Could you please let me know how to fix this.

Thanks,

Jane 

Accepted Solutions (0)

Answers (3)

Answers (3)

Former Member
0 Kudos

Hello All,

Thank You all so much for all the details.

We have 2 different ECC clients connecting to SAP PI box. Though the RFC destination which i used was available in both the the ECC box, somehow it was not working. So created a new RFC destination setup at ECC side, and modified the inbound RA config values accordingly. And then it worked fine.

Thanks,

Jane

Former Member
0 Kudos

Hi,

Can you please check that your IDoc_AAE has been setup correctly so that ECC can send IDocs to PI?

Please can you also send us the detailed error in  from the logs in NWA?

Also chech that the IDoc does have a receiver in PI.

Regards,

Jannus Botha

Former Member
0 Kudos

Hi Jannus,

I checked the set up. in of the link its mentioned that in RFC destination we need to add the SAP gateway and service details from PI. Currently in ECC side in  RFC destination the sap gateway n service is blank. And in inboundRA properties the localgateway is mentioned as "true'

I tried mentioning the PI gateway and service in RFC destination and triggered IDOC. But it showed error in SM58 as " And IDOC exception has occured"

Thanks,

Tina

Former Member
0 Kudos

Hi Jane,

You can setup IDoc_AAE like in the links below or you can do it in the channel.

The links are the best method but if you need to get connection up and running right away then maybe setup the link between ECC and PI in the channel.

Please see the attached screenshot. If you fill in the connection details on this channel and point it to the ECC gateway so that the program ID is registered there it should also work.

But this is only a temp solution. We can then help you to setup the correct config later.

Regards,

Jannus

Harish
Active Contributor
0 Kudos

Hi Jane,

Please check the below threads

regards,

Harish

Former Member
0 Kudos

Hi Harish,

I have gone through the link . And all the configuration are in place.

Though the message gets processed successfully[when i click on execute LUW in SM58], in PI the IDOC sender channel shows the status as red and the description is " Java Resource Adapter xi/IDOC/RA_/<BusinesssystemNAme>/<Idoc name> could not be started".

Could you please help me with this error .

Thanks,

Jane

former_member184720
Active Contributor
0 Kudos

Did you try restarting the Resource adapter from NWA?

NWA -> Operations -> Systems -> Start & Stop -> Java Applications  search for "com.sap.aii.adapter.idoc.sapjra.inboundRA "

Former Member
0 Kudos

Hi Hareesh,

I did restart the Resource adapter.But still issue exists.

sometimes IDOCs are getting processed and next time same IDOC when i re trigger from WE19 it shows Commit Fault error in ECC SM58.

Thanks,

Jane

Bhargavakrishna
Active Contributor
0 Kudos

Hi Jane,

Did you created JCO RFC provider destination in NWA? if so please remove it.. there should be only one active listener from ECC to PI.

Did you check the RFC destination's.. did you marked both the systems are uni-code?

Clear the cache and try to re-start the server.. it may be helpful..

Thanks

Bhargava Krishna

Former Member
0 Kudos

Hi,

I also faced the similar issue in sm58.

I checked the nwa logs, it was showing details about a different iflow and its channels were stopped.

I undeployed that int.flow and deployed my int.flow and started the chanels.

now its fine.

May be you can try my procedure.

reg, avinash M

Former Member
0 Kudos

Hi Bhargava,

JCO RFC Provider is not created. RFC destination connection test works fine, and is uni-code. But you have mentioned "both the systems are uni-code'. I checked in RFC destination in ECC and its uni-code. Where else i need to check. Please let me know.

Thanks,

Jane

Former Member
0 Kudos

Hi Avinash,

NWA logs shows the following error :

[JRA]Couldn't start ResourceAdapter Servers with properties {jco.server.gwhost=essdev03, jco.server.progid=SAPRDB670POALEFEDEX, jco.server.gwserv=sapxxxx}, cause: JCo server is currently running. Current server state is ALIVE


Global [startApp] operation of application [sap.com/ClonedRA_xi~idoc~RA_~MCK_RDA_D~IDOC_Out_CLMLeadData] failed with errors on server process [2664350].


Thanks,

Jane