--- sourceDocument: Australia Workflow Data Fabric sourceDocumentLink: https://www.servicenow.com/docs/r/australia/integrate-applications Release : - australia ft:locale : - en-US ft:publication_title : - Australia Workflow Data Fabric ft:clusterId : - crint bundleId : - crint workflow : - Creator --- # OData # Connecting Zero Copy Connector for ERP to ERP using OData {#ariaid-title1} Release version: Australia Updated August 5, 2026 ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 3 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 Connecting Zero Copy Connector for ERP to ERP using OData This guide explains how ServiceNow customers can securely extract data from ERP systems using OData v2 APIs through the Zero Copy Connector for ERP. It highlights key considerations such as potential data consistency issues due to OData v2's lack of snapshot isolation and prerequisites for enabling user access to OData services on the ERP backend. Show full answer Show less ## Configuring OData Access and System Properties To provide OData access, the ERP system must have OData enabled, and users require assigned OData service authorizations as per ERP vendor documentation (e.g., SAP). The glide.attachment.extensions system property must be checked to ensure XML file downloads are allowed, important for handling OData service catalog data. Several critical system properties govern OData integration: * **snerpintegration.catalogservicepath**: Defines the fixed path used to connect to the SAP OData Service Catalog across all ERP systems in the instance. A correct path enables automatic retrieval and storage of catalog information as an XML attachment on the system record. If the ERP uses a different path, services must be added manually. * **snerpintegration.odatamaxrecordfetchlimit**: Limits the maximum records retrieved in GET requests to manage performance. * **snerpintegration.odataservicepath**: Specifies the path for connecting to SAP OData services; this is a single path applied globally. * **snerpintegration.responsetimeout**: Sets the response timeout in seconds for OData calls, adjustable to prevent frequent timeouts. * **snerpintegration.usecookies** and **snerpintegration.usecsrftoken**: Control whether cookies and CSRF tokens are used for secure OData communications. These properties can be created or edited within the Zero Copy Connector for ERP scope and require admin or ERP admin roles. ## Heartbeat Monitoring and Data Retrieval Heartbeat indicators monitor connectivity status separately for RFC and HTTP protocols. When active and successful, parallel BAPI and OData data retrievals occur, with statuses reflected on the ERP system record, enabling proactive monitoring and troubleshooting. ## Practical Implications for ServiceNow Customers * Customers can integrate ERP data into ServiceNow through OData v2, supporting remote and extraction tables for flexible data use. * Configuring system properties properly ensures connectivity, performance tuning, and security compliance when accessing ERP OData services. * Manual management of OData service catalogs may be necessary if ERP systems deviate from standard catalog service paths. * Heartbeat monitoring provides real-time status, facilitating maintenance and troubleshooting of ERP integrations. Extract data securely from ERP OData v2 APIs for use in remote tables and extraction tables. Important: OData v2 doesn't 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 ERP system enabled for OData connections. 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). ## Enabling 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 hasn't been added to this property. For more information, see . ## System 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 path is used to connect with the SAP catalog service on every ERP system in the instance. The default is /sap/opu/odata/iwfnd/CATALOGSERVICE;v=2/ServiceCollection. The value must be the address of the OData Service Catalog. This property applies to all ERP systems in the instance. You can't set a different catalog service path for each system. If an ERP system exposes its catalog service at a different path, its services aren't retrieved. To use those services, add them manually. For more information, see [Add an OData service manually in Zero Copy Connector for ERP](https://www.servicenow.com/docs/X68Vhz7LY9gxZxmLWTwAkg "When adding an entity to a model using OData, if the service you need isn't listed, add the service manually in Zero Copy Connector for ERP (Enterprise Resource Planning)."). After creating the property and setting its value to the catalog service path, 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: To update the table catalog information after the catalog service changes, first remove the attachment displayed on the ERP Systems page. Then, run the retrieval process again to refresh the list. | Yes | admin | | sn_erp_integration.odata_max_record_fetch_limit | integer | Limits the number of records fetched for GET calls by adding the $top parameter to the OData calls. This reduces the number of records read from the OData endpoint. | No | admin | | sn_erp_integration.odata_service_path | string | After the hostname and port, this path is used to connect with any SAP OData service. Add a URL in Value to specify the OData service. The value is a single path, not a list of paths. 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 time 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 whether to use cookies for an OData connection. | No | admin or sn_erp_integration.erp_admin | | sn_erp_integration.use_csrf_token | true \| false | Indicates whether a CSRF token is sent for OData calls in Zero Copy Connector for ERP operations. | No | admin or sn_erp_integration.erp_admin | [ ] {#erp-canvas-use-odata-and-http-connection__table_qkj_xs4_bdc} Note: To add a property manually, verify that your scope is set to Zero Copy Connector for ERP, 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 are set to 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 appears on the system record. ## More information {#erp-canvas-use-odata-and-http-connection__section_jtn_kyk_fdc} For more information about using OData in Zero Copy Connector for ERP, see [Create an OData connection in Zero Copy Connector for ERP](https://www.servicenow.com/docs/l1jHe2bdOy_9g6tuxPcXkA "Create an OData v2 connection to link to an ERP system so data can be extracted for use in remote tables and extraction tables.") and [OData capabilities supported by Zero Copy Connector for ERP](https://www.servicenow.com/docs/lX20xWH2Nnf~mfBN3ZLk4Q "Zero Copy Connector for ERP (Enterprise Resource Planning) supports the $select, $filter, and $orderby OData v2 query capabilities.").