PP Report Custom development ALV report

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

  • C223 Maintain Production Versions. Maintains production versions per material; does not list inconsistencies with BOMs and routings across a plant.
  • CA03 Display Routing. Shows one routing; does not show whether a production version uses it.

Tables used

The tables the report reads and their join fields. ECC and S/4HANA differences are marked separately.

TableRoleJoinSystem
MARCPlant Data for MaterialIn-house produced materials, MRP controller (driving table)—ECC + S/4
MARAGeneral Material DataMaterial type and general deletion flagMARA-MATNR = MARC-MATNRECC + S/4
MASTMaterial to BOM LinkMaterial – BOM link and alternativesMAST-MATNR = MARC-MATNR AND MAST-WERKS = MARC-WERKSECC + S/4
STKOBOM HeaderBOM header: status and deletion indicatorSTKO-STLTY = 'M' AND STKO-STLNR = MAST-STLNR AND STKO-STLAL = MAST-STLALECC + S/4
MAPLAssignment of Task Lists to MaterialsMaterial – routing linkMAPL-MATNR = MARC-MATNR AND MAPL-WERKS = MARC-WERKSECC + S/4
PLKOTask List HeaderRouting header: usage, status, deletion indicatorPLKO-PLNTY = MAPL-PLNTY AND PLKO-PLNNR = MAPL-PLNNR AND PLKO-PLNAL = MAPL-PLNALECC + S/4
MKALProduction Versions of MaterialProduction versions: validity, lock, BOM and routingMKAL-MATNR = MARC-MATNR AND MKAL-WERKS = MARC-WERKSECC + S/4
MAKTMaterial DescriptionsMaterial descriptionMAKT-MATNR = MARC-MATNR AND MAKT-SPRAS = SY-LANGUECC + S/4

Selection screen parameters

ParameterDescriptionTypeReference fieldRequiredExample
S_WERKSPlantRange / multipleMARC-WERKSYes1000
S_MATNRMaterialRange / multipleMARC-MATNRNoFG-*
S_MTARTMaterial typeRange / multipleMARA-MTARTNoFERT, HALB
S_DISPOMRP controllerRange / multipleMARC-DISPONo001
P_STLANBOM usageSingle valueMAST-STLANYes1
P_DATEKey dateSingle valueMKAL-ADATUYes17.11.2026
P_GAPSOnly materials with findingsCheckbox—NoX

Output columns

#ColumnSource
1PlantMARC-WERKS
2MaterialMARC-MATNR
3DescriptionMAKT-MAKTX
4Material typeMARA-MTART
5MRP controllerMARC-DISPO
6Active BOM alternativesCalculated Number of MAST lines with STKO-LOEKZ blank
7Valid routingsCalculated Number of routing group/counters with PLKO-LOEKZ blank and released status
8Valid versionsCalculated Number of MKAL lines with MKSP blank and ADATU ≤ key date ≤ BDATU
9VersionMKAL-VERID
10Version valid toMKAL-BDATU
11BOM alternative in versionMKAL-STLAL
12Routing group in versionMKAL-PLNNR
13FindingCalculated Finding code V01–V06 with a short description
14Proposed versionCalculated '0001 / alternative / routing group-counter' when there is one active alternative and one valid routing

Sample output

PlantMaterialDescriptionMaterial typeMRP controllerActive BOM alternativesValid routingsValid versionsVersionVersion valid toBOM alternative in versionRouting group in versionFindingProposed version
1000FG-5003Packed product CFERT001110V01 No production version0001 / 01 / 50000120-1
1000FG-6100Panel cabinet 80 cmFERT002211000112/31/99990150000144V05 Alternative 02 not used by any version
1000SA-3100Body subassemblyHALB001110000112/31/20250150000098V02 Only expired versions
2000FG-7200Compressor unit K2FERT010101000212/31/99990150000210V04 Routing of the version is deleted
A view built with fictional sample data; not real system data.

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.

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

CA Package Custom

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 …

5 components · v1.0

PP Package Custom

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 …

5 components · v1.0

Related reports

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.

Related report: Missing Production Versions Check Report for S/4HANA Migration