# Missing Production Versions Check Report for S/4HANA Migration

> A custom ALV report that compares BOM alternatives, routings and production versions of in-house produced materials and lists, with a finding code, materials that have no version, only expired versions, versions pointing to a deleted BOM or routing, or alternatives that no version covers. For materials with one BOM and one routing the proposed version is shown on the line; the result can be downloaded as a mass upload template.

- Type: Report, Custom development, ALV report
- Module: PP
- Estimated effort: M (4–6 working days)
- Last updated: 2026-11-17
- URL: https://nekuhub.com/en/reports/missing-production-versions-s4hana-migration-check-report/


## Why is the standard not enough?

In S/4HANA, MRP and production orders select the BOM and routing only through the production version; in ECC many materials work with a selection method and have no version. C223 shows versions for maintenance per material, but does not answer 'BOM exists, routing exists, no valid version' or 'version points to a deleted routing' across a plant. The conversion tool SAP provides on the S/4HANA side creates missing versions, but does not give a finding list of the inconsistencies that should be cleaned in ECC before the conversion. The custom report performs this pre-check.

### Closest standard alternatives

- C223: Maintains production versions per material; does not list inconsistencies with BOMs and routings across a plant.
- CA03: Shows one routing; does not show whether a production version uses it.

## Tables used

| Table | Role | Access | Join | System |
|---|---|---|---|---|
| MARC | In-house produced materials, MRP controller (driving table) | Read | - | ECC + S/4 |
| MARA | Material type and general deletion flag | Read | MARA-MATNR = MARC-MATNR | ECC + S/4 |
| MAST | Material – BOM link and alternatives | Read | MAST-MATNR = MARC-MATNR AND MAST-WERKS = MARC-WERKS | ECC + S/4 |
| STKO | BOM header: status and deletion indicator | Read | STKO-STLTY = 'M' AND STKO-STLNR = MAST-STLNR AND STKO-STLAL = MAST-STLAL | ECC + S/4 |
| MAPL | Material – routing link | Read | MAPL-MATNR = MARC-MATNR AND MAPL-WERKS = MARC-WERKS | ECC + S/4 |
| PLKO | Routing header: usage, status, deletion indicator | Read | PLKO-PLNTY = MAPL-PLNTY AND PLKO-PLNNR = MAPL-PLNNR AND PLKO-PLNAL = MAPL-PLNAL | ECC + S/4 |
| MKAL | Production versions: validity, lock, BOM and routing | Read | MKAL-MATNR = MARC-MATNR AND MKAL-WERKS = MARC-WERKS | ECC + S/4 |
| MAKT | Material description | Read | MAKT-MATNR = MARC-MATNR AND MAKT-SPRAS = SY-LANGU | ECC + S/4 |

## Selection screen parameters

| Parameter | Description | Type | Reference field | Required |
|---|---|---|---|---|
| S_WERKS | Plant | Range / multiple | MARC-WERKS | Yes |
| S_MATNR | Material | Range / multiple | MARC-MATNR | No |
| S_MTART | Material type | Range / multiple | MARA-MTART | No |
| S_DISPO | MRP controller | Range / multiple | MARC-DISPO | No |
| P_STLAN | BOM usage | Single value | MAST-STLAN | Yes |
| P_DATE | Key date | Single value | MKAL-ADATU | Yes |
| P_GAPS | Only materials with findings | Checkbox | - | No |

## Output columns

| Column | Source |
|---|---|
| Plant | MARC-WERKS |
| Material | MARC-MATNR |
| Description | MAKT-MAKTX |
| Material type | MARA-MTART |
| MRP controller | MARC-DISPO |
| Active BOM alternatives | Calculated: Number of MAST lines with STKO-LOEKZ blank |
| Valid routings | Calculated: Number of routing group/counters with PLKO-LOEKZ blank and released status |
| Valid versions | Calculated: Number of MKAL lines with MKSP blank and ADATU ≤ key date ≤ BDATU |
| Version | MKAL-VERID |
| Version valid to | MKAL-BDATU |
| BOM alternative in version | MKAL-STLAL |
| Routing group in version | MKAL-PLNNR |
| Finding | Calculated: Finding code V01–V06 with a short description |
| Proposed version | Calculated: '0001 / alternative / routing group-counter' when there is one active alternative and one valid routing |

## How does the report work?

1. In-house produced materials (BESKZ = 'E' or 'X') without a deletion flag are read from MARC for the selected plants; MARA-MTART filters the material type.
2. MAST and STKO give the BOM alternatives for the selected usage (STLAN); alternatives with STKO-LOEKZ set are kept as 'deleted', and the number of active alternatives is counted.
3. Routing (PLNTY = 'N') and rate routing (PLNTY = 'R') groups are read from MAPL and PLKO; routings with PLKO-LOEKZ set or a PLKO-STATU that is not released are flagged.
4. The production versions of the material are read from MKAL; versions that are not locked (MKSP blank) and have ADATU ≤ key date ≤ BDATU count as valid.
5. Finding rules are applied: V01 no version, V02 only expired versions, V03 BOM alternative of the version missing or deleted, V04 routing of the version missing or deleted, V05 an active BOM alternative is not used by any version, V06 version without routing.
6. With exactly one active alternative and one valid routing, the proposed version (0001, alternative, routing group and counter) is written on the line; when 'only findings' is selected, materials without issues are hidden.

## Authorization objects

- M_MATE_WRK: Display material data by plant
- C_STUE_WRK: Display BOMs by plant
- C_ROUT: Display routings

## Frequently asked questions

### Why run it before S/4HANA?

In S/4HANA, MRP cannot create planned orders for materials without a production version, or selects the wrong BOM. Cleaning versions that point to deleted routings or have expired in ECC before the conversion prevents the conversion tool from creating wrong versions.

### Are the proposed versions created automatically?

The report only writes a proposal. After the proposals are exported to Excel and checked, they can be created with a separate upload program or standard tools; for materials with several alternatives the decision is left to the planner.

### Are rate routings and repetitive manufacturing considered?

Yes. Rate routings (PLNTY = 'R') are counted separately and versions needed for repetitive manufacturing are checked with the same rules; for repetitive manufacturing versions the finding line shows the related flag.

---
Let us build this report for your system: https://nekuhub.com/en/request-a-quote/?report=pp-production-version-readiness-s4
