This page shows you how to resolve common issues when you integrate SAP Business Data Cloud (BDC) with BigQuery.
NOT_FOUND or PERMISSION_DENIED errors when querying tables
This issue occurs when access is revoked on the SAP BDC side. Queries to the affected tables fail and return a "not found" or "permission denied" error originating from the Delta Sharing endpoint.
To resolve this issue, work with your SAP administrator to restore access to the tables. For more information about access management in SAP, see Working with Data Products in SAP Business Data Cloud Connect in the SAP documentation.
Data is stale or not updating
You query data live from SAP BDC by using the Delta Sharing protocol. New tables and table updates are periodically discovered by Lakehouse for Apache Iceberg according to the catalog's configured refresh interval. If data is not updating, the refresh interval might be too long or the background metadata refresh might be failing.
To resolve this issue, check the catalog's refresh interval and verify that the background metadata refresh cycle is completing successfully.
Cannot write data to SAP BDC tables
This issue occurs when you attempt to write or modify data in your SAP BDC tables from BigQuery. This integration provides read-only access to SAP BDC data.
To resolve this issue, modify the data directly in SAP BDC.
Unexpected pricing charges for Delta Sharing API calls
This issue can occur if your Lakehouse catalog synchronizes too frequently with SAP BDC, which calls Delta Sharing APIs to list tables and get table metadata. Those API calls are charged as Lakehouse Class A operations.
To resolve this issue, increase the catalog's refresh interval to reduce the frequency of API calls. For more information, see Lakehouse pricing.
SAP cannot find or query published tables
This issue can occur if the Apache Iceberg metadata required by SAP BDC has not been generated correctly in your Cloud Storage bucket.
To resolve this issue, verify that the expected metadata files exist at the storage path backing your table:
List the contents of the
metadatafolder for your table:gcloud storage ls "gs://BUCKET_NAME/NAMESPACE_NAME/TABLE_NAME/metadata/"
Verify the output contains standard Apache Iceberg metadata files, including:
version-hint.txtv*.metadata.json- Manifest files (
.avro). If these files are missing, check your Iceberg REST catalog configuration or write operations in BigQuery to ensure data and metadata are being successfully materialized to the storage bucket.
Queries on SAP fail with permission or not found errors
This issue can occur if access is revoked or permissions are modified in BigQuery after a catalog or Data Product has been published to SAP BDC. Queries to the affected tables will fail on the SAP side, typically with a "not found" or "permission denied" error originating from BigQuery.
To resolve this issue, verify that the Workload Identity Federation principal retains the required roles (like BigLake Viewer) and that standard BigQuery dataset/table access is granted. For more information about installing and consuming Data Products in SAP, see Installing Data Products in the SAP documentation.
New tables or metadata changes are not appearing in SAP BDC
This issue can occur when you add new tables or update existing table metadata in your Apache Iceberg REST catalog or Knowledge Catalog Data Product, but the changes are not visible to SAP consumers. While the underlying data remains fresh, metadata updates might require explicit action.
To resolve this issue, execute a new publish action (gcloud alpha biglake
data-product-sharing publish) for the catalog or Data Product to make the new
metadata discoverable in SAP BDC.
Unable to write data from SAP back to BigQuery
This issue occurs when you attempt to use the published SAP integration to write or modify data in BigQuery from SAP BDC. This integration provides read-only access to BigQuery data from SAP BDC to prevent accidental overwriting of data or security violations.
To resolve this issue, manipulate and write your source data directly using BigQuery or standard Google Cloud pipelines.
RESOURCES_NOT_IN_SAME_SERVICE_PERIMETER errors when querying tables
This issue can occur if your environment has VPC Service Controls enforced, and
the perimeter applied on the project restricts the storage.googleapis.com service.
Because Dremel needs to read the incoming Cloud Storage buckets in the SAP
project when querying tables, the request is prohibited since the SAP project
is outside your perimeter.
To resolve this issue, configure a VPC Service Controls egress rule. For more information, see VPC Service Controls configuration for SAP BDC.