Document 1248974.

https://support.oracle.com/epmos/faces/ui/km/DocumentDisplay.jspx?_...

PowerView is Off Search Knowledge Base

amresh

(0)

Contact Us

Help

Dashboard

Knowledge

Service Requests

Advanced

How To Create A Manual Transaction and Pay Commission In Oracle Incentive Compensation Release 12 [ID 1248974.1]
Modified: Feb 15, 2012 Type: BULLETIN Status: PUBLISHED Priority: 1 Comments (0)

To Bottom

In this Document Purpose Scope and Application How To Create A Manual Transaction and Pay Commission In Oracle Incentive Compensation Release 12 Create Manual Transactions Load Transaction Calculate Compensation Submit Payment Batch TROUBLESHOOTING Community Discussions

Applies to:
Oracle Incentive Compensation - Version: 12.0.0 to 12.1.3 - Release: 12.0 to 12.1 Information in this document applies to any platform. checked for relevance 17-Aug-2011

Purpose
The purpose of this document is to go through a simple testcase in Oracle Incentive Compensation of creating a manual transaction and go through the steps required in order to then pay commission. This will not cover importing transactions from Accounts Receivables (AR), Order Management (OM) or an external source. This will be covered in a separate document.

Scope and Application

This note is intended for Incentive Compensation Implementers and Administrators.

How To Create A Manual Transaction and Pay Commission In Oracle Incentive Compensation Release 12

Create Manual Transactions

(R) Compensation Manager (N) Tasks Maintain Transactions Create Transaction

1 of 6

4/3/2013 4:24 PM

Document 1248974.1

https://support.oracle.com/epmos/faces/ui/km/DocumentDisplay.jspx?_...

As mentioned in Note 1239863.1 Oracle Incentive Compensation needs to know where to collect transactions on which commission is to be paid from. In the example above the attribute AMC ATR26 was created against the table cn_commission_headers and defined in the classification rules and associated to the classification ruleset. This will associate the transaction with a compensation plan and allow a compensation amount to be paid when the transaction is calculated

Table Involved CN_COMM_LINES_API_ALL will be populated when either a manual transaction is created or Collection is run. (Collection pulls through from Receivables, Order Management or external source) To confirm that the table is successfully populated the following sql can be run to confirm:

1. First remember to set Multiorg environment: ---------------------------------------------begin MO_GLOBAL.set_policy_context('S', 2541); -- 2541 is example of org_id end; 2. Obtain salesrep_id: ---------------------select org_id, SALESREP_ID, name from jtf_rs_salesreps WHERE name like &name%'; 3. Confirm that transaction is loaded into table cn_comm_lines_api_all: ----------------------------------------------------------------------select * from cn_comm_lines_api_all where salesrep_id = &salesrep_id and processed_period_id = &period_id;
An example of data returned:

Load Transaction
After transactions are collected and adjusted, they must be loaded into Oracle Incentive Compensation tables prior to running the calculation and payment processes. (R) Compensation Manager (N) Tasks Load Transactions

You can choose to run load which will run online or schedule load which will kick of a concurrent request

Table Involved CN_COMMISSION_HEADERS will be populated once the transactions have been loaded. To confirm that the table is successfully populated the following sql can be run to confirm:

select * from cn_commission_headers_all Where direct_salesrep_id = &salesrep_id and processed_period_id = &period_id;

2 of 6

4/3/2013 4:24 PM

Document 1248974.1

https://support.oracle.com/epmos/faces/ui/km/DocumentDisplay.jspx?_...

An example of data returned:

Calculate Compensation
You can calculate compensation for all resources who have valid compensation plans, for all resources in the notify log file, or for resources you specify. (R) Compensation Manager (N) Tasks Calculate Compensation

You can choose to run load which will run online or schedule load which will kick of a concurrent request Either select a specific resource for which to run calculation or alternatively run for all resources

Incremental Calculation Incremental Calculation will only calculate newly added transactions and transactions that are affected by the new transactions. This option also calculates the compensation for resources who are affected by events that happened since the previous calculation. These events will include changes such as role assignment changing, updates to the compensation plan and new transactions created. Incremental Calculation does not recalculate transactions which have a status of XCALC as these transactions will already have gone through classification and rollup as part of the loading phase of Calculation. Table Involved CN_COMMISSION_LINES_ALL will be populated once calculation has been run. The table will contain information such as the commission amount, commission rate and posting status. To confirm that the table is successfully populated the following sql can be run to confirm:

select * from cn_commission_lines_all where direct_salesrep_id = &salesrep_id and processed_period_id = &period_id; You can also check the quota tables for cumulated data such PTD = Period_to_date, ITD = Interval To date, etc select name, quota_id from cn_quotas_all where name = '&plan_element_name'; You can then drill down specifically into a period for individual salesrep or for all salesreps for the period: SELECT * FROM cn_srp_period_quotas_all WHERE quota_id = &quota_id and period_id = &period_id -- and salesrep_id = &salesrep_id;
An example of data returned:

3 of 6

4/3/2013 4:24 PM

Document 1248974.1

https://support.oracle.com/epmos/faces/ui/km/DocumentDisplay.jspx?_...

The following screenshot shows the transaction with a status of calculated and commission amount payable

Submit Payment Batch

For detailed information on how to create the Pay Analyst/Manager and Payment setup steps refer to Note 1233331.1 Payment Setup Steps For Oracle Incentive Compensation Release 12. In order to be paid, a resource must be created in Resource Manager, be assigned to a pay group, and be assigned a compensation plan. (R) Compensation Manager (N) Tasks Maintain Payment Batch Create

You can only have one open payment batch per pay group at any one time. You will not be allowed to create a new payment batch until the status of any previous payment batches for the pay group is Paid. You can only create payment batches for the last period paid or a future period. After you have paid a payment batch for one period you cannot go back to the previous month to create a payment batch for the pay group.

In order to be able to pay the payment batch the individual paysheets need to be reviewed and approved: Select Payment Batch Click on Paysheet Details Select Paysheets Select Lock Go Select Paysheets Select Submit Go Select Paysheets Select Approve Go Pay payment batch

Tables Involved CN_PAYRUNS_ALL will provide information such as payrun_id, pay_date and status.

4 of 6

4/3/2013 4:24 PM

Document 1248974.1

https://support.oracle.com/epmos/faces/ui/km/DocumentDisplay.jspx?_...

To confirm that the table is successfully populated the following sql can be run to confirm:

1. First obtain the pay_group_id: select pay_group_id, name, start_date, period_type, period_set_name from cn_pay_groups_all where name like '&name of paygroup'; 2. Confirm payrun has been paid successfully select payrun_id, name, pay_date, pay_period_id, status from cn_payruns_all where pay_group_id = &pay_group_id
An example of data returned:

CN_PAYMENT_TRANSACTIONS_ALL - stores the details for each payment worksheet. The records that are created in this table are dependent on the value of the profile Pay by Transaction. When this profile is set to Y(es), the data in this table is populated at the same granularity that it is calculated. When the profile is set to N, the data in this table is populated at the plan element level

select pay_period_id, payrun_id, paid_flag, sum(amount) from cn_payment_transactions_all WHERE credited_salesrep_id = &salesrep_id AND credit_type_id = -1000 AND incentive_type_code IN ('COMMISSION', 'BONUS') group by pay_period_id, payrun_id, paid_flag order by pay_period_id
An example of data returned:

CN_PAYMENT_WORKSHEETS_ALL - contains information about a payment made to a salesperson

select payrun_id, pmt_amount_calc, current_earnings_due, current_earnings, bb_pmt_recovery_plans, creation_date FROM cn_payment_worksheets_all WHERE salesrep = &salesrep_id and quota_id is not null order by payrun_id
An example of data returned:

TROUBLESHOOTING
Note 862471.1Data collection script to resolve payment worksheet error

Data collection script to resolve payment worksheet error. (Doc ID 862471.1)

Community Discussions
Still have questions? Use the live My Oracle Support Incentive Compensation Community window below, to search for similar discussions or start a new discussion on this subject.

5 of 6

4/3/2013 4:24 PM

Document 1248974.1

https://support.oracle.com/epmos/faces/ui/km/DocumentDisplay.jspx?_...

Welcome, User533015 | My Profile Main Home Discussions Documents Private Messages (0) Contacts Tags Profile Subscriptions Off

What do you want to do? My Communities Find a Community

Create a Community Post

Upload/Write a Reference Document Popular Discussions Partitioning of OIC Tables (189 views) OIC Implementation (176 views) Failed population for more than one sale (141 views) Welcome to your Sales Compensation c (122 views) Regarding Product Define (111 views) OIC integration with Oracle Payable (103 views) Info required for CN tables (101 views) How to set up a compensation plan in In (95 views) Nothing is being collected from Receiva (92 views)

Sales Compensation News & Announcements Welcome to the Oracle Incentive Compensation Product Family Community

*My Oracle Support Community Suggestions Health Check Reviews Oracle Auto Service Request Patch Reviews - General Support Training Using My Oracle Support Application Integration Architecture Cross Industry Pre-Built Integrations Foundation Pack Industry Specific Pre-Built Integrations Patch Reviews - AIA Business Intelligence BI Patch Reviews Certifications for BI OBIA Subscribe to this Community

The purpose of the Service community is to connect people and facilitate the exchange of information, ideas, best practices, and breaking news around the following products: Oracle Incentive Compensation Oracle Incentive Compensation Data Analytics For Oracle Data Integrator If you are new to our Communities take a moment to review the Getting Started section under the Main Home page. There you can find information such as Training Available for My Oracle Support Community, New Member Orientation,Rules of Conduct and Community General FAQ. Take some time to review the following sections below: News and Announcements, All Community Discussions', 'All Community Documents', 'Tips and Tricks', 'White Papers' and 'Webcasts'.

Sales Compensation Webcasts Top Participants Community active users within last 90 days: 20 Pro 314 points / 592 total AmandaMc - Oracle Sales Compensation Featured Discussions Displaying items 1 - 3 out of 6 (page 1 of 2) Rating Subject Updates to E-Business Suite 11.5.10 Sustaining Support < Prev Next > Author

Collecting Order data from Invoice data (88 views)

Popular Documents Oracle Incentive Compensation Standar (65 views) PDF of Make the Most of Your Support D

Related
Products
Oracle E-Business Suite > Sales & Marketing > Incentive Compensation > Oracle Incentive Compensation > Support Codes > Payment

Keywords
CN_COMM_LINES_API_ALL; DYNAMIC ADV FEATURES; INCREMENTAL CALCULATION; PAYMENT; SETUP; TESTCASE; WORKSHEET Back to Top
Copyright (c) 2013, Oracle. All rights reserved. Legal Notices and Terms of Use Privacy Statement

6 of 6

4/3/2013 4:24 PM