Which objects are supported in cross-entity business rules? Note: There are 2 correct answers to this question.
Cross-entity business rules in SAP SuccessFactors Employee Central allow for data propagation and validation across different HRIS elements. The following objects are supported in cross-entity business rules:
A . Pay Component Recurring
This object pertains to regular, recurring payments such as salaries. Cross-entity rules can be configured to update or validate data between Pay Component Recurring and other entities like Job Information.
D . Job Information
This object contains details about an employee's job role, department, and other related information. Cross-entity rules can be used to ensure consistency between Job Information and other entities, such as Compensation Information.
Objects like Work Permit Information and Personal Information are not currently supported in cross-entity business rules. The focus of cross-entity rules is primarily on employment-related entities to maintain data integrity across core HR processes.
The HR admin has to change the salary of an employee, which will trigger a workflow for the employee's manager. The employee's manager
should be able to edit the transaction if the proposed amount is NOT correct.
Where in the workflow do you need to define this?
Refer to the screenshot to answer the question
To allow the employee's manager to edit a transaction in a workflow if the proposed salary change is incorrect, you must configure the 'Edit Transaction' setting in the workflow.
The 'Edit Transaction' option is part of the workflow configuration in Step 1 (as shown in the screenshot).
When enabled, it allows the approver (in this case, the manager) to make adjustments to the transaction before approving it.
Scenario 2: Approvals for Self-Service
In which cases should the value for CREATE Respects Target Criteria be set to Yes in the Position object definition? Note: There are 2 correct answers to this question.
The CREATE Respects Target Criteria setting in the Position object definition ensures that the system applies access control criteria when creating positions. This is critical for maintaining organizational and data security. It should be set to Yes in the following cases:
A . To restrict access to create positions based on the granted user's target population:
This ensures that users can only create positions for entities (e.g., departments, locations) within their authorized target population.
C . To restrict access to create lower-level positions from the Position Org Chart:
This limits the ability to create subordinate positions in the hierarchy to authorized users, maintaining the integrity of position relationships.
Manager A initiated a job code change for Employee X with an effectivity date of January 15. Another manager initiated the same request, but for January 30. What happens to the workflows triggered by both transactions?
When two workflows are initiated for the same employee with different effective dates, both workflows are allowed to proceed independently. The system processes them sequentially based on their respective effective dates. This ensures that updates are recorded in the order they occur without rejecting either workflow.
Other options, such as canceling or rejecting workflows, do not align with standard system behavior for managing multiple transactions.
Trina
5 days agoBrittni
7 days ago