This document will continue to evolve as existing sections change and new information is added. All updates appear in the following table:
Date | Update Version | Notes |
---|---|---|
24 JAN 2019 | January Maintenance Pack for 18C | Revised January Maintenance Pack for 18C. |
29 NOV 2018 | Update 18C | Delivered new features in update 18C. |
26 OCT 2018 | November Quarterly Maintenance Pack for 18B | Delivered new features in November Quarterly Maintenance Pack for 18B. |
28 SEP 2018 | October Maintenance Pack for 18B | Delivered new features in October Maintenance Pack for 18B. |
31 AUG 2018 | September Maintenance Pack for 18B | Delivered new features in September Maintenance Pack for 18B. |
29 JUN 2018 | July Maintenance Pack for 18A | Delivered new features in July Maintenance Pack for 18A. |
January Maintenance Pack for 18C
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 |
---|---|---|
24 JAN 2019 | Synopsis Integration | Removed feature from January Maintenance Pack for 18C. |
21 DEC 2018 | 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.
Opt In Only = These features are made available for use via Opt In. No additional setup steps are required.
Opt In, Plus Additional Steps Required = To use these features you must first Opt In, then perform additional setup steps.
Steps Required (No Opt In) = Setup steps must be performed before these features can be used. For example, new or expanded BI subject areas need to first be incorporated into reports. Integration is required to utilize new web services.
New Features Delivered Ready to Use 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. |
New Features That Customer Must Take Action to Use (Delivered Disabled) 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 |
Customer Action: |
Customer Action: |
Customer Action: |
![]() |
Enhancements for Mobile Application
The consumer goods mobile application enables you to:
- Configure and enter product quantities for dynamic combo on a single page without having to drill down.
- Update the dynamic combo discount behavior to calculate the total quantity requirement based on indicated number of combos to purchase and enforce the quantity requirement as the exact quantity to purchase.
Steps to Enable
No steps are required to enable this feature.
Role Information
- Sales Representative
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 |
---|---|---|
29 NOV 2018 | 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.
Opt In Only = These features are made available for use via Opt In. No additional setup steps are required.
Opt In, Plus Additional Steps Required = To use these features you must first Opt In, then perform additional setup steps.
Steps Required (No Opt In) = Setup steps must be performed before these features can be used. For example, new or expanded BI subject areas need to first be incorporated into reports. Integration is required to utilize new web services.
New Features Delivered Ready to Use 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. |
New Features That Customer Must Take Action to Use (Delivered Disabled) 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 |
Customer Action: |
Customer Action: |
Customer Action: |
![]() |
Enhancements for Consumer Goods Mobile
You can now do the following with the consumer goods mobile application:
- Warn sales representatives about checking in or checking out outside the preset radius of the stores.
- Allow sales representatives to create ad-hoc call records.
- Filter records of custom tasks using the account context.
Steps to Enable
The following enhancements must be enabled:
- Warning sales representatives about checking in or checking out outside the preset radius of the stores.
- Filtering records of custom tasks using the account context.
A. To enable this enhancement, create the following profile options in Setup and Maintenance:
- __ORACO_ENABLE_STORE_CHECK_IN_GEOFENCING. Set its site level value to Y.
- __ORACO_STORE_CHECK_IN_RADIUS. Set its site level value to a desired distance in meters, for example, 200. The default value will be set to 100 meters if the profile option is not present or it's site level value has not been set.
B. To enable this enhancement:
- Create your target custom object for your custom task.
- Create a one-to-many relationship between your source object and target custom object. Your source object can be either Activity or Account.
- In the Detail view of Mobile Application Composer, add your target custom object as a subtab of your source object.
- Create a store visit task for your custom task with TaskCode as Activity + APIName or Organization + APIName, depending on your source object. For example, if APIName is ActProductDetailing_c,
- TaskCode = ActivityActProductDetailing_c, if your source object is Activity.
- TaskCode = OrganizationActProductDetailing_c, if your source object is Account.
5. Add the new store visit task to a store visit type and use it in your store visit appointments.
Role Information
- Sales Representative
- Sales Administrator
November Quarterly Maintenance Pack for 18B
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 |
---|---|---|
26 OCT 2018 | Created initial document. |
Oracle CX 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 retail execution 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.
Customers Upgrading from Release 12
If you're upgrading from Release 12 to Release 13, then you should review all of the release readiness content for Release 13 (update 17D) to learn about all of the features available in release 13.
Give Us Feedback
We welcome your comments and suggestions to improve the content. Please send us your feedback at SALESCLOUD-PRODEX_WW@ORACLE.COM.
Action Required to Enable Feature |
|||||
---|---|---|---|---|---|
Feature |
None (Automatically Available) |
Enable via Opt In UI Only |
Enable via Opt In UI Plus Additional Steps |
Not Enabled via Opt In UI but Setup Required |
Issue Service Request |
![]() |
The enhanced mobile receipt now includes the summary and details of all transactions from a store visit. It also includes the relevant financial information for an account.
Steps to Enable
As part of enhanced mobile receipt feature, you can optionally display legal verbiage and privacy policy on the mobile receipt as follows:
- Navigate to Setup and Maintenance and create the following profile options:
- __ORACO__CREDIT_LEGAL_CLAUSE_FOR_MOBILE_PRINTOUT to display the legal clauses for new credit line usage.
- __ORACO__CONTAINER_LEGAL_CLAUSE_FOR_MOBILE_PRINTOUT to display the legal clauses for outstanding container loan balance.
- __ORACO__E_DATA_INFO_CLAUSE_FOR_MOBILE_PRINTOUT to display the legal clauses for billing information.
- __ORACO__PRIVACY_POLICY to display the privacy policy.
- Set the value of these profile options to your desired legal verbiage.
Role Information
- Sales Representative
- Sales Administrator
October Maintenance Pack for 18B
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 |
---|---|---|
28 SEP 2018 | Created initial document. |
Oracle CX 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 retail execution 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.
Customers Upgrading from Release 12
If you're upgrading from Release 12 to Release 13, then you should review all of the release readiness content for Release 13 (update 17D) to learn about all of the features available in release 13.
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.
Opt In Only = These features are made available for use via Opt In. No additional setup steps are required.
Opt In, Plus Additional Steps Required = To use these features you must first Opt In, then perform additional setup steps.
Steps Required (No Opt In) = Setup steps must be performed before these features can be used. For example, new or expanded BI subject areas need to first be incorporated into reports. Integration is required to utilize new web services.
New Features Delivered Ready to Use 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. |
New Features That Customer Must Take Action to Use (Delivered Disabled) 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 |
Customer Action: |
Customer Action: |
Customer Action: |
![]() |
Enhancements for Retail Execution Mobile
The following enhancements were included in this Retail Execution Mobile application update:
- Set and enforce minimum order quantity and amount. Minimum order quantity and amount can be set at both account and route level. When indicated, the account level settings take precedence over the route level settings.
- Prevent sales representatives from starting the route if there are items in the queue that are pending synchronization. This behavior can be enabled or disabled through a profile option.
- Prevent sales representatives from finishing the route if there are incomplete or unexcused store visits. In case the store visit is incomplete, the sales representative must provide a reason.
- Select from authorized bank accounts while making payments using check. Bank account information need not be entered manually by the user.
- Indicate and enforce account-level authorization for allowing proof-of-purchase and coupon payments by the account.
- Make My Inventory page read-only for sales representatives. This behavior can be enabled or disabled through a profile option.
Steps to Enable
- In Application Composer, navigate to the Account object in Standard Objects.
- Add Apply Account Order Minimums, Minimum Order Quantity, Minimum Order Amount, Proof of Purchase Payment Authorized, and Coupon Payment Authorized fields to all Detail layouts.
- Add field security validations for the above-mentioned fields. Refer to the examples in the Adding Field Validation section of the Consumer Goods Implementation Guide.
- Navigate to the Route object in Custom Objects.
- Add Minimum Order Quantity and Minimum Order Amount fields to all Detail layouts.
- Add field security validations for the above-mentioned fields. Refer to the examples in the Adding Field Validation section of the Consumer Goods Implementation Guide.
- Navigate to the Bank Account object in Custom Objects.
- Duplicate and activate all layouts in the order given for all layouts in Application Composer.
- Add Bank Account Number and Bank Name fields to the search layout.
- Navigate to the Payment Line object in Custom Objects.
- Add Bank Account Number DCL field to all layouts.
- Exit Application Composer.
- In Setup and Maintenance, create a new profile option __ORACO__SYNC_BEFORE_START_ROUTE. Set its site level value to Y.
- Create a new profile option __ORACO__ENABLE_REP_FULL_ACCESS_ON_ROUTE_INVENTORY. Set its site level value to N.
Role Information
- Sales Representative
- Sales Administrator
- Sales Manager
- Account Manager
September Maintenance Pack for 18B
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 |
---|---|---|
31 AUG 2018 | Created initial document. |
Oracle CX 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 retail execution 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.
Customers Upgrading from Release 12
If you're upgrading from Release 12 to Release 13, then you should review all of the release readiness content for Release 13 (update 17D) to learn about all of the features available in release 13.
Give Us Feedback
We welcome your comments and suggestions to improve the content. Please send us your feedback at SALESCLOUD-PRODEX_WW@ORACLE.COM.
Action Required to Enable Feature |
|||||
---|---|---|---|---|---|
Feature |
None (Automatically Available) |
Enable via Opt In UI Only |
Enable via Opt In UI Plus Additional Steps |
Not Enabled via Opt In UI but Setup Required |
Issue Service Request |
![]() |
Sales representatives must complete all the tasks or provide a reason for not completing the tasks before checking out of the store visit appointment. Sales administrators and sales managers can mark certain store visit tasks as mandatory for a store visit type or a store visit appointment in the web application.
Steps to Enable
- In Application Composer, navigate to the Store Visit Type object in Custom Objects.
- Duplicate and add the following Detail layouts in the given order:
- ORACO Duplicate Layout for any roles.
- ORACO Admin and Manager Layout for the sales administrator custom and sales manager custom roles.
- ORACO Sales Rep Layout for the sales representative custom role.
- Activate the new layouts.
- Navigate to the Activity object in Standard Objects.
- Duplicate the DSD Sales Admin and Manager Before Check In Layout for the Detail Layout for the sales administrator custom and sales manager custom roles. Set the expression as if(__ORACO__VisitStatusFCL_c=='ORA_ACO_VISIT_STATUS_NSTARTED'){return true}else{return false}
- Add the new layout after the DSD Before Check In Layout and activate it.
- Add the Mandatory, Reason, and Completed fields to all the existing Detail layouts.
- Exit Application Composer.
- In Setup and Maintenance, create a new profile option __ORACO__MANDATORY_TASK. Set its site level value to Y, if mandatory tasks must be completed or a reason must be provided for not completing them. Otherwise, set its site level value to N.
Role Information
- Sales Administrator
- Sales Manager
- Sales Representative
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 |
---|---|---|
29 JUN 2018 | Created initial document. |
Oracle CX 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 retail execution 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 guide 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.
Customers Upgrading from Release 12
If you're upgrading from Release 12 to Release 13, then you should review all of the release readiness content for Release 13 (update 17D) to learn about all of the features available in release 13.
Give Us Feedback
We welcome your comments and suggestions to improve the content. Please send us your feedback at SALESCLOUD-PRODEX_WW@ORACLE.COM.
Action Required to Enable Feature |
|||||
---|---|---|---|---|---|
Feature |
None (Automatically Available) |
Enable via Opt In UI Only |
Enable via Opt In UI Plus Additional Steps |
Not Enabled via Opt In UI but Setup Required |
Issue Service Request |
![]() |
Limit Selling to the Specified Product Category of a Route
This feature allows you to optionally specify a product category for a route. The sales representative for the route views and sells products based on the specified product category.
Specifically, in the mobile application,
- The account assortment shows only products from the product category of the route.
- The account promotions show only promotions from the product category of the route.
- When adding products and active promotions to the shopping cart, only products and active promotions of the specified product category for the route can be added. This behavior also applies to priority group and shopping cart template.
Steps to Enable
- In Application Composer, navigate to the Route, Promotion Program, Promotion, and Assortment Line objects in Custom Objects.
- Edit the active Create and Detail layouts for each object.
- Add the Category field and save the layouts.
- Go to Common Application > Object Workflow.
- Create a new object workflow for the Product object and enter its name as Assortment Line Update Workflow.
- In Event Point and Condition, set event as When a record is updated. Set condition as
"if (isAttributeChanged('__ORACO__IneligibleForShip_c') || isAttributeChanged('Description')|| isAttributeChanged('EligibleToSellFlag')|| isAttributeChanged('DefaultUOM')|| isAttributeChanged('ProductType') || isAttributeChanged('Name') || isAttributeChanged('__ORACO__Category_c')) return true;"
- In Actions, click Groovy. Enter the following values for the fields:
- Name: setAssortmentLine
- Description: Propagates the product changes to assortment lines
- Method Name: __ORACO__setAssortmentLineFields
- Exit Application Composer.
- In Setup and Maintenance, create a new profile option __ORACO__OVERWRITE_CATEGORY_CHANGE and set it to Yes, if product category change needs to be propagated to assortment line. Otherwise, set it to No.
Role Information
- Sales Administrator
- Sales Representative
---

Copyright © 2018, 2019, Oracle and/or its affiliates. All rights reserved.
This document is provided for information purposes only, and the contents hereof are subject to change without notice.This document is not warranted to be error-free, nor subject to any other warranties or conditions, whether expressed orally or implied in law, including implied warranties and conditions of merchantability or fitness for a particular purpose. We specifically disclaim any liability with respect to this document, and no contractual obligations are formed either directly or indirectly by this document. This document may not be reproduced or transmitted in any form or by any means, electronic or mechanical, for any purpose, without our prior written permission.
Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners.
Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation.All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. AMD, Opteron, the AMD logo, and the AMD Opteron logo are trademarks or registered trademarks of Advanced Micro Devices. UNIX is a registered trademark of The Open Group.
