Oracle® Retail Insights Cloud Service Suite Administration Guide Release 18.0.002 F20583-01 |
|
![]() Previous |
![]() Next |
This chapter describes the processes for maintaining users and roles as well as batch processes. For information regarding standard end user activities like creating and viewing reports, please see the Oracle Retail Insights User Guide.
It is considered to be a best practice to have all Oracle Retail Insights Cloud Service Suite supports requests submitted through a single point of contact for that customer environment; the client designated administrator is usually designated to perform this role.
The link to use when submitting Service Requests (SR) is:
Oracle Identity Cloud Service (IDCS) provides an innovative, fully integrated service that delivers all the core identity and access management capabilities through a multi-tenant Cloud platform.
For instructions on managing users and groups in IDCS, follow the Manage Users and Groups IDCS document at the following URL:
https://docs.oracle.com/en/cloud/paas/identity-cloud/index.html
Retail Insights Cloud Services is built with role-based access. Permissions are associated with roles.
The following roles are available:
Table 1-1 Retail Insights Cloud Services Default Enterprise Roles
Application Module | Default Enterprise Roles | Corresponding Application Roles |
---|---|---|
ORMI/ORCI |
AltHierarchyInsights_Job |
AltHierarchyInsights |
ORCI |
ConsumerInsights_Job |
ConsumerInsights |
ORCI |
CustomerInsights_Job |
CustomerInsights |
ORCI |
CustomerDetailInsights_Job |
CustomerDetailInsights |
ORCI |
CustomerLoyaltyInsights_Job |
CustomerLoyaltyInsights |
ORCI |
CustomerOrderInsights_Job |
CustomerOrderInsights |
ORCI |
CustomerSegmentInsights_Job |
CustomerSegmentInsights |
ORMI/ORCI |
EmployeeInsights_Job |
EmployeeInsights |
ORMI |
FranchiseInsights_Job |
FranchiseInsights |
ORMI |
InventoryInsights_Job |
InventoryInsights |
ORMI |
PlanningInsights_Job |
PlanningInsights |
ORMI/ORCI |
PromotionInsights_Job |
PromotionInsights |
ORMI |
PurchaseOrderInsights_Job |
PurchaseOrderInsights |
ORMI/ORCI |
SalesInsights_Job |
SalesInsights |
ORCI |
ScienceInsights_Job |
ScienceInsights |
ORMI |
SupplierInsights_Job |
SupplierInsights |
ORMI/ORCI |
RetailAnalysts |
RetailAnalyst |
ORMI/ORCI |
RIApplicationAdministrators |
RIApplicationAdministrator |
ORMI |
TenderInsights_Job |
TenderInsights |
POM |
PROCESS_SERVICE_ADMIN_JOB |
POM Business Role |
Using a combination of the roles above will grant access to sets of metrics and attributes in RI in an additive fashion. One exception is the CustomerDetailInsights role, which is a special role intended to grant access to detailed customer information, such as their name and phone number. This role must be used in combination with the CustomerInsights role to get access to these attributes, and can be limited to a subset of RI users. Without the additional role, the CustomerInsights role only grants access to basic non-identifying customer information such as the customer ID and generic user-defined attributes.
Additionally, the following Oracle Business Intelligence roles are used in combination with the application roles above. Assign a combination of these system roles depending on the level of access required for each user. For example, a local systems administrator could be granted all of the roles in this table, and the permissions will be additive.
Table 1-2 Retail Insights Cloud Services OBIEE Roles
Application Module | Application Roles | Permissions Level |
---|---|---|
ORMI/ORCI |
BI Consumer |
Ability to view content created by others. Cannot create new content. |
ORMI/ORCI |
BI Author |
Ability to create and share new content, including analyses and dashboards. |
ORMI/ORCI |
BI Content Author |
Visual Analyzer module within OBI EE, along with the ability to upload spreadsheets as data sources. |
Assign the above roles to the user following the steps mentioned in the previous section as per your requirement. The table below describes some common users and the associated roles they could be granted for RI access.
Table 1-3 Retail Insights Cloud Services OBIEE User Examples
User Group | Application Roles | Description |
---|---|---|
RI Admins |
BI Consumer BIAuthor BI Content Author Retail Analyst RIApplicationAdministrator |
This user group has access to all functional areas in RI and will have the ability to manage Agents and modify and delete objects in the /Shared Folders/Custom/ space in the catalog. |
Merchandisers |
BI Consumer BIAuthor BI Content Author SalesInsights InventoryInsights SupplierInsights |
This user group has access to the Sales, Inventory, and Supplier areas in RI, which are typically required for merchandisers and buying teams. |
Store Managers |
BI Consumer Retail Analyst |
This user group has read-only access to RI, meaning they can run any report which has been shared with them but cannot create content themselves. |
The following is the file upload process. For details regarding file contents and formatting please refer to the Oracle Retail Insights Cloud Services Integration Guide. The Private/Public Keys must be generated and the public Key must be associated with your SFTP Account for the file uploads. The Adding Authorized Keys section describes the step-by-step method to generate the Keys (2048 bit RSA Keys).
The following is the process to generate a 2048 bit RSA key and add the same to the SFTP server. This is done with the help of WinSCP tool on Windows. However the same can be done using ssh-keygen on Linux as well.
Launch WinSCP and select Tools -> Run PuttyGen.
Select "SSH-2 RSA" for the type of key to generate and enter "2048" for the number of bits in a generated key field and click Generate.
Move the mouse over the blank space in the window until the key is generated.
Once the key is generated, click the Save public key button to save the public key to a file.
Click the Save private key button to save the Private key to a file. Confirm to save it with/without a passphrase.
Open an SR with Oracle Support, to associate the Public half of the Key with your SFTP account (attach the Key with the SR).
The Upload steps uses the private key generated in the earlier section.
Launch WinSCP and connect to <SFTP Server> using port 22.
Enter the username and click Advanced.
Click Authentication.
In the Private Key File field, click the Browse button and select the private key created in the earlier section.
After loading the private key file, click OK.
Click Login. The window does not prompt for a password and logs into the SFTP server. Provide a passphrase if one has been set up.
Login to the WinSCP by Following the Steps – Login to WinSCP section.
Transfer all data files to the directory /<SFTP User>.
Create a directory called COMMAND under /<SFTP User>if it does not already exist.
Change to the /<SFTP User>/COMMAND directory.
Transfer an empty file called COMPLETE.
Login to the WinSCP by following the Steps – Login to WinSCP section. The following is the download file process.
Change directory to /<SFTP User>/EXPORT.
Download all data files.
After creating an Analysis (report) that is needed to be refreshed and saved to a file for downloading, from the OBIEE home screen select New -> Agent.
After setting the schedule for the Agent execution, go to the Delivery Content tab and select the analysis report, don't worry about the other settings on this tab such as format because these will be overridden by other selections on the Actions tab.
Ignore the Recipients and Destinations tabs, go to the Actions tab and add a new Action that "Invokes a Java Method".
Select "REPORT ARCHIVE EJBs / biserver / ArchiveReports / BIReportArchieveApplication-ArchiveReports-ArchiveReports / ArchiveReport".
Enter the filename that the report should be written into, and select "Delivery Content".
Click the small black page icon with the turned corner and select the file format to be written, then click OK.
Click Save Agent and give the Agent a name. At this point the Agent has been defined and will execute according to the defined schedule.
If you would like to do an immediate execution of the Agent you can click Run Agent Now.
The following dialog displays while the agent is running:
This section provides a detailed approach of configuring the dashboard detailed reports and InfoTiles created within OBIEE 12C. The new column and Info-Tile configuration optimizes the hard-coding of column (exception) values in Conditional Format and in case of InfoTiles, severity formula by storing the column range (min and max) values in the database and rendering it to the dashboard using presentation variables. At present, this has been implemented in CEO dashboard. User can change the dashboard column and tile configuration if required by following the steps mentioned below.
Perform the following procedures to configure the dashboard column values.
RI_DASHBOARD_CONFIG is the table to store the dashboard configuration. Below is the screenshot for the field values of the RI_DASHBOARD_CONFIG table.
Where,
Table 1-4 RI_DASHBOARD_CONFIG Table Fields
FIELD_NAME | Regular OBIEE Analysis | INFO-TILE Analysis |
---|---|---|
REPORT_NAME |
Name of the detailed report |
Tile Title |
PARAM_NAME |
Name of the column whose values need to be dynamic |
Tile Title |
PARAM_TYPE |
Tells whether it is a detailed report or tile. Value to be inserted: Column |
Tells whether it is a detailed report or tile. Value to be inserted: Tile |
ATTR1, ATTR1_MAX_VALUE, ATTR1_MIN_VALUE |
Name of the column whose values need to be dynamic. Max column value above which the column appears green and Min column value below which the column appears red. |
If the Tile Main Metric value (sub-metric value can also be compared by editing severity formula) lies between the MIN_VALUE and MAX_VALUE, the tile appears to be red (critical). ATTR1 must represent the severity value "critical" |
ATTR2, ATTR2_MAX_VALUE, ATTR2_MIN_VALUE |
Can be added in future. |
If the Tile Main Metric value lies between the MAX_VALUE and MIN_VALUE, the tile appears to be yellow. ATTR2 must represent the severity value "important" |
ATTR3, ATTR3_MAX_VALUE, ATTR3_MIN_VALUE |
Can be added in future. |
If the Tile Main Metric value lies between the MAX_VALUE and MIN_VALUE, the tile appears to be green. ATTR3 must represent the severity value "normal" |
ATTR4, ATTR4_MAX_VALUE, ATTR4_MIN_VALUE |
Can be added in future. |
If the Tile Main Metric value lies between the MAX_VALUE and MIN_VALUE, the tile appears to be blue. ATTR4 must represent the severity value "no severity" |
Note: For detailed reports columns, currently only ATTR1 is used. ATTR2, ATTR3,…ATTR8 can also be inserted in the future based on the requirement. For Info-Tiles, ATTR5, ATTR6, ATTR7, ATTR8 can also be inserted in the future based on the requirement. |
The MAX_VALUE and MIN_VALUE depend on the Tile severity logic. Example: For a dashboard containing Net Sales Amt Info-Tile, the tile severity is critical if the Main Metric value lies below the MIN_VALUE. For a dashboard containing Return Items Info-Tile, the tile severity is critical if the Main Metric value lies above the MAX_VALUE.
Now, a table for dashboard configuration is created. Let's now insert values into the table to get started. The following typical SQL insert query can be written to insert entries into the RI_DASHBOARD_CONFIG table.
The RI_DASHBOARD_CONFIG table has been exposed in the Retail Merchandising Analytics As-Was. It can be directly rendered in the front-end.
Now, we're going to create an Exceptions Threshold prompt to set the presentation variables.
Create a Dashboard Prompt by clicking New?Dashboard Prompt.
Note: Each page in the dashboard must have a single Exceptions Threshold Prompt.For example, if the dashboard has two pages namely Promotions and Sales, the prompts must be named Promotions Exceptions Threshold Prompt and Sales Exceptions Threshold Prompt respectively. |
Click the New icon and select variable prompt.
In the Edit Prompt Dialog Box, provide a name for the Presentation variable and select User Input as Text Field.
The naming for the Presentation variable should be logical to the context and camel cased.
For example: MtdClearanceSalesMaxCompColumn, MtdClearanceSalesMinCompColumn
We can have our own label for the variable.
Expand the Options pane and under General tab, the Variable Data Type can be based on the column type. Select 'SQL Results' for Default selection and enter a SQL statement in text box.
The SQL query added in the text field is explained below:
SELECT "RI Dashboard Config"."ATTR1_MAX_VALUE" FROM "Retail Merchandising Analytics As-Was" WHERE "RI Dashboard Config"."REPORT_NAME" = 'MTD Clearance Sales' AND "RI Dashboard Config". "PARAM_NAME" = 'Comp % Var' AND "RI Dashboard Config"."PARAM_TYPE"='Column'
The above query fetches the max value of the column "Comp % Var" of the report "MTD Clearance Sales" from the table "RI DASHBOARD CONFIG".
The number of Presentation variables depends on the number of attributes we added in the table.
Go to Edit Dashboard. Click on Tools icon on the right and select Dashboard Properties. In the Dashboard Properties dialog box, click edit Filters and Variables icon.
Load the prompt by clicking on the plus icon.
After loading the prompt the Dashboard Filters and Variables dialog box looks like:
Open the report in the dashboard (Make sure all the reports in the dashboard are formatted).
Go to criteria tab and choose Column Properties for the column that needs to be conditional formatted.
Go to Conditional Format tab in the Column Properties dialog box. Before including the presentation variables, the conditions look like:
Click on the condition to add presentation variable. Click Add more options in the Edit Condition dialog box and select Presentation variables.
Empty the Value field. Fill the Variable Expr field with the corresponding Presentation Variable. Click OK. Repeat the same for all the required exception columns. Refer the snapshot below for sample.
Note: For union-criteria analysis that has multiple criteria, include the Presentation Variable in three places:
|
We have configured the detailed reports using Presentation variables. Now, we are going to configure Info-Tile inside the dashboard.
Click on Edit formula on the severity column for the required Info-Tile.
Write CASE statements in the formula as below.
CASE WHEN (IfNull("Sales"."Net Pro Sales Amt MTD",0)) <= @{MtdPromotionSalesCriticalMinTile} THEN 'high' WHEN (((IfNull("Sales"."Net Pro Sales Amt MTD",0)) > @{MtdPromotionSalesImpSevMinTile}) AND (IfNull("Sales"."Net Pro Sales Amt MTD",0)) <= @{MtdPromotionSalesImpSevMaxTile}) THEN 'medium' WHEN ((IfNull("Sales"."Net Pro Sales Amt MTD",0)) > @{MtdPromotionSalesNoSevMinTile} AND (IfNull("Sales"."Net Pro Sales Amt MTD",0)) <= @{MtdPromotionSalesNoSevMaxTile}) THEN 'none' ELSE 'low' END
The above CASE statement returns the severity value of the tile:
If the main metric value is lesser than the MtdPromotionSalesCriticalMinTile, the severity is high.
If the main metric value is between the MtdPromotionSalesImpSevMinTile and MtdPromotionSalesImpSevMaxTile, the severity is medium.
If the main metric value is between the MtdPromotionSalesNoSevMinTile and MtdPromotionSalesNoSevMaxTile, the severity is none.
Otherwise, the severity is low.