Material Master Tables in SAP: MARA, MARC, MARD, MVKE, and Retail Article Data
Understanding SAP’s material master data isn’t just about memorizing table names. It’s about knowing where the data lives, why it matters, and what happens when it’s wrong. Many beginners get lost in the sheer volume of information.
In SAP, the material master is the central repository for all product-related information. This data isn’t stored in one giant table; it’s spread across many, each serving a specific purpose. For anyone working with SAP, especially in retail, knowing these core tables is non-negotiable.
Today, we’ll cut through the noise and focus on the heavy hitters: MARA, MARC, MARD, and MVKE. We’ll also touch on how these tables interact with retail article data, giving you a clear picture of what’s happening behind the scenes.
What are MARA and MARC?
MARA is the foundational table for all material master data in SAP. Think of MARA as the general ledger for your products – it holds the basic, client-level information that applies to a material no matter where it’s sold or stored. This includes the material number itself (MATNR), its description, unit of measure, material type, and industry sector.
If you change a material description in MARA, it changes everywhere. It’s the highest level of detail.
MARC, on the other hand, dives into plant-specific data. A plant in SAP is a physical location, like a factory or a distribution center. While MARA tells you what the material is, MARC tells you how that material behaves at a specific plant.
This table stores critical information like the material’s purchasing data (e.g., purchasing group), planning data (e.g., MRP type), and storage location requirements for that particular plant. Every material in every plant has an entry in MARC.
For example, a specific type of shirt (material in MARA) might be produced in one plant (entry in MARC for Plant A) and simply distributed from another (another entry in MARC for Plant B). The planning parameters for each plant could be vastly different.
What is MARD?
MARD takes us down another level: storage location data. A storage location is a more granular subdivision within a plant. For instance, within a factory (plant), you might have a “raw materials storage” location and a “finished goods storage” location. MARD tracks quantities and values of materials at these specific locations.
This table is where you’ll find details like the total stock quantity, unrestricted stock, blocked stock, and quality inspection stock for a material within a particular storage location. It’s crucial for inventory management. Without accurate MARD data, you wouldn’t know how much of a product you actually have available at a given warehouse bay.
In my experience, incorrect MARD entries are a common source of inventory discrepancies. A simple goods receipt posted to the wrong storage location can throw off your entire stock count.
How Does MVKE Fit In?
MVKE is all about sales data, specifically at the sales organization and distribution channel level. A sales organization is responsible for selling products, and a distribution channel defines how those products are sold (e.g., wholesale, retail, internet sales). This table stores information like sales unit, minimum order quantity, delivery plant, and pricing conditions specific to how a material is sold through a particular channel.
Imagine a laptop. The basic details are in MARA. How it’s managed in the factory is in MARC.
Its stock in the warehouse is in MARD. But how it’s priced and sold through an online store versus a physical retail outlet?
That’s MVKE’s domain. Each unique combination of material, sales organization, and distribution channel gets an entry here.
This table is vital for sales order processing and pricing determination. If MVKE data is missing or wrong, sales orders can’t be created correctly, leading to delays and customer frustration.
What About Retail Article Data?
In SAP Retail, materials are often referred to as “articles.” The core tables we just discussed (MARA, MARC, MARD, MVKE) still play a central role, but SAP Retail adds specialized tables and fields to handle the unique requirements of retail businesses.
For example, articles often have specific characteristics like color, size, or style, which are managed through variants. While MARA still holds the generic article data, additional retail-specific tables link these variants and their attributes. For instance, the learn SAP Retail journey often starts with understanding how these core tables are extended for fashion or grocery scenarios.
When you create and manage SAP Retail articles, you’re essentially populating these underlying tables, often through user-friendly interfaces that abstract away the complexity. But knowing the tables helps you troubleshoot, write reports, and understand data flows better.
Here’s a quick map of the tables and their organizational levels:
| Table | Organizational Level | Key Fields | Common Joins | Retail Article Implications |
|---|---|---|---|---|
| MARA | Client (highest) | MATNR (Material Number) | MARC, MARD, MVKE | Basic article data (description, type) |
| MARC | Plant | MATNR, WERKS (Plant) | MARA, MARD | Plant-specific article data (planning, purchasing) |
| MARD | Storage Location | MATNR, WERKS, LGORT (Storage Location) | MARA, MARC | Inventory quantities at specific storage locations |
| MVKE | Sales Org/Dist Channel | MATNR, VKORG (Sales Org), VTWEG (Dist. Channel) | MARA | Sales-specific article data (pricing, delivery plant) |
Understanding these material master tables is more than just academic knowledge; it’s practical wisdom. It empowers you to diagnose issues, extract meaningful data, and contribute more effectively to any SAP project. Each table tells a part of the material’s story, from its basic identity to its stock levels and how it’s sold.
Mastering these fundamentals will serve you well, whether you’re a consultant, an end-user, or a developer. It’s the backbone of virtually every process involving products in SAP.