How-to GuideSAP FPM

How To…Set upConsolidationEnvironmentusing BPC 7.0for NetWeaver

Applicable Releases:SAP BPC 7.0 NetWeaver Based VersionLast Updated: September 2008Version: 1.0

© Copyright 2007 SAP AG. All rights reserved.

No part of this publication may be reproduced ortransmitted in any form or for any purpose without theexpress permission of SAP AG. The informationcontained herein may be changed without prior notice.

Some software products marketed by SAP AG and itsdistributors contain proprietary software components ofother software vendors.

Microsoft, Windows, Outlook,and PowerPointareregistered trademarks of Microsoft Corporation.

IBM, DB2, DB2 Universal Database, OS/2, ParallelSysplex, MVS/ESA, AIX, S/390, AS/400, OS/390, OS/400,iSeries, pSeries, xSeries, zSeries, z/OS, AFP, IntelligentMiner, WebSphere, Netfinity, Tivoli, and Informix aretrademarks or registered trademarks of IBM Corporationin the United States and/or other countries.

Oracle is a registered trademark of Oracle Corporation.

UNIX, X/Open, OSF/1, and Motif are registeredtrademarks of the Open Group.

Citrix, ICA, Program Neighborhood, MetaFrame,WinFrame, VideoFrame, and MultiWin are trademarksor registered trademarks of Citrix Systems, Inc.

HTML, XML, XHTML and W3C are trademarks orregistered trademarks of W3C®, World Wide WebConsortium, Massachusetts Institute of Technology.

Java is a registered trademark of Sun Microsystems, Inc.

JavaScript is a registered trademark of Sun Microsystems,Inc., used under license for technology invented andimplemented by Netscape.

MaxDB is a trademark of MySQL AB, Sweden.

SAP, R/3, mySAP, mySAP.com, xApps, xApp, and otherSAP products and services mentioned herein as well astheir respective logos are trademarks or registeredtrademarks of SAP AG in Germany and in several othercountries all over the world. All other product andservice names mentioned are the trademarks of theirrespective companies. Data

contained in this document serves informationalpurposes only. National product specifications may vary.

These materials are subject to change without notice.These materials are provided by SAP AG and its affiliatedcompanies ("SAP Group") for informational purposesonly, without representation or warranty of anykind, and SAP Group shall not be liable for errors oromissions with respect to the materials. The onlywarranties for SAP Group products and services are thosethat are set forth in the express warranty statementsaccompanying such products and services, if any.Nothing herein should be construed as constituting anadditional warranty.

These materials are provided “as is” without a warrantyof any kind, either express or implied, including but notlimited to, the implied warranties of merchantability,fitness for a particular purpose, or non-infringement.SAP shall not be liable for damages of any kind includingwithout limitation direct, special, indirect, orconsequential damages that may result from the use ofthese materials.SAP does not warrant the accuracy or completeness ofthe information, text, graphics, links or other itemscontained within these materials. SAP has no controlover the information that you may access through theuse of hot links contained in these materials and does notendorse your use of third party web pages nor provideany warranty whatsoever relating to third party webpages.SAP CPM “How-to” Guides are intended to simplify theproduct implementation. While specific product featuresand procedures typically are explained in a practicalbusiness context, it is not implied that those features andprocedures are the only approach in solving a specificbusiness problem using SAP. Should you wish to receiveadditional information, clarification or support, pleaserefer to SAP Consulting.Any software coding and/or code lines / strings (“Code”)included in this documentation are only examples andare not intended to be used in a productive systemenvironment. The Code is only intended better explainand visualize the syntax and phrasing rules of certaincoding. SAP does not warrant the correctness andcompleteness of the Code given herein, and SAP shallnot be liable for errors or damages caused by the usage ofthe Code, except if such damages were caused by SAPintentionally or grossly negligent.

1 ScenarioThis document describes how to set up business consolidation environment with BPC7.0NetWeaver BI based version.

An ApShell (starting and example AppSet provided) in BPC7 NW initial release wouldnot contain any consolidation application, the strategy is to keep ApShell straight andreflect the baseline requirement for customer to start new implementation and ensurethere is nothing that will have to be re-engineered that is related to the customer’smaster/meta data, on the other hand, need minimize the “taken off” work on ApShell atcustomers. In this case, the document is intended for consultants or administrators thatunderstand the basic elements need to be set up in the Application in order to makeconsolidation engine work. It also tries to provide fairly detailed procedures to set up allthe elements composing the consolidation module as a referenced document to themanual. But we do not try to explain here for the consolidation rules that can be definedwith BPC consolidation engine and especially leaving the accounting principles such asIFRS, USGAAP building likely to the experts in COE team probably with the coming BPCStart Kits.

2 Prerequisites Successful installation of BPC7.0 NW ABAP server, .Net server and client

Completion of ApShell content activation

3 IntroductionFollowing steps outlines how consolidation environment should be set,

1) Consolidation (Legal) AppSet creation/Parameters setting

2) Master Data (Dimensions) Set-up

3) Application creation/Parameters setting

4) Table Driven ABAP Program Maintaining (Data Manager Packages, Scripts Logic,Business Rules)

5) Rate Data and Ownership Data Update

6) Work Status Setting

7) Journal Template and validation setting

4 The Step By Step SolutionWhat should be built in order to setup the fundamental legal consolidation? And How todo this from the scratch, here are the steps in detail:

4.1 Application Set Creation

1. Once installation and ApShellactivation have been completed, youshould be able to log on AdminConsole with the AppSet –ApShell.

Technical Aid: to check and ensure theApShell content activation process havebeen done successfully, either log onAdmin Console or access ABAP serverfrom GUI and run the transaction “RSA1”to check the BI Infoprovider “APSHELL”and its structure.

2. In Admin Console, Copy ApShellinto the target AppSet whichconsolidation environment needs tobe set with.

Legal Consolidation Environment ispossible to be built with in sameApplication Set where planning orreporting Application built in. As thedimensions can be shared byapplications within an Application Set.

3. Set AppSet Parameters

Following Parameters must be set during setting up the Application Set. (Most of themare not necessarily consolidation required, but the generic system requirement forAppSet. )

Technical Aid: At back end, all parameters are stored in ABAP DDIC table:UJA_USER_DEF.

Key ID Description

AVAILABLEFLAG Controls whether the system is offline or not. Yes means the system is online and available forsending data to the database. You can take the system offline by changing the value to No.Y=Yes; N=No

AVAILABLEMSG The message that is displayed to users who try to access an application that is offline(AVAILABLEFLAG = No).For example, the message might be Business Planning and Consolidation is temporarily unavailabledue to scheduled maintenance. Please try again later.

AVAILABLEURL The name of the Web page to display to users who try to access an application that is offline(AVAILABLEFLAG = No).For example, the url might be: /BPC/NotAvailable.aspSee Maintaining applications

ALLOW_EXTENSIONS If [ALL], It was allowed all extension in BPC.

DEFAULT_EXTENSIONS XLS,XLT,DOC,DOT,PPT,POT,XML,MHT,MHTML,HTM,HTML,XLSX,XLSM,XLSB,ZIP,PDF,PPTX,PPTM,POTX,POTM,DOCX,DOCM,DOTX,DOTM,CDM,TDM,PNG,GIF,JPG,CSS,MRC

ALLOW_FILE_SIZE Maximum Files Size allowed for uploading is 100M, which should be written as “104857600”.

UPLOADTEMP Temporary folder used to store Content Library documents. (Required)Directory for web server to put uploaded file before it was transferred into file share.

TEMPLATEVERSION Current version number of the dynamic templates in your application set. Whenever you add to orchange your input schedule or report dynamic templates, you should increment this version number sothat users will automatically get the new templates downloaded when they log on to this applicationset. For example: 01 (Version01).User can also reset the template version from the Admin Console.

JREPORTZOOM This parameter allows user to set the default zoom magnification value on HTML journal reports. Therecommended value = 75%

LOGLEVEL 0= No log, 1 = Error Log only, 2 = Error and Success Logs, 3 = All Logs ( Error, Warning, Success)

SYSTEM BPC 7 Internal system Parameter, default value = 1

MESSAGE BPC 7 Internal system Parameter, default value = Blank

STATUS BPC 7 Internal system Parameter, default value = 1

4.2 Master Data (Dimensions) Set-up

1. Set-Up Dimensions in Dimension Library

For consolidation, listed dimensions are must-to-have dimensions. Therefore, we need tohave a check and ensure that all the dimensions are available in the Dimension Library ofApplication Set just created from ApShell.

(It should be fine if the name is not exactly same, but the types of the dimensions aremandatory for corresponding applications.)For Legal Consolidation Application:

Here is the list of all the dimensions required for legal application:

C_Acct (A)

C_Category (C)

C_Datasrc (D)

Flow (S)

Group (R)

Entity (E)

Intco (I)

Time (T)

For the Application contains Exchange Rates:

Here is the list of all the dimensions required for rate application:

R_Acct (A)

C_Category (C)

R_Entity (E)

InputCurrency(R)

Time(T)

For Application stores ownership details:

Here is the list of all the dimensions required for Ownership application:

O_Acct (A)

C_Category (C)

Entity (E)

Time (T)

Intco (I)

Groups(R)

To create dimension, go to Admin Console -> Go to dimension library -> find the optionin action pane to create dimension as shown below.

2. Maintain consolidation required dimension property

When you create a dimension, all the required properties (attributes) are createdautomatically. But in order to function consolidation process (such as currency conversion,simulation, automatic adjustment etc.), most often additional dimension properties areneeded to achieve the filter, flagging and calculation of the target data. Therefore, weneed make sure those properties are well maintained with expected value to be involvedin the consolidation process according business requirement.

Here is the list of all the consolidation needed dimension properties (attributes).

Please note this only intends to help on checking the completeness of master datasetting for a base line consolidation process and the system automatically generated(required) attributes are not included in this list either. For those dimensions onlyrequested attributes are needed, again are not listed here.

C_CategoryProperty LengthCategory_For_OPE 20FX_DIFFERENCE_ONLY 2FX_SOURCE_CATEGORY 20OPENING_PERIOD 10OPENING_YEAR 4RATE_CATEGORY 20RATE_PERIOD 10RATE_YEAR 10YEAR 10

C_AcctProperty LengthFormula 500SolveOrder 20DIMLIST 20ICMATCH 20VARIATION 20

O_AcctProperty LengthIS_Input 2

EntityProperty LengthElim 10FX_Type 20IntCo 20Owner 255

C_DataSrcProperty LengthCOPYOPENING 1DATASRC_ORIG 10DATASRC_TYPE 2IS_CONSOL 2IS_CONVERTED 2OPENING_DATASRC 20

GroupProperty LengthCURRENCY_TYPE 2DATASRC_LEVEL 10ENTITY 20FIRST_CONS_DATE 20GROUP_CURRENCY 20PARENT_GROUP 10STORE_ENTITY 20STORE_GROUP_CURR 10

FlowProperty LengthDIMLIST 20Flow_Type 10IsInput 2

TimeProperty LengthMonthNum 2

To maintain the property of a dimension, Go to Admin Console - > left click to select adimension in dimension library -> find option “Maintain dimension property” in action pane.

3. Maintain the dimension member and its property values.

To maintain the dimension member of a dimension, go to Admin Console - > left clickto select a dimension in dimension library -> find option “Maintain dimension member” inaction pane.

Please note:

If the dimension is created as time-dependant dimension, user can not actuallydelete a hierarchy assigned dimension member out of the timestamp after it’screated.

The dimension member values are case sensitive with BPC7 NW version, whichmeans if upper case and lower case written are recognized as two differentmembers. But for RATE cube and Ownership cube, we strongly recommend thatnot set two members just with different cases, for example R_ACCT dimension“AVG” and “Avg” could be two different members to store the AVG exchange rate,this is not recommended to be used for storing exchange rate and ownership

details, as both script logic and consolidation program could be confused as wellas bad ender user recognition issues might be resulted.

4.3 Application Set-up

1. Create Applications (Equivalent asInfoCube in BI)

For a base line legal consolidationenvironment, Consolidation, Rate andOwnership applications are must-to-haveapplications, the consolidation engine willlook into these applications to retrievesome of the necessary information.

A. Create a RATE application,The Currency conversion processmakes use of a RATE application,where the appropriate exchangerates will be searched for eachrelevant currency. This cube can benamed as desired. But we will refer toit as the RATE application, in thisdocument.

Note: The master data (dimension) canbe shared by application within anapplication set.

But for RATE application, to fulfill certainconsolidation requirement, R_Acct(Account Dimension for RATEapplication) and R_Entity (EntityDimension for RATE application) arespecific and utilized only by RateApplication.

B. Create an ownership application Ownership application defines

ownership details such as theconsolidation scope, method, % ofshare owned by holding company orgroups etc.

For ownership application, the onlydimension which is specific for ownershipcube is Ownership Account (O_Acct), touse BPC consolidation engine; we haveto set up several required members,which include,

1. PostionInGroup, defines whichcompanies being consolidated in

Rate Application

R_Acct is utilized to detail the different types of rate(Average, End-of-period, etc.).

R_Entity is used to store multiple tables of rates, ifdesired, otherwise the R_Entity dimension may just belimited to one dummy member, typically named GLOBAL.

Currency dimension is utilized to store for each applicablelocal currency.

Time and Category dimensions can be shared by all theapplication involved in consolidation.

Ownership Application

each group.

2. Method, defines consolidationmethod

3. POWN, defines % of ownership(how much they are owned by thegroup)

4. PCON, defines % of consolidation5. PCTRL, defines % of control (how

much they are controlled by thegroup)

This application can be named asdesired, but the relate linkage betweenownership application and consolidationengine must be set up in the applicationparameter setting. (In this document, itwill be mentioned it in next section.)

C. Create consolidation application,Must assign the RATE and OWNERSHIPapplication just created as referenceapplications to the consolidationapplication.

Please refer to the steps wizard ofcreation process.

Step1 and 2: Create a new application,name it and the application type must be“Consolidation” type and definecorresponding RATE and OWNERSHIPapplication to be referred as shown.

Step3: Pick up the consolidationbusiness rules need to be implemented.

Please note: Only when the“consolidation” type application arecreated and the business rule “AutomaticAdjustments” are selected, the pre-delivered business rule library tables willbe activated and shown from AdminConsole UI, which includes MethodLibrary, Elimination Rule and Ruleformula tables, as only AutomaticAdjustment (Such as Minority posting,Investment adjustment) utilize thoseElimination rules and formulas for thecalculation of actual postings .

Time, Category, Entity, IntCo dimensions are shared byownership and legal consolidation cube to be created.

Legal Consolidation Application Creation Steps

Step 1, Step 2 & Step 3

Before the consolidation type applicationis created, from UI of BPC, user are notable to display the rules and the pre-delivered library table content are storedin following ABAP database table.

Method: UJP_Method

Rule Header:UJP_RULEH

Rule Formular: UJP_RULE

Step 4: Uncheck the dimensions checkas shown in order to select the desireddimensions required for legalconsolidation.

Step5: Set dimensions to be included inApplication and also set the Secureddimension for member access control.

Under most of the situation, the Entityand Category dimension tend to beset as secured dimension for memberaccess control against.

For Group dimension here, it storesboth group currency and reportingcurrency and also consolidationgroups.

Here is the Legal Application createdwith all the dimensions shown.

Step 4

Step 5

2. Set the Application Parameters

Go to BPC Administration (Web) -> Set Application Parameters -> Change the currentview and set to the consolidation cube.

Key ID DescriptionFXTRANS 1 for switch ON, 0 for switch OFF Business Rule

Table for the applicationINTCOBOOKINGS 1 for switch ON, 0 for switch OFF Business Rule

Table for the applicationINTERCOMPANY 1 for switch ON, 0 for switch OFF Business Rule

Table for the applicationOPENINGBALANCE 1 for switch ON, 0 for switch OFF Business Rule

Table for the applicationUSELIM 1 for switch ON, 0 for switch OFF Business Rule

Table for the applicationVALIDATION 1 for switch ON, 0 for switch OFF Business Rule

Table for the applicationORG_OWNERSHIPCUBE The value should be the name of OWNERSHIP

cube.ORG_ACCOUNTOWN The value should be the member ID of Ownership

Account (O_Acct) Dimension which controls theposition of a consolidation entity within the group.

OWNERSHIP_APP The value should be the name of OWNERSHIPcube. (This is similar asORG_OWNERSHIPCUBE, but in ConsolidationPrograms, both are utilized)

ORG_PARENTPROPERTY(Just need to be set inOwnership Application)

This parameter is used with dynamic hierarchy forlegal applications when defining consolidationhierarchies. The value set here must match the nameof property in GROUPS dimension in the legalconsolidation application in order to store theownership data.

YTDINPUT This parameter controls whether data is input inyear-to-date format. 1, for YTD

ORG_ACCOUNTLIST The value should be the ID of the member stores thevalue of METHOD, Ownership % and % ofconsolidation in Ownership Account (O_Acct)Dimension. For example, there could be“METHOD”, “POWN”, “PCON”.

4.4 Customizing for Table Driven ABAP Program

BPC7 (NW) pre-defined Data Packages and script logic provides the out-of-the boxintelligence for consolidation processes (such as CT, ICElim) by calling the heart of theconsolidation engine Table Driven ABAP Programs, which perform all the appropriatecalculations on a user-selectable region of data, and write the calculated results into thedatabase.

To run those Programs, we make use of the designed Data Manager Packages throughSAP BI Process Chains to invoke the Programs directly from the K2 scripts logic file andpass to them the appropriate parameters. Following is the full list of consolidationprocess that BPC7 supports with its BI Process Chain and Script File and correspondingBusiness Rules.

Consolidation Task Process Chain NameScript Logic FilesName

Business Rule TableName

Balance CarryForward

/CPMB/OPENING_BALANCES COPY_OPENING.LGF Carry-forward rules

Validation /CPMB/VALIDATIONS VALIDATION.LGF

Validation rules andValidation details

CurrencyConversion

/CPMB/FX_RESTATMENT FXTRANS.LGF

Currency ConversionRules

IntercompanyReconciliation /CPMB/ICDATA ICDATA.LGF No rules neededIntercompanyBalance Booking /CPMB/ICBOOKING ICBOOKING.LGF Intercompany bookingLegal Consolidation(Elimination andAdjustment)

/CPMB/LEGAL_CONSOLIDATION CONSOLIDATION.LGF

Automatic Adjustmentsand AutomaticAdjustmes Details

Account Calculation(Cash Flowfunctioned)

/CPMB/RUNCALCACCOUNT CALCACCOUNT.LGF Account Transformation

US widely usedIntercompanyElimination

/CPMB/IC_ELIMINATION ICELIM.LGF US Elimination

With each process, the pre-defined Data Manager Packages with their associatedScripts and tables of rules need to be created and maintained in order to function theconsolidation task according business requirement and specific business requirement isto be configured in corresponding Business Rule Tables.

With this approach the customer has the possibility to freely decide when and how aprocess should be triggered. We can, for example, invoke a currency conversion directlyfrom the DEFAULT logic, whenever a value is changed via WebExcel or via a data load,or we can decide to run one or more consolidation processes in a batch mode, usingsome customized data package that invokes an appropriately-designed logic file. Also,we can combine one or more of these specialized processes with other custom-definedcalculations, like allocations or modeling formulas or whatever else may be defined usingour general-purpose logic scripting technique.

In order to be able to run a baseline consolidation task,

1. Add the data Manager Packages forconsolidation application.

Go to BPC for Excel Interface -> eData-> Organize Data Package List -> Add adata Package-> look for theconsolidation task related pre-deliveredSAP BI Process Chain and select toadd.

The DM package could also be modifiedfor its dynamic script to achieve thespecific parameter passing requirementand reassign of the table driven programused scripts logic file (LGF).

To Modify DM Package, Go to BPC forExcel Interface -> eData-> OrganizeData Package List -> Select the packageand right click -> Modify Package ->Click View Package from ModifyPackage Screen -> The Dynamic ScriptEditor for Data Manager should beprompted up -> Click “Advance” button -> Edit the script of dynamic selectionscreen generation

2. Create consolidation engine usedScript Logic files (LGF)

Go to BPC Admin Console -> ExpandConsolidation Application -> Go to ScriptLogic Editor -> Create an LGF file byusing K2 script supported by BPC7.0NW

Please note: All the consolidation required K2

logic file (LGF) examples arestored in the File ServiceDirectory :\Root\Webfolder\ApShell\Systemlibrary\LogicLibrary,

Add DM Packages

Modify DM Packages

Dynamic Script Editor for DM

Admin - Logic File Creation

Access GUI for the File Service Directoryto get the K2 logic examples

which intents to help userunderstand the K2 syntax as anexample and can be copied andreused in a customer applicationas well.T-Code for File Service UI: UJFS

The K2 Logic File name must beidentical as the string defined withthe data package.

3. Maintain the business rule table

Go to BPC Admin Console -> ExpandConsolidation Application -> Go toBusiness Rule Editor -> Select the ruletable to create the content of the rulesaccording business requirement.

Admin Console - Business Rule Edit

4.5 Rate Data and Ownership Data Update

1. Loading exchange rate to rateapplication

Most often the Rate application shouldstore the exchange rates for doingcurrency conversion. There are severalways to upload the data to rateapplication, such as utilize the datamanager package – Import, or usedynamic templates to send data from theinput schedule.

If EVDRE are used, the Rate Accounttype dimension and Input Currencydimension can be set in Row and Timedimension can be set in column, savethe EVDRE as input schedule to senddata to the Rate Application. Such inputschedule could also be saved as atemplate in library for sharing and reuse.

Dynamic Input Schedule template(Nested Row) for Rate Input

2. Input ownership data andcalculate ultimate ownership

As the consolidation scope (such asownership percentage, group/unithierarchy) is time dependent and giventhe fact that the dynamic hierarchy editoris not implemented with initial release.Our recommendation is to leverage thesteps suggest below on how updatingthe ownership cube with ownershipdetails.

If the way direct share input is preferredby business,

Step1: Input direct ownership %between Investor unit (entity) andinvestee unit (Intco) under a groupdimension member (most often “LC”could be used) by category and time.Member “POWN” in O_Acct dimensionstores this information.

Step2: Input the consolidation method ofeach entity under each consolidationgroup.“90” Represents holding company in agroup“86” Purchase (Global)“70” Proportional“30” EquityMember “Method” in O_Acct dimensionstores this information.

Step3: Input the position of each entityin a consolidation group.Value 1 represents in the groupother value represents not in the group.Member “PGROUP” in O_Acctdimension stores this information.

The input schedule can be built to inputabove ownership details into cube.

Step1: Direct share input

Step2,3: Dynamic ConsolidationHierarchy Maintain, which includes theconsolidation method and positioning ina consolidation group, both of the factorscan be maintained with following inputschedule:

Step4: Run the pre-delivered DMpackage “Calculate Ultimate Ownership”to calculate the ultimate ownership thathow much each consolidation group ownon each entity. As a result that writeback after calculation, the ultimateownership is stored under the member“I_NONE” of IntCo dimension, andPOWN, PGROUP, METHOD memberhas the group-own-entity valuedescribed above.

If the way ultimate share input ispreferred by business, the only steprequired is to input the group-own-entityvalue for POWN, PGROUP, METHODunder I_NONE under IntCo dimension.

Step4: Run Group Share Calculation(DM package)

Check Ultimate Ownership Report

4.6 Work Status Setting

1. Work States Setting (AppSetdependent)

Go to BPC Admin Console -> WorkStates Setting -> Add the statesaccording the business needs -> Setfor different interface for the Approvalprivilege level for each work states justcreated -> Set appropriate privilege forchanging work states.

2. Work Status Setting(Application Dependent)

Go to BPC Admin Console -> launchthe application -> Work Status Setting-> Set the lock dimension and ownerdimension.

Please note: Owner dimension mustcontain the owner property dimension,which hierarchy controls the workstates change hierarchy.

4.7 Journal Template and Validation Setting

1. Journal Template

Go to BPC Admin Console -> launch theapplication -> Journals -> to create ajournal template

Once the template is created, thedimension in an application can’t bedeleted from the application any more aswell as all data.

2. Validation Setting

Validations are designed to prevent“incorrect” records being saved to thecube. In BPC 7, it is not possible (orsupported) to get data into a cubewithout going through the Write-Backmodule. Therefore, we implemented thevalidations in write-back, to ensure thatinvalid records can not get into the cubefrom any source not only for journals,but also for all DM package and manualdata input. An example for this is if aspecified intercompany account withempty Trading Partner dimension will beblocked from writing into the cube.

Admin - Journal Template Creation

To customize Validation, Go to SAPABAP systems with GUI UI -> go toTransaction code UJ_VALIDATION toconfigure the validation framework andcustomize the validation rules accordingbusiness requirement. Refer to the Howto guide on this for detail steps on howto setup the validation.

In the configuration screen the validationrules according business requirementare defined as shown. Please refer tothe How to guide on Validation setup inBPC 7NW for detail steps on how tosetup the validation.

Go to SAP GUI -> T-CodeUJ_Validation,

Validation Rule Configuration

www.sdn.sap.com/irj/sdn/bpx-cpm