Master data validations are needed to ensure that incorrect combinations of records are prevented from being saved

to the BPC cubes. For example, if an account (ICSales) is supposed to be used with a specific trading partner, then we should make sure that this account cannot be used with other specific trading partners. To define validations in an application, we use the concept of driver dimensions. The driver dimension in an application is the dimension from which all the validations are created from. In most cases, the driver dimension is the ACCOUNT type dimension. The rules for the validations are created at the Dimension level, not at the application level. Therefore, the same rules are valid for multiple applications. The validations are maintained using tcode UJ_VALIDATION, using ABAP language. You can define one rule for multiple dimension members. For example, we can have a validation that says if ACCOUNT = ACC1, ACC2 AND ACC3, then ENTITY = ENT1. You can define multiple rules for one dimension member. For example, we can have two different validations as 1. if ACCOUNT = ACC1, then ENTITY = ENT1 2. if ACCOUNT = ACC1, then RPTCURRENCY = USD In such a scenario, both these validation rules must be fulfilled for the record to be accepted by the BPC system. You can maintain a validation rule by either using the logic table on the screen (tcode = UJ_VALIDATION) or write a BADI code in the enhancement spot BADI_UJ_VALIDATION_RULE_LOGIC.

If you are trying to save a record where the ACCOUNT dimension contains the member COMMISSION, HEADCOUNT or SALARIES, then on the same record, the ENTITY must be equal to HR AND the INTCO must be equal to NON_INTERCO. Validation rules can be copied from one Appset to another Appset. It is possible to turn on/off the validations by application and by modules such as JOURNALS, DATA MANAGER, AND MANUAL PLANNING (or BPC for Excel). In other words, we can set up validations for just one of these modules: JOURNALS, MANUAL PLANNING OR DATA MANAGER. By default, the data validations feature for all the modules is turned off. Note: Manual Planning means BPC for Excel and BPC Web input by users. Data Manager includes all Data Manager logic, K2 Script Logic, and Parameter Driven Logic (Consolidations). When copying an Appset, all the validations are also copied. Likewise, for deleting an Appset. Similarly, when copying an Application, all the validations are also copied (for whatever module they are configured: Journals, Manual Planning or Data Manager). Likewise for deleting an application.

All the validations can be transported from the development system to the production system. It is up to the client to make the decision as to where they want to configure the validations. Deleting the driver dimension will (obviously) delete all the validations created using that dimension as the driver dimension.