...
General
In SAP a standards, the revision level is handled and valid across the company (client level).
As a consequence, plant data in a certain date validity range do not match precisely to the currently valid material revision , nevertheless they are used for the respective planton client. The requirement to handle a different revision in one plant towards the currently valid material revision and other plants can therefor 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 is are used, which does not match the state of 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 also supports the use of 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 are in a distinct 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 a analog client revision.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. Then it With this setting, the plant revision will be valid used for all plants handled by ProConfiguration.
...