CAL & Associates

BTP, data and AI readiness

A clear-eyed read on modern SAP. Adoption is worth tying to a justified use case, demonstrated readiness and a governance position. This page describes assessment and readiness work.

Core, integration, extensions, data and governed AI The SAP core sits on the left, connected through an integration boundary to side-by-side extensions on the right. Governed data services run beneath both, and a controlled Business AI band sits above them. Governed AI SAP core Extensions API Data services Core, integration, extensions, data and governed AI The SAP core sits on the left, connected through an integration boundary to side-by-side extensions on the right. Governed data services run beneath both, and a controlled Business AI band sits above them. Governed AI SAP core Integration Side-by-side extensions Data services

Clean core

Standard capability first, then a deliberate choice

SAP’s clean-core guidance is that changes to delivered functionality should be built outside the core through supported extensibility. In practice that starts one step earlier: establishing whether standard configuration and released functionality already meet the requirement.

Where a genuine gap remains, the pattern should follow the requirement — an on-stack extension with ABAP Cloud, a side-by-side extension on SAP Business Technology Platform, or SAP Integration Suite for connectivity across SAP and non-SAP systems. None of these removes the work that follows: clean-core patterns reduce direct core remediation, while extensions and integrations still require impact analysis, security review, testing, operations and regression.

S/4HANA transformation
Where each kind of change lives, and who owns it Five zones. A controlled Business AI band sits at the top, drawn with a dashed boundary. Beneath it the SAP core on the left and side-by-side extensions on the right are separated by an integration boundary, crossed only by released interfaces. Governed data services run as a band beneath both. A responsibility note on each zone states who owns upgrade impact: SAP for the core, shared at the boundary, and the customer for extensions. Controlled Business AI Governed use cases only SAP core Standard and on-stack SAP owns upgrade impact Side-by-side extensions SAP BTP You own upgrade impact Boundary Released interfaces only Governed data services One owned foundation under both sides Where each kind of change lives, and who owns it Five zones. A controlled Business AI band sits at the top, drawn with a dashed boundary. Beneath it the SAP core on the left and side-by-side extensions on the right are separated by an integration boundary, crossed only by released interfaces. Governed data services run as a band beneath both. A responsibility note on each zone states who owns upgrade impact: SAP for the core, shared at the boundary, and the customer for extensions. Controlled Business AI Governed use cases only SAP core Standard and on-stack SAP owns upgrade impact Boundary Released interfaces only Side-by-side extensions SAP BTP You own upgrade impact Governed data services One owned foundation under both sides
The boundary is the design. What crosses it should be a released interface, and each side of it has a different answer to the only question that matters at the next upgrade: who is holding this? Readiness assessment precedes production adoption, and nothing in this diagram is claimed as delivered.

Data and AI

Readiness is a data and process question first

SAP Business Data Cloud brings together SAP Datasphere, SAP Analytics Cloud and SAP Business Warehouse, and SAP Business AI is embedded across SAP applications with Joule as its assistant. Which of them is right for you is a later question than whether your data and processes can support acting on the output.

Data ownership

Who decides what a valid record looks like in each domain, and who is accountable when it is wrong.

Semantic quality

Whether a figure means the same thing in every system that reports it.

Process consistency

Where a transaction is handled differently across entities, automation may encode the variant present in its inputs.

Authorization

What an automated step may do, under whose authorization, and how that is evidenced to an auditor.

Automation boundaries

Which decisions keep a person in the loop — period close, partner billing, anything feeding statutory reporting.

Operability

Who runs and monitors what gets built, and what happens to it at the next upgrade.

Readiness, adoption and implementation are different questions

Assistance that summarizes, explains or drafts is forgiving, because a person reads the output before anything happens. Automation that posts, routes or approves is not: it inherits every weakness in the underlying data and applies it consistently. The useful question is which specific decisions your data is good enough to support today — and where we have hands-on delivery experience with a specific product, we will say so directly in conversation and name the context.

Scope

What CAL can responsibly help assess

Stated as assessment work, because that is what the available evidence supports.

  • Custom code and extensions graded against SAP’s clean-core level model
  • Extension pattern selection: standard, on-stack ABAP Cloud, side-by-side SAP BTP
  • Integration landscape and governance, including where SAP Integration Suite fits
  • Data ownership, semantic consistency and trustworthiness before platform decisions
  • Readiness questions for SAP Business Data Cloud and SAP Business AI
  • Authorization and segregation-of-duties implications of automation

Where this connects

Want an honest readiness read?

We assess where your estate sits before recommending anything — including recommending that you wait.

info@cal-assoc.com

8003 Bulrush Canyon Trail, Katy, TX 77494 · the Greater Houston area