![]() |
Copyright © TIBCO Software Inc. All Rights Reserved |
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."To configure the synchronous request response transaction, configure corresponding information in the following tabs, and then click Save to save the configurations.In the General tab, you can configure general information for synchronous request response transactions.The following table lists the fields in the General 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 and load the Validator Profile file (.apf). Click change to select a guideline file to translate X12 to TEXT. 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 Request Error Limit to 0, it means that no limit is imposed at this level.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 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. 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 Request Error Limit to 0, it means that no limit is imposed at this level.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 a guideline file for translating EDI rejection Ack to TEXT.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. To configure request actions for synchronous request response transactions, you have to configure information in the subtabs of the Request Action tab.In the General tab, you can configure general information for request actions.
Table 13 Request Action: General Tab In the Translation Map tab, you can configure translation map information for request actions.
Table 14 Request Action: Translation Map 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.To configure request actions for synchronous request response transactions, you have to configure information in the subtabs of the Response Action tab.In the General tab, you can configure translation map information for response actions.
Table 15 Response Action: General Tab In the Translation Map tab, you can configure translation map information for request actions.
Table 16 Response Action: Translation Map 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 |