SAP C_THR70_2404 SAP Certified Associate - SAP SuccessFactors Incentive Management Exam Practice Test

In SAP Commissions, go to the Users workspace and create a new user, then assign the user to the Comp_Admins Business Unit.

In Sales Performance Home, go to User Administration and create a new internal user, then assign the user to the Comp_Admins role.

In SAP Commissions, go to the Users workspace and create a new user, then assign the user to the Comp_Admins role.

In Sales Performance Home, go to User Administration and create a new admin user, then assign the user to the Comp_Admins role.

Keep the same name of a title over time.

Assign a compensation plan to a title.

Delete a title when it is no longer in use.

Assign the same name to both titles and positions.

Position Groups

Earning Codes

Event Types

Earning Groups

The assignment of a participant to a position for a period of time.

An employee or external entity who receives incentive compensation.

An entity who is a user in SAP Commissions.

A unique job role in an organization.

Bonus incentive rule

Secondary measurement rule

Per credit incentive rule

Indirect credit rule

Default View Data

Payment Threshold

Enable Processing Units

Prompt Settings

Default Business Unit

In the Relationships workspace, you can create additional roll types and relationships.

Companies use roll relationships to roll deposits from one position to another.

In the Relationships workspace, you CANNOT delete roll types.

As you designate a manager on a position record in the Positions workspace, SAP Commissions creates a reporting relationship by default.

A roll relationship is an association of two positions used by SAP Commissions to process rolledvalues.

In Sales Performance Home, modify the Data Protection policy under Global Settings.

In SAP Commissions, modify the purge settings under System Preferences.

In SAP Commissions, modify the Data Protection policy under System Preferences.

In Sales Performance Home, modify the Data Privacy policy under General Settings.

The amount of incentive earnings to deposit

The aggregation of credits from transactions

The period to make the deposit

The account to deposit into

It is the processing engine that performs calculations.

A schedule of recurring pipeline runs can be configured in the user interface.

It can generate payments, but NOT balances.

It requires a separate process to populate dashboards.

Once a Variable has been created, the Variable's type CANNOT be changed.

Variable assignments made at the position level supersede assignments made at the plan level.

Variable values can include currency, boolean, or string data types.

A Variable can be associated with any type of compensation element.

Any user for which you are a proxy

Any user account in the system

The administrator account only

Your user account only

A position CANNOT have multiple participants at a given time.

A position name does NOT have to be unique.

A position CANNOT be reused.

A participant can have multiple positions at a given time.

When retiring a position end date it by populating the effective end date with the last day of the position.

Never end date a compensation rule. Instead inactivate it by removing the rule from all compensation plans.

When a participant leaves a position do NOT end date the position. Instead inactivate it by removing the participant from the position.

Plans plan objects should only be versioned on a leaf period boundary.

Always use a Variable in a rule instead of a compensation element.

Avoid using Variables because they increase processing time.

Always leave the Variable default assignment field empty.

Set a default assignment for all Variables.

They always use attainment as the input.

They can calculate step commissions only.

They can calculate per-credit or aggregate commissions.

They depend on selections in the credit rule to make calculations.

Results Data

Payments and Balances

User Roles

Event Types

When a participant changes positions

When you NO longer want the commissions calculation to be processed

When you want to delete a participant from the system

When a participant is leaving an organization

Classify, Allocate, Reward, and Pay

Classify, Allocate, Reward, and Post

Reward, Pay, Post, and Finalize

Classify, Allocate, Pay, and Post

Run the pipeline in Incremental Mode.

Run the pipeline in Full Mode.

Leave the transactions for the next month.

Close the period by running Finalize.

If you end date a position or participant, it is deleted from the system.

If a participant has non-zero results data in a period, you can set the end date for the participant to the last day of the period.

If the Credit End and Process End fields on a position extend beyond the effective end date, the position continues to be processed.

You can end date a position or participant version if there is NO results data associated with that version.

Enable the Require Authentication for Proxy Log-in setting.

Disable the Allow Users to Change Password setting.

Enable the Allow Users to Change Password setting.

Enable the Usernames are Case-Sensitive on Login Page setting.

It determines how transactions and orders are paid out to participants.

It contains the data privacy guidelines for the organization.

It generates compensation results organized by Business Unit.

It contains the organizational structure in a hierarchy.

The administrator can release periods based on calendars.

Payees can view dashboards for released periods only.

Both administrators and payees can release periods.

Payees can view results prior to pipeline completion.

The administrator can release periods based on Processing Units.