Configuring Acknowledgments

This section describes how to configure acknowledgments.

To properly mark the ISA, GS, and ST segments with a DSR mark, as required for proper acknowledgments generation, see the documentation provided with the EDISIM Standards Editor.

Configuring 997 Functional Acknowledgments

The 997 transaction set is also called a functional acknowledgment. It is used to indicate the results of the syntactical analysis of a same type transaction group, such as all 850 transactions contained in the same functional group inside an interchange. If functional acknowledgments (997s) are to be sent or received for X12 transaction sets, you must configure a 997 transaction for each functional group containing the transaction sets.

The 997 transactions are not sent as acknowledgments for other 997 transactions

For example, the sample interchange X12-00403.csx contains the following information:

00403 interchange version 
005010 group version
850 transaction set
997 transaction set

You can configure the 997 transaction set in the Operations Editor just as you configure any other X12 transaction set. However, for the 997 transaction set it is not necessary to upload the guideline to use for validation. TIBCO BusinessConnect™ Container Edition - EDI Protocol powered by Instream® contains a generic 997 guideline, which is used by default. The generic 997 guideline X12_5010_997.sef can be found in the directory: BCCE_HOME\protocols\tibedi\samples\sampleDocs\guidelines.

Configuring the 999 Implementation Acknowledgments

The 999 implementation acknowledgments are used to report the status of implementation guide syntax edits. Automatic generation of the 999 acknowledgment is available for transactions in group 004061 and higher. Configuration of the 999 implementation acknowledgment is similar to configuring a 997 acknowledgment: you can configure the 999 as a transaction set in the operations editor just as you configure a 997.

For example, to use a 999 acknowledgment instead of a 997 acknowledgment in the X12-00403.csx example interface, you can replace the configuration of the 997 acknowledgment with a configuration for the 999 acknowledgment as follows: 00403 interchange version

005010 group version
850 transaction set
999 transaction set

When configuring the 999 transaction set in the Operations Editor, it is not necessary to upload the guideline for 999. TIBCO BusinessConnect™ Container Edition - EDI Protocol powered by Instream® contains a generic 999 guideline, which is used whenever the configuration of a 999 transaction set does not have a guideline uploaded. The generic 999 guideline for the preceding example is X12_5010_999.sef, and can be found in the directory: BCCE_HOME/protocols/tibedi/samples/sampleDocs/guidelines.

Configuring TA1 Interchange Acknowledgment Segments

The interchange acknowledgment segment (TA1) is used to indicate the receipt of the contents of one interchange control header and trailer envelope, in which the envelope surrounds one or more functional groups. If the interchange contains only TA1 segments, a TA1 is not returned for the interchange.

If interchange acknowledgment segments are sent or received for interchanges containing X12 transaction sets, you must configure a TA1 interchange segment for each interchange. You can configure the TA1 interchange segment with a guideline just as you configure any other X12 transaction set. However, since the TA1 is not really a transaction set and is never contained inside of a functional group, the TA1 interchange segment is configured inside of a group version named EmptyGroup.

For example, the sample interchange X12-00403.csx contains the following information:

00403 interchange version
005010 group version
850 transaction set
997 transaction set
EmptyGroup group version
TA1 interchange segment

The EmptyGroup group version is not configured with a guideline.

Similar to the 997, TIBCO BusinessConnect™ Container Edition - EDI Protocol powered by Instream® contains a generic TA1 guideline, which it uses by default. Therefore, it is not necessary to upload a guideline for the TA1. The generic TA1 guideline X12_TA1.sef can be found in the directory: BCCE_HOME\protocols\tibedi\samples\sampleDocs\guidelines.

Multiple Configurations for the Same Transaction Type

TIBCO BusinessConnect™ Container Edition - EDI Protocol powered by Instream® provides a name modifiers feature that you might need to use to provide multiple configurations for your message. This feature is called Transaction Name Modifiers. Transaction Name Modifiers The Transaction Name Modifiers are used to configure multiple guidelines for the same transaction type in cases when only certain trading partners are supported to use the alternate message configurations.

With them, you can create multiple operation bindings for a single operation set, which then allows them to target otherwise identical transactions, such as a purchase order, to a specific departments belonging to a trading partner. The trading partner departments are allowed to do the same when sending transactions to your departments.

You might need different guidelines for the same transaction type to satisfy the transaction exchange requirements for all of your trading partners. For example, the 850 guideline used for the trading partner A may include additional data elements which may not be suitable for other trading partners. These additional data elements may also generate an XSD for the guideline that is different from the XSD generated for the 850 guidelines that are used otherwise. To handle this situation, you can configure multiple versions of the same transaction type by using message name modifiers when configuring the transaction.

One business agreement can have only one Transaction Name Modifier of the same transaction or message type.

To use a Transaction Name Modifier:

  1. Navigate to New Notification Transaction > Notification Transaction > General tab.
  2. In the Name field, type the name of the transaction type.
  3. Append a colon (:) to the name.
  4. Provide a short description after the colon to differentiate the transaction type configurations.
    For example, you can configure two versions of a 00403 850 transaction as:
    00403/005010/850
    00403/005010/850:TPA
    You must configure the generic 00403/005010/850 version to exchange any 850 purchase order transactions with your trading partners, including transaction for the trading partner for which you are using the modified version. In the preceding example, this is Trading Partner A, using the version 00403/005010/850:TPA

For the name modified version 00403/005010/850:TPA to be used for trading partner A, you must bind the name modified version 00403/005010/850:TPA to trading partner A.

For more information, see Operation Bindings Tab.

When an inbound 850 transaction is received for trading partner A, the guideline associated with the named modified version 00403/005010/850:TPA is used for validation of the message. The operationID field of the ResponderRequest message to the private process contains the modified message name 00403/005010/850:TPA. With this transaction name, the private process can filter and handle this non-generic 850 message from trading partner A.

If the Transaction Name Modifier operation is not bound, the default operation without the modifier is picked byTIBCO BusinessConnect Container Edition to validate transactions.