Show TOC

Function documentationValidation Rule Setup Locate this document in the navigation structure


You can set up validation rules that prevent incorrect data records from being saved. In this context, the word incorrect refers to records that do not match the validation criteria within rules defined by system administrators.


  • Driver dimensions

    A driver dimension is the dimension in each application from which you create a validation rule. In most cases, the driver dimension is the Account dimension, but it can be any dimension. Only one driver dimension per application is possible.

  • You create validation rules at the dimension level, not at the application level. Therefore, you can use the same set of rules in multiple applications.

    Example Example

    For each application, you specify one dimension as the driver dimension, as illustrated in the following table:


    Driver Dimension







    Since rules are created at the dimension level, rules created for the ACCOUNT dimension apply to both applications, as shown in the following table:




    IntCo must have a trading partner


    Cannot post revenue to entities A, B, and C


    Cannot post revenue to periods X, Y, and Z

    End of the example.
  • All validation rule configuration is specific to an application set. In addition, an application set can be maintained by only one user at a time.


Creating Rules

To create a validation rule, use transaction UJ_VALIDATION within SAP GUI, then perform the following:

  1. Choose an application set ID.

  2. Choose Assign Driver Dimension and select a driver dimension for an application. If you leave a driver dimension empty, the system applies no validation rules to this application.

    Recommendation Recommendation

    Pressing F4 displays the dimensions assigned to the application.

    End of the recommendation.

    To then maintain the rule for the dimension, you can either choose Save Driver Dimension Settings and Rule Maintenance, or select an application ID and dimension row and choose Edit Rules.

    If you chose Rule Maintenance, select the driver dimension for which you want to maintain the rules. You can select any dimension available for the application set you have chosen.

  3. Choose Create Rule. The system automatically assigns a rule number. You can enter a description of the rule and assign the rule to one or more members.

  4. Choose whether to use the logic table or write a custom check as a BAdI, which is ABAP code for more complicated checks.

    If you choose to use the logic table, define one or more rows of validation logic that must be passed, and save the rule.

    Example Example

    Example 1

    You could set up a validation rule in which the driver dimension is Account and the assigned members are COMMISSION, HEADCOUNT or SALARIES. You can then enter validation logic of ENTITY = HR and INTCO = NON_INTERCO in the first two rows of the logic table. This validation rule indicates that the entity must be HR and the INTCO must be NON_INTERCO in order to save a record where the ACCOUNT dimension contains the member COMMISSION, HEADCOUNT or SALARIES.

    Example 2

    You could set up a validation rule with the description IntCo must have a trading partner in which the driver dimension is Account and the assigned member is ICSales. You can then enter INTCO = I_RESDEVUK, I_RESDEVUS in the first row of the logic table. This validation rule indicates that a record cannot be saved to ICSALES when INTCO is I_RESDEVUK or I_RESDEVUS.

    End of the example.

    If you choose Use BAdI Implementation, click the BAdi name provided to create the implementation.

    Note Note

    You must specify filter values to which your BAdI implementation applies. Also, you must define an implementing class that implements the specified interface.

    End of the note.

Maintaining Rules

When maintaining a rule, you can give it a text description.

You can assign a rule to multiple members.

You can use a range of members, which is useful for creating a rule that applies to all accounts or to a range of account numbers.

You can use members that do not exist yet, however you receive a warning.

Copying Rules

You can copy all validations from one application set to another.

If the Applications/Dimensions are different, the system copies only the matching entries. If the system cannot copy any entries, it displays a message.

If the target application set has customized validations defined for it, you can choose to override them or not.

Turning Validations On and Off

Turning validations on and off allows you to specify whether you want the rules that have been created to be obeyed. By default, all are turned off, so you must proactively turn on validations.

You can turn validations on and off by application and by the following modules:

  • Journals

  • Manual Planning, which is the Web and Microsoft Excel interfaces

  • Data Manager, including all Data Manager logic, K2 script logic, and parameter driven consolidations logic

Checking Validations

You can verify the accuracy of a validation rule by choosing Check Validations.

Additional Information

When you copy or delete an application set, all validations for the application set are copied or deleted.

When you copy or delete an application, the settings for turning validations on and off by module and the assignment of a driver dimension are copied or deleted.

All validation rule configurations can be transported.

When changes to a validation rule are made, the Last Changed By, Date, and Time are stored and are part of the Activity Audit module.

Authorization is controlled by access to the UJ_VALIDATION transaction.