Scenario:
ANSI X12 -
Sender AS2 to IDOC
For testing purposes, I have been using Sender File to IDOC.
Configuration:
ICO 1:
Sender: EDI
Sender: Interface:XiPatternInterface1
NameSpace: http://sap.com/xi/XI/System/Patterns
Sender Adapter : File (FTP)
Receiver Adapter: EDISeparator
Receiver: EDI
Inbound Interface: Interface:XiPatternInterface1
NameSpace: http://sap.com/xi/XI/System/Patterns
No mapping
ICO 2:
Sender: EDI
Interface:OutboundInterface
NameSpace: http://sap.com/xi/XI/System/Patterns
Receiver : ECC
Sender Adapter : EDISeparator
Receiver Adapter: IDOC
Mapping: EDI 861 to IDOC
Issue:
The interface fails when a file is placed for the sender file Adapter of ICO1 to pick.
But the same configuration works perfectly, when the test tool (Send Test Message) is used. Idocs are created correctly.
Message Log for the failure.
1/24/2016 10:30:21.563 PM Information Application attempting to send an XI message asynchronously using connection AFW
1/24/2016 10:30:21.565 PM Information Trying to put the message into the send queue
1/24/2016 10:30:21.582 PM Information Message successfully put into the queue
1/24/2016 10:30:21.582 PM Information The application sent the message asynchronously using connection AFW. Returning to application
1/24/2016 10:30:21.584 PM Information The message was successfully retrieved from the send queue
1/24/2016 10:30:21.590 PM Information Message status set to DLNG
1/24/2016 10:30:21.592 PM Information Trying to put the message into the send queue
1/24/2016 10:30:21.612 PM Information Message successfully put into the queue
1/24/2016 10:30:21.613 PM Information The message was successfully retrieved from the send queue
1/24/2016 10:30:21.619 PM Information Message status set to DLNG
1/24/2016 10:30:21.621 PM Information Delivering to channel: 060EDISeparatorReceiver861
1/24/2016 10:30:21.621 PM Information MP: processing local module localejbs/ModuleProcessorExitBean
1/24/2016 10:30:21.621 PM Information Message entered AF MP exit bean and will now be passed to the JCA adapter
1/24/2016 10:30:21.623 PM Error MP: exception caught with cause javax.resource.ResourceException: The message type can not be determined
1/24/2016 10:30:21.623 PM Error Message could not be forwarded to the JCA adapter. Reason: The message type can not be determined
1/24/2016 10:30:21.626 PM Error Exception caught by adapter framework: The message type can not be determined
1/24/2016 10:30:21.627 PM Error Transmitting the message to endpoint <local> using connection AFW failed, due to:com.sap.engine.interfaces.messaging.api.exception.MessagingException: javax.resource.ResourceException: The message type can not be determined
1/24/2016 10:30:21.629 PM Information The asynchronous message was successfully scheduled to be delivered at Sun Jan 24 22:35:21 EST 2016
1/24/2016 10:30:21.629 PM Information Message status set to WAIT