Cloud Readiness / Oracle Sales Performance Management Cloud
What's New
Expand All


  1. Update 22A
  1. Revision History
  2. Overview
  3. Feature Summary
  4. Sales Performance Management
    1. Incentive Compensation
        1. Use Simplified Participant Search
        2. Import and Export Participant Goals Using Import Management
    2. Territory Management
        1. Delete Territory Coverage Records Without Coverage Numbers Using Import Management
        2. Create Territories in Workspace
        3. Improve Performance Processing for Account Territory Assignment
        4. View the Territory Hierarchy Including More Details in Workspace
    3. Sales Forecasting
        1. Manage Aggregated Renewal Data Within the Product and Territory Tabs
  6. IMPORTANT Actions and Considerations

Update 22A

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
20 DEC 2021     Created initial document.

Overview

HAVE AN IDEA?

We’re here and we’re listening. If you have a suggestion on how to make our cloud services even better then go ahead and tell us. There are several ways to submit your ideas, for example, through the Ideas Lab on Oracle Customer Connect. Wherever you see this icon after the feature name it means we delivered one of your ideas.

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.

DISCLAIMER

The information contained in this document may include statements about Oracle’s product development plans. Many factors can materially affect Oracle’s product development plans and the nature and timing of future product releases. Accordingly, this Information is provided to you solely for information only, is not a commitment to deliver any material, code, or functionality, and should not be relied upon in making purchasing decisions. The development, release, and timing of any features or functionality described remains at the sole discretion of Oracle.

This information may not be incorporated into any contractual agreement with Oracle or its subsidiaries or affiliates. Oracle specifically disclaims any liability with respect to this information. Refer to the Legal Notices and Terms of Use for further information.

Feature Summary

Column Definitions:

Report = New or modified, Oracle-delivered, ready to run reports.

UI or Process-Based: Small Scale = These UI or process-based features are typically comprised of minor field, validation, or program changes. Therefore, the potential impact to users is minimal.

UI or Process-Based: Larger Scale* = These UI or process-based features have more complex designs. Therefore, the potential impact to users is higher.

Features Delivered Disabled = Action is needed BEFORE these features can be used by END USERS. These features are delivered disabled and you choose if and when to enable them. For example, a) new or expanded BI subject areas need to first be incorporated into reports, b) Integration is required to utilize new web services, or c) features must be assigned to user roles before they can be accessed.

Ready for Use by End Users
(Feature Delivered Enabled)

Reports plus Small Scale UI or Process-Based new features will have minimal user impact after an update. Therefore, customer acceptance testing should focus on the Larger Scale UI or Process-Based* new features.

Customer Must Take Action before Use by End Users
(Feature Delivered Disabled)

Not disruptive as action is required to make these features ready to use. As you selectively choose to leverage, you set your test and roll out timing.

Feature

Report

UI or
Process-Based:
Small Scale

UI or
Process-Based:
Larger Scale*

Sales Performance Management

Incentive Compensation

Use Simplified Participant Search

Import and Export Participant Goals Using Import Management

Territory Management

Delete Territory Coverage Records Without Coverage Numbers Using Import Management

Create Territories in Workspace

Improve Performance Processing for Account Territory Assignment

View the Territory Hierarchy Including More Details in Workspace

Sales Forecasting

Manage Aggregated Renewal Data Within the Product and Territory Tabs

>>Click for IMPORTANT Actions and Considerations

Sales Performance Management

Incentive Compensation

Use Simplified Participant Search

Use the simplified participant search option while adding paysheets to a payment batch so that the search returns only one row per participant when you don't search participants by role.

While adding individual paysheets to a payment batch, when you search for a participant, you have the option of searching by role or not searching by role. This is controlled by the profile option, Search Participant by Role. When the profile option is set to yes, Role appears as a field you can search by, and the search results also contain Role as a field. This means if a participant has multiple roles, you see multiple rows in the search results for the same participant. However, when this profile option is set to no, then Role is neither a searchable field, nor is it in the search results -- this means the search results always have one record per participant, irrespective of how many roles the participant has. The default value of the profile option is no.

This feature means reduced clutter in search results and the ability to add participant paysheets more easily.

Steps to Enable

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

Tips And Considerations

If you don't search participants by role, keep the default value of N for the profile option, Search Participant by Role (ORA_CN_SRCH_PARTIC_BY_ROLE). Otherwise, set it to Y.

Key Resources

Role Information

  • Incentive Compensation Analyst
  • Incentive Compensation Manager

Import and Export Participant Goals Using Import Management

Use Import Management to import and export participant goals to simplify your goal management process.

This feature lets you:

  • Streamline incentive goal management processes
  • Bulk-import participant goals
  • Export existing participant goals for modification

Steps to Enable

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

Key Resources

Role Information

  • Compensation Manager
  • Compensation Analyst

Territory Management

Delete Territory Coverage Records Without Coverage Numbers Using Import Management

Delete territory coverage records using Import Management, without having to reference the coverage number information. Instead, a territory coverage can be removed by referencing the unique territory number, dimension code, coverage type, and the appropriate ID or public unique identifier value.

Territory export and import is a key feature for all enterprise-scale customers using Territory Management. It's faster and easier to remove territory coverage records and realign territories using export and import.

Steps to Enable

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

Tips And Considerations

In import Management, when deleting territory coverage records, enter the unique territory number, and either:

  • Coverage number, or 
  • Dimension code, coverage type code, and the appropriate ID or public unique identifier value in the import file

Key Resources

Role Information

Sales Administrator

Create Territories in Workspace

Now you can create the top territory or a child territory from Territories in Workspace.

Workspace is a key differentiator for our customers and Territories in Workspace is now more consistent.

Steps to Enable

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

Key Resources

Role Information

Sales Manager and Sales Administrator

Improve Performance Processing for Account Territory Assignment

High-performance processing of large volumes of account territory assignment data uses pattern and rule matching that helps to resolve conflicts and initiate actions. By leveraging the capabilities of Oracle's database-centric and optimized rule-based algorithm processing, you can now significantly improve rule-based processing for territories. For example, high-performance of assignment processing of account territory data enables millions of records to be processed in minutes, rather than hours.

This enhanced territory assignment processing helps improve performance by enabling millions of sales account records to be processed in minutes, not hours.

Steps to Enable

Note: The improved performance processing for Account Territory Assignment 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 Improved Performance Processing for Account Territory Assignment post of the Sales forum on Oracle Cloud Customer Connect.

Role Information

Sales Administrator

View the Territory Hierarchy Including More Details in Workspace

Access the territories hierarchical UI from territories in Workspace. When the Navigate to an Object-Based Workspace Page from Your Sales Springboard opt-in feature is enabled, the Territories in Workspace feature is available for searching and managing active territories, and the Territory Hierarchy (More Details) page is available in a tab.

This new navigation feature helps improve both the user experience and the search experience for territories.

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 this feature, opt-in to the Navigate to an Object-Based Workspace Page from Your Sales Springboard feature in Setup and Maintenance > Offerings > Sales > Opt-in Features > Sales Foundation.

Tips And Considerations

You can configure this feature by setting the profile options, Default to Classic Territory Interface (MOT_DEFAULT_CLASSIC_INTERFACE) and Desktop Pages Version (FND_CLASSIC INTERFACE). 

Here's the navigation to set these profile options: 

  1. Go to Setup and Maintenance and search for the Manage Administrator Profile Values task.
  2. Search by the profile option code.
  3. Set the profile option values (at site or user level) to No.

Key Resources

Role Information

  • Sales Manager
  • Sales VP
  • Sales Administrator

Sales Forecasting

Manage Aggregated Renewal Data Within the Product and Territory Tabs

Manage aggregated renewal and new deals data within the Products and Territory tabs of Forecasting by segregating the metrics for renewal and new deals.

Renewal forecasting lets sales managers and sales staff review the renewal subscription forecast for a given territory or product.

Steps to Enable

Set the profile option value:

  1. In the Setup and Maintenance work area, go to the Manage Administrator Profile Values task.
  2. On the Manage Administrator Profile Values page, search for and select the profile option, Enable Renewal and Net New Forecasting.
  3. In the Profile Values section, set the value to Y at site level.

Key Resources

See this content:

Role Information

  • Sales Representative
  • Sales Manager
  • Sales Administrator

IMPORTANT Actions and Considerations

IMPACT OF NEW GROOVY VERSION ON EXISTING SCRIPTS AUTHORED IN APPLICATION COMPOSER

In this release, a new version of the Groovy scripting engine, version 2.5.14, is available with Application Composer. This new version changes some runtime application behavior, as described below. Review your existing Groovy to confirm that everything still operates as expected, or modify your scripts as needed.

1. LinkedList method behavior now matches Java behavior

The push and pop methods now work the same as in Java.

In Groovy 2.4.13 and below, LinkedList worked like a stack: Last In First Out (LIFO). In the new version, LinkedList works like a queue data structure: First In First Out (FIFO).

Let’s look at the push method:

def LinkedList list=new LinkedList();

list.add('A');

list.add('B');

list.push('C');

list.add('D');

println(list);

In 21D (Groovy 2.4.13 and below), the result was:

[A, B, C, D]

In 22A (Groovy 2.5.14), the result is now:

[C, A, B, D]

To preserve the same behavior of Groovy 2.4.x, modify your scripts as follows in Groovy 2.5.x:

Instead of list.push(), use list.add().

Next, let’s look at the pop method:

def LinkedList list=new LinkedList();

list.add('A');

list.add('B');

list.add('C');

list.add('D');

println(list.pop());

In 21D (Groovy 2.4.13 and below), the result was:

prints "D"

In 22A (Groovy 2.5.14), the result is now:

prints "A"

To preserve the same behavior of Groovy 2.4.x, modify your scripts as follows in Groovy 2.5.x:

Replace list.pop() with def value = list.last() ; list.remove(value);

2. ObjectRange iterator now returns NoSuchElementException instead of null when hasNext returns false

Calling next() on an ObjectRange iterator now returns NoSuchElementException (instead of null) when hasNext returns false, to adhere to the Iterator contract.

def itr = ('a'..'b').iterator()

assert itr.next() == 'a';

assert itr.next() == 'b';

itr.next(); /* itr is null in 21D - in 22A it throws a NoSuchElementException) */

To preserve the same behavior of Groovy 2.4.x, modify your scripts as follows in Groovy 2.5.x:

To avoid getting the unchecked exception NoSuchElementException, always have itr.hasnext() check before calling itr.next.

BPM PROJECTS FOR OBJECT WORKFLOW APPROVAL FLOWS NOW STORED IN BPM 'FUSIONAPPS' SPACE

With the migration to Oracle Business Process Management (BPM) 12C, all projects deployed for use with Application Composer object workflows are now part of the "FusionApps" space in BPM. Users who created and deployed projects in previous releases automatically have access to this space in Update 22A. Users can access this space by creating a new project, editing an existing project, or by getting a list of all projects from Application Composer.

------------------------------------------------------------

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.

  1. Click Metadata Upgrade.
  2. 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.
  3. 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.
  4. Repeat steps 7-8 for each row in the list.
  5. Repeat steps 4-8 for each application in the Application drop-down list in Application Composer.
  6. Publish the sandbox.

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

KEY RESOURCES