Oracle SCM Fusion Cloud Techno-Functional Consultant

Oracle SCM Fusion Cloud Techno-Functional Consultant
Job Description
Oracle SCM Fusion Cloud Techno-Functional Consultant
Experience
8+ years in Oracle SCM Cloud, including at least one full-lifecycle implementations and hands-on quarterly update regression or UAT cycles
Domain
Oracle Fusion SCM Fusion Cloud (Procurement, Inventory, Order Management, Manufacturing)
Role Overview
Oracle Fusion Cloud on UiPath. This is not an Oracle implementation role. You will be the Oracle SCM Fusion Cloud domain authority embedded in a UiPath automation team. You will shape a reference Oracle Fusion environment into a known, stable and repeatable state; define precisely what to automate and how each supply chain process behaves, step by step and field by field; lay down the foundational master and transactional data that automated scripts consume; and help engineers understand the Oracle behavior behind every test step.
Success is measured by two things: how quickly UiPath engineers can build reliable, reusable supply chain automation scripts without guessing about Oracle behavior, and how easily those accelerators can be adapted to a new customer's Fusion configuration.
Key Responsibilities
Reference Environment Configuration
Own the SCM configuration through Functional Setup Manager: opt into the in-scope offerings (Procurement; Manufacturing and Supply Chain Materials Management; Order Management) and complete setup tasks in dependency order, coordinating shared enterprise structure with the Financials consultant.
Materials foundation: item master organization, inventory organizations and parameters, sub-inventories and locators, units of measure and conversions, inter-organization parameters and shipping networks; Product Hub item classes, templates, item statuses and catalogs; lot and serial control.
Procurement: procurement and requisitioning business units (service provider model), procurement agents and access, document styles, line types, purchasing categories, supplier configuration, receiving parameters and receipt routing (standard, inspection, direct), and matching options feeding Payables.
Order Management: order types, orchestration process definitions and assignment rules, fulfillment line statuses, pricing (price lists, pricing strategies and segments), shipping methods, pick wave release and ship confirm rules, and the Receivables interface for billing.
Costing and Manufacturing (as scoped): cost organizations, cost books and profiles, receipt accounting; plants, work centers, resources, work definitions and work order types.
Build a deliberately realistic but 'vanilla' baseline (one manufacturing and one distribution organization) that mirrors common customer patterns, and record every deviation from Oracle defaults as a documented configuration assumption.
Approvals: configure requisition, purchase order and change order approvals (BPM Worklist / approval rules) with deterministic single- and multi-level routing so automated tests can predict approvers, including auto-approve settings needed for test runs.
RBAC: create role copies for personas (Requester, Buyer, Category Manager, Receiving Agent, Order Manager, Warehouse Manager, Inventory Manager, Production Supervisor, Cost Accountant), configure data access by business unit and inventory organization, and maintain a catalog of named test users per persona.
Replicability: export and import configuration packages and setup data so the baseline can be replicated into other pods or restored after a refresh; maintain a configuration change log.
Process Decomposition and Step by Step Design
Decompose core supply chain processes into L1 to L4 flows and map each L4 step to an automatable scenario with priority and risk rating. In-scope processes include but not limited to:
Procure-to-Pay: requisition (self-service and catalog), approval, PO creation and autocreate, blanket and contract agreements, change orders, receipt, inspection and delivery, returns to supplier, and handoff to Payables matching.
Order-to-Cash: sales order entry, orchestration and fulfillment, reservation, pick wave, pick confirm, ship confirm, billing interface to Receivables, holds, changes and cancellations, and returns (RMA) with receipt.
Inventory: miscellaneous receipts and issues, subinventory and inter-organization transfers (direct and in-transit), cycle counting, physical inventory, lot/serial transactions, min-max planning and consignment.
Manufacturing: work order creation and release, material issue and backflush, operation and product completion, work order close and cost impact.
Supplier and item master: supplier onboarding and item creation as preconditions and as standalone tests.
Author automation-ready steps: preconditions (items, on-hand, suppliers, customers, open periods), persona and role, navigation path (Redwood page, classic ADF page, work area or mobile page), field-level inputs with data references, expected results and the verification method for each checkpoint.
Cross-module flows: specify the end-to-end expected state across modules (on-hand, costing, receipt accounting, AP invoice match, AR invoice) and coordinate the Finance-side steps with the Financials consultant.
Define positive, negative and boundary variants (e.g. over-receipt tolerance, insufficient on-hand, credit check holds, lot expiry, approval rejection, partial shipment and backorder) and the permutations worth parameterizing.
Beyond the UI: define how each outcome is verified: SCM REST API GETs (e.g. purchaseRequisitions, purchaseOrders, receivingReceiptRequests, salesOrdersForOrderHub resources), BI Publisher data models or SQL against core tables (POR_REQUISITION_HEADERS_ALL, PO_HEADERS_ALL, PO_LINES_ALL, RCV_TRANSACTIONS, DOO_HEADERS_ALL, DOO_FULFILL_LINES_ALL, WSH_DELIVERY_DETAILS, INV_ONHAND_QUANTITIES_DETAIL, INV_MATERIAL_TXNS, EGP_SYSTEM_ITEMS_B, CST_TRANSACTIONS), OTBI analyses, fulfillment line status and ESS job status.
Data Foundation
Design the data model the automations consume: items and item structures, suppliers and sites, customers and ship-to sites, price lists, agreements, on-hand quantities by subinventory, lot and serial, work definitions, each seeded in a known, documented state.
Bulk seeding and reset: build and load FBDI templates (item import, supplier import, purchase order and agreement import, inventory transaction import, source sales order import) and use inventory transactions to seed on-hand; diagnose interface and import errors.
Inline preconditions: identify and document REST API calls (payloads and child resources, e.g. itemsV2, inventoryStagedTransactions) that UiPath workflows can call to create preconditions just before a test runs.
Stock consumption: define how tests consume and replenish inventory so runs stay repeatable: dedicated items or subinventories per test group, replenishment jobs, unique order and PO numbers, and recovery steps after a failed run.
Write the reseed and verification runbook for environment refreshes (production-to-test or test-to-test) and keep the data dictionary that engineers use for parameterization.
Use synthetic data only; no customer data in the reference pod.
Automation Enablement (pairing with UiPath engineers)
Walk automation engineers through each process live in Fusion before build starts, and remain their first point of contact for Oracle behavior during build, stabilization and maintenance.
Asynchronous behavior: explain every point where automations must wait or poll rather than proceed, and how to confirm completion: orchestration step progression and fulfillment line statuses, pick wave and ship confirm processes, ESS scheduled processes (e.g. Import Purchase Orders, Load Interface File for Import, Manage Inventory Transaction Interface, Transfer Transactions from Inventory to Costing, Create Cost Accounting Distributions), approval wait states and notification latency.
Recommend the most reliable path per step (UI, REST API, file-based import or scheduled process) and help decide what is validated through the UI versus prepared as a precondition through APIs or loaders.
Configuration-driven UI variability: flag the Oracle elements that change what a automation engineer sees, so engineers design resilient selectors and parameters: descriptive and extensible flexfields (including item EFFs), Order Management extensions and Groovy-based rules, Page Composer and Visual Builder Studio (Redwood) extensions, organization-specific parameters and mobile/RF pages.
Triage execution failures to root cause (application defect, configuration, data state, security/role, environment or script) and resolve the Oracle-side causes; log genuine product issues as Oracle SRs when required.
Key Deliverables
Reference environment: SCM configuration workbook, exported configuration packages and setup data, security/test-user catalog, and configuration change log.
Process and design specs: L1 to L4 process flows with automation-ready step by step specifications with verification methods.
Data kit: FBDI files, REST API collections, stock consumption plan

Work arrangement
Hybrid