In this blog we identify the most important SAP Production Planning (PP) tables for users of:
These tables cover the full plan-to-produce cycle, from MRP planned orders through production orders, bills of material, routings, work centres, confirmations and material document postings, along with the master data and configuration tables you will need to build complete manufacturing reporting and analytics workflows. Accurate production analytics, whether you are measuring plan attainment, yield, scrap, cycle time or material consumption, depend on joining these tables together correctly. SAP Production Planning tables are found in the following SAP systems:
SAP Production Planning (PP) Transaction TablesProduction Order TablesProduction orders are the central transactional object in PP. They tell the shop floor what to make, how much, when, using which routing and which components. The tables below describe the order header, items, operations, confirmations and component reservations. AUFK - Order Master Data. A shared table used by Production Planning, Plant Maintenance, Project System and Controlling. Contains one row per order with fields such as order number (AUFNR), order type (AUART), company code (BUKRS), plant (WERKS) and object number (OBJNR). Join to AFKO on AUFNR. The OBJNR field is the anchor for joining to CO actual and plan postings, so AUFK is essential when reconciling production orders to controlling data. AFKO - Production Order Header. Contains the PP-specific header for each production order. Key fields include order number (AUFNR), planned material (PLNBEZ), total order quantity (GAMNG) and basic finish date (GLTRP). Join to AUFK on AUFNR for order-type and organisational context, and to AFPO on AUFNR for the item detail. Use AFKO as your starting point for any production order analysis. AFPO - Production Order Item. Contains one row per order item with fields such as order number (AUFNR), item number (POSNR), material (MATNR), order quantity (PSMNG) and received quantity (WEMNG). Join to AFKO on AUFNR. The ratio of WEMNG to PSMNG is your yield indicator at order-item level. AFVC - Operation within an Order. Contains one row per operation in the order routing. Key fields include operation routing number (AUFPL), counter (APLZL), operation number (VORNR) and work centre ID (ARBID). Join to AFKO on AUFPL to link operations to their order, and to AFVV on AUFPL and APLZL to pick up the paired quantity and date values. AFVC drives operation-level routing analysis. AFVV - Operation Quantities, Dates and Values. Paired one-to-one with AFVC on AUFPL and APLZL. Contains the planned operation quantity (MGVRG), actual quantity (ISMNG) and earliest start date (FSAVD) along with other scheduling fields. You need AFVC and AFVV together to do anything meaningful with production operations. AFRU - Order Confirmations. Contains one row per confirmation posting from the shop floor. Key fields include confirmation number (RUECK), counter (RMZHL), order number (AUFNR), confirmed quantity (ISMNG) and yield (LMNGA). Join to AFKO on AUFNR, and to AFVC on AUFPL and APLZL to associate confirmations with their operations. AFRU is the transactional heart of shop-floor reporting: throughput, labour time, scrap and rework all come from here. RESB - Reservations and Dependent Requirements. Contains one row per component reservation created by MRP or the production order. Key fields include reservation number (RSNUM), reservation item (RSPOS), order number (AUFNR), material (MATNR), required quantity (BDMNG) and the final issue flag (KZEAR). Join to AFKO on AUFNR. RESB tells you what components each order expected to consume; compare against MSEG or MATDOC movements to measure actual component consumption versus plan. MRP / Planning TablesPLAF - Planned Orders. The output of the MRP run, one row per planned order. Key fields include planned order number (PLNUM), material (MATNR), plant (WERKS), planned quantity (GSMNG) and the planning and end dates (PSTTR and PEDTR). Planned orders are converted into production orders (in PP) or purchase requisitions (in procurement). PLAF is your source for supply-side demand planning analytics and is where you will see the net effect of MRP before anything is released to the shop floor. MDKP - MRP Document Header. Contains one row per MRP planning run for a given material and plant. Key fields include the planning document number (DBLNR), material (MATNR), plant (WERKS) and planning date (BDZEI). Join to MDTB on DBLNR to get the individual demand and supply elements. MDKP is effectively the pointer into the MRP list. MDTB - MRP Table. Contains the individual demand and supply elements that make up the MRP list: requirements, receipts, planned orders, production orders, purchase requisitions and so on. Key fields include the planning document number (DBLNR), item number (DTNUM), material (MATNR), requirements date (DAT01), quantity (DELB1) and MRP element type (DELKZ). Join to MDKP on DBLNR. MDTB is the single richest source of demand and supply reconciliation data in PP. SAP Production Planning (PP) Master Data TablesPP transactions are only meaningful when joined to the master data that describes what is being made, how it is structured, where it is produced and by which resources. Bills of material, routings, work centres and material master data form the backbone of every production analytics workflow. Bill of Materials TablesMAST - Material to BOM Link. Contains the mapping between a material, plant and its BOM. Key fields include material (MATNR), plant (WERKS), BOM usage (STLAN), BOM number (STLNR) and alternative (STLAL). Join to STKO on STLNR and STLAL. MAST is the entry point: start here when you want to find the BOM for a given material. STKO - BOM Header. Contains one row per BOM with fields such as BOM number (STLNR), alternative (STLAL), BOM category (STLTY), base quantity (BMENG) and valid-from date (DATUV). Join to STPO on STLNR to retrieve the component list. Use the valid-from date if you need to pick a historical BOM version. STPO - BOM Item. Contains one row per component within a BOM. Key fields include BOM number (STLNR), internal line number (STLKN), component material (IDNRK), quantity (MENGE) and item category (POSTP). Join to STKO on STLNR. STPO is where you find the actual recipe: exploding a BOM means walking MAST to STKO to STPO, and recursing into STPO for sub-assemblies. Routing / Task List TablesMAPL - Assignment of Task Lists to Material. Contains the mapping between a material and its routing (task list). Key fields include material (MATNR), task list type (PLNTY), task list number (PLNNR) and group counter (PLNAL). Join to PLKO on PLNTY, PLNNR and PLNAL. MAPL is the bridge from the material master to the routing used to produce it. PLKO - Task List Header. Contains one row per routing with fields such as task list type (PLNTY), number (PLNNR), group counter (PLNAL), plant (WERKS) and status (STATU). Join to PLPO on PLNTY, PLNNR and PLNAL. Filter on STATU to exclude inactive routings. PLPO - Task List Operation. Contains one row per operation in the routing. Key fields include task list type (PLNTY), number (PLNNR), node number (PLNKN), operation number (VORNR), work centre (ARBID) and the first standard value (VGW01) which typically holds setup or machine time. Join to PLKO on PLNTY and PLNNR. PLPO drives your planned cycle-time and capacity analytics. Work Centre TablesCRHD - Work Centre Header. Contains one row per work centre with fields such as object type (OBJTY), object ID (OBJID), work centre name (ARBPL), plant (WERKS) and usage (VERWE). The OBJID here matches ARBID in AFVC and PLPO, which is how work centres are referenced from production orders and routings. CRHD is your work centre dimension for capacity, utilisation and OEE reporting. CRTX - Work Centre Text. Contains the language-specific description for each work centre. Key fields include object type (OBJTY), object ID (OBJID), language (SPRAS) and description (KTEXT). Join to CRHD on OBJTY and OBJID and filter by language to pick up readable work centre names. Material Master TablesMARA - Material Master: General Data. Contains client-level material data that is not specific to any plant. Key fields include material number (MATNR), material type (MTART), material group (MATKL) and base unit of measure (MEINS). In SAP S/4HANA the MATNR field is extended from 18 to 40 characters, so downstream analytics pipelines built on ECC-era assumptions may need to be resized. MARA is your primary material dimension table. MARC - Material: Plant Data including MRP. Contains material data that is specific to a plant, including the MRP settings that drive the planning run. Key fields include material (MATNR), plant (WERKS), MRP type (DISMM), MRP controller (DISPO) and procurement type (BESKZ). Join to MARA on MATNR. MARC is essential for any analysis of how materials are planned: BESKZ tells you whether the material is made, bought or both, and DISMM tells you the planning strategy. MBEW - Material Valuation. Contains the valuation view of the material, one row per valuation area and valuation type. Key fields include material (MATNR), valuation area (BWKEY), price control indicator (VPRSV), standard price (STPRS) and moving average price (VERPR). Join to MARA on MATNR. MBEW is where you pick up the unit cost used to value production output and component consumption, so it is fundamental to cost-of-goods-manufactured analytics. SAP Production Planning (PP) Goods Movement TablesEvery production order generates goods movements: component issues to the order, and goods receipts of the finished product into stock. These movements post material documents, which are where the actual quantities and values are recorded. The structure of these tables changed significantly in SAP S/4HANA, and the difference matters for anyone building analytics workflows that need to work across both systems. MKPF - Material Document Header (ECC). Contains one row per material document with fields such as material document number (MBLNR), material document year (MJAHR), posting date (BUDAT) and document type (BLART). Join to MSEG on MBLNR and MJAHR for the item detail. In SAP ECC, MKPF and MSEG are the primary source for all goods movements, including component issues (typically movement type 261) and production order receipts (101). MSEG - Material Document Items (ECC). Contains one row per line in a material document. Key fields include material document (MBLNR), year (MJAHR), line (ZEILE), material (MATNR), plant (WERKS), movement type (BWART) and quantity (MENGE). Join to MKPF on MBLNR and MJAHR, and to AUFK or AFKO on AUFNR where MSEG records the linked production order. Use BWART to filter between component issues, receipts and reversals. MATDOC - Universal Material Document (S/4HANA). In SAP S/4HANA, MATDOC replaces MKPF and MSEG as the single universal material document table. Key fields include material document number (MBLNR), year (MJAHR), line (ZEILE) and most of the fields previously found in MSEG. MKPF and MSEG still exist as compatibility views on top of MATDOC, so existing queries continue to work, but new analytics workflows should target MATDOC directly for best performance. If you are building a workflow that must run on both ECC and S/4HANA, most analytics teams will either query the compatibility views, or use DVW Connectors to abstract the difference at extraction time. SAP Production Planning (PP) Configuration TablesConfiguration tables (also known as customising tables) contain the settings and descriptions that define how your SAP PP module behaves. These are small, slowly changing tables that are useful for decoding the values stored in transaction and master data tables. The configuration tables listed below apply to both SAP ECC and SAP S/4HANA. T024D - MRP Controllers. Contains the list of MRP controllers defined per plant, with fields such as plant (WERKS) and MRP controller (DISPO). Join to MARC on WERKS and DISPO to attribute material planning responsibility in your reports. T399X - Order Type Master per Plant. Contains the plant-specific settings for each production order type, keyed by plant (WERKS) and order type (AUART). Join to AUFK on WERKS and AUART to decode and filter order types at plant level. T001W - Plants. Contains the list of plants defined in your system, with fields such as plant (WERKS), plant name (NAME1), country (LAND1) and region (REGIO). Join to MARC, AUFK and virtually every other PP table using WERKS. T001W is your plant dimension for every geographic cut of production data. Explore SAP PP Tables with a DVW ConnectorThe fastest way to explore SAP PP tables is to connect directly to your SAP system from your preferred analytics platform. DVW Connectors let you browse available tables, preview fields and extract data without writing any ABAP code. All DVW products support both SAP ECC and SAP S/4HANA, and they handle the MKPF/MSEG to MATDOC transition transparently. To see how all 27 tables in this blog connect to each other, visit our SAP PP Table Relationships page for an interactive data model diagram with join keys and ECC vs S/4HANA compatibility. All DVW products include a 30-day free trial with full functionality, so you can start working with these tables right away. Visit our Free Trial page to get started, or explore our Help Centre for detailed documentation on connecting to SAP PP tables. Next StepsSee these SAP PP tables in action. Register for a 30-day free trial and start extracting production, BOM, routing and material data from your SAP system today. Comments are closed.
|
Categories
All
Archives
May 2026
|
RSS Feed