Service operation support for EDISeparator adapter

Question

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

Answer 1

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