# Oracle Fusion Manufacturing Roles: Job Roles, Privileges and Standard Business Process Models > Source: https://netray.co/erp-help/oracle-fusion-manufacturing-roles-and-business-process-models > Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems. > Section: ERP Help ## Short answer Fusion Manufacturing access comes from seeded job roles such as production supervisor, production operator and manufacturing engineer, which bundle duty roles and privileges. Copy them in the Security Console rather than editing them, assign them to users in Manage Users, and use Oracle's business process models as the reference for who does what. ## Kind how-to ## System oracle-fusion ## Erp Oracle Fusion Cloud Manufacturing ## Module Security Console / Manufacturing Job Roles ## Query oracle fusion manufacturing roles ## Alternate Queries - oracle fusion business process models - oracle fusion manufacturing job roles privileges - oracle fusion production supervisor role - oracle fusion copy seeded role manufacturing ## Applies To Oracle Fusion Cloud SCM, quarterly releases. Role display names are given as commonly seen; confirm exact names and codes in your Security Console because Oracle adds and renames roles between updates. ## Steps ### How to set up manufacturing roles in Oracle Fusion **Items:** List who does what in your plant: engineers who maintain work definitions, schedulers or planners, supervisors who release and close work orders, operators who report on the floor, cost accountants who review variances. Open Tools > Security Console and search for roles containing Manufacturing, Production or Work Order to see the seeded job roles for your release. Open a candidate role and review its role hierarchy: the duty roles it inherits and the function and data security privileges beneath them. Use Copy Role to create a custom role (for example, a company prefix plus the seeded name) instead of editing the seeded one. Remove or add duty roles as required and save. Define data security: users also need data access to the right manufacturing plant (inventory organization) and business unit. Assign data roles or security contexts accordingly. Assign roles to users in Tools > Manage Users, or automatically through role provisioning rules based on job, department or location. Run the user access reports and test with a real user in a test pod, covering the whole cycle: create work definition, create and release work order, report from the Dispatch List. Review segregation of duties, for example that the person who maintains work definitions is not also approving cost adjustments. ## Sections ### How Fusion security is layered **Body:** Fusion uses role-based access in three layers. Privileges grant access to a function or data object. Duty roles group privileges into a coherent task such as managing work orders. Job roles are what you assign to people, and they inherit duty roles. Data security then limits which organizations, business units or ledgers the access applies to. This is why a user can have the correct job role and still see nothing: the function security allows the screen but the data security gives no organization. If a user reports a missing work area or empty lists, check both layers before changing the role. ### Typical manufacturing job roles **Body:** Oracle seeds job roles for the main personas: a production supervisor who manages and releases work orders, a production operator who executes operations on the Dispatch List, a manufacturing engineer who maintains work definitions, work centers and standard operations, and planning-related roles for supply planners. Cost and inventory roles sit beside them in the cost accounting and inventory families. Do not assume one role fits a person. Real plants combine roles, for example a supervisor who is also an engineer in a small site. Prefer assigning two narrow roles to a person over making one over-broad custom role, since it keeps audits readable. **Code:** - Tools > Security Console > Roles > search 'Manufacturing' / 'Production' / 'Work' - Tools > Manage Users > Edit user > Roles > Add Role - Setup and Maintenance > Manage Role Provisioning Rules ### Standard business process models **Body:** Oracle publishes business process models for its Cloud applications that map end-to-end processes such as plan to produce, with the activities, the roles that perform them and the applications involved. They are found through the Oracle Help Center and the implementation documentation for each product family. They are useful as a starting point for design workshops. Use them to answer which role does this step and what is the standard flow, then document your deviations. Because they are generic, they do not know your plant. Treat them as a reference baseline, not a configuration. ### Common role problems **Body:** The commonest issues are missing data security, users who need a Setup and Maintenance task role to see setup pages, and roles that were provisioned but not synchronised because the nightly Retrieve Latest LDAP Changes job did not run. Role changes can also take time to apply when users already have an active session. When troubleshooting, use the Security Console's role and user analysis views, check the role hierarchy, and compare the failing user with a working colleague. Avoid solving access issues by granting a broad administrator role, which will fail any later audit. ## Pitfalls - Editing seeded roles directly, then losing the change or breaking upgrades; copy them instead. - Granting function privileges but no data security for the manufacturing plant, so lists stay empty. - Handing out an administrator role to bypass a missing privilege. - Giving operators the same role as supervisors, so anyone can close work orders or change quantities. - Forgetting that role changes may need the user to sign out and in, or for the sync job to run. ## Ai Angle An assistant grounded in Fusion can compare users who share a job but see different screens, list who holds a role that can close work orders, and flag combinations that break segregation of duties. It works from security reports and the access data you expose to it, shows its sources, and does not change roles itself. Running the model privately lets you keep security metadata inside your network. ## Faq ### What roles does Oracle Fusion Manufacturing use? **Answer:** Seeded job roles typically cover production supervisor, production operator, manufacturing engineer and related planning, inventory and cost roles. They inherit duty roles with the privileges. Check the exact list in your Security Console, since names vary by release. ### Should I edit the seeded roles? **Answer:** No. Copy the seeded role in the Security Console and change the copy. Seeded roles are maintained by Oracle and may be updated in quarterly releases, so edits to them can be overwritten or cause conflicts. ### Why does a user have the role but see no work orders? **Answer:** Usually data security is missing. The user needs access to the manufacturing plant (inventory organization) and business unit, not just the function privileges. Check the user's data roles or security contexts and retest. ### Where are Oracle's business process models? **Answer:** In the Oracle Help Center documentation for Oracle Cloud applications, usually within the implementation material of each product family. They show standard processes, the roles that perform them and the applications involved, and are best used as a design baseline. ## Search terms oracle fusion manufacturing roles, oracle fusion business process models, fusion security console, fusion production supervisor role, fusion manufacturing job roles, fusion copy role, fusion data security manufacturing, oracle plan to produce process, fusion role provisioning rules --- Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json