Purchasing Contract Utilization and Remaining Balance Report
Short answer: 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.
- Estimated effort
- S · 2–4 working days
- System
- ECC and S/4HANA
- Tables
- 5
- Scope
- Global
- Built by
- NeKuDos Teknoloji
- Last updated
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.
Who uses it? Purchasing managers, category managers and contract management 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 | Contract header: vendor, validity dates and header target value (driving table) | — | ECC + S/4 |
| EKPOPurchasing Document Item | Contract item: material, target quantity and target value | EKPO-EBELN = EKKO-EBELN | ECC + S/4 |
| EKABRelease Documentation | Release documentation: quantity and value of release orders | EKAB-KONNR = EKPO-EBELN AND EKAB-KTPNR = EKPO-EBELP | ECC + S/4 |
| LFA1Vendor Master (General Section) | Vendor name | LFA1-LIFNR = EKKO-LIFNR | ECC + S/4 |
| I_PurchaseContractItemAPI01Purchase Contract Item (API) | In S/4HANA it can be read for contract items with a clean core approach | PurchaseContract = EKKO-EBELN | S/4HANA only |
Selection screen parameters
| Parameter | Description | Type | Reference field | Required | Example |
|---|---|---|---|---|---|
| S_EKORG | Purchasing organization | Range / multiple | EKKO-EKORG | Yes | 1000 |
| S_EKGRP | Purchasing group | Range / multiple | EKKO-EKGRP | No | 001 |
| S_LIFNR | Vendor | Range / multiple | EKKO-LIFNR | No | 100245 |
| S_KONNR | Contract | Range / multiple | EKKO-EBELN | No | 4600000210 |
| S_BSART | Contract type (MK quantity, WK value) | Range / multiple | EKKO-BSART | No | MK |
| S_KDATE | Validity end date | Range / multiple | EKKO-KDATE | No | 01.11.2026 – 31.03.2027 |
| P_PCT | Utilization threshold for warning (%) | Single value | — | No | 80 |
| P_KEYDT | Key date | Single value | SY-DATUM | Yes | 17.11.2026 |
Output columns
| # | Column | Source |
|---|---|---|
| 1 | Contract | EKKO-EBELN |
| 2 | Item | EKPO-EBELP |
| 3 | Vendor | EKKO-LIFNR |
| 4 | Vendor name | LFA1-NAME1 |
| 5 | Material | EKPO-MATNR |
| 6 | Short text | EKPO-TXZ01 |
| 7 | Valid from | EKKO-KDATB |
| 8 | Valid to | EKKO-KDATE |
| 9 | Target qty | EKPO-KTMNG |
| 10 | Released qty | Calculated Σ EKAB-MENGE |
| 11 | Remaining qty | Calculated EKPO-KTMNG − released qty |
| 12 | Target value | EKPO-ZWERT |
| 13 | Released value | Calculated Σ EKAB-NETWR |
| 14 | Utilization (%) | Calculated Released ÷ target × 100 (value for value contracts, quantity for quantity contracts) |
| 15 | Currency | EKKO-WAERS |
| 16 | Days to expiry | Calculated EKKO-KDATE − key date |
Sample output
| Contract | Item | Vendor | Vendor name | Material | Short text | Valid from | Valid to | Target qty | Released qty | Remaining qty | Target value | Released value | Utilization (%) | Currency | Days to expiry |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 4600000210 | 00010 | 100245 | Atlas Ambalaj | RM-1001 | Carton box 40x30 | 01/01/2026 | 12/31/2026 | 120,000 | 103,500 | 16,500 | 204,000 | 175,950 | 86.30 | TRY | 44 |
| 4600000224 | 00010 | 100387 | Delta Metal | RM-2040 | Steel sheet 2 mm | 03/01/2026 | 02/28/2027 | 60,000 | 21,000 | 39,000 | 3,672,000 | 1,285,200 | 35 | TRY | 103 |
| 4600000231 | 00010 | 100700 | Kuzey Lojistik | Domestic freight service | 01/01/2026 | 12/31/2026 | 0 | 0 | 0 | 2,500,000 | 2,310,000 | 92.40 | TRY | 44 | |
| 4600000245 | 00020 | 100512 | Ege Kimya | RM-3105 | Solvent-based paint | 06/01/2026 | 11/30/2026 | 8,000 | 7,400 | 600 | 63,000 | 58,275 | 92.50 | TRY | 13 |
How does the report work?
- Contracts (BSTYP = K) are read from EKKO by purchasing organization, vendor and validity end (KDATE); deleted documents are skipped.
- 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.
- Release documentation is summed from EKAB per contract and item (KONNR, KTPNR): released quantity (MENGE) and released value (NETWR).
- Remaining quantity = KTMNG − released quantity; utilization percentage = released ÷ target × 100 (by value for value contracts).
- 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.
Performance notes
The number of contracts is usually small; take the EKAB totals for the contract list in a single SQL with GROUP BY KONNR, KTPNR. The report runs online; a background job with email can be used for monthly renewal tracking.
Features
- ALV list (sort, filter, subtotals)
- User-specific layout variants
- Double-click drill-down to the document Double-clicking the contract opens ME33K; clicking the released quantity shows the release orders.
- Export to Excel
- Runs as a background job
- Send the result by email Contracts close to expiry or above the threshold can be sent monthly.
Authorization objects
- M_RAHM_BSAContract display authorization by document type
- M_RAHM_EKOContract display authorization by purchasing organization
- M_RAHM_EKGContract 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.
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 …
Mass Purchase Order Creation from Excel Program
A custom program that creates purchase orders in bulk from Excel or CSV rows, grouping them by vendor, purchasing organization and group number. It …
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.