Skip to content
Consumer Goods · SAP Business Data Cloud + BigQuery
Europe Architecture & data engineering lead, six months

SAP S/4HANA Analytics Modernisation on Google BigQuery for a Global Consumer Goods Group

A global consumer goods group wanted its SAP S/4HANA data in Google Cloud, governed and consistent, for cross-system analytics, planning and AI. We led the architecture and engineering: Datasphere as the semantic and governance layer, Replication Flows for change-data capture, BigQuery and Looker for consumption.

Client
Global consumer goods group
Region
Europe
Engagement
Architecture & data engineering lead, six months
SAP S/4HANA → DATASPHERE → BIGQUERY · CDC, GOVERNED, SEMANTICSOURCESAP DATASPHERECONSUMPTIONSAP S/4HANAFinance · SCM · SalesSLT · CDS · ODPReplication FlowsThree-layer modelsData productsGoogle BigQueryLookerSelf-service · AI/MLSAP DATA DELIVERY · DAYS → MINUTES

Days → minutes

SAP data delivery, through automated CDC pipelines

3

SAP domains modelled: finance, supply chain, sales

1

Source of truth across SAP and non-SAP data in BigQuery

3 layers

Inbound, harmonised, consumption — every dataset traceable

Requirement

The challenge

  • The group was harmonising information across SAP and non-SAP systems as part of its digital strategy: one enterprise data model, standard business definitions, and consistent reporting across regions.
  • A key objective was to expose SAP S/4HANA data into Google Cloud, with Microsoft Azure to follow, for cross-system analytics, integrated planning and AI/ML use cases, without losing governance or semantic consistency on the way out of SAP.
  • SAP data reached analytics teams in days. High-volume tables such as financial documents, material master and sales orders needed change-data capture at scale, not batch extracts.
Approach

How we went about it

  1. 1

    Datasphere at the centre

    We architected the SAP → Datasphere → Google Cloud flow with SAP Datasphere as the semantic and governance layer, so that what left SAP was already modelled, defined and governed rather than raw tables to be reinterpreted downstream.

  2. 2

    Change-data capture at scale

    Replication Flows, SLT and ODP with ABAP CDS views delivered high-volume CDC from S/4HANA, including financial documents, material master and sales orders, with latency measured in minutes.

  3. 3

    Layered, traceable models

    Inbound, harmonised and consumption layers in Datasphere; dimensions, facts, hierarchies and business entities aligned to finance, supply chain, sales and procurement, following clean-core practice.

  4. 4

    BigQuery as the landing zone

    With the Google Cloud teams we defined the landing patterns, so BigQuery received clean, structured, business-ready datasets from Datasphere views and data products. Curated datasets and Looker dashboards opened self-service and KPI reporting to the business.

Solution

What we delivered

  • End-to-end SAP S/4HANA → Datasphere → BigQuery architecture, designed and owned through implementation.
  • CDC replication pipelines for finance, supply chain and sales, built on Datasphere Replication Flows, SLT and CDS views.
  • Semantic models, data products and a three-layer modelling standard in Datasphere, with lineage, metadata and quality checks.
  • Security and access controls through Datasphere spaces, privileges and role-based access, with IAM, encryption and data classification across SAP and Google Cloud.
  • Curated BigQuery datasets and Looker dashboards for finance, supply chain and sales.
ToolsSAP Business Data CloudSAP DatasphereSAP S/4HANASLTABAP CDS viewsReplication FlowsGoogle BigQueryLooker

Outcomes

What changed for the client

  • SAP data delivery reduced from days to minutes through automated CDC pipelines.
  • A single source of truth across SAP and non-SAP datasets in BigQuery, with definitions that match SAP.
  • Business teams enabled for self-service analytics, financial insight, supply-chain optimisation and predictive use cases.
  • A cloud analytics foundation aligned with the group's digital strategy, designed to serve Google Cloud first and Azure next.

Related insights

All articles
GOVERNANCE · WHO DECIDESOWNERS DECIDE · STEWARDS MAINTAIN · ONE FORUM, MONTHLYDOMAINS · A BUSINESS OWNER ON EACHCustomerOWNER · HEAD OF SALESSupplierOWNER · HEAD OF PROCUREMENTProductOWNER · HEAD OF OPERATIONSSTEWARDS KEEP DEFINITIONS AND QUALITY CURRENTFour decisionsBUSINESS DECISIONS, NOT DATA DECISIONS1Who defines a metric2Who fixes quality at source3Who approves a new use4Who answers the regulatorOne forumMONTHLY · 30–60 MINSelf-servicebecomes safeAIbecomes assurableRegulatory questionstake hours, not weeksGOVERNANCE OWNED BY THE PEOPLE WHO RUN THE BUSINESS PRODUCES TRUST · DELEGATED TO A FUNCTION, IT PRODUCES DOCUMENTATION

Governance

Governance Is a Strategy Problem, Not a Checkbox

THE DATA ESTATE · INFRASTRUCTURE, NOT A COST CENTRERETURNS ARE NON-LINEARPlatformLAKEHOUSE · WAREHOUSEPipelinesINDUSTRIALISED, NOT HAND-RUNModelsONE DEFINITION OF EVERY METRICDecisionsPRICING · CREDIT · ROUTINGGOVERNANCE AND DEFINITIONS RUN THROUGH EVERY LAYERThe Monday testONE QUESTION, TWO ESTATESWITH THE ESTATEAsked Monday · answered MondayWITHOUT ITReconciled by hand, debated until FridayAND THE WHOLE SEQUENCE RUNS AGAIN NEXT TIMETHE FIRST ESTATE PAYS FOR DATA EVERY TIME IT ASKS A QUESTION · THE SECOND PAID ONCE AND DRAWS THE RETURN

Architecture

The Data Estate as Competitive Infrastructure

MANUFACTURING · 7 OPERATIONSDATA ENGINEERING + DATA SCIENCEDATA WAREHOUSE · SENSORS1Predictive maintenance2Real-time monitoring3Demand & inventory4Price optimisation5Supply chain6Product development7Worker safety

Manufacturing Analytics

7 Manufacturing Operations that Data Engineering & Data Science will Revamp