This chapter covers the following topics:
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 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 for the procedure.
To set up account generation, you must log in to the Plan Administrator responsibility.
Navigation
Oracle Payables Integration > Account Generation Rule Sets
Steps
Click Create. Be sure you have selected the correct Operating Unit.
Give the rule set an appropriate name and dates that reflect the period of time that you will be using it.
Open the new rule set and click the Update icon.
Click the Create Child icon next to the parent rule to begin building the Account Generation rule set.
Enter an appropriate name for the child rule and select Expense and Liability account code names from the lists of values.
Click Apply.
Click the Update icon for the new rule.
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.
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.
Click Apply to save the rule.
Add rules in the rules hierarchy as needed.
Return to the Account Generation page, select the new rule set, and click Synchronize.
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.
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, 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
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 |
| 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.