Updated parameters and filters to ensure more efficient interactions and reduce the double call backs for incremental details. Use Case 1: Get Email Addresses by Specific Criteria. 0 authentication in your project please refer my blog on Using OAuth 2. upsert, insert, difference, differ, not insertable, post, sf, successfactors, odata, api, endpoint, url, uri, payload , KBA , LOD-SF-INT-ODATA , OData API. Use search and filter to find the corresponding servers for your company. Description. Select the exact fields that need to be integrated with 3 rd Party application. When that limit is exceeded, it uses a mechanism called Pagination, which will make the response return the exceeding records in a subsequent page. Admin Username – Enter the username of the SuccessFactors API user account, with the company ID appended. In this hands-on video tutorial, Philip Mugglestone shows how to create a service instance to consume the SAP SuccessFactors OData API. Build an application powered by SAP SuccessFactors and Cloud SDK. OData v2 uses HTTP method POST and HTTP header X-HTTP-METHOD: MERGE to merge records. Click an SAP SuccessFactors connection type tile for your source. Create custom MDF (Admin Center > Configuration Object Definitions) 2. The CompoundEmployee API is based on the Simple Object Access Protocol (SOAP). It assumes that you have configured and authorized a valid SuccessFactors Account (see SuccessFactors Basic Auth. And the response body (3) is exactly the response body from LMS API. You can browse and select a SuccessFactors data center URL by using the Select option. SAP SuccessFactors HXM Suite provides a variety of OData APIs for customers to build their extensions and integrations. Your username is assigned to you by your organization. You no longer require Employee Central Foundation OData API (read-only and editable), and Employee Central HRIS OData API. Learn about changes to the documentation for Learning OData API Reference in recent releases. Follow the steps below to create a WCF service application that will provide connectivity to SAP SuccessFactors data via OData. userName = leave it as it is. 1 (Successfactors Application UI) 15. In Azure, install the "SAP SuccessFactors" Enterprise Application, which will generate SAML Assertion. Use Case 1: Querying a Picklist Option. Postman is used to call the iflow URL (1), the request message body (2) is ignored in my demo. O to securely call SuccessFactors OData APIs from iRPA 2. Added an API for Learning Administrators to get library details. Pre-Requisites: Below are the required prerequisites for this process, 1. API Server Address can be identified using SAP HELP Documentation. OData Recruiting Management API Resolution Click Here to access the SuccessFactors OData API Developer Guide Keywords OData, Developer, Guide, API, Data, Dictionary,. 記述にあたり、こちらのSAPの技術文書を参考にしていますので、興味がある方はこちらも合わせて御覧ください. Picklist issues using Infoporter - SuccessFactors OData API. When the value is set to 1, or the property is not defined - SAP SuccessFactors HCM Suite OData API (in short. Available SFSF API test system. Amidst retirement of basic authentication for SAP SuccessFactors oData services, oAuth SAML Bearer authentication is the new alternative. A platform for all people and HR data that transforms your work experience. For individual OData v4 offerings in SAP SuccessFactors, the capabilities vary depending on the implementation of each. SuccessFactors has two API Data Dictionaries: OData API Data Dictionary. The most common use case for deriving time account balance information is to enrich the employee’s pay slip with time off data. To authorize your IP address for OData API access, go to API Center OData API IP Whitelisting. JOB TITLE LOCATION; Senior Electrical Engineer (Combat) (Permanent) Victoria: 30-Oct-2023 - N/A: Senior Technologist - Mechanical (Permanent) 30-Oct-2023 - N/AIt's now 2021 and a properly functioning OData connector in Power BI seems to still be outstanding. To set up connection between the service and SAP SuccessFactors, you need to set up OAuth Authentication in SAP SuccessFactors. P. This enables authentication for OData API Access using OAuth 2. 0. Scenario 1: personIdExternal='akoelemij'sample: /odata/v2/ or /sfapi/v1 endpoints. OData API, future dated records, API, OData, future date, historical records, past, fromDate, toDate, EC, Employee Central , KBA. API Server Address can be identified using SAP HELP Documentation. Select the General tab and provide values in the fields as follows. Configure and use your SAP SuccessFactors solutions to reduce biases and embed diversity, inclusion, and equity directly into your HR processes. userId = User ID used by the registered client in SuccessFactors. Image/data in this KBA is from SAP internal systems, sample data, or demo systems. The SuccessFactors OData API enables query, insert, update, and upsert of Generic Object data, including Position object data. Objective: Share the information with customers and partners, so new custom development integrations can already starting use OAuth. UI name. Hello SAP community, If you regularly call the SAP SuccessFactors’ OData API’s for test purposes using your API test tool of choice, chances are that you are already aware that the Basic Authentication is deprecated and must not be used; instead, the authentication using OAuth 2. I can get only 1000 rows in one JSON file (default limitation). SAP SuccessFactors HCM Suite; OData API; Cause. The entity contains information. SAP UI5: SAP UI5 is a user interface using HTML5. 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. cs and Service1. Registering Your OAuth2 Client Application. Using the search filters Entity, Complex Type, or Function Import also lets you narrow your search by Tag, for example EC - Payment Information . Related Information. This brings performance benefit especially when the service metadata is large in size (as is the case with SuccessFactors OData API). 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?. 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):For SAP SuccessFactors EP (Employee Profile) and SAP HCM ERP integration, you can use the Talent Addon via SAP CPI and SF OData API. Admin Center -> Select the Permission Role -> Click on Permissions Tab. 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. The Upsert operation is an SAP SuccessFactors function import to update or insert records. Learn how to retrieve OData metadata in SAP SuccessFactors HXM Suite. Error: The metadata document could not be. Choose the entities that you want to expose in the API from SAP Cloud Integration. This then ensures that under Name, you only see the entities. The OData API is a solution with allows to export, create and update. You may choose to manage your own preferences. OAuth Client Registration. It really depends on the server side implementation, and SuccessFactors actually supports it. Available SFSF API test system users: mbarista1 and nnnn. If there are network issues, you enable the integration flow to retry connecting to the SuccessFactors OData V2 service. The SuccessFactors OData V2 receiver adapter supports externalization. With these 1000 records, I also get a URL with a skip token to get the second 1000, and so on up to the last thousand of records. 0 with SAML Bearer Assertion. Currently SuccessFactors supports SFAPI ( Compound Employee ) and OData APIs for integration. 4. 0 Client API. SFAPI access includes access to CompoundEmployee API. HTTP content type that fits. SuccessFactors OData V2 receiver supportes Upsert with content-type : atom+xml only. Register your client application so that you can authenticate API users using OAuth2. By default, retry is enabled. Log into your SAP SuccessFactors HXM Suite system. Only enter the. Some OData services (e. You can use below references to know more about SFSF Adapter and Query Modeler. 0 methods. 8 onwards) provides you a feature to handle network issues in case of outbound connections. 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. Use the Position entity to. SAP SuccessFactors HXM Suite OData API provides methods for create, read, update and delete operations. 3. 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. It has more info about the Background entities and how they behave on OData API calls. 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. You can use this OData API to display non-effective-dated biological information about an employee such as date and place of birth, and date of death. Using the search filters Entity, Complex Type, or Function Import also lets you narrow your search by Tag, for example EC - Payment Information . Click to go back to the main page LMS ODATA WEBSERVICES KNOWLEDGE SESSION FOR CUSTOMERS, PARTNERS AND SAP PRODUCT SUPPORT 1. How artificial intelligence and machine learning can be used throughout the recruiting process. through a. Testing. SuccessFactors OData adapter uses a cache to store the service metadata refreshed every hour. OData getEntity method fetches only first entity. Timezone. The OData API Data Dictionary tool in API Center provides a user-friendly view of OData metadata. Please refer to the Authentication Using OAuth 2. 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. In case of SuccessFactors OData -V4 we dont have that luxury. Use Case 2: Creating a Position with Insert. How to clear an internet browser's cache? How to clear an internet browser's history and cache? How to clear an internet browser's temporary internet files? **Image/data in this KBA is from SAP internal systems, sample data, or demo systems. This KBA document discusses a sample Odata Upsert request to change or reset User Login Password with your preferred value via SFOdata. I have gone through couple of community post , but could not able to fix the problem. Error: The metadata document could not be. First, it's worth noting that the SuccessFactors API will paginate result sets when more than 1000 entities are returned. amazonaws. You can use tools such as OpenSSL to create a self-signed X. I am using Job Application OData API to achieve this. The asOfDate parameter retrieves the single records of. from 10 to 11 via ODATA Upsert: As additional confirmation the Application history shows that the Application status has been updated via OData: How to perform the same via manual ODATA Upsert: Is also possible to achieve the same result doing a manual ODATA Upsert, example using Postman application as below: URL:. 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. Step a: Add a Request-Reply step to make OData call to get User data from SuccessFactors with below configuration. Log into the operating system of the SAP Instance. This brief is to showcase the SAP SuccessFactors extensibility service when used directly from SAP BTP, Kyma runtime environment. User Assistance Overview Product Page for SAP Cloud Platform Integration. The OAuth 2. Under Application Name, enter edX OCN Integration. SuccessFactors (OData V2) Adapter Configuration. Step 1: Upload the transport request files. OData v2 uses HTTP method POST and HTTP header X-HTTP-METHOD: MERGE to merge records. Related Information. Use the generated token to call APIs. Open the SOAP UI. Here's a list of API servers and mTLS certificate servers for SAP SuccessFactors data centers. Tenant URL – Enter the name of the SuccessFactors OData API services endpoint. S – In the below output JSON code, i’ve shown only 3 types. edu account. 2253200 - How to add in allow list an IP for API access in SuccessFactors OData or SFAPI; You are able to safely provide the credentials of the API user in an case using the Secure Area. Personal and employment details for employees, referred to as Person Objects and Employment Objects. On this page. Creating User IDs via Option 1 (Provisioning) 14. SAP SuccessFactors Connector 4. If you need to use oAuth 2. 2. Thanks to this ,we have access to User. If you specified the Environment type API endpoint, you must select the API. 1. SuccessFactors EC shall go live alongside ECP for the concerned Company in the multi-tenant landscape, albeit a week in advance, so as to limit dual maintenance between EC and existing on-premise SAP HCM Suite. It is also recommended to join the Global SuccessFactors and SAP HXM Community and SAP. So, what was the requirement initially, to update the Recurring Pay Component created via ODATA API,. This means the fields/properties that can be found in the Ad Hoc Reports. Hello SAP Community, With the advent of the 2H 2020 in SAP SuccessFactors, the Entities Job Requisition and Job Offer in OData now support the Position Generic Object, so it is now possible to use both OData API and the UI to create a Job Requisition or Offer with the Position Generic Object. 0 Let’s call iRPA 2. version property controls which API you use. Step 1: Step 2: Step 3: The last Skiptoken URL return only a List of records without "__Next" with Skiptoken URL: I would like to ask for help with a. SAP Help PortalChanged We updated information on OData API permissions and the Mapping Extension Field topics. New and Improved Features in OData V4 Note The following features are supported in the standard OData v4 protocol. Use Case 1: Get the First PerPerson Record. -----FIRST: QUERY =. Operation. WFS requires data a week before it’s go live to set up the time profiles, and hence, we shall have EC going. version property controls which API you use. Note: As a best. The OData API is a solution with allows to export, create and update operations in the Recruiting Module. To find right OData end point URL for your SuccessFactors instance refer this link. References: SFSF Adapter – SuccessFactors (SFSF) Adapter for SAP NetWeaver Process Integration. 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. . Even if it seems to make sense semantically, the API will not interpret it as a range. Complete the configure connection properties. Stack Overflow Public questions & answers; Stack Overflow for Teams Where developers & technologists share private knowledge with coworkers; Talent Build your employer brand ; Advertising Reach developers & technologists worldwide; Labs The future of collective knowledge sharing; About the companyYou need to create VPC Endpoint Service for your SAP OData instance running in a VPC. 1. 509 certificate. 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. The below blog by Sriprasad S Bhat have the detailed information about the Data Dictionary. 0 authentication for inbound API calls to SAP SuccessFactors. I have only seen SuccessFactors Employee Central having OData v2. 2H 2022. To externalize the parameters of this adapter, choose Externalize and follow the steps mentioned in. This section provides information about MDF OData API entities including MDF Generic Object entities and MDF Foundation Object entities. You are trying to get data from deleted records in an MDF object using the ODATA API in SuccessFactors. Here's a list of API servers and mTLS certificate servers for SAP SuccessFactors data centers. Using the POST operation, you can insert ‘n’ number of new entities in your OData backend, using PUT/MERGE operation you can update entities and DELETE operation to delete entities. The key idea to understand this is that the. The video covers a sample of SF to SF integrations using custom parent/child effective dated MDFs entities. SAP SuccessFactors OData API; Resolution. OData v4 is the latest version of the OData protocol that offers more features and capabilities. 4. 2. Suggested reading: OData V2 Refresh Cache On. Regarding. Consume OData API Video Tutorial. For this Go to the Admin Center->Manage OAuth2 Client Applications-> Register. Sorted by: 1. Use Case 1: Query All Global Assignments of an Employee. Step 1: Create an app variable. SuccessFactors extensions leverage the SAP Cloud Portal to achieve dynamic branding and retheming of extension UIs by using SAP Portal sites configured with a corresponding template to mimic the look and feel of the extended SAP solution. Follow edited Dec 26, 2020 at 0:10. Type of Change Description More Info 13. Symptom. The Mule connector for SAP SuccessFactors provides full support to query, create, update, and delete entities using the ODATA API v2 exposed by SuccessFactors. Properties and Navigation Properties. To enable Basic Authentication, grant the permission to your role at Manage Integration Tools Manage OData API Basic Authentication. Admin Center > API. In the following example, admin users with OData API job application export permission can initiate assessment during insert operation if assessment is configured for the New/Default Application status. The refresh may take a few minutes. User Insert, apiOptionProfileID, processInactiveEmployees , KBA , LOD-SF-INT-ODATA , OData API Framework , LOD-SF-INT , Integrations , How ToIt's now 2021 and a properly functioning OData connector in Power BI seems to still be outstanding. DateTime and Edm. Use the generated token to call APIs. 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. 0 section in the SAP SuccessFactors HXM Suite OData API: Developer Guide (V2) There are 3 ways to. 1. In SuccessFactors, navigate to SuccessFactors > Admin Center > Company Settings > Manage OAuth2 Client Applications > Register Client Application. General guidelines about OData v2 APIs in SAP SuccessFactors HXM Suite, including general permissions, authentication, metadata, query and edit operations, as well as how. If you click on it, you will see the ‘ Job Execution Details‘. Description Web Service 1. Delete the autogenerated IService. Past year my. Navigate to next tab Processing and click on Select Button next to Resource. Use Case 3: Update External User Record with Employment-Related Information. Step 2: OAuth Configuration for OData (Manage OAuth2 Client Applications) Admin Center > API Center > OAuth Configuration for OData (Manage OAuth2 Client Applications) To learn more about the OData System query options used in the example URIs in this section, visit and search for "OData Version 2. Follow the steps mentioned in the next sections. 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. The SuccessFactors OData API test system comes with a predefined set of users and data configured in READ ONLY mode. Proxy Type. When creating connection using OAuth, your Authorization Code. The project was a side-by-side SuccessFactors extension. 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. Similar Blog Posts. With OData API, you can make use of SuccessFactors in providing Restful integration services for HR data in SAP Cloud. Copy the cofiles to the DIR_TRANS /cofiles folder. Open Visual Studio and create a new project. Enter a meaningful Project Name. Properties and Navigation Properties. 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. Admin password – Enter the password of the SuccessFactors API user account. 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. com Content-Type: multipart/mixed; boundary=batch_36522ad7-fc75-4b56-8c71-56071383e77b Before constructing the request body, I would like to explain the use of postman variables in the API request. Step 3: The Authentication dialogue box will appear and details over Basic authentication are being entered here: Step 4: Click on Connect , following message shows up, trying to connect to the server: Step 5: And viola !!! we get the Data (the SAP Successfactors data in Microsoft Power BI). The SuccessFactors connector enables you to authenticate using either Basic or OAuth 2. For a list of the API Endpoint URL for the SAP SuccessFactors environments, see About HXM Suite OData APIs. Hence you can avoid the refresh by disabling metadata refresh. Philip creates a BTP subaccount and configures entitlements for the SAP SuccessFactors Extensibility. Leveraging the Destination Service x. We show you what needs to be done (video 4), but this may require the involvement of an administrator. 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. 2. 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. Use Case 3: Creating a New Picklist Option. Hello SAP community, During the 2H 2020 release of SAP SuccessFactors application was announced the sunset (planned retirement) of HTTP Basic Authentication for API calls (both SFAPI & OData), you can find more details in this link. Properties and Navigation Properties. Once exposed, you can access the object through OData API calls. SuccessFactors OData V2 receiver supportes Upsert with content-type : atom+xml only. For learning to deploy and call the automation from a SAP CAI based chatbot please read my blog post: Let’s call the iRPA bot from CAI to update SuccessFactors. The SAP SuccessFactors HXM Suite OData service supports both Edm. ,] - SAP Successfactors Odata APISuccessFactors come with API Centre which has OData API Data Dictionary where you will find the entities of all the SuccessFactors modules. Admin password – Enter the password of the SuccessFactors API user account. O to securely call SuccessFactors OData APIs from iRPA 2. Unexpected XmlAttribute: The attribute ' CollectionKind' was not. This API can be used both by SuccessFactors/SAP module engineering teams, and by customers and partners for external integrations. The Microsoft Entra SuccessFactors connector uses SuccessFactors OData API to retrieve changes and provision users. SAP SuccessFactors HXM Suite OData API provides methods for create, read, update and delete operations. Connection Details URL : Enter the OData service provider URL of the SAP SuccessFactors service that you want to access. Some OData services (e. (Open Data Protocol) is an ISO/IEC approved, OASIS standard that defines a set of best practices for building and consuming RESTful APIs. Related Information. Image/data in this KBA is from SAP internal systems, sample data, or. Procedure. Connection Details URL : Enter the OData service provider URL of the SAP SuccessFactors service that you want to access. Use Case 2: Update the Personal Information of an Employee. You can use the dictionary to look up EntitySets, Complex Types, and Function Imports that are. 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. Stay tuned for more content about this topic. 0. In the context of a receiver adapter, this header can be used to dynamically change the URI to be called. For starters, the OData endpoint details are pre-filled based on. Admin Center > API Center. You can use the dictionary to look up EntitySets, Complex Types, and Function Imports that are. The SAP SuccessFactors HXM Suite OData API is a Web Service API feature based on the OData protocol. Click on Finish. SAP SuccessFactors Recruiting Management. 3) Register subaccount as OAuth client in SuccessFactors. In this guide, you'll learn how to work with OData v4. Choose Refresh. 0 bot from CAI chatbot to update SuccessFactors Principal Propagation in SAP Integration Suite from external system to SuccessFactors Using OAuth 2. 509 Certificate in SAP SuccessFactors Generating a SAML Assertion Requesting an Access Token SAP SuccessFactors HXM Suite all versions. Utilize server-side functionality and intelligent row-scanning to detect data types. 0 authentication: Use /oauth/idp to pass a private key to generate a signed SAML assertion. Steps to Download Odata API Audit Logs:learn how to work with OData v4 APIs in SAP SuccessFactors HXM Suite and what services we currently offer. Here's a list of API servers and mTLS certificate servers for SAP SuccessFactors data centers. To. URL of the SuccessFactors data center that you're connecting to. On your IPS tenant, go to your Source System, then select ‘ Jobs ‘ tile, and at ‘ Read Job ‘, select ‘ Run Now ‘ action. Using postman everything works fine but, once I check the connection of destination previously created, the response received is 401: Unauthorized. Center, you can build customized file extracts with any data using the SAP SuccessFactors OData APIs catalog. The value of sf. 2. 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. Common APIs under SAP. Configure People Profile. 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. Open the created artifact in Edit mode, choose Import Model Wizard. ) via OData API to local database for third party integration. A brief description on the different IDs which are used within Employee Central. This guide focuses on OData version 2. 2. Choose Internet. The field is auto-populated with /odata/v2. February 27, 2023. SAP SuccessFactors HXM Suite OData API provides methods for create, read, update and delete operations. SAP SuccessFactors Performance Management. SuccessFactors Learning customers, partner and implementation vendors need to identify the appropriate ODATA API information for LMS integration, configuration and customizations Where can customers find the latest SuccessFactors LMS ODATA API version documentations a. It acts as the master data broker between your core HR system of record – for example, SAP SuccessFactors Employee Central – and SAP S/4HANA. URL of the SuccessFactors data center that you're connecting to. Admin password – Enter the password of the SuccessFactors API user account. Select the edit option as we plan to use the same account for the Writeback to SuccessFactors scenario. Step a: Add a Request-Reply step to make OData call to get User data from SuccessFactors with below configuration. Successfactors. 1 - Mule 4. For example, CamelHttpQuery=abcd=1234. Conclusion… So now that we have seen what OAuth is, what its capabilities are, and how it can be easily implemented we must isolate use cases where OAuth is not suited and hence should not be used. It covers comprehensive guidelines for picking the right API for different use cases, delta and deletion handling, handling date/time data with API, batching API request, accessing workflow data and. 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. Sample. This is a collection of the most useful SAP SuccessFactors Employee Central resources: documents, blogs, reports, and videos. The custom MDF has three fields externalCode as AutoNumber, User ID as USER and comments as String. Creating User IDs via Option 1 (Provisioning) 14. So, we arrived at the last and critical part of the scenario, to trigger save rule while updating pay component information via ODATA API call. I want to reduce the number ofSetup mTLS (mutual Transport Layer Security) as your authentication method between Identity Provisioning and SuccessFactors. 0 client enables one to access protected. Blog – SuccessFactors: all you need to know about Authorizations and Security SAP Help Portal 41 7 7,960. The permissions listed here grant users and administrators access to the SAP SuccessFactors OData API and SFAPI. Call the “Photo” OData API, for demo purpose I’m using the s/w postman to query data. Consult the following page for reference on which permissions related to the User entity are needed: SAP SuccessFactors HXM Suite OData API: Reference Guide Besides granting the proper permissions to the API user, be sure that the users which should be queried are included in the target population of the permission role related to the API user:This blog is to demonstrate the steps to upsert an attachment in custom MDF through OData API. 11 5 2,306. 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. 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.