Skip to Content
Former Member
Aug 04, 2014 at 09:18 AM

EDI Seperator Adapter Issue for Inbound EANCOM Scenario


Hi Experts,

Am using latest service pack and SP12 and patch 5 it seems.

Still am getting same error.

Message could not be forwarded to the JCA adapter. Reason: Message cannot be dispatched: Message cannot be dispatched: senderChannel 'fbesfd4b25331eabe67a1d04ec4acf': Catching exception calling messaging system

I configured simple scenario.

I have set up the 2 ID flows :

- Partner 1 (Sender File) > (Partner 2) Receiver EDISeprator (didnt used any conversion modules)

- Partner 3 (Sender EDISeparator with Edifact Module) > to SOAP sending B2B XML to another PI system.

Done B2B **** Pit file Association.

Tested in B2B COckpit and it is working fine but working in E2E

Also note that this is not a Custom EDI. This is just Order D93A Standard message file containing multiple Orders in same file.

Also let me know one thing Is it required to make KEY Associations for standard EDIFACT Structure Secnario as well?

I understand from the above error that is able to lookUP the 2nd flow EDI Sender Channel ID but it is unable to deliver/despatch the message content to that flow.