Use the Purchase Order Receipt Interface to load purchase order receipt information using data from external applications. Information you load using this interface adds to the data already stored in PENTA.

Data files you load must have a Request Type assigned to the R Interface Type.

System Option 341 (PO Receipts IF-Auto Distrib) controls how PENTA distributes batches created by the interface request. If set to:

Y - PENTA automatically distributes the batch and you cannot modify it.
N - PENTA loads all error-free in balance records into the Purchase Order Receipts window and you are responsible for distributing them.

Limitations & Restrictions

PENTA places the following limitations and restrictions on purchase order receipt information loaded with the interface:

The User Id entered in the interface data file is the only user who can edit and distribute the purchase order receipt batch.

The person loading the interface file does not have to be the user identified in the Header Record. Zach can load the file, but if Larry is the user in the Header Record, only he can edit and distribute the batch once Zach loads the file.

If PENTA rejects a record, you cannot resubmit the file because a batch already exists for the file name and file type. In order to re-submit the information, rename the interface file and process the interface initiation process once again.

Where to View Loaded Data

If System Option 341 is set to N, you can review interfaced data in the Purchase Order Receipt window. (If this System Option is Y, error-free records are automatically distributed.)

If necessary, you can make corrections and/or late entries directly in PENTA. After loading, reviewing, and modifying the data, you can use PENTA to process the receipt batch and create the necessary accounting entries.

Available Tables

1 Header Record
2 Purchase Order Detail Record
3 Miscellaneous Attributes Detail Record
4 Purchase Order Line Detail Record
5 Tracking Detail Record
6 Warehouse Distribution Detail Record

Header Record

The following information relates to the INTR_PO_RCPT_HDR table.

Column	Entry	Format	Description

Column	Entry	Format	Description
INTR_RQST_ID	Key	C! 13	The interface request value that you enter to initiate the interface process. The value must be consistent for all records PENTA should process together.
RECORD_COUNT	Key	I 10	Each batch includes a count of the Detail Records within the file. If the number in the Header Record differs from the number read by PENTA, no update occurs and PENTA rejects the entire file.
D_RECEIPT_DATE	Key	D	The date you received the PO item(s). Each position must be zero or greater. For inventory-related purchase orders, PENTA uses this date for the accounting entry to increase the Inventory subledger account and the PO Receipt Accrual account defined in the Warehouse Information window.
DATA_CHECK_ VERIFIER	Opt	I 8	PENTA adds the Units columns in the POLINE and WHSEDISTR records, and compares the eight least significant digits to the left of the decimal point to this value.
RECORD_NUM	Opt	I 10	Do not assign this value. PENTA assigns this record number, which you can use to identify records with errors or warning messages.
USER_ID	Req	C 6	Id of the employee performing the load process. This user_id must exist in PENTA.
MODIFICATION_ DATE	Opt	D	Once the process completes, this displays the date PENTA marked the record as modified in the database. The current date is the default value.

Purchase Order Detail Record

The following information relates to the INTR_PO_RCPT_PO table.

Column	Entry	Format	Description

Column	Entry	Format	Description
INTR_RQST_ID	Key	C! 13	The interface request value that you enter to initiate the interface process. The value must be consistent for all records PENTA should process together.
PO_OU_ID	Req	X	The organizational unit assigned to the purchase order. PENTA validates this entry against the ORGANIZATION_UNIT table. If this value is invalid, PENTA rejects all records associated with the invalid PO OU Id.
PO_NUMBER	Req	X	PENTA validates the purchase order number against the PO_MSTR table. If this value is invalid for the associated PO OU Id, PENTA rejects all records associated with the invalid PO Number.
EMP_ID	Opt	X	This identifies the employee that has received the products. This entry must exist as a valid, active entry within the Employee Payroll Information window. PENTA displays this value in the Receipt History pop-up window in the Purchasing Inquiry windows.
RECV_DATE	Opt	D	This identifies the receipt date if it is different from the Header record’s receipt date. PENTA displays this value within the Receipt History pop-up window in the Purchasing Inquiry windows.
D_RECV_DATE	Key	D	Date you received the Purchase Order. For inventory-related Purchase Orders, PENTA uses this date for the accounting entry to increase the Inventory subledger account and the PO Receipt Accrual account defined on the Warehouse’s main record.
PACKING_SLIP_NUM	Opt	C 30	Use this column to identify the packing slip number associated with the Receipt document. PENTA displays this value within the Receipt History pop-up window in the Purchasing Inquiry windows.
RECORD_NUM	Opt	I 10	Do not assign this value. PENTA assigns this record number, which you can use to identify records with errors or warning messages.
USER_ID	Req	C 6	Id of the employee performing the load process. This user_id must exist in PENTA.
MODIFICATION_ DATE	Opt	D	Once the process completes, this displays the date PENTA marked the record as modified in the database. The current date is the default value.

Miscellaneous Attributes Detail Record

The following information relates to the INTR_PO_RCPT_MISC_ATTR table

Column	Entry	Format	Description

Column	Entry	Format	Description
INTR_RQST_ID	Req	C! 13	The interface request value that you enter to initiate the interface process. The value must be consistent for all records PENTA should process together.
PO_OU_ID	Req	X	The OU associated with the purchase order.
PO_NUM	Req	X	The Id of the purchase order.
PO_LINE_NUM	Req	I 9	PENTA validates the purchase order line number against the PO_DTL table.
TO_LOCATION_ID	Req	C 6	To Location should be valid for the warehouse associated with the purchase order from the last PO record. Required if the From Distribution Type column is W; otherwise, do not enter a value.
TRACKING_ATTR_ VALUE	Req	C 30	Value of the tracking attribute for the Product.
PROD_ATTRIBUTE_ID	Req	C 15	A value such as serial number that you want to track for a product on receipts and transfers. In most cases, products associated with a tracking attribute have low quantities in the warehouse but are typically the higher-priced items in the warehouse. For that reason, you may want to track which specific product you are receiving for future reporting purposes.
ATTR_VALUE	Req	C 30	Enter non-tracking attributes, such as color, style, type, etc., that you want to maintain for an individual product.
RECORD_NUM	Opt	I 10	Do not assign this value. PENTA assigns this record number, which you can use to identify records with errors or warning messages.
USER_ID	Req	C 6	Id of the employee performing the load process. This user_id must exist in PENTA.
MODIFICATION_ DATE	Opt	D	Once the process completes, this displays the date PENTA marked the record as modified in the database. The current date is the default value.

Purchase Order Line Detail Record

The following information relates to the INTR_PO_RCPT_PO_LINE table.

Column	Entry	Format	Description

Column	Entry	Format	Description
INTR_RQST_ID	Key	C! 13	The interface request value that you enter to initiate the interface process. The value must be consistent for all records PENTA should process together.
PO_OU_ID	Req	X	The organizational unit assigned to the purchase order. PENTA validates this entry against the ORGANIZATION_UNIT table. If this value is invalid, PENTA rejects all records associated with the invalid PO OU Id.
PO_NUM	Req	X	PENTA validates the purchase order number against the PO_MSTR table. If the entered PO Number does not exist for the associated PO OU Id, PENTA rejects all records associated with the invalid PO Number.
PO_LINE_NUM	Opt	I 9	PENTA validates the purchase order line number against the PO_DTL table.
UNITS_RCVD	Opt	F 12.3	The number of units received. This is the Purchase Units of Measure (PUM) quantity – not the Stocked Unit of Measure (SUM) quantity.
RECORD_NUM	Opt	I 10	Do not assign this value. PENTA assigns this record number, which you can use to identify records with errors or warning messages.
USER_ID	Req	C 6	Id of the employee performing the load process. This user_id must exist in PENTA.
MODIFICATION_ DATE	Opt	D	Once the process completes, this displays the date PENTA marked the record as modified in the database. The current date is the default value.

Tracking Detail Record

The following information relates to the INTR_PO_RCPT_TRACKING table.

Column	Entry	Format	Description

Column	Entry	Format	Description
INTR_RQST_ID	Req	C! 13	The interface request value that you enter to initiate the interface process. The value must be consistent for all records PENTA should process together.
PO_OU_ID	Req	X	The Id of the OU associated with the purchase order.
PO_NUM	Req	X	The Id of the purchase order.
PO_LINE_NUM	Req	I 9	PENTA validates the purchase order line number against the PO_DTL table.
TO_LOCATION_ID	Req	C 6	To Location should be valid for the warehouse associated with the purchase order from the last PO record. Required if the From Distribution Type column is W; otherwise, do not enter a value.
ATTR_VALUE	Req	C 30	Enter non-tracking attributes, such as color, style, type, etc., that you want to maintain for an individual product.
PROD_ATTRIBUTE_ID	Opt	C 15	A value such as serial number that you want to track for a product on receipts and transfers. In most cases, products associated with a tracking attribute have low quantities in the warehouse but are typically the higher-priced items in the warehouse. For that reason, you may want to track which specific product you are receiving for future reporting purposes.
UNITS	Req	F 12.3	The number of units.
RECORD_NUM	Opt	I 10	Do not assign this value. PENTA assigns this record number, which you can use to identify records with errors or warning messages.
USER_ID	Req	C 6	Id of the employee performing the load process. This user_id must exist in PENTA.
MODIFICATION_ DATE	Opt	D	Once the process completes, this displays the date PENTA marked the record as modified in the database. The current date is the default value.

Warehouse Distribution Detail Record

The following information relates to the INTR_PO_RCPT_WHSE_DISTR table.

Column	Entry	Format	Description

Column	Entry	Format	Description
INTR_RQST_ID	Key	C! 13	The interface request value that you enter to initiate the interface process. The value must be consistent for all records PENTA should process together.
PO_OU_ID	Req	X	The organizational unit assigned to the purchase order. PENTA validates this entry against the ORGANIZATION_UNIT table. If this value is invalid, PENTA rejects all records associated with the invalid PO OU Id.
PO_NUMBER	Req	X	PENTA validates the purchase order against the PO_MSTR table. If the entered PO Number does not exist for the associated PO OU Id, PENTA rejects all records associated with the invalid PO Number.
PO_LINE_NUM	Opt	I 9	PENTA validates the purchase order line number against the PO_DTL table.
TO_LOCATION_ID	Key	C 6	To Location should be valid for the warehouse associated with the purchase order from the last PO record. Required if the From Distribution Type column is W; otherwise, do not enter a value.
UNITS	Key	F 12.3	The number of units distributed to this location. This is in the Stocked Unit of Measure (SUM) quantity.
RECORD_NUM	Opt	I 10	Do not assign this value. PENTA assigns this record number, which you can use to identify records with errors or warning messages.
USER_ID	Req	C 6	Id of the employee performing the load process. This user_id must exist in PENTA.
MODIFICATION_ DATE	Opt	D	Once the process completes, this displays the date PENTA marked the record as modified in the database. The current date is the default value.

Penta Knowledge Base

Purchase Order Receipt Interface: Table Driven Method