cancel
Showing results for 
Search instead for 
Did you mean: 

How to update existing MIC without creating new Version?

Former Member
0 Kudos

Master Inspection characteristics have multiple Versions, I have to update each and every version, but it should not create new version. It has to be updated in the same version

Please Support on this requirement

Accepted Solutions (0)

Answers (1)

Answers (1)

AlbertSAP
Advisor
Advisor
0 Kudos

Hi Balaji,

the indicator which is responsible for the version handling of master inspection characteristics (MICs) can be found in the QM customizing on following path:
IMG
>Quality Management
>>Basic Settings
>>>Maintain Settings at Plant Level
-->select affected plant and goto Details

On tab 'Basic data' you can find indicator 'Master insp. characs with history'. This flag influences the version management for the MICs. F1 Help of this field explains what happens, if it is active (probably active in your scenario):

"Insp. Characteristics Are Maintained with History


Use
If you set this indicator, all released versions for the inspection characteristics are stored. If you access a released version using the function "Change inspection characteristic", the system creates a new version.

Dependencies
The system can manage different versions of master data records for inspection characteristics and inspection methods. The individual versions are clearly identified by a current version number that is assigned internally by the system. For each version, there is a date from which the data record is valid ( valid-from date). Several versions can be valid for the same key date.

If you first create a master record (function "Create inspection characteristic" or "Create inspection method"), you can either give it an alphanumeric or numerical key, or let the system assign a numerical key ( Number range definition). The system assigns this new master record version number 1. You must specify a valid-from date for this first version.

  1. You can create additional versions of the master record in the following ways.
    You use the function "Create version". You must specify a date from which the version is valid. This date must not be used in another version of the data record.
  2. You use the function "Change". You can choose and change a valid version for a key date.
    However, if this version is released and if history management is defined for inspection characteristics or inspection methods in the settings at plant level, the system then creates a new version with the same valid-from date. The original version is saved with no changes and can still be used."

This is how system handles the MIC versions depending on the MIC history indicator.


I wish you a nice day,

Albert