--- sourceDocument: Yokohama Build or modify applications sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/yokohama/application-development Release : - yokohama ft:locale : - en-US ft:publication_title : - Yokohama Build or modify applications ft:clusterId : - cadev bundleId : - cadev workflow : - Development, Data, and Analytics --- # Connect ERP Canvas to SAP using OData and HTTP # Connect ERP Canvas to SAP using OData and HTTP {#ariaid-title1} * Release version: Yokohama * * Updated January 30, 2025 * * ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 2 minutes to read Summarize ![AI sparkle icon](https://servicenow.com/docs/portal-asset/ai-sparkle-icon) Summarized using AI This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete. ## Summary of Connect ERP Canvas to SAP using OData and HTTP This guide explains how ServiceNow customers can securely extract data from SAP ERP systems using OData v2 APIs via HTTP connections in ERP Canvas. It enables integration by linking SAP data with ServiceNow remote tables and extraction tables, facilitating seamless data use within the platform. Show full answer Show less **Important:** OData v2 does not support snapshot isolation, which may lead to data consistency issues when retrieving data externally from SAP. ## Key Requirements and Setup * An SAP system must be enabled to support OData connections. * To provide users with OData access, appropriate authorizations must be assigned on the SAP backend as per SAP's guidelines. * Ensure XML file downloads are permitted by verifying that the `glide.attachment.extensions` system property does not restrict XML file types. ## Configuration Properties Several system properties in ServiceNow control and customize the OData integration: * **snerpintegration.catalogservicepath:** Defines the SAP catalog service path for retrieving and storing a list of available OData services as an XML attachment for offline use. * **snerpintegration.odataservicepath:** Specifies the SAP OData service endpoint path used for data extraction. * **snerpintegration.responsetimeout:** Sets the timeout duration (in seconds) for OData responses to manage call latency issues. * **snerpintegration.usecookies:** Indicates whether cookies should be used during OData connections. * **snerpintegration.usecsrftoken:** Controls whether CSRF tokens are sent with OData calls to enhance security. Administrators can manually create or modify these properties within the ERP Canvas scope via the system properties list. ## Monitoring and Health Checks ERP Canvas maintains separate heartbeat indicators for RFC and HTTP protocols to monitor connection health. Successful heartbeat checks trigger parallel data retrieval via BAPI (RFC) and OData (HTTP), with statuses viewable on the ERP system record. ## Additional Information * For detailed instructions on creating OData connections and supported query capabilities, customers should refer to the dedicated ERP Canvas documentation sections on OData integration. * Regularly updating the SAP catalog service data involves removing the existing XML attachment and re-fetching the service list to reflect any changes. Extract data securely from ERP OData v2 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 {#erp-canvas-use-odata-and-http-connection__section_nhc_nl4_bdc} You must have an SAP system that has been enabled to make an OData connection. 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](https://help.sap.com/doc/saphelp_ssb/1.0/en-US/6f/0e415370107d77e10000000a441470/content.htm?no_cache=true). ## Allowing download of XML files {#erp-canvas-use-odata-and-http-connection__section_h4n_vcx_c2c} The glide.attachment.extensions system property restricts the file types that can be downloaded. This property is empty by default. Check that the xml file extension has not been added to this property. For more information, see [Restrict attachment file extensions](https://www.servicenow.com/docs/access?context=t_DisablingTheDragAndDropFeature&version=yokohama&pubname=yokohama-platform-administration§ion=t_RestrictingFileExtensions&ft:locale=en-US). ## New properties {#erp-canvas-use-odata-and-http-connection__section_lrf_vl4_bdc} The following are properties related to OData.{#erp-canvas-use-odata-and-http-connection__table_qkj_xs4_bdc__entry__5} | Property | Type | Description | Create manually? | Role needed to edit property | |-|-|-|-|-| | 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 is 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. Note: If there is an update in the catalog service and you want to update the catalog information in the table, first remove the attachment displayed on the ERP Systems page and then run the retrieval process again to refresh the list. | Yes | admin | | 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 | admin | | 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 | admin or sn_erp_integration.erp_admin | | sn_erp_integration.use_cookies | true \| false | Specifies if cookies must be used for OData connection. | No | admin or sn_erp_integration.erp_admin | | sn_erp_integration.use_csrf_token | true \| false | Indicates if CSRF token should be sent for OData calls in ERP Canvas operations. | No | admin or sn_erp_integration.erp_admin | [ ] {#erp-canvas-use-odata-and-http-connection__table_qkj_xs4_bdc} Note: To add a new property manually, verify that your scope is set to ERP Canvas, then navigate to sys_properties.list and select New. ## Heartbeat information {#erp-canvas-use-odata-and-http-connection__section_idp_3p4_bdc} 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. ## More information {#erp-canvas-use-odata-and-http-connection__section_jtn_kyk_fdc} For more information about using OData in ERP Canvas, see [Create an OData connection in ERP Canvas](https://servicenow-prod.fluidtopics.net/EuQgWZf8jYw9Rn8sCkS5Uw "Create an OData v2 connection to link to SAP via HTTP so data can be extracted for use in remote tables and extraction tables.") and [OData capabilities supported by ERP Canvas](https://servicenow-prod.fluidtopics.net/hWaxy_VMZOzwsM3B~CzhaA "Details about the OData v2 query capabilities supported in ERP Canvas."). * **[OData capabilities supported by ERP Canvas](https://servicenow-prod.fluidtopics.net/hWaxy_VMZOzwsM3B~CzhaA)** Details about the OData v2 query capabilities supported in ERP Canvas. * **[Create an OData connection in ERP Canvas](https://servicenow-prod.fluidtopics.net/EuQgWZf8jYw9Rn8sCkS5Uw)** Create an OData v2 connection to link to SAP via HTTP so data can be extracted for use in remote tables and extraction tables.