# Bins With Mixed Stock Not Allowed by the Storage Type Report

> A custom ALV report that lists, across whole storage types, bins holding more than one material, batch or quant against the storage type's mixed storage setting. The quants in every violating bin are shown with goods receipt date and quantity, so it is clear at once which stock has to be moved.

- Type: Report, Custom development, ALV report
- Module: WM
- Estimated effort: S (3–5 working days)
- Last updated: 2026-11-17
- URL: https://nekuhub.com/en/reports/storage-type-mixed-storage-violation-bin-report/


## Why is the standard not enough?

LS03N shows one bin at a time; LX03 gives bin status but does not compare it with the mixed storage rule. Violations created after the mixed storage setting is tightened, after manual transfer orders or after stock loads are noticed only when the wrong product is picked.

### Closest standard alternatives

- LS03N: Shows the content of one bin; gives no violation list across a storage type.
- LX03: Lists bin status and occupancy; does not compare it with the mixed storage rule.

## Tables used

| Table | Role | Access | Join | System |
|---|---|---|---|---|
| LQUA | Quants in bins: material, batch, quantity, goods receipt date (driving table) | Read | - | ECC + S/4 |
| T331 | Mixed storage setting of the storage type | Read | T331-LGNUM = LQUA-LGNUM AND T331-LGTYP = LQUA-LGTYP | ECC + S/4 |
| LAGP | Storage section, number of quants and blocks of the bin | Read | LAGP-LGNUM = LQUA-LGNUM AND LAGP-LGTYP = LQUA-LGTYP AND LAGP-LGPLA = LQUA-LGPLA | ECC + S/4 |
| MAKT | Material description in the logon language | Read | MAKT-MATNR = LQUA-MATNR AND MAKT-SPRAS = SY-LANGU | ECC + S/4 |

## Selection screen parameters

| Parameter | Description | Type | Reference field | Required |
|---|---|---|---|---|
| S_LGNUM | Warehouse number | Range / multiple | LQUA-LGNUM | Yes |
| S_LGTYP | Storage type | Range / multiple | LQUA-LGTYP | No |
| S_LGBER | Storage section | Range / multiple | LAGP-LGBER | No |
| S_MATNR | Material | Range / multiple | LQUA-MATNR | No |
| P_BATCH | Also check batch mixing | Checkbox | - | No |
| P_ONLYV | Show violating bins only | Checkbox | - | No |

## Output columns

| Column | Source |
|---|---|
| Storage type | LQUA-LGTYP |
| Mixed storage setting | T331-MISCH |
| Storage section | LAGP-LGBER |
| Storage bin | LQUA-LGPLA |
| Quants | Calculated: Number of LQUA records in the bin |
| Materials | Calculated: Number of distinct LQUA-MATNR values in the bin |
| Batches | Calculated: Number of distinct LQUA-CHARG values in the bin |
| Quant | LQUA-LQNUM |
| Material | LQUA-MATNR |
| Description | MAKT-MAKTX |
| Batch | LQUA-CHARG |
| Total stock | LQUA-GESME |
| Unit | LQUA-MEINS |
| GR date | LQUA-WDATU |
| Violation | Calculated: By the rule: more than one quant, more than one material or more than one batch |

## How does the report work?

1. The mixed storage setting (MISCH) is read from T331 for the selected warehouse number and storage types and translated into the rule allowed per bin: one quant, one material (several batches allowed) or freely mixed.
2. All quants in these storage types are read from LQUA, and the number of quants, materials and batches is counted per warehouse number + storage type + bin.
3. Bins whose counts break the rule are flagged as violations; with "Also check batch mixing" selected, batch mixing is reported as well.
4. The storage section and block indicators of violating bins come from LAGP, and the material description from MAKT.
5. The quants of each violating bin are listed on separate lines, with the first quant to enter the bin at the top.

## Authorization objects

- L_LGNUM: Display authorization by warehouse number and storage type

## Frequently asked questions

### Doesn't the system already prevent mixed storage?

It does for new putaways. But when the setting is changed later, existing bins are not checked, and initial stock loads and some manual movements can leave violations. The report shows this accumulated state.

### How is a violating bin fixed?

The list is the starting point for a transfer order that moves the newest quant to another bin. If needed, a button can be added that creates a move transfer order, like LT01, for the selected quants; this increases the effort range.

### Does it work for storage types with storage unit management?

Yes. The storage unit number of the quants (LQUA-LENUM) can be shown as well; batch mixing on a pallet and batch mixing in a bin are evaluated separately.

---
Let us build this report for your system: https://nekuhub.com/en/request-a-quote/?report=wm-mixed-storage-violations
