![]() |
Copyright © TIBCO Software Inc. All Rights Reserved |
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.
To configure the Synchronous Request Response transaction, enter information into the following tabs, and then click Save:
An acceptance response transaction type. This is the type of transaction expected as a response from your trading partner. For example, if 850 is the request transaction, the acceptance response transaction type is 855. The rejection acknowledgement transaction type. This field indicates the type of transaction that would be expected to be returned as a response if the original request transaction had validation errors.
GS01 Functional Identifier Code (for Request) The mandatory functional identifier code of the transaction. Entering the GS01 functional identifier that would normally be indicated in the Functional Group Header is needed by the EDI conversion engine. Examples:
• Acceptance Response PR for an 855 purchase order acknowledgement transaction.
• Rejection Acknowledgement FA for a 997 functional acknowledgement transaction. Request Guidelines File (.sef or .std) Provide the path to the inbound synchronous request guidelines file. You can override this field at the business agreement level. This guideline file is used to validate the EDI document that is received from a trading partner, or that is sent to a trading partner.Click change to select the Guidelines File (.sef or .std). Request Validator Profile File (.apf) Provide the path to the inbound synchronous request Validator Profile file that you want to suppress errors into warning or information. You can override this field at the business agreement level.Click change to select the Validator Profile file (.apf). GS01 Functional Identifier Code (for Response) The mandatory functional identifier code of the transaction. Entering the GS01 functional identifier that would normally be indicated in the Functional Group Header is needed by the EDI conversion engine. Examples:
• Acceptance Response PR for an 855 purchase order acknowledgement transaction.
• Rejection Acknowledgement FA for a 997 functional acknowledgement transaction. Response Guidelines File (.sef or .std) Provide the path to the outbound synchronous response Guidelines file. You can override this field at the business agreement level.This guideline file is used to validate the synchronous response EDI document that is received from a trading partner, or that is sent to a trading partner.Click change to select the Guidelines File (.sef or .std). Response Validator Profile File (.apf) Provide the path to the outbound synchronous response Validator Profile file that you wanted to suppress errors into warning or informational if the responses have errors. You can override this field at the business agreement level.Click change to select the Validator Profile File (.apf). GS01 Functional Identifier Code (for Acknowledgement) Entering the GS01 functional identifier that would normally be indicated in the Functional Group Header is needed by the EDI conversion engine. Rejection Ack Guidelines File (.sef or .std) This guideline file would is used to validate the synchronous EDI rejection ack document that is received from a trading partner, or that is sent to a trading partner. Provide the path to the Rejection Ack Guidelines file. You can override this field at the business agreement level.Click change to select the Rejection Ack Guidelines File (.sef or .std).Loading the transaction schemas into the TIBCO BusinessConnect configuration store allows it to be retrieved automatically by TIBCO Designer when a connection to TIBCO BusinessConnect is created in TIBCO Designer. For further information refer to Creating Private Processes in the TIBCO BusinessConnect B2BPlugin for CMI, User’s Guide.
Request Transaction Schema (.xsd) To load the synchronous Request Transaction schema, and click change... to select the schema file for the synchronous request transaction. Example: X12_5010_850.xsd. Request Root Element Name Enter the name of the root element of the synchronous request Transaction Schema from the above field. Response Transaction Schema (.xsd) To load the synchronous Response Transaction schema, and click change... to select the schema file for the synchronous response transaction. Example: X12_5010_850.xsd. Response Root Element Name Enter the name of the root element of the synchronous response Transaction Schema from the above field. Rejection Ack Transaction Schema (.xsd) To load the Rejection Ack Transaction schema, and click change... to select the schema file for the rejection ack transaction.Example: X12_5010_997.xsd. Rejection Root Element Name To configure the outbound action for the Notification transaction, enter information into the following tabs:
Table 9 Request Action: General Tab
Table 10 Request Action: Translation Map Tab Request XML to EDI Translation Map File (.map) 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. Note that XML to EDI translation map files have the extension _XE. Response EDI to XML Translation Map File (.map) Click change to select the EDI to XML translation map file.When EDI to XML is selected as the inbound type of translation, then the appropriate B2B-X12 to XML translation map must be uploaded for the translation to occur. Note that EDI to XML translation map files have an extension _EX.map. Rejection Ack EDI to XML Translation Map File (.map) Click change to select the EDI to XML translation map file.When EDI to XML is selected as the inbound Type of Translation, then the appropriate B2B-X12 to XML translation map must be uploaded for the translation to occur. Note that EDI to XML translation map files have an extension _EX.map.
Table 11 Response Action: General Tab
Table 12 Response Action: Translation Map Tab Request EDI to XML Translation Map File (.map) Click change to select the EDI to XML translation map file.The appropriate B2B-X12 to XML translation map must be uploaded for the translation to occur. Response XML to EDI Translation Map File (.map) Click change to select the EDI to XML translation map file.When XML to EDI is selected as the outbound type of translation, then the appropriate XML to B2B-X12 translation map must be uploaded for the translation to occur. Note that XML to EDI translation map files have an extension _XE.map.
![]() |
Copyright © TIBCO Software Inc. All Rights Reserved |