Skip to content
Release: Australia · Updated: 2026-03-12 · Official documentation · View source

Connect Zero Copy Connector for ERP to SAP using OData

Extract data securely from ERP OData v2 APIs for use in remote tables and extraction tables.

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.

To give users OData access, see the following instructions on the SAP help site: Back-End Server: Assign OData Service Authorization to Users.

Enabling download of XML files

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

The following are properties related to OData.

PropertyTypeDescriptionCreate manually?Role needed to edit property
sn\_erp\_integration.catalog\_service\_pathstringAfter the hostname and port, this path is used 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's an update in the catalog service and you want to update the table catalog information, first remove the attachment displayed on the ERP Systems page. Then, run the retrieval process again to refresh the list.Yesadmin
sn\_erp\_integration.odata\_max\_record\_fetch\_limitintegerLimits the number of records fetched for GET calls by adding the $top parameter to the OData calls to reduce the number of records read from the Odata endpoint.No 
sn\_erp\_integration.odata\_service\_pathstringAfter 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 default is: /sap/opu/odata/sap.Yesadmin
sn\_erp\_integration.response\_timeoutintegerSpecifies 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.Noadmin or sn\_erp\_integration.erp\_admin
sn\_erp\_integration.use\_cookiestrue \| falseSpecifies if cookies must be used for OData connection.Noadmin or sn\_erp\_integration.erp\_admin
sn\_erp\_integration.use\_csrf\_tokentrue \| falseIndicates if CSRF token should be sent for OData calls in Zero Copy Connector for ERP operations.Noadmin or sn\_erp\_integration.erp\_admin

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

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 can be seen on the system record.

Image omitted: erpc-system-heartbeats.png
System record with ODATA retrieval status of completed.

More information

For more information about using OData in Zero Copy Connector for ERP, see Create an OData connection in Zero Copy Connector for ERP and OData capabilities supported by Zero Copy Connector for ERP.

Parent Topic:Configuring Zero Copy Connector for ERP