For partners that build or integrate commercially available applications and service solutions with the Oracle Cloud Platform
For partners that provide implementation or managed services around Oracle Cloud Applications
Subject Areas used – IC Performance & Earning Summary
Who can use this report (Roles)? - Incentive Compensation Manager/Analyst/ Sales Rep
The report which gives detailed information on the allocation of targets at participant level and at Plan Component level by their performance measure.
ITD Target Vs ITD Attainment:
Bar visuals showing target allocations of participants at Interval level
PTD Target Vs PTD Attainment:
Another Bar visual showing allocations at period level.
A detailed with all the details is shown next to the visuals.
Compensation manager/Analyst would be interested in setting participants based on their performance in attainment by comparing over the periods.
Similarly, the participant would like to know about this targets and overall attainment achieved over the periods.
Note:
All the below dashboards, reports are made based on the Oracle standard diction on formatting and layouts
Users are allowed to download the .catlog file and make their own customizations.
Participant Transaction & Dispute History
Subject Areas used – IC Dispute Real Time
Who can use this report (Roles)? - Incentive Compensation Manager/ Sales Rep/ Analyst
With the help of new subject area introduced in Incentive compensation area, it is so easy that we can take a count of transactions and count of disputes that a participant is holding
Compensation manager and comp admin can take a decision based on their counts in the allocation of new compensation plans to them.
An analyst and participants also can keep a track of their disputes and dispute status.
No report was developed on these lines, the first report which gives detailed information on how many disputes that a participant facing by year and by period and also listing what justification given for the same.
Count of Disputes Vs Transactions:
A horizontally stacked bar chart showing the count of transactions and disputes by the participant.
You are allowed o chose the particular participant if you are specific.
A detailed report gives you complete information by year and participant wise.
Note:
All the below dashboards, reports are made based on the Oracle standard diction on formatting and layouts
Users are allowed to download the .catlog file and make their own customizations.
Subject Areas used – IC Credits Real Time
Who can use this report (Roles)? - Incentive Compensation Manager/ Sales VP/ Comp Plan Admin
Most desirable report for a Sales VP, Performance measure always takes a lead in business development.
A manager he himself wants to compare his performance among peers and checks out the outcome. It helps in corrections and taking advisable decisions.
Below report gives a peer-peer ranking among the managers based on their performance on making Transaction Amount.
Ranking has been given Year, Period wise. A compensation manager can himself compare his rank over the periods along with his peers rank.
Bubble Chart:
The below bubble chart gives a pictorial info on manager made transaction amount in that period and his rank. Bigger the bubble size (transaction amount) ranks first.
Detailed reports given next to the visuals show more info on his transaction items.
Note:
All the below dashboards, reports are made based on the Oracle standard diction on formatting and layouts
Users are allowed to download the .catlog file and make their own customizations.
Attainment Ranking & Summary
Subject Areas used – IC Performance & Earning Summary
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.
Transactions & Discounts by Year
Subject areas used - IC Transactions Real Time
Who can use this report? - Incentive Compensation Manager/ Sales VP/Analyst/ Sales Rep
Marginal Discount and Discount that actually given by participants are key indicators in gaining transaction amounts, some of the participants will more discounts than the margin set.
A compensation manager/comp admin will decide the participant's behavior and observe their targets based on the margin discounts.
A simple report which gives detailed information on how much is the transaction Quantity and discounts offered by each participant followed by the end result Transaction Amount.
Discount is set for some set of products, participants for their goals they will sell for more discounts than the original amount. Giving a report with all of such transactions by participant or period helps in rebalancing the earnings
The below bar visual shows how each participant makes a deal with discount and actual margin discount set for each item.
A detailed report gives you complete info including achieved transaction amount.
Note:
All the below dashboards, reports are made based on the Oracle standard diction on formatting and layouts
Users are allowed to download the .catlog file and make their own customizations.
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:
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.
REPORT WITH BOTH SALES AND IC ATTRIBUTES -
Final Dashboard - Entire Prototype built on Oracle Data visualization Desktop Tool.
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.
Hi,
We have implemented the Sales rep Kanban report to show the Sales stages for various opportuntines. For some of the users its displayed fine where as for some of the users the top section is missing.
Do we need any setup for this Kanban report to display correctly
Thanks,
Prakash
Hi,
We have implemented the Sales rep Kanban report to show the Sales stages for various opportuntines. For some of the users its displayed fine where as for some of the users the top section is missing.
Do we need any setup for this Kanban report to display correctly
Thanks,
Prakash
Sales Manager :
Sales Manager needs to view
owned by him or by his subordinates for selected time period.
Sales Representative :
Sales Representative needs to view
owned by him for selected time period.
Shows the data for Lead - Opportunity Conversion Report with details in tabular form and also the graphs that give my overview about the conversion, such as the channel contribution to closed deals that are owned by the logged in user or the subordinates reporting into him
Note : Use Time Dimension filters as necessary
Shows the Master Detail Report functionality displaying the Account and their Opportunity Details.
Sales Manager/Representative needs to view
for all Accounts,Activities and Opportunities that are owned by him or by his subordinates.
Note -
With the Master Detail functionality, the data in second table view i.e. list of Opportunities changes based on the Account name selected in the first table view. This makes it easier to see the data for different entities in the same report view.
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).
Sales mockup flow “Campaign-Lead-Opty-Order”, IC mockup flow “Transaction-Credit_earning-Payment”.
Joins established to build the prototype are SALES.PartyID = IC.PartyID and SALES.OrderID = IC.TransactionID.
Pointes to Note:
Entire data model and dashboard was completed by considering above joins.
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.