Oracle CX Sales 2026 Implementation Professional key terms

The centralized Oracle Cloud tool used to configure and deploy enterprise applications. Implementers use guided task lists, offering registration, and implementation projects to move setup data from a staging environment to production.

The hierarchical opt-in structure that determines which application modules a customer enables. An offering such as Procurement groups functional areas like Purchasing and Self Service Procurement, and each area exposes its own setup task lists.

A container in Functional Setup Manager that assembles the setup tasks for one or more offerings and functional areas. Tasks are assigned to implementers, tracked to completion, and exported or imported as a configuration package.

A portable export of setup data from an implementation project, used to migrate configuration between environments. Packages are exported from source pods, then imported and verified in the target pod before go-live.

A refreshable copy of a pod used for testing configuration changes before promoting them. Sandboxes isolate setup work, allow patching preview, and can be published or abandoned without affecting the production environment.

The organizational unit that owns procurement transactions and policies. It defines defaulting rules, approval hierarchies, document numbering, and the suppliers and catalogs available to requisitioning organizations assigned to it.

The business unit that owns requisitions created by requesters. It is associated with a procurement business unit, which supplies purchasing controls, default accounts, and supplier data for the resulting purchase orders.

A named user with purchasing responsibility who manages purchase orders, negotiations, and supplier relationships. Agent profiles control document styles, approval limits, and which business units the agent can transact in.

The rule structure that routes requisitions, purchase orders, and agreements to approvers. It combines supervisory hierarchy, job-level, and position-based rules, with amount-based thresholds and parallel or serial routing options.

Configuration that controls numbering, approval routing, and defaulting behavior for a purchasing document type. A style is assigned to a procurement business unit and referenced when transactions are created.

A formal commitment document sent to a supplier authorizing delivery of goods or services at agreed prices and terms. It can be standard, blanket, or contract-based, and drives receipt, invoicing, and matching processes.

A long-term agreement committing to buy goods or services from a supplier over a defined period, typically with negotiated prices and quantities. Releases or orders are drawn against it as demand arises.

A purchasing document that establishes terms and conditions with a supplier without committing to specific quantities or amounts. Purchase orders reference it to inherit negotiated pricing and legal terms.

The control that compares a supplier invoice against the purchase order and the receipt before payment. Tolerances for quantity, price, and amount determine whether an invoice is automatically approved or placed on hold.

The record confirming that goods or services ordered on a purchase order were delivered. Receipts update on-hand inventory, enable three-way matching, and can be performed by requesters, receiving clerks, or via integration.

An internal request to procure goods or services, created by a requester and routed through approval before becoming a purchase order. Requisitions can be catalog-based, free-form, or generated from a shopping list.

A configurable requisition template that presents requesters with only relevant fields for a category of purchase, such as services or IT hardware. It simplifies entry and enforces required information.

A supplier-hosted catalog accessed through a round-trip integration from Self Service Procurement. Requesters shop on the supplier site, and selected items return as requisition lines with validated pricing and attributes.

A logical grouping of catalog content, such as a commodity or supplier set, that is exposed to specific requisitioning business units. Zones control which requesters see which catalogs and smart forms.

A self-service web channel where suppliers register, maintain profile and banking data, view purchase orders, submit invoices, and respond to negotiations. Access is controlled by supplier user accounts and roles.

The process by which a prospective supplier submits company information for review. Registrations can be internal or self-service, and approved registrations create or update supplier records in the supplier master.

The creation and management of supplier contact accounts that can access the Supplier Portal. Provisioning links a user to a supplier and contact, and assigns roles that determine visible transactions and actions.

A structured event for soliciting supplier bids, such as an RFQ or auction. It defines lines, requirements, response controls, and award rules, and can be two-stage or multi-round.

A sourcing event split into a technical and a commercial stage. Technical responses are evaluated and shortlisted first, and only qualified suppliers proceed to submit pricing in the commercial stage.

The decision that selects winning supplier responses in a sourcing event and converts them into a purchase order, agreement, or contract. Award rules can be automatic based on score or manual with justification.

A sourcing control that hides competitor pricing and responses until the event closes. It prevents suppliers from seeing each other's bids and preserves fairness in competitive negotiations.

The module for assessing suppliers against initiatives, questionnaires, and scoring models. It supports qualification areas, models, and responses that produce scores used in registration and sourcing decisions.

A category of assessment within SQM, such as financial stability or quality capability. Areas group questions and determine how responses are weighted and scored in a qualification model.

The calculation that converts questionnaire responses and sourcing criteria into comparable numeric values. Weights, rating scales, and score ranges determine how responses rank and feed award decisions.

A legally binding agreement with a supplier that defines terms, pricing, and deliverables. Contracts support clauses, templates, approvals, and deviations, and can be linked to purchase orders and sourcing awards.

A repository of reusable legal and commercial clauses that can be inserted into contract documents. Clauses carry version control, approval requirements, and rules for when they must appear.

A predefined structure for creating contracts, including sections, standard clauses, variables, and approval rules. Templates standardize authoring and reduce legal review effort for common agreement types.

The integration that links project and task information to procurement transactions. Requisitions and purchase orders carry project and task references so costs are charged directly to the correct project budget.

The accounting entry that records project cost from a procurement transaction. It captures the project, task, expenditure type, and amount, and flows to project cost collection for capitalization or billing.

The modern Oracle user interface design system applied to procurement pages. It delivers responsive layouts, simplified navigation, and consistent patterns across requisitions, purchase orders, and supplier pages.

An automated assistant embedded in procurement workflows that can draft documents, summarize supplier information, or recommend actions. Agents use configured data and permissions and require human review before committing transactions.

A conversational interface that lets users query procurement data and perform tasks using natural language. It routes requests to skills backed by application APIs and returns answers or guided actions.

A restriction that prevents an invoice from being paid until resolved. Holds arise from matching variances, missing receipts, or approval issues, and release requires correction or authorized override.