This document will continue to evolve as existing sections change and new information is added. All updates appear in the following table:
| Date | Product | Feature | Notes |
|---|---|---|---|
| 18 DEC 2020 | Created initial document. |
Oracle Customer Experience Cloud for Consumer Goods provides a comprehensive solution for managing retail execution and trade promotion processes. The retail execution management solution enables sales administrators and managers to set up and manage the product catalog, assortments, price books, routes, store visit appointments, store visit tasks, and other data required for retail execution processes. The consumer goods mobile application enables sales representatives to complete merchandising and direct store delivery tasks in the offline mode. With the trade promotion management solution, marketing and account managers can set up trade budgets and funds, create trade promotions, measure promotion performance, and settle claims and deductions.
This document outlines the information you need to know about new or improved functionality in this update, and describes any tasks you might need to perform for the update. Each section includes a brief description of the feature, the steps you need to take to enable or begin using the feature, any tips or considerations that you should keep in mind, and the resources available to help you.
Give Us Feedback
We welcome your comments and suggestions to improve the content. Please send us your feedback at SALESCLOUD-PRODEX_WW@ORACLE.COM.
Column Definitions:
Report = New or modified, Oracle-delivered, ready to run reports.
UI or Process-Based: Small Scale = These UI or process-based features are typically comprised of minor field, validation, or program changes. Therefore, the potential impact to users is minimal.
UI or Process-Based: Larger Scale* = These UI or process-based features have more complex designs. Therefore, the potential impact to users is higher.
Features Delivered Disabled = Action is needed BEFORE these features can be used by END USERS. These features are delivered disabled and you choose if and when to enable them. For example, a) new or expanded BI subject areas need to first be incorporated into reports, b) Integration is required to utilize new web services, or c) features must be assigned to user roles before they can be accessed.
| Ready for Use by End Users Reports plus Small Scale UI or Process-Based new features will have minimal user impact after an update. Therefore, customer acceptance testing should focus on the Larger Scale UI or Process-Based* new features. |
Customer Must Take Action before Use by End Users Not disruptive as action is required to make these features ready to use. As you selectively choose to leverage, you set your test and roll out timing. |
|||||
|---|---|---|---|---|---|---|
| Feature |
Report |
UI or |
UI or |
|
||
Support Contract Benefit Discount Calculation by Net Sales
You can use contract benefits to issue product discounts in terms of revenue percentage but the revenue is calculated within the application based only on calculations defined in the code. Support contract benefit discount calculation by net sales allows you to upload any revenue attainment value such as net or gross and makes the application use the revenue value that you provided as the basis for the discount calculation.
The business benefit of this feature is creating contracts with product benefits that are based on the net sales of a product allows account managers to account for discounts, returns, and inflation.
Steps to Enable
You don't need to do anything to enable this feature.
Key Resources
- Using Consumer Goods guide
Role Information
- Marketing Administrator
- Account Manager
Enhance Objective Tasks and the Associated Publish Logic
Objective tasks and the associated publish logic are enhanced in two ways:
- By publishing only those tasks that are appropriately indicated. Publishing only the appropriately indicated tasks results in retention of few tasks at objective level rather than publishing all of them to account level.
- By preventing deletion of tasks that are already published. Deleting tasks from an objective or contract that was published to accounts creates data inconsistencies. The administrator supposes that the task is deleted from consideration for the Sales field, but it remains and can be executed across accounts. This feature prevents deletion of published tasks. The administrator must modify the status or dates of tasks to obsolete them or request an update of all matching child tasks across accounts.
The business benefit of this feature is that it ensures that the right tasks are published and maintained at the account level provides clarity and directs the account manager efforts toward the correct in-store tasks.
Steps to Enable
You don't need to do anything to enable this feature.
Key Resources
- Using Consumer Goods guide
Role Information
- Marketing Administrator
- Account Manager