Show TOC

  Checks

Use

Some of the checks for phase 1 take place when you call up the transaction, or automatically when you save. Other checks for phase 1 take place when you choose Interim Status with the quick info text Check Interim Status . The follows checks are available:

  • Consistency Check

  • General checks

Features

Consistency Check

During the consistency check of the target history, the system displays the errors and represents them using traffic lights:

  • If an event contains an error, it is displayed with a red traffic light.

  • If an error occurs when subordinate pieces of equipment inherit data, red traffic lights are displayed for all events (that is, the entire target history). When data is inherited in the hierarchy, it is not always possible to tell which event in the top-level piece of equipment caused an error in a subordinate piece of equipment.

  • During the consistency check of the target history, the system also checks if recursions occur in the hierarchy. Recursions are not permitted in the hierarchy; however, the system checks if recursions exist during the consistency check. It cannot check whether the recursions also occur in terms of time. The check may therefore report recursions that do not occur at all in a certain period of time.

    Example Example

    On February 1, the structure looks like this:

    Piece of equipment C is installed in piece of equipment B. Piece of equipment B is installed in piece of equipment A.

    On March 1, the structure looks like this:

    Piece of equipment B is installed in piece of equipment C. Piece of equipment C is installed in piece of equipment A.

    In terms of time, this is not a recursion. However, if one of these constellations is scheduled to occur directly after the other one, the system may identify this as a recursion and report an error.

    End of the example.
General Checks

  • If an event that contains no history-relevant changes is created in the target history, the system issues a warning. You can still create this event. It just means that the target history has more events than would usually be the case. Incorrect data records are not generated. The reason for this behavior is that the Customizing for the history update may have changed since the piece of equipment was created.

  • If a piece of equipment is to be installed at a functional location where you are permitted to install one piece of equipment only, the system checks if another piece of equipment is already installed at this functional location at the time of installation, or at a later point in time. If this is the case, the system issues a warning.

    You can, however, still install the piece of equipment at the functional location. But you must check if this is simply a temporary double installation, or if the installation is not permitted. For example, you can subsequently change the history of the other piece of equipment so that it is no longer installed at the functional location. The system cannot automatically determine which installation is correct.