Users and Roles
-
Data filtering defines which merchandise and locations a user can access. For example, the user Tom may be limited to viewing only U.S. locations.
-
Role-based access governs what actions a user can perform within the application interface, ensuring users only see and interact with features relevant to their responsibilities.
Table 2-1 User Login Roles
| Role | Equivalent IDCS Role(s) | Description |
|---|---|---|
| Pricing Analyst | PRICING_ANALYST_JOB or PRICING_ANALYST_JOB_PREPROD | Main business user responsible for day-to-day LPO activities and working through price recommendations. |
| Pricing Manager (or Analytical Super User) | PRICING_MANAGER_JOB or PRICING_MANAGER_JOB_PREPROD | Manages analytical configurations, testing, and model diagnostics. |
| Pricing Administrator |
ADMINISTRATOR_JOB or ADMINISTRATOR_JOB_PREPROD |
Responsible for the general system setup and configuration tasks related to the business. |
| Buyer | BUYER_JOB or BUYER_JOB_PREPROD | Responsible for department(s), who submits, approves, or rejects the LPO recommendations, and for the translation of data between LPO and Oracle Retail Price Management (RPM) and Oracle Retail Customer Engagement (CE). |
| Targeted Offer User | TARGETED_OFFER_JOB or TARGETED_OFFER_JOB_PREPROD | Responsible for working through the targeted price recommendations. |
| Regular Price User | REGULAR_PRICE_JOB or REGULAR_PRICE_JOB_PREPROD | Dedicated to working with regular price recommendations. |
Note that the users must the following additional roles (depending on PROD or PREPROD) to access platform services such as saving preferences, saving Query Builder queries, and so on. PLATFORM_SERVICES_ADMINISTRATOR and PLATFORM_SERVICES_ADMINISTRATOR_ABSTRACT (OR) PLATFORM_SERVICES_ADMINISTRATOR_ABSTRACT_PREPROD and PLATFORM_SERVICES_ADMINISTRATOR_PREPROD
Table 2-2 Privileges on Runs and Recommendations
| Privilege | Description |
|---|---|
|
Create new LPO run |
Set up and execute optimizations. All steps on the main train can be carried out, including creating a new run via the copy run functionality. |
|
Modify the name and description of an existing LPO run |
Open an existing run and modify the name and description of that run. |
|
Modify the general strategy of an existing LPO run |
Ability to modify the general strategy for that run. Not applicable for regular LPO runs. |
|
View existing LPO run |
Open an existing run and visit any step in the main train. The user can view data and search/aggregate/filter but cannot change anything. |
|
Optimize a LPO run |
Optimize a new or modified run or a failed run. |
|
Review or Undo Review LPO recommendations |
Review recommendations. Reviewed recommendations can be submitted or approved. |
|
Submit or Undo Submit LPO recommendations |
Submit recommendations for flat files or RPCS web service. When integrated with RPCS, it sends recommendations in Submitted status. |
|
Approve or Undo Approve LPO recommendations |
Approve recommendations for flat files or RPCS web service. When integrated with RPCS, it sends recommendations in Approved status. |
|
Modify LPO recommendations |
Ability to accept, reject, override, or add promotion, markdown or regular price recommendations. |
|
Modify Targeted recommendations |
Ability to accept, reject, or override targeted recommendations for that run. |
|
Delete saved runs |
Delete run setup information and results from the database. |
Table 2-3 Privileges Based on Data Access
| Privilege | Data Access | Pricing Analyst | Pricing Manager | Pricing Administrator | Buyer | Targeted Offer User |
|---|---|---|---|---|---|---|
|
Create new LPO run* |
All runs |
X |
||||
|
View existing LPO run |
All runs |
X |
||||
|
Modify the name and description of an existing LPO run.* |
Runs they created |
X |
||||
|
Modify the general strategy of an existing promotion or markdown LPO run |
Runs they created |
X |
||||
|
Batch runs |
X |
|||||
|
Optimize or re-optimize LPO run |
Runs they created |
X |
||||
|
All runs with technical failures |
X |
X |
||||
| Delete saved LPO runs* | Runs they created | X | ||||
| All runs | X | |||||
|
Modify promotion or markdown recommendation |
Runs they created or batch runs |
X |
X |
X |
||
|
Recalculate LPO recommendations |
Runs they created or batch runs |
X |
||||
|
Review LPO recommendations |
Runs they created or batch runs |
X |
X |
|||
|
Submit LPO recommendations |
All runs |
X |
||||
|
Approve LPO recommendations* |
All runs |
X |
||||
| Modify targeted recommendations | Runs they created or batch runs | X | ||||
| * LPO runs for generating regular price recommendations require additional regular price user role to the above-mentioned roles. | ||||||
Table 2-4 Privileges Based on Run and Recommendation Status
| Role | Privilege | Object | Status |
|---|---|---|---|
|
Users |
cannot modify existing LPO run |
when run is |
running |
|
Users |
cannot optimize LPO runs |
when run is |
running or autorun |
|
Users |
cannot delete saved LPO runs |
when run is |
running |
|
Administrator |
cannot delete saved LPO runs |
when run has |
approved or submitted recommendations |
|
Users |
cannot optimize batch runs |
when run is in |
any status |
|
Users |
cannot modify recommendations |
when recommendation is |
reviewed, submitted, or approved |
|
Users |
cannot modify recommendations |
when recommendation is |
pending calculation or changes |
|
Users |
cannot recalculate |
when recommendation is |
reviewed, submitted, or approved |