Skip to content

Data strategy · Architecture · Governance

Data & Analytics Architecture

Where should your enterprise turn data into decisions?

A closing balance, a group margin and a forecast can start with the same posting. Each needs a different owner, time horizon and place to run. I help teams make those choices across SAP and enterprise data platforms.

Explore the approach
Logical enterprise analytical environment linking SAP and non-SAP sources, a business data hub, warehouse, advanced models and consumption within shared governance.
Enterprise Analytical Environment · Logical Responsibilities

The data architecture challenge

Who owns the number after it leaves the source?

A metric can reconcile in Finance and still tell a different story in Sales. Trace its meaning, permitted uses and operating cost before deciding where to model it.

Competing definitions

Does margin include rebates? Agree on grain, currency and timing before certifying a shared measure.

Unclear platform roles

Two teams may pay to store and transform the same postings. Give each reusable product an accountable owner.

Lost access context

A report can reach the warehouse through a shared identity. Test what two users with different entitlements can actually see.

Uncontrolled forecasts

When actuals change after sign-off, planners need an agreed snapshot and a record of which assumptions were approved.

Data Journey Explorer

“We Need an Overdue Receivables Report.”

What decision will this report support? Choose the answer you might hear in a workshop and see where the decision tree takes the request.

Operational Data Journey Candidate

The collector needs current open items from SAP S/4HANA to act on a customer account.

Evidence to gather
Demonstrate the standard SAP app with a collector. Confirm that cleared invoices drop off the list, access is appropriate and the expected workload is acceptable.
Next action
Record a standard fit when the evidence supports it. If a gap remains, assess released SAP content and route complex requirements for architecture review.

Corporate Data Journey

Credit management needs comparable balances across legal entities, source systems and reporting periods.

Evidence to gather
Agree on customer identity, currency and aging buckets. Decide how to retain balances as they stood at each period end.
Next action
Route the request to the corporate data team. Use the Data Warehouse to publish a reconciled historical measure that other reports can reuse.

Planning Journey

Treasury needs to change assumptions and see how future receipts move against an approved baseline.

Evidence to gather
Identify the actuals that anchor the forecast, who owns the payment assumptions and who approves a version.
Next action
Route the request to the planning team with the baseline, scenario inputs and approval owner identified.

Screening Pending

The request names a report, but the team cannot yet identify who will use it or what they will decide.

Evidence to gather
Ask the requester who acts on the result, what they would do differently and whether they need current items, historical comparisons or a simulation.
Next action
Keep the request open with an owner and the missing evidence. Resume screening when the business purpose is clear.

For a full reporting backlog, the Analytics Demand Decision Tree sets the rules. The screening workbook records the evidence, route and next action for each request so business and delivery teams can review open decisions together.

Choosing the right analytical architecture

Choose the enterprise analytical center of gravity first. Then decide which responsibilities each platform can sustain.

SAP-centric

When SAP business semantics and SAP-led processes carry most of the analytical workload, test how well a SAP-centered platform preserves meaning from source to consumer.

Prove that non-SAP history, AI workloads and external consumers can meet their service and access requirements at an acceptable cost.

Enterprise-platform-centric

When several domains already share engineering, compute and operations, test the enterprise platform as the primary analytical environment.

Measure the effort to retain SAP semantics, reconcile deltas and enforce identity across the boundary. Include exit costs and the skills needed to run both sides.

Where does SAP Business Data Cloud fit? It can lead SAP-centric analytics, supply contracted products to an enterprise platform, or serve a specialized SAP workload. Justify coexistence with a representative proof of concept, a consumer contract and an owner for recurring costs.

From strategy to governed execution

The Agnostic Informational Architecture separates logical responsibilities from deployment choices. Its Enterprise Analytical Environment gives each producer, model and consumer a place in the design.

  1. Assess

    Map the decision, users, sources and current cost of serving it.

  2. Architect

    Place acquisition, history, advanced models and consumption. Assign ownership at each handoff.

  3. Validate

    Run the same workload on viable platforms. Compare freshness, identity, cost and reversibility.

  4. Govern

    Certify grain, definitions, access and change contracts before releasing a data product.

  5. Operate

    Monitor delays, failed loads and spend. Name the team that reconciles and restores service.

Explore the research behind these logical responsibilities in Research & Publications.

Architecture Deliverables

The strategy framework sets the direction. The decision tree defines where each request belongs, and the screening workbook applies those rules report by report. The three handbooks guide platform delivery.

SAP Datasphere Architecture, Engineering & Governance

How do you make Datasphere production-ready?

What it is
Engineering guidance for domain Spaces, data contracts and logical Bronze, Silver and Gold layers.
Why it matters
Facts (DCA), master data (MCA) and consumption models (ICA) carry different stewardship duties. These are design roles within the method.
What it enables
Test effective identity and Data Access Controls through the actual consumer, including controlled Power BI paths. The handbook spans 22 phases and six quality gates.
How it adapts
Place logical roles in physical Spaces according to isolation, dependencies and reuse. Copy data only where justified.

SAP Analytics Cloud Seamless Planning Architecture & Operations

How can planners use trusted actuals and control the approved result?

What it is
A planning design connecting SAC models with supported Datasphere storage, certified actuals and master data.
Why it matters
Finance needs to distinguish an approved planning version from a technical release and permission to publish.
What it enables
Govern Data Actions, Multi Actions, version access and reconciliation for cash flow, OPEX or CAPEX.
How it adapts
Assess S/4HANA publication per target. Verify budget execution and availability control separately when required.

Architecture in Practice

Illustrative examples of how the approach applies to recurring architecture problems.

Modernizing SAP analytics

Finance wants a shared margin figure across company codes. Compare candidate SAP-managed products against the required grain and coverage. Certify the chosen measure with Finance and record who handles upstream changes.

Connecting a heterogeneous estate

An enterprise platform already joins sales and logistics. Keep cross-domain analysis there if a PoC can reconcile SAP postings and preserve effective access. Give the boundary a versioned contract and a recovery owner.

Governing enterprise planning

Treasury needs to rerun its cash forecast after a late close. Pin the actuals snapshot, separate working and approved versions, and reconcile any authorized publication against the signed-off plan.