Quick Guide: Restricting Item & Manufacturer Access in Oracle Fusion
Controlling access to sensitive product data is critical for maintaining supply chain integrity. In Oracle Fusion, security is managed through a combination of Function Security (what you can do) and Data Security (what data you can see).
1. Restricting Manufacturer Access
To secure manufacturer data, Oracle leverages Access Control Lists (ACLs) for granular permissions.
Enable Redwood UI: Ensure the profile option
EGP_MANUFACTURER_REDWOOD_ENABLEDis active.Define Privileges: Use the Security Console to assign standard privileges (e.g., View Manufacturers, Manage Manufacturers) to custom roles.
Apply ACLs: * Navigate to the manufacturer's Security tab.
Create specific grants for users or groups.
Assign 'View' or 'Maintain' access at the manufacturer or part level.
2. Restricting Item Access
Item security is primarily driven by the Item Class hierarchy and Organization-level data grants.
Segment by Item Class: Create distinct classes (e.g., "High Security" vs. "General").
Disable Public Access: Deselect the Public checkbox on the Item Class to move from an "open by default" to a "restricted" model.
Data Security Policies:
Go to the Security tab of the Item Class.
Create Data Grants specifying the User, the Organization, and the Actions (e.g., Browse Item, View Item).
Implementation Checklist
| Step | Action | Tools Used |
| 1 | Identify Stakeholders | Business Requirements |
| 2 | Create Custom Roles | Security Console |
| 3 | Assign Function Policies | Security Console (Privileges) |
| 4 | Define Data Grants | PIM / Product Development |
| 5 | User Assignment | Security Console / OIM |
Pro Tip: Always test your custom roles in a lower environment using the "Simulate Navigator" or by logging in as a test user to ensure the Data Grants are filtering items correctly.
