EBS 122 Cum RCD SME

ORACLE E-BUSINESS SUITE
RELEASE CONTENT DOCUMENT
Sales, Marketing, eCommerce, and

Incentive Compensation
Releases 12.1 and 12.2 (inclusive of 12.0.2 – 12.2.10)
Prepared by Oracle E-Business Suite Product Development
Last Updated: September 25, 2020
Copyright © 2011, 2020, Oracle and/or its affiliates.

Table of Contents
1. Disclaimer 1
2. Introduction 2
2.1. Purpose of Document 2
3. New and Changed Features in Sales and Marketing 3
3.1. Oracle Field Sales 3
3.1.1. Overview 3
3.1.2. Release 12.1.1 3
3.1.2.1. Enhanced Lead Search 3
3.1.2.2. Enhanced Opportunity Search 3
3.1.2.3. Prevent Duplicate Contacts Flow 4
3.2. Oracle Incentive Compensation 4
3.2.1. Overview 4
3.2.2. Release 12.1.1 4
3.2.2.1. Modeling and Plan Copy Features 4
3.2.2.2. Siebel CRM Integration to Oracle Incentive Compensation 5
3.2.2.3. PeopleSoft Enterprise Human Capital Management Integration Features 6
3.2.3. Release 12.1.2 7
3.2.3.1. Performance and Scalability Improvements 7
3.2.3.2. Support for Incentive Compensation Gadgets 8
3.2.4. Release 12.1.3+ 9
3.2.4.1. Calculation Performance Improvement 9
3.2.4.2. Archive & Purge 9
3.2.4.3. Subledger Archive and Ghosting/Purge 9
3.2.5. Release 12.2.4 9
3.2.5.1. Calculation Performance Improvement 9
3.2.5.2. Comprehensive Pre-Built Automated Component Based Testing for OIC 9
3.2.6. Release 12.2.5 10
3.2.6.1. New XML based WebADI Report for Plan Visualization 10
3.2.6.2. Improved Plan Administrator Usability for Expressions and Formulas 11
3.2.6.3. Archive and Purge 11
3.2.7. Release 12.2.6 12
3.2.7.1. Subledger Archive and Ghosting/Purge 12
3.2.7.2. Integration Enhancements to EBS Payrolls and Accounts Payable 13
3.2.7.3. Optimize Transactions Creates and Splits via Salesperson Number for Retail 13
3.2.7.4. Smarter ‘Use Incremental Calculation’ Default in Online Calculation Submission UI 14
3.2.7.5. Leverage Default Operating Unit in Additional UIs 14
3.2.8. Release 12.2.7 14
3.2.9. Release 12.2.9 14
3.2.9.1. Default Operating Unit based on MO: Default Profile Unit 14
3.2.9.2. Cancel Transactions in Maintain Transactions User Interface 15
3.2.9.3. Enforce Classification and Dimension Attribute Settings 15
3.2.10. Release 12.2.10 16
3.2.10.1. Concurrent Program to run Payment Collection Script for diagnostics 16
3.2.10.2. Concurrent Program to synchronize Accumulated Ledger Balances 16
Oracle E-Business Suite Releases 12.1 and 12.2 Release Content Document ii
3.2.10.3. Relax Maintain Transactions Search Page Query Criteria 16
3.2.10.4. Export of Incentive Compensation Reports to include Report Headers 16
3.2.10.5. Cancel Transaction support in the Maintain Transactions Page 16
3.3. Oracle Incentive Compensation Command Center 16
3.3.1. Overview 16
3.3.2. Released 12.2.8+ 17
3.3.2.1. Recent Jobs 17
3.3.2.2. Quality by Phase 17
3.3.2.3. Paysheet Console 18
3.3.2.4. Jeopardy by Phase 18
3.3.3. Released 12.2.9++ 18
3.3.3.1. Performance Evaluation 18
3.4. Oracle Incentive Compensation Analytics for Oracle Data Integrator 18
3.4.1. Overview 18
3.4.2. Release 12.1.2 19
3.4.2.1. Data Schema 19
3.4.2.2. ETL scripts 19
3.4.2.3. OBI Metadata 19
3.4.2.4. Dashboard for Modeling 19
3.4.2.5. Dashboard for other roles Schema 19
3.4.3. Release 12.1.3 19
3.4.3.1. Performance Distribution 19
3.4.4. Release 12.2.4 19
3.4.4.1. Certification of ODI 11g and OBIEE 11g 19
3.4.4.2. Mobile Incentive Insight for Payee Community 19
3.4.5. Release 12.2.5 20
3.4.5.1. Payment Fact 20
3.4.5.2. Territory Dimension 20
3.4.5.3. Six New Subject Areas 20
3.4.1. Release 12.2.6 20
3.4.1.1. Certification of ODI 12c and OBIEE 12c 20
3.4.1.2. New Commission Reporting for Payees 21
3.4.2. Release 12.2.7 21
3.4.2.1. Improved ETL Performance For Incremental Calculation Customers 21
3.5. Oracle Incentive Compensation Information Discovery 21
3.5.1. V6 (New Application introduced in V6) 21
3.5.1.1. Quality Assurance for OIC including Dispute Resolution 21
3.5.1.2. Lifecycle Statuses 21
3.5.1.3. Recent Jobs Dashboard 22
3.5.1.4. Quality by Phase Dashboard 22
3.5.1.5. Faster Effective Dispute Resolution 22
3.5.1.6. Jeopardy by Phase Dashboard 22
3.5.1.7. Paysheet Console 22
3.5.2. V7 23
3.5.2.1. Support for Pay by Transaction Mode OIC Customers 23
3.5.2.2. Enhanced Usability with Dashboard Metrics 23
3.5.3. V8 23
3.5.3.1. Improved ETL Performance 23
3.5.3.2. Support for Wildcard Search 23
3.6. Oracle Marketing 23
3.6.1. Overview 23
3.6.2. Release 12.1.1 24
3.6.2.1. Data Source Refresh 24
3.6.2.2. Extend Gantt Chart Functionality to Include Programs 24
3.6.2.3. Gantt Chart Functionality Date Display 25
3.6.2.4. Creation of ‘List at Time of Import’ as Default 25
3.6.2.5. List Import Organization and Contact Address Existence Checking 26
3.6.2.6. Modification of List Splitting by User Defined Attribute 27
Oracle E-Business Suite Releases 12.1 and 12.2 Release Content Document iii
3.6.2.7. Include Tasks when Copying Campaign Objects 28
3.7. Oracle Partner Management 28
3.7.1. Overview 28
3.7.2. Release 12.1.1 29
3.7.2.1. Additional Partner Profile Attribute Security 29
3.8. Oracle Proposals 30
3.8.1. Overview 30
3.8.2. Release 12.1.1 30
3.8.2.1. Addition of External Email Addresses 30
3.8.2.2. “Freight Terms” as Seeded Field 31
3.9. Oracle iStore 31
3.9.1. Overview 31
3.10. Oracle iStore Information Discovery 31
3.10.1. Overview 31
3.11. Oracle Quoting 32
3.11.1. Overview 32
3.11.2. Release 12.1.2 32
3.11.2.1. Quoting of Services to End Customer (Forms UI only) 32
3.11.3. Release 12.1.3 32
3.11.3.1. Configurator enhancements (HTML UI only) 32
3.11.3.2. Usability enhancements (HTML UI only) 33
3.11.3.3. QA Check framework (HTML UI only) 33
3.11.3.4. Quoting of Services to End Customer (HTML UI) 33
3.11.4. Release 12.1.3+ 34
3.11.4.1. Quote Purge 34
3.11.4.2. Gross Margin Computation (HTML UI only) 34
3.11.4.3. Reuse Credit Card (HTML UI only) 34
3.11.5. Release 12.2 34
3.11.5.1. Configurator enhancements (HTML UI only) 34
3.11.5.2. Quoting to Prospects 35
3.11.5.3. Parallel Approvals (HTML UI only) 35
3.11.6. Release 12.2.4 35
3.11.6.1. Gross Margin Computation (HTML UI only) 35
3.11.6.2. Item Orderability (HTML UI only) 36
3.11.6.3. Add Product Pop-up (HTML UI only) 36
3.11.6.4. Update Quote Line (HTML UI only) 36
3.11.6.5. Quote Purge 36
3.11.7. Release 12.2.5 37
3.11.7.1. Add Product Enhancement 37
3.11.7.2. Quote Validation Framework (HTML UI only) 37
3.11.8. Release 12.2.6 37
3.11.8.1. Mobile Quote Approvals 37
3.11.8.2. Specify the Quote Selling Price (HTML UI only) 37
3.11.8.3. Document Approvals using Electronic Signatures (HTML UI only) 38
3.11.8.4. Service Items in Configurator UI (HTML UI only) 38
3.11.8.5. Update Prior Quote Version (HTML UI only) 38
3.11.8.6. Configuration Effective Date (HTML UI only) 38
3.11.8.7. Support Model Configurations in the Quoting API 38
3.11.8.8. Print Quote Pop-up 39
3.11.9. Release 12.2.7 39
3.11.9.1. Quote Status Transition by Operating Unit 39
3.11.9.2. Support optional products 39
3.11.9.3. Update Cost from Quoting UI 39
3.11.9.4. Alternate Product Description for Quote line 40
3.11.9.5. Allow negative quote total 40
3.11.9.6. Support for Deliver-To Customer in Order Capture API 40
3.11.9.7. Email Style for Web Publish Notifications 40
Oracle E-Business Suite Releases 12.1 and 12.2 Release Content Document iv
3.11.10. Release 12.2.8 40
3.11.10.1. Create Quote from a spreadsheet 40
3.12. Oracle Quoting Information Discovery 41
3.12.1. Overview 41
3.12.2. V6 41
3.12.2.1. Quote Performance Dashboard 41
3.12.2.2. Manage Quotes Dashboard 41
3.12.3. V8 41
3.12.3.1. Advanced Search Capabilities 41
Oracle E-Business Suite Releases 12.1 and 12.2 Release Content Document v
1. Disclaimer
This Release Content Document (RCD) describes product features that are proposed for
the specified release of the Oracle E-Business Suite. This document describes new or
changed functionality only. Existing functionality from prior releases is not described. It
is intended solely to help you assess the business benefits of upgrading to the specified
release of the Oracle E-Business Suite.
This document in any form, software or printed matter, contains proprietary information
that is the exclusive property of Oracle. Your access to and use of this confidential
material is subject to the terms and conditions of your Oracle Software License and
Service Agreement, which has been executed and with which you agree to comply. This
document and information contained herein may not be disclosed, copied, reproduced or
distributed to anyone outside Oracle without prior written consent of Oracle. This
document is not part of your license agreement nor can it be incorporated into any
contractual agreement with Oracle or its subsidiaries or affiliates.
This document is for informational purposes only and is intended solely to assist you in
planning for the implementation and upgrade of the product features described. It 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 in this document remains at the sole discretion of Oracle.
Due to the nature of the product architecture, it may not be possible to safely include all
features described in this document without risking significant destabilization of the code.
Oracle E-Business Suite Releases 12.1 and 12.2 Release Content Document Purpose of Document 1
2. Introduction
2.1. Purpose of Document

This Release Content Document (RCD) communicates information about new or changed
functionality introduced in Oracle E-Business Suite Releases 12.1 and 12.2, and in
subsequent Release Update Packs (RUPs) and off-cycle patches. For your convenience,
it also includes new or changed functionality introduced in the RUPs for Release 12,
including 12.0.2 through 12.0.7.
The features and enhancements described in this document are grouped by product, and
then by the release in which they first became available, for example, “Release 12.1.1”.
Features released in an off-cycle patch have a special designation – for example, a feature
released after 12.1.1, but before 12.1.2, is designated as “Release 12.1.1+”.
Oracle E-Business Suite Releases 12.1 and 12.2 Release Content Document Purpose of Document 2
3. New and Changed Features in Sales and Marketing
3.1. Oracle Field Sales

3.1.1. Overview
Oracle Field Sales is an integrated application that provides Field Sales representatives,
Sales managers, and Sales executives with the tools they need to optimize selling
effectiveness. By automating the entire sales cycle, Oracle Field Sales enables sales
organizations to increase sales, lower sales costs and enhance long-term profitable
customer relationships. The capabilities delivered by Oracle Field Sales ensure that sales
people have the information and tools they need to be successful.
3.1.2. Release 12.1.1
3.1.2.1. Enhanced Lead Search
In Release 12, there was no direct and easy way for managers to see a consolidated view
of their subordinates’ Leads. Lead Search under the Sales manager responsibility required
the user to enter a Lead Number, Rank, or a combination of Status and Age (days),
making this search overly constrained while still not providing a comprehensive view. In
Release 12.1.1, managers will now be able to query and view their subordinates’
consolidated Leads based on a combination of only two mandatory fields: - Status and
Age (days). This will be accomplished by making search fields Lead Number and Rank
non-mandatory.
Additionally, the current search capabilities do not enable users to query Leads with
different statuses or sales channels at the same time. A user has to make multiple queries
in order to see the Leads with multiple statuses or with multiple sales channels. . In
Release 12.1.1, Sales Managers and Sales Representatives will be able to provide
multiple values for Status and Sales Channel in Advanced and Saved searches.
These additions will save users time and give them a more consolidated view of leads in
their pipeline.
3.1.2.2. Enhanced Opportunity Search

In Release 12, there was no direct and easy way for managers to see a consolidated view
of their subordinates’ Opportunities. Opportunity Search under the Sales Manager
responsibility required a user to enter either Opportunity Number or a combination of
Status, Stage, etc., making this search overly constrained while still not providing a
comprehensive view. In 12.1.1, managers will be able to query and view their
subordinates’ consolidated Opportunities based on a combination of only two mandatory
fields: Status and Close Date Quarter. This will be accomplished by making search fields
Opportunity Name, Opportunity Number, and Win Probability % non-mandatory.
Additionally, the current search capabilities do not enable a user to query Opportunities
with different statuses, sales channels, or owners at the same time. A user has to make
multiple queries in order to see the Opportunities for each of the above mentioned fields.
In 12.1.1, Sales Managers and Sales Representatives will be able to provide multiple
values for Status, Sales Channel, and Owner in Advanced and Saved searches.
These additions will save users time and give them a more consolidated view of
opportunities in their pipeline.
Oracle E-Business Suite Releases 12.1 and 12.2 Release Content Document Oracle Field Sales 3
3.1.2.3. Prevent Duplicate Contacts Flow
A Sales representative is informed that his contact at an organization has changed. Or a
Sales representative has inactivated a contact at an organization and learns that the
contact has acquired a new position at a different company. Currently in Oracle Sales, if
a Sales representative needs to inactivate a contact for one company and associate the
contact with a different company, the Sales representative needs to create a new contact
in order to associate it with the new company. He or she does not have the ability to
select inactive contacts and associate them with a new customer. This requirement results
in the creation of duplicate contacts.
In Release 12.1.1, users will be able to see both active and inactive contacts across all
organizations to prevent duplicate contact creation. If a Sales representative selects an
existing inactive contact, a new contact will not be created. This ability will make it
easier for Sales representatives to associate contacts with customers and improve their
productivity. This will also support a cleaner contact list by preventing the creation of
duplicate contacts.
3.2. Oracle Incentive Compensation

3.2.1. Overview
Oracle Incentive Compensation (OIC) is a global variable compensation application that
automates the design, administration, and analysis of incentive-based compensation
programs for employees and partners to successfully drive corporate goals.
3.2.2. Release 12.1.1
The 12.1 functionality delivers greater strategic advantage to our customers by providing
streamlined what-if modeling capabilities. In addition, this release provides PeopleSoft
customers with a lower TCO and faster time to market by extending out-of-the-box
integrations to include PeopleSoft Enterprise Human Capital Management. We have
incorporated these features into the product, by utilizing SOA technology for integration
and Oracle Business Intelligence Enterprise Edition for the analytics functionality.
We also released an out of box direct integration between Siebel and OIC 12.1, called
Siebel CRM Integration to Oracle Incentive Compensation, as part of Application
Integration Architecture (AIA) 2.5.
3.2.2.1. Modeling and Plan Copy Features

The Plan Administrator is responsible for the design, setup and maintenance of incentive
compensation plans, plan components and rules. The Plan Modeling solution addresses
the Plan Administrator’s need to design incentive plans that meet the company’s
performance and financial objectives. The modeling process allows the plan
administrator to create multiple scenarios; modify plan, plan components and rules within
each of the scenarios as required; run simulation of these plans against historical or
forecasted transactional data; and compare the results of the simulation across scenarios.
Once a scenario is chosen and approved by the compensation department, the plan
administrator will copy the plans and activate the new plans in the production
environment.
The solution includes a new user interface to manage the creation of scenarios, a utility to
copy plans from the modeling environment to the production environment for future
activation. The XML-based report containing relevant plan details provides the Plan
Administrator with a useful mechanism for communicating plan changes and obtaining
necessary approvals. Analytic content accessible via the modeling solution allows the
Oracle E-Business Suite Releases 12.1 and 12.2 Release Content Document Oracle Incentive Compensation 4
plan administrator to analyze the potential effectiveness of future plans in meeting
performance, financial and pay-for-performance objectives.
3.2.2.1.1. Scenarios
A new scenario entity is introduced in this release. The scenario allows objects to be
grouped together to support comparison of results across different sets of data.
Scenarios may be associated with different operating units to allow comparison
between scenarios with different rule and reference data sets. However more
commonly, scenarios are a grouping of plans, or more specifically plan-role
assignments, that allow users to compare the compensation costs of a set of plans in a
scenario with that of another scenario.
3.2.2.1.2. In-Line Plan and Plan Component Copy
The solution provides a one-click plan and plan component in-line copy feature. A
duplicate icon is included in the search results table in the Search Compensation
Plans, Search Plan Elements, Search Formulas, Search Rate Tables, Search Rate
Dimensions, and Search Expressions pages. This solution allows the Plan
Administrator to quickly create a copy of a compensation plan or plan component
within the same operating unit.
3.2.2.1.3. Copy Plan and Plan Components between Database Instances
At various times throughout the year, the Plan Administrator is faced with the task of
modifying or updating existing compensation plans to conform to new sales
objectives. To create the best solution, he may make copies of the existing plans,
modify them, and test out the results against historical or projected performance data.
When he has determined the appropriate plans to implement that best support the
company’s objectives, after receiving the necessary approvals, he puts the plans into
production.
To support these tasks, Oracle Incentive Compensation provides a simple and
flexible way to copy plans and plan components from the modeling environment to
the production environment leveraging XML technology. Plan copy includes the
copying of the following plan components: plan elements, formulas, expressions, rate
tables and rate dimensions. This solution focuses on the plans created by the Plan
Administrator, and excludes plans that may have been customized for a particular
resource.
This feature has been requested by many of our customers and may also be used by
consultants and implementers in migrating compensation plans from development to
test to production environments.
3.2.2.1.4. Plan XML Document
When a compensation plan has been modeled successfully, it may need to be
approved by the compensation manager and other people within the sales, HR and
finance departments before it is activated in the production environment. Oracle
Incentive Compensation facilitates plan approval by displaying the compensation
plan in an easy-to-read format. The Plan report is produced using XML Publisher and
a RTF template is provided so customers may easily modify the report for their own
business needs.
3.2.2.2. Siebel CRM Integration to Oracle Incentive Compensation

Many of Oracle’s current customers use Siebel CRM applications. Siebel CRM
Integration to Oracle Incentive Compensation delivers a sustained integration framework
supporting a sales order to commission process. Custom interfaces can represent a third
of the ICM (Incentive Compensation Management) implementation effort and costs
incurred. With delivered integrations the implementation risk, effort and costs are greatly
reduced. The direct integration provides out of the box mappings and business processes.
Functionality provided includes the following:
• Periodic synchronization of sales users from Siebel Sales to OIC
• Periodic synchronization of relationship managers, partners from Siebel PRM to OIC
• Periodic synchronization of sales orders from Siebel Order Management to OIC
• Support for compensating on bundles
• Support for compensating on margins down to the order line
• Support for currency conversion for consistent calculations
3.2.2.3. PeopleSoft Enterprise Human Capital Management Integration Features

Many of Oracle’s current customers use PeopleSoft Enterprise Human Capital
Management (HCM) applications. Employees defined within PeopleSoft HCM may be
participants who are compensated by the Oracle Incentive Compensation solution. An
out-of-the-box integration delivers faster implementation times to these customers by
providing a mechanism for importing employee, department and job information from
PeopleSoft HCM into Oracle Resource Manager to define the resources, roles, and
groups and sales compensation hierarchy used by Oracle Incentive Compensation.
The method for importing PeopleSoft employee data into Resource Manager for
subsequent use by Oracle Incentive Compensation (OIC) includes using BPEL for
configuration mapping and data loading into the Oracle schema. Both initial and
incremental data loading from PeopleSoft HR is included.
Functionality provided includes the following:
• Employee data import from PeopleSoft HCM into Oracle Resource Manager
Resource definition
• Job Code data import from PeopleSoft HCM into Oracle Resource Manager Role
definition for Compensation Plan Assignment
• Department and Department Tree data import from PeopleSoft HCM to Oracle
Resource Manager Group definition for use in defining the Sales Compensation
Hierarchy
• Business Events for synchronization of employee definition within source and
target system
3.2.2.3.1. Employee, Department, Job Synchronization

This process flow is designed to synchronize PeopleSoft Enterprise Human Capital
Management (HCM) employee, department, and job definitions with Oracle
Resource Manager Resource, group, and role definitions. The process handles the
initial full load of employee, job and department definitions from PeopleSoft to
Oracle as well as incremental updates.
Hierarchy definitions exist by Departments and Position in PeopleSoft HCM. Oracle
Incentive Compensation uses Departments rather than Positions for building the sales
compensation hierarchy as it is our assumption that most customer implementations
use Departments to define the organizational structure.
The integration process is triggered when the PeopleSoft HCM system generates an
XML message with employee definitions and puts it on a JMS queue dedicated for
this process. The BPEL process polls the JMS Queue for a message from PeopleSoft.
Once the message is consumed by the BPEL process, it is removed from the Queue
and processed.
3.2.2.3.2. Business Events to Trigger Resource Updates
There are many business events that affect a resource’s compensation pay.
Typically, compensation pay may be held for many such events like leave of absence,
job/role, and department changes or termination.
When an event occurs and resource records are either created and or updated in
Resource Manager using the processes, Oracle Incentive Compensation’s API is
automatically triggered by the system to create the compensation plan and pay group
assignments (where appropriate) within OIC. APIs are also triggered for updating
Assignment end dates and Hold Payment statuses.
The following business events are supported:
• New Employee/Re-Hire
• Terminated Employee
• Leave Of Absence
• Job/Role change
Customers may easily modify these events as required to suit their business needs.
3.2.2.3.3. Reporting for Plan Modeling

Scenario simulation is done by running calculation within the modeling environment.
Reports may be viewed against the modeling transactional environment to determine
the results of simulation.
3.2.3. Release 12.1.2
3.2.3.1. Performance and Scalability Improvements
One key reason for the market success of OIC is the unique ability to scale to large
volumes of data. We have customers that process millions of transactions per day,
compensating tens of thousands of resources. Both these features are designed to further
enhance our market leading position by extending our performance and scalability
capabilities.
3.2.3.1.1. New Summarization Method
When a company pays a resource, it is common to also pay their management chain
based on the subordinate’s position. Prior to 12.1.1 we met this requirement by
providing functionality of rolling up transactions from the subordinate resource to the
resource. Prior to 12.1.1 OIC customers have three options when they perform this
rollup. They can duplicate the subordinates resources’ transactions to the resource;
they can aggregate the transactions for the resource when they rollup, or they can
create a custom rollup function.
As part of 12.1.1, we have introduced an additional method for OIC customers; best
suited for use cases where the top tiers of the management chain receive a large
percentage of all transactions and do not require details of every transaction rolled
up. In this use case it is far more efficient not to duplicate individual transactions but
to summarize transactions and create an aggregation transaction. Once the
transactions have been rolled up without aggregation, we will allow the customer to
call a custom function to summarize those transactions.
When a compensation plan associated with a resource has an option selected, the
transactions from subordinates will be summarized by a method. This method will
include order, group and sum to be defined by the customer. Customers will use the
current functionality of Custom Aggregation API to define their logic.
We follow the logic that is currently used in the application for Aggregation for the
new Summery option. For example, for questions on the behavior of Full calculation
and Incremental calculation, we will follow the logic currently used in the
application.
There is a key assumption for using the feature which is customers will not be
allowed to have a resource have detail level of processing if the subordinate has the
option of summary. If a resource subordinate is summarized, and the resource is
detail, the detail will not be available for resource.
A second key assumption is that any one resource will only have one active role, thus
only one active plan.
3.2.3.2. Support for Incentive Compensation Gadgets

Providing relevant data to sales people about their compensation in a timely and easy to
understand method is one key to the successful rollout of Oracle Incentive Compensation.
Providing more than one method to best suit the needs of OIC customers of presenting
the relevant data is the goal of the OIC Gadgets. By providing a web service to expose
OIC data and creating Gadgets in the Adobe technology, OIC customers gain a new way
to communicate key data to sales people quickly and easily.
OIC’s gadgets answer for sales reps the great adoption question of “what’s in it for me”
and offer incentive insight that puts sales reps in charge to align them to incorporate
objectives for their own benefit.
Three sample gadgets were created to provide customers with a starting point for
information they want to present to their sales force.
3.2.3.2.1. Most Recent Transaction Gadget
This gadget shows the sales people the most recent Transactions that have been
credited to the sale people along with data about the Transaction, such as Customer,
Amount, Date and Earnings. During a current period this will allow the Sale people
to understand what the status of their earnings is and what they will get paid in the
upcoming period. This will reduce the number of inquiries into the Compensation
Analysts.
3.2.3.2.2. Top Customer Gadget
This gadget shows the sales people the rank order of their customers based on the
amount of commission they have earned. This allows the sales people to easily
understand who their most important customers are by putting the value into their
pay.
3.2.3.2.3. Top Product Gadget
This gadget shows the sales people the rank of the products they sell based on the
amount of commission they have earned. This allows the sales people to easily
understand the products that they are earning the most money on or “shop the plan.”
3.2.3.2.4. Infrastructure to Support Web 2.0 Data Access
Based on the open API’s for OIC, an additional structure was created to ease the
creation of gadgets.
3.2.4. Release 12.1.3+
3.2.4.1. Calculation Performance Improvement
This feature was back-ported from 12.2.4. Refer to the full feature description under the
12.2.4 section for this product.
3.2.4.2. Archive & Purge
3.2.4.3. Subledger Archive and Ghosting/Purge
This feature, Archive Ghosting/Purge for Subledger artifacts, was backported from
Release 12.2.6. This provides existing 12.1.3 customers with the ability to drastically
reduce their storage requirements/costs and improve performance. Refer to the full feature
description under the 12.2.6 section for this product.
3.2.5. Release 12.2.4
3.2.5.1. Calculation Performance Improvement
OIC leverages 2 system parameters to determine batch sizes for optimal calculation
performance. However depending on your data distribution of transactions across sales
reps, this query can take longer than the actual calculation stage. You may be a candidate
for this performance enhancement if a larger proportion of your total calculation time is
spent prior to the spawning of child sub-processes for calculation in Concurrent Manager.
For instance if the child sub-processes are not spawned till 2 hours 15 minutes into a 3
hour calculation, then this performance feature may reduce calculation times from 3
hours down to 1 hour.
This performance feature is driven by new Profile introduced in release 12.2.4 called
‘OSC: Use Number of Salesreps as Only Criteria for Determining Batch Size’ = YES,
which as the name states will leverage only the sales rep batch size and begin spawning
child sub-processes.
This feature is back-ported to 12.1.3+.
3.2.5.2. Comprehensive Pre-Built Automated Component Based Testing for OIC
Oracle Functional Testing Suite Advanced Pack for Oracle E-Business Suite enables
automated testing of detailed and complex OIC test flows. Designed for use with the
Oracle Functional Testing Suite and its Oracle Flow Builder capability, the pack provides
pre-built test components and flows for in-depth testing of the Oracle E-Business Suite
products including in-depth focus on Oracle Incentive Compensation. This includes
comprehensive coverage of OIC testing above and beyond the EBS Starter Pack.
Using Oracle Flow Builder, even non-technical testers can create working test scripts
using the pre-built components that Oracle provides. Each component represents an
atomic test operation such as “create a payment batch” or “split a transaction”. Testers
can assemble the pre-built components into test flows, and combine test flows with
spreadsheet data to drive the testing of multiple data conditions. The Oracle Flow Builder
framework allows customers to add, modify and extend the pre-built components to
address new functionality and customizations of the Oracle E-Business Suite and to
automatically generate related documentation.
Using Oracle Flow Builder’s component-based test generation framework instead of a

traditional record/playback approach has allowed the EBS’ own Quality Assurance team
to reduce their test automation effort by 60%. E-Business Suite customers can
significantly reduce their test automation effort using Oracle Functional Testing Suite
with Oracle Flow Builder and pre-built test components for all OIC components and a
majority of OIC specific test flows.
Also see Oracle Functional Testing Suite Advanced Pack Readme for E-Business Suite,
(Oracle Support Note 1947643.1)
3.2.6. Release 12.2.5

Release 12.2.5 focuses on driving additional value throughout the enterprise around a
mature crediting & calc engine.
On the SPM or Sales side, is the ability to motivate reps with incentive insight on their
mobile devices whether it is an iPad, iPhone or Android (please see what we are doing in
Oracle Incentive Compensation Analytics).
On the operational side, comp admin is naturally focused on a periodic processing cycle
for commission payments. Much of this process is validating the completeness and
accuracy to ensure quality and timeliness as transactions are moved through collect,
credit, calc and pay. Most customers have custom reports or a custom data mart to
support this validation. On the backend of this processing is researching disputes. Is a
dispute a single occurrence or the tip of the iceberg affecting a larger audience? And
what is the source of the issue? Being able to answer those questions easily and
effectively is the focus of a new E-Business Suite Endeca extension for Incentive
Compensation, named OIC Information Discovery.
In many industries the success of an OIC implementation beyond calculating the correct
numbers is determined by the agility of making plan changes. This is determined by a
proper architecture, a clear understanding of current plan design, and the ability to
quickly make the needed changes.
For the plan admin side, we have improved plan design understanding and improved the
user interface for plan design.
For the incentive compensation administrator, we have improved the cost of ownership
by providing reducing storage requirements for permanently closed periods and increased
the performance in batch payment processing.
3.2.6.1. New XML based WebADI Report for Plan Visualization
Plan administrators are responsible for plan design changes which require a very detailed
understanding of how the plan works. An interactive, pictorial representation of plan
components down to an expression is a picture worth a thousand words! This visual
representation of plans can also provide insight into improved modularity in plan design.
An interactive interface unlike a static report is powerful because it allows the plan
administrator to focus on a specific plan, plan element or formula.
Release 12.2.5 introduces a XML based WebADI report which can be leveraged by users
to visualize plan components and rules through network analysis toolsets such as open
source Gephi (the inspiration behind LinkedIn’s InMaps).
The ability to visually render a plan, its relationships and its rules can drive greater agility
and productivity from plan administrators because they can more easily understand how a
plan is built to facilitate accurate and agile plan changes. Via Gephi, Plan administrators
will select individual components for context and visually see interdependencies.
3.2.6.2. Improved Plan Administrator Usability for Expressions and Formulas
Plan administrator usability has been improved in the Expression Builder UI through the
following enhancements:
• LOV selection for Expressions and Formulas,

• Modal pop ups to view Expression definitions in their formula context and in the
list of Expressions UI.
Expressions can call other expressions or formulas and some customers can have many.
Expression selection in the Expression Builder UI includes LOV support so plan
administrators can more quickly select an expression without visually searching through
a list of all expressions. Formula selection in the Expression Builder UI includes LOV
support so plan administrators can quickly select a formula without visually searching
through a list of all formulas.
Without losing context of a formula, a plan administrator has modal pop ups to view
input, output and performance measure expression definitions from within the Formula
UIs and in the list of Expressions UI.
3.2.6.3. Archive and Purge
Many industries and customers have compliance requirements surrounding data retention
for their incentive systems. Other customers have been long time users of OIC and have
consumed sizable storage volumes which they wish to reclaim.
OIC archive and purge by period operates only on permanently closed periods and
addresses 2 categories of OIC tables:
• Category A – Housekeeping to purge obsolete runtime data by period

• Category B – Archive and purge sizable non salesrep subledger tables by period
Accompanying project planning guidance will be incorporated into the OIC

Implementation Guide to provide background, guidance and methodology behind the
provided archive and purge functionality so a customer can plan and determine the
impact of archive and purge to their implementation and/or customizations if any.
Category A tables include:
• Successfully completed CSV Import transaction uploads

o CN_IMP_HEADERS_ALL
o CN_IMP_LINES_ALL
• OIC Debug message logs
o CN_PROCESS_AUDITS_ALL
o CN_PROCESS_AUDITS_LINES_ALL
• Completed incremental calculation event and notification logs
o CN_EVENT_LOG_ALL
o CN_NOTIFY_LOG_ALL
Category B tables include:
• Collection and Interface Tables

o CN_TRX_SALES_LINES_ALL
o CN_TRX_LINES_ALL
o CN_TRX_ALL
o CN_NOT_TRX_ALL
o CN_INVOICE_CHANGES_ALL
o CN_COMM_LINES_API_ALL
• Transaction Tables
o CN_COMMISSION_HEADERS_ALL
o CN_COMMISSION_LINES_ALL
• Payment Tables (including some decommissioned tables)
o CN_PAYRUNS_ALL
o CN_PAYMENT_TRANSACTIONS_ALL
o CN_PAYMENT_API_ALL
o CN_POSTING_DETAILS_SUM_ALL
o CN_POSTING_DETAILS_ALL
o CN_PAY_APPROVAL_FLOW_ALL
o CN_WORKSHEET_BONUSES_ALL
o CN_WORKSHEET_QG_DTLS_ALL
o CN_PAYMENT_WORKSHEETS_ALL
o CN_LEDGER_JOURNAL_ENTRIES_ALL
• Concurrent calculation submission & parallelization process logs
o CN_PROCESS_BATCHES_ALL
3.2.7. Release 12.2.6

Release 12.2.6 continues driving additional value throughout the enterprise around a
mature crediting & calc engine.
Sales can leverage the latest OBIEE 12c techstack and UI for motivating reps (please see
what we are doing in Oracle Incentive Compensation Analytics).
In Release 12.2.5 we introduce the new OIC Information Discovery that builds in quality
assurance processes and actionable dashboards into OIC processing. With the second
release of OIC Information Discovery in 12.2.6, comp admin will see support for OIC
customers operating in pay by transaction mode.
Archive purge has been enhanced to include subledger content to further improve the cost
of ownership by reducing storage or transitioning to cheaper storage.
3.2.7.1. Subledger Archive and Ghosting/Purge
Long time users of OIC have sizable storage volumes in their subledgers which they may
wish to reclaim. In addition, reducing the size of these subledger tables can have a
dramatic effect on the performance of payment approvals processing.
This is in addition to archive and purge functionality for non-subledger tables in 12.2.5.
OIC archive and ghosting/purge by period operates only on permanently closed periods
and addresses a specific category of OIC tables:
• Category C – Archive and purge or ghost sizable salesrep subledger tables by

period
Accompanying project planning guidance will be incorporated into the OIC

Implementation Guide to provide background, guidance and methodology behind the
provided archive and ghosting functionality for subledgers so a customer can plan and
determine the impact to their implementation and/or customizations if any.
Category C tables include:
• Purged Subledger Tables

o CN_SRP_PER_QUOTA_RC_ALL
o CN_SRP_PERIOD_QUOTAS_ALL
o CN_SRP_PERIOD_QUOTAS_EXT_ALL
o CN_SRP_PERIOD_PAYEES_ALL
• Ghosted Subledger Tables
o CN_SRP_PERIODS_ALL
3.2.7.2. Integration Enhancements to EBS Payrolls and Accounts Payable
Prevent zero payments from being passed in the OIC integration to EBS Payroll and
Accounts Payable.
This will be driven by 2 new payment parameters in Configuration Workbench’s

Payment Parameters.
• Prevent Zero Payments to Payroll checkbox

• Prevent Zero Payments to AP checkbox
To improve visibility and reconciliation for AP departments, OIC payments interfaced to

EBS AP will pass the payrun name, plan element name and comp plan name in
AP_INVOICES_INTERFACE.DESCRIPTION.
To improve usability and help payroll analyst validate payments in EBS Payroll, an
Element Number will be generated for each line in a BEE batch.
3.2.7.3. Optimize Transactions Creates and Splits via Salesperson Number for
Retail
It is common in retail and other industries to manage salespersons via their employee
number or salesperson number.
The Create Transaction user interface directly exposes a ‘Salesperson Number’ field that
can be used to specify a salesperson.
The Split Transaction user interface directly exposes a ‘Salesperson Number’ field that
can be used to specify a salesperson.
3.2.7.4. Smarter ‘Use Incremental Calculation’ Default in Online Calculation
Submission UI
To avoid accidently running full calculation for incremental calculation customers,

calculation submission UIs will default the Use Incremental Calculation LOV to ‘Yes’
when the profile ‘OIC: Enable Incremental Calculation’ is enabled. If the profile is
disabled, then the default value of the LOV is ‘No’.
In addition to turning on logging into the Notify Log, the profile will determine the
default value of the ‘Use Incremental Calculation’ LOV in the online calculation
submission UI.
3.2.7.5. Leverage Default Operating Unit in Additional UIs

Leverage the profile ‘MO: Default Operating Unit’ to set the operating unit context in the
following 7 search UIs.
Responsibility Navigation Path to UI
Compensation Manager Tasks > Maintain Payment Batches > Search
Plan Administrator Compensation Plan and Components > Maintain
Component Library > Plan Elements > Search
Component Library > Rate Tables > Search
Component Library > Rate Dimensions >
Search
Component Library > Formulas > Search
Component Library > Expressions > Search
Component Library > Payment Plans > Search
3.2.8. Release 12.2.7
Release 12.2.7 continues driving additional value throughout the enterprise around a
mature crediting & calc engine. The theme for 12.2.7 is to further performance for
Oracle Incentive Compensation Analytics and Information Discovery.
Sales can leverage the latest OBIEE 12c techstack and UI for motivating reps (please see
what we are doing in Oracle Incentive Compensation Analytics). ETL performance for
Incremental Calculation customers is improved further with a partition strategy for
Earnings data.
In Release 12.2.7 we are improving the ETL performance of the new OIC Information
Discovery that builds in quality assurance processes and actionable dashboards into OIC
processing.
3.2.9. Release 12.2.9

3.2.9.1. Default Operating Unit based on MO: Default Profile Unit
Leverage the profile ‘MO: Default Operating Unit’ to default the operating unit context
in the following search and/or create UIs.
Responsibility Navigation Path to UI
Compensation Manager Search Resources (Resource 360) > Search
Compensation Manager Tasks > Calculate Compensation > Search
Compensation Analyst Setup > View Classification Rules > Search
Compensation Plans > Search
Component Library > Payment Plans > Search
Plan Administrator Product Classification > Maintain Products >
Search
Plan Administrator Product Classification > Maintain Product
Hierarchies > Search
Plan Administrator Product Classification > Maintain Classification
Rulesets > Search
Plan Administrator Other rule sets and hierarchies >> Maintain
credit allocation rule sets > Search
Plan Administrator Other Rule Sets and Hierarchies > Maintain
Projected Compensation Rulesets > Search
Plan Administrator Other Rule Sets and Hierarchies > Maintain
Other Hierarchies > Search
Plan Administrator Oracle Payables Integration > Expense/Liability
Accounts at Product Level > Search
Plan Administrator Oracle Payables Integration > Maintain Account
Generation Rule Sets > Search
Plan Administrator Requests > Export Setup Data > Search
Plan Administrator Requests > Export Setup Data > Create
Plan Administrator Requests > Import Setup Data > Search
Plan Administrator Requests > Import Setup Data > Create Op Plan
Modeling > Maintain Scenario > Search
3.2.9.2. Cancel Transactions in Maintain Transactions User Interface
Occasionally, transactions within OIC may need to be cancelled, manually. With this
feature, a new Cancel button enables the users to cancel transactions in the Maintain
Transactions page. Canceled transactions will not be processed within OIC. Only
transactions that are not POSTED may be cancelled. Users can also cancel the following
transactions.
• Collected Transactions
• Loaded Transactions (LOAD)
• Rolled Up Transactions (ROLL)
• SCA Generated Transactions
3.2.9.3. Enforce Classification and Dimension Attribute Settings
Within OIC, users may enable Descriptive Flex Fields (DFF attributes) to specify various
characteristics such as data type, value sets, etc. With this feature, all entries into DFFs of
the Maintain transaction page will be validated against the classification and dimension
metadata defined in the configure tables and columns interface.
3.2.10. Release 12.2.10
3.2.10.1. Concurrent Program to run Payment Collection Script for diagnostics
Enable business users to run the payment collection script as a concurrent request to
gather diagnostic information for a given sales person with whom payment issues are
encountered when creating / updating payment worksheets.
3.2.10.2. Concurrent Program to synchronize Accumulated Ledger Balances
Enable business users to Synchronize Accumulated Ledger Balances for a given sales
person after any data fix is applied in order to fix payment issues.
3.2.10.3. Relax Maintain Transactions Search Page Query Criteria
In Maintain Transactions Search page, make the “From” and “To” Dates optional,
thereby eliminating entry into multiple fields and making it easier for users to perform
quick search.
3.2.10.4. Export of Incentive Compensation Reports to include Report Headers
Export to Excel of Earning Statement and Year to Date Summary reports include report
headers such as Report Name, Salesperson Name, Report Execution Date, and Currency
for user to better understand the context of the report data.
3.2.10.5. Cancel Transaction support in the Maintain Transactions Page
Enable user to cancel transactions that are in the Rollup, Population or Calculated status.
3.3. Oracle Incentive Compensation Command Center

3.3.1. Overview
The Oracle Incentive Compensation Command Center dashboards empower Sales Plan
Administrators, Sales Compensation Managers with actionable insights to efficiently run
day to day operations, effectively mitigate processing failures, identify compensation
trends, resolve disputes and bring unpaid commissions to resolution.
The information presented in these dashboards is through clickable metrics, charts, and
results table enabling the user to quickly navigate through the information, drill down
into the details and take corrective action to resolve exceptions.
Within Incentive Compensation each processed transaction passes through a Collect,

Calc and Pay Phase. Validating that each transaction has correctly processed across these
phases is integral to the Compensation Administrators. Oracle Incentive Compensation
Oracle E-Business Suite Releases 12.1 and 12.2 Release Content Document Oracle Incentive Compensation Command Center 16
Command Center enriches transactions with lifecycle attributes that combine multiple
statuses to reflect what has how a transaction has been processed in OIC in a single
glance.
There are 4 lifecycle attributes; one for each for collect, calculate and pay phase; and a
single concatenated lifecycle status across all phases.
Lifecycle attributes include:
1. Collect Lifecycle
2. Calc Lifecycle
3. Pay Lifecycle
4. Lifecycle Status = Collect Lifecycle + Calc Lifecycle + Pay Lifecycle
For example:
- A paid transaction has a status : COLLECT: Collected -> Loaded -> CALC:
Calculated -> Posted -> PAY: Approved -> Paid
- An unpaid commission earning: COLLECT: Collected -> Loaded -> CALC:
Calculated -> Unposted
- A paid manual transaction has lifecycle status: COLLECT: -> CALC: ->
The Oracle Incentive Compensation Command Center feature is available at no

additional cost to licensed users of Oracle Incentive Compensation. It can be applied to
Release 12.2.4 and above.
The following functionality requires Oracle Enterprise Command Center Framework

Release 12.2 V2.
3.3.2. Released 12.2.8+
3.3.2.1. Recent Jobs

Incentive Compensation processing is very job centric. Jobs are kicked off for collection,
for load, for calculation and for creating paysheets.
The Recent Jobs dashboard empowers Sales Plan Administrators and Sales Compensation
Managers with a mechanism to discover the progress or outcome of job processing. You
can analyze data using various metrics, charts, graphs, and tables.
With this actionable dashboard one can quickly identify and drill down into processing
logs, and take appropriate steps to mitigate errored job runs to advance processing of
transactions.
3.3.2.2. Quality by Phase

The Quality by Phase dashboard provides Sales Plan Administrators and Sales
Compensation Managers with complete lifecycle transparency by bringing together
information across all the processing phases of an incoming transaction.
This dashboard enabling the users to drill into the life cycle of the transaction, and to
check for completeness and accuracy or research disputes to resolution.
Oracle E-Business Suite Releases 12.1 and 12.2 Release Content Document Oracle Incentive Compensation Command Center 17
3.3.2.3. Paysheet Console
The Paysheet Console Dashboard provides Sales Compensation Managers visibility into
the Paysheet processing. Metrics across multiple periods and pay runs can be analyzed
using various charts, graphs and tables.
This dashboard enables the users to quickly identify, drill, review and act to advance the
processing of paysheets.
3.3.2.4. Jeopardy by Phase

The Jeopardy by Phase Dashboard provides Sales Plan Administrators and Sales
Compensation Managers visibility into the incentives processing, an insight into the at-risk
commission earnings by processing phase and the compensation administration’s
readiness to pay. Metrics across multiple periods and pay runs can be analyzed using
various charts, graphs and tables.
It enables the users to take corrective action to advance the processing of incentive
payments across each phase and to ensure timely incentive payments.
3.3.3. Released 12.2.9++
The following functionality requires Oracle Enterprise Command Center Release
12.2 V4.
3.3.3.1. Performance Evaluation

The Performance Evaluation Dashboard provides Sales Plan Administrators and Sales
Compensation Managers visibility into the sales attainment and performance across roles,
plans and periods as well as compare sales quotas versus achievement.
3.4. Oracle Incentive Compensation Analytics for Oracle Data Integrator

3.4.1. Overview
Incentive Compensation defines and tracks rewards based on individual and team
achievement relative to corporate performance and profit targets. A key component of
this solution is to help Sales Executives, Finance staff, and Compensation Analysts and
Designers gain insight and visibility into designing and optimizing compensation
solutions to drive stronger performance (top-line growth), while reducing compensation
expenditure (bottom-line growth). This includes:
• Motivating reps with Incentive Insight
• Increased visibility into selling behavior relative to targets
• Increased visibility into compensation plan design to help optimize sales top-line
growth
• Increased visibility into compensation expenditure to help manage bottom-line
growth
This is a classic scenario of moving up the value chain of information, from data to
information that allows for actionable decision. OIC contains valuable data about sales,
territories, quotas, payout information, and we need to provide an infrastructure to allow
customers to move from reporting on their data, to making informed decisions. Allow
them to move from management of plans, to optimization of plans.
Oracle E-Business Suite Releases 12.1 and 12.2 Release Content Document Oracle Incentive Compensation Analytics for Oracle Data Integrator 18
3.4.2. Release 12.1.2
3.4.2.1. Data Schema
A new set of tables are established in the CN schema to support data warehousing of the
transactional tables.
3.4.2.2. ETL scripts
A new set of Oracle Data Integration scripts are used to move the data from the
transactional tables to the warehouse tables.
3.4.2.3. OBI Metadata
The OBI Metadata is defined to make the schema easily understandable to the sales
people, or others who might be creating or modifying in OBIEE Answers.
3.4.2.4. Dashboard for Modeling
A Dashboard is available to compare the results of one plan vs. another, or allows for the
user to group a set of plans called a scenario and compare one scenario with another.
3.4.2.5. Dashboard for other roles Schema
Three other Dashboards have been built for other Roles that use OIC including Sales,
Compensation Analyst and Compensation Managers.
3.4.3. Release 12.1.3
In release 12.1.3 Oracle Incentive Compensation Analytics for ODI leverages OBIEE and
ODI to provide better information to make informed compensation plan decisions.
3.4.3.1. Performance Distribution

In 12.1.3 we are providing two new dashboard reports on the Compensation
Administrators dashboard designed to reflect the performance distribution of a group of
sales people. This distribution curve will allow compensation analysts to compare the
curve of a plan overall. Specifically, it will allow better understanding of the impact of
the plan on commission and transactions amounts.
3.4.4. Release 12.2.4

3.4.4.1. Certification of ODI 11g and OBIEE 11g
As part of continual uptake of the latest technologies available, OIC Analytics is certified
against Oracle Data Integrator 11g and Oracle Business Intelligence 11g in release 12.2.4
3.4.4.2. Mobile Incentive Insight for Payee Community
Sales forces can be motivated with incentive insight on their mobile phones and tablets.
With the certification of OBIEE 11g, all deliverable and configurable OIC Analytic
content can be served up with native iPhone/iPad/Android support via OBIEE. The
Oracle BI Mobile app can be downloaded from the Apple and Google Play store. This
feature is back-ported to 12.1.3+.
3.4.5. Release 12.2.5
3.4.5.1. Payment Fact
In release 12.2 of OIC Analytics, the data schema, OBI metadata and supporting ETLs
have been provided to support the payment fact. The payment fact tracks the payment of
commission earnings. This feature is back-ported to 12.1.3+.
3.4.5.2. Territory Dimension
In release 12.2 of OIC Analytics, the data schema, OBI metadata and supporting ETLs
have been provided to support the territory dimension. The territory dimension maps the
E-Business Suite Territory Manager hierarchy used for sales crediting. This feature is
back-ported to 12.1.3+.
3.4.5.3. Six New Subject Areas
Six new subject areas have been introduced to support analytics in the following subject
areas in addition to the original subject area, Incentive - Earnings. This feature is back-
ported to 12.1.3+.
New Subject Area Description
Incentive – Payments This subject area provides the ability to report on payments by time, salesrep, plan
element (across plans), credit type, pay group, payrun and plan details.
Incentive –Paysheets This is a summary level subject area that provides the ability to report on payments
aggregated across plan element within a paysheet by time, salesrep, plan element
(across plans), credit type, pay group and payrun details.
Incentive –Paysheet This is a plan element level subject area that provides the ability to report on
Subtotals by Plan payments aggregated by paysheet by time, salesrep, plan element (across plans),
Element credit type, pay group and payrun details.
Incentive – Pay This subject area provides the ability to report on pay subledgers by time, salesrep,
Subledgers plan element (across plans), credit type, pay group and payrun details.
Incentive – Plan This subject area has the ability to report plan element subledgers by time, salesrep,
Element Subledgers plan, credit type, pay group and scenario details.
Incentive – Quotas This subject area provides the ability to report on quotas by time, salesrep, plan,
credit type, pay group and scenario details.
3.4.1. Release 12.2.6

3.4.1.1. Certification of ODI 12c and OBIEE 12c
As part of continual uptake of the latest technologies available, OIC Analytics is certified
against Oracle Data Integrator 12c and Oracle Business Intelligence 12c in release 12.2.6.
3.4.1.2. New Commission Reporting for Payees
New sales performance reporting for salespersons and sales managers leveraging the new
UIs afforded by the uptake of the 12c tech stack.
3.4.2. Release 12.2.7

3.4.2.1. Improved ETL Performance For Incremental Calculation Customers
Sales forces want timely sales performance and incentive reporting. Improved ETL
performance reduces this time window.
Many OIC customers run calculation in incremental mode rather than full calculation. In
incremental calculation, OIC attempts to selectively identify affected transactions and
only recalculate those. Clearly, OIC Analytics is a downstream process to this. In place
of selective deletes and inserts, a partition strategy for the Earnings fact by period
introduced in 12.2.7 improves ETL performance.
3.5. Oracle Incentive Compensation Information Discovery

3.5.1. V6 (New Application introduced in V6)
3.5.1.1. Quality Assurance for OIC including Dispute Resolution

Compensation administrators are responsible on a monthly/periodic basis for getting a set
of transactions through collection, calculation and pay processes. Validating these
transactions have been correctly processed across each stages is integral to comp admin;
and necessitates taking corrective actions where appropriate. A comp admin group will
have many of these processing channels all going on at once, so ensuring the
completeness and accuracy is not always a simple task.
As volumes are larger than what one can manually review, most customers generate BI
Publisher or OBIEE reports to capture well defined exceptions. This implies already
knowing the exception criteria but does not help to 'discover' new exceptions and criteria.
OIC Information Discovery can empower 'discovery' in a manner that traditional

reporting and analytic tools cannot. The OIC Information Discovery provides built in
configurable quality management functionality within OIC processing.
There are 4 dashboards: Recent Jobs, Quality by Phase, Jeopardy by Phase, and Paysheet
Console. The Quality by Phase Dashboard also facilitates faster dispute resolution.
3.5.1.2. Lifecycle Statuses

OIC Information Discovery enriches transactions with lifecycle attributes that combine
multiple statuses to reflect what has how a transaction has been processed in OIC. There
are four lifecycle attributes; one for each for collect, calculate and pay phase; and a single
concatenated lifecycle status across all phases.
Lifecycle attributes include:

• Collect Lifecycle
• Calc Lifecycle
• Pay Lifecycle
• Lifecycle Status = Collect Lifecycle + Calc Lifecycle + Pay Lifecycle
Oracle E-Business Suite Releases 12.1 and 12.2 Release Content Document Oracle Incentive Compensation Information Discovery 21
For example:
A paid transaction has lifecycle status: COLLECT: Collected -> Loaded -> CALC:
A paid manual transaction has lifecycle status: COLLECT: -> CALC: -> Calculated ->
Posted -> PAY: Approved -> Paid
An unpaid commission earning: COLLECT: Collected -> Loaded -> CALC: Calculated
-> Unposted
3.5.1.3. Recent Jobs Dashboard

As a Compensation Manager or Compensation Analyst responsible for day to day
compensation administration, it is critical to see where we are with most recent
processing jobs for current period(s), drilldown to logs or related transactions and launch
additional batch or online processing.
The Recent Jobs dashboard provides discovery into the progress/outcome of job
processing.
3.5.1.4. Quality by Phase Dashboard

As a Compensation Manager or Compensation Analyst, I need to validate the
completeness and accuracy of each phase of incentive processing (Collection,
Calculation, Pay) before moving on to the next. That is difficult as current UIs are siloed
by phase. As Compensation Analyst, I need to research disputes to resolution.
The Quality by Phase dashboard ensures completeness/accuracy and brings together
information related to an incoming transaction across all phases of calculation. OIC
Information Discovery also introduces phase oriented statuses (one for each phase) and a
concatenated single Lifecycle Status to quickly provide transparency into how a
transaction has made its way through OIC processing.
3.5.1.5. Faster Effective Dispute Resolution

Every comp administration group must handle disputes logged by the payee community.
The same Quality by Phase dashboard brings together all related information for a
transaction under dispute and eliminates silos traditional imposed by OIC phase.
Compensation Analyst are quickly and effectively able to determine the cause and scope
of a dispute and understand if the dispute represents the tip of an iceberg or who else may
be affected to take early corrective action if necessary.
3.5.1.6. Jeopardy by Phase Dashboard

As a Finance Manager or Compensation Manager responsible for paying incentives on
time, they are always trying to determine if incentives processing is on schedule to
complete on time; and take corrective action if necessary.
The Jeopardy by Phase dashboard answers will we pay on time and provides insight into
where processing is relative to calculated earnings. This dashboard is critical to proactive
elimination of obstacles so incentive payments will be on time.
3.5.1.7. Paysheet Console

As a Compensation Analyst/Manager responsible for payment processing, I need to see
how paysheet processing is progressing for current period(s), review paysheets, how
many outstanding paysheets assigned to which analysts, and eventually take action to
advance processing in OIC.
The Paysheet Console purpose is to provide visibility to paysheets across multiple
payruns and provide a launch point for taking action to advance paysheet processing.
Oracle E-Business Suite Releases 12.1 and 12.2 Release Content Document Oracle Incentive Compensation Information Discovery 22
3.5.2. V7
3.5.2.1. Support for Pay by Transaction Mode OIC Customers

In Release V6 (12.2.5) we introduce the new OIC Information Discovery that provides
built-in quality assurance processes and actionable dashboards into OIC processing.
With the second release of OIC Information Discovery in V7 (12.2.6), it will support OIC
customers operating in pay by transaction mode.
3.5.2.2. Enhanced Usability with Dashboard Metrics

Metrics in dashboards have been enhanced with drilldown capabilities that:
• Automatically add filters/refinements for better visibility into metric related data
• Automatically show specific tab content for better visibility into metric related
data
This will provide comp administration with better usability and more insight.
OIC Information Discovery will be utilizing this to quickly filter for
earnings/commissions not equal to zero.
3.5.3. V8
3.5.3.1. Improved ETL Performance

In Release V8 (12.2.7) we improved the performance of the ETLs.
3.5.3.2. Support for Wildcard Search

In Release V8 (12.2.7) we uptake support for wildcard searches. Out of the box we will
support wildcard searches for :
• Plan Element name
• Product name.
Often customers will have Plan Element names for a category of products but for
different roles in the sales organization. For example they will create plan elements for
PreSales Hardware, PreSales Software, Territory Rep Hardware, Territory Rep Software.
In researching how transactions are commissioned across different roles it is useful to be
able to identify transactions for hardware across plans & plan elements both in the
context of transactions and the plans people have. This can be achieved by implementing
partial search for plan elements so an analyst can search on ‘Hardware’. This is
important in the context of plans and earnings & payments.
The same is true of Product names which may have classification abbreviations
embedded in their naming.
3.6. Oracle Marketing

3.6.1. Overview
Oracle Marketing provides a comprehensive approach to enterprise-wide marketing
communications management. With emphasis on improving marketing operational
efficiency, aligning marketing and sales initiatives, providing key customer insight and
Oracle E-Business Suite Releases 12.1 and 12.2 Release Content Document Oracle Marketing 23
enabling marketing measurement and accountability, Oracle Marketing empowers
organizations to focus marketing resources on the most valuable opportunities.
3.6.2. Release 12.1.1
3.6.2.1. Data Source Refresh
Data sources are a fundamental component of the list management process. They provide
the end user view on customer data. Data sources are generally derived from a schema
table or view and are used extensively in a number of marketing processes.
Data sources determine:
• Attributes available to the end user during list or segment creation
• 3rd party / External data import mapping to the TCA schema
• Data to be stored and displayed in the AMS_LIST_ENTRIES table
• Attributes available for List splitting
• Query Template Creation
• Attributes available for Charting
• Attributes available for De-duplication rules
• Attributes available for Data Mining
Oracle Marketing Release 12 allows the creation of a data source based on either a TCA
or Non-TCA schema table or view. However, once the data source is created, any
modifications or changes in the underlying TCA or Non-TCA schema table or view are
not reflected in the data source.
To see the modifications, the Marketing end user currently has to re-create or duplicate
the existing data source to add the new attribute. This can be very time consuming if, for
example, the data source has say 200 columns. Additionally, there is no functionality to
delete redundant data sources.
A REFRESH button will be added to the UPDATE DATA SOURCE UI. When the
refresh button is CLICKED, the underlying Table or View will be checked for NEW
COLUMNS ADDED since the Data Source was CREATED or LAST REFRESHED.
NEW Columns found by the refresh will be displayed in the correct alphabetical position
within the Data Source Attribute UI.
This enhanced functionality provides the following business benefits:
• Reduction in Time / Resource due to re-creation of data sources
• Reduction in Time / Resource in maintaining data sources
• Reduction in number of redundant data sources.
3.6.2.2. Extend Gantt Chart Functionality to Include Programs
When preparing the annual marketing plan, marketers generally start with planning the
primary marketing hierarchy object, the Program. A Program is an umbrella object used,
ultimately, to combine different marketing objects such as Campaigns, Activities, and
Events under one entity.
Oracle Marketing Release 12 currently only displays Campaigns and Activities in the
Campaign Workbench Gantt Chart (Marketing Calendar). The primary object for the
Marketing hierarchy, the Program, cannot currently be displayed in a Gantt view.
Programs are only visible in the old JTF folder hierarchy view and drill-down
functionality from Programs in the old user interface only extends to the Campaign and
not to the Activity object.
The Campaign Workbench Gantt view functionality has been extended in 12.1.1 to
include the primary marketing hierarchy object, the Program, and provide the required
drill-down functionality to both the Campaign and Activity objects. This enhanced
functionality provides the following business benefits:
• The Marketing end user will be able to view the complete marketing plan from
Program, to Campaign, to Activity from within the Campaign Workbench Gantt
view.
• End users will no longer need to navigate to two different user interfaces.
• End users can drill down from Programs to Campaigns and Activities.
3.6.2.3. Gantt Chart Functionality Date Display
A fundamental requirement of any marketing application, particularly if deployed in a
B2C organization, is the ability to view all marketing activities within a user-defined
timeline. Looking at lists of activities and having to drill into each one to find the activity
start and end dates is not efficient.
Oracle Marketing Release 12 does allow marketers to create user-defined searches based
on date, for example ‘Show Activities between 01-Dec-2007 and 31-Dec-2007.’ The
marketer can then go to the Gantt view which provides a clear visualization of these
activities.
However, there are inconsistencies in the way Release 12 behaves. Some examples of the
date inconsistencies are as follows:
• Campaign Search By Date returns a fixed timeframe of 2000 to 2010
• Year Dates are repeated in Columns e.g. 2007 and ‘07
• No year is shown for Month searches
• Only the Day, for example M, T, W, T etc., is shown for Week searches; not
Date
In Release 12.1.1, the Gantt chart functionality will ensure that all Gantt views for
Programs, Campaigns and Activities display the Dates in a consistent format. Also, all
user-defined searches will return the results as per the specified time frame. This
enhanced Gantt view functionality provides the end user with the following business
benefits:
• Reliable results
• Improved end user experience
• Increased end user satisfaction
• Less time and fewer resources used when preparing marketing plans
3.6.2.4. Creation of ‘List at Time of Import’ as Default
Many Marketing departments rely heavily on externally-sourced customer or prospect
data. Oracle Marketing Release 12 allows 3rd-party and externally-sourced customer or
prospect lists to be imported. During the import process, the end user is presented with
the option to ‘Generate a list upon import’. If this option is checked, a marketing list will
be generated automatically, without the need for any further processing, and this list can
then be associated to a single or multiple marketing activities.
Approximately +95% of imported lists are used for marketing activities. The current
default however is to NOT ‘Generate a list upon import’. Some customers import
between 200 and300 lists a month for use with a marketing activity. If they forget to
check the ‘Generate a list upon import’ option, they must re-import and re-generate the
lists which is both time consuming and prone to errors.
The ‘List Import’ functionality will be modified in Release 12.1.1 to set the ‘Generate a
list upon import’ check box to YES as the default. This enhanced functionality provides
the following business benefits:
• +95% of Imported Lists the ‘Generate a list upon import’ default will now be set
to the correct value, i.e. YES.
• Administrative time and resources required for re-work will be reduced.
3.6.2.5. List Import Organization and Contact Address Existence Checking
Many Marketing departments rely heavily on externally sourced customer or prospect
data. Oracle Marketing Release 12 allows 3rd-party and externally-sourced customer or
prospect lists to be imported. During the import process Existence checking determines
the following:
• Does Organization Name exist
• Does Organization Address exist
• Does Organization Contact Name exist
• Does Organization Contact Address exist
The requirement from a business perspective is to:
• Create the Organization, where it does not already exist
• Add the Primary Organization address
• Add Organization Contacts
• Add Organization Contact Addresses
Business Scenario:
Assuming the Import file includes nine records for Organization and Contact details for a
new Organization.
The Import process should create the following:
• 1 New Organization Record
• 1 New Organization Primary Address (Assuming the Organization address is the
same on each record within the file)
• 9 New Contacts and their contact addresses
However the current functional code creates the following:
• 1 New Organization Record
• 1 New Organization Primary Address
• 8 Duplicate Organization Addresses
• 9 New Contacts and their contact addresses
The eight duplicate organization addresses are created because the current functional
code only checks the existence of the Organization Address the first time it finds the
Organization Name in the import file. If the organization address is contained in the file
against each additional Contact record, no further check is carried out so the duplicates
are created.
The current ‘List Import’ existence checking functional code will be modified to check
every record within the Import file prior to the creation of the Organization Address.
• Eliminate the creation of duplicate Organization Addresses
• Reduce the administrative time and resources used to maintain Address
information
3.6.2.6. Modification of List Splitting by User Defined Attribute
Data sources are a fundamental component of the customer and prospect list management
process; they provide the end user view on customer data. Data sources are generally
derived from a schema table or view and are used extensively in a number of marketing
processes to:
• Define the Attributes available for List Splitting
• Define the Attribute Values to be used for the List Split
Oracle Marketing Release 12 allows the end user to take a ‘Single’ marketing list and
split it into ‘Multiple’ marketing lists based on any of the data attributes, previously
defined as ‘Used for Splitting’ within a data source.
However, the current List Splitting process is time consuming, difficult for administrators
to maintain, and prone to errors when creating the required splits. It is also highly
inefficient when processing the List Splits due to the way it currently derives the attribute
values to be used for the splits.
To determine attribute values to be used for say a COUNTRY split; it looks at
FND_TERRITORIES_VL, which contains around 246 values. However, if the actual list
contains only say 3 countries, the 246 Countries are still displayed to the end user in the
List Split UI, which is confusing. Additionally when the list is processed, it still does it
on the basis of 246 possible country values being present. After initial processing Lists
containing 0 (ZERO) customers are not physically generated. This means 243 redundant
list are deleted and the actual time taken for a list split is much longer than it should be.
The current List Splitting functional code will be modified to pick up the actual
Generated List Attribute Values, from the AMS_LIST_ENTRIES table and not the EBS
FND_LOOKUP tables or views.
Based on the PROPOSED FUNCTIONAL CODE, the list splitting would now process
the country split based in this example on the 3 countries below:
• UK
• France
• Germany
As these are the three country code values found within the ‘Single List’ created earlier
and stored in the AMS_LIST_ENTRIES table.
• Elimination Confusion for the End User, being presented with additional values
for split they know are not contained in the ‘Single List’
Reduction in the processing time for List Splits
• Reduction in administrative Time / Resource maintaining Lists
3.6.2.7. Include Tasks when Copying Campaign Objects
Marketing activities tend to be very similar year-on-year, with only very minor changes
required for:
• Introduction of New Products.
• Date Changes e.g. Easter, Christmas
• New markets
It is a common marketing requirement to be able to copy this year's marketing activities
and re-use them, with minor tweaks, next year.
Business Scenario
When a marketer sets up a marketing activity, for example direct mail, there will be many
tasks that need to be set up and monitored for this activity, as generally direct mail
requires collaboration with 3rd-party agencies or bureaus. Typical tasks would be:
• Initial Meetings to decide on Agency / Bureau
• Meetings with Agencies to discuss deployment schedule
• Meetings with Agencies to design Collateral
• Monitor Collateral progress
• Ensure Collateral delivered
The number of tasks that need to be created for a complex activity could be in the 100’s.
Oracle Marketing Release 12 allows the end user to copy existing marketing objects—
Programs, Campaigns, Activities and Events. However, the current copy functionality
does not extend to Tasks associated with the objects. This means that every time a new
Activity is set up, all associated Tasks for that Activity need to be re-created.
The current Copy Program, Campaign, Event and Activity functional code will be
extended to include Tasks. This will allow the creation of standard Program, Campaign,
Event and Activity templates containing all the required Tasks. These Templates can then
be used to easily and quickly create NEW marketing objects.
• Standard templates can be created for marketing objects
• New Marketing Object creation is faster
• All required Tasks are copied – none are forgotten
• New Marketing employees can see all the required tasks associated to objects.
• Reduction in administrative Time / Resource maintaining marketing objects
3.7. Oracle Partner Management

3.7.1. Overview
Oracle Partner Management efficiently manages the entire partner lifecycle—from
recruiting and managing partners through marketing, channel sales and performance
measurement. Partner Management gives you the tools and processes you need to align
sales efforts across channels, reduce partner management costs, and monitor and improve
channel performance.
Oracle E-Business Suite Releases 12.1 and 12.2 Release Content Document Oracle Partner Management 28
3.7.2. Release 12.1.1
3.7.2.1. Additional Partner Profile Attribute Security
The current Oracle Partner Management functionality allows vendors to deploy seeded or
defined custom partner profile attributes. These attributes are managed via the Channel
Administrator responsibility via the Channel Administration Dashboard
The purpose of the profile attributes is to allow the Vendor to capture additional
information about the partner. However, if the profile attributes are exposed, Oracle
Partner Management Release 12 allows all end users to View and Update the profile
attribute values.
The Vendor requires additional security, for the profile attributes, to provide the
following:
• Allow attributes to be hidden from Vendor Channel Managers and Partners
• Allow Vendor Channel Managers and Partners Update access to attributes
• Allow Vendor Channel Managers and Partners Read Only access to attributes
This solution will require the creation of a New Profile Option to allow the Vendor
(Customer) to Turn On or Turn Off the additional Profile Security. For example:
• PV: Use Profile Attribute Security
The creation of 2 New Permissions:
• PV_ PARTNER_UPDATE_PROFILE
• PV_ PARTNER_VIEW_PROFILE
Currently there are 5 seeded Roles that are extensively used by existing customers:
• Vendor Channel Administrator
• Vendor Channel Manager
• Vendor Channel Representative
• Partner Primary/Admin User
• Partner Business/Secondary User
The Vendor (customer) may also want to define NEW ROLES to suit their business
processes and add the appropriate Update or View Only Permissions to those NEW
ROLES for example:
• Vendor Channel Manager – Update
• Vendor Channel Manager – View
• Vendor Channel Representative – Update
• Vendor Channel Representative – View
• Partner Primary/Admin User – Update
• Partner Primary/Admin User – View
• Partner Business/Secondary – Update
• Partner Business/Secondary – View
Each of the above ROLES would have the appropriate Update or View Permission
assigned to them, for example:
Oracle E-Business Suite Releases 12.1 and 12.2 Release Content Document Oracle Partner Management 29
• Partner Primary/Admin User – Update
(Assigned PV_ PARTNER_UPDATE_PROFILE Permission)
• Partner Business/Secondary – View
(Assigned PV_ PARTNER_VIEW_PROFILE Permission)
The proposed solution also involves the following:
The Modification of the existing R12 Channel Administration “Create Profile Attribute”
process in the following manner:
• Addition of ‘Update Attribute’ and or ‘View Attribute’ ROLE selector within
the Attribute Details UI
The Modification of the existing R12 Channel Administration “Update Custom Profile
Attribute” process in the following manner:
• Addition of ‘Update Attribute’ and or ‘View Attribute’ ROLE selector within
the Attribute Details UI
• Vendor control of visibility of ‘Sensitive’ profile attributes
• Vendor control of profile attribute update
• Tighter control of Partner Profile data capture
• Reduction in administrative Time / Resource maintaining Partner Profile
Attributes
3.8. Oracle Proposals

3.8.1. Overview
Complete, consistent, and professionally formatted proposals are crucial to closing sales
opportunities and winning deals. Yet creating proposals offline in a word processor is
sometimes laborious, repetitive, and often produces inconsistent results. Oracle Proposals
seamlessly integrates the proposal creation process into your sales business workflow by
automating routine standard tasks and providing consistent content. The software creates
proposals online from reusable templates, and saves even more time by automatically
transferring previously collected information into the proposal. With Oracle Proposals,
businesses can shorten the sales cycle by reducing the time taken to generate a proposal
from days to hours, thus projecting a consistent and high quality professional image to
customers, and also give Sales representatives more time to work with customers by
making the proposal generation process easier, faster, and more efficient.
3.8.2. Release 12.1.1
3.8.2.1. Addition of External Email Addresses
Many times, a Sales representative needs to send a proposal to external people outside of
their customer’s usual contact list. In the current application, sales users are able to select
contact addresses only from customer’s pre-defined contact list in the “To” and “CC”
fields. This requires that the sales user must add all e-mail recipients to their customer’s
contact list ahead of time so that recipients can only be selected from a list.
The restriction of selection based on current customer’s contact list is being removed
with this new feature. The sales user will now be able to enter external addresses by
typing directly in an additional “To / CC” field in a free-form fashion, removing the
Oracle E-Business Suite Releases 12.1 and 12.2 Release Content Document Oracle Proposals 30
restriction to only select a customer contact email address from a pre-defined list of
values.
The original feature of selecting email from customer’s contact list is still being retained,
as well as the capturing of the email interaction history. This will enable users to send a
proposal to any required individual without the need of adding them to the customer’s
contact list.
3.8.2.2. “Freight Terms” as Seeded Field
It is very common to use Freight Terms as defined in a sales quote within proposal
documents. In the current application, displaying the freight terms from a given quote
requires a product customization.
The ability to include Freight Terms as a standard available field is being added with this
new feature. As part of this enhancement, a new field will be seeded allowing the sales
user to associate the value for Freight Terms in a proposal document.
The new dynamic field called “Freight Terms” is being made available so that sales users
can include this additional field in any proposal template, and its value will be populated
automatically from other applications such as Oracle Quoting.
3.9. Oracle iStore

3.9.1. Overview
Oracle iStore is an electronic commerce application that enables companies to build,

manage, and personalize powerful, global and scalable Internet storefronts. Oracle iStore
may be used in Business-to-Business (B2B), Business-to-Consumer (B2C) and Partner
selling models. With seamless integration to Oracle's CRM and ERP applications, Oracle
iStore provides complete order and inventory management, and enables the execution of
the sales process, from lead generation to post-sales support.
For more information, refer to the “Oracle iStore” section in the Order Management
Release Content Document.
3.10. Oracle iStore Information Discovery

3.10.1. Overview
Oracle iStore Information Discovery provides users with a robust search tool to
supplement the existing Basic and Advanced search functionality in iStore. It enables
users to search on customer part number, cross reference part number and locate products
easily with auto-suggested searches. Oracle iStore users can also filter on price ranges,
perform product comparisons to highlight product differences, and export search results.
It also provides sophisticated guided navigation to product information, thus enabling
shoppers to easily choose the “right” product when making purchasing decisions. Lastly,
it delivers an intuitive interface that streamlines the buying process and enhances the
customer usability experience.
For more information, refer to the “Oracle iStore Information Discovery” section in the
Order Management Release Content Document.
Oracle E-Business Suite Releases 12.1 and 12.2 Release Content Document Oracle iStore 31
3.11. Oracle Quoting
3.11.1. Overview
Oracle Quoting is the sales application that automates and manages the entire quoting
process. Oracle Quoting is a key component of the Oracle Customer Relationship
Management solution, the integrated suite that drives profitable customer interactions.
3.11.2. Release 12.1.2
3.11.2.1. Quoting of Services to End Customer (Forms UI only)
3.11.2.1.1. Service reference for serviceable item in the Install Base for the End
Customer
In a business relationship where a company sells to a distributor who ultimately

resells an item to an end user, there is a need to quote a service contract to the end
user. Currently, the service reference for a serviceable item in the Install Base must
be owned by the Sold To customer on the quote. This does not work well for reseller
scenarios where the Sold To Customer is not the same as the End Customer. The
item in the Install Base is associated with the End Customer not the Sold To
Customer. This enhancement allows the Quoting user to specify a service reference
for a serviceable item in the Install Base for the End Customer on the quote.
3.11.2.1.2. Allow Service item to point to a serviceable item in the product catalog
In Quoting, you can quote a service long after the original purchase. In such a
scenario, the service item on the quote must point to the serviceable item in the
Install base. In reseller scenarios, there is a need to create separate quotes, one quote
for the serviceable item and a second quote for the service item. Each of the two
quotes may be created by different resellers. Since the first quote has not been
fulfilled, the service item on the second quote cannot reference the serviceable item
in the Install Base. This enhancement allows the service item to point to a serviceable
item from the Product Catalog. The service item can be priced based on the price for
the serviceable item in the Product Catalog. After the order for the first quote is
fulfilled, the second quote is changed so the service item points to the serviceable
item in the Install Base. Subsequently, the second quote can be placed as an order.
3.11.3. Release 12.1.3

3.11.3.1. Configurator enhancements (HTML UI only)
Currently, the effective date for a model configuration in the quote is the creation date of
the model configuration and cannot be changed. The creation date of a model
configuration is the date when the model was initially configured in the quote.
Subsequently, if there are changes to the configuration rules or the Bill of Materials for
the model item, then these changes are not available when the user reconfigures the
model item. This enhancement allows the effective date to be the current date or the
creation date of the model configuration. Additional flexibility is provided for customers
who wish to write their own rule for determining the effective date. Users can also
manually check the validity of the model configurations in the quote during the quote
lifecycle.
Oracle E-Business Suite Releases 12.1 and 12.2 Release Content Document Oracle Quoting 32
3.11.3.2. Usability enhancements (HTML UI only)
3.11.3.2.1. Amend the “Quote To” Customer on the quote
Currently, you cannot change the “Quote To” customer after the quote is created. The
Quoting user may have initially created the quote for one “Quote To” Customer and then
subsequently realized that the “Quote To” Customer was incorrect and needed to be
changed. This feature allows you change the customer on an existing quote without
having to start a new quote for the revised “Quote To” Customer.
3.11.3.2.2. Copy quote enhancements
Currently, users do not have flexibility to choose the attributes that should be copied from
the existing quote to the new quote. They cannot copy the existing quote for one
customer to a different customer. This enhancement allows users to copy a quote to a
customer different from that on the original quote. The user can also specify which quote
attributes should be copied to the newly created quote.
This feature saves time when creating an identical quote for a different customer. It also
saves time if you are creating a similar (but not identical) quote for a different customer.
Additionally, the user will be able to choose which quote attributes should be copied to
the newly created quote.
3.11.3.2.3. Create Quote template from a quote
Currently, users can apply multiple quote templates to a quote but cannot create a quote
template from a quote. Quoting users often need to reuse quote configurations created for
one customer and apply it to other customers. The quote template repository provides a
way to reuse quotes and reduces the time needed to configure identical quote
configurations. Thus if a particular large or complex model configuration on a quote
could be used for other customers, then the corresponding quote could be copied to a
quote template. This quote template can be subsequently applied to other quotes.
3.11.3.2.4. Apply quote templates from different operating units
Quotes and quote templates are inherently striped by the operating unit. Currently, the
quoting user cannot apply a quote template from an operating that is different from the
quote operating unit. This enhancement removes this restriction and provides a larger
library of quote templates to choose from. This promotes better reuse of the quote
templates.
3.11.3.3. QA Check framework (HTML UI only)
Currently, quoting validates the quote prior to quote transitions such as approval
submission and place order. Users cannot easily add custom validation checks prior to the
key quote transitions. The QA Check framework allows business process owners to
define custom business rule validations that need to be automatically performed prior to
key quote actions. Based on the outcome of the business rule validations, the user is
either allowed to perform the quote action or prevented from doing so. The quoting user
can also manually invoke the QA check during the quote lifecycle to preemptively fix
any errors prior to the automatic validation checks.
3.11.3.4. Quoting of Services to End Customer (HTML UI)
3.11.3.4.1. Service reference for serviceable item in the Install Base for the End
Customer
In a business relationship where a company sells to a distributor who ultimately

resells an item to an end user, there is a need to quote a service contract to the end
user. Currently, the service reference for a serviceable item in the Install Base must
be owned by the Sold To customer on the quote. This does not work well for reseller
scenarios where the Sold To Customer is not the same as the End Customer. The
item in the Install Base is associated with the End Customer not the Sold To
Customer. This enhancement allows the Quoting user to specify a service reference
for a serviceable item in the Install Base for the End Customer on the quote.
3.11.3.4.2. Allow Service item to point to a serviceable item in the product catalog
In Quoting, you can quote a service long after the original purchase. In such a
scenario, the service item on the quote must point to the serviceable item in the
Install base. In reseller scenarios, there is a need to create separate quotes, one quote
for the serviceable item and a second quote for the service item. Each of the two
quotes may be created by different resellers. Since the first quote has not been
fulfilled, the service item on the second quote cannot reference the serviceable item
in the Install Base. This enhancement allows the service item to point to a serviceable
item from the Product Catalog. The service item can be priced based on the price for
the serviceable item in the Product Catalog. After the order for the first quote is
fulfilled, the second quote is changed so the service item points to the serviceable
item in the Install Base. Subsequently, the second quote can be placed as an order.
3.11.4. Release 12.1.3+

3.11.4.1. Quote Purge
3.11.4.2. Gross Margin Computation (HTML UI only)

3.11.4.3. Reuse Credit Card (HTML UI only)
This feature allows the user to view previously saved credit cards associated with the
Bill-To customer. Subsequently, the user can select a credit card from the list and apply it
to the quote/quote line. This will save time as the user does not have to repetitively enter
the prior credit card details for each quote. Expired, inactive, single use, information only
and invalid credit cards are excluded from this list.
This feature is forward-ported to 12.2.5.
3.11.5. Release 12.2

3.11.5.1. Configurator enhancements (HTML UI only)
3.11.5.1.1. Separate Configurator session
Currently, the Configurator UI is embedded within a region inside the HTML

Quoting page. This takes away some vertical screen real estate from the Configurator
UI. Going forward, the Configurator session will be launched in a separate page that
is wholly dedicated to the configuration of the model item.
This enhancement provides several business benefits. The entire real estate on the
quoting page is used for the Configurator session minimizing or possibly eliminating
the vertical scrolling. The Quoting and Configurator sessions can be run in separate
individually optimized Java Virtual Machines (JVM). This architecture allows the
Java Virtual Machines for the Quoting and Configurator sessions to be tuned
independently of each other improving the scalability and performance of the
memory intensive Configurator session.
3.11.5.1.2. Pass custom parameters
You can pass custom parameters from the Quoting session to the Configurator
session using a hook. The custom parameters can be used as inputs when building the
configuration rules for the model. For example, the Ship To Country in the Quote
could be passed to the Configurator session to help choose the country specific power
cord when configuring a desktop computer. Additionally, the out of the box
initialization parameters for Configurator can also be passed via the hook, overriding
the parameter values passed by the Quoting application.
3.11.5.2. Quoting to Prospects

Currently, you can choose when the financial account should be automatically created for
the prospect customer in the Quote. Based on a profile option, Quoting will automatically
create the financial account when the prospect customer is selected, when web publishing
the quote or when placing the quote as an order. However, you do not have the option to
completely turn off the automatic creation of the financial account.
This enhancement provides the flexibility to completely turn off the automatic creation of
financial account for the prospect customer in the quote. In this quote scenario, the quote
cannot be web published or placed as an order. After the financial account is created in
Oracle Receivables, the quoting user can select that account and proceed with the quote
functions that require a financial account.
3.11.5.3. Parallel Approvals (HTML UI only)

Currently, the quote approvals functionality uses Oracle Approvals Management (AME)
to determine who should approve the quote based on the quote attribute values,
conditions, approval types and approval groups. The approvers have to approve the quote
in sequence (one after another).
In this release, Quoting has re-architected the integration with AME to leverage the latest
capabilities of the approval rules engine. This includes the ability for multiple approvers
to concurrently review and approve the quote. Approvers in a group can now
simultaneously review and indicate their approval after completing the review. This
expedites the overall approval process and enhances the approval efficiency.
Business users can also create approval rules with For Your Information (FYI)
notifications sent to approvers who can review the quote but do not need to
approve/reject the quote approval.
3.11.6. Release 12.2.4
3.11.6.1. Gross Margin Computation (HTML UI only)

Quoting will display the unit cost, margin amount and margin percent for the products in
the quote. It will also display the cost, margin amount and margin percent at the quote
level. The margin percent can be computed based on either the selling price or cost.
Additional flexibility is provided for customers who wish to use legacy applications to
compute cost and margin information.
Business rules can be setup to include approvers based on the quote margins. The QA
check feature can be used to warn the user if the quote margins are outside the established
limits at the product and the quote levels.
3.11.6.2. Item Orderability (HTML UI only)

Businesses need the ability to define which customers are allowed to order which
products, and the ability to apply the business logic when the quote is created. For
example, Customer A may purchase all items except for repair parts and promotional
items. Alternately, Customer B buys only repair parts from you. This new feature in
Quoting leverages the Item Orderability rules setup in Order Management and provides
users with a way to enforce business rules for ordering products. Based on the Item
Orderability rules defined in Order Management, the user will be able to restrict the
products that can be added to the quote.
3.11.6.3. Add Product Pop-up (HTML UI only)

Currently, the user has to search for each product they wish to add to the quote. This can
get cumbersome due to the excessive number of clicks needed to finish adding the
products to the quote.
The new feature allows users to quickly add products to the quote using a pop-up page.
The user specifies the product (part #) in a grid table and tabs out. The product
description is filled in; the primary UOM and quantity are defaulted in the UI. The user
can also specify the price list for each of the products prior to adding it to the quote.
Thus, this feature streamlines the process of adding products to the quote.
3.11.6.4. Update Quote Line (HTML UI only)

Currently, the process to update multiple quote lines is cumbersome as it involves
navigating to the respective quote line and subsequently updating it. The new approach
allows the user to navigate to a quote line by searching for it using the quote line number,
product (part#) or description. The quote changes are automatically saved when
navigating from one quote line to another, thus preserving the line context. For example:
the user can update quote line flexfields by searching for the respective quote lines and
remaining on the quote line flexfield region. This improves the usability when updating
quote line attributes for multiple lines.
3.11.6.5. Quote Purge
This feature allows the user to purge quotes and the related entities if it meets the user
specified purge criteria. The purge process is a two step process. The first step is to
identify the candidate quotes that will be purged based on the purge criteria. Customers
can also use the provided hook to identify the candidate quotes to be purged. The user
can review the candidate quotes and archive them if needed. The archival step is optional
and is managed by the customer implementing Quoting. Subsequently, the quote purge
process deletes the candidate quotes and the related entities. The performance for the
active quotes will be improved and space used by the purged quotes can be repurposed.
This feature can also be used to purge shopping carts created in Oracle iStore.
3.11.7. Release 12.2.5
3.11.7.1. Add Product Enhancement

Currently, you must specify the internal part number when searching for a product to add
to the quote. With this enhancement, you can search for products in one of three ways:
• Customer Part Number
• Cross Reference Type and Cross Reference Part Number
• Internal part number setup in the product catalog
This feature provides the quoting user more flexibility while adding products to the
quote. The Customer Part Number allows users to use the customer specific part numbers
instead of the internal part numbers. The Cross Reference Type and Cross Reference Part
Number allow users to use an alternate means to reference the items in the product
catalog.
3.11.7.2. Quote Validation Framework (HTML UI only)

Currently, the QA check feature in Quoting allows users to enforce business rules on the
quote during the quote lifecycle. If the QA check indicates an error, then the user has to
take corrective action to proceed. The results of the QA check are not persisted in the
quote.
The quote validation framework provides an infrastructure for customers to put in their
business rule validations. It uses EBS workflow technology to automate and streamline
quote validations. It can be setup to route notification requests as needed to address the
quote validations at the quote header and line levels. The quote line validation workflow
processes can run concurrently and independently of one another. The results of the quote
validation are persisted in the quote lines allowing users to track the status for each quote
line.
3.11.8. Release 12.2.6
3.11.8.1. Mobile Quote Approvals

Oracle Mobile Approvals for Oracle E-Business Suite is a smartphone application that
lets employees and managers respond on-the-go to pending approval requests. From their
phone, anywhere and anytime, employees and managers can take quick action on
approval requests for quotes, expenses, requisitions, purchase orders, recruitment
vacancies and offers, and more.
Sales representatives, Sales Managers and other quote approvers can quickly filter quote
approval requests by sender or subject, review header and line details, action history and
comments, and respond back with their approval or rejection, right from their
smartphone. This will be a big timesaver for the quote approvers as they can action the
approval request from their mobile device.
For a full description, refer to the E-Business Suite Applications Technology Release
Content Document.
3.11.8.2. Specify the Quote Selling Price (HTML UI only)

Currently, you can change the selling price at the quote line level by specifying a
discount percent or discount amount. However, you can only specify a discount percent
at the quote level. The discount percent at the quote level applies to the total list price. By
not being able to specify a discount amount or selling price at the quote level, it is not
possible to easily set the desired selling price for the quote.
Going forward, the user can specify the desired selling price for the quote. This provides
additional pricing flexibility to the quoting user during the sales negotiation process. The
desired selling price will not include the applicable tax and freight charges as they are not
included in the computation of the selling price.
3.11.8.3. Document Approvals using Electronic Signatures (HTML UI only)

The Ordering Document Approvals integration helps sales reps track ordering documents
sent to their customers. This feature provides an integrated and digital solution that
simplifies operations and reduces manual errors when managing quote document
signatures. The framework provides an integrated sales and document solution that
ensures compliance with business practices and legal standards. Sales teams can use this
feature to replace slow, manual-intensive contract workflow processes with more
streamlined electronic ones and reduce the time they spend preparing, sending, and
following up on contracts for signatures.
This feature also supports manual processes for sending and receiving ordering
documents via email.
3.11.8.4. Service Items in Configurator UI (HTML UI only)

In order to specify service items for a component included in a model configuration, the
user has to first select the component from the Configurator UI, return to the Quoting UI
and then select the service item for that component.
Going forward, quoting users can choose service items for a component of a model
configuration when selecting the component in the Configurator UI. Thus, the user can
select both the component and the associated service item for it at the same time in the
Configurator UI. The service item is a component of the Bill of Materials for the top level
model item.
3.11.8.5. Update Prior Quote Version (HTML UI only)

Currently, if a quote has multiple versions, the users can only update the quote having the
highest version number. The prior quote versions are read-only. This enhancement allows
the user to update a prior quote version by assigning the highest version flag to a specific
quote version. The quote versions for which the highest version flag is not set remain
read-only. This is useful when a sales representative offers the customer several quote
proposals, each quote proposal having a different quote version. If the customer approves
a quote proposal having a lower quote version, then the highest version flag can be set for
that quote version and the quote can subsequently be placed as an order.
3.11.8.6. Configuration Effective Date (HTML UI only)

Currently, the effective date for a model configuration in the quote is the current date or
the creation date of the model configuration. Additional flexibility is provided for
customers who wish to write their own rule for determining the effective date. However,
users do not have the ability to choose the previous model configuration effective date for
copied configurations. This enhancement allows the original effective date to be
preserved across copied configurations. It promotes greater reuse of prior approved
model configurations and reduces the time taken to reconfigure complex configurations.
3.11.8.7. Support Model Configurations in the Quoting API

Currently, the user cannot pass an existing model configuration to the Create Quote and
Update Quote API. This enhancement allows the user to pass the model configuration
header and revision number as parameters to the Create Quote and Update Quote API.
It allows customers to import existing model configurations into a new quote or update an
existing quote. This is especially useful when the model configuration is created in a
custom UI and then the model configuration can be imported into the newly created
quote.
3.11.8.8. Print Quote Pop-up

Currently, the quote printout is rendered within the Quoting application page. After
reviewing the quote printout, the user has to use the browser back button to return to the
print quote options page. If they accidentally close the quote printout page, then the
Quoting application is closed and has to be restarted.
Going forward, the quote printout will be rendered in a separate pop-up page. The user
can review the quote printout, close the pop-up page and return to the print quote options
page without having to use the browser back button.
3.11.9. Release 12.2.7
3.11.9.1. Quote Status Transition by Operating Unit

Currently, the quote status and quote status transitions are global and apply to all the
operating units. Thus, it is not possible to have different quote status transitions for an
operating unit.
This enhancement provides the ability to setup different quote status transitions for each
operating unit. If status transitions are not setup for an operating unit, then the status
transitions that are not associated with an operating unit will apply. At runtime, the
quoting application will look for quote status transitions setup for the operating unit on
the quote. If there are no status transitions setup for that operating unit, then it will use
the status transitions that are not specific to any operating unit.
3.11.9.2. Support optional products

Currently, the quote line quantity has to be greater than zero. Since the quantity is greater
than zero, it will result in a price that is greater than zero (assuming price after discounts
is more than zero). The zero quantity check in Quoting is in line with the current
functionality supported in Advanced Pricing and Order Management, which also do not
support zero quantities on order lines.
Customers often need to create quotes having quote lines with zero quantity to indicate
optional products. Optional products are added to the quote to indicate products that the
customer can purchase in a future quote. Such quotes are sometimes referred to as service
quotes and the service quotes are fulfilled by either legacy or EBS Service applications.
Going forward, the quoting user can add optional products to the quote by specifying
zero quantity on the quote line. The quote lines having zero quantity will have a list price
like other non-zero quantity quote lines. However, these quotes cannot be placed as an
order since Order Management does not support this feature.
3.11.9.3. Update Cost from Quoting UI

Currently, the item cost for the product on the quote line is retrieved from the EBS
Costing application or the custom hook. The item cost is shown in the Quoting UI and
cannot be changed by the user. This applies to all the item types that are supported in
Quoting. For expense type items, the cost is not determined by the Costing application as
it depends on how the item is procured.
Going forward, the user can change the cost for the expense items in the quote.
3.11.9.4. Alternate Product Description for Quote line
Currently, the product description for the product on the quote line comes from the item
master and the user cannot revise the product description. This feature allows the user to
specify an alternate product description for the quote line. The alternate product
description may come from the End Customer or from the Purchase Order line detail.
This feature can also be used to provide a more precise description for generic products
in the quote. Generic part numbers are often used as placeholders in the quote. The
alternate product description will be displayed in the Quoting UI and on the quote
printout.
3.11.9.5. Allow negative quote total

Currently, Quoting requires the quote total to be positive. Quoting supports trade-in
scenarios, where a customer can return (trade-in) a product and purchase other products
on a quote. However, the quote total must be positive in such scenarios.
Going forward, the negative quote total restriction has been removed to support
additional return use cases.
3.11.9.6. Support for Deliver-To Customer in Order Capture API

This feature allows the user to specify the Deliver-To customer, account, contact and
address details at the header level in the Create Quote, Update Quote and Submit Quote
public APIs. This requirement was driven by iStore customers who need the ability to
specify the Deliver-To Customer details during the checkout process. Note that this
feature is not available in the Quoting UI.
3.11.9.7. Email Style for Web Publish Notifications

This feature allows Quoting customers to specify the email style for the Web Publish
notifications sent from the Quoting application to the iStore user. The default email style
is determined by an iStore profile option. The iStore user can also set their email style
preference in the iStore application.
3.11.10. Release 12.2.8
3.11.10.1. Create Quote from a spreadsheet

Currently, you can create a quote using the Quoting UI or the Create Quote API. Creating
a hundred line quote using the Quoting UI will take considerable time. Alternately, the
same hundred-line quote can be created much faster by specifying the quote and quote
line information in a spreadsheet and processing it in bulk using the Create Quote API.
The spreadsheet can be created offline by a partner user and then sent to the Quoting user
to upload it into the system. The spreadsheet upload process performs the same
validations as that in the UI since it uses the existing Create Quote API to create the
quote. The spreadsheet approach also supports the ability to create multiple quotes in one
go. The layout of the spreadsheet can be personalized to meet the business requirements.
3.12. Oracle Quoting Information Discovery
3.12.1. Overview
Oracle Quoting Information Discovery is a useful complementary application to Oracle
Quoting. It is targeted at the day-to-day operational quoting user and the Sales Manager.
It leverages the quote security model allowing Sales managers to view their quotes and
their team’s quotes. It allows seamless navigation to the quotes in Oracle Quoting. It
helps the user find the correct quote using several quote header and line attributes
including flexfields. The user can create a quote, drill into a quote and update it.
Additionally, the user can compare two or more quotes, two or more quote lines
belonging to the same or different quotes. Users can view addresses associated with the
quotes on a map to determine geographical proximity. This will be useful when arranging
customer visits. Also, when launching a product campaign targeted based on the location
of the customers.
3.12.2. V6
3.12.2.1. Quote Performance Dashboard

Sales Managers can track quote performance metrics such as quote conversion, the
average time to convert the quote to an order, product related metrics and the effect of
discounts on quote conversion. This allows them to focus the sales force on top revenue
potential, identify and target high value quotes. The approval related metrics help Sales
Managers identify bottlenecks in the approval process and subsequently streamline it.
Sales Managers can identify top selling products and product categories as well as
products and product categories that are not doing well. They can view quote, order and
quote conversion trends by month and year as well as the performance of Sales channels
and Sales Groups.
3.12.2.2. Manage Quotes Dashboard

It allows quoting users to view open quotes, successful quotes and quotes in other
statuses between them. Users can determine what quotes should be worked on based on
the last time it was updated, the quote expiration date and the quote status. Thus if a large
quote is expiring soon, the user may want to work on that first. Or if a quote has not been
updated in a while they should look into why it is so. The user can perform several quote
actions without having to open the quote. The quote actions are quote versioning,
duplicate quote, view sales commission, print quote and place order. The user can also
create a quote, drill into a quote to update it. This helps improve the day-to-day
transactional quoting efficiencies.
3.12.3. V8
3.12.3.1. Advanced Search Capabilities

In this Release, Quoting Information Discovery users will have greater flexibility to filter
the quote records using a combination of additional criteria like “Boolean Search”,
“Partial Search”, “Show More”, “Exclude all” and “Select All”. The new capabilities
include:
• Partial value search in Available Refinements. Example: *text*
• Partial record search for the following attributes:
o Quote Name
o Customer
Oracle E-Business Suite Releases 12.1 and 12.2 Release Content Document Oracle Quoting Information Discovery 41
o Contact
o Bill To Customer
o Bill To Contact
o Ship To Customer
o Ship To Contact
o Primary Salesperson
o Internal Product Part Number
o Product Long Description
• Partial record search with Boolean expression. Example: *laptop* OR *monitor*
• Currently, negative refinements are available per attribute in Available Refinements.
This has been enhanced to use the negative refinement icon per attribute to refine the
data to only include records that do not have that value.
• New “Exclude All” functionality allows the user to apply all values of the attribute as
negative refinements. It is also used to exclude all search result values regardless of
the number of values displayed in the list.
• Change the behavior of “Select All”. The Select All button allows the user to apply
all values of the attribute as refinements. It is also used to select all search result
values regardless of the number of values displayed in the list.
Oracle E-Business Suite Releases 12.1 and 12.2 Release Content Document Oracle Quoting Information Discovery 42

EBS 122 Cum RCD SME

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

EBS 122 Cum RCD SME

Uploaded by

Copyright:

Available Formats

ORACLE E-BUSINESS SUITE

RELEASE CONTENT DOCUMENT

Sales, Marketing, eCommerce, and

Prepared by Oracle E-Business Suite Product Development

Last Updated: September 25, 2020

Copyright © 2011, 2020, Oracle and/or its affiliates.

2.1. Purpose of Document

3.1. Oracle Field Sales

3.1.2.2. Enhanced Opportunity Search

3.2. Oracle Incentive Compensation

3.2.2.1. Modeling and Plan Copy Features

3.2.2.2. Siebel CRM Integration to Oracle Incentive Compensation

3.2.2.3. PeopleSoft Enterprise Human Capital Management Integration Features

3.2.2.3.1. Employee, Department, Job Synchronization

3.2.2.3.3. Reporting for Plan Modeling

3.2.3.1. Performance and Scalability Improvements

3.2.3.1.1. New Summarization Method

3.2.3.2. Support for Incentive Compensation Gadgets

3.2.4.1. Calculation Performance Improvement

3.2.4.2. Archive & Purge

3.2.4.3. Subledger Archive and Ghosting/Purge

3.2.5. Release 12.2.4

3.2.5.1. Calculation Performance Improvement

This feature is back-ported to 12.1.3+.

3.2.5.2. Comprehensive Pre-Built Automated Component Based Testing for OIC

Using Oracle Flow Builder’s component-based test generation framework instead of a

3.2.6. Release 12.2.5

3.2.6.1. New XML based WebADI Report for Plan Visualization

3.2.6.2. Improved Plan Administrator Usability for Expressions and Formulas

• LOV selection for Expressions and Formulas,

3.2.6.3. Archive and Purge

• Category A – Housekeeping to purge obsolete runtime data by period

Accompanying project planning guidance will be incorporated into the OIC

Category A tables include:

• Successfully completed CSV Import transaction uploads

Category B tables include:

• Collection and Interface Tables

This feature is back-ported to 12.1.3+.

3.2.7. Release 12.2.6

3.2.7.1. Subledger Archive and Ghosting/Purge

• Category C – Archive and purge or ghost sizable salesrep subledger tables by

Accompanying project planning guidance will be incorporated into the OIC

Category C tables include:

• Purged Subledger Tables

3.2.7.2. Integration Enhancements to EBS Payrolls and Accounts Payable

This will be driven by 2 new payment parameters in Configuration Workbench’s

• Prevent Zero Payments to Payroll checkbox

To improve visibility and reconciliation for AP departments, OIC payments interfaced to

To avoid accidently running full calculation for incremental calculation customers,

3.2.7.5. Leverage Default Operating Unit in Additional UIs

3.2.9. Release 12.2.9

3.2.9.2. Cancel Transactions in Maintain Transactions User Interface

3.2.9.3. Enforce Classification and Dimension Attribute Settings

3.2.10.2. Concurrent Program to synchronize Accumulated Ledger Balances

3.2.10.3. Relax Maintain Transactions Search Page Query Criteria

3.2.10.4. Export of Incentive Compensation Reports to include Report Headers

3.2.10.5. Cancel Transaction support in the Maintain Transactions Page

3.3. Oracle Incentive Compensation Command Center

Within Incentive Compensation each processed transaction passes through a Collect,

Lifecycle attributes include:

The Oracle Incentive Compensation Command Center feature is available at no

The following functionality requires Oracle Enterprise Command Center Framework

3.3.2. Released 12.2.8+