# Purchasing Contract Utilization and Remaining Balance Report

> A custom ALV report that lists, for quantity and value contracts, how much of the target quantity and value has been used by release orders, the remaining balance, the utilization percentage and the days until the contract ends. Purchasing sees contracts that need renewal or are about to be used up in time.

- Type: Report, Custom development, ALV report
- Module: MM
- Estimated effort: S (2–4 working days)
- Last updated: 2026-11-17
- URL: https://nekuhub.com/en/reports/purchasing-contract-utilization-remaining-balance-report/


## Why is the standard not enough?

ME3L lists contracts per vendor, and the release documentation is opened one contract item at a time in ME33K. The utilization percentage against target, the remaining balance and the days until expiry for all contracts are not in one list. Teams keep the renewal and renegotiation calendar in Excel.

### Closest standard alternatives

- ME3L: Lists contracts per vendor; no utilization percentage and no days to expiry.
- ME33K: Shows the release documentation of one contract; does not compare all contracts.

## Tables used

| Table | Role | Access | Join | System |
|---|---|---|---|---|
| EKKO | Contract header: vendor, validity dates and header target value (driving table) | Read | - | ECC + S/4 |
| EKPO | Contract item: material, target quantity and target value | Read | EKPO-EBELN = EKKO-EBELN | ECC + S/4 |
| EKAB | Release documentation: quantity and value of release orders | Read | EKAB-KONNR = EKPO-EBELN AND EKAB-KTPNR = EKPO-EBELP | ECC + S/4 |
| LFA1 | Vendor name | Read | LFA1-LIFNR = EKKO-LIFNR | ECC + S/4 |
| I_PurchaseContractItemAPI01 | In S/4HANA it can be read for contract items with a clean core approach | Read | PurchaseContract = EKKO-EBELN | S/4HANA only |

## Selection screen parameters

| Parameter | Description | Type | Reference field | Required |
|---|---|---|---|---|
| S_EKORG | Purchasing organization | Range / multiple | EKKO-EKORG | Yes |
| S_EKGRP | Purchasing group | Range / multiple | EKKO-EKGRP | No |
| S_LIFNR | Vendor | Range / multiple | EKKO-LIFNR | No |
| S_KONNR | Contract | Range / multiple | EKKO-EBELN | No |
| S_BSART | Contract type (MK quantity, WK value) | Range / multiple | EKKO-BSART | No |
| S_KDATE | Validity end date | Range / multiple | EKKO-KDATE | No |
| P_PCT | Utilization threshold for warning (%) | Single value | - | No |
| P_KEYDT | Key date | Single value | SY-DATUM | Yes |

## Output columns

| Column | Source |
|---|---|
| Contract | EKKO-EBELN |
| Item | EKPO-EBELP |
| Vendor | EKKO-LIFNR |
| Vendor name | LFA1-NAME1 |
| Material | EKPO-MATNR |
| Short text | EKPO-TXZ01 |
| Valid from | EKKO-KDATB |
| Valid to | EKKO-KDATE |
| Target qty | EKPO-KTMNG |
| Released qty | Calculated: Σ EKAB-MENGE |
| Remaining qty | Calculated: EKPO-KTMNG − released qty |
| Target value | EKPO-ZWERT |
| Released value | Calculated: Σ EKAB-NETWR |
| Utilization (%) | Calculated: Released ÷ target × 100 (value for value contracts, quantity for quantity contracts) |
| Currency | EKKO-WAERS |
| Days to expiry | Calculated: EKKO-KDATE − key date |

## How does the report work?

1. Contracts (BSTYP = K) are read from EKKO by purchasing organization, vendor and validity end (KDATE); deleted documents are skipped.
2. The target quantity (KTMNG) and item target value (ZWERT) are taken from the EKPO items; for value contracts the header target value EKKO-KTWRT is used.
3. Release documentation is summed from EKAB per contract and item (KONNR, KTPNR): released quantity (MENGE) and released value (NETWR).
4. Remaining quantity = KTMNG − released quantity; utilization percentage = released ÷ target × 100 (by value for value contracts).
5. Days to expiry = EKKO-KDATE − key date. Contracts above the utilization threshold or ending within the given number of days are flagged; the vendor name is added from LFA1.

## Authorization objects

- M_RAHM_BSA: Contract display authorization by document type
- M_RAHM_EKO: Contract display authorization by purchasing organization
- M_RAHM_EKG: Contract display authorization by purchasing group

## Frequently asked questions

### How are service items without a target shown?

For items without a target quantity, utilization is calculated by value. If the item target value is also empty, the header target value (EKKO-KTWRT) is used.

### Do deleted release orders affect the utilization?

EKAB tracks the release order items. Deleted release items are checked against EKPO-LOEKZ and removed from the total.

### Does this report work on S/4HANA?

Yes. EKKO, EKPO and EKAB are used in S/4HANA as well. Central contracts in S/4HANA are out of scope and are assessed separately.

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