ORACLE FUSION CLOUD PROCUREMENT

Comprehensive Practical Implementation & Configuration Study Guide

Core Implementation Prerequisite: To execute any procurement setup tasks, a user must be assigned
a custom job role based on the Application Implementation Consultant
( ORA_ASM_APPLICATION_IMPLEMENTATION_CONSULTANT_JOB ) role, and explicitly opt into the
Procurement Offerings within the Functional Setup Manager (FSM).

1. Getting Started & Rapid Implementation

Navigation: Setup and Maintenance > Tasks > Manage Implementation Projects > Create Project > Add "Define
Procurement Configuration for Rapid Implementation"

Oracle provides two specialized rapid implementation task lists using Excel-based spreadsheet utilities to
accelerate core setup lines:

• With Purchasing Module: Includes legal, financial, and subledger reporting structures. Use spreadsheets
to load Chart of Accounts (COA), Ledgers, Legal Entities, Business Units (BUs), Bank Accounts,
Branches, and Payment Terms.
• Without Purchasing Module: Utilized for standalone deployments of Oracle Sourcing or Oracle Supplier
Qualification. Skips financial/ledger configurations but requires basic legal configurations ( Manage Legal
Addresses , Manage Legal Entities , Manage Legal Entity Registrations ).

The SMB Automated Shortcut

For small and medium-sized setups, running the Enterprise Scheduler Service (ESS) job "Configure Basic
Enterprise Structure for Procurement" auto-builds an entire centralized procurement framework for indirect
expense purchasing using only two parameters: Centralized Procurement Business Unit Name and
Currency . It automatically handles:

• Configuring the new BU with a procurement function acting as a shared service provider for all other BUs.
• Configuring all other BUs with the requisitioning function.
• Creating a master item inventory organization, individual inventory orgs per BU, receiving parameters,
standard workday shifts, a common content zone/catalog, and primary Units of Measure (UOMs).

2. Enterprise Structures & Reference Data Sharing (Set ID)

Navigation: Setup and Maintenance > Functional Area: Financial Reporting Structures > Manage Chart of
Accounts Structure Instances

Oracle Fusion organizes businesses along three axes: Legal (Legal Entities), Managerial (Divisions &
Business Units), and Functional (Departments, Inventory Orgs). Key structural nodes require distinct
components:

Oracle Fusion Cloud Procurement — Quick Implementation Notes 1

Chart of Accounts (COA) Design Checkpoints
• Thick vs. Thin GL: A Thin GL minimizes segments to summary levels (e.g., standard statutory accounts
and broad operational cost centers), shifting granular analysis to subledgers (like Projects or Inventory). A
Thick GL tracks specific lines of business, detailed cost components, or currencies directly via explicit
segments, increasing system resource loads.
• Mandatory Segment Labels: Every COA must feature at least one segment labeled as the Primary
Balancing Segment (maps to a Legal Entity to ensure balanced subledger journals) and one segment
labeled as the Natural Account Segment (defines the account type: Asset, Liability, Owner's Equity,
Revenue, or Expense).
• Optional Labels: Cost Center (required for tracking depreciation in Oracle Assets and approval routing
rules in Procurement) and Intercompany (used for automated balancing between trading legal entities).

Reference Data Sharing Methods (Set ID)

Instead of duplicating standard lists (e.g., Payment Terms, Locations, Grades) across business units, entries
are grouped into Reference Data Sets. BUs subscribe to these sets via three sharing behaviors:

Sharing Method Behavioral Logic Procurement/Common Example

One Set Only, No Data can belong to exactly one partition. Asset Prorate Conventions
Common Values

One Set Only, With A global Common Set is visible to all, Receivables Transaction Types,
Common Values alongside BU-specific entries. Locations, Departments, Jobs

Multiple Sets, No Individual attributes can be assigned to Payables Payment Terms, Tax
Common Values multiple specific sets. Classification Codes

Oracle Fusion Cloud Procurement — Quick Implementation Notes 2

 3. Currencies, Daily Rates & Core Configurations

Navigation: General Accounting > Period Close > Manage Currency Rates > Daily Rates

All transaction flows require synchronized currency definitions and conversion lookups:

• Currency Codes: ISO 4217 standards are natively supported. Predefined to USD by default. Once a
currency code is enabled and saved, it cannot be changed or deleted.
• Predefined Conversion Rate Types:
◦ Spot : For frequently fluctuating currencies where exact day-of-transaction conversion is necessary.
◦ Corporate : An organizational standard rate set across a stable currency for an entire month.
◦ User : Used for one-off, manual conversion entries when a daily lookup rate is absent.
◦ Fixed : Constant conversion rates (e.g., historical Euro/EMU locked rates).

• Practical Execution (Spreadsheet Upload): To load daily rates efficiently, install the Oracle ADF
Desktop Integration client add-in for Excel. Populate columns: From Currency , To Currency ,
Conversion Rate Type , From Date , To Date , and Rate . Enable
Enforce Inverse Relationship to auto-calculate the mirror currency conversion.

4. Approval Management for Procurement (BPM & AMX)

Navigation: Setup and Maintenance > Approval Management > Manage Requisition Approvals / Manage
Purchasing Document Approvals

Oracle Procurement utilizes the Approval Management Extension (AMX) inside the SOA suite to
orchestrate multi-stage approvals. Rules evaluate boolean conditions (IF) and produce routing mechanisms
(THEN).

Seeded Requisition Approval Routing Workflow

1. Header Preapproval Stage: Evaluates upfront constraints. Contains the out-of-the-box Requester FYI
participant which notifies the person an item is requested on behalf of.
2. Header Stage: The primary repository for corporate financial and hierarchy approvals based on document
dollar value.
3. Header Postapproval Stage: Executes final structural verification or special review loops (e.g., project/
funder validations).
4. Postapproval FYI Stage: Auto-sends an end-of-process informational receipt to the original document
preparer.

Key Routing Rule Types (THEN Builders)

• Supervisory Hierarchy: Evaluates standard employee reporting structures tracked in Oracle HCM.
Requires setting the Start With anchor (e.g., Submitter's Manager) and the Number of Approval
Levels .

• Job Level: Evaluates a worker's assigned numeric job ceiling against absolute or relative targets. You can
configure At least or At most values relative to absolute grades or document submitters.

Oracle Fusion Cloud Procurement — Quick Implementation Notes 3

 • Position Hierarchy: Routes approvals across structural corporate blocks (e.g., Buyer I > Senior Buyer >
Procurement Director) independent of the individual worker occupying the post. Direct reports roll up to the
position even if a manager position is temporarily vacant.
• Approval Group: Static or dynamic clusters of designated internal names evaluated sequentially or in
parallel.

Advanced Practical Rule Writing Techniques

The Null Value Check Rule (Strictest Practice): If an attribute evaluated inside an IF condition is
optional on the UI (e.g., a specific Sourcing Smart Form or Project Number), you must insert a prioritized
check verifying the field isn't blank before evaluating it.

Example Structure:
IF Smart Form Is Not Blank AND Smart Form Equals 'Work Visa Request' THEN Route...
IF Smart Form Is Blank OR (Smart Form Is Not Blank AND Smart Form Does Not Equal
'Work Visa Request') THEN Auto-Approve

Mapping Sets & Bounded Routing

To prevent rules inflation (authoring thousands of separate IF/THEN statements), use Mapping Sets
( REQ_APPROVAL_MAPPING_SET_X ). Define a matrix linking dynamic dimensions (e.g., Category, Location,
Department) to an approver name and a priority order number. Write a single master approval rule pointing to
the Mapped Approval Attribute to execute the entire matrix automatically.

Oracle Fusion Cloud Procurement — Quick Implementation Notes 4

 5. Sourcing & Supplier Portal Configuration

Navigation: Setup and Maintenance > Functional Area: Suppliers > Configure Supplier Registration and Profile
Change Request

Supplier Onboarding & Lifecycles

Oracle distinguishes suppliers via their operational business relationship:

• Prospective Suppliers: Enabled primarily for low-exposure engagements (e.g., responding to Sourcing
RFIs/RFQs, Supplier Qualification questionnaires). Requires minimal onboarding data. They cannot be
assigned purchase orders or invoices.
• Spend Authorized Suppliers: Formally vetted for active financial commitments. Onboarding requires
stringent validation controls including bank account entries, tax IDs, and regulatory compliance certificates.
Promotion can occur via manual action, or automatically as a negotiation award outcome.

The Next-Generation Responsive Experience

Leveraging Oracle's Visual Builder Studio (VB Studio) in Express Mode, administrators can implement
conditional business rules across supplier-facing web pages. Properties like Required , Hidden , or Read-
only can react dynamically to choices such as the onboarding country or organization type.

Intelligent Onboarding Example: Configure a business rule where selecting Country = United
States hides the foreign tax field and marks Taxpayer ID (EIN/SSN) as strictly mandatory. For
European onboarding, invoke conditional text instructions specifying the precise VAT formats and
required certificate uploads.

6. Purchasing, Self-Service & SCM Integration Flows

Navigation: Setup and Maintenance > Functional Area: Procurement Foundation > Manage Document Styles

Procurement Document Styles

Document Styles strip UI noise on purchase orders and agreements by disabling features not required for a
specific commodity or flow. For example, a Services Agreement Style can completely hide warehouse
shipping sections and enable complex services parameters (e.g., Progress Payments, Retainage, or Work
Confirmations).

• Outside Processing (OSP): To purchase service components executed on internal assemblies by

external manufacturers, use the delivered Outside Processing Style . Ensure Outside Processing
Enabled = Yes . (Note: OSP, Consignment Terms, and Configured Ordering are mutually exclusive within
a single Document Style).

Oracle Fusion Cloud Procurement — Quick Implementation Notes 5

Supply Chain Integration Mechanics

Integration Flow Procurement Setup & Behavioral Rules

Back-to-Back Enable Customer Sales Order Fulfillment . Set up a Blanket Purchase Agreement
(B2B) Fulfillment (BPA). In the Order Creation Options, select Group Requisitions and Use Customer
Sales Order to consolidate identical sales order requests onto a single PO.

Drop Shipment The material is delivered directly from the supplier to the end customer. Requisitions are
Fulfillment automatically spawned via the Purchase Request Web Service as approved items and must
feature the Negotiated flag to bypass manual buyer steps.

Internal Material Fulfills an inventory or expense requisition from an internal warehouse instead of a commercial
Transfers (IMT) supplier. Local catalogs must be configured with Include all master items = Checked
to surface non-agreement internal stock items during checkout.

7. Troubleshooting & Practical Operational Verification

Resolving Error POR-2010674

Symptom: A user attempts to search or checkout items and gets the error: "You aren't assigned to a business
unit that supports requisitioning."

Verification & Remediation Path:

1. Verify the BU configuration via Manage Business Units . Go to Assign Business Functions and
ensure Requisitioning is checked and marked active.
2. Navigate to Manage Business Unit Data Access for Users .
3. Create a row for the target user, select their role (e.g., Procurement Requester ), set the Security
Context to Business unit , and choose the active Requisitioning BU name in the Security Context Value
field. Save and let the security table synchronize.

Oracle Fusion Cloud Procurement — Quick Implementation Notes 6