Sapster.io
SAP Material Movements: MKPF and MSEG Deep Dive
Feb 8, 2025

SAP Material Movements: MKPF and MSEG Deep Dive

SAP Material Movements: MKPF and MSEG Deep Dive

Understanding SAP material movements requires mastery of two critical tables: MKPF (Material Document Header) and MSEG (Material Document Segment). Whether you're tracking goods receipts, managing inventory transfers, or auditing warehouse operations, these tables form the backbone of SAP MM functionality. In this comprehensive guide, we'll explore the intricate relationship between MKPF and MSEG, decode movement types, and provide practical queries that every SAP MM consultant needs in their toolkit.

The Foundation: Understanding Material Document Architecture

At the heart of every material movement in SAP lies the material document structure—a header-item relationship that mirrors the physical reality of warehouse operations. The MKPF table stores the header information for each material document, while MSEG contains the individual line items that detail what actually moved, where it went, and in what quantity.

This architecture reflects a fundamental principle in SAP: every physical goods movement generates a material document consisting of one header (MKPF) and one or more items (MSEG). The relationship is straightforward—one MKPF record can have multiple MSEG records, but each MSEG record belongs to exactly one MKPF header. The link between these tables is established through three key fields: MBLNR (Material Document Number), MJAHR (Material Document Year), and ZEILE (Item Number in MSEG).

MKPF: The Material Document Header

The MKPF table captures document-level information that applies to the entire material movement transaction. Think of it as the envelope that contains all the details about when, who, and why a movement occurred. Key fields in MKPF include:

  • MBLNR - Material Document Number: The unique identifier for each material document
  • MJAHR - Material Document Year: Fiscal year of document creation
  • BLDAT - Document Date: The date on which the document was created
  • BUDAT - Posting Date: The date used for accounting and valuation purposes
  • USNAM - User Name: Who created the document
  • TCODE - Transaction Code: Which transaction was used (MIGO, MB1A, etc.)
  • XBLNR - Reference Document Number: External reference like delivery note or bill of lading
  • BKTXT - Document Header Text: Free-text description of the movement

The MKPF table provides the transactional context. When you post a goods receipt against a purchase order, MKPF records who performed the transaction, when it was posted, and which transaction code was used. This audit trail is invaluable for compliance, troubleshooting, and process optimization.

MSEG: The Material Document Segment

While MKPF provides the context, MSEG contains the actual substance of what moved. Each line item in MSEG represents a specific material movement with granular details about quantities, storage locations, and valuation. Critical MSEG fields include:

  • MBLNR, MJAHR, ZEILE - The composite key linking back to MKPF
  • BWART - Movement Type: The most important field defining the nature of the movement
  • MATNR - Material Number: Which material moved
  • WERKS - Plant: Source or destination plant
  • LGORT - Storage Location: Specific warehouse location
  • MENGE - Quantity: How much moved (in base unit of measure)
  • MEINS - Unit of Measure: The UoM for the quantity
  • EBELN, EBELP - Purchase Order Number and Item: Links to procurement documents
  • SHKZG - Debit/Credit Indicator: Crucial for understanding inventory impact
  • SOBKZ - Special Stock Indicator: Identifies consignment, project stock, etc.
  • CHARG - Batch Number: For batch-managed materials
  • BWTAR - Valuation Type: For split valuation scenarios

The SHKZG field deserves special attention. This debit/credit indicator determines whether the movement increases (S = credit, adding to stock) or decreases (H = debit, removing from stock) inventory. Understanding SHKZG is essential for accurate inventory reconciliation and reporting.

Decoding Movement Types: The BWART Field

The movement type (BWART) is the DNA of every material movement in SAP. It defines not only what type of movement occurred but also triggers specific accounting postings, updates stock levels, and determines which fields are mandatory during posting. SAP delivers hundreds of standard movement types, but certain ones are fundamental to daily operations.

Essential Movement Types for Goods Receipt

  • 101 - Goods Receipt for Purchase Order: The most common movement type, posting materials into unrestricted stock when receiving against a PO
  • 103 - Goods Receipt into Blocked Stock: Used when received materials need quality inspection before release
  • 105 - Goods Receipt from Blocked Stock: Releasing materials from quality inspection into unrestricted use
  • 122 - Return Delivery to Vendor: Reversing a goods receipt or returning defective materials

Key Movement Types for Goods Issue

  • 201 - Goods Issue for Cost Center: Consuming materials for internal use, maintenance, or consumption
  • 261 - Goods Issue for Production Order: Issuing components to manufacturing
  • 601 - Goods Issue for Delivery: Shipping materials to customers (integrated with SD)
  • 551 - Goods Issue for Scrapping: Writing off damaged or obsolete inventory

Transfer and Adjustment Movement Types

  • 311 - Transfer Posting Plant to Plant: Moving materials between different plants in one step
  • 313/315 - Transfer in Transit: Two-step plant-to-plant transfer creating stock in transit
  • 301 - Transfer Posting Storage Location to Storage Location: Moving materials within the same plant
  • 309 - Transfer from Material to Material: Material substitution or conversion
  • 701/702 - Physical Inventory Differences: Adjusting stock based on cycle count results

Each movement type is configured in SAP with specific attributes that control its behavior. This configuration (accessible via transaction OMJJ) defines whether the movement updates quantity and value, which stock types are affected, and which account determination keys are used for financial posting. As an MM consultant, understanding these configurations allows you to troubleshoot posting issues and design custom movement types when business requirements demand them.

Special Stock Indicators: The SOBKZ Dimension

The special stock indicator (SOBKZ) in MSEG adds another layer of complexity to material movements. Special stocks are materials physically present in your plant but belonging to different ownership categories or segregated for specific purposes. Understanding SOBKZ is critical for accurate inventory valuation and reporting.

Common Special Stock Types

  • Blank/Space - No special stock, regular unrestricted/blocked/quality inventory
  • K - Consignment Stock: Materials owned by vendor but stored at your location
  • V - Customer Consignment: Materials you own but stored at customer location
  • W - Returnable Packaging: Containers and packaging materials for returns
  • Q - Project Stock: Materials earmarked for specific projects (WBS elements)
  • M - Pipeline/Vendor Consignment: For continuous supply scenarios

Special stock requires careful handling in queries. When you query MSEG for inventory, you must consider SOBKZ to avoid double-counting or misrepresenting available inventory. For example, consignment stock (SOBKZ = 'K') should not be included when calculating your own inventory value, as you don't own these materials until you withdraw them for consumption.

Practical SQL Queries for Material Movements

Theory becomes valuable only when applied. Here are battle-tested queries that SAP MM consultants use daily for analysis, troubleshooting, and reporting. These queries assume you're working with SAP HANA or a similar SQL-compliant database.

Query 1: Goods Receipts for Last 30 Days

SELECT
  h.MBLNR,
  h.MJAHR,
  h.BLDAT AS document_date,
  h.BUDAT AS posting_date,
  h.USNAM AS created_by,
  h.XBLNR AS reference,
  i.ZEILE AS item,
  i.BWART AS movement_type,
  i.MATNR AS material,
  i.WERKS AS plant,
  i.LGORT AS storage_location,
  i.MENGE AS quantity,
  i.MEINS AS uom,
  i.EBELN AS purchase_order,
  i.EBELP AS po_item,
  i.SHKZG AS debit_credit
FROM MKPF h
INNER JOIN MSEG i
  ON h.MBLNR = i.MBLNR
  AND h.MJAHR = i.MJAHR
WHERE h.BUDAT >= ADD_DAYS(CURRENT_DATE, -30)
  AND i.BWART IN ('101', '103', '105')
  AND i.SHKZG = 'S'  -- Credit (increasing stock)
ORDER BY h.BUDAT DESC, h.MBLNR, i.ZEILE;

This query retrieves all goods receipts posted in the last 30 days, filtering for the primary GR movement types. The SHKZG = 'S' condition ensures we only see movements that increase inventory. This query is invaluable for analyzing receiving efficiency, identifying bottlenecks in the procurement-to-payment process, and reconciling physical receipts with system postings.

Query 2: Material Consumption by Cost Center

SELECT
  i.KOSTL AS cost_center,
  i.MATNR AS material,
  SUM(CASE WHEN i.SHKZG = 'S' THEN i.MENGE ELSE -i.MENGE END) AS net_quantity,
  i.MEINS AS uom,
  COUNT(DISTINCT h.MBLNR) AS number_of_movements,
  MIN(h.BUDAT) AS first_movement,
  MAX(h.BUDAT) AS last_movement
FROM MKPF h
INNER JOIN MSEG i
  ON h.MBLNR = i.MBLNR
  AND h.MJAHR = i.MJAHR
WHERE i.BWART = '201'
  AND h.BUDAT BETWEEN '20250101' AND '20251231'
  AND i.KOSTL IS NOT NULL
GROUP BY i.KOSTL, i.MATNR, i.MEINS
HAVING SUM(CASE WHEN i.SHKZG = 'S' THEN i.MENGE ELSE -i.MENGE END) > 0
ORDER BY i.KOSTL, net_quantity DESC;

This query aggregates material consumption by cost center for the current year using movement type 201. The CASE statement handles the SHKZG indicator to calculate net consumption correctly (accounting for any reversal postings). Financial controllers and plant managers use this type of analysis to understand departmental spending patterns, identify cost-saving opportunities, and allocate overhead more accurately.

Query 3: Inventory Movements by Material (Complete History)

SELECT
  h.MBLNR,
  h.MJAHR,
  h.BUDAT AS posting_date,
  i.BWART AS movement_type,
  i.SHKZG AS dr_cr,
  CASE
    WHEN i.SHKZG = 'S' THEN i.MENGE
    ELSE -i.MENGE
  END AS signed_quantity,
  i.WERKS AS plant,
  i.LGORT AS sloc,
  i.SOBKZ AS special_stock,
  i.CHARG AS batch,
  i.EBELN AS po_number,
  i.AUFNR AS production_order,
  i.KDAUF AS sales_order,
  i.KDPOS AS so_item,
  h.USNAM AS user,
  h.BKTXT AS header_text
FROM MKPF h
INNER JOIN MSEG i
  ON h.MBLNR = i.MBLNR
  AND h.MJAHR = i.MJAHR
WHERE i.MATNR = '000000000000123456'  -- Replace with actual material
  AND i.WERKS = '1000'  -- Optional: filter by plant
  AND i.SOBKZ = ''  -- Only regular stock, not special stock
ORDER BY h.BUDAT, h.MBLNR, i.ZEILE;

This comprehensive material history query shows every movement for a specific material, signed appropriately to reflect increases and decreases. Notice how we include document references (PO, production order, sales order) to trace the movement back to its originating document. This query is essential for root cause analysis when investigating stock discrepancies, tracking material genealogy for quality issues, or performing forensic analysis of inventory movements.

Query 4: Open Goods Receipts Awaiting Quality Inspection

SELECT
  h.MBLNR,
  h.MJAHR,
  h.BUDAT AS gr_date,
  DAYS_BETWEEN(h.BUDAT, CURRENT_DATE) AS days_in_qa,
  i.MATNR AS material,
  i.MENGE AS quantity,
  i.MEINS AS uom,
  i.WERKS AS plant,
  i.LGORT AS sloc,
  i.CHARG AS batch,
  i.EBELN AS purchase_order,
  i.EBELP AS po_item,
  h.XBLNR AS delivery_note
FROM MKPF h
INNER JOIN MSEG i
  ON h.MBLNR = i.MBLNR
  AND h.MJAHR = i.MJAHR
WHERE i.BWART = '103'  -- GR into blocked stock
  AND NOT EXISTS (
    SELECT 1 FROM MSEG i2
    WHERE i2.MATNR = i.MATNR
      AND i2.WERKS = i.WERKS
      AND i2.LGORT = i.LGORT
      AND i2.CHARG = i.CHARG
      AND i2.BWART = '105'  -- Release from QA
      AND i2.MBLNR > i.MBLNR
  )
ORDER BY days_in_qa DESC;

This query identifies materials received into quality inspection (movement 103) that haven't yet been released with movement 105. The days_in_qa calculation helps quality managers identify aging inventory in blocked stock, prioritize inspection activities, and meet supplier SLAs. The NOT EXISTS subquery ensures we only see materials that haven't been subsequently released.

Query 5: Stock Transfers Between Plants

SELECT
  h.MBLNR,
  h.MJAHR,
  h.BUDAT AS transfer_date,
  i.BWART AS movement_type,
  i.MATNR AS material,
  CASE
    WHEN i.BWART = '311' THEN i.WERKS
    WHEN i.BWART = '313' THEN i.WERKS
  END AS source_plant,
  CASE
    WHEN i.BWART = '311' THEN i.UMWRK
    WHEN i.BWART = '315' THEN i.WERKS
  END AS destination_plant,
  i.MENGE AS quantity,
  i.MEINS AS uom,
  h.BKTXT AS transfer_reason
FROM MKPF h
INNER JOIN MSEG i
  ON h.MBLNR = i.MBLNR
  AND h.MJAHR = i.MJAHR
WHERE i.BWART IN ('311', '313', '315')
  AND h.BUDAT >= '20250101'
ORDER BY h.BUDAT DESC;

Plant-to-plant transfers are critical for multi-site operations. Movement 311 is a one-step transfer, while 313/315 is a two-step process creating stock in transit. This query tracks both types, using the UMWRK field (receiving plant in transfer postings) to identify source and destination. Supply chain planners use this data to analyze inter-plant material flows, optimize transfer frequencies, and reduce in-transit inventory.

Performance Considerations and Best Practices

MKPF and MSEG are among the largest tables in any production SAP system. A typical manufacturing company accumulates millions of material document records annually. Querying these tables efficiently requires understanding indexing and leveraging SAP's database optimization features.

Index-Friendly Query Patterns

Always include MJAHR (material document year) in your WHERE clause when querying by document number. The primary key of MKPF is MBLNR + MJAHR, and for MSEG it's MBLNR + MJAHR + ZEILE. Queries that omit MJAHR force full table scans or inefficient index range scans.

When filtering by date, use BUDAT (posting date) rather than BLDAT (document date) in MKPF. BUDAT is typically indexed and is the date used for financial and inventory valuation. Most SAP standard indexes include BUDAT, making date-range queries performant.

For material-specific queries, leverage the MATNR field in MSEG. However, be aware that MATNR is stored with leading zeros in SAP tables. Always use the proper 18-character format with leading zeros, or utilize SAP's CONVERSION_EXIT_ALPHA_INPUT function when building dynamic queries.

Partitioning and Archiving

In SAP HANA environments, MKPF and MSEG are often partitioned by MJAHR to improve query performance and facilitate archiving. When writing queries, explicitly filtering on recent years (e.g., MJAHR >= '2023') allows the database to prune partitions and scan only relevant data.

Establish a robust archiving strategy using SAP's MM_MATBEL archiving object. Archive completed material documents older than your retention requirements (typically 5-7 years for most jurisdictions). This keeps active tables lean and maintains system performance as transaction volume grows.

Avoiding Common Query Pitfalls

Never query MSEG alone without considering MKPF. While MSEG contains most fields you need, document-level attributes like USNAM (user), TCODE (transaction), and CPUDT (entry date) reside only in MKPF. More importantly, cancelled material documents have a MJAHR = '0000' indicator in MKPF—querying MSEG alone may include cancelled documents in your results.

Be cautious when aggregating quantities directly from MSEG without considering SHKZG. The MENGE field in MSEG always stores positive values; the SHKZG indicator determines whether the movement increases (S) or decreases (H) inventory. Always apply signed quantity logic: multiply MENGE by +1 for SHKZG = 'S' and by -1 for SHKZG = 'H'.

Integration Points and Related Tables

Material documents don't exist in isolation. MKPF and MSEG integrate with virtually every module in SAP, and understanding these connections unlocks deeper analytical capabilities.

Financial Integration: BKPF and BSEG

Every material document posting generates corresponding accounting documents stored in BKPF (Accounting Document Header) and BSEG (Accounting Document Segment). The link is established through MKPF-BELNR (accounting document number) and MJAHR. This connection allows you to trace material movements to their financial impact, essential for month-end closing and variance analysis.

Procurement Integration: EKKO and EKPO

Goods receipts against purchase orders link MSEG to EKKO (PO Header) and EKPO (PO Items) through the EBELN and EBELP fields. This relationship enables three-way matching (PO, GR, invoice) and provides visibility into procurement lead times, supplier performance, and open PO analysis.

Inventory Management: MARD and MCHB

While MSEG records movements, MARD (Storage Location Stock) and MCHB (Batch Stock) maintain current inventory balances. These tables are updated in real-time as material documents post. Reconciling MSEG movements with MARD/MCHB balances is a common audit and troubleshooting activity.

Production Integration: AFKO

Goods movements for production orders (particularly movement types 261 for issue and 101/131 for receipts) link to AFKO (Order Header) through the AUFNR field in MSEG. This connection enables production variance analysis, backflushing tracking, and manufacturing efficiency metrics.

Advanced Topics: Reversals and Cancellations

Understanding how SAP handles material document corrections is crucial for data integrity and accurate reporting. When you reverse a material document using transaction MBST, SAP doesn't delete the original document. Instead, it creates a reversal document with opposite quantity signs and links them through the SMBLN (Reversed Material Document) field in MSEG.

To identify reversed documents, check MSEG-SMBLN. If populated, this document has been reversed, and SMBLN contains the reversal document number. When querying for open goods receipts or issues, always filter out reversed documents to avoid including cancelled transactions in your analysis:

WHERE i.SMBLN = ''  -- Exclude reversed documents

Similarly, check MKPF-XBLNR_MKPF for cancellation indicators in newer SAP releases. Some organizations implement custom Z-fields to flag documents that shouldn't be included in operational reporting, so consult your system's specific configuration.

Conclusion: Mastering Material Movements

The MKPF and MSEG tables form the transactional foundation of SAP Materials Management. Mastering these tables—their structure, relationships, key fields, and integration points—transforms you from an SAP user into an SAP expert capable of solving complex inventory challenges, optimizing warehouse operations, and delivering data-driven insights.

The queries and concepts presented here represent just the beginning. As you apply these techniques to your specific business scenarios, you'll develop an intuition for material document behavior that enables rapid troubleshooting, intelligent reporting, and strategic process improvement. Whether you're investigating stock discrepancies, analyzing supplier performance, or designing custom reports, the knowledge of how material movements flow through MKPF and MSEG will serve as your compass.

Remember that SAP is highly configurable. Movement types can be customized, special stock indicators can be extended, and custom fields may capture business-specific data in your system. Always validate these concepts against your organization's SAP configuration, and maintain close collaboration with your functional teams to understand the business context behind the data.

Continue exploring, querying, and analyzing. The deeper your understanding of material documents, the more valuable you become to your organization's digital transformation journey.