# Subcontracting Component Consumption and Stock at Vendor Reconciliation Report

> 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.

- Type: Report, Custom development, ALV report
- Module: MM
- Estimated effort: M (5–7 working days)
- Last updated: 2026-11-17
- URL: https://nekuhub.com/en/reports/subcontracting-component-consumption-and-stock-at-vendor-reconciliation-report/


## 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.

### Closest standard alternatives

- MBLB: Lists stock at the vendor; does not compare expected and actual consumption by order.
- MB51: Lists the 543 consumption documents; planned quantity and finished goods receipt are not on the same line.

## Tables used

| Table | Role | Access | Join | System |
|---|---|---|---|---|
| EKKO | Subcontracting order header: vendor (driving table) | Read | - | ECC + S/4 |
| EKPO | Subcontracting item: finished material, order quantity, item category | Read | EKPO-EBELN = EKKO-EBELN | ECC + S/4 |
| EKET | Subcontracting delivery date | Read | EKET-EBELN = EKPO-EBELN AND EKET-EBELP = EKPO-EBELP | ECC + S/4 |
| RESB | Subcontracting components: planned component quantity | Read | RESB-EBELN = EKPO-EBELN AND RESB-EBELP = EKPO-EBELP | ECC + S/4 |
| EKBE | Finished goods receipts | Read | EKBE-EBELN = EKPO-EBELN AND EKBE-EBELP = EKPO-EBELP | ECC + S/4 |
| MSEG | Component consumption movements (543/544) | Read | MSEG-EBELN = EKPO-EBELN AND MSEG-EBELP = EKPO-EBELP AND MSEG-MATNR = RESB-MATNR | ECC + S/4 |
| MSLB | Special stock at the vendor (SOBKZ = O) | Read | MSLB-LIFNR = EKKO-LIFNR AND MSLB-MATNR = RESB-MATNR AND MSLB-WERKS = EKPO-WERKS | ECC + S/4 |
| LFA1 | Vendor name | Read | LFA1-LIFNR = EKKO-LIFNR | ECC + S/4 |

## Selection screen parameters

| Parameter | Description | Type | Reference field | Required |
|---|---|---|---|---|
| S_LIFNR | Subcontractor | Range / multiple | EKKO-LIFNR | No |
| S_WERKS | Plant | Range / multiple | EKPO-WERKS | Yes |
| S_EBELN | Purchase order | Range / multiple | EKPO-EBELN | No |
| S_MATNR | Component material | Range / multiple | RESB-MATNR | No |
| S_EINDT | Subcontracting delivery date | Range / multiple | EKET-EINDT | No |
| P_TOLPCT | Consumption variance tolerance (%) | Single value | - | No |
| P_OPEN | Only items not fully delivered | Checkbox | - | No |
| P_KEYDT | Key date for overdue check | Single value | SY-DATUM | Yes |

## Output columns

| Column | Source |
|---|---|
| Vendor | EKKO-LIFNR |
| Vendor name | LFA1-NAME1 |
| Purchase order | EKPO-EBELN |
| Item | EKPO-EBELP |
| Finished material | EKPO-MATNR |
| Component | RESB-MATNR |
| Order qty | EKPO-MENGE |
| Finished received | Calculated: Σ EKBE-MENGE (VGABE = 1, reversals negative) |
| Delivery date | EKET-EINDT |
| Planned component | RESB-BDMNG |
| Expected consumption | Calculated: RESB-BDMNG × finished received ÷ EKPO-MENGE |
| Actual consumption | Calculated: Σ MSEG-MENGE (BWART 543, 544 negative) |
| Excess consumption | Calculated: Actual − expected consumption |
| Unit | RESB-MEINS |
| Stock at vendor | MSLB-LBLAB |
| Status | Calculated: Matched, excess consumption, under-consumption or delivery overdue |

## How does the report work?

1. EKKO and EKPO are read by vendor, plant and order number; only the subcontracting item category (EKPO-PSTYP = 3) and non-deleted items remain.
2. Components are read from RESB by order item (RESB-EBELN, RESB-EBELP); deleted components (XLOEK) are excluded. The planned component quantity is RESB-BDMNG.
3. 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.
4. 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.
5. 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.

## Authorization objects

- M_BEST_EKO: Purchase order display authorization by purchasing organization
- M_BEST_WRK: Purchase order display authorization by plant
- M_MSEG_WWA: Goods 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.

---
Let us build this report for your system: https://nekuhub.com/en/request-a-quote/?report=mm-subcontracting-component-reconciliation
