IT CanvassTalk to an advisor
SAP tables · LessonBy , SAP Trainer, 10 yrs · Published · SAP S/4HANA 2023 · all levels

MARC

MARC is a key SAP table in MM (Materials). It stores plant-specific material data, the attributes of a material that vary by plant (MRP, procurement, production settings).

Quick answer

Use MARC to find plant-specific settings (MRP type, controller, procurement).

Key takeaways
  • The key is MATNR + WERKS, so there is one MARC row per material per plant.
  • MARA, general material data.
  • MARD, storage-location stock.
  • Watch out: Reading tables directly instead of using CDS/reports where appropriate.

What it stores

It stores plant-specific material data, the attributes of a material that vary by plant (MRP, procurement, production settings).

Key fields

  • MATNR, material (key).
  • WERKS, plant (key).
  • DISMM, MRP type.
  • DISPO, MRP controller.
  • BESKZ, procurement type.

Keys and relationships

The key is MATNR + WERKS, so there is one MARC row per material per plant. It complements MARA (general data) with the plant-level settings that drive MRP and procurement.

Working with it

Use MARC to find plant-specific settings (MRP type, controller, procurement). A material must be extended to a plant (MARC row) before it can be used there. View its structure in SE11 and its data (with authorization) in SE16N.

Common pitfalls

  • Reading tables directly instead of using CDS/reports where appropriate.
  • Ignoring header/item relationships.
  • Performance: querying large tables without indexed selection.

Practice challenge

+0 XPStreak ×0
Question 1 of 3
Which statement is true of MARC?

Frequently asked questions

What does MARC stand for in SAP?
MARC is a key SAP table in MM (Materials). It stores plant-specific material data, the attributes of a material that vary by plant (MRP, procurement, production settings).
Which fields matter most in MARC?
The key is MATNR + WERKS, so there is one MARC row per material per plant.
What is worth remembering about MARC in practice?
Use MARC to find plant-specific settings (MRP type, controller, procurement).
What tends to go wrong with MARC?
Reading tables directly instead of using CDS/reports where appropriate. Ignoring header/item relationships. Performance: querying large tables without indexed selection.
Already working on SAP and stuck on a live ticket?Get an expert SAP developer on screen-share to finish your daily tasks with you. Deliver on time, protect your reputation and your job. Monthly support only, no task-wise plans.Task assigned · no idea where to startStill stuck · your job on the lineExpert joins your screenDelivered on timeExplore On Job Support