Dinesh

The core material master data in SAP is split across several relational database tables, with the primary tables being MARA, MAKT, and MARC.

General and Descriptive Tables

• MARA: General material data (client level) like material type, industry sector, base unit of measure, and weights.
• MAKT: Material descriptions and short texts in multiple languages.

Plant and Storage Tables

• MARC: Plant-specific material data like MRP parameters, procurement type, and safety stock.
• MARD: Storage location data including stock quantities per storage location.

Valuation and Sales Tables

• MBEW: Material valuation and accounting data like standard price, moving average price, and valuation class.
• MVKE: Sales organization and distribution channel

I can provide the exact table joins

SAP Bill of Material (BOM) transactions manage the list of component items needed to build a product, using key codes like CS01 for creation, CS02 for changes, and CS03 for display. [1]

Material BOM Transactions

• CS01: Create material BOM by entering the parent material, plant, and usage.
• CS02: Change or update component quantities and add new parts.
• CS03: Display the item overview and structure safely without edit rights. [1, 2, 3]

Reporting and Explosion Transactions

• CS11: Single-level BOM explosion.
• CS12: Multi-level BOM explosion to see sub-components.
• CS15: Where-used list to check which parent assemblies use a specific component.

MRP types in SAP control how the system plans and replenishes inventory, split primarily into Deterministic Planning, Consumption-Based Planning, and Master Production Scheduling. These codes dictate whether procurement triggers from actual customer demands, past consumption levels, or targeted production schedules.

Deterministic Planning (MRP)

• PD (Material Requirements Planning): The standard workhorse code for production materials. It calculates net requirements based on all demands like sales orders and forecasts across multi-level Bill of Materials (BOM).
• P1 to P4: Specialised MRP types that factor in a Planning Time Fence, automatically firming up procurement proposals inside specific date ranges.

A lot size in SAP is a rule used by Material Requirements Planning (MRP) to calculate exact procurement or production order quantities. Key procedures include lot-for-lot (EX), fixed lot size (FX), and period lot sizing.

Key Types of Lot Sizing Procedures

• Lot-for-Lot (EX): Creates an order quantity that matches the exact net requirement without rounding or grouping.
• Fixed Lot Size (FX): Generates orders in a set, predefined quantity, splitting larger needs into multiple orders of that exact size.
• Period Lot Sizing: Groups requirements together across specific time frames, such as daily, weekly, or monthly intervals.

In SAP, Goods Receipt (GR) processing time is the number of workdays required to inspect, process, and place received goods into inventory after delivery. It ensures accurate material availability dates for Material Requirements Planning (MRP) and production scheduling.

Where to Find and Maintain GR Processing Time

This parameter is configured primarily at the material level in the SAP system:

• Material Master (MRP 2 View): Navigate to the MRP 2 view of your material (Transaction MM02 or MM03). Look for the GR processing time field (field name: WEBAZ). Here you can define the number of workdays required for the inspection and storage process.
• In SAP, the Planned Delivery Time (PDT) is the estimated number of calendar days a vendor needs to fulfill and deliver a purchase order. It is primarily used by the MRP (Material Requirements Planning) engine to calculate backward scheduling, ensuring that Purchase Requisitions (PR) and Purchase Orders (PO) are triggered with enough lead time. [1,

• Managed BOM creation via Enovia MatrixOne, maintaining 100% data accuracy within strict turnaround time (TAT).
• Executed complex Change Management processes and cut-overs, successfully controlling inventory levels.
• Collaborated with NPI and cross-functional teams in daily standups to ensure seamless project implementation.