Oracle® Incentive Compensation: Implementation Guide Release 12

Oracle® Incentive Compensation
Implementation Guide
Release 12
Part No. B25388-04
June 2007
Oracle Incentive Compensation Implementation Guide, Release 12
Part No. B25388-04
Copyright © 1996, 2007, Oracle. All rights reserved.
Primary Author: Steven Schaefer
The Programs (which include both the software and documentation) contain proprietary information; 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. This document is not warranted to be 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.
If the Programs are delivered to the United States Government or anyone licensing or using the Programs on
behalf of the United States Government, the following notice is applicable:
U.S. GOVERNMENT RIGHTS

Programs, software, databases, and related documentation and technical data delivered to U.S. Government
customers are "commercial computer software" or "commercial technical data" pursuant to the applicable
Federal Acquisition Regulation and agency-specific supplemental regulations. As such, use, duplication,
disclosure, modification, and adaptation of the Programs, including documentation and technical data, shall
be subject to the licensing restrictions set forth in the applicable Oracle license agreement, and, to the extent
applicable, the additional rights set forth 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 we disclaim liability for any damages caused by such use of the Programs.
The Programs may provide links to Web sites and access to content, products, and services from third parties.
Oracle is not responsible for the availability of, or any content provided on, third-party Web sites. You bear all
risks associated with the use of such content. If you choose to purchase any products or services from a third
party, the relationship is directly between you and the third party. Oracle is not responsible for: (a) the quality
of third-party products or services; or (b) fulfilling any of the terms of the agreement with the third party,
including delivery of products or services and warranty obligations related to purchased products or services.
Oracle is not responsible for any loss or damage of any sort that you may incur from dealing with any third
party.
Oracle, JD Edwards, PeopleSoft, and Siebel are registered trademarks of Oracle Corporation and/or its
affiliates. Other names may be trademarks of their respective owners.

Contents
Send Us Your Comments
Preface
1 Introduction
Implementing Oracle Incentive Compensation....................................................................... 1-1
Oracle Incentive Compensation Basics.....................................................................................1-2
Responsibilities in the Compensation Process.........................................................................1-2
The Oracle Incentive Compensation Process .......................................................................... 1-3
Getting Started.......................................................................................................................... 1-5
Using the Notes Feature............................................................................................................ 1-6
Starting Implementation........................................................................................................... 1-7
Beginning The Implementation Process...............................................................................1-7
Implementation Task Sequence............................................................................................... 1-8
2 Mandatory Dependencies and Integrations

Mandatory Dependencies......................................................................................................... 2-1
Oracle Resource Manager......................................................................................................... 2-2
Oracle General Ledger.............................................................................................................. 2-3
Integrations................................................................................................................................ 2-3
Oracle Payables......................................................................................................................... 2-4
Oracle Payroll............................................................................................................................ 2-6
Oracle Receivables and Oracle Order Management................................................................ 2-6
Oracle Human Resources.......................................................................................................... 2-7
Oracle Quoting or Third Party Quoting Application............................................................... 2-7
Oracle Territory Manager........................................................................................................ 2-10
iii
Integrate with the Territory Assignment Engine................................................................... 2-12
Modify the Code in the API Template................................................................................... 2-13
Oracle Sales............................................................................................................................. 2-19
3 General Ledger Setups

General Setup Tasks................................................................................................................. 3-1
Define Period Types.................................................................................................................. 3-1
Define Accounting Calendar.................................................................................................... 3-2
Define Periods........................................................................................................................... 3-2
Define Currency........................................................................................................................ 3-2
Define the Set of Books............................................................................................................. 3-2
4 Application Parameter Setups

Application Parameters............................................................................................................. 4-1
Set up General Parameters........................................................................................................ 4-1
Set up General Ledger Parameters............................................................................................ 4-2
Define Interval Settings............................................................................................................ 4-3
Define Credit Types and Conversion Factors...........................................................................4-3
5 Collection Setups
Set up Collection Parameters.................................................................................................... 5-1
Configure Tables and Columns for Collection........................................................................ 5-2
Define External Table Mapping for Collection........................................................................ 5-3
Define Collection Sources and Mapping................................................................................. 5-4
Add a New Transaction Source to the TRX TYPES Lookup.................................................... 5-6
Source Table.............................................................................................................................. 5-7
Parameters................................................................................................................................. 5-7
Notification Queries.................................................................................................................. 5-8
Column Mapping...................................................................................................................... 5-8
Collection Query..................................................................................................................... 5-10
Triggers.................................................................................................................................... 5-10
Filters....................................................................................................................................... 5-11
Generate Collection Packages................................................................................................. 5-11
6 Calculation Setups
Calculation Setup...................................................................................................................... 6-1
Set Up Calculation Parameters..................................................................................................6-2
Configure Tables and Columns for Calculation...................................................................... 6-4
Define External Table Mappings for Calculation.................................................................... 6-5
iv
7 Payment Setups
Set Up Payment Parameters...................................................................................................... 7-1
Account Generator..................................................................................................................... 7-2
Define Pay Element Mappings................................................................................................. 7-3
8 Credit Allocation Setups

Introduction............................................................................................................................... 8-1
Set up a New Transaction Source............................................................................................. 8-1
Configure Transaction Source Mappings................................................................................. 8-2
Set up Workflow Options......................................................................................................... 8-2
Set Up Workflow Background Process..................................................................................... 8-4
View Workflow Background Process Results.......................................................................... 8-5
9 Profile Options
Profile Options.......................................................................................................................... 9-1
Table of Profile Options............................................................................................................ 9-4
10 Lookups
Lookups................................................................................................................................... 10-1
Viewing and Editing Lookups................................................................................................ 10-1
Creating a Lookup................................................................................................................... 10-2
List of Lookups........................................................................................................................ 10-2
11 Flexfields
Flexfields................................................................................................................................. 11-1
A SQL Insert Statement for Credit Allocation

SQL INSERT STATEMENT FOR CREDIT ALLOCATION................................................... A-1
Index
v

Send Us Your Comments
Oracle Incentive Compensation Implementation Guide, Release 12

Part No. B25388-04
Oracle welcomes customers' comments and suggestions on the quality and usefulness of this document.
Your feedback is important, and helps us to best meet your needs as a user of our products. For example:
• Are the implementation steps correct and complete?
• Did you understand the context of the procedures?
• Did you find any errors in the information?
• Does the structure of the information help you with your tasks?
• Do you need different information or graphics? If so, where, and in what format?
• Are the examples correct? Do you need more examples?
If you find any errors or have any other suggestions for improvement, then please tell us your name, the
name of the company who has licensed our products, the title and part number of the documentation and
the chapter, section, and page number (if available).
Note: Before sending us your comments, you might like to check that you have the latest version of the
document and if any concerns are already addressed. To do this, access the new Applications Release
Online Documentation CD available on Oracle MetaLink and www.oracle.com. It contains the most
current Documentation Library plus all documents revised or released recently.
Send your comments to us using the electronic mail address: appsdoc_us@oracle.com
Please give your name, address, electronic mail address, and telephone number (optional).
If you need assistance with Oracle software, then please contact your support representative or Oracle
Support Services.
If you require training or instruction in using Oracle software, then please contact your Oracle local office
and inquire about our Oracle University offerings. A list of Oracle offices is available on our Web site at
www.oracle.com.
vii

Preface
Intended Audience
Welcome to Release 12 of the Oracle Incentive Compensation Implementation 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 Applications
training classes available through Oracle University.
• Oracle Self-Service Web Applications. To learn more about Oracle Self-Service Web
Applications, read the Oracle Self-Service Web Applications Implementation
Manual.
• The Oracle Applications graphical user interface. To learn more about the Oracle
Applications graphical user interface, read the Oracle Applications User's Guide.
The Oracle Incentive Compensation Implementation Guide contains the information

you need to understand and use Oracle Incentive Compensation. This guide contains
eleven chapters, one appendix, and an index:
• Chapter 1 provides an introduction to the implementation process.
• Chapter 2 describes mandatory dependencies and integrations with other Oracle

products.
• Chapter 3 gives guidance for general ledger setup tasks to be performed before the
main work of implementation begins.
• Chapter 4 covers Application Parameters.
ix
• Chapter 5 presents Collection setups.
• Chapter 6 describes Calculation setups.
• Chapter 7 talks about Payment setups.
• Chapter 8 contains setup steps for Credit Allocation, an optional feature.
• Chapter 9 details the profile options used in this release of Oracle Incentive
Compensation.
• Chapter 10 presents the lookups used in Oracle Incentive Compensation, updated

for this latest release of the product.
• Chapter 11 contains a detailed listing of flexfields used in Oracle Incentive

Compensation.
• Appendix A provides a SQL insert statement for Credit Allocation.
• The Index makes it easy for users to find specific information.
See Related Information Sources on page xi for more Oracle Applications product
information.
TTY Access to Oracle Support Services

Oracle provides dedicated Text Telephone (TTY) access to Oracle Support Services
within the United States of America 24 hours a day, seven days a week. For TTY
support, call 800.446.2398.
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. Accessibility standards will continue to
evolve over time, and Oracle 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 more information, visit the Oracle Accessibility Program Web site
at http://www.oracle.com/accessibility/ .
Accessibility of Code Examples in Documentation

Screen readers 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
x
empty line; however, some screen readers may not always read a line of text that
consists solely of a bracket or brace.
Accessibility of Links to External Web Sites in Documentation

This documentation may contain links to Web sites of other companies or organizations
that Oracle does not own or control. Oracle neither evaluates nor makes any
representations regarding the accessibility of these Web sites.
Structure
1 Introduction
2 Mandatory Dependencies and Integrations
3 General Ledger Setups
4 Application Parameter Setups
5 Collection Setups
6 Calculation Setups
7 Payment Setups
8 Credit Allocation Setups
9 Profile Options
10 Lookups
11 Flexfields
A SQL Insert Statement for Credit Allocation
Related Information Sources

You can choose from many sources of information, including 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 12 versions of those guides.
For a full list of documentation resources for Oracle Applications Release 12, see Oracle
Applications Documentation Resources, Release 12, OracleMetaLink Document
394692.1.
Online Documentation
All Oracle Applications documentation is available online (HTML or PDF).
PDF Documentation
See the Documentation CD provided with each release for current PDF documentation
for your product. This Documentation CD is also available on OracleMetaLink and is
updated frequently.
Online Help
You can refer to Oracle Applications Help for current HTML online help for your
product. Oracle provides patchable online help, which you can apply to your system for
updated implementation and end user documentation. No system downtime is
xi
required to apply online help.
R12 Release Content Document
Refer to the Release Content Document for new features listed release. The Release
Content Document is available on OracleMetaLink.
R12 Functional Upgrade Document
Refer to the R12 Functional Upgrade document for details on upgrading to R12 It is
available on OracleMetaLink (Document ID: 414710.1).
R12 Integration Repository
The R12 Integration Repository contains reference documentation on R12 OIC API's. To
access the Integration Repository, do the following:
1. Add the Integration Repository responsibility to a user, and log in to Self-Service as
that user.
2. When the Integration Repository launches, expand the Marketing and Sales Suite
node in the left navigation pane.
3. Expand the Incentive Compensation node, and click the Incentive Compensation
Plan link to browse the list of OIC API's
Related Guides
Oracle Incentive Compensation shares business and setup information with other
Oracle Applications products. Therefore, you may want to refer to other guides when
you set up and use Oracle Incentive Compensation.
You can read the guides 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.
Guides 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). 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.
Oracle Applications Developer's Guide
If you will be building custom logic into your application, please read the
Customization Standards chapter in the this guide.
xii
Guides Related to This Product
Oracle Incentive Compensation User Guide
Use this user guide to manage Oracle Incentive Compensation on a day-to-day basis.
Learn how to distribute quota, create compensation plans, collect transactions, calculate
and pay commission, and use Sales Credit Allocation.
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 12. 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 12, much of the installation process is handled using Oracle Rapid
Install, which minimizes the time to install Oracle Applications and the Oracle
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 guides and implementation guides.
Upgrading Oracle Applications
Refer to this guide if you are upgrading your Oracle Applications to Release 12. This
guide describes the upgrade process and lists database and product-specific upgrade
tasks.
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
xiii
development staff and describes the Oracle Application Object Library components that
are needed to implement the Oracle Applications user interface described in the Oracle
Applications User Interface Standards for Forms-Based Products. This manual also
provides information to help you build your custom Oracle Forms Developer forms so
that the forms integrate with Oracle Applications.
Integration Repository
The Oracle Integration Repository is a compilation of information about the service
endpoints exposed by the Oracle E-Business Suite of applications. It provides a
complete catalog of Oracle E-Business Suite's business service interfaces. The tool lets
users easily discover and deploy the appropriate business service interface for
integration with any system, application, or business partner.
The Oracle Integration Repository is shipped as part of the E-Business Suite. As your
instance is patched, the repository is automatically updated with content appropriate
for the precise revisions of interfaces in your environment.
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 an
Oracle Applications form 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.
xiv
1
Introduction
Implementing Oracle Incentive Compensation

Oracle Incentive Compensation is a sophisticated application that helps enterprises
manage their business objectives by controlling the way they compensate their sales
forces. However, many setups must be performed before anyone can actually build
compensation plans or pay salespeople for their efforts. This document is intended as a
first guide for customers and implementers of Oracle Incentive Compensation to
understand the scope, breadth, and depth of implementing the application, and how
Oracle Incentive Compensation leverages components of the Oracle E-Business Suite.
Oracle Incentive Compensation is designed to calculate and pay compensation to
salespeople (resources). Although Oracle Incentive Compensation is typically used to
compensate salespeople, it is flexible enough to compensation nonemployees, such as
vendors, suppliers, and partners.
Oracle Incentive Compensation can calculate monetary commissions as well as
nonmonetary commission, such as points.
This document does not address creating or assigning compensation plans, or with the
actual collection, calculation, or payment of compensation. See the Oracle Incentive
Compensation User Guide for those procedures.
Oracle Incentive Compensation integrates with other applications in the Oracle
E-Business Suite. Integrations with Oracle Resource Manager and Oracle General
Ledger are mandatory, because they are the repositories of information on employees in
Oracle Human Resources and accounting information. Using one central source of truth
for all Oracle applications helps to minimize errors and duplication. Oracle Incentive
Compensation is set up with out-of-the-box integration with Oracle Receivables and
Oracle Order Management, but is flexible enough to work with legacy applications.
The same can be said for the other end of the sales compensation process. Oracle Payroll
is used for paying salespeople and Oracle Payables can be set up to pay vendors and
suppliers. The Oracle Sales application uses reports from the application and Oracle
Quoting uses Oracle Incentive Compensation for projecting sales compensation. Oracle
Introduction 1-1
Incentive Compensation integrates with Oracle Territory Manager for sales credit
allocation, which is the process of determining who receives credit for sales
transactions.
Oracle Incentive Compensation supports multiple operating units within your
enterprise. At the operating unit level, sets of books, payment intervals, and matters of
credit types and credit conversion are determined. The tables used in collecting,
calculating, and paying resources are part of the operating unit setup regimen.
Oracle Incentive Compensation Basics

Here's a quick run through Oracle Incentive Compensation's basic features.
Oracle Incentive Compensation collects transactions, calculates commissions earned
and determines what to pay. The collected transactions are run against compensation
plans to determine if salespeople (known as resources in the application) are eligible for
compensation. The application calculates how much is earned and how much is to be
paid, and exports commission payments to payroll or Oracle Payables for actual
payment.
Oracle Incentive Compensation can compensate for a variety of resources, including
people or organizations, employees or vendors, suppliers, partners, and so on, as long
as they can be modeled in Oracle Resource Manager. Out of the box, Oracle Resource
Manager can import and synchronize employee data from Oracle HR. This enables
Oracle Incentive Compensation to collect order and invoice transactions from Oracle
Order Management and Oracle Receivables. Oracle Incentive Compensation also can be
configured to collect from legacy or other transaction sources. If you have a large
number of transaction sources you can use Oracle Data Warehouse/Warehouse Builder
to assist in the management of data collection.
Some collected transactions may require further processing to determine who to credit
and/or how much to credit for each transaction. As part of a post collection process,
Oracle Incentive Compensation integrates with Oracle Territory Manager to determine
who is a credit receiver and uses the Sales Credit Allocation module within Oracle
Incentive Compensation to determine the credit percentage that each resource receives
from an order line or an invoice line.
Oracle Incentive Compensation integrates out of the box with Oracle Payroll for
employees and with Oracle Payables for suppliers and vendors. The same interface
table can be used to integrate to legacy or other payroll and accounts payable systems.
To directly align and incent your salesforce to corporate objectives, Oracle Quoting
integrates to Oracle Incentive Compensation to provide projected commissions on
quotes.
Responsibilities in the Compensation Process

Oracle Incentive Compensation is delivered with six seeded responsibilities to establish
a pathway through the many procedures necessary for implementation and use of the
1-2 Oracle Incentive Compensation Implementation Guide

application. Your system administrator can configure responsibilities to match your
implementation requirements.
The responsibilities in this release have changed. For information on mapping resources
from the previous responsibilities to the new ones, see the Oracle Applications Upgrade
Guide: Release 11i to Release 12.
The process of Incentive Compensation normally starts with a group of people who
design the compensation plans. This group may include employees from Sales, Finance,
Human Resources, or a combination of people from all of these organizations. After the
organization has signed off on the content of the plans, the plans are created in Oracle
Incentive Compensation by the Plan Administrator. Other duties of the Plan
Administrator include creating and maintain the rules and rule hierarchies used in
classifying transactions and for other purposes.
However, before that is possible, all of the necessary setups must be performed by the
Incentive Compensation Administrator. For instance, the Incentive Compensation
Administrator sets up dependencies and integrations with other products in the
E-Business Suite, such as Order Management or Accounts Receivable. These tasks can
be operating unit specific or not.
Operating unit specific setups are accessed through the Configuration Workbench,
which steps the Incentive Compensation Administrator through the various setups and
provides a mechanism to help them to track the implementation work they have
completed. The Configuration Workbench is organized into 5 areas: Application
Parameters, Collection, Calculation, Payment and Credit Allocation.
After the plans are modeled in Oracle Incentive Compensation, a group is responsible
for the day to day administration of collecting, calculating and paying compensation.
This is the typical domain of a compensation group of Compensation Analysts and
Compensation Managers.
Oracle Incentive Compensation gives salespeople and their managers access to reports
through the Incentive Compensation User and Incentive Compensation Manager
responsibilities. Incentive Compensation Managers can see not only their own
compensation reports but also the reports of the people who work for them.
This Implementation Guide focuses primarily on the tasks of the Incentive
Compensation Administrator. The Oracle Incentive Compensation User Guide covers plan
creation, as well as the collection of transactions and the calculation and payment of
commission.
The Oracle Incentive Compensation Process

The illustration below shows how transactions are collected into Oracle Incentive
Compensation and processed in order to pay commission to resources. The process
allows for alternative methods in the collection sources, collection method, and
payment options.
Transactions are collected from the standard transaction sources, Order Management
Introduction 1-3
and Oracle Receivables (Order Booking), but can also be collected from custom and
legacy sources. You can import the transaction data directly using a CSV file, a
delivered API, or you can manually input transactions.
If you want to use Credit Allocation to determine who receives how much credit for
transactions, it takes care of loading on its own. If no credit allocation is required, you
can simply load the transactions for calculation. The Projected Compensation feature
uses Credit Allocation and the Calculation engine to provide approximate commission
figures for Oracle Quoting.
After the Calculation Engine has run, the Payment function sends commission data to
Oracle Payables for vendors and to Payroll for regular employees. A custom payroll
system also can be used.
Reports are available at the end of this process, which are used by the Oracle Sales
application.

Transaction Flow in Oracle Incentive Compensation
Getting Started
To begin implementation, log in to the Incentive Compensation Administrator
responsibility and click the Configuration Workbench link. The Setup Tasks page
appears, listing the five main areas involved with implementation.
On the Setup Tasks page, select an operating unit if your enterprise has multiple
operating units. To perform implementation tasks, click the icons in the Go to Task
column to go to the Tasks List for each section. The Status column in the Tasks List
pages is manually set by you. Use it to keep track of your progress.
You can set up favorites on the Configuration Workbench page. If you want to return to
this page after working in a specific area of the application, click the Home link.
Oracle Incentive Compensation pages display the page navigation along the top, for
Introduction 1-5
example, Setup Tasks > Application Parameters: Vision Operations >. This helps guide you
as you work in the application. Use these links to return to previous pages--don't use
the browser's Back button. Using the back button could create errors.
Using the Configuration Workbench

Oracle Incentive Compensation provides the Configuration Workbench to guide you
through the implementation process. Below is a screenshot of the initial page you see
when you enter the Configuration Workbench.
To begin the implementation, click the Application Parameters icon. Within Application
Parameters, you can set up general and general ledger parameters, define interval
settings, and set up credit types and credit conversion factors.
Using the Notes Feature

Oracle Incentive Compensation provides a Notes feature throughout the product. Notes
are useful for keeping track of changes that are made to setups. Notes aid in
Sarbanes-Oxley (SOX) compliance, as well.
Most pages contain a Notes History feature, and many also have an Add Note ability.
You can sort through the notes to find relevant information quickly. Notes are kept in
context to simplify the search and review process.
There are two kinds of notes--system generated and user entered. System generated
notes are created automatically when an action is performed, such as when you change
a parameter or create a new credit type. You enter user notes yourself to provide

additional information or to explain to other system users why you made a change or
performed an action.
Starting Implementation
Beginning The Implementation Process

The graphic below shows the basic setup flow of Oracle Incentive Compensation.
Implementation is primarily handled by the Incentive Compensation Administrator
using the Configuration Workbench. The graphic shows how after this initial setup
process, other responsibilities work with Resource Manager, set up hierarchies, build
compensation plans, and finish the job of setting up Oracle Incentive Compensation.
This document deals with activities performed by the Incentive Compensation
Administrator. The specific implementation steps are presented in detail following the
graphic.
Introduction 1-7
Setup Process Flow
Implementation Task Sequence

The steps needed for implementing Oracle Incentive Compensation are listed in the
recommended order in which they should be carried out. When the step includes steps
performed in another application, the relevant implementation guide is referenced.
Oracle strongly recommends that you implement Oracle Incentive Compensation in the
order listed.
The following table summarizes the necessary steps to successfully implement Oracle
Incentive Compensation. Further information detailing the implementation procedures
is provided in the sections following the table.

Prerequisites
Completion of installation and implementation steps as outlined in the following
documents:
• Oracle System Administrator's Guide
• Supplemental CRM Installation Steps Release 12
Standard Oracle Incentive Compensation Process
Step Description
PERFORM MANDATORY Oracle Resource Manager and Oracle

DEPENDENCIES AND INTEGRATIONS General Ledger are required. Other
integrations, such as Oracle Payroll and
Oracle Territory Manager, are optional. See
Chapter 2.
PERFORM GENERAL LEDGER SETUPS Oracle General Ledger provides the

accounting environment for Oracle
Incentive Compensation to work. You must
define period types, accounting calendar,
periods, functional currency, and set of
books in Oracle General Ledger. See
Chapter 3.
SET UP APPLICATION PARAMETERS The four sections below are essential setups
for the application to perform collection,
calculation, and payment. See Chapter 4.
Set up General Parameters Select your type of currency conversion and

indicate whether you will customize
compensation plans. Select a sales hierarchy
to provides secure access to resource data. If
your company doesn't use draws, you can
prevent draws from appearing on the Data
Summary Report.
Set up General Ledger Parameters Confirm your setups in General Ledger,

including set of books, functional currency,
accounting calendar, and period type.
Define Interval Settings Group predefined periods into intervals for

measuring sales achievement for bonus and
commission calculation.
Introduction 1-9
Step Description
Define Credit Types and Credit Conversion Define the credit types you need and set up
Factors conversion based on rates that you defined
previously in General Ledger.
PERFORM COLLECTION SETUPS In this part of the Configuration Workbench

you work with tables and columns to set up
the exact way that collection functions,
including defining parameters, external
table mapping, and collection sources and
mapping. See Chapter 5.
Set up Collection Parameters Set collection batch size, number of

clawback days, other collection parameters
Configure Tables and Columns Optional. Define tables and columns used in
collecting transactions into the application.
Define External Table Mapping Optional. Join external tables to destination

tables in the application if you need to use
data from external tables.
Define Collection Sources and Mapping Configure seeded transaction sources or

define new ones. Register tables, define
notification queries and runtime
parameters, define mapping, define
triggers, define filters, special features
Generate Collection Packages Define how you want collection to be

processed. You can test generate a collection
package first to verify that it works
properly.
PERFORM CALCULATION SETUPS Specify how you want calculation to work

in your instance of Oracle Incentive
Compensation and configure table and
column mappings, including external
tables. See Chapter 6.
Set up Calculation Parameters Set up batch sizes, set rate table precision,
and make other selections to configure the
calculation process.

Step Description
Configure Tables and Columns Optional. Define tables and columns used in
calculating commissions.
Define External Table Mappings Optional. Join external tables to destination

tables if needed for calculation purposes.
PERFORM PAYMENT SETUPS To define how you want the application to

produce payment batches, set up payment
parameters and define pay element
mappings in this section. See Chapter 7.
Set up Payment Parameters Select integration with Oracle Payroll or

Oracle Payables. If you select Oracle
Payables, you can specify at what level
account generation takes place.
Define Pay Element Mappings If you are integrating with Oracle Payroll,
you must map Oracle Incentive
Compensation plan elements with Oracle
Payroll pay elements.
PERFORM CREDIT ALLOCATION The Configuration Workbench has one

SETUPS section for configuring transaction source
mappings, but other necessary steps include
setting up profile options, workflow
options, and the workflow background
process. See Chapter 8.
Configure Transaction Source Mappings It is important to synchronize credit rules

and configure transaction source mappings.
MAINTAIN SYSTEM PROFILES System profiles allow you to further

configure the application to suit your needs.
See Chapter 9.
CREATE AND MAINTAIN LOOKUPS Lookups are preset selections for Lists of
Values. See Chapter 10.
MAINTAIN FLEXFIELDS Flexfields provide additional input fields on

a page with preset names and specific sets
of values. See Chapter 11.
Introduction 1-11
2
Mandatory Dependencies and Integrations
This chapter covers the following topics:

• Mandatory Dependencies
• Oracle Resource Manager
• Oracle General Ledger
• Integrations
• Oracle Payables
• Oracle Payroll
• Oracle Receivables and Oracle Order Management
• Oracle Human Resources
• Oracle Quoting or Third Party Quoting Application
• Oracle Territory Manager
• Integrate with the Territory Assignment Engine
• Modify the Code in the API Template
• Oracle Sales
Mandatory Dependencies
Oracle Incentive Compensation requires the following related products and
components to be installed and implemented:
• Oracle Resource Manager
• Oracle General Ledger
Resource Manager is the common source for resource definition. The ability of Oracle
Incentive Compensation to read Resource Manager directly eliminates the need to
create commonly used definitions and relationships in multiple applications.
Mandatory Dependencies and Integrations 2-1

Oracle General Ledger contains all of the accounting information that is used by Oracle
Incentive Compensation. Everything that is necessary for running Oracle Incentive
Compensation is included during setup.
Oracle Resource Manager

Use Resource Manager to:
• Create resources
• Create sales roles and assign them to resources
• Create compensation groups and teams
• Create hierarchies
The Compensation Manager maintains resources, roles, groups, and teams. See the
Oracle Incentive Compensation User Guide, Chapter 3, for details.
Refer to appropriate sections of the OracleCommon Application Components
Implementation Guide or OracleCommon Application Components User Guide.
Create Resources
To receive commission payments in Oracle Incentive Compensation, the resource must
be created, assigned a sales compensation role and assigned a compensation group. The
roles and groups are created in Resource Manager, and the assignment takes place
when employee resources are imported from HR. Resources that are not salespeople,
for example, nonemployees set up as supplier vendors or TBH (to be hired), are not
imported from HR, but are created directly in Resource Manager. See the Creating and
Importing Resources chapter in the Oracle Common Application Components
Implementation Guide for the procedures.
Create and Assign Sales Roles
In Oracle Incentive Compensation, compensation plans are assigned to roles, and the
salespeople are assigned a role. A Role may encompass one or more job descriptions
and job titles. Within the role type used for Oracle Incentive Compensation, roles are
assigned to resources, resource groups and resource teams. Oracle Resource Manager is
delivered with predefined role types for all CRM modules, including Oracle Incentive
Compensation, however you can define additional custom roles for your enterprise.
The role types for Incentive Compensation include Sales Compensation and Sales
Compensation Payment Analyst. See the Managing Roles and Role Types chapter in the
Oracle Common Application Components Implementation Guide for the steps for this
procedure.
Create Compensation Groups
Resources must belong to a group to receive payments in Oracle Incentive
Compensation. Groups are created in Resource Manager. A group is based on the
similar functionality or roles of its members. Groups exist in a hierarchy, with parent

and child groups defining the structure of the sales organization. Groups must have the
usage type of Sales Compensation in order to be used in Oracle Incentive
Compensation.
A Team is a type of group in which the members work together to complete a project.
Teams and groups are both created in Resource Manager, and are assigned when you
import the resource from HR. See the Managing Teams and Groups chapter in the
Oracle Common Application Components Implementation Guide.
Create Reporting and Payment Analyst Hierarchies
In Resource Manager, when you set up resources and groups, you select reporting
hierarchies, which determine who has access to information. These include Sales and
Telesales, Sales Compensation, and Compensation Reporting Hierarchy.
The Compensation Reporting Hierarchy usage in Resource Manager determines user
access to the Commission Statement report. This usage makes it easier to set up
reporting structures so that managers have access to commission statements for the
people that report to them. This usage can be selected using this system parameter:
Reporting Hierarchy for Manager Access to Resources Reports. It is located on the Set
Up General Parameters section of the Configuration Workbench. See Set Up General
Parameters, page 4-1.
Oracle General Ledger

Oracle General Ledger is a necessary part of an Oracle Incentive Compensation
implementation. Oracle Incentive Compensation uses calendars and periods from
General Ledger to calculate commission. You must select these General Ledger setups
at the beginning of the implementation process. See Chapter 3, General Setup Tasks, for
more information, and also Chapter 4, Operating Unit Specific Setup Tasks, Set up
General Ledger Parameters section, for details.
Also see the Oracle General Ledger User Guide.
Integrations
Oracle Payables, page 2-4 is used to pay companies who are vendors or suppliers, or
resources who are not full-time, regular employees. Oracle Payables recognizes
resources for payment only if they are activated as suppliers.
Oracle Payroll, page 2-6 is used by the application to pay employees.
Oracle Receivables and Oracle Order Management are the standard collection sources
for transactions in Oracle Incentive Compensation. You can also define custom sources.
Oracle Human Resources is where you must first create employees in order for them to
be paid compensation in Oracle Incentive Compensation. After creating employees in
Human Resources, you then import these records into Resource Manager to create
resources. See the Oracle Incentive Compensation User Guide, Resource section. See Oracle
Human Resources documentation for the procedures for creating employees.

Oracle Quoting, page 2-7 uses Oracle Incentive Compensation to project commissions
for resources and for Credit Allocation. Oracle Incentive Compensation receives data
through an API and then sends back projected commissions to Oracle Quoting. Because
the projected commissions calculator is less complex than a compensation plan, the
projections are approximate. The more complex the compensation plan, the more
inaccurate the projection may be.
Oracle Territory Manager, page 2-10 provides integration with the Territory
Assignment Engine for Credit Allocation. See Chapter 5, Implementing Credit
Allocation.
Oracle Sales, page 2-19 integrates with Oracle Incentive Compensation to provide
resources access to view their commission statements.
Oracle Workflow is a workflow management system that is used by Oracle Incentive
Compensation to integrate business processes. Workflow is already configured for use
in Oracle Incentive Compensation and does not require any setups.
Oracle Payables
Full-time, regular employees are paid using Payroll. If you want to pay commission to
other resources who are not part of your standard payroll system, you can set them up
as suppliers in Oracle Purchasing. This creates an integration with Oracle Payables to
pay the resource. For purposes of collecting transactions and paying commissions,
Oracle Incentive Compensation treats a supplier contact the same as any other resource.
To enable integration with Oracle Payables, see the Payment Setups in the
Configuration Workbench.
For the steps to this procedure, see the Oracle Payables User Guide. Please also refer to the
Oracle Purchasing User's Guide for more information.
After a payment batch has been processed (Paid status against the payment batch
name), the Salespeople Sub-ledgers are updated to reflect the amounts paid in the
appropriate accounts and balances, and the data is transferred to the Oracle Payables
Invoices Interface table.
Oracle Payables uses two interface tables as entry points for data from other
applications, including Oracle Incentive Compensation:
• AP_INVOICES_INTERFACE
• AP_INVOICE_LINES_INTERFACE
The following two tables show the columns that map to the columns in each invoice
interface table in Oracle Payables:

AP_INVOICES_INTERFACE Populated with
INVOICE_ID AP_INVOICES_INTERFACE_S.NEXTVAL
INVOICE_NUM CN_PAYMENT_TRANSACTIONS.PAYMEN
T_TRANSACTION_ID
INVOICE_DATE CN_PAYRUNS.PAY_DATE
VENDOR_ID PO_VENDOR_SITES.VENDOR_ID
VENDOR_SITE_ID PO_VENDOR_SITES.VENDOR_SITE_ID
INVOICE_AMOUNT CN_PAYMENT_TRANSACTIONS.PAYMEN
T_AMOUNT
INVOICE_CURRENCY_CODE FUNCTIONAL CURRENCY CODE
PAYMENT_CURRENCY_CODE REP CURRENCY CODE
SOURCE ORACLE.SALES.COMPENSATION
ACCTS_PAY_CODE_COMBINATION_ID CN_PAYMENT_TRANSACTIONS.LIABILIT
Y_CCID
INVOICE_TYPE_LOOKUP_CODE CREDIT (if amount <0); STANDARD (if

amount >0)
AP_INVOICE_LINES_INTERFACE Populated with
INVOICE_ID Same value as entered for

AP_INVOICES_INTERFACE
INVOICE_LINE_ID AP_INVOICE_LINES_INTERFACE_S.NEXTV
AL
LINE_NUMBER 1
LINE_TYPE_LOOKUP_CODE ITEM

AP_INVOICE_LINES_INTERFACE Populated with
AMOUNT CN_PAYMENT_TRANSACTIONS.PAYMEN
T_AMOUNT
DIST_CODE_COMBINATION_ID CN_PAYMENT_TRANSACTIONS.EXPENSE
_CCID
Oracle Payroll
You can integrate Oracle Incentive Compensation with Oracle Payroll for employee
type resources. When enabled, this integration transfers data from Oracle Incentive
Compensation to the Oracle Payroll Batch Element Entry (BEE) interface. Oracle
Incentive Compensation has an API that calls the payroll package to populate data into
the BEE interface.
The payroll mapping is stored in these tables:
• CN_QUOTAS_PAY_ELEMENTS_ALL
• CN_PAY_ELEMENT_INPUTS_ALL
A resource must already be set up in Resource Manager and be assigned to a role with a
compensation plan. See Defining Resources and Assign Resources to Roles and Groups
in the Oracle Incentive Compensation User Guide. Pay elements must be set up in Oracle
Payroll.
Navigation
Setup Tasks > Payment > Setup Payment Parameters
Steps:
1. Check the Integration to Oracle Payroll box. See Payment, page 7-1.
2. Map plan elements in Oracle Incentive Compensation to pay elements in Oracle

Payroll. See Define Pay Element Mappings, page 7-3.
3. Map Pay Element Input Values.
Oracle Receivables and Oracle Order Management

Transactions are primarily collected from Oracle Receivables and Oracle Order
Management. These are the standard transaction sources included in the application.
Oracle Incentive Compensation transactions can originate from a sales order, a

customer billing, a customer payment, or other business events.
As a customization, you can use APIs to bring transactions into Oracle Incentive
Compensation and to send transactions out to other systems.
From Oracle Receivables, you can collect the following types of transaction data:
• Invoices
• Credit and debit memos
• Payment postings
• Write-off postings
• Take-back (claw-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
resource's sales credit.
• Give-back postings, which are generated when a past due invoice that has been
deducted from the resource's sales credit is paid. The resource receives the credit.
• Revenue Adjustment Module (RAM) Adjustments, which makes transaction

adjustments one time, in Oracle Receivables using RAM (Revenue Adjustment
Module), and collects the adjustments into Oracle Incentive Compensation.
From Oracle Order Management, you can collect booked orders and adjustments to
booked orders.
To select these or any custom transaction source, go to the Configuration Workbench
and select Collection > Define Collection Sources and Mapping.
Oracle Human Resources

In Oracle Human Resources Management System (Oracle HRMS), you create
employees in order for them to be paid compensation in Oracle Incentive
Compensation. See Oracle Human Resource Management System documentation for
specific details of this procedure.
In addition, there is an integration that enables the compensation workbench in Oracle
HRMS to call an API to determine an employee's variable compensation earned and
paid for a given date range. Because the actual payment to a resource is made through
Oracle Payroll, Oracle Payables, or another third party payment system, the
compensation paid amount may or may not be the amount the resource receives.
Oracle Quoting or Third Party Quoting Application

Out of the box, Oracle Quoting integrates to Oracle Incentive Compensation's projected
commission API. After viewing the projected commission amounts, Oracle Quoting

users can perform commission what-if analysis by changing quantities and prices of the
items. This, in turn, alters the sales credit amount and recalculates the projected
commission. The changes are not saved to the quote itself--they are used only for
projecting commission. Projected commission can be displayed at three levels of
granularity: the header level, product category level, or individual quote line level.
When integrating with Oracle Quoting, you must set four profile options:
• ASO: Calculate Projected Commission - YES at the Site and Application level
• ASO: Automatic Sales Credit Allocation - Partial at the Site level
• ASO: Automatic Sales Team Assignment - Partial at the Site level
• MO: Operating Unit - This must be set at the responsibility level, but can be
overridden at the user level.
See the Profiles chapter for more information, or refer to the Oracle Quoting
Implementation Guide .
If Sales Credit Allocation is implemented as well, you must refresh sales credit before
viewing commissions.
There is a public API that you can use to project commission for salespeople. Projected
Compensation provides an estimation of projected variable compensation earnings and
their potential impact on quota attainment. Oracle Quoting uses Sales Credit Allocation.
Oracle Incentive Compensation receives data through the API and then sends back
projected commissions to the calling application. See the Oracle Incentive Compensation
API Reference Guide, for details on the API.
The projection calculator cannot be configured with the complexity of an actual
compensation plan, so projections are estimates only and are not guaranteed amounts.
The more complex the compensation plan, the more inaccurate the projection can be.
You can include disclaimer text in the output.
The calling application provides the following values to the Oracle Incentive
Compensation API table (CN_PROJ_COMPENSATION_GTT):
• resource_id
• Sales_credit_amount
• calc_date
• currency_code
• projection_identifier
In order for the application to process the projected commission, the following must be
verified:

• The resource has a compensation role for the date of the projection.
• The compensation plan is valid for the date of the projection.
• The plan element is Commission incentive type and is valid for the date of the
projection.
• The formula package is generated and has a status of VALID.
• The Plan Element Classification rule set must be valid for the date of the projection.
Oracle Incentive Compensation returns the following information to the calling

application:
• Plan Element Name (PE_NAME)
• Projected Compensation (PROJ_COMP)
• Plan Element Quota (PE_QUOTA)
• Plan Element Quota Achieved (PE_ACHIEVED)
• Plan Element Credit (PE_CREDIT)
• Plan Element Interval (PE_INTERVAL)
Integrating with Projected Compensation

These are the setups required to use Projected Compensation with Oracle Quoting or
with a third party quoting application. See the separate sections for any steps that are
specific to them.
1. Define input and output calculation expressions to be used by the Projected
Compensation API. See Define Calculation Expressions in the Oracle Incentive
Compensation User Guide.
2. Reference the expressions in a formula as forecast input expressions and forecast

output expressions. The formula must be of the Commission type. The expressions
can reference calculation values from the following tables:
• CN_QUOTAS
• CN_SRP_PERIOD_QUOTAS
• CN_PERIOD_QUOTAS
• CN_SRP_QUOTA_ASSIGNS

3. Configure the Plan Element Classification Rule set to include the Projection
Identifiers that are sent to the Projected Compensation API. These identifiers, which
are set up in Oracle Quoting, identify the appropriate plan element to be used to
determine the projected compensation for a given transaction. You must use the
Rules Attributes hyperlink for the corresponding rule in the Rules Hierarchy to
configure the projection identifiers. See Build a Rules Hierarchy in the Oracle
Incentive Compensation User Guide for the steps.
Integrating with a Third Party Quoting Application

Use the same three integration steps as shown previously. Then, write SQL code to:
1. Populate the API table with data
2. Call the Projected Compensation API with the required parameters.
Note: Both of these steps should be performed in the same SQL session.
Oracle Territory Manager

To support the credit allocation process, Oracle Incentive Compensation provides the
ability to integrate with Oracle Territory Manager. Sales Credit allocation in Oracle
Territory Manager is used to define and assign the Who (for example, a resource in a
role) on a transaction. Sales Credit Allocation in Oracle Incentive Compensation is used
to define and assign the How Much credit (for example, percentage credit splits) on a
transaction for a given resource in a role. If you don't use Sales Credit Allocation to
change the allocation percent the credit receivers get, then sales credit is split evenly
(transaction amount divided by number of credit receivers). See Chapter 8, Credit
Allocation Setups, for more information.
After territory rules are defined in Oracle Territory Manager, the Territory Assignment
Engine (TAE) applies these user-defined rules to provide a transactions with credit
receivers and their roles with evenly split amounts. Next, the allocation rules set up in
Oracle Incentive Compensation are applied to the transactions created by the Oracle
Territory Manager through the collection process to create the allocation splits.
The assignment of resources, using TAE, and the determination of credit allocation,
using the Sales Credit Allocation Engine, primarily occurs after the transaction is
collected into the Oracle Incentive Compensation transaction API table
CN_COMM_LINES_API during the Post Collection phase. Post Collection is a trigger
within the Collection process that provides the means for applying additional logic to
collected transactions.
The overall setup steps for using Oracle Territory Manager are:
1. Create resources
2. Create roles

3. Assign roles and groups to resources
4. Create customers
5. Enable Territory Manager access types if needed and not enabled
6. Create a territory and assign resources and roles
7. Generate a territory package using concurrent manager
See the Oracle Territory Manager User Guide for the procedures for steps 5 through 7.
Integrate with the Territory Assignment Engine
There are several ways of integrating with Oracle Territory Manager:
• Territory Manager is called as part of the post collection process in Oracle Incentive
Compensation.
• Territory Manager is called prior to collecting the transaction (for example, from
within your order entry application) so that all transactions collected in Oracle
Incentive Compensation have the correct credit receivers. This is custom code but
can follow much of the code in CN_POST_COLLECTION_TAE_PUB provided
below.
• In a related flow, Oracle Quoting integrates out of the box with Territory Manager
to get the Who, and with Credit Allocation to get the How Much. After accurate
sales credit is determined for a transaction, Oracle Incentive Compensation is called
to derive compensation projections.
To illustrate the first option above, Oracle Incentive Compensation integrates with
Territory Manager to validate credit allocations on a collected transaction as part of the
post collection phase. The integration flow is:
1. Collect Oracle Incentive Compensation transactions with credit allocations that may
or may not be validated. For example, transactions from a particular channel may
not require territory validation. See the following section for specifics on modifying
the code template.
2. Identify Oracle Incentive Compensation transactions that require credit allocation

validation. Oracle Incentive Compensation assumes that a single credit receiver
order line or invoice line is represented as a single Oracle Incentive Compensation
transaction record in CN_COMM_LINES_API.
3. Run collection.
4. If necessary (for example, if credit receivers do not all receive an even split) then
run the Sales Credit Allocation concurrent program to allocate percentage credit for
all Unprocessed transactions in CN_COMM_LINES_API for a given date range.

Integrate with the Territory Assignment Engine
These are the basic steps for integrating with the Territory Assignment Engine.
Steps:
1. Create a territory and rules to determine credit receivers.
2. Run the Generate Territory Package concurrent program for Oracle Field Sales and
Telesales usage and no value selected for transaction type.
3. Add the call to CN_POST_COLLECTION_TAE_PUB.get.assignments as a post

collection action for transaction source order booking/Receivable posting.
1. Log in to Oracle Incentive Compensation with the Incentive Compensation
Administrator responsibility.
2. In the Configuration Workbench, go to Collection > Define Collection Sources

and Mapping > Order Management trigger.
3. Select Order Booking and click Details.
4. Click the Triggers subtab and select Post-Collection in the Event drop-down.
5. Enter the following code:

CN_POST_COLLECTION_TAE_PUB.Get_Assignments
(
p_api_version => 1.0, -- IN parameter
x_start_period_id => x_start_period_id, -- IN parameter
x_end_period_id => x_end_period_id, -- IN parameter
x_conc_program_id => x_col_audit_id, -- IN parameter
x_return_status => x_return_status, -- OUT parameter
x_msg_count => x_msg_count, -- OUT parameter
x_msg_data => x_msg_data, -- OUT parameter
x_org_id => x_org_id -- OUT parameter
);
6. Click Update.
4. Navigate to the Collections page in Oracle Incentive Compensation and generate

the Collection package for the transaction source that calls the Territory Assignment
Engine. You should be able to run the Collection process, which integrates with
TAE during the post collection process.
Restrictions
You must run the concurrent program Synchronize Territory Assignment Rules (STAR)
before calling the Territory API for assignments. Run STAR with the following

parameter values:
• Usage: Sales
• Run Mode: Date Effective Refresh
• Start Date: A valid date , the date from which you want the territories to be
considered for assignment
• End Date: A valid date, the date to which you want the territories to be considered
for assignment
It is important to specify value for all the parameters while running STAR in @ date
effective mode.
The attributes in the insert statement will vary depending on the business requirement.
For example, if you are not using provinces, you can exclude squal_char05 from the
insert statement.
The attributes in the select statement will vary depending on the mappings that you
have defined in Oracle Incentive Compensation. For example, if you have configured
ATTRIBUTE22 to store the State name in CN_COMM_LINES_API, then you want to
map ATTRIBUTE22 in the select statement to the corresponding State column,
SQUAL_CHAR04, insert statement to JTF_TAE_1001_SC_TRANS.
The Trans_object_id is mandatory and must be a unique identifier. This is necessary so
you can pass in comm_lines_api_id.
You can use a Where clause, for example, on load_status, if you do not want to insert
every record from comm_lines_api.
Modify the Code in the API Template

Oracle Incentive Compensation does not require any modification of the Code in the
API template for regular integration with Territory Manager. However, if you need to
perform customization, the steps in this section are provided for that purpose.
To add or modify the code in the API Template, use the code template
CN_POST_COLLECTION_TAE_PUB.Get_Assignments to integrate with the Territory
Assignment Engine process.
Populate data from Oracle Incentive Compensation transaction interface table
(cn_comm_lines_api) into the TAE input interface table (jtf_tae_1001_sc_trans).
Populate SOURCE_ID with -1001, TRANS_OBJECT_TYPE_ID with -1002,
TRANS_OBJECT_ID with COMM_LINES_API_ID, and WORKER_ID with 1. For
details of the Territory qualifier attribute mapping in jtf_tae_1001_sc_trans, please refer
to the table following.
In this code template, first write the statement(s) or make your custom call(s) to insert
transaction data into the TAE input interface table. After that, perform the following

two procedure calls, which are already in the code template:
• JTF_TAE_ASSIGN_PUB.Get_Winners_Parallel: This is the TAE call to trigger the
territory assignment engine. It corresponds to step 3 above and should be called
after you populate the data in the TAE input interface table. The results of the
territory assignments are stored in the TAE output table.
• CN_PROCESS_TAE_TRX_PUB.Process_Trx_Records: This call reads the territory

resource from the TAE output table and populates the allocated resource
information back to the Oracle Incentive Compensation transaction interface table.
The original transaction in the Oracle Incentive Compensation transaction interface
table is obsoleted and corresponding new CN_COMM_LINES_API transactions are
created for each newly allocated resource.
Column Mapping of Account Qualifiers to JTF_TAE_1001_SC_TRANS

In Oracle Incentive Compensation, Sales Credit Allocation uses the Account transaction
object. The following section shows the data mapping between the Account transaction
object qualifier attributes and the corresponding value columns in the
JTF_TAE_1001_SC_TRANS table.
The account qualifiers are categorized into four types.
• Type 1: No Oracle dependencies; can be used for any mapping. Type 1 qualifiers
can be repurposed because there are no dependencies other than aligning your API
call to the territory setups.
• Type 2: Oracle Trading Community Architecture (TCA) dependencies. This means

that you must store your customer data in TCA.
• Type 3: Oracle Accounts Receivable (AR) dependencies, specifically for seeded

values in the AR lookup tables. This means that you must seed these lists of values
to use them.
• Type 4: Oracle Field Sales dependencies, specifically for seeded interest codes in the
AS_INTERESTS table. You must seed these lists of values to use them.
Use the following questions to determine which qualifiers you should use for column
mapping for territories.
1. Is this a stand alone implementation of Oracle Incentive Compensation?
1. If the answer is No, is your customer data stored in TCA?
• If the answer is Yes, and you want to create territories that use a qualifier of
type 2, you must place your customer data into TCA.
• If the answer is Yes, you can use one of the qualifiers of type 1 for any
purpose without dependencies.

2. If Yes, you can use qualifiers of type 1 and type 2.
3. If No, you can use qualifiers of type 1.
2. Are you creating territories that use a qualifier of type 3 or type 4?

1. If the answer is Yes, you must seed values appropriately.
2. If the answer is No, then ignore this question.
In the table below, column 1 indicates the JTF_TAE_1001_SC_TRANS column name.

Column 2 contains the name of the account qualifier. Column 3 displays the Type of
dependencies, as described earlier. Column 4 contains comments regarding the territory
qualifier mapping.
Account Qualifier Mapping
JTF_TAE_1001_SC_ Account Qualifier Type Comments

TRANS Column
SOURCE_ID - N/A Must be -1001
TRANS_OBJECT_ - N/A Must be -1002

TYPE_ID
TRANS_OBJECT_ID - 1 Map to unique OIC

transaction identifier
TRANS_DETAIL_ - 2 Only if your

OBJECT_ID customer record is
stored in Oracle's
Trading Community
Architecture (TCA),
this is a unique
identifier to the party
site ID on a
transaction.
Otherwise, set it to
NULL

TRANS Column
SQUAL_NUM02 Account Code 2 Only if your

customer data is
stored in Oracle's
Trading Community
Architecture (TCA),
maps to TCA's
PARTY_SITE_ID
SQUAL_NUM04 Account Hierarchy 2 Maps only to parties

rolling up to a
specific PARTY_ID
within TCA
SQUAL_CHAR08 Area Code 1 Area Code
SQUAL_CHAR09 Category Code 2 Maps only to the

TCA
CATEGORY_CODE
SQUAL_CHAR02 City 3 Maps only to Cities

set up in Oracle
Receivables (AR)
(Need to seed the AR

lookup values)
SQUAL_CURC01 Company Annual 1 Currency of

Revenue (Currency Company Annual
Code) Revenue, for
example, Euros
(Both
SQUAL_CURC01
and SQUAL_NUM06
need to be populated)

TRANS Column
SQUAL_NUM06 Company Annual 1 Company Annual

Revenue Revenue, for
example, 100,000,000
(Both
SQUAL_CURC01
and SQUAL_NUM06
need to be populated
to work together)
SQUAL_CHAR07 Country 3 Maps only to

Countries set up in
Oracle Receivables
(AR)

lookup values)
SQUAL_CHAR03 County 3 Maps only to

Counties set up in
Oracle Receivables
(AR)

lookup values)
SQUAL_NUM01 Customer Name 2 Maps only to Party

IDs set up in TCA,
identifying a unique
customer
SQUAL_FC01 Customer Name 1 First character of

Range Customer Name
Range
(First Character: for
LIKE processing) (Both SQUAL_FC01
and
SQUAL_CHAR01
to work together)

TRANS Column
SQUAL_CHAR01 Customer Name 1 Customer Name

Range Range
(Both SQUAL_FC01
and
SQUAL_CHAR01
to work together)
SQUAL_NUM10 DUNS Number 2 Maps only to DUNS

Number of parties set
up in TCA
SQUAL_NUM05 Number of 1 Number of

Employees Employees
SQUAL_CHAR06 Postal Code 1 Postal Code
SQUAL_CHAR05 Province 3 Maps only to

Province set up in
Oracle Receivables
(AR)

lookup values)
SQUAL_NUM_01 Registry ID 2 This is the

REGISTRY_ID in
TCA
SQUAL_NUM03 Sales Partner Of 2 This is the PARTY_ID

of the Partner in TCA
SQUAL_CHAR10 SIC Code 2 Maps only to SIC

Codes set up in TCA
SQUAL_CHAR04 State 3 Maps only to States

set up in Oracle
Receivables (AR)

lookup values)

TRANS Column
WORKER_ID N/A N/A Must be set to 1
Oracle Sales
Oracle Sales uses four reports from Oracle Incentive Compensation:
• Commission Statement
• Year to Date Summary
• Earnings Statement
• Attainment Summary
Oracle Sales users can access these reports on the Sales Dashboard. The Sales
Administrator must set up functions for each report:
• CN_COMM_STMT_REPORT_REP
• CN_YTD_SUMMARY_REPORT
• CN_EARN_STMT_REPORT
• CN_ATN_SUMM_REP
You must include the menu CN_ASN_INTEGRATION in the corresponding menu for
the pages to render correctly.

3
General Ledger Setups
General Setup Tasks

There are some tasks that you must set up in General Ledger for all implementations.
Oracle Incentive Compensation uses periods and calendars from General Ledger to
calculate commission. Go to the General Ledger User's Guide, Setup chapter, for the
correct procedures for all of the following General Ledger setups except for Define
Currency. For that procedure, see the Multi-Currency chapter.
After you have completed these processes, the rest of the implementation procedures
are done at the Operating Unit level. See Chapter 4 for those tasks. In Chapter 4 you
select the set of books that you have defined in this chapter.
Define Period Types

Oracle Incentive Compensation requires the period types to be defined in General
Ledger so that compensation can be calculated. Examples of period types are:
• Period (month)
• Quarter
• Year
You can also define custom period types to suit your business requirements.
A period type determines how you divide your calendar or fiscal year. The Calendar
Type page enables you to create period types for either a calendar or a fiscal year. On
the page you can also indicate the number of periods per year and enter a description.
After you have defined the period type, you must create an accounting calendar. If the
period type you need is already defined, proceed to Define Accounting Calendar.
General Ledger Setups 3-1

Define Accounting Calendar
The accounting calendar contains the exact date ranges for all the periods in a specific
calendar or fiscal year.
You can define different calendars for different business activities. Examples of these
calendars include Fiscal, Standard 12-month, or variations such as a Fiscal 13-month
calendar with 12 months and an adjustment period.
Notes
• For prefixes, for a month, you can use the abbreviation, such as Jan for January. For
a year, it can be FY-02 or something similar.
• Number indicates the sequence of the period. For monthly periods, for example,
enter 4 for April, 8 for August, and so on.
• The Name field is required, but it is automatically populated by the application.
• By default, the application builds the contents of the Subject field by combining the
data in the Prefix column with the year suffix and hyphenating them. You can
customize the field by entering a new name.
Define Periods
After you have defined your calendar, you need to add periods to it in General Ledger.
If no periods are defined in General Ledger, Oracle Incentive Compensation cannot
collect transactions or create payment batches.
Define Currency
Any currency that Oracle Incentive Compensation needs to calculate compensation
must be defined in General Ledger. For example, if your company trades in North
America, you want to define US dollars, Canadian dollars, and Mexican pesos. You can
also define multiple forms of the same currency, such as US dollar (next day) and US
dollar (same day).
Define the Set of Books

The set of books provides a means to collect and quantify financial data. Oracle
Incentive Compensation requires that a set of books be set up in General Ledger. The
set of books includes a chart of accounts, calendar, and functional currency.
A chart of accounts is the account structure that you define to fit the specific needs of
your organization. An accounting calendar defines the accounting year and the periods
it contains. You select the functional currency for your set of books as well as other

currencies that you can use for transacting business and reporting purposes.
One set of books can be used for your entire company or different set of books can be
set up for different divisions or locations.
General Ledger Setups 3-3

4
Application Parameter Setups

• Application Parameters
• Set up General Parameters
• Set up General Ledger Parameters
• Define Interval Settings
• Define Credit Types and Conversion Factors
Application Parameters
You must set application parameters in order for the application to perform key
processes. Here you identify the information you set up in General Ledger and set up
ways for Oracle Incentive Compensation to measure achievement and perform
currency conversion.
Navigation
Setup Tasks > Application Parameters
Set up General Parameters

At the beginning of implementation, you need to define the Instance Name and
Currency Conversion Type, and indicate whether compensation plans can be
customized.
• Define Instance Name: This cannot be changed after it is set.
• Currency Conversion Type: This setup is shared with General Ledger.
• Customizing Compensation Plans: Select Yes if you plan to personalize rates at the
resource level. If you don't plan to do so, then set this to No for more efficient
calculation processing.
Application Parameter Setups 4-1

For reports, at this early stage of the implementation process you can indicate the
reporting hierarchy and also whether draws should be displayed in the Year-To-Date
summary report.
Defining the reporting hierarchy is done as a security measure. It sets which resources'
reports a manager can access using the Incentive Compensation User (Manager Self
Service) responsibility.
There are three reporting hierarchies from which you can choose in this release:
• Sales Compensation
• Sales and Telesales
• Compensation Reporting Hierarchy
As an example, REP1 and MGR1 belong to compensation group GRP1, with usage of
Sales Compensation. If the system parameter is set for Sales Compensation. then the
manager can access reports for both REP1 and MGR1.
As a second example, the setups are as follows:
Resource Comp. Group Usage
REP2 CHILD-GRP1 Sales and Telesales
MGR2 GRP2 Sales Compensation
(parent group of CHILD-GRP1) Sales and Telesales
If the system parameter is set to Sales Compensation, then when you access any of the
manager reports and click on the Resource list of values, only MGR2 is listed. REP2
does not appear, because REP2 is not in the Sales Compensation reporting hierarchy.
However, if the reporting hierarchy is set to Sales and Telesales, when you access the
manager reports and click on the Resource LOV, both MGR2 and REP2 are displayed.
If your business doesn't use draws, you can select No in the Display Draw in the
Year-To-Date Summary report drop-down list to remove that field from the report.
Set up General Ledger Parameters

You must select a set of books to use for your instance of Oracle Incentive
Compensation. This set of books is previously created in Oracle General Ledger. After
you have selected the set of books it cannot be changed, and becomes a read-only field.
The application processes incentive compensation payments according to periods
defined in a calendar associated with the set of books. See Chapter 3 in this document
and also the Oracle General Ledger User's Guide, Setup chapter).

The following information is displayed as view-only on this page:
• Operating Unit
• Functional Currency associated with this set of books
• Accounting Calendar associated with this set of books
• Period type associated with this set of books
Define Interval Settings

Intervals are associated to a plan element to accumulate achievements for a specific
period of time. They group predefined periods into larger units of time. Achievements
accumulated during the interval are used to determine the rate at which compensation
is calculated. This depends on how your organization wants to pay compensation.
Commonly used intervals include period, quarter, and year. You must define interval
numbers for these intervals before they can be selected during creation of plan
elements.
On the Interval Settings page you can view seeded and previously created intervals and
create new intervals. Select the interval to assign interval numbers below.
Navigation
Setup Tasks > Define Interval Settings
Notes
• Years listed in the Year list of values must be previously defined in General Ledger.
• Interval numbers are user definable. When an interval is first created, all of the
interval number fields contain a single numeral 1. You must then manually enter
the interval numbers that you need for each year. After you have entered the
numbers and clicked Apply, they will remain stored, even if you select other years
from the drop-down list.
• Interval numbers must be unique for each interval. For example, for quarterly
intervals, JAN-07, FEB-07, MAR-07 are all numbered 2007001, APR-07, MAY-07,
JUN-07 are all numbered 2007002, and so on. For Monthly intervals, JAN-07 is
numbered 2007001, FEB-07 is numbered 2007002, MAR-07 is numbered 2007003,
and so on.
Define Credit Types and Conversion Factors

Credit types are associated with plan elements and are also used in reporting. Credit
types include functional currency, points, air miles, or any custom form of credit that
you want. These definitions are optional, and credits must be converted to functional
Application Parameter Setups 4-3

currency to be paid.
Oracle Incentive Compensation uses the functional currency to perform all calculations.
This is the currency used by General Ledger to record transactions and maintain
accounting data for the set of books. It cannot be changed within Oracle Incentive
Compensation.
You can view, change, remove, or add a credit type.
Use credit conversion 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.
Navigation
Setup Tasks > Application Parameters > Define Credit Types and Credit Conversion
Factors
Notes
• Precision defines the number of decimal places in which the credit type is
displayed. Extended precision is the number of places in which calculation is
performed.
• Only one conversion rate can be in effect for a particular date range. Date ranges
cannot overlap.

5
Collection Setups

• Set up Collection Parameters
• Configure Tables and Columns for Collection
• Define External Table Mapping for Collection
• Define Collection Sources and Mapping
• Add a New Transaction Source to the TRX TYPES Lookup
• Source Table
• Parameters
• Notification Queries
• Column Mapping
• Collection Query
• Triggers
• Filters
• Generate Collection Packages
Set up Collection Parameters

You must define from where Oracle Incentive Compensation collects the transactions
on which commission is paid. The first step is setting up collection parameters. Then,
you can proceed to configuring tables and columns, defining any external tables you
want to use, defining collection sources and mapping, and finally, generating collection
packages.
Navigation
Setup Tasks > Collection > Setup Collection Parameters
When you set up collection parameters, a number of factors affect how transactions are
Collection Setups 5-1

collected.
The Collection Batch Size affects the amount of time the application requires to process
the total transactions. The ideal collection batch size is related to your transaction
volume and the capacity of your system CPU. Start by using the default setting and
adjust it if needed.
The Number of Days for Clawback sets the number of days allowed after the invoice
payment due date before sales credit that has been paid out to resources is taken back.
This number depends on company business practices.
The Reload Errored Transactions parameter determines whether or not the system
resets the load status of errored transactions to UNLOADED so that they can be picked
up again during the next transaction loading process. The default setting is No.
When Apply Invoice Splits and Move to Credit Memos and Payments is set to Yes, any
splits or moves done to Invoices are automatically updated to the credit memos and
payments, unless the transactions are delinked. This is a convenience that can save time,
but if you don't need to split credit memos, you can set it to No. The default setting is
No.
If Collect Credit Memos from Oracle Receivables is set to No, the application collects
only invoices and regular credit memos. If set to Yes, then the application also collects
account credit memos when running Oracle Receivable Collection. Set this to match
your business practice. The default setting is No.
The Negate Original Transactions during Revenue Adjustments Collection parameter
gives you a choice of how transactions are collected for revenue adjustments. If set to
the default setting, Yes, Revenue Adjustments Collection first negates the
corresponding transactions that have been collected before, and then re-collects from
Oracle Receivables with the new revenue adjustments. If your business practices
indicate it, you can set the parameter to No, and only the new revenue adjustments in
Oracle Receivables will be collected.
Configure Tables and Columns for Collection

Tables from Accounts Receivable, Order Management, or an external source that are
used in collecting and calculating transactions in Oracle Incentive Compensation must
be defined before they can be used in collection.
Oracle Incentive Compensation collects transaction data from the comm.lines.api table
for processing commissions for resources. Set up the columns that contain the data you
need to collect. The application comes seeded with the setup you need for standard
collection. For custom collection use any of the 100 configurable attribute columns.
After you have defined tables for custom collection, use the Columns area below it to
define specific columns and relate them to columns in other tables. Be sure that you
have selected Collection in the Usage column and selected Attributes in the View
Column list of values in the Columns section below.
Navigation

Setup Tasks > Collection > Configure Tables and Columns
Notes
• Specify the CN schema to narrow your search to Oracle Incentive Compensation
tables.
• A table user name is an optional name you can specify that is easier to remember
and relevant to its use. Aliases are set up when the table is built, and are used in the
same way.
• For the Attributes 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 is
currently not used. You can see the name on the Collection related pages.
• The Data Type field indicates if the column contains alphanumeric material
(VARCHAR2), numerical data (NUMBER), or a date (DATE).
• The data length is already defined in the database.
• Check the Usage box to identify whether this column is available to build
expressions for formulas.
• The Foreign Key is not used in Collection.
Define External Table Mapping for Collection

If the information you need is in tables that are not in Oracle Incentive Compensation,
you can join those tables to destination tables in Oracle Incentive Compensation. For
example, you may want to use a product category name from an external table when
you are building your classification rules.
The tables must already exist, and must be in the same instance as Oracle Incentive
Compensation.
Navigation
Setup Tasks > Collection > Define External Table Mapping
Notes
• When you search for a table you must supply a valid search criteria value in at least
one field.
• The table name alias is system generated and the Columns link appears in the
External Columns column. It is used by the system to generate SQL code.
• Select a table to open the Columns area, where you can map columns.

Define Collection Sources and Mapping
You can collect transactions from a variety of transaction sources. Oracle Incentive
Compensation is delivered with two predefined transaction sources that allow the
collection of data from Oracle Receivables and Oracle Order Management. Collection
from these two seeded transaction sources is known as Standard Collection. For
standard collection sources, you do not need to set parameters, notification queries, or
collection queries.
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.
If you use Open collections, you must set all details for the collection process. These
processes are accessed through the Details icon:
• Use source tables to specify all the tables which are used during the creation of
compensation transactions.
• Use parameters to identify the transactions to be collected by a Notification Query

(see below).
• Use a notification query to identify and mark transactions for the collection process.
• Use column mapping to specify what data is used to fill each of the destination
columns when a compensation record is collected from the transaction source.
• Use a collection query after the notification query, to collect all the data attributes
mapped in the column mapping tab.
• Triggers: Triggers are PL/SQL statements (functions and procedures) that you can
insert at defined points in the collection procedure
• Filters: Filters allow you to define criteria to remove unwanted transactions.
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
Column Mapping, page 5-8.
These are the setups that need to be done to collect data from this system for Open
Collections.
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.

3. Define a new transaction source.
4. Add the new transaction source to the TRX TYPES lookup.
5. Identify the source tables from which the transactions are to be built.
6. Define the Notification and Collection Queries.
7. Define Runtime Parameters.
8. Define the mapping from the source system into an API table in Oracle Incentive
Compensation (CN_COMM_LINES_API). Mapping is the way to specify how data
from the source tables are used to populate the destination fields in the
compensation transaction.
9. Define any optional collection actions, including triggers or filters. Triggers can be
set up at three stages of collection:
• Pre-notification
• Post-notification
• Post-collection
10. Test generate a collection package (PL/SQL package) and correct errors, if any.
11. Review and when there are no errors, 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.
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.
When using open collections, you must tell Oracle Incentive Compensation from which
transaction source you will obtain the data for processing commissions. In the
Transaction Source area, perform the following procedure to set up a custom
transaction source.
Tables must be set up already in the transaction source.
Navigation
Setup Tasks > Collection > Define Collection Sources and Mapping

Notes
• For each Transaction Source there are three pieces of information:
• Name: User-defined and changeable, and may include legacy sources.
• Type: The short name of the Transaction Source. It is user-defined, must be

unique, cannot be empty, and cannot be changed after it is created. When
creating a new transaction source, the Type cannot be the same type as any
existing seeded transaction source, such as Order Booking (OC), or Receivables
(AR). It also cannot be the same as the type of existing receivables events, such
as INV (Invoice), PMT (Payment), CBK (Clawback), or WO (Writeoff).
• Status: Complete/Incomplete. This indicates whether the Collection package has

been generated for the Transaction Source since the latest setup changes were
made.
• The Line Table is the primary source table of the Transaction Source.
• The Key Column is the unique primary key of the line table.
Click Save after filling in all of the fields.
Add a New Transaction Source to the TRX TYPES Lookup

For any open or custom transaction source, you must create a new line in the TRX
TYPES lookup in Oracle Incentive Compensation. If this is not done, all transactions
collected from the custom transaction source will not appear on the Transactions page
until after they have been loaded using the Load Transactions process.
Navigation
Setup Tasks > Collection > Define Collection Sources and Mapping
Prerequisites
❒ The new transaction source must already be defined.
Steps:
1. Find the value in the Transaction Source Type column for the custom transaction
source.
2. In the Compensation Workbench, log in as the Incentive Compensation

Administrator responsibility.
3. Click the Lookups link.

4. Query the lookup type TRX TYPES.
5. Add a new row for the custom transaction source and enter the Transaction Source
Type value from step 1 into the Code column in the lookup set.
6. Save.
Source Table
After the Transaction source has been defined, you must specify all the tables which are
used during the creation of compensation transactions--the Direct Mapping tables. 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 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.
Tables must be registered before they can be used.
Navigation
Setup Tasks > Collection > Define Collection Sources and Mapping > Details icon
Notes
• Extra 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.
Parameters
Parameters allow you to narrow your focus of a notification query. For example, you
can specify parameters for start date and end date if you are using a custom transaction
source. The parameters are registered here during the collection setup process but the
specific values are entered 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 while leaving the collection setup alone.
Navigation
Setup Tasks > Collection > Define Collection Sources and Mapping > Details icon >
Parameters

Notification Queries
If you are collecting data from a source other than the two standard collection sources,
Receivables Posting and Order Booking, you need to tell Oracle Incentive
Compensation from where to collect the transaction data and what data to collect. You
can generate a list of transactions that are eligible for compensation using the
Notification Query and Parameters sections. For standard integration with Oracle
Receivables and Oracle Order Management, you cannot edit the query conditions.
Navigation
Notification Query
Notes
• 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 during source table
definition. The AND area links the tables together and creates the exact conditions
for collecting the transactions needed for calculation.
Column 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,
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.
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.
Tables must exist in the transaction Source and the destination. For relationship indirect
mapping, a Join relationship must be set up for any tables you plan to use.
Navigation
Mapping
Notes
• If you want to perform indirect mapping, after you have set up the source
expression and destination, click the Indirect Mapping icon to open the Indirect
Mapping page.
• For a relationship mapping, enter a join relationship. You must have set up the join

relationship in advance.
• For a freeform mapping, enter the From/Where clause.
• 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.
Collection Query
The Collection Query area lists the exact tables and rows from those tables that you
need to perform a collection. The 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.
Navigation
Collection Query
Triggers
You can change the Collection processing for the transaction source by adding triggers.
If you are using the standard collection sources, you can also use filters (see the
following section).
Triggers are single or multiple PL/SQL statements (functions and procedures) that you
can insert into the cn_comm_lines_api_all table at three defined points in the Collect
procedure:
• 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
Use the Pre-Notification and Post-Notification insertion points if you want to make
changes to the source tables. Use a Post-Collection trigger to make changes to data that
is already loaded into the API table.
Navigation
Triggers
Notes

• The code can run up to approximately 2,000 characters.
Filters
Transaction filters are especially relevant to Receivables and Order Management,
because you cannot change the collection query for those standard transaction sources.
Filters allow you to define criteria to remove unwanted transactions. For example, if
you want to filter out any transactions less than $100, you enter this text on a line in the
Filters section:
• api.transaction_amount < 100
There are two methods of filtering:

• Mark as Filtered: Filtered transaction is collected in the CN_COMM_LINES_API, is
marked as Filtered, but is not picked up for calculation.
• Physically Delete: Transaction is deleted from CN_COMM_LINES_API.
Deleting the transactions helps keep the table at a more efficient size, so it is the
recommended option.
Navigation
Filters
Generate Collection Packages

After the setup is complete, you must generate a collections package before it can be
used. You can test generate a package before generating the final package.
• Event:The Event column is only relevant to the Receivables Posting transaction
source.
• Collect Flag: The Collect flag indicates whether or not to generate the package for
the corresponding transaction source or Receivables event.
• Test Status: The Test Status field shows if there is an error in the test package.
• Package Status: The Package Status field tells you whether or not the Collection
package has been generated for the Transaction Source since the latest setup
changes were made.
To distinguish a test package from the actual package, the package name of the test
version always ends with "_t"
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 selecting the transaction

source and clicking Test Generate.
The Test Generation--Details page 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 trigger.
The Package Text section of the Test Generation--Details page also lets you review the
entire generated package to be sure it works correctly. For example, you can see exactly
where in the Collect procedure your triggers will be executed. If everything looks fine,
return to the Generate Collection Package page and click Generate.
As a convenience, Oracle Incentive Compensation groups five separate transaction
sources into the Receivables Posting transaction source. 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.
Before you generate a collection package, the collections setup must be complete. A
complete collections setup means that the following are defined and complete:
• Transaction sources
• Queries
• Collection mapping
• Direct and indirect mappings
• Triggers and filters
Navigation
Setup Tasks > Collection > Generate Collection Packages

6
Calculation Setups

• Calculation Setup
• Set Up Calculation Parameters
• Configure Tables and Columns for Calculation
• Define External Table Mappings for Calculation
Calculation Setup
Oracle Incentive Compensation performs calculation in two ways: Complete and
Incremental. Complete Calculation calculates all transactions in the interval, and it is
the default setting. However, calculating the entire set of transactions can take a long
time. Using Incremental Calculation, the calculation engine processes only transactions
that have been newly loaded or affected by setup changes since the last calculation was
run.
Calculation proceeds in phases. In the Classification phase, the application checks the
applicable product classification rules against the affected transaction attribute values.
In the Rollup phase, Oracle Incentive Compensation determines all resources who
should receive credit for a transaction based on the rollup date and the resource
hierarchy effective on that date. In the Population phase, Oracle Incentive
Compensation identifies the appropriate plan elements for every transaction by
matching the products of the plan elements with the products of the transaction. Lastly,
in the Calculation Phase, Oracle Incentive Compensation performs calculation on all
transactions that have passed the Population phase for resources specified for the
period. See the Oracle Incentive Compensation User Guide for more information on the
Calculation Process.
For calculation setup involves three processes:
• Set up calculation parameters: Change default settings as needed.
Calculation Setups 6-1

• Configure tables and columns: Optional--make changes only as needed.)
• Define external table mappings: Optional--use only external data is required.
See the following sections for information on these processes.
Set Up Calculation Parameters

Calculation parameters are used to configure the calculation process to your
requirements. They are important for making the application run as efficiently as
possible for the volume of transactions you must handle and the processing capability
of your system. Also, choices such as whether to rollup transactions or not can have a
significant impact on processing time.
The view-only Date Last Calculated field indicates the date of the latest transaction for
which calculation has been run. This information is important in case you rerun other
incremental calculation. It can also alert you to what transactions already have been run
so that you know if it is safe to close a period.
The Transaction Batch Size and Resource Batch Size together determine how many
transaction batch runners get submitted for calculation. During the transaction batch
pre-processing phase, Oracle Incentive Compensation determines how many batches
will be run for this calculation process. For example, if you want to calculate 10,000
transactions and the batch size is 1,000, ten batches will be created. These settings affect
calculation performance.
A good starting point for setting the values for resource 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. To help prevent problems with the open period process, It is essential that the
Resource Batch Size is not set to zero. Set it to a positive number, for example 2, or 200.
Rule Batch Size does not affect calculation in any way. This option is used when
creating the Classification Rules Package.
The resources are first assigned to physical batches (identified by
PHYSICAL_BATCH_ID) based on the transaction batch size and resource batch size. A
physical batch contains at most the number of resources specified by the resource batch
size parameter and at most the number of transactions specified by the transaction
batch size parameter. When a physical batch is filled up, Oracle Incentive
Compensation creates another physical batch to continue the assignment process until
all resources and their transactions are assigned to a physical batch.
Calculation assigns each resource to a single physical_batch_id. It does not split the
resource across two batches.
To improve the performance of concurrent calculation, and thereby save time, Oracle
Incentive Compensation reuses existing resource groupings to create batch runners.
Sometimes, over time or due to certain circumstances, the existing groupings create a
skewed distribution of transactions and need to be regrouped. A simple setting of the

Transaction Batch Size parameter controls this. To reuse existing groupings, enter a
transaction batch size ending in a zero (0), for example, 2,500. To make the application
regroup resources and transactions into new batch runners, enter a transaction batch
size ending in a number other than zero, for example, 2,501. After you are satisfied with
the new grouping and want to reuse it, reset the transaction batch size parameter to a
number ending in zero.
Use the Numeric Precision for Rate Tables field to set the precision of the calculation,
which affects the number of places to the right of the decimal point that are displayed in
the rate tables. This setting is not used for calculation purposes.
If the Allow Prior Period Adjustments parameter is set to No, it allows all plan elements
in a period to be calculated incrementally. Before selecting this parameter, be sure that
any transactions that have a processed date earlier than the latest processed date
showing in the System Parameter window have been calculated. If your business
processes require you to calculate for prior periods, set this parameter to Yes.
Select the correct product hierarchy in order to classify transactions. Only one product
hierarchy can be active at a time.
The amounts generated in Projected Compensation are not exact. If you want to
generate a disclaimer along with the amounts, you can indicate it on the Calculation
Parameters page. You can also specify the particulars of that disclaimer.
The Enable Managerial Rollup parameter is used to set up managerial rollups for a
resource who is assigned the same role in multiple groups or multiple roles in the same
group. If a resource is assigned a role in multiple groups, it must be the same role. This
release of Oracle Incentive Compensation does not support rollup along multiple paths
when the managers receiving the credit have different roles in the compensation groups
along the rollup paths. This is because the application picks the role at random.
Set the Enable Managerial Rollup parameter to Yes if you want sales credits to roll up
through the compensation group hierarchies. If the parameter is set to yes, 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 can use preprocessed code to control indirect credit on a transaction-by-transaction
basis.
Aggregate Transactions During Rollup: Select Yes for this parameter if you want to
aggregate matching transactions. For example, If you have a large volume of
transactions that are for the same product and the same resource, it is more efficient to
aggregate them and process them as one transaction.
Aggregate Transactions Based on Custom Criteria During Rollup: Select Yes for this
parameter if you want to use customized summarization code to aggregate transactions
during rollup. This works only if the Aggregate Transactions During Rollup parameter
is set to Yes.

Configure Tables and Columns for Calculation
Tables from Accounts Receivable, Order Management, or an external source that are
used in calculating compensation in Oracle Incentive Compensation must be defined
before they can be used in calculation.
Oracle Incentive Compensation calculates transaction data from the
CN_COMMISSION_HEADERS and CN_COMMISSION_LINES tables for processing
commissions for resources. Set up the columns that contain the data you need to
perform calculation. You can also define external mappings for calculation.
After you have defined tables for calculation, use the Columns area below it to define
specific columns and relate them to columns in other tables. Be sure that you have
selected Calculation in the Usage column and selected Attributes, Classification
Attributes, or Dimension Attributes in the View Column list of values in the Columns
section below.
The column name is set in the application, but you can assign a column user name to it
to match your business process or for ease of use. The external call field currently is not
used.
Navigation
Setup Tasks > Calculation > Configure Tables and Columns
Notes
• Specify the CN schema to narrow your search to Oracle Incentive Compensation
tables.
• A table user name is an optional name you can specify that is easier to remember
and relevant to its use. Aliases are set up when the table is built, and are used in the
same way.
• You can change the name in the User Name field for any view.
• For the Attributes view:

• The Data Type field indicates if the column contains alphanumeric material
(VARCHAR2), numerical data (NUMBER), or a date (DATE).
• The data length is already defined in the database.
• Check the Usage box to identify whether this column is available to build
expressions for formulas.
• For the Classification Attributes view:

• Check the Classification Value box next to a column to indicate that the column

can be used in the classification process and on the Transaction Maintenance
Search page as a search criterion. Check the Display in Results column if you
want this column to be displayed in the default search results table.
• The Value Set Name is used to set a value when this column is defined as a rule
attribute.
• You can select three data types: Alphanumeric, Date, and Numeric.
• For the Dimension Attributes view:

• The dimension name identifies the dimension (of hierarchies) associated with
this column.
• The Dimension Value box indicates whether the User Name column is being
used.
When building your custom logic on top of Oracle Incentive Compensation

functionality, make sure that you are not basing your logic on the Oracle Incentive
Compensation table columns that store the intermediate results of internal Oracle
Incentive Compensation processes. The representation and interpretation of the values
stored in these columns may be changed by the application without notice. For these
columns, do not change any of the stored values, and do not modify the list of allowed
values.
For example, the values in cn_commission_lines_all.input_achieved, output_achieved,
commission_rate store intermediate results of the calculation process and are used by
Oracle only. Any customization or custom logic based on these columns is not allowed
without Oracle's approval.
As another example, the column cn_commission_lines_all.status has a fixed list of valid
values. The addition of extra values to this list is not supported by Oracle.
Define External Table Mappings for Calculation

If the information you need is in tables that are not in Oracle Incentive Compensation,
you can join those tables to destination tables in Oracle Incentive Compensation. For
example, you may need to use salary information from an external table in order to
calculate commissions for resources.
The tables must already exist, and must be in the same instance as Oracle Incentive
Compensation.
Navigation
Setup Tasks > Calculation > Define External Table Mapping
Notes

• When you search for a table you must supply a valid search criteria value in at least
one field.
• The table name alias is system generated and the Columns link appears in the
External Columns column. It is used by the system to generate SQL code.
• Select a table to open the Columns area, where you can map columns.

7
Payment Setups

• Set Up Payment Parameters
• Account Generator
• Define Pay Element Mappings
Set Up Payment Parameters

You may integrate Oracle Incentive Compensation with Oracle Payroll and Oracle
Payables by configuring the Payment Parameters and mapping in this function. An
alternative is to use a third party payment application. Oracle Incentive Compensation
does not provide an API or interface to use a third party application.
Navigation
Payment > Setup Payment Parameters
If you integrate Oracle Incentive Compensation with Oracle Payroll, you must map
plan elements to the pay elements in Oracle Payroll. See this procedure following.
If you integrate with Oracle Payables, you can select Account Generation. Account
Generation populates account codes at the appropriate detail level and then indicates
from where the application pulls expense and liability information. Note: If the account
level population is set to Classification or Product, the system profile Pay by
Transaction must be set to Yes or Y for the account to be populated to the Accounts
Payable interface. See the Profiles chapter for details.
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
four levels are as follows:
• Product: Each product can be assigned a specific liability and expense account code.
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
Payment Setups 7-1

account code. 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 code.
• 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.
Oracle Incentive Compensation pulls expense and liability information from the Plan
Element tables to populate expense and liability account codes for manual transactions
and payments related to payment plans when account generation is set to Classification
or Product and payment is in Pay by Transaction mode.
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 Product level, the application ignores whatever you
enter at the Product level.
If you select the Classification level from the Account Generation drop-down list, you
must create a rule set type of Account Generation to define conditions and their
corresponding accounts. See Account Generator, page 7-2 for the procedure.
Account Generator
To set up account generation, you must log in to the Plan Administrator responsibility.
Navigation
Oracle Payables Integration > Account Generation Rule Sets
Steps:
1. Click Create. Be sure you have selected the correct Operating Unit.
2. Give the rule set an appropriate name and dates that reflect the period of time that
you will be using it.
3. Open the new rule set and click the Update icon.
4. Click the Create Child icon next to the parent rule to begin building the Account
Generation rule set.
5. Enter an appropriate name for the child rule and select Expense and Liability
account code names from the lists of values.

6. Click Apply.
7. Click the Update icon for the new rule.
8. Choose an attribute from the list of values and a value. If you select Equals or Does
Not Equal, you can only select a single value--Value From. If the condition is
Between or Not Between, you must set up a range by selecting both Value From
and Value To.
9. Enter any 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.
10. Click Apply to save the rule.
11. Add rules in the rules hierarchy as needed.
12. Return to the Account Generation page, select the new rule set, and click
Synchronize.
Restrictions
In order for the system to transfer the account code, you must first be able to classify the
transactions. To classify the transaction, see Define Classification Rule Sets in the Oracle
Incentive Compensation User Guide. Create the same rule as you created in the Rule set for
Account Generation. Then, you can calculate and pay for transactions.
Define Pay Element Mappings

Use Oracle Incentive Compensation to collect transactions, calculate compensation, and
create a payment batch. To use Oracle Payroll to pay a resource that has earned
compensation, you must set up an integration with the pay elements in Oracle Payroll.
If you are using Oracle Incentive Compensation as a stand-alone application, then you
need to create your own interface for payments to other systems.
Payment batches can be created and paid one time per period and also multiple times
per period, depending on your business needs. When the first payment batch is paid in
a period, the data is transferred to Payroll successfully. For an off-cycle payment batch,
after you pay the payment batch from Oracle Incentive Compensation and before you
validate the BEE batch, you must change the "Action if Entry Exists" from "Reject Entry"
to "Create New Entry" in the Batch Control and save the record before proceeding with
the validation process. However, to ensure that payment batches are automatically
accepted by Payroll without having to make the manual change each time, you can
change the setting of the profile option OIC: Approve or Reject Duplicate Payment
Transactions. To allow multiple payments to the same pay element in the same period,
Payment Setups 7-3

change the profile setting from Reject (the default setting) to Insert (create new entry) or
Update (change existing entry).
If a pay element in Oracle Payroll has been defined to have input values, then you can
define a mapping in Oracle Incentive Compensation that identifies which data columns
in application tables map to the input value of a pay element. The following tables can
be used to map Oracle Incentive Compensation to pay element input values:
• CN_PAYRUNS
• CN_SALESREPS
• CN_PAYMENT_TRANSACTIONS
This mapping is stored in the CN_PAY_ELEMENT_INPUTS table in Oracle Incentive

Compensation.
You can edit mappings or create new ones on this page.
Navigation
Setup Tasks > Payment > Define Pay Element Mappings
Prerequisites
❒ Plan elements and pay elements must already be created. See Define Plan Elements
in the Oracle Incentive Compensation User Guide for plan element setup; see Oracle
HRMS documentation for pay element setup.
Notes
• Select pay and plan elements and give them a range of applicable dates.
• Click the Inactive Employee box if you want to keep the mapping but not use it
now.
• You must map each plan element to at least one pay element.
• The mapping information is stored in the CN_QUOTA_PAY_ELEMENT_ALL map

table. The three-column table below shows examples of how the mapping is set up
between Oracle Incentive Compensation plan elements and Oracle Payroll pay
elements, with the resource status indicated in the third column:
Plan Element (OIC) Pay Element (Payroll) Resource Status
01 Account Quota Commission Pay ACTIVE
01 Account Quota Commission Pay INACTIVE

Plan Element (OIC) Pay Element (Payroll) Resource Status
Recoverable Payment Plan Commission Pay ACTIVE
Payment Plan Recovery Commission Pay ACTIVE
Q1 OCG Bonus Bonus Pay ACTIVE
Q1 OCG Bonus Bonus Pay INACTIVE
Education Commission Pay ACTIVE
Education Commission Pay INACTIVE
• In the Plan Element field, two seeded values are available to be used when
recoveries must be performed but they are not related to a specific plan
element:
• Payment Recovery: Amounts need to be recovered, but multiple plan
elements are consolidated on the payment worksheet.
• Carry Over Plan Element: The plan element end date has passed but
recoverable amounts remain. This value serves as a placeholder until the
amount is recovered.
• If the Pay by Transaction profile is set to No (N), the commission amounts are
summarized at the plan element level. Therefore, the pay element name is
displayed against the plan element name on the Payment Transactions page if
the mapping exists and the payment batch date falls within the mapping date
range. But, in the case of a payment recovery, the amounts are aggregated at the
resource level and not at the plan element level, so the pay element is listed but
the plan element name is not displayed.
• For a given date range, a pay element can be mapped to more than one plan
element, but a plan element can be mapped to only one pay element. However,
a plan element can be mapped to the same or a different pay element for an
overlapping date range if the box in the Inactive Employee column is checked.
• A plan element and pay element mapping cannot be deleted unless the element
input lines mapping between the table name and column name are deleted first.
After the payment batch has been paid that used a plan element which has been
mapped, it can be end dated as per the end dating rules mentioned above.
Payment Setups 7-5

8
Credit Allocation Setups

• Introduction
• Set up a New Transaction Source
• Configure Transaction Source Mappings
• Set up Workflow Options
• Set Up Workflow Background Process
• View Workflow Background Process Results
Introduction
Credit Allocation systematically applies a set of consistent rules to determine
automatically who receives credit for a sales transaction and how much of the credit
each person receives. This minimizes errors, thereby reducing the time analysts must
spend reconciling them.
To use Credit Allocation, refer to Oracle Incentive Compensation User Guide, Credit
Allocation.
Set up a New Transaction Source

The seeded transaction sources for credit allocation in this release are Oracle Incentive
Compensation and Oracle Quoting. You can also set up a custom user defined source
by adding it to the CN_LOOKUPS table in the Forms application. A link is provided in
the Incentive Compensation Administrator's menu. See the Lookups appendix for
details.
The Transaction Source name must be unique. It cannot be the name of an existing
transaction source or an existing credit rule name.
If you delete a transaction source, you cannot view or access any rule associated with it.
Credit Allocation Setups 8-1

Configure Transaction Source Mappings
In order to use the Credit Allocation engine, you must map the source tables that
contain the transactions to the Comm Lines API. If the transaction source is Oracle
Incentive Compensation, this mapping information is used to generate a dynamic
PL/SQL package. This mapping is also used to set up attributes that are used in the
Credit Allocation Rules by activating the attribute.
To create credit rules and run Credit Allocation, see the Credit Allocation chapter in the
Oracle Incentive Compensation User Guide.
Navigation
Setup Tasks > Credit Allocation > Configure Transaction Source Mappings
Notes
• Enter a value set name if an attribute has been assigned a value set. See value set
documentation for more information.
• The data type of the credit rule attribute must match the data type of the transaction
attribute column value or rules engine processing will fail. For example, if the data
type in the rule attribute is Numeric, the credit rule condition is Between 100,000
and 200,000, and the transaction attribute value is ABC, the rules engine will reject
the transaction, because ABC is not numeric data.
• If the transaction source is Oracle Incentive Compensation you must select a

transaction source in the table.
• After creating a transaction source mapping, activate it to use the attribute in your
credit rules. You can also deactivate a mapping if it is no longer needed.
• If you are using Oracle Incentive Compensation as a transaction source, click

Generate to generate the PL/SQL code.
Set up Workflow Options

During credit allocation processing, the credit rules engine checks whether the total
output revenue allocation percentage is equal to 100%. If the total revenue allocation
percentage is not equal to 100%, then the status of the transaction is updated to REV
NOT 100.
These transactions are processed by Workflow based on a system profile value. You can
set how you want to handle transactions that are not able to be processed normally. See
the example below.
There are three options provided in cases where the total percentage does not total
100%:

• Even Distribution: The remaining revenue percentage is distributed evenly among
the existing sales roles.
• Weighted Average: The remaining revenue percentage is distributed based on the

weighted average, which uses the percentages assigned to each role.
• Custom: Even Distribution and Weighted Average contain built-in logic, but the
Custom setting does not. You can add custom code if none of the seeded choices
suits your business requirements. You can also use the Custom option to set up for
the Workflow process to not process any transactions when the allocation
percentages do not total 100%.
For example, the allocation percentages for a transaction are 60% to Role 1, 20% to Role
2, and 20% to Role 3. However, during transaction processing, only the first two roles
are associated with the credit rule. What is to become of the remaining 20%?
Using Even Distribution, both of the remaining roles receives 10% credit, or half of the
remaining 20% credit. Using the Weighted Average, The first role gets 15% and the
second receives 5% of the sales credit, because 60% represents three times the 20% of the
second role. Each of the resources assigned to the roles that resulted in revenue output
receives additional credit.
The option is set in the system profile OIC: Allow split % less than 100%. If you do not set
the value at the application level, it defaults to the site level. If no selection is made, the
Workflow process fails. See the System Profile Options chapter for steps to set up this
profile.
The following table includes the following columns from left to right:
• Profile Name: Name of the profile.
• Description: Explains what the profile does.
• Level: Level at which this profile option can be set. A = Application, S = Site, R =
Responsibility, U = User.
• Default: Lists the seeded default for the profile, if any.
Profile Name Description Level Default
Total Rev % is Not In Credit Allocation, AS Custom

100 Revenue Split Total
is not 100%.
You can use Workflow configuration to decide what should happen after Rules Engine
processing is complete. If you have a PL/SQL package that copies the transactions from
output interface tables to your own schema, you can configure the workflow process to

perform this task.
For Oracle Incentive Compensation, Credit Allocation runs as a batch using a
concurrent program in the background. This is because of the large volume of
transactions that are normally processed in this application, which requires the use of
tables. For Oracle Quoting, the Credit Allocation engine runs as an online process,
because it needs to process a small amount of information to deliver information to a
resource quickly. In this case, Credit Allocation simply applies a rule to a transaction
and returns the credit allocation percentages.
Set Up Workflow Background Process

In order for Workflow to run for the processes in Credit Allocation, you must set up the
background process for it. This setup schedules when Workflow checks the queue.
For Credit Allocation, it is recommended that you set up the Workflow background
process parameters to run periodically. You should set up start and end dates which
encompass the full span of time for which you want the process to run.
After the setup is complete, you can log in to Self Service Web Applications (SSWA) to
view the Workflow Administrator Activities List.
To set up the Workflow background process and view Workflow activity, perform the
following steps.
Responsibility
System Administrator
Navigation
Oracle Forms: Requests > Find Requests
Steps:
1. On the Find Requests screen, select All My Requests, and Order By Request ID.
2. Click Submit a New Request.
3. Select Single Request and click OK.
4. In the Parameters screen, select an item type of Sales Credit Allocation. Click OK.
5. On the Schedule screen, select Periodically, and enter start and end dates.
The dates should encompass the time span for which you want to run the
background process. A year is a good standard span.
6. Set the process to run periodically and to apply the interval from the start of the
prior run.

7. Click OK.
View Workflow Background Process Results

To view the results of the Workflow background process, log in to Self Service Web
Applications.
Steps:
1. Select Workflow Administrator Web Applications from the Self Service list.
2. Click Find Processes.
3. On the Find Processes screen, you can select which activities to view.
If you select the Any Status button, active and complete Workflow activities will be
displayed. You can select Active or Complete to limit the display.
4. Select All from the Item Type drop-down list.
5. You can further narrow the Find process by entering information in the four fields
that follow:
• Item Key
• User Key
• Process Name
• Process Owner
6. You can limit the displayed activities by selecting Suspended or In Error, or select
Any Status to show all activities that match the parameters previously set.
7. Click Find.
8. In the Item Type field, select Sales Credit Allocation Process.
9. Click Find.
10. To view details about a process, click the link in the Process Name field.
11. Click View Diagram to see the Activities List queue.

9
Profile Options

• Profile Options
• Table of Profile Options
Profile Options
The tables below lists the profile options which need to be set to implement Oracle
Incentive Compensation after the product has been installed. You must set them before
the system is ready to be used to build compensation plans, collect and process
transactions, and pay incentive compensation. The options can be set in any sequence.
A few of the profile options are for applications other than Oracle Incentive
Compensation. For example, three are from Oracle Quoting (ASO) and there is one
from Multi Organization (MO). The Quoting profiles must be set if Quoting integration
is used. The Multi Organization profile is mandatory.
Profile options can be set at the following levels:
• Site: This is the lowest profile level. Site level profile option values affect the way all
applications run at a given site.
• Application: These profile option values affect the way a given application runs.
• Responsibility: These profile option values affect the way applications run for all
users of a given responsibility.
• User: These profile option values affect the way applications run for a specific
application user. The values you enter for options at the User level supersede the
values that your system administrator has entered for you for these options.
In this release of Oracle Incentive Compensation, 13 profile options have been changed
to system parameters. This was done because this release allows multiple operating
units to be controlled by the same responsibility. Profile options are operating unit
Profile Options 9-1

specific, so in order to continue to allow a single location for setting the profile values,
some profiles were added into the application's user interface directly. This maintains
the single location setup functionality of the previous release. The converted profile
options are listed below.
11.5.10 User Profile R12 System Parameter Parameter Location

Option Name
OSC: Collect on Account Collect Account Credit Set up Collection Parameters, page
Credits Memos from Oracle 5-1
Receivables?
OSC: Commission Rate Numeric Precision for Rate Set up Calculation Parameters,
Precision Tables page 6-2
OSC: Default Conversion Currency Conversion Type Set up General Parameters, page 4-
Type 1
OSC: Customized Aggregate Transactions Set up Calculation Parameters,

Summarization Based on Custom Criteria page 6-2
during Rollup?
OSC: Default Custom Flag Customize Compensation

Plan
OSC: Income Planner Display Projected Set up Calculation Parameters,

Disclaimer Compensation Disclaimer? page 6-2
Display Draw Display Draw in Year To Set up General Parameters, page 4-

Date Summary Report? 1
OSC: Apply non-revenue Collect Quantity for Non

split to quantity Revenue Credit Receivers?
OSC: Prior Adjustment Allow prior period Set up Calculation Parameters,

adjustments? page 6-2
OSC: Negate during Negate Original Set up Collection Parameters, page

Revenue Adjustments Transactions during 5-1
Collection Revenue Adjustments
Collection
OSC: Reporting Hierarchy Reporting Hierarchy for Set up General Parameters, page 4-
Manager Access to 1
Resources' Reports

11.5.10 User Profile R12 System Parameter Parameter Location
Option Name
OSC: Reset Error Reload Errored Transactions Set up Collection Parameters, page
Transactions 5-1
OSC: Roll Summarized Aggregate Transactions Set up Calculation Parameters,

Transactions during Rollup phase? page 6-2
Responsibility
System Administrator
Navigation
Oracle Forms: Navigator > System Profiles
Steps
1. In the Navigator, double-click Profile.
2. Double-click System.
3. In the Find System Profile Values window, query the following categories to
narrow your search:
• Site: Select if the profile option applies to all users at your site.
• Application: Oracle Sales Compensation
• Responsibility: Select only if the profile option you are defining is specific to a
responsibility.
• User: Select only if the profile option you are defining is specific to a user.
4. In the Profile field, you can enter OIC% to see most of the Incentive Compensation
profiles. Or, enter another search parameter. You can use the percent sign (%) as a
wildcard.
5. Click Find.
6. View or change the profile setting.
7. Save.
Note: After you change the setting of a profile option, you must bounce the Apache
Profile Options 9-3

server to reset it.
Table of Profile Options

The following table lists the system profiles used by Oracle Incentive Compensation.
The profiles are divided into nine categories:
• Calculation
• Collection
• Credit Allocation
• Debug
• Import
• Payment
• Performance
• Upgrade
• Other
: In the table, the Level column displays at which this profile option can be set. A =
Application, S = Site, R = Responsibility, U = User.
System Profile Options
Calculation Profiles
OIC: Enable Incremental If set to Yes, every event is put into ASRU Yes
Calculation the Notify Log so that it can be
included in the next incremental
calculation. Recommended that
you set it to No while setting up
your system, but change it to Yes
when you are ready to start
collecting transactions.

OIC: Frequency of Batch Sets the amount of idle time ASRU 30 seconds
Runners Status Check between batch runner status
checks performed by the parent
calculation process. The idle time
gives each phase time to complete
the current process without being
queried by the system for a status.
For high volume transactions, use
the default setting.
OIC: Multi Rollup Path Enables rollup of sales credits ASRU Null
through multiple paths of the
compensation group hierarchy.
See Guidelines for restrictions on
using this profile.
OIC: Reset Balances If the profile is set to Yes, then the S No

Each Year salesrep subledger balances
(cn_srp_periods) get reset to zero
at the beginning of each fiscal year
during calculation and payment.
Otherwise the balances carry over
across fiscal years.
Collection Profiles
OIC: Apply Invoice When this profile is set to 'Y', any ASRU No
Splits to Credit Memos splits or moves done to invoices
and Payments are updated to the credit memos
and payments, unless the
transactions are delinked.
Credit Allocation
Profiles
OIC: Allow split % less In Credit Allocation, Revenue Split AS Custom

than 100% Total is not 100%.
OIC: Number of Batch Set the number of parallel workers ASRU 1

Workers for Credit that the OIC Credit Allocation
Allocation Transfer process uses.
Debug Profiles
Profile Options 9-5

OIC: Enable Debug Determines whether debugging ASRU Yes

Mode messages are written to the process
log during execution of programs
(concurrent and online). Setting
Debug Mode to Yes writes these
errors to the
CN_PROCESS_AUDIT_LINES
table.
OIC: Enable Logging If set to Yes, debugging messages ASRU No

are written to a log file. Only
enable this profile option for
debugging purposes if there are
suspected problems with the
application. If enabled, this profile
option generates log files, which
can affect performance.
Import Profiles
OIC: SQL Loader This is the directory where the ASRU Null
Control File Directory SQL Loader control file is stored. It
is recommended that this profile
be set at the site level to absolute
path for $CN_TOP/bin.
$CN_TOP/bin has to be first
translated into a full physical path.
If the bin directory does not exist it
should be created, with read/write/
execute permission given to it.
OIC: SQL Loader Data The directory where the CSV files ASRU Null
File Directory for server side transaction import
are located. See Guidelines.
Payment Profiles
OIC: Approve or Reject Use this profile to set Payroll to S Reject

Duplicate Payment automatically accept multiple
Transactions payment batches submitted in the
same period. Settings are Reject
(do not allow multiple entry--the
default), Insert (create new entry)
or Update (change existing entry).

OIC: Enforce Payment Determines whether the validate S Y

Worksheet Approval payment worksheets statuses must
be Approved when paying a
payment batch. Enables auto
approval process for payment
batches after they have been
frozen. When set to Yes, the
approval process for worksheets is
enforced to pay a payment batch.
When set to No, a payment batch
can be paid after it has been frozen
regardless of the status of
worksheets in the payment batch.
OIC: Pay by Transaction Determines if payment details for S N

a worksheet are displayed at the
transaction level or aggregated at
the plan element level. Valid
values are Y and N.
If the value is set to Y, the payment

details are shown at the
transaction level. If the value is set
to N, the payment details are
aggregated at the plan element
level.
If set to N and integration with AP

is by Product, expense codes are
not displayed in AP.
Performance Profiles
OIC: LOV Input If set to Yes, the two profiles OSO: ASR Yes
Validation Minimum search string length and
OSO: Search Lead Wildcard are
enforced in LOVs.
Upgrade Profiles
OIC: Invoice Split Used to set an end date for the ASRU Null
Upgrade End Date invoice split upgrade process. This
enhances performance.
Profile Options 9-7

OIC: Invoice Split Used to set the start date for the ASRU Null
Upgrade Start Date invoice split upgrade process. This
enhances performance.
Other Profiles
AMS: Item Validation This is required if you want to ASRU Blank

Master Organization display the Product tab in Oracle
Incentive Compensation. The
value is selected by using an LOV
(master organization for which
items are defined).
ASO: Automatic Sales Determines if and when Quoting S Partial

Credit Allocation calls the sales credit allocation
engine to get sales credit receivers
and percentages.
ASO: Automatic Sales Determines if and when Quoting S Partial

Team Assignment calls Territory Manager to assign
sales teams to quotes.
ASO: Calculate Determines if projected AS Yes

Projected Commission commission is available in
Quoting.
Bypass Group Set to Y to bypass group usages ASR No

Validation when defining a resource and
assigning that resource to a
resource group.
JTFRS: Employee To make the Resource tab and R

Resource Update Access other HTML pages editable in
Oracle Incentive Compensation
and the 360 Degree view, this
profile must be set to Any. See
other two related profiles below.
JTFRS: Group Update To make the Resource tab and R

Access other HTML pages editable in
profile must be set to All.

JTFRS: Resource active Use this profile to end date the

days after termination of resource and sales rep records
resource used by Oracle Incentive
Compensation after a specific
number of days. Set the number of
days after actual termination that
you want the records to be
updated. For example, if the end
date is 15-June-2007 and the profile
is set for 60 days, then the records
will be end dated on 14-Aug-2007.
JTFRS: Role Update To make the Resource tab and R

Access other HTML pages editable in
profile must be set to All.
MO: Operating Unit Verify or set this profile option to R [operating unit
the appropriate operating unit. name]
Mandatory.
OSO: Debug Messages Setting to display or hide ASRU No

On debugging messages
OSO: Enabled If set to "On", instruction text ASRU On

Instruction Text appears on applicable pages.
If set to "Off", instruction text is not

displayed.
OSO: Enable Record Enables record count in tables. ASRU No

Count in Tables
OSO: Max Attachment Maximum attachment size in S 100,000

Size bytes.
OSO: Minimum search Used in Incentive Compensation to S 4

string length set the minimum number of
characters required for any search
from a text field.
Profile Options 9-9

OSO: Search Lead Indicates if % can be the first ASRU No

Wildcard character in a search sent to a list
of values
Notes
The following profile options are set automatically if you run AutoConfig. All of them
set the displayed default value at Site Level.
• OIC: SQL Loader Side Data File Directory - Set to @
"%s_applcsf%/inbound/%s_contextname%".
• OIC: SQL Loader Control File Directory - Set to "$CN_TOP/bin"
If your inbound/outbound file is being created or is used by a concurrent program, set

your profile option value as follows:
• If your profile is used for creating outbound files:
"%s_applcsf%/outbound/%s_contextname%"
• If your profile is used for reading or using inbound files:

"%s_applcsf%/inbound/%s_contextname%"
Variable and Description (Source adctxinf.tmp, adxmlctx.tmp from ARU):

• %s_applcsf% -> APPLCSF
• %s_contextname% -> The name of the Oracle Applications system which this
context points to. This is necessary in order to support running multiple Oracle
instances from the same APPL_TOP.
If the value for your profile needs to be defined as a directory in the utl_file_dir
parameter in the INIT.ora, please set the value for the profile to:
%s_applptmp% .
APPLPTMP is the standard directory in which Oracle Applications temporary files are
created and the directory in which PL/SQL output files are created.
After AutoConfig runs, some profile values will appear differently, as follows:
Before Autoconfig Runs After Autoconfig Runs
%s_applcsf%/inbound/%s_contextname% /u01/proddb/admin/inbound/cn

Before Autoconfig Runs After Autoconfig Runs
APPLCSF /u01/proddb/admin
contextname product name = cn
The OIC: Multi Rollup Path profile option, when set to Y, allows managerial rollups for
resources who are assigned the same role in multiple groups. If a resource is assigned a
role in multiple groups, it must be the same role. This release of Oracle Incentive
Compensation does not support rollup along multiple paths when the managers
receiving the credit have different roles in the compensation groups along the rollup
paths. This is because the application picks the role at random.
Profile Options 9-11

10
Lookups

• Lookups
• Viewing and Editing Lookups
• Creating a Lookup
• List of Lookups
Lookups
Lookups enable quick selection from drop-down menus. Lookups ensure accuracy
when entering data. Oracle Incentive Compensation has 100 lookups incorporated into
its system to speed the process of entering data into forms. The lookups listed in the
following table display the user name in the left column; the Type name is shown in full
caps in the right column with the default selections below it. You can add lookups and
add values to the default lists.
Oracle recommends that you do not delete any of the lookups shipped with the
application.
Viewing and Editing Lookups

Most lookups that come with Oracle Incentive Compensation when you install it are
editable to suit your business requirements. To view or edit existing lookups, perform
the following procedure.
Navigation
Incentive Compensation Administrator > Lookups
Lookups 10-1
Steps
1. Press the F11 key and query for Incentive Compensation in the Application field.
2. Press Control and the F11 key.
3. Scroll through the lookups by using the up and down arrow keys or use Find in the
View drop-down menu. Make changes as needed. Leave the cursor in the Type
field while scrolling.
Creating a Lookup
To create a new lookup, perform the following:
Steps
1. In the Navigator, double-click Lookups.
2. Select Incentive Compensation from the Application field.
3. Enter the name using all caps with underscores between words.
4. In the table in the lower part of the window, enter one or more values that you
want to use in the lookup. Enter a code, meaning, and description that are easy for
users to understand.
5. Enter effective dates.
6. Check the Enable box if you want the lookup to be operational within the effective
date range.
7. Save.
List of Lookups
The following table lists Oracle Incentive Compensation Lookups, including a
description, Access Level, and Seeded Values and Meanings.
Lookup Type Description Lookup Code and Meaning
ACCESS_CODE Access Code UPDATE
VIEW

ADJUSTMENT_REASON Manual Adjustment Reason AR_ERROR (Accounts

Receivable Processing Error)
OE_ERROR (Error During

Order Entry)
OTHER
SHARED (Commissions
should be Split)
ADJUSTMENT_STATUS Manual Adjustment Status CANCELED
POSTED
REVERSED
REVIEW
TRIAL
Lookups 10-3
ADJUST_STATUS Transaction Adjust Status DEALASGN (Deal Move)
DEALSPLIT (Deal Split)
FROZEN
INVLOAD (Invoice
Captured)
MANUAL
MASSADJ (Move Credits)
MASSASGN (Share Credits)
ORIGINAL
REVERSAL
SCA_ALLOCATED
(Processed - Credit Allocated)
SCA_DISTINCT_ERROR
(Error - More than one
Distinct Set of Mapping
Columns)
SCA_NOT_ALLOCATED
(Processed - No Credit
Allocated)
SCA_NOT_ELIGIBLE (Not
Eligible for Credit Allocation)
SCA_NO_RULE (Processed -
No Credit Rule Found)
SCA_PENDING (Frozen for

Credit Allocation)
SCA_REVENUE_ERROR
(Error - No Revenue Line)
SCA_ROLE_ERROR (Error -
Invalid Role)
SCA_SRP_ERROR (Error -
Invalid Salesrep)
SPLIT (Splits)

ADVANCED SEARCH Advanced Search ADJUSTED_BY
ADJUST_DATE
ADJUST_STATUS_DISP
(Adjust Status)
DIRECT_SALESREP_NAME
(Direct Salesperson Name)
DIRECT_SALESREP_NUMBE
R (Direct Salesperson
Number)
INVOICE_DATE
INVOICE_NUMBER
LOAD_STATUS
ORDER_DATE
ORDER_NUMBER
PROCESSED_DATE
QUANTITY
REVENUE_TYPE_DISP
(Revenue Type)
ROLLUP_DATE
STATUS_DISP (Calculation
Status)
TRANSACTION_AMOUNT
(Functional Amount)
TRX_TYPE_DISP
(Transaction Type)
ALL_COMPONENTS All Components ALL_COMPONENTS
ANALYST_NOTE_REASON Analyst Note Reason SYSTEM_GENERATED
USER_DEFINED
Lookups 10-5
ANC_CALC_METHOD LINE_CALC (Line

Calculation)
STEP_CALC (Step
Calculation
APPLICATION_TYPE Application Type AR (Oracle Receivables)
CN (Oracle Commissions and

Sales Analysis)
GL (Oracle General Ledger)
OE (Oracle Order Entry)
RA (Oracle Revenue
Accounting)
APPL_STATUS Applicable Status NA (Not Applicable)
APPROVE_REJECT Approve Reject APPROVE
REJECT
ASSIGN_TYPE_CODE Assign Type RESASGN (Resource

Assignment)
ROLEASGN (Role
Assignment)
BASE_RULE Base Rule BASE_RULE
BATCH_STATUS Batch Status POSTED
UNPOSTED
CALCULATION_STATUS Calculation Status COMPLETED
FAILED
INCOMPLETE
PROCESSING (Running)
CALCULATION_TYPE Types of Calculation BONUS
COMMISSION

CALC_SUBMISSION_OBJEC Calculation Submission CALC_TYPE (Calculation

T_TYPE Object Type)
CONCURRENT_FLAG
(Concurrent Calculation)
EMPLOYEE_NUMBER
EMPLOYEE_TYPE
END_DATE
HIERARCHY_FLAG (Entire
Hierarchy)
INTELLIGENT_FLAG
(Incremental Calculation)
INTERVAL_TYPE
NAME (Batch Name)
RESPONSIBILITY_NAME
SALESREP_OPTION
(Salespeople)
START_DATE
USER_NAME
CLASSIFICATION_DATATY Classification Datatype ALPN (Alpha Numeric)

PE
DATE
NUMB (Numeric)
CLASSIFICATION_STATUS Classification Status CLS (Classified)
NEVER (Never Classified)
XCLS (Failed Classification)
CN_COLL_FILTER_STATUS Collection Filter Status N (Mark As Filtered)
Y (Physically Delete)
PON (Post-Notification)
PRC (Post-Collection)
PRN (Pre-Notification)
Lookups 10-7
CN_CW_SETUP_TASK_STA Setup Task Status COMPLETED

TUS
INPROGRESS (In Progress)
NOTAPPLICABLE (Not
Applicable)
NOTSTARTED (Not Started)
CN_EXPRESSION_OPERAT Expression Operators 0 (AND)

ORS
1 (OR)
CN_HEAD_TRX Header Transaction Status CALC (Calculated)
OBSOLETE (Obsoleted)
POP (Populated)
ROLL (Rolled Up)
XCALC (Failed Calculation)
XPOP (Failed Population)
CN_NOTES Notes NOTES

CN_NOTE_FIELDS CN Note Fields CUSTOMIZED (Customized

Flag)
END_DATE
FIXED_AMOUNT
GOAL
LOCK_FLAG (Preserve
Customization)
MAX_AMT (Maximum
Amount)
MIN_AMT (Minimum
Amount)
PAYEE (Payee Name)
PMT_PLN (Payment Plan

Name)
START_DATE
TARGET
CN_OPERAND Incentive Compensation 0 (AND)

Operand
1 (OR)
CN_OPERATOR Incentive Compensation 0 (AND)

Operator
1 (OR)
CN_PAYMENT_TRX_TYPE Payment Transaction Type N (Summary)
Y (Transaction)
CN_PAY_GROUP_DTLS_TY Lookup code for Pay Group PERIODS

PE_CODE Details Display by
SALESPEOPLE
Lookups 10-9
CN_PROMPTS Prompt Texts used in UI DIMENSION_NAME

interface
EXP_NAME (Expression
Name)
FORMULA_NAME
RATE_TABLE_NAME
CN_R2P_CLUB_ELIG Club Eligible N (No)
Y (Yes)
CN_REPORTS_COMM_SUM Types for Commission ALL_PLAN_ELEMENTS

M_TYPES Summary Report
ALL_TRX_TYPES (All
Transaction Types)
BONUS
COMMISSION
PAYADJ (Payment
Adjustments)
CN_RULE_CREATE_TYPE Rule Create Type CHILD
ROOT
SIB (Sibling)
CN_RULE_OPERATORS Rule Operators BETWEEN
EQUALS
NOT_BETWEEN
NOT_EQUALS (Does not

equal)
CN_SEARCH_CATEGORIES Incentive Compensation JOBTITLE (Job Title)

Search Categories
QUOTA (Quota Modeling
Groups)
ROLE (Roles)
SALESREP (Salespeople)

CN_UNPROC_TRX_STATUS Unprocessed Transaction CLS (Classified)

Status
COL (Unloaded)
ROLL (Rollup)
XROLL (Failed Rollup)
CN_USAGE_FLAG Incentive Compensation C (Collection)

Usage Flag
Y (Calculation)
CN_VIEW_COLUMNS How to View Columns ATTRIBUTES
CLASS_ATTRIBUTES
(Classification Attributes)
DIMENSION_ATTRIBUTES
KEY_ATTRIBUTES (Primary
Key Attributes)
CN_VIEW_PAYGROUP How to View Paygroups ACTIVE (Active Pay Groups)
ALL (All Pay Groups)
CN_VIEW_PMT_PLAN How to View Payment Plans ACTIVE (Active Payment

Plans)
ALL (All Payment Plans)
CN_WORKBENCH_TASK_S Configuration Workbench COMPLETED

TATUS Task Status
INPROGRESS
NOTAPPLICABLE
NOTSTARTED
COLLECTION_FILTER_OPTI Collection Filter Options DELETE

ONS
MARKFILTER (Mark as
Filtered)
NONE
Lookups 10-11
COLLECTION_TRANS_SOU Standard Transaction COLLECTAR (Receivables

RCES Collection Sources Posting)
COLLECTOE (Order
Booking)
COLLECTION_TRANS_TYP Collection Transaction Types CBK (Clawbacks)

E
INV (Invoices)
PMT (Payments and

Givebacks)
RAM (Revenue Adjustments)
WO (Writeoffs)
COLLECTION_TRIGGERS Collection Triggers NONE (None)
POSTCOLLECT (Post
Collection)
POSTNOTIFY (Post
Notification)
PRENOTIFY (Pre
Notification)
COLLECTION_TYPE Collection Type CN_COLLECT_CLAWBACK
CN_COLLECT_CUSTOM
(Collect Custom Transaction
Source)
CN_COLLECT_INVOICES
CN_COLLECT_ORDERS
CN_COLLECT_PAYMENTS
(Collect Payments and
Givebacks)
CN_COLLECT_RAM (Collect
Revenue Adjustments)
CN_COLLECT_WRITEOFFS

COLUMN_TYPE Column Type CF (Commissions Factor)
CN (User Defined)
EF (Event Factor)
IN (System)
PF (Payment Factor)
CP_OBJECT_TYPE Compensation Plan Objects CP_NAME (Compensation

Plan Name)
DESC (Description)
END_PERIOD
REV_CLS_OVERLAP (Allow
Revenue Class Overlap)
START_DATE
START_PERIOD
STATUS_CODE
CP_PHASE_CODE Concurrent Request Phase C (Completed)

Code
I (Inactive)
P (Pending)
R (Running)
Lookups 10-13
CP_STATUS _CODE Concurrent Request Status A (Waiting)

Code
B (Resuming)
C (Normal)
D (Cancelled)
E (Error)
G (Warning)
H (On Hold)
I (@Normal)
M (No Manager)
P (Scheduled)
Q (Standby)
R (@@Normal)
S (Suspended)
T (Terminating)
U (Disabled)
W (Paused)
X (Terminated)
Z (@Waiting)
CURRENCY_TYPE Currency Type used in FUNCTIONAL_CURRENCY

reports
SALESREP_CURRENCY
(Resource Currency)
DATA_TYPE Column Datatypes DATE
LONG
NUMBER
VARCHAR2

DELIMITER_TYPE Delimiter Type COMMA
DOUBLEQ (Double
Quotation)
QUOTE (Single Quotation)
SEMICOL (Semicolon)
SPACE
TAB
DISCOUNT_OPTION Discount Option NONE (Not apply discount

percentage)
PAYMENT (Apply to
payment factor)
QUOTA (Apply to quota

factor)
DISTINGUISHED_HIERARC Distinguished Hierarchies REVENUE_CLASS (Revenue

HIES Class Rollup)
SALESREP (Sales
Representative Rollup)
DISTRIBUTE_METHOD Distribution Method EQUAL
EVEN
MIN (Minimum)
DYNAMIC_PROMPT Period Processing Status DISTRIBUTE_DRAW

Dynamic Prompt
DISTRIBUTE_TARGET
DRAW
PAYMENT
PERIOD_DRAW
PERIOD_TARGETS
TARGET
Lookups 10-15
ELEMENT_TYPE Element Type -1000 (Recoverable Payment)
-1001 (Nonrecoverable
Payment)
ENCLOSED_TYPE Enclosed Type COMMA
DOUBLEQ (Double
Quotation)
QUOTE (Single Quotation)
SEMICOL (Semicolon)

EVENT_NAME Event Name CHANGE_CLS_HIER

(Change a hierarchy used in
classification)
CHANGE_CLS_HIER_DATE
(Change a hierarchy date
range used in classification)
CHANGE_CLS_HIER_DELE
TE (Delete a hierarchy
interval used in classification)
CHANGE_CLS_HIER_PERIO
D (Change a hierarchy
interval used in classification)
CHANGE_CLS_RULES(Chan
ge classification rules)
CHANGE_CLS_RULES_ATT
R (Change classification rules
attribute)
CHANGE_CLS_RULES_DAT
E (Change classification rule
set date range)
CHANGE_CLS_RULES_HIE
R (Change classification rules
hierarchy)
CHANGE_CLS_RULES_REV
(Change classification rules
revenue class)
CHANGE_CLS_RULES_SET
(Change classification rule set
CHANGE_COMP_PLAN
(Change compensation plan)
CHANGE_COMP_PLAN_OV
ER_LAP_FLAG (Change
compensation plan overlap
flag)
CHANGE_COMP_PLAN_PE
RIOD (Change compensation
plan effective interval)
CHANGE_CP_ADD_MGR
Lookups 10-17
(Add a manager to a
compensation group)
CHANGE_CP_ADD_SRP
(Add a salesperson to a
compensation group)

EVENT NAME (continued) Event Name CHANGE_CP_DELETE_MG

R (Delete a manager from a
compensation group)
CHANGE_CP_DELETE_SRP
(Delete a salesperson from a
compensation group)
CHANGE_CP_HIER_ADD
(Add an edge to
compensation group
hierarchy)
CHANGE_CP_HIER_DATE
(Change date range of a
compensation group
hierarchy edge)
CHANGE_CP_HIER_DELET
E (Delete an edge from a
compensation group
hierarchy)
CHANGE_CP_MGR_DATE
manager)
CHANGE_CP_SRP_DATE
salesperson)
CHANGE_DELETE_TRX
(Delete transactions)
CHANGE_FORMULA
(Change a formula)
CHANGE_INSERT_TRX
(Insert new transactions)
CHANGE_PERIOD_INTERV
AL_NUMBER (Change a
period's interval number)
CHANGE_PLAN_ASSIGN
(Change plan assignment
CHANGE_PLAN_ASSIGN_I
NS_DEL (Insert or delete plan
assignment)
Lookups 10-19
CHANGE_PLAN_ASSIGN_P
ERIOD (Change plan
assignment effective interval)
CHANGE_QUOTA_CALC
(Change plan element)

EVENT_NAME (continued) Event Name CHANGE_QUOTA_DATE

(Change plan element date
range)
CHANGE_QUOTA_PERIOD
(Change plan element
effective interval)
CHANGE_QUOTA_POP
revenue class factors)
CHANGE_QUOTA_ROLL
revenue class)
CHANGE_QUOTA_UPLIFT_
DATE (Change plan element
uplift factors date range
CHANGE_RC_HIER_DATE
(Change revenue class
hierarchy date range)
CHANGE_RC_HIER_DELET
E (Delete revenue class
hierarchy effective interval)
CHANGE_RC_HIER_PERIO
D (Change revenue class
CHANGE_RT_INS_DEL
(Insert or delete rate tiers)
CHANGE_RT_RATES
(Change rate table rates)
CHANGE_RT_TIERS
(Change rate table tiers)
CHANGE_SRP_HIER
(Change salesperson
hierarchy)
CHANGE_SRP_HIER_DELE
TE (Delete salesperson
CHANGE_SRP_HIER_PERIO
D (Change salesperson
Lookups 10-21
CHANGE_SRP_PAY_GROU
P (Change pay
group/salesperson
assignment)
CHANGE_SRP_PAY_GROU
P_DATE (Change date range
of pay group/salesperson
assignment)
CHANGE_SRP_QUOTA_CA
LC (Change salesperson's
plan element setting)
EVENT_NAME (continued) Event Name CHANGE_SRP_QUOTA_PA

YEE_DATE (Change date
range of payee assignment)
CHANGE_SRP_QUOTA_PO
P (Change salesperson's uplift
factors or payee assignment)
CHANGE_SRP_ROLE_PLAN
(Change role/plan or
role/salesperson assignment)
CHANGE_SRP_ROLE_PLAN
_DATE (Change date range of
role/plan/salesperson
assignment
CHANGE_SYS_PARA_RC
(Change revenue class
hierarchy used)
CHANGE_SYS_PARA_SRP
(Change salesperson
hierarchy and roll up flag)
CHANGE_TEAM_ADD_REP
(Add a salesperson to a team)
CHANGE_TEAM_DEL_REP
(Delete a salesperson from a
team)
CHANGE_UPDATE_TRX
(Update transactions)

EXPRESSION_MESSAGES Messages Required for Rule AND

Attribute Expressions
BET (Between)
GT (Greater than)
IIH (In Hierarchy)
IS
LT (Less than)
NOT
OR
RES (Result)
WV (With Value)
EXPRESSION_TYPE Expression Type EXPRESSIONS
EXTERNAL_ELEMENTS
FORECAST_AMOUNT
FORMULAS
GROUP_FUNCTIONS
NUMBER_FUNCTIONS
OSC_ELEMENTS (Sales
Compensation Elements)
OTHERS
PLAN_ELTS (Plan_Elements)
RATE_TABLE_RESULT
SQL_FUNCTIONS
Lookups 10-23
EXTERNAL_TABLE External Table ALIAS
CN_CALC_EXT_TABLE_ID
(Table)
COLUMN (Columns)
EXTERNAL_COLUMN_ID
(External Column Name)
EXTERNAL_TABLE_ID
(External Table Name)
INTERNAL_COLUMN_ID
(Internal Column Name)
INTERNAL_TABLE_ID
(Internal Table Name)
NAME
SCHEMA
USED_FLAG
FORMULA_STATUS Formula Status COMPLETE
FAILED
INCOMPLETE
INPROGRESS
INVALID
VALID
FORMULA_TYPE Formula Type B (Bonus)
C (Commission)

GROUP_FUNCTIONS Group Functions AVG (Average)
COUNT
MAX (Maximum)
MIN (Minimum)
STDDEV (STDDEV)
SUM
VARIANCE
HEADER_TRX_STATUS Transaction Header Statuses CLS (Classified)
COL (Unprocessed)
ROLL (Rolled Up)
HOLD_REASON_CODE Hold Reason Code HOLD
IMPORT_STATUS Import Status CANCEL
COMPLETE
FAIL
IMPORT_FAIL (Failed at
Importing)
NEW
SCHEDULE
STAGE
STAGE_FAIL (Failed at
Staging)
SUBMIT
Lookups 10-25
IMPORT_TYPE Import Type CALCEXP (Expressions)
EXPORT
HIERARCHY
IMPORT
REVCL (Revenue Class)
RULES
TRXAPI (Transaction API)
INCENTIVE_TYPE Incentive Type BONUS
COMMISSION
MANUAL
PAYMENT
QUOTA
INCENTIVE_TYPES Incentive Types BONUS
COMMISSION
MANUAL_PAY_ADJ
(Manual Pay Adjustment)
PMTPLN (Payment Plan)
PMTPLN_REC (Payment
Recovery)
INDIRECT_CREDIT_TYPE Indirect Credit Type ALL
MGR (If Credit Receiver has

Manager Role)
NONE

INPUT_TOKEN Input Token CP_NAME (Comp Plan

Name)
NAME
PE (Plan Element)
PE_NAME (Plan Element

Name)
PERIOD_NAME (Period
Name)
QC (Quota Category)
QSR (Quota
Category/Sequence
Number/Role)
RC (Revenue Class)
RCS (Role/Compensation
Plan Name/Start Date)
ROLE_NAME
ROLLPERCENT (Rollover
Percentage)
RP (Base Quota
Component/Percent)
SD (Start Date)
SEQ (Sequence Number)
SPE (Source Plan Element)
SR_NAME (Salesrep Name)
INTERVAL_TO_DATE Interval to Date setting ALL
ANNUAL
ITD (Interval to Date)
PTD (Period to Date)
Lookups 10-27
JE_BATCH_REASON Reason for creating JE batch BONUS
CALC (Calculation)
DRAW_BONUS (Draw
Recovery from Bonus)
DRAW_COMM (Draw
Recovery from Commission)
PAYMENT
PAY_ADJ (Adjustment
Payment)
PAY_BONUS (Payment from

Bonus)
PAY_COMM (Payment from

Commission)
PAY_DRAW (Draw Payment)
LOAD_STATUS Load Status FILTERED
LOADED
UNLOADED

LOAD_STATUS_LOOKUP Load Status Error Messages ERROR - CANNOT

CONV/DEFAULT (Error -
Cannot Convert/Default
ERROR - INCORRECT
CONV GIVEN (Error -
Incorrect Conversion Given
ERROR - NO EXCH RATE

GIVEN (Error - No Exchange
Rate)
ERROR - PRIOR
ADJUSTMENT (Error - Prior
Adjustment Frozen
ERROR - REVENUE_CLASS
(Error - Revenue Class
Invalid)
ERROR - TRX_TYPE (Error -

Transaction Type Invalid)
LOADED
OBSOLETE
PERIOD ERROR (Unopened

Period)
SALESREP ERROR
(Salesperson Invalid)
UNLOADED
MAPPING_TYPE Mapping Types COL (Collection)
EVT (Event)
SLC (Slice)
MESSAGE_TYPE Message Types DEBUG
ERROR
TRANSLATE (Translated)
Lookups 10-29
MGR_REPORT Top Bottom Performance 1 (Directs)

Report Hierarchy Level
2 (Level 1 Indirects)
ALL (All)
MODULE_STATUS Module Status CONCFAIL (Concurrent

Manager Down)
GENERATED (Complete)
INSTFAIL (Install Failed)
INSTINPG (Install Pending)
UNSYNC (Incomplete)
MODULE_STATUS_OLD Old Module Status DEF (Definition)
GEN (Generated)
GRQ (Generate Request)
INS (Instantiated)
IRQ (Instantiate Request)

MODULE_TYPE Module Types ACCGEN (Account

Generation)
CALCULATION
CB (Clawback Collection
Module)
CB/GB (Clawback/Giveback
Collection Module)
CLS (Classification Module)
COL (Collection Module)
CPAPI (Compensation Plan

API Module)
INS (Commissions Instance

Module)
INV (Invoice Collection

Module)
LOADER (Transaction
Interface Loader)
ORD (Order Collection

Module)
PEAPI (Plan Element API

Module)
PECLS (Plan Element

Classification)
PMT (Payments Collections

Module)
PMT/GB (Payments/Giveback
Collection Module)
REVCLS (Revenue
Classification)
RUP (Rollup Module)
SLC (Slice Module)
TRF (Transfer Module)
TRX (Commissions
Transaction Table Module)
Lookups 10-31
WO (Writeoff Collection
Module)
NOTIFY_ACTION The action to be taken due to DELETE (Delete transactions)

events caused by changing
compensation group PULL (Pull transactions up)
hierarchy ROLL (Roll transactions up)
ROLL_PULL (Roll and pull

transactions up)
NOTIF_LOOKUP_TYPE Lookup used by SF Planning ACCEPT/REJECT (Accept)

workflow process
APPROVE (Approve)
CUSTOMIZED (Customized)
DISTRIBUTE (Distribute)
NOTIFIED (Notification Sent)
NOT_NOTIFIED
(Notification not Sent)
REMINDER (Reminder)
OBJECT_STATUS Object Status I (Invalid)
N (New)
V (Valid)
OBJECT_TYPE Object Types COL (Column)
DBL (Database Link)
IND (Index)
PKB (Package Body)
PKS (Package Specification)
PRC (Procedure)
SEQ (Sequence)
TBL (Table)
TRG (Trigger)

ORDER Order ASC (Ascending)
DESC (Descending)
ORGANIZATION Organization ALLIANCES (Alliances)
BOL (Business Online)
EDUCATION (Education)
ISD (Telesales)
SALES (Sales)
SC (Sales Consulting)
SUPPORT (Support)
PAYABLES_CCID_LEVEL Payables CCID Level REVCLS (Revenue Class)
PLANELEM (Plan Element)
CUSTOM (Custom)
CLASSIFICATION
(Classification)
PAYGROUP_UPGRADE_TY Paygroup Upgrade Type UPGRADE_PAYGROUP

PE (Upgrade Pay group)
PAYMENT_CHANGE Payment Change BONUS (Bonus Change)
COMMISSION (Commission
Change)
PAYMENT_GROUP_CODE Payment Group Code STANDARD (Standard)
PAYMENT_INCENTIVE_TY Payment Incentive Type ALL (All)

PE
BONUS (Bonus)
COMMISSION (Commission)
PAYMENT_PLAN_TYPE Payment Plan Type MIN/MAX

(Minimum/Maximum Plan)
Lookups 10-33
PAYRUN_ACTION Payrun Action CREATE (Create Payrun)
FREEZE (Freeze Payrun)
PAY (Pay Payrun)
REFRESH (Refresh Payrun)
REMOVE (Remove Payrun)
UNFREEZE (Unfreeze
Payrun)
PAYRUN_STATUS Payrun Status PAID (Paid)
PAID_WITH_RETURNED_F
UNDS (Paid with Returned
Funds)
POSTED (Posted)
RETURNED_FUNDS
(Returned Funds)
UNPAID (Unpaid)
FROZEN (Frozen)
ALL (All)
PAY_GROUP_DTLS_TYPE_C Pay Group Details Type Code PERIODS (Period)

ODE
SALESPEOPLE (Resource
Assignment)
ROLES (Role Assignment)
PAY_GROUP_VALIDATION Pay Group Validation END_DATE (Pay Group End

_TYPE Date)
PAY_GROUP_NAME (Pay
Group Name)
PERIOD_SET_NAME
(Calendar)
PERIOD_TYPE (Period Type)
START_DATE (Pay Group

Start Date)

PAY_RUN_VALIDATION_T Payrun Validation CREDIT_TYPE (Credit Type)

YPE
EMPLOYEE_NUMBER
(Employee Number)
EMPLOYEE_TYPE
(Employee Type)
PAY_DATE (Pay Date)
PAY_GROUP_NAME (Pay
Group Name)
PAY_RUN_NAME (Payrun
Name)
ROLE (Role)
SALES_PERSON
(Salesperson)
PAY_STATUS Pay Status PAID (Paid)
UNPAID (Unpaid)
PA_OBJECT_TYPE Compensation Plan EMP_NUM (Employee

Assignment Objects Number)
PERIOD_PROCESSING_STA Period Processing Status CALCULATED (Calculated)

TUS
CLASSIFIED (Classified)
CLEAN (Clean)
POPULATED (Populated)
PROCESSING (In Progress)
ROLLED_UP (Rolled Up)
UNCLASSIFIED
(Unclassified)
PERIOD_TARGET_DIST_RU Period Target Distribution EQUAL (Equal)

LE Rule
USER_DEFINED (User
Defined)
Lookups 10-35
PERIOD_TYPE_CODE Period Type PERIOD (Period)
QUARTER (Quarter)
YEAR (Year)

PE_OBJECT_TYPE Plan Element Objects CALC_FORMULA_ID

(Formula ID)
CALC_FORMULA_NAME
(Formula Name)
CREDIT_TYPE (Credit Type)
CUM_FLAG (Accumulate
Flag)
DESC (Description)
DISC_OPTION (Discount
Option)
DISC_RATE_TB (Discount
Rate Table)
DISC_RATE_TB_ID (Discount
Rate Table ID)
DRAW_AMOUT (Draw
Amount)
END_DATE(End Date)
END_PERIOD (End Period)
END_PERIOD_ID (End
Period ID)
INCENTIVE_TYPE_CODE
(Incentive Type)
INTERVAL NAME (Interval

Name)
ITD_FLAG (Interval to Date)
PACKAGE_NAME (Package
Name)
PAYMENT_AMOUNT
(Payment Amount)
PAYMENT_FACTOR
(Payment Uplift)
PAYMENT_TYPE (Payment
Type)
PERIOD_TYPE (Interval
Lookups 10-37
Type)

Name)
QUOTA_FACTOR (Quota
Uplift)
QUOTQ_TYPE (Element
Type)
RATE_TB (Rate Table)
RATE_TB_ID (Rate Table ID)
REV_CLS_ID (Revenue Class

ID)
REV_CLS_NAME (Revenue
Class Name))
PE_OBJECT_TYPE REV_CLS_TARGET (Revenue

(continued) Class Target
SPLIT_FLAG (Split Flag)
START_DATE (Start Date)
START_PERIOD (Start
Period)
START_PERIOD_ID (Start
Period ID)
TARGET (Quota)
TRX_GROUP (Apply Trx)
UPLIFT_END_DATE (Uplift
End Date)
UPLIFT_PAYMENT_FACTO
R (Uplift Payment Factor)
UPLIFT_QUOTA_FACTOR
(Uplift Quota Factor)
UPLIFT_START_DATE
(Uplift Start Date)

PLAN_ELEMENT_METRICS Plan Element Metrics COMMISSION_PAYED_ITD

(Interval To Date Commission
Paid)
COMMISSION_PAYED_PTD
(Period To Date Commission
Paid)
IMPUT_ACHIEVED_ITD
(Interval To Date Input
Achieved)
INPUT_ACHIEVED_PTD
(Period To Date Input
Achieved)
ITD_PAYMENT (Interval To
Date Payment)
ITD_TARGET (Interval to
Date Target)
PERF_ACHIEVED_ITD
(Interval To Date Sales Credit)
PERF_ACHIEVED_PTD
(Period To Date Sales Credit
PERIOD_PAYMENT (Period
Payment)
TARGET_AMOUNT (Target
Amount)
PLAN_GENERATE_STATUS Plan Generation Status FAILED (Failed)
NOT_PUSHED (Not
Activated)
PUSHED (Activated)
PLAN_OBJECT_STATUS Compensation Plan Object COMPLETE (Complete)

Status
INCOMPLETE (Incomplete)
PLAN_STATE Plan State ACTIVE (Active)
INACTIVE (Inactive)
IN_PROGRESS (In Progress)
Lookups 10-39
PMT_PLAN_VALIDATION_ Payment Plan Validation CREDIT_TYPE (Credit Type)

TYPE Type
PMT_PLAN_NAME
(Payment Plan Name)
POSTING_TYPE Posting Type EXPENSE (Expense)
NON_REC (Non
Recoverable)
REC (Recoverable)
TO_REC (To Recover)

PRE_PROCESSED_CODE Preprocessed Code CRPN (Skip Calculation)
CRPC (Skip Nothing)
CRNC (Skip Population)
CRNN (Skip Population and

Calculation)
CNPC (Skip Rollup)
CNPN (Skip Rollup and

Calculation)
CNNC (Skip Rollup and

Population)
CNNN (Classification Only)
NRPC (Skip Classification)
NRPN (Skip Classification

and Calculation
NRNC (Skip Classification

and Population)
NRNN (Rollup Only)
NNPC (Skip Classification

and Rollup)
NNPN (Population Only)
NNNC (Calculation Only)
NNNN (Skip All)
PROCEDURE_TYPE Procedure Types F (Function)
P (Procedure)
PRIVATE (Private Procedure)
PUBLIC (Public Procedure)
PROCESSING_STATUS_CO Processing Status CLEAN (No calculation has

DE ever happened in this period)
Lookups 10-41
PROCESS_TYPE Process Types GEN (Generate)
INS (Instantiate)
XFR (Transfer)
QUOTA_CATEGORY Quota Category Type FIXED (Fixed)
TOTAL_QUOTA (Total
Quota)
VAR_NON_QUOTA
(Variable, Non Quota Based)
VAR_NON_REVENUE
(Variable, Non Revenue
Based)
VAR_QUOTA (Variable,
Quota Based)
QUOTA_GROUP_CODE Quota Group Code BONUS (Bonus)
QUOTA (Quota)
QUOTA_PAYMENT_TYPE Quota Payment Type FIXED (Fixed Amount)
PAYMENT (Payment
Amount Percentage)
TRANSACTION (Applied
Transaction Amount
Percentage)
QUOTA_TRX_GROUP Quota Transaction Group GROUP (Grouped by

Interval)
INDIVIDUAL (Individually)

QUOTA_TYPE Quota Type DISCOUNT (Discount)
DRAW (Draw)
EXTERNAL (External)
FORMULA (Formula)
MANUAL (Manual)
MARGIN (Margin)
NONE (None)
REVENUE (Revenue Non

Quota)
TARGET (Revenue Quota)
UNIT_BASED_NON_QUOT
A (Unit Non Quota)
UNIT_BASED_QUOTA (Unit
Quota)
REPORT_SECURITY_LEVEL Report Security Level A (Analyst)
M (Manager)
R (Salesrep)
S (Super User)
REPOSITORY_STATUS Repository Status A (Active)
I (Inactive)
REPOSITORY_USAGE Repository Usages A (All)
P (Collector)
S (Calculator)
RESOURCE_PLAN_ACTIVA Resource Plan Activation FAILED (Failed)

TE_STATUS Status
NOT_PUSHED (Not
Activated)
PUSHED (Activated)
Lookups 10-43
RETURN_STATUS API Return Status E (Error)
S (Success)
U (Unexpected Error)
W (Warning)
REVENUE_TYPE Transaction Credit Type NONREVENUE

(Nonrevenue)
REVENUE (Revenue)
RS_OBJECT_TYPE Rate Table Objects COMM_AMT (Commission

Amount)
COMM_UNIT_CODE
(Commission Unit Code)
MAX_AMT (To Tier

Maximum Amount)
MIN_AMT (From Tier

Minimum Amount)
RATE_TB_NAME (Rate Table

Name)
TIER_UNIT_CODE (Tier Unit

Code)
RULE_CREATE_TYPE Rule Create Type for Root, CHILD (Child)

Sibling, Child
ROOT (Root)
SIB (Sibling)

RULESET_TYPE Rule set Type DATA_FLAG (Date Flag)
END_DATE (End Date)
EXPRESSION (Expressions)
MODULE_TYPE (Module
Type)
OBJECT_NAME (Object
Name)
PARENT_RULE_ID (Parent
Rule Identifier)
RULES (Rules)
RULE_ATTRIBUTES
(Attributes)
RULESET_ID (Rule set

Identifier)
RULESET_NAME (Rule set

Name)
RULE_ATTRIBUTE _ID (Rule

Attribute Identifier)
RULE_ID (Rule Identifier)
RULE_NAME (Rule Name)
SEQUENCE_NUMBER
(Sequence Number)
SALESREP_OPTION Salesrep Option ALL_REPS (All Resources)
REPS_IN_NOTIFY_LOG
(Resources in Notify Log)
USER_SPECIFY (Resources
specified by you)
SALESREP_STATUS Salesrep Status A (Active)
I (Inactive)
Lookups 10-45
SCALING_FACTOR OSC: Scaling Factor 0 (No Scaling)
1 (in tens)
2 (in hundreds)
3 (in thousands)
4 (in tens of thousands)
5 (in hundreds of thousands
6 (in millions)
SCENARIO_STATUS Scenario Status SET (Set)
NOT_SET (Not Set)
SPLIT_FLAG Split Flag N (No Split)
P (Proportional)
Y (Non-Proportional)
SRP_OBJECT_TYPE Salesrep Object Type ALL_ROLE (All Sales Roles)
EMP_NUM (Employee
Number)
END_DATE (End Date)
PAY_GRP (Pay Group Name)
PMT_PLN (Payment Plan

Name)
ROLE (Sales Role Name)
SRP_NAME (Salesperson
Name)
SRP_TYPE (Salesperson
Type)

SRP_PAYEE_OBJECTS SRP Payee Assigns Objects COMP_NAME

(Compensation Name)
EMPLOYEE_NUMBER
(Employee Number)
END_DATE (Payee End Date)
PAYEE_NAME (Payee Name)
PAYEE_START_DATE (Payee
Start Date)

Name)
ROLE_NAME (Role Name)
SALESREP_NAME (Resource
Name)
START_DATE (@Payee Start

Date)
TABLE_LEVEL Table Levels D (Dimension)
H (Header Level)
I (Internal)
L (Line +)
N (None)
S (Sales Line)
TABLE_TYPE Table Types T (Table)
V (View)
TABLE_USAGE Table Usage C (Collection)
N (None)
Y (Calculation)
TBL_COL_DETAIL Table Column Detail COL (Columns)
Lookups 10-47
TIMESCALE Timescale PERIOD (Period)
QUARTER (Quarter)
YEAR (Year)
TIME_INTERVAL_TYPE Time Interval Type PTD (Period to Date)
QTD (Quarter to Date)
YTD (Year to Date)
TOP_BOTTOM_PERF Top Bottom Performer BOTTOM (Bottom)
TOP (Top)
TRIGGERING_EVENT Triggering Event D (Delete)
I (Insert)
U (Update)

TRX_TYPES Transaction Types BALANCE_UPGRADE

(Balance Upgrade)
CBK (Clawback)
CM (Credit Memo)
DEP (Deposit)
DM (Debit Memo)
GBK (Giveback)
INV (Invoice)
MAN (Manual Transaction)
ORD (Order)
PMT (Payment)
PMTPLN (Payment Plan)
PMTPLN_REC (Payment Plan

Recovery)
RET (Order Return)
UPGRADE (Upgrade)
WO (Writeoff)
TRX_ROLLUP_METHOD Transaction Rollup Method INV (Invoice Processing Date)
ORD (Order Processing Date)
Lookups 10-49
TRX_STATUS Commission Line Status CALC (Calculated)
CLS (Classified)
COL (Unprocessed)
NCALC (No Calculation)
OBSOLETE (Obsoleted)
PAYEE (Payeed)
POP (Populated)
ROLL (Rolled Up)
XCALC (Failed Calculation)
XPAYEE (Failed Payee)
XPOP (Failed Population)
UNIT_OF_MEASURE Measurement unit AMOUNT (Amount)
EXPRESSION (Expression)
PERCENT (Percent)
STRING (String)
UNIT_TYPE Unit Type UNIT (Unit)
REVENUE (Revenue)
VIEW_PROCESS_LOG_TYPE View Process Log Type ALL (All)
BRIEF (Brief)
MILESTONE (Milestone
Only)
ERROR (Errors Only)
DEBUG (Debugs Only)

WORKSHEET_ACTION Worksheet Action APPROVE (Approve

Worksheet)
CREATE (Create Worksheet)
LOCK (Lock Worksheet)
REFRESH (Refresh
Worksheet)
REJECT (Reject Worksheet)
REMOVE (Remove
Worksheet)
SUBMIT (Submit Worksheet)
UNLOCK (Unlock
Worksheet)
WORKSHEET_STATUS Payment Worksheet Status APPROVED (Approved)
FAILED
LOCKED (Locked)
PROCESSING
SUBMITTED (Submitted)
UNPAID (Unpaid)
YES_NO Yes or No N (No)
Y (Yes)
YTD_GRAPH_TYPE YTD Graph Type A (All)
C (Achievement)
E (Earnings)
N (None)
P (Payment)
Lookups 10-51
11
Flexfields

• Flexfields
Flexfields
Flexfields are used in Oracle Incentive Compensation for classification of transactions,
in defining plan elements, and in setting up compensation plans. They are all optional.
Use a flexfield when you want to set up a additional input field on a page that is preset
with a recognizable name and a specific set of values from which to select. For example,
a field can be called Item Number, and be set up with particular values that you enter in
Oracle Forms. The built-in flexfields allow a small amount of custom formatting of a
page without programming.
Oracle Incentive Compensation uses descriptive flexfields, which provide customizable
expansion space on a page. There are three flexfields used in this release of Oracle
Incentive Compensation.
Flexfields Code
CN Commission Headers CN_COMMISSION_HEADERS_ALL
CN Compensation Plans CN_COMP_PLANS_ALL
CN Quotas CN_QUOTAS_ALL
The flexfields are enabled in three tables:

• CN Commission Headers
Oracle Incentive Compensation contains 100 numbered attributes that can be
customized for use with classification of transactions. These attributes are seeded
Flexfields 11-1
with the application.
• CN Compensation Plans
customized for use with defining compensation plans. These attributes are seeded
with the application. This flexfield appears on the Plan Design page.
• CN Quotas
customized for use with defining plan elements. These attributes are seeded with
the application. This flexfield appears on the Update Plan Element page.
When you display the context fields in the HTML application, the standard display is as
Context Value. The field names can be customized by logging into the Oracle Forms as
an Application Developer and using the Descriptive Flexfield Segments screen
(Flexfield > Descriptive > Segments). Or, you can eliminate the fields by not checking
the Displayed box. You can make the flexfield a required value. See the Oracle
Applications Flexfields Guide for information about setting up flexfields.

A
SQL Insert Statement for Credit Allocation
SQL INSERT STATEMENT FOR CREDIT ALLOCATION

In normal situations, you do not need to change this insert statement. It is only
necessary to change it if you are performing customizations.
1. Go to section or comment, which says == > " OIC CODE TO INSERT DATA INTO
JTF_TAE_1001_SC_TRANS GOES HERE"
2. Enter the following SQL script.
SQL Insert Statement for Credit Allocation A-1

Insert into JTF_TAE_1001_SC_TRANS (
source_id,
trans_object_type_id,
trans_object_id,
trans_detail_object_id, --PARTY SITE ID (TCA)
squal_num02, --ACCOUNT CODE (TCA)
squal_num04, --ACCOUNT HIERARCHY (TCA)
squal_char08, --AREA CODE
squal_char09, --CATEGORY CODE (TCA)
squal_char02, --CITY (AR)
squal_curc01, --CURRENCY CODE
squal_num06, --COMPANY ANNUAL REVENUE
squal_char07, --COUNTRY (AR)
squal_char03, --COUNTY (AR)
squal_num01, --PARTY_ID (TCA)
squal_fc01, --FIRST CHARACTER OF CUSTOMER NAME RANGE
squal_char01, --CUSTOMER NAME RANGE
squal_num10, --DUNS NUMBER (TCA)
squal_num05, --NUMBER OF EMPLOYEES
squal_char06, --POSTAL CODE
squal_char05, --PROVINCE (AR)
squal_num01, --REGISTRY ID (TCA)
squal_num03, --SALES PARTNER OF (TCA)
squal_char10, --SIC CODE (TCA)
squal_char04, --STATE (AR)
worker_id
)
SELECT -1001,
-1002,
comm_lines_api_id,
ATTRIBUTE1, --PARTY SITE ID (TCA)
ATTRIBUTE3, --ACCOUNT CODE (TCA)
ATTRIBUTE4, --ACCOUNT HIERARCHY (TCA)
ATTRIBUTE5, --AREA CODE
ATTRIBUTE6, --CATEGORY CODE (TCA)
ATTRIBUTE7, --CITY (AR)
ATTRIBUTE8, --CURRENCY CODE
ATTRIBUTE9, --COMPANY ANNUAL REVENUE
ATTRIBUTE10, --COUNTRY (AR)
ATTRIBUTE11, --COUNTY (AR)
ATTRIBUTE12, --PARTY_ID (TCA)
ATTRIBUTE13, --FIRST CHARACTER OF CUSTOMER NAME RANGE
ATTRIBUTE14, --CUSTOMER NAME RANGE
ATTRIBUTE15, --DUNS NUMBER (TCA)
ATTRIBUTE16, --NUMBER OF EMPLOYEES
ATTRIBUTE17, --POSTAL CODE
ATTRIBUTE18, --PROVINCE (AR)
ATTRIBUTE19, --REGISTRY ID (TCA)
ATTRIBUTE20, --SALES PARTNER OF (TCA)
ATTRIBUTE21, --SIC CODE (TCA)
ATTRIBUTE22, --STATE (AR)
1
FROM cn_comm_lines_api
WHERE process_batch_id in
(select process_audit_id from cn_process_audits where parent_
process_audit_id = x_conc_program_id);.
A-2 Oracle Incentive Compensation Implementation Guide

Index
column mapping, 5-8

A credit types
define, 4-3
account generation, 7-1
currency, 3-2
account generator, 7-2
API table, 5-10
Application Parameters, 4-1 D
dependencies
C mandatory, 2-1
calculation parameters
set up, 6-2 E
collect flag, 5-11 external table mapping, 5-3
Collection
configure tables and columns, 5-2 F
collection parameters
filtering, two methods, 5-11
set up, 5-1
filters, transaction, 5-11
collection query, 5-10
flexfields, 11-1
collections
collect flag, 5-11
G
collection query, 5-10
filters, 5-11 General Ledger
generate package, 5-11 accounting calendar, 3-2
header table, 5-5 General Ledger parameters
line table, 5-5 set up, 4-2
mapping, 5-8 General Parameters
notification query, 5-8 setup, 4-1
open, 5-4
test package name, 5-11 I
test status, 5-11 indirect mapping
transaction source, 5-5 types, 5-9, 5-9
user code blocks, 5-10 interval types
collection sources and mapping define, 4-3
define, 5-4
Index-1
K T
key column, 5-7 task sequence, implementation, 1-8
test generate, 5-11
L test package name, 5-11
test status, 5-11
ledger, define, 3-2
transaction source, 5-5
line table, 5-7
add to TRX TYPES lookup, 5-6
lookups, 10-1
information, 5-6
M
U
mapping
user code blocks, 5-10
direct, 5-9
indirect, 5-9
plan element to pay element, 7-3
N
notification query, 5-8
parameters, 5-7
O
open collections, 5-4
Oracle Order Management, 2-7
Oracle Payables, 2-4
Oracle Payroll, 2-6
Oracle Resource Manager, 2-2
P
periods, 3-2
period types, 3-1
plan element to pay element mapping, 7-3
profile options, 9-1
projected compensation, 2-8
R
Resource Manager, 2-1
S
source expression
contents, 5-8
source tables
identifying, 5-7
system parameters, 4-1
Index-2

Oracle® Incentive Compensation: Implementation Guide Release 12

Uploaded by

Document Informationclick to expand document information

Document Informationclick to expand document information

Copyright:

Available Formats

Oracle® Incentive Compensation: Implementation Guide Release 12

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: Implementation Guide Release 12

Uploaded by

Copyright:

Available Formats

Oracle® Incentive Compensation

Part No. B25388-04

Copyright © 1996, 2007, Oracle. All rights reserved.

Primary Author: Steven Schaefer

U.S. GOVERNMENT RIGHTS

Send Us Your Comments

2 Mandatory Dependencies and Integrations

3 General Ledger Setups

4 Application Parameter Setups

8 Credit Allocation Setups

A SQL Insert Statement for Credit Allocation

Oracle Incentive Compensation Implementation Guide, Release 12

• Oracle Incentive Compensation. If you have never used Oracle Incentive

The Oracle Incentive Compensation Implementation Guide contains the information

• Chapter 2 describes mandatory dependencies and integrations with other Oracle

• Chapter 4 covers Application Parameters.

• Chapter 6 describes Calculation setups.

• Chapter 7 talks about Payment setups.

• Chapter 8 contains setup steps for Credit Allocation, an optional feature.

• Chapter 10 presents the lookups used in Oracle Incentive Compensation, updated

• Chapter 11 contains a detailed listing of flexfields used in Oracle Incentive

• Appendix A provides a SQL insert statement for Credit Allocation.

• The Index makes it easy for users to find specific information.

TTY Access to Oracle Support Services

Accessibility of Code Examples in Documentation

Accessibility of Links to External Web Sites in Documentation

Related Information Sources

Do Not Use Database Tools to Modify Oracle Applications Data

Implementing Oracle Incentive Compensation

Oracle Incentive Compensation Basics

Responsibilities in the Compensation Process

1-2 Oracle Incentive Compensation Implementation Guide

The Oracle Incentive Compensation Process

1-4 Oracle Incentive Compensation Implementation Guide

Using the Configuration Workbench

Using the Notes Feature

1-6 Oracle Incentive Compensation Implementation Guide

Beginning The Implementation Process

Implementation Task Sequence

1-8 Oracle Incentive Compensation Implementation Guide

• Supplemental CRM Installation Steps Release 12

Standard Oracle Incentive Compensation Process

PERFORM MANDATORY Oracle Resource Manager and Oracle

PERFORM GENERAL LEDGER SETUPS Oracle General Ledger provides the

Set up General Parameters Select your type of currency conversion and

Set up General Ledger Parameters Confirm your setups in General Ledger,

Define Interval Settings Group predefined periods into intervals for

PERFORM COLLECTION SETUPS In this part of the Configuration Workbench

Set up Collection Parameters Set collection batch size, number of

Define External Table Mapping Optional. Join external tables to destination

Define Collection Sources and Mapping Configure seeded transaction sources or

Generate Collection Packages Define how you want collection to be

PERFORM CALCULATION SETUPS Specify how you want calculation to work

1-10 Oracle Incentive Compensation Implementation Guide

Define External Table Mappings Optional. Join external tables to destination

PERFORM PAYMENT SETUPS To define how you want the application to

Set up Payment Parameters Select integration with Oracle Payroll or