Clickable Business Models eBusiness Education Acronyms Cross References
B2B Content Standards EC Technology Standards Glossary Implementation Guidelines
Implementation Options General Recommendations References Methodology/Legends
 Home | Copyright Notice and Legal Disclaimers | Navigation Help | Tour! | Downloads | Contact Us | Site Index | Search
 Order Models Index | Supporting Documentation | Downloads | FAQs |
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)

Special Notes:            

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 information.


Inheritance of Basic (Common) Data

Order Model 1 inherits Basic Order Data and Basic Line Item data from the Class Diagram: Basic Data Requirements.

 


Contents of Standard Purchase Orders

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.

Order Model 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.


Last updated 01 February 2003