Configuring Control Number Settings

Module for EDI uses the control number maximum, minimum, increment, and window settings to determine the next control number to expect, whether a control number is valid or invalid, and whether an invalid control number is a duplicate or an out-of-sequence control number. Module for EDI maintains these settings in the EDIControlNumber table.

Setting	Description	Default
control number	The next control number to expect. You can set an initial value. Module for EDI updates this setting so it is always set to the next expected control number.	1
control number increment	The value you want Module for EDI to use to increment a control number when determining the next expected control number.	1
control number maximum	The highest number the control number can be.	99999999999999
control number minimum	The lowest number the control number can be.	0 (for VDA) 1 (for all other standards)
control number window	A number used to compute a range of numbers. Module for EDI uses this range of numbers to determine whether an invalid control number is a duplicate or an out-of-sequence control number. For more information, see Invalid Control Numbers.	100

For example, Module for EDI receives an Interchange document that has an interchange header identifying sender A, receiver B, a production mode of Production, and a type of Envelope. The module locates the control number settings by locating the EDIControlNumber table entry for sender A, receiver B, where production mode is Production, and type is Envelope. If the module is validating a control number in an inbound document, and an EDIControlNumber table entry does not exist for the combination of sender/receiver, EDI standard/version, production mode, and type, the module:

Note:
It is possible for Module for EDI to encounter more than one sender/receiver pair that maps to the same Trading Networks internal ID. For example, when you have the same sender ID/receiver ID pair combination for two separate sender/receiver pairs, the two pairs map to the same Trading Networks internal ID. Because Module for EDI uses the same Trading Networks internal ID to identify senders and receivers in the EDIControlNumber table, both sender/receiver pairs correlate to the same row in the EDIControlNumber table. As a result, when Module for EDI receives a document from either sender/receiver pair, it will update the next expected control number in the same row of the EDIControlNumber table.

When your environment is set up so that Module for EDI maintains separate control number sequences for each sender/receiver pair, the module will indicate that the example’s control numbers are invalid. This is because the module checks the control number sequences for two sender/receiver pairs using the same EDIControl number entry.

To identify sender and receiver pairs correctly in this scenario, set the EDIAllowCustomControlNumberSequence property to true. When EDIAllowCustomControlNumberSequence is set to true, Module for EDI looks up the next control number using both the sender/receiver ID and the sender/receiver qualifiers.

Configure control number settings using either the Control Numbers page or the Partner Profiles page in My webMethods. For more information about configuring control number settings using the Control Numbers page, see Configuring Control Number Settings Using the My webMethods Control Numbers Page. For more information about configuring control number settings using the Partner Profiles page, see Configuring Control Number Settings Using the My webMethods Partner Profiles Page.