Incentive Compensation Profile Options

This topic describes profile options for incentive compensation.

Compensation managers can search for participants while adding paysheets to a payment batch. This profile option controls whether or not managers can search by role. A search by role can find several paysheets for one participant if the participant has several roles. When the profile is set to no, the search finds one participant per search and the role is hidden.

Profile Option

Name

Description

Default Setting

ORA_CN_SRCH_PARTIC_BY_ROLE

Search Participant by Role

Use role as a participant search criterion in the Payments work area. Set to No to remove Role as a searchable field and in the search results. Set to Yes to enable searching by role.

No

These profile options are set for you to batch credits for optimum processing time for calculation. You can make changes to these profile options.

Profile Option

Name

Description

Default Setting

ORA_CN_CNT_CRDTS

Count Credits for All Participants During Calculation

If set to Yes, then count the credits for each participant included in the calculation run. If set to No, then count credits for the participant with more compensation plans assigned in the calculation date range.

Yes

ORA_CN_CALC_PCT_USG

Percentage of Total Number of Parallel Processes for Calculation

Specify the percentage of total allowable parallel processes that can be used for calculation.

80

ORA_CN_MIN_CRDTS

Minimum Number of Credits for Each Batch

Specify the minimum number of credits to be included in each calculation batch.

10,000

ORA_CN_MAX_CRDTS

Maximum Number of Credits for Each Batch

Specify the maximum number of credits to be included in each calculation batch.

1,000,000

ORA_CN_PCT_USG

Percentage of Total Number of Parallel Processes for Crediting, Classification, or Rollup

Specify the percentage of your total allowable parallel processes to use for crediting, classification, or rollup.

80

ORA_CN_CCR_MIN_RECS

Minimum Number of Records for Each Batch

Specify the minimum number of records to be included in each crediting, classification, or rollup batch. The batching logic calculates the number of records per batch based on the number of records being processed and the number of processes allowed. If this is less than the value mentioned in this profile option, it will use the value mentioned in this profile option, else it will disregard it.

10000

ORA_CN_CCR_MAX_RECS

Maximum Number of Records for Each Batch

Specify the maximum number of records to be included in each crediting, classification, or rollup batch. The batching logic calculates the number of records per batch based on the number of records being processed and the number of processes allowed. If this is more than the value mentioned in this profile option, it will use the value mentioned in this profile option, else it will disregard it.

1000000

This profile option controls the number of batches used by the Revert Transactions process. You can change the profile value. If you leave it set to 0, the Revert Transactions process determines the number of batches dynamically based on the volume of data for that specific run and the available workers in the environment. This is the recommended setting, but you can set the number of batches.

Profile Name User Profile Name Description Default Value
ORA_CN_BATCHES_REVERT Number of Batches for Revert Transactions Fixed number of batches to be used by the Revert Transactions process. 0

This profile option can be set for troubleshooting, but should be turned off again when you complete your analysis.

Profile Option

Name

Description

Default Setting

CN_DEBUG

Enable Debug Mode

Set to yes to write errors to the CN_PROCESS_AUDIT_LINES table for troubleshooting.

No

This profile option applies if you create credits manually using the UI or through import. It doesn't apply to transaction credits created during the crediting process from imported transactions. The profile applies if you use the direct credit rule hierarchy for roll up processing. Change this profile option to No if you don't want the roll up process to create rollup (also called indirect) credits from the credits you created or imported.

Profile Option

Name

Description

Default Setting

ORA_CN_ENABLE_CREDIT_ROLLUP

Credit Hierarchy- Based Roll Up for Manual and Imported Credits Enabled

Enable indirect crediting for manually entered and imported credits when using the direct credit rule hierarchy for roll up.

Yes

The participant detail import allows bulk import of participant detail records. Participant detail records serve a number of functions. One such function is as the reference point calculation uses to determine a participant's currency. Another validation ensures that whenever a participant is assigned to a compensation plan, a corresponding participant detail record exists that covers the full date range of the plan assignment. Validations also ensure that records are contiguous and don't overlap. If this profile is set to no, validations are conducted at the row level, and the file import automatically creates records to fill gaps in effective dates. Corrections can then be made in the UI where all changes are validated as a whole. Setting this profile to yes changes the run mode so that validations are done at a file level. You can correct multiple records using the import. Automatic gap rows aren't created and instead rows are ignored and a warning given for date range issues.

Profile Option

Name

Description

Default Setting

ORA_CN_SRP_DTLS_MULT_VLD

Enable Multiple Participant Detail Record Validation for Participant Detail File Import

If set to Yes, participant detail import validates records based on all file rows and won’t create rows to fill date range gaps. If set to No, records are validated individually.

No