# Released Purchase Requisitions Not Yet Converted to Purchase Orders Report

> A custom ALV report that lists released purchase requisition items not yet converted to a purchase order, with open quantity, open value and days waiting since release. It shows the workload per purchasing group and requisitions whose need date is close, on one screen.

- Type: Report, Custom development, ALV report
- Module: MM
- Estimated effort: S (2–3 working days)
- Last updated: 2026-11-17
- URL: https://nekuhub.com/en/reports/released-purchase-requisitions-not-converted-to-po-report/


## Why is the standard not enough?

ME5A lists open requisitions with their release status, but it does not show the days since release, the open value or the number of waiting requisitions per purchasing group. ME57 focuses on source assignment and gives no ageing. Managers process the list in Excel to see which group has kept how many requisitions waiting, and for how long.

### Closest standard alternatives

- ME5A: Lists open requisitions with release status; no days waiting and no workload summary per group.
- ME57: Assigns sources to requisitions and converts them; gives no ageing or management summary.

## Tables used

| Table | Role | Access | Join | System |
|---|---|---|---|---|
| EBAN | Requisition item: quantity, quantity ordered, release indicator and dates (driving table) | Read | - | ECC + S/4 |
| T024 | Purchasing group name and email address | Read | T024-EKGRP = EBAN-EKGRP | ECC + S/4 |
| MAKT | Material description (logon language) | Read | MAKT-MATNR = EBAN-MATNR AND MAKT-SPRAS = SY-LANGU | ECC + S/4 |
| I_PurchaseRequisitionItemAPI01 | In S/4HANA it can replace EBAN with a clean core approach | Read | PurchaseRequisition = EBAN-BANFN AND PurchaseRequisitionItem = EBAN-BNFPO | S/4HANA only |

## Selection screen parameters

| Parameter | Description | Type | Reference field | Required |
|---|---|---|---|---|
| S_WERKS | Plant | Range / multiple | EBAN-WERKS | Yes |
| S_EKGRP | Purchasing group | Range / multiple | EBAN-EKGRP | No |
| S_BSART | Requisition document type | Range / multiple | EBAN-BSART | No |
| S_AFNAM | Requisitioner | Range / multiple | EBAN-AFNAM | No |
| S_MATKL | Material group | Range / multiple | EBAN-MATKL | No |
| S_FRGDT | Release date range | Range / multiple | EBAN-FRGDT | No |
| P_MINAGE | Minimum days waiting | Single value | - | No |
| P_KEYDT | Key date (default: today) | Single value | SY-DATUM | Yes |

## Output columns

| Column | Source |
|---|---|
| Purchase requisition | EBAN-BANFN |
| Item | EBAN-BNFPO |
| Document type | EBAN-BSART |
| Purchasing group | EBAN-EKGRP |
| Group name | T024-EKNAM |
| Requisitioner | EBAN-AFNAM |
| Material | EBAN-MATNR |
| Short text | EBAN-TXZ01 |
| Plant | EBAN-WERKS |
| Open qty | Calculated: EBAN-MENGE − EBAN-BSMNG |
| Unit | EBAN-MEINS |
| Open value | Calculated: Open qty × EBAN-PREIS ÷ EBAN-PEINH |
| Currency | EBAN-WAERS |
| Release date | EBAN-FRGDT |
| Delivery date | EBAN-LFDAT |
| Days waiting | Calculated: Key date − EBAN-FRGDT (EBAN-BADAT if empty) |

## How does the report work?

1. EBAN is read with the selection criteria; deleted (LOEKZ) and closed (EBAKZ) items are skipped.
2. For items with a release strategy, only those whose release indicator (FRGKZ) allows conversion to a purchase order remain; the valid values are parameterized according to the customer's release strategy setup. Items without a release strategy are included directly.
3. Open quantity = requested quantity (MENGE) − quantity ordered (BSMNG); items with zero open quantity are skipped.
4. Open value = open quantity × valuation price (PREIS) ÷ price unit (PEINH).
5. Days waiting = key date − release date (FRGDT); if the release date is empty, the requisition date (BADAT) is used. The purchasing group name comes from T024, the material description from MAKT; the ALV shows count and value totals per purchasing group.

## Authorization objects

- M_BANF_WRK: Purchase requisition display authorization by plant
- M_BANF_EKG: Purchase requisition display authorization by purchasing group
- M_BANF_BSA: Purchase requisition display authorization by document type

## Frequently asked questions

### Do partly ordered requisitions appear in the list?

Yes. Because open quantity is EBAN-MENGE minus EBAN-BSMNG, partly ordered items are listed with the remaining quantity.

### How does it work for companies with different release strategies?

The release indicator values that count as convertible are stored in a parameter table during installation, so each company filters according to its own release strategy.

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

Yes. EBAN keeps the same structure in S/4HANA; flexible workflow approvals in Fiori fill the same release indicator. For clean core, I_PurchaseRequisitionItemAPI01 can be used.

---
Let us build this report for your system: https://nekuhub.com/en/request-a-quote/?report=mm-open-purchase-requisitions-aging
