Order Model 1 -
Discrete Purchase Order, Established Customer, Established Product, Version 2.0
Status: Provisional Ratification by Committee April 2000. Created as part
of recast of original order models, Pre-2000 Version C (Balloted and Ratified by
Membership, November 1996), into Replenishment Scenarios.
Data Requirements by Order Type - Standalone PO (ORD1)
This section contains a "technology-independent" view of the
data requirements for this order type. The individual technologies have specific
requirements - see Index of Business Documents for more
This section contains a "technology-independent" view
of the data requirements for Forecast/Planning requirements. The individual
business content and technology standards have specific requirements - see Index of
Business Documents for more information.
1 inherits Basic Order Data and Basic Line Item data from the Class Diagram: Basic Data Requirements.
The additional information sent in Blanket Order files is somewhat different than what is sent in
other types of order files. This
order type will contain n major pieces of
information. They are:
All of these pieces of information are necessary for a supplier to
process the buyer's order.
The following list of PO contents is standards-neutral. Different
standards may require elements that are not on this list; cardinality
(mandatory vs. optional, number of occurrences) in the standards may vary. We have not gotten as far as taking
a stand on which things should be expressed as name-value pairs (qualifier +
data) and which should be expressed as standalone data elements and which as
attributes of an element; most standards have developed beyond that point
anyway. We merely want to say what
information needs to be in a purchase order.
Order Identification (PO
Number, Document Number,
whatever) - mandatory
But we note that for blanket
orders (a different animal altogether), line item number will probably
Line Item Total
Unit of Measure - mandatory
Price - mandatory
Unit of Measure - - mandatory
Unit associated with the
price (not the delivery quantity),
e.g. per each, per hundred, per thousand, etc.
Currency Code - mandatory
Should be pre-established,
however, some jurisdictions require currency code to be explicitly sent;
to avoid having to keep track of the requirements of every jurisdiction,
this should be mandatory.
Tax Exemption Status - mandatory
Price basis - mandatory
Code indicating whether
price is based on contract, catalog, or quote
Contract number optional
Contract number is
optional even if pricing is based on a contract referencing the
contract number is not legally required but is good business practice
Delivery quote number optional
Price quote number optional
Ship instructions optional
Overrides may be sent;
standard ship instructions, transit times, etc. should be
Delivery Date optional
Actually, we were undecided
about this. There are many
cases where the buyer doesnt specify a delivery date, such as when
you order things from a
storefront web site; however,
the implication is that this means delivery is wanted
ASAP, so there is a de facto delivery date.
Elements need to be
available for specifying delivery date
The standard PO needs to
support the specification of multiple delivery dates.