Understanding the Procurement Application
End-to-end scope
Oracle Procurement Cloud links supplier management, sourcing, supplier qualification, contracts, requisitions, purchasing, receiving, and payables. The exam tests where a setup choice changes document behavior, not just page names. A requisition is demand; a purchase order is a commitment; a receipt records delivery; an invoice is matched to the order and receipt. Supplier header and site data carry payment, tax, and purchasing controls.
Business unit model
A procurement business unit owns purchasing documents and negotiations. A requisitioning business unit creates demand. The default procurement business unit on the requisitioning BU determines which procurement BU processes the requisition. Buyers and procurement agents need roles scoped to the correct BU. Catalog content, document styles, and approval rules can vary by BU.
Worked example
A requester in the US business unit orders a catalog item. The requisitioning BU is US, and its default procurement BU is US Procurement. The supplier site is validated for US Procurement, the PO is created there, receipt occurs at the requester location, and the invoice matches. If the default procurement BU points to a shared-services BU, the requisition routes to the wrong agents and the supplier site may fail validation.
Traps
Do not treat the supplier header as sufficient; site-level controls matter. Do not assume every requisition becomes a purchase order; internal fulfillment can apply. Do not confuse an approval action with a document action.