Standard purchase order number validation should be when a purchase order number is guaranteed to be unique across all company numbers, purchase order types, and suffixes. JD Edwards purchase orders differ from standard purchase orders. JD Edwards ERP system identifies a purchase order uniquely in the "F4311" purchase order header table using the following four keys.

• PONUMBER

• COMPANYCODE

• POTYPE

• POSUFFIX

Multiple records in the PO_HEADER table can have the same purchase order number. Because of this, database queries must account for other key fields.

When a purchase order number is extracted, Kofax AP Agility automatically separates the purchase order number and the purchase order type. This is done on the server side as well as in the Validation activity when the whole value is entered into the purchase order number field, and if the purchase order type is the first or last two characters of the value. The purchase order type is placed into a mandatory purchase order extension field.

In instances where the purchase order type is always a constant such as "OP," the JD Edwards configuration is not appropriate. In these instances, an alternate approach that uses the purchase order number and the company code to perform a lookup in the purchase order header table is needed. As the company code field forms part of the key for reading the purchase order, it cannot default from the purchase order. The company code is usually found as part of the image filename from the scanning processes. This is the most effective method of finding the company code. However, as an alternative, you can use the company code from the bill-to details on the invoice.