PO Number Validation tab
These setting control the purchase order number validation. It also controls how service purchase orders are identified. Depending on what options are selected, different settings are available. Each setting below indicates if it is only available under certain circumstances.
- Max Word Count
-
The maximum number of OCR words that are permitted for the purchase order number.
The value for this option is set to 3 by default. This is the recommended value.
For example, 45 0000 0020 and 12345 - OP are both purchase order number alternatives, where each value separated by a space is also recognized as an individual OCR word. A hyphen is considered a separate OCR word, regardless of the geometric distance to neighboring values on either side.
- Set Company Code From PO
-
If selected, the system overwrites any existing content in the company code field with the company code that is derived from the purchase order.
This option is selected by default.
- Keep Case Sensitive
-
If selected, the system retains lower case characters in extracted purchase order numbers.
This option is cleared by default.
- Validate From SAP
-
If selected, the purchase order number field is validated against SAP during Validation.
Important This option is not available in the Azure cloud environment.This option is cleared by default.
- Validate From DB
-
If selected, the extracted purchase order number is validated against a database table.
In addition, the extracted purchase order must exist in the database table. Also, the vendor identified on the invoice must be the vendor on the purchase order. In an Oracle implementation, the invoice site ID address does not have to be the same as the PO order-form vendor site ID.
In all other cases, the purchase order number field is set to invalid.
Important This option and all of its dependent settings are not available in the Azure cloud environment.This option is cleared by default.
- Read PO Header via User Exit
-
If selected, the purchase order header details are found using a custom lookup using the ReadPurchaseOrder user exit.
Important This option is not available in the Azure cloud environment.This option is cleared by default.
- Use Stored Procedure
-
If selected, the PO header details are retrieved from a database using a stored procedure.
This option is available only when Validate From DB is selected above.
This option is cleared by default.
- Stored Procedure Name
-
The technical name of the stored procedure used to retrieve the PO header details.
This option is available only when Validate From DB and Use Stored Procedure are selected above.
- Stored Procedure Parameters
-
A comma-separated list of stored procedure parameter indexes from defined stored procedure settings relevant to calling the above stored procedure.
This option is available only when Validate From DB and Use Stored Procedure are selected above.
- Database Connection Name
-
The database connection that specifies the purchase order database connection string
This setting is available only when Validate From DB is selected above.
This setting is available only when Validate From DB is selected above.
- DB Schema
-
Enter the name of a schema to filter the list of database tables available for the selected Database Connection Name.
If this field is left blank, all database tables that you have permission to access, are displayed.
-
This setting is available only when Validate From DB is selected above.
- DB Table Name
-
Selec the name of the database table that contains the purchase order header information. The list is populated based on the selected Database Connection Name and if used, the specified schema. If the selected table has columns that match the settings below, they are populated automatically.
This setting is available only when Validate From DB is selected above.
- Use PO Partition
-
If selected, the purchase order database lookup uses a purchase order partition. Purchase order partitions are set against the organization that is configured in .
This setting is available only when Validate From DB is selected above.
This option is cleared by default.
- PO Partition Column
-
The PO Partition ID as specified in the PO Number Partition tab.
This option is available only when Validate From DB and Use PO Partition are selected above.
- DB PO
-
The name of the database table field that holds the purchase order number.
This setting is available only when Validate From DB is selected above.
- DB Vendor ID
-
The name of the database table field that holds the vendor ID for a given purchase order. This setting is mandatory for database validation.
This must be set to the internal vendor ID that the ERP system uses.
This setting is available only when Validate From DB is selected above.
- DB Site ID
-
The name of the database table column that holds the purchase order document currency. This setting is optional.
This setting is available only when Validate From DB is selected above.
- DB Currency
-
The name of the database table column that holds the purchase order document currency. This setting is optional.
This setting is available only when Validate From DB is selected above.
- DB Company Code
-
The name of the database table column that holds the company code of the purchase order.
This setting is available only when Validate From DB is selected above.
- DB Status
-
The name of the database table column that holds the status of the purchase order. For example, released, suspended, closed and so on.
This setting is available only when Validate From DB is selected above.
- DB Doc Type
-
The name of the database table column that holds the purchase order document type.
Note This is mandatory for JD Edwards purchase orders only.This setting is available only when Validate From DB is selected above.
- DB Business Unit
-
The name of the database table column that holds the business unit.
This setting is available only when Validate From DB is selected above.
- PO Key Includes Company Code
-
If selected, the single purchase order unique key in the PO header database lookup table consists of both the purchase order number and the company code.
Tip Do not select this option for JD Edwards implementations.This setting is available only when Validate From DB is selected above.
This option is cleared by default.
- JDE PO
-
If selected, the purchase order is assumed to belong to JD Edwards.
This setting is available only when Validate From DB is selected above.
- JDE PO Types
-
The comma-separated list of purchase order document type that indicate a JD Edwards purchase order.
This option is available only when Validate From DB and JDE PO are selected above.
This option is cleared by default.
- PeopleSoft PO
-
If selected, the purchase order is assumed to belong to PeopleSoft.
This option is cleared by default.
- PeopleSoft Business Units
-
The comma-separated list of business unites for PeopleSoft invoices.
This option is available only when Validate From DB and PeopleSoft PO are selected above.
- Service PO Types
-
The comma-separated list of purchase order document types that indicate a service purchase order.
The value for this option is set to blank by default.
- Service PO Item Categories
-
The comma-separated list of item categories and line types at the purchase order line item level that indicate a service.
The value for this option is set to 1,9 by default.
- Service PO Prefixes
-
The comma-separated list of purchase order prefixes that exclusively identify a service purchase order.
The value for this option is set to blank by default.
- Service PO UOMs
-
The comma-separated list of units of measure at the purchase order line item level, that exclusively identify a service purchase order.
The value for this option is set to AU,LE by default.
- Stop ERS PO
-
If selected, the system sends a purchase order to Validation for all ERS/self-billing purchase orders.
This option is selected by default.
- Stop ERS PO in Validation
-
If selected, the system does not allow a purchase order to pass Validation if it is marked as an ERS/self-billing purchase order.
This option is selected by default.
- Skip Duplicate PO Check
-
If a database lookup is activated and the purchase order number exists more than once in the purchase order header table, a document is sent to Validation. The user may choose to accept the PO in Validation, but line pairing is not carried out.
If selected, the system does not reject a purchase order if a duplicate record is found in the purchase order number header table. Instead, the system uses the first purchase order found, and line pairing is carried out as usual.
This option is cleared by default.
The following buttons are available at the bottom of the window.
- Save
-
Saves your changes and the window is closed.
- Reload
-
Deletes any unsaved changes and resets the field values back to the last saved settings.