Scribd
Upload
124 views13 pages

OIC Integration Roles for Oracle ERP

Roles required to access modules in Oracle ERP

Uploaded by

Jei Raghav
Copyright
© All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
124 views13 pages

OIC Integration Roles for Oracle ERP

Roles required to access modules in Oracle ERP

Uploaded by

Jei Raghav
Copyright
© All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd

🔐 Essential Roles for OIC Integration with Oracle ERP Cloud

Role Name Purpose

Integration Specialist Core role to access ERP Cloud SOAP and


(ORA_ASM_INTEGRATION_SPECIALIST_J REST services, run integrations, and use
OB) FSM tasks.

Grants access to invoke ERP public web


ERP Integration User
services and REST APIs (commonly
(ORA_FND_INTEGRATION_USER_ABSTR
assigned to the integration user account
ACT)
used in OIC).

AttachmentsUser
Needed when uploading or downloading
(ORA_EGP_ATTACHMENTS_USER_ABSTR
attachments as part of integration.
ACT)

Required to schedule and monitor ESS


ESS Administrator
jobs (e.g., Submit ESS job for FBDI
(ORA_ESS_ADMINISTRATOR_JOB)
upload).

Grants access to run OTBI and BI


BI Consumer Role
Publisher reports. Needed when calling BI
(BIConsumer)
reports from OIC.

Allows access to setup and configuration


FSM Superuser
metadata (useful in deployments and
(ORA_FND_FSM_SUPERUSER_DUTY)
FSM interactions).

🧑‍💻 Optional but Useful Roles (depending on the module)

Role Name Purpose

Gives full access to functional setup manager


Application Implementation
(FSM) to configure services and perform
Consultant
functional configurations.

Sometimes necessary if the integration


General Accountant, Accounts
touches module-specific data or requires
Payable Manager, etc.
module-level privileges.

Needed when managing user roles or


IT Security Manager
checking SOAP/REST security access during
(IT_SECURITY_MANAGER_JOB)
troubleshooting.

Technical Notes
 OIC integrations typically use a dedicated integration user in Fusion
ERP Cloud. This user should be created specifically for API integrations and
assigned the roles listed above.
 The user credentials for this integration user are securely stored in the OIC
connection properties.
 Security policies on REST/SOAP services are enforced; if roles are
missing, you will see errors like “401 Unauthorized” or “You are not
authorized to access this service”.

🔷 1. Identify Need & Create Requisition


✅ Required Roles:
 Employee (ORA_PER_EMPLOYEE_ABSTRACT)
Enables users to create requisitions via Self Service Procurement.
 Requisition Preparer (ORA_PRC_REQUISITION_PREPARER_JOB)
Allows users to prepare requisitions in the Procurement module.
 Requisition Viewer (ORA_PRC_REQUISITION_VIEWER_JOB) (optional)
Allows viewing all requisitions.

🔷 2. Approval Workflow
✅ Required Roles:
 Requisition Approver (ORA_PRC_REQUISITION_APPROVER_JOB)
Enables designated users to approve requisitions based on approval rules.
 Application Implementation Consultant
(For configuring BPM workflows, rules, and escalation paths.)

🔷 3. Purchase Order (PO) Creation


✅ Required Roles:
 Buyer (ORA_PRC_BUYER_JOB)
Core role to create and manage Purchase Orders.
 Procurement Manager (ORA_PRC_PROCUREMENT_MANAGER_JOB)
(optional)
Higher access for managing procurement policies and documents.

🔷 4. Supplier Selection and Negotiation


✅ Required Roles:
 Supplier Qualification Manager
(ORA_PRC_SUPPLIER_QUALIFICATION_MANAGER_JOB)
To evaluate and manage supplier qualifications.
 Negotiation Creator (ORA_PRC_NEGOTIATION_CREATOR_JOB)
Allows creation and management of negotiations (RFQs, auctions).
 Supplier Manager (ORA_PRC_SUPPLIER_MANAGER_JOB)
For onboarding, updating, or approving suppliers.

🔷 5. Purchase Order Transmission


✅ Required Roles:
 Buyer (same as above)
Can transmit PO to suppliers using email, portal, or XML/EDI.

🔷 6. Goods/Services Receipt
✅ Required Roles:
 Receiving Agent (ORA_RCV_RECEIVING_AGENT_JOB)
Can perform receiving transactions.
 Warehouse Operator (ORA_INV_WAREHOUSE_OPERATOR_JOB)
Performs inventory transactions and receipts.
 Inventory Manager (ORA_INV_INVENTORY_MANAGER_JOB) (optional)
Manages inventory organizations and material flows.

🔷 7. Invoice Processing
✅ Required Roles:
 Accounts Payable Specialist
(ORA_AP_ACCOUNTS_PAYABLE_SPECIALIST_JOB)
To enter, validate, and manage supplier invoices.
 Payables Manager (ORA_AP_PAYABLES_MANAGER_JOB) (optional)
Approves payments and oversees AP activities.

🔷 8. Invoice Matching
✅ Required Roles:
 Accounts Payable Specialist
Can perform 2-way or 3-way match activities between PO, receipt, and invoice.

🔷 9. Payment Approval & Processing


✅ Required Roles:
 Payment Administrator (ORA_CE_PAYMENT_ADMINISTRATOR_JOB)
Manages payments, disbursement, and processing.
 Cash Manager (ORA_CE_CASH_MANAGER_JOB) (optional)
Manages bank accounts and cash positioning.

🔷 10. Payment Reconciliation


✅ Required Roles:
 Cash Manager
To reconcile bank statements and ensure payment status updates.

🔷 11. Reporting and Analytics


✅ Required Roles:
 BI Consumer (BIConsumer)
Access to OTBI, dashboards, and prebuilt reports.
 Financial Analyst (ORA_GL_FINANCIAL_ANALYST_JOB) (optional)
For generating and analyzing financial reports.

🔐 Suggested Integration Role for Automation (OIC)


If you're using Oracle Integration Cloud (OIC) to automate the P2P flow:
 ERP Integration User (ORA_FND_INTEGRATION_USER_ABSTRACT)
 Integration Specialist (ORA_ASM_INTEGRATION_SPECIALIST_JOB)
 Assign to the dedicated integration user used in OIC.

📋 Oracle Fusion P2P Cycle – Roles by Process Step


P2P Step Required Roles

- ORA_PER_EMPLOYEE_ABSTRACT (Employee)
🔹 1. Identify Need - ORA_PRC_REQUISITION_PREPARER_JOB (Requisition
Preparer)

- ORA_PRC_REQUISITION_PREPARER_JOB (Requisition
🔹 2. Create Requisition
Preparer)

- ORA_PRC_REQUISITION_APPROVER_JOB (Requisition
🔹 3. Approval Workflow Approver)
- Application Implementation Consultant

- ORA_PRC_BUYER_JOB (Buyer)
🔹 4. PO Creation
- ORA_PRC_PROCUREMENT_MANAGER_JOB (optional)

- ORA_PRC_SUPPLIER_MANAGER_JOB (Supplier
Manager)
🔹 5. Supplier Selection - ORA_PRC_NEGOTIATION_CREATOR_JOB (Negotiation
Creator)
- ORA_PRC_SUPPLIER_QUALIFICATION_MANAGER_JOB

🔹 6. PO Transmission - ORA_PRC_BUYER_JOB (Buyer)

- ORA_RCV_RECEIVING_AGENT_JOB (Receiving Agent)


🔹 7. Goods/Services
- ORA_INV_WAREHOUSE_OPERATOR_JOB (Warehouse
Receipt
Operator)

- ORA_AP_ACCOUNTS_PAYABLE_SPECIALIST_JOB (AP
🔹 8. Invoice Processing Specialist)
- ORA_AP_PAYABLES_MANAGER_JOB (optional)

🔹 9. Invoice Matching - ORA_AP_ACCOUNTS_PAYABLE_SPECIALIST_JOB

- ORA_CE_PAYMENT_ADMINISTRATOR_JOB (Payment
🔹 10. Payment
Admin)
Approval
- ORA_AP_PAYABLES_MANAGER_JOB (optional)

🔹 11. Payment - ORA_CE_PAYMENT_ADMINISTRATOR_JOB


Processing - ORA_CE_CASH_MANAGER_JOB (Cash Manager)

🔹 12. Payment
- ORA_CE_CASH_MANAGER_JOB
Reconciliation

🔹 13. Reporting & - BIConsumer


Analytics - ORA_GL_FINANCIAL_ANALYST_JOB (optional)

🔹 14. Integration User - ORA_FND_INTEGRATION_USER_ABSTRACT


(OIC) - ORA_ASM_INTEGRATION_SPECIALIST_JOB

📦 Roles to Create and Manage Suppliers and Supplier Sites in Oracle


Fusion
Functionality Required Roles

🔹 Create Suppliers
- Supplier Manager (ORA_PRC_SUPPLIER_MANAGER_JOB)
(Manually)

🔹 Manage Supplier
- Supplier Manager (ORA_PRC_SUPPLIER_MANAGER_JOB)
Sites

- Supplier Administrator
🔹 Approve Supplier
(ORA_PRC_SUPPLIER_ADMINISTRATOR_JOB) (for
Registration
registration approvals)

- Supplier Manager
🔹 View/Edit Supplier
- Supplier Profile Change Approver
Profile
(ORA_PRC_SUPPLIER_PROFILE_CHANGE_APPROVER_JOB)

🔹 Create/Manage
- Supplier Qualification Manager
Business
(ORA_PRC_SUPPLIER_QUALIFICATION_MANAGER_JOB)
Classifications

- Payables Manager (ORA_AP_PAYABLES_MANAGER_JOB)


🔹 Manage Supplier
- Accounts Payable Specialist
Bank Accounts
(ORA_AP_ACCOUNTS_PAYABLE_SPECIALIST_JOB)

🔹 Create Supplier via


Registration - Supplier Registration Requester
Requests (ORA_PRC_SUPPLIER_REG_REQUESTER_JOB)
(External/Internal)

🔹 Maintain Supplier
- Supplier Manager
Contacts

🔹 Manage Tax Details - Tax Manager (ORA_ZX_TAX_MANAGER_JOB) (if adding


(if applicable) tax info like TIN, PAN, GST, etc.)

✅ Essential Role for Full Access


 🔑 Application Implementation Consultant
(ORA_ASM_APPLICATION_IMPLEMENTATION_CONSULTANT_JOB)
This role provides superuser access to all setup and configuration tasks,
including Supplier creation, profile options, and approval flows.
✅ Useful during implementation or testing, but not recommended for regular
users.

🧠 Notes:
 Most supplier-related tasks are done via Procurement > Suppliers in
Oracle Fusion.
 For external supplier self-registration, workflow-based approval is
configured via BPM Worklist.
 Users may also need Data Access (Business Unit, Procurement BU, etc.)
to create suppliers tied to those orgs.

📘 P2P Process-Wise Data Access Requirements

P2P Step Data Access Required

- Business Unit (BU) for Procurement


🔹 Create
- Requisitioning BU access to create and submit
Requisition
requisitions

🔹 Approval - No specific DAS required, but approver must have


Workflow access to same BU as the requestor

🔹 Create Purchase - Procurement BU (to create/manage POs)


Order - Supplier site access tied to that BU

- Procurement BU (to assign suppliers and sites)


🔹 Supplier Creation
- Access to SetID or Reference Data Set (for lookups)

- Inventory Organization (required for receiving)


🔹 Goods Receipt
- Access to associated Business Unit

- Business Unit (Payables BU)


🔹 Invoice
- Ledger (for accounting entries)
Entry/Matching
- Legal Entity (for taxes)

- Business Unit for Payables


🔹 Payment
- Bank Account Access (Cash Management)
Processing
- Ledger access

- Bank Account Access (CE)


🔹 Reconciliation
- Business Unit & Ledger for reconciliation reports

- Ledger and BU access to fetch data from OTBI or BI


🔹 Reporting
Publisher reports

🔹 OIC Integration - All above BUs/Orgs/LEs that are involved in APIs


Access (based on REST/SOAP API scope and endpoint access)

🔑 Key Security Contexts for Data Access in P2P

Security Context What It Controls

Procurement, Payables, Receiving, Supplier


Business Unit (BU)
Master
Security Context What It Controls

Inventory
Receiving transactions, Inventory visibility
Organization

Legal Entity (LE) Tax setups, Payables liability accounting

Ledger Journal entries, Accounting validation

Reference Data Set Lookup values for Procurement, Financials,


(SetID) Suppliers

Payments, Reconciliation (in Cash


Bank Account Access
Management)

🎯 Example: For a Buyer


If a Buyer needs to create a PO for a requisition created in BU:
IN_Purchase_BU, the Buyer must be granted:
 Role: ORA_PRC_BUYER_JOB
 Data Access:
o Business Unit: IN_Purchase_BU

o Legal Entity: IN_Legal_Entity (if tax applicable)

o Inventory Org: IN_Inventory1 (if PO is inventory-based)

✅ How to Assign Data Access


1. Navigate: Security Console > Users > Select User > Roles
2. Under each assigned job role (e.g., Buyer), click "Add Data Access"
3. Select the Data Access Set (BU, Inv Org, etc.) and add
Oracle Fusion O2C Cycle – Required Roles by
Process Step
O2C Step Required Roles

- Order Entry Specialist


🔹 Order Entry (ORA_DOO_ORDER_ENTRY_SPECIALIST_JOB)
- Customer Service Representative (optional)

- Order Entry Specialist (same as above)


🔹 Order Validation - Order Manager (ORA_DOO_ORDER_MANAGER_JOB)
(optional)

- Global Order Promising User


(ORA_GOP_GLOBAL_ORDER_PROMISING_JOB)
🔹 Order Promising
- Order Promising Planner
(ORA_GOP_ORDER_PROMISING_PLANNER_JOB)

- Warehouse Operator
🔹 Order
(ORA_INV_WAREHOUSE_OPERATOR_JOB)
Fulfillment
- Shipping Agent (ORA_WSH_SHIPPING_AGENT_JOB)

- Billing Specialist (ORA_AR_BILLING_SPECIALIST_JOB)


🔹 Invoice
- Receivables Manager
Generation
(ORA_AR_RECEIVABLES_MANAGER_JOB)

- Billing Specialist
🔹 Invoice Delivery - Receivables Specialist
(ORA_AR_RECEIVABLES_SPECIALIST_JOB)

🔹 Accounts - Receivables Specialist


Receivable - Receivables Manager

🔹 Payment - Cash Manager (ORA_CE_CASH_MANAGER_JOB)


Processing - Accounts Receivable Specialist

- Cash Manager
🔹 Payment - General Accountant
Reconciliation (ORA_GL_GENERAL_ACCOUNTANT_JOB) (for GL
reconciliation)

🔹 Credit - Credit Analyst (ORA_AR_CREDIT_ANALYST_JOB)


Management - Collections Agent (for credit control monitoring)

- Collections Agent (ORA_IEX_COLLECTIONS_AGENT_JOB)


🔹 Collections
- Collections Manager
Management
(ORA_IEX_COLLECTIONS_MANAGER_JOB)

🔹 Reporting & - BI Consumer (BIConsumer)


Analytics - Financial Analyst (ORA_GL_FINANCIAL_ANALYST_JOB)

🔐 Key Technical Roles (for Integration or Setup)


Purpose Role

Integration via
- ORA_FND_INTEGRATION_USER_ABSTRACT
OIC (Order,
- ORA_ASM_INTEGRATION_SPECIALIST_JOB
Invoice)

Setup tasks and


- Application Implementation Consultant
functional
(ORA_ASM_APPLICATION_IMPLEMENTATION_CONSULTANT_JOB)
configs

Approval
- BPM Workflow Admin (often part of the Implementation
Workflow
Consultant role)
Configuration

🧠 Additional Notes:
 Most roles must be provisioned with appropriate Business Unit (BU)
and Ledger data access.
 Credit and Collection functions require Receivables setups like customer
profiles, credit limits, dunning policies.
 For services, fulfillment might involve Project Billing or Service
Logistics, which adds additional roles.

📘 O2C Process-Wise Data Access Requirements

O2C Process Step Data Access Required

- Business Unit (Order Management BU)


🔹 Order Entry - Legal Entity (optional)
- Customer Accounts (via Customer BU)

- Order Management BU
- Item/Inventory Org (for availability
🔹 Order Validation
checks)
- Shipping Org (if applicable)

- Global Order Promising (GOP) Org


🔹 Order Promising
- ATP Rule Set Access

- Inventory Organization (Shipping


Subinventory)
🔹 Order Fulfillment
- Warehouse Location
- Shipping BU

- Business Unit (Receivables BU)


🔹 Invoice Generation - Ledger (to generate accounting for AR)
- Legal Entity

🔹 Invoice Delivery - Customer BU and access to Customer


O2C Process Step Data Access Required

Account Set

- Receivables BU
🔹 Accounts Receivable - Ledger
- Legal Entity

- Bank Account Access (Cash Management)


🔹 Payment Processing - Receivables BU
- Ledger

- Bank Account
🔹 Payment
- Legal Entity
Reconciliation
- Ledger

- Credit Usage Rulesets / Credit Profiles


🔹 Credit Management
- Customer Account Set

- Customer Account Access


🔹 Collections
- Receivables BU
Management
- Dunning Configuration BU

- Ledger
🔹 Reporting & - Business Unit
Analytics - Inventory Org (for fulfillment reporting)
- Legal Entity

🔑 Core Security Contexts in O2C

Security Context Purpose

Business Unit
Used for Order Mgmt, AR, Collections, Fulfillment
(BU)

Inventory
Required for fulfillment, shipping, and ATP
Organization

Needed for invoice generation, accounting, and tax


Legal Entity (LE)
configurations

Ledger Needed for journal posting and accounting validation

Bank Account
Required for applying receipts, refunds, and reconciliations
Access

Customer Account Determines visibility into customer master, AR aging,


Set collections, etc.

🧾 Example: Data Access for a Receivables Specialist


Access
Example
Type

Business
US_Receivables_BU
Unit

Ledger US Primary Ledger

Legal Entity US_Legal_Entity

Bank
Wells Fargo USD
Account

Customer Vision Operations


Set Customers

✅ How to Assign Data Access in Oracle Fusion


1. Go to: Tools > Security Console > Users
2. Find the user, then click on their assigned role
3. Use “Add Data Access” to assign BU, Ledger, etc. to that specific role
instance
4. Save and test user access in respective functional flows

📋 Roles Required to Create and Manage Customers in Oracle Fusion O2C

Functionality Required Role

🔹 Create
Customer Account Manager
Customer
(ORA_CRM_CUSTOMER_ACCOUNT_MANAGER_JOB)
Account

🔹 Maintain
Customer Account Manager
Customer Sites

🔹 Manage
Customer Customer Account Manager
Contact Info

🔹 Manage
Receivables Specialist
Customer Profile
(ORA_AR_RECEIVABLES_SPECIALIST_JOB)
(Receivables)

🔹 Assign Bill-to /
Customer Account Manager
Ship-to Sites
Functionality Required Role

🔹 Manage
Receivables Manager (ORA_AR_RECEIVABLES_MANAGER_JOB)
Customer Bank
(optional for payment methods)
Accounts

🔹 View/Edit
Customer Receivables Specialist
Transactions

🔹 Credit Checks
Credit Analyst (ORA_AR_CREDIT_ANALYST_JOB)
& Limits

🔹 Approve Customer Data Steward Manager


Customer Data (ORA_ZMM_CUSTOMER_DATA_STEWARD_MANAGER_JOB)
Changes (optional, CDM-specific)

🔐 Optional Roles (depending on implementation scope):

Use Case Optional Role

Centralized
Customer Data Steward
Customer
(ORA_CDM_CUSTOMER_DATA_STEWARD_JOB)
Management

Implementation Application Implementation Consultant


& Setup (ORA_ASM_APPLICATION_IMPLEMENTATION_CONSULTANT_JOB)

Data Import / File Import and Export Administrator


Mass Upload (ORA_FND_FILE_IMPORT_EXPORT_ADMIN_ABSTRACT)

🧠 Notes:
 Customers are created under: Receivables > Billing > Customers
 Customer records are tied to Business Units, Legal Entities, and
Reference Data Sets.
 Role provisioning must include data access to:
o Customer Business Unit

o Customer Account Set

o Ledger (for AR transactions)

Common questions

Powered by AI

In Oracle Fusion, the Negotiation Creator facilitates the negotiation process by allowing users to create and manage various negotiation documents like RFQs and auctions. This role is essential in defining the terms and conditions under which potential suppliers compete. Meanwhile, the Supplier Manager oversees the onboarding and ensures that selected suppliers comply with negotiated terms. Together, these roles ensure that the negotiation process is both comprehensive and aligned with strategic procurement objectives, ultimately leading to optimized supplier relationships and cost savings .

Oracle Integration Cloud (OIC) streamlines the Procure-to-Pay (P2P) process by automating and integrating various steps across Oracle Fusion applications. It allows seamless data flow between modules, minimizing manual interventions and reducing processing times for tasks such as requisition approvals, purchase orders, and invoice matching. OIC enhances efficiency by providing a unified platform to manage integration specifics like APIs and ESS jobs, thereby facilitating a more integrated and responsive procurement process in Oracle Fusion .

The BI Consumer role in Oracle Fusion provides users with access to run and view reports within Oracle Transactional Business Intelligence (OTBI) and Business Intelligence Publisher (BI Publisher). This role is essential for users required to analyze operational data and generate reports for decision-making. It allows users to take advantage of predefined dashboards and reports, facilitating the analysis of business performance without needing to build reports from scratch, thus enhancing data-driven decision capabilities .

In the Order to Cash (O2C) cycle, a Cash Manager is responsible for managing bank accounts and ensuring proper cash positioning, which includes reconciling bank statements and managing payment applications in the accounts receivable process. Similarly, in the Procure to Pay (P2P) cycle, the Cash Manager handles bank account access, manages payments and disbursement processes, and ensures accurate payment reconciliation. These roles are crucial for maintaining financial control and ensuring efficient cash flow management across these business cycles .

The Requisition Approver role is crucial in Oracle Fusion's procurement approval workflow as it enables designated users to approve requisitions based on set approval rules. This role helps enforce procurement policies and ensures that requests for goods and services align with organizational standards and budgets before they proceed to the purchase order creation stage. By having the appropriate authority and responsibility, Requisition Approvers play a key role in maintaining accountability and control over procurement activities .

The ERP Integration User role in Oracle Integration Cloud (OIC) is vital as it grants access to invoke ERP Cloud's public web services and REST APIs. This role is commonly assigned to the integration user account used in OIC, allowing integrations between OIC and Oracle ERP Cloud to be executed effectively. It ensures that the integration user can connect to the ERP system and execute necessary functions, which is key in automating business processes through API interactions .

In Oracle Fusion, the Supplier Manager role is responsible for onboarding, updating, or approving suppliers, managing supplier sites, and maintaining supplier records. In contrast, the Supplier Qualification Manager focuses on evaluating and managing supplier qualifications, such as assessing suppliers' capabilities to meet organizational standards. Both roles are complementary within the procurement process, where the Supplier Manager handles operational aspects, while the Supplier Qualification Manager ensures compliance and suitability of suppliers .

Business Units (BU) in Oracle Fusion's O2C cycle control access to various functional areas such as Order Management, Accounts Receivable, Collections, and Fulfillment. Assigning the appropriate BU data access to roles ensures that users can perform their duties within the correct organizational context, preventing unauthorized access to critical functions. For instance, a user in the Order Entry step must have access to the Order Management BU to enter sales orders. Proper configuration of BU access supports security management by limiting exposure of sensitive data and ensuring compliance with organizational policies .

Without the IT Security Manager role, managing user roles and checking SOAP/REST security access during troubleshooting becomes challenging. This role is essential for ensuring that security policies on REST/SOAP services are enforced correctly. Failure to properly manage these aspects can lead to errors like '401 Unauthorized' indicating that access attempts to certain services are blocked, which may disrupt integrations or lead to unauthorized data exposure .

The Application Implementation Consultant role provides full access to the Functional Setup Manager (FSM) in Oracle Fusion, allowing users to configure services and perform functional setups. This role is crucial during implementation or testing phases as it offers superuser access to all setup and configuration tasks, including activities like configuring BPM workflows, rules, and escalation paths necessary for a smooth configuration and deployment of Oracle Fusion Applications .

You might also like