The below prototype helps in building common reporting solutions across fusion CRM and IC Pillars, current DWH model doesn't have direct reporting solution across the pillars.

Content:

Background & Business Case -

Customers who are using both CRM SALES and IC, as of now they are unable to create the report with common dimensions and metrics from both the pillars.

Any customer whose sales representatives involved in SALES activities and to check their compensation details till now customers are importing the same sales representatives data into IC and creating the reports.

Any customer if wants to create the report using SALES and IC dimensions there is no proper linking between these pillars and end up creating a cross SA with completely improper data.

Hence to resolve this we have an idea on joining CRM sales resource hierarchy and IC participant hierarchy, functionally which is same but technically there is no implementation.

CRM resources or sales representatives are the same IC participants who are getting compensation in IC. Hence using this functional derivation we are joining the CRM resource hierarchy and IC participant hierarchy details to get the common report across both the pillars.

CRM sales data ends once the order details have been placed, from there IC starts with the order data and ends with payment information.

As of now, we don't have any direct reports which have complete sales details along with the Incentive compensation metrics.

With this joining, we can get a complete report with SALES dimensions and metrics followed by IC metrics.

FA Implementation -

To implement this requirement we have to make a couple of table joins from FA side which was not implemented as of now.

Customers which are importing sales data into IC and creating reports from them we have to provide a solution with FA database tables join like below:

JTF_RS_REP_MANAGERS_CF is used to fetch manager/hierarchy for resources stored in JTF_RS_RESOURCE_PROFILES in Sales. IC participants are stored in CN_SRP_PARTICIPANTS_ALL and the hierarchy is sourced from HCM table PER_MANAGER_HRCHY_REPORTEES_DN

Sales resource hierarchy and participant hierarchy are not stored in a common table. There is no process to sync this data either. The only link is the hz_parties.party_id (TCA) present in both Sales and IC tables.

Ideally, a customer implementing both IC and Sales will import sales resources in IC as participants. So, yes, jtf_rs_resource_profiles.party_id can be looked up for matching party_id records in cn_srp_participants_all

Data Mockups -

Need to consider the participant's data directly from the database, so that we can cross-compare the same when implemented in OTBI.

SALES DATA with PARTYID as main columns followed by all the main dimensions columns BASE ID values, FOR IC data, we have participant ID for the equivalent PARTYID columns followed by all the base dimensions columns BASE ID values. Please refer to attached Mockups

Points to note - We have to make the join between PARTID from sales and PARTYID from IC.

Mandatory Join, We have to join ORDER_ID from sales and TRANSACTION_ID from IC. Because functionally OREDR_ID = TRANSACTION_ID. I.E. SALES REPS who are making orders, only those are considered as TRANSACTIONS in IC. Hence we have to consider this joins for PROPER reporting data.

Note -

1) Credit AMOUNT calculated based on the SPLIT PCT for each transaction handled by the participant.

2) SPLIT PCT was given if two participants involved in one single transaction.

3) Earning AMOUNT will be 5% of the credit amount.

4) Transactions with status "CREDITED" are only considered for credit amount calculations

5) Similarly credits with status "Credited" are only considered for earning calculations.

Please find the complete observations and current standings –

The entire idea of building this prototype is to provide a reporting solution which has both SALES and IC metrics.

The current model doesn’t support continuous reporting from sales to IC, hence to achieve this we want to integrate common dimensions shared across both the pillars i.e. joining both the pillars data using employee resource hierarchy from sales and participant hierarchy from IC. Similar to the partner dimension project.

By considering the above assumption we have started building the prototype by using SALES mockup (The one used for all the SALES POCS) and IC mockup(One we built completely new).

Current joining flow is “IC → Resource Hierarchy → SALES”, from the current FA model we were able to identify the joins to link IC facts to resource hierarchy dimensions(PFA FA tables screenshot).

Whereas we are encountering trouble finding the joins to resource hierarchy → sales facts. Because in the current model Order details are coming from ORDER management and SALES data ending with Opportunity data.

using Order_num from transactions table we can join IC data with Order management data but later from order management to SALES Oppty, we don't have proper joins to establish.

There are no proper joins to get SALES Oppty data and SALES facts to build the solution at RPD level.

Business Use Case:

Who can use this report (Roles) - Incentive Compensation Manager/ Analyst/ Sales Representative

The below dashboard is a sample implementation that shows how the Performance and Earnings Summary Subject area can be used to report metrics related to payment recovery.

This report is designed for the benefit of an Incentive Compensation Manager and/or an Incentive Compensation Analyst to help them understand the advance amount recovered and also the advance to be recovered based on ITD and PTD calculations so that the payments can be adjusted as required. Further, the Subject Area has been enhanced to support reporting of comp plan assignment types (Direct/Role-based) and also whether the participant’s incentive has been customized at a comp plan level.

All these enhancements are available from 19D onwards.

Quarterly Recovery Amounts by Participant:

A WAVE view provides info about all the recovery amounts by the participants against the target by Quarter.

You can move to each quarter by the using slider to move between quarters.

Period wise Recovery Amounts by Participant:

A bar chart provides info about all the recovery amounts by the participants against the target by each period. You can move to each quarter by the using slider to move between quarters.

How to deploy:

Un-archive “Recovery Amounts Dashboard.catalog” files which have all the individual report, dashboard prompt, and the dashboard.

Ensure that you un-archive it under /shared/custom folder to retain the references that the dashboard has to those individual files (else you may correct those again in the dashboard)

Implementation notes:

The data fetched is for the selected Year and Participant Name from the dashboard prompt.

From R13 onwards, you are allowed to select multiple values to check the results .E.g. You can submit one year and all the period/participant vales to see how the responses compare on different parameters

Cascading prompts is a feature that is liked by many customers because it allows them to have a preview of their data through prompts before actually seeing the data.

Content:

Business Use Case:

Attainment Summary

Who can use this report (Roles) - Incentive Compensation Manager/ Analyst/ Sales Representative

Cascading prompts is a feature that is liked by many customers because it allows them to have a preview of their data through prompts before actually seeing the data.

Most of the times customers want to do themselves a cascading report, the below example will show how to do the cascading within the report and you can select only required values.

Example: In the below report we have four prompts “Year”, “Participant”, “Unit of measure”, “Performance Measure”.

Cascading prompts will work by showing the results of the second prompt followed by the values you selected in the first prompt and goes on.

I.e. participant prompt values will show based on what year you selected, and performance measure will show values based on which participant and year we selected.

We can do this by selecting whichever prompt values we wanted to cascade and then go to edit section selecting more options and choosing “limit Values By”.

We can follow the same process for all the prompts which are needed to include as cascading.

Year wise participant list:

We have selected the year 2018 and all the participants involved in 2018 only will be listed.

Year, Participant wise performance measure:

We have selected the year 2016 and Participant as “Allison Flores” and only related performance measure values are showing up.

Without this change, you will end up seeing all the participants’ data irrespective of year and seeing all performance values irrespective of year and participant selected.

How to deploy:

Un-archive “Attainment Summary.catalog” files which have all the individual report, dashboard prompt, and the dashboard.

Ensure that you un-archive it under /shared/custom folder to retain the references that the dashboard has to those individual files (else you may correct those again in the dashboard)

Implementation notes:

The data fetched is for the selected Year, Participant Name, Unit of measure and Performance Measure.

From R13 onwards, you are allowed to select multiple values to check the results .E.g. You can submit one year and all the period/participant vales to see how the responses compare on different parameters

i need your help please on a BI-Reporting subject within Sales Cloud R13-18C.

Here is the scenario: i created a report based on Accounts and their opportunities, which are showing basically 2 axes (X= Opportunity Status which may be Lost, Won or Open), then Y= Expected revenue, which is the expected volume by Opportunity)

The report will be embedded as Mqshup content link within a sub-Tab in the Accounts (means within an account, you have several sub-Tabs, like contacts, opportunities, relationships etc...and i added another sub-tab called analysis, which will open this BI report.

All this works perfectly fine, but the rerport shows all volumes bases on the 3 statuses (open/lost/won) and is not filtered on the current account. Can somebody please help on how to go about it?

I need the report to trim values and show only those related to opportunities of the current account, where i've the sub-tab opened. When i select another one, it should be showing values of the second one..etc.

In R13.19A OTBI direct database query has been disabled by default. To prevent reports generating system errors, BI Administrator can modify BI privileges to revert this change.

Content:

What is the Change?

Prior to R13.19A, BI Administrator has the privilege to create and run Direct Database Query in BI Answers. In R13.19A, this feature has been disabled by default. Specifically, two privileges that control direct database query access, namely ‘Edit Direct Database Analysis’ and ‘Execute Direct Database Analysis’, have been denied for authenticated users.

Reports created with ‘Direct Database Query’ option prior to R13.19A will receive a system error when executed in R13.19A. To prevent the system error, customers can revert the R13.19A privilege changes by granting BI Administrator privilege to both ‘Edit Direct Database Analysis and ‘Execute Direct Database Analysis’.

Please note: This change does not affect BI Publisher SQL reports created with BI Publisher Data Model or BI Answers reports created with Logical SQL.

How to revert the change?

BI Administrator can modify direct database analysis privileges in BI Administration -> Manage Privileges page. To grant BI Administrator access to direct database query, customers can remove ‘Authenticated User’ that has ‘Denied’ permission from the seeded privileges and add a new role of ‘BI Administrator Role’ with ‘Granted’ permission.

Direct database query is not a supported OTBI feature for building reports. Customers are encouraged to use BI Answers to create interactive analyses, use BI Publisher for fixed-format reports and use BI Cloud Connector (BICC) for data extraction. If customers have created OTBI reports with Direct Database Query option, Oracle development strongly recommends migrating those reports to use OTBI subject areas as Direct Database Query will be deprecated in OTBI in 12 months.

Please refer to attached document for more detailed information. If you have further questions, please contact Oracle Support.

Starting with Release 13.18.10, a brand-new OTBI Help landing page is available -> https://docs.oracle.com/en/cloud/saas/business-intelligence/index.html. From an OTBI 18.10 instance (or a later release), users can click on the ‘OTBI Help’ link in Answers and launch the OTBI Help landing page. This page is a quick launch pad to relevant OTBI help documents – subject area guide, data lineage, report list and OTBI product Help. Users can also book mark the OTBI Help landing page and launch it directly from a browser. The OTBI Help landing page will save users from having to go to different places to locate OTBI help.

The subject area guide is a new tool that gives users helpful information on how to use a subject area, related business questions, and security roles. The hyper-linked subject area guide replaces the subject area description spreadsheets that OTBI product management have published in Customer Connect.

We welcome your feedback on the new OTBI Help landing page and suggestions on improving OTBI help and usability.

Customer where there have been no activities in the last 30 days (or selected time period)

Customers for which no Opportunity has been raised in the last 30 days (or selected time period)

Customers without any SRs in last 30 days (or selected time period)

Product that hasn’t contributed to Revenue in last 30 days (or selected time period)

Assets that are expiring in next month (or selected time period) and which don’t have any associated Opportunity raised

Negative Reporting:

Since the dashboard here has all the reports that shows the data in a negative context, it is aptly named as negative reporting dashboard.
This dashboard is an example of how a negative report can be created with few examples.

Essentially, to create a negative report, following high level steps are to be performed:

Let’s take a simple case where we want to see all the Accounts without any Activities

Step 1: Get the list of all the accounts (A)
Step 2: Get list of the accounts with activities (B)
Step3: A – B will give us the list of all the Accounts without activities

Thus to create such a report, we need to use a SET operation (MINUS).

The Catalog file attached here has a dashboard that essentially uses the same principle above for each of the reports and it shows –

Customer without Activities:
Customers that do not have any associated activities for a given time period, so that the Sales Representatives can plan a meeting accordingly.

Customer without Opportunities:
Customers’ existing in the system that do not have any Opportunities created for the selected time period, so that Sales Rep can review these accounts for next actions

Customer without SRs :
Customers existing in the system who have not raised any SR for a given time period

Product without Revenue:
What are the Products that have not contributed to revenue for a selected time period

Expiring Assets without Opportunities:
What are the Assets that are expiring in a selected time period, which don’t have any related Opportunity created in the system