Make sure you understand how to use the ODATA API Data Dictionary and the integration tools in general. Recruiter initiates background check. Step 2: Create SAP SuccessFactors API User and Granting Permissions. SAP SuccessFactors HCM Suite OData API: Developer Guide SAP SuccessFactors Employee Central OData API: Reference Guide. 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. SAP SuccessFactors HXM Suite Boomi Connector Guide. This KBA provides information about Successfactors Odata API Recommended Usage and Best Practices. • Unlike SFAPI-Adhoc, OData does not rely on creating and running reports on a scheduler server. Go to Admin Center API Center Audit Log Settings and turn on audit logs for SFAPI or OData API using the following options: Option. For Boomi developments, the recommendation from SAP is to use the SuccessFactors Partner Connector (ready to use OData and SFAPI with OAuth2) and. privacy statement, for purposes that may include site operation, analytics, enhanced user experience, or advertising. From the Field Name list, select the field that you want to map. Login to the Postman to construct the ODATA API call. : SAP. Please take note and update your bookmarks accordingly. To learn more about the OData System query options used in the example URIs in this section, visit and search for "OData Version 2. The OData operations supported by the SFSF adapter are Query, Read, Create, Update, Merge & Delete. Use Case 1: Query the Basic Information of an Objective. There is an API Option Profile which can configure manager transfer options and is used for OData API. This change makes it easier for you to find the information you need and get started with our APIs. The OData metadata describes the capabilities of the API in your SAP SuccessFactors HXM Suite instance. Abstract: As per the 2H 2020 announcement: Planned Retirement of HTTP Basic Authentication (SFAPI/ODATA API) , all the productized integrations built by SAP SuccessFactors is now updated with secure OAuth2. When OData receives this value, it converts it to 2014-04-22T18:10:10, and stores it in database. 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. This article describes the process on how one can access SuccessFactors OData APIs from an ABAP program using the OAuth 2. And the response body (3) is exactly the response body from LMS API. 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. If input date is 2014-4. Description. The API Business Hub is growing every day with new APIs from SAP and our Partners. 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. The Photo entity is used for retrieving employee photos. Here you need to pass the API Key in the payload and do an API call which is not secure. Error: The metadata document could not be. 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. This is also the reason why the SAP SuccessFactors reference and developer guide have new URLs mentioned SAP SuccessFactors API Server URLs. The SFAPI is SuccessFactors Data API. It has the format: username@companyID. 0, including Onboarding 1. 2) Create job information (OData API upsert in the EmpJob). For example, your SAP SuccessFactors instance may be having a. You wish to know how to perform an isolated API call for the EmployeeTime object. You may choose to manage your own preferences. - SAP SuccessFactors HCM Suite. All you need to do is create a definition of your destination Your destination will be called by the destination service find api any time you need to procure a bearer. SAP SuccessFactors HXM Suite provides a variety of OData APIs for customers to build their extensions and integrations. Under Application. SAP SuccessFactors tools are always kept up to date with technology roadmap as SAP SuccessFactors enhances the Integration. Setting the Passwords for the API User IDs created above. This would affect SFAPI/ODATA/REST API endpoints across all datacenters. 2. One of the critical parts of HR Management is dealing with the required attachments, this includes resumes, offer letters, confirmation letters, payslips, appraisal letters, tax certificates, etc. link - SAP SuccessFactors HXM Suite OData API: Reference Guide; link - SAP SuccessFactors Employee Central OData API: Reference Guide; link - SAP SuccessFactors HXM Suite OData API: Developer Guide; link - SAP SuccessFactors HXM Suite SFAPI: Developer Guide; link - Implementing the Employee Central. Product. Query Operations . Consider reimplementing integrations using Integration Center. This latest record does not match with this query statement. Embedding & Extending with Developer APIs - Motivation. 16. SFAPI also follows the API login exceptions set on the Password & Login Policy Settings page. Request. 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. privacy statement, for purposes that may include site operation, analytics, enhanced user experience, or advertising. Both SHA-2 and SHA-1 signing algorithms are supported. 2:00 – open Terminal and install a Yeoman generator. For integration configuration and implementation, it’s important to assess up front the resources and skillsets required. Community Blog: Using x. . Note that only MDF-specific information is documented here. Use Case: Send Pending Offer to a Candidate. This is a collection of the most useful SAP SuccessFactors resources: documents, blogs, reports, and videos. Access SFAPI Data Dictionary. The files generated in the Integration Center are directed to a configured SFTP server location. Find out the access limits of OData v2 APIs in SAP SuccessFactors HXM Suite. Setting up users for Successfactors OData API usage user, create, set up, setup, provisioning, SFAPI, user created, configure, configuration,. Field level. It is a SOAP Web Service designed for importing and exporting data Manage User API Options: The User entity allows you to specify a few processing parameters to control extra business logic that can be optionally applied when you edit a user either using API or Import Employee option. You would like to know if there is a limit for multiple single calls from a third party system to a single SuccessFactors end-point, before the SF server crashes and/or closes the connection (maybe to prevent a hacker attack). Double-click the Process Data Field field, and then select the column for. Getting Started In the first video, we see the end result of the our efforts: a web application hosted in the SAP Cloud Platform Cloud Foundry environment that. About SAP SuccessFactors OData APIs \(V2\) privacy statement, for purposes that may include site operation, analytics, enhanced user experience, or advertising. 6. Integration Overview- Technical. Configure People Profile. When you query an effective-dated entity without any date parameters, the result returns a single record effective on the present date. Adhoc Entities – The adapter enables querying Adhoc entities from SuccessFactors system. OData API, query execution, Running API query on the browser , KBA , LOD-SF-INT-ODATA , OData API. Search for additional results. Creating API User IDs Option 2. OData API Performance Optimization Recommendations: Tune your batch requests into proper sizes, The OData API can return a maximum number of 1000 records in a single page. In the Tools search field, enter Employee Export. Usually it follows the format:. 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. If you've already registered, sign in. 2. 2 Failed to load resource while consuming OData service. Insert. 0 Client API. Admin password – Enter the password of the SuccessFactors API user account. An example of a SFAPI is CompoundEmployee. Structure - The structure of the entities and properties in the ODATA API is a little different from SFAPI which is now. privacy statement, for purposes that may include site operation, analytics, enhanced user experience, or advertising. Changing these to "true" or "false" from the standard is not possible as these are standard fields. Here's a list of API servers and mTLS certificate servers for SAP SuccessFactors data centers. Swagger, swagger file, OpenAPI, 3rd party, down stream, downstream , KBA , LOD-SF-INT-ODATA , OData API Framework , LOD-SF-INT , Integrations , How To . Integration Center is. Supported Operations. OData API Audit Log. You can try making a separate query on the EmpJob Odata query using the fromDate parameter and lastmodifiedDate and then add it to a cache. Use the OData API Audit Log to monitor OData API calls to Employee Central. You can find the content at the new location: About SAP SuccessFactors OData APIs (V2). OData provides both a standard for how to represent your data and a metadata method to describe. The SuccessFactors OData API test system comes with a predefined set of users and data configured in READ ONLY mode. To enable the integration of your extension applications with the newly registered SFSF system, you need to first create a service instance of the corresponding service. This information can be used by integration as needed. It's now 2021 and a properly functioning OData connector in Power BI seems to still be outstanding. Disclaimer: Please note all the code snippets below are provided “as is”. Click on Close. Attachment is a generic API to upsert any. Operation. Date/Time data types have been reworked to include separate Date, TimeOfDay, Duration, and DateTimeOffset data types. 3 ODATA for SAP SuccessFactors Learning Application 1. Below is a list of available statuses and their meanings: Below is a list of available statuses and their meanings:Date and Time. Related Information. 4. 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. 0 can be found here: ODATA v2. The SuccessFactors activities. The operation-level permission checks whether the logged-in user can access the module to which the entities belong. 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. Log on to the SAP SuccessFactors Employee Central Admin Center as an Employee Central Administrator. 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. 2. All. The SFAPI is SuccessFactors Data API. From the search result, select ‘OData API Metadata Refresh and Export’. Use the ‘Basic Auth’ tab to enter the. 05-18-2023 11:44 AM. 13. If you do not have an SAP ID, you can create one for free from the login page. Please take note and update your bookmarks. SFAPIs are “legacy” APIs that existed before OData APIs. Add permissions as shown below to read using ODATA API and edit using ODATA API. SAP SuccessFactors Employee Central OData API: Reference Guide. Metadata . Use /odata/v2 to use the access token for authentication and access the OData APIs. 2. Use Case 1: Get Email Addresses by Specific Criteria. Properties and Navigation Properties. 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. I then configure the API server, and set its name and title. AS2 Sender Adapter with Best Effort Quality Of Service (QoS) OAuth2 Client Credentials Support in OData V2 Adapter. Hi, We have recently introduced a new custom field as per Business requirement in one of the SuccessFactors entity and provided access to 'Query' this object and also to make 'Upsert' operations through OData API calls. Access the SFAPI Audit Log. This often happens if the authentication fails in API Gateway. Integration Center as a package. The Third-Party OData API integration explains what it takes to make an external application ready for integration with SAP Jam Collaboration. Product SAP SuccessFactors HXM Suite all versions Keywords Setting up users for Successfactors OData API usage user, create, set up, setup, provisioning, SFAPI, user. Adapter SDK Guide. Query and manage public sector cost object Budget Period. Why ODATA? 1. Admin Username – Enter the username of the SuccessFactors API user account, with the company ID appended. Search for any standard entity. Choose Save. Go to Admin Center API Center OAuth Configuration for OData and choose Register Client Application. To integrate and automate SuccessFactors, Magic xpi Integration Platform leverages the Open Data Protocol (OData) which is a standardized protocol for creating. Click on Close. 2 SFAPI Audit Log. LMS WEB Services : ODATA 1. 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 resources. In order to get oData from success factors odata service, I'm trying to setting up a connection between SuccessFactors and SAP BTP by creating a destination as reported in this official guide. SAP SuccessFactors is a world-leading provider of cloud human experience management (HXM) – the new people-focused term for HCM. ODATA, ODATA API, Data Dictionary,. Capabilities of SFSF Adapter. API. Use search and filter to find the corresponding servers for your company. 0 topic under SAP SuccessFactors HXM Suite OData API: Developer Guide. (Open Data Protocol) is an ISO/IEC approved, OASIS standard that defines a set of best practices for building and consuming RESTful APIs. LMS Modularization and URL Pattern 2. Use Case 2: Update an Email Address. Click the Export button and after the process has completed, locate the generated XML file. Register your client application so that you can authenticate API users using OAuth2. Use search and filter to find the corresponding servers for your company. 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. Development and Deployment Flexibility. Integration Center's Guide. Represents the customer's company ID. Indicates from which server the response is returned. Specify export option Short format: only system fields. Through this blog I intend to cover some of the basic concepts for SuccessFactors Employee Central integration, such as entities and objects, API, load type processing parameter and other features. You may choose to manage your own preferences. Integration Flow Extension Using ProcessDirect Adapter. The content in this guide has moved. It is updated/refreshed whenever new feature and/or update for improving Odata API overall usability and performance is available and is live for customer or partner usage. You can find the content at the new location: About SAP SuccessFactors OData APIs (V2). The communication between OAuth 2. The OAuth 2. • Unlike SFAPI-Adhoc, OData does not rely on creating and running reports on a scheduler server. SAP SuccessFactors. Note: The templateId has to be replaced with the actual values that you have in your instance. This section contains information about query operations on MDF OData entities, including query parameters and examples. Complex types now support inheritance and navigation properties. You may choose to manage your own preferences. Describes the features of the API Center and required permissions . I will refer to this extension through. SAP SuccessFactors Employee Central OData API: Reference Guide. 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. About the OData API Reference Guide \(V4\) API UPSERT call to EmployeeTime. Document. When a user entity is queried, OData checks the logged-in user's permission against each property. Create custom MDF (Admin Center > Configuration Object Definitions) 2. Use the Position entity to query position details, create, and edit positions. e. 8 In the same permissions box, go to User Permissions -> Employee Data and review the attributes that the service account can read from the. Here you need to pass the API Key in the payload and do an API call which is not secure. 1 – Indicates that SAP SuccessFactors HCM Suite OData API (in short, OData API) is used. 8 PUBLIC SAP SuccessFactors HXM Suite SFAPI: Developer Guide Deprecation of Partner API, SFAPI Adhoc, and SFAPI for Simple Entities 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 details and samples for SAP Cloud for Customer OData API in a format that is most convenient to developers. Use Case 3: Modifying a Position. Configure Entitlements for SAP SuccessFactors Extensibility Service. Both REST and OData adhere to web-based architecture, statelessness, data format flexibility, resource-oriented design, and interoperability. However, we recommend that you use SHA-2 for better security. This may be particularly relevant in automation scenarios, where a leave may need to be cancelled or approved from a 3rd party software outside SAP SuccessFactors. The data could be sensitive. In Azure, install the "SAP SuccessFactors" Enterprise Application, which will generate SAML Assertion. Use the generated token to call APIs. However, we recommend that you use SHA-2 for better security. This document is the handbook for SFAPI developers. 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. Hi there, Second half 2022 release is here! This blog highlights key enhancements to SuccessFactors Onboarding. npm i -g generator-saphanaacademy-odata. 3 "Date and Time" and 5. SAP SuccessFactors HCM Suite SFAPI: Developer Guide. 509 trust with the destination. OData API can return a maximum number of 1000 records in a single page. Each service instance will result in creating: a separate OAuth2 client application on SFSF side and. About. Form OData APIs enable you to: Query a list of form templates. Example: cust_MyAttachmentNav N/AAdapter API for Adapter Development. SuccessFactors HCM Suite OData API: Developer Guide. The content of this guide has moved. Step 2: Create SAP SuccessFactors API User and Granting Permissions. Information about installing, configuring, and running the Data Services Adapter SDK . Copy SAP SuccessFactors EmployeeCentral Personal Information API. HRIS Element Information. Admin Username – Enter the username of the SuccessFactors API user account, with the company ID appended. It provides generic. Integrating SAP SuccessFactors Employee Central with Microsoft Active Directory (Boomi) Accessing. Use case 1: Initiate assessment through JobApplication entity using insert operation. 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). A global, cloud-based human resource management software system, evolving to help people and businesses thrive in the experience economy. SAP HCI for integration. 1) Create employment info (OData API upsert in the EmpEmployment) with the same person ID but with a different user ID. Quickly analyze the service definition code: First you import the solution model from the file you created in the previous tutorial as well as the PLTUserManagement OData service you imported in the third tutorial, referencing them through the aliases: model and UM_API, respectively. Keywords. Those APIs can be used in several scenarios, the most common one is knowing the permissions of a logged-on End User when building an application/extension to SAP SuccessFactors. 1. The row-level permission checks whether the logged-in user can query an entity. Keywords. Setup the application. Upsert in OData. They are fully ready to be imported to the external provider system that needs synchronized data with SAP SuccessFactors applications. 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. You can use this function import to send pending offer letters to a candidate. If your organisation’s. To view API Objects and their associated fields, you can view the API Data Dictionary. On this page. Net OData client which can be used to consume. This option is supported by the following receiver adapter types: OData V2, HTTP, IDoc, ODC, SOAP. Relationships, a key part of the entity model, are. 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. Query form details, including the User Info section, Objective section, Competency section, Summary section, and Signature section in the form. Use case 1: Initiate assessment through JobApplication entity using insert operation. c. 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. Only enter the. Use Case 2: Creating a Position with Insert. Operation level. Use Case 1: Query All Global Assignments of an Employee. Query and manage public sector cost object. surname which will be used in the subject -> nameid of the SAML assertion) 6. If you want to use location data, you must configure the OData API. SAP SuccessFactors HXM Suite OData API: Developer Guide (V2) SAP SuccessFactors HXM Suite SFAPI: Developer Guide. Please, follow the steps indicated in the SAP SuccessFactors HCM Suite OData API: Developer Guide documentation to confirm you are following the correct steps (See Registering your. Reference Guide SuccessFactors Foundation HCM Suite OData API: Reference Guide An Entity Reference ContentThe content in this guide has moved. It is an alternate integration. 2. A global, cloud-based human resource management software system, evolving to help people and businesses thrive in the experience economy. SAP SuccessFactors OData service supports a custom OData function called UPSERT. Pre-Read: Migrating SAP SuccessFactors API Calls from. 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. For any Attachment to upsert into Successfactors OData API, we should have to do this through Attachment OData API. For more complex transactions, you may need to decrease the size to avoid HTTP timeouts. It's intended to enable access to SAP SuccessFactors data in the. In SAP SuccessFactors, status values are used to identify the different types of users and their state of activeness in the system. Possible values are: BizX: Indicates that the response is from an API server. 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. SFAPI Audit Log can be used to monitor API calls to SuccessFactors Employee Central, and can be used to debug. A list of role-based permissions required to access API Center tools. Home | Qlik CommunitySAP SuccessFactors HXM Suite OData API: Developer Guide (V2) Scenario: User Propagation from the Cloud Foundry Environment to SAP SuccessFactors. The name of your company. The users, who have form OData Admin permission. Integration Center as a package. The name of your company. 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. Every to-do task is shown in the to-do panel. 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. Operations . SAP SuccessFactors API Reference Guide (OData V2) Favorite. You can use the dictionary to look up EntitySets, Complex Types, and Function Imports that are. Use Case 4: Upsert Job Information of an Employee with Multiple User IDs. 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. SAP SuccessFactors HXM Suite Boomi Connector Guide. In this guide, you'll learn how to work with OData v4 APIs in SAP SuccessFactors HXM Suite and what services we currently offer. Prepare configuration on SCP Cloud. 1 (Successfactors Application UI) 15. Step 3: SAP SuccessFactors HCM Suite OData API: Developer Guide 8 PUBLIC About HCM Suite OData APIs 3 Authentication Types for OData API. Please refer to the updated SAP SuccessFactors HXM Suite OData API: Developer Guide (V2) mentioned in KBA 2791956. Please refer to the official guide from SAP here. The Open Data Protocol (OData) is a standardized protocol for creating and consuming data APIs. SuccessFactors Data Access Choosing OData API Authentication type. The SAP SuccessFactors HXM Suite OData service supports both Edm. 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. For more information, refer to this SAP documentation. It has the format: username@companyID. You can use tools such as OpenSSL to create a self-signed X. Description. Philip then creates a service instance using the api-access service plan and reviews. 0 Bearer Assertion Flow typically comes into play when we want to give a client application’s users an automated access to remote resources or assets which are protected with the OAuth2. Example API call leveraging API Option Profile. Use Case 4: Upsert Job Information of an Employee with Multiple User IDs. Step 3:Configure the SuccessFactors OData V2 channel ( you can use SuccessFactors SOAP for Compound Employee API ). In order to have a configurable, automatically rethemable extension – you’ll use the Trial Cloud Portal service and create a portal site around your application, thus integrating with 1-st and 2-nd level. This option in API center will help to achieve the same using API option. Download PDF. Creating API User IDs via Option 2. The SAP HANA Academy YouTube is scheduled to close on December 31, 2023. 2735876 - Successfactors Odata API Best Practices [Query Modified Records, Pagination - Batch Size, Timeouts, etc. OData API – isContingentWorker. how to access the successfactors odata sales demo api. SAP SuccessFactors Integrations Product Page - Specific Handbooks: OData API: Developer Guide; OData API:. SuccessFactors has two API Data Dictionaries: The ODATA API Dictionary does not mirror Ad Hoc Reports. You will find integrations are easier. An assignment ID is an identifier assigned to the work relationship between a person and the company. A global, cloud-based human resource management software system, evolving to help people and businesses thrive in the experience economy. For example, your SAP SuccessFactors instance may be having a. The values supported to check for rehire are first name, last name, date of birth, and national ID details. 1. The OData standard provides a '__next' link in your query response if there are more results in the database. SAP SuccessFactors, ServiceNow, and SAP Integration Suite need to be configured and prepared before the integration content package can be configured and deployed. However, this can also lead to unintentional data changes if mishandled. Use Case 3: Updating the auto delegation configuration of user vicky to set delegation status as OFF. Go to Admin Center API Center OAuth Configuration for OData and choose Register Client Application. The relationship could be an employment relationship, contingent relationship, pensioner relationship, intern, global assignment. 2251702. Create Configuration UI (Admin Center > Manage Configuration UI) Set externalCode as not visible (which will auto-fill user ID) 3. For more information about querying OData Metadata, please go through this page of the official SuccessFactors OData Developer Guide: Retrieving Metadata. Create a Service Instance to consume the SAP SuccessFactors HXM Suite OData APIs. 1. You may choose to manage your own preferences. TodoEntryV2 allows you to query items of multiple users with the OData API Todo Export permission. The templateId is the ID of the Job Requisition template that will be used in creating the requisition. Tenant URL – Enter the name of the SuccessFactors OData API services endpoint. Other records not fetched via SFAPI EmpJob SOAP API issue , KBA. You can set the logging for both OData and SFAPI APIs. The content in this guide has moved. 6. Once done, click on Refresh Headers which adds the Base64 format of header to your request. 8 PUBLIC SAP SuccessFactors HXM Suite SFAPI: Developer Guide Deprecation of Partner API, SFAPI Adhoc, and SFAPI for Simple EntitiesFeatures. Choose Download Trust to get the certificate for this. These resources provide the motivation behind embedding analytical capabilities into an application, where APIs provides the bed rock foundation to achieve seamless embedding experience. Please notice that you will not need any OData API upsert in the OData. URL of your SAP SuccessFactors API tenant. SAP SuccessFactors Employee Central OData API: Reference Guide (V2) Content Has Moved PUBLIC 3. Consider reimplementing integrations using Integration Center. It assumes that you have configured and authorized a valid SuccessFactors Account (see SuccessFactors Basic Auth.