Oracle CX Sales 2026 Implementation Professional study plan

Map the procurement application's end-to-end flow (requisition to receipt to invoice match) and label where each of Purchasing and Common Procurement Functions setup tasks sits in that flow

Walk through the Purchasing functional setup task list and write a one-line purpose statement for every task, flagging the ones that are mandatory before a PO can be created

Configure document types, line types, and purchase order styles in a test instance and predict which combinations are valid before saving

Describe how common procurement functions (approval management, document sequencing, reference data sharing) are shared across Purchasing, Self Service Procurement, and Supplier Portal

Build a personal glossary of 25 procurement terms you must recognize instantly on exam day

Trace how approval management rules, hierarchies, and document sequencing interact when a purchase order is submitted for approval

Configure a reference data set and assign it to a business unit, then verify which procurement documents inherit it

Enable common application functions such as attachments, notes, and lookups, and identify which are prerequisites for later procurement setup

Explain how business units, legal entities, and inventory organizations relate to procurement transaction defaults

Draft five likely exam scenarios where a misconfigured common function breaks a downstream procurement process

Configure Self Service Procurement requisitioning behavior including catalog content, smart forms, and shopper defaults, then submit a test requisition end to end

Set up the Supplier Portal registration flow and identify which supplier profile sections are visible versus hidden to suppliers

Compare how requisition approvals and supplier registration approvals reuse the common approval framework

Configure punchout or content zone behavior conceptually and state which setup tasks must precede it

List the top five configuration errors that cause shoppers or suppliers to see empty or blocked screens

Create an implementation project in Functional Setup Manager, assign the procurement offerings, and export the task list to confirm scope

Explain the difference between an offering, a functional area, and a task, and predict which tasks appear for a given offering combination

Describe the provisioned procurement application's key components and how they map to the offerings you selected

Use the setup and maintenance export/import approach to move a configuration change between environments and note the limits

Self-test on FSM and application-understanding questions under timed conditions

Configure sourcing document types, negotiation styles, and award rules, then run a simulated negotiation from draft through award

Set up Supplier Qualification Management models, questionnaires, and scoring so a qualification outcome can be produced

Explain how negotiation outcomes feed supplier qualification and how qualification results influence sourcing eligibility

Configure two-stage sourcing or a comparable advanced negotiation pattern and describe when it is required

Identify which sourcing and SQM settings are seeded versus must be created

Configure contract types, contract templates, and clause libraries, then author a contract with clauses pulled from the library

Describe contract approval, amendment, and versioning behavior and predict what happens when an approved contract is amended

Set up Project-Driven Supply Chain foundations including project and task references on procurement documents

Explain how PDSC ties requisitions, purchase orders, and receipts to project expenditures and identify the required setup sequence

Compare contract and PDSC configuration touchpoints that overlap with Purchasing setup from week one

Identify the AI, machine learning, and automation features relevant to procurement and state the setup or enablement each requires

Describe how Redwood capabilities are enabled and which procurement pages or experiences they affect

Explain mobile procurement capabilities and the configuration that controls what a mobile user can do

Distinguish features that are on by default from those requiring opt-in or profile option changes

Write ten exam-style questions on automation and Redwood, then answer them without notes

Review every domain's weakest two topics identified from earlier weeks and re-explain each aloud without notes

Take two full-length timed practice passes and log every missed question by domain

Re-derive the setup sequence for the three heaviest domains from memory and check against your notes

Consolidate all deliverables into a single index you can scan in the final 48 hours

Confirm exam logistics and reserve a quiet test window