TLDR;
This video provides a detailed overview of Foundation Objects within SAP SuccessFactors Learning, focusing on the differences between XML-based and MDF-based objects, how to modify them, import data, and the significance of object definitions. It also covers key configurations such as effective dating, API visibility, and workflow processes.
- XML-based objects are modified via the Corporate Data Model, while MDF-based objects are managed through Configure Object Definition.
- Data can be imported in bulk using Excel sheets or CSV files via the "Import Foundation Data" tool for XML-based objects and "Import and Export Data" for MDF-based objects.
- Effective dating options (From Parent, Basic, Multiple Changes Per Day, None) determine how object dates are maintained and their dependency on parent objects.
- API visibility settings (Not Visible, Read Only, Editable) control data transfer to third-party applications.
Introduction to Foundation Objects [1:03]
The video begins by outlining the discussion of remaining Foundation Objects, distinguishing between XML-based and MDF-based objects. XML-based objects, prevalent in earlier versions of SuccessFactors, are gradually being replaced by MDF-based objects. Modifying MDF-based objects doesn't require access to the provisioning system, simplifying the process. The Configure Object Definition tool is used to modify existing or create new MDF objects.
Modifying and Managing Foundation Objects [4:08]
The presenter explains how to modify XML-based objects via the Corporate Data Model and MDF-based objects via Configure Object Definition. Data related to XML-based objects is created and modified in "Manage Business Configuration," while MDF-based object data is managed in "Manage Data." For importing data, XML-based objects use "Import Foundation Data," and MDF-based objects use "Import and Export Data." To verify data, XML-based objects use Ad Hoc reports, while MDF-based objects use "Import and Export Data."
Configure Object Definition: An Overview [14:29]
The video transitions to Configure Object Definition, highlighting options for legislatively sensitive data configuration and data privacy/retention. The presenter touches on General Data Protection Regulation (GDPR) and its role in ensuring user data is deleted from company databases after an employee leaves, with considerations for data retention periods to accommodate final settlements.
Object Definitions and Attributes [18:48]
The discussion covers object definitions, explaining that a location object comprises several fields. XML-based object definitions are found in the XML Corporate Data Model, while MDF-based objects have fields with attributes like length, data type, and label name. The presenter advises navigating to Configure Object Definition to configure MDF-based objects, specifically mentioning legal entity, division, department, and business unit as examples.
Effective Dating Explained [22:45]
The presenter describes effective dating options for MDF-based objects: From Parent, Basic, and Multiple Changes Per Day. "From Parent" means the object's existence depends on a parent object (e.g., a classroom depending on a school). "Basic" allows the object to exist independently with its own date. "Multiple Changes Per Day" is used when data changes multiple times within a day. The presenter uses the example of a production unit tracking employee output every two hours.
Parent and Child Objects [27:56]
The presenter explains the concept of parent and child objects, using the school and classroom analogy. A parent object can exist independently, while a child object depends on the parent. The effective dating setting "From Parent" indicates a child object. Standard objects cannot have their effective dating set to "None."
API Visibility and Data Integration [44:30]
The presenter discusses API visibility settings: Not Visible, Read Only, and Editable. These settings control whether data can be transferred to third-party applications via integrations. "Read Only" allows data to be sent from SuccessFactors to a third party, while "Editable" allows the third party to send data back. Examples include sending employee details to a bank (outbound, read-only) and receiving premium amounts from an insurance provider (inbound, editable).
Status, Version History and Default Screen [50:48]
The presenter covers the status of an object (active or inactive), MDF version history (maintaining only the current data or complete history of changes), and the default screen. Making an object inactive disables it, preventing data maintenance. MDF version history can be set to either maintain only the current data or keep a complete history of changes. The default screen refers to the UI layer assigned to an object, allowing customisation of field sequences.
Additional Configuration Options [1:00:12]
The presenter touches on label name, description, API subversion, and workflow routing. The label name is typically the company code, and the description provides context for the object. Workflow routing allows changes to go through an approval process, with options to display pending data and categorise to-do items on the homepage. The video concludes by encouraging viewers to explore objects like legal entity, business unit, division, and department in Configure Object Definition.
