Copyright © Cloud Software Group, Inc. All Rights Reserved

Notification Transaction

Notification transactions are asynchronous in nature: a transaction is sent to the trading partner, and the response from the trading partner is expected at some later time.

Only Notify transactions are currently supported for NAESB; Synchronous Request Response transactions are not supported. See also NAESB.

•	Notification Transaction Tab

•	Outbound Action Tab

Notification Transaction Tab

This tab contains three subtabs.

•	General Tab

•	Guideline Tab

•	Schema Tab

General Tab

In the General tab, you can configure general information for notification transactions.

The following table lists the fields in the General tab of the Notification Transaction tab:

Table 4 Notification Transaction: General Tab 

Field	Description
Name	Specify a name for the transaction.
Description	Provide a description for the transaction (optional)
Inbound Raw EDI Segments
Include in Private Process Request	Select this check box to include raw EDI message in the private process (RESPONDER.REQUEST) for this operation. This check box is unselected by default.
Include in Validation Error Advisory	Select this check box to include raw EDI messages in the Validation Error advisory. This check box is selected by default.
Extra Transaction Info	This text field is used to send any information to the private process at transaction level of RESPONDER.REQUEST message. It can also be included in RESPONDER.INTERCHANGE and ValidationAlert advisory.

Guideline Tab

In the Guideline tab, you can configure guideline information for notification transactions.

The following table lists the fields in the Guideline tab of the Notification Transaction tab:

Table 5 Notification Transaction: Guideline Tab 

Field	Description
GS01 Functional Identifier Code	The mandatory code of the message. Example: PO. Entering the GS01 functional identifier that is normally indicated in the Functional Group Header is needed by the EDI conversion engine.
Validation Guideline
Guideline File for validating X12 Partner data (.sef or .std)	The guideline file associated with this message type. It is used to validate the EDI document that is received from a trading partner, or that is sent to the trading partner. Click change to select the guideline file associated with this message type. Then, follow the procedure described in the section File Specification Dialog in TIBCO BusinessConnect Trading Partner Administration Guide.
Validator Profile File (.apf)	Click change to select and load the Validator profile file. Validator profile files are used to check on errors and categorize them to different levels of severity. For details, see Configuring Validation Profile (.apf) Files.
Error Limit	Specify a threshold to control the number of errors reported or audited at transaction, group or interchange level to avoid system overload. If you set Error Limit to 0, it means that no limit is imposed at this level. The default transaction setting is 10. Only up to 10 errors are reported per transaction, both in the audit and ERROR.VALIDATION. However, acknowledgments have all the errors that are being reported.
Inbound Type of Translation
Inbound X12 Translation Type (e.g. EDI to XML or EDI to TEXT)	Select one item from the list to specify the inbound X12 translation type. • EDI to XML   This is the default value. When you select EDI to XML from the list, the inbound X12 document is translated to XML. It can be overridden at the business agreement level to do EDI to TEXT translation. For more details, see Table 33, Override Settings for Notify: Guideline (Sheet 1 of 3). • EDI to TEXT    When you select EDI to TEXT from the list, the Inbound X12 document is translated into a TEXT document, depending on the structure of the guideline that is designed. When a proper TEXT guideline is uploaded and an appropriate translation map for mapping EDI to TEXT is created, the output is a TEXT file.
TEXT Translation Guideline
Guideline File used for translating X12 to TEXT (.sef or .std)	Click change to select a guideline file for translating X12 to TEXT. This TEXT guideline is used for translating an X12 EDI document into a TEXT document.

Schema Tab

In the Schema tab, you can configure schema information for notification transactions.

The following table lists the fields in the Schema tab of the Notification Transaction tab:

Table 6 Notification Transaction: Schema Tab

Field	Description
Transaction Schema (.xsd)	Click change to select the schema file associated with this message type. The message schema is required for the EDI conversion engine. When a connection to TIBCO BusinessConnect is created in TIBCO Designer or TIBCO Business Studio, loading the message schema into the TIBCO BusinessConnect configuration store allows it to be retrieved automatically by TIBCO Designer or TIBCO Business Studio.
Request Root Element Name	Specify the name of the Transaction Schema root element from the preceding field.
EDI to XML (or EDI to TEXT) Translation Map file (.map)	Click change to select the EDI to XML or EDI to TEXT translation map file associated with this message type. • If you select EDI to TEXT as the type of translation, the appropriate X12 to TEXT translation map must be uploaded for the translation to occur. • If you select EDI to XML as the inbound type of translation, the appropriate X12 to XML translation map must be uploaded for the translation to occur. Note that EDI to XML translation map files generally have the extension _EX.map.
XML to EDI Translation Map file (.map)	Click change to select the XML to EDI translation map file associated with this message type. Note that XML to EDI translation map files have the extension _XE.map.

Outbound Action Tab

To configure the outbound action for the Notification transaction, you must configure information in the subtabs of the Outbound Action tab.

•	General Tab

•	Batching Tab

•	Acknowledgement Tab

General Tab

In the General tab, you can configure general information for outbound actions.

The following table lists the fields in the General tab of the Outbound Action tab:

Table 7 Outbound Action: General Tab

Field	Description
Name	Specify a name for the outbound action.
Description	Provide a description for the outbound action.
Direction	Specify the Initiator to Responder (pre-filled).

Batching Tab

In the Batching tab, you can configure batching information for outbound actions.

The following table lists the fields in the Batching tab of the Outbound Action tab:

Table 8 Outbound Action: Batching Tab

Field

Description

Batch Option

Select one item from the Batch Option list: • Always  This is the default option. If Scheduled Transmission is enabled in the Scheduled Transmission tab of a trading partner's business agreement with the host, all messages of this transaction type for that trading partner are placed into batches. The batches are sent based upon the settings in the Scheduled Transmission tab of the business agreement. See Scheduled Transmission Tab. • Never  Messages of this transaction type are not to be included in any batches regardless of whether the scheduled transmission has been enabled for a trading partner. All messages of this type are sent immediately to your trading partners, and bypass the schedule time/batch settings for your trading partners. • Exclusively  When messages of this transaction type are included in a scheduled batch, they are separated into interchanges containing only messages of this type. With this choice, you can batch transactions based upon transaction type. For example, you can batch all 850 transactions and all 860 transactions so that your trading partners receive 850 transactions in one interchange and 860 transactions in another interchange. The exclusive batching feature includes two options where TIBCO BusinessConnect can transmit: − Each interchange in its own document. − Multiple interchanges in a single document.

Acknowledgement Tab

In the Acknowledgement tab, you can configure acknowledgment information for outbound actions.

The following table lists the fields in the Acknowledgement tab of the Outbound Action tab:

Table 9 Outbound Action: Acknowledgement Tab

Field	Description
Maximum Wait (minutes)	The default waiting time is 1440 minutes. This is the maximum amount of time that TIBCO BusinessConnect waits for an acknowledgment (997 functional acknowledgment transaction) from your trading partner when a message of this type is sent to your trading partner. If an acknowledgment is not received within the time limit specified, TIBCO BusinessConnect logs an ACK_RESPONSE_TIMEOUT state for the original message, and sends an alert message on the subject prefix.installation.X12.ERROR.TIMEOUT.ACK to the private process.
Reconcile After Timeout	Acknowledgments that are received after the timeout period are reconciled and processing of the original message continues. Normally when an acknowledgment times out, the final status of the original message is set to ACK TIMEOUT ERROR. If the acknowledgment is received after the timeout period, it is ignored.
Mark as Completed After Timeout	Final status of Completed with a state of ACK_RESPONSE_TIMEOUT is logged for the original message in the case when the acknowledgment for the message is not received before the specified timeout. If you select this check box and the acknowledgment is received after the timeout, it is ignored. This feature is useful when your trading partner is sending an acknowledgment only when validation errors occur for the original message. After the acknowledgment timeout period expires, the original message is assumed to be accepted by your trading partner.

For information on configuring acknowledgments, see TIBCO BusinessConnect EDI Protocol powered by Instream User’s Guide, Chapter 5, "Acknowledgments and Reconciliation."

Copyright © Cloud Software Group, Inc. All Rights Reserved