C_THR87_2405 SAP Certified Associate - Implementation Consultant - SAP SuccessFactors Variable Pay Question and Answers

Base x business performance x individual performance

Base x business performance x team performance x individual performance

Base x business performance

Base x (business performance + team performance + individual performance)

Base x (business performance + individual performance)

Use an MDF rule instead of importing eligibility rules.

Flag employees in the UDF as TRUE in COMPENSATION_ELIGIBLE.

Create a rule in Manager Form Eligibility to include employees.

Add employees to the history data file.

All bonus plans must have equally weighted business goals.

Business goal weights must be created first, before bonus plans are created.

Goals are uniquely weighted based on the bonus plan they are assigned to.

Goal weights are required to equal 100% for each bonus plan.

dfid1

ifid1

vfid5

ffid1

Use the correct performance management form template.

Use the user ID of each employee in the business goals file.

Use the Manage Employee grouping.

Use a common field value for all employees in the employee history file.

Employee History Overlaps report

Employee History Gaps report

Employee History report

Bonus Payout Details report

Bonus plan file

Business goals file

Business goal weights file

Design Worksheet

Export the rating from the US performance forms then load ratings for all eligible employees into the Overall Performance background element of the Employee Profile.

Import the German ratings into the Overall Performance background element of the Employee Profile. The US ratings remain in the performance forms.

Export the rating from the US performance forms then load ratings for all eligible employees into a lookup table.

Create a specific performance form template for the German employees and have the customer load their ratings into it.

Division

Subtraction

Multiplication

Addition

Change field groups.

Relabel employee history fields.

Create custom fields.

Deactivate form sections.

Use bonus plan caps.

Use guidelines where the maximum is set to 200%.

Use a bonus plan multiplier of 200%.

Use gates on business goals.

PM form start date >= Assignment end date. Assignment start date <= PM form start date

PM form start date <= Assignment start date. Assignment start date >= PM form end date

PM form start date <= Assignment end date. Assignment start date <= PM form end date

PM form start date <= Assignment start date. PM form end date <= Assignment end date

The date published transactions are effective in Employee Central

The date the system uses to pull data from Employee Central

The date the program ends

The date the program begins

The fields use a lookup table to derive the data based on conditional logic and are read-only.

The fields use a custom calculation and are read-only.

The fields are mapped to import keys uploaded within the UDF and are read-only.

The fields are mapped to import keys uploaded within the UDF and are editable.

One variable pay template with the bonus start date November 1 and end date October 31, and the bonus plan multiplier set to 25%

One variable pay template with the bonus start date November 1 and end date October 31; employee history is loaded with four records per employee (one per quarter) and bonus paid in fullon October 31

Four variable pay templates, with the bonus start and end dates aligned with the customer's dates and employee history to match

Four variable pay templates, with the bonus start and end dates aligned with "traditional" quarter dates and custom columns in the employee history to display the customer's dates

The customer is using a different bonus calculation formula.

The customer is using a different plan period date range.

The customer is using different eligibility rules.

The customer has some employees in Employee Central and others in an external system.

The customer is using a different route map.

The plan template name

The background element name

The variable pay objective plan ID

The background type ID

Business goal performance

Bonus payout

Employee history gaps

Employee history overlaps

Dates later than program dates

Dates should NOT be entered

Dates equal to the program dates

Dates earlier than program dates

Rounds proration to a monthly value

Changes start and/or end date used in BonusCalculation

Forces proration to have X decimal places, where X is configurable

Allows for the use of "point in time" salary calculations

Change in business goal name

Change in eligibility rule criteria

Update in an employee’s assignment date

Update in bonus cap