Implementation Considerations for Individual Compensation Processes

Here are the considerations for Administer Compensation, Individual Compensation, and Personal Compensation processes.

You can typically use field value defaulting and validation in these cases.

Default when date such that awards can be created after 1st of next quarter by employees only.
Validate that awards can be created after 1st of next quarter by employees only.
Validate that certain plans are excluded for line managers.
Validate when date such that it's in the current fiscal year (1 Apr to 31 Mar).
Validate spot bonus is effective either on 01 Apr 2024 or 01 Oct 2024.
Validate new hire bonus doesn't exceed $3000.
Validate car allowance increase is below or equal to 10%.
Validates new awards starts on or before 17th of a month.
Validate that only one award proposal is submitted at a time.
Validate bus and taxi reimbursement aren't claimed together.
Validate that bonus can be allocated once in 6 months only.
Advanced expressions working on Global HR and Recruiting pages need to be updated somewhat to work on the Administer Compensation, Individual Compensation, and Personal Compensation pages.

This table lists the supported attributes, exceptions, and the implementation recommendations for these pages:

My Client Groups > Administer Compensation
My Client Groups > Individual Compensation
My Team > Individual Compensation
Me > Personal Contribution

In the Conditions to Default Values	To Default Field Values	In the Condition to Validate Values	To Validate Field Values	Implementation Guidelines
User Roles Legal Employer Business Unit Country Assignment attributes including Assignment Status Bargaining Unit Business Unit Department FTE Grade Grade Code Grade Ladder Hire Date Hourly or Salaried Job* Job Code Job Family* Job Function* LDG* Legal Employer Location Next Payroll Start Date Payroll Start Date Person Type* Position* Position Budget Value* Position Code Position Standard Working Hours* Primary Work Relationship Termination Date Working Hours Working Hours Frequency *Can affect performance	Action Date Exclude Plans Exclude Options	For When Section User Roles Legal Employer Business Unit Country Action Date For Compensation Section User Roles Legal Employer Business Unit Country Plan Option Start Date End Date Value Currency Legal Entity Create or Edit Current Allocations Prior Allocations	NA	Can default Action Date only and validate individual compensation section data. You can validate at the record or section level. Record level validations are triggered on clicking Save in the edit panel drawer. Section Level validation are triggered on clicking Continue in the process All the current allocation records will be available in the Current Allocations attribute You can iterate through the records and create rule on the above mentioned record level fields Section level rules can be written only using Advanced Expression Mode Plan LOV and Plan – Option LOV in Business Rules is secured by the Individual Compensation Plan functional privilege: Define Variable Compensation Plan for Individual Compensation (CMP_DEFINE_VARIABLE_COMPENSATION_PLAN_FOR_ INDIVIDUAL_COMPENSATION). This is required for business rule design time users to view the values in Plan LOV, Plan – Option LOV. If you don't have this security, you won't see the values in the LOV. Initial Value is available for individual compensation fields to compare old and new values. Current Allocations can be accessed while creating validation using Advanced Expression only. When the flow is launched, the assignment data is fetched based on the effective date selected in Person Search. If effective date isn't selected, data will be fetched as of application date. Rules written for When section will always be evaluated on the effective date selected in Person Search / application date. If Action Date is changed in When section, rules written for Compensation section will be evaluated based on the assignment data effective as of action date. Prior Allocations: Similar to Current Allocations, prior allocations field is an array and user can iterate through the prior allocation records to write rule conditions. Because prior allocation data is constant, it will be available at both section and record level validations. Only when rules are written on Prior Allocations, the fragment loads prior allocation data and makes it available to the BR engine. Rules on Prior Allocations can be written only in Advanced Expression mode.

In the Conditions to Default Values

To Default Field Values

In the Condition to Validate Values

To Validate Field Values

Implementation Guidelines

User Roles
Legal Employer
Business Unit
Country
Assignment attributes including
- Assignment Status
- Bargaining Unit
- Business Unit
- Department
- FTE
- Grade
- Grade Code
- Grade Ladder
- Hire Date
- Hourly or Salaried
- Job*
- Job Code
- Job Family*
- Job Function*
- LDG*
- Legal Employer
- Location
- Next Payroll Start Date
- Payroll Start Date
- Person Type*
- Position*
- Position Budget Value*
- Position Code
- Position Standard Working Hours*
- Primary Work Relationship
- Termination Date
- Working Hours
- Working Hours Frequency

*Can affect performance

Action Date
Exclude Plans
Exclude Options

For When Section

User Roles
Legal Employer
Business Unit
Country
Action Date

For Compensation Section

User Roles
Legal Employer
Business Unit
Country
Plan
Option
Start Date
End Date
Value
Currency
Legal Entity
Create or Edit
Current Allocations
Prior Allocations

Can default Action Date only and validate individual compensation section data.
You can validate at the record or section level.
- Record level validations are triggered on clicking Save in the edit panel drawer.
- Section Level validation are triggered on clicking Continue in the process
- All the current allocation records will be available in the Current Allocations attribute
- You can iterate through the records and create rule on the above mentioned record level fields
- Section level rules can be written only using Advanced Expression Mode
Plan LOV and Plan – Option LOV in Business Rules is secured by the Individual Compensation Plan functional privilege: Define Variable Compensation Plan for Individual Compensation (CMP_DEFINE_VARIABLE_COMPENSATION_PLAN_FOR_ INDIVIDUAL_COMPENSATION). This is required for business rule design time users to view the values in Plan LOV, Plan – Option LOV. If you don't have this security, you won't see the values in the LOV.
Initial Value is available for individual compensation fields to compare old and new values.
Current Allocations can be accessed while creating validation using Advanced Expression only.
When the flow is launched, the assignment data is fetched based on the effective date selected in Person Search. If effective date isn't selected, data will be fetched as of application date.
Rules written for When section will always be evaluated on the effective date selected in Person Search / application date.
If Action Date is changed in When section, rules written for Compensation section will be evaluated based on the assignment data effective as of action date.
Prior Allocations:
1. Similar to Current Allocations, prior allocations field is an array and user can iterate through the prior allocation records to write rule conditions.
2. Because prior allocation data is constant, it will be available at both section and record level validations.
3. Only when rules are written on Prior Allocations, the fragment loads prior allocation data and makes it available to the BR engine.
4. Rules on Prior Allocations can be written only in Advanced Expression mode.

Field Details

Field	Field Accessor	Type	Comments
Action Date	`$fields.individualCompensationDetails.EffectiveDate.$value()`
Record Level Attributes
Plan	`$fields.individualCompensationDetails.PlanId.$value()`	Number	PlanId selected using Plan LOV which shows Plan Name
Plan Option	`$fields.individualCompensationDetails.ComponentId.$value()`	Number	OptionId selected using Option LOV which shows values in the format <Plan Name> - <Option Name>
Start Date	`$fields.individualCompensationDetails.EffectiveStartDate.$value()`	String	Allocation start date as string (Format: yyyy-MM-dd) Requires Advanced Expression mode for date comparison.
End Date	`$fields.individualCompensationDetails.EffectiveEndDate.$value()`	String	Allocation end date as string (Format: yyyy-MM-dd) Requires Advanced Expression mode for date comparison.
Value	`$fields.individualCompensationDetails.ValueString.$value()`	String	Primary input value as string. Requires Advanced Expression mode for nonstring primary input value. For numeric field, the value should be type-casted to Number for arithmetic operations. Similarly, for date field, the value should be type-casted to Date for date comparisons.
Currency	`$fields.individualCompensationDetails.DisplayCurrency.$value()`	String	Currency for monetary primary input value
Legal Entity	`$fields.individualCompensationDetails.LegalEntityId.$value()`	Number	LegalEntityId selected using Legal Entity LOV which shows LE Name
Create or Edit	`$fields.individualCompensationDetails.Mode.$value()`	String	Mode attribute is to identify whether the record is newly created or an existing record.
Section Level Attributes
Current Allocations	`$fields.individualCompensationDetails.CurrentAllocations.$value()`	Array	Object Structure `[ { "PlanId": "string", "ComponentId": "string", "EffectiveStartDate": "string", "EffectiveEndDate": "string", "ValueString": "string", "DisplayCurrency": "string", "LegalEntityId": "string", "Mode": "string" } ]`
Prior Allocations	`$fields.individualCompensationDetails.PriorAllocations.$value()`	Array	Object Structure `[ { "PlanId": "string", "ComponentId": "string", "EffectiveStartDate": "string", "EffectiveEndDate": "string", "ValueString": "string", "DisplayCurrency": "string", "LegalEntityId": "string", "Mode": "string" } ]`