on 12-04-2012 7:17 PM
Hi,
We have recently installed PI 7.3 and developed a scenario to send IDocs from ECC to PI AAE using IDOC_AAE adapter.
Completed all the steps/configuration as explained by http://scn.sap.com/docs/DOC-31398
When IDocs are triggered from ECC, they are stuck in SM58 with issue "Bean IDOC_INBOUND_ASYNCHRONOUS not found on host".
Please provide your inputs.
Thanks,
Suraj Pabbathi
Hi,
The error you encounter is mentioned in the blog that you used as a reference:
Bean IDOC_INBOUND_ASYNCHRONOUS not found on host
Solution: Please make sure that the user has sufficient authorizations. You need the S_IDOCDEFT (EDI_TCD = "WE30"; ACTVT = "03") authorization.
Make sure the authorization object is assigned to the technical user used by the RFC destination (not to your own user).
Also, you might want to review your overall configuration against some other blog (you know, "four eyes principle") like one of these:
Configuring PI 7.30 Java IDoc Adapter
Regards,
Greg
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Greg,
Thanks for your reply.
As we have also raised ticket with SAP, they have replied to remove additional JCO RFC Provider destination with program name XI_IDOC_DEFAULT_<SID> which is the program name (ProgramID)
also defined in inboundRA.
Reason: InboundRA has its own internal JCo Server which is created and registered when the inboundRA starts.
However we are now hit with another issue: IDoc is stuck in SM58.
JCO_ERROR_SYSTEM_FAILURE: Commit fault: ASJ.ejb.005043 (Failed in component: sap.com/com.sap.aii.adapter.idoc.app, BC-XI-CON-IDO)
IDocReceiverBean in application sap.com/com.sap.aii.adapter.idoc.app.; nested exception is: com.sap.conn.idoc.IDocRuntimeException: No channel found for message
We have created the Communication Channel in PI appropraitely, but unable to make how it is not identifying this channel.
Please provide the inputs.
Thanks,
Suraj Pabbathi
Hi,
We have solved the problem ourselves.
XPI code inspector is awesome to get the trace based on which we understood the issue and resolved it.
For IDoc Communication channel to be identified by the request from Sender System, Sender Agreement need to be in place. Also, Name the IDoc should match with Sender Interface name without any wrappers.
Thanks,
Suraj Pabbathi
User | Count |
---|---|
82 | |
10 | |
10 | |
9 | |
6 | |
6 | |
5 | |
5 | |
4 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.