Plant Revisions

General

In SAP standards, the revision level is handled across the company (client level).

As a consequence, plant data in a certain validity range do not match precisely to the material revision on client. The requirement to handle different revision levels and their assigned objects (e.g. documents, bill-of-materials, routings, plans) on plant level can therefore not be fulfilled.

Conclusion

As a result, plant data are used, which don’t match to the actual material revision. Management and usage of different material revisions per plant is not possible because of system restrictions in SAP standard.

Solution – Plant revisions in ProConfiguration

ProConfiguration supports the use of plant revisions, which are handled independent from the SAP standard revision.  Plant revisions and data packages are handled by separate processing scenarios and validities. However, plant revisions are independent from client revisions, but they are in a certain relation.

• Plant scenarios are related to plant revisions

• Introduction of a plant revision is only possible, if the current plant revision is lower than the client revision

• A plant revision can not be valid before the client revision

Benefit:
The plant revision allows to produce or purchase different configurations using one common material master

In order to use option plant revision, ProConfiguration LogisticExtension must be licensed and the option Activation plant revision in the ProConfiguration basic settings must be activated. With this setting, the plant revision will be used for all plants handled by ProConfiguration.

For program-technical access on validity and revision data of ProConfiguration objects (read or write) adequate of methods of class /PRONOVIA/CLA_OBJVAL_ROOT and its derivations should be used.