Delimited EDI Based ACH Application Codes

Edit online

If you select the ACH Message Category as Delimited EDI Based ACH Application, the pages displayed for the SEC code CTX are as follows:

Field
Description
Generate an acknowledgment
When an acknowledgement must be generated. Required. Valid values are:
  • Always
  • Only when requested by input (default)
  • Never
Generate an addenda record for the acknowledgment
When an addenda record for the acknowledgement must be generated. Required. Valid values are:
  • Yes
  • No
Map Name Mode
Mode in which to specify the map to use to perform a compliance check.

Required. Valid values are:

  • Specify
  • Generate from data
Note: Only displayed if Generate an addenda record for the acknowledgment is set to Yes.
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.

Note: Only displayed if Map 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 map. Optional.

Select from:

  • SEC Code (selected by default)
  • Receiving DFI Identification (selected by default)
  • DFI Account Number
  • Originating DFI Identification (selected by default)
  • Company identification
  • Standard contained in addenda (selected by default)
  • X12 Transaction Set/EDIFACT Message Type (selected by default)
  • X12 Group Version ID Code/EDIFACT Message Version and Release Number (selected by default)
Note: If you are using a generated map name (If Map Name Mode is set to Generate from data), the Sterling B2B Integrator tries to generate and match the following maps:
  • First, it tries to generate and match the map 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 map that matches the names generated in steps 1-3, an error is generated.

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

First Backup Name Format
The first backup name format to use when generating a map 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:

  • SEC Code (selected by default)
  • Receiving DFI Identification
  • DFI Account Number
  • Originating DFI Identification
  • Company identification
  • Standard contained in addenda (selected by default)
  • X12 Transaction Set/EDIFACT Message Type (selected by default)
  • X12 Group Version ID Code/EDIFACT Message Version and Release Number (selected by default)
Note: If you are using a generated map name (If Map Name Mode is set to Generate from data), the Sterling B2B Integrator tries to generate and match the following maps:
  • First, it tries to generate and match the map 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 map that matches the names generated in steps 1-3, an error is generated.

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

Second Backup Name Format
The second backup name format to use when generating a map 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:

  • SEC Code
  • Receiving DFI Identification
  • DFI Account Number
  • Originating DFI Identification
  • Company identification
  • Standard contained in addenda
  • X12 Transaction Set/EDIFACT Message Type
  • X12 Group Version ID Code/EDIFACT Message Version and Release Number
Note: If you are using a generated map name (If Map Name Mode is set to Generate from data), the Sterling B2B Integrator tries to generate and match the following maps:
  • First, it tries to generate and match the map 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 map that matches the names generated in steps 1-3, an error is generated.

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

Generate an error if no generated map name exists in the system
Specifies whether to generate an error if the map name selected is not found. Valid values are Yes (default) and No.
Note: Only displayed if Map Name Mode is set to Generate from data.
“Unstream” X12 and EDIFACT data
Valid values are:
  • Yes
  • No (default)
Note: Only displayed if ACH Message Category is set to Delimited EDI Based ACH Application.
Validate EDI data using a map
Whether you would like to validate the data using a map. Valid values are:
  • Yes (default)
  • No
Handling of batches with discrepancies
Specify how to handle batches with discrepancies. Required. Valid values are:
  • Accept
  • Reject (default)
Map Name Mode
Mode in which to specify the map to use to perform a compliance check.

Required. Valid values are:

  • Specify
  • Generate from data
  • Default (X12 820 version 003020)
Note: Only displayed if Validate EDI data using a map is set to Yes.
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.

Note: Only displayed if Map 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 map. Optional.

Select from:

  • SEC Code (selected by default)
  • Receiving DFI Identification (selected by default)
  • DFI Account Number
  • Originating DFI Identification (selected by default)
  • Company identification
  • Standard contained in addenda (selected by default)
  • X12 Transaction Set/EDIFACT Message Type (selected by default)
  • X12 Group Version ID Code/EDIFACT Message Version and Release Number (selected by default)
Note: If you are using a generated map name (If Map Name Mode is set to Generate from data), the Sterling B2B Integrator tries to generate and match the following maps:
  • First, it tries to generate and match the map 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 map that matches the names generated in steps 1-3, an error is generated.

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

First Backup Name Format
The first backup name format to use when generating a map 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:

  • SEC Code (selected by default)
  • Receiving DFI Identification
  • DFI Account Number
  • Originating DFI Identification
  • Company identification
  • Standard contained in addenda (selected by default)
  • X12 Transaction Set/EDIFACT Message Type (selected by default)
  • X12 Group Version ID Code/EDIFACT Message Version and Release Number (selected by default)
Note: If you are using a generated map name (If Map Name Mode is set to Generate from data), the Sterling B2B Integrator tries to generate and match the following maps:
  • First, it tries to generate and match the map 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 map that matches the names generated in steps 1-3, an error is generated.

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

Second Backup Name Format
The second backup name format to use when generating a map 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:

  • SEC Code
  • Receiving DFI Identification
  • DFI Account Number
  • Originating DFI Identification
  • Company identification
  • Standard contained in addenda
  • X12 Transaction Set/EDIFACT Message Type
  • X12 Group Version ID Code/EDIFACT Message Version and Release Number
Note: If you are using a generated map name (If Map Name Mode is set to Generate from data), the Sterling B2B Integrator tries to generate and match the following maps:
  • First, it tries to generate and match the map 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 map that matches the names generated in steps 1-3, an error is generated.

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

Generate an error if no generated map name exists in the system
Specifies whether to generate an error if the map name selected is not found. Valid values are Yes (default) and No.
Note: Only displayed if Map Name Mode is set to Generate from data.
Translate delimited EDI document after extraction
Valid values are:
  • Yes
  • No (default)
Map Name Mode
Mode in which to specify the map to use to perform a compliance check.

Required. Valid values are:

  • Specify
  • Generate from data
Note: Only displayed if Translate delimited EDI document after extraction is set to Yes.
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.

Note: Only displayed if Map 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 map. Optional.

Select from:

  • SEC Code (selected by default)
  • Receiving DFI Identification (selected by default)
  • DFI Account Number
  • Originating DFI Identification (selected by default)
  • Company identification
  • Standard contained in addenda (selected by default)
  • X12 Transaction Set/EDIFACT Message Type (selected by default)
  • X12 Group Version ID Code/EDIFACT Message Version and Release Number (selected by default)
Note: If you are using a generated map name (If Map Name Mode is set to Generate from data), the Sterling B2B Integrator tries to generate and match the following maps:
  • First, it tries to generate and match the map 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 map that matches the names generated in steps 1-3, an error is generated.

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

First Backup Name Format
The first backup name format to use when generating a map 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:

  • SEC Code (selected by default)
  • Receiving DFI Identification
  • DFI Account Number
  • Originating DFI Identification
  • Company identification
  • Standard contained in addenda (selected by default)
  • X12 Transaction Set/EDIFACT Message Type (selected by default)
  • X12 Group Version ID Code/EDIFACT Message Version and Release Number (selected by default)
Note: If you are using a generated map name (If Map Name Mode is set to Generate from data), the Sterling B2B Integrator tries to generate and match the following maps:
  • First, it tries to generate and match the map 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 map that matches the names generated in steps 1-3, an error is generated.

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

Second Backup Name Format
The second backup name format to use when generating a map 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:

  • SEC Code
  • Receiving DFI Identification
  • DFI Account Number
  • Originating DFI Identification
  • Company identification
  • Standard contained in addenda
  • X12 Transaction Set/EDIFACT Message Type
  • X12 Group Version ID Code/EDIFACT Message Version and Release Number
Note: If you are using a generated map name (If Map Name Mode is set to Generate from data), the Sterling B2B Integrator tries to generate and match the following maps:
  • First, it tries to generate and match the map 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 map that matches the names generated in steps 1-3, an error is generated.

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

Generate an error if no generated map name exists in the system
Specifies whether to generate an error if the map name selected is not found. Valid values are Yes (default) and No.
Note: Only displayed if Map Name Mode is set to Generate from data.
Invoke a business process if translation or extraction errors occur
Indicates whether or not to invoke a business process on the extracted data if an error occurs. If Yes is selected, additional screens appears that allow you to specify a business process. Valid values are Yes and No. Required.
Error Business Process Name Mode
Valid values are:
  • Specify
  • Generate from data

Required.

Note: Only displayed if 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.
Note: Only displayed if 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:

  • SEC Code (selected by default)
  • Receiving DFI Identification (selected by default)
  • DFI Account Number
  • Originating DFI Identification (selected by default)
  • Company identification
  • Standard contained in addenda (selected by default)
  • X12 Transaction Set/EDIFACT Message Type (selected by default)
  • X12 Group Version ID Code/EDIFACT Message Version and Release Number (selected by default)
Note: If you are using a generated error 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:

  • SEC Code (selected by default)
  • Receiving DFI Identification
  • DFI Account Number
  • Originating DFI Identification
  • Company identification
  • Standard contained in addenda (selected by default)
  • X12 Transaction Set/EDIFACT Message Type (selected by default)
  • X12 Group Version ID Code/EDIFACT Message Version and Release Number (selected by default)
Note: If you are using a generated error 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 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:

  • SEC Code
  • Receiving DFI Identification
  • DFI Account Number
  • Originating DFI Identification
  • Company identification
  • Standard contained in addenda
  • X12 Transaction Set/EDIFACT Message Type
  • X12 Group Version ID Code/EDIFACT Message Version and Release Number
Note: If you are using a generated error 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.
Determine the Business Process By
Required. Valid values:
  • Look up contract dynamically
  • Specifying a contract
  • Specifying a business process (default)
  • Generate the business process name from data
  • Default Deenvelope BP for Contained Standard
Contract List
Select a previously created contract to associate with this envelope. Required.
Note: Displayed only if Determine the Business Process By is set to Specifying a contract.
Business Process List
Select a previously created business process to associate with this envelope. Required.
Note: Displayed only if Determine the Business Process By 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:

  • SEC Code (selected by default)
  • Receiving DFI Identification (selected by default)
  • DFI Account Number
  • Originating DFI Identification (selected by default)
  • Company identification
  • Standard contained in addenda (selected by default)
  • X12 Transaction Set/EDIFACT Message Type (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 Determine the Business Process by 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:

  • SEC Code (selected by default)
  • Receiving DFI Identification
  • DFI Account Number
  • Originating DFI Identification
  • Company identification
  • Standard contained in addenda (selected by default)
  • X12 Transaction Set/EDIFACT Message Type (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 Determine the Business Process by 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 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:

  • SEC Code
  • Receiving DFI Identification
  • DFI Account Number
  • Originating DFI Identification
  • Company identification
  • Standard contained in addenda
  • X12 Transaction Set/EDIFACT Message Type
  • X12 Group Version ID Code/EDIFACT Message Version and Release Number
Note: If you are using a generated business process name (If Determine the Business Process by 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 Determine the Business Process by 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.

In the Confirm page, verify all the settings and click Finish to save the configurations for the envelope.