# Dye Lot (Shade) Consistency Check Report for Outbound Deliveries

> A custom ALV report that reads from batch classification which dye lot (shade) each fabric roll on an outbound delivery comes from, and flags sales order items that receive rolls from more than one dye lot. Shipping teams see mixed-shade deliveries before goods issue, swap the rolls, and returns caused by shade differences go down.

- Type: Report, Custom development, ALV report
- Module: SD
- Estimated effort: M (5–7 working days)
- Industry: Textile and Apparel
- Last updated: 2026-11-17
- URL: https://nekuhub.com/en/reports/delivery-dye-lot-shade-consistency-report/


## Why is the standard not enough?

Standard batch determination can propose batches with given characteristic values through a selection class, but it does not check whether rolls sent to the same order item in different deliveries come from the same dye lot, and it does not catch batches that were changed manually. VL06O shows deliveries and MSC3N shows the characteristics of one batch; no screen combines the two and lists mixed shades. The custom report joins delivery batches with the dye lot characteristic, compares them with shades already shipped and lists the deviations in one place.

### Closest standard alternatives

- VL06O: Lists deliveries by shipping point and date; it does not show the dye lot of the batches or check for mixed shades.
- MSC3N: Shows the characteristics of one batch; it does not compare them at delivery or order item level.

## Tables used

| Table | Role | Access | Join | System |
|---|---|---|---|---|
| LIKP | Delivery header: shipping point, planned goods issue, ship-to party (driving table) | Read | - | ECC + S/4 |
| LIPS | Delivery items: material, batch (roll), quantity and order reference | Read | LIPS-VBELN = LIKP-VBELN | ECC + S/4 |
| KNA1 | Customer name | Read | KNA1-KUNNR = LIKP-KUNNR | ECC + S/4 |
| INOB | Link between batch and classification object (class type 023) | Read | INOB-OBJEK = parti nesne anahtarı (malzeme + parti) AND INOB-KLART = '023' | ECC + S/4 |
| AUSP | Dye lot (shade) characteristic value | Read | AUSP-OBJEK = INOB-CUOBJ AND AUSP-ATINN = CABN-ATINN | ECC + S/4 |
| CABN | Translation of the characteristic name to its internal number | Read | CABN-ATNAM = P_ATNAM | ECC + S/4 |
| VBFA | Earlier deliveries for the same order item | Read | VBFA-VBELV = LIPS-VGBEL AND VBFA-POSNV = LIPS-VGPOS | ECC + S/4 |
| I_DeliveryDocumentItem | In S/4HANA it can replace LIPS with a clean core approach | Read | DeliveryDocument = LIPS-VBELN | S/4HANA only |

## Selection screen parameters

| Parameter | Description | Type | Reference field | Required |
|---|---|---|---|---|
| S_VSTEL | Shipping point | Range / multiple | LIKP-VSTEL | Yes |
| S_WADAT | Planned goods issue date | Range / multiple | LIKP-WADAT | No |
| S_KUNNR | Ship-to party | Range / multiple | LIKP-KUNNR | No |
| S_VBELN | Delivery | Range / multiple | LIKP-VBELN | No |
| P_ATNAM | Dye lot (shade) characteristic | Single value | CABN-ATNAM | Yes |
| P_GI | Also show deliveries with goods issue posted | Checkbox | - | No |
| P_DEV | Only lines with deviations | Checkbox | - | No |

## Output columns

| Column | Source |
|---|---|
| Delivery | LIKP-VBELN |
| Planned goods issue | LIKP-WADAT |
| Customer name | KNA1-NAME1 |
| Sales order | LIPS-VGBEL |
| Order item | LIPS-VGPOS |
| Material | LIPS-MATNR |
| Batch (roll no.) | LIPS-CHARG |
| Quantity | LIPS-LFIMG |
| Unit | LIPS-VRKME |
| Dye lot (shade) | AUSP-ATWRT |
| Dye lots in order item | Calculated: Number of distinct dye lot values across all delivery batches of the order item |
| Shade already shipped | Calculated: Dye lot values read from the batches of earlier deliveries in VBFA |
| Status | Calculated: Consistent / Mixed shades / No shade value |

## How does the report work?

1. LIKP is read by shipping point, planned goods issue date, delivery and ship-to party; depending on the selection, deliveries with goods issue already posted are included or left out.
2. Batch items are taken from LIPS. In deliveries with batch split, the sub-items are linked to the order reference (VGBEL, VGPOS) of their higher-level item.
3. For each batch the batch classification object (class type 023) is found in INOB; the dye lot characteristic given on the selection screen is converted to its internal number via CABN and its value is read from AUSP.
4. Earlier deliveries for the same order item are found via VBFA and the dye lots already shipped are collected.
5. The number of distinct dye lots per order item is calculated. If there is more than one, or the lot on the new delivery differs from what was already shipped, the line is flagged "Mixed shades"; if the characteristic is empty it is flagged "No shade value".
6. The ALV is sorted by shipping point and delivery; optionally only lines with deviations are shown.

## Authorization objects

- V_LIKP_VST: Delivery display authorization by shipping point
- C_TCLA_BKA: Authorization to read batch classification (class type 023)

## Frequently asked questions

### Which field holds the dye lot?

By default it is read from a characteristic in batch classification; the characteristic name is given on the selection screen. If the dye lot is kept in part of the batch number or in the vendor/manufacturer batch number, the report reads that field instead.

### Can goods issue be blocked for a mixed-shade delivery?

On its own the report only informs. The same check can be moved into an enhancement that runs when the delivery is saved and raises a warning or an error for mixed shades; this adds 2–3 days to the estimate.

### Does it work on S/4HANA?

Yes. LIKP, LIPS, VBFA and the batch classification tables are the same in S/4HANA. If clean core is preferred, delivery items can be read via I_DeliveryDocumentItem.

---
Let us build this report for your system: https://nekuhub.com/en/request-a-quote/?report=textile-dye-lot-shade-consistency
