Intended learning outcomes: Produce an overview on the object classes “order header”, and “partial order header”. Present in detail the attributes of the object classes “order header”, and “partial order header”.
The order header class combines all the data that represent the order as a whole. Its attributes can essentially be divided into the following subsets:
Firstly, attributes that describe the business partner. For a sales order, this is the customer. For a procurement order, it is the supplier; for a production order, it is the sales, R&D, or logistics department. These attributes include:
- Business partner ID and the address of the business partner
- Business partner’s object for
which the order is used
Secondly, attributes used to administer the order. These are attributes associated with the status of an order, typically:
- Order ID, that is, the order identification Validity date of the order (tender date, date on which order was issued, etc.)
- Kind of order (e.g., customer, procurement, production, or overhead order) Costing unit of the order (in order to combine orders to compare costs against profits) and other attributes to prepare for job-order costing
- Billing address
- Order status, that is, the administrative status of the order (e.g., in preparation, scheduled, released, started, cancelled, completed, inspected, deletable)
- Order conditions and other information that appears at the bottom of the order; allocation
to the order header means that a separate order footer class may be omitted
Thirdly, the attributes that concern planning & control of the order include:
- A flag to indicate whether it is a simulated or effective order
- The order priority
- The order urgency
- The order start date and the order end date or order completion date
- A flag indicating whether the dates are firm or may be postponed
The partial order header object class essentially incorporates the same attributes as the third subset of attributes for the order header class, plus the order ID, partial order ID (generally a consecutive number that supplements the order ID), and a description of the partial order.
Course section 17.1: Subsections and their intended learning outcomes
17.1 Order Data in Sales, Distribution, Production, and Procurement
Intended learning outcomes: Present the data structure of customers and suppliers. Describe the general data structure of orders in sales and distribution, production, and procurement. Disclose the data structure of the order and partial order header as well as the order position.
17.1.1 Customer and Supplier Data, and the Corporate Group Structure
Intended learning outcomes: Present the business object “business partner”: customer and supplier data. Identify the corporate group structure.
17.1.2 The General Data Structure of Orders in Sales and Distribution, Production, and Procurement
Intended learning outcomes: Explain the general data structure of an order in sales and distribution, production, or procurement. Disclose the basic object classes in an order database.
17.1.3 The Order Header Data and Partial Order Header Data
Intended learning outcomes: Produce an overview on the object classes “order header”, and “partial order header”. Present in detail the attributes of the object classes “order header”, and “partial order header”.
17.1.4 The Order Position Data
Intended learning outcomes: Produce an overview on the object class “order position”. Present in detail the attributes of the object class “order position”.
17.1.5 Inventories and Inventory Transactions Data
Intended learning outcomes: Produce an overview on the object classes for inventories. Present in detail the attributes of the object class “inventory transaction”.
