In case of SuccessFactors OData -V4 we dont have that luxury. The entity contains information. 2 (Import Employee via SFSF Application UI) Section 5*: Setting the Password for the API User. 0. In the following example, we were able to get most of the oData standard information, but we were also interested in getting the “Label” (here below: Address) and the oData “sf. Usually with SuccessFactors OData -V2 we will be able to get the schema once perform model operation. Now customers can use new SCIM APIs (not OData) with a certificate-based approach. When that limit is exceeded, it uses a mechanism called Pagination, which will make the response return the exceeding records in a subsequent page. Additional Information. “data”: Defines the data. Create the OData Service. “item”: Maps the fields of the data to the fields of the UI Card. Use search and filter to find the corresponding servers for your company. 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. Supports single, full, and comma-delimited metadata queries, examples: Supports metadata query on service level only. This 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. sap entity query-builder odata metadata-extractor api-builder successfactors Updated Sep 14, 2023; C#; dirigiblelabs / successfactors-synchronizer Star 0. Enter the Server, User ID, Password, and Org Code provided by your SuccessFactors System Administrator. API to access 360 Reviews forms. SAP SuccessFactors HXM Suite. odata – Success Factors. The CompoundEmployee application programming interface (API) for SAP SuccessFactors Employee Central is used to extract employee data out of Employee Central. I have chosen Products and Suppliers (without Address fieds)Admin Username – Enter the username of the SuccessFactors API user account, with the company ID appended. The SuccessFactors OData V2 Receiver adapter enables you to communicate with the SuccessFactors system. Go to Admin Center OData API Metadata Refresh and Export. If you have right access, then navigate to API Center > OData API Data Dictionary. In the adapter configure all the mandatory parameters. The value of sf. For example, CamelHttpQuery=abcd=1234. 2. SAML 2. How ever in order to consume any OData service from the SuccessFactors OData API test system,you will be using your SAP Cloud Platform trial account user id and password. Operation. Admin Center > API Center. This. In the context of a receiver adapter, this header can be used to dynamically change the URI to be called. Help Portal – List of SAP SuccessFactors API Servers. It's now 2021 and a properly functioning OData connector in Power BI seems to still be outstanding. This then ensures that under Name, you only see the entities. With OData API, you can make use of SuccessFactors in providing Restful integration services for HR data in SAP Cloud. How to check and understand Odata API Audit logs in SuccessFactors System? Image/data in this KBA is from SAP internal systems, sample data, or demo systems. Properties and Navigation Properties. 8 Getting users up and running: Permission settings) each permission specified and the. You can find detailed information about the SuccessFactors OData V2 API on SAP Business Accelerator Hub. This is expected behavior. The SAP SuccessFactors HXM Suite OData API is a Web Service API feature based on the OData protocol. Philip creates a BTP subaccount and configures entitlements for the SAP SuccessFactors Extensibility service. This query will fetch all the 8 different dimension photos. SAP SuccessFactors HXM Suite OData API provides methods for create, read, update and delete operations. 0 Uri Conventions". In this case, it’s defined to query the SuccessFactors OData V2 API. When the value is set to 1, or the property is not defined - SAP SuccessFactors HCM Suite OData API (in short. S – In the below output JSON code, i’ve shown only 3 types. I will demonstrate this with a simple custom MDF. It's now 2021 and a properly functioning OData connector in Power BI seems to still be outstanding. This VPC endpoint service must have Amazon AppFlow service principal appflow. This KB article explains what OData API is and what possibilities it offers when in use with the Recruiting Management Module. It replicates employee master data from Employee Central to SAP systems, payroll. The OData API can return a maximum number of 1000 records in a single page. If you can’t find it, please contact your system administrator. The idea here is, the tasks as part of TodoEntryV2 api shall be fetched which are owned by the logged on user of myTasksApp application. It is a front end application to display the data in the browser sent by ODATA for Fiori application. Learn how to retrieve OData metadata in SAP SuccessFactors HXM Suite. Get access to your organization’s Success Factors Instance. Proxy Type. 1. In the SAP BTP cockpit, navigate to your extension subaccount in the Cloud Foundry environment. With use of OData API, it provides with built on protocols like HTTP following the REST methodologies for data transfer. Some OData services (e. HTTP content type that fits. 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. It’s intended to enable access to SAP SuccessFactors data in the system. The Upsert operation is an SAP SuccessFactors function import to update or insert records. Image/data in this KBA is from SAP internal systems, sample data, or demo systems. Your username is assigned to you by your organization. HRIS Element Information. Find below the URL for the Guided Answer, and more information on setting up users for Odata API usage: Create API User account for Successfactors Odata API; SAP SuccessFactors Employee Central OData API: Reference Guide (Permission Settings Section)We store the credentials in the OAuth2 credentials in the CPI Security Material. When you query an effective-dated entity without any date parameters, the result returns a single record effective on the present date. Compound Employee will be used when you are building Integrations around Employee Master data and for rest of the scenarios we can leverage OData APIs. Step 1: Create an app variable. x) adapter. Blog Posts. Leveraging the Destination Service x. In SuccessFactors, navigate to SuccessFactors > Admin Center > Company Settings > Manage OAuth2 Client Applications > Register Client Application. SAP SuccessFactors Documentation on OData APIs can be. Our CAP app consumed v2 OData services from SuccessFactors and provisioned v4 OData services which in turn were consumed by our freestyle UI5 apps. OpenSQLAccess. OData v2 uses HTTP method POST and HTTP header X-HTTP-METHOD: MERGE to merge records. Related Information. Past year my. Proxy. Understood. Compound Employee will be used when you are building Integrations around Employee Master data and for rest of the scenarios we can leverage OData APIs. You can get such files from SAP API Business Hub. Creating Connector for SAP SuccessFactors in GRC. 3) Register subaccount as OAuth client in SuccessFactors. Error: The metadata document could not be. We can see under the CPI message processing the. Note the OData API does not replace the SFAPI solution. This application allows user to explore SuccessFactors oData API metadata. One Model typically sources data from SAP SuccessFactors Employee Central via the OData API. SAP SuccessFactors Performance Management. cs and Service1. If input date is 2014-4. The adapter only supports SuccessFactors Learning Management System (LMS) OData V4 entities. 0 authentication in your project please refer my blog on Using OAuth 2. It has the format: [email protected] or not, SuccessFactors OData V2 implementation applies filters on expanded entity and the URL i posted is an example of that. Step 1: Upload the transport request files. privateKey = Use the private key you uploaded when you register your client in Successfactors or for this example, we will use the private key we generate from Successfactors. It's now 2021 and a properly functioning OData connector in Power BI seems to still be outstanding. Their HXM suite lets you provide employees with experiences that recognize their individual value and consistently motivate them to achieve peak performance levels. Objective: We would like to share one video with hands on using SAP SuccessFactors inbound Integrations Center along with custom MDF entities in OData V2 integration. Click on File -> New SOAP Project. Attachment is a generic API to upsert any. The most common use case for deriving time account balance information is to enrich the employee’s pay slip with time off data. The OAuth 2. Use Case 1: Querying Position Details by Keys. 3. How the ODATA APIs delivered by SAP SuccessFactors can support many different use cases, from reading requisition template configuration for custom UIs to supporting new candidate experiences. Delete the autogenerated IService. Creating API User IDs via Option 2. Code. I am trying to get current and future dated records from SuccessFactors for any entity. In the adapter configure all the mandatory parameters. 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. An easy way to get external data to be made available within the Data Warehouse Cloud, is. See Full PDF Download PDF. Managing contingent workers in SAP SuccessFactors Employee Central system enables a complete view of the workforce and the ability to include contingent workers in select HR processes. SAP SuccessFactors Recruiting Management. It has successfully deleted entry of Position. Tenant URL – Enter the name of the SuccessFactors OData API services endpoint. SAP blogs let you read about and share your own technical know-how, industry insights, and the latest buzz about technology, events, and all things SAP. Anypoint Connector for SAP SuccessFactors (SuccessFactors Connector) provides full support to query, create, update, and delete entities using the OData API exposed by SuccessFactors. A global, cloud-based human resource management software system, evolving to help people and businesses thrive in the experience economy. Admin password – Enter the password of the SuccessFactors API user account. The SuccessFactors OData V2 Receiver adapter enables you to communicate with the SuccessFactors system. Stay tuned for more content about this topic. 1. 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. The value of sf. It has the format: username@companyID. OpenJDK. The SAP SuccessFactors HXM Suite OData API is a Web Service API feature based on the OData protocol. Register the service in the SAP SuccessFactors system. Properties and Navigation Properties. The asOfDate parameter retrieves the single records of. OAuth Client Registration. It is a SOAP Web Service designed for importing and exporting data to and from your SuccessFactors instance. Now let's start doing OData API queries using 4 different scenarios. SAP SuccessFactors Onboarding supports both rehire on new employment and rehire with old employment information. 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). Select the OData API call to investigate and click on the button with the three dots: In the resulting popup check for the string “ Authorization: Bearer ” or “ Authorization: Basic ” in the “ Request Header ” section. Producing the XML file from the SuccessFactors system. 0. . After ‘Request Reply’ is defined that is named ‘Invoking userId’ in the flow, SuccessFactors OData v2 adapter configurations are made as shown below. Registering Your OAuth2 Client Application. Integration center; Cause. Any resemblance to real data is purely coincidental. 0 and later. 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. Both SHA-2 and SHA-1 signing algorithms are supported. In order to resolve the issue, you need to ensure you pass the REQUEST in correct format. Calling SuccessFactors OData APIs via iRPA 2. Step a: Add a Request-Reply step to make OData call to get User data from SuccessFactors with below configuration. Why does oData return less users than Azure DevOps shows on organization users page. 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. The SuccessFactors activities. To check the statistic for the job, open the ‘ Job Execution Logs ‘. URL of the SuccessFactors data center that you're connecting to. 記述にあたり、こちらのSAPの技術文書を参考にしていますので、興味がある方はこちらも合わせて御覧ください. These support cases should be handled over to LOD-SF-INT-OUT component. 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. There are two entities which can store the HR Manager of a user: User; EmpJobRelationships. The wizard can also fetch the Externalized parameters that are maintained under the Connection details of the OData receiver adapter. Switch to Variables (View ←→ Variables on top of your screen) Select App Variables in the left menu. Select Operation as “Upsert” and select the fields that needs to be updated. If you click on it, you will see the ‘ Job Execution Details‘. The SAP SuccessFactors Human Experience Management (HXM) Suite supports extensibility and integration with third-party solutions using comprehensive application programming interfaces (APIs). DateTime and Edm. Enhancements to Onboarding Dashboard. Register your client application so that you can authenticate API users using OAuth2. It has more info about the Background entities and how they behave on OData API calls. For example, with the "Department" field of the "JobApplication" entity in SuccessFactors, you'd be able to create a report and filter by "Department" in Gem and see stats like interview. 0. SAP SuccessFactors HXM Suite - Odata API; Resolution. Follow below steps to refresh metadata: When clicking , notice the message “ ” after metadata gets refreshed. Use Case 4: Modifying a Picklist Option with Replace. To integrate and automate SuccessFactors, Magic xpi Integration Platform leverages the Open Data Protocol (OData) which is a standardized protocol for creating and. After signing in, click "Connect". SAP Knowledge Base Article - Public. It assumes that you have configured and authorized a valid SuccessFactors Account (see SuccessFactors Basic Auth. However there is one caveat to it, namely the trust (=the public X509 certificate key) has to be manually downloaded from the DestinationService GUI on the. To support three different types of pagination types described in, there is an explicit UI control provided in the SuccessFactors OData V2 connector as shown below. You can dynamically configure the address field of the SOAP (SOAP 1. You can browse and select a SuccessFactors data center URL by using the Select option. 0) APIs for integration and data replication. With use of OData API, it provides with built on protocols like HTTP following the REST methodologies for data transfer. Wait until you see a success message, along with a date and timestamp. Available SFSF API test system. DateTime and Edm. a}, the value of a header or an exchange property (from the incoming message) is written into Camel header CamelDestinationOverrideUrl at runtime. Supported Operations. Resolution. version property controls which API you use. Example 2: Upsert Multiple Records of an Effective Dated Entity. SuccessFactors. We show you what needs to be done (video 4), but this may require the involvement of an administrator. Personal and employment details for employees, referred to as Person Objects and Employment Objects. Description. privacy statement, for purposes that may include site operation, analytics, enhanced user experience, or advertising. The Upsert operation is an SAP SuccessFactors function import to update or insert records. 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. ICF inturn invokes a search operation on the SuccessFactors Connector Bundle and then the bundle calls the OData API for reconciliation operation. You can use the Integration Center to immediately run or schedule a job to export a provider-specific OData object to SFTP, based on defined filter conditions and applying a provider-defined output order and file format. Complete the configure connection properties. When a user entity is queried, OData checks the logged-in user's permission against each property. The SAP SuccessFactors HXM Suite OData service supports both Edm. upsert, insert, difference, differ, not insertable, post, sf, successfactors, odata, api, endpoint, url, uri, payload , KBA , LOD-SF-INT-ODATA , OData API. One of the missing functionality in SAP BW/4HANA 1. SuccessFactors OData V2 receiver supportes Upsert with content-type : atom+xml only. 2. Follow the steps below to create a WCF service application that will provide connectivity to SAP SuccessFactors data via OData. 0 with SAML Bearer Assertion. 16. 0 Execution Manager with Payload odata; sap-successfactors; Share. With enhanced SAP SuccessFactors oData V2 outound connector, it’s possible to configure oAuth SAML Bearer in context of an API user for SAP SuccessFactors system. 1. Procedure. 1. Utilize server-side functionality and intelligent row-scanning to detect data types. It is also recommended to join the Global SuccessFactors and SAP HXM Community and SAP. 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. SAP SuccessFactors, ServiceNow, and SAP Integration Suite need to be configured and prepared before the integration content package can be configured and deployed. This would affect ODATA API request and validate if client Application from where ODATA API call is being triggered is encoding the special character " Space" or not. Timezone. First, you have to create an app variable where you will persist the profile picture retrieved from the SAP SuccessFactors API. Step 6: If you are still wondering. Get the required Success Factors credentials for your organization instance along with the. In the above iflow Successfactors Odata V2 adapter is used. 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. OData (Open Data Protocol) is an ISO/IEC approved, OASIS standard that defines a set of best practices for building and consuming RESTful APIs. Complete the configure connection properties. The SAP SuccessFactors ODBC Driver is a powerful tool that allows you to connect with live data from SAP SuccessFactors, directly from any applications that support ODBC connectivity. More Information. Supported Operations. 0. The list of Main Data Source connectors is displayed. In the next screen, press connect. 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). Click on SuccessFactors, and then click on Select. 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 use SuccessFactors ODATA Connector to connect to SuccessFactors from. Provide the below permissions to the API user. Click an SAP SuccessFactors connection type tile for your source. However, SAP SuccessFactors recommends that you use OAuth 2. The custom MDF has three fields externalCode as AutoNumber, User ID as USER and comments as String. This article describes the process on how one can access SuccessFactors OData APIs from an ABAP program using the OAuth 2. This section provides information about MDF OData API entities including MDF Generic Object entities and MDF Foundation Object entities. The test steps described in this KBA are to verify if there is any SPACE special character being sent by client application to SuccessFactors. 4. API to access Calibration data such as subject rank, feedback and rating. In productive scenarios, the metadata seldom changes. 401. DateTimeOffset data types of the OData protocol. Reproducing the Issue. Query and manage public sector cost object Budget Period. If there are network issues, you enable the integration flow to retry connecting to the SuccessFactors OData V2 service. 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. 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. 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. It also allows user to search an API and build & execute oData query. Only enter the host name of server. SuccessFactors has two API Data Dictionaries: OData API Data Dictionary. With 1H 2021 SuccessFactors release, new enhancement has been done for SuccessFactors Connector in Boomi to support OAUTH authentication for OData API call. Related Information. The scenario includes highlighting the location of US-based candidates on an interactive map: It also covers how to trigger and process. 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. Procedure. 4. 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. How to enable the OData API (V2) in SuccessFactors? Image/data in this KBA is from. To enable Basic Authentication, grant the permission to your role at Manage Integration Tools Manage OData API Basic Authentication. Using postman everything works fine but, once I check the connection of destination previously created, the response received is 401: Unauthorized. Learn about changes to the documentation for Learning OData API Reference in recent releases. Select the WCF Service Application template. 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. Conclusion and Outlook. 8. User Upsert, SFOdata. SuccessFactors API. SAP SuccessFactors. Common APIs under SAP. g. This enables authentication for OData API Access using OAuth 2. userId = User ID used by the registered client in SuccessFactors. The stream request is also very important as this is the direction the policy will apply to. In Azure, modify one existing user's attribute (for example user. MDF OData API. You can use tools such as OpenSSL to create a self-signed X. MDI is a cornerstone of SAP’s new integration strategy for master data. Use the example code attached to 3031657 to generate SAML assertions for your application. This would affect SFAPI/ODATA/REST API endpoints across all datacenters. The performance OData APIs has some limitations. This section contains OData API entities for SAP SuccessFactors Onboarding 1. 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. Sample. Even if it seems to make sense semantically, the API will not interpret it as a range. Available SFSF API test system users: mbarista1 and nnnn. There are three main steps in this wizard: Connect to System: In this step, you provide the details required for connecting to the Web Service that you’re accessing. Hence you can avoid the refresh by disabling metadata refresh. 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. Error: The metadata document could not be read from the. Note If you want to create an onboarding external user record in the system with the information collected from your external ATS, it is recommended that you use the createOnboardee API instead of using the ExternalUser API. A27) In the past, the communication between IPS and SAP SuccessFactors was using the OData APIs and Basic Authentication. SuccessFactors (OData V2) Adapter Configuration. It has more info about the Background entities and how they behave on OData API calls. This enables authentication for OData API Access using OAuth 2. The SuccessFactors adapter enables you to communicate with the SuccessFactors system. The. . This connector enables you to: Create, update, and delete entities. Tenant URL – Enter the name of the SuccessFactors OData API services endpoint. This adapter exchanges data with a remote component that might be outside the scope of SAP. Note: As a best. SAP Knowledge Base Article - Preview. To set up connection between the service and SAP SuccessFactors, you need to set up OAuth Authentication in SAP SuccessFactors. 4. 1 - Mule 4. 509 Certificate in SAP SuccessFactors Generating a SAML Assertion Requesting an Access Token SAP SuccessFactors HXM Suite all versions. For those looking for light-weight connection option with SuccessFactors, OData API is the answer. Type of proxy you want to use for connecting to SuccessFactors OData V2 service. There are two ways to retrieve OData metadata in SAP SuccessFactors HXM Suite:. Features. PerPerson Odata API issue, Employee Central HRIS OData API, call, blank, empty, null, results, values, field, query. Configure People Profile. 1. but we are only taking costCenter for ease, here) from ‘EmpJob’, Entity of Employee Central module of SuccessFactors. The API key generated will be needed in the next step. The SuccessFactors OData V2 receiver adapter supports externalization. Creating API User IDs Option 2. The field is auto-populated with /odata/v2. 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. • SAP SuccessFactors will roll out network changes across all Datacenters. Testing. SAP SuccessFactors Employee Central is a flexible, global core HR solution that supports core HR processes and employee self-services for your total workforce. Any resemblance to real data is purely. On this page. This document explains: How to perform a query operation using the Odata API entity? What is the API response in this case? How to retrieve profile Photo from the API response without Provisioning job?. svc. 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. The solution is a standalone application that will read the basic employee (SF user) information from SAP SuccessFactors using the User entity from the platform user management OData service and write the project assignments to the employees’ background using the Background Special Assign entity from the employee profile OData. Overview. The steps. Use Case 2: Update an Email Address. This option enables you to mitigate intermittent network issues. Error: The metadata document could not be. Follow Like RSS Feed Alert Moderator Alerting is not available for unauthorized users. Use the Common Name (CN): SF and then press “Generate”. 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 9Supports metadata query on service level only. Then, we tested this by making OData API call for getting metadata of this entity using Postman tool and could see this newly added. Follow the steps mentioned in the next sections. 1 Configuration in SAP SuccessFactors A Technical Communication User is needed to call OData services in SAP SuccessFactorsPass your SAML assertion and API key (in the client_id field) along with other information to generate an OAuth token. The SuccessFactors OData API enables query, insert, update, and upsert of Generic Object data, including Position object data. API Server Address can be identified using SAP HELP Documentation. Example. Use Case 2: Retrieve the Employment Records of All Candidates Created in Onboarding. Improve this question. 0 Let’s call iRPA 2. SAP SuccessFactors makes three types of data available in the API: Employee Objects. This roundtrip is one of the supported integration types of the integration center. This article describes the steps on how to perform ODATA API queries and upsert requests via Postman. 2613670 – What are the available APIs for SuccessFactors? You can also check the SF available Fields in the API Center with in SuccessFactors. Procedure. Use SuccessFactors ODATA Connector to read data from SuccessFactors and integrate the data with other applications, databases, and flat files. Version : Displays the OData version used to implement the SAP SuccessFactors OData service. You can read data from. 0 bot from CAI chatbot to update SuccessFactors Principal Propagation in SAP Integration Suite from external system to SuccessFactors Using OAuth 2. This KBA document discusses a sample Odata Upsert request to change or reset User Login Password with your preferred value via SFOdata. Create an HTTP connector Type G between SAP Access Control and SAP SuccessFactors. Environment. Example 3: Get a Faster Upsert Response by Specifying Entity Names in URI. Error: The metadata document could not be. It really depends on the server side implementation, and SuccessFactors actually supports it. With OData API, you can make use of SuccessFactors in providing Restful integration services for HR data in SAP Cloud. 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.