Planning-Vers.-Depend. and Planning-Vers.-Independ. Master Data 
The following sections contain information on which master data is planning-version-dependent and which is planning-version-independent.
Global Product Master
The data in the global product master is independent of a planning version.
Location
By choosing a planning version and the change mode on the initial screen for location master data maintenance, you can process all fields that are dependent on the planning version.
For more information, see Displaying, Creating and Changing a Location.
Location Product
By choosing a planning version (via Extras ® Choose Planning Version) and choosing the change mode on the initial screen of the location-specific product master, you can process all fields that are dependent on the planning version.
If you did not choose a planning version on the initial screen, the values you specified in the planning-version-dependent fields will automatically be assigned to planning version 000 (this applies in any case to planning-version-independent fields).
If you change the planning-version-dependent data in the location product master without explicitly specifying a planning version, you will also change the planning-version-dependent values of version 000 and all versions for which no planning-version-dependent data has previously been defined.
Only the location products for which you have explicitly created planning-version-dependent data use separate data and not the planning-version-dependent data of planning version 000.
For more information, see Maintaining Location-Dependent Product Master Data.
Production Process Model (PPM)
Time-dependent parameters of a PPM are dependent on the planning version. You can define time-dependent parameters in the PPM for the following data:
· Scrap of an activity
· The duration of an activity defined at the mode
· The capacity requirement of an activity defined at the resource
· The material consumption defined at an alternative component
If you define one of these parameters dependent on time, you can specify a planning version for which this setting is valid.
· If you specify a planning version, the system only uses this setting for the specified planning version.
If you copy this planning version, the system also copies the time-dependent parameters. If you change the parameters in the original planning version later, this has no effect on the parameters of the copy.
· If you do not enter a planning version, the system uses this setting for all planning versions for which you have not defined any other time-dependent parameters. If you change this parameter, this also affects all planning versions for which you have not defined any individual settings.
If you copy a planning version for which no planning-version-dependent data and no time-dependent parameters have been defined, the copy also uses this information.
For more information, see PPM Plan.
Resource
All the data of a resource is dependent on the planning version. Specific data for the resource, such as the resource type, cannot be changed; some data can only be changed depending on the status of the activities scheduled on the resource.
If you assign a resource to a model, the system automatically assigns it to all planning versions of this model. If you create a new planning version for this model later, the system also automatically assigns the resource to the new planning version.
If you change the data for a resource, you only change it in the planning-version-specific copy; in other words, if necessary, you have to change the data in all planning-version-dependent copies of the resource.
On the initial screen of the master data for the resources, you can copy the resource data of all planning versions of a model via Tools ® Copy Resources.
Behavior of the planning-version-dependent resource master data when a planning version is copied
Source version | Copy |
Planning version 000 without separate planning-version-dependent data | Not possible |
Planning version 000 with separate planning-version-dependent data including capacity variant data; uses the data of the shift definition | Separate planning-version-dependent data, separate variant data; uses the data of the shift definition |
Planning version XYZ without separate, planning-version-dependent data | Not possible |
Planning version XYZ with separate planning-version-dependent data including capacity variant data; uses the data of the shift definition | Separate planning-version-dependent data, separate variant data; uses the data of the shift definition as in the source version |
For more information, see Creating and Changing Resources.
Quota Arrangement
All quota arrangements can be defined as dependent on the planning version. However, you can also define planning-version-independent quota arrangements. Planning-version-independent data is used in all quota arrangements for which there is no planning-version-dependent data.
If you wish to explicitly assign quota arrangement data to planning version 000, you must specify the planning version 000 while in quota arrangement maintenance mode (Master Data ® Quota Arrangementsfrom the SAP Easy Access screen). If you change this data, the change will have no effect on other planning versions.
If you copy a planning version for which no planning-version-dependent data has been defined, the copy contains no planning-version-dependent data and also uses the planning-version-independent data.
If you copy a planning version for which separate, planning-version-dependent data has been defined, this data is also copied. If you change the original version (after copying), this change has no effect on the data of the copy.
If you copy planning version 000, all planning-version-dependent data is copied at the same time. If you change the data in planning version 000, this change has no effect on the data of the copy.
Changes to the planning-version-independent quota arrangement data affect all planning versions for which no planning-version-dependent data has been defined.
For more information, see Validity of Quota Arrangements.
No comments:
Post a Comment