Difference between revisions of "Purchasing & Procurement"
Jump to navigation
Jump to search
Stefanseiler (talk | contribs) |
Stefanseiler (talk | contribs) |
||
| Line 20: | Line 20: | ||
*Main data objects | *Main data objects | ||
**[[Purchase requisition]] | **[[Purchase requisition]] | ||
* | **[[Purchase order]] | ||
*[[Purchase order]] | **[[Customer Order|Customer orders]] | ||
* [[Customer Order|Customer orders]] | |||
Revision as of 13:49, 1 October 2025
Purchasing & Procurement always adheres to this core flow inside the purchasing organization:
- Internal Order - Users are creating purchase requisitions (internal orders) to document demand inside the company
- Internal Order Approval - Internal orders in some scenarios have to undergo approval process before they are handed over to purchasing (e.g. internal budgeting, material approval flows, ... )
- Purchasing Automation - The Purchasing Automation Engine creates preliminary purchase orders, with the goal to optimize the individual purchase order for best purchasing conditions (money & delivery speed)
- Purchase Order Pooling - Preliminary purchase orders can be pooled to aggregate them by specific rules for better purchasing conditions. The result of this step is the issuance of purchase orders.
- Purchase Order Approval - Finally the purchase order must be approved by internal parties (e.g. fiscal approval processes)
- Purchase Order Transmission - the trigger point of the P2P process, where the purchase orders are handed over to the suppliers.
Main data objects
See also
- P2P System - Procure to Pay system
- S2P System - Source to Pay system
- Purchasing Automation Engine
- Main data objects