Understanding the SD-MM Table Relationship in SAP

Categories: SAP Materials Management (MM), SAP Sales and Distribution (SD)

Pic. Type: Transaction Codes & Tables Cheat Sheets

Ref: https://blog.csdn.net/weixin_52158549/article/details/122597572

SAP SD-MM table relationship diagram illustrating sales orders, deliveries, purchase orders, goods movements, and accounting document flow.

Picture Description

This handy diagram breaks down the basic table relationships showing the document flow from a sales order all the way through to purchasing and accounting in SAP. It’s a simplified view of SD-MM Integration, but perfect for getting a grasp of the big picture.

Sales Side (SD) Tables – Customer Order to Billing

On the left side, we see the typical SD process:

It starts with a Sales Order: This is where it all begins! Key tables are VBAK (header) and VBAP store details about the sales order itself, such as customer, order dates, and ordered products.
Delivery is Created: Once the order is ready to ship, a delivery document is made (LIKP – header, LIPS – item).
Goods Issue Happens: When the goods are physically shipped, a Material Document is created (MKPF – header, MSEG – item) on the SD side to reflect the stock leaving the warehouse.
Finally, Billing is Processed: To invoice the customer, a Billing Document is generated (VBRK – header, VBRP – item).

Materials Management Side (MM) Tables – Purchasing the Goods

Now, let’s look at the MM side on the right. This usually comes into play if the sales order triggers a need to purchase materials (think of make-to-order or if stock levels are low).

Purchase Requisition & Purchase Order: If materials need to be procured, a Purchase Requisition (EBAN) is created, which then gets converted into a Purchase Order (EKKO – header, EKPO – item).
Goods Receipt: When the purchased goods arrive from the vendor, another Material Document is created (MKPF – header, MSEG – item) in MM to record the stock coming into the warehouse.
Invoice Receipt: Finally, when the vendor sends their invoice, it’s recorded in the system via an Invoice document (RBKP – header, RSEG – item).

The SD-MM Connection – How Tables Link Up

The magic happens in the middle!

Schedule Lines are Key: The VBEP table (Sales Order Schedule Line) in SD is crucial. It can trigger the creation of a Purchase Requisition (EBNK) or even directly a Purchase Order (EKKN). This is how the sales demand flows into the purchasing process.
Material Documents Bridging the Gap: Notice the MKPF and MSEG tables appearing on both sides. This is because the Goods Issue in SD and Goods Receipt in MM both use Material Documents to track stock movements, even though they are for different purposes.

Accounting Impact of SD & MM Transactions – The End Result

At the bottom, you see Accounting Header (BKPF) and Accounting Segment (BSEG). Both SD and MM processes eventually post financial data into these accounting tables, ensuring everything is reflected in your financial books!

SD-MM Integration In a Nutshell

This diagram is a great visual to understand how a sales order can kick off a whole chain of events across both SD and MM in SAP. It shows the key documents created and the tables where the important data resides.

A sales order in SD can prompt a purchase order in MM if additional materials are needed.
Deliveries handle the logistics of shipping items to customers (SD) or receiving them from vendors (MM).
Goods movements update inventory, recorded by material documents.
Billing (customer invoices) and invoicing (vendor checks) feed into accounting to keep financials accurate and synchronized.

This flow ensures that every step—order creation, stock handling, and final settlement—connects logically between SD and MM, and ultimately ties into the financial accounting core of SAP.