privacy statement, for purposes that may include site operation, analytics, enhanced user experience, or advertising. I want to reduce the number ofSetup mTLS (mutual Transport Layer Security) as your authentication method between Identity Provisioning and SuccessFactors. Features. The API extracts user records that match the reconciliation criteria and hands them over through the bundle and ICF back to the scheduled task, which brings the records to Oracle Identity Manager. We are writing in incremental purge mode, which means we are just updating records from the. API to access 360 Reviews forms. In the OData API data dictionary, you can use Search All, or narrow your search to Entity, Complex Type, or Function Import. Past year my. Host: apisalesdemo4. Logical Operators LOGICAL OPERATOR SAP SuccessFactors provides two APIs for its integration with Identity Provisioning: SAP SuccessFactors HCM Suite OData API and SAP SuccessFactors Workforce SCIM API. 2. When the value is set to 1, or the property is not defined - SAP SuccessFactors HCM Suite OData API (in short. 0 Let’s call iRPA 2. LGN0011. The EmpTimeAccountBalance entity provides time account balance information, enabling external systems like payrolls to capture this data. OData API. 2. In 2021 a set of new and more secure authentications mechanisms have been released for SAP SuccessFactors OData and SOAP APIs as well as for the corresponding SAP Integration Suite and Boomi connectors. Address Suffix. Insert. OData getEntity method fetches only first entity. SuccessFactors (OData V2) Adapter Configuration. IAS is setup. Get access to your organization’s Success Factors Instance. SuccessFactors OData V2 receiver supportes Upsert with content-type : atom+xml only. API to query and maintain candidate's profile and background information. To externalize the parameters of this adapter, choose Externalize and follow the steps mentioned in. Make sure that the data exchange complies with your company’s policies. Register the service in the SAP SuccessFactors system. Through. Unexpected XmlAttribute: The attribute ' CollectionKind' was not. SAP SuccessFactors Onboarding supports both rehire on new employment and rehire with old employment information. Register your client application so that you can authenticate API users using OAuth2. You may choose to manage your own preferences. Testing. Step 1: Create an app variable. SuccessFactors extensions leverage the SAP Cloud Portal to achieve dynamic branding and retheming of extension UIs by using SAP Portal sites configured with a corresponding template to mimic the look and feel of the extended SAP solution. It is a framework to develop a responsive web application by using HTML, CSS, jQuery and Java script. Creating API User IDs Option 2. This is expected behavior. This guide focuses on OData version 2. SuccessFactors; Photo Entity; Integration Center; Exporte Profile Photo;. g. How to clear an internet browser's cache? How to clear an internet browser's history and cache? How to clear an internet browser's temporary internet files? **Image/data in this KBA is from SAP internal systems, sample data, or demo systems. This KB article explains what OData API is and what. In SuccessFactors you need to register a new OAuth client with the public key downloaded from your subaccount in the previous step. User id should be specified as userid@SuccessFactorcompanyid. The list of Main Data Source connectors is displayed. Register New Client Application in SAP SuccessFactors. OAuth Client Registration. This is even more true for integrations and API based communication. 0. We show you what needs to be done (video 4), but this may require the involvement of an administrator. This blog describes how to upsert the attachments into Successfactors using SAP Cloud Platform Integration. Steps to Download Odata API Audit Logs:learn how to work with OData v4 APIs in SAP SuccessFactors HXM Suite and what services we currently offer. Let’s Start – Login to SuccessFactors Portal (I assume you have full access or ability to Proxy as “sfadmin” user) Step 1: OData IP Allowlisting. However, the deleted record is not able to capture from OData API. 2. You can use this entity to query and edit the information of legacy. You can use this OData API to display non-effective-dated biological information about an employee such as date and place of birth, and date of death. SAP SuccessFactors HXM Suite. MDF OData API. This application allows user to explore SuccessFactors oData API metadata. api. Business logic: Mainly consists of business logic with OData/REST service and security checks. Using a datasource that we use often in joining Cloud HR related data to other SAP related data, Success Factors odata endpoints: SuccessFactors as a source. This brief is to showcase the SAP SuccessFactors extensibility service when used directly from SAP BTP, Kyma runtime environment. OpenSQLAccess. The SuccessFactors OData API test system comes with a predefined set of users and data configured in READ ONLY mode. Additional Information. To make OData API calls to a SAP SuccessFactors company (system), be it demo, test, or production, you need to have an account with the OData Export privilege and this requires access to Admin Center for configuration. Blog Posts. Click more to access the full version on SAP for Me (Login required). UI name. The reason for these errors is due to incorrect request data sent to the SFSF system. This issue can happen with any Odata entity in SuccessFactors and this blog will help to understand why it happens and how to get rid of it. all the instructions provided in this blog post apply exactly the same to any OData Service from any application (SAP S/4HANA. O to securely call SuccessFactors OData APIs from iRPA 2. In the following example, admin users with OData API job application export permission can initiate assessment during insert operation if assessment is configured for the New/Default Application status. The API Server is a lightweight software application that allows users to create and expose data APIs for SAP SuccessFactors, without the need for custom development. Note: A side remark; the Accept-Encoding GZIP configuration has been provided for the newer SuccessFactors OData V2 connector version 1. Foundation Entities: Describes other general data such as organization, job code and pay component. The OData V2 message protocol for the SuccessFactors adapter is available only in the receiver channel. externalId and Status are mandatory fields. 3 ODATA for SAP SuccessFactors Learning ApplicatiUse case 1: Initiate assessment through JobApplication entity using insert operation. For example, CamelHttpQuery=abcd=1234. 17. This blog explains how you can trigger workflows attached to a MDF object using OData APIs. 2. The SuccessFactors connector enables you to authenticate using either Basic or OAuth 2. The below blog by Sriprasad S Bhat have the detailed information about the Data Dictionary. In the adapter configure all the mandatory parameters. Pre-Read: Migrating SAP SuccessFactors API Calls from. Use Case 4: Modifying a Picklist Option with Replace. SAP SuccessFactors HXM Suite; OData API (V2) Resolution. 0, including Onboarding 1. 2250344 - How to enable OData API (V2) - SuccessFactors | SAP Knowledge Base Article. userId = User ID used by the registered client in SuccessFactors. In order to resolve the issue, you need to ensure you pass the REQUEST in correct format. I will refer to this extension through out this blog. This article describes the steps on how to perform ODATA API queries and upsert requests via Postman. Properties and Navigation Properties. It's now 2021 and a properly functioning OData connector in Power BI seems to still be outstanding. This will ensure that when Gem makes queries to the SuccessFactors OData API for certain fields, they will be visible and allow you to report on them. Registering Your OAuth2 Client Application. For example, a user interface can display a field as a label if the field is read only, or display it as an input box if it’s mandatory. The refresh may take a few minutes. The steps. Error: The metadata document could not be. The OData API is a solution with allows to export, create and update operations in the Recruiting Module. After ‘Request Reply’ is defined that is named ‘Invoking userId’ in the flow, SuccessFactors OData v2 adapter configurations are made as shown below. The end point type is set to TargetEndpoint which is the SuccessFactors API URL that was set when the API definition was created. If necessary, move the XML file. 0 Uri Conventions". The scenario includes highlighting the location of US-based candidates on an interactive map: It also covers how to trigger and. How to enable the OData API (V2) in SuccessFactors? Image/data in this KBA is from. Cloud Integration is interconnected with the sender and SAP SuccessFactors. Choose Refresh. but we are only taking costCenter for ease, here) from ‘EmpJob’, Entity of Employee Central module of SuccessFactors. Postman is used to call the iflow URL (1), the request message body (2) is ignored in my demo. Use Case 1: Querying a Picklist Option. I am trying to get current and future dated records from SuccessFactors for any entity. You can use SuccessFactors ODATA Connector to connect to SuccessFactors from. The Upsert operation is an SAP SuccessFactors function import to update or insert records. The SAP SuccessFactors HXM Suite OData API is a Web Service API feature based on the OData protocol. Learn about changes to the documentation for Learning OData API Reference in recent releases. It is important to understand what is going on here. SAP SuccessFactors extensibility service comprises SuccessFactors ODATA api-access automation and SSO. 2 (Import Employee via SFSF Application UI) Section 5*: Setting the Password for the API User. It's now 2021 and a properly functioning OData connector in Power BI seems to still be outstanding. Use the generated token to call APIs. I am replicating the Successfactors Employee Central Data (including FO, MDF, BG elements and etc. Step 6: If you are still wondering. The SAP SuccessFactors HXM Suite OData API is a Web Service API feature based on the OData protocol. In SuccessFactors, navigate to SuccessFactors > Admin Center > Company Settings > Manage OAuth2 Client Applications > Register Client Application. API to access Calibration data such as subject rank, feedback and rating. 8. Step 3:Configure the SuccessFactors OData V2 channel ( you can use SuccessFactors SOAP for Compound Employee API ). 11 5 2,306. This causes timeout. 8 Getting users up and running: Permission settings) each permission specified and the. com Content-Type: multipart/mixed; boundary=batch_36522ad7-fc75-4b56-8c71-56071383e77b Before constructing the request body, I would like to explain the use of postman variables in the API request. The key idea to understand this is that the. JOB TITLE LOCATION; Senior Electrical Engineer (Combat) (Permanent) Victoria: 30-Oct-2023 - N/A: Senior Technologist - Mechanical (Permanent) 30-Oct-2023 - N/AIt's now 2021 and a properly functioning OData connector in Power BI seems to still be outstanding. Picklist issues using Infoporter - SuccessFactors OData API. Added an API for Learning Administrators to get library details. References: SFSF Adapter – SuccessFactors (SFSF) Adapter for SAP NetWeaver Process Integration. 4. Select the exact fields that need to be integrated with 3 rd Party application. Description. 1 - Mule 4. In productive scenarios, the metadata seldom changes. SAP SuccessFactors offers a comprehensive set of Role Based Permission (RBP) APIs based on OData V2. Related Information. This site uses cookies and related technologies, as described in our privacy statement , for purposes that may include site operation, analytics, enhanced user experience, or. If you have right access, then navigate to API Center > OData API Data Dictionary. Example 2: Upsert Multiple Records of an Effective Dated Entity. Click an SAP SuccessFactors connection type tile for your source. Build an application powered by SAP SuccessFactors and Cloud SDK. A global, cloud-based human resource management software system, evolving to help people and businesses thrive in the experience economy. You are trying to upsert records in parent/child entities using inline / associations of OData entities (like EC and MDF, MDF to MDF, etc). User Assistance Overview Product Page for SAP Cloud Platform Integration. Some OData services (e. SAP SuccessFactors HXM Core all versions. 0) and for Access token as “access_token” as followed in the RFC-7522 specification. This Workflow has only one. 2800150 – How to test OAuth authentication via Postman. In SuccessFactors OData v2 adapter Processing properties, the TodoEntryV2 entity/api has been modeled with Query operation. While SuccessFactors OData feed can be contacted using the "/odata/v2" URL extension, PBI will register invalid metadata errors: "OData: the feed's metadata document appears to be invalid. Only enter the host name of server. 8 In the same permissions box, go to User Permissions -> Employee Data and review the attributes that the service account can read from the. Supported Operations. Proxy Type. More Info. Our CAP app consumed v2 OData services from SuccessFactors and provisioned v4 OData services which in turn were consumed by our freestyle UI5 apps. 0 provides a standards-based mechanism for Single Sign-On (SSO). This API can be used both by SuccessFactors/SAP module engineering teams, and by customers and partners for external integrations. 47. Assigned Tags. Click on Add app variable. Learning now features enhancements to the Learning Plan API to improve the experience for customers and partners in portal situations. In productive scenarios, the metadata seldom changes. With use of OData API, it provides with built on protocols like HTTP following the REST methodologies for data transfer. You may choose to manage your own preferences. If you can’t find it, please contact your system administrator. These support cases should be handled over to LOD-SF-INT-OUT component. You may choose to manage your own preferences. Creating API User IDs via Option 2. Symptom. The User entity has field-level permission control. Description. Even if it seems to make sense semantically, the API will not interpret it as a range. Properties and Navigation Properties. 2. Resolution. The example shows how you can use the SuccessFactors Upsert Snap to create new users and update data for existing users via the Foundation/Platform (PLT) - User API entity in the Success Factors Data Center. The Mule connector for SAP SuccessFactors provides full support to query, create, update, and delete entities using the ODATA API v2 exposed by SuccessFactors. Give the Application name as irpa_client and Application URL as 3. Registering Your OAuth2 Client Application. Prepare configuration on SCP Cloud. Your username is assigned to you by your organization. Note the OData API does not replace the SFAPI solution. While SuccessFactors OData feed can be contacted using the "/odata/v2" URL extension, PBI will register invalid metadata errors: "OData: the feed's metadata document appears to be invalid. SAP SuccessFactors HXM Suite OData API provides methods for create, read, update and delete operations. Use Case 2: Retrieve the Employment Records of All Candidates Created in Onboarding. In this hands-on video tutorial, Philip Mugglestone shows how to create a service instance to consume the SAP SuccessFactors OData API. SAP SuccessFactors Connector 4. If there are network issues, you enable the integration flow to retry connecting to the SuccessFactors OData V2 service. Related Information. Data Integration. Error: The metadata document could not be. This may seem backwards, listing all the secondary assignments rather than just the primary one, but that is the way it is stored. We can see under the CPI message processing the. An easy way to get external data to be made available within the Data Warehouse Cloud, is. There are two ways to retrieve OData metadata in SAP SuccessFactors HXM Suite:. In Azure, install the "SAP SuccessFactors" Enterprise Application, which will generate SAML Assertion. This query will fetch all the 8 different dimension photos. The Upsert operation is an SAP SuccessFactors function import to update or insert records. Get access to your organization’s Success Factors Instance. Choose Internet. Our SAP SuccessFactors Connector delivers metadata information based on established standards that allow Power BI to identify data fields as text, numerical, location, date/time data, and more, to help BI tools generate meaningful charts and reports. Then, we tested this by making OData API call for getting metadata of this entity using Postman tool and could see this newly added. VMS using a web services call and then uses this data to create contingent workers in Employee Central via an OData API web services call. Only enter the. Related Information. General guidelines about OData v2 APIs in SAP SuccessFactors HXM Suite, including general permissions, authentication, metadata, query and edit operations, as well as how. -----FIRST: QUERY =. You can use below references to know more about SFSF Adapter and Query Modeler. Click on the under the Main Data Source heading. This is a collection of the most useful SAP SuccessFactors Employee Central resources: documents, blogs, reports, and videos. If you specify the address field of the adapter as $ {header. Leveraging the Destination Service x. URL of the SuccessFactors data center that you want to connect to. SAP Help Portal The OData Query will return you with a list of Countries that are configured in your SuccessFactors instance like in the above screenshot. This then ensures that under Name, you only see the entities. DateTime and Edm. Once exposed, you can access the object through OData API calls. It also allows user to search an API and build & execute oData query. The APIs are based on the ODATA protocol and offer methods for CRUD (Create,. Image/data in this KBA is from SAP internal systems, sample data, or demo systems. SAP SuccessFactors technology supports the full range of talent processes for your HR professionals, managers, and employees, but can be leveraged to create talent processes to allow you to detect. SAP SuccessFactors HXM Suite; OData API; Cause. 1. Access SAP SuccessFactors data like you would a database - read, write, and update SAP SuccessFactors Benefits, Compensation, Jobs, etc. In this hands-on video tutorial, Philip Mugglestone shows how to create a service instance to consume the SAP SuccessFactors OData API. To find right OData end point URL for your SuccessFactors instance refer this link. Click on File -> New SOAP Project. By default, Server-Side Pagination is selected and as per the requirements, you can select the appropriate pagination type. a}, the value of a header or an exchange property (from the incoming message) is written into Camel header CamelDestinationOverrideUrl at runtime. Admin Center > API Center. Search for additional results. p: SAP Business Accelerator Hub: A resource portal where you can find the specifications of all APIs offered by SAP and try them out in your own environment. I will refer to this extension through. To see the Goal for other employees it is necessary to include in the filters the userid, example. Supported Operations. 2251702. Admin Username – Enter the username of the SuccessFactors API user account, with the company ID appended. through a. Related Information. The API provides a REST based web service following the OData protocol. So, we arrived at the last and critical part of the scenario, to trigger save rule while updating pay component information via ODATA API call. Click more to access the full version on SAP for Me (Login required). You can dynamically configure the address field of the SOAP (SOAP 1. Step 1: Upload the transport request files. 1. Suggested reading: OData V2 Refresh Cache On. This article describes the steps on how to perform ODATA API queries and upsert requests via Postman. Suggested reading: OData V2 Refresh Cache On Expiry To set up OAuth authentication, you need to complete the following procedures: 1. ,] - SAP Successfactors Odata APISuccessFactors come with API Centre which has OData API Data Dictionary where you will find the entities of all the SuccessFactors modules. Although the query's semantic structure suggests the following logic: IF ANY of the employee's records. Will try to explain with one use case or API. 3) Register subaccount as OAuth client in SuccessFactors. About SAP SuccessFactors OData APIs (V2) Authentication Restricting Access HTTP Basic Authentication (Deprecated) Authentication Using OAuth 2. I can get only 1000 rows in one JSON file (default limitation). 18, which is aimed to reduce the time taken between SAP Cloud Integration and SAP SuccessFactors endpoint HTTP communication through zip stream over the network. Retrieve a single entity by. What are Web Services? 1. Use Case 1: Get Email Addresses by Specific Criteria. SAP SuccessFactors Employee Central is a flexible, global core HR solution that supports core HR processes and employee self-services for your total workforce. 4. Admin password – Enter the password of the SuccessFactors API user account. This is part of a larger SAP SuccessFactors HXM Suite – Useful Resources and Documents collection. Also note, I’ve mentioned “BINARY CODE” for the field “photo” which will contain the actual base64 encoded binary code. This article describes the process on how one can access SuccessFactors OData APIs from an ABAP program using the OAuth 2. This. 0 section in the SAP SuccessFactors HXM Suite OData API: Developer Guide (V2) There are 3 ways to. Environment. The entity contains information. SuccessFactors OData adapter uses a cache to store the service metadata refreshed every hour. There are two entities which can store the HR Manager of a user: User; EmpJobRelationships. For more information about OData API configurations, see the SuccessFactors HCM Suite OData API Programmer's Guide Note Currently, location data is fetched via OData API. To set up connection between the service and SAP SuccessFactors, you need to set up OAuth Authentication in SAP SuccessFactors. Configure and use your SAP SuccessFactors solutions to reduce biases and embed diversity, inclusion, and equity directly into your HR processes. 2. DateTime and Edm. Description Web Service 1. From the Admin menu, click on Manage OAuth2 Client Applications ->Register New Client Application. Creating User IDs via Option 1 (Provisioning) 14. . x comes with addition of OData V4 outbound/receiver adapter. Error: The metadata document could not be. For this Go to the Admin Center->Manage OAuth2 Client Applications-> Register. OData (Open Data Protocol) is an ISO/IEC approved, OASIS standard that defines a set of best practices for building and consuming RESTful APIs. How artificial intelligence and machine learning can be used throughout the recruiting process. The value of sf. 0. More Info. select Services > Service Marketplace, and on the right-side search for SAP SuccessFactors Extensibility and select it; Click on Create in the next window and add the following settings Service: SAP SuccessFactors Extensibility. Entity Relation Diagram. Click Load to establish the connection to your SAP SuccessFactors data from Power BI. Image/data in this KBA is from SAP internal systems, sample data, or. SAP SuccessFactors Recruiting Management. Use Case 2: Add a New Employee. A global, cloud-based human resource management software system, evolving to help people and businesses thrive in the experience economy. Admin Username – Enter the username of the SuccessFactors API user account, with the company ID appended. if you want to use OAuth2SAMLBearerAssertion for authentication type then refer this blog, for detailed configuration steps to create OAuth client key in SuccessFactors instance. OData (Open Data Protocol) is built on protocols like HTTP following the REST methodologies for data transfer. 1. There are two ways to retrieve OData metadata in SAP SuccessFactors HXM Suite: The OData API Data Dictionary tool in API Center provides a user-friendly view of OData metadata. Navigate to next tab Processing and click on Select Button next to Resource. Different touch points for API:Click Here to access the SuccessFactors OData API Developer Guide Keywords OData, Developer, Guide, API, Data, Dictionary, O, Entity , KBA , LOD-SF-INT-ODATA , OData API Framework , LOD-SF-RCM-API , Webservices & APIs , How ToThis guide focuses on OData version 2. Software Version; Mule. SAP SuccessFactors Documentation on OData APIs can be. Personal and employment details for employees, referred to as Person Objects and Employment Objects. When you start developing extension application for SuccessFactors, the thing you need to remember is that your OData endpoint URLs for accessing the OData. 16. You can find detailed information about the SuccessFactors OData V2 API on SAP Business Accelerator Hub. The scenario includes highlighting the location of US-based candidates on an interactive map: It also covers how to trigger and process. 0. If you want to use location data, you must configure the OData API. Register the service in the SAP SuccessFactors system. Proxy. In OData v4, you can use the PATCH HTTP method to merge records. In case of SuccessFactors OData -V4 we dont have that luxury. SAP Knowledge Base Article - Preview. . The CompoundEmployee API is based on the Simple Object Access Protocol (SOAP). • SAP SuccessFactors will roll out network changes across all Datacenters. While SuccessFactors OData feed can be contacted using the "/odata/v2" URL extension, PBI will register invalid metadata errors: "OData: the feed's metadata document appears to be invalid. Enter the URL of the SAP SuccessFactors OData API you want to consume. When creating connection using OAuth, your Authorization Code. SAP SuccessFactors uses the terminology for Authorization token as “Assertion” (SAML2. Connection Details URL : Enter the OData service provider URL of the SAP SuccessFactors service that you want to access. HTTP Basic Authentication (Basic Auth) is an authentication method used to access APIs in SAP SuccessFactors. Add destinations in HCP for SAP Successfactors & 3 rd party application. You can build a API query to retrieve the goals, but the system will return by default your own user goal (it will not return the Goals of all employees). You can use the OData APIs to generate access tokens for OAuth 2. 1. Supports SAP-proprietary function import /odata/v2/upsert with HTTP method POST. The SAP SuccessFactors HXM Suite OData API is a Web Service API feature based on the OData protocol. Copy the data files to the DIR_TRANS /data folder. Use search and filter to find the corresponding servers for your company. Admin password – Enter the password of the SuccessFactors API user account. In successfactors Odata autdit log, we can see HTTP request like this. Only enter the. Complete the configure connection properties. Any resemblance to real data is purely coincidental. OAuth2, CPI, SAP Cloud Integration, OData, SAP Cloud Integration – OAuth2 SAML Bearer/X. Now Generate X509 certificate. And the response body (3) is exactly the response body from LMS API. OData Recruiting Management API Resolution Click Here to access the SuccessFactors OData API Developer Guide Keywords OData, Developer, Guide, API, Data, Dictionary,. privacy statement, for purposes that may include site operation, analytics, enhanced user experience, or advertising. 2253200 - How to add in allow list an IP for API access in SuccessFactors OData or SFAPI; You are able to safely provide the credentials of the API user in an case using the Secure Area. Hello SAP community, With the 2H 2020 Release of SAP SuccessFactors application, we are announcing the sunset (planned retirement) of HTTP Basic Authentication for API calls (both SFAPI & OData). The Open Data Protocol (OData) is a standardized protocol for creating and consuming data APIs. The OData API Data Dictionary tool in API Center provides a user-friendly view of OData metadata. SAP Online HelpIn this example, the user logs in to a sender app to fetch tasks retrieved from an SAP SuccessFactors system (which, in OAuth terms, contains the protected resources). Version : Displays the OData version used to implement the SAP SuccessFactors OData. amazonaws. You're upserting a new EmpCompensation record (Compensation Information time slice) via OData API for a given user; After the upsert, you verify the user's new compensation record and observe that apart from having the pay components specified in the upsert, it has also inherited the same pay components from the previous time slice;Each line of the file has multiple fields with the 10 th field being Employee Id, for which we need to fetch corresponding CostCenter (in actual scenario it can be multiple other fields like Company, payscaleArea etc. A New Home in New Year for SAP Community: Exciting times ahead for the SAP Community!8. OData v2 uses HTTP method POST and HTTP header X-HTTP-METHOD: MERGE to merge records. The term technical user or non-RBP usually is the same as Admin Mode. To celebrate this most recent release, here’s SuccessFactors Onboarding look at some of the most interesting features and changes introduced since last time. This enables authentication for OData API Access using OAuth 2. In the Authentication select Oauth2 Saml Bearer Assertion and in the Credential Name enter the alias name of the Security material of type Oauth2SAMLBearer created in section 9 Differences Between OData v2 and v4. 0 MDF entities, and Onboarding entities. User Insert, apiOptionProfileID, processInactiveEmployees , KBA , LOD-SF-INT-ODATA , OData API Framework , LOD-SF-INT , Integrations , How ToIt's now 2021 and a properly functioning OData connector in Power BI seems to still be outstanding. SAP SuccessFactors. 0 Client API. Connection Details URL : Enter the OData service provider URL of the SAP SuccessFactors service that you want to access. WFS requires data a week before it’s go live to set up the time profiles, and hence, we shall have EC going. successfactors. In the upcoming releases, we will be supporting some more features and blog for the same will be updated. OData API v2. The workflow Manager_approval is attached to the above MDF.