Change Not Permitted

Use

You use this function to prohibit changes to identifiers and value assignment instances. To do this, you have to assign the Change Not Permitted indicator to a status in Customizing. In the header data of the specification, a status entry with the corresponding status must apply for the specification data to be protected. For example, by default, the status Released prohibits changes to related data.

If you do not want to prohibit changes, but want to warn the user about making changes, you can do this in Customizing by selecting the Warning if Changed indicator.

Prerequisites

You have assigned the Change Not Permitted indicator to the corresponding status under Define Status in Customizing for Basic Data and Tools.

On the Status tab page in the header data of the specification, you have defined the usage and validity period for the status.

Note Note

You can use value assignment type ESTST to define a default setting for the status entries in IMG activity Specify Value Assignment Types. The system will take this default setting into account when there is no status entry for a specification.

End of the note.

To ensure that a status entry is taken into account for specification data, the Active indicator must be set when using specification data.

Features

Checking Process

When a value assignment instance or identifier is called, the system checks for each day of the data validity interval

Whether data record usage is active

Whether a status entry exists for which the Change Not Permitted indicator has been set in Customizing and which applies to active usage

For the status entry to apply,

The status and specification data record must have the same rating

The related validity periods must have at least one country (or plant, profit center etc.) in common; in other words, must have an intersection with a value.

Example Example

Status entry: PUBLIC/DE/released (Change Not Permitted indicator set)

Usage of value assignment instance B1: PUBLIC/REG_EU/active

Since DE is contained in REG_EU, the status entry applies. Value assignment instance B1 is therefore released and can no longer be changed.

End of the example.
Result

If the conditions for a status entry are fulfilled, preventing changes, the data record is not ready for input. In the case of a value assignment instance, a data record also includes source information and user-defined text data, etc.

The usage of the data record can be edited, but only if the number of related released data records does not change. In view of this,

Active, released usages cannot be changed

New, non-active usages can be added Additional validity areas can be created. The existing validity areas are protected from changes.

Unreleased or inactive usages can be deleted

When creating or editing a data record, the Active indicator cannot be set if a status entry with the status Released applies for the usage. It is therefore not possible to release a data record by activating the usage.

Example Example

The identifier for a specification has the following usages:

PUBLIC / DE / inactive

PUBLIC / US / inactive

The specification has the following status entry

PUBLIC / REG_EU / released (Changes not permitted indicator set)

Since the usage and the status entry overlap in PUBLIC / DE (DE is a subset of REG_EU), the usage PUBLIC / DE for the identifier cannot be activated. The usage PUBLIC/US, however, may be activated.

End of the example.

A released data record can only be edited once a person with the necessary authorization has assigned a status to the status entry that does not prohibit changes, e.g. the status In Process. In status In Process, for example, you can activate the usage of the data record. The status of the status entry can then be set back to Released by an authorized person.

Note Note

If conditions for the triggering of a warning are met for a status entry (Warning if Changed indicator), you can decide to continue editing.

End of the note.

Example

The following example illustrates the system behavior if different validity sections exist for a value assignment instance or identifier. Since the system checks the validity interval of the data record every day, the Change Not Permitted indicator protects all versions of the value assignment instance or identifier.

In the following graphic, therefore, changes to data are not permitted for all active value assignment instances: