Oracle Cloud Procurement key terms

An organizational unit that performs a specific business function and owns procurement transactions such as requisitions, purchase orders, and invoices. It determines the default ledger, currency, and approval routing for documents created within it.

A person granted the authority to create, approve, and manage purchasing documents on behalf of requesters. Agent authority is scoped by business unit, document type, and spending limits so buyers cannot exceed their delegated control.

A configuration that controls which fields, actions, and approval rules apply to a purchasing document type such as a purchase order or change order. It governs numbering, security, and what users can see or modify.

A condition-based rule that routes a purchasing document to the correct approvers based on attributes such as amount, category, or requester. Rules can be chained so multiple approvers act in sequence or in parallel.

A position-based structure of approvers used to determine who must approve a document when amount or other thresholds are met. It is separate from the supervisory hierarchy and can be assigned per document type.

A time-based rule that reassigns or notifies an approver when a document has waited too long without action. It prevents bottlenecks by moving stalled approvals up the approval hierarchy after a defined period.

The business unit in which a requisition is created and owned. It supplies defaults for the requisition and determines which catalog content and approval rules apply, even when the requisition is fulfilled by another business unit.

A classification of goods or services used to control purchasing policy, default accounts, approval rules, and sourcing. Categories can be structured hierarchically and assigned to catalog items and purchase order lines.

A tree structure of procurement categories where child categories inherit policy settings from parent categories. It supports reporting rollups and lets administrators apply rules at a broad level rather than item by item.

An internal request to purchase goods or services, created by an employee or requester. Once approved it becomes eligible to be placed on a purchase order or fulfilled through an internal transfer or catalog order.

A single item, service, or amount requested within a requisition, including quantity, price, need-by date, and delivery location. Lines can be grouped, split, or returned for correction during the approval process.

A requisition sent back to the requester or preparer for changes instead of being approved or rejected. It re-enters the approval flow once resubmitted, and the return reason is visible to the requester.

A legally binding document sent to a supplier committing to buy specified goods or services at agreed prices and terms. It can be created directly, from a requisition, or from a sourcing award.

A detailed row on a purchase order describing an item or service, its quantity, unit price, delivery date, and accounting distribution. Lines drive receipt, invoicing, and matching activities.

A modification to an existing approved purchase order that records what changed and requires its own approval. It preserves the original order history while updating quantities, prices, or terms.

A long-term agreement with a supplier that sets prices or terms for repeated purchases over a period. Buyers release orders against it rather than negotiating a new purchase order each time.

A purchasing agreement that commits a business to buy from a supplier under negotiated terms but does not itself obligate funds. Individual purchase orders are issued against it to actually commit spending.

A control that compares the purchase order, the goods receipt, and the supplier invoice before payment. Quantities and prices must fall within tolerance, otherwise the invoice is placed on hold for review.

A record confirming that ordered goods or services were delivered and accepted. It updates inventory or expense accounting and provides the receipt side of a three-way match.

A block that prevents an invoice from being paid until a discrepancy is resolved. Holds can be triggered by matching failures, missing receipts, or manual review, and each hold has a reason and release path.

An external party that provides goods or services to the organization. Supplier records hold addresses, contacts, payment terms, and tax details used across purchasing and payables transactions.

A specific location or address belonging to a supplier, used for ordering, receiving, and payment purposes. A supplier can have multiple sites, each with its own contacts and payment details.

The process by which a prospective supplier submits company information to be considered for onboarding. It may be self-service through the portal or entered internally, and it typically leads to a qualification review.

A structured evaluation of a prospective or existing supplier against defined criteria before or during onboarding. It may involve questionnaires, assessments, and approvals that determine whether the supplier is eligible for business.

A self-service web interface where suppliers manage their profile, view purchase orders, submit invoices, and respond to negotiations. Access is controlled by user accounts linked to specific supplier records.

A purchasing model where employees create their own requisitions from catalogs or free-form entries, guided by policy and approvals. It reduces buyer workload while keeping spending controlled and visible.

An external supplier website integrated into the buying application so users can shop there while prices and items are passed back into a requisition. It combines supplier-maintained content with internal approval and purchasing controls.

A configurable internal request form used to capture information that does not fit a standard catalog or requisition flow, such as a service request or an IT access request. It can route for approval and trigger downstream actions.

The process of identifying and evaluating potential suppliers and obtaining competitive bids for goods or services. It produces awards that feed negotiations, agreements, and purchase orders.

A sourcing document that asks suppliers to submit pricing and terms for specified requirements. Responses are compared side by side, and the best response can be awarded to create an agreement or order.

The decision that selects a supplier response and converts it into a purchase order, agreement, or negotiation. It records which lines were awarded and communicates the outcome to participating suppliers.

A structured online exchange with one or more suppliers to refine pricing, terms, or requirements before an award. It can involve multiple rounds, messages, and attached documents, and it is tracked for audit.

The clauses, conditions, and legal language that define obligations in an agreement, such as payment, liability, and termination. Terms can be templated, versioned, and approved before a contract becomes active.

A formal agreement between the organization and a supplier that records negotiated terms, deliverables, and effective dates. It is managed through authoring, approval, and renewal, and it may link to purchasing documents.

A specific output, milestone, or service that a supplier must provide under a contract, often with due dates and acceptance criteria. Deliverables support tracking of contract performance and obligations.