on 09-08-2014 8:02 PM
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
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
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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
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
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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
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
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
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.