Dear Bobby
First of all, welcome to SCN.
Hope you have read the The SCN Rules of Engagement. Please avoid creating duplicate threads with the same content as you have with the following thread below. This is cross posting and goes against the ROE.
dynamic interface determination or receiver determination
Now back to your question.
Another approach you can consider is to use multiple operations in the sender service interface. This approach is applicable for any interface with just one sender agreement, irrespective of the sender comm channel type, i.e. can be used for SOAP, AS2, File/FTP.
The prerequisite for this approach is that the source content is XML and the different message types have a different root element (you cannot save and activate a service interface with multiple operation having same root element.) For your case it would work because the different source IDoc have different root, i.e. <ORDERS05> or <WMMBXY>
The advantage of this approach is that you do not need to specify additional Xpath conditions at the receiver determination or interface determination step. The runtime engine automatically checks the root element of a message against the different operations of the service interface to determine which should be used.
To achieve this, here are the key areas you need to take note of:
1) Add one operation (to the sender service interface) for each IDoc type you are expecting to receive from your partner. i.e. one for ORDERS, one for WMMBXY
2) Use non specific operation in Receiver Determination
3) At interface determination, use operation-speficic setting, and for each operation, choose the relevant Operation Mapping for that source IDoc type.
Rgds
Eng Swee