# Weaving Loom Loading Plan Report by Width, Design and Warp Compatibility

> A custom ALV report that groups open weaving orders by loom width, fabric design and the warp they use, and proposes a sequence per loom that keeps warp changes to a minimum. Planners see on one screen which order can run on which loom, how many warp changes are needed and how many hours of work each loom is loaded with.

- Type: Report, Custom development, ALV report
- Module: PP
- Estimated effort: L (10–14 working days)
- Industry: Textile and Apparel
- Last updated: 2026-11-17
- URL: https://nekuhub.com/en/reports/weaving-loom-loading-plan-report/


## Why is the standard not enough?

The CM21 planning table dispatches orders to work centers by date and capacity, and CM01 shows the work center load; neither knows whether the fabric width fits the loom width or whether consecutive orders use the same warp. Setup-optimized sequencing can be done in PP/DS with setup matrices, but that needs its own implementation and maintenance. The custom report applies these compatibility rules from existing order, work center and classification data.

### Closest standard alternatives

- CM21: Dispatches orders to work centers by date and capacity; it does not check loom width or warp compatibility.
- CM01: Shows the work center capacity load per period; it does not propose an order sequence or warp changes.

## Tables used

| Table | Role | Access | Join | System |
|---|---|---|---|---|
| AFKO | Order header: basic dates, MRP controller, routing number (driving table) | Read | - | ECC + S/4 |
| AFPO | Order item: fabric, order quantity and unit | Read | AFPO-AUFNR = AFKO-AUFNR | ECC + S/4 |
| JEST | Order status: orders with TECO, DLV or deletion flag are excluded | Read | JEST-OBJNR = 'OR' + AFKO-AUFNR AND JEST-INACT = ' ' | ECC + S/4 |
| AFVC | Weaving operations and work center link | Read | AFVC-AUFPL = AFKO-AUFPL | ECC + S/4 |
| CRHD | Loom (work center) code | Read | CRHD-OBJID = AFVC-ARBID AND CRHD-OBJTY = 'A' | ECC + S/4 |
| KBED | Remaining capacity requirement of the operation | Read | KBED-AUFPL = AFVC-AUFPL AND KBED-APLZL = AFVC-APLZL | ECC + S/4 |
| RESB | Order components: warp material | Read | RESB-RSNUM = AFKO-RSNUM | ECC + S/4 |
| KSSK | Class assignment of the loom (class type 019) | Read | KSSK-KLART = '019' | ECC + S/4 |
| AUSP | Fabric width, design and loom reed width characteristic values | Read | AUSP-OBJEK = AFPO-MATNR AND AUSP-KLART = '001' | ECC + S/4 |
| MAKT | Fabric description | Read | MAKT-MATNR = AFPO-MATNR AND MAKT-SPRAS = SY-LANGU | ECC + S/4 |
| I_ManufacturingOrderOperation | In S/4HANA it can replace AFVC with a clean core approach | Read | ManufacturingOrder = AFKO-AUFNR | S/4HANA only |

## Selection screen parameters

| Parameter | Description | Type | Reference field | Required |
|---|---|---|---|---|
| S_WERKS | Plant | Range / multiple | AFPO-PWERK | Yes |
| S_ARBPL | Looms (work center) | Range / multiple | CRHD-ARBPL | Yes |
| S_DISPO | MRP controller | Range / multiple | AFKO-DISPO | No |
| S_GSTRP | Basic start date range | Range / multiple | AFKO-GSTRP | No |
| P_ATWID | Fabric greige width characteristic | Single value | CABN-ATNAM | Yes |
| P_ATDES | Design characteristic | Single value | CABN-ATNAM | No |
| P_ATLOM | Loom reed width characteristic | Single value | CABN-ATNAM | Yes |
| P_WARP | Warp material group | Single value | MARA-MATKL | Yes |

## Output columns

| Column | Source |
|---|---|
| Loom | CRHD-ARBPL |
| Reed width (cm) | Calculated: Reed width characteristic in work center classification (AUSP-ATFLV) |
| Proposed sequence | Calculated: Sequence number within the loom by warp, design and basic finish date |
| Production order | AFKO-AUFNR |
| Fabric | AFPO-MATNR |
| Fabric description | MAKT-MAKTX |
| Greige width (cm) | AUSP-ATFLV |
| Design | AUSP-ATWRT |
| Warp | RESB-MATNR |
| Order quantity | AFPO-PSMNG |
| Unit | AFPO-MEINS |
| Basic start | AFKO-GSTRP |
| Remaining load (hours) | Calculated: Σ KBED remaining capacity requirement, converted to hours |
| Warp change | Calculated: X if the warp differs from the previous order in the proposed sequence |
| Cumulative load % | Calculated: Σ remaining load / available hours in the planning horizon × 100 |
| Fit | Calculated: Fits / Width mismatch (greige width > reed width) |

## How does the report work?

1. Orders in the selected plant, MRP controller and basic start range are read from AFKO; via JEST only orders that are created or released and not technically completed remain.
2. Weaving operations are taken from AFVC and the work center (ARBID) is translated to the loom via CRHD. The remaining capacity requirement of the operation is totalled in hours from KBED.
3. The greige width and the design of the fabric are read via AUSP from characteristics in material classification (class type 001). The reed width of the loom comes from work center classification (class type 019) via KSSK and AUSP.
4. The warp of the order is the component in RESB that falls into the warp material group given on the selection screen.
5. Orders whose fabric width exceeds the loom width are flagged "Width mismatch". The remaining orders are sorted per loom first by warp, then by design, then by basic finish date; when the warp differs from the previous order a "Warp change" flag is set.
6. For each loom the cumulative load is compared with the available hours in the planning horizon; the summary line shows how many warp changes are saved against the current sequence. The report only proposes and does not change the orders.

## Authorization objects

- C_AFKO_AWK: Production order display authorization by order type and plant
- C_ARPL_WRK: Work center display authorization by plant

## Frequently asked questions

### Does the report assign orders to looms by itself?

No, it proposes. The planner applies the proposal in the planning table. If needed, the confirmed sequence can be transferred by an extra function that updates the work center and dates of the order operations; this adds 3–4 days to the estimate.

### What if the warp is not in the bill of material?

If the warp is not kept as a component, the warp properties of the fabric (such as yarn count and end count) are read from a material characteristic, and orders with the same value are treated as sharing a warp.

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

Yes. The tables are the same in S/4HANA; operations can be read via I_ManufacturingOrderOperation. In systems that use PP/DS, the report can also be used to try out compatibility rules before setup matrices are built.

---
Let us build this report for your system: https://nekuhub.com/en/request-a-quote/?report=textile-loom-loading-plan
