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


Chapter 3 Managing X12 Interchanges, Functional Groups, and Transactions : Synchronous Request Response Transaction

Synchronous Request Response Transaction
Synchronous request-response transactions are transactions where a response transaction is expected to be returned quickly and using the same transport connection as the request transaction. In case of validation errors, the normal response cannot be returned but another transaction, for example, 997 or TA, is returned indicating that validation errors occur.
For example, you can agree with your trading partner that each 850 purchase order transaction you send must have an 855 purchase order acknowledgment transaction returned as a response on the same transport connection. If a validation error occurs in the 850 purchase order transaction, an 855 response cannot be returned. Instead, a 997 response is returned, indicating that the 850 is rejected. You do not usually choose to keep a transport connection open for more than a minute or two. Therefore, the time frame, which the response is expected within, must be fairly short. Synchronous request-response transactions are only supported on those transports for which a response transaction can be returned on the same connection used for sending the request transaction.
Synchronous Request and Notify Operations
Users receiving a synchronous request from their trading partner can also receive a notify operation of the same transaction type under the same group and interchange.
This result can be achieved by having a mandatory business agreement with the trading partner and configuring the following information:
Default Response for a Synchronous Request
You can send a default response for a synchronous request in case the response from the private process on the responder side fails due to validation errors.
To configure the default response, upload this response file to the following location:
BusinessAgreement>X12>Partner can initiate>operation>Action Settings> Default response
The Default Response field is available only in the Partner can initiate field of the operation binding. It is configurable to send a templated response to the trading partner if the synchronous response sent from the private process contains any validation errors or errors in the response XML. In such case, this templated response is sent back to the trading partner with no validation or syntax check. Users have to ensure that the Default Response is a valid response.
For more information on synchronous request-response transactions, see TIBCO BusinessConnect EDI Protocol powered by Instream User’s Guide, Chapter 8, "Private Messages."
Configuring the Synchronous Request Response Transaction
To configure the synchronous request response transaction, configure corresponding information in the following tabs, and then click Save to save the configurations.
General Tab
In the General tab, you can configure general information for synchronous request response transactions.
The following table lists the fields in the General tab:
Guideline Tab
In the Guideline tab, you can configure guideline information for synchronous request response transactions.
The following table lists the fields in the Guideline tab
EDI to XML  This is the default value.
When you select EDI to XML from the list, the inbound Synchronous X12 document is translated to XML. It can be overridden at the business agreement level to do EDI to TEXT translation. For 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 appropriate synchronous X12 document is translated to TEXT.
Click change to select a .sef or .std guideline file.
Click change to select and load the Validator Profile file (.apf).
Click change to select a guideline file to translate X12 to TEXT.
The default value 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.
Click change to select and load the .sef or .std Guidelines File.
Click change to select and load the Validator Profile File (.apf).
Click change to select a guideline file for translating EDI to TEXT.
TEXT to EDI    TEXT data can be sent from the private process, converted to the EDI data, and sent back to the Initiator.
For more details, see TIBCO BusinessConnect EDI Protocol powered by Instream User’s Guide, "TEXT to EDI Conversion."
Click change to select and load a guideline file for translating TEXT to EDI.
The default value 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.
Click change to select and load the Rejection Ack Guidelines File (.sef or .std).
Click change to select and load a guideline file for translating EDI rejection Ack to TEXT.
Schema Tab
In the Schema tab, you can configure schema information for synchronous request response transactions.
Loading the transaction schemas into the TIBCO BusinessConnect configuration store allows it to be retrieved automatically by TIBCO Designer or TIBCO Business Studio when a connection to TIBCO BusinessConnect is created in TIBCO Designer or TIBCO Business Studio. For further information, see TIBCO BusinessConnect EDI Protocol powered by Instream User’s Guide, "Creating Private Processes."
The following table lists the fields in the Schema tab:
To load the synchronous Request Transaction schema, click change to select the schema file for the synchronous request transaction.
Example: X12_5010_850.xsd.
To load the synchronous Response Transaction schema, click change to select the schema file for the synchronous response transaction.
Example: X12_5010_850.xsd.
To load the Rejection Ack Transaction schema, and click change to select the schema file for the rejection acknowledgment transaction.
Example: X12_5010_997.xsd.
Request Action Tab
To configure request actions for synchronous request response transactions, you have to configure information in the subtabs of the Request Action tab.
General Tab
In the General tab, you can configure general information for request actions.
The following table lists the fields in the General tab of the Request Action tab:
Translation Map Tab
In the Translation Map tab, you can configure translation map information for request actions.
The following table lists the fields in the Translation Map tab of the Request Action tab:
Click change to select the XML to EDI translation map file. This file is associated with this message type for sending XML from the private process to TIBCO BusinessConnect and is sent to the Trading Partner as a synchronous request.
Click change to select the EDI to XML or EDI to TEXT translation map file.
Click change to select the EDI to XML or EDI to TEXT translation map file.
Response Action Tab
To configure request actions for synchronous request response transactions, you have to configure information in the subtabs of the Response Action tab.
General Tab
In the General tab, you can configure translation map information for response actions.
The following table lists the fields in the General tab of the Response Action tab:
Translation Map Tab
In the Translation Map tab, you can configure translation map information for request actions.
The following table lists the fields in the Translation Map tab of the Response Action tab:
Click change to select and load the EDI to XML (or EDI to TEXT) translation map file.
Click change to select the XML to EDI (TEXT to EDI) translation map file. This file is associated with this message type for sending the synchronous response to a trading partner that is received from the private process.
For TEXT to EDI translations, see TIBCO BusinessConnect EDI Protocol powered by Instream User’s Guide, "TEXT to EDI Conversion."

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