# Open Posting Change Notices Aging Report

> A custom ALV report that lists posting change notices (stock category, batch or material changes) not yet converted to transfer orders by age, next to the stock waiting in the posting change interim storage. Stock that quality has already released but still shows as blocked in the warehouse is found at a glance.

- Type: Report, Custom development, ALV report
- Module: WM
- Estimated effort: S (2–3 working days)
- Last updated: 2026-11-17
- URL: https://nekuhub.com/en/reports/open-posting-change-notices-aging-report/


## Why is the standard not enough?

LU04 shows open posting change notices as a worklist, but it does not give the number of days a notice has been waiting, the related material document and the stock left in the posting change interim storage (e.g. 922) together. Because usable stock stays in its old stock category in the warehouse, it cannot be picked, and the team usually notices only when an order gets stuck.

### Closest standard alternatives

- LU04: Shows open posting change notices as a worklist; no age and no stock in interim storage.
- LS24: Shows the quants of a material; does not say which quant belongs to a waiting notice.

## Tables used

| Table | Role | Access | Join | System |
|---|---|---|---|---|
| LUBU | Posting change notice: movement type, source and target material/plant, quantity, status, material document (driving table) | Read | - | ECC + S/4 |
| LQUA | Quants waiting in posting change interim storage and their dates | Read | LQUA-LGNUM = LUBU-LGNUM AND LQUA-MATNR = LUBU-MATN1 AND LQUA-WERKS = LUBU-WERK1 | ECC + S/4 |
| MAKT | Material description | Read | MAKT-MATNR = LUBU-MATN1 AND MAKT-SPRAS = SY-LANGU | ECC + S/4 |
| T333 | WM movement type settings: automatic transfer order and source/destination storage type | Read | T333-LGNUM = LUBU-LGNUM AND T333-BWLVS = LUBU-BWLVS | ECC + S/4 |

## Selection screen parameters

| Parameter | Description | Type | Reference field | Required |
|---|---|---|---|---|
| S_LGNUM | Warehouse number | Range / multiple | LUBU-LGNUM | Yes |
| S_BWLVS | WM movement type | Range / multiple | LUBU-BWLVS | No |
| S_MATNR | Material | Range / multiple | LUBU-MATN1 | No |
| S_WERKS | Plant | Range / multiple | LUBU-WERK1 | No |
| S_BDATU | Notice date | Range / multiple | LUBU-BDATU | No |
| P_IFTYP | Posting change interim storage type | Single value | LQUA-LGTYP | Yes |
| P_MINAGE | Minimum age (days) | Single value | - | No |

## Output columns

| Column | Source |
|---|---|
| Notice | LUBU-UBNUM |
| Movement type | LUBU-BWLVS |
| Material | LUBU-MATN1 |
| Description | MAKT-MAKTX |
| Plant | LUBU-WERK1 |
| Target material | LUBU-MATN2 |
| Notice qty | LUBU-MENGE |
| Open qty | Calculated: LUBU-MENGE − LUBU-TAMEN |
| Unit | LUBU-MEINS |
| Qty in interim | Calculated: Sum of LQUA-GESME in the interim storage type |
| Material doc. | LUBU-MBLNR |
| Notice date | LUBU-BDATU |
| Age (days) | Calculated: Key date − LUBU-BDATU |
| Created by | LUBU-BNAME |

## How does the report work?

1. Notices with status open or partially processed are read from LUBU for the selected warehouse number and movement types.
2. Open quantity = notice quantity (MENGE) − quantity already in transfer orders (TAMEN); lines with zero are skipped.
3. For the posting change interim storage type (from the selection screen, default 922), quants of the same material and plant are read from LQUA; the quantity in interim storage and the oldest quant date (WDATU) are added.
4. Age = key date − notice creation date (BDATU). If the target material (MATN2) differs from the source material, the line is flagged as a material change.
5. The material description is added from MAKT and the result is shown in ALV in descending order of age.

## Authorization objects

- L_LGNUM: Display authorization by warehouse number
- L_BWLVS: Authorization by WM movement type

## Frequently asked questions

### When is a posting change notice created?

When the stock category (for example from quality inspection to unrestricted), the batch or the material number changes in a storage location managed by WM, the MM posting opens a notice in WM. The quants keep their old status until the notice is processed with a transfer order.

### Does the report process the notices automatically?

No, the report only reads. You can jump from a line to LU04 to create the transfer order; automatic processing should be handled as a separate background job.

### Can interim storage types other than 922 be used?

Yes. The interim storage type is a selection-screen parameter, so a different value can be entered per warehouse number.

---
Let us build this report for your system: https://nekuhub.com/en/request-a-quote/?report=wm-open-posting-change-notices-aging
