Symptom
Odata APIs allows third party systems or interfaces to communicate and exchange data with SuccessFactors, and even also some SF modules to communicate to one another.
Environment
SAP SuccessFactors Onboarding
Resolution
There are hundreds of OData API entities that SuccessFactors has defined. Many MDFs objects can have an underlying OData API entity so that data can be read.
Here is the list of ONB2.0 MDF entities that are available for OData API entities.
- ONB2Process
- ONB2ProcessTrigger
- ONB2ProcessTask
- ONB2BuddyActivity
- ONB2EquipmentActivity
- ONB2EquipmentItem
- ONB2EquipmentType
- ONB2EquipmentTypeValue
- ONB2DataCollectionUserConfig
Important to note! The following fields will be available for ONB2ProcessTrigger, instead of ONB2Process. As 'Process' is a sub object of Process Trigger, it is expected that this object doesn't pull the required information. You can continue to use Process Trigger instead:
- Job Requisition ID
- Job Application ID
- Job Offer ID
- Candidate ID
Keywords
Odata Api Entities, Odata, API, MDF objects, MDF, Onboarding, OBX, Job, Requisition, application, Offer, Candidate, ID, blank, show, pull, nothing , KBA , LOD-SF-OBX-NF , Notifications Framework , How To