Field exceptions: Examples

Here are some examples of how to solve common problems by creating field exceptions.

The scenario

Receiver 1 and Receiver 2 are different service centers that belong to the same organization. Sender X is used by both of them. The format of the purchase order numbers issued by Receiver 1 and Receiver 2 differs:

Receiver 1: 123456 (six numerals)

Receiver 2: Buy2-1234 ("Buy2-" is always used as the prefix, followed by four numerals)

Those purchase order numbers are subsequently quoted on the documents.

In addition, Sender X has two bank accounts and prints both account numbers on all documents. However, Receiver 1 only requires the first bank account number and has no need for the second.

The current document profile used to process documents from Sender X is set up to:

  1. Capture purchase order numbers (DocumentOrderNumber) using the format specification: X(6-9). This covers both of the above purchase order formats.

    Problem 1: The format specification is general so that it accommodates two different formats. As a result, sometimes other values on documents also match this format and are incorrectly interpreted as being the purchase order number. This causes extra work for Verify operators.

  2. Capture two bank account numbers: SupplierAccountNumber1 and SupplierAccountNumber2.

    Problem 2: This creates unnecessary work for Receiver 1, who does not need to capture and process this number.

Solution to problem 1: Differentiate between the two purchase order numbers

Solution to problem 2: Ignore the second bank account for Receiver 1