Overview
What is SAP BW/4HANA: SAP BW/4HANA is SAP SE's enterprise data warehouse for on-premise and private cloud deployment. Built entirely on SAP HANA, it consolidates SAP and non-SAP sources into a governed warehouse layer where project teams apply business rules, including hierarchies and analysis authorizations. SAP BW/4HANA 2023 remains under mainstream maintenance through December 31, 2030.
How to integrate SAP BW/4HANA with Datagrid
Datagrid connects to the SAP HANA database layer beneath BW/4HANA through a generic SAP HANA SQL connection. SAP BW/4HANA can generate external SAP HANA calculation views from CompositeProvider models, aDSOs, InfoObject master data, and BW queries; SAP administration and data teams configure these views, authorize the database user, and BW/4HANA then makes the views available as HANA SQL objects over JDBC or ODBC. When authorized external HANA views are available, data flows in one direction from BW/4HANA into Datagrid as full loads on the configured schedule. Datagrid's AI agents then query the authorized models, analyze the returned data, and route results into operational workflows, while business rules and security controls remain in BW/4HANA. The setup does not cover OData or ODP ingestion. Follow this setup order: configure the SAP HANA connection, authenticate the database user, then schedule one-way data syncs.
Configure the SAP HANA connection
Complete the connection setup in Datagrid:
Sign in to Datagrid.
Click Integrations.
Select the SAP HANA thumbnail.
Enter the connection details: host or IP address, port, and database name.
Enter the database user ID and password.
Click Validate, then Save.
Use the following structure to prepare the connection values:
host_or_ip: <HANA host or IP>
port: <HANA port>
database_name: <database name>
user_id: <database user ID>
password: <database user password> If validation fails, check for an incorrect host or IP, gaps in the IP allowlist, TCP disabled, or an invalid database name.
Authenticate the database user
The integration uses direct SQL access to the HANA database layer with a user ID and password. SQL access through generated HANA views requires generated-view authorizations in both SAP HANA and SAP BW/4HANA. SAP HANA Analytic Privileges map against BW Analysis Authorizations at query runtime.
Use this credential-field structure:
authentication_type: Database user
user_id: <database user ID>
password: <database user password> Schedule one-way data syncs
Project teams can expose aDSOs, CompositeProviders, InfoObjects, and BW queries as external HANA views. After they authorize the database user, Datagrid can query those views as HANA SQL objects for agent processing. Extraction is pull-based; BW/4HANA does not push events.
Use a deployment-specific generated-view identifier in the SQL query:
SELECT *
FROM <authorized_generated_hana_view>; The following table describes potential SQL access through generated external HANA views:
aDSO: External HANA view, Export
CompositeProvider: External HANA view, Export
InfoObject (master data): External HANA view, Export
BW query: External HANA view, Export
Reads for aDSOs, CompositeProviders, and InfoObject master data return full loads. BW query reads return snapshots or full loads. BW/4HANA supports change-log delta through separate ODP-BW paths for some objects, but ODP-BW delta extraction and object-specific sync behavior are outside the current Datagrid integration scope.
Why use SAP BW/4HANA with Datagrid
Connecting governed BW/4HANA models to Datagrid gives project teams an execution path from curated warehouse data to analysis, reports, notifications, and downstream records.
Governed data can feed agents directly: Project teams expose predefined measures, hierarchies, filters, and authorization behavior through external HANA views. Where supported by the view, these can include currency conversions and security filters.
One warehouse replaces many source connections: Operations and data teams read cross-source data from BW/4HANA when project teams expose the relevant SAP and non-SAP models as authorized SQL views.
Agents execute extraction workflows: Project teams query warehouse data, analyze the returned data, and route results and notifications through automated retrieval.
Write-back through connected systems: Account and operations teams push warehouse-computed scores and segments from BW/4HANA into CRM and operational tools via Datagrid's other integrations, keeping warehouse-derived account data available where teams act on it.
What you can build with SAP BW/4HANA Datagrid integration
Project teams can turn authorized warehouse views into repeatable reporting and planning workflows that support account action. The following examples keep modeling in BW/4HANA while agents execute analysis and delivery.
Curated analytics agents for sales and supply chain: An agent queries an authorized external view generated from a BW/4HANA CompositeProvider that holds consolidated sales performance data. It compares results against targets and delivers a summarized report to the operations lead. Business logic stays in the warehouse where the generated view preserves it; the agent handles retrieval and interpretation.
Extraction and analysis workflows: Agents query configured warehouse views and route the results to the data team. Engineers can then focus on analysis, and teams that field repetitive data-status questions can route them to a data analysis agent.
Consolidated demand signals for predictive replenishment: A retail agent extracts demand data that BW/4HANA has already merged from ERP, POS, and supplier feeds. It hands larger modeling jobs to a connected analytics environment, then generates replenishment recommendations from that merged data.
Reverse ETL from warehouse to CRM: An agent reads customer segmentation or churn scoring exposed from BW/4HANA and writes it into CRM records through a connected system. Reps act on the risk score directly in their account view.
Resources and documentation
CompositeProvider models: SAP guidance for CompositeProviders exposed through generated views.
InfoObject master data: SAP guidance for InfoObject master data in SAP BW/4HANA.
Generated-view authorizations: Configuration guidance for SAP HANA and SAP BW/4HANA access.
Creating an OData query: SAP's instructions for configuring separate OData access.
SAP BW/4HANA Security Guide: Application-server authentication and security guidance.
Frequently asked questions
Can Datagrid extract data using ODP-RFC?
No. Third-party applications cannot use RFC modules of the ODP Data Replication API, and SAP has moved to block unauthorized calls at the protocol level. Use authorized external HANA views for SQL access instead.
How do you expose a BW query for external access?
Generate an external SAP HANA view for the BW query and grant the required SAP HANA and SAP BW/4HANA authorizations. SAP can separately expose a query over OData by following the instructions for Creating an OData query and enabling By OData under General > Remote Access.
How do you authenticate BW/4HANA connections?
Use a database user ID and password for the SAP HANA SQL connection. The SAP BW/4HANA Security Guide also lists these authentication methods at the application server layer: user ID and password, SNC, SAP Logon Tickets, and OpenID Connect.
Does the integration support webhooks or event push?
No. Native BW/4HANA webhooks and event push are outside the scope of this integration. Extraction is pull-based on the configured schedule.
Similar integrations
Databricks: Downstream analytics environment for BW/4HANA exports, supporting zero-copy or replicated warehouse data for model training and large-scale analytics.
BigQuery: Cloud data warehouse for ingesting BW/4HANA extracts and running scalable analytics or federated reporting alongside SAP datasets.
Amazon Redshift: Cloud warehouse target for Open Hub or exported BW datasets, with BI, reporting, and reverse-ETL workflows.
Azure Data Lake Storage: Enterprise data lake destination for BW/4HANA Open Hub or file-based exports used in downstream ETL, archiving, and analytics.
Amazon AWS S3: Object storage endpoint for Open Hub flat-file exports or staged BW/4HANA extracts feeding cloud analytics and ML pipelines.
Google Cloud SQL - PostgreSQL: Managed cloud Postgres for storing transformed BW/4HANA extracts, providing application-level access and reverse-ETL syncs to operational systems.