Purchase Order 
A request from a purchaser to a supplier to deliver a specified quantity of goods, or perform a specified service, at a specified price within a specified time
Technical Data
Entity Type |
Business Object |
Software Component Version |
ESM ERP 606 |
PurchaseOrder |
|
Object Category |
Business Process Object |
Business Context and Use
Business object Purchase Order is used to procure products.
Features
Industry-Specific Information for SAP Apparel and Footwear
To suit the AFS specific requirements, the following concept is used for the Purchase Order:
For Synchronous services
In AFS Purchasing document can be processed at SKU (schedule line) level. The AFS concept for Purchase Order uses item-subitem approach to represent the document structure in the backend. It means that the item in AFS backend is represented as main item and the schedule line is represented as subitem. Each subitem carries reference of main item as parent item. A unique item number for each subitem is generated during save of AFS purchase order. Determination of value-added-services and seasons data happens during save of AFS purchase order.
For example, consider a scenario where a Purchase Order has to be created with one item (AFS material -Shirt) and having two schedule lines with Grid Values (Red and Green) each of quantity 10. The data passed is as shown below:
Item No- 10, Parent Item Number- Nil, Material- Shirt (main item)
Item No- 11, Parent Item Number- 10, Material- Shirt, Grid Value- Red, Quantity- 10 (subitem- Mapped as AFS schedule line1 in the backend)
Item No- 12, Parent Item Number- 10, Material- Shirt, Grid Value- Green, Quantity- 10 (subitem- Mapped as AFS schedule line2 in the backend)
The data is passed in the same way as in the case of the synchronous services, except that the Material Variant numbers based on AFS Grid Value are passed. For example, Material- ShirtRed (Material Variant)
Item No- 10, Parent Item Number- Nil, Material- Shirt (main item)
Item No- 11, Parent Item Number- 10, Material- Shirt, Grid Value- Red, Quantity- 10 (subitem- Mapped as AFS schedule line1 in the backend)
Item No- 12, Parent Item Number- 10, Material- Shirt, Grid Value- Green, Quantity- 10 (subitem- Mapped as AFS schedule line2 in the backend)
For Asynchronous services
The data is passed in the same way as in the case of the synchronous services, except that the Material Variant numbers based on AFS Grid Value are passed. For example, Material- ShirtRed (Material Variant)
Material variant is not based on AFS Stock Categories. AFS stock category can be determined using dynamic filling of category customizing in the AFS backend.
Note: Each sub-Item must have only one schedule line . If more than one schedule lines exists, then only the first one is considered.