Subcontracting Component Consumption and Stock at Vendor Reconciliation Report
Short answer: A custom ALV report that compares the planned consumption of components sent to the vendor on subcontracting orders with the consumption posted at finished goods receipt (543) and lists it together with the stock left at the vendor. Excess consumption, scrap and overdue subcontracting deliveries show up in one list.
- Estimated effort
- M · 5–7 working days
- System
- ECC and S/4HANA
- Tables
- 8
- Scope
- Global
- Built by
- NeKuDos Teknoloji
- Last updated
Why is the standard not enough?
ME2O monitors the component stock provided to the vendor and the requirements, and MBLB lists the stock at the vendor, but neither compares the actual component consumption at finished goods receipt with the consumption expected for the finished quantity and shows excess consumption and overdue subcontracting deliveries on the same line. Year-end stock reconciliation with the vendor is therefore done by hand with MB51 and ME2O output.
Who uses it? Subcontracting and purchasing specialists, production planning, inventory control and costing teams.
Closest standard alternatives
Tables used
The tables the report reads and their join fields. ECC and S/4HANA differences are marked separately.
| Table | Role | Join | System |
|---|---|---|---|
| EKKOPurchasing Document Header | Subcontracting order header: vendor (driving table) | — | ECC + S/4 |
| EKPOPurchasing Document Item | Subcontracting item: finished material, order quantity, item category | EKPO-EBELN = EKKO-EBELN | ECC + S/4 |
| EKETPurchasing Schedule Lines | Subcontracting delivery date | EKET-EBELN = EKPO-EBELN AND EKET-EBELP = EKPO-EBELP | ECC + S/4 |
| RESBReservation/Dependent Requirements | Subcontracting components: planned component quantity | RESB-EBELN = EKPO-EBELN AND RESB-EBELP = EKPO-EBELP | ECC + S/4 |
| EKBEPurchasing Document History | Finished goods receipts | EKBE-EBELN = EKPO-EBELN AND EKBE-EBELP = EKPO-EBELP | ECC + S/4 |
| MSEGMaterial Document Item | Component consumption movements (543/544) | MSEG-EBELN = EKPO-EBELN AND MSEG-EBELP = EKPO-EBELP AND MSEG-MATNR = RESB-MATNR | ECC + S/4 |
| MSLBSpecial Stocks with Vendor | Special stock at the vendor (SOBKZ = O) | MSLB-LIFNR = EKKO-LIFNR AND MSLB-MATNR = RESB-MATNR AND MSLB-WERKS = EKPO-WERKS | ECC + S/4 |
| LFA1Vendor Master (General Section) | Vendor name | LFA1-LIFNR = EKKO-LIFNR | ECC + S/4 |
S/4HANA notes
- MSEG → MATDOC: In S/4HANA MATDOC replaces MSEG; reading MSEG works through a compatibility view but is slow at high volumes.
- MSLB → MATDOC: In S/4HANA special stock at vendor is no longer persisted in MSLB; it is calculated from MATDOC and the name MSLB is read through the compatibility view NSDM_V_MSLB. Reading code keeps working, but the table must not be written directly.
Selection screen parameters
| Parameter | Description | Type | Reference field | Required | Example |
|---|---|---|---|---|---|
| S_LIFNR | Subcontractor | Range / multiple | EKKO-LIFNR | No | 100733 |
| S_WERKS | Plant | Range / multiple | EKPO-WERKS | Yes | 1100 |
| S_EBELN | Purchase order | Range / multiple | EKPO-EBELN | No | 4500013320 |
| S_MATNR | Component material | Range / multiple | RESB-MATNR | No | RM-2040 |
| S_EINDT | Subcontracting delivery date | Range / multiple | EKET-EINDT | No | 01.09.2026 – 30.11.2026 |
| P_TOLPCT | Consumption variance tolerance (%) | Single value | — | No | 2 |
| P_OPEN | Only items not fully delivered | Checkbox | — | No | — |
| P_KEYDT | Key date for overdue check | Single value | SY-DATUM | Yes | 17.11.2026 |
Output columns
| # | Column | Source |
|---|---|---|
| 1 | Vendor | EKKO-LIFNR |
| 2 | Vendor name | LFA1-NAME1 |
| 3 | Purchase order | EKPO-EBELN |
| 4 | Item | EKPO-EBELP |
| 5 | Finished material | EKPO-MATNR |
| 6 | Component | RESB-MATNR |
| 7 | Order qty | EKPO-MENGE |
| 8 | Finished received | Calculated Σ EKBE-MENGE (VGABE = 1, reversals negative) |
| 9 | Delivery date | EKET-EINDT |
| 10 | Planned component | RESB-BDMNG |
| 11 | Expected consumption | Calculated RESB-BDMNG × finished received ÷ EKPO-MENGE |
| 12 | Actual consumption | Calculated Σ MSEG-MENGE (BWART 543, 544 negative) |
| 13 | Excess consumption | Calculated Actual − expected consumption |
| 14 | Unit | RESB-MEINS |
| 15 | Stock at vendor | MSLB-LBLAB |
| 16 | Status | Calculated Matched, excess consumption, under-consumption or delivery overdue |
Sample output
| Vendor | Vendor name | Purchase order | Item | Finished material | Component | Order qty | Finished received | Delivery date | Planned component | Expected consumption | Actual consumption | Excess consumption | Unit | Stock at vendor | Status |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 100733 | Kuzey Döküm | 4500013320 | 00010 | FG-5010 | RM-2040 | 1,000 | 800 | 11/05/2026 | 2,500 | 2,000 | 2,140 | 140 | KG | 360 | Excess consumption |
| 100733 | Kuzey Döküm | 4500013320 | 00010 | FG-5010 | CH-0315 | 1,000 | 800 | 11/05/2026 | 50 | 40 | 40 | 0 | KG | 10 | Matched |
| 100841 | Anadolu Kaplama | 4500013356 | 00020 | FG-6120 | PK-1180 | 600 | 0 | 10/28/2026 | 600 | 0 | 0 | 0 | PC | 600 | Delivery overdue |
How does the report work?
- EKKO and EKPO are read by vendor, plant and order number; only the subcontracting item category (EKPO-PSTYP = 3) and non-deleted items remain.
- Components are read from RESB by order item (RESB-EBELN, RESB-EBELP); deleted components (XLOEK) are excluded. The planned component quantity is RESB-BDMNG.
- The received finished quantity is summed net from EKBE (VGABE = 1). Actual consumption is summed from 543 movements in MSEG (544 reversals negative) by order item and component material.
- Expected consumption = RESB-BDMNG × received finished qty ÷ EKPO-MENGE; excess consumption = actual − expected. If the difference exceeds the tolerance percentage the line is flagged as excess, if it is below as under-consumption. If EKET-EINDT is before the key date and the finished goods have not fully arrived, the line counts as overdue.
- Stock at the vendor is added from MSLB per vendor and component (LBLAB + LBINS); the subtotal at vendor + component level gives the reconciliation of shipped, consumed and remaining quantities.
Performance notes
The number of subcontracting orders is usually limited; read RESB for the order list and MSEG for movement type 543 and the order list. For the yearly reconciliation, running in the background and exporting to Excel is enough.
Features
- ALV list (sort, filter, subtotals)
- User-specific layout variants
- Double-click drill-down to the document The order number opens ME23N, the actual consumption opens the 543 documents in MB51 and the stock at vendor opens MBLB.
- Export to Excel
- Runs as a background job
Authorization objects
- M_BEST_EKOPurchase order display authorization by purchasing organization
- M_BEST_WRKPurchase order display authorization by plant
- M_MSEG_WWAGoods movement authorization by plant
Frequently asked questions
Why does excess consumption occur?
The component consumption may have been increased by hand at the finished goods receipt, the vendor may have reported scrap or the component unit conversion may be wrong. The report shows the difference; the reason is clarified with the vendor and the subcontracting owner.
Why is the stock at the vendor not shown per order?
SAP keeps the special stock at the vendor (MSLB) at vendor, plant and material level, not per order. The report therefore shows the stock at the vendor in the component subtotal and gives the shipped, consumed and remaining reconciliation at that level.
Does the report work on S/4HANA?
Yes. Subcontracting orders, RESB and the order history keep the same structure in S/4HANA; the MSEG and MSLB reads work through compatibility views.
Related reports
Open Purchase Orders by Vendor Report
A custom ALV report that shows, per vendor, the quantity not yet received, the open order value and the days of delay since the delivery date in a …
Scrap and Yield Analysis by Work Center Report
A custom ALV report that totals yield, scrap and rework from production confirmations per work center and operation, and compares the actual scrap …
Let us build this report for your system
Briefly describe your system and expectations. We will clarify the scope and come back with an effort and price quote.