How It Works...
How It Works
Buyer-originating Procurement Transaction
Procurement Contracts
Procurement Planning
Procurement Control
Buyer-originating Procurement Transaction
For an introduction of the procurement aggregation cycle and an explanation of the difference between the Buyer-originating Procurement Transaction and the Supplier-originating Procurement Transaction, please refer to the Procurement Life Cycle Overview page.
In this version of the aggregated procurement cycle - the Buyer-originating Procurement Transaction - the buyer creates and sends digital Purchase Order (PO) object to the aggregator, where it (the buyer's PO), is transformed into a Sales Order; the aggregator then raises its own Purchase Order (which is based on the the Sales Order), and forwards it to the designated supplier. When it is received at the supplier, the aggregator's PO is turned into (the supplier's) Sales Order. The supplier picks and packs the goods, and then notifies the aggregator of its intention to deliver the goods (by raising a Delivery Notification). The aggregator in turn notifies the buyer that the ordered goods are on its way. When the goods have been delivered (by the supplier), the buyer acknowledges receipt of the goods with a Goods Received Voucher (GRV). The original buyer PO serves as the foundation for the GRV, which is forwarded to the aggregator. The aggregator in turn acknowledges the delivery by forwarding a Goods Received Acknowledgement to the Supplier. The aggregator also raises an Invoice (based on the GRV), which is sent to the buyer.
Certain exceptions may disrupt the standard flow described above, such as out-of-stock scenarios, and insufficient credit. The following swimlane diagram provides a comprehensive illustration of all the possible 'paths' the procurement cycle may take.
<swimlane.diagram>
The following table provides a summary of the procurement steps, with corresponding 'how-to' references where applicable:
Certain prerequisite data (such as the Master Procurement List) must be setup and ready prior to the transaction cycle being initiated; in other words, before the Buyer can create a Purchase Order, the Buyer's workspace must have certain master data ready. For more information about this requirement, please refer to the Catalogs and Master Procurement Lists page.
NEXT:
Supplier-Originating Procurement Transaction
Catalogs & Master Procurement Lists
Buyer Portal Functions
Supplier Portal Functions
Aggregator Portal Functions