Sync 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
Guideline
Schema

General

Synchronous Request Response Transaction: General tab
Field	Description
Name	Specify a name for the transaction. Example: 850.
Description	Provide a description for the transaction.
Transaction Type
Acceptance Response	Specify 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.
Rejection Ack	Specify a rejection acknowledgment transaction type. This field indicates the type of transaction that is expected to be returned as a response if the original request transaction has validation errors. The default type is 997.
Inbound Raw EDI Segments
Include in Private Process Request	Select this check box to include raw EDI message in the private process (RESPONDER.REQUEST) for this operation. This check box is cleared by default.
Include in Validation Error Advisory	Select this check box to include raw EDI messages in the Validation Error advisory. This check box is selected by default.

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:

Synchronous Request Response Transaction: Guideline Tab
Field	Description
Request
GS01 Functional Identifier Code (for Request)	Specify the mandatory functional identifier code of the transaction. Entering the GS01 functional identifier, which is normally indicated in the Functional Group Header, is required by the EDI conversion engine. Examples: Request PO for an 850 purchase order transaction. Acceptance Response PR for an 855 purchase order acknowledgment transaction. Rejection Acknowledgment FA for a 997 functional acknowledgment transaction.
X12 Validation Guideline for Request
Request Guidelines File (.sef or .std)	Upload the inbound synchronous request guidelines file. You can override this field at the business agreement level. You can use this guideline file to validate the EDI document that is received from a trading partner or sent to a trading partner. Click Upload file to select a .sef or .std guideline file.
Request Validator Profile File (.apf)	Upload 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 Upload file to select and load the Validator Profile file (.apf).
Request Error Limit	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.
Acceptance Response
GS01 Functional Identifier Code (for Response)	Specify the mandatory functional identifier code of the transaction. Entering the GS01 functional identifier, which is normally indicated in the Functional Group Header, is required by the EDI conversion engine. Examples: Request PO for an 850 purchase order transaction. Acceptance Response PR for an 855 purchase order acknowledgment transaction. Rejection Acknowledgment FA for a 997 functional acknowledgment transaction.
X12 Validation Guideline for Response
Response Guidelines File (.sef or .std)	Upload 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 Upload file to select and load the .sef or .std Guidelines File.
Response Validator Profile File (.apf)	Upload the outbound synchronous response Validator Profile file that you want to suppress errors into warning or informational if the responses have errors. You can override this field at the business agreement level. Click Upload file to select and load the Validator Profile File (.apf).
Response Error Limit	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.
Rejection Ack
GS01 Functional Identifier Code (for Acknowledgement)	Specify the mandatory code of the acknowledgment. Example: FA. Entering the GS01 functional identifier, which is normally indicated in the Functional Group Header, is required by the EDI conversion engine.
Rejection Ack Guidelines File (.sef or .std)	Upload the Rejection Ack Guidelines file. You can override this field at the business agreement level. Click Upload file to select and load the Rejection Ack Guidelines File (.sef or .std). This guideline file is used to validate the synchronous EDI rejection acknowledgment document that is received from a trading partner, or that is sent to a trading partner.

Schema Tab

In the Schema tab, you can configure schema information for synchronous request response transactions.

Loading the transaction schema into the TIBCO BusinessConnect Container Edition configuration store allows it to be retrieved automatically by TIBCO Studio when a connection to TIBCO BusinessConnect Container Edition is created in TIBCO Studio. For further information, see TIBCO BusinessConnect™ Container Edition - EDI Protocol powered by Instream® User’s Guide, Creating Private Processes.

The following table lists the fields in the Schema tab:

Synchronous Request Response Transaction: Schema Tab
Field	Description
Request
Request Transaction Schema (.xsd)	To load the synchronous Request Transaction schema, click to select the schema file for the synchronous request transaction. Example: X12_5010_850.xsd.
Request Root Element Name	Specify the name of the root element of the synchronous request Transaction Schema from the above field.
Acceptance Response
Response Transaction Schema (.xsd)	To load the synchronous Response Transaction schema, upload the schema file for the synchronous response transaction. Example: X12_5010_850.xsd.
Response Root Element Name	Specify the name of the root element of the synchronous response Transaction Schema from the preceding field.
Rejection Ack
Rejection Ack Transaction Schema (.xsd)	To load the Rejection Ack Transaction schema, and click to select the schema file for the rejection acknowledgment transaction. Example: X12_5010_997.xsd.
Rejection Root Element Name	Specify the name of the root element of the Transaction Schema from the preceding field.