<p>about your learning experience to help us improve.</p>

You've completed

cleanFiles/bookmap_New_HOSF81_en-US_learning-sap-com_lsc-prod.zip (MMCP-DROPZONE) - 2025-01-13T08:30:14.000Z

Validating Transactions Configuration

<div id="content"><p tabindex="0">Watch the <a target="_blank" href="https://sapvideoa35699dc5.hana.ondemand.com/?entry_id=1_ebmx8mbk">Validating Transactions Configuration</a> video to validate your configuration.</p><div class="kalturaVideoLessonWrapper"><div aria-label="" class="kalturaVideoLessonContainer" data-testid="video" id="1_ebmx8mbk"></div></div></div>

Validate Transactions

Configuring SAP SuccessFactors Employee Central Core

Unit 4 Validation.mp4

For this workshop task, our objective is to create event reasons and additional rules to facilitate the transactions based on the change requests. Let's look at some of the current configurations. The current Event Reason Derivation Rule uses Transfer Event Reason when employees move to a different entity and country. Changes to employee location use Transfer Location instead of Location Change Event Reason. Changes to the local job title default to data change. When the job title changes, the approver is a valid approval group regardless of whoever initiated the request. The currency and the frequency are not auto-populated when the pay component is changed. There is no error message for the home address when attempting to predate the address change six months back. The region of birth is not visible for U.S. and German employees. It's time to verify if our configuration resulted in the expected behavior. Let's start the proxy as MarcusHoff to validate the manager self-service. We created a few event reasons and updated the event reason and workflow derivation rules. Let's verify if the rules work by initiating some transactions. Changing the employees company triggers international transfer event reason and goes to the HR admin group and the new manager. Initiating a local job title change triggers the approval for HR admin and copy to the manager. The currency and frequency fields are auto-populated when there is a change in the pay component. When a manager initiates a spot bonus, it triggers a workflow that goes to the HRBP and the manager's manager for approval. Now, for the employee self-service, let's verify if I changed the address. We can see that any address change older than 6 months generates an error message. Changes to personal information trigger the personal changes workflow. Let's go ahead and test as an HR or admin. We can verify that the admin alert message shows whenever the field is changed from pending hire to show. In the biographical information, the region of birth is only visible when the country of birth is Germany. And finally, when we are using the rehire screen, we can see the new event reason for rehiring.