SuccessFactors Recruiting. 509-based authentication with SAP SFSF IC, ISC and CPI. A global, cloud-based human resource management software system, evolving to help people and businesses thrive in the experience economy. 509 certificate. Example 2: Upsert Multiple Records of an Effective Dated Entity. 13. Both SHA-2 and SHA-1 signing algorithms are supported. Properties and Navigation Properties. Integration Overview- Technical. Admin Username – Enter the username of the SuccessFactors API user account, with the company ID appended. SAP SuccessFactors HXM Suite OData API: Developer Guide. The SuccessFactors activities. 1 – Indicates that SAP SuccessFactors HCM Suite OData API (in short, OData API) is used. It has the format: username@companyID. The HR organization can build value-based relationships with everyone supporting the business – engaging permanent and. The images that follow are not complete but show a representation of some of the most important entities and their relationships within the Employee Central OData Structure. Please take note and update your bookmarks. I know I am reopening an old one (Perform filter on expanded entity with SAP Cloud SDK), but it was a while ago and was referencing the Java version of the API used to consume an S/4 HANA service. 6 PUBLIC SAP SuccessFactors Learning OData APIs Change HistorySAP SuccessFactors Visa and Permits Management enables the administration of workforce visas and permits, helping companies ensure local compliance and support international expansion. Build a new Spring application. To integrate and automate SuccessFactors, Magic xpi Integration Platform leverages the Open Data Protocol (OData) which is a standardized protocol for creating. The OData API is a solution with allows to export, create and update operations in the Recruiting Module. Use the generated token to call APIs. The OData API Data Dictionary tool in API Center provides a user-friendly view of OData metadata. SAP SuccessFactors OData service supports a custom OData function called UPSERT. 1. You can use the dictionary to look up EntitySets, Complex Types, and Function Imports that are. OData API (V2) is by default enabled in Provisioning ("SF Web Service" switch under "Web Services" section). Here you need to pass the API Key in the payload and do an API call which is not secure. Copy SAP SuccessFactors EmployeeCentral Personal Information API. Description. Use the Position entity to query position details, create, and edit positions. For more information on general OData API operations, refer to. This document will walk you through the simple steps to test connection with SuccessFactors and extract some data. Make any changes in the Host Alias, API Base Path, if applicable, and. Login to the Postman to construct the ODATA API call. g. Resolution : – Consider below example of an employee in SuccessFactors. SAP Online Help For more information, see the Authentication Using OAuth 2. The API center is a one-stop shop for accessing OData API tools. OData is the only API available in Integration Center. 0 MDF entities, and Onboarding entities. Step 2: Navigate to Admin Center and open Employee Export from Tools Search bar. You can find the content at the new location: About SAP SuccessFactors OData APIs (V2). It is an alternate integration. SAP SuccessFactors. Each to-do task may also be shown in several other places, such as the home page or SAP Task Center. Setup the application. While the majority of MDF OData API operations follow the same rules defined by the framework, there are patterns specific to MDF when you use MDF. (Optional) Check whether your access token has expired or not. Make sure the client IP address is also allowed in the setting. API to access 360 Reviews forms. Download PDF. In this blog, I will walk you through the step-by-step process of uploading the attachments in the success factors system using OData API. This KB article explains what OData API is and what possibilities it offers when in use with the Recruiting Management Module. LMS Modularization and URL Pattern 2. Pre-Read: Migrating SAP SuccessFactors API Calls from. Make sure you understand how to use the ODATA API Data Dictionary and the integration tools in general. Development and Deployment Flexibility. I have chosen Products and Suppliers (without Address fieds)2735876 - Successfactors Odata API Best Practices [Query Modified Records, Pagination - Batch Size, Timeouts, etc. 1) Create employment info (OData API upsert in the EmpEmployment) with the same person ID but with a different user ID. The Third-Party OData API integration explains what it takes to make an external application ready for integration with SAP Jam Collaboration. (1) Retrieve Employee Photo from SuccessFactors using OData API. SAP Help PortalThe OData API is a solution with allows to export, create and update operations in the Recruiting Module. Procedure. This's an open-source OData Desktop client built specially for SF OData with . In Admin Center, the tool is called SFAPI Data Dictionary, but in API Center, it is called Legacy SFAPI Data Dictionary. SAP SuccessFactors HXM Suite OData API: Developer Guide (V2) SAP SuccessFactors HXM Suite SFAPI: Developer Guide. Please don't use SOAP APIs or Ad hoc APIs for building new integrations in Employee Central. This video tells about the new course published on Udemy over SAP Successfactors Compound Employee API, which is a very robust and proven methodology for inn. You can use this function import to send pending offer letters to a candidate. The Main components/systems needed are, 1. On the Reconciliation Field Mappings tab of the process definition, click Add Field Map. In this hands-on video tutorial, Philip Mugglestone shows how to create a service instance to consume the SAP SuccessFactors OData API. OData API can return a maximum number of 1000 records in a single page. Read more. Step 5: In auto discovery mode click “Verify”. version property controls which API you use. SAP Help PortalThis KBA provides information about Successfactors Odata API Recommended Usage and Best Practices SAP Knowledge Base Article - Preview 2735876 - Odata API Best Practices [Query Modified Records, Pagination - Batch Size, Timeouts, etc. 2. Consider reimplementing integrations using Integration Center. The SAP SuccessFactors HXM Suite is an evolved, cloud-based human resources management system (HRMS) with a focus on engagement and. 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. Refer to the SAP SuccessFactors HXM Suite OData API: Developer Guide (V2) on how to work with oData APIs in SAP SuccessFactors. Make any changes in the Host Alias, API Base Path, if applicable, and. Creating API User IDs via Option 2. The HXM Suite OData API is SuccessFactors Web Services API based on OData protocol intended to enable access to data in the SuccessFactors system. Pre. To view the timezone information of an API server, go to your company login page or open your account on the header bar after login, and choose Show version information. The SAP SuccessFactors HXM Suite OData API is a Web Service API feature based on the OData protocol. 2 Create a scope (in this example it is called dummyScope) 5. If you do not have an SAP ID, you can create one for free from the login page. 0. The SFAPI is SuccessFactors Data API. Query a list of user form folders. You would like to update Dynamic Groups using SuccessFactors OData API. Related Information. For any Attachment to upsert into Successfactors OData API, we should have to do this through Attachment OData API. OData API Audit Log. Use the OData API Audit Log to monitor OData API calls to Employee Central. Note that only MDF-specific information is documented here. SuccessFactors; BizX; Web Client; Product. Related Information This guide provides information specific to the latest version (v4) of OData APIs in SAP SuccessFactors HXM Suite. Creating API User IDs Option 2. Metadata . If this is the option you need to adopt you might consider using the SAP API Management’s SuccessFactor connectivity policy. Employee Central Entities and Interfacing. Note: The templateId has to be replaced with the actual values that you have in your instance. Then, you define a namespace to contain the service definition. Related Information. The templateId is the ID of the Job Requisition template that will be used in creating the requisition. Under Application. You'll find the API Center in the Admin Center. Operation. Informatica Support Guide and Statements, Quick Start Guides, and Cloud Product Description Schedule. We're excited to announce a major change to our API documentation with the 1H 2023 Release: we've merged OData API developer and reference guides into single comprehensive guides for both OData v2 and v4. Select Data Source Type as ODATA, Browse the Edmx file saved in step 2. If you do not have an SAP ID, you can create one for free from the login page. privacy statement, for purposes that may include site operation, analytics, enhanced user experience, or advertising. Admin password – Enter the password of the SuccessFactors API user account. SuccessFactors has two API Data Dictionaries: The ODATA API Dictionary does not mirror Ad Hoc Reports. 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 advertising. SuccessFactors OData API query, Historical records missing in the response, Employee Central (EC) effective dated entities behavior, toDate, fromDate, Latest record , KBA ,. But What it is ODATA? 1. Use Case 1: Query the Basic Information of an Objective. This is also the reason why the SAP SuccessFactors reference and developer guide have new URLs mentioned SAP SuccessFactors API Server URLs. They are fully ready to be imported to the external provider system that needs synchronized data with SAP SuccessFactors applications. Every to-do task is shown in the to-do panel. Philip creates a BTP subaccount and configures entitlements for the SAP SuccessFactors Extensibility service. 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. You can set the logging for both OData and SFAPI APIs. Normal users can only access the forms in their folders. Please notice that you will not need any OData API upsert in the OData. In the search bar at the top right of the. Only enter the. User Creation: We will take file based approach where we will export existing User Data and using the same temple will be creating new User ID required for our purpose. In this document we will review how the $top and $skip parameters work in the context of pagination in an OData API query. If you are unable to select a field in filters of Integration Center or OData API, navigate to OData API Data Dictionary tool and select the entity name. 0 Uri Conventions". privacy statement, for purposes that may include site operation, analytics, enhanced user experience, or advertising. Use the ‘Basic Auth’ tab to enter the credentials. Handling Special Characters . OAuth 2 authentication in your production environment you can refer to this link from the SAP SuccessFactors HXM Suite OData API: Developer Guide. SAP SuccessFactors HXM Suite OData API: Developer Guide (V4) Content Has Moved PUBLIC 3. Step 1: Log on to SuccessFactors as Administrator. UserSourceSystem to the User OData API. 0 authentication for inbound API calls to SAP SuccessFactors. Use the ‘Basic Auth’ tab to enter the. It contains the details of each entity that is accessible through the API, including fields, their names and labels, their data types, and the relationships (associations) between entities. It's intended to enable access to SAP SuccessFactors data in the. About the OData API Reference Guide (V4)Resource Description; SAP SuccessFactors HXM Suite OData API: Developer Guide (v2): General guidelines about OData v2 APIs in SAP SuccessFactors HXM Suite, including general permissions, authentication, metadata, query and edit operations, as well as how to use the API Center tool to help you get your way around OData APIs. Community Blog: Using x. API Gateway: Indicates that the response is from the API Gateway. Capabilities of SFSF Adapter. Information about installing, configuring, and running the Data Services Adapter SDK . You wish to know how to perform an isolated API call for the EmployeeTime object. There are three permission levels for querying OData API entities: Permission Level. SAP Help Portal The SAP SuccessFactors HXM Suite OData API: Reference Guide (Reference Guide) ODATA Data Model Example. HRIS Element Information. SAP SuccessFactors. You should receive the following message: Click on Close. Pagination limits the maximum size of a query response to 1,000 records. Find key information, best practices, and training for API and Integration. If you want to use location data, you must configure the OData API. To learn more about the OData System query options used in the example URIs in this section, visit and search for "OData Version 2. We show you what needs to be done (video 4), but this may require the involvement of an administrator. NET platform which includes URI parsing, request and response reading and writing, Entity Data Model (EDM) building, and also a . Discover and test SuccessFactors APIs and ready to use integration packages on the SAP API Business Hub ( SAP API Business Hub) Use the SAP Integration Suite to build powerful integrations with SuccessFactors or start for simple use cases with the SuccessFactors built. COE0005This blog is to demonstrate the steps to upsert an attachment in custom MDF through OData API. Create a Service Instance to consume the SAP SuccessFactors HXM Suite OData APIs. OData reference. SAP SuccessFactors. Access SFAPI Data Dictionary. JSMPlease find below the discount coupon (33% off!) for the course, only valid till August 27, 2022:Case 1: Query Job Information by Company and Manager. According to the SFAPI and OData guides, for both the Manager and Custom Manager hierarcies, the individual at the top of the employee hierarchy (e. User entity (this is created automatically after your OData API upsert in the EmpEmployment. Use built-in SAP SuccessFactors IdP SAML bearer assertion generation endpoint. 2735876 - Successfactors Odata API Best Practices [Query Modified Records, Pagination - Batch Size, Timeouts, etc. How effective-dating is handled in an OData API query The following rules are followed when an effective dated entity is queried: If both the base entity and the navigation entity are effective-dated, then when expanding the navigation entity, the effectiveStartDate of the base entity is used as the asOfDate of the navigation entity. 2735876-Odata API Best Practices [Query Modified Records,. How to use WSDLs in the SOAP Adapter. Testing SAP. For a list of the API Endpoint URL for the SAP SuccessFactors environments. Click on Check Connection. OData V2 Headers. Relationships, a key part of the entity model, are. Step 3: Go to Admin Center > Set up Interview Scheduling Outlook Integration. Integration Center as a package. Use Case 3: Delete an Employee Record. Community Blog: How to setup secure inbound connection with client certificates153 388 335,705. Field level. An example of a SFAPI is CompoundEmployee. Is this app in a private networkMDF Foundation Object entities are Employee Central Foundation Objects that have been migrated to the Metadata Framework (MDF) and exposed as OData API entities. Integration is done through a standard Cloud Integration package with Alight Exchange. Philip then creates a service instance using the api-access service plan and reviews. The SAP HANA Academy YouTube is scheduled to close on December 31, 2023. Enable OData VDM code generation. JSMPlease find below the discount coupon (33% off!) for the course, only valid till August 27, 2022:…Use Case 1: Query Job Information by Company and Manager. Both REST and OData adhere to web-based architecture, statelessness, data format flexibility, resource-oriented design, and interoperability. Furthermore, it also covers known restrictions and limitations. 1. Parameters. The values supported to check for rehire are first name, last name, date of birth, and national ID details. Use /oauth/idp to pass a private key to generate a signed SAML assertion. An assignment ID is an identifier assigned to the work relationship between a person and the company. For starters, the OData endpoint details are pre-filled based on. Integration Center as a package. SAP SuccessFactors HXM Suite all versions ; SAP SuccessFactors Performance & Goals all versions Keywords API, Manager Transfer, Option Profile, Performance Managerment, Document Visibility. Specify export option Short format: only system fields. The following example I specify the user ID and photo type – 1 (Live Profile picture) for testing purpose. Service to fetch or update the internal username of the new hires after completing the hiring process. OData provides both a standard for how to represent your data and a metadata method to describe. Please do not use the API Key to generate SAML assertion. There is no risk of a scheduler being backed up, etc. Keywords. This includes links that will cover an introduction to SAP SuccessFactors, the acquisition by SAP, SAP’s strategy, the SAP SuccessFactors HXM suite, integration, and other related documents and. SAP SuccessFactors HXM Suite OData API: Reference Guide (V2) Content Has Moved PUBLIC 3. A common assumption is that the user’s remote resource access scope will be determined by the user’s identity as it is known on. ". SAP SuccessFactors is a leader in cloud-based Human Capital Management (HCM) software for talent management, core HR, and HR analytics. Search for any standard entity. Consider reimplementing integrations using Integration Center. Use Case 2: Update an Email Address. If necessary, move the XML file. 2. It has the format: username@companyID. - SAP SuccessFactors HCM Suite. The SAP Cloud for Customer OData API Developer’s Guide complements the SAP Cloud for Customer OData API Reference (a link will be provided later) with usage. The Open Data Protocol (OData) is a standardized protocol for creating and consuming data APIs. OData v4 enhances the entity model, adding support for containment, singletons, enums, and type definitions. Supported Operations. Step 3: SAP SuccessFactors HCM Suite OData API: Developer Guide 8 PUBLIC About HCM Suite OData APIs 3 Authentication Types for OData API. Swagger, swagger file, OpenAPI, 3rd party, down stream. 0. SAP Help PortalThe content of this guide has moved. 5 (SPS 05) Available Versions:. SAP Knowledge Base Article - Public Swagger file for SuccessFactors ODATA API You wish to know whether SAP SuccessFactors provide a Swagger file. • Unlike SFAPI-Adhoc, OData does not rely on creating and running reports on a scheduler server. For more information about querying OData Metadata, please go through this page of the official SuccessFactors OData Developer Guide: Retrieving Metadata. You will find integrations are easier to develop. You may choose to manage your own preferences. 1 - Mule 4. API to access 360 Reviews forms. Query and manage public sector cost object. Go to Admin Center API Center OAuth Configuration for OData and choose Register Client Application. Community Blog: How to setup secure inbound connection with client certificates 153 388 335,705. Setup and run a mock server test. 2 – Indicates that SAP SuccessFactors Workforce SCIM API (in short, SCIM API) is used. Figure 7 – Check Connection. SuccessFactors Learning. Each service instance will result in creating: a separate OAuth2 client application on SFSF side and. Community Blog: Using x. Please refer to the Authentication Using OAuth 2. SuccessFactors is a collection of various entities, and the connection to SF is always based on an Entity, regardless of whether you access it as an OData source or through the native connection. It is a simple mapping that loads data from flat file to SAP. Please check out more details like overview, Frequently asked questions FAQ in the Customer Community blog or the Partner Delivery Community blog. When OData receives this value, it converts it to 2014-04-22T18:10:10, and stores it in database. You can find the content at the new location: About SAP SuccessFactors OData APIs (V2). Use Case 2: Update Job Related Information. Use /oauth/validate to pass the access token to the API and verify that it’s still valid. Structure - The structure of the entities and properties in the ODATA API is a little different from SFAPI which is now. API Servers. How to initiate an OAuth connection to SuccessFactors Employee Central? To learn how to setup OAuth 2 authentication in your production environment you can refer to this link from the SAP SuccessFactors HXM Suite OData API: Developer Guide. The User entity exposes every <standard-element> and <userinfo-element> field that appears in the Succession Data Model. SFAPI is SuccessFactors web-service to import or export data to or from SuccessFactors. privacy statement, for purposes that may include site operation, analytics, enhanced user experience, or advertising. It is updated/refreshed whenever new feature and/or. Steps to Download Odata API Audit Logs: Login to the SF instance-> Admin center -> Tool Search-> Odata API Audit log. npm i -g generator-saphanaacademy-odata. Use Case 4: Upsert Job Information of an Employee with Multiple User IDs. The generated IDs are used in the User entity (fields: username and userID ), PerPerson entity (field: personIdExternal, userID. 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. You use this API to generate the next person ID assigned for a new hire, incrementing it as required. An assignment ID is an identifier assigned to the work relationship between a person and the company. These. What are Web Services? 1. Use Case 3: Delete an Employee Record. A modified URL can lead to unexpected results. Viewing and Updating the Temporary Time Information Once the upload is complete, you can view the newly uploaded temporary time information records on the Work Schedule tab of the Time Workbench. In this blog, I will walk you through the step-by-step process of uploading the attachments in the success factors system using OData API. Here you need to pass the API Key in the payload and do an API call which is not secure. 1. SAP SuccessFactors Employee Central OData API: Reference Guide. The API provides a REST based web service following the OData protocol. Select the edit option as we plan to use the same account for the Writeback to SuccessFactors scenario. There are two ways to retrieve OData metadata in SAP SuccessFactors HXM Suite:. The OAuth 2. This article explains how to enable settings in your Success Factors System for Manager Transfer for an OData API call. Here are the quick decision points on the advantages of using SAP SuccessFactors Integration tools: SAP SuccessFactors Integration tools provide dedicated adapter out of the box. Related Information. The OData API provides two types of authentication: HTTP Basic Authentication (Basic Auth) and. In the Tools search field, enter Employee Export. Note : Subscribe to SAP SuccessFactors HCM Suite OData API: Developer Guide. Use Case 2: Creating a Position with Insert. This value is prefilled based on the instance of the company currently logged in. API Center. 2 SFAPI Audit Log. 4 5. You will find integrations are easier to develop. Figure 7 – Check Connection. Use Case: Send Pending Offer to a Candidate. • The. Query and manage public sector cost object. 2:30 – Run the yo command and select Saphanaacademy Odata template: enter the app name, SAP HANA Cloud endpoint, database user, password, schema, OData v2 support, authentication and authorization, build and deploy. Additional parameters can be found in the SAP SuccessFactors HCM Suite OData API: Reference Guide document. 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. The relationship could be an employment relationship, contingent relationship, pensioner relationship, intern, global assignment. Pre. The following documentation can be also found on the SAP Help Portal under SAP SuccessFactors Release Information, quick links to the "What's New" section in each document can be found below for the latest release. SAP SuccessFactors HXM Suite OData API: Developer Guide (V4) Content Has Moved PUBLIC 3. Open the created artifact in Edit mode, choose Import Model Wizard. To view the timezone information of an API server, go to your company login page or open your account on the header bar after login, and choose Show version. g. You may choose to manage your own preferences. SAP SuccessFactors Employee Central OData API: Reference Guide (Permission Settings Section) 2732680 - USER x ADMIN permission modes - SuccessFactors OData API Permissions; Keywords. It defaults to &asOfDate=<today's date>. Find out the access limits of OData v2 APIs in SAP SuccessFactors HXM Suite. 2 – Indicates that SAP SuccessFactors Workforce SCIM API (in short, SCIM API) is used. 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. SAP SuccessFactors, ServiceNow, and SAP Integration Suite need to be configured and prepared before the integration content package can be configured and deployed. csv: The API Subversion is showed on. Open Developer’s Guide available. Copy SAP SuccessFactors EmployeeCentral Personal Information API. Related Information. You can find this in provisioning. Free essays, homework help, flashcards, research papers, book reports, term papers, history, science, politicsPass your SAML assertion and API key (in the client_id field) along with other information to generate an OAuth token. About SAP SuccessFactors OData APIs (V2) Authentication . Use search and filter to find the corresponding servers for your company. You can use tools such as OpenSSL to create a self-signed X. 0 protocol. SAP SuccessFactors Recruiting Management. 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 advertising. Now look for the corresponding field value under sap:filterable column, you'll be able to confirm if the field is filterable or not (it will show filterable=true/false):SAP SuccessFactors API Reference Guide (OData V2) This document. SAP SuccessFactors offers a comprehensive set of Role Based Permission (RBP) APIs based on OData V2. Once done, click on Refresh Headers which adds the Base64 format of header to your request. Step 1. Other records not fetched via SFAPI EmpJob SOAP API issue , KBA. Product. The User entity exposes every <standard-element> and <userinfo-element> field that appears in the Succession Data Model. Hint: In some cases it might be required to refresh the OData API metadata after creating the object before a first successful API call. When you want to connect to the Successfactors APIs you could use Basic Authentication to access the SFSF OData API or OAuth. If you choose Atom as the format of your query response and the __next URL contains an ampersand, the link doesn't work because the server doesn't recognize. This often happens if the authentication fails in API Gateway. If your system cannot consume either OData APIs or SOAP for an initial data load, then you should consider importing and exporting employee data using a CSV. 2. Enter API endpoint. Producing the XML file from the SuccessFactors system. Hi Yves, As mentioned in the blog, the value for Common Name (CN) should be the username that exists in your SAP SuccessFactors instance who has the access/authority to invoke the SuccessFactors API through OAuth2 token, don't append the company ID. About the OData API Reference Guide \(V4\) API UPSERT call to EmployeeTime. This permission allows user to view data sent in every SFAPI call. How effective-dating is handled in an OData API query The following rules are followed when an effective dated entity is queried: If both the base entity and the navigation entity are effective-dated, then when expanding the navigation entity, the effectiveStartDate of the base entity is used as the asOfDate of the navigation entity. Go to Admin Center > Import and Export Data (use the tool search): On Monitor Job, it is possible to verify if the export was done: Click on Download Status to download the export (This link is on the last column from the table on step 7); After download, open the . 5. Viewing and Updating the Temporary Time Information Once the upload is complete, you can view the newly uploaded temporary time information records on the Work Schedule tab of the Time Workbench. Description. The operation-level permission checks whether the logged-in user can access the module to which the entities belong. Visit SAP Support Portal's SAP Notes and KBA Search. SAP SuccessFactors Recruiting. The User entity has field-level permission control. This document is the handbook for SFAPI developers. This guide provides information specific to the latest version (v4) of OData APIs in SAP SuccessFactors HXM Suite. The SFAPI Metering Details tool gives you analytics on your API usage up to the last 30 days. Principal Propagation with SuccessFactors OData V2. The OData standard provides a '__next' link in your query response if there are more results in the database. You are trying to build OData API queries in. The Implementation Guide provides instructions which will assist in the process of integrating data fromCheck SAP handbook for OData API SAP SuccessFactors HXM Suite OData API: Reference Guide (V2). MDF OData API is based on SAP SuccessFactors HXM Suite OData API framework, currently on OData Version 2. To fully understand how OData works in general or how OData v2 works in SAP SuccessFactors, refer to the 1) IDP SuccessFactors Integrations - Best Practices using SAP SuccessFactors APIs for Custom Integrations V1.