Validations

The validation function lets you check the values and value intervals entered in the SAP environment with the help of user-defined rules. If data is entered in the system, it is checked against the validation rules. If the data does not correspond to these rules, it may not be posted in certain circumstances,. Since the validation is carried out before posting, only checked data is accepted into in EC-EIS and EC-BP.

Validations are always valid for one aspect and are created in Customizing. How you maintain and copy validations is described in detail in Customizing.

If are you maintaining validations for the first time for an aspect, the system first generates the necessary environment.

The validations can be used in three places in EC-EIS and EC-BP.

  1. You can lay down rules for the manual entry of transaction data , which are checked before saving. This way you can avoid entering meaningless or incorrect data. (For general information on data entry, see Transaction Data ).

  2. As with the entry of transaction data, you can store rules for interactive planning that are checked before saving. (For general information on planning, see Business Planning ).

  3. Validation rules can also be stored for automatic data transfer . The received records are checked against these rules after the summarization but before posting. This way incorrect or meaningless data will not be transferred to EIS. (For general information on data transfer, see Data Transfer ).

Each validation consists of up to 999 steps. A check processes the steps one after the other. A validation step consists of the following components:

  • Prerequisite

    The entry values to be verified are selected using the prerequisite. If entry values are not selected for verification (if the prerequisite is not fulfilled), then the values are valid and the transaction will be carried out. In some cases, the use of a prerequisite is not necessary.

  • Check

    During the check, the values selected using the prerequisite are verified. If the check result is true (TRUE), the transaction is continued. If the check result is false (FALSE), a message is issued by the system.

  • Message

    If the prerequisite is fulfilled, but the check is not, the system issues a message.

Prerequisites and checks are defined with the help of Boolean logic. You can define simple logical statements, or you can use rules, user exits and sets in your logical formulas to define very complex statements. You can find further information about Boolean logic under Validations, Substitutions, and Rules .

There are four different types or importance levels of messages:

Type

Meaning

A

Termination

E

Error

W

Warning

I

Information

Messages of type A and E are genuine errors, which lead to the data not being updated. Messages of type W and I are only additional information which is logged, but the data is updated anyway.

Types of Validation

There are two different types of validation in EC-EIS and EC-BP.

  1. Single record validation

    Each new or changed data record is checked individually in single record validation. For example, a check can be made as to whether the sum of two key figures is lesser than or equal to a third key figure.

    Example Example

    If revenue is greater than zero, then it must be greater than the sum of the bonuses and sales commissions.

    You can find out how to define this validation under Example of Single Record Validation .

    End of the example.

  2. Matrix validation

    The data records are checked in their entirety with the matrix validation. For example, a check can be made, as to whether the sum of the assets equals the sum of the liabilities.

    Example Example

    The plan data for 1998 may not deviate from the actual data for 1997 by more than 20%.

    You can find out how to define this validation under Example of a Matrix Validation .

    End of the example.

Maintaining and copying rules and validations

You can store parts of validations which you use often or which you wish to use in several validations. You store them in rules and can use them repeatedly. You can also copy validations and rules. You can find further information on maintaining validations and rules in Customizing.

Activating validations

After you have created a validation, you must activate it for data entry, planning, or data transfer. For more information see Activating Validations for Data Entry and Planning and Activating Validations for Data Transfer .