What's new with BigQuery Connector for SAP

Stay organized with collections Save and categorize content based on your preferences.

This document lists significant changes to the BigQuery Connector for SAP including version-specific enhancements.

To view all of the announcements from SAP on Google Cloud, see Release notes.

Updating BigQuery Connector for SAP

For information on how to update BigQuery Connector for SAP, see Update BigQuery Connector for SAP.

Version 2.5


  • Support for RFC destinations: You can now use RFC destinations to connect to Google Cloud. To get you started, the transport files include sample RFC destinations. By using RFC destinations, you can perform the following: connect to Google Cloud through Private Service Connect endpoints, configure proxy server settings, and enable HTTP compression. For more information, see RFC destinations.

  • Support for using Private Service Connect: You can now use Private Service Connect (PSC) endpoints to allow private consumption of Google Cloud APIs and services. You specify your PSC endpoints in your RFC destinations that the connector uses to connect to Google Cloud. RFC destinations are new with version 2.5 of BigQuery Connector for SAP. For more information, see:

  • Token caching: To improve replication performance and fault tolerance, the BigQuery Connector for SAP now supports caching of the access token that allows access to BigQuery. For more information, see:

  • Automatic retry of access token retrieval for off-Google Cloud workloads: For SAP workloads that are running outside of Google Cloud, BigQuery Connector for SAP now automatically retries access token retrieval in case there is a failure to do so. You can control the number of retries by setting a value for the advanced setting parameter CMD_EXEC_TRIES. For more information, see Advanced settings.

  • Authenticate to Google Cloud using JWT for off-Google Cloud workloads: For SAP workloads that are running outside of Google Cloud, you can now set up authentication to Google Cloud and authorization to access BigQuery using JSON Web Tokens (JWT) signed by Google Cloud. With JWT based authentication, you can authenticate to Google Cloud without the need of installing the Google Cloud CLI and creating an OS level command on the SAP LT Replication Server host. For more information, see Authentication using JWT to obtain access tokens.

  • Dynamic chunk sizing: The dynamic chunk size feature enables you to automatically reduce the chunk size and retry replication to BigQuery when the byte size of a chunk exceeds the maximum byte size for HTTP requests that BigQuery accepts. For more information, see Dynamic chunk size.

  • New enhancement exit: This version introduces a new enhancement exit that enables you to collect logging data in case of HTTP errors, after the HTTP calls to BigQuery API. You can use those logs for troubleshooting the HTTP errors. For more information, see Enhancement exits.

  • Load Simulation tool: The Load Simulation tool allows you to simulate load to BigQuery. This in turn enables you to assess replication performance, identify potential problems, understand the root cause of issues, and resolve them prior to actual replication of SAP data into BigQuery by using BigQuery Connector for SAP. For more information, see Load Simulation tool.

Version 2.2 to 2.4 (Not available)

Version 2.2 to 2.4 of BigQuery Connector for SAP are not available.

Version 2.1


  • Language support: The connector supports execution of background jobs that are running on the SAP LT Replication Server in all languages that SAP SLT supports. For more information, see Language support.

  • Troubleshooting invalid data errors: The connector contains improved error messages to help you troubleshoot invalid data errors. For more information, see Issue: Error messages related to invalid data.