Oracle EBS Procurement Suite - Functional Architect

Role Overview

This is a critical client-facing role on an active Oracle EBS R12.2.15 upgrade program. The incoming SME steps directly into a live CRP 1 delivery track covering Implementation of Procurement Contracts, Sourcing/Solicitation, iSupplier Portal, and Supplier Qualification Management modules. The role demands dual depth: strong functional delivery at CRP/UAT quality across all five Procurement Suite modules, combined with the ability to serve as a Functional-to-Technical Bridge, translating business requirements into precise technical specifications consumable by the EBS development team. The business team is deeply engaged, technically literate, and asks precise system-behavior questions in real time. The SME must earn business trust from Day 1, lead sessions independently, configure the system under business scrutiny, respond authoritatively to gap questions, and drive module closure without escalation dependency.

Module Scope

• Oracle Sourcing / Solicitation
• Full Sourcing lifecycle: RFQ, sealed bids (IFB), open solicitations, and AutoGen-driven BPA replenishment within the same Sourcing engine
• Negotiation document types: RFQ, IFB, RFI configuration and differentiation
• Sourcing homepage layout and sealed bid controls in R12.2.15
• RFQ/custom template management, analysis methods, collaboration team configuration
• Supplier response submission workflow: Quote creation, attachment, quantity, promised delivery date, validate and submit
• AutoGen BPA configuration and management
• Supplier non-response handling: Intend to Participate (ITP) options, online discussion, email buyer workflow
• Supplier Qualification Management (SQM)
• Full SQM lifecycle: qualification initiative creation, supplier invitation, questionnaire design, scoring, outcome management
• Assessment tab configuration within the SQM module
• Qualification initiative types supported in R12.2.15 including version-specific limitations vs prior releases
• Scoring and evaluation: qualification scoring setup, evaluation workflow, outcome routing
• Integration with iSupplier Portal: how qualification status surfaces in the supplier portal and access control behavior
• Potential supplier public self-registration: awareness of R12.2.15 native availability and alternative approaches
• Guided learning / training material for suppliers: delivery approach and coordination with PMO
• Access control configuration: supplier user management, role assignment, portal security
• Oracle Procurement Contracts
• Contract types: CPA (Contract Purchase Agreement), BPA (Blanket Purchase Agreement), standard T&C application
• Capital procurement contract tracking and co-op / GSA contract management
• T&C template configuration: creation, versioning, application across procurement scenario types
• Preview Contract Terms PDF behavior in R12.2.15
• Deliverables tracking within Procurement Contracts
• Product limitation awareness: ability to distinguish native fitment from configurable gaps from genuine product limitations
• Contract data conversion: R12.1.3 Procurement Contracts entity structures and mapping to R12.2.15 target
• Oracle Purchasing
• Full Req-to-PO lifecycle across all scenario types: inventory requisitions, expense requisitions, auto-create POPurchasing document types: Standard PO, Blanket Release, Planned PO, Contract PO
• AME (Approvals Management Engine): approval hierarchy setup, rules, conditions
• Buyer Work Center: configuration and operational usage
• PO acknowledgement from supplier side via iSupplier Portal confirms receipt of PO document
• High-volume requisition processing: multiple pathways and performance considerations
• Oracle iSupplier Portal
• Supplier architecture: DMZ-hosted, separate from main EBS application tier; supplier access model
• Supplier notification channels: worklist, Oracle notification bell, email (test vs production configuration)
• Intend to Participate (ITP): homepage notification path configuration; direct negotiation link behavior
• Supplier PDF printable view: configuration, element management, environment migration (Dev $B"*(B Test $B"*(B UAT $B"*(B Prod)
• Supplier self-registration: R12.2.15 native capability assessment and alternative approaches
• Guided learning / training material for suppliers: delivery approach and coordination with PMO
• Access control configuration: supplier user management, role assignment, portal security

Responsibilities

This role requires active technical bridge accountability not just functional delivery. The SME must:

• Translate confirmed CRP business requirements into precise technical specifications consumable by the EBS technical team without further translation
• Produce Functional Design Documents (FDDs) for all customization, report, and integration items within Procurement Suite scope
• Classify each open item: (A) EBS R12.2.15 native fitment close; (B) Product limitation document and confirm with business; (C) Customization candidate size effort (minimum / medium / high)
• Ensure no open configuration item blocks CRP session progress all items tracked in project governance tool as Action/Decision items
• Work with IT, Technical Lead, and Technical Advisor to align on technical approach before committing to business
• Coordinate with Wave 1 functional team on cross-wave dependency items (solicitation number on PO, T&C template naming conventions)
• Drive resolution within nightly and weekly technical team sync cadence R12.1.3 And R12.2.15 Dual-Version Depth Required R12.1.3 Current State Knowledge Hands-on experience with R12.1.3 Sourcing, Purchasing, Contracts, iSupplier, and SQM in at least one prior engagement
• Version-specific limitations vs R12.2.15: inline T&C view behavior, sealed bid UI differences, notification framework
• R12.1.3 Procurement Contracts data structures: required for conversion mapping to R12.2.15 target
• R12.2.15 Target State Exchange Current working knowledge of R12.2.15 Sourcing, Purchasing, Contracts, iSupplier, and SQM including version-specific UI changes
• Online patching framework: ADOP awareness relevant to Procurement Suite module updates
• OCI deployment: environment chain familiarity (GOLD $B"*(B DEV $B"*(B SIT $B"*(B TEST $B"*(B UAT $B"*(B PRD)
• EBS EXACC connectivity: nuances relevant to Procurement module configuration and environment migration
• BI Publisher: data model, RTF/XSL template, concurrent program linkage, environment migration
• Data Conversion: Oracle EBS Procurement Contracts entity; mapping, conversion program coordination, validation
• FDD Production: Functional Design Documents consumable by Oracle EBS technical developer without further translation
• SQL/PL/SQL: working knowledge for issue investigation, data validation, and report data model support
• Project governance tool (JIRA or equivalent): ticket management; Action/Decision governance for gap items

Mandatory Requirements

• Hands-on experience in ALL of the following areas: Oracle EBS R12.1.3 AND R12.2.15: both versions, hands-on configuration, and delivery
• Oracle Sourcing: sealed bid (IFB), RFQ template management, analysis methods, AutoGen BPA, collaboration team
• Oracle Supplier Qualification Management: full lifecycle, scoring, evaluation workflow, R12.2.15 behavior
• Oracle Procurement Contracts: CPA/BPA, T&C templates, deliverables, co-op process, product limitation awareness
• Oracle Purchasing: full Req-to-PO lifecycle across all scenario types; AME; Buyer Work Center
• Oracle iSupplier Portal: DMZ architecture, notification configuration, supplier experience delivery
• BI Publisher: data model, RTF/XSL template, concurrent program linkage, environment migration
• Data Conversion: Oracle EBS Procurement Contracts entity; mapping, conversion program coordination, validation
• Integration: functional specification for EBS inbound/outbound interfaces; integration test scenario definition
• FDD Production: Functional Design Documents consumable by Oracle EBS technical developer without further translation
• SQL/PL/SQL: working knowledge for issue investigation, data validation, and report data model support
• Project governance tool (JIRA or equivalent): ticket management; Action/Decision governance for gap items