![]() |
Copyright © TIBCO Software Inc. All Rights Reserved |
Once you have configured your interchange and group versions, you can configure the EDIFACT message:
2. Click New Message.
3. Click OK.Figure 16 Edit Notification Message
Enable the output of the raw EDI segments in the private process request. The raw EDI data of the interchange and group envelope header and trailer segments are always included. The interchange envelope includes the header UNB segment and the trailer UNZ segment. The group envelope includes the header UNG segment and trailer UNE segment.
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. Click change to select the Validator profile file.
• EDI to XML This is the default value.
It can be overridden at the business agreement level to do EDI to TEXT translation (see Table 24, Override Settings for a Transaction: Guideline)
• EDI to TEXT 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. Click change to select a guideline file for translating EDIFACT to TEXT.
Click change to select the schema file associated with this message type. Click change to select the EDI to XML or EDI to TEXT translation map file associated with this message type. 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 an extension _XE.map.
Table 7 Outbound Action: General Tab
Table 8 Outbound Action: Batching Tab Select from among the following options in 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 will be placed into batches. The batches will be sent based upon the settings in the business agreement's Scheduled Transmission tab. See Overview.
• 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 will be sent immediately to your trading partners and will bypass the schedule time/batch settings for your trading partners.
• Exclusively When messages of this transaction type are included in a scheduled batch, they will be separated into interchanges containing only messages of this type. This choice allows you to batch transactions based upon transaction type.Acknowledgement Tab
This is the maximum amount of time that TIBCO BusinessConnect will wait for an acknowledgment (CONTRL 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. Normally when an acknowledgment times out, the final status of the original message will be set to ACK TIMEOUT ERROR. If the acknowledgment is received after the timeout period, it will be ignored. 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 and the acknowledgment is received after the timeout, it will be ignored.For information on configuring acknowledgments, see Chapter 5, Acknowledgments and Reconciliation in TIBCO BusinessConnect EDI Protocol powered by Instream User’s Guide
![]() |
Copyright © TIBCO Software Inc. All Rights Reserved |