C_THR86_2405 SAP Certified Associate - Implementation Consultant - SAP SuccessFactors Compensation Questions and Answers

Executive Review Export Permissions

Report Permissions

Executive Review Edit Permissions

Compensation Management Permissions

4

2

3

There is no limit on custom columns

The Rollup Report provides a summary of compensation entries budget information.

The Standard, Compensation, Rollup Hierarchies are all supported.

Custom Columns with the "Show Totals" attribute selected are shown.

The Rollup Report is based on the current hierarchy not that at form creation.

Enabling the Rollup Report for End-Users requires a specific tag in the XML.

By exporting troubleshooting information found on the Define Planners screen

By using the Check Tool

By changing the Method of Planner to Compensation Manager Hierarchy

By using the Rollup Hierarchy report

Guideline is displayed as 4-6%

•Total Increase is $500

Guideline is displayed as 4-6%

•Total Increase is $1,000

Guideline is displayed as 2-3%

•Total Increase is $500

Guideline is displayed as 2-3%

•Total Increase is $1,000

Ad Hoc report

Executive Review

Story reports

Aggregate export

Process Setup → Manager Planning → Next Level Manager Review → Final Review → Complete

Manager Planning → Next Level Manager Review → Compensation Admin Review → HR Manager Planning → Complete

Process Setup Manager Planning → Next Level Manager Review → Third Level Manager Review → Complete

Manager Planning → Next Level Manager Review → HR Manager Planning → Complete

The new pay grade is displayed.

The employee becomes ineligible.

The pay grade remains the same as it was when the forms were created.

New forms need to be created because an error will be shown.

An error message when planners enter a promotion without changing pay grade

A warning message when the budget is exceeded

An error message when adjustments are entered in two different fields

An error message when the maximum guideline is exceeded

Create a custom editable Money field. In the formula to calculate the final salary, use the dateDiff() function to determine if the custom column can override the calculated value.

Create a custom read-only Money field change read-only to No on the correct date.

Create a custom editable Money field use custom validation to check that values are NOT entered until the correct date.

Create a custom editable Money field with field-based permissions set to read-only. Change the permissions to editable on the correct date.

Create a read-only string field make it reportable.

Create an editable string field make it reportable.

Create an editable string field with enumerated values.

Create a read-only string field make it reloadable.

Create two different templates use eligibility rules to ensure employees appear on the correct one.

Ensure the Used for Comp Planning flag of the pay components is set to Comp do NOT map to a specific pay component ID in the worksheet.

Create two custom columns map each to the pay components. Use a third custom column to display whichever is non-zero.

Create a pay component group that includes both pay components use that for the planning.

Start with all employees are eligible. In the UDF, set the LUMPSUM ELIGIBLE field to FALSE for Grades 1 2, TRUE for Grades 3 through 9.

Start with all employees are ineligible. Using the legacy eligibility rules engine, create a rule condition that goes through the eligible Pay Grades makes them eligible for the Lump Sum field.

Start with all employees are eligible. Using the legacy eligibility rules engine, create a rule condition that makes the Pay Grades 1 2 ineligible for the Lump Sum field.

Start with all employees are ineligible. Using the legacy eligibility rules engine, create a rule condition that makes the Pay Grades 1 2 ineligible for the Lump Sum field.

Start with all employees are eligible. Using the legacy eligibility rules engine, create a rule condition that makes the Pay Grades 3 through 9 eligible for the Lump Sum field.

You can hide the Lump Sum column on the compensation worksheet using Field-Based Permissions. If the column is hidden on the worksheet, it won't appear on the statement.

You cannot do this with a single statement template; a second template must be created to include this item statement groups used to assign the templates appropriately.

You can include the Lump Sum item in the statement template put a disclaimer in the signature section alerting non-sales employees that that item pertains only to sales employees.

You can include the Lump Sum item in the statement template set a condition on its display so that it will only be shown if it is greater than 0.

Create a lookup table that contains the different dates that uses country as an input.

•Create a custom date column that reads from the lookup table based on employee country.

•Map the column ID of the custom date column to the "start-date" of the pay component in the XML.

Create a lookup table that contains the different dates that uses country as an input.

•Map the lookup table name to the "start-date" of the pay component in the XML.

On the Employee Central Settings screen in Compensation Home, set the Effective Date to be that of the largest country.

•Use the Publish Selected Employees in Employee Central to publish the data for this country.

•Manually modify the effective date to be that of the next country publish the data for them. Repeat for all countries.

Enter the effective date for the largest country in the Employee Central Settings screen.

•Publish the results of the planning for all countries.

•Manually modify the effective dates of the resulting EC data for the smaller countries.

9500

9570

9000

9600

Use reporting Executive Review for reviewing trends aggregate budgets.

Only include those that would alter a decision, not simply review.

Use a Signature step so the employee is aware of the decisions once the form is marked as "Complete".

Use the "Get Feedback" function to allow people outside the hierarchy to comment on the decisions.

In Display Settings use min-max

•Hard Limit: No

•High/Low Action: Allow

In Display Settings use min-max

•Hard Limit: Yes

•High/Low Action: Allow

In Display Settings use min-max

•Hard Limit: No

•High/Low Action: Warn

In Display Settings use low-high

•Hard Limit: Yes

•High/Low Action: Allow

Enable a hard limit stop for the merit guideline in Admin Center.

•Set the maximum value to 10 for all guideline formulas.

Create a guideline rule with the High/Low Action option set to Allow in Admin Center.

•Define each guideline formula with a default value of 10.

Enable a hard limit stop for the merit guideline in Admin Center.

•Set the maximum value to 0.10 for all guideline formulas.

Set the guideline pattern to be low-high.

•Set the high value for all guidelines to be 10.

Map TC to the standard Current Salary field.

•Use the Merit column for the TC update.

•Use the finSalary field some custom columns to calculate the components publish those back to EC.

Map TC to the standard Current Salary field.

•Use the Merit column for the TC update.

•Publish the finSalary value back to the pay component group in EC have business rules split the sum into the components.

Map TC to the standard Current Salary field.

•Use the Merit column for the TC update.

•Extract the new TC with a report manually create import files to update EC.

Map SALARY to the standard Current Salary field TC to meritTarget.

•Use merit to update the TC use custom fields to allow planners to update the allowances.

•Publish each component back separately.

toNumber(lookup("2018_BudgetPool", custom Country,customStatus,1))"'curSalary

toNumber(lookup("2018_BudgetPool,custom Country, customStatus, Adjustment))*curSalary

toNumber(lookup("2018_BudgetPool", custom Country.customStatus,2))"'curSalary

toNumber(lookup("2018_BudgetPool", custom Country,customStatus,adjustment))"curSalary