You must configure the generic 1/D98A/BANSTA version to exchange any BANSTA messages with your trading partners, including messages for the trading partner for which you are using the modified version. In the example above, this is Trading Partner A, using the version
1/D98A/BANSTA:TPA.
For the name modified version 1/D98A/BANSTA:TPA to be used for trading partner A, you must bind the name modified version
1/D98A/BANSTA:TPA to trading partner A.
When an inbound BANSTA message is received for trading partner A, the guideline associated with the named modified version 1/D98A/BANSTA:TPA will be used for validation of the message. The o
perationID field of the
ResponderRequest message to the private process will contain the modified message name
1/D98A/BANSTA:TPA. This message name allows the private process to filter and handle this non-generic BANSTA message from trading partner A.
The disadvantage of using message name modifiers in this situation is that you would have to bind 1/EmptyGroup/ORDERS:D98A for every trading partner that uses it. This can become cumbersome if you have to manage more than a few trading partners.