Your client wants to restrict entry into the Lump Sum field to only members of the reward team. How can you achieve this?

• A. Update guidelines to put a hard stop on the Lump Sum field set all of the guideline values to 0.
• B. Set the Lump Sum field to read-only to prevent planners from using it.
• C. Use mass actions through the Executive Review.
• D. Use field-based permissions on the Lump Sum field a permission group of named individuals.

설명: (Fast2test 회원만 볼 수 있음)

Your non-EC customer wants only users in Pay Grade 1 2 to be ineligible for Lump Sum; Pay Grades 3 through 9 are eligible.
What can you do to fulfill this requirement?
Note: There are 3 correct answers to this question.

• A. 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.
• B. 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.
• C. 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.
• D. 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.
• E. 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.

Your customer has the requirement that employees with low performance ratings have a different text in their statement than those with high performance ratings.
How can you accomplish this?

• A. Use conditional text sections in the statement editor.
• B. Create multiple statement templates use groups.
• C. Use the suppress statement function.
• D. Use two compensation worksheet templates.

설명: (Fast2test 회원만 볼 수 있음)

In an EC-integrated compensation worksheet, what are some of the reasons you might include a lookup table in your configuration? Note: There are 3 correct answers to this question.

• A. Converting money values from functional to local currency
• B. Holding previous year's salary by Employee ID
• C. Converting a code into its text equivalent for display
• D. Determining appropriate car allowance by grade
• E. Providing budget percentage by country

You have configured a worksheet for a client that uses the following formula in a custom column of type Money: (curSalary lookup("budget_table",customCountry,1))/100.
The lookup table "budget_table" is configured with one input one output. There are three rows in the table:
*USA = 5
*GBR = 3
**=2
When the worksheet loads, the column displays correctly, but when a merit value is changed, it switches to N
/A for the employee. What could be done to fix this behavior?

• A. Surround the curSalary with the toString function.
• B. Remove the extra parentheses.
• C. Change the column to be of the Amount type.
• D. Surround the lookup function with the toNumber function.

설명: (Fast2test 회원만 볼 수 있음)