Skip to main content

Clean Core Model

· 3 min read
Ross Thompson
Managing Director
  • The Future of SAP S/4HANA Customization

Whitepaper: The Agentic Clean Core​

Decoupling Logic with Data-Xchange, MCP, and SAP BTP​

1. The Architect’s Dilemma: The Customization Tax​

Traditionally, SAP "differentiation" happened inside the core. Every custom price logic, every unique supplier validation, and every partner-specific workflow was written in ABAP.

  • The Result: Upgrade-heavy systems, technical debt, and an ERP that is "too fragile to touch."
  • The SAP 2026 Solution: SAP BTP and "Side-by-Side" extensions.

2. Moving Beyond "Side-by-Side" to "Agentic-Outside"​

While BTP keeps the core clean, you still have to build and maintain the "bridge" code (the ETL). Data-Xchange introduces a third way: Agentic-Outside.

Instead of writing custom code on BTP to handle a specific retailer's data format, you deploy an MCP Server. This server acts as a semantic translator that allows your AI agents to handle the logic outside of the SAP code base.

3. How Data-Xchange Enforces Clean Core Principles​

Clean Core PillarTraditional ApproachData-Xchange + MCP Approach
ExtensionsCustom BTP Apps / ABAP Cloud.Agentic Tools (Zero-code logic).
IntegrationsFragile point-to-point ETL.Standardized GS1 REST Endpoints.
Data QualityManual Cleansing in SAP.Network-level GS1 Validation.
ProcessesHard-coded if/then workflows.Autonomous AI Orchestration.

4. Technical Implementation: The Semantic Bridge​

By using the Model Context Protocol (MCP), Data-Xchange allows your SAP Joule agents (or third-party agents) to see your SAP data as "Tools."

  • Step 1: Expose standard SAP OData entities to BTP.
  • Step 2: Data-Xchange wraps these entities in GS1-standardized MCP tools.
  • Step 3: Your business logic (e.g., "If the supplier is from Region X, apply Tax Rule Y") is handled by the Agent in the Data-Xchange network, not by a line of ABAP code.

Developer Quick Start: The "Zero-ABAP" Partner Integration​

This guide shows how to onboard a new trading partner with complex rules without touching your SAP source code.

Step 1: Connect SAP to the Network​

Register your SAP BTP instance as a "Resource Host" in the Data-Xchange portal.

// Data-Xchange Config: Link to SAP BTP
{
  "host_type": "SAP_BTP_OData",
  "endpoint": "https://tenant.it-cpi001.cfapps.eu10.hana.ondemand.com",
  "auth": "OAuth2_Principal_Propagation"
}

Step 2: Define the "Agentic Logic" (Prompt-as-Code)​

Instead of a mapping tool, you provide the agent with a Business Context Policy.

"When a Purchase Order is received from Partner_A via the GS1 network, verify the price against our SAP Material Master tool. If the price variance is >5%, trigger a 'Price Exception' tool in Data-Xchange. Otherwise, post the PO to SAP via the 'Create_PO' tool."

Step 3: Execute the Autonomous Loop​

The Data-Xchange network monitors the incoming GS1 stream. When a transaction hits:

  1. AI Agent detects the intent (New PO).
  2. MCP Client calls the SAP Material Master tool (Live data fetch).
  3. Agent performs the logic (Price check).
  4. Agent executes the final action (Post to SAP).

The Result: Your SAP Core remains 100% standard. No custom Z-tables, no custom enhancement points, and no technical debt.