Extending Successfactors With The Metadata Framework: Community
Extending Successfactors With The Metadata Framework: Community
Community
Luke Marson
June 25, 2013 7 minute read
As part of the SAP PRESS title SuccessFactors with SAP ERP HCM I was lucky enough to have an hour-long
private session with Mike Rossi about the SuccessFactors Metadata Framework (MDF). Mike was kind enough
to give me an overview of some of the details of the MDF, as well as some of the upcoming functionality. In this
blog I’m going to provide a high-level overview of the MDF, how it works, and what it means to customers and
consultants.
The MDF is a UI-based con guration and extension framework that provides creation, modi cation,
maintenance, and deletion of custom objects (called Metadata Objects) within the SuccessFactors HCM suite.
It replaces XML-based con guration and the need to import Master Data via CSV/Excel les. It is also leveraged
by the SAP HANA Cloud Platform.
At its core the MDF provides one generic set of the components that are re-used by all objects. This is because
each object’s data is Metadata – nothing is hard-coded within the SuccessFactors system. These components
include:
API
Controller
https://blogs.sap.com/2013/06/25/overview-of-the-successfactors-metadata-framework/ 1/30
5/23/2021 Extending SuccessFactors with the Metadata Framework | SAP Blogs
This means that there is no additional processing or memory consumption to use additional custom objects in
the system. It also means that there is a common framework for the objects; the Metadata Objects only need
their behavior to be con gured through the UI and they have consistent behavior and design. And, most
importantly, there is upgradability because standard objects and components are not changed. For example,
when creating a Metadata Object attributes such as eld names, the eld data type, and the validation rules for
each eld are con gured. The components such as the API, user interface, and database tables do not require
con guration – they automatically work with the user’s custom de nitions. All of this means that
SuccessFactors can deliver features faster as they do not need to write code and customers can extend their
system without the need to write a single line of code.
Customers cannot overwrite standard SuccessFactors objects, but through the MDF they can con gure
standard objects with their own customers-speci c attributes. For example a customer could create attributes
of a Job Code object that are speci c to their business, but this would not change the SuccessFactors Job Code
object – the customer’s changes would be saved separately and would just override those supplied as standard.
From a customer perspective they are unable to identify this, but from a technical perspective it helps maintain
upgradability of the system.
Although SuccessFactors applications do not use genuine objects in many of the Talent Management
applications, this will change once the MDF is rolled out across the SuccessFactors HCM suite. Currently it is
available in Employee Central and Succession, Time O , and the new Job Description Manager application.
There are further plans to extend it across the entire SuccessFactors HCM suite. For example, it is planned for
SuccessFactors Recruiting to use the MDF from 1311 with more functionality added in the next 2 releases. Since
this requires re-architecting of the Database layer and Application layer then this is by no means an easy
activity.
Metadata Objects
The structure of each Metadata Object is xed, although there is a degree of exibility. Customers have the
ability to add up to 200 custom elds for each Metadata Object, in addition to the standard attributes that are
required. These required attributes can be seen in the screenshot below.
https://blogs.sap.com/2013/06/25/overview-of-the-successfactors-metadata-framework/ 2/30
5/23/2021 Extending SuccessFactors with the Metadata Framework | SAP Blogs
There are also some attributes that contain system assigned data, including Internal ID, Creator, Creation Date,
Last Modi er, and Modi ed Date.
Metadata Objects can leverage e ective dating if required and labels and data can be maintained in multiple
languages if any are enabled in the system. They can also have associations (relationships) assigned, just as it
is possible with standard objects. And Metadata Objects can have rules triggered at 9 speci c points within its
transaction ow. These points are called Hooks and allow rules to be executed at point such as during object
initialization, when a eld is changed, before data is saved, or after data is saved etc. Here is an example of the
Position object with rules assigned during the initialization or creation of a position. You can assign more than
rule at Hook.
https://blogs.sap.com/2013/06/25/overview-of-the-successfactors-metadata-framework/ 3/30
5/23/2021 Extending SuccessFactors with the Metadata Framework | SAP Blogs
In addition to the standard Metadata Objects there are also other types of Metadata Object, such as Rules, UI
components, and Picklists. I will not cover these in this blog, although Rules and Picklists are covered in the
blog Rules and Picklists in the SuccessFactors Metadata Framework.
The MDF is accessible in OneAdmin for system administrators – these are under Company Settings and
Employee Files.
https://blogs.sap.com/2013/06/25/overview-of-the-successfactors-metadata-framework/ 4/30
5/23/2021 Extending SuccessFactors with the Metadata Framework | SAP Blogs
Below shows the Employee Files options in OneAdmin. Note that the transactions for Manage Time O
Structures and Manage Time O Calendars are not available unless the Time O feature has been switched on.
In the old Admin Tools look for the section called Generic Objects.
https://blogs.sap.com/2013/06/25/overview-of-the-successfactors-metadata-framework/ 5/30
5/23/2021 Extending SuccessFactors with the Metadata Framework | SAP Blogs
OneAdmin provides multiple options for managing di erent types of Metadata Objects. It also allows you to
import or export Metadata Objects. These options are:
Con gure Generic Object De nition: Create, modify, or delete Metadata Objects (e.g. Building object) and
Picklists
Manage Generic Objects: Create and maintain instances of Metadata Objects (e.g. Building number)
Manage Rule Objects: Create rules and validations
Manage Position Objects: Perform Position Management that is used within Succession & Development
Manage Time O Structures: Create, modify, and delete di erent Time O structures (e.g. Work Schedule)
Manage Time O Calendars: Create, modify, and delete holiday calendars
Manage Con g UI: User interface designer
Generic Objects Import/Export: import or export Metadata Object data
The screenshot below shows a new instance of the Country object being created in Manage Generic Objects.
https://blogs.sap.com/2013/06/25/overview-of-the-successfactors-metadata-framework/ 6/30
5/23/2021 Extending SuccessFactors with the Metadata Framework | SAP Blogs
The principles and technical aspects of MDF di er from SAP HCM. Within SAP HCM when you create an object
type, very little object-speci c information is maintained. Rather, the infotypes and allowed relationships for
the object type are maintained. New elds for new objects require new infotypes or using standard infotype
elds in a di erent way from which they were designed. For more detail on the process of creating new object
types see this blog.
In SuccessFactors – as we have seen – the process for creating an object is based in a single screen and is
signi cantly simpli ed. Although more data can be maintained, it is structured and easy-to-use each time that
you create an object.
The MDF means simpli cation and exibility for creating new objects. It provides a exible and consistent
framework for customers and consultants to extend the object model of SuccessFactors and add their own
unique objects, rules, validations, business logic, and UIs to SuccessFactors. It also means that while the
SuccessFactors system is adaptable, it retains its upgradability and protects both the application and the
customer from issues caused by enhancing the standard system.
However, it should be noted that management of the system is still required and the MDF is not intended to be
available to large audiences. Rather, it should be managed in the same way that the authorizations are
managed to restrict access to transactions in SAP in which objects can be created or maintained. It should also
be managed as such so that Master Data is created by a central team, as would be the case with SAP. Saying
that, the MDF now makes it possible for a business user to be able to enhance the standard SuccessFactors
system without relying on a technical consultant or other technical individual to do this.
For consultants, it removes the need to maintain XML and thus reduces the likelihood of introducing errors into
the system. In my experience of XML, it can be easy to introduce small errors that render the XML unparseable
and are di cult to identify. It also makes extending the system much quicker and provides an object-orientated
approach to data design and maintenance.
Summary
The MDF is a powerful object con guration framework in SuccessFactors. It empowers system administrators
to easily extend the SuccessFactors object model and create objects of their own. It also allows organizations
to introduce their own rules, validations, and business logic to both standard and customer-created objects.
The UI designer means that customers can control the visualization of their objects and take advantage of the
bene ts of the SuccessFactors UI.
https://blogs.sap.com/2013/06/25/overview-of-the-successfactors-metadata-framework/ 7/30
5/23/2021 Extending SuccessFactors with the Metadata Framework | SAP Blogs
Although not fully rolled out across the SuccessFactors HCM suite, the MDF will introduce a huge level of
exibility once it extended to cover all of the solutions in the suite. And although the MDF is very exible and
removes the reliance on technical consultants, it is not a replacement for a well-managed system of maintaining
object types and Master Data. All-in-all the MDF is a huge step forward for SuccessFactors to provide optimal
con guration and extension options across the SuccessFactors HCM suite.
The MDF is covered in detail in the SAP PRESS title SuccessFactors with SAP ERP HCM.
*Addendum*
In the August (1308) release some of the options for the Metadata Framework in OneAdmin were changed. The
changes are:
Alert Moderator
https://blogs.sap.com/2013/06/25/overview-of-the-successfactors-metadata-framework/ 8/30
5/23/2021 Extending SuccessFactors with the Metadata Framework | SAP Blogs
Assigned tags
HCM (Human Capital Management) | Cloud | SAP HANA | cloud on-demand and saas | con guration |
View more...
Related Questions
65 Comments
Former Member
Needed some additional features checked in provisioning and authorizations to turn MDF on in my demo-
system though;)
Like(0)
Thanks J.
The MDF is not enabled by default, although it is usually enabled in demo environments. At a customer you
need to switch on "Enable Generic Objects" in Provisioning. In addition, based on which feature you are
implementing (e.g. Position Mgmt, Time O etc), you also need to check additional options accordingly. With
respect to authorizations, RBP selections are required only if you con gure your Generic Object de nition to be
secured.
Best regards,
Luke
Like(1)
Jarret Pazahanick
Very Good blog Luke and not hard to see the power and exibility that MDF brings to the table especially when it
is incorporated into the entire SuccessFactors suite of products.
Like(0)
Thanks Jarret and I agree. Once the MDF is rolled out fully it will provide a lot of extensibility for customers and
will make SuccessFactors a real option where previously it might not have been.
Like(0)
Former Member
Excellent blog Luke. I like how you have struck the right balance between the foundation of MDF and given us a
quick peek into some of the highlights of MDF objects. I do like your succinct comparison of MDF with SAP
HCM. I can vouch that both customers and consultants are loving what they have seen of MDF so far and have
appetite for more.
Cheers,
Jyoti
https://blogs.sap.com/2013/06/25/overview-of-the-successfactors-metadata-framework/ 10/30
5/23/2021 Extending SuccessFactors with the Metadata Framework | SAP Blogs
Like(0)
Thanks Jyoti - that means a lot from an expert like yourself. The feedback I have received from customers is
very positive, although for some they still need this rolled out further across the BizX suite to reap the full
bene ts of SuccessFactors.
Best regards,
Luke
Like(0)
Former Member
Hi Luke,
Would it be a fair comparison to say that the hooks could be used in a similar way to an SAP event? Linking and
creating a sequence.
Like(0)
Hi Nico,
Yes. A hook is like a user exit or adding some code in a BAdI or an Enhancement Point of a function module.
They are in set places where it makes logical sense for an event to occur.
Best regards,
Luke
Like(0)
Former Member
Hi Luke,
https://blogs.sap.com/2013/06/25/overview-of-the-successfactors-metadata-framework/ 11/30
5/23/2021 Extending SuccessFactors with the Metadata Framework | SAP Blogs
Many thanks for the sharing. I read about the various enhancement options like MDF (as you've written), via
XML and foundation objects. In typical SFSF implementation that has gone 'live', can customers (assuming
they have the know-how) do these enhancements (big or small) themselves or do they have to depend on SFSF
or its partners to do at a cost ? For on-premise, it is clear.
Is this the same model (i.e. customer can do vs. all controlled by vendor) with other SaaS like Workday etc. ?
Kir Chern
Like(0)
Hi Kir Chern,
The MDF allows customers to manage extending the data model themselves so that they do not need to rely on
professional services, much like they can do with SAP (although it is much more complicated in SAP).
Previously to the MDF customers relied on professional services of SuccessFactors Professional Services or
partners to implement changes in XML - if changes could be made at all. Now this reliance has gone with the
MDF.
It is important to note that the process does need managing so as to not create duplicate or unnecessary
objects. Master Data (as we know it in SAP HCM) needs to be carefully managed.
Best regards,
Luke
Like(0)
Former Member
Hi Luke,
Would you be able to provide an example of the hooks function? the screen above show that they are used for
the position object, but I am fuzzy at what they actually do, as relationships are mentioned separately. that
is a part that I haven't yet seen in action.
https://blogs.sap.com/2013/06/25/overview-of-the-successfactors-metadata-framework/ 12/30
5/23/2021 Extending SuccessFactors with the Metadata Framework | SAP Blogs
Comment. Yes, MDF provides a tremendous exibility to customers - with the possibility of easy development to
be done without a big expertise requirement. HOWEVER in my experience a large part of the work in extensions
project is the de nition of the requirements and how they will interact with the standard features and avoiding
un-necessary loops. In the end, it is not only the cost of developments, but we are also talking about the costs of
running a system long term (including ensuring data integrity). The technical layer now becomes easier - but
without the utmost restraint and great business foresight, we'll witness very complex results.
Like(0)
Hi Chiara,
Hooks are a point where a Rule can be triggered for the object or eld (it can be for either). For an object, you
have the 4 distinct points shown in the screenshot above where one or more Rule can be triggered at that stage.
For example, you can add a Rule at the validationRules hook to check that the Job Code you entered is valid and
then in the saveRules hook you could call a Rule to update the Pay Grade if the Job Code is of a certain type.
Associations are relationships between objects that relate to how they interact with each other or when there
are parent-child dependencies.
You've absolutely hit the nail on the head with your comment. I alluded to this in the section "What the MDF
means for customers and consultants" because the governance and compliance around MDF should be no less
than in SAP HCM - in fact, maybe it should be more given the freedom and ease with which Metadata Objects
can be created and modi ed. With great power comes great responsibility, to quote my favorite comic book
(Spiderman)
Best regards,
Luke
Like(0)
Former Member
Agree with you - it possibly should be more, because with the MDF being of such an easy access, there is a layer
of counseling that is not there. Now, it is true that many consultants didn't have (and many still don't) have the
business experience to play a role of trusted advisor...
Like(0)
https://blogs.sap.com/2013/06/25/overview-of-the-successfactors-metadata-framework/ 13/30
5/23/2021 Extending SuccessFactors with the Metadata Framework | SAP Blogs
Now, it is true that many consultants didn't have (and many still don't) have the business experience to
play a role of trusted advisor...
Like(0)
Former Member
Like(0)
Absolutely!
Like(0)
Former Member
Hi Luke,
If I need to custom new elds in SF to a form, would that be the location to do that from the admin tools?
I have a PM form which I'd like to add new elds to it, would that be done by using the SF admin tools for new
elds? in other words, can I create and edit the new elds in the PF admin tools or I need to SAP HCM system
for that?
Since we do not have the SAP HCM system and just the SF system, would that be su cient to create new elds
at SF system?
Thanks,
Shai
Like(0)
Hi Shai,
The Metadata Framework is not yet available for Performance & Goals, so it cannot be used to add or modify
objects in Performance & Goals.
To add new elds it really depends on your exact scope. You could add a new section to your template, but I
don't know if that suits your needs or not. You can also look at SuccessFactory.
Best regards,
Luke
Like(0)
Former Member
Hi Luke,
Quick question: As you mentioned -MDF Objects can have rules triggered at 9 speci c points within its
transaction ow ( Hooks ). For an object, we have 4 distinct points ( Save, Validate, Initiate and Delete ). Can you
please share what are all the other 5 points? Are they eld level?
Best Regards,
Murugan
Like(0)
Hi Murugan,
The hooks are technical, since they vary by type (e.g. object type, object-level, and eld-level). Basically, from
an end-user perspective you need to look at:
Initialization
Change
Save
https://blogs.sap.com/2013/06/25/overview-of-the-successfactors-metadata-framework/ 15/30
5/23/2021 Extending SuccessFactors with the Metadata Framework | SAP Blogs
Some objects also have other hooks, such as on-the- y calculations. See the rules engine handbook for more
details.
Best regards,
Luke
Like(0)
Former Member
Best Regards,
Murugan
Like(0)
Former Member
Luke,
Great article! I should say i went to your article soon after reading the implementation guide for MDF as there
may be some requirements to create MDF's at my project.Your article is a great summary of what is there in the
MDF implementation guide. One question , how do we replicate what i would normally do through an HCM P&F
in SAP HCM within SF.Say for example i want an online form to be lled in by the employee which would need to
update certain elds in SF.
Regards
Harris
Like(0)
Thanks Harris! My blog actually precedes the MDF implementation handbook (in its current state) so that's
good feedback to get.
You could use the MDF to create a form object and then use rules to propagate information on the target portlet
(e.g. JobInfo). You can also attach work ow to the object so that the data won't be updated until it is approved. I
https://blogs.sap.com/2013/06/25/overview-of-the-successfactors-metadata-framework/ 16/30
5/23/2021 Extending SuccessFactors with the Metadata Framework | SAP Blogs
would also consider looking at using an EC extension on HCP rather than MDF if you think it could be a complex
process.
Like(0)
Former Member
Hi Luke,
thanks a lot for that great article ( as always ). One Question: Do you expect MDF and HCP extensions comming
for performance and goals ( and succession) ? Today I spent some time on SCN and SAP related sites and I do
not nd any informations on that topic. All slides, PDF's and videos related to that topic deal only with EC.
BR
Martin
Like(0)
Hi Martin,
Thanks for your feedback! As it stands right now, MDF and the extensions package on HCP are only available for
Employee Central. There are plans to roll this out to Recruiting this year, but so far I have not heard of any
timelines or additional plans to roll this out to Performance & Goals. I will update you if I hear more.
Best regards,
Luke
Like(0)
Former Member
Hi Luke,
best regards
Martin
https://blogs.sap.com/2013/06/25/overview-of-the-successfactors-metadata-framework/ 17/30
5/23/2021 Extending SuccessFactors with the Metadata Framework | SAP Blogs
Like(0)
Readers of this blog might enjoy this article if they have an SAPexperts subscription:
Like(0)
Sumanthanan. B
Hi Luke,
Could you give update on the current status of MDF & latest Blog link.
Many Thanks !
Best Regards,
Suman
Like(0)
Hi Suman,
MDF continues to have its capabilities extended. There are no blog updates at this time.
Best regards,
Luke
Like(0)
Former Member
https://blogs.sap.com/2013/06/25/overview-of-the-successfactors-metadata-framework/ 18/30
5/23/2021 Extending SuccessFactors with the Metadata Framework | SAP Blogs
Can you please advise if I want modify behavior of foundation object then should that be done from MDF or
using export corporate data XML and making changes before importing through provisioning account.
Moreso in my demo system I cant nd option "Manage Organization, Pay and Job Structure" link under
employee le. Also exported corporate data model from provisioning I nd XML le only contains string
"corporate-datamodel.xml is not imported prior to export." Not sure why corporate data model is blank in my
system.
Thanks
Abhay
Like(0)
Thanks Abhay.
Foundation Objects are not managed through MDF as they are not MDF objects (although that will change in
the future). It sounds like you have a non-EC demo system or a demo system that hasn't had EC loaded. You will
need to check that you have the correct Provisioning settings, upload the standard data model, and permission
your user for the "Manage Organization, Pay and Job Structure" link.
Best regards,
Luke
https://blogs.sap.com/2013/06/25/overview-of-the-successfactors-metadata-framework/ 19/30
5/23/2021 Extending SuccessFactors with the Metadata Framework | SAP Blogs
Like(0)
Former Member
Thanks Luke for prompt reply. This system was originally con gured for RCM. I also think that corporate data
model has not been loaded. However if I want to con gure EC then where do I nd standard data models. Can I
use option of uploading Pre-packaged templates as mentioned below?
Like(0)
Like(0)
Former Member
Like(0)
https://blogs.sap.com/2013/06/25/overview-of-the-successfactors-metadata-framework/ 20/30
5/23/2021 Extending SuccessFactors with the Metadata Framework | SAP Blogs
Former Member
Hi Luke,
Regards,
Aiivenn
Like(0)
Hi Aiivenn,
Best regards,
Luke
Like(0)
Former Member
Hey Luke
Is MDF going to replace all XML's part con g. How much di erence can we notice if SF switch completely to
MDF's.
Cheers
Pradyp
Like(0)
Hi Pradyp,
https://blogs.sap.com/2013/06/25/overview-of-the-successfactors-metadata-framework/ 21/30
5/23/2021 Extending SuccessFactors with the Metadata Framework | SAP Blogs
I believe that one day all XML-based con guration will move to MDF, but that will take some time. EC is moving
to MDF rst and the di erence for customers means that everything can be con gured in the UI with no XMLs.
Best regards,
Luke
Like(0)
Former Member
Hi Luke,
I have one question on import/export functionality. Is there any way of creating an MDF object de nition in one
tenant and moving it to another tenant using export and import as le? If I have a set of MDF data objects
created in one tenant and I want to create same objects in another tenant, is there any way of moving them as
le system.
I have seen the option export metadata to le options but not sure whether that is the correct way of doing it or not.
Sourav
Like(0)
Hi Sourav,
Yes, you can export MDF objects from one system and import them to another (this includes rules and
con guration UIs). However, bear in mind that when they are from di erent systems with di erent languages
and con gurations that the object de nitions will not always import without some form of modi cations.
Within the same customer system, you can copy MDF objects from one instance to another using the Instance
Synchronization Tool. This is the recommended solution for a customer.
Luke
Like(0)
https://blogs.sap.com/2013/06/25/overview-of-the-successfactors-metadata-framework/ 22/30
5/23/2021 Extending SuccessFactors with the Metadata Framework | SAP Blogs
Former Member
Hi Luke,
I have got the Instance Synchronization Tool enabled in provisioning account. Could you please tell me how to
access the tool from my tenant. I am not able to see the option. Do I need to check some options in admin
roles?
Sourav
Like(0)
Former Member
Hi Luke,
In the screen below, I need to get my target instance, Could you please tell me where to set up this
con guration.
Sourav
Like(0)
Hi Sourav,
https://blogs.sap.com/2013/06/25/overview-of-the-successfactors-metadata-framework/ 23/30
5/23/2021 Extending SuccessFactors with the Metadata Framework | SAP Blogs
Is this a demo instance or customer instance? If it is a demo instance you won't get any options.
Luke
Like(0)
Former Member
Hi Luke,
So I won't get that option as i am on demo instance. But can you please tell me whether there is some separate
con guration steps to be done other than just adding the customer instance in provisioning?
Kind Regards,
Sourav
Like(0)
Hi Sourav,
The tool only works to sync from one customer instance to another. You can't sync from a demo instance to a
customer instance.
If you want to transfer con guration from a demo instance to a customer instance then you need to use the
import/export options and then modify your object CSV les to ensure they can be imported (e.g. remove/add
any languages that are not in the customer instance).
Luke
Like(0)
Paula DiTallo
Luke,
https://blogs.sap.com/2013/06/25/overview-of-the-successfactors-metadata-framework/ 24/30
5/23/2021 Extending SuccessFactors with the Metadata Framework | SAP Blogs
I'm an enterprise integrations developer outside of the SAP stack recently tasked with retrieving data from the
SF objects via OData calls for usage in another company wide application. I've had success with this-- in all but
incremental searches, where I am looking for data between a speci c date range. A query such as:
https://api[dub].successfactors.com/odata/v2/EmpJob?$&$top=5&fromDate=2015-05-01&toDate=2015-06-
10 does not return updated records within the date range. After reading your post, I see that this may have to
do with how SF is con gured. I am not well versed in SAP to know how to look to see if this is the root cause. I
can contact our SF administrator, however, more broadly speaking, is there an OData call to the metadata
framework which can answer that question? The calls to $metadata do not appear to include object de nition
info.
Like(0)
Former Member
There is an special Entity called Entity which you can call to get object de nitions
Like(0)
Former Member
Hello Luke,
Is there a limit to how many MDF objects that can be created? If so, Is there a way to extend beyond the limit?
Thanks,
Raul
Like(0)
Former Member
My understanding is there's a 25 MDF object limit for the full suite of modules unless you have Hana Cloud
integration platform (HCI). Then the number can go up to unlimited depending on the contract. This is
controlled in Provisioning. Hope this helps
Like(0)
https://blogs.sap.com/2013/06/25/overview-of-the-successfactors-metadata-framework/ 25/30
5/23/2021 Extending SuccessFactors with the Metadata Framework | SAP Blogs
The limit depends on the SAP HANA Cloud Platform license (not HCI). It can be more than the provided number
if an additional license is purchased.
Like(0)
Former Member
But also, you can use MDF objects without HCP at all up to 25. Once above 25, HC Platform is required. We had
this issue with a customer that has EC but does not have Hana Cloud. There were allowed to use up to 25 MDF
objects.
Thanks!
Like(0)
Former Member
Hello Luke,
Is there any further steps need to be process? How can we nd the relationship between employee id and
position id?
Thank you!
Like(0)
https://blogs.sap.com/2013/06/25/overview-of-the-successfactors-metadata-framework/ 26/30
5/23/2021 Extending SuccessFactors with the Metadata Framework | SAP Blogs
Hi Wei,
These steps are correct. You de ne the Position Id in the Job Information import (called Job History in the
Import Employee Data screen).
Best regards,
Luke
Like(0)
Barin DESAI
Hi Luke
What is the property e ective dating in MDF used for any clue?
regards
barin
Like(0)
Hi Barin,
Best regards,
Luke
Like(0)
Former Member
Like(1)
Sirilug Sorpitpakdeepong
Hi Luke,
Thanks for this articles but I need ask some questions about MDF. I can use MDF without Employee Central
module?
Thanks
Like(0)
Like(0)
Former Member
Hi Luke,
I am working in LMS and have requirement Meta Data tag for an Item or Curriculum, please guide or suggest
how to do that.
Regards,
Pallavi
Like(0)
https://blogs.sap.com/2013/06/25/overview-of-the-successfactors-metadata-framework/ 28/30
5/23/2021 Extending SuccessFactors with the Metadata Framework | SAP Blogs
Like(0)
Liran Azuri
Hi everyone,
I have a question regarding connecting a new MDF object for the employee pro le:
I have created a new MDF object and assigned it successfully for the employee pro le. However, I wish that each
employee may have simultanousely several records of this object (just like the possibility to add an employee
several nationality records under the "National ID Information" portlet).
I know it's possible by using the background elements, but this option is not suitable for me becuase I also need
to set di erent permissions for this object's elds (which is not possible doing by background elements).
Thank you!!
Like(0)
Like(0)
hanumagutti rajinipriya
excellent blog
Like(1)
Joachim Dengler
Dear Luke,
you compare the MDF with SAP-OM. Can you please comment on how you would implement OM evaluation
paths within the MDF? This question is crucial for an application that I have in mind, involving long and
customer speci c evaluation paths.
Like(0)
Hi Joachim,
I wouldn't quite say that the MDF compares with SAP-OM. MDF compares with creating custom infotypes in
SAP PA/OM and/or creating custom object types in OM.
There isn't really a concept of evaluation paths in EC. You do, however, have associations between objects, but
evaluation paths are not used.
Best regards,
Find us on
Newsletter Support
https://blogs.sap.com/2013/06/25/overview-of-the-successfactors-metadata-framework/ 30/30