# Oracle Fusion Role Provisioning Worksheet

> Source: https://netray.co/tools/oracle-fusion-role-provisioning-worksheet
> Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems.
> Section: Free Tools

## Short answer

Plan who gets which Fusion job role, with which data access, who approved it and whether it raises a segregation of duties concern.

## Category

oracle

## Erp

Oracle Fusion Cloud SCM

## Audience

- Oracle Cloud consultant
- Security administrator
- Internal auditor

## Tool

**Kind:** worksheet

**Mode:** editable

**Columns:**

#### User

**Key:** user

**Type:** text

#### Department

**Key:** department

**Type:** text

#### Job role

**Key:** job_role

**Type:** text

#### Data security context

**Key:** context

**Type:** text

#### Scope value

**Key:** scope

**Type:** text

#### Access level

**Key:** access

**Type:** select

**Options:**

- Inquiry
- Transact
- Administer

#### SoD concern

**Key:** sod

**Type:** select

**Options:**

- None
- Review
- Conflict accepted

#### Approver

**Key:** approver

**Type:** text

#### Request ticket

**Key:** ticket

**Type:** text

#### Approved on

**Key:** approved_on

**Type:** date

**Rows:**

**User:** a.rao

**Department:** Production control

**Job role:** Production Supervisor

**Context:** Inventory organization

**Scope:** Plant 01

**Access:** Transact

**Sod:** None

**Approver:** Plant manager

**Ticket:** REQ-1042

**Approved on:** 2026-10-12

**User:** m.lopez

**Department:** Purchasing

**Job role:** Buyer

**Context:** Procurement business unit

**Scope:** US1 Procurement BU

**Access:** Transact

**Sod:** Review

**Approver:** Procurement manager

**Ticket:** REQ-1043

**Approved on:** 2026-10-12

**User:** k.chen

**Department:** Finance

**Job role:** Accounts Payable Specialist

**Context:** Business unit

**Scope:** US1 BU

**Access:** Transact

**Sod:** Review

**Approver:** Controller

**Ticket:** REQ-1044

**Approved on:** 2026-10-13

**User:** s.iyer

**Department:** IT

**Job role:** Application Implementation Consultant

**Context:** None (functional setup)

**Scope:** All

**Access:** Administer

**Sod:** Conflict accepted

**Approver:** IT director

**Ticket:** REQ-1045

**Approved on:** 2026-10-14

**User:** j.smith

**Department:** Warehouse

**Job role:** Warehouse Manager

**Context:** Inventory organization

**Scope:** DC 02

**Access:** Inquiry

**Sod:** None

**Approver:** Logistics manager

**Ticket:** REQ-1046

**Approved on:** 2026-10-14

**Totals:**

#### Assignments

**Key:** user

**Agg:** count

**Format:** integer

**Notes:** Job role names in the sample rows are illustrative. Use the seeded and custom roles that exist in your environment and your own segregation of duties matrix. Role copies, duty roles and data security policies differ per implementation, so verify them in the Security Console before provisioning.

## Content

**Intro:** Giving someone the wrong Oracle Fusion role is easy, and cleaning up afterwards is slow. This worksheet records each assignment with its data access, approver and segregation of duties note, so the audit trail exists before anyone asks for it.

**Sections:**

#### How to use the worksheet

**Body:** Add one row per user and job role. Fill in the data security context and the scope value, because job roles alone do not decide what a user can see. Record the approver and request ticket, and mark any segregation of duties concern for review. Export to Excel and send it to the business owner for confirmation before the assignments are made in the system, then keep it as evidence.

#### Roles and data access in Fusion

**Body:** Access in Fusion comes from job roles, which bundle duty roles and privileges, combined with data security that limits which business units, organizations, ledgers or other contexts a user can reach. Two people with the same job role can see very different data. That is why the worksheet captures both the role and the data scope. Mistakes usually appear in the scope, not the role name.

**Bullets:**

- Job role: what functions the user can perform
- Data security context: where they can perform them
- Access level: inquiry, transact or administer
- Approval: who authorized it and when

#### Segregation of duties

**Body:** Flag combinations where one person could both create and approve, or maintain suppliers and pay them. Use your organization's own conflict matrix and review any Review rows with the process owner. If a conflict is accepted, write the compensating control, such as an independent review report, in the notes and set a review date. Auditors want to see that the decision was deliberate.

#### Common mistakes

**Body:** Copying a colleague's access wholesale accumulates privileges over time. Provisioning implementation consultants as permanent administrators after go live is a frequent finding. Another is forgetting to remove access on transfers and leavers. Schedule a periodic recertification, quarterly for sensitive roles, and use the approval dates here to drive it.

**Cta:** Netray can help build read-only reports over your ERP security data on your own infrastructure so role reviews are quicker. The worksheet works without it.

**Faq:**

#### What is the difference between a job role and a duty role?

**Answer:** A job role represents a position such as a buyer and is made up of duty roles, which group privileges for particular tasks. Users are generally assigned job roles, while duty roles are the building blocks within them.

#### Why must I record data security context?

**Answer:** Because the job role only says what functions a user can use. The data security context decides which business units, inventory organizations or ledgers they can use them in. Without it, the record of access is incomplete.

#### How often should access be reviewed?

**Answer:** At least annually for general users and more often, such as quarterly, for privileged or financial roles. Also review on transfers, leavers and after major changes to role design.

#### Should I change seeded roles?

**Answer:** Generally copy a seeded role and adjust the copy, rather than editing the delivered role. This keeps your changes visible and lowers the risk of surprises when updates change delivered roles.

## Search terms

oracle fusion role provisioning, oracle fusion job role assignment worksheet, oracle fusion user access matrix, oracle fusion segregation of duties, oracle cloud security role mapping, oracle fusion data security context, oracle fusion role matrix excel, oracle fusion user access request

---
Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json
