Request
In SAP a revision is handled and valid across the client. As a consequence plant data in a certain date range do not match the currently valid material revision, nevertheless they are used for the respective plant. The requirement to handle a different revision in one plant towards the currently valid material revision and other plants can therefor not be fulfilled.
Conclusion
As a result, plant data is used, which does not match the state of 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 also supports plant revisions, which are handled on the client 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 have a distinct 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 a analog client revision.
In order to use option plant revision ProConfiguration LogisticExtension must be licensed and option Activation plant revision in the ProConfiguration basic settings must be activated. Then it will be valid 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.