<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 Foundation Data Configuration

<div id="content"><p tabindex="0">Watch the video to validate your configuration.</p><div class="kalturaVideoLessonWrapper"><div aria-label="" class="kalturaVideoLessonContainer" data-testid="video" id="1_bflq63b6"></div></div></div>

Validate Foundation Data

Configuring SAP SuccessFactors Employee Central Core

Unit 2 Validation.mp4

For this workshop task, our objective is to update the foundation objects and the field definitions to support the change requests. First, let's look at the existing configuration. When we look at the location configuration, the length of the code is set to 32 characters. The business address for Germany only has two address lines and doesn't have the state field. The pay component Id is also set to 32 characters long. The event reason doesn't have the payroll event field enabled. For the MDF-based objects, the Legal Entity ID is also set to 32 characters. The same with the Cost Center. The job classification doesn't have local fields for Germany except for the job title. And lastly, we do not have any structure to hold the new requirement for the building records. And finally, the foundation data names are not translated into German. Now let's check the system to verify if we completed all the required tasks. Let's start with validating the changes to XML-based foundation objects. The location's external code has been shortened to 20 characters. The business address for Germany has been updated to reflect the required fields. The max length of the pay component ID has been updated to 10 characters. We also have the new pay component for Germany. The payroll event field has been added to the event reason with max length of 4. The names of the dynamic roles now include German translations. For the MDF-based objects, the legal entity ID has been shortened to 20. The same with the cost center code. For the German-specific job classification, we now have the additional local fields for clinic director job code in German. For the custom object, we now have the required building records. And we can see the custom fields. The cascading picklist is evident. And we also have the one-to-many association to the entity. When we look at the job information, the legal entity is configured to filter the building field. Lastly, we can opt to create a rule that will auto-populate the security clearance field when there is a change to the building field.