Mirror of Oracle documentation
Converted for search and offline reading. Authoritative source: Oracle. Diagrams and some complex tables are simplified — check the PDF when in doubt.
4 Users, Roles and Privileges
LPO enforces two independent layers of access control: role-based security, which governs what actions a user can perform, and data-level security, which governs which merchandise and location data a user can see and act on. Both must be configured correctly before a user can work with Rules Based Regular Pricing runs and recommendations.
Role-Based Security
Role-based security in LPO is managed through Oracle Identity Cloud Service (IDCS) role assignments. Each LPO role grants a defined set of privileges: the actions a user is permitted to perform within the application. A user may hold multiple roles simultaneously, and their effective privileges are the union of all privileges across their assigned roles. Role assignments are managed by the Pricing Administrator.
Data-Level Security
Data-level security restricts which merchandise hierarchy nodes and locations a user can view and act on, independent of role-based privileges. For example, a Pricing Analyst may have the privilege to accept recommendations but can only accept recommendations for the departments and zones assigned to them in data-level security. Data-level security is configured per user by the Pricing Administrator.
End-to-End Workflow and Role Context
Rules Based Regular Pricing follows a six-stage workflow. Understanding this flow helps users see where their role, privileges, and responsibilities fit in the overall pricing process.
Rules Based Regular Pricing User Guide G58167-03 Copyright© 2026, Oracle and/or its affiliates.
Table 4-1 (Cont.) User Login Roles
| Role | IDCS Role | Responsibility |
|---|---|---|
| Buyer | BUYER_JOB BUYER_JOB_PREPROD | Owns merchandise departments. Takes final action on reviewed recommendations: Submit or Approve. Both actions trigger export to downstream systems. Can also reject recommendations. |
| Pricing Administrator | ADMINISTRATOR_JOB ADMINISTRATOR_JOB_PREPR OD | Manages application configuration including Rules Based Regular Pricing enablement using PRO_LPO_REGULAR_LITE_EN ABLED_FLG flag, auto-approval criteria, and export frequency rules. |
Run and Recommendation Privileges
LPO privileges govern what actions each role can perform on runs and recommendations. The tables below define each privilege and show which roles hold them.
Table 4-2 Privileges on LPO Runs and Recommendations
| Privilege | Description |
|---|---|
| Create new LPO run | Set up and execute optimization runs, including copying existing runs. |
| View existing LPO run | View run data at each stage. Can search and filter but cannot edit. |
| Optimize a LPO run | Trigger optimization or re-optimization, including for failed runs. |
| Modify recommendations | Accept, reject, or override regular price recommendations. |
| Review / Undo Review | Transition recommendations to Reviewed status, a prerequisite for Submit or Approve. |
| Submit recommendations | Send final recommendations to the export interface for execution by the downstream system. |
| Approve recommendations | Approve recommendations for export. May bypass the Submit step depending on configuration. |
| Finalize What-If run | Promote a finalized What-If run result to replace the current batch recommendations. |
| Delete a run | Remove a run and its recommendations, subject to status restrictions. |
Rules Based Regular Pricing User Guide G58167-03 Copyright© 2026, Oracle and/or its affiliates.
Role Based Privileges
Table 4-3 Privileges Based on Data Access and User Role
| Privilege | Data Scope | Pricing Analyst / Regular Price User | Pricing Manager | Buyer | Pricing Administrator |
|---|---|---|---|---|---|
| Create/Copy Run | All runs | ✓ | |||
| View Run | All runs | ✓ | ✓ | ✓ | |
| Modify Run | Runs owned by user | ✓ | ✓ | ||
| Run / Re-run | Runs owned by user | ✓ | ✓ | ||
| Delete saved LPO run | Runs owned by user | ✓ | ✓ | ||
| Modify recommendatio ns | Runs owned / batch | ✓ | ✓ | ✓ | |
| Recalculate recommendatio ns | Runs owned / batch | ✓ | ✓ | ||
| Review recommendatio ns | Runs owned / batch | ✓ | ✓ | ✓ | |
| Submit recommendatio ns | All runs | ✓ | |||
| Approve recommendatio ns | All runs | ✓ | |||
| Optimize all technical failures | All runs with technical failures | ✓ | ✓ |
Action Restrictions By Status
Table 4-4 Action Restrictions by Status
| Who | Object |
|---|---|
| Auto Approved | Cannot be selected for price override, date override, accept/reject, review/submit/approve, undo review, or undo approve actions. These recommendations are processed automatically by the export workflow and cannot be modified manually. |
| Export Success | Must not be pushed again to the downstream pricing system. |
Rules Based Regular Pricing User Guide G58167-03 Copyright© 2026, Oracle and/or its affiliates.
Table 4-4 (Cont.) Action Restrictions by Status
| Who | Object |
|---|---|
| Export Failed | Can be picked up again by the batch or ad hoc integration push process after the failure is investigated. |
| Rejected | Excluded from downstream export. |
Rules Based Regular Pricing User Guide G58167-03 Copyright© 2026, Oracle and/or its affiliates.
In this guide
- Guide: Lifecycle Pricing Optimization Rule Based Regular Pricing User Guide
- Previous: 3 Navigating the Application
- Next: 5 Rules and Strategies
Related chapters
- 2 LPO Workflow and User Roles — Lifecycle Pricing Optimization User Guide · shares
ADMINISTRATOR_JOB,ADMINISTRATOR_JOB_PREPR,BUYER_JOB,BUYER_JOB_PREPROD