Missing Production Versions Check Report for S/4HANA Migration
Short answer: 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.
- Estimated effort
- M · 4–6 working days
- System
- ECC and S/4HANA
- Tables
- 8
- Scope
- Global
- Built by
- NeKuDos Teknoloji
- Last updated
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.
Who uses it? PP consultants in an S/4HANA conversion project, master data teams and production planning leads.
Closest standard alternatives
Tables used
The tables the report reads and their join fields. ECC and S/4HANA differences are marked separately.
| Table | Role | Join | System |
|---|---|---|---|
| MARCPlant Data for Material | In-house produced materials, MRP controller (driving table) | — | ECC + S/4 |
| MARAGeneral Material Data | Material type and general deletion flag | MARA-MATNR = MARC-MATNR | ECC + S/4 |
| MASTMaterial to BOM Link | Material – BOM link and alternatives | MAST-MATNR = MARC-MATNR AND MAST-WERKS = MARC-WERKS | ECC + S/4 |
| STKOBOM Header | BOM header: status and deletion indicator | STKO-STLTY = 'M' AND STKO-STLNR = MAST-STLNR AND STKO-STLAL = MAST-STLAL | ECC + S/4 |
| MAPLAssignment of Task Lists to Materials | Material – routing link | MAPL-MATNR = MARC-MATNR AND MAPL-WERKS = MARC-WERKS | ECC + S/4 |
| PLKOTask List Header | Routing header: usage, status, deletion indicator | PLKO-PLNTY = MAPL-PLNTY AND PLKO-PLNNR = MAPL-PLNNR AND PLKO-PLNAL = MAPL-PLNAL | ECC + S/4 |
| MKALProduction Versions of Material | Production versions: validity, lock, BOM and routing | MKAL-MATNR = MARC-MATNR AND MKAL-WERKS = MARC-WERKS | ECC + S/4 |
| MAKTMaterial Descriptions | Material description | MAKT-MATNR = MARC-MATNR AND MAKT-SPRAS = SY-LANGU | ECC + S/4 |
Selection screen parameters
| Parameter | Description | Type | Reference field | Required | Example |
|---|---|---|---|---|---|
| S_WERKS | Plant | Range / multiple | MARC-WERKS | Yes | 1000 |
| S_MATNR | Material | Range / multiple | MARC-MATNR | No | FG-* |
| S_MTART | Material type | Range / multiple | MARA-MTART | No | FERT, HALB |
| S_DISPO | MRP controller | Range / multiple | MARC-DISPO | No | 001 |
| P_STLAN | BOM usage | Single value | MAST-STLAN | Yes | 1 |
| P_DATE | Key date | Single value | MKAL-ADATU | Yes | 17.11.2026 |
| P_GAPS | Only materials with findings | Checkbox | — | No | X |
Output columns
| # | Column | Source |
|---|---|---|
| 1 | Plant | MARC-WERKS |
| 2 | Material | MARC-MATNR |
| 3 | Description | MAKT-MAKTX |
| 4 | Material type | MARA-MTART |
| 5 | MRP controller | MARC-DISPO |
| 6 | Active BOM alternatives | Calculated Number of MAST lines with STKO-LOEKZ blank |
| 7 | Valid routings | Calculated Number of routing group/counters with PLKO-LOEKZ blank and released status |
| 8 | Valid versions | Calculated Number of MKAL lines with MKSP blank and ADATU ≤ key date ≤ BDATU |
| 9 | Version | MKAL-VERID |
| 10 | Version valid to | MKAL-BDATU |
| 11 | BOM alternative in version | MKAL-STLAL |
| 12 | Routing group in version | MKAL-PLNNR |
| 13 | Finding | Calculated Finding code V01–V06 with a short description |
| 14 | Proposed version | Calculated '0001 / alternative / routing group-counter' when there is one active alternative and one valid routing |
Sample output
| Plant | Material | Description | Material type | MRP controller | Active BOM alternatives | Valid routings | Valid versions | Version | Version valid to | BOM alternative in version | Routing group in version | Finding | Proposed version |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1000 | FG-5003 | Packed product C | FERT | 001 | 1 | 1 | 0 | V01 No production version | 0001 / 01 / 50000120-1 | ||||
| 1000 | FG-6100 | Panel cabinet 80 cm | FERT | 002 | 2 | 1 | 1 | 0001 | 12/31/9999 | 01 | 50000144 | V05 Alternative 02 not used by any version | |
| 1000 | SA-3100 | Body subassembly | HALB | 001 | 1 | 1 | 0 | 0001 | 12/31/2025 | 01 | 50000098 | V02 Only expired versions | |
| 2000 | FG-7200 | Compressor unit K2 | FERT | 010 | 1 | 0 | 1 | 0002 | 12/31/9999 | 01 | 50000210 | V04 Routing of the version is deleted |
How does the report work?
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
Performance notes
Read each table once with the plant and material list and match in internal tables; do not run a MAST/MAPL SELECT per material. For plants with tens of thousands of materials, run the report in the background and export the result as an upload template.
Features
- ALV list (sort, filter, subtotals)
- User-specific layout variants
- Double-click drill-down to the document The material opens C223 production version maintenance, the routing group opens CA03.
- Export to Excel Proposed versions can be exported in the layout of a mass upload template.
- Runs as a background job
Authorization objects
- M_MATE_WRKDisplay material data by plant
- C_STUE_WRKDisplay BOMs by plant
- C_ROUTDisplay 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.
Packages that include this solution
S/4HANA Conversion Readiness Pack
A five-component pack that finds the master data and finance inconsistencies to clean up before a system conversion from ECC to S/4HANA: business …
BOM, Routing and Production Version Pack
A five-component pack that loads, changes and audits production master data: mass routing creation from Excel, mass BOM component changes, an audit of …
Related reports
Multi-Level BOM Where-Used Report with Open Production Orders
A custom ALV report that shows in which assemblies and, at the top, in which finished goods one or more components are used, as a flat list that …
Orders Using Expired or Locked Production Versions Report
A custom ALV report that checks production versions against their validity dates, lock status and the validity of the BOM and routing they point to, …
Let us build this report for your system
Briefly describe your system and expectations. We will clarify the scope and come back with an effort and price quote.