- SAP Managed Tags:
As I already explained in my previous blog MRP: Simplification on S/4HANA, a new logic called Simplified Sourcing was implemented for the source determination. When we talk about the source of determination for internal procurement, the major change was that the production version is now mandatory for the correct BOM explosion during the MRP run.
Since the release of S/4HANA, SAP provided the report CS_BOM_PRODVER_MIGRATION, which allowed customers to automatically generate the missing production versions during a migration to S/4HANA, or even on a new implementation. The problem was that the report would generate a valid production version for each Bill of Material, but it would not consider the routings. That means, we would a production version created without any reference to the routing, which would cause problems during the MRP lead-time scheduling.
However, a solution for this issue was provided with the following SAP Note:
2463759 - Migration Report CS_BOM_PRODVER_MIGRATION does not consider routings
This note introduces the new report CS_BOM_PRODVER_MIGRATION02, which can generate production versions for all the valid combinations of BOMs and routings in S/4 HANA. The following picture shows the selection screen of the new report.
The report provides the following options to limit the number of production versions that will be generated:
1 - Only PV with routing: Production versions will not be generated if there is no routing for a specific material.
2 - Only same alternatives: A production version will be only generated if the BOM alternative matches with the routing group counter.
3 - Based on production orders: A production version will be only generated for BOMs/routings that were actually used on production orders.
4 - Also unchanged PVs: The report also shows existing production versions that were not changed.
Just like the previous report, we can select if the report will be executed in simulation mode (without changes to the database) or in actual mode, where the production versions will be generated.
In the screenshot below we can see the results after the report execution, where the missing production versions were proposed. We can see, for example, that two different production versions will be created for material S4HANA_FERT_004, since there are two different BOM alternatives.
We can now select which production versions will be created by using the Approve or Approve Selected button.
Since the release of S/4HANA, SAP provided the report CS_BOM_PRODVER_MIGRATION, which allowed customers to automatically generate the missing production versions during a migration to S/4HANA, or even on a new implementation. The problem was that the report would generate a valid production version for each Bill of Material, but it would not consider the routings. That means, we would a production version created without any reference to the routing, which would cause problems during the MRP lead-time scheduling.
However, a solution for this issue was provided with the following SAP Note:
2463759 - Migration Report CS_BOM_PRODVER_MIGRATION does not consider routings
This note introduces the new report CS_BOM_PRODVER_MIGRATION02, which can generate production versions for all the valid combinations of BOMs and routings in S/4 HANA. The following picture shows the selection screen of the new report.
The report provides the following options to limit the number of production versions that will be generated:
1 - Only PV with routing: Production versions will not be generated if there is no routing for a specific material.
2 - Only same alternatives: A production version will be only generated if the BOM alternative matches with the routing group counter.
3 - Based on production orders: A production version will be only generated for BOMs/routings that were actually used on production orders.
4 - Also unchanged PVs: The report also shows existing production versions that were not changed.
Just like the previous report, we can select if the report will be executed in simulation mode (without changes to the database) or in actual mode, where the production versions will be generated.
In the screenshot below we can see the results after the report execution, where the missing production versions were proposed. We can see, for example, that two different production versions will be created for material S4HANA_FERT_004, since there are two different BOM alternatives.
We can now select which production versions will be created by using the Approve or Approve Selected button.
9 Comments
