Service operation support for EDISeparator adapter

[saurabhkumbhare]

Hello Experts,

I am configuring the Sender EDISeperator adapter and the Sender service interface assigned to this EDISeperator adapter has multiple service operations attached to it.

An example is shown below :

I am getting the below error :

Questions:

1.Can anybody help me to resolve this error.

2. Does the EDISeparator adapter support Stateless interface pattern (i.e Service interface with multiple operations)

3.Is it mandatory to have the message type name (See "Name" column above) as ORDERS96A..i.e can we add suffixes to it like ORDERS96A_MT. I have noticed that if we add these suffixes the EDISeparator adapter throws an error. Is this understanding correct.

Thanks

Saurabh

[Ryan-Crosby]

Hi Saurabh,

The EDI Separator adapter does support service interfaces with multiple operations because we are doing the same thing with our service interface patterns.  Are you trying to split one source message to multiple receivers or determine one specific receiver based on the source message?

Regards,

Ryan Crosby

[saurabhkumbhare]

Hi Ryan,

Thanks for your quick reply.

I have the following scenario.

Communication Component A                     Mapping                      Communication Component B

SI_Orders.Ean007                                            MM_EAN007             ZCNOSE_ORDERS.ORDERS03

SI_Orders.Ean008                                            MM_EAN008             ZCNOSE_ORDERS.ORDERS03

SI_Orders.Ean009                                            MM_EAN009             ZCNOSE_ORDERS.ORDERS03

I get the error something like, Could not find the receiver determination at all

Thanks

Saurabh

[Ryan-Crosby]

Hi Saurabh,

It appears that you are doing an interface split instead of any receiver split.  What is the root message node that gets generated at the EDI Separator Receiver for each of the cases?  Do those root message nodes match up with the message types that you have in your service interface operations that you have shown?

Regards,
Ryan Crosby

[saurabhkumbhare]

Hi Ryan,

Exactly the question i was expecting.

Communication Component A                    Mapping                      Communication Component B

SI_Orders.Ean007  (  ORDERS96A )                                 MM_EAN007           ZCNOSE_ORDERS.ORDERS03

SI_Orders.Ean008  (  ORDERS96A )                                   MM_EAN008           ZCNOSE_ORDERS.ORDERS03

SI_Orders.Ean009   (  ORDERS96A )                                  MM_EAN009           ZCNOSE_ORDERS.ORDERS03

all the services interface have ORDERS96A message types ( but in different namespaces ) as its root node as shown above and the EDISeparator adapter at the receiver side is generating ORDERS96A before the split.

FYI, the mapping is done between the messages types in their respective namespaces and the common IDoc.

Thanks

Saurabh

[Ryan-Crosby]

Hi Saurabh,

If you convert these different messages in the B2B cockpit what is the root message node... is it ORDERS96A?  I have only used x12 but my understanding is that the system will generate the root message node based on the message version also so that <ORDERS96></ORDERS96A> for each operation would not match what the system generates via conversion.  Can you confirm what the message nodes are for each version?

Regards,

Ryan Crosby