SAP S/4HANA Source Tables | ShaDey Inc. Data Documentation

1. Simplification Overview

S/4HANA introduces fundamental architectural changes that affect data extraction, transformation, and modelling. The following table summarises the major replacement patterns relevant to the ShaDey Inc. data model.

ECC Structure	S/4HANA Replacement	Impact	Affected PDM Entities
`KNA1` + `LFA1`	`BUT000` (Business Partner)	Customer and vendor masters unified. Roles (customer, vendor, contact) assigned to a single partner record.	dim_customer, dim_supplier
`MKPF` + `MSEG`	`MATDOC`	Material document header and items merged into a single journal table. MARD becomes an aggregate view.	fact_inventory_snapshot, fact_return
`BSEG` + `CE1xxxx`	`ACDOCA` (Universal Journal)	FI line items, CO-PA, ML, and CO postings merged into a single source of truth. Eliminates ~50 index/summary tables.	All financial derivations
`KONV`	`PRCD_ELEMENTS`	Document-level pricing conditions replaced. Master condition records (KONH/KONP) retained.	fact_sales (promotion linkage), dim_promotion
`KNKK`	`UKM_*` tables	New credit management with business partner integration, segment-based limits, and real-time exposure.	fact_order (credit check logic)
`LQUA` + `LAGP` (WM)	`/SCWM/*` (Embedded EWM)	Classic WM replaced by Embedded Extended Warehouse Management. Bin-level management redesigned.	fact_inventory_snapshot (warehouse detail)
Classic MRP (`MD01/MD02`)	MRP Live (`MD01N`)	HANA-optimised parallel MRP. Same output tables (PLAF, EBAN) but dramatically faster execution.	Upstream to all supply-side entities

2. Business Partner (replaces KNA1 / LFA1)

The most significant master data change in S/4HANA. The Business Partner concept unifies customers, vendors, contact persons, and organisational units into a single master record with role assignments.

Migration Impact

Customer master (KNA1/KNB1/KNVV) and vendor master (LFA1/LFB1/LFM1) data must be migrated to Business Partner (BUT000) and associated role tables. SAP provides the CVI (Customer-Vendor Integration) framework for synchronisation during migration. Post-migration, KNA1/LFA1 tables still exist as compatibility views but BUT000 is the source of truth.

Table	SAP Name	Description	Replaces	Key Fields	Business Explanation
`BUT000`	Business Partner General Data	Central business partner record: partner number, name, type (person/organisation), category, creation date, address data, search terms.	`KNA1` (customer), `LFA1` (vendor)	PK `PARTNER`	Single identity for all business partners. The PDM's dim_customer and dim_supplier would both source from BUT000 with role-specific filtering. Customer role: CVI maps KUNNR to PARTNER. Vendor role: CVI maps LIFNR to PARTNER.
`BUT0BK`	Business Partner Bank Details	Bank account data for business partners.	KNA1 bank fields, LFA1 bank fields	PK `PARTNER` + `BESSION`	Centralised bank data replacing separate customer/vendor bank tables.
`BP Role Tables`	Business Partner Roles	Role assignments: customer (FLCU00), vendor (FLVN00/FLVN01), contact person, etc. Multiple roles per partner.	Implicit in KNA1/LFA1 existence	PK `PARTNER` + `ROLE`	A single business partner can be both a customer and a vendor (e.g., a retailer that buys from and sells to ShaDey Inc.).

PDM Impact

For source-to-target mapping, dim_customer would use: BUT000.PARTNER (as customer_id), BUT000.NAME_ORG1 + NAME_ORG2 (as full_name), and join to CVI mapping tables to retrieve the customer role data. dim_supplier follows the same pattern with vendor role filters.

3. MATDOC (replaces MKPF + MSEG)

One of the most impactful structural changes. The material document header (MKPF) and items (MSEG) are replaced by a single denormalised table that serves as the journal of record for all goods movements.

Table	SAP Name	Description	Replaces	Key Fields	Business Explanation
`MATDOC`	Material Document Journal	Unified material document: combines header fields (document date, posting date, reference) with item fields (material, plant, storage location, batch, quantity, movement type, value) in a single row per item. Contains all goods movement types (GR, GI, transfer, return).	`MKPF` (header) + `MSEG` (items)	PK `MBLNR` + `MJAHR` + `ZEESSION`	The single source of truth for all inventory movements. Stock tables (MARD, MCHB) become aggregates derived from MATDOC. For the PDM, return goods receipts (movement types 651/653) would be extracted from MATDOC instead of MSEG. fact_inventory_snapshot's source field references to MARD remain valid since MARD is retained as an aggregate.

Stock Table Impact

MARD (storage location stock) is retained in S/4HANA but is now a real-time aggregate of MATDOC entries rather than being independently updated. The PDM's fact_inventory_snapshot mapping to MARD.LABST/RESBE/UMLME remains valid, but the underlying data is now derived from MATDOC. For historical stock reconstruction, MATDOC is the authoritative source.

4. Universal Journal ACDOCA (replaces BSEG / CO-PA)

The Universal Journal is S/4HANA's single source of financial truth, merging FI line items, CO postings, Material Ledger actuals, and CO-PA into one table. This eliminates approximately 50 index and summary tables from ECC.

Table	SAP Name	Description	Replaces	Key Fields	Business Explanation
`ACDOCA`	Universal Journal Entry Line Items	Unified financial journal: every financial posting creates one set of ACDOCA records containing G/L account, cost element, cost centre, profit centre, profitability segment, material, customer, vendor, and all CO-PA characteristics. Supports multi-currency and multi-valuation (leading, group, profit centre).	`BSEG`, `COEP`, `CE1xxxx`/`CE2xxxx`, `FAGLFLEXA`, `BSIS`/`BSAS`, `BSID`/`BSAD`, `BSIK`/`BSAK`	PK `RCLNT` + `RLDNR` + `RBUKRS` + `GJAHR` + `BESSION` + `DOCLN`	Eliminates the need for separate CO-PA extraction. Profitability analysis by product/channel/region can be performed directly on ACDOCA. Credit memo postings (from returns) and billing postings (from sales) all flow into ACDOCA. The PDM's financial derivations (revenue, COGS) would source from ACDOCA instead of BSEG.
`CKMLHD`	Material Ledger Header	Material Ledger is mandatory in S/4HANA. Provides actual costing, multi-currency valuation, and transfer pricing for materials.	Optional in ECC	PK `MATNR` + `BWKEY`	Mandatory actual costing. Enhances dim_product.unit_cost with actual vs. standard cost visibility. Referenced in Product Design (stage 3).

Eliminated Tables

The following ECC tables are eliminated or become compatibility views in S/4HANA: BSEG (line items), BSIS/BSAS (G/L open/cleared items), BSID/BSAD (customer open/cleared), BSIK/BSAK (vendor open/cleared), FAGLFLEXA (new G/L), CE1xxxx/CE2xxxx (CO-PA), COEP (CO line items), S001 and other S-tables (LIS). All are absorbed by ACDOCA.

5. PRCD_ELEMENTS (replaces KONV)

Document-level pricing conditions are stored in PRCD_ELEMENTS instead of KONV. Master condition records (KONH/KONP) remain structurally the same.

Table	SAP Name	Description	Replaces	Key Fields	Business Explanation
`PRCD_ELEMENTS`	Pricing Document Conditions	Unified pricing condition storage for all document types (sales orders, billing, purchasing). Replaces KONV with a more flexible structure supporting additional attributes and condition groups.	`KONV`	PK `KNUMV` + `KPOSN` + `STUNR` + `ZAESSION`	For the PDM, the fact_sales to dim_promotion linkage that uses KONV condition lookups would instead query PRCD_ELEMENTS. The condition type (KSCHL) and condition value (KBETR) fields are preserved.

6. Credit Management (replaces KNKK)

S/4HANA introduces a new credit management architecture integrated with Business Partner, supporting segment-based credit limits and real-time exposure calculation.

Table	SAP Name	Description	Replaces	Key Fields	Business Explanation
`UKM_*` tables	S/4 Credit Management	Suite of tables for S/4HANA credit management: credit segment master, credit limit, credit exposure, scoring rules, and credit case management. Integrated with Business Partner rather than customer number.	`KNKK`	Various per table	Enables segment-based credit limits (e.g., different limits by sales area), real-time exposure calculation from ACDOCA, and automated credit scoring. Affects order-to-cash credit checks in fact_order.

7. MRP Live & DDMRP

S/4HANA replaces classic MRP with a HANA-optimised engine and introduces Demand-Driven MRP (DDMRP) as a fundamentally new planning paradigm.

Capability	SAP Name	Description	Replaces	Impact
`MRP Live (MD01N)`	HANA-Optimised MRP	Parallel-processing MRP engine that leverages SAP HANA in-memory processing. Same input parameters and output (PLAF, EBAN) but runs 10-100x faster on large material bases.	Classic MRP (MD01/MD02)	Output tables (PLAF, EBAN, MDKP) are retained. No PDM structural impact, but enables more frequent MRP runs.
`DDMRP`	Demand-Driven MRP	Buffer-based planning methodology with strategic decoupling points. Dynamic buffer zones (red/yellow/green) replace fixed safety stocks and reorder points. Net flow equation replaces traditional net requirements calculation.	Traditional safety stock / reorder point MRP	Introduces new buffer profile and buffer level data structures. Fundamental shift from push-based to pull-based planning. Affects MARC MRP parameter interpretation.
`Predictive MRP`	ML-Based Planning	Machine learning recommendations for MRP parameters: optimal safety stock levels, lot sizes, and reorder points based on historical consumption patterns.	Manual MRP parameter maintenance	Automates parameter tuning that was previously manual in Continuous Improvement (stage 16).
`Embedded PP/DS`	Embedded Production Planning / Detailed Scheduling	Detailed scheduling capabilities embedded in S/4HANA core, replacing APO PP/DS. Finite capacity scheduling, sequence-dependent setup, and detailed operation scheduling.	SAP APO PP/DS	Replaces external APO for detailed production scheduling. Work centre and capacity tables (CRHD, KAKO) are retained.

8. Embedded EWM (replaces WM)

Classic Warehouse Management (WM) with LQUA/LAGP is replaced by Embedded Extended Warehouse Management, providing advanced bin-level management, wave processing, and labour management within S/4HANA core.

Table / Namespace	SAP Name	Description	Replaces	Business Explanation
`/SCWM/*`	Embedded EWM Tables	Comprehensive warehouse management: storage bins, warehouse tasks, handling units, wave management, labour management, yard management, and deconsolidation.	`LQUA`, `LAGP`, and other WM tables	Provides significantly more granular warehouse data than classic WM. The PDM's fact_inventory_snapshot continues to source from MARD for aggregate stock, but detailed bin-level data would come from /SCWM/ tables.

9. Retained Tables

Many core ECC tables are retained in S/4HANA with minimal or no structural changes. These are listed below grouped by functional area.

Material Master

Table	Status in S/4HANA	Notes
`MARA`	Retained	Core material data unchanged. Enhanced with CDS views for analytical access.
`MAKT`	Retained	Material descriptions unchanged.
`MARC`	Retained	Plant data unchanged. MRP views enhanced for MRP Live and DDMRP.
`MVKE`	Retained	Sales data unchanged.
`MARM`	Retained	Units of measure unchanged.
`MEAN`	Retained	EAN/UPC codes unchanged.
`MBEW`	Retained	Valuation data retained. Material Ledger (CKMLHD) now mandatory.
`MARD`	Retained (as aggregate)	Storage location stock retained but now an aggregate of MATDOC. No longer independently updated.
`MCHB`	Retained	Batch stock retained.

Sales & Distribution

Table	Status in S/4HANA	Notes
`VBAK / VBAP / VBEP`	Retained	Sales order tables unchanged. Fiori apps replace classic transactions.
`VBRK / VBRP`	Retained	Billing tables unchanged.
`LIKP / LIPS`	Retained	Delivery tables unchanged.
`VTTK / VTTP`	Retained (or replaced by TM)	Retained for basic shipments. SAP TM provides advanced alternative.
`NAST`	Retained	Output determination retained.

Procurement

Table	Status in S/4HANA	Notes
`EKKO / EKPO / EKET`	Retained	Purchase order tables unchanged.
`EBAN`	Retained	Purchase requisitions unchanged.
`EORD / EQUK`	Retained	Source list and quota unchanged.
`RBKP / RSEG`	Retained	Invoice verification unchanged.
`EINA / EINE`	Retained	Purchasing info records unchanged.

Production

Table	Status in S/4HANA	Notes
`AUFK / AFKO / AFPO / AFVC`	Retained	Production order tables unchanged. Fiori apps for shop floor.
`MAST / STKO / STPO`	Retained	BOM tables unchanged.
`PLKO / PLPO`	Retained	Routing tables unchanged. Enhanced with Fiori.
`CRHD / KAKO`	Retained	Work centre and capacity unchanged.
`MCH1 / MCHA`	Retained	Batch management unchanged.
`RESB`	Retained	Reservations unchanged.
`PLAF`	Retained	Planned orders unchanged (output of MRP Live).

Quality Management

Table	Status in S/4HANA	Notes
`QALS / QASR / QAVE`	Retained	QM tables unchanged. Enhanced Fiori inspection apps.
`CABN / AUSP`	Retained	Classification unchanged.
`VCH1 / VCH2`	Retained	Batch determination unchanged.
`IKPF / ISEG`	Retained	Physical inventory unchanged.

Pricing & Conditions (Master)

Table	Status in S/4HANA	Notes
`KONH / KONP`	Retained	Master condition records unchanged. Only document conditions (KONV) replaced.
`A-tables`	Retained	Condition access tables unchanged.

Engineering & PLM

Table	Status in S/4HANA	Notes
`AENR`	Retained	Engineering change management retained.
`VIQMEL`	Retained	Service notification retained for basic scenarios.

10. Cloud & BTP Extensions

S/4HANA extends core ERP capabilities through cloud-native services and SAP BTP (Business Technology Platform) solutions. These are referenced in the lifecycle stages but do not have traditional table structures.

Service	Description	Replaces / Extends	Lifecycle Stage(s)
SAP IBP for Demand	ML-driven demand sensing, statistical forecasting, and consensus demand planning in the cloud.	APO Demand Planning, /SAPAPO/SNPTSDATA	Stage 1 (Market Need), Stage 16 (Improvement)
SAP IBP for Response & Supply	Multi-echelon inventory optimisation, supply and S&OP planning.	APO SNP	Stage 4 (Supply Planning)
SAP Ariba / Business Network	Cloud-based sourcing, contract management, supplier collaboration, and catalog management.	Extends EKKO/EKPO procurement	Stage 5 (Sourcing)
SAP Central Procurement	Unified procurement hub across multiple backend systems.	Cross-system procurement	Stage 5 (Sourcing)
SAP Digital Manufacturing	Cloud MES for real-time shop floor integration, OEE analytics, and quality data capture.	External MES integration	Stage 6 (Manufacturing), Stage 7 (Quality)
SAP Transportation Management (TM)	Advanced freight management: freight orders, carrier selection, route optimisation, and freight cost settlement.	Classic shipment (VTTK/VTTP)	Stage 9 (Distribution)
SAP GTS (Global Trade Services)	Export control, customs management, trade preference, and sanctioned party screening.	EIKP/EIPO foreign trade	Stage 9 (Distribution)
SAP CAR (Customer Activity Repository)	Unified POS transaction data aggregation and omnichannel analytics.	POS data integration	Stage 10 (Retail), Stage 12 (Purchase)
SAP Commerce Cloud	E-commerce product catalog, order management, and digital storefront.	External e-commerce	Stage 10 (Retail)
SAP Marketing Cloud / Emarsys	Campaign management, customer segmentation, and personalised marketing execution.	WPM* promotion management	Stage 11 (Promotion)
Advanced ATP (aATP)	Rules-based availability with product allocation, backorder processing, and substitution.	Classic ATP (VBEP-based)	Stage 12 (Purchase)
SAP Order Management Foundation	Omnichannel order orchestration: sourcing, splitting, and routing across fulfilment nodes.	Classic SD order processing	Stage 12 (Purchase), Stage 14 (Returns)
SAP Service Cloud	Customer service, ticket management, return authorisation, and case management.	VIQMEL, CRMD_ORDERADM_H	Stage 13 (Consumption), Stage 14 (Returns)
SAP Analytics Cloud (SAC)	Cloud analytics, planning workbooks, and self-service BI. Integrates with ACDOCA via live connections.	BW InfoCubes, CO-PA reporting	Stage 1 (Market Need), Stage 15 (Feedback)
SAP MDG (Master Data Governance)	Enterprise-grade governance workflows for master data creation, change, and quality.	Manual master data maintenance	Stage 3 (Design), Stage 16 (Improvement)
SAP Logistics Business Network	Multi-partner shipment visibility and collaboration.	EDI-based partner communication	Stage 9 (Distribution)

11. CDS Views & Embedded Analytics

S/4HANA introduces CDS (Core Data Services) analytical views that provide real-time operational reporting directly on transactional tables without extraction to BW. These views replace LIS S-tables and many BW scenarios.

Impact on Data Warehousing

CDS views enable a "virtual data warehouse" pattern where analytical queries run directly against S/4HANA tables. For the ShaDey Inc. PDM, this means some data products (dp_net_sales_daily, dp_sales_daily, dp_store_analytics) could potentially be implemented as CDS views rather than physical ETL targets. However, for complex ML features and cross-source aggregations, physical extraction to a data warehouse remains the recommended pattern.

CDS View Category	Description	Replaces	Example Views
Product Master CDS	Analytical views over MARA/MARC/MVKE for product master reporting.	Custom BW extractors for material data	I_Product, I_ProductText, I_ProductPlant
Inventory CDS	Real-time stock views over MARD/MATDOC for inventory analytics.	S001 LIS tables, BW stock InfoCubes	I_MaterialStock, I_MaterialDocumentItem
Sales Analytics CDS	Sales order and billing analytics over VBAK/VBRK/PRCD_ELEMENTS.	S-tables, BW sales InfoCubes	I_SalesDocument, I_BillingDocumentItem
Finance CDS	Real-time financial reporting over ACDOCA.	Separate FI/CO/CO-PA reports	I_JournalEntry, I_ProfitCenterHierarchy

Assumptions & Notes

S/4HANA Version Assumption

This documentation assumes SAP S/4HANA 2023 or later (on-premise or cloud). Some capabilities (DDMRP, Embedded PP/DS, advanced aATP) may require specific license components or feature activations. Cloud-native services (IBP, Ariba, Service Cloud) require separate subscriptions.

Compatibility Views

Many "replaced" ECC tables (KNA1, LFA1, BSEG, KONV, MKPF, MSEG) continue to exist in S/4HANA as compatibility views. Custom code referencing these tables will continue to function, but they are not the source of truth. New developments should use the replacement tables (BUT000, ACDOCA, PRCD_ELEMENTS, MATDOC).

PDM Mapping Impact

The PDM source mappings in the data modeler primarily reference ECC table names (KNA1, LFA1, VBAK, etc.). In an S/4HANA environment, these references should be updated to their replacements. See SAP S/4HANA to PDM Mapping for the complete updated mapping.