Class Notes as per Videp.pdf

8/20/2019 Class Notes as per Videp.pdf

http://slidepdf.com/reader/full/class-notes-as-per-videppdf 1/50

Class 11. Creating an Application Set

1. Login to Admin Client

2. Login to existing Application Set-(PR_APP1 instead of APSHELL)3. Add a new application set - Select one of the existing application sets as a source-

PR_APP1

4. Copy with/without database records5. Re-Login to the new Application Set(Click on connection wizard, enter the id and pw again)

2. Creating a Dimension (Account, Entity, Intco, DataSrc, Category, Groups, Product)

1. Select Dimension Library-Add a new Dimension2. Give a Name and Select Type of Dimension

3. Add Properties if required and Add the Dimension3. Adding Properties to dimensions

1. Select the Dimension 2. Click on Maintain Dimension Properties

3. Add Properties and Process the Dimension

4. Maintaining Dimension Members1. Select the Dimension2. Click on Maintain Dimension Members

3. Update the Members sheet4. Process the Dimension

5. Make the APPSET Available (Change the Status)5. Creating Hierarchy in Dimensions using PARENTH1 Column property

1. Values in PARENTH1 Column must be values from ID column



Class 11. Creating an Application

• Select Application• Add a new application (Finance)

• Select Application Type (Reporting Type and Generic)

• Select a source application (Planning)

• Chose your dimensions and add the application (Account, Entity,DataSrc, Groups, Intco, Time, Category)

• Dimension Types A,E,C,T are required in every application.

• Standard Dimension Types cannot be added twice to an application.

•There can many User Defined Dimension Types (Type U)

• Note:Grant access to the new application (Security-MemberAccessProfile - Adminmbrprf-Read&Write to All members of securedDimensions in your Application)



Class 1

1. Application in BI 7.5• Creates infoprovider and Multiprovider in BI• Infoprovider is a real-time infoprovider

• namespace /CPMB/

• Dimensions and Properties are created asInfoobjects in BI

• Properties are created as attribute infoobjects

• Tables in Application(NW) - E and FFactTables of Infocube



Class 1

1. Optimization in BPC NW

Optimization

Before compression F-Table

entity Category Time Amount

1000 Actaul 2008.jan 100

1000 Actaul 2008.jan -100

2000 Actual 2008.Jan 200

Lite Optimize After Compression E-Table

1000 actual 2008.jan 0

2000 Actual 2008.jan 200

Full Optimize

2000 Actual 2008.Jan 200 E-Table



Class 1

1. Application Optimization in MS Version

• Tables in Application(MS) - Fact(Long-term),Writeback(Real-Time), Fac2(Short_term)

Writeback/Fac2 Tables to Fact Table

• Compression: Based on the DimensionValues the data is compression, amounts are

added.



Class 1

1. Incremental Optimization in BPC MS

Incremental Optimization Takes System Offline

W riteback table

RealTime

Fact Table

LongTerm

Fac2 Table

Short-Term



Class 1

1. Lite Optimization in BPC MS

Lite Optimization

Doesn’t Take System Offline

Writeback table

RealTime Fac2 Table

Short-Term



Class 1

1. Full Optimization in BPC MS

Full Optimization (Incremetal Optimization + Process Dimensions)

Takes System Offline

Writeback table

RealTime

Fact Table

LongTerm

Fac2 Table

Short-Term



Class 2

1. Load Transactional Data1. Login to BPC Office Client• Upload the File to the Server(edata->Data Upload)

• Conversion File(Optional)

• Create a new Conversion File(eData->New Conversion File)

• ->• Transformation File(Required in 7.0 and Optional in 5.1)

• Create a new transformation file(eData->New TransformationFile)

• Validate and process the transformation file with/without datafile(eData->Validate and Process)

• Import the file to Application(edata->run package->import)



Class 2

1. Create Conversion File

• Converting Data (External Format ->

Internal Format)

2. Create a Transformation File

• Options

• Mapping

• Conversion



Class 21. Transformation File-Options

AMOUNTDECIMALPOINT=<text_character>Default: Period

Allows you to specify a non-period decimal point for countries that use a different character, such as acomma. Note: the character specified in this option must differ from the character specified for theDELIMITER.

CONVERTAMOUNTWDIM=<dim_name>

Default: Account

Specifies which dimension to look at for value calculations.You must specify a dimension conversion sheet using the Amount *Conversion option. See Mapping

dimensions to conversion files for more information.If there is no formula in the Formula column of the Amount conversion sheet this parameter has no affect at

* . , . .increased by 10% during the conversion.

CREDITPOSITIVE= YES | NO

Default: YESIf No, all amounts referring to an ACCOUNT type (LEQ, INC) will have their signs reversed.DELIMITER <text_character> | SPACE | TAB

Default: , (comma)If the FORMAT option is set to DELIMITED, this option defines the single character that is the delimiter

between columns. use the keywords SPACE or TAB if space- or tab-delimited.

FORMAT= DELIMITED | FIXED | CATEGORYBYTIME

Default: There is no default. This option must be defined.The format of the data in the input or output file. You must enter a format type. Delimited means that there

is a special character between each column of data, defined by the Delimiter option (below). Fixedmeans that the data is in a fixed field format. Use the FCOL mapping option, defined below.CategoryByTime means that the data is listed by categories that represent time periods.

HEADER= YES | NODefault: YESIf YES, then your input file contains one header row that defines the fields. If you do have a header row, you

can refer to a field by name in the MAPPING section.



Class 2

1. Transformation File-Options

MAXREJECTCOUNT=<empty_string> | -1 | positive number

Default: <empty_string>If validating records, the number of rejected records at which to stop processing. A value of -1 implies that

DM should keep processing no matter how many rejected records exist. The default value is500, which can be represented by an empty string.

OUTPUTDELIMITER= <text_character> | SPACE | TAB

Default: , (comma)Same as DELIMITER, but used to define the delimiter when using the transformation to export data.The above example should be placed all in the same cell in the transformation file.

ROUNDAMOUNT=<integer>Default: no rounding occurs

Specifies the amount of decimal places to round values during the transformation.SKIP= <integer>

Default: 0 (zero)Number of lines to skip at the top of a data file. If your data file has a header, set this value so that those

lines are skipped during transformation.SKIPIF= <text string> | NULLDefault: <empty_string>Skip a line in the data file if it begins with the specified string. Setting this option to an empty string means

that no lines are skipped in the body of the data file. Header lines can still be skipped using theSKIP command, above. You can skip null database records by setting SKIPIF=NULL.



Class 2

1. Transformation File-Options

SPECIFICMAPPING= No | YesDefault: No

Allows ou to turn off the automatic dimension ma in feature. When set to YES, Data Manager does not automatically mapdimension names. This is especially useful for data export.

VALIDATERECORDS= No | Yes

Default: NoIf YES, validate the mapping and that members exist, and map data in

the proper order for Business Planning and Consolidation. For example, the Amount field is always moved to the end of the

records even though it might be written in the first line of themapping section.

If NO, will not validate. In this case, if the mapping section is out of order or just wrong, fields will be skipped.



Class 2

1. Transformation File-Mapping

*COL(A)

A = column index in the data file

Defines a dimension for a field in the data file when the data file does not have a header row. See the note below about automatic fieldnames when you do have a header row.

Example:

Account =*COL(2)

*COL(A,B:C)

= coumn n ex n e a a eB:C = start/end position within the column

Defines a dimension for a subset of a field in the data file.

Example:

Account=*COL(3,1:4)*FCOL(A:B)

A:B = start/end position within the data row

When using Fixed format data files, this option allows you to define the start and end character columns for each field. In the example below,the columns 4 through 7 represent the Account dimension.

Example: Account=*FCOL(4:7)

*MVAL(A:B)

A:B = start/end column of time period

Use this command if your data file has multiple period columns. For example, if you have columns that are like this:

Account,Category,DATASRC,entity,IntCo,RptCURRENCY,JAN,FEB,MAR,APR,MAY,JUN,JUL,AUG,SEP,OCT,NOV,DEC

You would use Time = *MVAL(7:18), since columns 7 through 18 contain data based on time periods. Using this command

requires that you use a Time.xls conversion sheet. See the sample Time.xls conversion file, located in the ConveresionFiles

folder, for more information.

If your data does not have a header row, the time periods will be named P1, P2, P3,...,PN by default.

Example:

Time = *MVAL(7:18)



Class 2

1. Transformation File-Mapping

*NEWCOL(A)

A = dimension member

Creates a new field with the given value.

Example:

Account=*NEWCOL(Revenue)*Str(string)

Adds a text string to the members of a column. Useful if you need to map data file fields to fields in your database that have the same names,except they have extra characters appended or in front of the field name.

xamp e:Entity = *Str(NE) + *COL(1)

*Pad(A,B,C,D)

A = Field nameB = Total lengthC = Padding directionD = Padding character

Use to format exported data into fixed-width records. Use in conjunction with the "None" delimiter. The Padding character is optional and is aspace by default.

Example:

Account=*Pad(Account,10,L) Account=*Pad(Account,10,L,0)

*If(Condition1 then Action1;Condition2 then Action2;Default Action)

Condition1 - If this evaluates to "True," map using Action1Condition2 - If Condition1 is "False" and Condition2 is "True," map using Action2

Default Action - If both Condition1 and Condition2 are "False", map using this Default ActionCondition1 and Condition 2 can contain multiple items that are added together (using the plus (+) sign), as in this example:Product=*if (Product+ID+Entity = *str(148552) then *str(MHarn);ID(1:1) = *str(C) then *str(XX) ; *str(YY))which means:

IF Product + ID + Entity value are equal to “148552” then Change Product value to “MHarn” or

Else IF first value of ID field is equal to “C” then Change Product value to “XX”

Else change product value to “YY”



Class 2

1. Transformation File-Conversion

Dimension Name = [COMPANY]WorkbookName[!SheetName]

Items in brackets are optional.

If [COMPANY] is defined then DM will try to obtain the conversion file from the Maincompany Data Manager folder, otherwise Data Manager looks in the appropriate

.Examples:

Where AccountConv.xls is the name of the Account dimension conversion file.

Account = AccountConv.xls

Amount = AccountConv.xls (Use the Amount keyword with the ConvertAmountWDim

transformation option)

Account = AccountConv.xls!newaccount

Account = [COMPANY]AccountConv.xls!newaccount



Class 2

1. Conversion File*skip

If you want to ignore certain external data, you can place the keyword *skip in the Internal column. For

example:

External Internal

ACCPAY *SKIP

Wildcards

You can use the asterisk (*) and question mark (?) wildcards in the External and/or Internal columns.

asterisk (*) stands for ANY character, while question mark (?) stand for any SINGLE character.

For example, if you want to reference all members, use the asterisk (*). This would be useful to apply a

formula to all members:

External Internal Formula

* * value*1.10



Class 2

1. Conversion FileIn the formula column, you can use following options:

1. arithmetic functions You can use +,-,*, / to perform scaling and basic arithmetic.value*3value*0.5 + 2

2. Round(value, digits) Use the Round function to round off values to the specified number of digits. Round(value,2),Round(amount,2)Round(value*100,2)

You use the keywords amount or value to specify the target of the formula.

For example:

FORMULAvalue*0.5Round(value,2)Round(amount,2)Round(value*100,2)



Class 2

Creating transformation file for Loading BI Infocube to BPC Application:•Before we run the data manager package to load data, we should prepare the transformation and conversion

files. An example of a transformation file that we can use to load data from other infoproviders is given below.

•Mapping Dimensions:The dimension names in the BPC Application are mapped to the corresponding

characteristics from the Infoprovider from where we want to load the data. Please note that as far as the BPC

dimension names are concerned, we are using the dimension names (and not the technical names of the BW

characteristics, we must use the technical names of the BW characteristics. For example, the TIME dimension

in BPC is mapped to 0FISCPER characteristic in BW. Also please note the mapping for AMOUNT. The

AMOUNT is mapped to the technical mane of the key figure in the source Infoprovider. So in this case,

ZMAOUNT01 is the technical name of the key figure in the source Infoprovider.

•Mapping KeyFigures: please note that the source BW Infoprovider can have multiple key figures. If so, we

can choose only one key figure in a transformation file since our BPC cube has only one key figure. If for any

reason, you have a situation where you have to get data from two or more key figures, you can use multiple

transformation files and run the data manager package multiple times with each transformation file. However inthat case, please note that the data from all those key figures will end up in the same single key figure in the

BPC cube.

•Please see the examples of the transformation and Conversion files below.



CLASS 2



CLASS 2



CLASS 2





Class 1&2- Assignments

1. Dimensions:1. Create Dimensions (You can give your own name eg. BT_ACCT)

1. <XX_Account> = A

2. <XX_DataSrc> = D

3. <XX_Entity> = E

4. <XX_Groups> = R

5. <XX R tCurrenc > = R _6. <XX_InputCurrency> = R

7. <XX_Product> = U

8. <XX_Category> = C

9. <XX_Intco> = I10. Time = T ( Use the existing TIME Dimension)

2. Add Properties (According to dimensions_properties.doc)

3. Maintain Dimension Members (According to

dimensions_members.xls)




1. Application:1. Create Application Finance with dimensions according

to financedata.csv file (Make Category and Entity your secured dimensions)

2. Grant member access rofile AdminMbrAccPrf to finance application for the secured dimensions(Allmembers and R/W access)

3. Upload the financedata.csv file in BPC Excel

4. Create Default Transformation File - Validate andProcess the transformation with datafile.

5. Import the file using the default transformation file.




1. Labs 1-10 in BPC330

2. Lab 15 in CPM 330



Class 1&2- Assignments-

Issues1. ApplicationSet Not Available

1. Go to BPC Administration->Select the Application Set->Set Application Set Status->Chose Available

2. Unable to View the Application Created1. Go to BPC Administration->Security->Select

Member Access Profile->Select AdminMbrAccPrf->Modify Member AccessProfile->Grant Access Read&Write to [ALL]

Members of secured dimensions



Class 3

1. Menu Options of BPC Office Client

1. eAnalyze - Reporting

2. eSubmit - Planners(Input Schedules)

3. eTools - Administrators

4. eData - Data Management

5. ePublish - Publish Books



Class 3

1. evDES: Reads the description of member IDs for a give IDand Application(Optional)

2. evCVW: Reads the current View of dimensions

3. evPRO: Reads the property values of the members

4. EvTIM: Can offset Time Dimension

. : e ransac ona a a amoun or e se ec emember values - Default is current view values

6. EVSND: Send Data to the application for selectedmembers and value - Note: Can send data only for basemembers not to parents or nodes



Class 3

1. Creating a simple report using EVDRE1. Open a blank worksheet

2. Type ‘=EVDRE() and Enter IN CELL A1

. 4. Select the dimensions in Rows and Columns

5. Change the Current View selectionsaccording to the required data

2. Undertand EVDRE function to create

reports.



Class 3

1. Creating a simple report with Evdre

• Pagekeyrange-Filtering Section

• Rowkeyrange-Values in Rows

• Colkeyrange-Values in Columns

• Expansions in Rows and Columns

• Membersets for Dimensions in rows

and columns



Class 3- Exercise1. Create the Income Statement using Evdre



Class 4

1. Inserting Buttons in report and

Schedules and make use of Built-in

Macros

2. Formatting options using Excel

functions and Dimension Properties



Class 4- Report1. Income Statement:

1. EVDRE in Cell A1->Enter->Refresh Workbook2. Select Account in Rows and Entity in Columns3. Member Set of Entity is BAS, SELF4. Member Set for Account is ALL,SELF,PARENTAFTER

5. Insert a column next to Account IDs for reading CALC property values6. Use EVPRO function to read the property values

7. Use conditional formating to make nodes bold italic based on property(CALC) values8. Format the cells according to the template-Changing the borders and fill colour 9. Move the Header(Pagekeyrange section) to hidden area

10. Type the Report name and header section according to the report(use appropriate functionsto read the header values

11. Insert Buttons-View->ToolBars->Forms->Button12. Use Appropriate Macros for Refresh and Select Period buttons

13. Insert a combo Box for MTD and YTD values-Format Control and Assign Macro to AutoRefresh

14. Insert a check box next to Suppress Zeros15. Format Control of Check Box-> Cell Link16. Suppress section formula

17. HardCode the Pagekeyvalues for the dimension that should not change18. Group the rows that should be hidden

19. Suppress row keys and col keys from options section

20. Hide the rows and freeze window pane.21. Tool-options and uncheck Rows and Column Sections , Outline Symbols



Class 4-Reporting Assigments

1. Create Consolidated IncomeStatement as per the above steps

2. Create Trial Balance Report using multipleEVDREs(Hint: Common Column but differentRow Key Ranges one with BalanceSheetaccounts and other with NetIncome Accounts

3. Create MultiApplication report using 2 EVDREsone reading data from each application(Hint:common RowkeyRange but different Columns)

4. Note: Sample Reports are attached as

spreadsheets.



Class 4

1. Creating a simple Input Schedule with Evdre• Planning Layouts in BPS or Input-Ready Queries in IP• Building InputSchedules is same as building reports

using EvDRE(Have to change the workbook optionsfrom Re ort->In utSchedule

• Planning can only be done on leaves(Base Members)• Input Schedule can also be build using EVSND



Class 5

1. Security:

1. User

2. Team: Team is a group of users

3. Task Profile: To restrict on task that

can be performed by a user

4. Member Access Profile: To restrict on

accessing data.



Class 5

1. Datamanager Packages:

1. Understand the Standard DM packages

available

. 3. Customize DM Package

4. Creating Process Chains(7.0)

5. Attaching process chains to DM packages



Class 6

1. Currency Translation:1. Rate Application

1. Upload the exchange rates

2. Dimension Member Properties

.2. Entity:Currency

3. Currency: Reporting, Currency_type

4. [DataSrc: Datasrc_Type, IS_converted]

3. Script Logic for Translation

1. FXTrans.LGF2. Default.LGF includes FXTrans.LGF

4. Business Rules

5. Run the Default Logic or FXTrans Package



Class 6

Currency Translation Logic FXTRANS.lgf:

*RUN_PROGRAM CURR_CONVERSION

CATEGORY = %C_CATEGORY_SET%

_ TID_RA = %TIME_SET%

RATEENTITY = GLOBAL

OTHER = [ENTITY=%ENTITY_SET%]

*ENDRUN_PROGRAM



Class 6

Eliminations:

1. Dimension Member Properties

1. Account:ElimAcc

2. Entity:Elim

3. Intco: Entity4. Currency: Reporting,

2. Script Logic for Eliminations1. ICElim.LGF

2. Default.LGF includes ICElim.LGF

3. Run the Default Logic or Run ICElim Package



Class 6

Elimination Logic ICELIM.lgf:

*RUN_PROGRAM US_ELIM

CATEGORY = %CATEGORY_SET%

GROUP = %GROUPS_SET%

TID_RA = %TIME_SET%

OTHER = [ENTITY=%ENTITY_SET%]

*ENDRUN_PROGRAM



Class 7

Planning:

1. Input Schedule Layouts

2. What are different calculations

1. Worksheet Calculation

2. Script Logic

3. Allocations

1. Worksheet Spread Functions

2. Script Logic

Run the Default Logic or Run ICElim Package



Class 7

Allocations: An allocation is essentially always made up of the following

components:

- WHAT needs to be allocated

- WHERE the results of the allocation must be written

- a r ver s ou e o per orm e a oca on- The member set defined in a dimension of the

“TOTAL” region is in general automatically added upinto a TOTAL value, to generate the total amount touse as the denominator in the calculation of theallocated amounts.

- How the allocation driver should be used, i.e. what

FACTOR must be applied to the source amountsduring the calculation



Class 7

Allocations Example:

* RUN_ALLOCATION

*FACTOR USING/TOTAL

*DIM ACCOUNTWHAT= Commission;

= ;USING=ExtSales;TOTAL= <<<

*DIM ProductWHAT= pdummy;

WHERE=BAS(CON_PET_TYPE);USING=<<<;

TOTAL= <<<*ENDALLOCATION



Class 7

Script Logic Statements:1. The *REC( ) instruction tells the program what to do once a criteria has been

met. Each REC instruction generates one new record to post to the database.Each source record can generate as many records as desired, even pointing tothe same destination cell.

2. The s ecial instruction *SELECT allows the user to retrieve a list of elements

. from a dimension and save it in a user-defined variable for later use anywhereelse in the logic.*SELECT ({variable}, {What}, {From}, {Where})

3. WHEN / ENDWHEN structure works in the same way as the SELECTCASE /ENDSELECT structure, with *REC( ) statements that generate new records.

4. Lookup

5. Include

6. For/Next

7. Commit

8. XDIM_MEMBERSET



Class 7

Script Logic Examples:To Calculate External Sales from Units and Price:*XDIM_MEMBERSET TIME = <ALL>*XDIM_MEMBERSET B_ACCT = SALESUNITS,SALESPRICE*XDIM_MEMBERSET CATEGORY = BUDGET*XDIM_MEMBERSET ENTITY = <ALL>*XDIM_MEMBERSET DATASRC = INPUT*XDIM_MEMBERSET B_INTCO = NON_INTERCO

*XDIM_MEMBERSET GROUPS =LC

*when B_ACCT

*is "SALESUNITS"*REC(FACTOR=[B_ACCT].[SALESPRICE],B_ACCT="EXTSALES“)

*REC(EXPRESSION=%VALUE%*[B_ACCT].[SALESPRICE],B_ACCT="EXTSALES“)

*endwhen*COMMIT



Class 7

Script Logic Examples:Currency Translation using Script Logic:*LOOKUP RATE

*DIM TIME=2008.JAN*DIM CATEGORY="ACTUAL"

*DIM R_ACCT="AVG"

*DIM R ENTITY="GLOBAL"

_

*DIM RATECHF:INPUTCURRENCY="CHF"*DIM MEASURES="PERIODIC"

*ENDLOOKUP

*WHEN GROUPS

*IS "LC"

*REC(FACTOR=LOOKUP(RATECHF), GROUPS="USD")

*ENDWHEN

*COMMIT



Class 7Script Logic Examples:Logic to Move data between Applications:*DESTINATION_APP=ManagerialCons

*xdim_memberset IntCo=<all>

*xdim_memberset Category=actual

*xdim_memberset Company=<all>

*xdim_memberset CostCenter=<all>

*xdim_memberset datasrc=<all>

* = _*ADD_DIM PRDFAMILY=P9999

*ADD_DIM SKU=SKU9999

*calculate_difference

*clear_destination

*When ACCOUNT.LC_TO_MC

*IS<>""

*REC(FACTOR=1)

*ELSE*ENDWHEN*COMMIT



Class 8 Additional Topics:

1. Comments(EVCOM,EVCGT,EVCGP) -> BPC Excel2. Data/Activity Audit ->

1. BPC Launch Page->BPC Administration->Manage Data/Activity Audit

2. BPC WEB ->System Reports->BPC Audit Reports

3. WorkStatus

1. MNU_ESUBMIT_MODIFY - to set workstatus

2. EVLCK- to read workstatus status

4. Custom Menus(EVMNU)5. HotAnalysis(EVHOT)- To jump from report to report

6. Journals

7. Transports (TCode = UJBPCTR)8. Delta of 5.1 to 7.0

1. NewID property is removed (from the default view of members)

2. InAPP for properties is removed3. Builtin Programs replace Stored Procedures for FXTrans, ICElim,etc

4. ScriptLogic Syntax has changed for GET function where TULEPsare used. Eg [account].[salesprice] = get(account=salesprice)

5. SQL Tables = Infocubes and InfoObjects

6. MNU Commands (Macros have changed a bit)

7. BPF is completely removed8. Master Data and Transactional Data upload from BI to BPC

Applications is available in BPC NW

9. Transport mechanism in 5.1

Documents

Class Notes as per Videp.pdf