Purchase Order Processing
Purchase Order Processing is the main component of Seasonal Procurement. Purchase Order Processing contains the workbench application PO Manager, from which you can access all other applications in PO Processing, for example, the Order List, the Grouped Purchase Order Document, the Purchase Order, Open-to-Buy, and the Purchase Order Monitoring views.
Purchase Order Processing supports integration with planning components, such as, Operational Assortment Planning and Control (OAPC).
It is closely integrated with the applications named above, which are also implemented as workbenches. For more information, see:
· Grouped Purchase Order Document
· Purchase Order Processing (Seasonal Procurement)
For more information about the uniform user interface (for example, with data preparation in worklists) for these applications, see Standardized User Interface.
Seasonal Procurement uses Incoterms in the following ways:
· Incoterms appear in all purchase order document items and order list items in Seasonal Procurement.
· If you do not enter the Incoterms and Incoterms (Part 2) in the dialog box, the system determines these values automatically:
¡ The system determines the Incoterms from the vendor master, among other places.
¡ It determines the Incoterms (part 2) depending on the transfer date. You define this in Customizing for Seasonal Procurement under Scheduling → Assign Transfer Dates to Incoterms [part1]. The system copies the Arrival Region (description) belonging to the transfer date into the Incoterms (part 2).
If there is no arrival region, the system uses the Arrival Country (description).
In place of the standard ordering process, you can also implement a cross-docking procedure with prepacking for single-store vendor orders.
You can configure your order processing in Customizing for Seasonal Procurement under PO Processing → General Settings → Maintain Creation of Single-Store Purchase Orders so that the system groups purchase order items that have certain common criteria under a collective number, so that single-store purchase orders can then be generated from them.
· PO Manager
The application is used for the following:
¡ Processing documents
You can process order lists, grouped purchase order documents, and purchase orders.
¡ As a working environment for the manager
You have authorization to release documents and have quick access, for example, to the net values.
· Core Master Data Entry for Article Items
You can create a new article with core master data that is relevant for the order. This type of fast data entry is possible in the following applications:
¡ Order List
¡ Grouped Purchase Order Document
¡ Purchase Order
¡ PO Manager
For more information, see
Articles: Core Master
Record Processing.
· Status Report to OAPC
The program reports the status of order items that OAPC transfers to procurement back to OAPC. The order list, grouped purchase order document, and purchase order report back the current processing status and any changes (quantity, date, site).
· Purchasing-Group-Specific Purchasing
During the order process, the system checks whether the article is permitted for the purchasing group. This ensures that employees in a purchasing group do not execute any cross-purchasing-group purchase orders or orders from a different area.
You can configure purchasing that is not restricted by the purchasing group in Customizing for Seasonal Procurement under PO Processing → General Settings → Maintain Cross-Purchasing-Group Purchasing.
The following constraints apply:
· Item categories
Within the order list, the grouped purchase order document, and the purchase order, Order Processing supports the following item categories:
¡ Standard
¡ Consignment
· Account assignment
You cannot assign accounts to individual items in the order list, the grouped purchase order document, or the purchase order.

Use the standard Create Purchase Order function (transaction ME21N) to procure merchandise with account assignment.
· Stock transport orders
You cannot use stock transport orders.
· Currency
The currency used in the planning system and in Order Processing in Seasonal Procurement must be identical within a company code.
· OTB-specific constraints:
¡ Reconciliation of planning with the budget level
You cannot make any subsequent enhancements (for example, additional fields in the budget level) in Purchase Order Processing. To do so, use the revision of planned data.
¡ Planned data transfer
The interface for the planned data transfer only provides a data transfer from the planning system into Seasonal Procurement. You can only transport the data in this direction. The system updates current document data using standardized statistical methods (for example, data extraction for planning).
¡ Adjustment of the budgets by non-purchasing processes
The system does not adjust the budgets through other logistics processes (for example, under- or overdelivery during goods receipt).