Connect ERP Data Hub to SAP using OData and HTTP

  • Release version: Xanadu
  • Updated October 16, 2024
  • 2 minutes to read

    • Extract data securely from ERP OData APIs using ETL for use in remote tables and extraction tables. OData connects to SAP via HTTP.

    Important:

    OData v2 does not use snapshot isolation so you might experience some data consistency issues when retrieving data from an external ERP source.

    Providing OData access to users

    You must have an SAP system that has been enabled to make an OData connection.

    As of Xanadu Store Release 2, extract data using OData and an HTTP connection. To give users OData access, see the following instructions on the SAP help site Back-End Server: Assign OData Service Authorization to Users.

    New properties

    The following are properties related to OData available for ERP in Xanadu Store Release 2.
    Property Type Description Create manually?
    sn_erp_integration.response_timeout integer Specifies the timeout value for OData response. If OData calls are timed out frequently, increase the timeout value. Specify the value in seconds. The default is 100 seconds. This value is used for responses both from external web and from a MID Server. No
    sn_erp_integration.use_csrf_token true | false Indicates if CSRF token should be sent for OData calls in ERP Data Hub operations. No
    sn_erp_integration.catalog_service_path string After the hostname and port, this is the path to connect with any SAP catalog service. The default is: /sap/opu/odata/iwfnd/CATALOGSERVICE;v=2/ServiceCollection. After creating the property and setting it to true, a list of all services are retrieved from SAP. The information is stored in an XML file and attached to the system record. The XML can be used later. For example, parse the XML while offline with no connection to SAP. Yes
    sn_erp_integration.odata_service_path string After the hostname and port, this is the path to connect with any SAP OData service. Add a URL in Value to specify the OData service. The default is: /sap/opu/odata/sap. Yes
    Note:
    To add a new property manually, verify that your scope is set to ERP Data Hub, then navigate to sys_properties.list and select New.

    Heartbeat information

    For an ERP system, there are separate heartbeat indicators for RFC and HTTP. When a system is established, the heartbeats become active and the status is updated, including any errors. If the heartbeat calls are successful, BAPI and OData retrieval is triggered in parallel and the status can be seen on the system record. BAPI and table list retrieval is done via RFC. OData retrieval is done via HTTP.

    ERP Data Hub systems page with RFC and HTTP heartbeat status.

    More information

    For more information about using OData in ERP Data Hub, see Create an OData connection in ERP Data Hub and OData capabilities supported by ERP Data Hub.