on 06-06-2018 3:23 AM
Hello B2B Experts,
I am testing inbound EDI ANSI X12 with scenario and steps as described in
https://blogs.sap.com/2012/09/27/b2b-edi-inbound-step-by-step-configuration/ but getting below error. The EDI Separator Receiver channel was able to parse the EDI file successfully but getting error:
Message could not be forwarded to the JCA adapter. Reason: com.sap.aii.adapter.ediseparator.ra.integration.ChannelNotFoundException: No matching sender channel found to dispatch X12 message with transaction set 810, Version / Release / Industry Identifier Code 004010, interchange control number 00793597, interchange receiver id 2222 and interchange sender id 1111
I looked at all the threads relevant to this error but could not find any specific message that was resolved with this error. Has anyone encountered this error and help with how it was resolved?
Hi,
Please check if you have done below things.
1.Check if unique identifier defined the EDI matches with the what you have defined in your sender EDI separator channel.
2.If you have already configured those things correctly try to do JAVA restart.
Best Regards,
Sugeet.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello,
Sender/Receiver identifiers have been specified as they are from EDI file but getting error -
EDI Separator Receiver Channel -
Message could not be forwarded to the JCA adapter. Reason: {0}
MP: exception caught with cause javax.resource.ResourceException
Exception caught by adapter framework: {0}
Transmitting the message to endpoint <local> using connection File_http://sap.com/xi/XI/System failed, due to: com.sap.engine.interfaces.messaging.api.exception.MessagingException: javax.resource.ResourceException
Can you provide any screenshot of Sender and Receiver Separator adapter module config/parameters?
EDI Separator Sender Channel -
Cannot deliver message: com.sap.aii.af.lib.mp.module.ModuleException: Sender Channel 'EDIseparatorSender' 'ID ...' Catching exception calling messaging system. Will deliver negative 997 if requested.
Thanks!
Hi,
this type of error is usually thrown in two cases:
1) There is no sender EDISeparator channel with ANSI X12 message protocol for 810 messages (wildcarded interchange receiver and sender id)
2) There is a sender EDISeparator channel with ANSI X12 message protocol for 810 messages but not with the same interchange receiver or sender ID.
Best regards,
Mate
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello,
1) There is no sender EDISeparator channel with ANSI X12 message protocol for 810 messages (wildcarded interchange receiver and sender id)
- I have specified sender as EDI Separator Sender and Receiver as XML file receiver.
2) There is a sender EDISeparator channel with ANSI X12 message protocol for 810 messages but not with the same interchange receiver or sender ID.
- I have provided proper receiver and sender ID and qualifiers from EDI file.
Still getting same error. Seems like EDI Receiver channel is not connecting with Separator Sender channel so the EDI conversion from EDI receiver channel is not able to pass EDI to EDI sender channel. Is there any EDI separator comm. channel module configuration needed? I have already specified X12ConvertModule in EDI Separator Sender channel. Do I need to specify Control Key in any Separator comm channel?
Sorry for late reply, here is the screenshot of Sender and Receiver EDI Separator channel. Now I am getting error -
Transmitting the message to endpoint <local> using connection File_http://sap.com/xi/XI/System failed, due to: com.sap.engine.interfaces.messaging.api.exception.MessagingException: javax.resource.ResourceException: The message type can not be determined.
Sender EDI Separator Channel
Receiver Separator Channel
User | Count |
---|---|
86 | |
10 | |
10 | |
9 | |
6 | |
6 | |
6 | |
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.