Show TOC

  Change Not Permitted

Use

With this function you can prohibit changes for identifiers and value assignment instances. To do this you must have assigned a status to the Change Not Permitted indicator in Customizing. For the specification data you want to protect, a status entry with the correct status must apply in the header data of the specification. As the default setting, the status Released prevents changes to related data, for example.

If you do not prevent changes, but want to warn the user against making changes, you can set this up in Customizing using the Warning If Changed indicator.

Prerequisites

You have assigned the Change Not Permitted indicator to the appropriate status in Customizing for Basic Data and Tools under Specify Statuses .

In the header data for the specification on the Status tab page you have defined for which usage and in which validity period the status should apply.

Note Note

You can specify a default setting for the status entries in the IMG activity Specify Value Assignment Types using the value assignment type ESTST. The system takes the default setting into account if no status entry exists for a specification.

End of the note.

So that a status entry is taken into account for specification data, the Active indicator must be set in the usage of the specification data.

Features

Check Process

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

  • The usage of the data record is active

  • A status entry is available for which the Change Not Permitted indicator is set in Customizing and that applies for the active usage

    For the status entry to apply, the following conditions must be met:

    • The rating of the status and specification data record must be the same.

    • The corresponding validity areas must have at least one country (or plant, or profit center, and so on) in common, that is their intersection must not be empty.

      Example Example

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

      Usage of value assignment instance V1: PUBLIC/REG_EU/Active

      As DE is included in REG_EU, the status entry applies. The value assignment instance V1 is therefore released and can no longer be changed.

      End of the example.
Result

If the conditions for a status entry that prohibits changes are fulfilled, the data record is not ready for input. For a value assignment instance, the data record also includes the data for source information and user-defined texts, and so on.

The usage of the data record can be edited, but only such that the number of released data records belonging to it does not change. This means that:

  • Active released usages cannot be changed.

  • New, inactive usages can be added. For example, additional validity areas can be created. The existing validity areas are protected from changes.

  • Not released or inactive usages can be deleted.

When you create a new data record or edit a data record for whose usage a status entry with the status Released applies, the Active indicator cannot be set. A data record cannot therefore be released 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 ( Change 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 after an authorized person has assigned a status to the status entry that does not prohibit changes, for example, the status In Process . In the status In Process , for example, you can activate the usage of the data record. The status of the status entry can then be set to Released again by an authorized person.

Note Note

If the conditions for a status entry that causes a warning are fulfilled ( Warning If Changed indicator set), you can decide yourself whether you want to edit it.

End of the note.

Example

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

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