New Sync RequestResponse 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:
- Naming the synchronous request operation of the transaction 101, so that it ends with R, for example, 101R.
- Configuring the trading partner to send the GS02 Sender Application ending with R.
Then, the receiving BusinessConnect Container Edition can detect the operation as a synchronous transaction and to trade synchronously with their partner. If either one of the preceding two configurations is missing and two different operation types are configured, namely synchronous (101R) and notify operations (101) for the same transaction type, the receiver always receives the transaction as a notify transaction even though the initiator might have sent it in synchronous mode.
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 > Operations > Responding Operations > transaction id ( Sync Transactions) > 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 template 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 template 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™ Container Edition - EDI Protocol powered by Instream® User’s Guide, Private Messages.
To configure New Sync RequestResponse Transaction tab see the following tabs: