AS2-->PI 7.31 -->IDOC Scenario Issue with EDI Separator

[Former Member]

Hi Team,

i am working on inbound scenario,which is AS2-->PI-->IDOC

I have done 2 flows as2---edireciver and edisepartor senderidoc

i have given the details in edisaeprator with all possiable details but not working.

i have given the details of below mentioned in XXXX also

could please let me know what is control key scenario association.  (Screen Shots attached)

i have given the dataof reciver SI and NAMESPACE in control key scenario association,but when i have saved the data in control key scenario association i am not able to see the data whatever i have saved.

Message could not be forwarded to the JCA adapter. Reason: com.sap.aii.adapter.ediseparator.ra.integration.DispatchException: Message cannot be dispatched: No senderchannel matches the Message type ORDERS, Message version number D, Message release number 96A, Interchange sender identification XXXXX, Interchange sender identification code qualifier 14, Interchange recipient identification XXXXXXXX, Interchange recipient identification code qualifier 14

Searching sender channel for Eancom message part message with Message type ORDERS, Message version number D, Message release number 96A, Interchange sender identification 8435235300007, Interchange sender identification code qualifier 14, Interchange recipient identification 8432505000018, Interchange recipient identification code qualifier 14, Message Subversion EAN008, Message Agency UN

MP: exception caught with cause javax.resource.ResourceException: com.sap.aii.adapter.ediseparator.ra.integration.DispatchException: Message cannot be dispatched: No senderchannel matches the Message type ORDERS, Message version number D, Message release number 96A, Interchange sender identification xxxxxxxx, Interchange sender identification code qualifier 14, Interchange recipient identification xxxxxxxx, Interchange recipient identification code qualifier 14

Exception caught by adapter framework: com.sap.aii.adapter.ediseparator.ra.integration.DispatchException: Message cannot be dispatched: No senderchannel matches the Message type ORDERS, Message version number D, Message release number 96A, Interchange sender identification xxxxxxxxx, Interchange sender identification code qualifier 14, Interchange recipient identification xxxxxxxx, Interchange recipient identification code qualifier 14

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: com.sap.aii.adapter.ediseparator.ra.integration.DispatchException: Message cannot be dispatched: No senderchannel matches the Message type ORDERS, Message version number D, Message release number 96A, Interchange sender identification XXXXXXXX, Interchange sender identification code qualifier 14, Interchange recipient identification xxxxxxxxx, Interchange recipient identification code qualifier 14

Also, Could you please share an idea on how to insert data in a control key Scenario association and what is the purpose of the same.

[Dimitri · Accepted solution]

Hi,

Take a look at and especially step 5.2.

Also, can you share your EDI message you send to the SAP PI system?

I see a mix between EANCOM settings and an EDI ORDERS message.

Kind regards,

Dimitri

[Former Member · Accepted solution]

Hi ,

i have given the dataof reciver SI and NAMESPACE in control key scenario
association,but when i have saved the data in control key scenario association
i am not able to see the data whatever i have saved..

[Dimitri · Accepted solution]

The sender and receiver is not that important. You should have the correct control key name, reflecting the message type.

Please make sure you modify the configuration accordingly and make sure EANCOM is used everywhere.

[Former Member · Accepted solution]

Hi,

Can you please let me know. Since,I am working for the first time..

The sender and receiver is not that important. You should have the

correct control key name, reflecting the message type.

  controlkey name and reflecting the message type means?

    Please make sure you modify the configuration accordingly and make

sure EANCOM is used everywhere.

mine is ORDERS 96A  and also EANCOM is used everywhere means?

[Dimitri · Accepted solution]

Can you share your complete configuration and an example of an EDI file?

[Former Member · Accepted solution]

AS2-PI-IDOC is my scenario.

I have created 2 interfaces one is AS2-PI-EDISEPARATOR and
another one is

EDISEPARATOR SENDER--PI-IDOC RECEIVER.

Scenario1:

AS2-PI-EDISEPARATO:

I have given sender details:

PARTY:               
PTY_ZZ_RED

Communication component: BC_ZZ_RED

Interface: MI_RED_ORDERS_D96A

Namespace: http://red.com

I have given RECEIVER details:

PARTY:               
PTY_ZZ_YYY

Communication component: BC_ZZ_RED

Communication Channel:
CC_EDISeparator_RECEIVER

I am keeping for sender channel FILE instead of AS2 and in
module I kept edifact converter module and I have taken the input paload from
Message mapping.

Scenario2:

EDISEPARATOR SENDER--PI-IDOC RECEIVER:

sender details:

PARTY                                   :
PTY_ZZ_YYY

Communicationcomponent:
BC_ZZ_RED

Interface: MI_RED_ORDERS_D96A

Namespace:http://red.com

CommunicationChannel:CC_EDISeparator_Sender

Pls find the below screen shots of configuration for
ediseparator sender channel:

[Dimitri · Accepted solution]

Hi Prem,

I've already sent you a direct message...

Please check your reply above and complete it with screen shots and configuration details.

Make sure you edit the post and do not create a new one to keep this thread clean and accessible.

Thank you

Dimitri

[Former Member · Accepted solution]

Sorry I was unable to edit the post hich is already there. However, attached the detailed flow to keep the post simple.

Scenario Flow.txt.zip

[Dimitri · Accepted solution]

Hi Prem,

I checked your content and it seems something like

Please check that first.

Kind regards,

Dimitri

[Former Member · Accepted solution]

Thanks Dimitri, I got it working when the message protal in EDI Separator channel chaged from EDIFACT to EANCOM.

Could you please help me to know what is the basic difference between these two here and how I am able to recognize and achieve the result going forward.

Thanks

Prem

[Former Member · Accepted solution]

Hi Dimtiri

Could you please let me know difference between EDIFACT and EANCOM.How can we differentiate in the payload these two?

what is the importance of control key scenario association?

[Dimitri · Accepted solution]

Hi Prem,

Check out the payload (UNH segment, field 0057). Perhaps you could see a different value.

Control keys are intended to determine the incoming message type. This allows the system to correctly parse the EDI format to XML format.

Kind regards,

Dimitri