ACH Inbound CTX Envelope Properties, Document Level

Edit online

The following table describes ACH inbound Batch-Level envelope properties at the document level:

Field
Description
* Destination Identification
Routing number of the ACH Operator or receiving point to which the message is being sent. Required.
* Origin Identification
Routing number of the ACH Operator or sending point that is sending the message. Required.
* Destination Name
Name of the ACH or receiving point for which the message is destined. Optional.
* Origin Name
Name of the ACH Operator or sending point that is sending the message. Optional.
Perform duplicate File ID Modifier check
Whether duplicate File ID checking be performed when receiving an ACH File Level envelope. Valid values are Yes and No. Required.
Maximum age of File ID Modifier History Records in days
Maximum days to retain a history of File ID Modifiers to use for duplication determinations. Valid value is nine standard characters. Optional.
Map Name Mode
Mode in which to specify the map to use to perform a compliance check. Required. Valid values:
  • Specify
  • Generate from data
  • Default (default)
Map Name
Select the Sterling B2B Integrator or WebSphere® Transformation Extender map to be used to perform a compliance check. The map must already be checked in. Optional.
Primary Name Format
Check boxes to instruct what information to include when generating and matching a name for the map. Optional.

Select from:

  • Destination Identification (selected by default)
  • Origin Identification (selected by default)
  • X12 Group Version ID Code/EDIFACT Message Version and Release Number (selected by default)
Handling of batches with discrepancies
Specify how to handle batches with discrepancies. Required. Valid values are:
  • Accept
  • Reject (default)
Specify the extracted 820 business process selection method
Determines how to select a business process to which to send the 820. Required. Valid values are:
  • Use the default X12 ISA interchange business process (default)
  • Looking up contract dynamically
  • Specifying a contract
  • Specifying a business process
  • Generating the business process name from data
Generate an error if the business process name does not exist in the system
Specify whether to generate an error if the business process name specified does not exist in the system. Required. Valid values are Yes and No.
Contract List
Select a previously created contract to associate with this envelope. Optional.
Note: Only displayed if the Specify the extracted 820 business process selection method is set to Specifying a contract.
Business Process List
Select a previously created business process to associate with this envelope. Required.
Note: Only displayed if the Specify the extracted 820 business process selection method is set to Specifying a business process.
Primary Name Format
Check boxes to instruct what information to include when generating and matching a name for the business process. Optional.

Select from:

  • Destination Identification (selected by default)
  • Origin Identification (selected by default)
  • X12 Group Version ID Code/EDIFACT Message Version and Release Number (selected by default)
Note: If you are using a generated business process name (If Specify the extracted 820 business process selection method is set to Generating the business process name from the data), the Sterling B2B Integrator tries to generate and match the following business processes:
  • First, it tries to generate and match the business process in the primary name format (replacing the values that are selected for the corresponding value in the message).
  • Second, it tries to generate and match the First Backup Name.
  • Third, it tries to generate and match the Second Backup Name.
  • Fourth, if there is not an existing business process that matches the names generated in steps 1-3, an error is generated.

Only occurs if Generate an error if no generated business process name exists in the system is set to Yes.

First Backup Name Format
The first backup name format to use when generating a business process name. The system allows for two alternatives if the Primary Name Format is not found—checking for the First Backup Name Format and then, if that is not found, checking for the Second Backup Name Format. Optional.

Select from:

  • Destination Identification
  • Origin Identification
  • X12 Group Version ID Code/EDIFACT Message Version and Release Number (selected by default)
Note: If you are using a generated business process name (If Specify the extracted 820 business process selection method is set to Generating the business process name from the data), the Sterling B2B Integrator tries to generate and match the following business processes:
  • First, it tries to generate and match the business process in the primary name format (replacing the values that are selected for the corresponding value in the message).
  • Second, it tries to generate and match the First Backup Name.
  • Third, it tries to generate and match the Second Backup Name.
  • Fourth, if there is not an existing business process that matches the names generated in steps 1-3, an error is generated.

Only occurs if Generate an error if no generated business process name exists in the system is set to Yes.

Second Backup Name Format
The second backup name format to use when generating a business process name. The system allows for two alternatives if the Primary Name Format is not found—checking for the First Backup Name Format and then, if that is not found, checking for the Second Backup Name Format. Optional.

Select from:

  • Destination Identification
  • Origin Identification
  • X12 Group Version ID Code/EDIFACT Message Version and Release Number
Note: If you are using a generated business process name (If Specify the extracted 820 business process selection method is set to Generating the business process name from the data), the Sterling B2B Integrator tries to generate and match the following business processes:
  • First, it tries to generate and match the business process in the primary name format (replacing the values that are selected for the corresponding value in the message).
  • Second, it tries to generate and match the First Backup Name.
  • Third, it tries to generate and match the Second Backup Name.
  • Fourth, if there is not an existing business process that matches the names generated in steps 1-3, an error is generated.

Only occurs if Generate an error if no generated business process name exists in the system is set to Yes.

Invoke a business process if translation or extraction errors occur
Specify whether to invoke a business process if translation or extraction errors occur. Required. Valid values are Yes and No.
Error Business Process Name Mode
Valid values are:
  • Specify
  • Generate from data

Required.

Note: Only displayed if the Invoke a business process if translation or extraction errors occur is set to Yes.
Business Process for Non-Compliant Documents
Select the business process for the non-compliant documents from the list. Required.

Only displayed if the Error Business Process Name Mode is set to Specify.

Primary Name Format
Check boxes to instruct what information to include when generating and matching a name for the business process. Optional.

Select from:

  • Destination Identification (selected by default)
  • Origin Identification (selected by default)
  • X12 Group Version ID Code/EDIFACT Message Version and Release Number (selected by default)
Note: If you are using a generated business process name (If Error Business Process Name Mode is set to Generate from data), the Sterling B2B Integrator tries to generate and match the following business processes:
  • First, it tries to generate and match the business process in the primary name format (replacing the values that are selected for the corresponding value in the message).
  • Second, it tries to generate and match the First Backup Name.
  • Third, it tries to generate and match the Second Backup Name.
  • Fourth, if there is not an existing business process that matches the names generated in steps 1-3, an error is generated.

Only occurs if Generate an error if no generated business process name exists in the system is set to Yes.

First Backup Name Format
The first backup name format to use when generating a business process name. The system allows for two alternatives if the Primary Name Format is not found—checking for the First Backup Name Format and then, if that is not found, checking for the Second Backup Name Format. Optional.

Select from:

  • Destination Identification
  • Origin Identification
  • X12 Group Version ID Code/EDIFACT Message Version and Release Number (selected by default)
Note: If you are using a generated business process name (If Error Business Process Name Mode is set to Generate from data), the Sterling B2B Integrator tries to generate and match the following business processes:
  • First, it tries to generate and match the business process in the primary name format (replacing the values that are selected for the corresponding value in the message).
  • Second, it tries to generate and match the First Backup Name.
  • Third, it tries to generate and match the Second Backup Name.
  • Fourth, if there is not an existing business process that matches the names generated in steps 1-3, an error is generated.

Only occurs if Generate an error if no generated business process name exists in the system is set to Yes.

Second Backup Name Format
The second backup name format to use when generating a business process. The system allows for two alternatives if the Primary Name Format is not found—checking for the First Backup Name Format and then, if that is not found, checking for the Second Backup Name Format. Optional.

Select from:

  • Destination Identification
  • Origin Identification
  • X12 Group Version ID Code/EDIFACT Message Version and Release Number
Note: If you are using a generated business process name (If Error Business Process Name Mode is set to Generate from data), the Sterling B2B Integrator tries to generate and match the following business processes:
  • First, it tries to generate and match the business process in the primary name format (replacing the values that are selected for the corresponding value in the message).
  • Second, it tries to generate and match the First Backup Name.
  • Third, it tries to generate and match the Second Backup Name.
  • Fourth, if there is not an existing business process that matches the names generated in steps 1-3, an error is generated.

Only occurs if Generate an error if no generated business process name exists in the system is set to Yes.

Generate an error if no generated business process name exists in the system
Specifies whether to generate an error if the Business Process selected is not found. Valid values are Yes (default) and No.
Note: Only displayed if Error Business Process Name Mode is set to Generate from data.
Extraction Options
Business process data extraction. Valid values:
  • Determined by business process (default)
  • Extract to a file system directory
  • Extract to a mailbox
Data Extraction Directory
Directory for data extraction. Optional.
Data Extraction Filename
Filename for data extraction. Optional.
Data Extraction Mailbox
Mailbox for data extraction. Required.
Data Extraction Mailbox Message Name
Mailbox message name for data extraction. Optional.