SAP ECC Source Tables | ShaDey Inc. Data Documentation

1. Master Data Tables

Core master data objects that represent the foundational business entities in ShaDey Inc.'s retail/CPG operations. These tables define products, customers, vendors, plants/stores, and organisational structures.

Material / Article Master

The material master is the central repository for all product-related data in SAP. In a retail context, the material master serves as the article master, containing item descriptions, units of measure, pricing references, MRP parameters, and classification attributes.

Table	SAP Name	Description	Category	Confidence	Key Fields	Business Explanation
`MARA`	General Material Data	Client-level material attributes: material type, industry sector, base UoM, weight, volume, material group. Every material in SAP has exactly one MARA record.	Master Data	Explicit	PK `MATNR` (Material Number)	The single source of truth for a product's identity. Referenced in lifecycle stages 2 (draft creation), 3 (full creation), and 16 (revisions). Fields used: MATNR, MATKL (material group), BRAND_ID, MTART (material type), MEINS (base UoM).
`MAKT`	Material Descriptions	Language-dependent material short text. One record per material per language.	Master Data	Explicit	PK `MATNR` + `SPRAS`	Provides the human-readable product name. The PDM uses MAKTX WHERE SPRAS='EN' for the English description. Linked from Product Design stage (stage 3).
`MARC`	Plant Data for Material	Plant-level material data including MRP views, procurement type, planning parameters, safety stock, lot sizing, and reorder point settings.	Master Data	Explicit	PK `MATNR` + `WERKS`	Central to supply planning (stage 4) and continuous improvement (stage 16). MRP parameters (DISMM, DISPO, DISLS, MINBE) drive replenishment. Each plant/store maintains independent planning parameters.
`MVKE`	Sales Data for Material	Sales-organisation-level attributes for materials: delivering plant, item category group, material statistics group, and sales text assignments.	Master Data	Explicit	PK `MATNR` + `VKORG` + `VTWEG`	Controls how the product behaves in sales transactions. Referenced in both Product Design (stage 3) and Retail/E-Commerce (stage 10).
`MARM`	Units of Measure for Material	Alternative units of measure and their conversion factors relative to the base UoM. Handles pack-to-each, case-to-pallet conversions.	Master Data	Explicit	PK `MATNR` + `MEINH`	Essential for multi-unit operations in retail (selling by each, purchasing by case, warehousing by pallet). Referenced in Product Design (stage 3).
`MEAN`	EAN/UPC Codes	International Article Number (EAN) and Universal Product Code (UPC) bar codes assigned to a material, optionally per unit of measure.	Master Data	Explicit	PK `MATNR` + `MEINH` + `LFNUM`	Critical for POS scanning and supply chain identification. Each SKU/UoM combination can have a unique barcode (GTIN).
`MLAN`	Tax Classification	Tax classification indicators for material per country. Determines applicable tax rates for sales transactions.	Master Data	Explicit	PK `MATNR` + `AESSION`	Drives tax determination in billing. Particularly important for food vs. non-food tax rates in retail.
`MBEW`	Material Valuation	Valuation data per material and valuation area (plant). Holds standard price (STPRS), moving average price (VERPR), and total stock value.	Master Data Finance	Explicit	PK `MATNR` + `BWKEY`	The PDM maps dim_product.unit_cost from MBEW.STPRS (standard price). Central to product costing (stage 3) and margin calculations.
`T023`	Material Group Master	Material group descriptions. Defines the merchandise category hierarchy for classification and reporting.	Reference Data	Explicit	PK `MATKL`	The PDM derives dim_product.category via MARA.MATKL joined to T023.WGBEZ. Provides the category and department hierarchy.
`KLAH`	Class Header	Classification system class definitions. Defines characteristics-based classes for batch classification, material classification, etc.	Reference Data	Explicit	PK `CLINT` (Internal class number)	Used alongside KSML for material and batch classification in Product Design (stage 3) and Quality/Packaging (stage 7).
`KSML`	Class Assignments	Links objects (materials, batches, equipment) to classification classes.	Reference Data	Explicit	PK `CLINT` + `OBJEK`	Assigns materials to merchandise classes and batches to quality classes.
`DRAW`	Document Info Record	Document management system header. Links technical drawings, specifications, and certificates to materials.	Master Data	Explicit	PK `DOKNR` + `DOKAR` + `DOKVR`	Product specification documents attached during design (stage 3). Referenced alongside DRAT (document descriptions).
`DRAT`	Document Descriptions	Language-dependent text for document info records.	Master Data	Explicit	PK `DOKNR` + `DOKAR` + `DOKVR` + `LANGU`	Descriptions of product specifications and technical documents.
`EORD`	Source List	Approved sources of supply per material per plant. Defines which vendors can supply which materials and in what timeframes.	Procurement	Explicit	PK `MATNR` + `WERKS` + `ZEESSION`	Links products to suppliers. The PDM uses EORD to derive dim_product.supplier_sk. Referenced in Sourcing (stage 5).
`EINA`	Purchasing Info Record (General)	General data for a material-vendor combination. Contains vendor sub-range, order unit, and standard delivery time.	Procurement	Explicit	PK `INFNR`	Carries the vendor's lead time (APLFZ), mapped to dim_supplier.lead_time_days. Referenced in Sourcing (stage 5).
`EINE`	Purchasing Info Record (Org Level)	Purchasing-organisation-level info record data. Holds net price, pricing date, and planned delivery time per purchasing org.	Procurement	Explicit	PK `INFNR` + `EKORG` + `ESOKZ` + `WERKS`	Purchasing-org-specific pricing and conditions for vendor-material combinations.

Customer Master

SAP ECC maintains customer data across three levels: general (KNA1), company code (KNB1), and sales area (KNVV). The customer master is central to the order-to-cash process and drives credit management, partner determination, and pricing.

S/4HANA Simplification

In S/4HANA, the separate customer master (KNA1) and vendor master (LFA1) are unified under the Business Partner concept (BUT000). Customer and vendor roles are assigned to business partners. See S/4HANA Business Partner for details.

Table	SAP Name	Description	Category	Confidence	Key Fields	Business Explanation
`KNA1`	Customer Master (General)	Client-level customer data: name, address, search terms, industry, account group (KTOKD), creation date (ERDAT). One record per customer across all company codes.	Master Data	Explicit	PK `KUNNR`	Primary customer identity. The PDM maps: customer_id from KUNNR, full_name from NAME1+NAME2, customer_type from KTOKD, registration_date from ERDAT. Central to Customer Purchase (stage 12).
`KNB1`	Customer Master (Company Code)	Company-code-level data: reconciliation account, payment terms, dunning procedure, cash management group.	Master Data	Explicit	PK `KUNNR` + `BUKRS`	Financial view of the customer. Drives payment and dunning processes.
`KNVV`	Customer Sales Area Data	Sales-area-level attributes: sales district, customer group, pricing procedure, delivering plant, shipping conditions, incoterms.	Master Data	Explicit	PK `KUNNR` + `VKORG` + `VTWEG` + `SPART`	Controls sales transaction behaviour: pricing, shipping, and delivery processing.
`KNVP`	Customer Partner Functions	Partner function assignments: sold-to, ship-to, bill-to, payer partners for each customer in a sales area.	Master Data	Explicit	PK `KUNNR` + `VKORG` + `VTWEG` + `SPART` + `PARVW`	Determines who receives the goods, the invoice, and who pays. Essential for B2B retail operations.
`KNKK`	Customer Credit Management	Credit control area data: credit limit, credit exposure, risk category, last credit review date.	Master Data Finance	Explicit	PK `KUNNR` + `KKBER`	Governs credit checks during order creation (stage 12). Blocked orders are held until credit is approved.
`KNVH`	Customer Hierarchy	Customer hierarchy assignments for pricing and rebate determination. Maps customers to hierarchy nodes for group pricing.	Master Data	Explicit	PK `HESSION` + `KUNNR` + `VKORG` + `VTWEG` + `SPART` + `DATAB`	Enables hierarchical pricing for retail chains and buying groups. Referenced in Promotion (stage 11).

Vendor Master

Vendor (supplier) master data in SAP ECC spans general data, company code data, and purchasing organisation data. The vendor master is central to the procure-to-pay cycle.

S/4HANA Simplification

In S/4HANA, LFA1 is replaced by BUT000 (Business Partner) with a vendor role. The separate vendor master concept is eliminated in favour of unified business partners. See S/4HANA Business Partner.

Table	SAP Name	Description	Category	Confidence	Key Fields	Business Explanation
`LFA1`	Vendor Master (General)	Client-level vendor data: name, address, country, account group (KTOKK), industry sector, one-time vendor indicator.	Master Data	Explicit	PK `LIFNR`	The PDM maps: supplier_id from LIFNR, supplier_name from NAME1+NAME2, supplier_type from KTOKK, country_code from LAND1. Central to Sourcing (stage 5).
`LFB1`	Vendor Master (Company Code)	Company-code-level vendor data: reconciliation account, payment terms, payment methods, withholding tax codes.	Master Data	Explicit	PK `LIFNR` + `BUKRS`	Financial view of the vendor. Controls payment processing and accounting.
`LFM1`	Vendor Master (Purchasing Org)	Purchasing-organisation-level vendor data: order currency, incoterms, GR-based IV flag, purchasing group.	Master Data	Explicit	PK `LIFNR` + `EKORG`	Purchasing-specific vendor attributes used during PO creation.

Plant / Store Master

In SAP, retail stores and distribution centres are modelled as plants (WERKS). The plant master contains location, address, and organisational assignment data.

Table	SAP Name	Description	Category	Confidence	Key Fields	Business Explanation
`T001W`	Plants / Branches	Plant master: plant name (NAME1), city (ORT01), region (REGIO), country (LAND1), factory calendar (FABKL), valuation area, purchasing organisation assignment.	Master Data	Inferred	PK `WERKS`	The PDM maps dim_store fields: store_id from WERKS, store_name from NAME1, region from REGIO+T005S, city from ORT01, country_code from LAND1, store_type from FABKL. Inferred from PDM source mappings in data-modeler.html.
`T005S`	Region Texts	Language-dependent region descriptions per country. Provides human-readable region names.	Reference Data	Inferred	PK `LAND1` + `BLAND`	Joined to T001W.REGIO to provide region text for dim_store.region.

Work Center & Capacity

Table	SAP Name	Description	Category	Confidence	Key Fields	Business Explanation
`CRHD`	Work Center Header	Work center master data: category, plant, responsible cost center, standard value keys. Defines production resources.	Master Data	Explicit	PK `OBJID`	Work centres represent machines, production lines, or labour groups. Referenced in Supply Planning (stage 4) and Manufacturing (stage 6).
`KAKO`	Capacity Header	Capacity definition for work centres: available capacity, operating time, number of individual capacities, capacity category.	Master Data	Explicit	PK `OBJID`	Defines how much a work centre can produce. Referenced in Supply Planning (stage 4) and Manufacturing (stage 6).
`T399D`	MRP Controller Master	MRP controller definitions per plant. An MRP controller is responsible for planning a group of materials.	Reference Data	Explicit	PK `WERKS` + `DESSION`	Organisational assignment for MRP planning responsibilities. Referenced in Supply Planning (stage 4).

2. Sales & Billing (SD)

Sales and Distribution tables covering the order-to-cash cycle: sales orders, schedule lines, billing documents, and output/message determination. These tables are central to the Customer Purchase (stage 12) and Returns (stage 14) lifecycle stages.

Table	SAP Name	Description	Category	Confidence	Key Fields	Business Explanation
`VBAK`	Sales Document Header	Header data for all SD documents: sales orders (OR), returns (RE), debit/credit memo requests. Contains order date (AUDAT), customer (KUNNR), net value (NETWR), sales org, distribution channel.	Transactional	Explicit	PK `VBELN`	The PDM maps fact_order: order_date_sk from AUDAT, channel from AUGRU, total_amount from NETWR. Return orders use document type RE. Central to stages 12 and 14.
`VBAP`	Sales Document Item	Item-level data: material (MATNR), quantity, net value, plant, item category, and rejection reason code.	Transactional	Explicit	PK `VBELN` + `POSNR`	Line items for orders and returns. The PDM uses MATNR for product lookups and maps return items.
`VBEP`	Sales Document Schedule Lines	Schedule line data: confirmed quantity, delivery date (EDATU), ATP confirmed date, schedule line category.	Transactional	Explicit	PK `VBELN` + `POSNR` + `EESSION`	ATP (Available-to-Promise) results. The PDM maps dp_order_fulfillment.promise_date from EDATU. Central to Customer Purchase (stage 12).
`VBKD`	Sales Document Business Data	Business data at header/item level: payment terms, billing plan, incoterms, pricing date, customer group.	Transactional	Explicit	PK `VBELN` + `POSNR`	Additional business context for sales documents. Referenced in Customer Purchase (stage 12).
`VBUK`	Sales Document Status	Overall status of sales documents: overall status (GBSTK), delivery status, billing status, credit status.	Transactional	Inferred	PK `VBELN`	The PDM maps fact_order.status from VBUK.GBSTK (A=Pending, B=Partial, C=Complete). Inferred from PDM source mapping.
`VBRK`	Billing Document Header	Billing header: billing type (F2=invoice, G2=credit memo), billing date (FKDAT), payer, net value, currency (WAERK).	Transactional	Explicit	PK `VBELN`	The PDM maps fact_sales from billing data: order_date_sk from FKDAT, currency_code from WAERK. Credit memos (G2) drive fact_return.refund_amount from NETWR.
`VBRP`	Billing Document Item	Billing items: material (MATNR), plant (WERKS), billed quantity (FKIMG), net price (NETPR), net value (NETWR).	Transactional	Explicit	PK `VBELN` + `POSNR`	The PDM maps fact_sales: quantity from FKIMG, unit_price from NETPR, line_total from NETWR, product_sk via MATNR, store_sk via WERKS.
`KONV`	Pricing Conditions (Document)	Pricing conditions applied to a specific sales or billing document: condition type, rate, value, and calculation schema.	Transactional	Explicit	PK `KNUMV` + `KPOSN` + `STUNR` + `ZAESSION`	Document-level pricing details. The PDM uses KONV to link fact_sales to dim_promotion via condition lookups. Replaced by PRCD_ELEMENTS in S/4HANA.
`NAST`	Output/Message Status	Output determination results: which messages (order confirmation, invoice, delivery note) have been generated and their processing status.	Transactional	Explicit	PK `KAPESSION` + `OBJKY` + `KSCHL` + `SPESSION` + `PESSION` + `NAESSION`	Tracks output documents: order confirmations, invoices, shipping notifications. Referenced in Customer Purchase (stage 12) and Distribution (stage 9).

3. Procurement (MM-PUR)

Purchase requisitions, purchase orders, scheduling agreements, contracts, and invoice verification tables. Central to the Sourcing lifecycle stage (stage 5).

Table	SAP Name	Description	Category	Confidence	Key Fields	Business Explanation
`EBAN`	Purchase Requisition	Purchase requisition items: material, quantity, delivery date, requisitioner, account assignment, source. Can be MRP-generated or manually created.	Transactional	Explicit	PK `BANFN` + `BNFPO`	Entry point for procurement. MRP-generated requisitions (stage 4) flow into purchase orders (stage 5).
`EKKO`	Purchasing Document Header	Header data for POs, contracts (MK), scheduling agreements (LP), and stock transport orders (UB). Contains vendor, purchasing org, document type, and overall status.	Transactional	Explicit	PK `EBELN`	Central procurement document. The PDM references EKPO for cost variance calculations in dp_supplier_scorecard. Referenced in Sourcing (stage 5) and Warehouse (stage 8, for STOs).
`EKPO`	Purchasing Document Item	Item-level PO data: material, quantity, net price, plant, storage location, account assignment category, item category.	Transactional	Explicit	PK `EBELN` + `EBELP`	Line items of purchase orders. Used for cost variance analysis in dp_supplier_scorecard.
`EKET`	Delivery Schedule Lines	Delivery schedule lines for PO items: scheduled delivery date, scheduled quantity, and confirmed quantity.	Transactional	Explicit	PK `EBELN` + `EBELP` + `EESSION`	Tracks expected delivery dates from suppliers. Enables on-time delivery measurement.
`EQUK`	Quota Arrangement Header	Quota arrangement: distributes procurement quantities across multiple approved vendors for a material/plant combination.	Procurement	Explicit	PK `MATNR` + `WERKS`	Multi-vendor sourcing strategy. Referenced in Sourcing (stage 5).
`EQUP`	Quota Arrangement Items	Individual quota items: vendor, quota percentage, maximum quantity, validity period.	Procurement	Explicit	PK `MATNR` + `WERKS` + `QUESSION`	Defines the split ratio between vendors for a material.
`RBKP`	Invoice Document Header	Incoming invoice header: invoice date, gross amount, vendor, payment terms, GR/IR reference.	Transactional	Explicit	PK `BESSION`	Invoice verification (3-way match). Referenced in Sourcing (stage 5).
`RSEG`	Invoice Document Items	Invoice line items: PO reference, material, invoiced quantity, amount.	Transactional	Explicit	PK `BESSION` + `BUZEI`	Line-level invoice data for three-way matching against PO and goods receipt.
`A0xx`	Pricing Condition Tables	Condition access tables (e.g., A004 for material/vendor pricing). Generated by condition table maintenance. Each table represents a unique key combination.	Reference Data	Explicit	Varies by table	Procurement pricing conditions. Each A-table maps a specific key combination to a condition record number (KNUMH). Referenced in Sourcing (stage 5).

4. Production Planning (PP)

Production orders, BOMs, routings, and cost collection tables. Central to the Manufacturing lifecycle stage (stage 6).

Table	SAP Name	Description	Category	Confidence	Key Fields	Business Explanation
`AUFK`	Order Master Data	Central order header: order type, order status, settlement rule, controlling area. Applies to production orders, internal orders, maintenance orders.	Production	Explicit	PK `AUFNR`	The master record for production orders. Referenced in Manufacturing (stage 6).
`AFKO`	Production Order Header	Production-order-specific header: planned quantities, actual quantities, BOM reference, routing reference, finish date.	Production	Explicit	PK `AUFNR`	Controls production execution: what to make, how much, and by when.
`AFPO`	Production Order Items	Items (goods produced): material produced, order quantity, goods receipt quantity, storage location.	Production	Explicit	PK `AUFNR` + `POSNR`	Output material of a production order.
`AFVC`	Order Operations	Individual operations/activities within a production order: work centre, setup time, machine time, labour time, confirmed quantity.	Production	Explicit	PK `AUFPL` + `APLZL`	Shop floor execution steps. Activity confirmations update these records.
`MAST`	BOM Link to Material	Links a material to its BOM (Bill of Materials) via BOM number and alternative.	Master Data	Explicit	PK `MATNR` + `WERKS` + `STLAN` + `STLAL`	Entry point for BOM explosion. Referenced in Manufacturing (stage 6) and Continuous Improvement (stage 16).
`STKO`	BOM Header	BOM header: base quantity, BOM status, validity dates, BOM usage (production, engineering, costing).	Master Data	Explicit	PK `STLNR` + `STLAL`	Controls BOM versioning and validity. Referenced in Manufacturing (stage 6) and Continuous Improvement (stage 16).
`STPO`	BOM Items	BOM components: component material, quantity, unit, item category (stock, non-stock, assembly).	Master Data	Explicit	PK `STLNR` + `STLKN`	Defines what goes into a product. Drives component reservation and backflushing.
`PLKO`	Routing Header	Task list (routing) header: routing group, group counter, status, usage, and validity.	Master Data	Explicit	PK `PLNTY` + `PLNNR` + `PLNAL`	Defines the sequence of operations to produce a product. Referenced in Manufacturing (stage 6) and Continuous Improvement (stage 16).
`PLPO`	Routing Operations	Operation detail: work centre, control key, standard values (setup, machine, labour), operation text.	Master Data	Explicit	PK `PLNTY` + `PLNNR` + `PLNKN`	Individual manufacturing steps. Defines time and resource requirements per operation.
`RESB`	Reservation Items	Material reservations for production orders: component, required quantity, movement type, withdrawal date, batch.	Production	Explicit	PK `RSNUM` + `RSPOS`	Reserves raw materials for production. Referenced in Manufacturing (stage 6) and Warehouse (stage 8).
`COBK`	CO Document Header	Controlling document header: document number, posting date, transaction type. Records cost postings against orders.	Finance	Explicit	PK `KOKRS` + `BESSION`	Production cost collection. Referenced in Manufacturing (stage 6).
`COEP`	CO Line Items	Controlling line items: cost element, amount, quantity, sender/receiver objects, value type.	Finance	Explicit	PK `KOKRS` + `BESSION` + `BUZEI`	Detailed cost postings for production order settlement and variance analysis.

5. MRP & Demand Planning

Materials Requirements Planning and demand forecasting tables. Central to Market Need (stage 1), Supply Planning (stage 4), and Continuous Improvement (stage 16).

Table	SAP Name	Description	Category	Confidence	Key Fields	Business Explanation
`PBIM`	Independent Requirements (Planned)	Planned independent requirements header: material, plant, requirements type, version. Represents forecasted demand before consumption by sales orders.	Planning	Explicit	PK `BESSION`	Demand planning output. Referenced in Market Need (stage 1) and Continuous Improvement (stage 16).
`PBED`	Independent Requirements Data	Quantity and date breakdowns for planned independent requirements: period, planned quantity, consumed quantity.	Planning	Explicit	PK `BESSION` + `PESSION`	Period-level demand quantities. The difference between planned and consumed drives MRP net requirements.
`PLAF`	Planned Orders	MRP-generated planned orders: material, plant, order type (procurement or in-house), planned quantities, planned dates, firming status.	Planning	Explicit	PK `PLNUM`	MRP output. Planned orders are converted to production orders (in-house) or purchase requisitions (external). Referenced in stages 4 and 6.
`T459A`	Forecast Parameters	Forecast profile parameters: forecast model, smoothing factors, tracking signal limits, historical periods.	Planning	Explicit	PK `PRESSION`	Controls statistical forecast models used in demand planning. Referenced in Market Need (stage 1).
`PLSC`	Planning Scenario	Long-term planning scenarios: simulation versions for capacity and supply planning.	Planning	Explicit	PK `PLSCN`	Enables what-if analysis for demand and supply scenarios. Referenced in Market Need (stage 1).
`MDKP`	MRP Document Header	Header for MRP results: material, plant, MRP type, planning date, exception messages summary.	Planning	Explicit	PK `DTNUM`	MRP run results. Exception messages guide planner actions. Referenced in Supply Planning (stage 4).
`MDTB`	MRP Table Structure	MRP element data: individual supply/demand elements with dates and quantities (the "MRP list").	Planning	Explicit	Various	Detailed supply/demand pegging. Shows the complete supply-demand picture per material/plant.
`MDVM`	Planning File Entries	Flags materials that need re-planning. Set by relevant changes (stock, requirements, master data) to trigger the next MRP run.	Planning	Explicit	PK `MATNR` + `WERKS`	MRP change indicator. Only flagged materials are included in net-change MRP runs.
`KBED`	Capacity Requirements Header	Capacity requirements generated by planned/production orders: work centre, capacity category, requirement dates.	Planning	Explicit	PK `BEDID`	Evaluates whether sufficient production capacity exists. Referenced in Supply Planning (stage 4).
`KBEZ`	Capacity Requirements Items	Detailed capacity requirement splits: time slots, required capacity, available capacity overlap.	Planning	Explicit	PK `BEDID` + `BDESSION`	Granular capacity loading data for scheduling. Referenced in Supply Planning (stage 4).
`/SAPAPO/SNPTSDATA`	APO SNP Time-Series Key Figures	SAP APO Supply Network Planning time-series data: demand, supply, stock, and forecast key figures across planning buckets.	Planning	Explicit	Composite	Advanced planning data from SAP APO. Referenced in Market Need (stage 1). Replaced by SAP IBP in S/4HANA.

6. Inventory Management (MM-IM)

Stock management, goods movements, physical inventory, and special stock tables. Central to the Warehouse lifecycle stage (stage 8).

S/4HANA Simplification: MKPF/MSEG to MATDOC

In S/4HANA, the material document header (MKPF) and items (MSEG) are replaced by a single table MATDOC. This is one of the most significant structural changes. MARD is retained but serves as an aggregate; MATDOC is the single source of truth for all inventory movements. See MATDOC details.

Table	SAP Name	Description	Category	Confidence	Key Fields	Business Explanation
`MARD`	Storage Location Stock	Current stock by material, plant, and storage location. Holds unrestricted (LABST), quality inspection (INSME), blocked (SPEME), reserved (RESBE), and in-transit (UMLME) quantities.	Inventory	Explicit	PK `MATNR` + `WERKS` + `LGORT`	The PDM maps fact_inventory_snapshot: quantity_on_hand from LABST, quantity_reserved from RESBE, quantity_in_transit from UMLME. Lookups via MATNR and WERKS to product and store dimensions.
`MCHB`	Batch Stock	Stock at batch level per material, plant, and storage location. Enables batch-specific inventory tracking.	Inventory	Explicit	PK `MATNR` + `WERKS` + `LGORT` + `CHARG`	Batch-level stock visibility. Essential for shelf-life management and recall traceability in CPG.
`MKPF`	Material Document Header	Header for goods movements: document date, posting date, movement type, reference document. Every inventory change creates a material document.	Transactional	Explicit	PK `MBLNR` + `MJAHR`	Audit trail for all inventory movements. Replaced by MATDOC in S/4HANA. Referenced in Warehouse (stage 8) and Returns (stage 14, movement types 651/653).
`MSEG`	Material Document Items	Item-level goods movement data: material, plant, storage location, batch, quantity, movement type, value.	Transactional	Explicit	PK `MBLNR` + `MJAHR` + `ZEESSION`	Detailed inventory transaction records. Movement types determine the nature: 101=GR, 261=GI to production, 601=GI for delivery, 651=return GR.
`IKPF`	Physical Inventory Document Header	Physical inventory count header: count date, plant, storage location, inventory type (annual, cycle, continuous).	Inventory	Explicit	PK `IBLNR` + `GJAHR`	Physical inventory reconciliation. Referenced in Warehouse (stage 8).
`ISEG`	Physical Inventory Document Items	Count results: material, counted quantity, book quantity, difference, batch, serial number.	Inventory	Explicit	PK `IBLNR` + `GJAHR` + `ZEESSION`	Item-level count results for physical inventory. Differences posted as inventory adjustments.
`RKPF`	Reservation Header	Material reservation header: movement type, reservation date, requirement date, account assignment.	Inventory	Explicit	PK `RSNUM`	Reserves stock for planned consumption (production, project, cost centre). Referenced in Warehouse (stage 8).
`MKOL`	Consignment Stock Liabilities	Consignment stock held at customer or from vendor: material, plant, customer/vendor, consignment quantity and value.	Inventory	Explicit	PK `MATNR` + `WERKS` + `LIFNR`	Tracks vendor-managed or customer consignment inventory. Referenced in Warehouse (stage 8).

7. Warehouse Management (WM)

Classic Warehouse Management (WM) tables for bin-level stock tracking. In S/4HANA, legacy WM is replaced by Embedded EWM.

Table	SAP Name	Description	Category	Confidence	Key Fields	Business Explanation
`LQUA`	Warehouse Quants	Individual stock quantities at bin level (quants): material, batch, stock type, quantity, storage bin, and GR date.	Inventory	Explicit	PK `LGNUM` + `LQNUM`	Bin-level stock visibility. Replaced by /SCWM/ tables (Embedded EWM) in S/4HANA. Referenced in Warehouse (stage 8).
`LAGP`	Storage Bins	Storage bin master: bin type, section, bin coordinates, maximum weight, capacity, and status.	Inventory	Explicit	PK `LGNUM` + `LGTYP` + `LGPLA`	Warehouse physical layout. Defines the storage structure for putaway and picking. Replaced by Embedded EWM in S/4HANA.

8. Logistics & Shipping (LE-SHP)

Delivery processing, shipment planning, handling units, and route determination tables. Central to the Distribution lifecycle stage (stage 9).

Table	SAP Name	Description	Category	Confidence	Key Fields	Business Explanation
`LIKP`	Delivery Header	Delivery header for outbound (LF) and return (LR) deliveries: ship-to party, planned GI date (WADAT_IST), actual GI date, delivery date (LFDAT), route, total weight/volume.	Logistics	Explicit	PK `VBELN`	The PDM maps fact_shipment: ship_date_sk from WADAT_IST, delivery_date from LFDAT, store_sk via WERKS, carrier via ROUTE. Return deliveries use type LR. Referenced in stages 9 and 14.
`LIPS`	Delivery Items	Delivery line items: material, delivered quantity, batch, plant, storage location, picking status, and weight.	Logistics	Explicit	PK `VBELN` + `POSNR`	Line items of deliveries and return deliveries. Drives goods issue posting.
`VTTK`	Shipment Header	Shipment document: transportation planning point, carrier, shipment type, dates, route.	Logistics	Explicit	PK `TKNUM`	Groups deliveries into shipments for carrier assignment and transport planning. Referenced in Distribution (stage 9).
`VTTP`	Shipment Items	Links deliveries to shipments: delivery number, leg indicator, loading point.	Logistics	Explicit	PK `TKNUM` + `TPNUM`	Maps which deliveries ride on which shipments. Referenced in Distribution (stage 9).
`VEKP`	Handling Unit Header	Handling unit (pallet, carton, container) header: HU number, packaging material, gross weight, volume.	Logistics	Explicit	PK `VENUM`	Physical packaging structure. Referenced in Distribution (stage 9).
`VEPO`	Handling Unit Items	Items packed into handling units: material, quantity, batch, and nesting (HU within HU).	Logistics	Explicit	PK `VENUM` + `VEPOS`	Packing details for shipments.
`TVRO`	Route Determination	Route master: route code, transportation zone, transit time, distance. Used for automatic route determination during delivery creation.	Reference Data	Explicit	PK `ROUTE`	Maps delivery to carrier route. Referenced in Distribution (stage 9).

9. Quality Management (QM)

Inspection lots, results recording, usage decisions, batch classification, and batch determination tables. Central to the Quality & Packaging lifecycle stage (stage 7).

Table	SAP Name	Description	Category	Confidence	Key Fields	Business Explanation
`QALS`	Inspection Lot Header	Inspection lot master: lot number, material, plant, inspection type, sample size, lot status, start date.	Quality	Explicit	PK `PRUESSION`	Created automatically by goods movements or manually. The PDM references QM for dim_supplier.is_certified. Referenced in Quality (stage 7).
`QASR`	Inspection Results	Inspection results by characteristic: measured value, valuation (accepted/rejected), sample number.	Quality	Explicit	PK `PRUESSION` + `VESSION`	Detailed quality test results. Referenced in Quality (stage 7).
`QAVE`	Usage Decision	Usage decision for inspection lot: decision code (accepted, rejected, restricted), follow-up action, decision date.	Quality	Explicit	PK `PRUESSION`	Final quality disposition. Determines if goods can be released to unrestricted stock.
`QAMR` / `QMEL`	Quality Notification	Quality notifications for defects, complaints, and non-conformances: notification type, problem description, root cause, corrective action.	Quality	Explicit	PK `QMNUM`	Tracks quality issues. Referenced in Quality (stage 7) and Returns (stage 14) for complaint tracking.
`QPCD`	Inspection Plan Characteristics	Characteristics assigned to inspection plans: inspection characteristic, sampling procedure, tolerances.	Quality	Explicit	Composite key	Defines what is inspected and how. Referenced in Quality (stage 7).
`MCH1`	Batch Master	Batch master data: batch number, material, creation date, shelf life expiration date (SLED), production date.	Master Data	Explicit	PK `MATNR` + `CHARG`	Central batch identity. Essential for shelf life management and recall traceability in CPG. Referenced in Quality (stage 7) and Manufacturing (stage 6).
`MCHA`	Batch Plant Assignment	Plant-level batch data: links batches to specific plants and their classification values.	Master Data	Explicit	PK `MATNR` + `CHARG` + `WERKS`	Plant-specific batch attributes. Referenced in Quality (stage 7) and Manufacturing (stage 6).
`CABN`	Classification Characteristics	Characteristic definitions for classification: characteristic name, data type, allowed values, units.	Reference Data	Explicit	PK `ATINN`	Defines batch and material characteristics (e.g., colour, size, potency). Referenced in Quality (stage 7).
`AUSP`	Classification Values	Actual characteristic values assigned to objects (batches, materials): object key, characteristic, value.	Reference Data	Explicit	PK `OBJEK` + `ATINN` + `ATZHL`	Stores the actual values of batch characteristics. Used in batch determination strategies.
`VCH1`	Batch Search Strategy Header	Batch determination strategy: defines the search sequence and selection criteria for automatic batch assignment during goods movements and deliveries.	Reference Data	Explicit	PK `VEESSION`	Controls FEFO (First Expired, First Out) and other batch selection strategies. Referenced in Quality (stage 7) and Distribution (stage 9).
`VCH2`	Batch Search Strategy Items	Individual selection criteria within a batch determination strategy: characteristic, sort order, selection type.	Reference Data	Explicit	PK `VEESSION` + `VCESSION`	Detailed batch search rules for FEFO/FIFO strategies.

10. Pricing & Conditions

Condition master records and condition access tables used for pricing, discounts, surcharges, and promotional pricing.

S/4HANA Simplification: KONV to PRCD_ELEMENTS

Document-level pricing conditions stored in KONV are replaced by PRCD_ELEMENTS in S/4HANA. Master condition records (KONH/KONP) remain structurally similar. See S/4HANA Pricing.

Table	SAP Name	Description	Category	Confidence	Key Fields	Business Explanation
`KONH`	Condition Record Header	Master condition records: condition number (KNUMH), condition type reference, creation date, validity period.	Reference Data	Explicit	PK `KNUMH`	The PDM maps dim_promotion: promotion_id from KNUMH+KOPOS, promotion_name from VTEXT. Referenced in Promotion (stage 11).
`KONP`	Condition Record Items	Condition details: condition type (KSCHL), rate (KBETR), unit, validity start (DATAB), validity end (DATBI), calculation type, scales.	Reference Data	Explicit	PK `KNUMH` + `KOPOS`	The PDM maps dim_promotion: type from KSCHL, discount_pct from KBETR/10, start/end_date from DATAB/DATBI. Also maps dim_product.unit_price from KBETR WHERE KSCHL=PR00.
`A-tables`	Condition Access Tables	Generated condition tables (A004, A904, etc.) that map key combinations to condition record numbers. Each table represents a unique access sequence step.	Reference Data	Explicit	Varies per table	Pricing access sequences determine which condition records apply. A904 is referenced for promotional pricing. Referenced in Retail (stage 10) and Promotion (stage 11).

11. Finance & Controlling (FI/CO)

Accounting documents, profitability analysis, and controlling structures.

S/4HANA Simplification: BKPF/BSEG to ACDOCA

In S/4HANA, the accounting document line items (BSEG) and secondary index tables are replaced by the Universal Journal (ACDOCA). ACDOCA merges FI, CO, ML, and CO-PA into a single source of truth. BKPF (header) is retained. See ACDOCA details.

Table	SAP Name	Description	Category	Confidence	Key Fields	Business Explanation
`BKPF`	Accounting Document Header	FI document header: company code, fiscal year, document number, document type, posting date, reference.	Finance	Explicit	PK `BUKRS` + `BESSION` + `GJAHR`	Every financial posting creates an accounting document. Referenced in Customer Purchase (stage 12).
`BSEG`	Accounting Document Line Items	FI line items: G/L account, amount, cost centre, profit centre, customer/vendor, tax code. The detailed financial posting data.	Finance	Explicit	PK `BUKRS` + `BESSION` + `GJAHR` + `BUZEI`	Detailed financial line items. Replaced by ACDOCA in S/4HANA. Referenced in Customer Purchase (stage 12).
`CE1xxxx`	CO-PA Actual Line Items	Profitability Analysis actual data: operating concern-specific tables with profitability segments, revenue, COGS, and margin data.	Analytics	Explicit	Operating concern key + record	Product/channel/region profitability. Absorbed into ACDOCA in S/4HANA. Referenced in Feedback (stage 15).
`CE2xxxx`	CO-PA Plan Line Items	Profitability Analysis plan data: planned revenue, planned costs, and margins by profitability segment.	Analytics	Explicit	Operating concern key + version + record	Planned profitability for budget vs. actual analysis. Referenced in Feedback (stage 15).

12. PLM & Engineering Change

Product lifecycle management, innovation, and engineering change management tables. Central to Product Ideation (stage 2) and Continuous Improvement (stage 16).

Table	SAP Name	Description	Category	Confidence	Key Fields	Business Explanation
`CVRP` / `CVPR`	Recipe / Product Development	PLM recipe and product development management: recipe versions, ingredient lists, and development workflows.	PLM	Explicit	Composite	Early-stage product development data before formal material master creation. Referenced in Product Ideation (stage 2).
`AENR`	Engineering Change Master	Engineering change record: change number, description, valid-from date, status, reason for change, affected objects.	PLM	Explicit	PK `AESSION`	Tracks formal changes to product specifications, BOMs, and routings. Provides an audit trail for product modifications. Referenced in Continuous Improvement (stage 16).
`PS Module (WBS)`	Project System (Work Breakdown Structure)	Project structures for managing product development projects: WBS elements, milestones, budgets, and status.	PLM	Explicit	PRPS (WBS Element), PROJ (Project)	Manages product development timelines and budgets. Referenced in Product Ideation (stage 2).

13. SAP Retail-Specific

Tables specific to the SAP for Retail industry solution, covering article listing, assortment management, and promotion management.

Table	SAP Name	Description	Category	Confidence	Key Fields	Business Explanation
`WLK1`	Listing Conditions (Header)	Article listing condition header: material, listing profile, validity dates, listing status per site group.	Sales/Retail	Explicit	Composite	Controls which articles are available for sale at which store groups. Referenced in Product Design (stage 3) and Retail (stage 10).
`WLK2`	Listing Conditions (Items)	Article listing detail: individual site assignments, listing dates, and delisting dates.	Sales/Retail	Explicit	Composite	Site-level article availability. Referenced in Product Design (stage 3) and Retail (stage 10).
`WRSZ`	Assortment	Assortment definitions: assortment module, assigned articles, site assignments, validity periods, and assortment type.	Sales/Retail	Explicit	Composite	Manages store-specific product assortments. Controls which products appear in which stores. Referenced in Retail (stage 10).
`WPM*`	Promotion Management Tables	Suite of SAP Retail promotion management tables: promotion header, items, assigned articles, participating sites, and promotional pricing.	Sales/Retail	Explicit	Various	Retail-specific promotion planning and execution. Referenced in Promotion (stage 11).

14. Analytics & Reporting

Logistics Information System (LIS), BW structures, and other analytics tables referenced in the Feedback & Analytics lifecycle stage (stage 15).

Table	SAP Name	Description	Category	Confidence	Key Fields	Business Explanation
`S001` (S-tables)	LIS Statistics Tables	Logistics Information System statistical summary tables: pre-aggregated sales, purchasing, inventory, and production data at various granularity levels.	Analytics	Explicit	Various	Legacy operational reporting. Eliminated in S/4HANA in favour of CDS-based real-time analytics. Referenced in Feedback (stage 15).
`BW InfoCubes`	SAP BW Reporting Structures	SAP Business Warehouse InfoCubes: star schema structures for enterprise reporting and analytics across all SAP modules.	Analytics	Explicit	InfoCube-specific	Enterprise data warehousing for cross-module analytics. Migrated to SAP BW/4HANA or SAP Datasphere in S/4HANA environments. Referenced in Feedback (stage 15).

15. Service & CRM

Service management and CRM tables for post-sale customer engagement. Central to the Consumption lifecycle stage (stage 13).

Table	SAP Name	Description	Category	Confidence	Key Fields	Business Explanation
`VIQMEL`	Service Notification	Service notifications: notification number, type, customer reference, material, problem description, priority, status.	Service	Explicit	PK `QMNUM`	Post-sale service requests and complaints. Referenced in Consumption (stage 13) and Returns (stage 14).
`JEST`	Object Status	Individual status assignments for business objects: active, inactive, user status, system status.	Service	Explicit	PK `OBJNR` + `STAT`	Status management for service objects and equipment. Referenced in Consumption (stage 13).
`JSTO`	Status Profile	Object status profile: consolidates all system and user statuses for an object.	Service	Explicit	PK `OBJNR`	Overall status view for service objects. Referenced in Consumption (stage 13).
`CRMD_ORDERADM_H`	CRM Order Header	CRM service/interaction order header: order type, status, partner, dates. Only applicable if SAP CRM is deployed.	Service	Explicit	PK `GUID`	CRM service orders for advanced customer interaction management. Referenced in Consumption (stage 13). Conditional on SAP CRM deployment.

16. Foreign Trade

Import/export document tables for trade compliance and customs. Referenced in the Distribution lifecycle stage (stage 9).

Table	SAP Name	Description	Category	Confidence	Key Fields	Business Explanation
`EIKP`	Import/Export Header	Foreign trade document header: document number, export/import indicator, customs office, declaration date.	Logistics	Explicit	PK `EESSION`	Customs and trade compliance documentation. Referenced in Distribution (stage 9).
`EIPO`	Import/Export Items	Foreign trade document items: commodity code, country of origin, statistical value, preference indicator.	Logistics	Explicit	PK `EESSION` + `EPOSN`	Line-level customs data. Replaced by SAP GTS in S/4HANA.

Assumptions & Conventions

Inferred Tables

The following tables were not explicitly named in the application but were inferred from the data modeler's PDM source mappings (e.g., SAP:T001W.WERKS in dim_store attributes): T001W, T005S, VBUK. These are standard SAP tables and the inference confidence is high.

Naming Conventions

Table names follow SAP standard naming exactly as documented in SAP data dictionaries.
Field names use SAP technical field names (e.g., KUNNR, MATNR, VBELN) as referenced in the application.
"Composite" key means the primary key spans multiple fields specific to the table's function and varies by usage context.
Categories align with standard SAP module classification (MM, SD, PP, QM, FI, CO, WM, LE).

Scope

This document covers SAP ECC tables identified from the Product Lifecycle Journey application (index.html) and supporting PDM source mappings (data-modeler.html). It does not cover SAP APO tables beyond /SAPAPO/SNPTSDATA or external system tables. For S/4HANA equivalents and simplification patterns, see SAP S/4HANA Source Tables.