This document will continue to evolve as existing sections change and new information is added. All updates appear in the following table:
| Date | Feature | Notes |
|---|---|---|
| 16 APR 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:
Features Delivered Enabled
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. |
Action is Needed 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 |
|
||
Work with Distributor Modelling and Pricing
Manage distributors and their relationships with other accounts. You can identify an account as a distributor, map the account-distributor relationship, and create the relevant associations with price books and assortment lines.
Steps to Enable
- Duplicate all default layouts and enable them.
- If you plan to override the validation on uniqueness of your implementation (i.e. if you plan to manage duplicate assortment lines for distributors), in Setup and Maintenance, go to Manage Profile Options. Create a Profile Option for "__ORACO__DISABLE_ASSORT_LINE_UNIQUE_CHECK" with value = "Y".
- Set Role Security for object __ORACO__AccDistributorRel_c
Tips And Considerations
The option to disable the out-of-the-box validation on uniqueness is added to support you for adding your own custom validations in implementation.
Key Resources
Role Information
- Marketing Manager
- Sales Administrator
Uptake Segment in Mobile Sync Logic
Most objects included in sync follow direct data relationships to either route, account, or appointment. Your sync package includes contract templates and condition templates, though these two objects have no direct relationship to route, account, or appointment. To improve sync performance and optimize the data relevance in your mobile application, the contract templates and condition templates in your sync package are now automatically filtered based on the segment value of your route.
Steps to Enable
You don't need to do anything to enable this feature.
Key Resources
Role Information
- Sales Administrator
You can now benefit from the following enhancements:
- Contract history generation via row copy, enhancing the extensibility of these contract details.
- Assigned segment values for key objects assortment plan, shopping cart template, promotion program, and contract template now carry through to the child objects generated (assortment, shopping cart, promotion, contract) when publishing these key objects.
Steps to Enable
You don't need to do anything to enable this feature.
Key Resources
Role Information
- Sales Administrator
Schedule and run ESS jobs for only a set of accounts, routes, and other associated data. You can run ESS jobs with an input parameter by segment so that only the desired data is selected for the ESS job.
Segment commonly represents a business division or a sales market. Management of your data by the segments such as an individual division or market can bring a lot of operational efficiency.
Steps to Enable
You don't need to do anything to enable this feature.
Key Resources
Role Information
- Sales Administrator