SAP Message RSCV056 - Consistency of time dimension of InfoCube &1

Description
This test checks whether or not the time characteristics of the InfoCubeused in the time dimension are consistent. The consistency of timecharacteristics is extremely important for non-cumulative Cubes andpartitioned InfoCubes.
Values that do not fit together in the time dimension of an InfoCuberesult in incorrect results for non-cumulative cubes and InfoCubes thatare partitioned according to time characteristics.
For InfoCubes that have been partitioned according to timecharacteristics, conditions for the partitioning characteristic arederived from restrictions for the time characteristic.

Errors
When an error arises the InfoCube is marked as a Cube with annon-consistent time dimension. This has the following consequences:

  • The derivation of conditions for partitioning criteria is deactivated on
    • account of the non-fitting time characteristics. This usually has anegative effect on performance.
    When the InfoCube contains non-cumulatives, the system generates awarning for each query indicating that the displayed data may beincorrect.

    Repair Options

    Caution

    • No action is required if the InfoCube does not contain non-cumulatives
      • or is not partitioned.
      • If the Infocube is partitioned, an action is only required if the read
        • performance has gotten worse.
        You cannot automatically repair the entries of the time dimension table.However, you are able to delete entries that are no longer in use fromthe time dimension table.
        The system displays whether the incorrect dimension entries are stillbeing used in the fact table.
        • If these entries are no longer being used, you can carry out an
          • automatic repair. In this case, all time dimension entries not beingused in the fact table are removed.
          After the repair, the system checks whether or not the dimension iscorrect. If the time dimension is correct again, the InfoCube is markedas an InfoCube with a correct time dimension once again.
          • If the entries are still being used, use transaction Listcube to check
            • which data packages are affected. You may be able to delete the datapackages and then use the repair to remove the time dimension entries nolonger being used. You can then reload the deleted data packages.Otherwise the InfoCube has to be built again.