Skip to main content

Data Interface Requirements - Completed Purchase Orders

Judi Zietsman avatar
Written by Judi Zietsman
Updated over 3 months ago

Completed Purchase Orders

File name

pohist.csv

Importance

Preferred

Description

Completed purchase order lines and their associated receipts. Used to assess supplier delivery performance, adjust safety stock, and estimate lead times.

⚠️ Note: Purchase order lines with multiple deliveries will produce multiple records where only the Date of Receipt and Quantity Received differ.

Criteria

Include all closed purchase order lines completed in the last 12 months.

For large volumes of data, the 12-month history can be provided as a one-off extract, and thereafter only the last 30 days of completed POs are required on an ongoing basis.


Columns

Pos.

Name

Type

Importance

Description

1

Item Code

Char

Required

Product / SKU code

2

Location

Char

Required

Warehouse/branch code

3

Supplier Code

Char

Required

Vendor code of the supplier

4

Order Number

Char

Required

Purchase order number

5

Line Number

Char

Required

Purchase order line number

6

Order Date

Date

Required

Date the purchase order was raised. Format: YYYY/MM/DD

7

Order Quantity

Integer

Required

Original quantity ordered (in Netstock unit of measure)

8

Expected Arrival Date

Date

Preferred

Expected arrival date. Format: YYYY/MM/DD

9

Order Urgency

Char

If Applicable

Categorize urgency:
ST = Standard order (default)
EM = Emergency order (forced faster than standard lead time).
Helps prevent emergency deliveries from skewing lead time performance.

10

Quantity Received

Integer

Required

Quantity delivered by the vendor (in Netstock unit of measure)

11

Date of Receipt

Date

Required

Date the delivery was received. Format: YYYY/MM/DD

12

Purchase Unit Cost

Decimal

If Applicable

The purchase unit cost for this item when purchased (in Netstock unit of measure).


Forget about these 👇 😞 😐 😃 Have your say here!

Did this answer your question?