KBJ Builds SAP Practice Around Clean Core and a Unified Data Layer

KBJ, a Polish SAP partner, positions its practice around SAP’s Intelligent Enterprise stack, from S/4HANA and the Business Technology Platform to analytics and planning. The company reports more than 600 SAP projects over 17 years, a team holding over 90 international SAP certifications, and a training footprint it puts at roughly 30 percent of all SAP trainings in Poland. Its work operates as a Partner Center of Expertise, covering implementation, maintenance, and support alongside proprietary products that address Polish statutory reporting such as e-KSF invoicing and e-JPK. Two commitments run through the portfolio: keeping the ERP core standard, and consolidating scattered data into a single layer.

Keeping the ERP Core Clean While Extending It on BTP

KBJ frames its S/4HANA work around SAP’s Clean Core strategy, which separates the ERP core from an extension layer so that custom functionality lives outside standard application code. Under this model, new features are built as side-by-side extensions, integration runs through official SAP APIs, and processes follow a fit-to-standard design rather than bespoke code. The mechanism carries a direct operational payoff: fewer modifications shorten upgrade cycles and lower the testing and support burden that heavily customized systems accumulate.

The extension layer is SAP BTP, which KBJ treats as the connective tissue between S/4HANA, SuccessFactors, BW, Datasphere, and third-party systems. BTP hosts integrations, low-code and workflow automation, and AI services without touching the ERP core, so teams can add applications and automate approvals or data flows while the underlying system stays upgrade-ready. KBJ’s stated sequence moves from architecture analysis to defining BTP’s role, then to building integrations and connecting the data and analytics layers.

Clean Core depends on trustworthy master data, and KBJ pairs its core work with SAP Master Data Governance for centralized creation, consolidation, and distribution of records across customer, material, product, financial, and asset domains. MDG replaces error-prone manual maintenance across multiple systems with governed data entry points and quality rules, which matters when a fit-to-standard core and side-by-side extensions all draw on the same definitions.

Human capital sits in the same architecture: KBJ maintains and develops SAP HCM, integrates it with SuccessFactors and S/4HANA finance, and offers a proprietary self-service portal named HeaRt for HCM users. Integrating HR data with finance and analytics lets labor cost, headcount, and absence figures feed management reporting rather than staying siloed in payroll.

Consolidating the Data, Analytics, and Planning Estate

KBJ’s analytics practice centers on SAP Business Data Cloud, which combines SAP Datasphere and SAP Analytics Cloud to unite data management, reporting, planning, and AI in one environment. The problem it targets is fragmentation: warehouses, reporting tools, and planning systems built up independently over years, producing conflicting metric definitions and analysts who spend more time reconciling data than interpreting it. BDC addresses this by building a coherent business data layer with common KPI definitions, then layering reporting and planning on top, which shortens the path from raw data to a decision. KBJ presents BDC as an evolution rather than a rip-and-replace, with paths for organizations on BW, BW/4HANA, Datasphere, or SAC to extend what they already run.

Within that estate, SAP Analytics Cloud is the management analytics and planning layer, handling budgeting, controlling, dashboards, forecasting, and what-if simulation across SAP and non-SAP sources. KBJ addresses the common situation where budget versions circulate by email and forecasts take a week to assemble, and it supports customers still running SAP BusinessObjects by keeping BO as the operational reporting layer while SAC handles management analytics on shared data from BW, Datasphere, or S/4HANA. Its consultants have worked with SAP business intelligence in complex environments for over a decade, including data architectures for central public institutions with classified data requirements, and its SAC and BO solutions serve more than 1,000 users.

Planning extends into the supply chain through SAP Integrated Business Planning, which links financial, sales, operations, demand, and inventory planning on real-time SAP data. IBP supports sales and operations planning, statistical demand forecasting, inventory optimization, demand-driven replenishment, and response and supply planning, with what-if analysis to test how supply disruptions or delivery delays ripple into financial results. Coupled with SAC and BDC, IBP closes the loop between operational execution and the planning models that management reviews.

What This Means for SAPinsiders

• Clean Core reshapes how you scope customizations. SAP teams weighing an ECC to S/4HANA move now face an architectural choice at the design stage: retire custom code toward fit-to-standard, or migrate extensions onto BTP. Both paths change how upgrades and testing get budgeted.
• Master data governance becomes a prerequisite, not a cleanup task. Consolidating records under MDG before extending on BTP prevents divergent definitions from propagating into every side-by-side app. Buyers should sequence data governance ahead of analytics investment to protect KPI consistency.
• Unified data layers shift analyst effort toward interpretation. Standing up Business Data Cloud with shared KPI definitions can reduce reconciliation work that consumes planning teams today. Leaders evaluating BW or SAC modernization should test whether a single data layer frees staff for analysis over data preparation.