Copyright © TIBCO Software Inc. All Rights Reserved
Copyright © TIBCO Software Inc. All Rights Reserved


Chapter 3 Managing EDIFACT Interchanges, Functional Groups, and Messages : Configuring CONTRL Transactions

Configuring CONTRL Transactions
*T
If acknowledgments will be sent or received for EDIFACT documents, you must configure a CONTRL message by following these conventions:
Therefore, a CONTRL message would typically be configured under a group version named D3. However, if functional groups are not used, the CONTRL message would be configured under a group version named EmptyGroup.
Multiple Configurations for the Same Message Type
TIBCO BusinessConnect EDI Protocol powered by Instream provides a feature called name modifiers that you may need to use to provide multiple configurations for your message. There are two types of name modifiers:
Message Name Modifiers
Message name modifiers are used when you need to configure multiple guidelines for the same message type and only certain trading partners will be allowed to use the alternate message configurations.
You may need different guidelines for the same message type to satisfy the message exchange requirements for all of your trading partners. For example, the BANSTA guideline used for a trading partner A may include additional data elements which may not be suitable for other trading partners. These additional data elements may also result in the generation of an XSD for the guideline which is different from the XSD generated for normally-used BANSTA guidelines.
To handle this situation, you can configure multiple versions of the same message type by using message name modifiers when configuring the message.
To use a message name modifier:
1.
Enter the name of the message type in the Name field of the Notification Transaction > General tab.
2.
Append a colon : to the name.
3.
For example, you can configure two versions of a D98A BANSTA message as:
1/D98A/BANSTA
1/D98A/BANSTA:TPA
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.
For further information, see Operation Bindings Tab.
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 operationID 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.
EmptyGroup Name Modifiers
EmptyGroup name modifiers are used when you don't use functional groups and you need to configure different versions of the same message type. For example, you may need to configure both versions D93A and D98A of an ORDERS message under the group EmptyGroup.
When not using functional groups, you may need to configure multiple versions of the same message type. For example, you may need to configure a D93A ORDERS message type and a D98A ORDERS message type.
You could use message name modifiers to configure the message types as follows:
1/EmptyGroup/ORDERS
1/EmptyGroup/ORDERS:D98A
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.
EmptyGroup name modifiers can be used in this situation to identify the different message types in the Operations Editor. Multiple group versions are created using the following EmptyGroup name modifier syntax:
EmptyGroup:Version/ReleaseNumber
For this example, you would configure the following in the Operations Editor:
1/EmptyGroup:D93A/ORDERS
1/EmptyGroup:D98A/ORDERS
This configuration would allow TIBCO BusinessConnect EDI Protocol powered by Instream to detect at runtime the appropriate configuration, and therefore guideline, to use for validating the different ORDERS messages.

Copyright © TIBCO Software Inc. All Rights Reserved
Copyright © TIBCO Software Inc. All Rights Reserved