Update 21C

Revision History

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
1 OCT 2021	Sales Force Automation	Update Your LinkedIn Integration	Added feature in Update 21C.
27 AUG 2021	Sales Force Automation	Validate Contacts for Opportunity and Lead through Sales Insights	Updated document. Revised feature information.
27 AUG 2021	Intelligent Advisor	Configure First Day of Week for Calendar Controls	Added feature in Update 21C.
27 AUG 2021	Intelligent Advisor	Debug Logs for Deployments	Added feature in Update 21C.
27 AUG 2021	Intelligent Advisor	Refresh API Access Token	Added feature in Update 21C.
27 AUG 2021	Intelligent Advisor	Statistics REST API	Added feature in Update 21C.
27 AUG 2021	Intelligent Advisor	Test Decision Service Rules in a Browser	Added feature in Update 21C.
30 JULY 2021	Sales Assistant	Define Edit Layouts for Task, Appointment, and Call Report for Microsoft Teams	Updated feature information.
30 JULY 2021	Sales Assistant	Access Leads and Associated Object Relationships in Microsoft Teams via Oracle Sales Assistant	Updated feature information.
30 JULY 2021	CX Sales Mobile	View Analytics with Modern Visualizations	Added feature in Update 21C.
30 JULY 2021	REST APIs	Import Participants Using REST API	Updated feature information.
30 JULY 2021	Import Management	Import and Export Participants Using Import Management	Updated feature information.
30 JULY 2021	REST APIs	Capture Recent Items Using REST API	Updated feature information.
30 JULY 2021	Integrations	Enhance Employee to Person Party Synchronization	Updated feature information.
30 JULY 2021	Sales Analytics	Use Prebuilt OTBI Reports to Understand User Adoption	Updated feature information.
30 JULY 2021	Work Assignment	Enable High-Performance Processing for Access Group Rules	Updated feature information.
17 JUNE 2021			Created initial document.

Overview

This guide outlines the information you need to know about new or improved functionality in this update.

GIVE US FEEDBACK

We welcome your comments and suggestions to improve the content. Please send us your feedback at oracle_fusion_applications_help_ww_grp@oracle.com.

Update Tasks

This section gives you information to help you plan, deploy, and validate your update. We make frequent additions to this document, so don’t forget to check back and get the latest information before your update starts.

Use the following resources to prepare for, deploy, and validate your update:

• Read Prepare for your Quarterly Update (Doc ID 2445338.1) on My Oracle Support to learn how to prepare for and validate your quarterly update.

• Publish or delete any in-progress sandboxes. Read the Overview of Sandboxes topic in the Configuring and Extending Applications guide for more information.

• Review the latest Known Issues and Update Documents for this release (Doc ID 1603154.1) on My Oracle Support.

• Review Oracle CX Sales and B2B Service: Removed Features (Doc ID 2530879.1) on My Oracle Support.

• Review the IMPORTANT Actions and Considerations in this document, to see what additional actions you may need to take after your update.

Optional Uptake of New Features (Opt In)

Oracle Cloud Applications delivers new updates every quarter. This means every three months you'll receive new functionality to help you efficiently and effectively manage your business. Some features are delivered Enabled meaning they are immediately available to end users. Other features are delivered Disabled meaning you have to take action to make available. Features delivered Disabled can be activated for end users by stepping through the following instructions using the following privileges:

• Review Applications Offering (ASM_REVIEW_APPLICATIONS_OFFERINGS_PRIV)
• Configure Oracle Fusion Applications Offering (ASM_CONFIGURE_OFFERING_PRIV)

Here’s how you opt in to new features:

1. Click Navigator > My Enterprise > New Features.
2. On the Features Overview page, select your offering to review new features specific to it. Or, you can leave the default selection All Enabled Offerings to review new features for all offerings.
3. On the New Features tab, review the new features and check the opt-in status of the feature in the Enabled column. If a feature has already been enabled, you will see a check mark. Otherwise, you will see an icon to enable the feature.
4. Click the icon in the Enabled column and complete the steps to enable the feature.

For more information and detailed instructions on opting in to new features for your offering, see Offering Configuration.

OPT IN EXPIRATION

Occasionally, features delivered Disabled via Opt In may be enabled automatically in a future update. This is known as an Opt In Expiration. If your cloud service has any Opt In Expirations you will see a related tab in this document. Click on that tab to see when the feature was originally delivered Disabled, and when the Opt In will expire, potentially automatically enabling the feature. You can also click here to see features with Opt In Expirations across all Oracle Cloud Applications.

Feature Summary

Engagement

Customer Data Management

Enhance Employee to Person Party Synchronization

The Maintain Party and Location Current Record Information (MPLCRI) scheduled process has been enhanced. This scheduled process synchronizes a new worker record to a person party record, or synchronizes the changes made to an existing worker record into the person party record. Additional parameters are introduced to manage the execution mode. Select a subset of data for synchronization based on the filter provided.

The MPLCRI scheduled process now supports the update of the following list of attributes:

• Work Email
• Work Phone
• First Name
• Last Name
• Middle Name
• Person Title

The following HR person types are now supported to sync as person parties:

• Ex-Employee
• Employee
• Ex-Contingent Workers
• Contingent Workers
• Non Workers
• Pending Workers

The following parameters were added:

• Synchronization Type: Select the operation to be performed. The options are: Only synchronization HR worker records, De-normalize Parties, or perform both (when no option specified).
• Person Type: HR Person Types that are supported by this scheduled process. The values are restricted by the list of values. If nothing is specified, all are in scope.
• From Date: Starting date of the date range to recognize the persons to be considered for synchronization.
• To Date: End date of the date range to recognize the persons to be considered for synchronization.
• Person Number: External Key of the HR Person. Provide any text. No list of values are available.

This scheduled process synchronizes a new worker record or an existing worker record into a person party record.

Steps to Enable

You don't need to do anything to enable this feature.

Tips And Considerations

The profile option, Enable Current Active Worker Sync for MPLCRI Job (ORA_HZ_ENABLE_MPLCRI_ACTIVE_WORKER), is used to manage the execution of the batch job as restricted or unrestricted. In restricted mode, active workers like employee and contingent workers aren't synchronized. In unrestricted mode with the profile value set to Yes, all supported worker types, including active workers, are synchronized.

When you're using the scheduled process in unrestricted mode with the profile value set to Yes, you must ensure that the events are turned off using another profile option, HRC_DISABLE_HCM_EVENTS_PROCESSING, by setting the value to Y.  This setting avoids possible duplicates for active workers synchronized into person parties using the auto-sync process, which is event driven. 

Setting the HRC_DISABLE_HCM_EVENTS_PROCESSING to yes turns off all HCM events. This is very risky because this setting can break business flows that consume HCM events. So, ensure that this profile option is set to yes only during very short periods of time.

Key Resources

• See the "Sales and B2B Service Scheduled Processes" chapter in the Understanding Scheduled Processes guide.

Review the Effects of Attribute Survivorship on Updates

Use the Organization and Person Profile History pages to review which field updates were accepted or rejected based on the application of attribute survivorship logic. With this enhancement, each profile history entry lists the names of the attributes whose values changed during the update operation. The history also lists the names of the attributes whose values didn't change because the survivorship rules determined that the incumbent value was of higher quality than the new value. The enhanced Profile History page lets you easily differentiate between changes that were accepted per survivorship logic versus those changes that were accepted because survivorship was not configured for those attributes.

See Which Field Updates Were Accepted or Rejected

These enhancements to the Profile History page provide transparency and auditability for master records when survivorship rules have been applied to updates. The enhancements are useful for the testing and validation of survivorship-on-update processing logic.

Steps to Enable

You don't need to do anything to enable this feature.

Tips And Considerations

These enhanced Profile History pages show the effects of survivorship on updates made by both REST and Import Management interfaces.

Role Information

Any user who has access to the Organizations and Persons pages can use these enhancements. In particular, the enhancements were designed to support the duties of users with these job roles:

• Customer Data Steward
• Data Steward Manager
• Master Data Management Application Administrator

Make Historical Data Available to Attribute Survivorship Processing During Updates

Synchronize historical data with the attribute survivorship processing during update operation. This feature lets you build the attribute source change history for a newly configured attribute.

Synchronize Historical Data

This feature increases the reliability and accuracy of survivorship on update logic by making relevant attribute change history information available to the survivorship framework when new attributes are added to the source confidence setup.

Steps to Enable

To use this feature, follow these steps:

1. Click Navigator > My Enterprise > Setup and Maintenance work area.
2. Go to the Manage Source System Confidence task by selecting the offering as Customer Data Management and the functional area as Customer Hub.
3. Add new attributes to your source confidence configuration as dictated by your customer data management process.
4. After saving your new source confidence configurations, click the Synchronize button on the Manage Source System Confidence setup page.
5. Accept the default recommended synchronization time frame or specify your own.
6. Click the Submit button to launch the synchronization job.

Tips And Considerations

• The synchronization process is only needed when source confidence is configured for a new attribute the first time. For example, adding a third source system to an attribute that already has source confidence setup for two source systems doesn't require synchronization.
• The synchronization module analyzes your setup data and calculates the data window for synchronization based on when the source system was enabled. You can override this value based on personal knowledge of when a field started being used, or any other potential optimizations you may be aware of.
• Even if you choose not to synchronize the history of a newly added attribute, the attribute source change history will still be tracked going forward.

Key Resources

• See the "Duplicate Resolution Setup" chapter in the Implementing Customer Data Management for CX Sales and B2B Service guide.

Role Information

This feature is available to users with the Master Data Management Application Administrator role.

Reconfigure Address Cleansing Parameters Before Submitting an Address Cleansing Job

Fine-tune the address cleansing configuration parameters such as Minimum Verification Level and Minimum Verification Score prior to submitting an address cleansing job. The default configuration continues to be defined in the Setup and Maintenance task, Manage Address Cleansing Configurations, but this feature allows additional tuning of these parameters at each batch job level.

As a data steward, you can now reconfigure the address cleansing configuration parameters for a specific address cleansing job by overriding the address cleansing parameter settings for the application. As a data steward, you control the address cleansing batch job configuration because the configuration parameters can be tuned while creating a batch job. You can fine-tune your batch jobs without affecting other batch jobs that are submitted by other data stewards, or without changing the default configuration applicable for all batch jobs.

Steps to Enable

You don't need to do anything to enable this feature.

Key Resources

• See the "Cleanse Addresses" chapter in the Using Customer Data Management for CX Sales and B2B Service guide.

Use D&B Attribute Mapping for Account and Contact Batch Enrichment

Use Account and Contact Enrichment by Dun & Bradstreet (D&B) attribute mapping for batch enrichment of account and contact data in Customer Data Management. Also, you can now map predefined Account and Contact Enrichment by D&B attributes to all attributes available from Dun & Bradstreet.

If you're a user of Account and Contact Enrichment by D&B who uses batch enrichment, you can now leverage custom attribute mappings and map key attributes, such as competitor, using this new mapping.

Steps to Enable

You don't need to do anything to enable this feature.

Key Resources

See this content:

• "Configure Oracle DaaS and Oracle DataFox for Data Enrichment" chapter in the Implementing Customer Data Management for CX Sales and B2B Service guide
• "Enrich Data" chapter in the Using Customer Data Management for CX Sales and B2B Service guide.

Workspace and Adaptive Search

Publish a Limited Set of Objects in Adaptive Search

You can now choose to publish only Workspace objects whose configuration has changed. This avoids having to perform a full publish every time a configuration change is done, thus saving time.

This feature significantly reduced the publish time when changing the Adaptive Search configuration or when adding new objects to your Workspace.

Steps to Enable

This feature is disabled by default. To enable this feature: 

1. Sign in as a user with an administrator or setup role. 
2. Go to the Configure Adaptive Search setup task. 
3. Click the Parameters tab. 
4. Click Edit to enable edit mode on the page. 
5. Update the value of  Enable Partial Publish to Y.
6. Click Save.

Key Resources

• See the "Adaptive Search and Workspace" chapter in the Implementing Sales guide.

Role Information

• Sales Administrator

Enable Create and Export Buttons for Objects and Fiscal Year Date Filters in Workspace

Administrators can add or remove Create and Export buttons for every object enabled in Workspace. In addition, users can filter their records by fiscal year when searching records. These additional features let administrators manage Workspace objects more efficiently and give users additional flexibility when viewing records using date filters.

This feature improves configurability for Create and Export at an object level. It also provides an additional option of filtering by fiscal year on date filters in Workspace.

Steps to Enable

You don't need to do anything to enable this feature.

Key Resources

See this content:

• "Adaptive Search and Workspace" chapter in the Implementing Sales guide
• "Workspace" chapter in the Using Sales guide

Role Information

• Sales Administrator

Sales Force Automation

Leads and Opportunities

Validate Contacts for Opportunity and Lead through Sales Insights

You can improve your sales effectiveness and gain productivity by receiving key data insights about contacts for opportunities and leads. Using data analytics and mining, the Sales Insights feature validates whether contacts associated with an opportunity or lead are sufficient and accurate to help effectively close the deal.

Salespeople can improve the sales effectiveness and gain productivity by receiving key data insights on contacts in opportunities and leads.

Steps to Enable

Use the Opt In UI to enable this feature. For instructions, refer to the Optional Uptake of New Features section of this document.

Offering: Sales  No Longer Optional From: Update 22B

Contacts validation is a new feature under the Sales Insights feature released in Update 21B. The steps to enable are the same as those provided in the Implementing Sales guide for Sales Insights.

In addition to the instructions mentioned above, remember to schedule the sales insights processes with the recommended frequency. Details are in Tips and Considerations section.

Tips And Considerations

Before you opt-in to this feature, you must:

1. Navigate to My Enterprise > Enterprise.
2. Click the Manage Promotion Code link.
3. Click Enter Promotion Code. To get a promo code, read the post on Sales Insights Early Adopter access in the Sales forum on Oracle Customer Connect or raise a service request on My Oracle Support.
4. Enter the promotion code for this feature. A new entry called Sales Insights will be added.
5. Click Done.

After you're done with the above steps, then:

1. Navigate to Setup and Maintenance by clicking the Setup and Maintenance link under your user name in the global header.
2. Select the Sales Offering.
3. Click Change Feature Opt-In.
4. For the Sales root node, click the edit icon.
5. Find the feature, Sales Insights, and select the Enable check box.
6. Click Done.

Next, you must schedule Sales Insights data processes. The instructions to schedule the jobs are here: Submit Processes.

Once you have reviewed the steps, you can proceed with scheduling these Sales Insights processing jobs to run on a periodic basis:

Step	Job Name	Recommended Frequency
1	Generate Sales Insight Metrics	Once a week
2	Generate Sales Insight Facts	Once a week
3	Generate Sales Insight Facts Using Signals	Daily
4	Purge Redundant Sales Insight Facts	Once a month

Ensure that you have performed the steps to display Sales Insights section using Application Composer. See the section "Enable Sales Insights for Custom Layouts" here.

Key Resources

See this content:

• For information on using Sales Insights, see the "Sales Insights" chapter in the Using Sales guide.
• For setup information, see the "Sales Insights" chapter in the Implementing Sales guide.

Role Information

• Sales Administrator

View Verification Status of Email and Phone Numbers for Leads

Salespeople can get phone numbers and emails verified as soon as they enter them in the leads UI. This ensures that phone calls go through and that emails won't bounce. When a phone number or an email address is invalid for some reason, salespeople see a notification right below the entered value. They can also use the service to reverify the contact information periodically.

Salespeople don't need to spend their valuable time manually validating contact information of their prospects or for leads that don't have reliable phone or email address information. These contribute to an increased productivity of your sales team's time.

Steps to Enable

Use the Opt In UI to enable this feature. For instructions, refer to the Optional Uptake of New Features section of this document.

Offering: Sales

To enable the verification service:

1. Sign in as a sales administrator.

2. In Setup and Maintenance, navigate to:

   • Offering: Sales
   • Functional Area: Data Quality Verification Services
   • Quick Setup (under the Settings icon)

3. On the Configure Verification Services page, ensure that the Email and Phone check boxes are selected to enable email and phone verification.
4. Specify the number of days before users see the Valid verification status. The predefined value is 180 days.
5. Save your updates.

Tips And Considerations

The email and phone verification services are available to customers who have purchased a new license of the Oracle Address, Email, and Phone Verification service starting in 2021. Existing customers who purchased the Address Verification Cloud Service will be able to access the email and phone verification features by following the Opt In steps to enable the feature.

Key Resources

See this content:

• For Sales setup details, see the "Account Data Enrichment and Verification" chapter in the Getting Started with Your Sales Implementation guide.

• See the "Leads" chapters in the Using Sales and Implementing Sales guides.

• For a description on how salespeople can use the feature, see the "Phone and Email Verification" section in the "Accounts, Contacts, and Households" chapter in the Using Sales guide.

• See the Using Oracle Address, Email, and Phone Verification guide if you're a new customer using the Oracle Address, Email, and Phone Verification service.

Role Information

Access this feature using these predefined roles:

• Sales Administrator
• Sales VP
• Sales Manager
• Sales Representative

Update Your LinkedIn Integration

If your sales teams use LinkedIn Sales Navigator from your sales application, you must upgrade to the LinkedIn Version 2.1 partner application to continue using the feature in CX Sales and B2B Service. This upgrade is necessary because of changes in the web services in the LinkedIn Sales Navigator offering.

Once you have successfully upgraded to LinkedIn Version 2.1, salespeople can use LinkedIn Sales Navigator to:

• Identify prospects
• Communicate with accounts, contacts, or leads
• View sales-related updates

Steps to Enable

1. Sign in as the sales administrator or as a setup user.
2. Navigate to My Enterprise > Setup and Maintenance > Setup LinkedIn Integration.
3. Click Create. The LinkedIn Application screen appears with the additional Application ID and Application Key fields.
   • Note: Oracle has supplied the developer app credentials (Client ID and Client Secret) previously generated in LinkedIn.
4. Click OK.
5. If you're using the LinkedIn Sales Navigator region only on the Contacts and Leads pages, then no further action is needed.
6. If you're using the LinkedIn Sales Navigator mashup content for Accounts, then remove the mashup content. Enable the new LinkedIn Sales Navigator region in the Profile tab on the Account details page.

Tips And Considerations

You need a LinkedIn account and a LinkedIn Sales Navigator Team or Enterprise license to use LinkedIn Sales Navigator.

Key Resources

• For setup information, see the "LinkedIn Sales Navigator" chapter in the Implementing Sales guide.
• For information on how to use LinkedIn Sales Navigator, see the "LinkedIn Sales Navigator" chapter in the Using Sales guide.

Role Information

Sales Administrator

Work Assignment

Enable High-Performance Processing for Access Group Rules

Use the high-performance capabilities of Oracle's database-centric and optimized rule-based algorithm processing to significantly improve rule-based processing.

High-performance access group rule processing helps improve performance by enabling millions of records to be processed in minutes, not hours.

Steps to Enable

NOTE: High Performance Access Group Rule Processing is available only to an initial set of early adopters. If you're interested in becoming an early adopter, apply for access in the Early Adopter Beta access to High Performance Access Group Rule Processing post of the Customer Experience - Sales forum on Oracle Cloud Customer Connect.

Role Information

• Sales Administrator

Sales Catalog

Use Access Groups to Configure Data Security for Products, Product Groups, and Price Books

Easily give a set of users access to Products, Product Groups, and Price Books using access group security. Simply create an access group, assign members to the group, and then define rules to grant the group access to the Product, Product Group, or Price Book object's data. All group members receive the data access set for the group. If you add a user to multiple access groups, the user gets access to all the data records that each of the groups has access to.

With this setup, users can only see the products, product groups, and price books that they have access to. This is helpful when there are different groups of users who should have access to different products, product groups or price books.

Steps to Enable

By default, preconfigured system access group rules let users access all products, product groups, and price books. When you set up custom access groups, you deactivate and replace these default system access group rules with your own custom access group rules.

Here are the basic steps, using the All Products system access rule as an example:

1. First, deactivate the All Products system access group rule:
   1. Go to Tools > Sales and Service Access Management > Configure Groups > Object Sharing Rules > Object > Product.
   2. In the Rules section, notice that, for the All Products system rule, the Predefined and Active columns are checked.
   3. Drill down into the All Products system rule and uncheck the Active checkbox.
   4. Next, click Actions > Save and Close. 
   5. Finally, click Actions > Publish Rules. Keep refreshing the screen, using the circular arrow next to the Rules Last Published field, until you confirm the rule deactivation has been published. You can also drill into the All Products rule to confirm the Published Status field indicates Published.
2. Next, set up one or more custom access groups for the Product object by following Oracle's documented custom access group rules setup procedures. Select the Product object when doing so. See the Key Resources section, below, for the documentation.

To create custom access groups on product groups or price books, follow the same process as outlined above, substituting the correct values for product groups or price books.

• For product groups, the default system access group rule to deactivate is All Product Groups.
• For price books, the default system access group rule to deactivate is All Price Book Headers.

Tips And Considerations

When reporting on products with custom access groups in Oracle Transactional Business Intelligence (OTBI), access group security is reflected for dimensional browsing. However, when a report includes a field from a fact table, the fact security takes precedence over access groups. For Update 21C, custom access group security on product groups is not reflected in OTBI reporting. 

Key Resources

See this content:

• "Access Groups" chapter in the Securing CX Sales and B2B Service guide for general information about setting up access groups
• "Products" chapter in the Implementing Sales guide for product-specific access group setup

Role Information

• Sales Administrator

Sales Forecasting

Manage Renewal Revenue Lines in Forecasting

Manage renewal revenue lines within forecasting with a category indicator, which denotes whether the forecast item is a net new deal or a renewal. Additionally, the aggregate renewal forecast amount is shown in the header section. Renewal forecasting enables sales staff to review the renewal subscription forecast lines and the relevant forecast amount.

In order to protect your growth, analyzing your business for risk should be at the forefront of your renewal forecast process. Renewal Forecasting enables sales managers and sales staff to review the renewal subscription forecast.

Steps to Enable

Leverage Application Composer to expose and adjust page layout and attributes. To learn more about extending your application using Application Composer, visit Oracle Help Center > your apps service area of interest > Books > Configuration and Extension.

1. Create and activate a new sandbox.
2. Navigate to Configuration > Application Composer > Forecast Territory Details > Pages.
3. Create a duplicate of the Details Page Layout.
4. Select the Products tab in the duplicated layout. Click the Edit Subtab: Summary edit (pencil) icon and add the Renewal Forecast field.
5. Select the Item tab in the duplicated layout. Click the Edit Forecast Items Table edit (pencil) icon and add the Category field.
6. Save and close.

Key Resources

See this content:

• "Forecasting" chapter in the Implementing Sales guide
• "Forecasts" chapter in the Using Sales guide

Role Information

• Sales Representative
• Sales Manager
• Sales Administrator

Quotes and Orders

Create a Renewal Opportunity from a Renewal Quote

You can now allow your users to create a renewal opportunity manually or automatically from a renewal quote generated in Oracle Configure, Price, and Quote (Oracle CPQ). This capability helps salespeople track new and renewal opportunities separately. It also helps them apply appropriate sales tasks to close the deal.

Salespeople can create renewal opportunities from renewal quotes automatically without a sales representative having to manually create them when recurring revenues or subscriptions are nearing expiration.

Steps to Enable

1. You need to have an Oracle CPQ license and have it enabled.
2. You need to enable the Revenue Line sync feature delivered in Update 21B. See the "Set Up Reconciliation of Revenue Lines from Quote Lines" topic in the "Quotes and Orders" chapter in the Implementing Sales guide.
3. You need to enable the attribute, Opportunity Type, using Application Composer and add it to the Opportunity Header.
4. Also enable the attribute, Revenue Type Category, and add it to the Products section in the Opportunity details (edit) page. The Revenue Type Category will be set to Renew based on the information provided by the renewal Oracle CPQ quote.

Key Resources

• See the "Quotes and Orders" chapter in the Implementing Sales guide.

Role Information

• Sales Representatives and Sales Managers are the roles that benefit from this feature.
• All setup tasks need to be carried out by the Sales Administrator role.

Forecast Renewal Opportunities

With this update, we have added renewal revenue lines so that salespeople can forecast renewal opportunities. This complements the existing forecasting of new opportunities.

Your sales team can manage the pipeline forecasts for the renewal type of revenue lines separately from new opportunity revenue lines. Every opportunity revenue line can be specified as a renew type. The renew attribute is used in pipeline forecasting. The sales team can distinguish new and renew types of forecasts as separate categories for tracking and managing quota.

Steps to Enable

Leverage Application Composer to expose and adjust page layout and attributes. To learn more about extending your application using Application Composer, visit Oracle Help Center > your apps service area of interest > Books > Configuration and Extension.

1. You need to have an Oracle CPQ license and have it enabled.
2. You need to enable the Revenue Line sync feature delivered in Update 21B. See the "Set Up Reconciliation of Revenue Lines from Quote Lines" topic in the "Quotes and Orders" chapter in the Implementing Sales guide.
3. Expose the Revenue Type Category attribute on Opportunity Revenue Lines, using Application Composer.

Tips And Considerations

Also review the Forecast enhancement features available in Update 21C.

Key Resources

• See the "Quotes and Orders" chapter in the Implementing Sales guide.

Role Information

• Sales Administrator

Sales Assistant

Define Edit Layouts for Task, Appointment, and Call Report for Microsoft Teams

Use the Microsoft Teams Composer administrator tool to define Edit Layouts for task, appointment, and call report objects for Microsoft Teams users of Oracle Sales Assistant. When you create a standalone or follow-up task, follow-up appointment, or follow-up call report, Oracle Sales Assistant asks a set of questions based on the edit layouts defined. For example, Oracle Sales Assistant asks questions for fields on a layout that are required and don't have a default value. You also can define custom dynamic layouts based on roles and/or regions.

NOTE: Oracle Sales Assistant is available only to an initial set of early adopters. If you're interested in becoming an early adopter, apply for access on the Sales Assistant forum on Oracle Cloud Customer Connect.

This feature lets you customize the edit layouts for tasks, appointments, and call reports, so that you can add mandatory fields that prompt for a value during conversational create using the Oracle Sales Assistant in Microsoft Teams.

Steps to Enable

You don't need to do anything to enable this feature.

Key Resources

• See the "Sales Assistant" chapters in the Using Sales guide and in the Implementing Sales guide.

Role Information

• Sales Administrator
• Sales Representative

Access Leads and Associated Object Relationships in Microsoft Teams via Oracle Sales Assistant

Salespeople can now conversationally view a lead and its related objects, as well as its child objects in Microsoft Teams using Oracle Sales Assistant. Users can also add a note to a lead. Using the Microsoft Teams Composer administrator tool, you can modify the list and summary views of your Lead object to suit your business requirements.

NOTE: Oracle Sales Assistant is available only to an initial set of early adopters. If you're interested in becoming an early adopter, apply for access on the Sales Assistant forum on Oracle Cloud Customer Connect.

In additional to other supported objects, salespeople can now access their lead details in Microsoft Teams using Oracle Sales Assistant.

Steps to Enable

You don't need to do anything to enable this feature.

Key Resources

• See the "Sales Assistant" chapter in the Using Sales guide.

Role Information

• Sales Administrator
• Sales Representative

Intelligent Advisor

Intelligent Advisor Connector Performance Enhancement for Service Request and Activity

The Intelligent Advisor connector has an enhanced performance option when mapping to Service Request and Activity objects.

Enabling this feature may improve speed when loading and saving interview data.

Steps to Enable

Use the Opt In UI to enable this feature. For instructions, refer to the Optional Uptake of New Features section of this document.

Offering: Sales

You may need to change existing mappings in Policy Modeling after enabling this feature in your site profile options.

Intelligent Advisor Connector Performance Enhancement for Lead, Household, Account, Partner, Deals, Enrolment, Case and Customer Profile

The Intelligent Advisor connector has an enhanced performance option when mapping to the Lead, Household, Account, Partner, Deals, Enrolment, Case and Customer Profile objects.

Enabling this feature may improve speed when loading and saving interview data.

Steps to Enable

Use the Opt In UI to enable this feature. For instructions, refer to the Optional Uptake of New Features section of this document.

Offering: Sales

You may need to change existing mappings in Policy Modeling after enabling this feature in your site profile options.

Tips And Considerations

You may need to change existing mappings in Policy Modeling after enabling this feature in your site profile options.

Configure First Day of Week for Calendar Controls

Interview designers can now choose the start day of the week for calendar controls (by default it is Sunday).

Changing the start date of the week for calendar controls allows interview designers to match user expectations and existing websites.

Steps to Enable

You don't need to do anything to enable this feature.

Tips And Considerations

This feature is only available for Latest Version interviews. It is also available for calendar controls using the getCalendarWeekStart() property on the control object for an interview extension.

Key Resources

• Change the display of calendars

Role Information

• Interview designers

Debug Logs for Deployments

Debug logging can be enabled by a Manager in Intelligent Advisor Hub to provide detailed information about what is happening when data is run through an interview. Debug logs are captured for interview sessions created by Web Determinations interviews, Determinations Server interview service, and the Chat API.

These logs can be used by customers to help them resolve their own issues, and by support staff to help them replicate customer issues. Deployment session debug logging is available through the Intelligent Advisor Hub user interface, as well as by using the Deployments REST API.

Steps to Enable

You don't need to do anything to enable this feature.

Tips And Considerations

Debug logging may have security implications and have a significant impact on performance. Debug events are recorded user and system events, significantly increasing the amount of data collected and stored.

Key Resources

• Enable debug logging
• View the debug log for a deployment
• Managing deployments (REST API)

Role Information

• Managers

Refresh API Access Token

By default, OAuth2 access tokens used to authenticate and authorize calls to the Intelligent Advisor REST API expire after 30 minutes of inactivity. Once an access token expires, it needs to be refreshed. An API client can now request a long term (refresh) token to use when their access token expires.

This enables the API client to continue to access the Intelligent Advisor REST services without needing to supply user credentials.

Steps to Enable

You don't need to do anything to enable this feature.

Tips And Considerations

Requests must be:

• sent using HTTP POST with the URI https://<site>/opa-hub/api/{version}/auth where {version} is 12.2.23 or later.
• made with grant_type=offline_access. The OAuth API will then return two tokens: an access_token and a refresh_token.

Key Resources

• Refresh an API access token

Role Information

• Developers

Statistics REST API

System integrators can now access Intelligent Advisor statistics through a REST API.

This enables the statistics to be shared without logging in through the Hub user interface.

Steps to Enable

You don't need to do anything to enable this feature.

Role Information

• System Integrators

Test Decision Service Rules in a Browser

While writing decision service rules, authors can now instantly switch to a Live view to add data objects and input values and see how these flow through the rule logic. 

This interactive experimentation can reduce the time spent troubleshooting before integration testing via the decision service API.

Steps to Enable

You don't need to do anything to enable this feature.

Key Resources

• Test rules

Role Information

• Authors

Optional Decision Service Inputs

Decision service authors can now mark input contract fields as not being required.

This feature enables input fields to either be omitted or passed as null.

Steps to Enable

You don't need to do anything to enable this feature.

Tips And Considerations

For a deployed project that contains decision service references, the decision service will be invoked as follows:

• If an input field is required and the policy model value is uncertain, then the decision service is not invoked and the decision service outputs are all presumed to be uncertain.

• If an input field is optional and the policy model value is uncertain, then the decision service will be invoked.

• If any of the input values are unknown, then all the outputs will be unknown.

Key Resources

Add inputs

Set the value for an input

Role Information

Decision service authors

Oracle Analytics Publisher

Interview authors can now use Oracle Analytics Publisher Desktop 5.5.0 (previously known as BI Publisher), for form creation and editing.

Analytics Publisher supports Office 365.

Steps to Enable

You don't need to do anything to enable this feature.

Tips And Considerations

Existing users will need to uninstall BI Publisher Desktop before installing Analytics Publisher Desktop.

Key Resources

Download Analytics Publisher

Role Information

Interview authors

Enterprise Contracts

Enable Start and End Date Update for Award Contracts

You can update the start and end date of an award contract to keep it in sync with the start and end date of an award.

This feature provides administrators with the flexibility to make updates to the contracts based on the revised approval or start dates.

Steps to Enable

You don't need to do anything to enable this feature.

Search by Amount in Search Contracts by Text

Along with other search filters available on the Search Contracts by Text page, you can also use the contract amount or currency to find a contract. When using contract amount or currency, you can use operators. For example, you can search between a minimum and maximum contract amount.

Search by Amount

Searching based on the contract amount offers additional criteria to find your contracts faster.

Steps to Enable

You don't need to do anything to enable this feature.

Tips And Considerations

When searching based on contract amount, always use the Amount field where you can take advantage of the operators. The application doesn't support the amount search using the Text field.

Key Resources

• See the "Create Customer Contracts" chapter in the Using Customer Contracts guide.

Share In Progress Contracts in Supplier Portal

When you're ready to have your suppliers review and respond to a contract that's in progress, you can share the contract from the Edit Contract page. You'll see a warning before the contract is shared externally.

Share Warning Message

Once shared, the supplier contacts who have access to the contract can view the contracts you have shared with them in Oracle Supplier Portal. They can search for these contracts using the Manage Contracts task.

Manage Contracts

The suppliers can download contract documents and upload their revisions. Documents that you have shared with your suppliers are listed as Internal Shared documents. Documents that your supplier uploads through the portal are listed as External Shared documents.

Download and Upload Contract Documents from the Supplier Portal

You can find the documents shared with suppliers or the documents shared with you on the Documents tab of the Edit Contract page.

Shared Documents from Edit Contract

This feature minimizes the steps you need to take outside the application and streamlines collaboration between you and your suppliers.

Steps to Enable

Use the Opt In UI to enable this feature. For instructions, refer to the Optional Uptake of New Features section of this document.

Offering: Enterprise Contracts

Sales for Microsoft 365

Enable Microsoft 365 Exchange Email Integration

We are introducing a new service for Microsoft 365: Exchange email integration with Sales. This integration lets you feed emails from Microsoft Exchange to Sales applications.

Exchange email integration lets clients use this service to compose and send emails from Microsoft Exchange.

Steps to Enable

In the Manage Microsoft 365 page, the administrator needs to provide this information before enabling the Email Integration Enabled check box:

• Application ID
• Application Key
• Email Integration Address
• Email Integration Keyword

Key Resources

• See the "Email Integration" section in the "Microsoft 365" chapter in the Implementing Sales guide.

Role Information

• Sales Administrator

CX Sales Mobile

Use Your Many-to-Many Relationship Setup When You Create Page Layouts

Add your many-to-many relationship intersection objects to your page layouts, so that you can display the intersection object fields along with the target object fields in the page layout.

The ability to add many-to-many relationship fields to CX Sales Mobile provides sales representatives with even more information when they're on the go.

Steps to Enable

Leverage Application Composer to expose and adjust page layout and attributes. To learn more about extending your application using Application Composer, visit Oracle Help Center > your apps service area of interest > Books > Configuration and Extension.

1. In Application Composer, click Mobile Application Setup.
2. Click on the Source object of the Many-to-Many relationship, such as the Opportunity object.
3. Edit or create a new page layout, and click + Add Child or Related at the bottom of the page layout.
4. Search for your intersection object and select it.
5. Add fields from the intersection object, or the Source object, in the page layout.

Add M:M Relationships to Mobile App

Tips And Considerations

• You can add the source object fields only in the page layout view. Editing the layout of the intersection object only allows adding fields from the intersection object.

• Use the edit layout of the source object to edit fields on the source object.

• Tapping the summary page layout on the mobile app navigates users to the source object summary page layout. The edit page layout only displays the details of the intersection object.

Key Resources

• For more information, see the "CX Sales Mobile" section in the "Mobile Applications" chapter in the Implementing Sales guide.

Role Information

• CRM Application Administrator
• Sales Administator

Enable Notifications for Sales Objects

Enable notifications to be triggered automatically when certain business events occur in the CX Sales Mobile app, or in the CX Sales web app. For example, you can set up a notification for a sales representative when they've been assigned a lead or task. You choose to have a notification pushed to the mobile device or have it viewed inside the app as in-app notification.

Enabling notifications means sales representative receive timely updates to key sales data, so that they can take action on the updates.

Steps to Enable

1. In the Setup and Maintenance work area, select the Change Feature Selection option in the Sales Foundation functional area.
2. Expand the Notifications feature and ensure that Mobile Notifications are enabled.
3. Navigate to Application Composer and click Mobile Application Setup.
4. Click Settings in the Application Features pane and expand the Notification Settings menu.
5. Ensure that the Enabled setting is on. This option only enables and disables the in-app notification, and is enabled by default.

Enable Notifications within Mobile App Composer

Enable notifications for business events:

1. Navigate to Application Composer and expand the Standard Objects menu.
2. Expand the relevant sales object, such as Account, and click Server Scripts.
3. Click the Triggers tab, and in the Object Triggers section, click Action > Add.
4. Add a before insert/update object trigger and enter the following Trigger Definition:

def map = new HashMap();adf.util.sendNotification(adf, map);

/* Condition when the notification is raised e.g. lead is assigned or task is assigned *//* Condition when the notification is raised e.g. lead is assigned or task is assigned

adf.util.sendNotification(adf, map);

Configure delivery channels and notifications recipients:

1. In Application Composer, expand the Common Setup menu.
2. Click Notification Preferences.
3. In the Object field, select your sales object, such as Account.
4. Click Add. Enter or select the following values:
   1. Enabled: Select Yes.
   2. Triggering Event: Select the trigger that you set up in the previous steps.
   3. Notification Name: Enter a value to identify the notification. For example, "Push notification for lead assignment".
   4. Description: Enter a value to describe the notification.
   5. Recipients: Select the Bell Notifications and Mobile Notifications for the relevant recipients.
5. Click Done.
6. Click the link in the Notification Text field for your trigger and enter the text that's displayed when the notification is triggered.
7. Click Publish.
8. Click Save in the Notification Preferences page.

 

Configure Notification Delivery Channel and Recipients

Tips And Considerations

• In-app notifications display the same set of notifications as the Sales web application. Since not all objects are enabled in CX Sales Mobile, you can only view object details from a notification for objects that are enabled in CX Sales Mobile.

• Be selective in which notifications are sent as push notifications to mobile devices, to ensure users are received push notifications only for key events. 

Key Resources

• See the "CX Sales Mobile" section in the "Mobile Applications" chapter in the Implementing Sales guide.

Role Information

• CRM Application Administrator
• Sales Administrator

View Quotes and Share Quote Proposals

View your quotes in CX Sales Mobile and stay updated on the quote status. You can find a quote easily using the fast search from the home page, or from within a quote list. You can view and send quote proposal documents to customers quickly from where you are, or share them with your team for feedback. Quote lists in the context of an account and opportunity help identify the active quote. Also, your opportunity revenue is updated from the active quote in Oracle Configure, Price, Quote (Oracle CPQ), making it easier for you to keep track of your current pipeline.

Review the quote status and view proposal document from anywhere using the mobile app. Easily share the proposal document from using standard sharing options, such as messaging and email.

Steps to Enable

Before enabling Quotes in the CX Sales Mobile application, ensure that the pre-requisite steps to enable the integration between Oracle Sales and CPQ Cloud are complete. Refer to the Integrating Oracle CX Sales with Oracle CPQ guide and the Quotes and Orders chapter in Implementing Sales guide.

After Oracle CPQ Cloud integration is setup, follow these steps to enable the Quotes feature in the CX Sales Mobile application:

1. Enable Quote lists in the Navigator to display the Quote and Orders saved searches setup in Workspace:

• Enter a sandbox and navigate to Application Composer > Mobile Application Setup. Select the 'CX Sales Mobile Composer' tab. 
• With the Application Features set to Home, scroll down in the mobile preview screen in the center pane and select the Quotes and Orders feature.
• In the Feature Details, toggle Show On Navigator to On. 

2. Enable Quotes as related records for Accounts and Opportunities:

    Quotes and Orders are enabled by default in the summary views of Accounts and Opportunities. To enable Quotes functionality for custom layouts created in previous releases:

• In Summary view of the Accounts feature, select the custom layout. In the mobile preview screen scroll down to select Add Child or Related entity
• On the mobile preview pane, scroll down and select Add Child or Related.
• From the list of options, select SalesOrders. 
• Repeat these steps for Summary view of Opportunities.

3. Save the changes and validate before publishing the sandbox

Key Resources

• See the "CX Sales Mobile" section in the "Mobile Applications" chapter in the Implementing Sales guide, 
• Also refer to the Integrating Oracle CX Sales with Oracle CPQ guide and the "Quotes and Orders" chapter in Implementing Sales guide

Role Information

• Sales Administrator

Add Dynamic Choice List Fields for Territories and Languages, and Look Up City, State, and Postal Code in Lead Address

Create dynamic choice list fields for territories and languages, and then add them to list, summary, or edit layouts for any standard or custom objects. In addition, you can look up address field values like city, state and postal code when you're creating or editing a lead. The address values that can be selected are dynamically constrained based on previous selections.

Additional capability to add dynamic choice lists for territories and languages

Steps to Enable

Leverage Application Composer to expose and adjust page layout and attributes. To learn more about extending your application using Application Composer, visit Oracle Help Center > your apps service area of interest > Books > Configuration and Extension.

To enable Sales Territory as a Dynamic Choice List, follow these steps: 

1. In Application Composer, navigate to Objects > Standard Objects > Contacts > Fields.
2. Click Create Custom Field. In the dialog window that pops up, click Choice List (Dynamic). Then click OK.

3. Enter the required fields, including Display Name and click Next. In the List Data Source section, select Related Object as Sales Territory.

The newly created Territory Dynamic Choice List is now available as a custom field:

4. In Application Composer, navigate to Common Setup > Mobile Application Setup. Click the CX Sales Mobile Composer tab.
5. In the mobile interface designer, scroll to the bottom and click Add Feature.
6. In the dialog box, select Sales Territories. Then click Next.

7. Pick a suitable icon from the list of icons. Then click Next.

8. Click OK.

9. Navigate to the Sales Territories Layout from the Application Features pane.

10. Select the layout where you want to add the newly created Dynamic Choice List as a field. In this case for example, clone the list layout and the edit/create layout.

11. Add the field that you created in steps 1 through 3. Sales Territory as a Dynamic Choice List is now enabled.

To enable Language Dynamic Choice Lists, follow these steps:

1. In Application Composer, navigate to Objects > Standard Objects > Contacts > Fields.
2. Click the Create Custom Field icon. In the dialog window that pops up, click Choice List (Dynamic). Then click OK.

3. Enter the required fields, including Display Name, and then click Next. In the List Data Source section, select the Related Object as LanguagePVO.

The newly created Dynamic Choice List is now available as a custom field. You can now add the Dynamic Choice List as a field in any page layout.

The enhanced address lookup when creating a lead part of this feature doesn't require any setup.

Key Resources

• For more information, see the "CX Sales Mobile" section in the "Mobile Applications" chapter in the Implementing Sales guide.

Role Information

• Sales Administrator

Plan Your Sales Activities Using the Map

Assess and prioritize which customers to visit around your current location, by viewing your leads, opportunities, contacts, and accounts plotted on the map. You can also plan future appointments in a specific city, or near an address, with an easy location search that plots your sales records in your vicinity. Tap the pins in the map to view more information, easily create tracking activities and call reports, or get in touch with the contact, all while still in the map view. Directions to your points of interest are just a tap away.

See a demo.

Directions to your sales points of interest are just a tap away, as you can use the map in the app to view your leads, opportunities, contacts, and accounts nearest your vicinity.

Steps to Enable

You need to ensure Geocoding is setup and processes to populate the latitude and longitude of accounts, contacts and leads are scheduled. Refer to the "Set up the Maps Feature" topic in the CX Sales Mobile section of the Mobile Applications chapter in the Implementing Sales guide for details.

Key Resources

• For more information, see the "CX Sales Mobile" section of the "Mobile Applications" chapter in the Inplementing Sales guide.

Role Information

• Sales Representative

Sort List Pages and Related Record Lists Using Available Fields

Sort lists to your preferred order, using standard or custom fields that have been added to standard or custom object list pages. In addition, you can now sort a sales object's related records using available standard or custom fields. For example, you can re-sort the tasks for your account. The sort order is preserved in subsequent uses of the app, providing a very desirable personalized experience.

Sales representatives can configure the sort order of the list pages and the related record lists, so that they have a personalized experience of the app. This helps sales representatives work more effectively and quickly.

Steps to Enable

You don't need to do anything to enable this feature.

Tips And Considerations

The sort capability is available for the following parent/related objects:

Opportunity

Related objects: Appointments, Tasks, Call Reports, and Quotes

Account

Related objects: Appointments, Tasks, Call Reports, Contacts, Opportunity, Leads, Assets, Service Requests, and Quotes

Contact

Related objects: Appointments, Tasks, Call Reports, Opportunity, Leads, and Service Requests

Partner

Related objects: Appointments, Tasks, Call Reports, Opportunity, Leads, and Service Requests

Appointment

Related object: Call Reports

Task

Related object: Call Reports

Call Report

Related objects: Leads (Appointments, Tasks, Call Reports) and Assets (Appointments, Tasks, Call Reports, Opportunity, Leads)

Service Requests

Related objects: Appointments and Tasks

View Analytics with Modern Visualizations

Bring tailored insights into the state of your business wherever you are, with reports and analytics in CX Sales Mobile. Role-based layouts allow sales administrators to provide unique experiences to sales representatives, managers, and others. Enrich insights for your users with beautiful visualizations optimized for mobile displays, such as bar graphs, funnels, bubble charts, and more. Allow sales representatives to personalize report lists assigned to them. Search report lists in CX Sales Mobile, so that insights are just a keyword away. Easily access most recent versions of reports online or offline.

Increase revenue and reduce cost of sale by viewing insights into account health, pipeline performance, activity effectiveness, and more, directly from your mobile device.

CX Sales Mobile Analytics Demonstration

Steps to Enable

See the "Configure the Report Page Layouts" topic in the "Mobile Applications" chapter in the Implementing Sales guide.

See a demo of the CX Sales Mobile Report List Configuration.

Key Resources

• See the "Configure the Report Page Layouts" topic in the "Mobile Applications" chapter in the Implementing Sales guide.
• More information on implementing Oracle CX Sales Mobile
• Additional information on providing Analytics for sales users

Show Recently Viewed Records in Object Lists and Receive Confirmation Messages for Recently Created Records

View recent records without having to search the object list when you tap the Search icon. This allows sales representatives to create, edit, or open a sales record, and then quickly review and make updates to related records of Opportunities, Accounts, Partners, Contacts, Tasks, Call Reports, Assets, Leads, Service Requests, and custom objects.

Receive confirmation messages of records created, lead conversions in-progress, and completed lead conversions that will auto-dismiss. These messages provide timely feedback for actions taken. Sales representatives can tap the message to add to recently created items.

  

Improve the speed and ease by which sales representatives review and edit recent records.

Steps to Enable

You don't need to do anything to enable this feature.

Tips And Considerations

• To view recent records, tap the Search icon in an object list page. Recent records remain visible until you start typing a search within that object list.
• Messages for recently created items can be tapped to view/edit the record.
  • These are available for Opportunity, Account, Contact, Task, Appointment, Call Report, Asset, Sales Lead, Service Request, and custom objects.
  • Lead conversion messages do not allow tap to view.

Key Resources

For more information, see the "CX Sales Mobile" section of the "Mobile Applications" chapter in the Using Sales guide.

Role Information

• Sales Representative

Sales Performance Management

Incentive Compensation

Use a Predefined Function to Accumulate Results by a Different Interval

Use a predefined function to accumulate results of one measure or component using another dependent measure's or component's interval and reduce plan configuration effort.

The accumulate by any interval function accumulates any metric of a performance measure or plan component by any interval, irrespective of the measure’s or component's own interval. It accumulates the metrics from the cn_srp_per_form_metrics_all table and takes the following as inputs:

• Participant Plan ID (required)
• Plan Component ID (required)
• Formula ID (required)
• Interval Type (required): Could be any of the interval types defined for the business unit. For example: Quarter or Period.
• Period ID (required)
• Metric to be accumulated (optional): The metric of the measure of the component that you want to accumulate. For example, OUTPUT_ACHIEVED_PTD, INPUT_ACHIEVED_PTD or COMMISSION_PAID_PTD.

If you're accumulating a metric of a performance measure and don’t pass the final metric parameter, the default metric accumulated is OUTPUT_ACHIEVED_PTD. If you are accumulating a metric of a plan component and don’t pass the final metric parameter, the default metric accumulated is COMMISSION_PAID_PTD.

Use Case Example

A measure, M1, has an interval of Period. Another measure, M2, with an interval of Quarter, depends on M1, but needs the accumulated output value of M1 for the entire quarter. The call to the function is Accumulate By Any Interval (Participant Plan ID, Plan Component ID, in which measure M1 is present, Formula ID of measure M1, Quarter, Period ID are calculated).

Create Expression Page

This feature reduces plan configuration effort.

Steps to Enable

You don't need to do anything to enable this feature.

Key Resources

• See the "Expressions" chapter in the Using Incentive Compensation guide.

Role Information

• Incentive Compensation Plan Administrator

Add Descriptive Labels to Parts of an Expression

Add user-friendly labels to expression parts so that it's easy to understand what each part of an expression does. Easily troubleshoot expressions or create similar expressions by copying and modifying the expression, since you know exactly what each part of the expression is doing with the help of the labels. Add labels while creating the expression or edit them after you create the expression. View the formatted expression to best view the labels.

Add or Edit Label

Label in Formatted Expression

Troubleshoot expressions more easily. Since expressions are easy to understand now, copy existing expressions and modify them to use in new plans, thus reducing plan configuration effort and making plan maintenance easy.

Watch a Demo

Steps to Enable

You don't need to do anything to enable this feature.

Key Resources

• Watch the Add Descriptive Labels to Part of Expression Demo.
• See the "Expressions" chapter in the Using Incentive Compensation guide.

Role Information

• Incentive Compensation Plan Administrator

Create Generic Expressions Using Measure and Component Attributes

Use generically available attributes of a measure or plan component to make formula expressions more generic and reduce plan configuration effort. Build generic expressions without referring to specific components or measures when possible, making expressions reusable across components and measures. The Calculation process uses the attributes of the measure or component being calculated at runtime.

After you enable the attributes of the table CN_SRP_PER_FORM_METRICS in Configure Tables and Columns -- in addition to appearing under the User-Defined Objects section as attributes of specific measures and components -- they will also appear under the generic Attributes section in these groups:

• Under Plan Component group: Plan Component ID, Formula ID and Period ID
• Under Measure group: Formula ID and Period ID
• Under Participant group: Participant ID and Participant Plan ID

                      

Usage Example

Instead of creating an expression that refers to a specific plan component like this:

• Prorated Plan Component Participation (Plan component result.Green Servers Component.Participant Plan ID, Plan component result.Green Servers Component.Plan Component ID, Plan component result.Green Servers Component.Period ID)

Create a generic expression that doesn't refer to any specific plan component, like this:

• Prorated Plan Component Participation (Participant.Participant Plan ID, Plan Component.Plan Component ID, Plan Component.Period ID)

This feature makes expressions reusable and reduces plan configuration effort.

Watch a Demo

Steps to Enable

You don't need to do anything to enable this feature.

Key Resources

• Watch the Create Generic Expressions Using Measure and Component Attributes Demo.
• See the "Expressions" chapter in the Using Incentive Compensation guide.

Role Information

• Incentive Compensation Plan Administrator

Configure Extended Precision for Earning Types

Now you can easily set extended precision for earning types from the Manage Earning Types work area. Use the Extended Precision column to set the precision of earning types.

Adjust Extended Precision for Earning Types

Easily control extended precision values for different earning types.

Steps to Enable

You don't need to do anything to enable this feature.

Key Resources

• See the "Configuration for a Business Unit" chapter in the Implementing Incentive Compensation guide.

Role Information

• Compensation Administrator

Territory Management

Search Territories in Workspace using Additional Team Fields

Allow users to search for territories in Workspace using additional territory team fields, such as team member function, delegated administrator and forecasting delegate. In addition, Workspace users can search for territories using the source territory, or using these territory coverage fields: geography high, partner and include hierarchy.

This feature makes it easier to locate territories with a specific team member function. Territory Workspace continues to be especially useful for the sales operations team when resolving territory gaps and overlap issues.

Steps to Enable

You don't need to do anything to enable this feature.

Key Resources

• See the "Adaptive Search and Workspace" chapter in the Implementing Sales guide

Role Information

• Sales Manager
• Sales VP
• Sales Administrator

Import Account Inclusions using Original System References

Import account inclusion or exclusion territory coverage records using original system references. Additionally, the original system references information for account inclusion or exclusion records is available when exporting sales territory coverages. A new field, Original Reference, is available to use when exporting and importing sales territory coverage records.

This feature means an improvement for all customers who track and manage accounts using Original System references.

Steps to Enable

You don't need to do anything to enable this feature.

Tips And Considerations

When importing new customer inclusion or exclusion sales territory coverage records, you may provide the Account ID, Registry ID, or Original Reference value. The Registry ID field takes precedence. If the Registry ID value is not provided or is not valid, then the Original Reference value is used. 

Key Resources

• See the "Territories" chapter in the Implementing Sales guide.

Role Information

• Sales Manager
• Sales VP
• Sales Administrator

Sales Analytics

Support Reporting on Activities and Their Related Activities

With this new feature, you can report on the association between appointments or tasks, for example, as well as their related call reports or follow-up activities using the new CRM Activities with Related Activities subject area. Salespeople use the Activities pages to schedule appointments and create tasks. They can create follow-up tasks or appointments and associate them with existing appointments and tasks. In addition, call reports are used to record the outcome of sales activities. Call reports can be associated with scheduled appointments or can be ad-hoc call reports for unscheduled sales activities. The existing activities-related subject areas can be used to report individually on the different types of activities, like appointments, tasks, call reports, or follow-up activities.

Use the new CRM Activities with Related Activities subject area to report on the association between activities by adding attributes from both the Activity and Related Activity folders. You can use this subject area in combination with other activities related subject areas to report on activities that don't have associated activities, or to report on ad-hoc activities.

This feature will help customers to report on meeting activities (tasks and appointments) with call reports, call reports without a preliminary meeting activity (tasks and appointments) and meeting activities (tasks and appointments) without call reports.

Steps to Enable

Leverage new subject area(s) by adding to existing reports or using in new reports. For details about creating and editing reports, see the Creating and Administering Analytics and Reports book (available from the Oracle Help Center > your apps service area of interest > Books > Administration).

Key Resources

• See the Oracle CX Sales and B2B Service Subject Areas for Transactional Business Intelligence guide.

Enable Reporting on Quote Line Items

With this new feature, you can report on quotes and their associated quote line items using the new Sales CRM Quote Lines subject area. Sales representatives can create quotes from an opportunity as part of a deal cycle. The quote information, such as quote number, quote amount, status, and proposal documents are captured in the quotes and can be reported on, using the existing Sales CRM Quotes subject area. Quotes created from opportunities can have multiple quote line items that typically contain product information, quantities, discounts, list and net prices.

With this new subject area, you can report on the quotes associated with opportunities, the quote line items and the associated products. You can analyze useful metrics like recurring and non-recurring revenue, usage revenue and contract value at both quote and quote line item level, as well as number of quotes and number of quote line items. Products listed on quotes in multiple currencies can be converted to the corporate currency as part of Quote Line reporting due to currency rates stamped on the quote header.

Steps to Enable

Leverage new subject area(s) by adding to existing reports or using in new reports. For details about creating and editing reports, see the Creating and Administering Analytics and Reports book (available from the Oracle Help Center > your apps service area of interest > Books > Administration).

Key Resources

• See the Oracle CX Sales and B2B Service Subject Areas for Transactional Business Intelligence guide.

Use BI Cloud Connector View Objects for Incentive Compensation Transactions, Credits, Performance, and Goals Reporting

The new Business Intelligence (BI) Cloud Connector view objects let you extract data for:

• Transactions
• Transaction History
• Credits
• Credit History
• Goals
• Attainment
• Participant Details
• Participant Roles

You also can use this feature for high-volume data extraction and for extracting data for use in data warehouses or other tools.

Steps to Enable

You don't need to do anything to enable this feature.

Key Resources

• Getting Started with BICC
• BICC Database Lineage Mapping

New Design of Application Usage Insights

Application Usage Insights now has a new design to provide an even cleaner look, support different browser widths, and more closely align with Oracle's Redwood design. The new design supports table filtering and exporting of table data to CSV for later use.

More easily explore user adoption insights in Application Usage Insights. Get insights at a glance, filter tabular data, and export tabular data to CSV for use offline.

Steps to Enable

You don't need to do anything to enable this feature.

Key Resources

• See the "Application Adoption and Usage Reporting" chapter in the Creating and Administering Analytics guide.

Use Prebuilt OTBI Reports to Understand User Adoption

You can now use prebuilt reports to report on and understand user adoption. Available in Cloud Customer Connect, the reports can be downloaded and used in Oracle Transactional Business Intelligence (OTBI). The reports feature insights on logins, sessions, object usage, OTBI usage and performance, and click history. The reports allow easy access to OTBI's powerful reporting in the area of user adoption.

Explore the world of user adoption reporting in OTBI and easily leverage OBTI's existing user adoption subject areas. Use the reports as-is, or use them as a foundation to create more extensive insights in user adoption using OTBI.

Steps to Enable

You don't need to do anything to enable this feature.

Tips And Considerations

Download the .catalog file from the Cloud Customer Connect posting containing the report templates, and upload it into your OTBI instance. The Cloud Customer Connect posting also contains other useful information about the report samples, including content, subject areas they refer to, and more.

Key Resources

• In addition to the above references, see the "Application Adoption and Usage Reporting" chapter in the Creating and Administering Analytics guide.

Role Information

• Sales Administrator

B2B Service

Service Request Management

Evaluate the Resources who Follow Specific Service Requests

Use the Purge Obsolete Notification Followers scheduled process to evaluate whether a resource is still valid and enabled to follow specific service requests. This scheduled process removes invalid users from following the service request, so that the application does not get overloaded with stale data.

This feature helps your organization ensure that your data on notification followers is not stale.

Steps to Enable

To enable this feature, your administrator must enable the scheduled process "Purge Obsolete Notification Followers".

Key Resources

• For more information, see the "Configure Notifications" chapter in the Implementing B2B Service guide.

Role Information

• Service Administrator

Clean Up User Notification Personalization Data

Use the Purge Obsolete User Preferences scheduled process to clean up the user notification preferences data, in case the resource leaves your company or is no longer active.

This feature helps your organization ensure that your data on user notification preferences is not stale.

Steps to Enable

Make the feature accessible by assigning or updating privileges and/or job roles. Details are provided in the Role section below.

To enable this feature, your administrator must enable the scheduled process "Purge Obsolete User Preferences".

Key Resources

• For more information, see the "Configure Notifications" chapter in the Implementing B2B Service guide.

Role Information

• Service Administrator

View All and Select the Notifications to Un-Follow

View all the service requests you're currently following to receive notifications, in a single view, and un-follow the selected service requests that you are no longer interested in. To follow a service request, you need to navigate to that service request's details, and select the follow functionality from the Actions menu. All service requests that you follow for notifications are displayed on the Notifications Followed page. You access this page from Settings and Actions > Set Preferences > User Notification Preferences. On this page, you can select the service requests you want to un-follow.

This feature provides users with greater visibility into the service requests that they're following for notifications. Through this interface, users have the ability to un-follow those service requests that they're no longer interested in receiving notifications for.

Steps to Enable

You don't need to do anything to enable this feature.

Tips And Considerations

The follow functionality itself is controlled using a privilege. If you have the correct privilege to let you follow service requests for the purpose of receiving notifications, you will be able to see this management page.

Key Resources

• See the "Notifications" chapter in the Using B2B Service guide.

Role Information

• Customer Service Representative
• Customer Service Manager
• Other Sales and Service users

Optimize Sending Emails in Bulk

Using Groovy scripts or REST APIs, application developers can send outbound emails in bulk. This feature has enhancements to optimize the process of sending emails, and is supported for the SR messages and Outbound Message objects.

This feature is useful if your company needs to send large volumes of email in certain situations without affecting the normal email communication with your customers.

Steps to Enable

Review the REST service definition in the REST API guides, available from the Oracle Help Center > your apps service area of interest > REST API. If you're new to Oracle's REST services you may want to begin with the Quick Start section.

Tips And Considerations

• If you're using REST APIs to create outbound messages and want to send them out in batch, you must set the value of the DeliveryTypeCd attribute to ORA_SVC_BATCH.

• If you're using REST APIs to create outbound SR messages and want to send them out in batch, you must set the value of the ProcessingStatusCd attribute to ORA_SVC_BATCH_READY.

• Once you have created all the outbound messages or SR messages, you can then run the Send Outbound Messages scheduled process to send these messages in batch.

Key Resources

• See the “Email Channels” chapter in the Implementing B2B Service guide.

Role Information

• Application Developer

Define Data Security Policies Based on System Access Groups

You can use system access groups and predefined rules to support service request data security for your users. Every standard job role provided by Oracle has a corresponding system access group. And the predefined object-sharing rules assigned to each system access group provide the same access to service request data as provided by the standard job roles. The predefined object-sharing rules associated with each system access group are inactive by default.

System access groups give you an alternative way to manage a user's access to service request data. You can also create access extension rules to extend the access provided by the predefined rules to related objects.

Steps to Enable

System groups are active by default. But the predefined rules are inactive by default, so you must activate these rules before you can use them. The association between system groups and predefined rules is also disabled by default. So for each system group, you must also enable the predefined rules you want to apply to the group. Here are the steps:

1. Navigate to the Access Groups page in the Sales and Service Access Management work area.
2. From the List menu, select System Groups - Role to display all system access groups.
3. Click the name of a system access group whose rules you want to enable.
4. Click the Object Sharing Rules subtab. The predefined rules associated with the access group as part of the default security configuration have a Lock icon and the Predefined check box is selected.
5. To enable each of the rules associated with this system group as part of the default security configuration, select the Enable check box for each rule.
6. Click Save.
7. Activate each of the predefined rules you enabled:
   • In the Name field, click the rule name link.
   • On the Edit Object Sharing Rule page, click the Active check box.
   • From the Actions menu, click Save and Publish.
   • Click Save and Close.
8. On the Edit Access Group page, click Save and Close.
9. Run the Perform Object Sharing Rule Assignment Processing scheduled process to ensure that the access group sharing rules for each object are assigned properly.

Tips And Considerations

Every predefined rule was created to match an existing predefined SQL-based data security policy. So, if you're enabling predefined rules, you must end date the matching predefined SQL-based data security policy.

Here's what you need to do:

• Navigate to Security Console.

• Edit the role for which you're enabling predefined rules.

• The service request data security policies are given to duty roles such as Service Request Troubleshooter, Service Request Power User, and Service Request Contributor. So, you would edit the roles that you copied from these predefined roles.

• Go to Step 3, Data Security Policies, in the wizard.

• Find the matching SQL-based data security policy for your predefined rule.

• Edit the data security policy and set a past date as the end date for the data security policy.

NOTE: If you're using the predefined service duty roles such as Service Request Troubleshooter, you must copy those roles first because the predefined roles can't be edited.

Key Resources

• See the “Users and Security” chapter of the Implementing B2B Service guide.

Role Information

• Customer Relationship Management Application Administrator (if you're only setting up the predefined rules).
• IT Security Manager to manage predefined  job roles in Security Console.

Create and View Relationships between Service Requests

Create business-driven relationships between service requests and leverage these relationships to make easy updates across your service requests using the Object Links REST API resource.

Relationships enhance the efficiency of your agents and improve your service request resolution outcomes. In this release you can create and update relationships only using the REST API.

Steps to Enable

Review the REST service definition in the REST API guides, available from the Oracle Help Center > your apps service area of interest > REST API. If you're new to Oracle's REST services you may want to begin with the Quick Start section.

Key Resources

See the "Object Links" chapter of the REST API for CX Sales and B2B Service guide.

Role Information

• Any service agent can create and view relationships between service requests.

Override Coverage Time Zone on a Milestone Using the Service Request Time Zone

Set an override on the milestone configuration that calculates the milestone due date based on the time zone populated in the service request. If there is no time zone specified on the service request, the time zone specified in the coverage line is used. This feature provides a second option to override the coverage time zone, in addition to the existing option to override using the time zone of the resource to whom the SR is assigned.

Companies supporting customers across many time zones may use this feature to allow service request-specific information to dictate which time zone the due date is computed against. This makes it easier to assign milestone due dates to global resources or for global customers, and avoids setting up multiple coverages, calendars, and Groovy scripts to support this scenario.

Steps to Enable

1. In the Setup and Maintenance work area, go to the following:
   • Offering: Service
   • Functional Area: Service Entitlements
   • Task: Manage Service Milestone Configuration
2. Select the milestone you'd like to use the time zone override.
3. Set the Time Zone Override Source field to Service Request.

Key Resources

• See the "Service Entitlements" chapter in the Implementing B2B Service guide.

Role Information

• Service Administrator.

Set the Visibility of a Channel Type for Internal Conversations

You can determine whether a channel type must be visible when forwarding a service request to a user. The following channel types are visible by default when forwarding an SR to a user: Email, Slack, and any custom channel types that have been defined. You have the option to disable the channel types that you want to hide when forwarding an SR.

You can disable channel types that you don't want to show up when forwarding an SR. For example, if you don't use Slack in your organization, you can disable Slack for internal communications.

Steps to Enable

1. Navigate to Setup and Maintenance.
2. Select the Service offering and click the Service Request functional area.
3. Drill down on the Manage Service Request Channel Type Visibility task.
4. On the Manage Service Request Channel Type Visibility page, click Sync on the toolbar to bring in all the channel types defined in the application.
5. You can filter the Property Name to show only the channel types for the Enabled for Collaboration property.
6. To disable channel types that you don’t want to appear when forwarding an SR, set the value in the corresponding Property Value field to No.

Key Resources

• See the "Profile Options, Lookups, and Scheduled Processes for Service Requests" chapter in the Implementing B2B Service guide.

Role Information

• Customer Relationship Management Application Administrator

Default Color Changes for Service Request Severity Badges in the Fusion Service Request List Page

If you're using the default colors configured in the Manage Service Request Severities task, and if you have enabled coloring through the SVC_ENABLE_SEVERITY_COLOR_IN_SR profile option, you will now see updated colors on the Service Request List page. If you have previously modified the service request severity colors, those modifications will remain active.

New colors for the service request severities

Steps to Enable

You don't need to do anything to enable this feature.

Tips And Considerations

Use the Manage Service Request Severities task in Setup and Maintenance to make changes to the service request severity colors.

Key Resources

See the "Enable Productivity Tools" chapter in the Implementing B2B Service guide.

Role Information

Service Administrator

Digital Customer Service

Select Multiple Self-Service Registration Requests for Approval or Rejection

NOTE: Digital Customer Service is on a monthly release cadence. This feature was released in the April 2021 release.

Account managers can select multiple self-service registration requests and then approve or reject them simultaneously. This simplifies the management of self-service registration requests.

Approve or Reject Multiple Self-Service Registration Requests

Account managers can save time by selecting multiple self-service registration requests and either approving or rejecting all of them in a single click.

Steps to Enable

You don't need to do anything to enable this feature.

Tips And Considerations

If one or more of the selected registration requests are unable to be approved (or rejected), all registration requests in the selected group will return to the pending status and an error will be displayed.

Role Information

• This feature is available to users with the Customer Self-Service Account Administrator role.

Manage Product Assets

NOTE: Digital Customer Service is on a monthly release cadence. This feature was released in the April 2021 release.

Self-service users can manage their Installed Base Assets within the Digital Customer Service application. The following capabilities are provided in the Digital Customer Service reference implementation:

• View a list of product assets
• Register a product asset
• View the details of a product asset
• Update the product asset description
• See knowledge articles associated with a product asset
• See service requests logged against a product asset
• Create a new service request against a product asset from the product asset details page

There are also three new components available:

• Asset List - Component to show a list of installed base assets registered by the signed in user. Account managers can view a list of all assets of the account for which they are the account manager.

• Asset Data - Component to view and edit the details of an installed base asset.

• Asset Register - Component to enable a user to register an installed base asset.

This feature demonstrates best practices in implementing Installed Base Assets.

List of Registered Products

Registered Product Details

Register a Product

Asset owners and account managers can easily manage their assets, search for knowledge articles related to their assets, and create service requests against their assets.

Steps to Enable

The ODCS product picker will, by default, show all products flagged as ‘Enabled for Customer Self Service’. An additional property needs to be set to enable a product to be managed as an Installed Base Asset.

• Sign in to B2B Service as a user who has the privileges to manage product catalog items.
• Navigate to the Product Management work area and click Product Information Management.
• Click the Tasks icon, then click Manage Items.
• Search for the product item you want to configure.
• Click the desired product item in the table.
• Click the Specifications tab.
• In the Item Organization grouping, select Service.
• Click the Enable Asset Tracking drop down list and select Full Lifecycle.
• Click Save.

The provided Customer Self-Service Proxy User role includes the privileges to view Installed Base Assets. It doesn't include Update and Create Installed Base Asset privileges. These privileges must be added manually using the B2B Security Console. It is recommended you create a role with a name such as Create_Update_Assets.  Assign the following Functional Security Policies to this new role:

• Create Customer Assets by Service
• Update Customer Assets by Service

Then assign this new role to the Customer Self-Service Proxy User.

Tips And Considerations

Asset management can be disabled by deleting the user menu link.

Key Resources

• See the "Additional Feature Configuration" chapter in the Implementing Digital Customer Service guide. 

Role Information

• This feature allows Customer Self-Service Users to manage the assets that they own.
• Customer Self-Service Account Managers can manage all assets for the account for which they are the account manager.

Simplify Creating Developer Users and Locating Required URLs

Simplify creating Digital Customer Service developer users and locating required URLs. By entering a few key fields, you can automatically create a Digital Customer Service developer user, assign the required roles, and approve the user in a single step.

Create Developers for Digital Customer Service

You can also easily locate and copy Visual Builder and Visual Builder Studio URLs. In a test environment, you will see the Oracle Visual Builder and Oracle Visual Builder Studio URLs. In a production environment, you will only see the Oracle Visual Builder URL.

View Digital Customer Service URLs

These two new Functional Setup Manager Tasks make it easier for a developer to set up a Digital Customer Service application.

• Easily create Digital Customer Service developer users.
• Quickly find and copy the Digital Customer Service URLs you need.

Steps to Enable

You don't need to do anything to enable this feature.

Key Resources

• See the "Mandatory Setup Tasks" chapter in the Implementing Digital Customer Service guide.

Role Information

A developer will use these Functional Setup Manager Tasks.

View Your Technician's Location

NOTE: Digital Customer Service is on a monthly release cadence. This feature was released in the May 2021 release.

Self-service users can quickly locate their technician on the day of service so that they know when the technician will arrive at their site. Users can see the name of the assigned technician, the estimated arrival time and the location of the technician on a map.

Key benefits of this feature include a reduction in the number of contact center inquiries of the technician's current location, an improvement in your customer's experience, and cost savings due to fewer customer no-shows.

Steps to Enable

You don't need to do anything to enable this feature.

Tips And Considerations

The capability to view your technician's location only applies to Oracle Field Service work orders, not to general work orders. This capability is currently only available in the 21B reference implementation.

Role Information

This feature is available to all users with the Customer Self-Service User role.

Provide Users with View Your Technician's Location functionality using the Work Order Data Component

NOTE: Digital Customer Service is on a monthly release cadence. This feature was released in the June 2021 release.

The ability for self-service users to view their technician's location is now available in the Work Order Data component. Developers can add this component to their application so self-service users can quickly locate their technician and know when the technician will arrive at their site.

Key benefits of this feature include a reduction in calls to contact centers to determine a technicians's location, an improvement in customer experience, and cost savings due to fewer customer no-shows. Additionally, it's easy on your developers who simply drag and drop the component onto a page in their application.

Steps to Enable

You don't need to do anything to enable this feature.

Tips And Considerations

The Work Order Data Component is available for Digital Customer Service developers to use in their applications.

Key Resources

• See the "Components" chapter in the Implementing Digital Customer Service guide.

Role Information

Digital Customer Service Developers can add the Work Order Data component to their applications.

Knowledge Management

Set Scores for Concepts in the Dictionary

Search administrators can change the scores of concepts in the dictionary. You can assign scores of high, medium, and low to concepts to better manage search results for questions about those concepts. You can set the score for new concepts and change the score for existing concepts, and you can manage scores for predefined concepts, as well as those that you have added to the dictionary.

Managing the scores for both predefined and user-defined concepts provides added flexibility when tuning search results. This additional control enables you to ensure that the most important and relevant documents appear at the top of search results lists.

Steps to Enable

You don't need to do anything to enable this feature.

Tips And Considerations

• You should consider adding a concept to the dictionary only when:
  • There are one or more synonyms for the term you want to add.
  • The current search results for the term do not reflect its actual relevance to your users; either search is emphasizing or de-emphasizing the term too much.

• You should tune search sparingly, since it can cause significant changes in search results throughout the application.

• You can't use the concept score to tune individual search queries. Changing a concept's score will affect every search that uses that term (or its synonyms).

• If a term is not in the dictionary, its score will be automatically set according to its frequency in the application content. Very common terms will get low scores, while rare terms will get high scores. You usually don't need to add these terms to the dictionary.

Key Resources

• See the "Manage the Search Dictionary" chapter in the Administering Knowledge Management guide.

Role Information

Knowledge Administrator

Field Service Integration

Estimate, Review, and Post Charges for Work Orders in Service Logistics

Your agents can now estimate work order charges for customer approval before ordering parts and scheduling service. They can also review the customer's actual charges that were entered by the technician in the Debrief and post for billing.

Visibility to work order charges prior to performing service helps a service representative to properly set the customer's expectations. For completed work orders, access to the debrief details helps a service representative to respond to any follow up questions from the customer and post the charges for customer billing.

Steps to Enable

Use the Opt In UI to enable this feature. For instructions, refer to the Optional Uptake of New Features section of this document.

Offering: Service

Tips And Considerations

The Estimate, Review, and Post Charges for Work Orders functionality is designed only to work with the Oracle Service Logistics solution. This includes the integration with Oracle Supply Chain Management and work orders that are synchronized with Oracle Field Service.

Key Resources

See the following guides for implementing and using our Service Logistics solution:

• Chapter 24, "Set Up Service Work Orders", in Implementing B2B Service
• Integrating B2B Service with Field Service
• Oracle Field Service
• Service Logistics

Role Information

• The Sales Administrator role is required to opt-in to the Service Work Order Charges and Estimates feature in Setup and Maintenance.
• The Customer Service Representative role is required to edit a work order and access the Manage Charges and Estimates page through the Charges button on the work order.
• The Post Charges privilege must be granted to allow the posting of the charges for customer billing through the Complete Debrief button on the Manage Charges and Estimates page.

Import and Export and REST APIs

View Import and Export Jobs Submitted Only by You

Unless you're able to see import jobs as part of the management hierarchy, you can only view import and export jobs that you submitted. You can't view the import and export jobs and associated data files submitted by other users. But, this new security does honor the management reporting hierarchy, in that managers can view their directs' imports and exports.

This feature means enhanced data privacy for Sales users performing imports and exports within the same organization.

Steps to Enable

You don't need to do anything to enable this feature.

Tips And Considerations

You can configure this feature by setting the profile option, ORA_ZCA_IMPEXP_RESTRICT_USERACCESS.

Here's the navigation to set the profile option: Setup and Maintenance > Search > Manage Administrator Profile Values task > Search for the profile option code.

Key Resources

• See the "Get Started with Import" chapter in the Understanding Import and Export Management for CX Sales and B2B Service guide.

Assign Account Automatically During Import Management

Enable automatic territory-based assignment after sales accounts are imported. You can enable this feature by setting the profile option, ZCA_BATCH_ASSIGN_ON_BULK_IMPORT. If the profile option is disabled, then you must manually run a batch assignment or assign each sales account individually.

This feature increases efficiency because accounts are assigned automatically during both import management and high-volume import.

Steps to Enable

You don't need to do anything to enable this feature.

Key Resources

• See the "Import Your Data" chapter in the Understanding Import and Export Management for CX Sales and B2B Service guide.

Add New Fields in the Contact findDuplicates REST Response

View additional detail in the findDuplicates REST method’s response for the Contacts REST API. The response now displays JobTitle, concatenated contact name, and account unique name to help Oracle Digital Sales identify duplicates.

This enhancement makes it easier to display useful information about possible duplicates that have been identified through the REST findDuplicates action.

Steps to Enable

Review the REST service definition in the REST API guides, available from the Oracle Help Center > your apps service area of interest > REST API. If you're new to Oracle's REST services you may want to begin with the Quick Start section.

Tips And Considerations

This enhancement does not change the general behavior or functionality of the findDuplicates REST action.

Key Resources

• See "Contacts" section in the REST API for CX Sales and Service guide.

Role Information

All roles that can access the Contact REST resource can use this enhancement.

Apply Attribute Survivorship Logic to Customer Records Updated from REST API and Import Management

Maintain the quality of customer master records using attribute survivorship logic on customer records updated through REST APIs and Import Management. Survivorship on Update actions applies the exact same Source Confidence or Data Quality Rules-based survivorship configuration that's used during merges to updates, thereby assuring that lower quality attribute values from spoke systems do not overwrite existing master record values of higher quality. Survivorship on Update actions is utilized on a per-REST request and per-import job basis, and is available for the Account, Contact, Organization, and Person objects.

To use this feature with REST:

• Enable Survivorship on Update for REST updates by including the Enable-Survivorship custom property in the request header and set its value to Y.
• You can optionally set the REST-Framework-Version header property to 6 to receive validation details in the request response

To use this feature with Import Management:

• Enable Survivorship on Update for Import by selecting the Enable Survivorship Logic check box when submitting an import job.

Survivorship on Update preserves the quality of master customer records by assuring that spoke systems do not update master records with lower quality attribute values.

Steps to Enable

Review the REST service definition in the REST API guides, available from the Oracle Help Center > your apps service area of interest > REST API. If you're new to Oracle's REST services you may want to begin with the Quick Start section.

• Survivorship on Update is utilized on a per-REST-request and a per-import-job basis.

• Survivorship on Update implements the same Attribute Survivorship settings and configuration as the Data Quality Merge process, so the setup and enablement process is the same.
  1. Configure Source Systems with the Manage Trading Community Source Systems setup task.
  2. Configure Source System Confidence with the Manage Source System Confidence setup task.
  3. Configure Data Quality Rules with Application Composer.
  4. Configure CDM to use Attribute Survivorship with the Manage Customer Data Management Options setup task. Use:
     • Enable Attribute Source Tracking: Yes
     • Attribute Selection Type: Use Source Confidence
     • Add Groovy to Attribute Selection: Yes or No

Tips And Considerations

• Customer Data Management implementations with properly configured survivorship logic can use this feature.

• This feature is supported for the Account, Contact, Organization, and Person objects.

• The same survivorship logic configuration is shared between merge and update operations.

• To use this feature, no changes are required to the JSON body structure of REST requests or to the CSV structure of Import Management files. The exact same data integration assets can be used interchangeably with or without survivorship processing.

• Survivorship on Update is compatible with Source Confidence-based survivorship and Data Quality Rules (Groovy script) based survivorship
• The Enable Survivorship Logic check box for Import Management is only available for the objects that support survivorship on update and only when survivorship logic has been configured.

Key Resources

• See the "Import Your Data" section in the Understanding Import and Export Management for CX Sales and B2B Service guide.

Role Information

Any role that can update account, organization, contact, and person records via REST API and Import Management is able to use this feature.

Use Validation Status and Validation Date Fields in REST API Header

Use the Validation Status and Validation Date fields in the REST API headers for account, contact, and household resources. These fields indicate the last date when email and phone information was validated, as well as their validation status. You can also use these fields in Import and Export Management. Verification status and verification date were earlier made available to the Contact Point child object. These are now exposed at header levels with similar functionality. These attributes were added:

Account:

PhoneVerificationStatus

PhoneVerificationDate

FaxVerificationStatus

FaxVerificationDate

EmailVerificationStatus

EmailVerificationDate

Contact:

WorkPhoneVerificationStatus

WorkPhoneVerificationDate

MobileVerificationStatus

MobileVerificationDate

HomePhoneVerificationStatus

HomePhoneVerificationDate

EmailVerificationStatus

EmailVerificationDate

FaxVerificationStatus

FaxVerificationDate

Household:

PhoneVerificationStatus

PhoneVerificationDate

FaxVerificationStatus

FaxVerificationDate

REST consumers can use the verification information for primary contact data like phone and email at the header level, without need to drill down to the contact-point child level.

Steps to Enable

You don't need to do anything to enable this feature.

Key Resources

• See the "Accounts" and "Contacts" sections in the REST API for CX Sales and B2B Service guide.

Capture Recent Items Using REST API

The Recent Items REST API is designed to capture recently viewed, created, or updated records of selected objects in Sales. Recently accessed records appear in lists of values in the applications. For example, if a salesperson views, creates, or updates an account record (thus invoking the Recent Items REST API), that same account record is captured and shown as the first account in Account list of values in any of object's create or edit pages in the Sales applications.

The Recent Items REST API also increases the relevancy score for the account record as a result of the recent item operations.

The REST API allows other application clients, such as Oracle Visual Builder or Oracle JET platforms, to interact with objects to capture recently viewed, created, or updated records as a recent item -- and the same information is accessible in the same lists of values as in Sales.

The Recent Items REST API also interacts with use relevancy scoring and user context in Workspace. Smart Lists provide a list of records with recent items and relevancy scores. For more information on Smart Lists in Workspace, see the "Smart List" topics in the Implementing Sales guide.

Steps to Enable

Review the REST service definition in the REST API guides, available from the Oracle Help Center > your apps service area of interest > REST API. If you're new to Oracle's REST services you may want to begin with the Quick Start section.

Tips And Considerations

Here are the objects that support Recent Items REST API:

• Accounts
• Activities
• Assets
• Budget
• Campaigns
• Claim
• Contact
• Contract
• Deal Registration
• Enrollment
• Forecasting
• Households
• Opportunities
• Partner
• Partner Contact
• Partner Program
• Price Book
• Product
• Program Enrollment
• Promotion
• Sales Lead
• Sales Orde
• Service Request
• Subscription

Key Resources

See the "Recent Items" topic in the "Task" section in the REST API for CX Sales and B2B Service guide.

Role Information

The Recent Items REST API can be executed by any authenticated user.  

Capture User Favorites Using REST API

The User Favorites REST API captures favorite objects consistently among all objects, including the display of favorites in various user interface page areas like list views, saved searches, and Workspace. Listing favorites,  marking an object as a favorite, and umarking an existing object as a favorite are various use cases in user favorites.

You can use the new User Favorites REST API with the Sales Mobile and Microsoft 365 applications. The favorites information is captured in the data model used by the User Favorites REST API. An object marked as a favorite is indicated as the same record in Sales, Workspace lists, Sales Mobile and Microsoft 365.

Marking an object as a favorite also boosts the relevancy score of the object instance for that user. The records with higher relevancy scores are displayed toward the top in each object list in Workspace Smart Lists.

Salespeople can mark records as favorites to make it easier to find them. To mark a favorite record, salespeople:

• Click the favorite icon in the edit page of a record, such as an account or lead.
• In Workspace, click the favorite icon for the record in the list page of an object.

To view a list of all their favorites, salespeople can use the saved search and search for favorite objects in Workspace.

Steps to Enable

Review the REST service definition in the REST API guides, available from the Oracle Help Center > your apps service area of interest > REST API. If you're new to Oracle's REST services you may want to begin with the Quick Start section.

Tips And Considerations

Currently, salespeople can mark favorites for:

• Accounts and contacts
• Assets
• Activities
• Campaigns
• Contacts
• Deal registrations
• Leads
• Opportunities
• Partners and partner contacts
• Territories
• Custom objects

Favorites are also available in CX Sales Mobile and Microsoft 365.

Key Resources

• See the "Identify and Display the Data Your Users Want" topic in the REST API for CX Sales and B2B Service guide.

Role Information

The User Favorites REST API can be executed with any user that is authenticated.

Use Export Management for Territory Geographies Export

Use the Export Management framework to export territory geographies information.

This feature helps you export geography objects using the Export Management framework, rather than using file-based export.

Steps to Enable

You don't need to do anything to enable this feature.

Key Resources

• See the "Export Your Data" section in the Understanding Import and Export Management for CX Sales and B2B Service guide.

Use REST API to View Renewal Forecast Items

Use the ForecastItemDetail REST resource to view the category of each forecast item. Category denotes whether the line is a renewal or new deal. Renewal Forecasting enables sales staff and sales managers to review the renewal subscription forecast lines.

In order to protect your growth, analyzing your business for risk should be at the forefront of your renewal forecast process. Renewal forecasting lets sales managers and sales staff review the renewal subscription forecast for the forecast period.

Steps to Enable

Review the REST service definition in the REST API guides, available from the Oracle Help Center > your apps service area of interest > REST API. If you're new to Oracle's REST services you may want to begin with the Quick Start section.

Key Resources

• See the "Forecasts" section in the REST API for CX Sales and B2B Service guide.

Manage Project Entities using REST APIs

You can use REST services to do several tasks for project entities:

• Delete a bill plan
• Create and update contract line internal attributes
• Update bill plan and revenue plan translations
• Create, update, and delete bill plan descriptive flexfields
• Create, update, and delete revenue plan descriptive flexfields

This feature lets you integrate Subscription Management with external systems.

Steps to Enable

Review the REST service definition in the REST API guides, available from the Oracle Help Center > your apps service area of interest > REST API. If you're new to Oracle's REST services you may want to begin with the Quick Start section.

Key Resources

• See the sections for Subscriptions in the REST API for CX Sales and B2B Service guide.

Individualize Payment Plan Amounts Using REST API

Individualize payment plan amounts for participants using the Payment Plans REST API. Pass the individualized amount for each participant in the payload and easily assign each of them a different draw amount. For recoverable payment plans, individualize recovery start and end dates using this REST API.

Leverage REST APIs to individualize draw amounts and recovery dates programmatically, instead of doing it manually.

Steps to Enable

You don't need to do anything to enable this feature.

Key Resources

• See the "Payment Plans" section in the REST API for CX Sales and B2B Service guide.

Role Information

• Incentive Compensation Analyst
• Incentive Compensation Manager

View Participant Credit Details Using REST API

You can now use the Incentive Compensation Credit Details REST resource to view the credit details with the specified date range for a credit receiver. This REST resource can be used to provide credits visibility through additional channels, other than traditional reporting. This resource can be used for multiple use cases, including Oracle Visual Builder applications or integrating information with other programs.

You can use this REST API for a variety of use cases, including Oracle Digital Assistant chatbots, Oracle Visual Builder applications, or integrating information with other programs.

Steps to Enable

Review the REST service definition in the REST API guides, available from the Oracle Help Center > your apps service area of interest > REST API. If you're new to Oracle's REST services you may want to begin with the Quick Start section.

Key Resources

• See the "Incentive Compensation Credit Details" section in the REST API for CX Sales and B2B Service guide.

Role Information

• Incentive Compensation Participants
• Incentive Compensation Participant Managers

Mask Participant Information Using File Import

Use the Participant Detail file import to mask participant data. This feature lets you mask participant name, participant first name, participant last name, and person number for specified participants.

This feature lets you anonymize participant data and provides privacy compliance.

Steps to Enable

You don't need to do anything to enable this feature.

Tips And Considerations

• Data masking is permanent and can't be reverted.
• Masking only masks the data in Incentive Compensation tables.
• Masking doesn't appear in UI-based or subject-area-based reports.
• Fields need to be updated or masked in Customer Data Management in order for changes to appear in UI or subject-area reporting.

Key Resources

• See the "Participant Imports" chapter in the Using Incentive Compensation guide.

Role Information

• Compensation Administrator
• Compensation Manager
• Compensation Analyst

Import and Export Participants Using Import Management

You can now import and manage Incentive Compensation participants using Import Management.

This feature makes it easier to create and manage participants by providing bulk import of participants.

Steps to Enable

You don't need to do anything to enable this feature.

Tips And Considerations

When creating new participants, you can also initialize several attributes. 

These participant detail attributes can also be initialized when creating a new participant as part of a new participant import:

• Currency Code
• Country Code
• Cost Center

Key Resources

• See the "Participant Imports" chapter in the Using Incentive Compensation guide.
• See the "Import Your Data" chapter in the Understanding Import and Export Management for CX Sales and B2B Service guide.

Role Information

• Compensation Manager
• Compensation Analyst

Import Participants Using REST API

You can now import Incentive Compensation participants from REST API.

This feature gives you:

• Simplified participant creation and management
• Easy bulk importing of participants

Steps to Enable

Review the REST service definition in the REST API guides, available from the Oracle Help Center > your apps service area of interest > REST API. If you're new to Oracle's REST services you may want to begin with the Quick Start section.

Key Resources

• See the sections for Incentive Compensation in the REST API for CX Sales and B2B Service guide.

Role Information

• Compensation Manager
• Compensation Analyst

Use Audit Functionality on High-Volume Import of Custom Objects

You can now use auditing functionality while performing high-volume import of custom objects. In general, import follows the same audit history setting for each object. With this feature, you can override global audit history settings for a high-volume import job, using the import UI. The same capability is available in REST APIs, using an additional override parameter for the individual job.

This feature provides the capability to audit high-volume imports of your custom objects.

Steps to Enable

You don't need to do anything to enable this feature.

Tips And Considerations

Configure this feature by setting the profile, ORA_ZCA_IMPORT_ENABLE_AUDIT_HIGHVOLUME.

Here's the navigation to set the profile option: Setup and Maintenance > Search > Manage Administrator Profile Values > Search for the profile option code.

Key Resources

• See the "Overview of Import Management" chapter in the Understanding Import and Export Management for CX Sales and B2B Service guide.

Security

View Updates to Opportunities and Leads Secured Using Access Groups in Near Real-Time

You can access opportunity and lead records that are secured using access groups in near real-time. When an opportunity or lead is updated, when a user gets access to an opportunity or lead through a hybrid rule, or when an access extension rule provides a user with access to an object related to an opportunity or lead, the user can access the new records or objects immediately. You no longer have to run the Perform Object Sharing Rule Assignment Processing scheduled process before users get access to the relevant records.

With this feature, users have quicker access to opportunity and lead records.

Steps to Enable

To implement near real-time access for opportunity and lead records, you must enable the Signals functionality by setting the profile option, Common CRM Signals Active (ORA_ZCA_ENABLE_SIGNALS), to Yes. By default, Signals functionality is disabled. Here are the steps:

1. From Setup and Maintenance, navigate to the Manage Administrator Profile Values task.
2. Search for the profile option name, Common CRM Signals Active.
3. Change the default value of the profile option from to Yes.
4. Click Save and Close.

Key Resources

• See the "Access Groups" chapter in the Securing CX Sales and B2B Service guide.

Role Information

• IT Security Manager 
• Sales Administrator

View Access Group Information Using Access Explorer

Use the Access Explorer to view the data access users receive from their access group membership as well as from the roles they are assigned.

Integrated support for access groups in Access Explorer lets you easily troubleshoot user access issues.

Steps to Enable

You don't need to do anything to enable this feature.

Key Resources

• See the "Access Groups" chapter in the Securing CX Sales and B2B Service guide.

Role Information

• IT Security Manager
• Sales Administrator

Use System Access Groups with a Set of Predefined Rules

You can use system access groups and predefined rules to configure access to object data for your users. System groups provide an alternative method of managing a user's access to data. There is a system access group to correspond to each of the standard job roles Oracle provides. Predefined object sharing rules assigned to each group provide the same access to data provided by the standard job roles and associated data security policies.

With this update, predefined rules are now available for these objects: Partner, Deal Registration, MDF Budget, MDF Request, MDF Claim, Program Enrollment, Business Plan, Quota Plan, Price Book, Product, Product Group, Household, Resource, Service Request, Sales Territory Proposal, Sales Territory and Resource Quota.

Steps to Enable

Here are the steps to enable a predefined rule for a system access group:

1. On the Access Groups page in the Sales and Service Access Management work area, select the Object Sharing Rules tab.
2. Select the object for which you want to use predefined rules from the Object list.
3. Select the object sharing rule you want to use.
4. To activate the rule, select the Active check box.
5. In the Action: Assign Access Group area, select the Enable check box for each access group you want to assign the rule to.
6. Click Save and Close from the Actions menu.
7. On the Object Sharing Rules page, select the Publish Rules option from the Actions menu.
8. Run the Perform Object Sharing Rule Assignment Processing scheduled process to ensure that the access group sharing rules for the object are assigned properly.

Key Resources

• See the "Access Groups" chapter in the Securing CX Sales and B2B Service guide.

Role Information

• IT Security Manager 
• Sales Administrator

Import Rules for Access Groups

You can now use the standard import framework to import object sharing rules and group membership rules for access groups into your sales environment. You can import rules previously exported from the same or another environment, or can use this functionality to update multiple access group rules at a time.

This feature lets you manage your access group rules more easily and efficiently.

Steps to Enable

You don't need to do anything to enable this feature.

Key Resources

• See the "Access Groups" chapter in the Securing CX Sales and B2B Service guide.

Role Information

• IT Security Manager 
• Sales Administrator

Application Composer

Enable Bidirectional Reporting for Custom Reference and DCL Relationships

You can now create custom subject areas to support reporting in both directions for custom one-to-many reference relationships and dynamic choice list relationships created in Application Composer. When choosing primary and child objects for a custom subject area, you can select either the source or target object in the object hierarchy. Depending on the type of relationship, the other side of the relationship is available as either a child or related object.

The enhancement provides endless reporting opportunities and reduces the need for multiple custom subject areas and joins, resulting in improved usability and performance.

Steps to Enable

Leverage new subject area(s) by adding to existing reports or using in new reports. For details about creating and editing reports, see the Creating and Administering Analytics and Reports book (available from the Oracle Help Center > your apps service area of interest > Books > Administration).

Key Resources

• See the "Add Objects and Fields" chapter in the Configuring Applications Using Application Composer guide.

Delete Custom Fields in an Unpublished Sandbox

You can now delete custom fields from both custom and standard objects, provided your sandbox is still unpublished.

Delete Custom Fields

Instead of abandoning an unpublished sandbox due to unwanted custom fields, you can now delete a custom field if needed and continue to use the sandbox for your application changes before publishing it.

Steps to Enable

Leverage Application Composer to expose and adjust page layout and attributes. To learn more about extending your application using Application Composer, visit Oracle Help Center > your apps service area of interest > Books > Configuration and Extension.

You don’t need to do anything to enable this feature.

Key Resources

• See the "Add Objects and Fields" chapter in the Configuring Applications Using Application Composer guide.

Use Custom REST-Based Smart Actions to Update Multiple Records in Workspace

Configure custom REST-based smart actions to let your users update multiple records at once in Workspace.

Configuring custom smart actions to update multiple records at once lets your users be more efficient when working in Workspace.

Steps to Enable

Leverage Application Composer to expose and adjust page layout and attributes. To learn more about extending your application using Application Composer, visit Oracle Help Center > your apps service area of interest > Books > Configuration and Extension.

Key Resources

• See the "Add Objects and Fields" chapter in the Configuring Applications Using Application Composer guide.

Simplified Setup

Use Setup Assistant to Complete Initial Sales Setup for Existing Deployments

Customers with existing deployments, including Financials and HCM, can use Setup Assistant to speed up their initial Sales setup. Setup Assistant automatically performs many manual setup tasks required for opportunities, forecasting, the import of geographies data, and the creation of sales users. Setup Assistant leverages the existing enterprise setup data and accounting calendar.

Customers with existing cloud application deployments can speed up their initial Sales deployments.

Steps to Enable

You don't need to do anything to enable this feature.

Key Resources

• See the Getting Started with Your Sales Implementation guide.

IMPORTANT Actions and Considerations

DEPRECATE TERRITORY PROPOSAL ASSOCIATION WITH QUOTA PLANS

Quota Plans Can Only Be Synchronized with an Active Territory Hierarchy

Sales managers or administrators frequently make changes to active territories directly. These changes can also be done using territory proposals

Currently, when a user has associated a draft proposal with a Quota Plan, the changes done to the territories as part of the draft proposal are also applied to the Quota Plan.

Beginning in Update 21C, quota plans can only be synchronized with an active territory hierarchy.

Prior to Update 21C, quota plans could be synchronized with both active and draft proposal territory hierarchies.

Territory proposal association with quota plans is being deprecated.

_________________________________________________________________________________

FUNCTIONAL PRIVILEGES FOR MDF CLAIM AND CLAIM SETTLEMENTS

Prior to Update 21C, a user’s update access to approval-related attributes in MDF Claim, and the user's edit access to Claim Settlement, were granted through data security policies. However, starting with Update 21C, this access is granted through functional privileges. Thus, you need to explicitly assign the privileges shown in the following table to your applicable custom roles, so that users can update approval-related attributes in MDF Claim and update Claim Settlement after the upgrade to Update 21C.

You can find more information about adding privileges to roles in the Securing Sales and B2B Service guide.

Privilege	Impact	Predefined Roles That Are Assigned the Privilege
Title: Update Marketing Claim Approval Details Technical Name:  MKT_UPDATE_MARKETING_CLAIM_APPROVAL_DETAILS_PRIV	Lets users update these approval details on an MDF Claim: Approved Amount Reject Reason Return Reason Approval Comments	This is meant for channel users. These predefined roles are already assigned this privilege: Sales Administrator Channel Operations Manager Channel Sales Manager Channel Account Manager
Title: Update Marketing Claim Settlement Details Technical Name: MKT_UPDATE_MARKETING_CLAIM_SETTLEMENT_DETAILS_PRIV	Gives users edit/update access to claim settlements.	This is meant for channel users. These predefined roles are already assigned this privilege: Sales Administrator Channel Operations Manager Channel Sales Manager Channel Account Manager
Title: Update Completed Marketing Claim Settlement Technical Name: MKT_UPDATE_COMPLETED_MARKETING_CLAIM_SETTLEMENT_PRIV	Gives users edit/update access to claim settlements where the claim settlement is in completed status. This privilege should be granted only to roles who should be able to edit claim settlements in completed status	This is meant for channel users,. This predefined role is already assigned this privilege: Sales Administrator

NOTE: If you don't add these privileges after upgrading to Update 21C, users who previously had update access to approval-related and budget attributes will no longer have access.

_________________________________________________________________________________

SELECTION OF INCREMENTAL CALCULATION NOW AUTOMATED

With enhanced incentive calculation processes, the application intelligently determines if incremental processing is required or not. After Update 21C, you no longer need to manually set the Disable Incremental Calculation parameter. Additionally, this parameter is no longer supported

Steps to Enable

Prior to Update 21C, you needed to set the Disable Incremental Calculation parameter to No to get the full benefit of performance enhancements.

1. Sign-in to the application as Incentive Compensation Administrator.
2. Navigate to Setup and Maintenance > Sales Offering > Incentives functional area.
3. Select the Manage Parameters task.
4. In the Earnings Calculation Parameters section of the Manage Parameters page, set Disable Incremental Calculation to No.
5. When prompted to do so, run the Deploy Compensation Plans scheduled process. The process may take some time to finish.
6. You must repeat the above process for all business units where the Disable Incremental Calculation parameter is set to Yes. Running the scheduled process updates the business unit data and completes the change.

After you make these changes, the application is ready to use.

_________________________________________________________________________________

POST-UPDATE TASKS

UPDATE APPLICATION COMPOSER CUSTOMIZATION TO THE LATEST ENHANCED BEHAVIOR

During your upgrade, most existing customizations made in Application Composer are automatically updated to the latest enhanced behavior in the new release. However, there are a few exceptions that require you to manually initiate the upgrade script for each of those customizations.

NOTE: Some upgrade tasks will not be removed from this page even after the upgrade is completed, as they are re-runnable for certain feature enhancements that are expected in future releases.

STEPS TO ENABLE

You must sign in as a user with an administrator role to perform these steps.

IMPORTANT: Do not perform these steps when there are pending changes in an active sandbox. Be sure to save and publish sandboxes with any changes you want to keep before proceeding, and delete any sandboxes that you do not intend to publish.

1. Sign into the application. 
2. From the Navigator, select Sandboxes (under Configuration).
3. Create a new sandbox and set it as the active sandbox. The current active sandbox displays at the top of the application.
4. Go to: Navigator > Application Composer (under Configuration).
5. From the Application drop-down list, select the first application whose metadata you want to upgrade, such as Common or Sales.
6. From the navigation tree on the left, under Common Setup, click Metadata Manager.

NOTE: You need to upgrade the existing customization metadata for each application separately.

7. Click Metadata Upgrade.
8. By default, the list displays the Not Started upgrade items that you need to manually upgrade. Highlight the first row in the list, and then click the Upgrade button.
9. Click OK in the confirmation dialog box. This process may take a couple of minutes. When the upgrade is done, the dialog box closes and the Upgrade Completed column shows an indicator.
10. Repeat steps 7-8 for each row in the list.
11. Repeat steps 4-8 for each application in the Application drop-down list in Application Composer.
12. Publish the sandbox. 

After the processes have completed, the application is ready to use.

KEY RESOURCES

• Read Prepare for Your Quarterly Update (Doc ID 2445338.1) on My Oracle Support to learn how to prepare for and validate your quarterly update.