Introduction

control number processing is an important part of trading partner workflow and helps you manage the processing of the transactions and files under the trading partner trade relationships. As a part of this process, XEngine validates or generates control numbers during native data processing and XData generates control numbers. Trading Partner Management allows you to define the control number settings and assign them to trade relationships. These settings consist of a scope, type, increment value, and initial value and allow you to set the parameters for control number generation and validation.

Control number settings scope

Trading Partner Management allows you to select one of the following three scopes for the control number settings:

• Local: This scope is defined within the parent data node and has no effect on the sibling of the parent data nodes. For each parent data node, handling of control numbers on the child data nodes is reset to the defined starting point value.
• Global: When this scope is selected, control numbers are processed globally in the file on the same data node level as if all sibling data nodes are merged into one scope.
• Persisted: This scope is used when you want to validate the control numbers across Electronic Data Interchange (EDI) files and transactions for a given partner.

Control number settings type

Trading Partner Management allows you to select one of the following four Types for control number Settings:

• Sequential: You can choose an initial value which is used as the first control number and define the increment value which Trading Partner Management will add to each control number to get the next control number in the exact sequential order.
• Chronological: For Outbound Transactions, you can choose an initial value which will be used as the first control number and define the increment value which Trading Partner Management adds to each control number to get the next control number. For inbound transactions, the next control number value has to be greater than the previous number but does not necessarily have to be sequential based on any defined increment value.
• Duplicate: You can choose this setting for inbound validation to disallow the processing of duplicate control numbers. When this setting type is selected, Trading Partner Management checks the control number against the previously stored control numbers and throws an error when a duplicate is retrieved.
• None: This is the default control number settings type and when this type is selected there is no validation and generation of control numbers.

Note Only admin users and partnership owners can add or modify the control number settings.

Note The control number settings are only applicable for HIPAA, X12 standards.