Location via proxy:   [ UP ]  
[Report a bug]   [Manage cookies]                
Scribd Logo
Upload

Welcome to Scribd!

  • 2K views

    MDF, Foundation and Generic Objects

    Uploaded by

    samiksha yadav
    The document discusses the Metadata Framework (MDF) in SAP SuccessFactors, which provides a UI-based system for configuring and managing custom metadata objects to replace XML configuration and CSV/Excel imports. It lists several foundation objects that were migrated to the MDF, including cost center, department, division, and others. It also describes how field level permissions can be set using the MDF to restrict access to specific fields when viewing or editing objects.

    Copyright:

    © All Rights Reserved
    Download as DOCX, PDF, TXT or read online from Scribd

    MDF, Foundation and Generic Objects

    Uploaded by

    samiksha yadav
    2K views2 pages
    The document discusses the Metadata Framework (MDF) in SAP SuccessFactors, which provides a UI-based system for configuring and managing custom metadata objects to replace XML configuration and CSV/Excel imports. It lists several foundation objects that were migrated to the MDF, including cost center, department, division, and others. It also describes how field level permissions can be set using the MDF to restrict access to specific fields when viewing or editing objects.

    Original Title

    Mdf, Foundation and Generic Objects

    Copyright

    © © All Rights Reserved

    Available Formats

    DOCX, PDF, TXT or read online from Scribd

    Did you find this document useful?

    Is this content inappropriate?

    The document discusses the Metadata Framework (MDF) in SAP SuccessFactors, which provides a UI-based system for configuring and managing custom metadata objects to replace XML configuration and CSV/Excel imports. It lists several foundation objects that were migrated to the MDF, including cost center, department, division, and others. It also describes how field level permissions can be set using the MDF to restrict access to specific fields when viewing or editing objects.

    Copyright:

    © All Rights Reserved
    Download as DOCX, PDF, TXT or read online from Scribd
    Download as docx, pdf, or txt
    2K views2 pages

    MDF, Foundation and Generic Objects

    Uploaded by

    samiksha yadav
    The document discusses the Metadata Framework (MDF) in SAP SuccessFactors, which provides a UI-based system for configuring and managing custom metadata objects to replace XML configuration and CSV/Excel imports. It lists several foundation objects that were migrated to the MDF, including cost center, department, division, and others. It also describes how field level permissions can be set using the MDF to restrict access to specific fields when viewing or editing objects.

    Copyright:

    © All Rights Reserved
    Download as DOCX, PDF, TXT or read online from Scribd
    Download as docx, pdf, or txt
    You are on page 1of 2

    The 

    MDF is a UI-based configuration and extension framework that provides creation,


    modification, maintenance, and deletion of custom objects (called Metadata Objects) within
    the SuccessFactors HCM suite. It replaces XML-based configuration and the need to
    import Master Data via CSV/Excel files.
    Purpose of the Generic Object. Changes to standard fields, such as data type or source of
    valid values (e.g., a Picklist or Foundation Object) Custom fields added, along with details of
    the new field (e.g., data type, valid values source, rules, etc.) MDF Picklist objects that have
    been created.
    Foundation objects are categories or structures for listings of data that are set up to be
    used across an entire company.
    SAP SuccessFactors' Foundation Objects can be used to populate data at the employee
    level. For example, if a job code is assigned to an employee, that employee's record is then
    populated with all information based on the attributes of the job code.

    As part of the phased migration of Foundation Objects (FO) to the Metadata Framework


    (MDF), the following Foundation Objects are now MDF Foundation Objects (also referred to
    as GOs). Any organizational information configured using these FOs will now be configured
    using the corresponding MDF FO. Please note these are Employee Central MDF Objects and
    not Custom MDF objects. Any issues relating to these objects must be raised with Employee
    Central team.
    This Foundation Object... Was migrated in this release...
    Cost Center Q4 2014 Release
    Department Q2 2015 Release
    Division Q2 2015 Release
    Business Unit Q2 2015 Release
    Legal Entity Q2 2015 Release
    Legal Entity Local Q2 2015 Release
    Job Function Q4 2015 Release
    Pay Group Q4 2015 Release
    Pay Calendar Q4 2015 Release
    Job Family (Deprecated)       Q4 2015 Release
    Job Classification Q4 2015 Release
    Job Classification Local Q4 2015 Release

    Field Level Overrides When granting permissions to MDF Objects, it's possible to further
    restrict a user's permissions to only see or not even see a specific field when viewing the object.
    This kind of restriction is achieved by using the "Field Level Overrides" option in RBP, when
    granting permissions to MDF Objects.
    For example, a company may want to allow managers to change some details of the Position
    object for Succession Planning, but only allow HR Business Partners to edit the "Position
    Criticality". So, in the Managers permission role, you'd grant access to Insert/Correct for the
    Position object, but use the "Field Level Overrides" option to restrict the permission of field
    "Position Criticality" to "Read Only". The result will be that, when a manager is editing a Position,
    he/she will not be able to edit the "Position Criticality" field, but only to see it.
    Similarly, there may be some fields that only the Admin Users should be able to see. For
    example, the Position object may have a "Source of Creation" field, which is useful to help
    managing the Position Data, but not so useful for the Managers. In this case, you'd be able to
    use the "Field Level Overrides" option to set up "No Access" restriction for the "Source of
    Creation" field. The result will be that, when a manager is viewing the details of a Position,
    he/she will not be able to see the "Source of Creation" field at all.

    You might also like