Oracle Incentive Compensation

Oracle Incentive Compensation
User Guide
Release 11i
September 2002
Part No. B10103-01
This is a guide to using Oracle Incentive Compensation.

Oracle Incentive Compensation User Guide, Release 11i
Part No. B10103-01
Copyright © 1996, 2002, Oracle Corporation. All rights reserved.
Primary Author: Steven Schaefer
The Programs (which include both the software and documentation) contain proprietary information of
Oracle Corporation; they are provided under a license agreement containing restrictions on use and
disclosure and are also protected by copyright, patent and other intellectual and industrial property
laws. Reverse engineering, disassembly or decompilation of the Programs, except to the extent required
to obtain interoperability with other independently created software or as specified by law, is prohibited.
The information contained in this document is subject to change without notice. If you find any problems
in the documentation, please report them to us in writing. Oracle Corporation does not warrant that this
document is error-free. Except as may be expressly permitted in your license agreement for these
Programs, no part of these Programs may be reproduced or transmitted in any form or by any means,
electronic or mechanical, for any purpose, without the express written permission of Oracle Corporation.
If the Programs are delivered to the U.S. Government or anyone licensing or using the programs on
behalf of the U.S. Government, the following notice is applicable:
Restricted Rights Notice Programs delivered subject to the DOD FAR Supplement are "commercial
computer software" and use, duplication, and disclosure of the Programs, including documentation,
shall be subject to the licensing restrictions set forth in the applicable Oracle license agreement.
Otherwise, Programs delivered subject to the Federal Acquisition Regulations are "restricted computer
software" and use, duplication, and disclosure of the Programs shall be subject to the restrictions in FAR
52.227-19, Commercial Computer Software - Restricted Rights (June, 1987). Oracle Corporation, 500
Oracle Parkway, Redwood City, CA 94065.
The Programs are not intended for use in any nuclear, aviation, mass transit, medical, or other inherently
dangerous applications. It shall be the licensee's responsibility to take all appropriate fail-safe, backup,
redundancy, and other measures to ensure the safe use of such applications if the Programs are used for
such purposes, and Oracle Corporation disclaims liability for any damages caused by such use of the
Programs.
Oracle is a registered trademark, and OracleMetaLink is a trademark or registered trademark of

Oracle Corporation. Other names may be trademarks of their respective owners.
Contents
Part I Introduction and Overview
1 Introduction to Oracle Incentive Compensation

1.1 Overview of Introduction to Oracle Incentive Compensation ....................................... 1-1
1.2 Oracle Incentive Compensation Key Features .................................................................. 1-3
1.2.1 Incentive Planning ......................................................................................................... 1-4
1.2.2 Compensation Plans ...................................................................................................... 1-4
1.2.3 Quota Assignment ......................................................................................................... 1-6
1.2.4 Quota Approval Process ............................................................................................... 1-8
1.2.5 Compensating Transactions ......................................................................................... 1-9
1.2.6 Revenue Classes ........................................................................................................... 1-10
1.2.7 Hierarchies .................................................................................................................... 1-11
1.2.8 Classification Rules ...................................................................................................... 1-12
1.2.9 Classification Rules Hierarchy ................................................................................... 1-12
1.2.10 Compensation Groups ................................................................................................ 1-14
1.2.11 Data Collection ............................................................................................................. 1-15
1.2.12 Calculation .................................................................................................................... 1-18
1.2.13 Payment ......................................................................................................................... 1-20
1.3 Oracle Incentive Compensation Integrations.................................................................. 1-21
1.3.1 Overview ....................................................................................................................... 1-22
1.3.2 Oracle Sales Online ...................................................................................................... 1-23
1.3.3 Oracle Resource Manager ........................................................................................... 1-29
1.3.4 Oracle Payable .............................................................................................................. 1-30
1.3.5 Oracle Partners Online ................................................................................................ 1-31
v
1.4 What’s New .......................................................................................................................... 1-31
1.4.1 Collecting Revenue Adjustment from Oracle Receivables..................................... 1-31
1.4.2 Accumulation and Splits in Multidimensional Rate Tables................................... 1-32
1.4.3 Payment ......................................................................................................................... 1-32
1.4.4 Revenue Management Adjustments Automatically Collected ............................. 1-33
1.4.5 Import/Export Module Enhanced............................................................................. 1-34
1.5 What’s Obsolete ................................................................................................................... 1-34
2 Overview of Using Oracle Incentive Compensation

2.1 Accessing Oracle Incentive Compensation........................................................................ 2-1
2.1.1 The Home Tab................................................................................................................. 2-2
2.1.2 The Incentive Tab ........................................................................................................... 2-2
2.1.3 The Modeling Tab .......................................................................................................... 2-3
2.1.4 The Resource Tab ........................................................................................................... 2-3
2.1.5 The Quota Tab ................................................................................................................ 2-4
2.1.6 The Transaction Tab....................................................................................................... 2-4
2.1.7 The Requests Tab............................................................................................................ 2-5
2.1.8 The Product Tab ............................................................................................................. 2-6
2.1.9 The Administration Tab ................................................................................................ 2-6
2.2 Navigation .............................................................................................................................. 2-8
2.2.1 HTML Navigation .......................................................................................................... 2-8
2.3 How Oracle Incentive Compensation Relates to the E-Business Suite.......................... 2-9
2.4 Summary of Oracle Incentive Compensation Tasks ........................................................ 2-9
Part II Incentive Planning
3 Incentive Planning
3.1 Overview of Incentive Planning.......................................................................................... 3-1
3.1.1 The Incentive Planning Process.................................................................................... 3-2
3.2 Incentive Planning Enhancements in this Release............................................................ 3-3
3.2.1 Support for Non-Quota Based Components .............................................................. 3-3
3.2.2 Customization of Club Eligibility ................................................................................ 3-3
3.3 Setups for Incentive Planning.............................................................................................. 3-4
3.3.1 Associate Responsibilities with Responsibility Groups ........................................... 3-4
vi
3.3.2 Define Default Contract Text........................................................................................ 3-5
3.3.3 Define User Access......................................................................................................... 3-6
3.3.4 Define Quota Components ........................................................................................... 3-7
3.3.5 Define Attainment Schedule......................................................................................... 3-8
3.3.6 Seasonality Schedules.................................................................................................... 3-9
3.3.7 Define Jobs .................................................................................................................... 3-10
3.4 Creating the Agreement ..................................................................................................... 3-11
3.4.1 Defining a Sales Role ................................................................................................... 3-11
3.4.2 Using Quota Estimates from Resources.................................................................... 3-14
3.4.3 Completing the Agreement ........................................................................................ 3-14
3.4.4 Computed Component Formulas.............................................................................. 3-18
3.4.5 Customizing On Target Earnings and Anchors for Individual Resources.......... 3-19
3.5 Allocating Quotas to Resources ........................................................................................ 3-21
3.6 Allocation Details - Quota and Pay Assignment ............................................................ 3-23
3.7 Approving Contracts .......................................................................................................... 3-25
3.7.1 Viewing the Contract................................................................................................... 3-26
3.7.2 Compensation Plan History ....................................................................................... 3-27
3.8 Distributing Contracts ........................................................................................................ 3-27
3.9 Salespeople Accept Plans Using Oracle Sales Online .................................................... 3-28
3.10 Activating Compensation Plans........................................................................................ 3-28
3.10.1 Regoaling....................................................................................................................... 3-29
4 Modeling Agreements
4.1 Overview of Modeling Agreements ................................................................................... 4-1
4.1.1 The Modeling Process.................................................................................................... 4-2
4.1.2 The Lifecycle of an Agreement Version...................................................................... 4-2
4.2 Modeling Enhancements...................................................................................................... 4-3
4.3 Creating an Agreement Version.......................................................................................... 4-3
4.4 Assigning Details to an Agreement Version ..................................................................... 4-3
4.5 Allocating Quotas to Quota Based Components .............................................................. 4-6
4.6 Comparing Agreement Version Contracts ........................................................................ 4-7
4.7 What-If Scenarios .................................................................................................................. 4-9
Part III Resources and Compensation Plans
vii
5 Creating Resources, Roles and Groups
5.1 Introduction to Creating Resources, Roles, and Groups ................................................. 5-1
5.1.1 Set Up Resources for Team Compensation ................................................................ 5-1
5.2 Assign Resources to Roles and Groups.............................................................................. 5-2
6 Building Compensation Plans

6.1 Overview of Building Compensation Plans ...................................................................... 6-1
6.2 Enhancements to Building Compensation Plans.............................................................. 6-2
6.3 Defining Calculation Expressions ....................................................................................... 6-2
6.4 Defining Rate Dimensions.................................................................................................... 6-6
6.5 Defining Rate Tables ........................................................................................................... 6-10
6.6 Defining Formulas............................................................................................................... 6-11
6.7 Defining Plan Elements ...................................................................................................... 6-15
6.7.1 Assigning Revenue Classes to a Plan Element......................................................... 6-18
6.7.2 Assigning Rate Tables to a Plan Element.................................................................. 6-19
6.8 Transaction Factors and Accelerators............................................................................... 6-21
6.8.1 Accelerators................................................................................................................... 6-22
6.8.2 Transaction Factors ...................................................................................................... 6-23
6.9 Defining Compensation Plans ........................................................................................... 6-24
6.9.1 Compensation Plan Details......................................................................................... 6-25
7 Assigning Compensation Plans, Pay Groups, and Payment Plans

7.1 Assigning a Compensation Plan to a Role ......................................................................... 7-1
7.1.1 Method 1: Using the Incentive Tab.............................................................................. 7-2
7.1.2 Method 2: Using the Resource Tab .............................................................................. 7-3
7.2 Assigning a Role to a Resource............................................................................................ 7-4
7.3 Customizing a Compensation Plan for a Resource .......................................................... 7-4
7.4 Assigning a Pay Group to a Resource ................................................................................ 7-5
7.5 Assigning a Payment Plan to a Resource........................................................................... 7-6
7.6 Regoaling ................................................................................................................................ 7-7
Part IV Collection, Calculation, Payment, and Reports
viii
8 Collecting and Adjusting Transactions
8.1 Overview of Collecting Transactions ................................................................................. 8-1
8.2 Open Collections ................................................................................................................... 8-3
8.2.1 Identifying the Header and Line Tables ..................................................................... 8-4
8.2.2 Registering the Tables ................................................................................................... 8-4
8.2.3 Defining a New Transaction Source............................................................................ 8-5
8.2.4 Identifying Source Tables ............................................................................................. 8-7
8.2.5 Defining Notification and Collection Queries and Runtime Parameters .............. 8-8
8.2.6 Defining Mapping........................................................................................................ 8-12
8.2.7 Defining Pre-Notification, Post-Notification, and Post-Collection Actions ........ 8-15
8.2.8 Defining Filters ............................................................................................................. 8-17
8.2.9 Generate and Test Generate........................................................................................ 8-18
8.3 Standard Collection............................................................................................................. 8-21
8.3.1 How Direct and Indirect Mapping can Be Modified .............................................. 8-22
8.3.2 Special Features ............................................................................................................ 8-22
8.4 Submitting a Collection Request ....................................................................................... 8-26
8.4.1 Runtime Parameters .................................................................................................... 8-26
8.4.2 Submit a Request.......................................................................................................... 8-27
8.4.3 Viewing the Request Status and Logs....................................................................... 8-28
8.5 Collecting Adjustments ...................................................................................................... 8-30
8.5.1 Collecting Adjustments for Order Transactions...................................................... 8-30
8.5.2 Collecting Adjustments for Custom Transaction Sources ..................................... 8-30
8.5.3 Collecting Adjustments for AR - RAM ..................................................................... 8-31
8.6 Imports and Exports ........................................................................................................... 8-33
8.6.1 Defining Imports .......................................................................................................... 8-33
8.6.2 Mapping Source Fields to Target Fields ................................................................... 8-35
8.6.3 Reviewing Your Mapping........................................................................................... 8-36
8.6.4 Confirming your Mapping ......................................................................................... 8-36
8.6.5 Import Details and Results ......................................................................................... 8-36
8.6.6 Process Log.................................................................................................................... 8-37
8.6.7 Failed Records .............................................................................................................. 8-37
8.7 Adjusting Transactions....................................................................................................... 8-37
8.7.1 Create New Transaction.............................................................................................. 8-39
8.7.2 Move Credits................................................................................................................. 8-40
8.7.3 Deal Split ....................................................................................................................... 8-41
ix
8.7.4 Split Transaction ........................................................................................................... 8-42
8.8 Loading Transactions.......................................................................................................... 8-43
8.8.1 Viewing Transaction Requests ................................................................................... 8-44
8.9 Using the Transaction Interface......................................................................................... 8-44
8.9.1 Validation Checks and Resolution Method.............................................................. 8-49
9 Calculating Compensation
9.1 Overview of Calculating Compensation............................................................................ 9-1
9.1.1 Two Types of Calculation ............................................................................................. 9-1
9.1.2 Two Methods of Calculation ........................................................................................ 9-2
9.1.3 Phases of Calculation ..................................................................................................... 9-2
9.1.4 Unprocessed and Failure Statuses ............................................................................... 9-3
9.1.5 The Calculation Process................................................................................................. 9-4
9.2 Calculation Enhancements in this Release......................................................................... 9-5
9.2.1 Rollup Summarized Transactions................................................................................ 9-5
9.2.2 Accumulation and Splits in Multidimensional Rate Tables..................................... 9-8
9.2.3 Batch Runners Automatically Cancelled after Failure............................................ 9-12
9.2.4 Calculation Resubmission ........................................................................................... 9-12
9.3 Preparing for Calculation ................................................................................................... 9-13
9.4 Submitting Calculation ....................................................................................................... 9-13
9.5 Using Incremental Calculation .......................................................................................... 9-17
9.5.1 Revert_To_State ............................................................................................................ 9-19
9.5.2 Action Column.............................................................................................................. 9-19
9.5.3 The Notify Log.............................................................................................................. 9-20
9.5.4 Customizing the Notify Log Search .......................................................................... 9-20
10. ................................................................................................................................................ 9-22
10 Payment with Payruns

10.1 Overview of Payment with Payruns ................................................................................ 10-1
10.1.1 Prerequisites .................................................................................................................. 10-3
10.2 Payment Enhancements in this Release ........................................................................... 10-4
10.2.1 Automated Posting ...................................................................................................... 10-4
10.2.2 Lock Payment Worksheets.......................................................................................... 10-4
10.2.3 Add and Track Comments on Payment Worksheets.............................................. 10-4
10.2.4 Payment Administrative Hierarchy and Payrun Sign-Off Report........................ 10-5
x
10.2.5 Recoverable and Non-Recoverable Manual Payment Adjustments .................... 10-6
10.2.6 Payment Worksheet History Page............................................................................. 10-6
10.2.7 Refresh Worksheet ....................................................................................................... 10-7
10.3 Using the Payrun Summary .............................................................................................. 10-7
10.4 Creating a Payrun................................................................................................................ 10-9
10.5 Using the Worksheet Summary ...................................................................................... 10-10
10.5.1 Current Estimated Payout Page............................................................................... 10-14
10.6 Using the Payment Transactions Page ........................................................................... 10-14
10.7 Approving a Payrun ......................................................................................................... 10-17
10.7.1 The Payrun Sign-Off Report ..................................................................................... 10-20
10.8 Submitting a Payrun for Payment .................................................................................. 10-21
10.8.1 View Requests............................................................................................................. 10-21
10.8.2 Submit Requests ......................................................................................................... 10-22
11 Reports
11.1 Overview of Oracle Incentive Compensation Reports .................................................. 11-2
11.1.1 Road Map of Reports from Version to Version ....................................................... 11-2
11.2 Reports Enhancements in this Release ............................................................................. 11-5
11.3 Incentive Planning Reports................................................................................................ 11-5
11.3.1 Quota Modeling Summary ......................................................................................... 11-6
11.3.2 Average Quota Report................................................................................................. 11-8
11.3.3 Quota Overassignment Report ................................................................................ 11-10
11.3.4 Quota Range Report .................................................................................................. 11-11
11.3.5 Compensation Contract Status Report.................................................................... 11-12
11.3.6 Overlay Report ........................................................................................................... 11-13
11.3.7 Vacancy Report........................................................................................................... 11-14
11.3.8 Transition Report ....................................................................................................... 11-15
11.3.9 Plan Activation Status Report .................................................................................. 11-15
11.3.10 Role to Compensation Plan Mapping Report ........................................................ 11-17
11.4 Compensation Reports ..................................................................................................... 11-18
11.4.1 Year To Date Summary ............................................................................................. 11-19
11.4.2 Transaction Details Report ....................................................................................... 11-21
11.4.3 Compensation Group Hierarchy Report ................................................................ 11-22
11.4.4 Classification Rules Report ....................................................................................... 11-23
11.4.5 Commission Summary Report ................................................................................. 11-25
xi
11.4.6 Quota Performance Report ....................................................................................... 11-27
11.4.7 Commission Statement.............................................................................................. 11-29
11.4.8 Unprocessed Transactions ........................................................................................ 11-32
11.5 Configuring Reports.......................................................................................................... 11-33
11.6 Discoverer Workbooks ..................................................................................................... 11-37
11.6.1 Calculation Batch Process Report ............................................................................ 11-37
11.6.2 Compensation Plan Revenue Class Mapping ........................................................ 11-38
11.6.3 Resources Not Validated for Calculation ............................................................... 11-38
11.6.4 Resources with Pay Group Assignment Different than Compensation Plan Dates......
11-39
11.6.5 Commission Statement Report................................................................................. 11-39
11.6.6 Transaction Details Report........................................................................................ 11-40
11.6.7 Formula Definitions ................................................................................................... 11-41
11.6.8 Resource Assignments Overview ............................................................................ 11-41
Part V Administration
12 Administration
12.1 Overview of Administration.............................................................................................. 12-2
12.2 System Parameters .............................................................................................................. 12-2
12.2.1 General ........................................................................................................................... 12-3
12.2.2 General Ledger ............................................................................................................. 12-3
12.2.3 Collection....................................................................................................................... 12-3
12.2.4 Calculation..................................................................................................................... 12-4
12.2.5 Payment ......................................................................................................................... 12-5
12.3 Tables..................................................................................................................................... 12-7
12.3.1 Columns......................................................................................................................... 12-8
12.4 External Table Join Conditions........................................................................................ 12-11
12.4.1 External Table Join Conditions - External Columns ............................................. 12-12
12.5 Accumulation Periods....................................................................................................... 12-12
12.6 Pay Periods ......................................................................................................................... 12-13
12.7 Interval Types .................................................................................................................... 12-14
12.7.1 To View an Interval Type.......................................................................................... 12-14
12.7.2 To Create a New Interval Type ................................................................................ 12-15
12.8 Revenue Class .................................................................................................................... 12-16
xii
12.9 Rulesets ............................................................................................................................... 12-17
12.9.1 Rules Hierarchy .......................................................................................................... 12-19
12.9.2 Create Rules ................................................................................................................ 12-20
12.9.3 Rule Attributes............................................................................................................ 12-21
12.9.4 Build Expression......................................................................................................... 12-22
12.10 Hierarchy Types ................................................................................................................ 12-23
12.10.1 Hierarchies Detail....................................................................................................... 12-24
12.10.2 Intervals ....................................................................................................................... 12-24
12.10.3 Adding and Deleting Hierarchy Nodes.................................................................. 12-25
12.11 Credit Types ....................................................................................................................... 12-28
12.12 Credit Conversion ............................................................................................................. 12-29
12.13 Collection............................................................................................................................ 12-30
12.14 Pay Groups ......................................................................................................................... 12-30
12.15 Payment Plan ..................................................................................................................... 12-31
12.16 Payroll ................................................................................................................................. 12-33
12.16.1 Pay Element Input Values Mapping ....................................................................... 12-34
12.17 Components ....................................................................................................................... 12-35
12.18 Attainment.......................................................................................................................... 12-37
12.19 Job Titles ............................................................................................................................. 12-38
12.20 User Access......................................................................................................................... 12-39
12.21 Settings................................................................................................................................ 12-40
12.21.1 Workday Calendar..................................................................................................... 12-41
12.22 Seasonality Schedules ....................................................................................................... 12-43
12.22.1 Create New Seasonality Schedule ........................................................................... 12-44
12.23 Rate Dimensions................................................................................................................ 12-45
Part VI Appendixes
A External Formula Code Examples

A.1 Example 1 ............................................................................................................................... A-1
A.1.1 Spec of Example 1 .......................................................................................................... A-1
A.1.2 Body of Example 1 ......................................................................................................... A-4
A.2 Example 2 ............................................................................................................................. A-20
A.2.1 Spec for Example 2....................................................................................................... A-20
A.2.2 Body of Example 2 ....................................................................................................... A-22
xiii
B Customized Summarization Code Examples
Glossary
xiv
Send Us Your Comments
Oracle Incentive Compensation User Guide, Release 11i
Part No. B10103-01
Oracle Corporation welcomes your comments and suggestions on the quality and usefulness of this
document. Your input is an important part of the information used for revision.
■ Did you find any errors?
■ Is the information clearly presented?
■ Do you need more information? If so, where?
■ Are the examples correct? Do you need more examples?
■ What features did you like most?
If you find any errors or have any other suggestions for improvement, please indicate the document
title and part number, and the chapter, section, and page number (if available). You can send com-
ments to us via postal service:
Oracle Corporation
CRM Content Development Manager
500 Oracle Parkway
Redwood Shores, CA 94065
U.S.A.
If you would like a reply, please give your name, address, telephone number, and (optionally) elec-
tronic mail address.
If you have problems with the software, please contact your local Oracle Support Services.
xv
xvi
Preface
Intended Audience
Welcome to Release 11i of the Oracle Incentive Compensation User Guide.
This guide assumes you have a working knowledge of the following:
■ The principles and customary practices of your business area.
■ Oracle Incentive Compensation
If you have never used Oracle Incentive Compensation, Oracle suggests you
attend one or more of the Oracle Incentive Compensation training classes
available through Oracle University.
■ The Oracle Applications graphical user interface.
To learn more about the Oracle Applications graphical user interface, read
the Oracle Applications User’s Guide.
See Other Information Sources for more information about Oracle Applications
product information.
How To Use This Guide

This document contains the information you need to understand and use Oracle
Incentive Compensation.
■ Chapter 1 begins Part 1 of this User Guide. It provides a brief introduction to
the new features of Oracle Incentive Compensation and explains how the
product works.
■ Chapter 2 continues Part 1 and gives an overview of Oracle Incentive
Compensation. This includes a brief explanation of the HTML user interface
xvii
and a breakdown of how its tab structure works. Also included is a section on
how Oracle Incentive Compensation relates to the Oracle E-Business Suite.
■ Chapter 3 begins Part 2 of the User Guide. It explains the purpose and usage of
Incentive Planning, and how it enables managers to apportion quotas
effectively and lets salespeople submit estimates to make that process more
accurate.
■ Chapter 4 discusses the Modeling feature of Oracle Incentive Compensation
which allows you to compare proposed agreements to each other to determine
which one best suits your needs. It explains the steps used with the Modeling
tab.
■ Chapter 5 begins Part 3 of the User Guide by discussing how to create the
elements needed to build compensation plans. These include resources, roles,
and groups.
■ Chapter 6 is where the actual building of compensation plans gets underway. In
this chapter, you start by creating the expressions, rate dimensions, formulas,
and plan elements that make up a compensation plan.
■ Chapter 7 explains how to assign newly created compensation plans to roles
and how the roles are then assigned to individual resources.
■ Chapter 8 begins Part 4, which deals with processing of transactions and
payment of compensation. This chapter explains how to collect transactions,
including importing them into Oracle Incentive Compensation, adjusting them,
and loading them before calculation begins.
■ Chapter 9 continues the processing of transactions by outlining and explaining
the steps performed for calculation of commission.
■ Chapter 10 deals with the payment of compensation, including posting and the
setting up and payment of payruns.
■ Chapter 11 discusses the two sets of reports that are available in Oracle
Incentive Compensation. These include Incentive Planning reports and
Compensation reports. A table shows which reports are available to different
responsibilities within Oracle Incentive Compensation.
■ Chapter 12 details the administrative steps used in Oracle Incentive
Compensation. Many of these steps are performed just once a year, or
occasionally, to set up features such as system parameters or payment groups.
These activities are all performed using the Administration tab.
■ Appendixes provide additional information that may be of use to you as a
reference. This includes examples of typical formulas, plan elements, and
xviii
compensation plans and a map showing how different procedures are
performed in the current version of the product compared to previous ways
they were performed.
■ A Glossary of important terms and an Index are provided to it easier.
Documentation Accessibility
Our goal is to make Oracle products, services, and supporting documentation
accessible, with good usability, to the disabled community. To that end, our
documentation includes features that make information available to users of
assistive technology. This documentation is available in HTML format, and
contains markup to facilitate access by the disabled community. Standards will
continue to evolve over time, and Oracle Corporation is actively engaged with
other market-leading technology vendors to address technical obstacles so that
our documentation can be accessible to all of our customers. For additional
information, visit the Oracle Accessibility Program Web site at
http://www.oracle.com/accessibility/.
Accessibility of Code Examples in Documentation JAWS, a Windows screen

reader, may not always correctly read the code examples in this document. The
conventions for writing code require that closing braces should appear on an
otherwise empty line; however, JAWS may not always read a line of text that
consists solely of a bracket or brace.
Other Information Sources

You can choose from many sources of information, including online
documentation, training, and support services, to increase your knowledge and
understanding of Oracle Incentive Compensation.
If this guide refers you to other Oracle Applications documentation, use only the
Release 11i versions of those guides.
Online Documentation
All Oracle Applications documentation is available online (HTML or PDF).
Online help patches are available on MetaLink.
xix
Related Documentation
Oracle Incentive Compensation shares business and setup information with other
Oracle Applications products. Therefore, you may want to refer to other product
documentation when you set up and use Oracle Incentive Compensation.
You can read the documents online by choosing Library from the expandable
menu on your HTML help window, by reading from the Oracle Applications
Document Library CD included in your media pack, or by using a Web browser
with a URL that your system administrator provides.
If you require printed guides, you can purchase them from the Oracle Store at
http://oraclestore.oracle.com.
Documents Related to All Products
Oracle Applications User’s Guide

This guide explains how to enter data, query, run reports, and navigate using the
graphical user interface (GUI) available with this release of Oracle Incentive
Compensation (and any other Oracle Applications products). This guide also
includes information on setting user profiles, as well as running and reviewing
reports and concurrent processes.
You can access this user’s guide online by choosing ”Getting Started with Oracle
Applications” from any Oracle Applications help file.
Documents Related to This Product
Installation and System Administration
Oracle Applications Concepts

This guide provides an introduction to the concepts, features, technology stack,
architecture, and terminology for Oracle Applications Release 11i. It provides a
useful first book to read before an installation of Oracle Applications. This guide
also introduces the concepts behind Applications-wide features such as Business
Intelligence (BIS), languages and character sets, and Self-Service Web
Applications.
Installing Oracle Applications

This guide provides instructions for managing the installation of Oracle
Applications products. In Release 11i, much of the installation process is
handled using Oracle Rapid Install, which minimizes the time to install Oracle
xx
Applications, the Oracle8 technology stack, and the Oracle8i Server technology
stack by automating many of the required steps. This guide contains instructions
for using Oracle Rapid Install and lists the tasks you need to perform to finish
your installation. You should use this guide in conjunction with individual
product user’s guides and implementation guides.
Oracle Applications Supplemental CRM Installation Steps

This guide contains specific steps needed to complete installation of a few of the
CRM products. The steps should be done immediately following the tasks given
in the Installing Oracle Applications guide.
Upgrading Oracle Applications

Refer to this guide if you are upgrading your Oracle Applications Release 10.7 or
Release 11.0 products to Release 11i. This guide describes the upgrade process
and lists database and product-specific upgrade tasks. You must be either at
Release 10.7 (NCA, SmartClient, or character mode) or Release 11.0, to upgrade
to Release 11i. You cannot upgrade to Release 11i directly from releases prior to
10.7.
Maintaining Oracle Applications

Use this guide to help you run the various AD utilities, such as AutoUpgrade,
AutoPatch, AD Administration, AD Controller, AD Relink, License Manager,
and others. It contains how-to steps, screenshots, and other information that you
need to run the AD utilities. This guide also provides information on
maintaining the Oracle applications file system and database.
Oracle Applications System Administrator’s Guide

This guide provides planning and reference information for the Oracle
Applications System Administrator. It contains information on how to define
security, customize menus and online help, and manage concurrent processing.
Oracle Alert User’s Guide

This guide explains how to define periodic and event alerts to monitor the status
of your Oracle Applications data.
Oracle Applications Developer’s Guide

This guide contains the coding standards followed by the Oracle Applications
development staff. It describes the Oracle Application Object Library
components needed to implement the Oracle Applications user interface
xxi
described in the Oracle Applications User Interface Standards for Forms-Based
Products. It also provides information to help you build your custom Oracle
Forms Developer 6i forms so that they integrate with Oracle Applications.
Oracle Applications User Interface Standards for Forms-Based Products

This guide contains the user interface (UI) standards followed by the Oracle
Applications development staff. It describes the UI for the Oracle Applications
products and how to apply this UI to the design of an application built by using
Oracle Forms.
Other Implementation Documentation
Multiple Reporting Currencies in Oracle Applications

If you use the Multiple Reporting Currencies feature to record transactions in more
than one currency, use this manual before implementing Oracle Incentive
Compensation. This manual details additional steps and setup considerations for
implementing Oracle Incentive Compensation with this feature.
Multiple Organizations in Oracle Applications

This guide describes how to set up and use Oracle Incentive Compensation with
Oracle Applications’ Multiple Organization support feature, so you can define and
support different organization structures when running a single installation of
Oracle Incentive Compensation.
Oracle Workflow Guide

This guide explains how to define new workflow business processes as well as
customize existing Oracle Applications-embedded workflow processes.You also
use this guide to complete the setup steps necessary for any Oracle Applications
product that includes workflow-enabled processes.
Oracle Applications Flexfields Guide

This guide provides flexfields planning, setup and reference information for the
Oracle Incentive Compensation implementation team, as well as for users
responsible for the ongoing maintenance of Oracle Applications product data. This
manual also provides information on creating custom reports on flexfields data.
Oracle eTechnical Reference Manuals

Each eTechnical Reference Manual (eTRM) contains database diagrams and a
detailed description of database tables, forms, reports, and programs for a
xxii
specific Oracle Applications product. This information helps you convert data
from your existing applications, integrate Oracle Applications data with
non-Oracle applications, and write custom reports for Oracle Applications
products. Oracle eTRM is available on Metalink
Oracle Applications Message Reference Manual

This manual describes Oracle Applications messages. This manual is available in
HTML format on the documentation CD-ROM for Release 11i.
Oracle CRM Application Foundation Implementation Guide

Many CRM products use components from CRM Application Foundation. Use
this guide to correctly implement CRM Application Foundation.
Training and Support
Training
Oracle offers training courses to help you and your staff master Oracle Incentive
Compensation and reach full productivity quickly. You have a choice of educational
environments. You can attend courses offered by Oracle University at any one of
our many Education Centers, you can arrange for our trainers to teach at your
facility, or you can use Oracle Learning Network (OLN), Oracle University’s online
education utility. In addition, Oracle training professionals can tailor standard
courses or develop custom courses to meet your needs. For example, you may want
to use your organization’s structure, terminology, and data as examples in a
customized training session delivered at your own facility.
Support
From on-site support to central support, our team of experienced professionals
provides the help and information you need to keep Oracle Incentive
Compensation working for you. This team includes your Technical Representative,
Account Manager, and Oracle’s large staff of consultants and support specialists
with expertise in your business area, managing an Oracle8i server, and your
hardware and software environment.
OracleMetaLink
OracleMetaLink is your self-service support connection with web, telephone menu,
and e-mail alternatives. Oracle supplies these technologies for your convenience,
available 24 hours a day, 7 days a week. With OracleMetaLink, you can obtain
information and advice from technical libraries and forums, download patches,
xxiii
download the latest documentation, look at bug details, and create or update TARs.
To use MetaLink, register at (http://metalink.oracle.com).
Alerts: You should check OracleMetaLink alerts before you begin to install or
upgrade any of your Oracle Applications. Navigate to the Alerts page as follows:
Technical Libraries/ERP Applications/Applications Installation and
Upgrade/Alerts.
Self-Service Toolkit: You may also find information by navigating to the
Self-Service Toolkit page as follows: Technical Libraries/ERP
Applications/Applications Installation and Upgrade.
Do Not Use Database Tools to Modify Oracle Applications Data

Oracle STRONGLY RECOMMENDS that you never use SQL*Plus, Oracle Data
Browser, database triggers, or any other tool to modify Oracle Applications
data unless otherwise instructed.
Oracle provides powerful tools you can use to create, store, change, retrieve, and
maintain information in an Oracle database. But if you use Oracle tools such as
SQL*Plus to modify Oracle Applications data, you risk destroying the integrity
of your data and you lose the ability to audit changes to your data.
Because Oracle Applications tables are interrelated, any change you make using
Oracle Applications can update many tables at once. But when you modify
Oracle Applications data using anything other than Oracle Applications, you
may change a row in one table without making corresponding changes in
related tables. If your tables get out of synchronization with each other, you risk
retrieving erroneous information and you risk unpredictable results throughout
Oracle Applications.
When you use Oracle Applications to modify your data, Oracle Applications
automatically checks that your changes are valid. Oracle Applications also keeps
track of who changes information. If you enter information into database tables
using database tools, you may store invalid information. You also lose the ability
to track who has changed your information because SQL*Plus and other
database tools do not keep a record of changes.
About Oracle
Oracle Corporation develops and markets an integrated line of software
products for database management, applications development, decision
support, and office automation, as well as Oracle Applications, an integrated
xxiv
suite of more than 160 software modules for financial management, supply
chain management, manufacturing, project systems, human resources and
customer relationship management.
Oracle products are available for mainframes, minicomputers, personal
computers, network computers and personal digital assistants, allowing
organizations to integrate different computers, different operating systems,
different networks, and even different database management systems, into a
single, unified computing and information resource.
Oracle is the world’s leading supplier of software for information management,
and the world’s second largest software company. Oracle offers its database,
tools, and applications products, along with related consulting, education, and
support services, in over 145 countries around the world.
xxv
xxvi
Part I
Introduction and Overview
This part contains the following chapters:

■ Chapter 1, "Introduction to Oracle Incentive Compensation"
■ Chapter 2, "Overview of Using Oracle Incentive Compensation"
1
Introduction to Oracle Incentive
Compensation
This chapter discusses the key features and process flows of Oracle Incentive
Compensation. Sections in this chapter include:
■ Section 1.1, "Overview of Introduction to Oracle Incentive Compensation"
■ Section 1.2, "Oracle Incentive Compensation Key Features"
■ Section 1.3, "Oracle Incentive Compensation Integrations"
■ Section 1.4, "What’s New"
■ Section 1.5, "What’s Obsolete"
1.1 Overview of Introduction to Oracle Incentive Compensation

Whether your organization is a start-up or a global enterprise, Oracle Incentive
Compensation provides a unique online application for the design, distribution,
and administration of variable compensation plans. Based on logic that can be
configured or modified by an end user, the application determines:
■ What events are eligible for incentive payments
■ Who should receive credit
■ How the credits are calculated and paid
Everyone who needs to work with incentive information can do so online as part of
a single system of compensation management. For example, the Sales Planner
collaborates with the finance department, marketing experts, and sales
management on configuring new compensation plans for salespeople and allocates
quota to the sales organization. The resulting plans can be rolled out to the sales
Introduction to Oracle Incentive Compensation 1-1

Overview of Introduction to Oracle Incentive Compensation
force for online approval. When the sales force accepts, the new plans are activated
for commission processing in the application.
The application controls the ongoing task of determining incentive payments from
incoming transactions. The first step in this process is collecting transactions from a
source system. The Open Collections feature supports transaction information from
any source, including legacy systems, provided that the other system’s data can be
accessed in the same database instance. This is in addition to the collection abilities
from the out of-the-box integration with Oracle ERP systems, Order Management,
and Receivables.
A typical compensation plan consists of one or more modular components, or plan
elements. Plan elements may reflect variations of commission or perhaps a bonus
based on the accumulated achievement of the sales agent. Plan elements can also be
configured for tracking nonmonetary credits such as managerial points or
production credits.
All modular components used in the system can be configured and reused in
different combinations. Taking full advantage of this capability simplifies system
configuration as well as administration. For example, from a relatively small library
of plan elements, you can configure many compensation plans.
Plan elements consist of modular components that can be freely assigned in
different combinations. These underlying components have several distinct
functions:
■ Revenue Class is a user-defined category of business revenue used to classify a
transaction for compensation and calculation.
■ A Formula determines how the compensation will be calculated.
■ A Rate Table is part of a formula that determines the rate at which achievements
are commissioned.
The Oracle Incentive Compensation Payment process enables the application to
process all the calculated transactions and complete payment. An optional payment
plan can be set up to establish a minimum or maximum payment to a salesperson.
The enhanced payment process enables you to prepare your pay run for each pay
group when due, adjust the calculated pay as needed, and submit the pay run to be
paid. Use this procedure to edit scheduled compensation, hold payment on a
transaction, and submit for payment.
There are three types of payment:
■ Regular Payment: The application collects data, prepares it, and formats it to be
used by a non-Oracle Payable system.
1-2 Oracle Incentive Compensation User Guide

Oracle Incentive Compensation Key Features
■ Accounts Payable Integration: Used for vendors, this method prepares payment
for Oracle Accounts Payable by classifying the resources as suppliers.
■ Payroll Download File: The application collects data and creates a file that can
be used by Oracle Payroll
Pay Group assignment determines the frequency with which a salesperson receives
payment. You exercise control over the total amounts paid to salespeople through
Payment Plans. You can specify a minimum and/or a maximum payment as well as
whether any minimum payments are recoverable or not against future amounts
payable. In addition, there is control over commission payment for each transaction
by a salesperson. Payments to nonemployees such as agents, brokers, and suppliers
are automatically posted to Oracle Payable Invoice Interface Table.
In addition to timely and accurate transaction processing, Oracle Incentive
Compensation serves as a feedback mechanism for the sales organization and
management through eighteen different incentive planning and compensation
reports.
Granting online access to all professionals involved in compensation management,
such as sales planners, sales analysts, and internal and external salespeople, creates
a large, collaborative community of stakeholders who can both use and contribute
real-time information about incentive systems. Oracle Incentive Compensation
supports a wide variety of sales relationships and alternative sales channels, letting
sales representatives and managers access and view compensation information over
the Web. You can use the Year to Date Commission Summary Report to look at
achievements for each period until the current period in a given fiscal year. The
report also has a summary of payments made and outstanding balance for a given
salesperson. Salespeople can analyze their own performance and sales managers
can measure their teams’ performance using the Quota Performance report.
1.2 Oracle Incentive Compensation Key Features

Oracle Incentive Compensation includes the following features:
■ Section 1.2.1, "Incentive Planning"
■ Section 1.2.2, "Compensation Plans"
■ Section 1.2.3, "Quota Assignment"
■ Section 1.2.4, "Quota Approval Process"
■ Section 1.2.5, "Compensating Transactions"
■ Section 1.2.6, "Revenue Classes"

■ Section 1.2.7, "Hierarchies"

■ Section 1.2.8, "Classification Rules"
■ Section 1.2.9, "Classification Rules Hierarchy"
■ Section 1.2.10, "Compensation Groups"
■ Section 1.2.11, "Data Collection"
■ Section 1.2.12, "Calculation"
■ Section 1.2.13, "Payment"
1.2.1 Incentive Planning

The objective of Incentive Planning is to steer sales force effort towards achieving
the organization’s sales target through compensation plans. Incentive Planning
helps to automate the sales budgeting process by giving salespeople a tool to
communicate their quota estimate to their sales managers. Sales managers can then
allocate a quota based on their direct salespersons’ estimates. Incentive Planning
generates compensation plans with quotas based on sales managers’ quota
allocation and lets them track the approval process. Sales managers can apportion
quotas between departing directs and new hires. Incentive Planning Contract
Approvers review and approve compensation plans, and Incentive Planning
Finance Managers then pass the approved compensation plans to Oracle Incentive
Compensation Administration for commission processing.
In addition, Incentive Planning analysts are able to assign new sales roles to
salespeople and move salespeople to other compensation groups. There are reports
to locate those salespeople with quotas outside a value range for senior
management control purposes and also there are reports to calculate the quota
overassignment percentages between each level of sales management hierarchy.
Quota overassignments are quotas that are allocated to subordinate salespeople
from a manager that add up to more than 100 percent of the manager’s quota.
1.2.2 Compensation Plans

The following information explains how you can use compensation plans to
correctly compensate and provide incentives for your salespeople:
■ What Is a Compensation Plan?
■ Purpose of Compensation Plans
■ Using Compensation Plans

What Is a Compensation Plan?

The conditions that control incentive compensation are defined in a compensation
plan. A compensation plan captures your organization’s unique practices for
paying compensation, with individual rules that determine commission and track
achievement.
You have complete flexibility to create incentive compensation plans that you can
customize for your company’s unique sales situations. You can:
■ Create as many compensation plans as you need
■ Customize existing plans for individual sales representatives or situations
■ Build compensation plans using calculation expressions, rate tables, formulas,
and other building blocks from existing compensation plans
■ Control the validity of all aspects of the compensation plan using precise start
and end dates
Purpose of Compensation Plans

A compensation plan is a set of elements governing the compensation payments to
a salesperson. Using compensation plans, you can:
■ Determine commissions, bonuses, and nonmonetary compensation
■ Provide incentives to salespeople to achieve specific and measurable sales
goals, including yearly and periodic sales targets, as well as sales targets for
individual sales categories. Sales categories are defined in Oracle Incentive
Compensation as a hierarchy of revenue classes, which are often based on
product or service types, but can also be based on factors like target markets,
industry, or customer account.
■ Vary compensation rates based on user-defined measures, such as quota
achievement, gross sales, and unit sales
■ Vary quotas or compensation rates based on the revenue class hierarchy
■ Stage compensation payment over the life of a sale
■ Specify compensation accelerators for sales promotions
■ Specify goals to track achievement for recognition programs
■ Customize plans for individual salespeople

■ Specify plan changes to occur on specific dates
Using Compensation Plans

A compensation plan relates to a sales role within your organization. Different roles
require different pay components, and therefore different compensation plans.
In a sales organization that has highly varied tasks, much overhead is required to
create a different compensation plan for every salesperson. To avoid the costs
associated with maintaining a large number of plans, you can create a set of
compensation plans that target general compensation needs for most of your sales
force, then adjust individual quotas, goals, accelerators, and compensation rates
when you assign the plan to an individual salesperson.
As you build a variety of plans for your sales force, remember that you can assign a
formula to more than one plan element, and you can assign a plan element to more
than one compensation plan.
1.2.3 Quota Assignment

In this section, you will read about:
■ Overlay Salespeople
■ Quota Distribution Techniques
■ Overassignment Percentages
Overlay Salespeople
Checking the overlay check box enables you to segregate your salespeople into
either overlay salespeople or nonoverlay salespeople. Overlay salespeople are not
part of a distributed quota of a manager.
Some organizations define overlay as nonrevenue sales credits. The term
"nonrevenue sales" indicates that the value is not posted to General Ledger.
Consider the following example.
The Account Manager and the Hardware Salesperson of a company are the direct
participants and they are responsible for closing the sale. The Business
Development Manager is considered an overlay salesperson because he or she
made contact with the customer on more general sales activities but was not
responsible for price negotiations for example, that is specific to this sale. If the sale
value is 10,000, an extract of the transaction lines would look like this:

Sales Role Revenue Type Sales Value

Account Manager Revenue 6,000
Hardware Salesperson Revenue 4,000
Business Development Manager Nonrevenue 2,000
The Business Development Manager in the above example received 20%

nonrevenue credit for the sale:
2000/(6000+4000) = 20%
The manager’s commission on this sale will depend on the compensation plan rules
and rate table that can be applied to the transaction upon calculation.
Quota Distribution Techniques

You can perform an initial distribution of quota by using the Quota Allocation
Details page. There are several methods for allocating quotas:
■ Even distribution of manager’s quota over immediate direct salespeople, with
or without an overassignment
■ Minimum Quota allocation as preset on the Sales Role Detail page
■ Equal distribution: Allocation to each direct salesperson a quota amount as
much as the manager’s, with or without an overassignment
Overassignment Percentages
The table below shows a manager’s quota and how the manager can overassign the
quota to his subordinates at a rate more than 100 percent.
Main Support Total

Hardware Software Revenue Service Quota Overlay
Manager 3000 1000 4000 160 4160 No
Direct 1 1200 330 1530 75 1605 No

Direct 2 1200 330 1530 75 1605 No
Direct 3 1200 400 1600 80 1680 No
Direct 4 3000 1000 4000 160 4160 Yes

The Direct overassignment is 117.55%

Explanation of calculation:
Total quota excluding overlay is 1605+1605+1680= 4890
Manager’s quota = 4160
Therefore, direct overassignment is 4890/4160 = 1.1755
This means that this manager has divided his or her quota to the subordinate
salespeople plus 17.55% extra.
If any of these directs have subordinate salespeople and they in turn have quota as
well, then a street level overassignment calculation will be performed. If the street
level total quota is 5000, then the street level overassignment is 5000/4160, or
120.19%.
Overassignment percentages exclude quota allocated to overlay salespeople, such
as Direct 4, as they are regarded as nonprimary salespeople. See section on overlay
salespeople for explanation of the term overlay.
1.2.4 Quota Approval Process

This section covers:
■ Approval Sequence
■ Workflow
Approval Sequence
After a quota is locked by the sales manager, the sales manager needs to generate
the compensation plan. The compensation plan incorporates the quota allocated by
the sales manager to the direct salesperson, calculates the commission rates based
on the input of On-Target-earnings and quota, and incorporates the Terms and
Conditions text. The electronic document as a whole is referred to as a contract.
Next, using Oracle Sales Online, the Contract Approver reviews the contract and
either accepts or rejects it.
If the Contract Approver accepts the contract, then the sales manager distributes the
contract to the direct salesperson. The salesperson, using Oracle Sales Online, can
then view, accept, and print the contract.
If the Contract Approver rejects the contract, then the sales manager needs to adjust
the quota if that is the solution to the rejection. The approval process repeats after
the sales manager locks the quota for a specific resource again.

Workflow
Oracle Workflow must be installed so Incentive Planning users can be notified by
email to prompt the email receiver that an action is required to move along the
approval process for the compensation plans. Refer to the Implementation Guide
for instructions on how to customize workflow notification messages for Sales Force
Planning.
1.2.5 Compensating Transactions

You choose the source transactions, the orders, invoices, or customer payments on
which to base your compensation payments. Transactions are classified based on
business rules, into revenue classes. A revenue class is assigned to a plan element, a
set of conditions a salesperson must meet to be eligible for compensation. For each
revenue class assigned to a plan element, you need to specify how much
compensation you want to award for each type of transaction you collect. Each sale
corresponds to one or more transactions, depending on when during the life of the
sale your organization pays compensation.
For each revenue class, you define transaction factors or multipliers for each type of
transaction relevant to that class. Transaction factors help you stage sales credit
(sales amount accredited to a salesperson) over the life of a sale, assigning
percentages of the transaction amount to the events that are important to your sales
organization.
When calculating the compensation payment, the sales credit is multiplied by the
transaction factor you defined for that transaction type, normally resulting in net
sales credit for the compensation transaction.
Transaction types supported by Oracle Incentive Compensation are listed below.
They are automatically identified when collecting against an Oracle ERP system
(Accounts Receivable, Order Management). For external sources, distinguish the
transactions by populating this column before collecting into Oracle Incentive
Compensation:
■ Order Booked: The order is processed when it is booked and its status changes
to booked.
■ Invoice: The invoice is processed when posted to Oracle General Ledger. After
it is posted, no changes can be made to the invoice.
■ Payment: Payment is received in Oracle Receivables.
■ Take Back: When the invoice due date grace period is exceeded, the outstanding
amount of compensation credited for this sale is taken back.

■ Credit and Debit Memo: An invoice is fully or partially reversed (credit) or

increased (debit) and posted to Oracle General Ledger.
■ Give Back: A payment is received for a take back.
■ Manual Adjustment: An adjustment is made.
■ Writeoff: A sale is written off the books for a variety of reasons and posted to
Oracle General Ledger.
For all revenue reducing transactions, such as take backs and credit memos, the
application creates a new transaction for a negative amount of the sales credit.
Note: The application does not check to see whether the salesperson(s) credited on
the original invoice is the same salesperson(s) on the revenue reducing transaction.
Therefore, it is possible to reduce a salesperson’s commission on transactions for
which he or she did not receive sales credit previously.
When you choose a particular transaction factor, you are specifying that you want
to pay compensation based on the state of the compensation system at the time that
transaction occurred. For example, if an organization chooses to pay 50% on order
and 50% on invoice, one compensation payment is made based on the plan
elements on the date of the order and the remaining payment is made based on plan
elements on the date the invoice is posted.
1.2.6 Revenue Classes

A revenue class is a user–defined category of sales for which your organization
awards compensation. Each revenue class represents a different type of sale for
which your organization pays compensation. Thus, different companies have
different revenue classes because each sales organization awards compensation
differently. By assigning revenue classes, you specify different ways in which each
salesperson can earn compensation.
After defining your organization’s revenue classes, you assign one or more revenue
classes to a plan element and assign the plan element(s) to a compensation plan.
Many companies award compensation based on the types of products or services
their salespeople sell. Depending on the business practices of your sales
organization, you can award compensation based on factors other than products or
services sold. For example:
■ Your sales organization can have customer account teams, where salespeople
only receive compensation for sales to their assigned set of accounts. In this
case, each customer account can be a separate Oracle Incentive Compensation
revenue class.

■ Your company can organize its sales strategy around expansion into new
markets, where each new market can be a separate revenue class.
■ Your company can use product–based incentive compensation, paying
compensation only for sales made in a salesperson’s assigned set of products.
For example, an organization awards compensation based on the types of products
or services its salespeople sell. At the broadest level, the company sells PCs,
peripherals, education services, consulting services, and support maintenance
services. While some types of salespeople, such as resellers, are authorized to sell
only a subset of this offering, the company awards compensation to some of its
salespeople for all types of products and services. Thus, for the company, each
product or service category is an Oracle Incentive Compensation revenue class.
1.2.7 Hierarchies
While the functions of hierarchies differ, the concepts and terminology used are the
same for all hierarchies.
The term dimension refers to a named and defined type of hierarchy. As many
hierarchies as needed can be created for each dimension. However, only one
hierarchy per dimension can be effective at any given time.
A dimension is a high-level hierarchy type that is based on a table, which must be
defined in Oracle Incentive Compensation. A dimension can be used
■ To create a hierarchy that you use to define rules, or
■ To hold the primary and foreign key links between Oracle Incentive
Compensation and other tables
Oracle Incentive Compensation provides one default dimension: Revenue Classes.
Create as many dimensions as you need, for example, for product code or customer,
to use for referencing in defining the rules classification. To define a dimension,
these criteria must be met:
■ The dimension must be based on an existing table in the database.
■ There can be only one dimension per base table.
■ The table must be defined in Tables in Oracle Incentive Compensation.
■ The database table must have either a numeric primary key assigned or have no
primary key and numeric columns in the table.
■ Table information defined in Tables must accurately describe the table.

1.2.8 Classification Rules

Classification rules are used by Oracle Incentive Compensation to determine how
transactions are classified as they enter the application from a feeder system. Each
rule contains one or more conditions. These conditions specify the characteristics a
transaction must have to classify into a given revenue class. Each rule is associated
with a revenue class. During classification the revenue class is assigned to a
transaction when it passes all conditions in the rule. The transaction attribute value
expresses each condition.
For example, an organization awards compensation based on the type of products
or services sold, thus defining a transaction attribute for product code. This
transaction attribute is represented in the compensation transaction tables as the
column PROD_TYPE. To determine whether to award consulting revenue, the
organization checks whether the product code is CON. Vision creates a rule to check
for this type of revenue. The rule has one condition: PROD_TYPE = CON.
Because the application classifies a transaction by checking values of specific
transaction attributes, be sure to specify all attributes you need for classification
when you set up transaction collection.
1.2.9 Classification Rules Hierarchy

The following information explains the hierarchy of revenue classes classification
rules and how transactions roll through the hierarchy to determine compensation:
■ The Rules Hierarchy
■ Comparing Transaction Attributes with Revenue Classes Classification Rules
■ Multiple-Condition Rules
■ Changes to Revenue Classification
The Rules Hierarchy

The rules hierarchy determines the order in which the rules are evaluated. After a
match is made, the application removes the transactions from the classification
phase. Rules are evaluated from top to bottom and from right to left in the rules
hierarchy.
When you define classification rules, notice the common conditions among the
classification rules. For economy of expression and ease of maintenance, assign the
common conditions once to the parent of rules that share the same conditions. For
example, the Standard Multimedia PC and the ATO Multimedia PC are in the same
hierarchy and share the condition Product_Code=MM. This condition is specified

once in the application for the parent rule of the two rules that differentiate
Standard Multimedia PC and the ATO Multimedia PC.
Comparing Transaction Attributes with Revenue Classes Classification

Rules
When a compensation transaction passes a rule (all conditions are true), the
application then compares the children of that rule, working left to right, until it
finds a match. Then it looks at the children of that rule, and so on, and stops if it
cannot find a match in the children. It returns the revenue class of the last matching
rule. After the classification process, the matching revenue class’ name is marked on
each transaction as an additional attribute.
Multiple-Condition Rules
If any one of several conditions associated with a revenue class qualifies a
compensation transaction to be assigned to a class when the condition is true, you
can define multiple sibling rules in the hierarchy, one for each condition. Because
the application evaluates other sibling rules if a transaction does not satisfy the first
rule on a level in the hierarchy, the application processes these rules as if they were
joined by an AND operator. When a transaction fails a rule, the application
compares the transaction attributes with other sibling rules from left to right.
For example, suppose that an organization classifies products by ID number and
decides to sell its products via telesales in addition to its existing direct channel. The
organization can add a new rule:
■ PROD_TYPE BETWEEN 1201 and 1600 (existing condition or rule)
■ CHANNEL_TYPE is 03 (new rule)
Therefore, if a transaction’s attributes satisfy all rules, then the transaction will
classify against the revenue class. If the OR condition is used, then the transaction
will classify against that revenue class if the transaction attributes meet any of the
revenue class’ rules.
If several revenue classes share multiple conditions, you can minimize data entry by
creating a parent rule that includes the shared conditions, and by defining only the
unique conditions as child rules.
Changes to Revenue Classification

You can make changes to your revenue classification setup. You can add, change, or
delete:
■ Revenue classes

■ Revenue classes in a hierarchy

■ Rules in the classification rules hierarchy
■ Conditions for a rule
1.2.10 Compensation Groups

The following information explains how hierarchies of compensation groups are
used to compensate multiple salespeople for one sales transaction:
■ Purpose of Compensation Groups
■ Credit Sharing
Purpose of Compensation Groups

A compensation group is a group of salespeople who share sales credit, directly or
indirectly, when a sale is made. They are placed together in a hierarchy to accurately
account for the payment of commission and sales credit. For example, at one
company, when salespeople close a sale, they receive commission, their managers
receive sales credit toward their quotas, territory sales managers receive sales credit
from the manager’s transactions, and territory sales consultants also receive indirect
credit for performing consulting work that helped to close the business.
In many sales organizations, multiple salespeople can receive sales credit for the
same commission transaction. If you choose to compensate multiple salespeople for
the same commission transaction, you use a compensation group hierarchy to
specify the relationships among the credit receivers.
If a manager has two salespeople in his or her group and three more salespeople in
a compensation group below him or her in the hierarchy, then transactions from the
salespeople in the lower group will roll up to the manager and also to the two
salespeople in the manager’s group.
A salesperson can have more than one sales role and belong to more than one
compensation group. For example, at one organization, sales representatives A, B,
and C are in the same compensation group because their sales roll up to manager X.
Manager X also belongs to a different compensation group that includes a separate
group of salespeople who are working on another project.
A salesperson can have the same role in multiple groups, or multiple roles in the
same compensation group. In either case, sales commission can be calculated with
no problem. However, if a salesperson is in multiple compensation groups with
different roles, and another salesperson’s transactions are set to roll up to him along
multiple paths, the application may not be able to process the commissions

correctly. See Credit Sharing or Phases of Calculation for more information on credit
rollups.
Credit Sharing
You can allocate sales credit for a commission transaction:
■ To one or more of a salesperson’s managers in an organizational hierarchy. This
type of credit allocation is called a rollup, because the application rolls credit up
within the sales organization.
■ When transactions are processed, the manager(s) automatically receive all sales
credit applied toward subordinate salespeople, provided that they have the
same revenue classes as their subordinates. Therefore, the manager need not be
named on the transaction.
■ To peers of a salesperson. To enable Oracle Incentive Compensation to process a
single transaction that credits more than one salesperson for a single
transaction, each transaction that is fed from feeder system(s) must identify all
the salespeople to be credited. Therefore, the system(s) must allow the user to
create orders and/or invoices with many transaction lines, each line crediting a
salesperson.
Salespeople need not be members of the same Compensation Group to share
credit for the same transaction.
1.2.11 Data Collection

You can also read about:
■ Listing Notification
■ Creating Compensation Transactions
■ Updating Compensation Transactions
■ Purging
The Collections function of Oracle Incentive Compensation is responsible for
collecting compensation transactions from different feeder systems, including AR,
OM, and external sources, and storing them in an API table (CN_COMM_LINES_
API). The compensation transactions subsequently can be imported from this API
table into Oracle Incentive Compensation.
A compensation transaction is a record which identifies a compensation event (such
as the sale of an item). The main attributes of a transaction are the:

■ Type of compensation event

■ Order
■ Invoice
■ Payment
■ Takeback
■ Giveback
■ Credit and Debit Memo
■ Manual
■ Writeoff
■ Identity of the person who is directly credited for the event
■ Value of the transaction
■ Processed date of the transaction
A transaction may optionally contain other attributes, such as transaction currency,
product identification, and customer identification.
When compensation transactions are loaded into Oracle Incentive Compensation,
they are stored in the CN_COMMISSION_HEADERS table. The columns in this
table are direct equivalents of columns with the same names in CN_COMM_
LINES_API.
Collections allows you to collect compensation transactions from the Oracle
Receivables and Oracle Order Management applications. These are known as
Standard Transaction Sources. You can also create your own Transaction Sources
from the database tables of any legacy applications that you wish. The process of
setting up Collections to collect from a legacy system consists of the following
components:
■ Source Tables. Identify the tables from which the transactions are to be built.
■ Queries. Specify how these tables are to be joined together and how
appropriate rows are identified.
■ Mappings. Specify how data from the Source tables are used to populate the
destination fields in the compensation transaction.
■ Actions. Specify filters to remove unwanted transactions, and extra logic to be
incorporated into the collection procedure.

■ Collection Package. Generate a collection package which will build

compensation transactions based upon the setup from the previous steps, and
will store those transactions in CN_COMM_LINES_API.
■ Concurrent Program. Collect transactions from the required transaction source
whenever you want, by running a predefined Concurrent Program.
For example, assume that a Transaction Source is an Order database and that each
order consists of an Order Header containing general information about the order,
plus a set of Order Lines where each Line represents an ordered item. This
information is stored in an Order Header table (L_ORDER_HEADERS) and an
Order Line table (L_ORDER_LINES). In the Order system it is possible for a number
of salespeople to receive credit for each Order Line. There is therefore also a Sales
Credits table (L_SALES_CREDITS) to hold this information.
The end result of setting up Collections for a particular Transaction Source is a
PL/SQL package that is stored in the applications database. The Collect procedure
within this package builds compensation transactions from the Transaction Source
and stores them in CN_COMM_LINES_API. The Collect procedure executes the
listing notification and the creation and updating of compensation transactions.
Listing Notification
This feature makes a list of all individual transaction lines from the Transaction
Source for which compensation is payable. The feature stores the unique identifier
of each line in a Notification Table. In the example, the list of individual transactions
is obtained by examining the Order Lines table, L_ORDER_LINES, and the unique
identifiers of rows in this table are stored in the Notification Table.
Creating Compensation Transactions

For each unprocessed individual transaction line identifier in the Notification Table,
you can build as many compensation transactions as you need. In the example
Transaction Source, it is necessary to join together the Order Lines and Sales Credits
tables. Suppose there is a particular Order Line for which three salespeople earned
credit. The Order Line identifier was stored in the Notification Table, but you need a
join to the Sales Credits table to find out that three transactions need to be created
and three salespeople must be identified.
The compensation transactions are created using a single SQL query. As a
minimum, this query must join together all the tables necessary to decide the
number of individual compensation transactions which are created from each line
item (L_ORDER_LINES and L_SALES_CREDITS in the example). The tables used
in this query are referred to as the Direct Mapping tables.

Updating Compensation Transactions

Suppose that you need to include the salesperson’s territory identifier into each
compensation transaction but this information is stored in a separate L_
TERRITORIES table. The key of this table is Salesrep_ID. There are two ways that
this information can be pulled into the compensation transaction.
■ The first way would be to add a join to this table in the query that creates
compensation transactions, thus making it a Direct Mapping table. This is a
valid approach, but not always practical. For example, if not every salesperson
has territory information, then you have to know how to make the join to this
table an Outer Join, without which no compensation transactions will build for
salespeople without territories. If you need your compensation transaction to
contain 10 informational fields, all of which are sourced from different tables,
the Collection Create query would have to join all these tables together,
resulting in a query that is difficult to maintain and does not improve
performance.
■ You can set up Collections to delay populating territory identifier fields until
after the initial creation of the compensation transaction. After the
compensation transaction has been created and inserted into CN_COMM_
LINES_API, the territory identifier field is populated by a series of update
statements. For example:
UPDATE cn_comm_lines_api api SET attribute1 =
(SELECT territory_name FROM l_territories lte WHERE lte.salesrep_id =
api.salesrep_id);
When a destination field in the compensation transaction is populated in this
manner, it is known as an Indirect Mapping.
Purging
There is no purge utility in this release of Oracle Incentive Compensation.
1.2.12 Calculation
Calculation is a process used by the system to calculate commission and bonus
plans for salespeople. This calculation section explains:
■ Types of Calculation
■ Phases of Calculation
■ Unprocessed and Failure Statuses

■ Calculation Process
Types of Calculation
■ Commission Incentive: Transaction based compensation.
■ Bonus Incentive: Compensation based on aggregated transactions.
Phases of Calculation
When you calculate a set of transactions, the application performs these steps:
■ Revert: This feature restores the transactions within your specified parameters
back to their original unprocessed state. When a full calculation is performed,
the application deletes any system-generated (rollup) transactions and reverts
the status of transactions to unprocessed.
■ Classification phase: The application checks the revenue classification rules
that have been defined for the affected transactions, and determines if the
transactions were successfully classified. Using the classification rules you
defined, the application is able to determine a unique revenue class for each
transaction.
■ Rollup phase: Oracle Incentive Compensation runs a process to determine all
salespeople who should receive credit for this transaction based on the rollup
date, and the salespeople hierarchy effective for that date. For every credit
receiver, the application creates a new system-generated transaction for each
manager entitled to a rollup credit.
■ Population phase: Oracle Incentive Compensation identifies the appropriate
plan elements that are associated with the revenue classes that have been
matched with each transaction. The application updates each transaction with
the plan element information.
■ Calculation Phase: Based on the information gathered, Oracle Incentive
Compensation performs calculation on all transactions for salespeople during
the specified period.
Unprocessed and Failure Statuses

The following statuses can occur when a transaction has not been processed or if
there is a failure during one of the calculation phases.
■ Unprocessed: The transaction has not been processed. The application displays
a status for unprocessed transactions in transaction status.

■ Failed Classification: Indicates that the transaction did not have a matching
revenue class. Be sure that you have defined and synchronized revenue
classification rules before further investigation.
■ Failed Population: The transaction did not match the quota rules for the
credited salesperson. Although the transaction had a matching revenue class,
the credit salesperson did not have the revenue class assigned to his or her plan
element.
■ Failed Calculation: The transaction failed to be calculated. Oracle Incentive
Compensation indicates a failed status for transactions that have failed the
calculation phase in the transaction status. Check your calculation rules, ensure
that your calculation expressions, rate tables (if applicable), plan elements, and
compensation plans are valid.
Calculation Process
Efficient calculation is accomplished by automatically recording in the Notify Log
every change in the system that affects the calculation. The log also lists what part
of the calculation is affected and therefore must be rerun as a result of the event.
For example, a new transaction is collected and all salespeople affected by that
transaction are recorded in the log. Other examples of events include changes made
to rate tables, compensation plans, and classification rules. The log also records the
point where calculation needs to restart.
When you perform an incremental calculation, the application calculates everything
in the notify log. For better performance, use the incremental calculation for your
normal calculation needs.
You can choose to perform a full calculation to recalculate everything within a given
date range. The full calculation takes longer than the incremental calculation.
1.2.13 Payment
In Oracle Incentive Compensation, payment is a multistep process. This release of
Oracle Incentive Compensation has a substantially upgraded Payment functionality.
The six major enhancements include automated posting, lockable payment
worksheets, the ability to add and track comments on payment worksheets, an
enhanced payment approval process, manual payment adjustments on the payment
worksheet, and a Payment Worksheet History page. See Section 10, "Payment with
Payruns", for detailed information.

Oracle Incentive Compensation Integrations
Payment in Oracle Incentive Compensation is made by creating payruns. The

application does not actually pay people, but a list is created, which is then sent to
Payroll.
Create a Payrun using Transaction > Payment. You can view and adjust the
payment amount for each transaction, for each salesperson (Transaction > Payment
> Payrun Details). Select a salesperson on the Payrun Details page to view or adjust
the payment for that person.
When ready to pay, go to Requests > Payment, click the Submit Request link, and
search for the payrun, and Pay Payrun from the list.
The CN_POSTING_DETAILS table is updated with pay information. Pay data for
non employees go further when posted to the Oracle Payable Invoice Interface
Table (user activation required).
1.3 Oracle Incentive Compensation Integrations

Oracle Incentive Compensation integrates with other applications in the Oracle
e-Business Suite to optimize the powerful functions of the product. Interface
programs systematically link two or more systems to each other. With Oracle
Incentive Compensation and custom interfaces, you can accomplish some of the
critical tasks of an incentive compensation process:
■ Collect sales transaction data from Oracle Receivables, Oracle Order
Management, and other legacy sources
■ Pay supplier contact type resources using Oracle Accounts Payable
■ Integrate with Oracle Payroll for employee type resources
■ Generate reports related to compensation and other useful sales benchmarks.
■ Use Oracle Sales Online for Income Planner and salesperson self service needs
Using Oracle CRM Foundation Resource Manager module, you can:
■ Maintain sales roles and compensation groups
■ Maintain resource information
As a customization, you can create multiple interfaces, referred to as application
programing interfaces (APIs), to bring transactions into Oracle Incentive
Compensation and to send transactions out to other systems. Oracle Incentive
Compensation transactions can originate from a sales order, a customer billing, a
customer payment, or other business functions.

1.3.1 Overview
Oracle Incentive Compensation exchanges information with other products within
the Oracle e-Business Suite. Transactions, the raw material that fuels Oracle
Incentive Compensation, are collected from the two standard transaction sources,
Oracle Receivables and Oracle Order Management, or from any legacy system
through open APIs.
Oracle Receivables and Oracle Order Management are out-of-the-box collection
packages that provide sales transaction information that forms the basis for
calculating incentive compensation.
Examples of the types of transaction data Oracle Receivables can provide include:
■ Invoices
■ Credit and debit memos
■ Payment postings
■ Write-off postings
■ Claw-back (Take-back) postings, which are generated when an invoice due
date goes beyond the set grace period. The credit for the sale is deducted
from the salesperson’s sales credit.
■ Give-back postings which are generated when a past due invoice that has
been deducted from the salesperson’s sales credit is paid. The salesperson
receives the credit.
■ Revenue Adjustment postings
From Oracle Order Management, you can collect booked orders and adjustments to
booked orders. In release 11i of Oracle Applications, Order Management replaces
the Order Entry system interface for collecting order information. Oracle Incentive
Compensation, as well as all other applications in the Oracle e-Business Suite, must
use the Oracle Capture module to interface to Order Management.
Resource Manager is the common source for resource definition, and the ability of
Oracle Incentive Compensation to read Resource Manager directly eliminates the
need to create commonly used definitions and relationships in multiple
applications. Use Resource Manager to:
■ Create resources (salespeople)
■ Create sales roles and assign salespeople to them
■ Create compensation groups, the basis of a sales hierarchy

■ Create the sales credit rollup hierarchy

In addition to these traditional sources of information, release 11i of Oracle
Incentive Compensation provides two-way integration to applications such as
Oracle Sales Online, Business Intelligence Systems (BIS), and other applications
within the e-Business Suite.
Oracle Sales Online provides a sales performance and compensation forecasting
tool for sales representatives and managers, based on current compensation plans.
It is also a means for monitoring sales force performance through self-service
compensation reports, the Year-to-Date Commission Summary, the Quota
Performance Report, and a set of pre-seeded Discoverer worksheets. Salespeople
can view their compensation summary and break down their commissions by deal,
product line, period, adjustments, or transactions. They can also use Sales Online to
view projected compensation based on opportunities they enter into the system or
commit to the forecast.
Compensation information is also made available to Oracle Sales Intelligence.
1.3.2 Oracle Sales Online

The Compensation tab > Compensation Plan subtab in Oracle Sales Online can be
used by:
■ A salesperson to accept a compensation plan.
■ A manager to distribute compensation plans for salespeople in his or her
hierarchy.
If salespeople have access to Oracle Sales Online, they can submit their estimate of
their own Quota and either accept or reject their Compensation Plans when the
Plans are distributed to them by their manager via Oracle Sales Online.
Perform the following procedure to enable access to the Compensation tab in Oracle
Sales Online.
Prerequisites
System Administrator responsibility is required. This procedure is performed in the
Forms version of Oracle Incentive Compensation.
Steps
1. In the System Administrator Navigator, select Security.
2. Expand the Security menu by double-clicking on Security.

3. Double-click User.
4. Double-click Define.
5. Enter your User’s name in the User Name field. Start the search from the Menu
bar by clicking View > Query by Example > Run. (Pressing the Control key and
the F11 key together performs the same function.)
6. Assign Sales Online user responsibility to the user.
7. In Resource Manager, assign the role type of Sales to the user with a manager or
member role.
8. Assign Group usage Sales and Telesales for the group to which the user
belongs.
Year to Date Summary

This report is an overview of a salesperson's achievements, commission and bonus
earnings and advances or draws.
The figures are grouped by period and by plan element. Super user can control
which plan element appears as a quota or bonus category through the Quota Group
check box on the Plan Element form. The pay out section is grouped by earnings
type and by period.
Prerequisites
You must have access to Oracle Incentive Compensation through Oracle Sales
Online.
Steps
1. Click the Compensation tab and click the Year to Date Summary subtab.
2. Select a credit type from the drop-down list. Functional Currency is the default
setting.
3. Select a reporting currency from the drop-down list. Functional Currency is the
default setting.
4. Select a fiscal year from the drop-down list.
5. Click Apply.
Planning
Planning allows both managers and salespeople to provide feedback about the
estimated sales amount that they feel is achievable.

Prerequisites
A compensation plan must already be created.
Steps
1. Click the Compensation tab and click the Planning subtab.
The My Compensation Groups page appears.
2. Select an organization from the drop-down list.
3. Select an effective date. You can click the calendar icon to open a pop-up
calendar.
4. Any compensation groups within the parameters is displayed below.
Guidelines
For more information, see Incentive Planning in Chapter 3.
Compensation Plan
This subtab is divided into two areas: My Compensation Plans and My Salespeople.
As a manager, you can see compensation plans for which you are responsible in the
first area and also the resources to whom the plans can be assigned. You can then
distribute compensation plans in the My Salespeople area.
Steps
In the Distribute column, check the check box for each plan you want to distribute.
Click Distribute.
Income Planner
Income planner enables salespeople to plan their sales volumes to reach their
commission earning goals. A salesperson can enter a Commission Forecast number
and see the amount of commission he or she will earn, based on their compensation
plan. Click the Compensation tab in Oracle Sales Online to access Income Planner.
To use Income Planner in Oracle Sales Online, you must have assigned a forecast
input expression and a forecast output expression to the formula used in your
Compensation Plan in Oracle Incentive Compensation. When you create a formula,
you can assign two input expressions and two output expressions. You can assign a
regular input expression for production and a forecast input expression for Income
Planner. You can do the same for the output expression.

To enable Income Planner in Oracle Sales Online, perform the following procedures
in Oracle Incentive Compensation.
Steps
To create Forecast expressions, do the following:
1. Click the Incentive tab and click the Expression subtab.
The Calculation Expression page appears.
2. Click Create to open a blank page.
3. Enter a name for the input formula.
4. In the Details area, enter Forecast Expressions from the Type drop down list.
5. In the Expression Block, select your Expression fields. Forecast Amount MUST
be one of the elements selected as part of your expression if it is to be used in
Oracle Sales Online.
6. Click Update to save your input expression.
7. Repeat steps 2 through 6 to create an output expression.
Note: The output expression must contain Rate Table Result as the first element
selected and Forecast Amount should appear in the expression as well.
8. Click Update to save your output expression.
To assign your Forecast expressions to the formula in your plan element, do the
following:
1. Click the Formula subtab in the Incentive tab.
2. Select the formula you want from the table or use the search parameters to
search by name, type, or status.
The Formula Definition page appears.
3. Click the Expressions link to open the Expressions page.
4. In the Input area, select your input forecast expression from the drop down list.
5. In the Output area, select your output forecast expression from the drop down
list.
6. Click Update to save your work.
7. Perform this series of steps for each formula in your compensation plan.

8. When making revisions to a saved page, click Restore to return to the

previously saved version.
Guidelines
For example, a salesperson’s compensation is based on a revenue quota and the rate
table tiers relate to achievement as a percentage of the quota. Because the forecast
results are hypothetical figures, the forecast formula does not affect the actual
achievement result. In this case, suppose the input forecast formula is Forecast
amount/TARGET and the output forecast formula is Rate Table Result*Forecast
amount. The input formula expresses the proportion of the forecast amount to the
quota, and the output formula applies a commission rate to the forecast amount.
The commission rate chosen depends on the salesperson’s achievements to date as
compared to the commission rate tiers.
A forecast amount based on each plan element is displayed if the Interest Type from
Oracle Sales is mapped to the plan element.
Reports
Users of Oracle Sales Online can click the Reports subtab of the Compensation tab
to see three Oracle Incentive Compensation reports:
■ Year to Date Summary
The Year to Date Summary is an overview of a salesperson's achievements,
commission and bonus earnings and advances or draws. This report is
accessible by default by the Manager, Salesperson, Incentive Compensation
Payment, and Incentive Compensation Super User responsibilities.
■ Quota Performance
This report is a snapshot of salespeople achievement and earnings.
Achievements are shown against interval to date quota and annual quota.
Earnings total are broken down by period to date and interval to date.
■ Commission Statement
This report shows transaction details broken down by period for a salesperson.
It is configurable and you can hide or show selected columns. You can use
search parameters to make the report specific to your needs.

Top Performers Bin

The Top Performers bin in Oracle Sales Online enables you to monitor the
performance of your direct reports and indirect reports in a number of ways. You
can:
■ View total payments by quarter.
■ Drill down to the top performers reports.
■ Show reports for direct and indirect salespeople in the same organization or
across organizations.
■ Show Year to Date as well as quarterly information.
■ View payments and earnings in the currency you select.
■ View the payments and earnings for the accounting calendar by manager.
To set up the Top Performers bin on your Oracle Sales Online home page, perform
the following procedure.
Prerequisites
Steps
1. Log in to Oracle Sales Online.
2. Click the Profile icon in the upper right.
A side panel menu opens.
3. Under Sales Online, click the Home Page link.
The Home Page Preferences page appears.
4. In the Narrow Bin Preferences area, any bins that have already been set up are
displayed. If no bins have been set up yet, the columns are contracted.
5. Click Add New Rows.
6. The Narrow Bin Preferences area expands and fields become available in the
Bin Name column.
7. Select a bin number in the Bin Number column.
This controls the order the bins are displayed on the Home page. This is a
required field. If this is the only bin on the Home page, select 1.
8. In the Bin Name column, select Top Performers from the drop-down list.

9. Click Update. A confirmation message appears at the top of the page.

10. Click the Home tab.
The Top Performers bin is displayed in the upper left part of the page.
11. You can edit the parameters of the Top Performers bin. Click Edit in the bin
itself or during setup steps 7 through 9 above.
The Top Performers Parameters page appears. Select appropriate scaling from
the drop-down list.
Forecast Hierarchy Drilldown to Year to Date Summary

You can drill down to the Year to Date Summary from the Forecast page in Oracle
Sales Online. Perform the following procedure to do this:
Steps
1. Click the Forecast tab.
The Forecast page appears.
2. In the Subordinate Forecasts area, click the icon in the Compensation column to
the far right of the table.
3. The Year to Date Summary page appears.
1.3.3 Oracle Resource Manager

Resource Manager is used to maintain roles, resources, the sales credit rollup
hierarchy, and the incentive planning hierarchy.
Defining Roles
A Role may encompass one or more job descriptions and job titles. Use Roles to
assign jobs to resources, resource groups and resource teams. Oracle Resource
Manager is delivered with pre-defined Roles for all CRM modules. Use this
procedure to define additional custom Roles for your enterprise.
Prerequisites
Make sure that a Role Type exists with which you can associate the new Role.
Steps
1. In the CRM Resource Manager responsibility, navigate to Setup > Roles.

The Roles window displays fields you can use to define a role.
2. Enter your values in the Code and Name fields. Choose a Role Type from the
list of values. For Incentive Compensation choose Sales Compensation.
3. Select the Active box to make the Role active. Select one or more of the job title
boxes–Manager, Member, Admin, Lead–to associate the Role to job titles.
4. Use one or more of the Job lines to describe jobs associated with the Role.
5. Select File > Save to complete the Role definition.
1.3.4 Oracle Payable

Oracle Payable recognizes salespeople that are outside the company for payment
only if they are activated as Suppliers through Oracle Purchasing. They are then
paid with invoices, not through the normal payroll system. Full-time, regular
employees are paid through Payroll. Please refer to Oracle Payroll documentation.
When a Payrun has been processed (Paid status against the Payrun name), the
Salespeople Sub-ledgers are updated to reflect the amounts paid in the appropriate
accounts and balances. When the payrun is paid, the payrun details are sent to the
Oracle Payable Invoices Interface table.
The following two tables show the columns that map to the invoice interface in
Oracle Payable:
AP_INVOICES_INTERFACE Populated with

INVOICE_ID AP_INVOICES_INTERFACE_S.NEXTVAL
INVOICE_NUM CNPD.COMMISSION_LINE_ID
INVOICE_DATE CN_PAYRUNS.PAY_DATE
VENDOR_ID FND_USER.SUPPLIER_ID
VENDOR_SITE_ID PO_VENDOR_SITES.VENDOR_SITE_ID
INVOICE_AMOUNT CN_POSTING_DETAILS_SUM.PAYMENT_
AMOUNT
INVOICE_CURRENCY_CODE FUNCTIONAL CURRENCY CODE
PAYMENT_CURRENCY_CODE REP CURRENCY CODE
SOURCE “OSC” (NEW quick code of type SOURCE)

What’s New
AP_INVOICE_LINES_INTERFACE Populated with

INVOICE_ID Same value as entered for AP_INVOICES_
INTERFACE
INVOICE_LINE_ID AP_INVOICE_LINES_INTERFACE_S.NEXTVAL
LINE_NUMBER CNPD.COMMISSION_LINE_ID
LINE_TYPE_LOOKUP_CODE ITEM/ TAX / MISCELLANEOUS
AMOUNT CNPD
The Liability Account will also be mapped to the Oracle Payable Interface. This will
be done using the account generator, accessible via the Ruleset Form or liability
account information entered at the plan element or revenue class level.
1.3.5 Oracle Partners Online

Oracle Partners Online permits access to some pages in Oracle Incentive
Compensation, much the same as Oracle Sales Online does, through the
Compensation tab. However, Oracle Partners Online does not allow access to a Year
to Date Summary or a Top Performers Bin, and there is no drilldown to the Year to
Date Summary in the Forecast Hierarchy. See Section 1.3.2, "Oracle Sales Online"
for more details on the specified functionality.
1.4 What’s New

The following new features have been added to Oracle Incentive Compensation in
this release.
1.4.1 Collecting Revenue Adjustment from Oracle Receivables

In this release of Oracle Incentive Compensation, the standard collections interface
with Oracle Receivables has been enhanced. Now, Revenue Management
adjustments made in Oracle Receivables are automatically collected into Oracle
Incentive Compensation without the need for manual adjustments. Oracle Incentive
Compensation and Oracle Receivables must be fully implemented and Oracle
Receivables must be the source of the transactions. There are no changes to the user
interface.
Previously, transaction adjustments made using Revenue Management in Oracle
Receivables were not reflected in Oracle Incentive Compensation. After a

What’s New
transaction line, such as an invoice, went through the two stages of collection,
Notification and Collection, subsequent collections would not identify or collect the
same transaction line if Revenue Management adjustments had been made. This
inability to collect Revenue Management adjustments into the application could
result in inaccurate compensation calculations unless manual adjustments were
performed in Oracle Incentive Compensation for each transaction on which
Revenue Management adjustments were made in Oracle Receivables.
Now, you can make transaction adjustments one time, in Oracle Receivables using
the Revenue Adjustment module (RAM), and eliminate the need to make
corresponding manual adjustments in Oracle Incentive Compensation. This saves
time and effort, and provides greater certainty of accuracy in compensation
calculation. See Chapter 8, section 8.5.3 for more details.
1.4.2 Accumulation and Splits in Multidimensional Rate Tables

Under some circumstances, commission must be derived from multiple aggregated
values. This can be accomplished by setting up interdependent plan elements,
however this approach is complicated and can be difficult to understand. It is
simpler to use a single plan element with a multidimensional rate table. However,
until now, you could not use cumulative values in multidimensional rate tables. In
this version of Oracle Incentive Compensation you now can use multiple
aggregated values in a formula that utilizes a multidimensional rate table.
In this version of Oracle Incentive Compensation, it is possible to split rate tiers in
multidimensional rate tables.
Now, when you assign expressions to a cumulative formula, you can specify for
each expression whether is is cumulative or not. If you want to split rate table tiers
when calculating commission, you can select one dimension upon which to perform
the split.
There is no limit as to how many expressions can be cumulative, however you can
specify only one dimension to be split in any formula that is used in a
multidimensional rate table. The dimension that is split creates a one-dimensional
rate table and the tiers of the other dimensions are selected and frozen.
1.4.3 Payment
The Payment functionality is significantly revised in this release of Oracle Incentive
Compensation. See Chapter 10 for details on the following features:
■ There is a new, more flexible payment administrative hierarchy for approval of
payment worksheets.

What’s New
■ Posting from the calculation tables to the posting tables is done automatically
before a payrun.
■ You can refresh a payment worksheet with most current commissions data.
■ You can freeze and unfreeze payruns to prevent adjustments.
■ You can lock and unlock payment worksheets.
■ You can create recoverable and nonrecoverable manual adjustments directly
from the payment worksheet before final payment, and can hold a transaction
or waive recovery before payment.
■ An Analyst Notes page, linked to the Worksheet Summary, enables you to add
or review notes connected with a payment worksheet.
■ A Payment Worksheet History page enables you to track the changes made to
payment worksheets and transactions.
1.4.4 Revenue Management Adjustments Automatically Collected

In this release of Oracle Incentive Compensation, the standard collections interface
with Oracle Receivables has been enhanced. Now, Revenue Management
adjustments made in Oracle Receivables are automatically collected into Oracle
Incentive Compensation without the need for manual adjustments. Oracle Incentive
Compensation and Oracle Receivables must be fully implemented and Oracle
Receivables must be the source of the transactions. On the Collect > Transaction
Source page, there is one more receivables event. Also, in the Collection Submission
> Submit Request page one more collection type can be submitted.
Previously, transaction adjustments made using Revenue Management in Oracle
Receivables were not reflected in Oracle Incentive Compensation. After a
transaction line, such as an invoice, went through the two stages of collection,
Notification and Collection, subsequent collections would not identify or collect the
same transaction line if Revenue Management adjustments had been made. This
inability to collect Revenue Management adjustments into the application could
result in inaccurate compensation calculations unless manual adjustments were
performed in Oracle Incentive Compensation for each transaction on which
Revenue Management adjustments were made in Oracle Receivables.
Now, you can make transaction adjustments one time, in Oracle Receivables using
Revenue Management, and eliminate the need to make corresponding manual
adjustments in Oracle Incentive Compensation. This saves time and effort, and
provides greater certainty of accuracy in compensation calculation.

What’s Obsolete
Oracle Incentive Compensation uses a new system profile, OSC: Negate during
Revenue Adjustment Collection, to allow users to decide whether to negate the
corresponding transactions that have been collected before and re-collect them from
Oracle Receivables with the new RAM adjustment. This new system profile has a
YES/NO value. The default for this system profile is Yes. Choosing YES ensures
data integrity with Oracle Receivables, but you lose any Oracle Incentive
Compensation adjustments. Choosing NO preserves adjustments made in Oracle
Incentive Compensation on collected adjustments, but may result in the loss of data
integrity with respect to Oracle Receivables. The system profile can be modified
only by users with Incentive Compensation Super User responsibility.
1.4.5 Import/Export Module Enhanced

The Import/Export module has been enhanced to give users the ability to upload
and download additional setups. The data is imported into the application using
the mapping you specify. You can download any failed records and modify them
before uploading them again. A process log is also maintained for the setups to
provide the status of the import/export process.
You can import data into Oracle Incentive Compensation for the following features:
■ Hierarchies
■ Classification Rulesets
■ Calculation Expressions
■ Revenue Classes
■ Transactions
You can export data from Oracle Incentive Compensation for the following features:
■ Hierarchies
■ Expressions
1.5 What’s Obsolete

Posting details are no longer a required step for payment. Posting is now performed
automatically.
.

2
Overview of Using Oracle Incentive
Compensation
This chapter provides an overview of the user interface and the major tasks you can
perform using Oracle Incentive Compensation. Sections in this chapter include:
■ Section 2.1, "Accessing Oracle Incentive Compensation"
■ Section 2.2, "Navigation"
■ Section 2.3, "How Oracle Incentive Compensation Relates to the E-Business
Suite"
■ Section 2.4, "Summary of Oracle Incentive Compensation Tasks"
2.1 Accessing Oracle Incentive Compensation

Starting with the 11.5.6 release of Oracle Incentive Compensation 11i, an HTML user
interface replaces the Forms user interface used in previous releases (see
Section 2.2.1, "HTML Navigation" ). This change improves integration of Oracle
Incentive Compensation with other Oracle products, and puts it in line with the
consistent look and feel of other HTML based Oracle CRM applications. Users
upgrading from pre-11.5.6 releases of Oracle Incentive Compensation will notice
that the HTML interface reduces the number of steps and drilldowns required to
perform some functions.
This change to HTML means that the Forms Navigator, icons, "View By" drop-down
lists, and hierarchies have been replaced by a row of nine tabs, using subtabs and
side panel menus to display finer levels of detail.
Listed below are the nine tabs in Oracle Incentive Compensation. Explanations of
each tab follow the list.
Overview of Using Oracle Incentive Compensation 2-1

Accessing Oracle Incentive Compensation
The Home Tab

The Incentive Tab
The Modeling Tab
The Resource Tab
The Quota Tab
The Transaction Tab
The Requests Tab
The Product Tab
The Administration Tab
2.1.1 The Home Tab

The Home tab is the starting point for using Oracle Incentive Compensation. The
text on it can be configured.
2.1.2 The Incentive Tab

The Incentive tab is where compensation plans are built, viewed, and activated.
There are seven subtabs. See Chapter 3, "Incentive Planning" for using the
Agreement and Activation subtabs, and see Chapter 6, "Building Compensation
Plans" for details on using the remaining five subtabs.
The first subtab, Agreement, is used in Incentive Planning. It opens to an
Agreements search page. Click the link in the Name column of search results to go
to the Sales Role Detail page, where you can define the agreement for the role.
The Activation subtab is where agreement definitions from Incentive Planning are
activated into the Commissions module of Oracle Incentive Compensation: Role
assignment, compensation plan assignment, plan element assignment, formula and
rate table assignment, and effective date assignment.
The Plan subtab is where you can assign plan elements and sales roles. Below the
subtab level you can view plan details, assign plan elements and sales roles, and
view the list of salespeople using the compensation plan.
The Element subtab is where you view and create plan elements. Drill down on a
plan element on the opening page to go to the Plan Element Details page, where
you can assign formulas and revenue classes.

The Formula subtab is where you create formulas from input expressions, output
expressions, and rate tables.
The Rate subtab is where you can create rate dimensions and rate tables, and define
commission rates.
The Expression subtab is where you create expressions to be used in formulas.
2.1.3 The Modeling Tab

The Modeling tab accesses a What-If commissions modeling features. A
compensation analyst can create different commission scenarios and compare the
commissions earned by each compensation plan. The most appropriate
compensation plan can then be activated for use with the commissions module.
The three subtabs in the Modeling tab are Agreement, Comparison, and
Performance. All three subtabs open to a search page and then display summary
pages that show various agreement versions.
The Agreement subtab is where the agreements are defined. Quota and on-target
earnings are also defined in the Agreement tab. Analysis of earnings payouts occurs
in the other two Modeling tab subtabs.
The Comparison tab displays in graphs and tabs the payouts earned in each version
of a plan.
The Performance tab shows Estimated Achievement and Estimated Payout fields
along with other plan version information. The analyst must input a revenue
amount to evaluate what the commissions will be.
Agreement versions are created in the Agreement subtab and can be activated to
final agreements from the Comparison subtab or Performance subtab. See
Chapter 4, "Modeling Agreements" for detailed information.
2.1.4 The Resource Tab

Use the Resource tab to manage information about resources. The Resource tab
contains four subtabs, including Planning, Resources, Role, and Group. See
Chapter 7, "Assigning Compensation Plans, Pay Groups, and Payment Plans" for
more information.
The Planning subtab is used by Incentive Planning and enables the assignment of
roles to resources for a specific group. It displays current assignments and allows
earnings to be customized as defined by the agreement to the role.

The Resources subtab displays all resource assignments such as roles, compensation
plan, plan elements, customized quotas and rates, pay groups, payment plans, and
compensation summaries.
The Group subtab enables a view of compensation groups to which a logged in user
is a member. It also displays details about those groups. Click a group name on the
Groups page, and then you can view details and a hierarchy by clicking links on a
side panel menu.
2.1.5 The Quota Tab

The Quota tab is where you use Incentive Planning to distribute quota from a sales
manager to directs and down to street level salespeople. The five subtabs are
Allocate, Approve, Distribute, Activate, and Report, which brings includes ten
Incentive Planning reports. See Chapter 3, "Incentive Planning" for a complete
explanation.
The Allocate subtab is where you allocate quota to resources. Sales projections can
be spread from top-to-bottom as the page displays managers and direct reports. The
manager’s ratio of his or her quota to the allocated quota of the reports is calculated
and displayed here.
The Approve subtab is where a quota, after it is allocated to a resource, becomes a
generated contract and is submitted to the contract approver for approval. The
approver receives notification that a contract has been submitted and must approve
or reject it.
The Distribute subtab enables you to distribute approved contracts by using the
Distribute column.
The Activate subtab updates the quota and rates agreed upon by the resources and
moves it into the commission module of Oracle Incentive Compensation.
The Report subtab gives access to the ten Incentive Planning reports.
2.1.6 The Transaction Tab

The Transaction tab contains eight subtabs: Collect, Import/Export, Adjust, Load,
Calculate, Notification Log, Payment, and Report.
Use the Collect subtab to view past collection submission records or to submit
collection. The View Request Status page allows you to view the collection type,
phase and status of the transactions collected, with a default of All in each. On the
Submit Request page you can indicate a start period and end period, and submit a

request for a new collection. On the Runtime Parameters page you can narrow the
collection process by entering values for previously defined runtime parameters.
The Import/Export module has been enhanced to give users the ability to upload
and download additional setups. You can import data into Oracle Incentive
Compensation for hierarchies, classification rulesets, calculation expressions, and
revenue classes. You can export data from Oracle Incentive Compensation for
hierarchies and expressions
Use the Adjust subtab to correct errors in transactions or adjust sales credit
assignment for transaction information in the CN_COMMISSION_HEADERS table.
You can create a new transaction or load a transaction from the first page of the
subtab.
Use the Load subtab to copy transactions from the Transaction Interface Table into
Oracle Incentive Compensation. This must be performed before calculation can take
place.
Use the Calculate subtab to run calculation processes. The opening page enables
you to select a batch name or create a new batch by clicking the Create button.
Use the Notification Log subtab to view the Notify Log. The Notify Log
automatically records every change in the system that affects calculation and lists
what part of the calculation must be rerun as a result of an event.
Use the Payment subtab to create or view information on a payrun. A payrun pays
members of a pay group for a particular pay period.
Use the Report subtab to refer to the eight Compensation reports.
2.1.7 The Requests Tab

The Requests tab is where you can make concurrent requests to perform collection,
calculation, and payment. There are four subtabs: Collection, Transaction,
Calculation, and Payment. These subtabs have redundancy with pages on the
Transaction tab, particularly in the Collection and Calculation areas.
Collection - Use to submit collections of clawbacks, invoices, orders, payments
givebacks, and custom transaction sources. Three subcategories include View
Request Status, Submit Request, and Runtime Parameter. See Chapter 8, "Collecting
and Adjusting Transactions" for detailed information.
Transaction - Use this subtab to identify all credit memos and payments that need to
be split. The two links on this page are View Request Status and Submit Request.

Calculation - Use the Calculation subtab to run calculation processes. The opening
page enables you to select a batch name or create a new batch by clicking the Create
button. See Chapter 9, "Calculating Compensation" for the complete process.
Payment - On this page you can delete a payrun, create a worksheet, or pay a
payrun. See Chapter 10, "Payment with Payruns" for details.
2.1.8 The Product Tab

The product tab is used to manage products and their price lists. In a connection to
Oracle Marketing Online, this tab is used to work with products or product
bundles. Use of the tab in Oracle Incentive Compensation is optional.
Functions include:
■ Searching, creating, or viewing details for a product or a product bundle in
inventory
■ Creating or viewing offers for a product or a product bundle
■ Specifying products for a product bundle
■ Modifying a product or product bundle
■ Displaying, creating, or modifying price lists
■ Other activities relating to marketing products and product bundles
The Product tab is accessed through Oracle Marketing Online. See the section,
"Implementing the Product Tab" in the Oracle Marketing Online documentation.
2.1.9 The Administration Tab

The Administration tab is the home of many of the setup functions of Oracle
Incentive Compensation. Administration tab functions mostly are those that are
provided when Oracle Incentive Compensation is implemented, but are
infrequently changed afterwards. See Chapter 12, "Administration" for details and
processes.
The Administration tab has multiple subtabs, including General, Marketing,
Partner, Sales, Incentive, and Collections, to enable administrative functions in
different Oracle products. The Incentive subtab is the one that applies to Oracle
Click the Incentive subtab to open a side panel menu with 22 selections. Their
primary functions are listed below:

Parameters - View and set System Parameters.

Tables - Define tables from Accounts Receivable, Order Management, or an external
source that are used in collecting and calculating transactions in Incentive
Compensation.
External Table - Map external tables to destination tables in Oracle Incentive
Compensation. Column mapping is performed here, too.
Accumulation Period - Change the status of accumulation periods.
Pay Periods - View essential information about pay periods that are set up for a
particular calendar.
Interval Types - View and define interval types.
Revenue Class - Create or remove revenue classes and assign expense codes and
liability codes.
Ruleset - Create and synchronize rulesets in the rules hierarchy.
Hierarchy - Display hierarchy types and create, remove, or edit them, and set the
effective date intervals.
Credit Type - Set credit types.
Credit Conversion - Set conversion rates between credit types.
Collection - Define and Maintain Collection setup. There are six subheadings within
this subtab, including Transaction Sources, Source Tables, Queries, Mapping,
Actions, and Generate.
Pay Group - View, create, or remove pay groups.
Payment Plan - View payment plan data, with check boxes to indicate if
compensation is recoverable or to be paid later.
Payroll - Map Oracle Incentive Compensation plan elements to Payroll Pay
Elements. Remove or deactivate elements, or map input values.
Component - Display or remove Quota Components by name, description, type,
unit/revenue, and computed flag.
Attainment - Add, delete, or edit existing attainment schedules by defining the
specific levels of quota achievement.
Job Titles - Assign a Sales Role to a Job Title.
User Access - Set the access privilege of users with finance manager responsibility
only.

Navigation
Settings - Set the Transaction Calendar and write Contract Text for a compensation
plan.
Seasonality - Set up a schedule to define the pattern of a product or service income
by period in the form of proportions expressed in percentages of the year’s total.
Rate Dimensions - View, edit, or create rate dimensions here that can be used when
building rate tables for formulas.
2.2 Navigation
This release of Oracle Incentive Compensation 11i uses two different technology
stacks: Java Server Pages (JSP) and Forms. Now, you can use an HTML based JSP
user interface for all Oracle Incentive Compensation functions. However, in this
release, you must use the Forms instance in some cases, for example, to access
Resource Manager, General Ledger, or AOL to set profile options or set lookups.
2.2.1 HTML Navigation

The HTML user interface uses five levels of navigation: global icons, tabs, subtabs,
and side panel menu (two levels). In general, HTML-based pages are easier to use
and require fewer drilldowns to complete a task than the Forms interface used in
earlier versions of Oracle Incentive Compensation.
When navigating in HTML, place your cursor over a tab or subtab, the arrow
changes to a pointing hand. Click the tab or subtab to go to the new page.
HTML pages provide links to other pages. Links are shown as underlined text. Use
a link the same way you use a tab or subtab:
1. Roll the cursor onto the link.
2. Click the left mouse button.
The new page appears.
Many tabs and subtabs open with a brief search page. Enter search data in a field or
use a list of values, click Apply, and a summary page appears. Continue to search
using the search button, or move to the next group of rows by clicking the
drop-down list and then selecting a range. In some cases, you can click the Next or
Last links to see the following or final group of listing, or click the First or Previous
links to view the first or previous listings. If there are hundreds of items listed, the
drop-down lists enable easier selection.

Summary of Oracle Incentive Compensation Tasks
HTML pages use a Quick Find search field, located at the top of the page just below
the subtabs. Each subtab has a Quick Find, with a drop-down list and an Advanced
Search link. Many pages provide a wildcard search and drop-down lists in the
parameters area near the top of the page. A Go button is provided to initiate
searches of lists of values. Many of the pages that display tables use Update,
Restore, and Create buttons at the beginning and end of the display:
Update - Used to saving newly entered data
Restore - Returns the display to the original content before the last save
Create - Opens a new page on which to create new data
2.3 How Oracle Incentive Compensation Relates to the E-Business

Suite
Oracle Incentive Compensation shares modules and exchanges information with
other applications in the Oracle e-Business Suite.
Oracle Receivables and Oracle Order Management provide sales transaction
information that forms the basis for calculating incentive compensation.
Oracle Resource Manager provides information about salespeople, whether they are
employees or non-employees, compensation group hierarchies, and roles. Part of
CRM Foundation modules. In this release of Oracle Incentive Compensation, Oracle
Order Management is a required patch.
Oracle Sales Online and Oracle Partners Online provide a mechanism to the sales
force to estimate their commission based on their current compensations plans. This
capability is in the Income Planner under the Compensation tab in Oracle Sales
Online.
Oracle Payables and Oracle Payroll are used to pay resources after compensation
has been calculated.
Oracle HRMS is connected to Oracle Incentive Compensation through Resource
Manager.
Compensation information can be made available to Oracle Sales Intelligence.
2.4 Summary of Oracle Incentive Compensation Tasks

Use Oracle Incentive Compensation to perform the following types of tasks:
■ Communicate with Resources While Planning Quota Distribution (Chapter 3)

Summary of Oracle Incentive Compensation Tasks
■ Distribute Quotas (Chapter 3)

■ Generate Contracts (Chapter 3)
See: Chapter 3, "Incentive Planning"
■ Model Agreements (4)
See: Chapter 4, "Modeling Agreements"
■ Build Compensation Plans (Chapter 6)
■ Create and Use Formulas (Chapter 6)
■ Create Rate Tables and Rate Dimensions for Formulas (Chapter 6)
■ Create Expressions for Formulas (Chapter 6)
See: Chapter 6, "Building Compensation Plans"
■ Assign Compensation Plans (Chapter 7)
See: Chapter 7, "Assigning Compensation Plans, Pay Groups, and Payment
Plans"
■ Collect Transactions (Chapter 8)
See: Chapter 8, "Collecting and Adjusting Transactions"
■ Calculate Compensation (Chapter 9)
See: Chapter 9, "Calculating Compensation"
■ Pay Commission (Chapter 10)
See: Chapter 10, "Payment with Payruns"
■ Generate Reports (Chapter 11)
See: Chapter 11, "Reports"
■ Perform Setups (Chapter 12)
See: Chapter 12, "Administration"

Part II
Incentive Planning

■ Chapter 3, "Incentive Planning"
■ Chapter 4, "Modeling Agreements"
3
Incentive Planning
Sections in this chapter include:

■ Section 3.1, "Overview of Incentive Planning"
■ Section 3.2, "Incentive Planning Enhancements in this Release"
■ Section 3.3, "Setups for Incentive Planning"
■ Section 3.4, "Creating the Agreement"
■ Section 3.5, "Allocating Quotas to Resources"
■ Section 3.6, "Allocation Details - Quota and Pay Assignment"
■ Section 3.7, "Approving Contracts"
■ Section 3.8, "Distributing Contracts"
■ Section 3.9, "Salespeople Accept Plans Using Oracle Sales Online"
■ Section 3.10, "Activating Compensation Plans"
3.1 Overview of Incentive Planning

Incentive Planning is a quota management, planning, and communication tool that
improves and enhances the incentive compensation process. When used with the
commission module, it provides:
■ Hierarchal Quota Distribution: Quota is allocated from each level of sales
manager to his or her direct reports, who then allocate it to their direct reports.
A Finance Manager can allocate quota to anyone in the sales hierarchy.
■ Self Service Approvals: Incentive Planning Contract Approvers receive email
notification that contracts need to be reviewed and approved. They approve the
contracts and the managers receive email notification that the contracts are
Incentive Planning 3-1

Overview of Incentive Planning
approved. The managers then electronically distribute the contracts to their

directs. Those resources receive an email notification from their manager that
their contracts are ready to accept. The resources then accept the plans by
responding to the email. The entire process is recorded.
■ Activation of Contracts: Approved and accepted contracts are pushed by the
Incentive Planning Analyst into the standard Oracle Incentive Compensation
commission processing system, where they become full fledged compensation
plans.
Oracle Incentive Compensation contains ten reports that help managers keep track
of contracts and resources. See Incentive Planning Reports in Section 11, "Reports"
for more details.
When you create a plan within Incentive Planning, the input and output
expressions that you build and associate with the formula are used to calculate the
estimated payouts that appear on generated contracts.
3.1.1 The Incentive Planning Process

The Incentive Planning module is useful but is optional. Incentive Planning is
dependent upon the Commissions building blocks such as rate dimensions, rate
tables, expressions, and formulas. Incentive Planning creates agreements, which are
the planning equivalent of compensation plans. After an agreement is activated, its
becomes a regular compensation plan.
To create compensation plans without using Incentive Planning. See Section 6,
"Building Compensation Plans".
These are the major steps in the Incentive Planning Process.
1. The Incentive Planning Analyst creates agreements, using components built in
the commission module of Oracle Incentive Compensation.
2. The Incentive Planning Manager or Finance Manager allocates quota. Managers
allocate quota to their directs, but the Finance Manager allocates quota to
anyone in the hierarchy to whom they have access. Resources submit estimates
to their managers using Oracle Sales Online.
3. The Incentive Planning Manager or Finance Manager locks the plan.
4. The Incentive Planning Manager or Finance Manager generates the contract for
resources.
5. The Incentive Planning Manager or Finance Manager submits the plan to the
Incentive Planning contract approver.

Incentive Planning Enhancements in this Release
6. The Incentive Planning Contract Approver receives notification that plans are
generated. Approver reviews and approves them.
7. Managers of resources receive email notification that the plans are approved.
The managers distribute them to their directs using Oracle Sales Online.
8. The resource receives email notification that contract is ready for acceptance.
The resource responds to the email to accept it. The resource can also print out
the contract at this time.
9. Incentive Compensation Analyst activates accepted contracts. The contracts
then become compensation plans, ready to be used to calculate and pay
commission.
3.2 Incentive Planning Enhancements in this Release

The following enhancements are part of this release:
3.2.1 Support for Non-Quota Based Components

In this release, the Incentive Planning Finance Manager or Incentive Planning
Analyst can assign a Variable Pay Non-Quota component to an agreement. Because
non-quota components do not have a target, the percent paid on transactions is the
same regardless of achievement. Non-quota components have rate tables, but they
use one rate for all transactions. Non-quota components do not have anchors,
because they are not needed.
A Variable Non-Quota component can be customized on the On Target Earnings
page for an individual resource that uses the role. For example, if the normal rate is
1%, you can change it to 2% for a resource. However, you must be sure to check the
customized check box.
3.2.2 Customization of Club Eligibility

In this release, when they are allocating quota, the Incentive Planning Finance
Manager or Incentive Planning Analyst can assign a club qualification value to a
resources’ plan based on predefined business rules. As in previous releases of
Oracle Incentive Compensation, you must check the Club Eligibility check box on
the Resource Detail page to make an agreement club eligible. You must also check
the Display Plan Text check box to automatically display the quota amount in the
Club Eligible area of the Plan Text page.

Setups for Incentive Planning
In this release, a new feature enables the Incentive Planning Finance Manager or
Incentive Planning Analyst to customize the default club amount for a resource that
is entered on the Plan Text page. This is done by entering a new number in the Total
Quota field in the Club Attainment area of the Allocation Details - Quota and Pay
Assignment page (Resource > Planning). The only components that are listed in this
area are components that have rate tables.
3.3 Setups for Incentive Planning

Before Incentive Planning can be performed, you must perform certain setups on
the Administration tab of Oracle Incentive Compensation. These steps put together
the responsibilities and building blocks needed to create and allocate agreements
during the Incentive Planning process. If these setups have already been performed,
please move on to section 3.4.
3.3.1 Associate Responsibilities with Responsibility Groups

Any responsibility that is created for use in Incentive Planning must be put in a
responsibility group. This can be done by setting the OSC: SFP Responsibility
Group profile for the responsibility. Permissible responsibility groups are listed
below, with their associated responsibility in OIC:
■ Incentive Planning Analyst is assigned Super User
■ Incentive Planning Finance Manager is assigned Finance Manager
■ Incentive Planning Contract Approver is assigned Contract Approver
■ Incentive Planning Sales Manager is assigned Sales Manager.
The data access privileges of a responsibility are determined by the responsibility
group it is put in.
Navigation
Forms Instance > Profile > System
Prerequisites
System Administrator responsibility is required.
Steps
1. Log in to the Forms instance.
2. Select the System Administrator responsibility.

The Navigator - System Administrator window opens.

3. Double-click Profile.
4. Under Profile, double-click System.
The Find System Profile Values window opens.
5. Check the Responsibility check box.
6. Enter Incentive in the Responsibility field. Click Find.
The Responsibilities window opens.
7. Select Incentive Planning Analyst. Click OK.
8. Quickly, in the Find System Profiles window, enter OSC%Resp% in the Profile
field. If you do not click in the Profile field quickly, the entire list of
responsibilities displays.
The System Profile Values window opens.
9. In the Responsibility column, in the row for OSC:SFP Responsibility Group,
select the access for the Super User responsibility from the list of values. Click
OK in the list of values window.
10. Repeat steps 7 through 9 for each of the three other responsibilities as shown
above.
11. Close the form.
3.3.2 Define Default Contract Text

Use the Default Contract Text page to define the text that accompanies the
Compensation Plan.
Navigation
Administration > Incentive > Settings
Prerequisites
Incentive Compensation Super User responsibility is required.
Steps
1. Click the Administration tab and click the Incentive subtab.
2. Click Settings in the side panel Menu.

The Settings page appears.

3. Select a Transaction calendar from the drop-down list. You can choose from Five
Day Week or a Six Day Week.
4. Enter the title of the contract in the Contract Title field.
5. Enter the Eligibility Rules in the Club Qualification text box.
6. Enter the Terms & Conditions of the Compensation Plan.
7. Enter the Approver’s details in the Approver section.
8. If necessary, click Restore to retrieve the last saved set of information.
Guidelines
The text in the Terms & Conditions text box can be made to refer to the location of
the Terms & Conditions. Example, “I accept the Terms & Conditions as set out in the
Company Handbook that is posted on the Notice Board or the Company Handbook
that was issued with the Employment Contract.” This text will appear at the bottom
of the Compensation Plan that will be generated later.
The Approver’s details will appear at the bottom of the Compensation Plan as well
3.3.3 Define User Access

This function can be accessed by users with Incentive Planning Analyst
responsibility.
Navigation
Administration > Incentive > User Access
Prerequisites
Users must be assigned Incentive Planning Financial Manager responsibility to
appear on the User Access screen.
Steps
1. On the Administration tab, click Incentive.
2. Click User Access on the side panel menu.
The User Access page opens.

3. Select a User by clicking on the name.

The User Access Details page opens.
4. On the User Access Details page, enter a compensation group in the
Compensation Group column, or click Go to select one from the pop-up menu.
5. In the Organization column, select an organization from the drop-down list.
6. Select an access level of Update or View from the drop-down list.
7. If necessary, click Restore to return to the most recently saved information
8. Click Update to save your changes.
3.3.4 Define Quota Components

Components are parts of an agreement that is created in Sales Force Planning. Fixed
pay components do not change from period to period, for example, Salary or Car
Allowance, which is the same for each pay period and is not based on a quota or
achievement. Variable pay components change depending on sales activity and are
associated with commission rather than salary or expenses. Variable pay
components can be based on a quota or be nonquota based.
Navigation
Administration > Incentive > Component
Prerequisites
None
Steps
2. In the side panel menu, click Component.
The Quota Components page appears.
3. Use the search parameters to find an existing component.
a. Enter one or more characters in the Name field to narrow your search. Or,
leave the percent sign (%) to display all components matching the other
parameters you select.
b. Select one of five types from the Type drop-down list.
c. Select Unit or Revenue from the Unit drop-down list.

d. Click Apply. The page refreshes and displays a list of all components that
match the search parameters.
4. To create a new component, enter a name in the first blank field in the Name
column. This field is required.
5. Optionally, enter a short description of the component.
6. Select a component type from the Type drop-down list. This is a required field.
7. Select Unit or Revenue from the Unit column drop-down list.
8. Check the Computed Flag check box if the value of the component is to be
derived from a formula.
9. Click Update to save your work. If necessary, click Restore to return to the
previously stored information.
10. If you want to delete a component, check the Remove check box and click
Update.
Guidelines
Component types are either fixed or variable. Variable component types are either
Quota Based or Non Quota Based, depending on whether there is a quota as part of
the compensation plan.
If the Quota for a Component is to be derived from using a formula, then check the
Compute Flag box.
3.3.5 Define Attainment Schedule

The Attainment Schedule is used in the Compensation Contract where earnings for
each level of achievement are displayed. To create an attainment schedule, perform
the following procedure.
Navigation
Administration > Incentive > Attainment
Prerequisites
Incentive Planning Analyst responsibility is required.
Steps
1. Click the Administration tab and the Incentive subtab.

2. Click Attainment in the side panel menu.

The Attainment Schedule Summary page appears.
3. Enter the name of the attainment schedule you want to create in the blank field
in the Attain Schedule Name column.
4. Click Update.
5. Click the new name from the Attainment Schedule Summary.
The Define Attainment Schedule page opens.
6. Enter the desired percentages in the blank fields.
If you need more than two fields, click Update and two more blank fields will
appear under the saved ones.
7. Repeat step 6 until your attainment schedule is complete.
8. Click Update to save.
Guidelines
To delete an attainment schedule, check the Remove check box and click Update.
You cannot delete an attainment schedule that is already assigned to a role. To
change the name of an attainment schedule, create a new schedule with the same
percentages, assign it to the role, and remove the old schedule.
3.3.6 Seasonality Schedules

Seasonality schedules show how a product/service income or cost/expense is
distributed throughout the year, expressed in percentages of the year’s total.
Seasonality schedules can be assigned to multiple agreements, and agreements can
use multiple seasonality schedules for different components. Because of the
variability from period to period, a new hire’s quotas and pay are affected. If
seasonality schedules are not assigned, an even distribution is assumed by default,
where each period’s quota is the same amount for the entire year.
Seasonality schedules can only be assigned to variable non computed components,
such as salary or monthly car allowance.
Seasonality schedules make it possible to weight a quota. For example, if a resource
works for only the last six months of the fiscal year, with the default seasonality of
even monthly quota, the amounts for the variable non computed elements in their
compensation plan would be exactly half the annual total for the sales role. If,
however, seasonality weighted the last two months of the fiscal year with a larger

quota, the annual amount of variable non computed compensation would be more
than 50 percent of a full year’s total.
To create new seasonality schedules, go to Administration > Incentive > Seasonality.
3.3.7 Define Jobs

Job titles are used by Human Resources to categorize employees. Oracle Incentive
Compensation uses roles, and a job title can be assigned to a particular role by using
the Job Titles page.
Perform the following procedure to assign roles in Oracle Incentive Compensation
to Job Titles.
Navigation
Administration > Incentive > Job Titles
Prerequisites
Incentive Planning Analyst responsibility is required. Resources must be set up in
Oracle Resource Manager.
Steps
2. Click Job Titles in the side panel menu.
The Job Titles page appears.
3. Use the search parameters at the top of the page to search for a job title by name
or by job code. Click Go to display the search results.
4. Click the link in the Job Titles column to go to the Resource Details - Job Titles
page.
This page displays any roles that are already assigned to the job title.
5. To add a role, enter it in the Role column. You can click Go to open a pop-up
window listing roles from which to select.
6. Enter a start date and end date. Click the calendar icon to open a pop-up
calendar. A start date is mandatory; the end date is optional.
7. Click Update to save your work. If you are editing a role assignment, you can
click Restore to return to the previously saved version.

Creating the Agreement
Guidelines
If using Oracle Human Resources Management System, the job title information
here is read from HRMS via Oracle Resource Manager. If you are not using HRMS,
please refer to Oracle Resource Manager for more information.
3.4 Creating the Agreement

Use the following sections to create agreements. In section 3.5, you use the
agreements to allocate quota to resources.
3.4.1 Defining a Sales Role

The first step in creating agreements for resources is to define a sales role. The sales
role of type Sales Compensation is created in Oracle Resource Manager using
Forms. A role describes a set of salespeople who share a common compensation
structure, for example, Salesperson, Consultant, or Regional Sales Manager. After a
role is created, you define it in Incentive Planning.
Use the following procedure to define the details of a sales role.
Navigation
Incentive > Agreements
Prerequisites
Sales Roles must already be created in Oracle Resource Manager. Rate tables,
components, and attainment schedules must be created in Oracle Incentive
Compensation.
Steps
1. Click the Incentive tab.
The Agreements page appears. It is the first page of the Agreement subtab.
2. Select a sales role name. Use the search parameter at the top of the page to
search if needed. Enter all or part of the sales role name before the percent sign
and click Apply to use the search parameter. Click the sales role to go to the
Sales Role Detail page.
3. If desired, copy the fields from an existing role by selecting a role from the
drop-down list. Click Apply.

4. In the On Target Earning field, enter Total Earnings if the Salesperson assigned
this role achieves 100% of quota.
5. Check the Club Eligible check box if this role is entitled to Club participation on
achieving Club rules.
6. Use the Rounding Factor field if you want to round the assigned quota. For
example, input 1000 if assigned quota is to be rounded up to the nearest 1000.
7. In the Quota Minimum and Quota Maximum fields, enter the range of quota
figures that this role should have.
8. Input the Compensation Plan Level to indicate the position of the role in the
sales hierarchy. For example, a street level salesperson will be assigned to Level
1.
9. Select an Attainment Schedule from the drop-down list that is applicable to the
compensation plan for this role.
10. Select Fixed Pay Components and then enter numbers against each component
to indicate the sequence that it is to appear in the Assign Quota and My Quota
Estimate windows. Enter the fixed pay amount for each fixed component. (For
example: if the fixed salary of a salesperson is 50,000, then enter 50,000 against
the fixed salary component).
11. Select Variable Pay, Non Computed Components as in step 10:
a. Enter the name of the component. Click Go to open a pop-up list.

b. Enter the sequential order of display in the Sequence column.
c. In the % of Total Quota column, enter the percentage of the quota that you
want this component to represent in the compensation plan. This must be
entered for the Distribute Quota function to work.
d. Enter the amount of commission at 100% of attainment.
e. Select a seasonality schedule. Click Go to open a pop-up list from which to
make your selection. The default seasonality schedule is even.
f. Select a calculation formula by clicking Go and selecting it from the pop-up
list.
g. Select a rate table from the drop-down list.
h. Select a rate calculation method:
■ Anchors - These must be defined separately. If Anchors is selected, the
Define link appears in the Anchors column.

■ Manual - Uses the predefined rate table.

■ Single Tier - All transactions are compensated at the same rate.
12. Select Variable Pay Computed Components and enter the sequential order of
display. The selections are the same as the Non Computed Components in step
9, except that seasonality is not used but formulas are.
13. Select Variable Pay Non Quota Components. Click Go to open a pop-up list.
Then, perform the following:
a. Enter the sequential order of display.
b. Enter the calculation formula. Click Go to open a pop-up list from which to
make your selection.
c. Select a rate table from the drop-down list. The rate table must have only
one tier.
14. The sections for variable components in steps 9, 10, and 11 also contain fields
for selecting a Calculation Formula and Rate Table. Enter information into these
fields to enable calculation for these variable components.
a. Components with quotas additionally include an anchor column and a
Disable Anchors check box.
b. Click Define in the Anchors column to go to the Agreement Details page.
c. Use anchors to indicate the maximum that can be earned at each tier of the
rate table you selected.
15. Enter the name of the compensation plan in the Map to Compensation Plan
field if you want the element to appear in that compensation plan after the
activation process has been run.
Guidelines
Entering the Quota range enables the Quota Range Report to be run. The minimum
quota on the Sales Role Details window will be picked up on the Minimum Quota
field on the Quota Modeling window when the minimum function is invoked by
the user.
Compensation Plan Levels are used in the Quota Model Summary and Average
Quota Summary Reports where the quota for each Component are totaled for each
level of Salespeople in the Salespeople Hierarchy for the selected parameters
(example, Organization, Effective Date) of each Report.

The Attainment Schedule will be used in the Compensation Contract where

earnings for each level of achievement are displayed.
Oracle Incentive Compensation automatically accounts for seasonality when it
calculates prorated annual quotas.
3.4.2 Using Quota Estimates from Resources

The My Quota Estimate page allows salespeople, through Oracle Sales Online, to
communicate to management what they think their new quota should be for the
next compensation plan cycle. The manager and the manager’s manager can view
the quota estimate by logging on to Oracle Sales Online, and then take it into
consideration when allocating the final quota.
Navigation
Oracle Sales Online - Compensation > My Compensation Plans > My Quota
Estimate
Prerequisites
Resource access to Oracle Sales Online.
Steps
1. Click the Compensation tab.
2. Enter a quota estimate against each quota component and under the Quota
from Field column.
3. To erase an estimate, click Restore and the application will retrieve the last
saved estimate.
Click Update to save.
3.4.3 Completing the Agreement

Use the Agreement Details page to complete the definition of the rate table and
quota anchor details for a sales role.
Navigation
Incentive > Agreement > Sales Role Detail

Prerequisites
Rate tables must be created. Rate tables must also be assigned to the component to
which you want to apply anchor values.
Steps
1. On the Sales Role Detail page, in the Variable Pay, Computed Components area,
click Define in the Anchors column.
The Agreement Details page appears.
1. Select a calculation method, Line or Step, from the Anchor Rate Calculation
Method drop-down list (See Guidelines).
2. In the Rate Range area, enter the Minimum Rate and Maximum Rate for each
tier of the Rate Table (optional).
3. In the Multi-Tier Rate Table Anchors area, enter the Percent of Attainment in the
first column. This is displayed based on the rate dimension definition. You can
change only the first and last values in this column (See Guidelines).
4. In the drop-down list of the Anchor Type column, select the method of
commission calculation to be used. Choose Amount if you are entering the
commission earnings amount for each attainment/achievement level. If the
percentage of quota is to be used, select Percent in the Anchor Type column and
enter the percentage of quota for each attainment level. See Guidelines for more
explanation.
5. Click Update to save new information.
6. If necessary, click Restore to retrieve the last saved set of information.
Guidelines
There are two methods of Anchor Rate calculation, Line and Step. These
methods are used to fill in the Commission rates for the rate tables created in
the Administration part of Oracle Incentive Compensation.
Step calculation simply uses the amounts in the anchor (expected commission
column), with no calculation. When attainment reaches the percent in the tier,
the commission amount shown in the tier is paid. The Line method calculates
commission on a sliding scale, with commission depending on the exact rate in
each separate tier of the rate table, calculated on a sliding scale.
Here is an example of how Line and Step calculation works:

Step 1. Create a rate dimension in the administration part of Oracle Incentive

Compensation:
0 - 25%
25% - 50%
50% - 75%
75% - 100%
100% - 999%
Step 2. Assign the rate dimension to a rate table. Here the dimension type is
percent and the rate type is amount:
Expected
From To Commission
0 25% To be calculated
25% 50% To be calculated
Step 3. Assign this rate table to a component in Incentive Planning and define
the anchors as follows:
Expected
% of Attainment Type Commission
0% Amount 0
25% Amount 100,000
50% Amount 150,000
75% Amount 180,000
100% Amount 200,000
999% Amount 200,000
Step 4. If the anchor method calculation is Step calculation, the commission

rates for the rate table are:

From To Commission Rate

0 25% 0
25% 50% 100,000
50% 75% 150,000
75% 100% 180,000
100% 999% 200,000
Step 5. If the anchor calculation method is Line calculation, commission rates

for the rate table will be calculated as follows (TQ = 20,000 total quota):
1st Tier (0 - 25%)
100,000 - 0/(25% - 0%) TQ
100,000/25% * 20,000 = 20
2nd Tier (25% - 50%)
(150,000 - 100,000)/50% - 25%) TQ
50,000/25%*TQ = 10
3rd Tier (50% - 75%)
(180,000 - 150,000)/(75% - 50%) TQ
30,000/25% *TQ = 6
4th Tier (75% - 100%)
(200,000 - 180,000)/(100% - 75%) TQ
20,000/25% *TQ = 4
5th Tier (100% - 999%)
(200,000 - 200,000)/(999% - 100%) TQ = 0
Note: Real data will be set up so that the commission rates increase from tier to
tier.
Step calculation can be used only for rate type of amount.
Anchors are used only to calculate the commission rates for the rate table. After
activation from Incentive Planning to Administration, these rates can be seen in
Resource > Resources, which are customized rates for the specific salesperson.

If the step calculation method is used in Incentive Planning, the rate table in
step 4 will be used to calculation commission. If the line calculation method is
used, then the rate table in step 5 will be used to calculation commission.
In step 3 above, if the rate dimension for a rate table is defined as:
0 - 25%
20 - 50%
50 - 100%
then when this rate table is assigned to a compensation plan in Incentive
Planning, the multi-tier rate table percent of attainment column is displayed as:
0%
25%
50%
100%
You can change only the 0% and 100% values.
Note: If, during setup, you use a currency that is different from the operating unit’s
functional currency (for example, for setting On Target Earnings, a quota, and so
on), then you should use a rounding factor of 0.01 or lower (0.001, 0.0001) to disable
the effects of rounding.
3.4.4 Computed Component Formulas

Use this page to define a formula for a computed formula.
Navigation
Prerequisites
Components must be created.
Steps
1. Select a component from the list of values.
2. Enter the percentage against this selected component. Repeat steps 1 and 2 until
all variables of the formula have been defined.

3. Click Restore to retrieve the last saved set of information.

4. Click Save to save new information.
Guidelines
The percentages entered against each component selected will be multiplied with
the value of each component. The results of all multiplication will be added
together.
Here is an example of a computed component formula:
A resource sells 2 types of products: computers and accessories; the compensation
plans will be based on the quota for computers and accessories. Computers is
broken up into desktops and laptops and accessories into printers and monitors. To
accurately define the computers and accessories quota, variable pay non computed
components are made for desktops, laptops, printers, and monitors. A Computers
and an Accessories variable pay computed component are created; the computed
component formulas defined for each are as follows:
Computers = 100% x Desktop + 100% x Laptop
Accessories = 100% x Printers + 100% x Monitors
If you want to the Total Quota to reflect the totals of individual quota components,
then you will define to configure the Total Quota Component formula
Total Quota is used to add up quota that has been allocated to plans at every level
of the sales force planning hierarchy.
Example: Company projects $11 billion in sales for upcoming fiscal year. Sales reps
are assigned $350k and $250K in desktops and laptop computers, respectively. The
$600K allocated to each sales rep needs to roll back up to the $11 billion that the
company projected. This is done by defining the Computed Component Formula
for the Total Quota to be ‘Desktops + Laptops.’ The Total Quota formula would be =
100% x Computers + 100% x Accessories
3.4.5 Customizing On Target Earnings and Anchors for Individual Resources

On Target Earnings and Anchors are part of the definition of a role, but they can
also be customized for individual salespeople. On the Resource Details - On Target
Earnings page, you can view fixed and variable compensation plan elements for a
resource, based on their compensation plan.

Navigation
Resource > Planning > Resource Details - Main
Prerequisites
The sales role must already be created in Resource Manager. The sales role details
must already be created in the Agreement subtab of the Incentive tab. Rate tables
must be created. Rate tables must also be assigned to the component to which you
want to apply anchor values.
Steps
1. Click the Resource tab and click the Planning subtab.
2. Use the Resource Search page to search for a resource.
The Resource Search Results page appears.
3. Click the name of the resource you need.
The Resource Details - Main page appears.
4. Click the amount in the On Target Earnings column.
The Resource Details - On Target Earnings page appears.
5. Enter revised amounts in the fields for the Fixed and Variable Amount fields.
6. To customize anchors, click Anchor in the Details column in the Variable, Quota
Based area.
The Resource Details - Customized Anchors page appears.
7. In the Rate Schedule Detail section, enter the commission rate range for each
tier of the Rate Table.
8. In the Quota Anchors Detail section, select Amount if entering the commission
earnings amount for each attainment/achievement level. For Percentages, select
percentage and enter the percentage for each attainment level (percentage of
quota). See Guidelines for more explanation.
9. To view rate tables for variable non-quota elements, click the Rate link in the
Details column of the Variable, Non-Quota area.
10. If you are editing previously created information, you can click Restore to
retrieve the last saved set of information.

Allocating Quotas to Resources
Guidelines
In the example below, at 0% achievement of quota, the variable pay is zero. At
25% of quota, the additional variable pay is 5,000. At 50% of quota achievement,
the additional variable pay is increased to a maximum of 12,000. This means
that the earnings in the 25-50% tier of the rate table are compensated at a higher
percentage than the 0-25% tier. At the 100% level of quota achievement, the
additional variable pay is 20,000. Any achievements over 200% of quota are
capped by entering the same value as the previous tier (no additional variable
pay) against the highest rate tier.
0 Amount 0.00
25 Amount 5,000
50 Amount 12,000
100 Amount 20,000
200 Amount 50,000
9999 Amount 50,000
3.5 Allocating Quotas to Resources

After the agreements are complete, the manager uses them to allocate quota to his
or her directs in a compensation group. A Compensation Group is a number of
salespeople who share the same rollup relationship. Quotas also can be allocated by
the Incentive Planning Analyst or Incentive Planning Finance Manager.
The Quota Allocation Details page is where you perform the actual allocation of
quota to your Directs. There is reference information to help you perform the quota
allocation, such as:
■ Your directs’ role(s) in your compensation group as well as effective start and
end dates
■ Your directs’ participation period in your Compensation Group (hierarchy start
and end dates)
■ Your directs’ estimate of their own quota, entered by the directs (Quota from
Field column)
■ The status of Compensation Plans. See Guidelines below regarding the
approval process.

Allocating Quotas to Resources
Navigate down the hierarchy of Compensation Groups to view your directs’

allocation of quota to their own directs (hierarchy column), if applicable.
There are several options for allocating quotas. You may distribute your quota
evenly to each of your directs by selecting Even (Distribute Quota field) and
clicking Distribute. Alternatively, you can allocate the minimum quota by Sales
Role by selecting Minimum. You can also allocate to each of your directs a quota
amount equal to your own quota by selecting Equal.
Navigation
Quota > Allocate
Prerequisites
Resource must be defined in Resource Manager. Incentive Planning Finance
Manager responsibility is required.
Steps
1. Click the Quota tab.
The My Compensation Groups page appears.
2. Enter a group name in the Group Name field. Or, use a wildcard with the
percent sign (%) after it.
If you leave the single percent sign (%) in the field, all compensation groups
display when you click Submit.
3. Enter an effective date. Today’s date is the default setting.
4. Click Submit. The My Compensation Groups page appears. Alternatively, click
Clear to change your entries.
5. Click the Compensation Group for which you wish to view details.
The Quota Allocation Details page appears.
6. Do an initial distribution of quota by using the fields at the bottom right of the
page. To enter quota figures individually for each of your directs, click the
hyperlink under the Planning Quota column.
7. To produce a compensation plan that you can view after you have updated the
quota that you have allocated to your directs, click Generate.
8. To create a vacancy or position to be filled by a new salesperson, Click Create
Vacancy.

Allocation Details - Quota and Pay Assignment
The Add To-be-Hired page appears.

d. Select a compensation group from the drop-down list.
e. Enter a start date and an end date. The dates must be in the future or an
error message is generated (see Guidelines).
9. The quota must be locked before it is allocated.
10. After the agreement is the way you want it, click Generate to generate a
contract. The Generate button becomes a Submit button.
11. Click Submit to submit it to the Incentive Planning Contract Approver. The
Contract Approver can then view and approve the draft Contract with the
locked quota.
Guidelines
The draft Contract is made up of the agreement with Terms and Conditions added
at the end.
In step 6, Distribute Quota will work only if the % of Total Quota is given for the
components in the Sales Role Detail page for the resource.
In step 8b, the dates that the enter to add a To-Be-Hired must be in the future. For
example, on June 1, 2002, you cannot use a start dates of January 1, 2002 and an end
date of May 31, 2002.
In the Overassignment fields at the lower right:
■ Direct Level Overassignment is the total quota of your directs expressed as a
percentage of your own quota.
■ Street Level Overassignment is the total quota of the salespeople at the lowest
level of the hierarchy (subordinate to your Compensation Group) expressed as
a percentage of your own quota.
Once the draft Contract is approved, you can distribute the Contract to your directs.
Your directs will then have the opportunity to view their new Contracts and either
accept or print it. The approval status of the Contract can always be seen under the
column called Plan Status. Click the link in the Plan Status column to view the
Compensation Plan History page.
3.6 Allocation Details - Quota and Pay Assignment

The Allocation Details - Quota and Pay Assignment page provides information to a
manager to view, adjust, and assign a quota to a salesperson based on prorated

Allocation Details - Quota and Pay Assignment
information. Quota components as well as variable pay components are displayed.

The application automatically prorates the computed amounts based on the
seasonality schedule and workday calendar, which are defined on the
Administration tab. You can override the system generated prorated amounts.
Only variable pay, non-computed components can use unique seasonality
schedules. Every other kind of component defaults to even seasonality and the
standard workday calendar.
You can see any quota entered by the salesperson by using the Planning subtab on
the Compensation tab in Oracle Sales Online, and any direct or street
overassignments that might affect the salesperson’s quota.
The screen is divided into two sections, Quota and Variable Pay. The quota
components in the upper table can be changed and prorated, while for the variable
pay components below, you can only change the final prorated amount.
All of this information enables a manager to assign a final prorated quota to the
salesperson.
Navigation
Resource > Planning > Allocation Details - Quota and Pay Assignment
Prerequisites
The resource must already be created in resource manager and assigned a quota.
Steps
1. The top section of the Allocation Details - Quota and Pay Assignment page
displays read-only information about the resource. Check the Overlay check
box to exclude the resource’s quota from over assignment percentage
calculations.
2. Check the Customize Quota and Pay check box to indicate that the final
prorated quota and pay have been customized for the resource (see Guidelines).
3. The names of the quota components and variable pay components are listed in
the first column of the upper and lower tables of the page. You can adjust the
annual quota in the Annual Quota field next to any listed component.
If you make any adjustments to the annual quota, click Prorate to display the
revised prorated quota in the Computed Prorated Quota field.

Approving Contracts
4. The data in the Quota from Field field was submitted by the resource by using
the Compensation tab in Oracle Sales Online. Use the data to evaluate and
determine the final prorated quota.
5. The Final Prorated Quota area contains three columns, Amount, Direct
Overassign and Street Overassign. In the Amount field, set the final prorated
quota for the resource based on the information displayed in the previous
columns. The two overassignment columns automatically display any
overassignments that have been assigned to the resource.
6. In the Variable Pay area, the already allocated annual amount is listed, with an
automatically computed prorated amount. You can adjust the final prorated
amount, changing it from the automatically generated prorated amount to
another amount that you choose.
7. Click Update to save any revised amounts on the page.
8. Click Lock to freeze the agreement before submitting it to the Contract
Approver.
Guidelines
If you check the Customized Quota and Pay check box, the amount that you
entered in the Final Prorated Quota field for the resource is stored, and is not
prorated automatically if the annual quota is changed at a later time. For example, if
you assign an annual quota of $1,000,000 to a plan that lasts for six months, the
prorated amount is $500,000. If you then assign a final prorated quota of $550,000 to
a resource and check the Customized Quota and Pay check box, the $550,000
remains, even if you change the annual quota for the plan to $1,500,000 afterwards.
If you did not check the check box, the final prorated quota would change to
$750,000 when you changed the annual quota.
3.7 Approving Contracts

The Incentive Planning Contract Approver uses the Contract Approval page to
view details of any plans to be approved. The report identifies the resource by
Name, Job Title, Employee #, Organization, and Sales Role. The Start Date and End
Date columns show effective dates of the contract. On Target Earnings columns are
shown as a total and broken down into fixed and variable pay. The Assigned Quota
and Club Eligible columns are displayed for reference, and if the employee is an
overlay it is noted. The Name, Sales Role, and Plan Status columns can be clicked to
open other pages.

Approving Contracts
Navigation
Quota > Approve
Prerequisite
There must be a plan to be approved, and the plan must be locked. Incentive
Planning Contract Approver responsibility is required.
Steps
1. Click the Quota tab and click the Approve subtab.
The Resource Search page appears.
2. Enter one or more search parameters and click Apply.
3. Click a name in the Resource Name column.
The Contract Approval page appears.
4. In the Action column, select No Action, Approve, or Reject from the drop-down
list.
5. Click Update to make changes permanent.
6. Click Approve All to approve listed contracts.
7. If necessary, click Restore to return to the previously saved version.
3.7.1 Viewing the Contract

To see the contract, click the link in the Sales Role column of the Quota Allocation
Details, Contract Approval, Distribute Contract, or Compensation Plan Activate
pages of the Quota tab.
This page displays a completed contract. All quotas, plan elements, and attainment
levels are displayed, along with approval and acceptance information, if the plan
has already been approved and accepted.
If a contract has only a single non-quota-based element, the quota box at the top of
the page displays only the single flat rate of the plan.
Attainment levels are displayed for quota-based plans. If the plan has only
non-quota-based elements, attainment levels are not shown.
The compensation plan page is a view-only document, so no changes can be made
to it.

Distributing Contracts
3.7.2 Compensation Plan History

The Plan Status column of the Contract Approval page shows the current status of
the plan. To view a history of all of the actions taken on a contract, click the link in
the Plan Status column. The Compensation Plan History page appears.
This page is a log of records changes in the status of a salesperson’s compensation
plan. The changes are date-stamped, and the identity of the person or role who
performed the action that changed the status is noted.
If the plan has been accepted, it become a link. Click the link to go to a page
displaying the complete compensation plan. This page shows the total quotas, and
the possible earnings for each plan element at each percentage of attainment. The
approval and acceptance information is displayed at the bottom.
3.8 Distributing Contracts

Managers receive notification that the contracts are approved by the Incentive
Planning Contract Approver. They can then use the Distribute Contract page to
distribute any plan that has been approved. Click the Name, Sales Role, and Plan
Status columns to open other pages.
Prerequisite
There must be an approved plan to distribute.
Steps
1. Click Name to view the Quota Allocation Details page or
2. Click Sales Role to view the complete contract, or
3. Click Plan Status to open the Compensation Plan History.
4. Check the check box in the Distribute column next to the plans that you want to
distribute.
5. Click Distribute.
After a plan is distributed, the listing disappears from the Distribute Contract
page.
6. Optionally, click Distribute All to distribute all contracts
7. Optionally, click Restore to return to the previously saved version.

Salespeople Accept Plans Using Oracle Sales Online
3.9 Salespeople Accept Plans Using Oracle Sales Online

Salespeople can log on to Oracle Sales Online and accept their Compensation Plans.
To do this, perform the following procedure:
Navigation
Log in to Oracle Sales Online > Compensation > Compensation Plan
Steps
1. Log onto Oracle Sales Online.
2. Click the Compensation tab and click the Compensation Plan subtab.
3. Click the plan to be accepted.
4. Click the Accept button on the plan (contract).
3.10 Activating Compensation Plans

The Incentive Compensation Analyst uses the Compensation Plan Activate page to
activate plans that have been approved, distributed, and accepted. Click the link in
the Name column to go to the Quota Modeling Summary. Click the link in the Sales
Role column to go to view the compensation plan details. Click the link in the Plan
Status column to go to the Compensation Plan History page.
Navigation
Quota > Activate
Prerequisite
Incentive Planning Analyst responsibility is required. There must be an approved
plan to activate.
Steps
1. Check the check box in the Activate column next to plans you want to activate.
2. Click Activate.
After a plan is activated, the listing disappears from the Compensation Plan
Activate page.
3. Optionally, click Activate All to activate all contracts.
4. Optionally, click Restore to return to the previously saved version.

Activating Compensation Plans
3.10.1 Regoaling
Regoaling is a new functionality that enables managers to change the quota or
variable pay of a salesperson’s compensation plan at any time. These changes could
be required because of:
■ A change in business circumstances
■ A salesperson is receiving too much commission
■ A salesperson is receiving too little commission
■ A salesperson receives a promotion to a new role with a new goal
Regoaling can only be used if a plan is already accepted and activated.
Regoaling uses new seasonality and workday calendar features to calculate the
exact amount to be paid. Seasonality allows planners to assign different quotas to
each month to accommodate business cycles, and the workday calendar lets
planners count each workday of each month, accounting for holidays and
weekends. Seasonality can only be used on noncalculated plan elements, such as
Licenses and salary.
For example, a salesperson’s compensation plan has effective dates of January 1 to
December 31. The salesperson can receive a new compensation plan on the 24th of
July and the exact amount of compensation can be calculated for the rest of the year,
based on the quotas assigned to August through December and on the exact
number of work days remaining in July.
Prerequisites
Log in as an Incentive Compensation Super User or Sales Manager responsibility.
Workday calendar profile must be set up in Forms. The transaction calendar must
be set up in General Ledger and selected from the drop-down list in Administration
> Incentive > Settings. Seasonality must be set up in Administration > Incentive >
Seasonality.
Steps
1. Click the Incentive Tab and click the Agreement subtab.
2. Use the search parameter to list roles.
3. Click a role.
The Sales Role Detail page appears.
4. Select seasonality in the Variable Pay, Non Computed Components area.

5. Use workday calendar with fixed pay elements.

6. Select Rate calculation method:
■ Anchors - These must be defined separately
■ Manual - Use the predefined rate table
■ Single Tier - all transactions are compensated at the same rate
7. Click Submit to enter any changes.
8. Click the Resource tab. The Resource Search page on the Planning subtab
appears automatically.
9. Use parameters to search for the resource.
10. Click the Resource name on the Resource Search Results page.
11. Click the Adjust Quota button.
12. Click Update.

The Resource Details - Quota Adjustment page appears.
13. Click the button next to an existing role to adjust it, or click the button next to
the blank row to enter information for a new role.
If you are regoaling an existing role, enter start and end dates for the new
quota. Be sure to set the end date an old quota the day before the start of a new
one.
14. Click the link to Quota Allocation Details.
The Allocation Details - Quota and Pay Assignment page appears.
15. Click Prorate.
16. Adjust any prorated amount that you want to manually. This is good for
rounding amounts to even numbers.
When you change the amounts manually, it changes the proration factor, which
changes the On Target Earnings (OTE) as well.
17. After you have made any changes you want to make, click Update to save
them.
18. Click Lock.
19. Click Generate.

The Generate button then becomes the Submit button.

20. Click Submit to submit the plan to the Contract Approver.
21. Click the Single Tier Rate link to go to the Allocation Details - Rate page.
22. Check the Standard Rate button if you want to calculate based on the computed
figures. Click the Effective Rate button if you want to base calculations on
previous achievements.
23. Click Generate Effective Rate.
After the plan is submitted to the Contract Approver, it needs to be approved by
someone with the responsibility of Contract Approver or Incentive Compensation
Super User. This is the procedure:
Steps
2. Enter search parameters and click Go.
3. Click the salesperson name link to go to the Contract Approval Page.
4. Select Approve in the drop-down list in the Action column next to contracts you
want to approve. You can also click Approve All to approve all of the submitted
contracts at once.
A manager can distribute a plan by using My Salespeople in Oracle Sales Online.
After the compensation plan has been distributed, the resource must log into Oracle
Sales Online to accept the plan, using the following procedure:
Steps
The plan status is Issued.
2. Click the Rate link to go to the Contract page.
3. Review the contract and click Accept to accept the contract.
The plan status changes to Accepted.

4. Click the Printable button to print out a hard copy.

To Activate the sales role, perform the following procedure:
Prerequisites
Log in as Incentive Compensation Super User responsibility. The compensation
plan must already be accepted by the resource.
Steps
1. Click the Incentive tab and click the Activation subtab.
The Role Activation page appears.
2. Check the Activate check box.
3. Click Update.
4. To activate all plans, click Activate All.
To activate the salesperson, perform the following procedure:
1. Click the Quota tab and click the Activate subtab.
2. Enter parameters in the Salespeople Search page to find the salesperson you
need. The Salespeople Found page appears.
3. Click the name in the Salespeople Name column.
The Compensation Plan Activate page appears.
4. Click the check box in the Activate column.
5. Click Activate.

4
Modeling Agreements

■ Section 4.1, "Overview of Modeling Agreements"
■ Section 4.2, "Modeling Enhancements"
■ Section 4.3, "Creating an Agreement Version"
■ Section 4.4, "Assigning Details to an Agreement Version"
■ Section 4.5, "Allocating Quotas to Quota Based Components"
■ Section 4.6, "Comparing Agreement Version Contracts"
■ Section 4.7, "What-If Scenarios"
4.1 Overview of Modeling Agreements

Before a role is actually assigned to a resource in Incentive Planning, it can be
modeled with agreement versions. Modeling enables incentive planners to
experiment with different versions of compensation plans before assigning a final
version to the sales field. For example, incentive planners could compare a plan that
pays a single commission rate with a plan that determines the commission rate
based on multiple tiers. In the second plan, the correct tier would be identified by
input from a formula.
The Modeling tab contains three subtabs: Agreement, Comparison, and
Performance. The Agreement subtab lets you create and view agreements and
assign quotas to the various agreement versions. The Comparison tab enables you
to compare different versions of an agreement by displaying the payout of each
compensation plan at predefined levels of quota attainment. The Performance tab is
where you can compare versions based on estimated achievement in what-if
scenarios.
Modeling Agreements 4-1

Overview of Modeling Agreements
Agreement versions are created in the Agreement subtab and can be activated to an
actual role in Incentive Planning or the commissions module of Oracle Incentive
Compensation from the Comparison subtab or Performance subtab.
4.1.1 The Modeling Process

The modeling process follows these steps:
1. Multiple agreement versions are created for a role.
2. Each agreement version is assigned details, such as an attainment table, quota
components, formulas, rate tables, anchors, and on target earnings.
3. Quotas are assigned to the quota components of each agreement version.
4. A contract is generated for each agreement version.
5. What-if scenarios are run for each agreement version.
6. The agreement versions and what-if scenarios are compared.
7. The analyst activates an agreement version to a role in Incentive Planning.
4.1.2 The Lifecycle of an Agreement Version

Agreement versions pass through a series of states as they are processed. The
statuses, in order, are:
1. New: A name and description have been entered for the agreement version, but
no details have been assigned.
2. Pending: The agreement version has been assigned details such as quota
components, formulas, rate tables, anchor values, and so on. An agreement
version in Pending status can be updated.
3. Generated: Quotas have been assigned to an agreement version that was in
pending status and rates for the quota components have been generated. A
what-if scenario can be can be set for agreement versions in Generated status.
4. Modeled: After a what-if scenario has been saved and the estimated payout is
automatically calculated, the status of the agreement version changes to
Modeled. The what-if scenario can be changed as long as the agreement version
has not been activated.
5. Activated: All details of the agreement version are assigned to the actual role in
Incentive Planning or directly into the commission module of Oracle Incentive
Compensation.

Assigning Details to an Agreement Version
4.2 Modeling Enhancements

There are no changes to the Modeling functionality in this release.
4.3 Creating an Agreement Version

The Model Create page is used to create a new agreement version.
Navigation
Modeling > Agreement > Create
Prerequisites
A sales compensation role must already be created in Resource Manager.
Steps
1. Click the Modeling tab. The Agreement Version Summary page appears.
2. Query for a role in the search parameter. Enter a name or four or more
characters and click Go to search.
3. Click Create. The Model Create page appears.
4. Enter a Version Name. This is a required field.
5. Enter a Version Description. This is a required field.
6. Enter a Start Date and End Date. Click the calendar icon to open a pop-up
calendar. This is a required field.
7. Click Create to save your new version.
8. Repeat steps 3 through 6 to create as many versions for the role as you need.
4.4 Assigning Details to an Agreement Version

The Agreement Version Summary page is the starting point for working with
agreement versions. For each role that is queried on the Summary page, the
high-level details, such as on-target-earnings, total quota, name, version, start date,
end date, and status are displayed.
Click the link in the Total Quota column to go the Assign Quota to Version page,
where you can assign or view quota amounts.

Click the View link in the Plan column to see the version of the modeled
compensation plan that was defined on the Agreement Version Details page. It
displays the agreement components, including rate tables and commission amounts
for each attainment level.
The version name is a hyperlink that brings you to the Agreement Version Details
page. It is here that you can define the compensation plan and how commissions
will be calculated. You can copy another version of an agreement. This saves time if
the new version you are creating differs in a minor way from another version.
Navigation
Modeling > Agreement
Prerequisites
Super User responsibility is required. Roles must be created in Resource Manager.
Attainment schedules must be defined.
Steps
1. Enter a role name in the Role Name field. Or, to search for a role, enter the name
in the Role Name field, or click Go to open a pop-up list. Click your selection on
the list.
2. Click Apply.
A list of role versions is displayed.
3. To assign details to a version, click the link the Version Name column.
The Agreement Version Details page is displayed.
4. If you want to copy another agreement version, select it from the Copy Version
drop-down list.
5. Click Apply.
6. Enter an amount for On Target Earnings.
7. Check the Club Eligible check box if the agreement includes club benefits at a
certain level of achievement.
8. Enter a rounding factor for calculation. The default is 1.00, but a lower setting
may be better under certain circumstances. See Guidelines.
9. Enter a Quota Minimum figure and a Quota Maximum, if there is one.

10. Select a Plan Level. This indicates the level in the salesperson hierarchy. Level 1
is the street level.
11. Select an attainment schedule from the Attain Schedule drop-down list.
Attainment schedules are defined in the Administration tab.
12. Click Submit to save your work.
Now, Enter components for the agreement version in the five sections following.
Fixed components are not calculated, so they require fewer fields of information.
The components can be sequenced by placing numbers into the Sequence column
starting at 1. This determines the order in which the components will appear on the
generated contract. In each section, you can remove components by checking the
Remove check box. The component will be deleted when you click Submit.
For all components, click Go to open a pop-up list. Click your selection to enter it
into the field. Also, you can click Submit to save or Restore to return to the
previously saved version at each section.
1. In the Fixed Pay components section, enter the amount in the Fixed Pay
Amount field.
2. In the Variable Pay, Non Computed Components section:
a. Enter an amount in the % of Total Quota field to indicate the importance of
a particular component in the resource’s compensation.
b. Enter the commission amount at 100% attainment. This is the amount that
will be paid out if the resource meets all of his or her sales goals.
c. If you need to use a calculation formula, select it from the list. Click Go to
open a pop-up list of selections.
d. If you selected a calculation formula, select a rate table from the drop-down
list.
e. Anchors are also part of a calculated component. You can disable them by
checking the Disable Anchors check box if you want to assign rates directly.
Click Define in the Anchors column to go to the Resource Details -
Customized Anchors page where you can customize anchors for this
specific agreement version.
f. To use a plan element, enter it in the Plan Element Name field.
3. For Variable Pay, Computed components, enter information in the fields in the
same way as you did for Non Computed components. The only difference is
that because the amounts are computed, a formula is required, and it can be

Allocating Quotas to Quota Based Components
edited. To make changes in the formula, click Edit in the Edit Formula column.
This takes you to the Computed Component Formula page.
4. The Variable Pay, Non Quota Components area has fewer fields, but you can
select calculation formula and rate table fields.
5. After the agreement version is approved and activated, it can be moved into a
compensation plan. To indicate the name of the future compensation plan, in
the Map to Compensation Plan area, enter the compensation plan name, along
with start and end dates.
Guidelines
In Incentive Planning, if you set up a different currency from the operating unit’s
functional currency (for example, for setting On Target Earnings, a quota, and so
on), then you should disable the rounding effect by setting the rounding factor to
0.01 or lower. This setting implies that the quota is not rounded in rate calculation
and contract generation. More information is available in Chapter 3, Incentive
Planning.
4.5 Allocating Quotas to Quota Based Components

Quotas can be assigned to quota based components of an agreement version that is
in the Pending, Generated, or Modeled state. Quota based and non-quota based
variable quota components can have rate table assignments. Commission rates are
calculated by the system if the agreement details setups require calculation.
Assigning quotas automatically generates rates for all of the agreement version’s
associated quota components and changes the agreement version’s status to
Generated.
Quota based and non-quota based variable quota components can have rate tables
assigned to them. Rate information must be populated into Incentive Planning.
To allocate quotas to components, perform the following procedure:
Navigation
Modeling > Agreement > Query for Role > Click figure in Total Quota column >
Assign Quota to Version
Prerequisites
The agreement version must be in Pending state or later, but cannot be already
activated.

Comparing Agreement Version Contracts
Steps
1. Click the Modeling tab. The Agreement Version Summary page appears.
2. Query for a role in the search parameter. Enter a name or four or more
characters and click Go to search.
3. Click the amount link in the Total Quota column. The Assign Quota to version
page appears.
The page displays the sales role, version name, version start date and version
end date.
4. Enter amounts in the blank fields in the Amount column. The Total rows are
automatically populated by the application.
5. When you are satisfied with the quota, click Update to save it.
4.6 Comparing Agreement Version Contracts

Use the Agreement Version Comparison page to compare two or more agreement
version contracts; The system calculates the payouts at each level of quota
attainment based on the attainment schedule assigned to each version. The
application displays graphically and tabularly the payouts at each attainment level
for each version. Then, you can activate the one that best suits your requirements.
Agreement version contracts can be compared more accurately if they have the
same attainment schedule. Comparison results are in the form of a table showing
total compensation for each attainment point on the attainment schedule and in a
line graph with %Attainment on the X axis and Total Compensation on the Y axis
and in a bar graph.
You can also use the Agreement Version Comparison page to view the agreement
details of a single agreement.
Navigation
Modeling > Comparison
Prerequisites
Agreement versions must already be created and be in the Generated state.
Steps
1. Click the Modeling tab and the Comparison subtab. The Agreement Version
Summary page appears.

Comparing Agreement Version Contracts
2. Select a role name.

a. Click Go to open a pop-up list.
b. Select a role.
c. Click Apply.
The agreement versions are displayed.
3. In the Select column, check the check boxes for the agreement versions you
want to compare.
4. Click Compare.
The Agreement Version Comparison page appears and displays the generated
payouts at different levels of attainment graphically and tabularly. Changes to
the agreement (setups and quotas) can be made from the Comparision page.
The following steps detail the specific changes that can be made to an
agreement that will have an effect on payouts.
5. Click the numbers in the Assigned Quota column to go to the Assigned Quota
to Version page. The amounts for each component can be changed. Click
Update to save any changes.
6. To change anchor values, click Modify in the Anchors column to go to the
Resource Details - Customized Anchors page.
7. Click Apply on the Agreement Version Comparison page to see the results of
your modifications.
If the planning analyst can determine which version best meets the company
objectives, he or she can activate a version so that it is eligible for use to assign
to the sales field. This can be performed on the Agreement Version Comparison
page or the Agreement Version Summary page that is under the Modeling >
Comparision subtab. Otherwise, the analyst can take advantage of the
Performance functionality.
8. After you have compared the versions, click the Comparison subtab to return to
the Agreement Version Comparison page.
9. If you want to activate one of the versions, in the Select column, check the check
box next to the version you want to activate.
10. Click Activate.
In the Activation Status column, Not Activated changes to Activated.

What-If Scenarios
11. If necessary, before clicking Activate, click Restore to return to the previous
information. You cannot undo an activation, however.
4.7 What-If Scenarios

In a what-if scenario, you enter values for variables used in the formula and obtain
an expected income figure. Inputs can be estimated achievements (amount or
quantity) or other variables used in the formula, such as payment amount.
The Performance subtab estimates the payouts for each compensation plan based
on a revenue value that is entered by the planning analyst. This estimated payout
differs from the values calculated during Comparision. Performance values are
entered by the planning analyst while the Comparision values are obtained by the
attainment schedules defined at the agreement version levels. Ideally, the
Performance values are those not present in the attainment values. Otherwise, the
payout will be the same as the payout displayed in the Comparision tab.
To create scenarios, perform the following procedure.
Navigation
Modeling > Performance
Prerequisites
Agreement versions must already be created and be in the Generated state.
Steps
1. Click the Modeling tab and the click Performance subtab.
The Agreement Version Summary page appears. It looks like the Agreement
Version Summary pages for the Agreement and Comparison subtabs, but it
includes an Estimated Payout column and a Scenario column.
2. Select a role name.
a. Click Go to open a pop-up list.
b. Select a role.
c. Click Apply.
The agreement versions are displayed.
3. Click a name in the Version Name column to go to the Estimated Achievements
page.

What-If Scenarios
a. Change the amount/units for estimated achievements for any variable

component. The assigned quota amounts are already populated to the left
for reference.
b. Click Update to save your changes and return to the Agreement Version
Summary page.
4. As before, to compare performance between versions, check the check box in
the Select column for each version you want to compare.
5. Click View Performance.
The Agreement Version Comparison page appears.
6. Click the numbers in the Assigned Quota column to go to the Assigned Quota
to Version page. The amounts for each component can be changed. Click
Update to save any changes.
7. To change the anchors, click Modify in the Anchors column.
The Resource Details - Customized Anchors page appears.
8. Click a number in the Estimated Achievements column to go to the Estimated
Achievements page (see step 3 previous).
9. Click Apply on the Agreement Version Comparison page to see the results of
your modifications.
If the planning analyst can determine which version best meets the company
objectives, he or she can activate a version so that it is eligible for use to assign
to the sales field. This can be performed on the Agreement Version Comparison
page or the Agreement Version Summary page that is under the Modeling >
Comparision subtab. Otherwise, the analyst can take advantage of the
Performance functionality.

Part III
Resources and Compensation Plans

■ Chapter 5, "Creating Resources, Roles and Groups"
■ Chapter 6, "Building Compensation Plans"
■ Chapter 7, "Assigning Compensation Plans, Pay Groups, and Payment Plans"
5
Creating Resources, Roles and Groups

■ Section 5.1, "Introduction to Creating Resources, Roles, and Groups"
■ Section 5.2, "Assign Resources to Roles and Groups"
5.1 Introduction to Creating Resources, Roles, and Groups

Before anyone can be paid compensation in Oracle Incentive Compensation, they
must exist as a resource in Resource Manager. In addition, a resource is assigned a
role and a compensation group, which are also created in Resource Manager. For
complete steps to perform these processes, refer to appropriate sections of the Oracle
CRM Application Foundation Implementation Guide (Implementing Resource Manager)
or Oracle CRM Foundation Concepts and Procedures (Understanding Resource
Manager).
5.1.1 Set Up Resources for Team Compensation

You can use Resource Manager to define resource teams that are recognized by
Oracle Incentive Compensation when calculating compensation amounts for
members of a team.
A transaction typically is associated with a single resource (especially if Oracle
Order Management is the transaction source). If the resource on the transaction is a
member of a team, then Oracle Incentive Compensation automatically calculates
compensation for every member of the team. For example, assume Steve is a
member of a team consisting of Steve, John, and Bill. A transaction for $100 is
collected into OIC. Steve is entitled to 100% credit for this transaction, but because
he is also a member of a team, OIC automatically gives 100% credit to John and Bill
as well.
Creating Resources, Roles and Groups 5-1

Assign Resources to Roles and Groups
However, even though team members all receive credit for the transaction, the sales
credit rolls up a sales hierarchy only on the original transaction. For example, if
Steve, John, and Bill all report to Bob, Bob receives only $100 sales credit (from
Steve). If Steve reports to Bob but John and Bill report to Sally, only Bob receives
rollup sales credit. Even if Steve, John, and Bill each have different managers, only
Bob receives the rollup sales credit.
Refer to the Oracle CRM Application Foundation Implementation Guide for the specific
steps necessary for creating a team and adding resources to it.
5.2 Assign Resources to Roles and Groups

Resources are assigned to roles and groups in Resource Manager. Refer to
appropriate sections of the Oracle CRM Foundation Implementation Guide (Defining
Dynamic Groups) or Oracle CRM Foundation Concepts and Procedures (Understanding
Resource Manager). Or, Refer to Oracle CRM Application Foundation Implementation
Guide (See: Implementation Tasks for Resource Manager).
Navigation
Toolbar > Tasks > Import Resources
Prerequisites
Access to Resource Manager as Super User.
Steps
NOTE: All items that have a reference of creating or assigning an item should be
noted as a prerequisite prior to adding a Supplier to Oracle Payable. The following
steps are in the Forms user interface.
1. In the Toolbar, click Tasks > Import Resources
2. In the Resource Category field, select Supplier Contact from the list of values.
3. Enter information into the Name and Contact fields or select from the list of
values.
4. Click Search. This populates the Search Results field.
5. Click Create Resource.
6. Verify the start date, then click OK.
7. Click Save Resource, then click Details.

8. Create Sales Role and Compensation Group.

9. In the Resource form, assign a valid Salesperson number.
10. Click the Roles tab. Assign a role type from list of values as Incentive
Compensation.
11. Assign a Role from the list of values. Save.
12. Click the Group tab and assign Group from list of values.
13. Click Save. Resources tab is displayed. Select desired sales credit type from list
of values. Save.
Guidelines
In some cases you may not be able to find Sales Compensation in the Role Type list
of values. If this is the case, try the following:
Run the following SQL query.
select table_name, nullable
from dba_tab_columns
where column_name = ’ROLE_MODEL_ID’
and owner = ’CN’ ;
The correct output for the above query is below:
TABLE_NAME Nullable
CN_PLAN_TEXTS Y
N_ROLE_MODELS_ALL N
CN_ROLE_PLAN_MAPS Y
CN_ROLE_QUOTA_CATES Y
CN_SRP_QUOTA_CATES_ALL Y
CN_SRP_ROLE_DTLS_ALL Y
CN_SRP_TOTAL_COMPS_ALL Y
Creating Resources, Roles and Groups 5-3

If CN_ROLE_QUOTA_CATES, CN_SRP_QUOTA_CATES_ALL, and CN_SRP_ROLE_

DTLS_ALL are not set to ’Y’, run the following SQL scripts and commit after each
script:
ALTER TABLE CN.CN_ROLE_QUOTA_CATES MODIFY (ROLE_MODEL_ID
NULL);
ALTER TABLE CN.CN_SRP_QUOTA_CATES_ALL MODIFY (ROLE_MODEL_ID
NULL);
ALTER TABLE CN.CN_SRP_ROLE_DTLS_ALL MODIFY (ROLE_MODEL_ID
NULL);

6
Building Compensation Plans

■ Section 6.1, "Overview of Building Compensation Plans"
■ Section 6.2, "Enhancements to Building Compensation Plans"
■ Section 6.3, "Defining Calculation Expressions"
■ Section 6.4, "Defining Rate Dimensions"
■ Section 6.5, "Defining Rate Tables"
■ Section 6.6, "Defining Formulas"
■ Section 6.7, "Defining Plan Elements"
■ Section 6.8, "Transaction Factors and Accelerators"
■ Section 6.9, "Defining Compensation Plans"
6.1 Overview of Building Compensation Plans

A typical compensation plan consists of one or more modular components, or plan
elements. Plan elements may reflect variations of commission or perhaps a bonus
based on the accumulated achievement of the sales agent. Plan elements can also be
configured for tracking nonmonetary credits such as managerial points or
production credits.
A compensation plan is built from plan elements and is assigned an effective start
date and an effective end date. The plan can then be assigned to multiple sales roles.
Compensation plans can be defined directly in Oracle Incentive Compensation or
can be activated from an approved and accepted agreement from the Incentive
Planning area of Oracle Incentive Compensation.
Building Compensation Plans 6-1

Enhancements to Building Compensation Plans
All modular components used in the system can be configured and reused in
different combinations. Taking full advantage of this capability simplifies system
configuration as well as administration. For example, from a relatively small library
of plan elements, you can configure many compensation plans.
Plan elements consist of modular components that can be freely assigned in
different combinations. These underlying components have several distinct
functions:
■ Revenue Classes are used to classify a bundle of classification rules that
establishes the event eligible for compensation and the basis of calculation.
■ Formulas determine how the compensation will be calculated.
■ Rate Tables are the part of a formula that determines the rate at which
achievements are commissioned. Rate dimensions are the structural part of a
rate table to which values are added.
■ Calculation expressions are interchangeable, reusable parts that are used in
input and output expressions of formulas, expression-based rate dimensions,
and performance measures.
To build a compensation plan, you start at the smallest pieces and work up to larger
ones. That means that you build compensation plans in this order:
1. Create calculation expressions and rate dimensions
2. Create rate tables using rate dimensions
3. Build formulas out of expressions and rate tables
4. Set up revenue classes
5. Make plan elements containing formulas and revenue classes
6. Build a compensation plan from plan elements
6.2 Enhancements to Building Compensation Plans

There are no major enhancements to building compensation plans in this release.
6.3 Defining Calculation Expressions

Calculation expressions are interchangeable, reusable parts that are used in input
and output expressions of formulas, expression-based rate dimensions, and
performance measures.

Defining Calculation Expressions
There are 100 user definable column attributes. You can use these calculation
expressions as performance measures, input expressions, output expressions, or rate
table dimensions. You can also nest one calculation expression within another.
As part of the definition process you can select columns from a list of table columns
on the Expressions subtab of the Incentive tab to create expressions. Once they have
been saved the expressions can be assigned and reassigned to any number of
formulas you need.
Do this by selecting a valid expression from a List of Values at each of the pages for
performance measure, input and output.
You can place a formula inside a calculation expression if you want to be certain
that the expression is used after that formula. Sequencing plan elements in a
compensation plan can also assure that calculations are performed in the order you
need.
A performance measure can be an accumulation of transaction values that are
captured by the plan element to which it is assigned. Performance measures serve
as a mechanism to gather cumulative information by plan element and group them
for use in reports that compare achievements to quota, goal and performance
measure.
An example of a performance measure is revenue. You can select and define the
columns where revenue information for transactions is held. As transactions are
entered and collected for the assigned plan element, the transaction values are
accumulated. An example performance measure is:
TRANSACTION_AMOUNT
Note: Performance measures must use numeric expressions to work correctly. In a
formula, if no performance measure is assigned, the application uses the first (*)
input expression. If that expression evaluates to string values, the calculation will
fail. Therefore, it is important when using an input expression that is not numeric to
assign a numeric performance measure.
Input formulas tell Oracle Incentive Compensation what to evaluate from the
transactions and how to match the results to the corresponding rate table. Think of
the input expression as a sorter for all incoming transactions for Oracle Incentive
Compensation. An example input formula expression looks like this:
(TRANSACTION_AMOUNT*EVENT_FACTOR)/TARGET
For example, as a condition, a company can establish that its sales force will be
compensated based on transaction amount. The input expression will merely state

that transactions will be sorted by TRANSACTION_AMOUNT from the CN_

COMMISSION_HEADERS column.
This is an example of a rate table:
$0 - $100 4%
$100 - $500 5%
$500 - $99,999 6%
As transactions are sorted by through the input expression they are matched to the
established rate table tiers. If a transaction is collected in Oracle Incentive
Compensation with the following attributes:
1. Customer X
2. Transaction Amount $100
3. Product Z
Oracle Incentive Compensation, using the input expression created matches the
above transaction of $100 with the rate table and determines that 5% will be paid on
this order.
Outputs of the formula instruct the application how much to pay salespeople. The
payment amount can either be tied to a rate table or not. This will be determined by
the users.
In this example above, business users determined that the salespeople will be paid
based on the rate table result, transaction amount, and a constant uplift/accelerator
factor of 1.035. Users will need to tell Oracle Incentive Compensation in which
columns this information resides and then apply the calculations.
Example of an output expression:
Rate Table Result * (TRANSACTION_AMOUNT * PAYMENT_FACTOR)
Using the above output expression, multiply 5% with the transaction amount
($100), event factor of 100% and 1.035 for the payment accelerator or payment
uplift. The 4% is multiplied by the result of the sum in the brackets. If the payment
factor is 1.05, then the result or commission is $5.25 ($100 x 4% x 1.05 = $5.25).
Use the following procedure to define calculation expressions.
Navigation
Incentive > Expression

Prerequisites
Table and column mapping is complete.
Steps
1. Click the Incentive tab and click the Expression subtab.
The Calculation Expressions page displays a list of already created calculation
expressions.
2. To create a new calculation expression, click Create.
The Calculation Expressions page with blank fields appears.
3. Enter a unique name for the expression. This is a required field.
4. Optionally, provide a description for the expression.
5. Select a Type from the drop-down list. The seven selections represent groups of
calculation elements, such as expressions, formulas, and SQL functions. Only
the calculation elements in that selection are displayed in the Calculation Values
box.
6. From the Calculation Values box, select the column to be used in the expression.
7. Click the right arrow button to move the element in the Calculation Values box
into the Expression box.
If you change your mind, you can click the left-arrow button to remove an entry
from the Expression box.
8. If your expression requires it, select an operand from the row below the
Expression box. It appears immediately in the Expression box without using the
right arrow button.
Again, to remove an item from the Expression box, click the left arrow button.
9. Optionally, numeric constants or string values can be added to an expression.
Enter the numeric value or string value desired and click the right arrow button
to move it to the Expression box. As above, click the left arrow button to remove
an entry from the Expression box.
10. Add elements and operands until the desired expression has been created.
11. Optionally, click Restore to return to the previously saved information.
12. Click Update to save and compile your expression.

The status of the expression should read Valid if it has compiled properly.

Defining Rate Dimensions
13. The usage of the expression will also be displayed once it is saved. The usage
rules will determine where the expression may be applied.
Guidelines
A Bonus calculation expression cannot include an element from the table cn_srp_
period_quotas or any table that is mapped to this table. A Bonus calculation
expression cannot be used as an embedded formula and cannot be mixed with a
commission type formula. See Bonus Formulas for more information.
User table names are listed under External Elements. You join an external table to an
internal table by mapping them using Administration > External Tables.
Selected columns are accessible for use in building formulas and performance
measures. The user column name is listed rather than the actual column name.
The following Oracle Incentive Compensation tables are predefined in the system
and can be used as calculation values in defining performance measures and
formulas:
CN_COMMISSION_HEADERS
CN_COMMISSION_LINES
CN_SRP_QUOTA_ASSIGNS
CN_SRP_PERIOD_QUOTAS
CN_QUOTAS
A rate dimension calculation expression can only be defined from the following
tables:
CN_SRP_PERIOD_QUOTAS
CN_SRP_PAN_ASSIGNS
CN_SRP_QUOTA_ASSIGNS
CN_SALESREPS
An output expression cannot contain both ITD_TARGET and ITD_PAYMENT.
6.4 Defining Rate Dimensions

Rate dimensions define the tiers that are used in a rate table. There are four kinds of
rate dimensions:

■ Amount: The rate tiers are quantities.

■ Percent: The rate tiers are percentages of a quota.
■ Expression: The rate tiers use an expression that has already been defined.
■ String: The rate tiers are alphanumeric, such as product numbers or the names
of states.
These values comprise the ranges from which compensation is calculated in a rate
table.
You can select Amount or Percent dimensions on the Dimensions page from a
drop-down list.
If a commission rate is based on multiple criteria, then a multidimensional rate table
must be created to reflect all criteria. Use one dimension per criterion.
The calculation module has been modified to support accumulation across multiple
dimensions when a multidimensional rate table is assigned to a plan element.
With this release, the calculation module also provides users the ability to specify
one dimension in a multi-dimensional rate table for which they would like the rates
to be split.
In the following example, three dimensions are used to calculate various
commission rates: License Revenue (percent of quota), State, and Product. The
formula first compares transaction revenue with the first dimension, License
Revenue. Next, the formula compares transaction location with the second
dimension, State. Finally, the formula compares product identification with the
third dimension, Product.
A dimension contains rate tiers to establish different levels of achievement to be
compensated at different rates. In this example, two dimensions have two tiers and
one has three, but any number can be defined.
The License Revenue dimension:
0-100
100-9,999
The State dimension:
Arizona
California
Oregon

The Product dimension:

PCs
Peripherals
Together, there are 12 possible combinations, and each one can be assigned a
different commission rate.
Your minimum and maximum values in the Rate Tiers section must be stated in
terms consistent with your input information.
You can change both the tiers and rates for a rate table. Any changes you make are
propagated to all plan elements to which those rate tables are assigned, and thus to
any salespeople that are assigned to roles that are assigned plans containing those
plan elements. If you change the levels of quota achievement in a tier, or add or
delete a tier in a rate table, those changes propagate to all salespeople, regardless of
whether their plans have custom quotas or rates.
The following table shows four columns of a Dimension and Rates Example.
Columns are License Revenue, State, Product, and Rate. Product is chosen as the
base dimension. There are 6 possibilities for each of the two tiers in the License
Revenue dimension, including all combinations with the other two dimensions.
License Revenue State Product Rate

0-100 Arizona PCs 1%
0-100 Arizona Peripherals 5%
0-100 California PCs 1.5%
0-100 California Peripherals 4.5%
0-100 Oregon PCs 1.25%
0-100 Oregon Peripherals 6.25%
100-9,999 Arizona PCs 4%

100-9,999 Arizona Peripherals 8%
100-9,999 California PCs 4.5%
100-9,999 California Peripherals 7.5%
100-9,999 Oregon PCs 4.25%
100-9,999 Oregon Peripherals 9.25%

Navigation
Incentive > Rate
Prerequisites
For an expression type dimension, the expressions must already be defined.
Steps
1. Click the Incentive tab and click the Rate subtab.
The Rate Tables page appears.
2. Click the name of the rate table for which you want to create or edit a
dimension.
The Rate Table Details page appears.
3. In the Dimension area, click Details next to any already created dimensions to
open the Dimensions page. It contains the rate tiers assigned to the dimension.
4. To create a new dimension, click Create.
The Dimension page opens. The fields are blank.
5. On the Dimensions page, for a new dimension, enter a name in the Name field.
If you are editing an existing dimension, be sure the field contains the name of
the dimension on which you want to work.
6. Select or verify the type from the drop-down list.
7. Optionally, enter a description.
8. In the Rate Tiers area, enter numbers in the From and To columns to create rate
tiers. Follow the sequence, and do not leave any gaps between the tiers.
9. If you want to add a tier, use the blank fields at the bottom of the table.
10. To delete a tier, click the Remove check box next to the tier and click Update.
11. If necessary, click Restore to return to the previously saved information.
13. Click Back to return to the Rate Table Details menu, where you can assign the
dimension you created to the rate table.

Defining Rate Tables
Guidelines
If the application is unable to find a match in a string dimension in a rate table, the
application picks the last rate value by default. For example, suppose that in the
example above, a transaction has dimension values of 10,000, Iowa, and Service. No
matches occur, and the rate table result is 9.25%, the last value in the Rate column.
If you do not want non-matching transactions to receive commission, add "OTHER"
as the last string value to each string dimension with a corresponding commission
rate of 0, for example.
Another method of dealing with non-matching transactions is to use classification
rules. Transactions with attributes that do not match your classification rules will
have a failed classification status. You can correct these failed transactions’
attributes by changing their values and maintain a record of the adjustment through
the manual adjustments window.
6.5 Defining Rate Tables

Rate tables are used to establish compensation percentage rates or fixed amounts
for different performance levels. The compensation formula and plan element
determine the type of information to be compared to the rate table as well as how
the resulting rate is used in the calculation.
The Rate subtab contains a side panel menu that provides links to several pages.
After you have chosen a rate table, click the links to see the following:
■ Summary: Lists all rate tables that have been created
■ Detail: Displays details of the rate table you selected
■ Commission Rates: Displays the commission rates for the selected rate table
■ Formulas: Displays the formulas to which the rate table is assigned
■ Plan Elements: Displays the plan elements in which the rate table is used
Amount type rate tables base compensation on amount of sales volume. Percent
type rate tables are based on percentage of goal achieved.
To define rate tables, perform the following procedure:
Navigation
Incentive > Rate

Defining Formulas
Prerequisites
None.
Steps
1. Click the Incentive tab and click the Rate subtab.
The Rate Tables page appears
2. Click Create.
The Rate Table Details page appears.
3. In the Name field, enter a unique name for the rate table.
4. Select a Rate Table type, either Amount or Percent, from the drop-down list.
6. To add an already created dimension to the rate table, on the Rate Table Details
page, enter four or more characters in the Dimension Name field and click Go
to open a pop-up list. See Guidelines.
7. Select a rate dimension from the list.
8. To assign or change commission rates, click the Assign Commission Rates link
to go to the Assign Commission Rates page.
9. To create a new dimension, on the Rate Schedule Detail page, click Create.
The Dimensions page appears.
10. After you have assigned the dimensions you need to the rate table, click Update
to save your work. If necessary, click Restore to return to the previously saved
information.
Guidelines
If a rate schedule is already assigned to a formula or plan element, it cannot be
deleted and the commission type cannot be updated. Dimension assignments
cannot be changed. An error message displays if you attempt to delete or change a
rate schedule that is already assigned.
6.6 Defining Formulas

You have complete flexibility to create formulas for calculating compensation. Some
formulas can be embedded in another formula definition or in a plan element
definition. You can save an incomplete formula and return to complete it later.

Defining Formulas
Any expressions that you use in a formula must be created before you define a
formula. Expressions can be repeated in your formula and can be reused in other
formulas as well. See the Guidelines section of Defining Calculation Expressions for
more information on the types of calculation expressions that you can use for
commission and bonus formulas.
Any column from any table can be part of your formula, as long as the Calculation
Value check box for the column is selected in Columns and Tables.
To create formulas, perform the following procedure.
Navigation
Incentive > Formula
Prerequisites
Expressions must be created first.
Steps
1. Click the Incentive tab and click the Formula subtab.
The Formulas page appears.
2. Click Create to create a new formula.
The Formula Definition page appears.
3. Enter a unique name and a description for your formula.
4. Enter Commission or Bonus from the drop-down list in the Type field. (See
Guidelines)
5. Select Individually or Group from the Apply Transactions drop-down list. (See
Guidelines)
6. Make a selection from the Split drop-down list. (See Guidelines)
7. Check the Cumulative check box if you want to aggregate the transactions. (See
Guidelines).
8. Check the Interval To Date check box if you want to base the calculation on a
period different from the plan element interval. (See Guidelines)
9. Check the Planning check box if this formula is used for plan modeling
purposes.

Defining Formulas
10. Click Update to save your work. If you are making changes to a previously
saved formula, you can click Restore to return to the previously saved version.
11. Click the Expressions link on the side panel menu.
The Expressions page appears.
12. In the Input area, select an expression from the drop-down list to represent your
formula input. You can use more than one input expression, but the number of
input expressions must equal the number of dimensions in the rate table that
you select later.
13. Assign a forecast, if desired.
14. If you selected Proportional or Non-Proportional in the Split drop-down list on

the Formula Definition page (step 6), a Split Flag button appears on the
Expressions page. Click this button next to the expression of the formula for
which you want to use the split. You cannot split more than one expression in a
formula.
15. If you checked the Cumulative check box on the Formula Definition page (in
step 7), a Cumulative Flag check box appears on the Expressions page. Check
the check box for any expression that you want to be aggregated.
16. Click the eraser icon in the Remove column to delete an expression from the
formula.
17. In the Output area, select an expression from the drop-down list.
18. As with the input expression, you can select a forecast from the drop-down list.
19. In the Performance Measure area, select an expression from the drop-down list.
The performance measure, as well as the quota, is used in reports for
comparison with achievement.
20. Click Update to save your work. If you saved the expression before, you can
click Restore before you click Update to return to the previously saved version.
21. Click the Rate Tables link on the side panel menu to assign a rate table to the
formula.
22. Click Go in the first blank field in the Name column to open a pop-up box.
Select a rate table and click it.
23. Enter an effective start date and end date. You can view the rate table details
and rates by clicking Rate Table Details.

Defining Formulas
24. Click the Detail link on the side panel menu and click Generate. If you have
successfully created the formula, the status field above the Generate button will
change from Incomplete to Complete.
Guidelines
A Bonus Formula is a type of Formula where there are no links or references to
transactions. See the Guidelines section of Defining Calculation Expressions for
more information. Also see Bonus Formulas.
Do not split tiers if you want a rate from the rate table applied to the full amount.
Split tiers if you want portions of the full amount paid at each rate up to the top
qualifying rate. For example, the rate table shows 0-1000 at 1%, 1000-2000 at 2%.
The transaction amount is 1500. If you select No Split in the drop-down list, 2% is
applied to the whole transaction amount of 1500. If you select Non-Proportional in
the drop-down list, 1% is applied to 1000 and 2% is applied to 500.
The Proportional selection in the Split drop-down list is intended for use with
amount rate tables. For example, if the rate table shows 0−1000 at 100, 1000−2000 at
200. The first transaction amount is 200. The commission for this transaction is 20
because 200 is one fifth of the first rate tier and one fifth of the 100 rate is 20. If the
second transaction amount is 1300, the remaining four fifths of the first rate tier
pays 80, and half of the second tier [(1300−800)/(2000−1000)] pays 100 (half of the
rate 200). Total commission for the second transaction is 180.
Select the Cumulative check box if transactions are required to be aggregated in
total. The rate applied will be determined by the transactions-total achieved to date
within the interval.
Use interval-to-date quotas and fixed amounts if:
■ Calculation is to occur before the end of the plan element interval (for example,
if the interval is quarter and calculation occurs monthly)
■ Quotas are set cumulatively within the interval
■ Performance to date is to be compared to the quota to date
Note: Performance measures must use numeric expressions to work correctly. In a
formula, if no performance measure is assigned, the application uses the first (*)
input expression. If that expression evaluates to string values, the calculation will
fail. Therefore, it is important when using an input expression that is not numeric to
assign a numeric performance measure.

Defining Plan Elements
Dependency Notes
Commission Formulas
1. Individual Option for Transactions can be used with any Accumulate/Interval
to Date option.
c. By default Interval to Date and Accumulate options must be used together.
You cannot select Interval to Date by itself. Split options are selectable (each
is mutually exclusive).
d. Accumulate can be selected by itself. Split options are selectable (each is
mutually exclusive).
2. Group by Interval for Transactions can only be used with Accumulate. Split
options are selectable (each is mutually exclusive).
Bonus Formulas
Bonus formulas calculate only against Individual transaction options. Split options
are selectable (each is mutually exclusive).
Use interval to date quotas and fixed amounts if:
■ Quotas are set each period
■ Quotas are set cumulatively within the interval
■ Performance to date is to be compared to the quota to date
6.7 Defining Plan Elements

A plan element is part of a compensation plan. It specifies the conditions a
salesperson must meet to be eligible for compensation, and it determines how the
compensation is calculated. Use the following procedure to define plan elements.
Prerequisites
If the plan element includes a formula, then the formula must exist. (See Defining
Formulas.)
If the plan element includes a rate table, then the rate table must exist. (See Defining
Rate Tables.)
If the plan element includes a revenue class, then the revenue class must exist.

Steps
1. Click the Incentive tab and click the Element subtab.
The Plan Elements page appears.
2. Navigate to the Plan Element Details page by performing one of the following.
■ To view or make changes to the plan element, click a plan element name in
the Name column. The Plan Element Details page will contain the
previously entered information.
■ To create a new plan element, click Create. The Plan Element Details page
will be blank.
3. Enter or verify the Name and Description at the top of the page. The Name field
is required.
4. Select a Quota Group from the drop-down list. See Guidelines.
5. Enter or verify Start Date and End Dates. The Start Date is a required field.
6. In the Parameters area, select an incentive type from the drop-down list.
Selections include Commission, Bonus, and Manual. See Guidelines.
7. Select an Interval Type from the drop-down list. See Guidelines.
8. Select a Credit Type from the drop-down list. The credit type is normally the
functional currency, but it can be any type that you define in the application.
9. Select a Formula Type from the drop-down list. This is a required field. See
Guidelines.
10. If you select a Formula type of Formula, select a formula from the drop-down
list in the Choose Formula field. See Guidelines.
11. If you select Formula type of External, you must enter the package name in the
Package Name field. See Note in the Guidelines section.
12. Liability accounts can be identified at the plan element level. Earnings for the
plan element are assigned to the specified liability account. To assign a liability
account to a plan element, enter four or more characters in the Liability Account
field and click Go. From the Code Combination window, select the desired
liability account. See Guidelines.
13. Expense accounts can be identified at the plan element level. Earnings for the
plan element are assigned to the specified expense account. To assign an
expense account to a plan element, enter four or more characters in the Expense

Account field and click Go. From the Code Combination window, select the
desired expense account. See Guidelines.
14. Check the Eligible for Payee Assignment check box if you want the eventual
payment to be assigned to someone other than the salesperson credited with the
sale.
15. In the Variables area of the Plan Element Details page, enter the Target, Fixed
Amount and Goal figures. See Guidelines.
16. If you make a mistake, click Restore to return to the previously saved version.
17. Click Create to save your work.
Guidelines
The Quota Group drop-down list contains three choices. If you select:
■ None: The plan element name does not display in the Year to Date Summary.
■ Bonus: The plan element displays in the Bonus category of the Year to Date
Summary.
■ Quota: The plan element name displays in the Quota category of the Year to
Date Summary.
In step 6, the Commission incentive type is based on formulas in a compensation
plan. Bonus incentives are additional compensation based on aggregated
transactions.
In step 7, commonly used intervals are Period (month), Quarter, and Year. After a
compensation plan has been assigned to a sales role, you can change the interval
type of the plan element. If you have assigned the plan and you want to change the
interval for a plan element, you must remove the plan assignment, change the plan
element’s interval, then reassign the compensation plan. You should not change the
credit type of a plan element once the plan element is in use.
In step 9, if you choose an external formula type, you must enter the name of the
PL/SQL package in the Package Name field. If you select a formula type of
Formula, be sure to select a formula with a status of Complete.

Note: You can use an external formula in a plan element in this

release of Oracle Incentive Compensation. External formulas are
similar to system generated formulas, except that they contain
customized material. This means that when you upgrade the
application, any changes that were made are not automatically
applied to the external formula, so they must be applied manually.
To use an external formula in a plan element, select External
Formula type in the Formula Type field and enter the name of the
PL/SQL package in the Package Name field.
To create an external formula, perform the following steps:
■ Start with a system generated formula that resembles your
desired formula as closely as possible.
■ In the PL/SQL code, rename the formula, changing the name in
every place it appears.
■ Change the formula number to Null.
■ Add customization as required.
6.7.1 Assigning Revenue Classes to a Plan Element

Revenue classes are user-defined categories of business revenue used to determine
whether sales credit is applied toward a compensation payment. Plan elements
contain revenue classes because resources are given certain categories or specific
products or services to sell. To assign a revenue class to a plan element, perform the
following procedure.
Navigation
Incentive > Element > Plan Element Details > Revenue Classes
Prerequisites
Revenue classes must already be defined on the Administration tab. Plan element
details have been defined in the Plan Element Details page.
To assign revenue classes to a plan element, perform the following procedure:
Steps
1. Click the Incentive tab and click the Element subtab.

The Plan Elements summary page appears.

2. In the Name column, click the name of the plan element to which you want to
assign a revenue class.
The Plan Element Details page appears.
3. In the side panel menu, click Revenue Classes.
The Assign Revenue Classes page appears.
4. Select a revenue class by clicking Go next to the first empty field in the Revenue
Class column under any previously assigned revenue classes.
A pop-up window appears listing all available revenue classes.
5. Select a revenue class by clicking it.
6. Assign a quota to the plan element for the selected revenue class and enter it in
the Quota column.
7. Assign a fixed amount to the revenue class for this plan element.
8. Assign a goal in the Goal column for this plan element.
9. If necessary, click Restore to return to the previously saved version.
11. Click Details in the Details column to go to the Plan Element Details page. On
that page you can specify transaction factors and other factors that affect
commission payments.
6.7.2 Assigning Rate Tables to a Plan Element

Rate Tables are essential to calculation commission with a plan element. To assign a
rate table to a plan element, perform the following procedure.
Navigation
Incentive > Element > Plan Element Details > Rate Tables
Steps
1. Click the Incentive tab and the Element subtab.
The Plan Elements summary page appears.
2. In the Name column, click the name of the plan element to which you want to
assign a rate table.

The Plan Element Details page appears.

3. In the side panel menu, click Rate Tables.
4. Enter a rate table name in the Name column. Click Go to open a pop-up list.
5. Select a rate table from the pop-up list and click it.
6. Enter an effective start date and end date. You can view or adjust the
commission rates by clicking Rate Table Details.
7. Enter a child formula from the drop-down list if desired. See Guidelines.
8. Click Apply.
Guidelines
Child rate tables are referenced within embedded formulas. The following example
illustrates how child rate tables are used.
First, you create the formula to be embedded, and then create the formula that is
referenced by the plan element, which includes the embedded formula within it.
Assume that you want to calculate commissions based on percentage of quota, but
only for transactions where the sales credit is greater than $1,000. First you must
create an expression to determine if the sales credit is greater than $1000. The
expression looks like this:
Commission.Headers.TRANSACTION_AMOUNT/1000
Use this expression as the input expression for the embedded formula. If the result
is greater than 1, then you know that the sales credit is greater than $1000.
Next, configure an amount rate table with two tiers (one tier for values less than 1
and one tier for values greater than 1):
Amount Rate
0-1 0
1-999,999,999 1
In this example, the first tier with an amount of less than 1 has a rate of 0, and in the
second tier, anything greater than one has a rate of 1.

Transaction Factors and Accelerators
Create an output expression that references the rate table result. Select Others from
the Type drop-down list and click Rate Table Result.
Next, you need to configure the embedded formula out of the input expression, rate
table, and output expression you have just created. It will be referenced by the other
formula.
Now you can configure the formula that will be referenced by your plan element.
First, configure an expression to reference the formula that you just created. This
expression looks like this:
Commission Headers.TRANSACTION_AMOUNT/(SRP Period Quota.TARGET_
AMOUNT*<embedded formula>).
Next, create the rate table for your formula, as follows:
Percent Rate
0-100% 3%
100-9999% 4%
Finally, create an output expression that multiplies your rate table result by the
transaction amount:
Rate Table Result*Transaction_Amount
When you build this formula, use the expressions and the rate table you have just
created. Then, when you configure your plan element, reference the second formula
that you created.
When you save the plan element, the rate tables associated with the formula and
with the embedded formula are both associated with the plan element. When you
view the rate tables associated with the plan element on the Incentive > Element >
Rate Tables page, the Parent Rate Table section shows the rate table that was created
for the second formula, while the Child Rate Tables section displays the rate table
associated with the embedded formula. Because it is possible to create multiple
embedded formulas, OIC provides a drop-down menu that enables you to select
any one of the embedded formulas that you may have configured.
6.8 Transaction Factors and Accelerators

In a plan element, you can modify the incentive amounts by using payment and
quota accelerators, as well as transaction factors and other factors. You define the
effective period for these temporary changes by assigning a Start Date and an End

Date. Accelerators increase compensation during that time period, and can be used
as incentives for salespeople.
6.8.1 Accelerators
For each revenue class, at plan element level, you can define incentives known as
accelerators. Oracle Incentive Compensation provides you with two types of
accelerators:
■ Payment factor: Increases the salesperson’s commission payment without
affecting the level of quota achievement
■ Quota factor: Increases a salesperson’s quota credit without affecting the
payment
When you want to provide an incentive without affecting a salesperson’s quota
achievement, you can define a payment factor. The payment factor is a percentage
factor multiplied against the net sales credit, resulting in compensation credit. The
application then applies the compensation rate to this compensation credit to
calculate the compensation. Thus, a payment factor results in a higher
compensation amount but no higher quota achievement.
For example, a payment factor of 200% has been put onto the revenue class of
LIC-DB compensation plans for field salespeople to promote sales of this type of
license. The application calculates the amount of sales credit due to Salesrep A and
which tier in the rate table should be used. It then calculates the net sales credit due.
The payment factor is then multiplied against this amount to get to the total
compensation amount due to Salesrep A.
How the Accelerators and transaction factors are used will depend on how your
calculation expression is defined. For example, a common input expression that
complements a percentage rate table is as follows:
EVENT_FACTOR* QUOTA_FACTOR*TRANSACTION_AMOUNT/TARGET.
A typical output expression looks like this:
Rate_ Result* TRANSACTION_AMOUNT* EVENT_FACTOR* PAYMENT_
FACTOR.
You can change the rate table assigned to a plan element at any time, regardless of
the rate table assigned to the formula.
Steps 12, 13, and 14 only apply if you are integrated with Oracle Payroll and/or
Oracle Payables.

In steps 12 and 13, expense and liability accounts are used to transfer and post
information from Oracle Incentive Compensation to Oracle Payables. This function
is used for outside suppliers and vendors, not for internal employees, who are paid
through Oracle Payroll or a third party application.
Expense and Liability Accounts can be assigned at three levels: plan element,
revenue class, and classification. After the data is mapped to the interface table in
Oracle Incentive Compensation, the subledger is updated to reflect the amounts
paid. The liability account is also mapped to the Oracle Payables interface using the
account generator in Oracle Incentive Compensation.
In step 15, target, fixed amount, and goal are measurements that will be compared
against actual achievements. If you have target, fixed amount, and goal figures
against more than one revenue class assigned to this plan element, you can check
the sum amounts from the Revenue Classes check box and the totals from all
revenue classes will appear in these three fields. The Distribute function allows you
to seasonalize your quota, fixed amount and goals.
In general, you can assign multiple plan elements to a compensation plan, and you
can assign the same plan element to multiple compensation plans. When you
change the structure of a plan element, it applies to every compensation plan that
uses it and for every salesperson assigned to that plan. The affected compensation
plans must again be validated.
6.8.2 Transaction Factors

Transaction factors help you stage sales credit over the life of a sale, assigning
percentages of the transaction amount to the events that are important to your sales
organization.
Prerequisites
Revenue class is already created.
Steps
1. In the Accelerators area, enter a start date and end date for each accelerator.
Click the calendar icons to the right of each field to use the calendar pop-up
window.
2. Enter numbers in the Payment% and Quota% fields to show the amount of
acceleration you want to assign. The default is 100, which is the full amount.
Entries can be above or below 100.

Defining Compensation Plans

5. In the Transaction Factors area, enter numbers in the Factor% fields to stage the
payment of commission. See Guidelines.
6. If there are more transaction factors than can be seen at one time, use the drop-
down list at the bottom of the area to scroll through them.
7. In the Other Factors area, assign any changes you want to make to the listed
events. The default entry for the Factor% column is 100 for each field.
8. If there are more other factors than can be seen at one time, use the drop-down
list at the bottom of the area to scroll through them.
9. If necessary, click Restore to return to the previously stored information.
Guidelines
Make sure that your transaction factors add up to 100% in total. For example, you
can have 50% of the commission calculated upon order, 20% calculated at invoice
value and the final 30% calculated upon payment.
Items listed under Other Factors do not need to total 100%, and each can be over
100%. These items include Takeback, Credit Memo, Deposit, Debit Memo,
Giveback, Manual Transaction, Payment Plan, Payment Plan Recovery, Order
Return, Upgrade, and Write-off.
6.9 Defining Compensation Plans

A compensation plan is built from plan elements. After the plan is assigned an
effective start date and an effective end date, it can be assigned to multiple sales
roles.
In this release of Oracle Incentive Compensation, four pages are used to define
compensation plans. The main page is called Compensation Plan. This page lists all
defined compensation plans. It also contains a Create button to go to another page
to create new compensation plans.
The three other pages are subheadings of Incentive > Plan, and are called General,
Assign Plan Elements, and Sales Roles. The General subheading displays the
Compensation Plan Details page, where you name the compensation plan and enter
basic information for it. The second page, Assigning Plan Elements, is where you

assign the already defined plan elements to the compensation plan. You also can
sequence the elements to run in a particular order. The third page, Sales Roles, is
where the compensation plan is assigned to sales roles. This is presented in Chapter
7, Assigning Compensation Plans.
Prerequisites
Plan elements must be created.
Steps
1. Click the Incentive tab and click the Plan subtab.
The Compensation Plan page appears.
2. To view or change details for an already created compensation plan, click the
plan name in the Name column to go to the Compensation Plan Details page.
3. You can use the search field at the top of the page. Select a saved search from
the drop-down list, or click Personalize to create a new search.
4. To create a new compensation plan, click Create. This takes you to a blank
Compensation Plan Details page.
5. Check the Remove check box to delete a compensation plan.
6. If you are updating an existing compensation plan, you can click Restore to
return to the previously saved information.
6.9.1 Compensation Plan Details

The Compensation Plan Details page is where you can make changes to an
established compensation plan or create a new plan. If you have arrived at this page
by clicking the name of the plan on the Compensation Plan page, some fields will
be filled in already. If you clicked Create, the fields are blank. To create a new
compensation plan, perform the following procedure:
Navigation
Incentive > Plan > Click name link or click Create
Steps
1. In the Name field, assign a unique name to the new compensation plan.

2. Enter an objective description for this plan based on the associated sales role.
The description is used as part of a contract for the salesperson.
3. Assign a start date and end date to the plan. Click the calendar icon to open a
pop-up calendar.
4. Check the Allow Revenue Class Overlap check box if you want your plan
elements to share some revenue classes.
5. If you are updating an existing plan, you can click Restore to return to the
previously saved information.
7. Click Assign Plan Elements to go to the Assigning Plan Elements page.
8. To open the list of compensation plan names for the Name field, enter search
parameters and Click Go. This opens a pop-up list of available plan elements.
Click your selection.
9. Enter a sequence number in the sequence column. This tells the application the
order in which to process the plan elements.
10. You can remove a plan element by checking the Remove check box and clicking
Update.
11. If you are updating an existing compensation plan, you can click Restore to
12. When you are finished, click Update to save the plan element assignment. The
Description, Start Date and End Date fields will populate automatically.
13. Optionally, you can click Details next to any plan element to review the plan
element details.
14. After the plan elements are assigned and saved, click General to return to the
Compensation Plan Details page.
15. Click Validate to ensure that you have entered the plan information correctly. If
everything is correct, the status in the Status field changes from Incomplete to
Complete. See Guidelines.
16. To assign the compensation plan to a sales role, see Chapter 7, Assigning
Compensation Plans.
Guidelines
For easy identification, define plan names by job titles or area of sales you are
compensating.

You can change or restructure any aspect of a compensation plan. Because you can
assign the same plan to many salespeople, however, be aware of how the changes
you are making impact individual salespeople.
When you change a compensation plan, the changes propagate to the salespeople
assigned to the plans. For customized plans, the salesperson receives all changes
except the customized changes.
When you validate a compensation plan, the following are verified:
■ The plan has a name and start and end dates.
■ The plan has one or more plan elements assigned with start and end dates
within the plan start and end dates.
■ Each plan element has a rate table with contiguous tiers and with start and end
dates within the plan start and end dates.
■ Each plan element has at least one revenue class and uplift factors assigned,
with start and end dates within the plan start and end dates.
■ Each plan element has a rate table structure that makes sense for the plan
element type.
■ Each revenue class has at least one key transaction factor and at least one other
transaction factor.
If each of the above conditions is met, then the Status field shows Complete. If the
Status field displays Incomplete, the plan cannot be used to calculate
compensation.
A quota factor enables a salesperson to reach higher levels of quota achievement
more quickly, resulting in higher compensation payments. This is because Oracle
Incentive Compensation uses quota achievement to determine which rate to use.
For example, instead of a payment factor, a quota factor of 200% is put onto the
revenue class of LIC-DB compensation plans for field salespeople to promote sales
of this type of license. The application essentially doubles the amount of quota
credit towards quota achievement. This can move a salesperson up into a higher tier
of a rate table, and therefore a higher amount of compensation.
Guidelines
The payment factor or a quota factor is a percentage expressed as a whole number.
If there is no payment factor or quota factor, calculation defaults to 100%, which
means to multiply the calculated payment amount by 1. A factor of 200% (entered

as 200) means to multiply the commission amount by 200% or a factor of 2 (as in the
above examples).
If you enter a value for a payment or quota factor of less than 100, Oracle Incentive
Compensation reduces the incremental credit to the commission payment amount
for payment factors or the current quota performance level for quota factors.
Payment factors work only when they are used in the calculation output expression
assigned to the formula. For example:
(Rate Table Result*Transaction_Amount)*Payment_Factor
Quota factors work only when they are used by the calculation input expression
assigned to the formula. For example:
(Transaction_Amount*Quota_Factor)/Target
Payment factors can only be used when the Apply Txn Type is set to Individually as
they apply to each individual revenue class. Payment factors have no meaning if the
Apply Txn Type is set to Group by Interval.

7
Assigning Compensation Plans, Pay
Groups, and Payment Plans

■ Section 7.1, "Assigning a Compensation Plan to a Role"
■ Section 7.2, "Assigning a Role to a Resource"
■ Section 7.3, "Customizing a Compensation Plan for a Resource"
■ Section 7.4, "Assigning a Pay Group to a Resource"
■ Section 7.5, "Assigning a Payment Plan to a Resource"
■ Section 7.6, "Regoaling"
7.1 Assigning a Compensation Plan to a Role

A sales role describes a set of salespeople who share a common compensation
structure, for example, marketer, broker, and sales manager. Sales roles are created
in Oracle Resource Manager.
After you have created a compensation plan, you can assign it to multiple sales
roles. A compensation plan must be assigned to a sales role in order for the
resources assigned to the role to receive compensation. Perform either of the
following procedures to assign a sales role to a compensation plan.
There are two ways to connect a compensation plan to a role. You can either assign
the role to the compensation plan on the Incentive tab > Plan subtab, or on the
Resource tab > Resources subtab.
Assigning Compensation Plans, Pay Groups, and Payment Plans 7-1

Assigning a Compensation Plan to a Role
7.1.1 Method 1: Using the Incentive Tab

To assign a compensation plan to a role using the Incentive tab, perform the
Navigation
Incentive > Plan
Prerequisites
Sales roles are defined using Oracle Resource Manager and have the Oracle
Incentive Compensation role type. A valid compensation plan must already be
created.
Super User responsibility is required.
Steps
1. Click the Incentive tab and click the Plan Subtab. Or, alternatively, you can click
the Resource tab and click the Role subtab.
The Compensation Plan page opens.
2. In the Name column, click the compensation plan that you want to assign. Click
Search or use a saved search for quick access to a list of plans.
The Compensation Plan Details page appears.
3. Click Sales Roles to go to the Sales Roles page.
The sales roles already assigned to the compensation plan are listed.
4. Click Go next to the first blank name field to open pop-up list of sales roles.
5. Select a sales role and click it.
6. Enter a start date and an end date for the role. If desired, use the calendar icons
to open pop-up calendars.
7. Enter additional sales roles in the blank rows provided.
8. As you work, you can click the eraser icon at the left to clear information in a
specific row.
9. To delete a sales role, check the Remove check box. The sales role is deleted the
next time Update is clicked.
10. If you are updating a compensation plan assignment, you can click Restore to

Assigning a Compensation Plan to a Role
11. Click Update to save your work. If the sales role has a description, it will be
displayed.
7.1.2 Method 2: Using the Resource Tab

To assign a compensation plan to a role on the Resource tab, perform the following
procedure:
Navigation
Resource > Role
Prerequisites
Sales roles are defined using Oracle Resource Manager and have the Oracle
Incentive Compensation role type. A valid compensation plan must already be
created.
Super User responsibility is required.
Steps
1. On the Role page, click a sales role to view it.
The Assign Compensation Plans page is displayed. Any plans already assigned
are listed.
2. To assign a new compensation plan, enter the name in the Compensation Plan
Name column of the first blank row. You can enter search parameters and click
Go to open a pop-up list.
Only compensation plans with Complete status may be used.
3. Select a start date and an end date to define the effective period for the
compensation plan to be assigned to this sales role. Click the calendar icon to
open a pop-up calendar.
4. If you want to remove a compensation plan, check the Remove check box.
Guidelines
The date range used to assign a compensation plan to a sales role must be within
the start and end dates of the compensation plan itself.

Assigning a Role to a Resource
7.2 Assigning a Role to a Resource

Resources are assigned to Roles in Resource Manager. Refer to appropriate sections
of the Oracle CRM Foundation Implementation Guide (Defining Dynamic Groups) or
Oracle CRM Foundation Concepts and Procedures (Understanding Resource Manager).
Or, Refer to Oracle CRM Application Foundation Implementation Guide (See:
Implementation Tasks for Resource Manager).
7.3 Customizing a Compensation Plan for a Resource

Compensation groups are used to place a resource into a hierarchical relationship
with managers, directors, directs, and other people with whom the resource shares
compensation credit. Compensation Plans are designed to pay each member of the
sales team the agreed upon compensation for each transaction they generate.
Compensation plans are assigned to sales roles, and a resource is then assigned to a
sales role.
It is convenient to have a plan that can be assigned to multiple resources.
Sometimes, however, you want to make changes to the compensation plan for a
specific resource. To customize a compensation plan, perform the following
procedure.
Navigation
Resource > Resources > Compensation Plan
Prerequisites
None
Steps
1. Enter search parameters into the Role Name field at the top of the page and
click Go.
2. Click the sales role you need and click Apply.
The compensation plans and plan elements for the resource and sales role are
displayed.
3. Check the check box in the Customized Flag column next to the plan element
to be customized.
Note: If you leave the Customized check box unchecked for a plan element,
then any changes you make to the quota or rates for that plan element are

Assigning a Pay Group to a Resource
inherited by the salesperson. If you check the check box, that element will not
be affected by any overall changes you make to it.
4. Click the plan element name.
The Plan Element Details page is displayed.
5. Edit the details to customize the plan. See the table under References for a list of
fields that can be changed and where they can be found on the Plan Element
Details page.
7.4 Assigning a Pay Group to a Resource

A pay group defines the frequency of payments, such as monthly or semi-monthly,
for the resources who are assigned to the pay group. To assign a pay group to a
resource, perform the following procedure.
Navigation
Resource > Resources > Pay Group
Prerequisites
The pay group must be defined in Administration > Incentive > Pay Group. A valid
resource has been selected from the Employees page that is generated from an
advanced search request.
Steps
1. In the Name field, enter the name of the pay group to be assigned. You can click
Go to open a pop-up list of values. Click the pay group name to select it.
2. Enter a start date and an end date. Click the calendar icons to open a pop-up
calendar.
4. Click Update to save the pay group assignment.
Guidelines
A salesperson can be assigned multiple pay groups, but only one pay group can be
active at a time.

Assigning a Payment Plan to a Resource
Pay groups can be assigned to multiple resources at the same time and you can start
and end pay group assignments by individual resource at any time within the
duration of the pay group. Therefore, the application does not default any dates in
the Resource Details > Assign Pay Groups table in the Resource tab.
When you assigned a pay group to a resource, the application automatically checks
to see if there are any conflicts between the start and end dates of the pay group and
the start and end dates for every resource to which the pay group has been
assigned. For example, if you define a pay group starting Jan 1 and ending on Mar
31 and you have assigned it to a resource, the application will not let you change the
end date for the pay group assignment beyond Mar 31.
7.5 Assigning a Payment Plan to a Resource

Payment plans are optional and are used to set up advance or deferred payments
and to define minimum and maximum payments.
In this new version of Oracle Incentive Compensation, the recovery schedule and
draw amount can be set up independently of the earnings for the period, and you
can waive a recovery amount due from a salesperson. See Defining Payment Plans
for more information.
To assign a payment plan to a resource, perform the following procedure.
Navigation
Resource > Resources > Payment Plan
Prerequisites
The payment plan must be defined in Administration > Payment Plan.
Steps
1. On the Assign Payment Plans page, review the salesperson’s payment plan
information.
2. To assign a new payment plan, enter it in the Name column of the first blank
row. You can click Go to open a pop-up list. Select the plan from the list and
click it.
3. Enter a start date in the next column. You can click the calendar icon to open a
calendar. Enter the date and it will appear in the Start Date field. This field is
required.
4. Optionally, enter an end date in the End Date column.

Regoaling
5. If you want to pay the salesperson either a minimum or maximum amount

regardless of commissions earned, then enter the amount in the Minimum or
Maximum column.
6. The Recoverable, Pay Later, Recoverable Interval, and Pay Against Commission
fields display read-only information about the payment plan as it was created
in the Administration tab.
7.6 Regoaling
Regoaling enables managers to change the quota or variable pay of a salesperson’s
compensation plan at any time. These changes could be required because of:
■ A change in business circumstances
■ A salesperson is receiving too much commission
■ A salesperson is receiving too little commission
■ A salesperson receives a promotion to a new role with a new goal
Regoaling can only be used if a plan is already accepted and activated.
Regoaling uses new seasonality and workday calendar features to calculate the
exact amount to be paid. Seasonality allows planners to assign different quotas to
each month to accommodate business cycles, and the workday calendar lets
planners count each workday of each month, accounting for holidays and
weekends. Seasonality and workday calendar can only be used on variable
non-computed components, such as Licenses and salary.
For example, a salesperson’s compensation plan has effective dates of January 1 to
December 31. The salesperson can receive a new compensation plan on the 24th of
July and the exact amount of compensation can be calculated for the rest of the year,
based on the quotas assigned to August through December and on the exact
number of work days remaining in July.
Prerequisites
Log in as an Incentive Compensation Super User or Sales Manager responsibility.
The salesperson must be activated. The OSC: Use Work Day Calendar profile must be
set up in Forms. The transaction calendar must be set up in General Ledger and

Regoaling
selected from the drop-down list in Administration > Incentive > Settings.
Seasonality must be set up in Administration > Incentive > Seasonality.
Steps
1. Click the Resource tab. The Resource Search page on the Planning subtab
appears automatically.
2. Use parameters to search for the resource.
3. Click the Resource name on the Resource Search Results page.
4. Click the Adjust Quota button.
5. Click Update.
The Resource Details - Quota Adjustment page appears.
6. Click the button next to an existing role to adjust it, or click the button next to
the blank row to enter information for a new role.
■ If you are regoaling an existing role, enter start and end dates for the new
quota. Be sure to set the end date of an old quota the day before the start of
a new quota.
■ You can end date a role and then assign a new role to a resource. Or, a
resource can keep the same role but move to new group or you can assign
the resource a new role in a new group.
7. Click the link to Quota Allocation Details.
The Allocation Details - Quota and Pay Assignment page appears.
8. Click Prorate.
9. Adjust any prorated amount that you want to manually. This is good for
rounding amounts to even numbers.
When you change the amounts manually, it changes the proration factor, which
changes the On Target Earnings (OTE) as well.
10. After you have made any changes you want to make, click Update to save
them.
11. Click Lock.
12. Click Generate.

The Generate button then becomes the Submit button.

Regoaling
13. Click Submit to submit the plan to the Contract Approver.
14. Click the Single Tier Rate link to go to the Allocation Details - Rate page.
15. Check the Standard Rate button if you want to calculate based on the computed
figures. Click the Effective Rate button if you want to base calculations on
previous achievements.
16. Click Generate Effective Rate.
Approving the Plan

After the plan is submitted to the Contract Approver, it needs to be approved by
someone with the responsibility of Contract Approver or Incentive Compensation
Super User. This is the procedure:
Steps
3. Click the salesperson name link to go to the Contract Approval Page.
4. Select Approve in the drop-down list in the Action column next to contracts you
want to approve. You can also click Approve All to approve all of the submitted
contracts at once.
A manager can distribute a plan by using My Salespeople in Oracle Sales Online.
Resource Accepts the Plan

After the compensation plan has been distributed, the resource must log into Oracle
Sales Online to accept the plan, using the following procedure:
Steps
The plan status is Issued.
2. Click the Rate link to go to the Contract page.
3. Review the contract and click Accept to accept the contract.

Regoaling
The plan status changes to Accepted.

4. Click the Printable button to print out a hard copy.
Activating the Sales Role

To activate the sales role, perform the following procedure:
Prerequisites
Log in as Incentive Compensation Super User responsibility. The compensation
plan must already be accepted by the resource.
Steps
1. Click the Incentive tab and click the Activation subtab.
The Role Activation page appears.
2. Check the Activate check box.
3. Click Update.
4. To activate all plans, click Activate All.
To activate the salesperson, perform the following procedure:
1. Click the Quota tab and click the Activate subtab.
2. Enter parameters in the Salespeople Search page to find the salesperson you
need. The Salespeople Found page appears.
3. Click the name in the Salespeople Name column.
The Compensation Plan Activate page appears.
4. Click the check box in the Activate column.
5. Click Activate.

Part IV
Collection, Calculation, Payment, and
Reports

■ Chapter 8, "Collecting and Adjusting Transactions"
■ Chapter 9, "Calculating Compensation"
■ Chapter 10, "Payment with Payruns"
■ Section 11, "Reports"
8
Collecting and Adjusting Transactions

■ Section 8.1, "Overview of Collecting Transactions"
■ Section 8.2, "Open Collections"
■ Section 8.3, "Standard Collection"
■ Section 8.4, "Submitting a Collection Request"
■ Section 8.5, "Collecting Adjustments"
■ Section 8.6, "Imports and Exports"
■ Section 8.7, "Adjusting Transactions"
■ Section 8.8, "Loading Transactions"
■ Section 8.9, "Using the Transaction Interface"
8.1 Overview of Collecting Transactions

The Collections function of Oracle Incentive Compensation collects the transactions
it needs to calculate commission for your salespeople. It allows the collection of
data from different data sources, such as Oracle Receivables and Oracle Order
Management, based on the configuration and mapping defined between the source
tables and destination tables, which are in CN_COMM_LINES_API.
Collections allows you to collect compensation transactions from the Oracle
Receivables and Oracle Order Management applications out of the box. These
seeded sources are known as Standard Transaction Sources, and they are shipped
with the application. You can read about how to set up mapping to these sources for
your classification needs in section 8.3.
Collecting and Adjusting Transactions 8-1

Overview of Collecting Transactions
You can also create your own Transaction Sources from the database tables of any
legacy application. This is called Open Collections, and is covered in section 8.2.
Data is collected on a periodic basis by submitting a concurrent request. The
concurrent request uses the mapping and rules that are defined to determine what
data to collect and how to collect it. See section 8.4 for steps to submitting a
concurrent request for collection.
A compensation transaction is a record which identifies a compensation event (such
as the sale of an item). It is the smallest unit of data on which a compensation
payment can be calculated. Each transaction comprises several attributes, for
example, the salesperson’s name, the amount of the sale, the sale date, the product
type, and so on. Some of the attributes can be user-defined during Implementation.
The main attributes of a transaction are the:
■ Type of compensation event
■ Order
■ Invoice
■ Payment
■ Takeback - The amount of sales credit that the application takes back from
the salesperson when an invoice due date grace period is exceeded. (Also
known as a clawback).
■ Giveback - The payment received for a takeback.
■ Credit and Debit Memo - Generated when an invoice is fully or partially
reversed and posted to Oracle General Ledger.
■ Manual
■ Writeoff
■ Identity of the person who is directly credited for the event
■ Value of the transaction
A transaction may optionally contain other attributes, such as transaction currency,
product identification, and customer identification.

Open Collections
8.2 Open Collections

Open collections allows you to collect data from any legacy system. For example,
you can use a homegrown Order Management system that is the source of sales
credits that need to be calculated to pay compensation to your sales force.
These are the setups that need to be done to collect data from this system.
1. Identify the header tables and line tables in the legacy system. You need to
define either synonyms or views in the apps schema to point to these tables.
2. Register the tables in Oracle Incentive Compensation using the Administration
> Incentive > Tables page.
3. Define a new transaction source.
4. Identify the source tables from which the transactions are to be built.
5. Define the Notification and Collection Queries.
6. Define Runtime Parameters.
7. Define the mapping from the source system into an API table in Oracle
Incentive Compensation (CN_COMMISSION_LINES). Mapping is the way to
specify how data from the source tables are used to populate the destination
fields in the compensation transaction.
8. Define any optional collection actions, including setting user codes or defining
filters. User codes can be set up at three stages of collection:
■ Pre-notification
■ Post-notification
■ Post-collection.
9. Test generate a collection package (PL/SQL package) and correct errors if any.
10. Review and generate the collection package.
The end result of setting up Collections for a particular Transaction Source is a
PL/SQL package that is stored in the applications database. The Collect procedure
within this package builds compensation transactions from the Transaction Source
and stores them in CN_COMM_LINES_API. The Collect procedure executes the
listing notification and the creation and updating of compensation transactions.

Open Collections
8.2.1 Identifying the Header and Line Tables

When you use a transaction source other than the two standard transaction sources,
you must decide from which source tables you want to collect the transactions. The
source of transaction lines will be the Line table. You can also use a Header table to
collect other information that you need to calculate compensation, such as an
employee number.
8.2.2 Registering the Tables

Use the Tables page to set up the tables that are used in collecting and calculating
transactions in Incentive Compensation. Tables must be defined before they can be
used in collection or calculation. After you register a table, it can be selected from
the drop-down list in the Identifying Source Tables procedure (section 8.2.4). See
Administration > Incentive > Tables in Chapter 12 for information on defining the
columns in those tables.
To register a table, perform the following procedure.
Navigation
Administration > Incentive > Tables
Prerequisites
Tables, views, or synonyms must exist in the database.
Steps
2. Click the Tables link in the side panel menu.
The Tables page appears.
3. If you want, enter search parameters by Schema, Table Name, or User Name.
4. Click Apply.
5. Enter a Schema in the Schema field. Click Go to open a pop-up list from which
to select a name.
6. Enter a Table Name from which you want to collect data. Use the pop-up list if
necessary.
7. Enter a User Name.
8. Enter a description if desired.

Open Collections
9. In the Usage column, select Collection from the drop-down list.

8.2.3 Defining a New Transaction Source

When using open collections, you must tell Oracle Incentive Compensation from
which transaction source you will obtain the data for processing commissions. Use
the Collection - Transaction Sources page to set up.
The table on the Transaction Sources page contains five columns:

■ Transaction Source Name: User-defined and changeable, and may include
legacy sources
■ Type: The short name of the Transaction Source. User-defined, must be unique
and cannot be changed once defined. See Guidelines for restrictions.
■ Status: Complete/Incomplete. This tells you whether the Collection package
has been generated for the Transaction Source since the latest setup changes
were made.
■ Line Table: The primary source table of the Transaction Source
■ Key Column: The unique primary key of the line table
In the Transaction Source area, perform the following procedure to set up a custom
transaction source.

Open Collections
Navigation
Administration > Incentive > Collection > Transaction Sources
Prerequisites
Tables must be set up already in the transaction source.
Steps
1. Click Administration tab and the Incentive subtab.
2. Click the Collection link in the side panel menu.
The Collections - Transaction Sources page appears.
3. Enter the name of the transaction source in the first empty field in the
Transaction Source column.
4. Enter a type, in the same format but not identical to the standard transaction
sources, which are AR (Accounts Receivable) and OC (Oracle Order Capture).
See Guidelines for restrictions.
5. Enter the Line Table name. Click Go to open a pop-up list from which to select a
line table name. Click your selection to enter it into the field.
6. Select a Key Column for the table. Click Go to open a pop-up list.
8. To remove a transaction source, check the remove check box and click Update.
Guidelines
When creating a new transaction source, the Type (for example, the short name of
the transaction source) has the following restrictions:
■ It cannot be empty.
■ It must be unique.
■ It cannot be the same type as any existing seeded transaction source, such as
OC - Order Booking, or AR - Receivables.
■ It cannot be the same as the type of existing receivables events, such as INV,
PMT, CBK, WO, or RAM.

Open Collections
8.2.4 Identifying Source Tables

After the Transaction source has been defined, you need to specify all the tables
which are used during the creation of compensation transactions--the Direct
Mapping tables. The Collection - Source Tables page is used for this purpose. For
the Receivables Posting and Order Booking selections, all the transaction source
data is predefined and cannot be deleted or modified. However, for custom
transaction sources, the Line Table and Key column are required, which were
defined in section 8.2.3 when creating a new transaction source. The Line table
contains the line items against which compensation is to be paid. The Key column is
the field in the table which uniquely identifies each line.
To define source tables for custom transaction sources, perform the following
procedure.
Navigation
Administration > Incentive > Collection > Source Tables
Prerequisites
Tables must be registered in the Tables subtab before they can be used.

Open Collections
Steps
The Collections - Transaction Sources page appears.
3. Click the Source Tables link.
The Collection - Source Tables page appears.
4. Select a transaction source from the drop-down list.
5. Click Apply.
The Type and Status fields populate, and any tables that are already defined for
this transaction source populate in the fields below.
6. Enter information into the Line Table and Header Table areas.
7. Enter any extra direct tables in the Extra Direct Tables area below.
8. Click Update to save your changes. Click Restore to return to the previously
saved information.
Guidelines
Extra direct tables are used to attach additional information to the transactions so
that they can be calculated. This table information should exist for all of the
resources and may indicate Territory, Organization, or some other distinguishing
feature.
If you specify an optional Header table, you must specify a Key column for it and in
the Line Table Header Identifier you must specify the field in the line record which
allows it to be joined to the Key column of the Header table.
8.2.5 Defining Notification and Collection Queries and Runtime Parameters

Use the Queries page to define a custom source from which to collect to Oracle
Incentive Compensation. For standard integration with Oracle Accounts Receivable
and Oracle Order Capture, you cannot edit the query conditions.

Open Collections
The Notification Query shows the exact query which will be used to create the
Notification list of line-level transactions which are eligible for compensation. The
query joins together the mandatory Line table and the optional Header table. The
optional Header table area is provided on the Source Tables page because many
times users want to restrict the collection using an AND clause, which makes the
Header table necessary.
The AND area is the only place where you can make changes; the FROM and
WHERE sections are read-only. They were defined earlier in during source table
definition. The AND area links the tables together and creates the exact conditions
for collecting the transactions needed for complete calculation.

Open Collections
The Parameters subsection of the Notification Query section allows you to narrow
your focus, for example, by start date and end date, if you are using a custom
transaction source. The parameters are registered here on the Queries page during
the collection setup process but the specific values are entered on the Transaction
tab during the collection submission process. This allows you to change the values
of the parameters whenever you need to without having to regenerate the collection
package. For example, if one of the parameters is the name of a month, then each
month you can change it on the Transaction tab while leaving the collection setup
alone.

Open Collections
The Collection Query area lists the exact tables and rows from those tables that you
need to perform a collection. These tables in the FROM clause include the Line
table, the (optional) Header table, and all of the tables listed as Extra Direct Tables
on the Source Tables page. The WHERE clause already contains the necessary join
information to get the right rows from the Line and Header tables. You must
complete the WHERE clause for any Extra Direct tables.
Perform the following procedure to change or enter new parameters.
Navigation
Administration > Incentive > Collection > Queries
Prerequisites
The Queries page is only accessible for nonstandard collection sources.
Steps
The Collection - Transaction Sources page appears.
3. Click the Queries link.
The Collection - Queries page appears.

Open Collections
4. Select the transaction source from the drop-down list.

Click Apply.
5. Enter the name of the parameter in the field.
6. Click Update.
The Type field populates.
7. While entering data, click the eraser icon to clear the field. If you want to return
to the previously stored information, click Restore.
When entering any information in either Query section, click Update to save it or
Restore to return to the previously saved material.
8.2.6 Defining Mapping

Use the Mapping page to specify what data is used to fill each of the destination
columns when a compensation record is collected from the Transaction Source.
Some of the Source Expression and Destination fields are prepopulated with the
mandatory mappings required to perform collection to the CN_COMM_LINES_
API. Some mandatory columns include Employee_Number, Transaction_Amount,

Open Collections
Transaction_Type, and Source_Doc_Type. Some mandatory mappings cannot be

removed but permit you to select the source expression, and some have both the
source expression and the destination column defined and cannot be changed. You
cannot generate a collection package if any of the required mappings contains a
blank source expression field.
The contents of a source expression can be more than just a column name. It can
contain an expression formed from one or more of the following items. An example
for each is shown in parentheses.
■ a null value (NULL)
■ literal value (’My Text’)
■ a column name (booked_date)
■ a table name with a column name (l_order_headers.booked_date)
■ a table alias with a column name (loh10000.booked_date)
■ a SQL function NVL(lol10001.ordered_quantity, 0)
■ a user function my_function(loh10000.booked_date,lsc10002.salesrep_id)
Mapping can be direct or indirect. Direct mapping uses source data from one or
more of the tables in the From clause of the Collection Query. It is part of the
Collection Creation query, so to define a direct mapping you simply type the
appropriate SQL expression into the Source Expression field.
Indirect mapping is more complex, and uses From and Where clauses in an
UPDATE statement. UPDATE statements are run after the main collection process
has completed. Indirect mapping is used under special circumstances, for example,
when you want to collect from a table that affects only some of the resources for
whom you are collecting transactions.

Open Collections
There are two types of indirect mapping, free-form and relationship. With free-form
mapping, you must manually type the exact FROM/WHERE clause in the
FROM/WHERE box in the Indirect Table Details section on the Mapping page. A
relationship indirect mapping requires that you set up a relationship on the External
Table page first and then select it in the Join Relationship field of the Indirect Table
Details section. The relationship type of indirect mapping is more restrictive, in that
you can only define simple equivalence joins (=). Free-form mapping can include
other tests, such as OR, BETWEEN, <, and so on. Relationship indirect mappings
also only allow a join to a single indirect table.
However, the benefits of relationship mapping are that it is simpler to set up, can be
reused in multiple mappings, and is easier to maintain.
To map data on the Mapping page, perform the following procedure.
Navigation
Administration > Incentive > Collection > Mapping
Prerequisites
Tables must exist in the transaction Source and the destination. For relationship
indirect mapping, a Join relationship must be set on the External Tables page of the
Administration tab for any tables you plan to use.
Steps

Open Collections

3. Click the Mapping link.
The Collection - Mapping page appears.
4. Enter a source expression in the Source Expression field.
5. Enter a destination. Click Go to open a pop-up list. In the Select box, enter
search parameters and click Go. Select from the list. See Guidelines.
6. If you want to perform indirect mapping, after you have set up the source
expression and destination, click Indirect to open the Indirect Mapping Details
area at the bottom of the page.
7. For a relationship mapping, enter a join relationship or click Go and select one
from the pop-up list.
You must have set up the join relationship in advance.
8. For a freeform mapping, enter the From/Where clause.
9. Click Update.
The Update field and sequence field populate automatically.
Guidelines
The API table in Oracle Incentive Compensation contains 100 seeded attributes that
you can use for direct or indirect mapping, for example, Attribute 1, Attribute
2...Attribute 99.
In the inherited column, if === is displayed, the mapping is standard. If it has been
changed, the display will look like this: =x=. Click Inherit to restore the original
standard setup.
8.2.7 Defining Pre-Notification, Post-Notification, and Post-Collection Actions

The Actions page allows you to change the Collection processing for the transaction
source in two ways--the addition of user code blocks and the specification of
transaction filters (For Filters see Section 8.2.8, "Defining Filters").

Open Collections
User code blocks are single or multiple PL/SQL statements that you can insert at
defined points in the Collect procedure. User code blocks can be inserted at three
locations:
■ Pre-Notification: at the beginning of the Notification query
■ Post-Notification: between running the Notification and Collection queries
■ Post-Collection: after the Collection query has been run
To create a User Code Block, perform the following procedure.
Navigation
Administration > Incentive > Collection > Actions
Prerequisites

Open Collections
Steps
3. Click the Actions link.
The Collection - Actions page appears.
4. Select a location for the user code block from the Location drop-down list.
5. Enter the code in the Code field.
The code can run up to approximately 2,000 characters.
8.2.8 Defining Filters

Transaction filters are especially relevant to Receivables and Order Management,
because you cannot change the collection query for those standard transaction
sources. In fact, you cannot access the Queries page for a standard transaction
source at all. Filters allow you to define criteria to remove unwanted transactions.
For example if you want to filter out any transaction under $100, you enter this text
on a line in the Filters section:
api.transaction_amount < 100
There are two methods of filtering from which to select:
■ Mark as Filtered: transaction will appear in CN_COMM_LINES_API but be
marked as filtered.
■ Physically Delete: transaction will be deleted from CN_COMM_LINES_API.
Deleting the transactions helps keep the table at a more efficient size, so it is the
recommended option.
To create a filter, perform the following procedure:
Navigation
Administration > Incentive > Collection > Actions

Open Collections
Prerequisites
Steps
3. Click the Actions link.
4. Select the method of filtering by clicking a radio button.
5. Enter the text of the action you want in the Filters area of the page.
8.2.9 Generate and Test Generate

After the setup is complete, use this page to generate a collections package. The
page contains two sections, Summary and Details.

Open Collections
The information about each transaction source in the Summary section of the
Generate page is as follows.
■ Transaction Source: The name of the transaction source
■ Type: The short name of the transaction source
■ Status: Complete / Incomplete. This tells you whether or not the Collection
package has been generated for the Transaction Source since the latest setup
changes were made.
■ Receivable Event: Events of the Oracle Receivables. This column is only
relevant to the Receivables Posting transaction source.
■ Collect Flag: This flag indicates whether or not to generate the package for the
corresponding Receivable Events. For a non-Receivable Transaction Source, the
value is always YES.

Open Collections
■ Test Package Name: This is the test version of the package. To distinguish it
from the actual package, the package name of the test version always ends with
"_t"
■ Test Status: This field shows if there is an error in the test package. Click the
Error link to see the error message in the Details Section.
The Details section in the lower part of the page lists the detailed test result of the
selected transaction source, including Transaction Source, Test Package Name, Error
Text, and Package Text. It also contains two buttons--Test Generate and Generate.
A generated package replaces the existing version of the package, so in order to be
sure it is correct, you can create a test version of the package by clicking Test
Generate in the Details section for the transaction source you want to collect.
The Details section displays the lines where the errors are so you can fix them.
Mistakes are often due to invalid SQL that has been entered on the Queries or
Mapping pages or in a User Code Block.
The Package Text section of the Details area lets you review the entire generated
package to be sure it is working the way you intended it to work. If everything
looks fine, you can click Generate to finish the job.
Navigation
Administration > Incentive > Collection > Generate
Prerequisites
Collections setup must be complete.
Steps
3. Click the Generate link.
The Collection - Generate page appears.
4. In the Summary area, click the button in the Select column next to the
transaction source for which you want to run a test generation.
5. Click Test Generate.
A test version is generated.

Standard Collection
6. If Error appears in the Test Status column, click it to open the details area below
the Summary area.
The Error Text and entire Package text are displayed.
7. Fix the errors and rerun the test generation until you are satisfied with the
result.
8. You can click Yes or No in the Collect Flag to return to the Transaction Sources
page and verify it or change it.
Click Generate to generate the actual Collection package.
8.3 Standard Collection

As mentioned in section 8.1, Oracle Incentive Compensation is delivered with two
predefined transaction sources which allow the collection of data from Oracle
Receivables and Oracle Order Management. Collection from these two seeded
transaction sources is known as Standard Collection.
Standard Collection uses the same concepts as explained in Section 8.2, Open
Collections. However, for ease of use, some of the setups are shipped with the
product. These setups, source tables and queries, cannot be modified for Order
Management or Oracle Receivables.
Use the Collection - Transaction Sources page to determine which Receivables
events you want to generate transactions. The two standard transaction sources are
already built into the table as Receivables Posting and Order Booking.
As a convenience, Oracle Incentive Compensation groups five separate transaction
sources into the Receivables Posting transaction source. In the Receivables Event
area you can select which receivables events you want to be collected. By excluding
transactions that you do not need, you can save time in the collection process. The
default value for each event is No.
To set these events to collect data, perform the following:
1. Check the check box in the Collect Column next to the event for which you
want to collect.
2. Click Update to save your change. If necessary, click Restore to return to the

Standard Collection
8.3.1 How Direct and Indirect Mapping can Be Modified

Both of the standard transaction sources are delivered with a set of mappings to
populate the important columns in CN_COMM_LINES_API. You are allowed to
change source values for these mappings and also to create new mappings of your
own. See: Section 8.2.6, "Defining Mapping".
In the partial view of the Mapping page below, note the Inherited column on the
right side. When you first display the Mapping page for a standard transaction
source, this column displays === for every mapping. This tells you that the
mapping is a standard one and has not been changed. If you change the value in
either the source, relationship, or FROM/WHERE field for a standard mapping, the
Inherited column changes to display =x=, as seen in the third row in the example
below. If you want to revert a mapping to its original standard setup, click the
Inherit button. The Source Expression, Relationship and FROM/WHERE fields
change back to their original values and the Inherited field reverts to ===. If you
create any new mappings, the Inherited column is blank for these rows and the
Inherit button has no effect.
8.3.2 Special Features
Oracle Receivables
The predefined Receivables data source is slightly different from any other data
source because it really represents five transaction sources which have been

Standard Collection
combined into one, so that they can share a set of mappings. The five sources are
referred to as Receivables Events and are as follows:
■ Invoices, Credit Memos, and Debit Memos
■ Take-backs (once an invoice due date goes beyond the set grace period, the
credit for the sale is deducted from the resource’s sales credit)
■ Payments and Givebacks (a giveback is a past due invoice that had been taken
back but has now been paid)
■ Writeoffs
■ Revenue Adjustment Posting
These events occur when the relevant transaction is posted to the Oracle General
Ledger application.
The transaction collection queries for these events are all based around the same
core set of Receivables source tables, but the tables are joined together in different
ways so five different transactions sources would normally be required. The five
have been combined into a single transaction source so that you only set up the
mappings that you want once and they are applied to the collection of
compensation transactions for all five events.
When you click the Generate button for the Receivables transaction source, five
packages are generated--one for each of the Receivables events. This generation
takes five times as long as for any other transaction source. However, you may not
be interest in all of those events. You can restrict the generation to only those
packages for the events that you require. Use the Collection - Transaction Source
page (Administration > Incentive > Collection) to select for which Receivables
events you want to generate transactions.

Standard Collection
Use this table at the bottom of the Collection - Transaction Source page to select the
events in which you are interested. In the above screen shot, only Invoice, Credit
Memo Posting is selected. When the Generate button is clicked, the full package
will be generated for the collection of invoices, credit memos, and debit memos. For
the other four events (Writeoffs, and so on), simple stub packages will be generated,
which speeds up the Generation process.
Each Receivables event has a dedicated concurrent program. Each of these requires
two parameters: a Start Period and End Period. The parameter entry is supported
by a list of values. The concurrent programs are:
■ Collect Invoices
■ Collect Clawbacks
■ Collect Payments and Givebacks
■ Collect Writeoffs
■ Collect Revenue Adjustments
Oracle Order Management

Compared with Receivables, the Order Management transaction source behaves
more like the user-defined transaction sources that were defined earlier.
There is a single collection package which is called by a dedicated concurrent
program--Collect Orders. The concurrent program requires two parameters: Start
Period and End Period. The parameter entry is supported by a list of values.

Standard Collection
Order information can be, and often is, changed after the order has been set to the
status of Booked. Such changes, known as adjustments, can be automatically
applied to transactions which have already been collected. If a change is made to
any line on an order, then all of the sales credits (compensation transactions) for that
line are considered to be changed.
There are two possible scenarios:
1. The compensation transactions have been collected but have not been loaded
into Oracle Incentive Compensation.
2. The compensation transactions have been collected and also loaded into Oracle
In scenario 1, the transactions have only got as far as the CN_COMM_LINES_API
table. In this case the original transactions are marked OBSOLETE and they will be
re-collected into CN_COMM_LINES_API with their new values the next time
Collect Orders is run.
In scenario 2, the transactions are already loaded into the application in CN_
COMMISSION_HEADERS and may already have been used to calculate
commission for a resource. This requires a different approach. The original
transactions in CN_COMMISSION_HEADERS are marked FROZEN. For each of
these a reversing transaction is also created in CN_COMM_LINES_API. This is a
duplicate of the FROZEN line, but with an opposite polarity (usually meaning it
becomes negative) on the transaction amount. This transaction has the effect of
reversing out the original. Finally, as in scenario 1, the compensation transactions
for this line will be re-collected into CN_COMM_LINES_API with their new values
the next time Collect Orders is run.
Each time Collect Orders is run, the list of unprocessed updated Order Lines must
first be processed. This can take a long time. To avoid this, when running Collect
Orders it is a good idea to process this list of updated order lines at regular
intervals, perhaps daily. Use the Order Update Notification concurrent program to
do this.
The list of updates to Orders is maintained for Oracle Incentive Compensation by
the Order Capture application. This, however, only occurs if Order Capture has
been informed of this requirement. Order Capture just acts as an interface here. The
transactions actually originate in Oracle Order Management.
You must register Oracle Incentive Compensation with Order Capture in the Forms
instance as follows:
1. Switch responsibility to Oracle Order Capture.

Submitting a Collection Request
2. Open the Lookups form.

3. Display the ASO_ORDER_FEEDBACK_CRM_APPS lookup type.
4. If it is not already there, create a row with code CN, meaning Incentive
Compensation, and check the Enabled check box. Save this row.
8.4 Submitting a Collection Request

After performing all of the setups on Administration > Incentive > Collect, you
actually run the package to collect transactions that you created in the Collection -
Generate page. Collection Submission has three parts, represented by three pages:
■ Runtime Parameter
■ Submit Request
■ View Request Status and Logs
8.4.1 Runtime Parameters

Runtime parameters are used to narrow the range of transactions collected in a
collection package if you are using a custom transaction source. For example, a start
date and end date can be defined. The parameters are defined on the Queries page
in the setup process. These values are not provided during the collection setup, but
are instead entered during the collection submission process. This allows you to
change the values without regenerating the collection package.
Navigation
Transaction > Collect > Collection Submission - Runtime Parameter
Prerequisites
Parameters must already be created in the Collection setup process.
Steps
1. Select the parameter you want to change.
2. Enter a value in the Runtime Parameters field.

8.4.2 Submit a Request

To submit a transaction collection request, perform the following procedure.
Navigation
Transaction > Collect > Submit Request
Prerequisites
The collection setup must be completed and the collection package must have been
generated successfully.
Steps
1. Click the Transaction tab. The Collect subtab page opens automatically. Click
the Submit Request link. The Collection Submission - Submit Request page
appears.
2. In the Collection Type field, select a collection type from the drop-down list.
The collection types include:
■ Collect Clawbacks
■ Collect Custom Transaction Source
■ Collect Invoices
■ Collect Orders
■ Collect Payments and Givebacks
■ Collect Revenue Adjustments
■ Collect Writeoffs
3. Click Apply.
Note: If you select Collect Custom Transaction Source, the parameter changes to
Transaction Source. Specify the custom transaction source on which you want to
run collection and skip to step 5.
4. Select Start Period and End Period from the drop-down lists.
5. Click Submit Request.
A confirmation window appears.
6. Click OK to submit the request. Click Cancel to return to the current page.

If you clicked OK, the requested data is displayed below the search parameter
fields.
7. Click Refresh Data periodically to monitor the progress of the collection
submission.
Guidelines
The Collect Orders collection type collects data from Oracle Order Management.
The Collect Custom Transaction Sources collection type collects data from external
sources. The other events collect data from Oracle Receivables.
The Process Log page shows the details of the processing of a request.
8.4.3 Viewing the Request Status and Logs

Data must be collected from the mapped tables into Oracle Incentive Compensation
before calculation for payment can occur. Use this procedure to view the status of
the collection submission.
Navigation
Transaction > Collect > View Request Status
Prerequisites
None.
Steps
1. Click the Transaction tab. In the Collect subtab the Collection Submission - View
Request page appears automatically.
2. Select the type of collection event you want from the Collection Type
drop-down list. The list includes:
■ All
■ Clawbacks
■ Custom Transaction Source
■ Invoices
■ Orders
■ Payments and Givebacks
■ Revenue Adjustments

■ Writeoffs
3. Select one of five options from the Phase drop-down list:
■ All
■ Completed
■ Inactive
■ Pending
■ Running
4. Select one of 18 statuses in the Status drop-down list.
■ All
■ @@Normal
■ @Normal
■ @Waiting
■ Cancelled
■ Disabled
■ Error
■ No Manager
■ Normal
■ On Hold
■ Paused
■ Resuming
■ Scheduled
■ Standby
■ Suspended
■ Terminated
■ Terminating
■ Waiting
■ Warning
5. Optionally, enter a search string in the Request ID field.

Collecting Adjustments
6. Click Apply to view a list of collection submissions.

7. Click View Log in the Log column to go to the Process Log.
8.5 Collecting Adjustments
8.5.1 Collecting Adjustments for Order Transactions

Order information can be, and often is, changed after the Order has been set to the
status of Booked. Such changes, known as adjustments, can be automatically
applied to transactions, which have already been collected. If a change is made to
any Line on an Order then all of the Sales Credits (Compensation Transactions) for
that line are considered to be changed. See Section 8.3.2, "Special Features" for a
complete explanation.
8.5.2 Collecting Adjustments for Custom Transaction Sources

You can cope with adjustments to transactions in your custom Transaction Sources
in the same way as standard Collections from Order Capture does. All you need to
do is to call a Collections API, identifying the transaction that has been changed.
If you specified a Header Table on your Source Tables tab then you need to pass the
unique identifiers of both the Header record and the Line record of the changed
transaction. Otherwise only the identifier of the Line record is required.
Suppose that Collections has already been run for October 2001 transactions in our
example legacy system. We have also imported those transactions into OIC. Now a
change is made to one of the orders for that month. The ID of the Order Header is
1001 and the ID of the Order Line is 1234. To notify OIC of this change you make
the following call:
CN_NOTIFICATION_PUB.Create_Notification
( p_api_version => 1.0,
x_return_status => l_return_status, -- OUT parameter
x_msg_count => l_msg_count, -- OUT parameter
x_msg_data => l_msg_data, -- OUT parameter
p_line_id => 1234, -- Line Table Id
p_source_doc_type => ’LEG’, -- Transaction Source Type
p_adjusted_flag => ’Y’, -- Adjustment(not new record)
p_header_id => 1001, -- Header Table Identifier
p_org_id => your_org_id, -- Operating Unit (optional)
x_loading_status => l_loading_status -- OUT parameter
);

The next time Collections is run for this Transaction Source, reversing transactions
will be created to nullify all of the sales credits associated with this transaction line.
All of the sales credits will then be collected again with the new values in. This
reversal and re-collection of the October transaction will occur even if you specify
that you want to collect only November transactions this time.
Note: to understand the p_org_id parameter, you need to first understand the
Oracle Applications ’Multi-org’ strategy, which allows data for multiple operating
units to exist, partitioned from each other, within a single database. Discussion of
Multi-org is beyond the scope of this document. If you don’t understand this
concept then please consult the appropriate documentation before trying to
understand the rest of this paragraph. If your procedure which calls CN_
NOTIFICATION_PUB.Create_Notification is running in a database session where
the Org-Id has been set, and your procedure is only dealing with transactions for
this Org-Id, then you can omit the p_org_id parameter. In any other situation (for
example where you have a single procedure or database trigger which detects
updates to transactions from multiple Org-Ids) you must specify the correct value of
p_org_id for the transaction when you call Create_Notification.
8.5.3 Collecting Adjustments for AR - RAM

An enhancement to Oracle Incentive Compensation for this release enables revenue
adjustments to be collected. This new feature allows you to make transaction
adjustments one time, in Oracle Receivables using RAM (Revenue Adjustment
Module), and collect the adjustments into Oracle Incentive Compensation. This
eliminates the need to make corresponding manual adjustments in Oracle Incentive
Compensation to reflect the RAM adjustments.
A new receivables event, Revenue Adjustment Posting. has been introduced. Like
the other four existing receivables events, to collect the revenue adjustment, you
need to enable this new event during the collection setup process, generate the
collection package, and submit the concurrent request Collect Revenue Adjustments
to collect the adjustments.
Submit the Collect Invoice concurrent request to collect your invoice transactions
from Oracle Receivables. After collecting the invoice transactions, you can
subsequently run Collect Revenue Adjustments on a regular basis to collect any
adjustments that has been made on the transactions since the last collection. Oracle
Incentive Compensation compares the time of the adjustments with the time of last
run of collection and determine which adjustments should be included.
During the process of Revenue Adjustments Collection, you can control whether the
manual adjustments that have been made on the Oracle Incentive Compensation

side should be negated or not. To do so, use the profile OSC: Negate During
Revenue Adjustments Collection. There are two possible values for the profile as
follows:
■ Yes: Revenue Adjustments Collection will negate the corresponding
transactions that have been collected before and then re-collect them from
Oracle Receivables with the new RAM adjustments. Any manual adjustment
that has been done in Oracle Incentive Compensation against the original
collected transactions will be negated. This option ensures the data integrity
from Oracle Receivables; however, you lose the manual adjustments made in
Oracle Incentive Compensation side if any.
■ No: Revenue Adjustments Collection will not negate any corresponding
transactions that have been collected before. Only the new RAM adjustment
transactions will be collected. This option preserves your manual adjustments,
which have been done on the collected transactions, but it may result in the loss
of the data integrity. In certain cases, the data in Oracle Incentive Compensation
may need to be manually synchronized with the data in Oracle Receivables
Navigation
To set up and generate the package:
Administration > Incentive > Collection
To submit the concurrent request:
Transaction > Collect > Submit Request > Collect Revenue Adjustments
Prerequisites
■ The collection setup must be completed and the collection package for Revenue
Adjustment Posting event must have been generated successfully.
■ The invoice transactions have been collected into Oracle Incentive
Compensation.
■ The adjustments have been done in Revenue Adjustment Module in Oracle
Receivables (Receivables Responsibility > Control > Accounting > Revenue
Accounting).
Steps
1. Click the Transaction tab.
The Collection subtab page opens automatically.

Imports and Exports
2. Click the Submit Request link.

The Collection Submission - Submit Request page appears.
3. In Collection Type field, select ’Collect Revenue Adjustments’ from the drop
down list
4. Click Apply
5. Select a Start Period and End Period from the drop-down lis.t
These parameters provided here indicate the period during which the RAM
adjustments were made, not the period that the transaction’s processed date
belongs to.
A confirmation window appears.
7. Click OK to submit the request. Click Cancel to return to the current page.
8. Click Refresh Data periodically to monitor the progress of the submission.
8.6 Imports and Exports

You can import a batch of transactions rather than importing them one at a time.
Create an Import transaction on the Imports Definition page.
The importing process begins with the Import Definition page, which is Step 1 of
the Imports Wizard. It walks you through the process of importing transactions. The
process continues on to Step 2: Import Header Mapping, Step 3: Review, and
Confirmation pages. Required fields are marked with an asterisk (*).
Note: The profile option of OSC: Import Control File Directory must be set to $CN_
TOP/bin. Be sure that the $CN_TOP/bin exists on the Concurrent Manager tier and
that write privileges are enabled.
8.6.1 Defining Imports
Navigation
Transaction > Import/Export
Prerequisites
The source file must have data delimited in one of the formats recognized by the
Transaction API (comma, double quote, single quote, semicolon, space, or tab).

Imports and Exports
A transaction must already exist.
Steps
1. Click the Transactions tab and click the Import/Export subtab.
The Imports Definition page appears.
2. Enter an import type. Select from Transaction API, Hierarchy, Expressions,
Rules, or Revenue Classes.
3. Enter a name for the import process. The Name field is required and must be
unique.
4. Optionally, enter a description in the Description field.
5. Click the Client or Server button to define your data source. If your source data
file location is from a Client, click Go to open a pop-up box and select the file
name from the list.
6. Select the column delimiter from the drop-down list (see Prerequisites for
complete list). Comma is the default.
7. Select how you want your fields to be enclosed from the drop-down list. Double
Quotation is the default.
8. Check the File Header Exists check box if there is a header on the source file.
Mapping begins at the first column, so it is important to specify if your source
file has a header.
9. Click Next to proceed to Step 2 Import Header Mapping.
Guidelines
Note: If the source file is created using Excel and saved with a .csv file extension,
the data will automatically be delimited with commas by Excel. If you want to
update the source file and remove any rows, select the row(s) and use Edit > Clear >
All to remove the data. This will clear the data and the delimiters. Manually
deleting each cell will not clear the delimiters. Failure to do so may cause the import
to fail. This issue may also arise when using other spreadsheet applications.
The table below shows an acceptable format for transaction data. It is a very brief
example of data that would work for a transaction API format.
Revenue Processed Transaction

Name Type Date Amount Item ID State
Randy Roth Revenue 31-Mar-01 250 AS72111 CA

Imports and Exports
Revenue Processed Transaction

Name Type Date Amount Item ID State
Suzanne Chalmers Revenue 31-Mar-01 250 AS72111 WA
Azid Hakim Revenue 31-Mar-01 250 AS72111 OR
8.6.2 Mapping Source Fields to Target Fields

This page is Step 2 of the Imports Wizard. It is used to map source fields to target
fields in the application. The process then continues on to Step 3: Review, and
Confirmation pages. Required fields are marked with an asterisk (*).
You can map source fields to target fields for each import or you can load an
existing mapping that you created previously. Using an existing mapping
eliminates reentering information, which saves time and prevents entry errors. To
use an existing mapping or to create a new mapping see the following steps.
Prerequisites
Source fields must be defined in the file to be imported.
Steps
1. Optionally, use the fields at the top of the page to load an existing mapping or
save a new mapping.
a. To load an existing mapping, enter four or more characters, including the
percent sign wild card (%) and click Go.
A Select box appears, listing all available previously defined mappings.
b. Click the name of the mapping you want to use.
The mapping appears in the areas below.
c. To save a new mapping, after you have defined it, enter a unique name in
the Save New Mapping field and click Next.
The Import process moves to step 3.
2. To create a new mapping, click a source field in the first column to highlight it.
3. Click the target field in the second column. Target fields marked with an
asterisk (*) are required.
4. Click the right arrow button to move the mapping to the third column.
5. View the Preview window to see what your mapping looks like.

Imports and Exports
6. Click Next to save and move to Step 3: Review.
8.6.3 Reviewing Your Mapping

Review is Step 3 of the Imports Wizard. It is used to review your mapping of source
fields in a file to target fields in Oracle Incentive Compensation. The process then
continues on to the Confirmation page. Required fields are marked with an asterisk
(*).
Prerequisites
Source to target mapping must already be done.
Steps
1. Review the general information and mapping on the page.
2. If all the information is correct, click Import. The Confirmation page appears.
3. If the information is not correct, click Cancel, and then return to the Import
Header Mapping page to make corrections.
8.6.4 Confirming your Mapping

The Confirmation page is Step 4 of the Imports Wizard. It confirms that your
mapping of source fields in a file to target fields in Oracle Incentive Compensation
has been submitted for processing.
Prerequisites
None.
Steps
1. Click Finish to go to the Imports Search page. You can check there to see if your
import was successful.
2. If you want to perform another import, click New Import.
8.6.5 Import Details and Results

This page displays details of transactions that have been imported, including User
Input Data File Names Server Side Data File Names, and an Import ID number. This
information is useful for tracking the history of previous imports and for finding
the location of the original Excel spreadsheet.

Adjusting Transactions
8.6.6 Process Log

This page enables viewing of the Process Log in four ways:
■ Brief
■ Debugs only
■ Errors only
■ Milestones only
8.6.7 Failed Records

Sometimes records fail during the import process. This occurs because the content
or the organization of the record is incorrect. The Failed Records page displays any
records that failed during the import process. The reasons for failure are shown at
the end of each record.
To correct failed records and reimport them, perform the following procedure:
Prerequisites
None.
Steps
1. Click the Download to CSV File image icon to download the records to a .csv
file.
2. Correct the data in the new .csv file.
3. Create a new import using the corrected .csv file to load the data into the
application.
Guidelines
Correcting failed records individually is much more efficient than reimporting an
entire file. That is because reimporting creates an entire new set of records in the
database in addition to the old set.
8.7 Adjusting Transactions

Use the Transactions page to review transactions and prepare to load them for
calculation. Also, if a collected transaction contains errors in information or credit

assignment, then it can be corrected on this page. To make preparations or

corrections, perform the following procedure.
Navigation
Transaction > Adjust
Prerequisites
Incentive Compensation Super User or Incentive Compensation Commission
Analyst responsibility is required.
The application has collected the transaction.
Steps
1. Click the Transaction tab and the Adjust subtab. The Transactions page appears.
2. In the Basic Search area, enter information in the fields as needed to find the
transaction you need. Search parameters include:
■ Resource Name: Enter all or part of the name and click Go to open a
pop-up list. Select from the list.
■ Resource Number: Enter the number.
■ Processed Date From: Click the calendar icon to open a pop-up calendar.
■ Processed Date To: Click the calendar icon to open a pop-up calendar.
■ Invoice Number: Enter the invoice number if it is available.
■ Order Number: Enter the order number if it is available.
■ Calculation Status: Select All (the default) or one of five other choices from
the drop-down list.
3. Click Apply.
A list of transaction records appears.
4. At the top or the bottom of the page, click the appropriate button for the type of
action you want to perform:
■ New Transaction
Click this button to go the Create New Transaction page, where you can
create a new manual transaction.
■ Load Transaction

Click this button to go to the Load Transactions - Submit Request page.

■ Move Credits
Click this button to go to the Move Credits page, where you can move
credit from the existing credited salesperson to a salesperson you specify.
■ Deal Split
Click this button to go to the Deal Split page, where you can split the sales
credit for an entire deal, which may include more than one transaction.
Note: This button appears only when you query a specific transaction.
5. To adjust or split an individual transaction, click Adjust or Split in the Action
column next to the transaction you want to adjust.
6. If you click Adjust, the Transaction Details - Adjust page opens. If you click
Split, the Transaction Details - Split page opens.
7. Perform the steps you need on the appropriate page.
Guidelines
You cannot split a nonrevenue, obsolete, frozen, or reversal transaction.
8.7.1 Create New Transaction

If any salesperson needs manual sales credit line adjustments, you can create a
manual transaction for the effective date. To enter new transactions, perform the
Navigation
Transaction > Adjust > New Transaction
Prerequisites
None
Steps
1. Enter the Resource Name and Resource Number. These are required fields. You
can enter some or all of the name and click Go to open a pop-up list.
Select the resource from the list and the fields on the page populate.
2. Enter a Processed Date. Click the calendar icon to open a pop-up calendar. This
is a required field.

3. Enter a Revenue Type from the drop-down list.

4. Enter Transaction Amount. This is a required field.
5. Optionally, enter the other fields that follow, as available.
6. At the bottom of the page, enter a Reason. A drop-down list is available.
7. Enter comments, if any.
9. Click Update to save the transaction.
Guidelines
All adjustments made with the above process must be loaded before they are
available for calculation.
8.7.2 Move Credits

Move Credits gives you the ability to mass adjust a group of transactions based on
criteria selected in the parameters. Use the Move Credits function when the sales
credit for a number of transactions has been erroneously assigned to the wrong
salesperson.
Navigation
Prerequisites
None
Steps
1. In the Receiving Resource Name area, enter the Resource Name and Resource
Number. Click Go to open a pop-up list.
2. Enter a Customer Name and Customer Number, if available.
3. Enter your comments, if any.
4. If necessary, click Restore to return to the previously saved information
6. In the Attribute Columns area, enter any information that identifies your
transaction.


Guidelines
The feature maintains the history of the original transaction or transactions while
displaying the corrected transactions.
8.7.3 Deal Split

Use this page to divide up the sales credit on an entire deal. You must query a
specific transaction by order number or invoice number to expose the Deal Split
button on the Transactions page. Click the Deal Split button to open the Deal Split
page.
Navigation
Prerequisites
None
Steps
1. In the Revenue Type column, select Revenue or Non Revenue from the
drop-down list.
2. In the Resource Name field, enter a resource name. Click Go to open a pop-up
Select page to search through existing resources.
The resource number populates automatically.
3. Alternatively, enter a resource number in the Resource Number field. Click Go
to open a pop-up Select page to search through existing resource numbers.
The Resource name populates automatically.
4. Repeat steps 1 through 3 for each resource.
5. In the split field, enter a percentage for each resource. The numbers should add
up to 100 percent.

6. Click Update to save. If you are making changes to an existing deal split, you
can click Restore to return to the previously saved information.
Guidelines
Deal split is used only for order and invoice type transactions. You cannot perform
a deal split for a manual type transaction with the order number or invoice number.
You cannot have only nonrevenue types in a deal split if the original transactions
are of revenue type. A deal split with only nonrevenue types is possible only if the
original transactions are of nonrevenue type.
All revenue transactions in a deal split must add up to 100%.
8.7.4 Split Transaction

Use the Split Transaction page to distribute sales credit in whole or in part between
one salesperson to another or among a group of salespeople. To split transactions,
perform the following procedure.
Navigation
Prerequisites
Transaction must already exist
Steps
1. In the Revenue Type column, select Revenue or Non Revenue from the drop-
down list.
2. In the Resource Name column, enter the name of resource with whom you want
to split the credit. Click Go to open a pop-up list.
3. You can use the Resource Number if necessary. The Resource Number column
populates automatically if you select a resource name.
4. Enter the percentage or amount of sales credit each person is to receive in either
the Split % or Split Amount column.
5. Enter User Comments if you wish.
7. Click Update to save your work

Loading Transactions
Guidelines
The sales credit for split revenue transactions must equal 100%. If the original
salesperson is still eligible for sales credit he or she must be specified as a credit
receiver. Nonrevenue sales credit does not have the 100% constraint of revenue
credit.
8.8 Loading Transactions

After transactions are collected and adjusted, they must be loaded into Oracle
Incentive Compensation tables for calculation and payment. To load transactions,
Navigation
Transaction > Load > Submit Request
Prerequisites
Transactions must be collected.
Steps
1. Click Transactions tab and Load subtab. The Load Transactions - Submit
Request page appears.
1. In the Parameters area, enter Load Date From and To in the first two fields.
Click the calendar icon to open a pop-up calendar. These are required fields.
2. Enter a Resource Name in the next field. Click Go to open a pop-up list.
3. Optionally, enter the Resource Number.
4. Select a Load Method from the drop-down list.
5. Check the Perform Classification and Rollup check box if you want the
transactions to be processed and move up the compensation hierarchy.
7. Click Refresh Data to display updated information as the concurrent
processing proceeds.

Using the Transaction Interface
8.8.1 Viewing Transaction Requests

To view requests you have already loaded, perform the following procedure:
Prerequisites
Transactions must be collected.
Steps
1. Enter parameters to narrow your search.
■ To select a Submission Date, click the calendar icon to open a pop-up
calendar.
■ Use the drop-down list to select a Phase. All is the default.
■ Use the drop-down list to select a Status. There are 19 choices, but All is the
default.
■ Search by Request ID number if you have the number available.
2. Click View Log in the Log column to display the Process Log.
8.9 Using the Transaction Interface

Oracle Incentive Compensation supports use of a transaction interface to bring
compensation transactions into the system. To process incentives, Oracle Incentive
Compensation uses the CN_COMM_LINES_API table as a transaction interface for
the following:
■ Standard collection of sales credit transactions using out-of-box integration with
Oracle Receivables (for Invoices/Credit Memos/Payments and so on) and
Oracle Order Management (for Booked Orders).
■ Collection from custom sources of data using the standard collection feature.
■ Uploading transactions directly into the CN_COMM_LINES_API table using
SQL*LOADER, SQL, PL/SQL routines, and so on, for processing Incentives.
■ Importing data from a spreadsheet (see Section 8.6.1, "Defining Imports" and
following pages).
The table below provides a detailed description of key attributes of the CN_
COMM_LINES_API table. See the Oracle Incentive Compensation 11.5.6 TRM for more
detailed information on each column.

Column Data Type Description

COMM_LINES_API_ID NUMBER(15) This is the unique
identifier of the table and
must be populated with
a value. If using the SQL*
LOADER then use the
the sequenceCN_
COMM_LINES_API_
S.next val.
PROCESSED_DATE DATE The date the transaction
needs to be processed for
commission calculation.
This is a mandatory
column.
TRANSACTION_ NUMBER The transaction amount
AMOUNT that needs to be used as a
basis for arriving at the
commission value. This
is a mandatory column.
TRX_TYPE VARCHAR2(30) The type of the
transaction. It can have
any one of the following
values:
CBK: Claw Back (or Take
Back)
CM: Credit Memo
GBK: Give Back
INV: Invoice
MAN: Manual
Adjustment
ORD: Booked Orders
PMT: Payment Received
WO: Write Off
This is a mandatory
column.


EMPLOYEE_NUMBER VARCHAR2(30) The resource that is
receiving credit for the
transaction. If using the
SQL*LOADER option or
the spreadsheet, the
value needs to be
Salesrep Number as
defined in Resource
Manager. Please refer to
Resource Manager
documentation for more
information on how to
define a resource.
OBJECT_VERSION_ NUMBER Sequential number
NUMBER which is set at 1 on insert
and incremented on
update. Used by APIs to
ensure that the current
record is passed. This is a
mandatory column.
When you upload a
transaction directly into
the API, the value must
be set to 1.
SALESREP_ID NUMBER(15) This value is populated
by standard collection
programs of the
application. Custom and
nonstandard processes
should not populate a
SALESREP_ID value.
The EMPLOYEE_
NUMBER column should
be used instead.


LOAD_STATUS VARCHAR2(30) This denotes the status of
the transaction after the
Transaction Interface
Loader process is run to
load transactions from
the API table to the CN_
COMMISSION_
HEADERS table. It must
have one of the following
values:
UNLOADED: Status of
new transactions when
they are first loaded into
the API table. It also
denotes transactions that
have not been picked up
for loading into the CN_
COMMISSION_
HEADERS table.
LOADED: The
transaction is
successfully loaded into
the CN_COMMISSION_
HEADERS table. See
Validation Checks and
Resolution Method for
more details.
TRANSACTION_ VARCHAR2(15) The currency code of
CURRENCY_CODE transaction amount that
comes with the
transaction, for example,
USD. The value must
correspond to the
currency code as defined
in GL-Currencies. See the
GL-Currencies form to
confirm. See Note: in
Exchange Rates
following.


EXCHANGE_RATE NUMBER The exchange rate that
needs to be applied to
determine the actual
amount of the
transaction. Ideally, this
matches what is defined
in the GL-Daily Rates
table. Note: Transaction_
Currency_Code and
Exchange_Rate are not
mandatory. If left as Null
the application assumes
that the currency_code
matches the functional
currency and that no
exchange rate will be
applied.
ADJUST_STATUS VARCHAR2(10) The adjustment status of
the transaction. It is
automatically updated
on the Adjustments
screen when the system
makes adjustments. This
is a system-generated
field and should not be
populated with any
value.
ORG_ID NUMBER Needs to be populated
with the specific org for
which the transactions
are being loaded for
Incentives calculation. If
the implementation is
multi-org, then it is a
mandatory column. If the
implementation is not
multi-org, then the
column can have null
value.


ROLLUP_DATE DATE The date the transactions
must use to roll up the
sales credit using the
compensation group
hierarchy. If this column
is null, the date value in
the PROCESSED_DATE
column will be set for
this column. If you need
this date to be different
from the PROCESSED_
DATE you can set it to a
different value.
REVENUE_TYPE VARCHAR2(15) This column denotes
whether the transaction
is of a Revenue or
Nonrevenue sales credit
type. For transactions
collected directly from
out-of-box integration
with Oracle Order
Management or Oracle
Receivables, this column
is populated
automatically with the
respective sales credit
type defined in these
source systems.
ATTRIBUTE1 - VARCHAR2(240) These are the descriptive
ATTRIBUTE100 flexfield columns on the
transaction. They can be
populated with values to
be used in defining
classification rules or for
defining expressions to
be used in formulas, rate
tables, and so on.
8.9.1 Validation Checks and Resolution Method

The transaction interface loader process starts by collecting transactions from the
API based on the parameters provided by the user and looking at transactions in
the API that have the following load_status:

UNLOADED: Status of the transaction when it is first loaded into the API table. It
also denotes that it has not been picked up for loading into the CN_COMMISSION_
HEADERS table.
ERROR - PRIOR ADJUSTMENT: This means that the value of the profile OSC:
Prior Adjustment has been set to No and the transaction processed_date has a
column value that is less than the last processed transaction processed_date. To
resolve this, perform the following:
1. Make sure to set the profile OSC: Prior Adjustment to Yes so that the system can
process prior period adjustments.
2. If the profile OSC: Prior Adjustment is set to No, change the processed_date on
the transaction to be greater than the date for which calculation was last run.
ERROR - TRX_TYPE: This means that the trx_type column value of the transaction
is not a system recognized transaction type. The possible values for this column are
Claw Back, Credit Memo, Give Back, Invoice, Manual Adjustment, Booked Orders,
Payment Received, or Write Off. To resolve this, fix the trx_type value on the
transaction.
ERROR - REVENUE CLASS: This means that the revenue_class_id column value
provided on the transaction is not defined in the system. To resolve this, make sure
that the revenue_class_id value populated on the transaction refers to the revenue
class defined in the system.
ERROR - NO EXCH RATE GIVEN: This means that the transaction currency is
different from the functional currency defined for the system and the value of the
exchange_rate column is not populated. To resolve this, populate the exchange_rate
column with a value on the transaction.
ERROR - INCORRECT CONV GIVEN: This means that no value has been given to
the transaction_currency_code column and the exchange_rate column but the value
of the transaction_amount is not equal to acctd_transaction_amount. To resolve this,
make sure that the transaction’s transaction_amount column is not a functional
currency based value, and then provide values for the transaction_currency_code
and exchange_rate columns. This error should not occur if you are using
SQL*LOADER or importing a spreadsheet. This is because the acctd_transaction_
amount is not required in those cases.
ERROR - CANNOT CONV/DEFAULT: This is a catch-all bucket in case the process
cannot do currency conversion of transaction_amount column of the transaction.
Possibly the currency code has not been defined.

SALESREP ERROR: This means that the process did not find any resources defined
in the system for the given employee_number column value or salesrep_id column
value. To resolve this, perform the following procedure:
1. Make sure the employee_number or salesrep_id column is populated with a
value in the API table. If you are using SQL*LOADER or a spreadsheet, only
employee_number needs to be entered.
2. Make sure the employee_number or salesrep_id on the transaction is defined in
the system and active for the processed_date of the transaction.
PERIOD ERROR: This means that the given processed_date column value on the
transaction does not fall within the accumulation period start date and end date
that is defined in the system. To resolve this, perform the following procedure:
1. Provide a value for the column processed_date on the transaction for which the
accumulation period start date and end date are defined in the system and also
Open.
2. Verify that the accumulation period start date and end date are defined in the
system to include the processed_date column value on the transaction.
For example, if periods are defined as follows:
Jan-02 (1-Jan-02 to 31-Jan-02)
Feb-02 (1-Feb-02 to 28-Feb-02)
A transaction that is processed for 2-March-02 will create a period error message.
The transaction interface loader process does not pick up transactions in the API
that have the following load_status:
OBSOLETE: This means the transaction has been adjusted prior to the transaction
interface loader being run and cannot be uploaded into the system.
FILTERED: This means that as part of Standard collections, the post collection
process is defined to filter this transaction, therefore that it cannot be loaded into the
system.
LOADED: This means the transaction is already successfully loaded from the table
CN_COMM_LINES_API into the transaction table CN_COMMISSION_HEADERS.
See Validation Checks and Resolution Method for more details.
Additional Note
The profile OSC: Reset Error Transactions allows you to decide whether or not to
attempt to load the unloaded transactions which failed to load in prior attempts.

The default value for this profile is No. When this profile is set to Yes, the
transaction interface loader attempts to load the transactions that failed to load in
prior loads.
If API transaction data are populated through Collection or created through
Maintain Transaction, the data is always valid. Invalid data, in most cases, are
introduced into the API table by a direct upload into the API table from an external
source.
For example, suppose that the invalid salesrep_id, invalid employee_number or
both columns are null. For such invalid transactions, the loader sets the Load_Status
to SALESREP ERROR or PERIOD ERROR, respectively. To fix this problem, correct
the data and then turn on the OSC: Reset Error Transactions profile so that these
error transactions can be picked up again in the next run of the load process.
Because this is an expensive operation, the profile should be set to Yes only if errors
have indeed been fixed in the transactions that could not be loaded.

9
Calculating Compensation

■ Section 9.1, "Overview of Calculating Compensation"
■ Section 9.2, "Calculation Enhancements in this Release"
■ Section 9.3, "Preparing for Calculation"
■ Section 9.4, "Submitting Calculation"
■ Section 9.5, "Using Incremental Calculation"
9.1 Overview of Calculating Compensation

Calculation is a process used by Oracle Incentive Compensation to calculate
commission and bonus plans for resources. This overview section explains:
Section 9.1.1, "Two Types of Calculation"
Section 9.1.2, "Two Methods of Calculation"
Section 9.1.3, "Phases of Calculation"
Section 9.1.4, "Unprocessed and Failure Statuses"
Section 9.1.5, "The Calculation Process"
9.1.1 Two Types of Calculation

Oracle Incentive Compensation calculates compensation based on two types,
Commission and Bonus. Commission calculation is calculated based on transactions
applied to formulas in a compensation plan. A Bonus formula is a type of formula
where there are no links or references to transactions.
Calculating Compensation 9-1

Overview of Calculating Compensation
9.1.2 Two Methods of Calculation

Oracle Incentive Compensation performs calculation in two ways: nonincremental
or incremental.
Nonincremental Calculation
Nonincremental Calculation calculates all transactions in a period, and it is the
default setting. Calculating all transactions is necessary if any major changes have
been made to the sales transactions database. For example, if a node or root is
added or deleted in the classification hierarchy or the effective periods of that
hierarchy, you need to recalculate every transaction. However, calculating the entire
set of transactions can take a long time.
Incremental Calculation
Incremental Calculation enables the calculation engine of Oracle Incentive
Compensation to process only transactions that are affected by a change. When you
run Incremental Calculation, the application uses the Notify Log, which tracks all
changes made in the system since the last calculation. See Section 9.5, "Using
Incremental Calculation", for more detail on this calculation method.
9.1.3 Phases of Calculation

When you calculate a set of transactions, the application performs these actions:
■ Preprocessing: The application determines which transactions are to be
calculated and performs validation. For example, it checks the resources to be
sure that they all have compensation plans with active dates and are assigned to
a pay group.
■ Revert: This feature restores the transactions within your specified parameters
back to their original unprocessed state. When a nonincremental calculation is
performed, the application deletes any system-generated (rollup) transactions
and reverts the status of transactions to Unprocessed. This way the new
calculation starts with no data left over from a previous calculation.
■ Classification phase: The application checks the revenue classification rules
that have been defined against the affected transaction attribute values. If a
match is found, a unique revenue class is assigned for each transaction. The
status of matched transactions is Classified.
■ Rollup phase: Oracle Incentive Compensation runs a process to determine all
resources who should receive credit for a transaction based on the rollup date
and the resource hierarchy effective for that date. For every credit receiver, the

application creates a new system-generated transaction for each manager

entitled to a rollup credit. The lines are marked as Rolled Up.
■ Population phase: Oracle Incentive Compensation identifies the appropriate
plan elements that are associated with the revenue classes that have been
matched with each transaction. The application updates each transaction with
the plan element information. The status after this phase succeeds is Populate.
■ Calculation Phase: Based on the information gathered, Oracle Incentive
Compensation performs calculation on all transactions that have passed the
Population phase for resources specified for the period. It totals the credit for
the transaction, checks against the accumulated quota figure to determine the
rate tier, calculates the final commission amount, and updates the commission
due amount. The transaction status is then displayed as Calculated.
9.1.4 Unprocessed and Failure Statuses

The following statuses can occur when a transaction has not been processed or if
there is a failure during one of the calculation phases.
■ Unprocessed: The transaction has not been processed or has been returned to
unprocessed state after a revert phase. The application displays a status for
unprocessed transactions in transaction status.
■ Failed Classification: Transactions that do not match a predefined revenue
classsification rule receive the Failed Classification status. This could be a result
of not defining or synchronizing the revenue classification rules before running
the calculation process. A primary cause of Failed Classification status is that
the transaction attributes do not satisfy the very top classification rule in the
hierarchy. Another cause of failed classification is that the processing date is
outside the dates defined for the Classification Ruleset. Check the dates of failed
transactions on the Unprocessed Transactions report (Navigation: Transaction >
Report). Transactions that fail classification receive a status of XCLS.
■ Failed Rollup: If a resource is not in the hierarchy in a compensation group, the
rollup fails, and a transaction status of XROLL is displayed.
■ Failed Population: Population fails if a transaction does not match the quota
rules for the credited resource. Population also fails if a transaction has a
matching revenue class, but the credit resource does not have the revenue class
assigned to his or her plan element. Transactions that fail population are
marked as XPOP.
■ Failed Calculation: Oracle Incentive Compensation indicates a failed status for
transactions that have failed the calculation phase in the transaction status.

Check your calculation rules, and be sure that your calculation expressions, rate
tables (if applicable), plan elements, and compensation plans are all valid.
Transactions that fail calculation are marked XCALC.
9.1.5 The Calculation Process

The process of calculation comprises three main sections, as follows.
The Rollup Phase

During the Rollup phase, Oracle Incentive Compensation runs a process to
determine all resources who should receive credit for a transaction based on the
rollup date, and the resource hierarchy effective for that date. For every credit
receiver, Oracle Incentive Compensation creates a new system-generated
transaction and the lines are marked as Rolled Up.
Rollup will fail if a resource is not in the hierarchy in a compensation group. A
transaction status of XROLL will be displayed.
Multiple resources can receive credit for the same commission transaction. For
example, a sales manager may receive sales credit for his subordinate’s transactions.
If you choose to compensate multiple resources for the same commission
transaction, you must organize your compensation groups into a hierarchy to
specify the relationships among the credit receivers in your sales force.
When transactions are processed with a hierarchy in effect, resources in parent
positions automatically receive all of the sales credit applied toward resources in
child positions that report to them, regardless of revenue classes. This roll-up credit
is also called indirect credit.
When Oracle Incentive Compensation allocates sales credit to multiple credit
receivers, each person receiving credit for the transaction receives 100% of the sales
credit.
The Population Phase

During the Population phase, Oracle Incentive Compensation identifies the
appropriate plan elements that are associated with the resource’s compensation
plan that have been allocated to the transactions. The application attempts to match
transactions with the Plan Elements for the credited resources and if the match is
successful, the transaction is populated.
The application performs the following checks during the Population phase. It
■ Identifies the pay period

Calculation Enhancements in this Release
■ Identifies the plan element and assigned Sales Role and Compensation Plan
(based on Plan Element to Revenue Class Mapping)
■ Uses the Revenue Class Hierarchy (traversing the hierarchy upwards to
determine the most general revenue class)
■ Handles revenue class overlap (The system generates a duplicate transaction
line record for any transaction that is associated with more than one Plan
Element due to revenue class overlap.)
■ Handles multiple roots (The system creates a system-generated duplicate
transaction line record for any transaction that is associated with more than one
sales role.)
■ Fails population. If the transaction does not find a matching revenue class in the
compensation plan for the credited resource then no commission can be
calculated. Oracle Incentive Compensation displays a status of Failed
Population (XPOP) in the transaction status column.
The Calculation Phase

During the Calculation Phase, Oracle Incentive Compensation performs the
calculation on all transactions for resources specified for the period. It totals the
credit for the transaction, checks against the accumulated quota figure to determine
the rate tier, calculates the final commissionable amount, and updates the
commission due amount. Oracle Incentive Compensation displays a status for
calculated transactions in the transaction status column.
Failed Calculation: If transactions failed to be calculated, Oracle Incentive
Compensation displays a status of XCALC for those transactions.
9.2 Calculation Enhancements in this Release
9.2.1 Rollup Summarized Transactions

Before the Rollup Summarization feature, the collection process replicated base
transactions to every resource in the rollup hierarchy. This means that in a rollup
hierarchy that was five levels deep with five base reps all rolling up to the same set
of managers, all transactions from the five base reps were replicated to every
manager. As an example, if each of the five base reps has ten transactions, there is a
total of 50 base transactions. After rollups, including all transactions for each
resource to their manager, there are 250 transactions, as shown below:
10 transactions x 5 levels deep x 5 base reps = 250

However, if the Rollup Summarized Transactions feature is turned on, then the
following occurs:
Before Rollup:
Total base transactions = 50 in CN_Commission_Headers (same as before)
Total summarized transactions = 5 in CN_Commission_Headers (one for
each base resource)
After Rollup:
Total number of transactions = 5 x 5 = 25 (five summarized transactions are
rolled up to each of the five managers)
The rollup summarization process results in huge reductions in the number of
transactions that need to be processed, which improves performance substantially.
You can summarize transactions if they share common definitions. The default set
of definitions includes the following fields:
■ direct_salesrep_id
■ processed_period_id
■ processed_date
■ rollup_date
■ comp_group_id
■ revenue_class_id
■ trx_type
Any transactions that match in these seven fields will be aggregated and processed
together. Therefore, it is very important to verify that your aggregated calculations
create the same result as when they are calculated separately. Some formulas can
generate different amounts of commission if aggregated transactions are used.
The following examples show a situation where aggregation does not affect
calculations and a situation where it does:
Example 1: Aggregation Yields same Result as Individual Transactions

The formula uses these settings:
■ Cumulative Flag: Yes
■ Non-proportional Flag: Yes

■ Apply Transactions Individually

■ Input: transaction_amount
■ Output: rate*transaction_amount
Rate Table below shows two columns and two rows, with 0-100 at 1% and 100-500
at 3%:
0-100 1%
100-500 3%
There are two transactions:

1. Transaction Amount of 90
2. Transaction Amount of 20
Without aggregation, the calculation proceeds as follows:
For the first transaction, the input of 90 falls into the first tier of the rate table, and is
compensated at 1%. Commission is 90 * 1% = 0.9.
For the second transaction, the input is 90+20=110, because the cumulative flag is
selected. This puts the transaction into the second tier. Because there is a
non-proportional split, the commission is 10 * 1% + 10 * 3% = 0.4.
The total commission for both transactions is 0.9 + 0.4 = 1.3.
If the aggregation profile is turned on, there will be one aggregated transaction with
a transaction amount of 110. The calculation process proceeds like this:
The input is 110. Because there is a non-proportional split, the commission is 100 *
1% + 10 *3% = 1.3. The aggregated transactions yield the same result as the
individual transactions.
Example 2: Aggregation Yields a Different Result

This example uses the same transactions, but the formula is not cumulative. Because
of this, the calculation result of an aggregated transaction is different from the total
of the individual transactions.
Commission is calculated as follows:
Transaction Amount is 90 * 1% = .09
Transaction Amount is 20 * 1% = .02

The total commission for both transactions is 0.9 + 0.2 = 1.1.

If aggregation is turned on for these non-cumulative transactions, there will be one
aggregated transaction of 110. The calculations are as follows:
Aggregated Transaction 100 * 1% + 10 * 3% = 1.3 (with a non-proportional split).
In this case, the commission derived from the aggregated transaction is different
from the commission derived from individual transactions.
Two Profile Options

Two profile options control Rollup Summarized Transactions.
■ Roll summarized transactions: This profile option sets up the application to
aggregate matching transactions. Set Yes or No; the default is No
■ Customized summarization: This profile option works only if the first profile is
set to Yes. This profile tells the application whether you are using default or
customized summarization code. Set Yes or No; the default is no. See
Appendix B, Customized Summarization Code Examples, for examples of the
code you need to set this up.
9.2.2 Accumulation and Splits in Multidimensional Rate Tables

Under some circumstances, commission must be derived from multiple aggregated
values. One way to accomplish this is to set up interdependent plan elements,
however this approach is complicated and can be difficult to understand. It is
simpler to use a single plan element with a multidimensional rate table. However,
until now, you could not use cumulative values in multidimensional rate tables. In
this version of Oracle Incentive Compensation you now can use multiple
aggregated values in a formula.
In this version of Oracle Incentive Compensation, it is possible to split rate tiers in
multidimensional rate tables.
Now, when you assign expressions to a cumulative formula, you can specify for
each expression whether it is cumulative or not. If you want to split rate table tiers
when calculating commission, you can select one dimension upon which to perform
the split.
There is no limit as to how many expressions can be cumulative, however you can
specify only one dimension to be split in any formula that is used in a
multidimensional rate table. Any more splits would render the calculation process
meaningless.

Generic Example of Accumulation Along Multiple Dimensions

Suppose we have the following rate table.
0-80% 80-90% 90-999%

0-100 1% 1.5% 2%
100-200 1.5% 2% 2.5%
200-1000 2% 2.5% 3%
The first dimension measures the total quantity of the sales and the second
dimension measures the percentage achievement of the total transaction amount
against the target.
Assume the following formula is used:
■ Name: Formula 1
■ Type: Commission/Apply individual transaction
■ Cumulative: Yes
■ ITD: No
■ Split: No split
■ Input1: quantity (cumulative: Yes)
■ Input2: transaction_amount/target (cumulative: Yes)
■ Output: RateResult * transaction_amount
Suppose you have the following transactions.
Transaction ID Quantity Transaction Amount

1 50 1000
2 100 2500
3 500 4000
The target for the example salesperson is 5000.

The commission will be calculated in the following way. For the first transaction,
the cumulative total from input1 is 50 and the cumulative total from input2 is 1000
/ 5000 = 20%. Comparing the two cumulative values against the rate table, the rate

is 1%. Now apply this rate to the current transaction’s transaction amount and you
get 1000 * 1% = 10.
For the second transaction, the cumulative total from input1 is 150 (adding 100 to
the previous total of 50 from transaction1) and the cumulative total from input2 is
20% + 2500 / 5000 = 70%. Comparing these two cumulative values against the rate
table, we find the rate to be 1.5%. Apply this rate to the current transaction’s
transaction amount and you get 2500 * 1.5% = 37.5.
For the third transaction, the cumulative total from input1 is 650 (adding 500 to the
previous total of 150 from transaction1) and the cumulative total from input2 is 70%
+ 4000 / 5000 = 150%. Comparing these two cumulative values against the rate
table, the rate is 3%. Apply this rate to the current transaction’s transaction amount
and you get 4000 * 3% = 120.
The total commission for all these three transactions will be 10 + 37.5 + 120 = 167.5.
Note that both input values are accumulated and the cumulative totals are used to
look up the rate from the rate table.
Generic Example of Split in a Multi-dimensional Rate Table

Suppose we have the following rate table.
0-80% 80-90% 90-999%

0-100 1% 1.5% 2%
100-200 1.5% 2% 2.5%
200-1000 2% 2.5% 3%
The first dimension measures the total quantity of the sales and the second
dimension measures the percentage achievement of the total transaction amount
against the target.
Assume the following formula is used:
■ Name: Formula 1
■ Type: Commission/Apply individual transaction
■ Cumulative: Yes
■ ITD: Yes
■ Split: Non-proportional split

■ Input1: quantity (cumulative: Yes/Split: Non-proportional split)

■ Input2: transaction_amount/target (cumulative: Yes)
■ Output: RateResult * quantity
Note that split is performed on the first dimension which corresponds to the first
input. Suppose you have the following transactions.
Transaction ID Quantity Transaction Amount

1 50 1000
2 100 2500
3 500 4000
The target for the example salesperson is 5000.

The commission is calculated in the following way. For the first transaction, the
cumulative total from input1 is 50 and the cumulative total from input2 is 1000 /
5000 = 20%. Since 20% matches the first column in the rate table, you use the rates in
the first column while splitting the quantity total along the first dimension. Since 50
is completely within the first tier of the first dimension, all of it is compensated at
the rate of 1, thus yielding a commission of 50 * 1 = 50.
For the second transaction, the cumulative total from input1 is 150 (adding 100 to
the previous total of 50 from transaction1) and the cumulative total from input2 is
20% + 2500 / 5000 = 70%. Since 70% still matches the first column in the rate table,
you use the rates in the first column while splitting the quantity total along the first
dimension. The first 100 out of the total of 150 is paid at the rate of 1 and the
remaining 50 that falls in the second tier is compensated at a rate of 1.5. Therefore,
the commission is 100 * 1 + 50 * 1.5 = 175. Since it is ITD calculation, we need to
subtract the previous payout. So, the commission is 175 - 50 = 125.
For the third transaction, the cumulative total from input1 is 650 (adding 500 to the
previous total of 150 from transaction1) and the cumulative total from input2 is 70%
+ 4000 / 5000 = 150%. Since 150% matches the third column in the rate table, you
use the rates in the third column while splitting the quantity total along the first
dimension. So, the first 100 gets paid at a rate of 2, the next 100 gets paid at a rate of
2.5 and the remaining 450 gets paid at a rate of 3. The total is 100 * 2 + 100 * 2.5 + 450
* 3 = 1800. Subtracting the previous payouts, the commission is 1800 - 125 - 50 =
1625.

Note that only the dimension marked to perform a split is traversed while splitting
the total amount. The other dimension(s) is only used to determine which set of
rates are used in computing the commission.
9.2.3 Batch Runners Automatically Cancelled after Failure

In previous releases of OIC, when one batch runner failed during calculation, all of
the other batch runners continued to be processed by the concurrent manager. There
was no way to cancel the running/pending request. In this release, if the application
detects a failed or cancelled batch runner during calculation, it automatically
cancels the other running/pending batch runners. Note: It takes the concurrent
manager a while to stop running requests.
9.2.4 Calculation Resubmission

In this release of Oracle Incentive Compensation, if calculation fails, you can
resubmit calculation from the point of failure rather than having to start from the
beginning. Calculation can fail at any phase in the process:
■ Revert
■ Classification
■ Rollup
■ Population, or
■ Calculation
If you resubmit calculation, calculation resumes starting with the failed phase.
To perform calculation resubmission, perform the following procedure:
Navigation
Transaction > Calculate
Prerequisites
Transactions must be collected and loaded.
Steps
1. Click the Transaction tab and the Calculate subtab.
The Calculation Submission page appears.

Submitting Calculation
2. In the search parameters, query for the batch by name or select Failed from the
Calculation Status drop-down list to list all failed batches.
3. Click Apply.
4. Click the batch name in the Batch Name column.
5. Click Calculate.
Calculation begins from the failed phase.
9.3 Preparing for Calculation

Before you run a compensation calculation, you must make sure that calculation is
possible for the salespeople chosen. You must verify the following things before
attempting to calculate compensation payments:
■ Make sure that all salespeople needing to be compensated have a valid
compensation plan assigned to them and are assigned to a pay group.
■ Make sure that the period for which you are calculating is open (this can only
be done if the current accumulation period status is either Never Opened,
Future Enterable, or Closed). To open a period, navigate to Administration >
Incentive > Accumulation Period.
■ You must have defined your classification rules and synchronized your
classification ruleset.
■ The revenue class hierarchy must be defined and set in the system parameters
window.
9.4 Submitting Calculation

You can calculate compensation for all resources who have valid compensation
plans, for all resources in the notify log file, or for resources you specify. The
Calculation Submission page displays a summary of all of the calculations that you
have submitted. You can click the link in the Batch Name column or use the search
parameters at the top to narrow your search to selected batch names. Or, click
Create to go to another detail page, where you can create a new calculation
submission.
Calculation can be run as often as necessary until the transactions have gone
through the payment process.

Use the following procedure to run or create a batch for calculation. To create a new
batch, start at step 1. To use a previously defined batch, click the link in the Batch
Name column and begin at step 8.
Navigation
Transaction > Calculate
Prerequisites
Transactions must already be collected and loaded.
Steps
1. Click Create. A new page appears, with blank fields.
2. Enter a batch name in the Batch Name field or click a link on the page in the
Batch Name column.
3. Select the dates of the transactions to be calculated. You can click the calendar
icon to open a pop-up calendar.
4. From the drop-down list, select the type of calculation to be submitted, either
Commission or Bonus.
6. Click Next.
Another page, also called Calculation Submission, appears, with the
information you entered displayed and new choices to make.
7. In the Resource Option field, select one of three options from the drop-down
list:
■ All Resources
■ Resources Specified by You
■ Resources in Notify Log
This enables you to calculate compensation for everyone, for a specially selected
group, or limits it to just resources affected by recent changes to their
compensation plan (See Guidelines).
The following steps apply to batches that you have just created or previously
created batches.
8. Check any of the three check boxes as needed:

■ Entire Hierarchy
■ Concurrent Calculation
■ Incremental Calculation
See Guidelines for more information.
10. Click Previous to view the previous Calculation Submission page.
11. Click Next to proceed with submitting the calculation.

If you selected All Resources or Resources in Notify Log in the Resource Option
field previously, the page that displays now will include the information you
entered along with a Calculate button. Click it to initiate the calculation process.
If you selected Resources Specified by You previously, the page that displays
includes a fields to enter the specific resources for whom you want to submit a
calculation.
To enter specific resources for calculation, perform the following procedure.
Steps
1. Enter the resources’ names.
Their employee numbers populate automatically.
To create more blank rows, place the cursor in the final field and press Enter.
The previous screen appears. Click Next to return to entering names.
2. When you have finished entering names, click Calculate.
3. If the calculation was successful, the Status field now shows Completed.
Note: To verify that the calculation was processed correctly, you can go to the
Year to Date Summary for the corresponding fiscal year (Transaction > Report >
Year to Date Summary). Search for the resource name and select the correct
fiscal year.
4. To view the Process Log, perform the following steps:
a. Return to the Calculation Submission page.
b. Enter the request ID for your transaction.
c. Click View Log in the Log column.

The Process Log appears and displays the information relating to your
calculation process.
Guidelines
The Status field displays the status of the calculation using these values:
■ Incomplete: The calculation has not been submitted.
■ Complete: The calculation has completed successfully.
■ Failed: An error has occurred. You can run the calculation again, if necessary.
■ In progress: The calculation is still in the processing of running.
Transactions with process dates that fall within the dates you specify are included in
the calculation.
If you have made a change that will affect the calculation, such as a rate table
change, then the application lists in the Notify Log all resources and periods that are
affected by the change. Select Resources in Notify Log to calculate all the resources
affected by the changes made.
Following is an explanation of the sort parameters:
■ Entire Hierarchy: Selecting this option submits calculation for resources on the
entire hierarchy. If you selected Resources Specified by You or Resources in
Notify Log, disable this option to perform the calculation on only the specific
resources you selected rather than their hierarchy.
■ Concurrent Calculation: If the calculation is large, select this option to run the
calculation as a background process in the Concurrent Manager. After you
submit a concurrent process, you can proceed to do other things while it
completes the calculation. You may want to make a note of the concurrent
request ID number in case you want to check the status of the process later on.
If a batch runner fails during concurrent calculation, the application
automatically cancels other running and pending batch runners. If you deselect
this option, then calculation is performed online.
■ Incremental Calculation: Use incremental calculations for most or all of your
calculations. This option calculates only newly added transactions. This option
also calculates the compensation for resources who are affected by events that
happened since the previous calculation.

Using Incremental Calculation
9.5 Using Incremental Calculation

If you have a large volume of transactions to process, it can save time to process
only those transactions that have been affected by some change. Incremental
calculation marks all predefined transaction events in a notification log table known
as the Notify Log. By marking all pre-defined transaction events in the Notify Log,
Oracle Incentive Compensation enables Incremental calculation only for the
resources that require it.
In the Notify Log table, the REVERT_TO_STATE columns tell the calculation engine
to what state the transactions need to be reverted. In nonincremental calculation,
transactions are completely deleted and returned to the Umprocessed state.But in
incremental calculation, the calculation engine can selectively skip various phases of
calculation for individual transactions.
The Notify Log records changes related to five phases of calculation (see
Section 9.1.3, "Phases of Calculation"):
■ Revert
■ Classification
■ Rollup
■ Population
■ Calculation
Any changes occurring to the following elements could cause the need for
recalculation:
■ System Parameters
■ Classification Rules
■ Revenue Class Hierarchy
■ Dimensions used in classification rules
■ Formulas
■ Rate Tables
■ Plan Elements
■ Start date, end date
■ Revenue classes
■ Transaction factors

■ Compensation Plans
■ Role plan assignment
■ Resource role assignment
■ Resource level plan element change
■ Interval number
■ New transactions
To use Incremental Calculation you must check the Incremental Calculation check
box on the Calculation Submission page when running the calculation. To enable
the Notify Log functionality you must set the profile option OSC: Mark Events to Y.
If you normally use Incremental Calculation for every calculation you do not need
to deselect the Incremental Calculation check box. The Notify Log keeps track of
changes and if a Nonincremental Calculation is required it will do this
automatically. You can check the Notify Log to see if it will run for all sales people
to get an indication of how long the calculation will take. However, making entries
into the Notify Log can impact performance so it is advisable to deselect the
Incremental Calculation check box for the first time when you are expecting to
make major changes to the classification rules or revenue class hierarchy.
Oracle Incentive Compensation can track notifications to the following four levels:
■ Resource Level: If an event causes re-calculation for multiple periods, then the
mark event creates an entry for a resource with a Null period and specifies the
date range.
■ Resource/Period Level: A resource usually has one entry per period with a
status of Incomplete in the Notify Log table. If the event causes a change to all
resources, then instead of adding an entry for all the resources, there is a global
entry, which tracks all resources for a period.
■ Resource/Period/Start Date Level: If an event causes the change at the specific
date level within a period, notification can track at specific date range level.
This allows recalculation to be done for transactions falling within the specified
date range instead of calculating for the entire period.
■ Resource/Period/Start Date/Plan Element Level: This level is the most granular
level that is captured, and it makes incremental calculation the most efficient.
For the events that cause the REVERT_TO_STATE to go only to the Population
phase, only the Calculation phase needs to be rerun. This makes sense if, for
example, the transaction is being rerun only because of a change in the
commission rate of a single plan element.

9.5.1 Revert_To_State
Revert_to_state determines the state to which all transactions will be reverted in the
Revert phase of the Calculation. For example, if revert_to_state is ’ROLL, then all
transactions created by Oracle Incentive Compensation after ROLL will be deleted
and all source transactions (transactions not generated by the application) will have
a transaction status of ’ROLL’. If a transaction has been reverted to ROLL, the
Rollup phase of the Calculation will skip Rolling up the transactions with ROLL
status.
Revert_to_State alone does not determine which calculation phases to skip. The
Action column in the notification table, in conjunction with Revert_to_State,
determines which calculation phases are executed.
If there are multiple entries in the notify log for the same period then the entry with
the lowest revert_to_state will take precedence. For example, if an event creates an
entry with Revert_to_State ’CALC’ and ’ROLL’ then the revert phase of the
calculation reverts all the transactions for a resource to the ’ROLL’ status, and will
re-process the transactions from the Population phase.
Incremental calculation goes through all phases of the calculation, but the revert
phase based on the Revert_to_State intelligently figures out to what state the
different transactions for a salesrep need to be reverted. If the transactions are
reverted to POP status, the Population phase of the calculation ignores all the
transactions with the POP phase, which improves performance.
9.5.2 Action Column

Action is a column in the Notify Log which in conjunction with Revert_to_state,
optimizes incremental calculation.
For example, if a hierarchy change event results in adding a manager to a
compensation group, then the update to the Notify Log adds an entry for the
manager, with revert_to_state of ’ROLL’ and an action of ’PULL’. When incremental
calculation is submitted, the Rollup phase creates the Roll Up transactions instead
of skipping the Rollup phase for the manager, because the Revert_to_State is
’ROLL’.
If the hierarchy change event results in the deletion of a resource or a manager from
a compensation group, then the Notify Log has an entry for all the affected
resources for the Revert_to_State as ’ROLL’ and the Action as ’DELETE_SOURCE’
or ’DELETE_ROLL_PULL’ and so on. When Incremental Calculation is submitted,
during the Revert phase of the calculation all the rolled up transactions are deleted

because the Action is ’DELETE_SOURCE’ or ’DELETE_ROLL_PULL’ although the

Revert_to_Status is ’ROLL’ .
9.5.3 The Notify Log

The Notify Log automatically records every change in the system that affects
calculation. The Notify Log lists what part of the calculation is affected and
therefore must be rerun as a result of an event.
You must turn the OSC: Mark Events profile option to Y for every transaction event
to be put into the Notify Log so that it is included in the next calculation phase.
To view the Notify Log, perform the following procedure.
Prerequisites
Resources must exist. An event must have taken place.
Navigation
Transaction > Notification Log
Steps
1. To search, click Search to use the NotifyLogDefault parameters or any searches
you have already saved. To create a custom search, click Personalize (see
Customizing the Notify Log Search below).
2. Click any of the table headers that are links to sort the log on that particular
column.
3. Use Previous and Next go move from the displayed rows to the ones before or
after them.
9.5.4 Customizing the Notify Log Search

Because the Notify Log Summary page may contain hundreds of entries, it helps to
be able to narrow down the search parameters. You can use the Search page in the
Notification Log subtab to customize it to suit your needs.
Navigation
Transaction > Notification Log > Personalize

Prerequisites
None
Steps
1. On the Search page, enter search parameters into the six fields in the Notify Log
area. Parameters include:
■ Resource Name (text)
■ Employee Number (text)
■ Start Date (text or click the icon for a pop-up calendar)
■ End Date (text or click the icon for a pop-up calendar)
■ Revert to State (drop-down list with 14 options)
– All (default)
– No Calculation
– Unprocessed
– Calculated
– Classified
– Obsoleted
– Payeed
– Populated
– Rolled Up
– Failed Calculation
– Failed Classification
– Failed Payee
– Failed Population
– Failed Rollup
■ Status (drop-down list with 5 options.)
– All
– Completed (default)
– Failed

– Incomplete
– In Progress
2. In the Display Options area, select which columns you want to be displayed in
the search results page.
3. Click a selection once in the Available Columns and then click the right arrow
button in the center area to move the selection to the Displayed Columns list.
You can also click an item in the Displayed Columns area and then click the left
arrow to move it back to the Available Columns list. The double arrow buttons
move the entire contents to the other side.
4. From the drop-down list, select which parameter you want to use first to sort
the list.
5. Select Ascending or Descending from the drop-down list. Ascending is the
default setting.
6. Select second and third level sort parameters, if needed. These parameters can
be sorted in an ascending or descending order.
7. Select the number of rows to be displayed at a time.
8. In the Save As area, give a name to your custom search. You can also use the
default by leaving the Default check box checked.
9. Click Save to save your search parameters. Or, click Save and Apply Search to
go directly to searching.
10. Click Search to initiate a search process. Click Restore to return to the

10
Payment with Payruns

■ Section 10.1, "Overview of Payment with Payruns"
■ Section 10.2, "Payment Enhancements in this Release"
■ Section 10.3, "Using the Payrun Summary"
■ Section 10.4, "Creating a Payrun"
■ Section 10.5, "Using the Worksheet Summary"
■ Section 10.6, "Using the Payment Transactions Page"
■ Section 10.7, "Approving a Payrun"
■ Section 10.8, "Submitting a Payrun for Payment"
10.1 Overview of Payment with Payruns

After you have used Oracle Incentive Compensation to collect transactions and
calculate commissions, the last step in the process is payment. The Oracle Incentive
Compensation payrun process is much like that used in most companies. The
Oracle Incentive Compensation Payment process considers the following:
■ Who is paid
■ Which transactions are paid
■ How much is paid
■ When payment occurs
Oracle Incentive Compensation does not actually produce paychecks. The
application uses payruns to determine payment amounts. When a payrun is paid, it
Payment with Payruns 10-1

Overview of Payment with Payruns
is automatically transferred to Oracle Payroll or Oracle Payables, as long as the

integration between Oracle Incentive Compensation and Oracle Payroll or Oracle
Payables has been enabled. For external payment applications, you can feed the
data to the application using a .CSV file. Oracle Incentive Compensation saves
payruns and their associated worksheets, which can be referenced as an audit trail.
You must create a separate payrun for each pay group. Set up pay groups on the
Administration Tab (See Chapter 12, Administration, for more details). Use the
Payrun Summary page to view this information (see below). You can set up
multiple payruns per period.
The table below lists the steps for creating, approving, and paying a new payrun.
Step OIC Page Used/Navigation

Manager assigns payment plan to resources Payment Plan
(optional)
Resource > Resources > Payment Plans link
Super User creates a payrun Create Payrun
Transaction > Payment > Create Payrun
button
Analyst views and adjusts payment Worksheet Summary
worksheet details
Transaction > Payment > Click Analyst
Payrun Total link
Payment Transactions
Transaction > Payment > Worksheet
Summary > Click Total Worksheet Amount
link
Analyst locks payment worksheet Payment Transactions
Transaction > Payment > Worksheet
Summary > Click Total Worksheet Amount
link
Analyst submits payment worksheet to Worksheet Summary
manager
Transaction > Payment > Click Analyst
Payrun Total link
Manager approves or rejects worksheet Payrun Sign-Off Report
Transaction > Payment > Click Signoff
Report link
Super User runs a pay payrun request Requests > Payment > Submit Requests

Overview of Payment with Payruns
Step OIC Page Used/Navigation

For external pay payment applications, Payrun Sign-Off Report
Super User downloads payrun details to
Transaction > Payment > Click Signoff
a.CSV file, which can be opened by a
Report link > click download icon
spreadsheet application (optional)
10.1.1 Prerequisites
In order for resources to receive payment, they must be assigned to a pay group and
a compensation plan that are effective for the period for which the payrun is
created. This is how OIC determines if a resource is qualified to receive
compensation.
To create a pay group, navigate to Administration > Incentive > Pay Group. See
Chapter 12, Administration, for information on how to create a pay group.
To assign a resource to a pay group, navigate to Resource > Resources, enter the
name of the resource, and click Pay Groups in the left-hand menu. See Chapter 7,
Assigning Compensation Plans, to assign a pay group to a resource.
The resource optionally can be assigned a payment plan, which is used to control
how much of the resource’s earnings are paid in each payrun. Some payment plans
contain minimum or maximum amounts per pay period. Minimum amounts are
used to pay resources compensation during periods in which they do not earn
substantial commissions, and maximum amounts are used to reduce payment when
a resource earns more commission than they can be paid.
Minimum amounts may be recoverable or nonrecoverable. Recoverable payments
need to be paid back, but nonrecoverable payments do not. The payback by the
resource can be scheduled and limited in various ways. Overpayments can be
carried forward or waived with the Pay Later feature.
To create a payment plan, navigate to Administration > Incentive > Payment Plan.
See Chapter 12, Administration for the steps for this process. Assign the payment
plan to the resource in the same way you assigned the pay group. Navigate to
Resource > Resources, enter the name of the resource, and click Payment Plans in
the left-hand menu.
All calculations for all resources for which you want to pay commission must be
completed for the appropriate date range before you can start the payrun process.
Calculation creates the commission amounts for transactions and updates the
commission due amounts. The Payment process then uses these amounts to
populate the payment amount for each resource. If any adjustments are made later,
they will be resolved the next time a payrun is run.

Payment Enhancements in this Release
10.2 Payment Enhancements in this Release

This release of Oracle Incentive Compensation has a substantially upgraded
Payment functionality. The six major enhancements include automated posting,
lockable payment worksheets, the ability to add and track comments on payment
worksheets, an enhanced payment approval process, manual payment adjustments
on the payment worksheet, and a Payment Worksheet History page. Also, you can
now refresh a payment worksheet.
10.2.1 Automated Posting

In previous releases of Oracle Incentive Compensation, you had to perform posting
after calculation was complete and before processing any payment. Posting
transfers the calculation data from the calculation tables to the posting tables. Then,
payment uses the posting tables as input for payruns.
In this release, posting is done automatically. Because the process is automatic, you
have the option of paying commissions individually or by summarizing the
transactions. When you create a payrun that pays by individual transaction, a
posting line is created for each transaction. This allows you to maintain transaction
line details for each commission line. However, if you elect to summarize
transactions, the application automatically aggregates the transactions by plan
element and other factors when it posts them. Summarizing transactions speeds the
processing of a large volume of transactions in situations where you do not need to
pay by individual transaction.
10.2.2 Lock Payment Worksheets

The Worksheet Summary page replaces the Payrun Details page that was used in
releases 11.5.6 and 11.5.7. It enables you to lock, unlock, and submit payment
worksheets. The Worksheet Summary contains much more information than the old
Payrun Details page, including detailed search parameters and links to five other
pages. See Section 10.5, "Using the Worksheet Summary" for more information and
steps for using this new page.
10.2.3 Add and Track Comments on Payment Worksheets

The Worksheet Summary includes a link to the Analyst Notes page. This page
includes comments on the worksheet and individual transactions. Users can add or
review notes associated with a payment worksheet. Audit information on this page
makes it easier to track changes and make adjustments. Individual notes on this
page are limited to 4,000 characters each. Additional system generated messages

also appear in the Analyst Notes, such as holds, waives, adjustments, and refreshes.
See Section 10.6, "Using the Payment Transactions Page" for more information.
10.2.4 Payment Administrative Hierarchy and Payrun Sign-Off Report

The pay worksheet lifecycle, as defined in section 10.1, is as follows. An analyst
reviews the pay worksheets for his resources that are assigned to him. He makes
any adjustment, adds note to the worksheet explaining the adjustments, and when
satisfied, he locks the worksheet and submits it for approval by his manager. His
manager must approve the worksheet as should her manager until the chain
reaches the Super User.
Before the payrun can be paid, all worksheets must be in the approved status. The
approval hierarchy is created in Resource Manager. It defines who possesses
approval and the ability to edit the analyst worksheets.
Oracle Incentive Compensation uses a Payment Administrative Hierarchy to define
the relationship between analysts, payment managers, and the Super User. An
analyst must possess a role within this hierarchy in order to access the payment
hierarchy.
At the top of the hierarchy is the Super User. This is the root node. Super Users are
the only people who can perform actions on payruns. These actions are: create,
delete, freeze, unfreeze, refresh, and pay.
Analysts can only access worksheets for resources assigned to them and resources
not assigned to any analyst. An analyst’s manager can access worksheets for
resources assigned to them plus any resources assigned to any analyst under them
and any unassigned resources.
The Payrun Sign-Off Report is used by managers to approve or reject a payment
worksheet. The report is customizable to display as much resource compensation
information as needed. See Section 10.7, "Approving a Payrun" for details on the
steps used by a hierarchy to approve a payrun.

10.2.5 Recoverable and Non-Recoverable Manual Payment Adjustments

In 11.5.8, a manual pay adjustment can be made to the pay worksheet. This is an
additional amount that reduces or increases the payment amount on the worksheet.
The amount can be made recoverable during the next payrun that is created. If the
manual pay adjustment is not recoverable, it will not be owed by the resource at a
later date and will not show up in the balances. To make an adjustment recoverable,
check the ’Recoverable’ check box on the manual pay adjustment line.
10.2.6 Payment Worksheet History Page

Click the link in the Worksheet Status column on the Worksheet Summary page to
see the Payment Worksheet History page. This page displays all of the auditing
information related to worksheet activities. This information is useful for tracking
changes made to payment worksheets. Columns include Status Change Date, New
Status, and Updated By, which gives the name of the person who updated the
worksheet.

Using the Payrun Summary
10.2.7 Refresh Worksheet

In the previous versions of Oracle Incentive Compensation, the only way a
worksheet could be refreshed with the latest commission data was if the worksheet
was deleted. However, if the worksheet was deleted, all adjustments associated
with the worksheet were lost. In this release, the worksheet indicates to the analyst
that the commission data captured at the time of worksheet creation is not the most
up-to-date data. The worksheet displays the earnings due (beginning balance +
current period earnings) captured at the time of worksheet creation and the
earnings due in the commissions module. The analyst can chose to refresh the
worksheet so that these values mirror each other. With the worksheet refresh, no
adjustments, no notes, no history, nor manual payment adjustments will be deleted;
they will only be modified by the analyst manually.
10.3 Using the Payrun Summary

To view previous payruns or create a new one, navigate to Transaction > Payment.
Use the search parameters on this page to list previous payruns. The results of your
search are displayed as the Payrun Summary. From this page you can either click
Create to open the Create Payrun page or drill down on an existing payrun to
obtain more information on the Worksheet Summary page.

Using the Payrun Summary
Prerequisites
None.
Steps
1. Click the Transaction tab and the Payment subtab. The Payrun Summary page
appears.
2. To create a new payrun, click Create Payrun. This takes you to the Create
Payrun page. See Section 10.4, "Creating a Payrun".
3. To list all payruns, click Apply in the search parameters section at the top of the
page. Or, you can use the parameters to narrow your search. The Payrun and
Paygroup parameters use a search feature, with a Go button. The other three
parameters use a drop-down list of values from which to select. The parameters
are:
■ Payrun: Enter the full name or partial name and click Go.
■ Pay Period: Select from the drop-down list. All pay periods that are already
created in the Administration tab and are open are displayed. The default
setting is All.
■ Paygroup: Like the Payrun parameter, use the full or partial name, or enter
the percent sign (%) as a wild card. Enter at least four characters, and click
Go. To be listed, the pay group must be defined in the Administration tab.
■ Payrun Status: Select All, Frozen, Paid, or Unpaid from the drop-down list.
Payruns can be frozen only by the SuperUser. The default setting is All.
■ Incentive Type: Select All, Bonus, or Commission from the drop-down list.
The default setting is All.
4. Click Apply. Any payruns that match the parameters you selected are
displayed.
5. Verify payrun information by checking the first four columns. They display
basic information that identifies the name of the payrun, the paygroup that uses
it, the incentive types (All, Bonus or Commission, and the pay period.
6. Click the link in the Payrun Status column to view the Payrun History page.
There, status changes are listed by:
■ Status Change Date - Date the action was performed.
■ New Status - Unpaid, Locked, Submitted, Approved, or Paid.
■ Updated By - Name of the person performing the status change.

Creating a Payrun
7. Look at the Worksheet Statuses column on the Payrun Summary page to see the
quantity and status of worksheets that were in the payrun. This information
helps managers see the progress of their reporting analysts, so they can contact
the analysts to be sure they submit their worksheets in a timely manner.
8. Click the link in the Analysts Payrun Total column. The Worksheet Summary
page appears. Many actions can be performed on this page. See Section 10.5,
"Using the Worksheet Summary" for details.
9. The Payrun Total column displays the total amount for all payment worksheets
for the payrun.
10. If the Payrun Summary shows approved worksheets in the Worksheet Statuses
column, you can click Signoff Report to go to the Payrun Sign-Off Report page.
This page supplies additional details about the Payrun, and is used by
managers approve or reject a payment worksheet.
Guidelines
If you are logged in as a manager, the Analysts Payrun Total column displays the
sum of the payments due to resources assigned to you or analysts assigned to you.
If you are logged in as a Super User, the field displays 0.00.
The Payrun Summary can be sorted in ascending or descending order on any
column except Worksheet Status or Signoff Report.
10.4 Creating a Payrun

To create a payrun, click Create Payrun on the Payrun Summary page.
Prerequisites
In order to be paid, a resource must be created in Resource Manager, be assigned to
a pay group, and be assigned a payment plan.
Steps
1. Click the Transaction Tab and the Payment subtab. The Payrun Summary page
appears.
1. Enter a payrun name. This is a required field.
2. Select a pay group from the drop-down list. The drop-down list displays pay
groups that have been created in the Administration tab.

Using the Worksheet Summary
3. Select a pay period from the drop-down list. Pay periods are defined in the
Administration tab.
4. Select a payment incentive type from the drop-down list. Choices are All,
Bonus, or Commission. All is the default.
5. Select a Pay Date. Click the calendar icon to open a pop-up calendar.
6. Click Update to save the payrun. If necessary, click Restore to return to the
Guidelines
You can only have one open payrun per pay group at any one time. The application
will not allow you to create a new payrun until the status of any previous payruns
for the pay group is Paid.
You can only create payruns for the last period paid or a future period. Once you
have paid a payrun for one period you cannot go back to the previous month to
create a payrun for the pay group.
It is possible to have more than one payrun for the same pay group in the same
period as long as you have paid the first one. This is known as an off-cycle
payment.
10.5 Using the Worksheet Summary

The Worksheet Summary contains many columns of useful information about
payruns, listed by individual resource. On this page you can remove, refresh, lock,
unlock, and submit payment worksheets. The enhanced search capability enables
you to view all payment worksheets for a given payrun or narrow your search for a
specific set of worksheets. But the worksheets that are available to a logged-in user
are defined by the user’s position in the payment hierarchy.

In addition, you can click five different links on this page to go to other pages for
additional information. The table below shows the column that contains a link in
the report and the page that appears when you click the link:
Click Link in this To Display this

Column Page Meaning
Resource Name Details The Details page lists data on the resource,
including personal information, work location, and
sales team details.
Current Earnings Current Estimated The report breaks down the amount that is owed to
Due Payout the resource, displaying beginning balances and
earnings.
Total Worksheet Payment Use the Payment Transactions page to make
Amount Transactions adjustments in the payment amount for a
transaction for a resource.

Click Link in this To Display this

Column Page Meaning
Analyst Notes Analyst Notes The Analyst leaves useful annotations here that
explain reasons and comments for future reference
by the analyst, manager, or Super User.
Worksheet Status Payment This page shows every status change made to the
Worksheet Payment Worksheet.
History
A resource may be assigned to an analyst, but it is not required. If a resource is

assigned to an analyst, the analyst’s name appears on the Worksheet Summary. A
manager can view information only about resources assigned to the analysts who
report to him or her, and can also view unassigned resources by checking the
Unassigned Resources check box before clicking Apply Search.
After a search finds qualified resources, the worksheet displays earnings, payments,
recoveries, and adjustments. Original earnings and subsequent adjustments are
shown, as well as the amount that would be paid according to the payment plan,
including payment and recovery adjustments. The Total Worksheet Amount is the
final payment figure, after all earnings and adjustments are considered.
To use the Worksheet Summary page, perform the following procedure:
Prerequisites
The payrun must already be created.
Steps
1. Use the search parameters at the top of the page to call up worksheet
information.
■ Resource Name
■ Resource Number
■ Analyst
■ Worksheet Status: Select All, Approved, Locked, Submitted, or Unpaid
from the drop-down list. All is the default.
Note: Check the Unassigned Resources and My Analysts check boxes to
generate a list all data for all of your analysts and unassigned resources when
you click Apply Search.

2. Click Apply Search.

3. The search results are displayed below.
4. Optionally, click the download icon to download to Worksheet Summary to a
.CSV file.
5. For unpaid payruns, create a worksheet by entering a name or number into the
fields for Resource Name and Resource number. Enter four our more characters
and click Go to search for a resource name or number. Click Update.
6. For paid payruns, you can click on five different links to display other pages
(see preceding table).
7. Click the link in the Resource Name column to go to a Details page for the
resource.
The Details page lists data on the resource, including personal information,
work location, and sales team details. In addition, the role type and group
membership are show. For role type and group you can click the Show History
button to see separate reports.
8. Click the link in the Current Earnings Due column to go to the Current
Estimated Payout page.
This view-only page shows the total payment amount and all of the earnings
made to determine the calculated earnings. This report is customizable by
displaying specific columns for each quota group code. See section 10.5.1 for a
list of the columns.
9. Click the amount in the Total Worksheet Amount column to go to the Payment
Transactions page.
On this page, you can view the individual transactions that are part of the
payrun for the specific resource.
10. Click the link in the Analyst Notes column to go to the Analyst Notes page.
This page enables the Analyst to leave useful annotations that explain reasons
and comments for future reference by the analyst or others. A new row can be
created on this page or on the worksheet summary page as well.
11. Click the link in the Worksheet Status column to go to the Payment Worksheet
History page.
This page shows every status change made to the Payment Worksheet. Status
change dates are listed chronologically, along with the new status and the name
of the person who updated the worksheet.

Using the Payment Transactions Page
Guidelines
As a business process, a payrun can be populated with resource worksheets in two
ways:
■ The Super User runs a concurrent program that creates all the worksheets for
the members of the paygroup for the specified payrun.
■ The Analysts manually add their resources’ worksheets.
You can sort the Worksheet Summary page on any column except for Current
Earnings Due or Analyst Notes. You can sort in ascending or descending order.
10.5.1 Current Estimated Payout Page

This view-only page appears when you click the Current Earnings Due link on the
Worksheet Summary page. The report breaks down the total payment amount for
the period for the resource. It displays current calculated earnings as the sum of the
beginning balance due to prior period adjustments and the current period earnings.
The page display takes into account whether the resource has multiple roles and
displays the amounts correctly.
This report is customizable by displaying the following columns for each quota
group code:
■ Percent Annual Quota, Period-to-Date: Credit, Earnings, Target, Achievement
■ Year-to-Date: Credit, Earnings, Target, Achievement.
Once a payrun has been paid, these figures become the status of the time of
payment.
10.6 Using the Payment Transactions Page

The Payment Transactions page displays the details of the total payment amount. It
comprises earnings, beginning balances, payment plan totals, and recoveries. Use
the Payment Transactions page to make adjustments in the payment amount for a
transaction or to review the payment amounts for a resource. The page displays the
transactions for a resource that are part of a pay worksheet, including Transaction
Type, Calculated Amount, Payment Difference, and Payment Amount. You can
view the history of the pay worksheet by clicking the link in the Worksheet Header
Comments area under the History column. However, it cannot be edited.

Payments may need to be adjusted for one of the following reasons:

■ You want to pay a different amount from what was calculated.
■ You want to make a payment for a future transaction.
■ The resource is receiving a bonus.
■ Any other reason as indicated in the comments in the Analyst Notes.
Use the buttons in the Worksheet adjustments area to lock the worksheet or add a
payment plan. This cannot be done, however, after the payrun has been paid.
The Payment Transaction page can be created, removed, refreshed, locked,
unlocked, submitted, approved, and rejected.
Prerequisites
Payment worksheet must already be created. Analyst can work only on worksheets
assigned to him or her or unassigned.

Steps
1. Enter comments into the Analyst Notes in the Worksheet Header Comments
area.
a. Select a reason code from the drop-down list.
b. Add any additional comments in the Additional Comments field.
c. Click the History link to see the Payment Worksheet History page.
2. Check the Hold Transaction check box to hold a transaction. This delays
payment for the transaction to a future payrun.
3. Check the Waive Recovery check box to waive recovery for a transaction. This
means that the resource does not have to pay back the payment for the
transaction.
4. The Calculated Amount column displays the total amount calculated for the
resource at the time calculation was run.
5. The Payment Difference column displays the difference between the Calculated
Amount and Payment Amount, if any, for unpaid transactions. Values other
than ’0.00’ indicate that the earnings captured by the worksheet are not the most
current for the resource. A worksheet refresh obtains the most up-to-date
commission data.
6. To create a manual pay adjustment, enter the amount into the Payment Amount
column. Use the Waive Recovery check box to indicate if it is recoverable or
non-recoverable.
7. The Plan Element Name and Pay Element Name fields show information that
may be helpful when changing the payment amount.
8. Click Update to save any changes. Click Restore to return to the previously
saved information.
9. Click the Lock Worksheet button to lock the data on the payment worksheet for
the resource. This must be done to before submitting the worksheet for
approval by the manager, or it can be done to keep the information from being
changed.
10. Optionally, click Add Payment Plan to add a payment plan to the resource that
will be in effect for the pay worksheet.
Guidelines
The Payment Transactions page can be sorted on three columns, in ascending or
descending order:

Approving a Payrun
■ Calculated Amount
■ Payment Difference
■ Payment Amount
The Payment Transactions page is a worksheet that displays all transactions for the
resource, including Transaction Type, Calculated Amount, Payment Difference, and
Payment Amount. Now, while looking at this information, you can add a payment
plan if the payrun has not yet been paid.
You can hold a transaction or waive recovery for a transaction by checking the
appropriate check box next to it. When you hold a transaction it is taken out of the
payment worksheet and is not paid in the current payrun. It can be paid in a future
payrun. A new feature allows you to create manual transactions that are recoverable
or non-recoverable. Check the Waive Recovery check box next to a manual
transaction if it does not need to be paid back later by the resource.
The Payment Difference column displays the difference between the Calculated
Amount and Payment Amount for unpaid transactions. Any changes to
transactions will affect the total payment amount to the resource.
10.7 Approving a Payrun

After a payrun has been created, it must be approved by the Payment
Administrative Hierarchy. As payment worksheet approvals work their way up the
hierarchy, records are created and stored.
The table below lists four different Worksheet Status types, with a description of the
meaning:
Worksheet Status Description

Unpaid Before a payment worksheet has been through the approval
process, its status is Unpaid. A payment worksheets has this
status when it is created.
Locked After reviewing a payment worksheet and making any
adjustments, the analyst locks it to prevent any changes before
submitting it to the manager. If the analyst of the manager
unlock a payment worksheet, the status resets to Unpaid.
Submitted After the analyst submits a worksheet for approval by the
manager, its status changes to Submitted. Payment worksheets
must be locked by the analyst before they submit them.

Approving a Payrun
Worksheet Status Description

Approved The worksheet has been approved by the manager and has been
submitted to his or her manager. The approval process continues
until it reaches the Super User. The Super User pays the
worksheet after all worksheets under them are approved.
After calculation is complete, payruns are created using the Run Create Worksheets
Concurrent Process. The payrun is opened and analysts begin reviewing the
commission information for resources assigned to them. Analysts can drill down on
the Current Earnings Due link on the Worksheet Summary to the Current Estimated
Payout page. There, analysts can see the resource’s overall performance to quickly
verify that the overall earnings match what the resource is supposed to receive. On
the Current Estimated Payout page, analysts review the resource’s annual
quota/target, YTD achievement, Period-to-Date data, and the earnings by quota or
bonus.
If an analyst decides that some adjustments are necessary, he or she can make
manual adjustments to the payment amount using the Payment Transactions page.
These adjustments can be:
■ Adjustments to earnings

Approving a Payrun
■ Manual pay adjustments

■ Waived recoveries
■ Held transactions
■ Payment plan additions
While the payrun is open, commission recalculation may take place if some
transaction adjustments were not loaded for the current or a prior period. To
compensate for this, analysts can selectively refresh payment worksheets. This lets
the analyst include changes for resources that need it while preserving the
comments and manual adjustments that they have already made for the resource.
For example, a worksheet is created for a resource with a payment plan for $1,000. If
the resource’s earnings are $600, then the payment plan adds $400 to bring the total
to $1,000. However, after transactions are recalculated for the resource, the earnings
are reduced to $450. If the payment plan is reapplied during a refresh, the amount
of the plan increases from $400 to $550 to compensate for the lost earnings and keep
the total at $1,000. If the refresh is not applied, the original amounts remain
unchanged.
In a similar scenario, a worksheet is created for a resource with a payment plan of
$1,000. The earnings are $600 and the payment plan adds $400 to bring the total to
$1,000. For this resource, a manual transaction of $200 is made. The transactions are
recalculated and the total earnings are reduced to $450. In this case, the manual pay
adjustment is added to the $450 earnings, so after the refresh, the payment plan
amount is reduced to $350 so the total can be $1,000. Without the refresh, the
original amounts stay the same.
The Payment Difference column on the Payment Transactions page makes it easy
for analysts to see which resources have a payment difference because of a
commission recalculation.
After the analysts are finished examining and verifying a resource’s data, they can
click Lock Worksheet to put the payment worksheet in Locked status. Then, they
submit the worksheet for approval by their manager, which puts the payment
worksheet in Submitted status. Locking the worksheet preserves the information on
it in the event that the Payment Super User later performs a refresh at the payrun
level. In that case, any locked worksheets are not refreshed. A worksheet can be
unlocked by the analyst. This puts the worksheet in Unlocked
The manager uses the Payrun Sign-Off Report to review all of the details pertaining
to the worksheet and then approve it of reject it, adding comments if desired. When
a manager rejects a payment worksheet, it returns to Unpaid status. Any comments
added during the approval process are maintained for future reference. If

Approving a Payrun
When all the worksheets for the payrun are approved by all levels of managers, the
Super User submits a Pay Payrun. The payrun status then changes to Paid. If the
Super User freezes the payrun, no changes can be made to the worksheets by
analysts.
10.7.1 The Payrun Sign-Off Report

The Payrun Sign-Off Report is used by managers to approve or reject worksheets
that have been submitted by the analysts that report to them. The search parameters
at the top can be personalized to set up targeted searches. The columns shown in
the report can be customized to display only those the information that you need to
approve the payment worksheets. For example, columns that display quota
information about each resource can be added so it is easy to reference that
information during the approval process.
[Screenshot here]
To approve or reject payment worksheets, perform the following procedure.
Prerequisites
Payment worksheets must be submitted to the manager by the analyst.
Steps
1. Log in as a manager responsibility.
2. Click the Transaction tab and the Payment subtab. The Payrun Summary page
appears.
3. Click Signoff Report in the Signoff Report column next to the payrun you want
to work on. The Payrun Sign-Off page appears.
4. Click Select next to the payment worksheets that you want to reject or approve.
You can click Select All to select all of the worksheets.
5. Optionally, click the Analyst Notes link to see the Analyst Notes. Information in
the notes may be useful in determining whether to reject or approve a
worksheet.
6. Click Reject or Approve.
7. You can download the report to a .csv file by clicking the download icon to the
right of the Approve button. The file can be opened in a spreadsheet program.

Submitting a Payrun for Payment
Guidelines
Any adjustments performed at the payment plan level will be redone.
10.8 Submitting a Payrun for Payment

After all the worksheets have been approved by the entire payment administrative
hierarchy, the Super User can submit the payrun for payment. Use the Payment
subtab on the Requests tab to create a concurrent request for this purpose.
The Payment subtab of the Requests tab contains two pages which enable you to
view or submit payruns. Simply make selections from the drop-down menus to
initiate your request.
10.8.1 View Requests

Use this page to view requests.
Prerequisites
Payrun must be approved by Super User.
Steps
1. Click the Requests tab and click the Payment subtab. The Payment Requests -
View Requests page appears.
2. Select from the drop-down lists in the search parameters to narrow your
request:
■ Request Name. Selections include:
– All (the default)
– Pay Payrun
– Delete Unpaid Payrun
– Create Worksheet
■ Phase. Selections include:
– Completed
– Inactive
– Pending

– Running
■ Status. Selections include:
– 18 other options, including Normal and Error
■ Request ID. Enter the number of the request, or sort in request ID order.
3. Click Apply.
Any records that match the search parameters are displayed, in reverse
chronological order, with the most recent record at the top.
Guidelines
Information displayed includes:
■ Request ID
■ Request Name
■ Phase
■ Status
■ Parameter
■ Submission Date
■ Requestor
■ Priority
■ Log (explanation of what happened)
This information is helpful in determining the status of your current payruns, and
in planning new payruns.
10.8.2 Submit Requests

Use the Submit Requests link on the Payment Requests page to create a worksheet,
pay a payrun or cancel an unpaid payrun.
Prerequisites
Payrun must be approved by Super User.

Steps
1. Click the Requests tab and click the Payment subtab. The Payment Requests -
Submit Request page appears.
2. In the Request Name field, select Create Worksheet, Pay Payrun, or Delete
Unpaid Payrun from the drop-down list.
3. Select a Payrun name from the drop-down list. All payruns that have been
created in the Transaction tab are listed.
A new row appears at the top of the table, with a Request ID number in the first
column.
5. Click Refresh Data to update the table to reflect any changes to the phase.


11
Reports

■ Section 11.1, "Overview of Oracle Incentive Compensation Reports"
■ Section 11.1.1, "Road Map of Reports from Version to Version"
■ Section 11.2, "Reports Enhancements in this Release"
■ Section 11.3, "Incentive Planning Reports"
■ Section 11.3.1, "Quota Modeling Summary"
■ Section 11.3.2, "Average Quota Report"
■ Section 11.3.3, "Quota Overassignment Report"
■ Section 11.3.4, "Quota Range Report"
■ Section 11.3.5, "Compensation Contract Status Report"
■ Section 11.3.6, "Overlay Report"
■ Section 11.3.7, "Vacancy Report"
■ Section 11.3.8, "Transition Report"
■ Section 11.3.9, "Plan Activation Status Report"
■ Section 11.3.10, "Role to Compensation Plan Mapping Report"
■ Section 11.4, "Compensation Reports"
■ Section 11.4.1, "Year To Date Summary"
■ Section 11.4.2, "Transaction Details Report"
■ Section 11.4.3, "Compensation Group Hierarchy Report"
■ Section 11.4.4, "Classification Rules Report"
Reports 11-1
Overview of Oracle Incentive Compensation Reports
■ Section 11.4.5, "Commission Summary Report"

■ Section 11.4.6, "Quota Performance Report"
■ Section 11.4.7, "Commission Statement"
■ Section 11.4.8, "Unprocessed Transactions"
■ Section 11.5, "Configuring Reports"
■ Section 11.6, "Discoverer Workbooks"
11.1 Overview of Oracle Incentive Compensation Reports

Oracle Incentive Compensation provides two sets of reports. These assist in
planning compensation and in monitoring the processing of transactions. The
reports are located on the Report subtabs of the Quota and Transaction tabs.
The table below describes the changes that have been made to the reports from the
11.5.3 to the 11.5.8 releases.
11.1.1 Road Map of Reports from Version to Version
Release 3i 11.5.3 11.5.4 11.5.5 11.5.6 11.5.7 11.5.8 Notes

x means Report
is available
Planning
Reports
(Quota tab)
Quota Model x x x x x x Changed from Quota Modeling
Summary Summary in 11.5.6
Average Quota x x x x x x
Summary
Quota x x x x x x Changed from Overassign Quota
Overassignment Summary in 11.5.6
Report
Quota Range x x x x x x Changed from Quota Range
Report Summary in 11.5.6

Release 3i 11.5.3 11.5.4 11.5.5 11.5.6 11.5.7 11.5.8 Notes

Compensation x x x x
Contract Status
Overlay Report x x x x x x Changed from Overlay Summary in
11.5.6
Vacancy x x x x x x Changed from To-Be-Hired
Transition x x x x x x Changed from Transitional
Report Salespeople Report in 11.5.6
Plan Activation x x x x x x Changed from Plan Generation
Status Report Status in 11.5.4 and Plan Status in
11.5.5
Role To x x x x x x Changed from Role to Plan Mapping
Compensation in 11.5.4
Plan Mapping
Report
Salesperson x Replaced by Role to Plan Mapping
Plan Report in 11i.
Assignments
Compensation
Reports
(Transaction
tab)
Compensation x Replaced in 11.5.4 by Year-To-Date
Summary Summary.
Details Summary.
Details (Fiscal Summary
View)
Year to Date x x x x x x Replaced 6i Compensation Summary,
Summary Compensation Details,
Compensation Details (Fiscal View)
in 11.5.4
Adjustments x Replaced by Transaction Details
report in 11.5.4
Transaction x x x x x Replaced Adjustments report in
Details 11.5.4
Reports 11-3
Release 3i 11.5.3 11.5.4 11.5.5 11.5.6 11.5.7 11.5.8 Notes

Compensation x x x x x Replaced by Hierarchy report in
Group 11.5.4. HTML version introduced in
Hierarchy 11.5.5
Salespeople x Replaced by Hierarchy report in
Hierarchy 11.5.4
Hierarchy x x Replaced Compensation Group
Hierarchy and Salespeople Hierarchy
reports in 11.5.4
Classification x x x x x x 6i report decommissioned in 11.5.4.
Rules HTML report introduced in 11.5.5
Payrun Listing x x After 11.5.3, information available on
Payrun Details page in application
Payrun Details x After 11.5.3, information available on
Payrun Details page in application
Analyst x Replaced by Commission Summary
Consolidated in 11.5.4
Summary
Commission x x x x x x Replaced Analyst Consolidated
Quota x x x x x x x 6i report in 11.5.3 replaced by HTML
Performance report of same name in 11.5.4
Commission x x x x x x x
Statement
Performance x 6i report decommissioned after 11.5.3
Details
Blind Ranking x 6i report decommissioned after 11.5.3
Top/Bottom x 6i report decommissioned after 11.5.3
Performers
Compensation x 6i report decommissioned after 11.5.3
Trending
Unprocessed x x x x x x
Transactions
Payment Hold x Decommissioned after 11.5.3
Pending x Decommissioned after 11.5.3
Payment

Incentive Planning Reports
Release 3i 11.5.3 11.5.4 11.5.5 11.5.6 11.5.7 11.5.8 Notes

Pending x Decommissioned after 11.5.3
Transactions
11.2 Reports Enhancements in this Release

The Commission Statement report has been enhanced to give users the ability to
personalize the content of the report.
Also, eight seeded Discoverer workbooks are provided in this release. See
Section 11.6, "Discoverer Workbooks" for more details.
11.3 Incentive Planning Reports

There are ten Incentive Planning reports on the Quota tab. To access a report,
navigate to Quota > Reports. In the report name column, click the link for the report
you want to view.
For the first nine reports, the Resource Search page appears. On the Resource Search
page, enter search parameters and click Apply, and the report appears.
For the Role To Compensation Plan Mapping Report, clicking the link takes you to a
specific search page with three fields. Enter search parameters, click Apply, and the
report appears.
Note: The report link name on the Reports summary page may vary slightly from
the actual name of the report.
These are the ten Incentive Planning reports:
■ Section 11.3.1, "Quota Modeling Summary"
■ Section 11.3.2, "Average Quota Report"
■ Section 11.3.3, "Quota Overassignment Report"
■ Section 11.3.4, "Quota Range Report"
■ Section 11.3.5, "Compensation Contract Status Report"
■ Section 11.3.6, "Overlay Report"
■ Section 11.3.7, "Vacancy Report"
■ Section 11.3.8, "Transition Report"
■ Section 11.3.9, "Plan Activation Status Report"
Reports 11-5
■ Section 11.3.10, "Role to Compensation Plan Mapping Report"
11.3.1 Quota Modeling Summary

With this report, you can get a snapshot of:
■ A compensation group’s total quota and its constituents
■ A compensation group’s quota approval status by salesperson
■ The over assignment effect reverberating through lower levels of the
organization hierarchy
You can see in one report the quota allocations to every resource or salesperson,
including the manager of a selected compensation group. The quota is broken down
by individual components that make up the total quota. Additionally, the user can
see the over assignment expressed in values as well as percentages between each
level of the organization hierarchy. These are represented by subtotals at the bottom
of the report for each level of salespeople; for example, the total quota for
salespeople at the bottom of the hierarchy (street level), the total quota for the
immediate manager (first line manager) and the total quota for the manager of the
first line manager.
Navigation
Quota > Report > Quota Model Summary
Parameters
Prompts Choices Mandatory

Name Search field No but the default is "All" or
%
Employee Number Search field No but the default is "All" or
%
Compensation Group Search field No but the default is "All" or
%
Organization List of Values No but the default is "Any"
Effective Date Calendar pick list No but the default is today’s
date

The search criteria produces a list of Compensation Groups. You must select one
Compensation Group.
Data
The first table of information
:
Column Title Description

Resource Name Lists salespeople in the Compensation Group selected
Employee Number Displays associated employee numbers
Role Displays associated roles
Role Start Date Displays the start date of each salesperson’s assigned role
Role End Date Displays the end date of each salesperson’s assigned role
Component 1 Name Displays the assigned quota against this user-defined
Component
Component
Component
Total Quota Displays the total assigned quota for all Components for each
role
Assigned Quota Displays the rounded figure of the total quota
Plan Status Displays the approval status of the Compensation Plan
Overlay Yes or No flag (see Concepts and Procedures for explanation of
overlay)
The second and last table of information:
Row Title Description

Total quota for second Displays column totals for all salespeople with Plan Level value
line manager of 2 (see Sales Role Details screen and Plan Level field)
Total quota for first line Displays column totals for all salespeople with Plan Level value
manager of 1
Total quota for street Displays column totals for all salespeople at the bottom of the
hierarchy for this Compensation Group and with Plan Level
value of 0 or null
Reports 11-7
Row Title Description

Over assign from second Displays the second line manager’s quota as a percentage of the
line manager to first line first line manager’s quota
manager
Over assign from first Displays the first line manager’s quota as a percentage of the
line manager to street street salespeople quota
11.3.2 Average Quota Report

With this report, you can view the average quota value by role for the selected
compensation group. It is useful to know the average quota value for comparable
roles in various compensation groups and organizations. In some companies,
compensation groups are organized by sales territory. Therefore, it is possible with
this report to compare the quota between comparable roles over various territories.
Additionally for reference, the planned sales figure to be delivered by the selected
compensation group is shown by means of a summary table that displays the total
quota, excluding overlay and a breakdown of total quota by role. Against each role,
there is a headcount. In the next and subsequent tables for each role there is a list of
salespeople and a simple average of the quota assigned by role.
Note: The percentage values shown are percentages of the actual quota and not
rounded figures.
Navigation
Quota > Report > Average Quota Summary
Parameters

Name Search field No but the default is "All" or %
Employee Number Search field No but the default is "All" or %
Compensation Group Search field No but the default is "All" or %
Effective Date Calendar pick list No but the default is today’s date
The search criteria will produce a list of Compensation Groups and User is required
to select one Compensation Group.

Data
First table of information:

Role Lists the roles available in the Compensation Group selected
Number of People Displays the total number of people of each assigned role
Component 1 Name Displays the total assigned quota against this user-defined
Component by role
Component by role
Component by role
role
Assigned Quota Displays the rounded figure of the total quota by role
The last row displays the grand total.

Second and subsequent tables of information are listed by role or Compensation
Plan:

Name Lists the salespeople with the relevant role or Compensation
Plan
Component for each salesperson
salesperson
Assigned Quota Displays the rounded figure of the total quota for each
salesperson
Reports 11-9
The last row displays the total number of salespeople for the role and the simple
mathematical average for each column.
11.3.3 Quota Overassignment Report

The Quota Overassignment report shows in one report the over assignment value
and percentage effect on the immediate level of salespeople and the street level
salespeople. In the case of managers that have only street level salespeople
reporting to them, the overassignment figures are displayed under Direct
Overassignment and not Street Overassignment, even if the salespeople are street
level. The Street Overassignment column is populated only for a manager who has
both managers and street level resources as direct reports.
This report displays only salespeople with manager roles.
Navigation
Quota > Report > Overassign Quota Summary
Parameters

The search criteria will produce a list of Compensation Groups and User is required
to select one Compensation Group.
Data

Name Lists the manager of the compensation group selected
Plan Start Date Displays the start date of each salesperson’s assigned plan


Plan End Date Displays the end date of each salesperson’s assigned plan
Final Quota Displays the rounded figure of the total quota assigned
Direct Overassignment Displays the compensation group manager’s quota as a
percentage of his/her directs’ total quota
Street Overassignment Displays the compensation group manager’s quota as a
percentage of street-level salespeople’s total quota
11.3.4 Quota Range Report

The Quota Range Report enables you to scan the list for those salespeople who fall
outside the range of minimum and maximum quota values predefined for each role.
Contract Approvers can use this report as a means of rejecting compensation plans
or contracts that have been submitted for their scrutiny.
For each selected compensation group, the maximum and minimum quota range is
displayed for each role. In addition, there is a column that shows how each
salesperson’s assigned quota in the selected compensation group fared against the
minimum quota set for the role.
Navigation
Quota > Report > Quota Range Summary
Parameters

The search criteria produce a list of Compensation Groups and you must select one
Compensation Group.
Reports 11-11
Data

Resource Number Displays associated employee numbers
Resource Name Lists salespeople in the compensation group selected
Sales Role Displays associated roles
Assigned Quota Displays the rounded figure of the total quota assigned
Quota Minimum Displays the role’s minimum quota as defined under the Sales
Role Details screen
Quota Maximum Displays the role’s maximum quota as defined under the Sales
Role Details screen
Percent of Minimum Displays each salesperson’s actual assigned quota as a
percentage of each role’s quota minimum
11.3.5 Compensation Contract Status Report

The Compensation Contract Status report shows the number of people at each state
of the approval process for a selected manager in a compensation group. To create a
report for a specific manager, enter information into one or more fields below.
Navigation
Quota > Report > Compensation Contract Status
Parameters

The search criteria produce a list of Salespeople Found. Select a name in the
salesperson Name column.

Data
In the Compensation Contract Status report, the columns represent lines of
business, including a total. The rows represent stages in the contract process,
including Pending Approval, Pending Distribution, Pending Acceptance, and
Accepted. There is a total row for each line of business.
11.3.6 Overlay Report

The Overlay Report lists all overlay salespeople, if any, who are members of the
compensation group and groups below this group. This report is a concise display
of overlay salespeople as distinct from previous reports where both overlay and
nonoverlay salespeople are displayed together.
Navigation
Quota > Report > Overlay Summary
Parameters

The search criteria produce a list of Compensation Groups. You must select one
Compensation Group.
Data

Name Lists salespeople in the compensation group selected
Job Title Displays each salesperson’s job title as read from Oracle
Resource Manager
Reports 11-13

Assigned Quota Displays the rounded figure of the total quota assigned
11.3.7 Vacancy Report

The Vacancy report lists all positions, by sales role and compensation group, that
have not been filled for a particular manager. It is a concise means of listing
vacancies and additional headcount requirements on one report.
Navigation
Quota > Report > Vacancy Summary
Parameters

Compensation Group.
Data

Name Lists vacancies in the compensation group selected
Compensation Group Lists the compensation group manager’s name
Plan Start Date Displays the start date of each salesperson’s assigned plan
Plan End Date Displays the end date of each salesperson’s assigned plan
Final Quota Displays the rounded figure of the total quota assigned

11.3.8 Transition Report

The Transition report lists all salespeople who have not been allocated a role, in the
selected compensation group and groups below. It is a means of identifying those
salespeople who do not have a role for the next contract cycle.
Navigation
Quota > Report > Transitional Salespeople
Parameters

Compensation Group.
Data

Resource Number Displays employee numbers of the salespeople in the selected
compensation group
Manager Name Lists the compensation group manager’s name
Manager Employee Displays the compensation group manager’s employee number
Number
11.3.9 Plan Activation Status Report

The Plan Activation Status report lists the compensation plan activation status for
all salespeople in the selected compensation group. The activation process is related
to passing approved compensation plans from Sales Force Planning to commission
Reports 11-15
processing. This report helps you to identify those compensation plans that have
not been activated for commission processing and to take action to investigate its
non-active status.
Prior to this release of Oracle Incentive Compensation, the components in Salesforce
Planning had to be identical to the plan elements in Oracle Incentive Compensation
used for commission processing, or the activation failed. In this release, activation
will succeed as long as each component in the Incentive Planning compensation
plan has a matching plan element in the compensation plan in Oracle Incentive
Compensation, even if additional plan elements exist in the compensation plan.
For example, an Incentive Planning compensation plan has three components
which match three plan elements in a compensation plan in Oracle Incentive
Compensation, but the latter plan has a fourth element allowing manual
transactions to be processed. In this case, the plan should be activated successfully.
Navigation
Quota > Report > Plan Status
Parameters

Compensation Group.
Data

Resource Number Displays employee numbers of the salespeople in the selected
compensation group


Compensation Group Lists the compensation group’s name
Compensation Plan Displays compensation plan
Plan Status Displays the approval status of the Compensation Plan
Reason Displays the reason for any incomplete status
11.3.10 Role to Compensation Plan Mapping Report

The Role to Compensation Plan Mapping report lists all sales roles and how each
was mapped to job title(s) as read from Oracle Resource Manager, for each
compensation group selected.
This report is configurable. For instructions on how to hide or show selected
columns, go to the Configuring Reports section below.
Navigation
Quota > Report > Role to Compensation Plan Mapping
Parameters

Role Name Search field
Plan Name Search field
Data
The first table of information:

Role Displays all roles that satisfy the effective date search criteria
Compensation Plan Displays the name of each compensation plan
Start Date Displays the beginning date of the compensation plan
End Date Displays the lapsed date of the compensation plan
Reports 11-17
Compensation Reports
11.4 Compensation Reports

Oracle Incentive Compensation provides eight Compensation Reports. There are
eight Compensation reports on the Transaction tab. To access a report, navigate to
Transaction > Reports. In the report name column, click the link for the report you
want to view.
For some of the reports, when you click the link, a Salespeople Search page appears.
Use search parameters to get to a Salesperson Search Results page. A few reports
display another search parameter page after you make a selection from the
Salesperson Search Results page.
Three reports do not use the Salesperson Search page or Salesperson Search Results
page. The Classification Rules Report link leads to the Classification Rules Search
page. The Commission Summary Report and the Quota Performance Report open
directly from their Summary of Compensation Reports page links.
The steps below apply to the reports that use the Salesperson Search page and
Salesperson Search Results page.
Prerequisites
Incentive Compensation Online Super User responsibility is required.
Steps
1. Click the name of the report you want to view.
The Salesperson Search page appears.
The Salesperson Search Results page appears.
3. Click the Salesperson Name to open the report.
These are the eight Compensation reports:
■ Section 11.4.1, "Year To Date Summary"
■ Section 11.4.3, "Compensation Group Hierarchy Report"
■ Section 11.4.4, "Classification Rules Report"
■ Section 11.4.5, "Commission Summary Report"
■ Section 11.4.6, "Quota Performance Report"

■ Section 11.4.7, "Commission Statement"

■ Section 11.4.8, "Unprocessed Transactions"
Salespeople Search
Use this page to search for a specific salesperson’s report.
Prerequisites
Salesperson must exist in Resource Manager.
Steps
1. Select an analyst from the drop-down list. The default is All.
2. Enter a name or employee number.
You can use a partial name or number followed by a percent sign (%) to
perform a general search, such as for names beginning with the letter S. Or,
leave the percent sign alone in the fields to list all possible salespeople in the
search results.
3. Click Go.
4. The Salesperson Search Results page appears.
5. Click the Salesperson Name to open the report for that person.
6. To start over, click Clear to return the page to its original settings.
Salesperson Search Results

This page lists the results of the search based parameters you entered on the
Salespeople Search page. Click a name in the Salesperson Name column to view the
report you requested for that person.
11.4.1 Year To Date Summary

The Year to Date Summary is an overview of a salesperson's achievements,
commission and bonus earnings and advances or draws. This report is accessible by
default by the Manager, Salesperson, Incentive Compensation Payment, and
Incentive Compensation Super User responsibilities.
The figures are grouped by period and by plan element. A Super User can control
which plan element appears as a quota or bonus category through by checking the
Quota Group check box on the Plan Element form. If you check:
Reports 11-19
■ Quota: The plan element name displays in the Quota category.

■ Bonus: The plan element displays in the Bonus category.
■ None: The plan element name does not display.
The pay out section is grouped by earnings type and by period.
You can click the Download button to save the report in a .csv file that can be
opened in a spreadsheet program. Note: If all of the digits do not display properly
in the downloaded report, right-click in the cell and format the cell as General.
Note: Any transactions from December must be posted in order to appear in the
January summary for the following year.
Navigation
Transaction > Report > Year to Date Summary
Parameters

Salesperson Name/Number Search fields on Salespeople Yes
Search screen.
Credit Type List of Values
Reporting Currency List of Values No, but defaults to functional
currency.
Fiscal Year List of Values
Graph List of Values
Data

Quota Category Displays each quota assigned to the resource
Period Periods of the year displayed, for example, Jan-01 through
Dec-01, with earnings shown below them.
Other Begin Balance, Quota Earnings, and Payment rows shown
at the bottom for each column. Also, Recoverable Draw
Paid, Nonrecoverable Draw Paid, Draw Recovered. At the
bottom is End Balance.

11.4.2 Transaction Details Report

The Transaction Details report shows transactional details of the specified
salesperson and is used primarily by the Analyst. The report can be run to show
results of any specified period and by transaction status.
This report is configurable and for instructions on how to hide or show selected
columns, go to the section below.
Navigation
Transaction > Report > Transaction Details Report
Parameters

Salesperson Name List of Values Yes
Order Number
Adjustment Status List of Values
Invoice Number List of Values
Processed Date From List of Values Yes
Processed Date To List of Values Yes
Transaction Type List of Values
Adjustment Date List of Values
Calculation Status List of Values
Reporting Currency List of Values
Data
This standard report lists the transactions a salesperson is eligible to receive
commission for during a specified period. The columns visible are controlled by
the System Administrator. You can display up to 12 columns without having to
scroll left or right. You can customize the report by adding columns, such as
Attribute1 shown in the table. Below is a sample of the available columns for this
report.
Reports 11-21

Invoice Number Invoice Number
Invoice Date Invoice Date
Order Date Order Date
Order Number Order Number
Creation Date Creation Date (such as 03-JAN-2002)
Process Date Process Date
Transaction Type Transaction Type
Adjustment Status Adjustment Status (Frozen, Reversal, etc.)
Adjusted By Adjusted By
Calculation Status Calculation Status (Rolled Up, etc.)
Original Currency Code Original Currency Code (USD, etc.)
Sales Credit Sales Credit
Commission Commission Amount
Attribute1 Customizable attribute (part number, etc.)
11.4.3 Compensation Group Hierarchy Report

The Compensation Group Hierarchy report is useful not only for displaying
compensation groups and the resources in each, but also for showing the roll up
hierarchy of the groups in relation to each other. In the first column, the number
indicates the level in the hierarchy of the compensation group. The Level 1 group is
at the top of the hierarchy, and is also at the top of the report. Where there is a
hyperlink, click the resource name to display a Year to Date Summary for that
person.
Navigation
Transaction > Report > Compensation Group Hierarchy Report
Parameters

Salesperson Name Search field Yes


Compensation Group List of Values
Effective Date List of Values No, but today is the default
Data

Level Read only numeral
Comp Group/Salesrep Name Two fields (Expandable hierarchy)
Role Role name (read only)
Start Date Start date (read only)
End Date End date (read only)
Steps
1. Use the Salespeople Search window to search by Analyst, Name, or Employee
Number.
2. If multiple search results appear, click the name that you need.
The Compensation Group Hierarchy Report opens.
3. If the resource belongs to multiple compensation groups, select one from the
drop-down list.
4. Effective date defaults to today’s date. You may change it by clicking the
calendar icon to select a different date.
5. Click Submit.
6. Repeat steps 3 through 5 with other names and compensation groups as
required.
7. Optionally, click a resource name in the table body to display a Year to Date
Summary for that person.
11.4.4 Classification Rules Report

The Classification Rules report displays the Rule Name, Revenue Class, and
Expression for classification rules selected from the list on the Rules Found page.
Reports 11-23
Click Download to generate a .csv file that can be opened in a spreadsheet.
Navigation
Transaction > Report > Classification Rules Report
Parameters

Ruleset Name Search field Yes, but set in System
Parameters
Rule Name Search field No, but useful for narrowing
search
Effective Date Calendar icon No, but today is default
Data

Rule Name Rule Name
Revenue Classes Revenue Classes
Expression Expression
Classification Rules Search

Use this procedure to perform searches of Classification rulesets.
Steps
1. Select the ruleset name from the list of values, and enter a search key in the Rule
Name field, for example, FY01.
2. The Effective Date field populates with the current date, but any other date can
be selected by clicking the calendar icon to the right of the field.
3. Use Clear to start over, or click Go after you have entered all of the necessary
search information. The Rules Found page is displayed.
4. Click a rule to go to the Classification Rules Report for that rule.

The report generated displays the Rule Name, Revenue Class, and Expression.
Click Download to generate a .csv file that can be opened in a spreadsheet
program.
11.4.5 Commission Summary Report

The Commission Summary report is a snapshot of salespeople achievement and
earnings. Achievements are shown against interval to date quota and annual quota.
Earnings total are broken down by period to date and interval to date.
This report is identical to the Quota Performance report except that there are 3 extra
columns (on the far right) available through this report. This report is accessible
through Incentive Compensation Payment responsibility by default. For users with
Manager and Salesperson responsibilities, the Quota Performance report is the
default report.
You can change four fields before displaying the report by selecting from drop-
down lists.
Navigation
Transaction > Report > Commission Summary
Parameters

Analyst List of Values Yes
Period List of Values Yes
Credit Type List of Values Yes
Data

Name Salesperson Name
Resource Number Salesperson Number
Cost Center Salesperson Cost Center
Charge to Cost Center Cost Center where commission will be charged
Reports 11-25

Analyst Analyst Name
Sales Role Salesperson Sales Role
Compensation Plan Compensation Plan
Start Date Start Date
End Date End Date
Bonus Annual Quota Bonus Annual Quota
Bonus Percent Bonus Percent
Quota Annual Quota Quota Annual Quota
Quota Percent Quota Percent
YTD Bonus Target Year to date bonus target
YTD Bonus Credit Year to date bonus credit
YTD Bonus Earnings Year to date bonus earned
YTD Quota Target Year to date quota
YTD Quota Credit Year to date sales credit
YTD Quota Earnings Year to date quota-based earnings
YTD Total Earnings Year to date total earnings (quota-based earnings plus bonus
earned)
PTD Bonus Target Period to date bonus
PTD Bonus Credit Period to date bonus credit
PTD Bonus Earnings Period to date bonus earnings
PTD Quota Target Period to date quota
PTD Quota Credit Period to date sales credit
PTD Quota Earnings Period to date quota-based earnings
PTD Total Earnings Period to date total earnings (quota-based earnings plus
bonus)
Begin Balance Beginning Balance of what is due to the salesperson
Draw Amount of Draw paid
Net Due Amount due after deductions

Steps
1. Select an Analyst from the drop-down list. The default is All.
2. Select a period from the drop-down list.
3. Select Functional Currency in the Credit Type field.
4. Select a Reporting Currency for the report from the drop-down list.
5. Click Apply.
The report appears.
6. Click the Personalize button at the end of the report to customize the report.
The Quota Performance Personalization page appears. Check check boxes to
select Display Quota Groups (Bonus or Quota) and Display Periods (Annual,
Year to Date, Period to Date).
7. Click the Download button at the end of the report to download the report as a
file.
11.4.6 Quota Performance Report

This report is a snapshot of salespeople achievement and earnings. Achievements
are shown against interval to date quota and annual quota. Earnings totals are
broken down by period to date and interval to date.
Navigation
Transaction > Report > Quota Performance
Parameters

Analyst List of Values Yes (only for super user)
Credit Type List of Values Yes
Reports 11-27
Data

Name Salesperson Name
Resource Number Salesperson’s Employee Number
Cost Center Salesperson Cost Center
Charge to Cost Center Cost Center where commission will be charged
Analyst Analyst Name
Sales Role Salesperson Sales Role
Compensation Plan Compensation plan name
Start Date Start date
End Date End date
YTD Draw Target Year to date draw
YTD Draw Credit Year to date Draw sales credit
YTD Draw Earnings Year to date draw earnings
YTD Formula Target Year to date formula
YTD Formula Credit Year to date formula credit
YTD Formula Earnings Year to date formula earnings
YTD Quota Target Year to date quota
YTD Quota Credit Year to date sales credit
YTD Quota Earnings Year to date quota-based earnings
YTD Total Earnings Year to date total earnings (quota-based earnings plus bonus
earned)
PTD Draw Target Period to date draw
PTD Draw Credit Period to date Draw sales credit
PTD Draw Earnings Period to date draw earnings
PTD Formula Target Period to date formula
PTD Formula Credit Period to date formula credit
PTD Formula Earnings Period to date formula earnings
PTD Quota Target Period to date quota


PTD Quota Credit Period to date sales credit
PTD Quota Earnings Period to date quota-based earnings
PTD Total Earnings Period to date total earnings (quota-based earnings plus bonus)
11.4.7 Commission Statement

The Commission Statement report shows transaction details broken down by
period for a salesperson. It is configurable and for instructions on how to hide or
show selected columns, go to Configuring reports section below. This report can be
navigated to from the Year to Date Summary report for given sales credit and for a
specific plan element.
You can change four fields before displaying the report by selecting from drop-
down lists.
Navigation
Transaction > Report > Commission Statement
Also, you can drill down to this report from the Year to Date Summary.
Parameters

Period Type List of Values Yes
Compensation Category List of Values
Data
commission for during a specified period. The columns visible are controlled by the
System Administrator. You can display up to 12 columns without having to scroll
left or right. Below is a sample of the available columns for this report.
Reports 11-29

Creation Date Creation date
Compensation Category Compensation category
Transaction Type Transaction type
Sales Credit Sales credit
Commission Amount Commission Amount
Credit Receiver Credit Receiver
Attribute1 (-100) Custom attributes
Steps
1. In the Period Type field select Period, Quarter, or Year from the drop-down list.
2. In the Period field select a period.
3. In the Compensation Category field, make a selection. The default setting is All.
4. In the Reporting Currency field, you can select from a list of currencies in
which to display the report.
5. Click Apply to display the report.
Guidelines
After the report is displayed, you can drill down on a amount in the Invoice
Number column to display the Invoice Detail page. This page displays the
following information:
■ Number
■ Payment Type
■ Receipt Date
■ Maturity Date
■ Customer Name

■ From Bank
■ From Account
Payment information includes the following:
■ Currency
■ Payment Amount
■ Amount Applied
■ On Account
■ Unapplied Account
The Line Details area displays eleven columns of information related to the
transaction.
You can click the amount in the Order Number column to display the Order Detail
page. This page shows the following general information:
■ Number
■ Date
■ Type
■ Salesperson
The Order Detail page displays the following shipping information:
■ Ship to Person
■ Ship to Address
■ Ship Method
The area below the shipping information displays billing information:
■ Bill to Person
■ Bill to Address
■ Taxable
■ Currency
■ Freight Terms
■ Total
Reports 11-31
The Line Details area at the bottom of the screen shows nine fields of information
related to the order itself, including the product, quantity ordered, and extended
price.
11.4.8 Unprocessed Transactions

The Unprocessed Transactions report shows all transactions that:
■ Have not been loaded, or
■ Are in the status of Failed Classification, Classified, Rolled Up or Failed Rollup.
You can run this report for any calculation status, load status and adjustment status
for any specified salesperson, date, transaction type, order and invoice number.
This report is configurable and for instructions on how to hide or show selected
columns, go to the Configuring reports section below.
Navigation
Transaction > Report > Unprocessed Transactions
Parameters

Order Number List of Values
Adjustment Status List of Values
Load Status List of Values
Invoice Number List of Values
Processed Date From List of Values
Processed Date To List of Values
Transaction Type List of Values
Adjustment Date List of Values
Calculation Status List of Values

Configuring Reports
Data
commission for during a specified period. The columns visible are controlled by
the System Administrator. You can display up to 12 columns without having to
scroll left or right. Below is a sample of the available columns for this report.

Creation Date Creation date
Process Date Process date
Transaction Type Transaction type
Adjustment Status Adjustment status
Adjustment Date Adjustment date
Adjusted By Adjusted by
Load Status Load status
Calculation Status Calculation status
Sales Credit Sales credit
Attribute 1 (-100) Custom attribute
11.5 Configuring Reports

Each JSP report has a corresponding region in the Applications Core Module. The
information in that region determines what end users see displayed on their screens
in the form of the reports. System Administrators can go into the Application
Developer Common Modules responsibility and configure the JSP reports.
For all 18 reports mentioned below, you can change the name of the column labels
in the report. For example, in the Commission Statement report, you can change the
name of the Salesperson Name column to Partner Name if you are trying to pay
partners. See Steps for Changing Label Names to perform this procedure.
Reports 11-33
Configuring Reports
Three reports can also be configured to hide or display certain columns. These
reports are:
■ Transaction Details
■ Commission Statement
■ Unprocessed Transactions
See Steps for Hiding or Displaying Columns to perform this procedure.
NOTE: Some JSP reports share the same region in the Application Core Module.
Therefore, any changes you make in the region to hide or show a column affect all
reports that reference the same region.
For example, the Commission Summary report and Quota Performance report share
the Quota Summary region name. Also, the Commission Statement report and
Unprocessed Transactions report share the Adjustments Report region.
Steps for Changing Label Names

1. Log in to the Forms version of the application as the System Administrator.
The Navigator - System Administrator screen appears.
2. Click File in the toolbar and select Switch Responsibility.
The Responsibilities screen appears.
3. Select Application Developer Common Modules. Click OK.
The Navigator - Application Developer Common Modules screen appears.
4. Double-click Define Regions.
The Regions screen appears.
5. Query the specific JSP name of report. See Guidelines for a table of specific
Region IDs for the reports. To search, perform the following four steps:
a. With the cursor in the Region ID field, click View in the toolbar and select
Query by Example > Enter from the menus. The fields turn blue.
b. Enter the Region ID of the report. You can enter the first part of the name
followed by a percent sign (%).
c. Click View in the toolbar and select Query by Example > Run in the menus.
The Regions screen appears, displaying a list of Region IDs.
d. Scroll down to the Region ID you want and click in the field.

Configuring Reports
6. Click the Region Items button in the lower right corner.

The Region Items screen appears.
7. Scroll over to the Long Label field and enter a descriptive name for the
attribute.
8. Click Save.
This process changes the label name.
9. Bounce the Middle Tier server.
Steps for Hiding or Displaying Columns

These steps apply only to the Transaction Details, Commission Statement, and
Unprocessed Transactions reports.
1. Log in to the Forms version of the application as the System Administrator.
The Navigator - System Administrator screen appears.
2. Click File in the toolbar and select Switch Responsibility.
The Responsibilities screen appears.
3. Select Application Developer Common Modules. Click OK.
The Navigator - Application Developer Common Modules screen appears.
4. Double-click Define Regions.
The Regions screen appears.
5. Query the specific JSP name of report. See Guidelines for a table of specific
Region IDs for the reports. To search, perform the following four steps:
a. With the cursor in the Region ID field, click View in the toolbar and select
Query by Example > Enter from the menus. The fields turn blue.
b. Enter the Region ID of the report. You can enter the first part of the name
followed by a percent sign (%).
c. Click View in the toolbar and select Query by Example > Run in the menus.
The Regions screen appears, displaying a list of Region IDs.
d. Scroll down to the Region ID you want and click in the field.
6. Click the Region Items button in the lower right corner.
The Region Items screen appears.
Reports 11-35
Configuring Reports
7. Find the Attribute or Column name in the list and then select the Node Display
check box to show the column or deselect the Node Display check box to hide
the column.
8. If you are setting a column to show, scroll over to the V Align column and select
Top from the List of Values.
9. Scroll over to the Long Label field and enter a descriptive name for the
attribute.
10. Click Save.
11. Bounce the Middle Tier server.
Guidelines
The table below displays the Region ID, Region Name, and jsp Name for each
report:
Table 11–1
Report Region ID Region Name jsp Name
Year to Date Summary CN1152_YTD_ Year to Date Summary cnytdsum.jsp
SUMMARY
Transaction Details CN1152_ADJUST_DTL Adjustments Report cnadjdtl.jsp
Report
Compensation Group CN1152_CG_HIER Group Hierarchy Report cncghier.jsp
Hierarchy Report
Classification Rules CN1152_RULES CN1152_RULES cnclrls.jsp
Report
Commission Summary CN1152_QUOTA_ Quota Summary cnquota.jsp
SUMMARY1
Quota Performance CN1152_QUOTA_ Quota Summary cnquota.jsp
SUMMARY1
Commission Statement CN1152_ Adjustments Report cncomm.jsp
COMMISSION
Unprocessed CN1152_ADJUST_DTL Adjustments Report cnunprdl.jsp
Transactions
Quota Model Summary CN_QM_SUMMARY CN QM Summary cnranqms.jsp
Average Quota CN1152_REP_AQS Average Quota cnranaqs.jsp
Summary Summary

Discoverer Workbooks
Table 11–1
Report Region ID Region Name jsp Name
Quota Overassignment CN1152_REP_OAS Overassign Quota Sum cnranoas.jsp
Report
Quota Range Report CN1152_REP_QMR Quota Range Summary cnranqmr.jsp
Compensation Contract CN_ANAL_REP_ Plan Summary Region cnranpsr.jsp
Status PLANSUMMARY
Overlay Report CN1152_REP_OSR Overlay Summary cnrvaosr.jsp
Vacancy Summary CN1152_REP_TBH To be Hired Report cnrvatbh.jsp
Transition Report CN1152_REP_TSR Transitional SP cnrvatsr.jsp
Plan Activation Status CN1152_COMP_GEN_ Plan Generation Status cnrgests.jsp
Report STS
Role to Compensation CN1152_ROLE_PLAN_ Role Plan Mapping cnrgemap.jsp
Plan Mapping MAP
11.6 Discoverer Workbooks

Eight Discoverer workbooks are provided in this release. They are:
■ Section 11.6.1, "Calculation Batch Process Report"
■ Section 11.6.2, "Compensation Plan Revenue Class Mapping"
■ Section 11.6.3, "Resources Not Validated for Calculation"
■ Section 11.6.4, "Resources with Pay Group Assignment Different than
Compensation Plan Dates"
■ Section 11.6.5, "Commission Statement Report"
■ Section 11.6.7, "Formula Definitions"
■ Section 11.6.8, "Resource Assignments Overview"
11.6.1 Calculation Batch Process Report

This workbook allows the monitoring and analysis of batch calculation processes as
they run. Columns include:
■ Batch Number
Reports 11-37
■ Concurrent Manager Phase

■ Calculation Phase
■ Calculation Phase Start Time
■ Calculation Phase End Time
■ Calculation Batch Total Completion Time
11.6.2 Compensation Plan Revenue Class Mapping

This workbook shows, for a given effective date, all plan element and revenue class
assignments for a compensation plan. The workbook can be used to list revenue
classes that identify a compensation plan’s plan elements that will generate
commissions. Columns include:
■ Plan Element Name
■ Revenue Class Name
■ Revenue Class Parent
11.6.3 Resources Not Validated for Calculation

This workbook checks pay group assignment and compensation plan validity for a
specific effective date. There are two worksheets, one for invalid compensation
plans and one for resources without a pay group. This report should be run before
initiating a calculation batch process. Columns include:
■ Analyst Name
■ Resource Name
■ Resource Number
■ Role Name
■ Compensation Plan Name
■ Compensation Plan Start Date
■ Compensation Plan End Date

11.6.4 Resources with Pay Group Assignment Different than Compensation Plan
Dates
This workbook identifies resources whose compensation plan assignments are not
correlated with their pay group assignments. This report should be run before
starting the calculation process. Columns include:
■ Analyst Name
■ Resource Name
■ Resource Number
■ Role Name
■ Pay Group Name
■ Pay Group Start Date
■ Pay Group End Date
11.6.5 Commission Statement Report

This workbook provides transaction details by resource for a specified time period.
It can also be run for a specific analyst for a time period to collect all transactions for
all analyst resources. All transactions that have been calculated successfully are
reported. It displays batch calculation process status. Columns include:
■ Period
■ Invoice Number
■ Invoice Date
■ Order Number
■ Order Date
■ Created Date
■ Plan Element
■ Transaction Type
■ Sales Credit
Reports 11-39
■ Commission
■ Credit Receiver
■ Direct Credit Receiver
■ CN_COMMISSION_HEADERS attributes
■ Total - Sales Credit
■ Total - Commission
11.6.6 Transaction Details Report

This workbook provides transaction details by resource for a specified time period.
It can also be run for a specific analyst for a time period to collect all transactions for
all analyst resources. All transactions are reported irrespective of their status. It
displays the same information as the online version of the report. Columns include:
■ Adjustment Status
■ Calculation Status
■ Transaction Type
■ Invoice Number
■ Invoice Date
■ Order Number
■ Order Date
■ Created Date
■ Processed Date
■ Plan Element
■ Adjusted By
■ Sales Credit
■ Commission
■ Credit Receiver
■ Direct Credit Receiver
■ CN_COMMISSION_HEADERS attributes
■ Total - Sales Credit

■ Total - Commission
11.6.7 Formula Definitions

This workbook shows the details of the calculation formula that is associated with a
resource’s compensation plan. There are two worksheets. One worksheet shows
input and output expressions for calculation and another worksheet shows input
and output expressions used for forecasting. The worksheets identify all incomplete
formulas that have been assigned to resources and also identifies all formulas that
utilize a specific expression. Columns include:
■ Compensation Plan Element Name
■ Formula Name
■ Formula Type
■ Formula Status
■ Apply Transactions
■ Split
■ Cumulative
■ Interval to Date
■ Planning
■ Input Expression Name
■ Output Expression Name
■ Performance Measure
■ Rate Table Name
11.6.8 Resource Assignments Overview

This report captures all of the assignments that a resource has: compensation group,
role, compensation plan, pay group, analyst, and effective date assignments for
resources. Columns include:
■ Analyst Name
■ Resource Name
■ Resource Number
Reports 11-41
■ Resource Start Date

■ Resource End Date
■ Resource Hold Flag
■ Pay Group Name
■ Pay Group Start Date
■ Role Name
■ Role Start Date
■ Role End Date
■ Compensation Group Name
■ Compensation Group Start Date
■ Compensation Group End Date

Part V
Administration
This part contains the following chapter:

■ Chapter 12, "Administration"
12
Administration

■ Section 12.2, "System Parameters"
■ Section 12.3, "Tables"
■ Section 12.4, "External Table Join Conditions"
■ Section 12.5, "Accumulation Periods"
■ Section 12.6, "Pay Periods"
■ Section 12.7, "Interval Types"
■ Section 12.8, "Revenue Class"
■ Section 12.9, "Rulesets"
■ Section 12.10, "Hierarchy Types"
■ Section 12.11, "Credit Types"
■ Section 12.12, "Credit Conversion"
■ Section 12.13, "Collection"
■ Section 12.14, "Pay Groups"
■ Chapter 12.15, "Payment Plan"
■ Section 12.16, "Payroll"
■ Section 12.17, "Components"
■ Chapter 12.18, "Attainment"
■ Section 12.19, "Job Titles"
■ Section 12.20, "User Access"
Administration 12-1
Overview of Administration
■ Section 12.21, "Settings"

■ Chapter 12.22, "Seasonality Schedules"
■ Section 12.23, "Rate Dimensions"
12.1 Overview of Administration

The Administration tab is home to many of the setups in Oracle Incentive
Compensation. For example, this is where pay periods, quota components,
seasonality schedules, and other essentials of the Incentive Compensation process
are defined.
In some cases, such as system parameters, the set of books is defined in Oracle
General Ledger but is selected in the Administration tab for Oracle Incentive
Compensation purposes.
In this chapter, for easy reference, the setups are listed in the order in which they
appear on the Administration tab, Incentive subtab.
12.2 System Parameters

This page is used to define the basic parameters of Oracle Incentive Compensation.
It is divided into five sections:
■ Section 12.2.1, "General": Where you define the name of the instance and select
from existing revenue class hierarchies.
■ Section 12.2.2, "General Ledger": Where you select a set of books, which
identifies a company or fund within Oracle Applications that shares a common
chart of accounts, structure, calendar, and functional currency.
■ Section 12.2.3, "Collection": Where you control performance settings, including
Collection Batch Size and Transfer Batch Size, and Takeback grace days.
■ Section 12.2.4, "Calculation": Where you make five settings, four of which affect
calculation performance, including Transaction Batch Size, latest processed
date, Salesperson Batch Size, and Managerial Rollup.
■ Section 12.2.5, "Payment": Where you indicate whether Oracle Payroll and
Oracle Payables are implemented, and set the level of account code generation.
Navigation
Administration > Incentive > Parameter

System Parameters
12.2.1 General
1. Enter the name of your Oracle Incentive Compensation instance.
2. Select a Revenue Class Hierarchy from the list of values.
12.2.2 General Ledger

A set of books identifies a company or fund within Oracle Applications that shares
a common chart of accounts, structure, calendar, and functional currency. Oracle
Incentive Compensation processes sales compensation payments according to
periods defined in a calendar associated with a set of books that are defined in
Oracle General Ledger (see Oracle General Ledger Reference).
Prerequisites
None
Steps
1. In the Set of Books field, choose a GL set of books from the list of values, which
Oracle Incentive Compensation obtains from all sets of books that have been
defined.
2. You will then see displayed this information obtained from the GL books:
■ Currency associated with this set of books (view only, cannot be edited)
■ Calendar associated with this set of GL books (view only, cannot be edited)
■ Period Type associated with this set of GL books (view only)
12.2.3 Collection
Steps
1. Select a Collection Batch Size. This affects the amount of time the application
requires to process the total transactions.
2. Select a Transfer Batch Size.
3. Select the number of Clawback Grace Days. This determines the number of
days allowed after the payment due date before sales credit is taken back.
Administration 12-3
System Parameters
12.2.4 Calculation
Within the Calculation area of the System Parameters page, there are five fields.
Four of the fields may affect calculation and its performance: Transaction Batch Size,
Latest Processed Date, Salesperson Batch Size, and Managerial Rollup. A fifth field
included under calculation, Rule Batch Size, does not affect calculation in any way.
This option is used when creating the Classification Rules Package.
The Transaction Batch Size and Salesperson Batch Size together determine how
many transaction batch runners get submitted for concurrent calulation.
Nonconcurrent calculation always uses one batch. During the transaction batch
processor phase, Oracle Incentive Compensation determines how many batches will
be run for the concurrent calculation process. For example, if you want to calculate
10,000 transactions and the batch size is 1,000, ten batches will be created.
The salespeople are first assigned to a PHYSICAL_BATCH_ID based on the
transaction batch size and salespeople batch size as defined on the System
Parameters page. During the assignment, calculation moves through each of the
salesrep_id sequentially (for example, 1000, 1001, 1002, 1010, and so on).
Calculation assigns each salesperson to a single physical_batch_id. It does not split
the salesperson across two batches.
Note: A good starting point for setting the values for salesperson batch size is a
rough equivalent to the maximum number of concurrent manager slots and the
number of server processors available. You can then fine tune the numbers to get
the best setting for your setup.
The Latest Processed Date field is a view-only field that indicates the date of the
latest transaction for which calculation has been run. If the system profile OSC:
Prior Adjustment is set to no, it allows all plan elements in a period to be calculated
incrementally. Before enabling the profile option, be sure that any transactions that
have a processed date earlier than the latest processed date showin in the System
Parameter window have been calculated.
Check the Managerial Rollup check box if you want sales credits to roll up through
the compensation group hierarchies. If the box is checked, Oracle Incentive
Compensation awards indirect credit for each transaction whose direct credit
receiver is in the compensation group hierarchy. This parameter affects all
transactions--you cannot selectively allocate indirect credit on a
transaction-by-transaction basis.

System Parameters
Steps
1. Configure a transaction batch size that is appropriate to your calculation
requirements.
2. Configure a salesperson batch size that is appropriate to your calculation
requirements.
3. Check the Managerial Rollup check box if you want sales credits to roll up
through the compensation group hierarchies.
12.2.5 Payment
Steps
1. Indicate whether Oracle Payable and Payroll are implemented.
2. Use the Account Generation field to instruct the application from what level
you want account codes to be generated. Select Revenue Class, Plan Element,
Custom, or Classification from the drop-down list.
Guidelines
Account Generation is an option you can use to populate account codes at the
appropriate detail level and then select from where the application pulls expense
and liability information.
There are four levels of detail where population can occur:
■ Classification - The application takes expense and liability accounts that are
provided on the Ruleset Details page and passes that information to Accounts
Payable.
■ Plan Element - The application takes expense and liability accounts that are
provided on the Plan Element page and passes that information to Accounts
Payable.
■ Revenue Class - The application takes expense and liability accounts that are
provided on the Revenue Class Summary page and passes that information to
Accounts Payable.
■ Custom - The Custom option provides flexibility for companies that want to
pass along expense and liability data which are independent of the normal
Oracle Incentive Compensation classification process. Mapping to this data is
required.
Administration 12-5
System Parameters
Account Generation is set at the application level. Once it is set, the application
obtains all of the information from only that level. This means that regardless of
where you populate data, if it doesn’t match the system option, it cannot be used.
For example, if you set the system parameter to Plan Element and begin populating
expense and liability account information at the Revenue Class level, the
application ignores whatever you enter at the Revenue Class level.
If you select the Classification level from the Account Generation drop-down list,
you must perform the following setup, which is similar to the current classification
Ruleset procedure:
Steps
1. Click the Administration tab and click the Incentive tab.
2. In the side panel menu, click Ruleset.
The Rulesets page appears.
3. Define the name of the ruleset
4. Enter a start date and an end date for the ruleset. Click the calendar icons to
open pop-up calendars.
5. Select the type of Account Generation from the drop-down list.
7. Click Rules in the Rules column.
The Rules Hierarchy page appears.
8. Click the name of the rule to go to the Create Rules page.
9. On the Create Rules page, click Create Child.
10. Assign a name to the rule that you are about to define.
11. Click Go to choose a revenue class from the list of values.
12. On the Rule Attributes tab, choose a user column name from the list of values,
choose the type of values from the drop-down list, and enter the value or values
that apply.
13. Optionally, enter additional attributes for the rule.
Note: Every attribute is assumed to be linked to other attributes with AND. If
you want any of the attributes to be related with OR, use the Build Expression
tab to relate the first two attributes with AND or OR.

Tables
14. An additional value of Result1 appears in the first column and is added to the
attribute list of values.
15. Continue to relate the remaining attributes. Use Result1 to relate a third
attribute to the first two.
16. Save the rule.
The expression appears.
17. To add rules in the rules hierarchy, position your cursor over the parent rule,
right click, and choose New Rule. Repeat from step 2.
18. Return to the Ruleset form for every ruleset that has new or changed rules and
click Synchronize.
Guidelines
The application checks to see what account generator level has been set. Based on
this level, the appropriate Accounts Payable accounts are associated to the line item.
The three levels are as follows:
Revenue Class: Each revenue class will be assigned a specific liability and expense
account. This option should be used if tracking expenses for each product is
required.
Plan Element: Each plan element can be assigned a specific liability and expense
account. This option should be used if all products assigned to the plan element will
be assigned to the same expense and liability account.
Classification: An entire rule can be assigned a specific liability and expense
account.
12.3 Tables
Use the Tables page to define tables from Accounts Receivable, Order Management,
or an external source that are used in collecting and calculating transactions in
Incentive Compensation. Tables must be defined before they can be used in
collection or calculation. To define tables, perform the following procedure.
Navigation
Administration > Incentive > Tables
Administration 12-7
Tables
Prerequisites
Tables must exist in the database.
Steps
2. Click the Tables link in the side panel menu.
3. The Tables page appears.
4. If you want, enter search parameters by Schema, Table Name, or User Name.
5. Click Apply.
6. Enter a Schema in the Schema field. Click Go to open a pop-up list from which
to select a name.
7. Enter a Table Name from which you want to collect data. Use the pop-up list if
necessary.
8. Enter a User Name.
9. Enter a description if desired.
10. In the Usage column, select Collection, Calculation, or None from the drop-
down list.
12. Use the details field to add any useful information. Click Columns in the details
column to go to the Columns page.
12.3.1 Columns
After you have defined tables for collection or calculation, use the Columns page to
define specific columns and relate them to columns in other tables.
There are four views of the Columns page, selected from the View drop-down list at
the top of the page. The four views have different fields of information that can be
entered.
■ The Columns view displays the column data type and data length, and contains
check boxes for Usage and Foreign Key.

Tables
■ The Dimensions view contains a field for Dimension Name and a Value check
box.
■ The Classification view provides a Value check box, enables classification as
alphanumeric, date, or numeric, and contains a field for selecting a value set
name.
■ The Primary Key view supplies a Primary Key check box. The Position column
is not used in the current release.
All four views contain the column name, the user name assigned to it, and a field
for an external call. The external call column is used only in the Column view. The
column name is set in the application, but you can assign a user name to it to match
your business process or for ease of use.
The external call column enables you to optionally enter the name of a jsp, which is
then invoked by Oracle Incentive Compensation as the source of data for the
Invoice Number and Order Number fields in the Commission Statement report. For
the Commission Statement drilldown to work, the Enable Commission Statement
Drilldowns profile should be set to Yes.
Navigation
Administration > Incentive > Tables > Columns
Prerequisites
None
Steps
1. The Columns view is the default display. To use a different view, select it from
the View drop-down list.
2. To use the Columns view, click Apply.
The Columns page display changes to the view you have selected.
3. For the Columns view, perform the following steps:
a. Change the name in the User Name field to assign a name that is used in
your business or is easy to understand.
b. Optionally, enter an external call (see previous information in this section).
c. The Data Type field indicates if the column contains alphanumeric material
(VARCHAR2), numerical data (NUMBER), or a date (DATE).
Administration 12-9
Tables
d. Check the Usage check box if you plan to use the column for calculation.
e. Check the Foreign Key check box if you plan to use the column as a foreign
key to relate the column to columns in another table.
f. Click Update to save your changes. If necessary, click Restore to return to
the previously stored information.
4. For the Dimensions view, perform the following steps:
b. Select a dimension name. Enter four or more characters in the Dimension
Name field and click Go. A pop-up list appears from which you can make a
selection.
c. Check the Value check box next to the column to use that column’s value as
the basis for defining the hierarchy of the selected dimension.
d. Click Update to save your changes. If necessary, click Restore to return to
5. For the Classification view, perform the following steps:
b. Check the Value check box next to a column to use that column for defining
classification rules.
c. Make a selection from the Classification drop-down list. Choices include
Alpha Numeric, Date, or Numeric.
d. Optionally, enter a name in the Value Set Name field. Enter four or more
characters in the Dimension Name field and click Go. A pop-up list appears
from which you can make a selection.
e. Click Update to save your changes. If necessary, click Restore to return to
6. For the Primary key view, perform the following steps:
a. You can change the name in the User Name field to assign a name that is
used in your business or is easy to understand.
b. Optionally, check the Primary Key check box. If a column is enabled as the
primary key, it will be used in the join condition with an external table
when doing an external table join.

External Table Join Conditions
c. Click Update to save your changes. If necessary, click Restore to return to

12.4 External Table Join Conditions

Sometimes the information you need is located on a table that is not in Oracle
Incentive Compensation. Use this page to join external tables to destination tables in
Oracle Incentive Compensation.
Navigation
Administration >Incentive > External Table
Steps
2. Click the External Table link in the side panel menu.
The External Table Join Conditions page appears.
3. If the list is long, you can search for a join condition by entering a search string
in the Name field at the top and clicking Apply. Note: This search is case sensitive.
4. Enter a name for the condition in the Name column. This is a required field.
5. In the Usage column, select Collection or Calculation from the drop-down list.
This is a required field.
6. Enter the source table. You can click Go to open a pop-up list. Click your
selection to enter it into the field.
7. The Alias is system generated.
8. Enter a name of the destination table in Oracle Incentive Compensation. Click
Go to open a pop-up list from which to make a selection.
9. Click Columns in the External Columns column to another page where you can
specify source and destination columns.
10. If you want to remove a line, check the Remove check box and the line will be
deleted the next time Update is clicked.
Administration 12-11
Accumulation Periods
12.4.1 External Table Join Conditions - External Columns

Use this page to indicate which external columns to use from an external table. The
table join conditions are defined on the External Table Join Conditions page.
Navigation
Administration > Incentive > External Table
Prerequisites
External Tables must be joined.
Steps
2. Click the External Table link in the side panel menu.
The External Table Join Conditions page appears.
3. Enter a source column name from an external table in the left hand column.
Click Go to search. You must enter a minimum of four characters. Choose a
column name from the results in the Select pop-up window.
4. Enter a destination column name in the right hand column.
This column uses the same search method as in step 1.
5. Continue adding pairs of columns as necessary.
6. Click Update to save your work. Click Restore to return to the previously saved
information.
12.5 Accumulation Periods

Use the Accumulation Periods page to select the period status of your accumulation
periods, verify their Status, or freeze them so they can be opened for a Year-to-Date
Summary or Commission Statement by a salesperson using Oracle Sales Online.
Most of the Accumulation Periods page is read-only information. Only the Period
Status and Freeze columns are changeable.
The period status can be set to Future Enterable, Open, Closed, or Permanently
Closed. If a period is permanently closed, it cannot be opened.

Pay Periods
Navigation
Administration > Incentive > Accumulation Period
Prerequisites
None.
Steps
2. Click the Accumulation Period link in the side panel menu.
The Accumulation Periods page appears.
3. Select a year from the drop-down list and click Apply.
The accumulation periods for the selected year are displayed.
4. Change the period status by selecting Open, Closed, or Permanently Closed
from the drop-down list.
5. Optionally, check the Freeze check box to enable a Year To Date summary.
6. Click Update to save your changes. Before you save by clicking Update, you
can click Restore to return to the most recently saved information.
Guidelines
You cannot close a period if there is a period before it that is open. For example, you
cannot close the June 2002 period if the March 2002 period remains open. If you
attempt to close a period that has an open period before it, a message displays at the
top of the page:
Cannot close a period when previous period is not closed.
If this occurs, click the browser’s back button and close any previous open periods.
You cannot open a period if the previous period is in Never Opened status.
When you are updating or changing accumulation periods to Open, update only
one date range at a time. Wait until the status changes from In Progress to Open
before changing the next date range.
12.6 Pay Periods

This page displays essential information about pay periods that have been set up
for a particular calendar and enables you to activate a period.
Interval Types
Navigation
Administration > Incentive > Pay Periods
Prerequisites
Pay periods are set up already.
Steps
2. Click the Pay Periods link in the side panel menu.
The Pay Periods page appears.
3. Select a calendar from the drop-down list.
4. Click Apply.
5. Activate a pay period that is currently inactive by selecting Active from the
drop-down list in the Period Status column.
Note: Active periods cannot be deactivated from this window.
6. If desired, select Previous Year or Next Year to view earlier or later pay periods.
7. Optionally, click Restore to return to the previously saved data.
12.7 Interval Types

Intervals are used to set the time period during which commission is calculated.
This page displays all intervals that have been created and enables creation of new
intervals.
12.7.1 To View an Interval Type

To view an interval type, perform one of the following procedures.
Navigation
Administration > Incentive > Interval Types
Prerequisites
None.

Interval Types
Steps
2. Click the Interval Types link in the side panel menu.
The Interval Types page appears.
3. To view details of an already created interval in the Name column click the
name of the interval.
The Interval Numbers page appears. It shows the interval numbers based on
the parameters of your selected interval. For example, If you selected a Quarter
interval, with a period of a Month, the months of January, February, and March
will display the same interval number.
Guidelines
As an example, for quarterly intervals:
JAN-01, FEB-01, MAR-01 are all numbered 2001001
APR-01, MAY-01, JUN-01 are all numbered 2001002, and so on.
For Monthly intervals:
JAN-01 is numbered 2001001
FEB-01 is numbered 2001002
MAR-01 is numbered 2001003, and so on.
Interval numbers are user definable.
12.7.2 To Create a New Interval Type
Navigation
Administration > Incentive > Interval Types
Prerequisites
None.
Steps
2. Click the Interval Types link in the side panel menu.
Revenue Class
The Interval Types page appears.

3. Click Create.
4. Enter a name and description for the new interval.
5. If needed, click Restore to return to the previously saved information.
12.8 Revenue Class

Revenue classes are user-defined categories of business revenue used to determine
whether sales credit is applied toward a compensation payment. Revenue classes
are placed in hierarchies composed of broader revenue classes at the top, or root,
with subclasses as children of the root. A revenue class hierarchy makes it possible
to pay compensation for broader revenue classes without specifying all possible
subclasses in a compensation plan.
Perform the following procedure to define a revenue class.
Navigation
Administration > Incentive > Revenue Class
Prerequisites
None.
Steps
2. Click the Revenue Class link in the side panel menu.
The Revenue Class page displays all revenue classes that have been already
been defined.
3. To define a new revenue class, enter the name in the first blank Name field.
4. Optionally, enter a description. The description often is the same as the name.
5. Select a Liability Code and Expense Code if needed to integrate with Accounts
Payable.
6. To search for liability codes and expense codes, click Go to open a pop-up list.
Use sort parameters in the field to narrow your search.

Rulesets
A Confirmation message displays across the top of the page when the save is
successful.
8. To define a revenue class hierarchy, start at the Hierarchy Types page. That is
also the place to add or delete nodes of the hierarchy.
12.9 Rulesets
A classification ruleset is used to classify sales transactions to determine the
appropriate revenue class for the transaction. Then, using the revenue class, a
transaction is matched with a compensation plan and a compensation amount to be
paid for the transaction is calculated.
Rulesets are of two types, Revenue Classification and Account Generation.
■ Revenue Classification defines the rules that are used to identify a revenue class
for each transaction that the system processes as part of calculating
commissions.
■ Account Generation is used to integrate Oracle Incentive Compensation
automatically with Accounts Payable and to classify transactions to identify
Expense and Liability Accounts.
Create a rules hierarchy that accurately reflects your business requirements. Name
your rules after the revenue classes they describe. Rules do not require unique
names.
The Rulesets page lists all rulesets that have already been created. To view or edit a
ruleset, find it and click Rules. Or, use the Saved Searches drop-down list. Click
Personalize to create a custom search.
Use the following procedure to create a revenue classification ruleset and account
generation rulesets for integration with Accounts Payable.
Navigation
Administration > Incentive > Ruleset
Prerequisites
Revenue Classes have been created and the user-defined flexfields of the CN_
COMMISSION_HEADERS table have been defined.
Rulesets
Steps
2. Click the Ruleset link in the side panel menu.
3. In the first blank field in the Ruleset Name column, enter the name of the new
ruleset.
4. Enter a start and an end date for the ruleset. Click the calendar icons to open
pop-up calendars. These fields are required.
5. Select Revenue Classification from the Ruleset Type drop-down list. This is a
required field.
6. Click Update to save your ruleset.
Note: If the ruleset dates overlap the dates of another ruleset, an error message
displays at the top of the page and you cannot continue with creating the
ruleset.
7. Click the Rules link in the Rules column to display the Rules Hierarchy. See
Section 12.9.1, "Rules Hierarchy" for complete information on this page.
Guidelines
You can define multiple date-effective classification rulesets. Ruleset active dates
may not overlap.
When you make changes to a ruleset, you must synchronize it. When you check the
Synchronize check box and click Update, the application generates a database
package based on the revenue classes and revenue class rules and saves it in an
internal table. Before the status changes from Incomplete to Complete, it may
display Install Pending. You do not need to synchronize a ruleset if you only
rearranged the rules but did not otherwise change them.
A hierarchy of rules can be defined for each ruleset.
Every rule must have at least one attribute.
You can build expressions on the rules using the Build Expression page.
A rule may or may not have a revenue class. If the rule does not have a revenue
class, then its children rules must define the revenue class. If a rule has a revenue
class, then the revenue class is assigned to the transaction only if none of its child
rules match the transaction.

Rulesets
If you specify high and low values in a rule condition, the values can be
alphanumeric.
Every attribute is assumed to be linked to other attributes with AND. If you want
any of the attributes to be related with OR, use the Build Expression page to relate
the first two attributes with AND or OR.
Selecting the Hierarchy Values option allows you to enter the value in the hierarchy
you want to match. The fields that appear are Hierarchy and Hierarchy Values. If
the value of the transaction attribute rolls up the hierarchy to the value you specify,
then the compensation transaction satisfies the condition.
You can specify the exclusion of a value you defined by checking the Not check box.
The compensation transaction satisfies the condition if the attribute is not equal to
the specified value, is not between the range of values specified, or does not roll up
to the specified ancestor value.
Always customize the classification rules using the setup forms available. Do not
modify the generated PL/SQL code.
Troubleshooting
When a transaction fails classification for a rule that uses hierarchy values, the most
common problem is that the primary key value in the transaction attribute column
is not the same as the primary key value defined in the hierarchy (the value for the
EXTERNAL_ID field).
12.9.1 Rules Hierarchy

A rules hierarchy sets up relationships between rules. The structure of a rules
hierarchy starts with a root, then adds one or more parent rules, and then as many
child rules as needed. A rule can have one or more child rules or siblings.
To create rules and add them to the rules hierarchy, perform the following
procedure:
Navigation
Administration > Incentive > Ruleset > Click Rules link
Prerequisites
Classification Ruleset has been created.
Rulesets
Steps
3. Click the Rules link in the Rules column.
4. In the lower section of the Rules Hierarchy page, select Root from the Add Rule
column drop-down list.
5. Name the rule.
6. To assign the rule a revenue class name, enter at least four characters in the
Revenue Class Name field and clicking Go. Click the revenue class from the list
generated by the search. This step is optional. See Guidelines.
7. Click Update. The rule is displayed in the upper table of the Rules Hierarchy
page. A confirmation message appears at the top of the page.
8. To define attributes for the rule, click Attributes in the Rule Attributes column
next to the rule.
The Rule Attributes page appears. See Chapter 12.9.3, "Rule Attributes" for
more information.
9. To get to the Build Expression page, click Expressions in the Rule Expression
column. See Guidelines.
The Build Expression page appears.
10. If necessary, click Restore to return to the most recently saved information.
12.9.2 Create Rules

The Create Rules page enables you to create a child or sibling to a rule on the Rules
Hierarchy page. In this version of Oracle Incentive Compensation, this can also be
done on the Rules Hierarchy page itself.
Navigation
Administration > Incentive > Ruleset > Rules Hierarchy > Click Rule Name link
Prerequisites
Ruleset must be created.

Rulesets
Steps
4. Click the link in the Rule Name column.
5. The Create Rules page appears.
6. Click Create Child or Create Sibling.
7. In the Rule name field, assign a name to the rule that you are about to define.
8. Enter a revenue class in the Revenue Class Name field. You can click Go to
open a pop-up window. Click a name on the list.
12.9.3 Rule Attributes

Use the Rule Attributes page to assign single value, range value, and hierarchy
attributes to rules. This page can be accessed from the Attributes link on the Rules
Hierarchy page.
Navigation
Administration > Incentive > Ruleset > Rules Hierarchy > Click Rule Attributes link
Prerequisites
Steps
Rulesets
4. Click the Attributes link in the Rule Attributes column.

The Rule Attributes page appears.
5. In each of the three areas, enter four or more characters in the Attribute field
and click Go to open a pop-up window list from which to select an attribute.
6. For the Single Value attributes, enter a value in the Value field.
7. For Range Value attributes, enter a low value and a high value in the fields.
8. For Hierarchy values, enter a hierarchy and a value. For the Hierarchy and
Value fields you can enter four or more characters and click Go to open a list of
values.
9. Each area has a Not Flag column containing a check box. Check the check box
to indicate that you want to exclude that value from the rule. See Guidelines.
10. Every attribute is assumed to be linked to other attributes with AND. If you
want any of the attributes to be related with OR, use the Build Expression tab to
relate the first two attributes with AND or OR.
11. If necessary, click Restore to return to the most recently saved information.
12. Click Update to save your attributes.
12.9.4 Build Expression

Use the Build Expression page to create expressions for use in linking attributes in
rules. All expressions require two operands and an operator. To build an expression,
Navigation
Administration > Incentive > Ruleset > Rules Hierarchy > Click Expressions link
Prerequisites
The rule must have two or more attributes in order to enable the Build Expressions
link.
Steps

Hierarchy Types

4. Click the Expressions link in the Rule Expressions column.
The Build Expression page appears.
5. To delete an expression, select it and click Delete Expression.
If you delete an expression by mistake, click Restore immediately, before
saving, to return it to the list.
6. Enter Operand1 and Operand 2. Enter search parameters and click Go to open a
pop-up list. Click your selection from the list displayed.
7. Select an Operand from the drop-down list.
9. Click Build Expression to save your work.
12.10 Hierarchy Types

The Hierarchy Types page lists the types of hierarchies used in Oracle Incentive
Compensation by name, along with Base Table, Primary Key, and Hierarchy Values,
which are all required fields. To define a hierarchy, perform the following
procedure.
Navigation
Administration > Incentive > Hierarchy
Prerequisites
Dimension Base table, primary key, and hierarchy values must exist.
Steps
2. Click Hierarchy in the side panel menu.
The Hierarchy Types page appears.
3. In the first blank Name field, enter the name of the new hierarchy.
4. Add the correct Base Table, Primary Key, and Hierarchy Values information.
Hierarchy Types
5. Click Go to open a pop-up list. Use search parameters, followed by a percent

sign (%), in the fields to narrow your search. Four characters are required to
perform a search. You must know at least four characters of the value.
8. To add nodes to the hierarchy,
a. Click the Details link on the Hierarchy Types page to go to the Hierarchies
detail page.
b. On the Hierarchies page, click the Details link to go to the Intervals page to
find the hierarchy.
c. On the Intervals page, assign a start date and an end date. Click the Details
link to go to the Hierarchies page, where the nodes can be added.
12.10.1 Hierarchies Detail

This page, called Hierarchies, displays the name of a hierarchy with a details link.
Navigation
Administration > Incentive > Hierarchy > Details link
Prerequisites
At least one hierarchy must exist.
3. To remove a hierarchy, check the Remove check box.
4. If necessary, click Restore to return to the previously stored information
6. Click the Details link to go to the Intervals page (following).
12.10.2 Intervals
This page shows start and end dates, among the name of the root node, for a
hierarchy. Perform the following procedure to make changes to hierarchy intervals.

Hierarchy Types
Navigation
Administration >Incentive > Hierarchy > Hierarchies > Details link
Prerequisites
Hierarchy must be created.
Steps
3. Click the Details link to go to the Hierarchies page.
4. Click the Details link to go to the Intervals page.
5. To enter or change Start Date an End Date fields, type in new dates or use the
calendar icon at the right of the field. Click the icon to open a pop-up calendar.
6. Click Details to go to the Hierarchies page. This page is different from the
Hierarchies detail page. This Hierarchies page is where new nodes can be
added to or deleted from a hierarchy.
7. Check the Remove check box to remove an interval.
12.10.3 Adding and Deleting Hierarchy Nodes

Use this procedure to define the parent-child relationship between all nodes in a
hierarchy. You can add nodes to or delete nodes from a hierarchy.
Navigation
Administration >Incentive > Hierarchy > Hierarchies > Intervals > Hierarchies
Prerequisites
Hierarchy must be created.
Steps
Hierarchy Types

3. Click the Details link to go to the Hierarchies page.
4. Click the Details link to go to the Intervals page.
5. Click the Details link to go to the Hierarchies page (not the same page as in step
3).
6. To enter or change Start Date an End Date fields, type in new dates or use the
calendar icon at the right of the field. Click the icon to open a pop-up calendar.
7. Click Details to go to the Hierarchies page. This page is different from the
Hierarchies detail page. This Hierarchies page is where new nodes can be
added to or deleted from a hierarchy.
Guidelines
Root node is the highest level of the hierarchy. In Oracle Incentive Compensation,
you can place as many nodes under the root node as necessary to meet the business
objective. Oracle Incentive Compensation provides you with the flexibility of
creating multiple root nodes. For example, you can create a root node for France
Products and another for Germany Products.
A parent node is a node that has at least one node that rolls up to it. A parent node
typically summarizes information concerning the nodes below it, referred to as
child nodes. An example of a parent node would be Western States and under it
child nodes called California, Oregon and Washington.
A child node rolls up to a parent node. A child node can roll up to only one parent
node. For example, under the parent node of California the child nodes could be
called San Francisco and Los Angeles.
You can create a new hierarchy under an existing hierarchy type, or you can create a
new hierarchy type and then build the hierarchy there. To create a hierarchy in a
new hierarchy type, perform the following procedure. For more information on the
structure of a hierarchy, see Guidelines.
This process is performed on the Hierarchies page, which is the main page for the
hierarchy tree. To see a list of all the hierarchies in your implementation of Oracle
Incentive Compensation, see Section 12.10, "Hierarchy Types".

Hierarchy Types
Steps for Adding Nodes

1. Starting at the Base Node, enter the names of all children of this node. Use the
list of values to select the children.
2. To add a child node to the Base Node, or to any node, click the button in the
Child column next to that node.
3. To define the next level in the hierarchy, click the plus sign in the hierarchy to
open the child node below it.
The child moves to the Current Node position and the application displays the
children of the new parent, if they exist.
4. Enter the names of all children of this parent.
a. Use the Add Child field to select child nodes.
b. Click Go to open a pop-up list.
5. Repeat steps 2 through 4 to define all nodes in the hierarchy.
Guidelines
By default, Oracle Incentive Compensation names the highest level root of every
hierarchy base node. You can change this name.
You can create as many hierarchies as you need. However, only one hierarchy can
be effective at any given time.
Steps for Deleting Nodes

1. Expand the nodes by clicking the plus sign to the left of their names to get to
the node that you want to delete.
1. Check the check box in the Remove column next to node.
3. Click Update to save your deletion. See Guidelines for important information.
Guidelines
Hierarchy deletes are cascading. This means that if you delete a node, all children of
that node are deleted along with it.
Credit Types
You can import any portion of another hierarchy to become a child of your selected
node in the hierarchy you are building.
12.11 Credit Types

Use the Credit Types page to define all credit types to be used in Oracle Incentive
Compensation. Credit types include Functional Currency, points, air miles, or any
custom form of credit that you want. These definitions are optional, and
non-monetary credits must be converted to functional currency to be paid. To view,
change, or remove a credit type, perform the following procedure.
Navigation
Administration > Incentive > Credit Type
Prerequisites
None
Steps
2. Click the Credit Type link in the side panel menu.
The Credit Types page appears.
3. Use the search parameters at the top of the page if necessary.
4. Change the values in the Precision and Extended Precision fields if needed.
Precision defines how fine a grain the credit type can be divided.
5. The Functional Currency cannot be changed by the user.
6. If desired, check the Remove check box next to a credit type to remove it from
the listing.
To add a new credit type, perform the following procedure.
Steps
1. Enter a name for your credit type into the Name column in the topmost empty
row.

Credit Conversion
Click the eraser icon to erase any mistakes in the current row as you work.
2. Enter precision and extended precision information.
12.12 Credit Conversion

Use the Conversion Factor page to set conversion factors for converting one credit
type to another, such as setting the conversion rate between the nonmonetary credit
type and the functional currency. The credit types are defined using the Credit
Types page.
Navigation
Administration > Incentive > Credit Conversion
Prerequisites
None
Steps
2. Click the Credit Conversion link in the side panel menu.
The Credit Conversion page appears.
3. Enter a credit type in the From Credit Type column.
Click Go to select from a list of values.
4. In the To Credit Type Column, indicate the credit type to which you want to
convert the credit.
Click Go to select from a list of values.
5. Enter a conversion factor. For example, $100 credit can equal 10,000 Air Miles.
6. Enter effective dates in the Start Date and End Date fields.
7. To return to the previously saved version, click Restore.
Collection
12.13 Collection
For all information on Collection setups on the Incentive subtab of the
Administration tab, see Chapter 8, "Collecting and Adjusting Transactions".
12.14 Pay Groups

A pay group defines the frequency of payments, such as monthly or semi-monthly,
for the salespeople who are assigned to the pay group. Use this procedure to define
pay groups.
Navigation
Administration > Incentive > Pay Group
Prerequisites
Calendars and related pay periods must be defined in GL and activated in Oracle
Incentive Compensation. (See Oracle Incentive Compensation Implementation Guide.)
Steps
The Pay Groups page lists all pay groups that have already been created. Use the
search parameter fields at the top to search for a pay group.
2. Click the Pay Group link on the side panel menu.
The Pay Groups page appears.
3. Enter a name, date range, or calendar name. You can use partial entries in the
name and calendar fields followed by a percent sign (%).
4. Click Apply.
5. In the Name field, assign a unique name to the pay group.
6. Enter a description.
7. Select an effective start date and end date for the pay group. Click the calendar
icon to use the pop-up calendar.
8. Select a calendar from the list of values. Click Go to open a pop-up window list.
9. Select a period type from the list of period types that were defined for the
selected calendar. Click Go to open a pop-up window list.

Payment Plan
11. Click Update to save the pay group.
Guidelines
The period type defines the frequency of payments for the pay group. Even if a
period type, such as quarter or year, is displayed in the list of values, it must be
activated in Oracle Incentive Compensation before it can be used.
Note: In this release of Oracle Incentive Compensation, the period type must be set
to Month for values to roll over to the next year in Year to Date reports.
Each pay group can have one or many pay periods. A pay period is a range of dates
over which calculated commissions are summarized for payment.
Each pay group can be associated with one unpaid pay run at any time.
Pay groups can be assigned to multiple resources at the same time and you can start
and end pay group assignments by individual resource at any time within the
duration of the pay group. Therefore, the application does not default any dates in
the Resource Details > Assign Pay Groups table in the Resource tab.
When you assigned a pay group to a resource, the application automatically checks
to see if there are any conflicts between the start and end dates of the pay group and
the start and end dates for every resource to which the pay group has been
assigned. For example, if you define a pay group starting Jan 1 and ending on Mar
31 and you have assigned it to a resource, the application will not let you change the
end date for the pay group assignment beyond Mar 31.
See Resource > Resource Details > Assign Pay Groups to assign the pay group to
resources.
12.15 Payment Plan

Oracle Incentive Compensation uses payment plans to set rules governing how
much is paid. Payment plans are optional and are used to set up advance or
deferred payments and to define minimum and maximum payments.
The recovery schedule and draw amount can be set up independently of the
earnings for the period, and you can waive a recovery amount due from a
salesperson. Note: For Waive Recovery to work properly, the pay periods must be
defined correctly.
Payment Plan
The Payment Plans page lists all payment plans already defined in Oracle Incentive
Compensation. To search for a plan, enter all or part of the name in the Name field
at the top of the page and click Apply.
To define a new payment plan, perform the following procedure.
Navigation
Administration > Incentive > Payment Plan
Prerequisites
None.
Steps
2. Click the Payment Plan link on the side panel menu.
The Payment Plan page appears.
1. In the Name column, assign a unique name to the payment plan.
2. Enter a Start Date and an End Date in the appropriate columns. Click the
calendar icons to use a pop-up calendar. The Start Date field is required.
3. In the Credit Type column, select a credit type from the drop-down list.
Functional Currency is the default, but you can select other, previously defined
credit types. The Credit Type field is required.
4. In the Payment Interval column, select a pay interval from the drop-down list.
Period is the default, but you can select any previously defined pay interval
from the list.
5. Optionally, establish a minimum amount to be paid at the end of each pay
interval. Check the check box in the Recoverable column if it is recoverable from
later earnings.
6. Optionally, establish a maximum amount that can be paid for any pay interval.
If you check the check box in the Pay Later column, any amounts over the
maximum to be paid can be rolled over and paid in future periods.
7. Select a recovery interval from the drop-down list. The default setting is the
same as the pay interval.

Payroll
8. Check the Pay Against Commission check box if you want the payment plan to
apply its rules using earnings that have been collected in the application when
it calculates draw recovery at the end of the recovery interval.
10. Click Update to save the payment plan.
The payment plan can be assigned to a salesperson in the Resources subtab of
the Resource tab.
Guidelines
The application checks first for the minimum amount and pays it. Recoverable
amounts are calculated after the minimum is met.
12.16 Payroll
Use this page to map the plan elements in Oracle Incentive Compensation to the
pay elements in Payroll. To add or change a record, perform the following
procedure.
Navigation
Administration > Incentive > Payroll
Prerequisites
Plan elements and pay elements must already be created.
Steps
If you want to make a change in mapping or dates to an existing line, perform the
2. Click the Payroll link on the side panel menu.
The Payroll Mapping page appears.
3. Enter the changes. Click Go to open a pop-up list of choices, or the calendar
icon to open a calendar.
4. Check the Remove check box if you want to eliminate the plan element to pay
element mapping.
Payroll
5. Check the Inactive Employees check box if you want to keep the mapping but
not use it now.
Steps 2 and 3 are completed when you click Update.
6. You can click the Element Input link to go to the Pay Element Input Values
Mapping page.
7. Click Update.
8. If necessary, click Restore before clicking Update to return to the previously
stored information.
To enter a new mapping, perform the following procedure.
1. Enter a plan element in the first blank plan element field. Click Go to use a
pop-up list.
2. Enter the pay element from Payroll that you want to use.
3. Enter a Start Date and an End Date.
5. Click Update to save your mapping.
12.16.1 Pay Element Input Values Mapping

After you have mapped the pay elements to the plan elements, use this page to map
table and column names to Payroll input values. Input values that have already
been mapped are displayed. To map table and column names to Payroll input
values, perform the following procedure.
Navigation
Administration > Incentive > Payroll > Element link
Prerequisites
Plan elements and pay elements must already be created.
Steps
2. Click the Payroll link in the side panel menu.
The Payroll Mapping page appears.

Components
3. Click the link in the Element column.

The Pay Element Input Values Mapping page appears.
4. Enter a table name in the first blank field in the Table Name column. Click Go
to open a pop-up list.
5. Enter a column name in the Column Name column. Click Go if needed.
6. In a line that is not yet saved, click the eraser icon to clear the fields.
7. To remove a saved line, check the check box in the Remove column.
8. If necessary, click Restore to return to previously saved information.
12.17 Components
Use the Components page to create and edit quota components. These components
are used in building compensation plans in Incentive Planning. Components must
be created here before they can be used in Incentive Planning.
On the Quota Components page, you can provide a description of the component,
specify whether it is revenue or unit based, indicate if the compensation is fixed or
variable, and set the compensation to be based on a quota or simply on revenue
amount. A check box is provided to indicate if the component requires
computation.
To edit or create quota components, perform the following procedure.
Navigation
Administration > Incentive > Component
Prerequisites
None
Steps
2. Click the Component link on the side panel menu.
The Quota Components search page appears.
Components
3. Enter a name or partial name with a percent sign (%) or select a type and unit
from the drop-down lists. Making no selection means that all components will
be displayed when you click Apply in step 4.
4. Click Apply.
A table appears containing any previously defined components that meet the
search parameters.
5. Edit component information as needed and click Update to save your changes.
If necessary, click Restore to return to the previously saved information.
6. To create a new quota component, in the last line in the quota components list,
enter the name of the Component in the Name field.
7. Enter a short description for each component.
8. Select a type from the drop-down list. You can select Fixed or one of three
Variable types (See Guidelines).
9. In the Unit column, select Unit or Revenue from the drop-down list.
10. Check the Computed Flag check box if you want to use a formula to derive the
value of the component.
12. To remove a component, check the check box in the Remove column and click
Update. You cannot delete components that are currently in use in
compensation plans.
Guidelines
Quota Components are parts of a compensation plan, and can be of different types.
Fixed components remain the same regardless of the salesperson’s performance.
Typical Fixed components include Salary and Car Allowance. Variable components
include calculations based on performance, and are based on a quota or can be
nonquota based.
Unit and Revenue, selected in the Unit column, indicate if compensation is revenue
based or unit based. Revenue can be used during currency conversion, but unit
based components are not currency converted as they are point based.
Fixed components can be of revenue type only. Therefore, the unit type of Revenue
is not displayed as a drop-down list.

Attainment
12.18 Attainment
Attainment schedules are used in Incentive Planning to display anticipated payouts
for compensation contracts. Earnings for each level of achievement are calculated
based on the attainment percentages contained in the Attainment schedule. You can
create, delete, or edit attainment schedules on the Attainment Schedule Summary
page.
Navigation
Administration > Incentive > Attainment
To Create a new attainment schedule, perform the following procedure.
Prerequisites
None.
Steps
2. Click the Attainment link on the side panel menu.
The the Attainment Schedule Summary page appears.
3. Type the new name into the blank field in the Attain Schedule Name column
and click Update.
4. Click the new link in the Attain Schedule Name column to go to the Define
Attain Schedule page.
5. Fill in percent information in ascending order in the first two tiers, then, to add
more tiers, click Update. Two additional blank tiers appear.
6. Click Update to add more tiers until you have as many as you need.
7. Click Update when you are done to save your work.
8. If you have already saved your work, click Restore at any time to return all tiers
to the settings they had at the last update.
To edit or view an existing attainment schedule, perform the following procedure.
1. Click a schedule name in the right column of the Attainment Schedule
Summary page to open the Define Attainment Schedule page.
2. After making any adjustments, click Update to save your work. Or, click
Restore to return to the previously saved information.
Job Titles
3. To delete a tier, select the Remove check box beside that tier and click Update.
12.19 Job Titles

Job titles are created in Human Resources (HR), but are important for Incentive
Planning. Sales roles must be assigned to job titles for quota modeling purposes.
Use the page to view a list of current job titles. Click a Job Title to access the
Resource Details - Job Title Details page, where you can view sales roles assigned to
the job title, assign a sales role to the selected Job Title, and assign start and end
dates for that role.
Navigation
Administration > Incentive > Job Titles
Prerequisites
Super User responsibility is required. Resources have been set up in Oracle
Resource Manager.
Steps
2. Click the Job Titles link in the side panel menu.
The Job Titles page appears.
3. Use the search parameters at the top of the page to search for a job title by name
or by job code. Click Go to display the search results. You can also simply find
the job title in the listing if the number listed is not too great.
4. Click the link in the Job Titles column to go to the Resource Details - Job Titles
page.
This page displays any roles that are already assigned to the job title.
5. To add a role, enter it in the Role column. You can click Go to open a pop-up
window listing roles from which to select.
6. Enter a start date and end date for the role. Click the calendar icon to open a
pop-up calendar. A start date is mandatory; the end date is optional.
7. Click Update to save your work. If you are editing a role assignment, you can
click Restore to return to the previously saved version.

User Access
Guidelines
If using Oracle Human Resources Management System (HRMS), the Job Title
information is read from HRMS via Oracle Resource Manager. If not using HRMS,
please refer to Oracle Resource Manager for information on how to define
resources.
12.20 User Access

Use the User Access Detail page to set the access privilege of users with finance
manager responsibility. All of the user’s compensation groups and organizations
are displayed.
Navigation
Administration > Incentive > User Access
Prerequisites
Users must be assigned Finance Manager responsibility to appear on the User
Access screen.
Steps
2. Click the User Access link in the side panel menu.
The User Summary page appears.
3. Select a User by clicking his or her name.
4. The User Access Detail page appears.
5. Enter a compensation group in the Compensation Group column, or click Go to
select one from the pop-up list.
6. In the Organization column, select an organization from the drop-down list.
7. Select an Access Level of Update or View from the drop-down list.
8. To remove a listing, check the Remove check box and click Update.
9. If necessary, click Restore to return to the most recently saved information
Settings
12.21 Settings
On the Settings page, you can select the Transaction Calendar and write Contract
Text for a compensation plan.
Text from the Default Contract Text for the organization is carried over to the
agreement contract text. The text can be customized at the Agreement level for
individual resources as follows:
■ Display names for quota components
■ Display names for rate tables
■ Selection of displayed components for an attainment schedule
■ Unique text for title, terms and conditions, club eligibility
Navigation
Prerequisites
The Transactions Calendar must be predefined so that it can be assigned through
the Settings page. Incentive Planning Super User or Incentive Analyst responsibility
is required.
Steps
2. Click the Settings link on the side panel menu.
3. Select a Transaction calendar from the drop-down list.
4. In the Contract Text area, enter text as required into the fields. For club
eligibility, write out the details, such as 100% Eligible.
5. In the Approver area, enter your name, title, and organization.

Settings
12.21.1 Workday Calendar

The workday calendar is a type of transaction calendar that is assigned to a
compensation plan. The value of a transaction calendar is that it defines the specific
workdays of a particular year, and excludes weekends and holidays. For example, a
USA Workday Calendar 2002 lists only the workdays in the United States for the
calendar year 2002. The holidays vary from country to country and even from state
to state.
Workday calendars are useful for calculating compensation based on the exact
number of workdays in a given month. A calendar’s duration can be defined to
match your organization’s financial year. You need to assign a new workday
calendar every year as the dates of weekends and many holidays change from year
to year.
To view or select the workday calendar that is assigned to a particular
compensation plan, perform the following procedure.
Navigation
Prerequisites
To use a workday calendar, the profile option OSC: Use Work Day Calendar must
be set to Yes. Incentive Compensation Super User responsibility is required.
Steps
2. Click the Settings link on the side panel menu.
3. Select a transaction calendar from the drop-down list.
4. Click Update to save your changes. Before clicking Update, you can return to
the previously saved settings by clicking Restore.
To create a workday calendar, perform the following procedure.
Steps
1. Click the Administration tab.
The General subtab appears automatically.
Settings
2. Click the Transaction Calendar link in the side panel menu.

The Transaction Calendar page appears, listing all transaction calendars that
have been defined.
3. To modify the days of the week of an existing transaction calendar, check or
uncheck the appropriate check boxes. To modify exact dates, see step 8.
4. To create a new transaction calendar, enter the name of the new calendar in the
first empty name field.
6. Check the check boxes for the days of the week that you want to designate as
workdays in the transaction calendar.
7. Click Update to save your work. Before clicking Update, you can return to the
previously saved settings by clicking Restore.
8. To define the exact dates of holidays or additional work days, click the
transaction calendar link in the Name column.
A different Transaction Calendar page appears. This page lists each date as a
separate row, containing the calendar date, day of the week, and a Business Day
check box. See Guidelines for more details.
9. Check the check box next to any date that you want to set as a business day.
10. Uncheck the check box next to any date that you want to designate as a holiday.
11. Click Update to save your work. Before clicking Update, you can return to the
previously saved settings by clicking Restore.
Guidelines
This Transaction Calendar page does not start at the current year, and the listing of
dates is extensive. In the current release, dates begin at January 1, 1994 and run
through December 31, 2010. To get to the beginning of the year you want, use the
drop-down list and select the area that is approximately where you want to work.
Then, use the Previous and Next links to get to the exact dates you need.
If you use the Search field, the application displays only the single day you
requested.

Seasonality Schedules
12.22 Seasonality Schedules

use multiple seasonality schedules for different components. Because of the
variability from period to period, a new hire’s quotas and pay are affected. If
seasonality schedules are not assigned, an even distribution is assumed by default,
where each period’s quota is the same amount for the entire year. Seasonality
schedules are built using the Incentive subtab of the Administration tab in Oracle
Incentive Compensation. Seasonality can only be applied to variable non computed
plan elements, such as salary or a car allowance.
To begin to view, edit, or create seasonality schedules, perform the following
procedure.
Navigation
Administration > Incentive > Seasonality
Prerequisites
None.
Steps
2. Select Seasonality on the side panel menu.
The Seasonality Schedules page appears. Seasonality schedules that have
already been created are displayed.
3. If necessary, use the search parameters at the top of the page to search by fiscal
year or by schedule name. Select the fiscal year from the drop-down list or enter
all or part of the name before the percent sign and click Search.
4. Click the name for the schedule you wish to view or edit.
The Seasonality Schedule Details page for the schedule appears.
5. In the Seasonality area, the percentages for each month are displayed. To
change the numbers in the Percentage column, edit the field. Note: The
numbers in the Percentage column must add up to 100 percent.
Seasonality Schedules
8. Click Validate to validate your seasonality schedule. After it is validated, the

Validation Status in the top section of the page reads VALID. If the percentages
do not add up to 100 percent the schedule cannot achieve a Valid status.
Guidelines
You must click Update to save a new seasonality schedule before clicking Validate. If
you click Validate without clicking Update first, it will return all of the percentage
entries to 0.
Be sure that after any changes are made, the Table Total adds up to 100 percent.
12.22.1 Create New Seasonality Schedule

To create a new seasonality schedule, perform the following procedure.
Navigation
Administration > Incentive > Seasonality > Click Create
Prerequisites
None.
Steps
2. Select Seasonality on the side panel menu.
The Seasonality Schedules page appears.
3. Click Create.
The Create New Seasonality Schedule page appears.
4. Enter a name for the new seasonality schedule in the name field. This is a
required field.
5. Enter a description. This is a required field.
6. Select a year from the drop-down list.
8. In the Seasonality area, enter the percentage of annual quota in each field next
to each month. Be sure that the percentages add up to 100 percent.
9. When the schedule is the way you want it, click Update to save your work.

Rate Dimensions
10. Click Validate to verify that your percentages add up to 100 percent. If
validation is successful, then the Validation Status in the top area of the page
reads Valid.
Guidelines
You must click Update to save a new seasonality schedule before clicking Validate. If
you click Validate without clicking Update first, it will return the all percentage
entries to 0.
12.23 Rate Dimensions

Rate dimensions define the tiers that are used in a rate table. The Dimensions
summary page displays all of the rate dimensions that have already been created.
There are four kinds of rate dimensions--Amount, Percent, String, and Expression.
■ Amount and Percent: These are the most common rate dimensions, and are
numeric based.
■ String: These dimensions are useful when you want to create non-numeric
dimensions, such as states.
■ Expression: These rate dimensions reference calculation expressions, and can be
used to create more complex rate tiers. For example, rather than creating a static
set of rate tiers such as 0% to 25%, 25% to 50%, and so on, an expression rate
dimension can be configured as 10% * Quota, 25% * Quota, and so on, using a
calculation expression.
To view, edit, or create rate dimensions, perform the following procedure.
Navigation
Administration > Incentive > Rate Dimensions
Prerequisites
Dimensions must exist to be displayed on the Dimensions page.
Steps
2. Select Rate Dimensions on the side panel menu.
The Dimensions page appears.
Rate Dimensions
3. Use the Name search parameter at the top to locate a specific dimension
quickly. Enter one or more letters or number and click Apply.
All dimensions that fit that description are displayed.
4. The Dimensions page lists dimensions by name, and also by number of tiers
and type. A dimension must have at least one tier, but can have as many as you
need. See above regarding dimension type.
5. To view or edit details of a dimension, click the name of a dimension. The
Dimension details page appears.
6. To create a new dimension, click Create on the Dimension summary page. The
Dimension details page appears, but the fields are blank.
7. Enter a name in the Name field for your dimension. This is a required field.
8. Select or verify the type from the drop-down list. You can select Amount,
Percent, Expression, or String. This is also a required field.
Depending on which type you select, the lower part of the page refreshes to
provide the appropriate fields into which you can enter data.
10. For Amount or Percent dimensions, in the Rate Tiers area, enter numbers in the
From and To columns. Follow the sequence, and do not leave any gaps in the
rates. These are required fields.
Enter numbers for the first tier. To add a tier, click Update and another blank
field appears. Repeat this process until you have as many tiers as you need.
11. For String dimensions, enter the string value for the rate tier. This is a required
field.
12. For Expression dimensions, select expressions from the drop-down list for the
From and To columns.
13. Click Update to save your work. Or, If necessary, click Restore to return to the
previously saved values.
Guidelines
After you create a rate dimension with a type of String or Expression, you cannot
change the type with a future update. However, for rate dimensions created with a
type of Amount or Percent, you can update a rate dimension definition.
For expression rate dimensions, expressions must be defined in the application in
order for the drop-down list to contain any selectable values.

Rate Dimensions
Rate Dimensions

Part VI
Appendixes
This part contains the following Appendixes:

■ Appendix A, "External Formula Code Examples"
■ Appendix B, "Customized Summarization Code Examples"
A
External Formula Code Examples
Following are two examples with notes indicating the customization of the existing
packages. The Spec code is shown first, with the Package Body following. Areas in
the package body that can be customized for external packages are shown in
boldface type. Notes of interest are displayed in Italics. The Spec code cannot be
changed.
■ Section A.1, "Example 1"
■ Section A.2, "Example 2"
A.1 Example 1
A.1.1 Spec of Example 1
CREATE OR REPLACE PACKAGE cn_formula_10510_pkg AS
-- Procedure Name
-- get_input
-- Purpose
-- This procedure gets the input values
-- History
-- 04-SEP-2001 APPS Created
External Formula Code Examples A-1

Example 1
PROCEDURE get_input(p_commission_line_id NUMBER,

p_salesrep_id NUMBER,
p_period_id NUMBER,
p_quota_id NUMBER,
p_srp_plan_assign_id NUMBER,
p_processed_date DATE,
x_mul_input_tbl IN OUT
cn_formula_common_pkg.mul_input_tbl_type);
-- Procedure Name
-- get_perf
-- Purpose
-- This procedure is to accumulate performance measure.
-- History
FUNCTION get_perf(p_commission_line_id NUMBER,

p_period_id NUMBER,
p_quota_id NUMBER,
p_start_date DATE) RETURN NUMBER;
-- Procedure Name
-- get_commission
-- Purpose
-- This procedure is to calculate the commission
-- History
A-2 Product Title/BookTitle as a Variable

Example 1
FUNCTION get_commission(p_commission_line_id NUMBER,

p_period_id NUMBER,
p_quota_id NUMBER,
p_rate NUMBER) RETURN
NUMBER;
-- Procedure Name
-- calculate_quota
-- Purpose
-- This procedure is the hook to the calculation engine
-- History
PROCEDURE calculate_quota(p_srp_plan_assign_id NUMBER,

p_period_id NUMBER,
p_start_date DATE,
p_quota_id NUMBER,
p_process_all_flag VARCHAR2,
p_intel_calc_flag VARCHAR2,
p_calc_type VARCHAR2,
x_latest_processed_date OUT DATE);
-- Procedure Name

Example 1
-- get_result
-- Purpose
-- This procedure is invoked if this formula is used as an
embeded formula
-- History
FUNCTION get_result(p_commission_line_id NUMBER) RETURN

NUMBER;
END cn_formula_10510_pkg ;
A.1.2 Body of Example 1
CREATE OR REPLACE PACKAGE BODY cn_formula_10510_pkg AS
g_commission_payed_ptd NUMBER;
g_commission_payed_itd NUMBER;
g_input_achieved_ptd NUMBER;
g_input_achieved_itd NUMBER;
g_output_achieved_ptd NUMBER;
g_output_achieved_itd NUMBER;
g_perf_achieved_ptd NUMBER;
g_perf_achieved_itd NUMBER;
g_intel_calc_flag VARCHAR2(1);
g_calc_type VARCHAR2(30);
g_select_status_flag VARCHAR2(30);
g_formula_id NUMBER := 10510;

Example 1
g_number_dim NUMBER := 3;
g_split_flag VARCHAR2(1) := ’N’;
g_trx_group_code VARCHAR2(30) := ’INDIVIDUAL’;
g_itd_flag VARCHAR2(1) := ’N’;
g_output_achieved NUMBER;
-- Procedure Name
-- get_input
-- Purpose
-- This procedure gets the input values
-- History

p_period_id NUMBER,
p_quota_id NUMBER,
x_mul_input_tbl IN OUT
cn_formula_common_pkg.mul_input_tbl_type)
IS
l_input NUMBER;
--Note: define the following local variables

l_input_string1 VARCHAR2(30);

Example 1
--Note: you can define local variables and cursors to get

information
-- from the other tables or views as long as you are
sure that at
-- this point in time, those tables/views have the
correct information.
-- For example, you can get the commission_payed_itd
from another
-- plan element in the same compensation plan from cn_
srp_period_quotas
-- by the following query:
-- select commission_payed_itd
-- into l_comm
-- from cn_srp_period_quotas
-- where srp_plan_assign_id = p_srp_plan_assign_id
-- and quota_id = :quota_id
-- and period_id = p_period_id
BEGIN
--Note: modify the following SQL statement to get the input
values
select ch.transaction_amount, ch.attribute46, ch.attribute47
into l_input, l_input_string1, l_input_string2
from cn_commission_lines cl, cn_commission_headers ch
where cl.commission_line_id = p_commission_line_id
and ch.commission_header_id = cl.commission_header_id;
--Note: pass the input values to the corresponding array

element
l_input := nvl(l_input, 0);
x_mul_input_tbl(1).rate_dim_sequence := 1;

Example 1
x_mul_input_tbl(1).input_string := l_input_string1;
x_mul_input_tbl(1).base_amount := l_input;
x_mul_input_tbl(3).input_amount := l_input;
x_mul_input_tbl(3).amount := l_input;
--Note: pass the total revenue (g_input_achieved_itd+l_

input)
-- as the base_amount instead of l_input
x_mul_input_tbl(3).base_amount := g_input_achieved_itd + l_
input;
EXCEPTION WHEN OTHERS THEN
cn_message_pkg.debug(’EXCEPTION IN GET_input, ’ || sqlerrm);
raise;
END get_input;
-- Procedure Name
-- get_perf
-- Purpose
-- This procedure is to accumulate performance measure.
-- History

Example 1
FUNCTION get_perf(p_commission_line_id NUMBER,

p_period_id NUMBER,
p_quota_id NUMBER,
p_start_date DATE) RETURN NUMBER
IS
l_perf NUMBER;
BEGIN
--Note: you can manipulate l_perf here
select ch.transaction_amount
into l_perf
l_perf := nvl(l_perf, 0);

return l_perf;
cn_message_pkg.debug(’EXCEPTION IN GET_PERF, ’ || sqlerrm);
raise;
END get_perf;
-- Procedure Name
-- get_commission
-- Purpose
-- This procedure is to calculate the commission

Example 1
-- History
FUNCTION get_commission(p_commission_line_id NUMBER,

p_period_id NUMBER,
p_quota_id NUMBER,
p_rate NUMBER) RETURN
NUMBER
IS
l_commission NUMBER;
l_output NUMBER;
BEGIN
--Note: you can manipulate l_commission here
select p_rate*ch.transaction_amount
into l_commission
l_commission := nvl(l_commission, 0);

return l_commission;
cn_message_pkg.debug(’EXCEPTION IN GET_COMMISSION, ’ ||
sqlerrm);
raise;
END get_commission;

Example 1
-- Procedure Name
-- calculate_quota
-- Purpose
-- History

p_period_id NUMBER,
p_start_date DATE,
p_quota_id NUMBER,
x_latest_processed_date OUT DATE)
IS
l_mul_input_tbl cn_formula_common_pkg.mul_input_tbl_type;
l_rate NUMBER;
l_rate_tier_id NUMBER;
l_tier_split NUMBER;
l_input NUMBER;
l_perf NUMBER;
l_itd_target NUMBER;
l_itd_payment NUMBER;
l_processed_date DATE;

Example 1
l_error_reason VARCHAR2(150);
l_trx_rec_old cn_formula_common_pkg.trx_rec_type;
l_trx_rec_new cn_formula_common_pkg.trx_rec_type;
l_trx_rec_null cn_formula_common_pkg.trx_rec_type;
CURSOR l_lines_csr IS
SELECT cl.commission_line_id,
cl.commission_header_id,
cl.credited_salesrep_id salesrep_id,
cl.srp_plan_assign_id,
cl.quota_id,
cl.processed_date,
cl.processed_period_id,
cl.pay_period_id,
cl.commission_amount,
cl.commission_rate,
cl.rate_tier_id,
cl.tier_split,
cl.input_achieved,
cl.output_achieved,
cl.perf_achieved,
cl.posting_status,
cl.pending_status,
cl.created_during,
cl.trx_type,
cl.error_reason,
cl.status
FROM cn_commission_lines cl,

Example 1
cn_commission_headers header
WHERE cl.credited_salesrep_id = p_salesrep_id
AND cl.quota_id = p_quota_id
AND cl.srp_plan_assign_id = p_srp_plan_assign_id
AND cl.processed_period_id = p_period_id
AND cl.processed_date >= p_start_date
AND header.commission_header_id = cl.commission_header_
id
AND substr(header.pre_processed_code, 4,1) = ’C’
AND ((g_select_status_flag = ’PCX’ and cl.status in
(’POP’,
’CALC’, ’XCALC’))
OR (g_select_status_flag = ’P’ and cl.status =
’POP’))
AND ((g_calc_type = ’FORECAST’ and cl.trx_type =
’FORECAST’)
OR (g_calc_type = ’BONUS’ and cl.trx_type =
’BONUS’)
OR (g_calc_type = ’COMMISSION’ and cl.trx_type NOT
IN
(’BONUS’,’FORECAST’,’GRP’)))
ORDER by cl.processed_date asc, cl.commission_line_id
asc;
BEGIN
g_intel_calc_flag := p_intel_calc_flag;
g_calc_type := p_calc_type;
cn_formula_common_pkg.calculate_init(p_srp_plan_assign_id,
p_salesrep_id,
p_period_id,

Example 1
p_quota_id,
p_start_date,
p_process_all_flag,
g_intel_calc_flag,
g_calc_type,
g_trx_group_code,
g_itd_flag,
g_commission_payed_ptd,
g_commission_payed_itd,
g_input_achieved_ptd,
g_input_achieved_itd,
g_output_achieved_ptd,
g_output_achieved_itd,
g_perf_achieved_ptd,
g_perf_achieved_itd,
g_select_status_flag);
Open l_lines_csr;
LOOP
l_trx_rec_new := l_trx_rec_null;
FETCH l_lines_csr into l_trx_rec_old;
EXIT WHEN l_lines_csr%notfound;
BEGIN
get_input(l_trx_rec_old.commission_line_id,
p_salesrep_id,
p_period_id,
p_quota_id,
p_srp_plan_assign_id,

Example 1
l_trx_rec_old.processed_date,
l_mul_input_tbl);
--Note: display l_mul_input_tbl(3).amount instead of

-- l_mul_input_tbl(1).amount because we add two
more inputs and the third
-- one actually have the numeric value
cn_message_pkg.debug(’AFTER get_input ’ || l_mul_input_
tbl(3).amount);
cn_formula_common_pkg.get_rates(p_salesrep_id,
p_period_id,
p_quota_id ,
g_split_flag,
g_itd_flag,
l_trx_rec_old.processed_
date,
g_number_dim,
l_mul_input_tbl,
g_formula_id,
l_rate,
l_rate_tier_id,
l_tier_split);
--Note: you can manipulate l_rate here. For example,

double the portion that exceeds
-- 100% in the following way:
-- if (l_rate > 1) then

Example 1
-- l_rate := 1 + 2*(l_rate - 1);

-- end if;
cn_message_pkg.debug(’AFTER get_rates ’ || l_rate);
l_commission := get_commission(l_trx_rec_old.commission_
line_id,
p_salesrep_id,
p_period_id,
p_quota_id,
l_rate);
--Note: you can manipulate l_commission here.

cn_message_pkg.debug(’AFTER get_commission ’ || l_
commission);
l_perf := get_perf(l_trx_rec_old.commission_line_id,
p_salesrep_id,
p_period_id,
p_quota_id,
l_trx_rec_old.processed_date);
cn_message_pkg.debug(’AFTER get_perf’ || l_perf);
--Note: l_input should be l_mul_input_tbl(3).input_

amount
-- instead of l_mul_input_tbl(1).input_amount
l_input := l_mul_input_tbl(3).input_amount;

Example 1
x_latest_processed_date := l_trx_rec_old.processed_date;
l_trx_rec_new.status := ’CALC’;
l_trx_rec_new.commission_amount := l_commission;
l_trx_rec_new.commission_rate := l_rate;
l_trx_rec_new.rate_tier_id := l_rate_tier_id ;
l_trx_rec_new.tier_split := l_tier_split ;
l_trx_rec_new.input_achieved := l_input ;
l_trx_rec_new.output_achieved := l_input;
l_trx_rec_new.perf_achieved := l_perf ;
EXCEPTION when others then
l_trx_rec_new.error_reason := substr(sqlerrm,1,150);
l_trx_rec_new.status := ’XCALC’ ;
END;
cn_formula_common_pkg.update_trx(l_trx_rec_old, l_trx_rec_
new);
g_perf_achieved_ptd := g_perf_achieved_ptd+ l_perf;
g_perf_achieved_itd := g_perf_achieved_itd+ l_perf;
g_input_achieved_ptd := g_input_achieved_ptd + l_input;
g_input_achieved_itd := g_input_achieved_itd + l_input;
g_commission_payed_ptd := g_commission_payed_ptd + l_
commission;
g_commission_payed_itd := g_commission_payed_itd + l_
commission;
END LOOP;
CLOSE l_lines_csr;

Example 1
cn_formula_common_pkg.calculate_roll(p_salesrep_id,
p_period_id,
p_quota_id,
p_calc_type,
g_perf_achieved_itd);
EXCEPTION
when others then
IF l_lines_csr%isopen THEN
CLOSE l_lines_csr;
END IF;
cn_message_pkg.debug(’Exception in calculate_quota’ ||
sqlerrm);
cn_debug.print_msg(’calculate_quota<<’, 1);
END calculate_quota;
-- Procedure Name
-- get_result
-- Purpose
-- This procedure is invoked if this formula is used as an
embeded formula
-- History

Example 1
FUNCTION get_result(p_commission_line_id NUMBER) RETURN NUMBER

IS
l_mul_input_tbl cn_formula_common_pkg.mul_input_tbl_
type;
l_rate NUMBER;
l_salesrep_id NUMBER(15);
l_period_id NUMBER(15);
l_quota_id NUMBER(15);
l_processed_date DATE ;
l_srp_plan_assign_id NUMBER(15);
CURSOR l_comm_line_csr IS
select credited_salesrep_id,
processed_period_id,
quota_id,
srp_plan_assign_id,
processed_date
from cn_commission_lines
where commission_line_id = p_commission_line_id;
BEGIN
OPEN l_comm_line_csr ;
FETCH l_comm_line_csr into l_salesrep_id, l_period_id, l_
quota_id,
l_srp_plan_assign_id, l_processed_date;

Example 1
CLOSE l_comm_line_csr;
get_input(p_commission_line_id,
l_salesrep_id,
l_period_id,
l_quota_id,
l_srp_plan_assign_id,
l_processed_date,
l_mul_input_tbl);
cn_formula_common_pkg.get_rates(l_salesrep_id,
l_period_id,
l_quota_id,
g_split_flag,
g_itd_flag,
l_processed_date,
g_number_dim,
l_mul_input_tbl,
g_formula_id,
l_rate,
l_rate_tier_id,
l_tier_split);
l_commission := get_commission(p_commission_line_id,
l_salesrep_id,
l_period_id,
l_quota_id,

Example 2
l_rate);
return l_commission;
cn_debug.print_msg(’get_result<<’, 1);
END get_result;
A.2 Example 2
A.2.1 Spec for Example 2
--Note: this is a customized version of a system generated

package
-- for a group by formula and it has three inputs
CREATE OR REPLACE PACKAGE cn_formula_10356_pkg AS
--
-- Procedure Name
-- get_input
-- Purpose
-- This procedure is to calculate the input
-- History
-- 24-OCT-01 APPS Created
p_period_id NUMBER,

Example 2
p_quota_id NUMBER,
x_mul_input_tbl IN OUT cn_formula_
common_pkg.mul_input_tbl_type,
p_endofinterval_flag VARCHAR2,
p_start_period_id NUMBER);
--Note: procedures get_perf and get_commission are also

removed because
-- they are computed in the customized procedure
calculate_quota
-- directly.
--
-- Procedure Name
-- calculate_quota
-- Purpose
-- History
p_period_id NUMBER,
p_start_date DATE,
p_quota_id NUMBER,

Example 2
x_latest_processed_date OUT DATE);

--
-- Procedure Name
-- update_revclass_perf
-- Purpose
-- To accumulate performance by revenue classes in group by
case.This is
-- a call back when updating plan element subledger
-- History
PROCEDURE update_revclass_perf(p_salesrep_id NUMBER,
p_period_id NUMBER,
p_quota_id NUMBER,
p_srp_plan_assign_id NUMBER);
A.2.2 Body of Example 2
--Note: this is a customized version of a system generated

package
-- for a group by formula and it has three inputs
CREATE OR REPLACE PACKAGE BODY cn_formula_10356_pkg AS
g_commission_payed_ptd NUMBER;
g_commission_payed_itd NUMBER;
g_input_achieved_ptd NUMBER;
g_input_achieved_itd NUMBER;
g_output_achieved_ptd NUMBER;

Example 2
g_output_achieved_itd NUMBER;
g_perf_achieved_ptd NUMBER;
g_perf_achieved_itd NUMBER;
g_intel_calc_flag VARCHAR2(1);
g_calc_type VARCHAR2(30);
g_select_status_flag VARCHAR2(30);
g_formula_id NUMBER := 10356 ;
g_number_dim NUMBER := 3 ;
g_split_flag VARCHAR2(1) := ’N’ ;
g_itd_flag VARCHAR2(1) := ’N’ ;
g_output_achieved NUMBER;
--
-- Procedure Name
-- get_input
-- Purpose
-- This procedure is to calculate the input
-- History
p_period_id NUMBER,
p_quota_id NUMBER,
x_mul_input_tbl IN OUT cn_formula_
common_pkg.mul_input_tbl_type,

Example 2
p_endofinterval_flag VARCHAR2,
p_start_period_id NUMBER)
IS
l_input NUMBER;
l_input_string2 varchar2(30);
BEGIN
--Note: the code to compute the aggregated values is removed
because they
-- are computed in the customized procedure calculate_
quota.
select ch.transaction_amount, ch.attribute3, ch.attribute1
into l_input, l_input_string1, l_input_string2
from cn_commission_headers ch, cn_commission_lines cl
l_input := nvl(l_input,0);

Example 2
x_mul_input_tbl(3).input_amount := l_input;
x_mul_input_tbl(3).amount := l_input;
cn_message_pkg.debug(’EXCEPTION IN GET_input, ’ || Sqlerrm);
raise;
END get_input;
--Note: procedures get_perf and get_commission are also

removed because
-- they are computed in the customized procedure
calculate_quota
-- directly.
--
-- Procedure Name
-- calculate_quota
-- Purpose
-- History
p_period_id NUMBER,
p_start_date DATE,
p_quota_id NUMBER,

Example 2
x_latest_processed_date OUT DATE)
IS
l_mul_input_tbl cn_formula_common_pkg.mul_input_
tbl_type;
l_rate NUMBER;
l_input NUMBER;
l_perf NUMBER;
l_itd_payment NUMBER;
l_processed_date DATE;
l_error_reason VARCHAR2(150);
l_trx_rec_old cn_formula_common_pkg.trx_rec_type;
l_trx_rec_new cn_formula_common_pkg.trx_rec_type;
l_trx_rec_null cn_formula_common_pkg.trx_rec_
type;
l_endofinterval_flag VARCHAR2(1);
l_start_period_id NUMBER(15);
l_grp_trx_rec cn_formula_common_pkg.trx_rec_type;
CURSOR l_lines_csr IS
SELECT cl.commission_line_id,
cl.commission_header_id,
cl.credited_salesrep_id salesrep_id,

Example 2
cl.srp_plan_assign_id,
cl.quota_id,
cl.processed_date,
cl.processed_period_id,
cl.pay_period_id,
cl.commission_amount,
cl.commission_rate,
cl.rate_tier_id ,
cl.tier_split,
cl.input_achieved ,
cl.output_achieved,
cl.perf_achieved,
cl.posting_status,
cl.pending_status,
cl.created_during,
cl.trx_type,
cl.error_reason,
cl.status
FROM cn_commission_lines cl,
cn_commission_headers header
WHERE cl.credited_salesrep_id = p_salesrep_id
AND cl.quota_id = p_quota_id
AND cl.srp_plan_assign_id = p_srp_plan_assign_id
AND cl.processed_period_id = p_period_id
AND cl.processed_date >= p_start_date
AND header.commission_header_id = cl.commission_header_
id
AND substr(header.pre_processed_code, 4,1) = ’C’

Example 2
AND ((g_select_status_flag = ’PCX’ and cl.status in

(’POP’, ’CALC’, ’XCALC’)) OR
(g_select_status_flag = ’P’ and cl.status =
’POP’))
AND ((g_calc_type = ’FORECAST’ and cl.trx_type =
’FORECAST’) OR
(g_calc_type = ’BONUS’ and cl.trx_type = ’BONUS’)
OR
(g_calc_type = ’COMMISSION’ and cl.trx_type NOT IN
(’BONUS’,’FORECAST’,’GRP’)))
order by cl.processed_date, cl.commission_line_id;
BEGIN
g_intel_calc_flag := p_intel_calc_flag;
g_calc_type := p_calc_type;
cn_formula_common_pkg.calculate_init(p_srp_plan_assign_id,
p_salesrep_id,
p_period_id,
p_quota_id,
p_start_date,
p_process_all_flag,
g_intel_calc_flag,
g_calc_type,
g_commission_payed_ptd,
g_commission_payed_itd,

Example 2
g_perf_achieved_itd,
g_select_status_flag);
l_endofinterval_flag := ’N’;
--Note: the code in the following loop is simplified. Its

sole purpose is to
-- set the status of each transaction to CALC if there
is no error in
-- calling get_input. If there is error, the status is
set to XCALC.
Open l_lines_csr;
LOOP
l_trx_rec_new := l_trx_rec_null;
FETCH l_lines_csr into l_trx_rec_old;
EXIT WHEN l_lines_csr%notfound;
BEGIN
get_input(l_trx_rec_old.commission_line_id,
p_salesrep_id,
p_period_id,
p_quota_id,
p_start_date,
l_mul_input_tbl,
l_endofinterval_flag,
null);
l_commission := 0;
l_perf := 0;

Example 2
x_latest_processed_date := l_trx_rec_old.processed_date;
l_trx_rec_new.status := ’CALC’;
EXCEPTION when others then
l_trx_rec_new.error_reason := substr(sqlerrm,1,150);
l_trx_rec_new.status := ’XCALC’ ;
END;
cn_formula_common_pkg.update_trx(l_trx_rec_old, l_trx_rec_
new) ;
END LOOP;
CLOSE l_lines_csr;
-- get the begining of the interval

l_start_period_id := cn_formula_common_pkg.get_start_period_
id(p_quota_id, p_period_id);
-- check if it is the end of the interval

IF cn_formula_common_pkg.EndOfInterval(p_quota_id, p_period_
id) THEN
l_endofinterval_flag := ’Y’;
END IF;
-- get the end_date of the interval

SELECT end_date into l_processed_date
FROM cn_period_statuses
WHERE period_id = p_period_id;
--Note: the following is the customized code to compute the

total commission. get_rates is called

Example 2
-- more than once. You can write any code you wish to
compute the right commission
declare
cursor totals is
select ch.attribute3, ch.attribute1, sum(transaction_
amount) revenue
where cl.credited_salesrep_id = p_salesrep_id
and cl.srp_plan_assign_id = p_srp_plan_assign_id
and cl.quota_id = p_quota_id
and ch.commission_header_id = cl.commission_header_id
and cl.processed_period_id between l_start_period_id
and p_period_id
and cl.status = ’CALC’
and ((g_calc_type = ’FORECAST’ and cl.trx_type =
’FORECAST’) or
(g_calc_type = ’BONUS’ and cl.trx_type =
’BONUS’) or
(g_calc_type = ’COMMISSION’ and cl.trx_type not
in (’BONUS’, ’FORECAST’, ’GRP’)))
group by ch.attribute3, ch.attribute1;
begin
l_commission := 0;
l_perf := 0;
for total in totals loop
l_input := nvl(total.revenue,0);
l_mul_input_tbl(1).rate_dim_sequence := 1;
l_mul_input_tbl(1).input_string := total.attribute3;
l_mul_input_tbl(1).base_amount := l_input;

Example 2
l_mul_input_tbl(2).input_string := total.attribute1;
l_mul_input_tbl(3).input_amount := l_input;
l_mul_input_tbl(3).amount := l_input;
cn_formula_common_pkg.get_rates(p_salesrep_id,
p_period_id,
p_quota_id,
g_split_flag,
g_itd_flag,
l_processed_date,
g_number_dim,
l_mul_input_tbl,
g_formula_id,
l_rate,
l_rate_tier_id,
l_tier_split);
cn_message_pkg.debug(’AFTER get_rates ’ || l_rate);
l_commission := l_commission + l_rate*l_input;

l_perf := l_perf + l_input;
end loop;

Example 2
l_grp_trx_rec.status := ’CALC’;
l_grp_trx_rec.commission_amount := l_commission ;
l_grp_trx_rec.commission_rate := l_commission/l_perf;
l_grp_trx_rec.rate_tier_id := l_rate_tier_id;
l_grp_trx_rec.tier_split := l_tier_split ;
l_grp_trx_rec.input_achieved := g_input_achieved_itd;
l_grp_trx_rec.output_achieved:= g_output_achieved_itd;
l_grp_trx_rec.perf_achieved := l_perf;
l_grp_trx_rec.status := ’XCALC’;
l_grp_trx_rec.error_reason := substr(sqlerrm, 1, 150);
END;
-- if it is the end of the interval, create a GRP type

transaction to record
-- the calculated commission.
IF (l_endofinterval_flag = ’Y’) THEN
l_grp_trx_rec.salesrep_id := p_salesrep_id;
l_grp_trx_rec.created_during := ’CALC’;
l_grp_trx_rec.srp_plan_assign_id := p_srp_plan_assign_id;
l_grp_trx_rec.quota_id := p_quota_id;
l_grp_trx_rec.processed_date := l_processed_date;
l_grp_trx_rec.processed_period_id := p_period_id;
l_grp_trx_rec.pay_period_id := cn_api.get_pay_period(p_
salesrep_id => p_salesrep_id,
p_
date => l_processed_date);
l_grp_trx_rec.posting_status := ’UNPOSTED’;
l_grp_trx_rec.pending_status := null;

Example 2
l_grp_trx_rec.trx_type := ’GRP’ ;
cn_formula_common_pkg.create_trx(l_grp_trx_rec);
END IF;
g_perf_achieved_ptd := l_perf - g_perf_achieved_itd;

g_perf_achieved_itd := l_perf;
g_input_achieved_ptd := l_input - g_input_achieved_itd ;
g_input_achieved_itd := l_input;
g_commission_payed_ptd := l_commission - g_commission_payed_
itd;
g_commission_payed_itd := l_commission;
cn_formula_common_pkg.calculate_roll(p_salesrep_id,
p_period_id,
p_quota_id,
p_calc_type,
g_perf_achieved_itd);
EXCEPTION
when others then
IF (l_lines_csr%isopen) THEN
CLOSE l_lines_csr;

Example 2
END IF;
cn_message_pkg.debug(’Exception in calculate_quota’ ||
Sqlerrm);
cn_debug.print_msg(’calculate_quota<<’, 1);
END calculate_quota;
--
-- Procedure Name
-- update_revclass_perf
-- Purpose
-- To accumulate performance by revenue classes in group by
case.This is
-- a call back when updating plan element subledger
-- History
PROCEDURE update_revclass_perf(p_salesrep_id NUMBER,
p_period_id NUMBER,
p_quota_id NUMBER,
p_srp_plan_assign_id NUMBER)
IS
l_perf NUMBER;
CURSOR l_rev_classes_csr IS
SELECT revenue_class_id, srp_per_quota_rc_id
FROM cn_srp_per_quota_rc rc
WHERE rc.srp_plan_assign_id = p_srp_plan_assign_id
AND rc.salesrep_id = p_salesrep_id
AND rc.period_id = p_period_id

Example 2
AND rc.quota_id = p_quota_id;

BEGIN
FOR l_rev_class IN l_rev_classes_csr LOOP
select sum(ch.transaction_amount)
into l_perf
where cl.credited_salesrep_id = p_salesrep_id
and cl.srp_plan_assign_id = p_srp_plan_assign_id
and cl.quota_id = p_quota_id
and ch.commission_header_id = cl.commission_header_id
and cl.status = ’CALC’ and (( g_calc_type = ’FORECAST’
and cl.trx_type = ’FORECAST’) or (g_calc_type =
’BONUS’
and cl.trx_type = ’BONUS’) or (g_calc_type =
’COMMISSION’
and cl.trx_type not in (’BONUS’, ’FORECAST’, ’GRP’)))
and cl.processed_period_id = p_period_id
and ch.revenue_class_id = l_rev_class.revenue_class_id
;
l_perf := nvl(l_perf, 0);
UPDATE cn_srp_per_quota_rc
SET period_to_date = l_perf
WHERE srp_per_quota_rc_id = l_rev_class.srp_per_quota_rc_
id;
END LOOP;
cn_debug.print_msg(’update_revclass_perf<<’, 1);

Example 2
END update_revclass_perf;

Example 2

B
Customized Summarization Code Examples
In Chapter 9, summarized transactions are discussed. If you want to use customized

code, you must provide the package body cn_aggrt_trx_pkg. Examples are shown
below.
Spec for the examples:
PACKAGE cn_aggrt_trx_pkg AUTHID CURRENT_USER AS
-- $Header: cnagtrxs.pls ship $
-- API name: aggregate_trx

-- When the profile ’Roll Summarized Transactions’ is set to ’Yes’ and
the profile
-- ’Customized summarization’ is set to ’Yes’, the following procedure
will be executed at
-- the beginning of the rollup phase to summarize transactions.
PROCEDURE aggregate_trx(p_physical_batch_id IN NUMBER);
END cn_aggrt_trx_pkg;
Package Body for the examples:

PACKAGE BODY cn_aggrt_trx_pkg AS
-- $Header: cnagtrxb.pls 115.0 2002/02/14 23:00:01 arkrishn noship $
G_PKG_NAME CONSTANT VARCHAR2(30) :=

’CN_AGGRT_TRX_PKG’;
G_FILE_NAME CONSTANT VARCHAR2(12) := ’cnagtrxb.pls’;
G_LAST_UPDATE_DATE DATE := sysdate;

G_LAST_UPDATED_BY NUMBER := fnd_global.user_id;
G_CREATION_DATE DATE := sysdate;
G_CREATED_BY NUMBER := fnd_global.user_id;
Customized Summarization Code Examples B-1

G_LAST_UPDATE_LOGIN NUMBER := fnd_global.login_id;
G_ROWID VARCHAR2(30);
G_PROGRAM_TYPE VARCHAR2(30);
g_system_rollup_flag VARCHAR2(1);
g_roll_sum_trx_flag VARCHAR2(1);
g_srp_validation_flag VARCHAR2(1);
g_mode VARCHAR2(30);
g_event_log_id NUMBER(15);
type num_tbl_type is table of number index by binary_integer;

type date_tbl_type is table of date index by binary_integer;
type str_tbl_type is table of varchar2(30) index by binary_integer;
PROCEDURE aggregate_trx(p_physical_batch_id IN NUMBER) IS

rep_ids num_tbl_type;
header_ids num_tbl_type;
rollup_dates date_tbl_type;
group_ids num_tbl_type;
rev_class_ids num_tbl_type;
trx_types str_tbl_type;
amounts num_tbl_type;
units num_tbl_type;
processed_dates date_tbl_type;
period_ids num_tbl_type;
tca_amounts num_tbl_type;
l_start_date DATE;
l_end_date DATE;
l_start_period_id NUMBER;
cursor sum_trxs is
select ch.direct_salesrep_id,
ch.processed_period_id,
ch.processed_date,
nvl(ch.rollup_date, ch.processed_date),
ch.comp_group_id,
ch.revenue_class_id,
ch.trx_type,
sum(ch.transaction_amount),
sum(ch.quantity),
sum(ch.attribute58)
from cn_commission_headers ch,
cn_process_batches pb
B-2 Product Title/BookTitle as a Variable

WHERE pb.physical_batch_id = p_physical_batch_id
AND ch.direct_salesrep_id = pb.salesrep_id
and ch.processed_date BETWEEN pb.start_date AND pb.end_date
AND ch.status = ’CLS’
-- this might give better performance
AND ch.revenue_class_id not in
(SELECT revenue_class_id
FROM CN_REVENUE_CLASSES CRCA
WHERE UPPER(NAME) LIKE ’EXA%MRC’)
group by ch.direct_salesrep_id,
ch.processed_date,
ch.comp_group_id,
ch.trx_type;
BEGIN
open sum_trxs;
fetch sum_trxs
bulk collect into
rep_ids,
period_ids,
processed_dates,
rollup_dates,
group_ids,
rev_class_ids,
trx_types,
amounts,
units,
tca_amounts;
close sum_trxs;
IF rep_ids.count > 0 THEN

forall i in rep_ids.first..rep_ids.last
insert into cn_commission_headers
(commission_header_id,
direct_salesrep_id,
processed_date,
trx_type,
status,
rollup_date,
comp_group_id,
revenue_class_id,

transaction_amount,
quantity,
attribute36,
attribute49,
attribute57,
pre_processed_code,
parent_header_id,
creation_date,
created_by)
values
(cn_commission_headers_s.nextval,
rep_ids(i),
processed_dates(i),
period_ids(i),
trx_types(i),
’CLS_SUM’,
rollup_dates(i),
group_ids(i),
rev_class_ids(i),
amounts(i),
units(i),
tca_amounts(i),
1,
1,
’CRPC’,
-1,
sysdate,
g_created_by)
returning commission_header_id bulk collect INTO header_ids;
forall i IN rep_ids.first..rep_ids.last
UPDATE cn_commission_headers
SET parent_header_id = header_ids(i)
WHERE direct_salesrep_id = rep_ids(i)
AND processed_period_id= period_ids(i)
AND processed_date = processed_dates(i)
AND nvl(rollup_date, processed_date) = rollup_dates(i)
AND nvl(comp_group_id, -999999) = nvl(group_ids(i), -999999)
AND revenue_class_id = rev_class_ids(i)
AND trx_type = trx_types(i)
AND status = ’CLS’;
END IF;
update cn_commission_headers
set status = ’CLS_SUM’,

parent_header_id = commission_header_id
where commission_header_id in
(select ch.commission_header_id
where pb.physical_batch_id = p_physical_batch_id
and ch.direct_salesrep_id = pb.salesrep_id
and ch.processed_date BETWEEN pb.start_date AND
pb.end_date
and ch.status = ’CLS’
and ch.revenue_class_id in
(SELECT revenue_class_id
FROM CN_REVENUE_CLASSES CRCA
WHERE UPPER(NAME) LIKE ’EXA%MRC’));
END;
END CN_AGGRT_TRX_PKG;
To customize the code, use one of the three examples below as a basis and make
only the changes you need. Then, add the code that follows example 3.
PACKAGE BODY cn_aggrt_trx_pkg AS Examples to Customize the Summarization
Code
1. To add a summarizing criterion, for example, attribute12, add attribute12 into
select and group by of the summarization SQL, and modify the insert and update
statements accordingly.
cursor sum_trxs is
ch.processed_date,
ch.comp_group_id,
ch.trx_type,
ch.attribute12, --add attribute12
sum(ch.quantity)

ch.processed_date,
ch.comp_group_id,
ch.trx_type,
ch.attribute12; -- add attribute12
2. To get the total value of an attribute column, for example, attribute13, add
sum(attribute13) into the select part. This time, attribute13 is not the summarizing
criteria and should not be added to the group by clause. Modify the insert statement
accordingly.
cursor sum_trxs is
ch.processed_date,
ch.comp_group_id,
ch.trx_type,
sum(ch.quantity),
sum(attribute13) -- add sum(attribute13)
ch.processed_date,
ch.comp_group_id,
ch.trx_type;
3. If transactions of one kind need to be summarized differently from transactions of

another kind, use two separate SQL statements to do it. For example, transactions of

revenue_class_id in list1 are summarized differently from transactions of revenue_
class_id in list2. Modify the insert and update statements (or have two
insert/update statements if needed).
-- cursor for revenue_class_ids in list1

cursor sum_trxs1 is
ch.processed_date,
ch.comp_group_id,
ch.trx_type,
sum(ch.quantity)
and ch.revenue_class_id in (list1) -- constraint on
revenue_class_id
ch.processed_date,
ch.comp_group_id,
ch.trx_type;
-- cursor for revenue_class_ids in list2

cursor sum_trxs2 is
ch.processed_date,
ch.comp_group_id, ch.revenue_class_id,
ch.trx_type,
ch.attribute24,
sum(ch.quantity),
sum(ch.attribute15)

and ch.revenue_class_ids in (list2) -- constraint on
revenue_class_ids
ch.processed_date,
ch.comp_group_id,
ch.trx_type,
ch.attribute24;
This part of the code is used in all of the three customizations above. Add the code
after the code you customized. You can change the variables in the lefthand column
to suit your requirements, but you should leave the rest of the code as it is.
-- type declaration
type num_tbl_type is table of number index by binary_integer;
type date_tbl_type is table of date index by binary_integer;
type str_tbl_type is table of varchar2(30) index by binary_integer;
PROCEDURE aggregate_trx(p_physical_batch_id IN NUMBER) IS

-- declare PL/SQL tables to store the aggregation result
rep_ids num_tbl_type;
header_ids num_tbl_type;
rollup_dates date_tbl_type;
group_ids num_tbl_type;
rev_class_ids num_tbl_type;
trx_types str_tbl_type;
amounts num_tbl_type;
units num_tbl_type;
processed_dates date_tbl_type;
period_ids num_tbl_type;
g_created_by NUMBER := fnd_global.user_id;

g_creation_date date := sysdate;
-- SQL to summarize transactions

cursor sum_trxs is

ch.processed_date,
ch.comp_group_id,
ch.trx_type,
sum(ch.quantity)
ch.processed_date,
ch.comp_group_id,
ch.trx_type;
BEGIN
-- fetch the summarized transactions into PL/SQL tables
open sum_trxs;
fetch sum_trxs bulk collect into rep_ids, period_ids,
processed_dates, rollup_dates,
group_ids,
rev_class_ids, trx_types, amounts, units;
close sum_trxs;
IF rep_ids.count > 0 THEN

-- insert summarized transactions into cn_commission_headers
-- summarized transactions’ status is CLS_SUM
forall i in rep_ids.first..rep_ids.last
insert into cn_commission_headers
(commission_header_id,
direct_salesrep_id,
processed_date,
trx_type,
status,
rollup_date,
comp_group_id,
revenue_class_id,

transaction_amount,
quantity,
pre_processed_code,
parent_header_id,
creation_date,
created_by)
values
(cn_commission_headers_s.nextval,
rep_ids(i),
processed_dates(i),
period_ids(i),
trx_types(i),
’CLS_SUM’,
rollup_dates(i),
group_ids(i),
rev_class_ids(i),
amounts(i),
units(i),
’CRPC’,
-1,
g_creation_date,
g_created_by)
returning commission_header_id bulk collect INTO header_ids;
-- set original transactions’ parent_header_id

-- original transactions remain in CLS status
forall i IN rep_ids.first..rep_ids.last
UPDATE cn_commission_headers
SET parent_header_id = header_ids(i)
WHERE direct_salesrep_id = rep_ids(i)
AND processed_period_id= period_ids(i)
AND processed_date = processed_dates(i)
AND nvl(rollup_date, processed_date) = rollup_dates(i)
AND nvl(comp_group_id, -999999) = nvl(group_ids(i), -999999)
AND revenue_class_id = rev_class_ids(i)
AND trx_type = trx_types(i)
AND status = ’CLS’;
END IF;
end;
END CN_AGGRT_TRX_PKG;

Glossary
These are the terms most commonly used in Oracle Incentive Compensation.
Accelerators
Types of incentives that vary compensation. Payment accelerators are a multiplier
on the compensation rate without affecting the quota. Quota accelerators work on
sales credit, sometimes changing compensation amounts by moving calculation to a
different tier in a rate table
Accumulation Period
The time interval during for which commissions are collected. For example, a
salesperson can have an accumulation period of a month and a pay period of
semimonthly.
Agreement
An agreement is an early stage of a compensation plan used in the planning area of
Oracle Incentive Compensation. In the Modeling tab, incentive planners experiment
with creating an agreement and assigning it to a role before defining details and
associating a resource with a role in the Quota tab.
Application Programmable Interface (API)

A set of procedures to import or export information to and from Oracle Incentive
Compensation.
Attainment Schedule
Attainment schedules enable planners to pay different levels of compensation
depending on the percentage of attainment of a set sales goal. Attainment schedules
are used in the Compensation Contract where earnings for each level of
achievement are displayed.
Glossary-1
Bonus
Incentive compensation typically paid for meeting a goal, including quantitative
and qualitative goals.
Classification Rules
User defined categories used to classify sales transactions. The classified
transactions are part of a classification ruleset. Classification rules vary greatly from
one company to another, depending on the product or service provided and the
different ways that salespeople are compensated.
Classification Ruleset
A group of classification rules assigned to a specific time period or location that
sorts transactions into preset categories, so that they can be compared to revenue
classes in a salesperson’s compensation plan. Only one classification ruleset can be
active at a time.
Collection
The process of collecting transactions from feeder systems into Oracle Incentive
Compensation.
Compensation Group
A group of salespeople who share sales credit, directly or indirectly, when a sale is
made. They are placed together in a compensation group hierarchy to accurately
account for the payment of commission and sales credit. For example, at one
company, when salespeople close a sale, they receive commission, their managers
receive sales credit toward their quotas, territory sales managers receive sales credit
from the manager’s transactions, and territory sales consultants also receive indirect
credit for performing consulting work that helped to close the business.
Compensation Plan
A collection of one or more modular plan elements used to calculate a
compensation payment. One compensation plan is assigned to a sales role, which is
then assigned to a salesperson. Some parts of a compensation plan can be
customized for individual salespeople, such as a payment plan or pay group.
Concurrent Program
Concurrent programs run at the same time as other Oracle Incentive Compensation
functions. For example, you can run a concurrent program to collect transactions
from a transaction source while you are building compensation plans.
Glossary-2
Credit Memo
A document generated when an invoice is fully or partially reversed. Credit memos
are later collected and applied against transactions.
Dimension
Rate dimensions define the tiers that a rate table uses to apply rates. A dimension
contains rate tiers to establish different levels of achievement to be compensated at
different rates.
Direct Sales Credit

Sales credit directly assigned to a salesperson in a transaction in a feeder system,
such as Order Capture or Order Management, or another nonOracle legacy system.
Draw
Draws are a mechanism to pay salespeople a minimum amount of compensation for
a specified period of time. As part of the agreement with salespeople, this amount
can be recoverable or nonrecoverable. You can define the period that the draw and
recovery will be in effect.
Formula
A set of instructions that determines how compensation will be calculated.
Formulas are built from input expressions, output expressions, and rate tables.
Indirect Sales Credit

Credit inherited by a salesperson according to his or her place in the salesperson
hierarchy. Indirect credit can roll up from a subordinate to a manager.
Interval
Intervals are time periods during which a compensation or a plan element is
effective. Plan element intervals must be contained within the effective interval of a
compensation plan.
Interval Type
The time period of the interval, for example, month, quarter, or year.
Job Title
Job titles are used by Human Resources to categorize employees. Oracle Incentive
Compensation uses Roles, and a Job Title can be assigned to a particular Role by
using the Job Titles page.
Glossary-3
Manual Transaction
A user-entered transaction created for reversing or changing sales credit.
Mapping
Rules defining collection that connect the table columns of a feeder system to the
transaction columns in Oracle Incentive Compensation.
Notification Log
The Notification log automatically records every change in the system that affects
calculation and lists what part of the calculation must be rerun as a result of an
event.
Pay Group
An assignment that determines the frequency with which a salesperson receives
payment. A salesperson cannot belong to more than one pay group at a time.
Payment
There are three types of payment:
■ Regular Payment: The application collects data, prepares it, and formats it
to be used by a non-Oracle Payable system.
■ Accounts Payable Integration: Used for vendors, this method prepares
payment for Oracle Accounts Payable by classifying the resources as
suppliers.
■ Payroll Download File: The application collects data and creates a file that
can be used by Oracle Payroll
Payment Plan
An arrangement in affect for some salespeople who need to receive a minimum
payment regardless of their earnings. You can specify a minimum and/or a
maximum payment as well as whether any minimum payments are recoverable or
not against future amounts payable. Payment recovery can be on a separate
schedule from the pay period.
Performance Measure
An accumulation of transaction values that is captured by a Plan Element and
grouped for use in reports that compare achievements to Quota, Goal and
Performance Measure. Performance measures are not used to calculate commission.
Glossary-4
Plan Element
Parts of a compensation plan that may reflect variations of commission or perhaps a
bonus based on the accumulated achievement of the salesperson. Plan elements can
also be configured for tracking nonmonetary credits such as managerial points or
production credits. Plan elements consist of modular components that can be freely
assigned in different combinations, including revenue classes, formulas, and rate
tables.
Push
Push is a way of referring to the movement of an approved and accepted
compensation plan from the planning area into the administrative area of Oracle
Rate Table
Part of a formula, along with input and output expressions, that determines the
amount of compensation based on amount or percentage of achievement compared
to quota.
Regoaling
A new functionality that enables managers to change the quota or variable pay of a
salesperson’s compensation plan at any time. These changes could be required
because of a change in business circumstances, a salesperson is receiving too much
or too little commission, or if a salesperson receives a promotion to a new role with
a new goal. Regoaling can only be used if a plan is already accepted and activated.
Revenue Class
A user-defined category of business revenue used to classify a transaction for
compensation and calculation. Revenue classes are assigned to plan elements and
help Oracle Incentive Compensation determine whether classified sales credit is
applied toward a compensation payment.
Revenue Class Rules

One or more conditions a revenue class must meet to classify into a given revenue
class.
Revenue Class Hierarchy

An arrangement of revenue classes and subclasses in which the broadest classes are
at the top of the structure. Classified transactions are
Glossary-5
Role
A role describes a set of salespeople who share a common compensation structure.
Examples are Salesperson, Consultant, and Regional Sales Manager. In Oracle
Incentive Compensation, you assign each individual salesperson to a
predetermined role, which can be customized in some ways. Changes to a role
affect everyone assigned to that role who does not have the "Customized" check box
checked on the compensation plan. A resource can have more than one role at the
same time.
Ruleset Types
Rulesets are of two types, Revenue Classification and Account Generation.
■ Revenue Classification defines the rules that are used to identify a revenue class
for each transaction that the system processes as part of calculating
commissions.
■ Account Generation is used to integrate Oracle Incentive Compensation
automatically with Accounts Payable and to classify transactions to identify
Expense and Liability Accounts.
Sales Credit
An amount of revenue or nonrevenue credit that is awarded to a salesperson.
Seasonality
use multiple seasonality schedules for different components.
Takeback
The amount of compensation credited for a sale that Oracle Incentive Compensation
takes back when the invoice due date grace period is exceeded. If the invoice is
subsequently paid, then a giveback can be used to restore credit to a salesperson.
Takebacks are sometimes called clawbacks.
Transaction Calendar (Workday Calendar)

A calendar that can be defined to contain only workdays and exclude weekends
and holidays. The workday calendar is a type of transaction calendar. A calendar’s
duration can be defined to match the organization’s financial year. A new workday
calendar can be assigned every year as the dates of holidays and weekends will
differ.
Glossary-6
Transaction Factor
A multipler on sales credit that determines net sales credit given for each type of
transaction.
Glossary-7
Glossary-8

Oracle Incentive Compensation

Uploaded by

Document Informationclick to expand document information

Copyright:

Available Formats

Oracle Incentive Compensation

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

Oracle Incentive Compensation

Uploaded by

Copyright:

Available Formats

Oracle Incentive Compensation

This is a guide to using Oracle Incentive Compensation.

Part No. B10103-01

Copyright © 1996, 2002, Oracle Corporation. All rights reserved.

Primary Author: Steven Schaefer

Oracle is a registered trademark, and OracleMetaLink is a trademark or registered trademark of

Part I Introduction and Overview

1 Introduction to Oracle Incentive Compensation

2 Overview of Using Oracle Incentive Compensation

Part II Incentive Planning

Part III Resources and Compensation Plans

6 Building Compensation Plans

7 Assigning Compensation Plans, Pay Groups, and Payment Plans

Part IV Collection, Calculation, Payment, and Reports

10 Payment with Payruns

A External Formula Code Examples

How To Use This Guide

Accessibility of Code Examples in Documentation JAWS, a Windows screen

Other Information Sources

Documents Related to All Products

Oracle Applications User’s Guide

Documents Related to This Product

Installation and System Administration

Oracle Applications Concepts

Installing Oracle Applications

Oracle Applications Supplemental CRM Installation Steps

Upgrading Oracle Applications

Maintaining Oracle Applications

Oracle Applications System Administrator’s Guide

Oracle Alert User’s Guide

Oracle Applications Developer’s Guide

Oracle Applications User Interface Standards for Forms-Based Products

Other Implementation Documentation

Multiple Reporting Currencies in Oracle Applications

Multiple Organizations in Oracle Applications

Oracle Workflow Guide

Oracle Applications Flexfields Guide

Oracle eTechnical Reference Manuals

Oracle Applications Message Reference Manual

Oracle CRM Application Foundation Implementation Guide

Training and Support

Do Not Use Database Tools to Modify Oracle Applications Data

This part contains the following chapters:

1.1 Overview of Introduction to Oracle Incentive Compensation

Introduction to Oracle Incentive Compensation 1-1

1-2 Oracle Incentive Compensation User Guide

1.2 Oracle Incentive Compensation Key Features

Introduction to Oracle Incentive Compensation 1-3

■ Section 1.2.7, "Hierarchies"

1.2.1 Incentive Planning

1.2.2 Compensation Plans

1-4 Oracle Incentive Compensation User Guide

What Is a Compensation Plan?

Purpose of Compensation Plans

Introduction to Oracle Incentive Compensation 1-5

■ Specify plan changes to occur on specific dates

Using Compensation Plans

1.2.3 Quota Assignment