bw knowledge for bpc.pdf

8/10/2019 BW Knowledge for BPC.pdf

http://slidepdf.com/reader/full/bw-knowledge-for-bpcpdf 1/25



SAP 2009

Why know a little SAP Business Warehouse (BW)?

You are not expected to become a BW expert any more than you would be

expected to become a SQL expert in the Microsoft release. However, knowing

a little about the BW system can help you when working with the application.

- This presentation won’t get into things that BW consultants may do like data extraction

or application tuning that can affect BPC.

- The point is to know that both you and a BW person both contribute to a solution.

There are some backend features you should know that are related to the BPC

application. Some examples are:- File system access - Script logic tester

- Validations - Process chains

There are some other BW features that can help you during an

implementation. Some examples are:

- Direct table access for transaction or master data (RSA1/LISTCUBE)

- SE38/SA38

- RSINPUT

- SM50/51/66

- SE19

- SE01

- SNOTE



SAP 2009

Terminology

MS Version Term BW Version Term

Application Infoprovider

Dimension Infoobject (Characterstic)

Dimension Member Characteristic Value

Dimension Property Attribute

Hierarchy Hierarchy

Description Text

SignData Key Figure

Measure Calculated Key Figure



SAP 2009

BW Architecture

Applications directly translate to an infoprovider in BW

- A place that holds transaction data.

Applications are set up with many dimensions

- This equates to the characteristics and one key figure that make up an infoprovider

Fundamentally BPC is not a BW application.

- It is a separate application that uses BW architecture to store data.

- BPC related objects are stored in a unique namespace (i.e. /CPMB/ separated from other

true “BW” objects)

This actually violates a lot of traditional BW principles (e.g., “one version of the truth”, shared master

data, etc)

- Some features will work different vs the MS version.

For example, SSIS packages Process chains

While you can get away with using some BW functionalities behind the scenes, it

is generally not a good idea.



SAP 2009

File System Access (UJFS)

UJFS is mostly equal to the webfolders in the MS version.

Anything the file system would hold would be here (e.g, user logs, script files,

report/schedule templates, team files, etc)



SAP 2009

Script Logic Tester (UJKT)

Accessed via t-code UJKT or by executing SE38 program below

Allows testing of script logic via validation or simulation



SAP 2009

Validations (UJ_VALIDATION)

Accessed via t-code UJ_VALIDATION

Allows validation rules to be made on a driver dimension (one driver dimension

per application – typically account). Validations are possible on data loads,

input schedules or journals. This is in addition to normal validation of data on

import/entry as to member existence.

- For example, you could ensure an IC account has to have a trading partner.



SAP 2009

Process Chains (RSPC)

BW feature that replaces DTSX packages in data manager tasks. Accessed

via t-code RSPC.

Delivered chains found in two BPC folders (examples and system). Use these

or copy them to make your own chains.



SAP 2009

Other useful BPC t-codes

BPC Transports - Create Request (UJBPCTR)

- Read the white paper

Query Runtime Parameters (UJQ0)

- SPARSITY_COEF settings for an application. Valid until SP3.

- If (the number of dimensions multiplied by the number of unique members in each

dimension) is greater than (number of records multiplied by the this value), then the

record set is considered sparse.

Writeback Runtime Parameters (UJR0)

- Maintain writeback parameters by application such as package size or record based

locking. See BPC 70NW configuration guide from help.sap.com website for details.

BPC Performance Statistics Report (UJSTAT)

- Used to display runtime statistics if the BPC_STATISTICS web application parameter

is set to ON.



SAP 2009

Direct Table Access – RSA1 (1)

For pure backend what’s in the infoprovider. Useful when you want to see

what’s there vs what your query may be showing.

Right mouse click on the infoprovider in the data warehousing workbench

modeling view and pick “display data”



SAP 2009


In the next screen, pick the elements you want displayed (characteristics and

attributes – aka dimension members and properties)- Note that some of the lines are SIDs (technical BW identifiers). Don’t pick these.



SAP 2009


On the next screen, select the “fld selection for output”. You don’t need to pick

everything because the system will then aggregate on non-shown fields if youselect “use DB aggregation” on the selection screen.



SAP 2009


Once done, from this selection screen just put in the criteria for the data

selection range (single values, ranges, etc) and execute to see data (note thatyou may need to increase the maximum results set).



SAP 2009

Direct Table Access – Master Data

Similar to what we did with transaction data, infoobjects can also display data.

This would allow you to see master data from the BW point of view.

Via RSA1, you can right mouse click an infoobject and display data.



SAP 2009

Direct Table Access – LISTCUBE

Alternatively for direct table access you can use t-code LISTCUBE.

The difference here is you need to know the technical name of the

infoprovider, but you can also tell the system not to display SID values and

default to DB aggregation.

Once you execute, the functionality is the same as previously discussed in

RSA1 display data.



SAP 2009

Table Display – SE16

For other tables not related to transaction or master data (e.g., configuration

tables, etc), use SE16 to access the data browser. All BPC related tables startwith UJ.



SAP 2009

ABAP Editor – SE38 or SA38

Used to execute certain programs (typically those starting with UJ) that don’t

have an associated t-code yet.- Note: you can make your own t-codes and assign the programs to them.

Some useful ones which may not yet have t-codes can be found in Appendix

11 of the BPC330 course

- E.g. UJA_DATA_CHECKER (way to check consistency of an appset)



SAP 2009

RSINPUT (2)

Easy way to append a selection of records by purely BW means, but this

avoids the front end’s validation checks, etc.



SAP 2009

BAdI Builder (SE19)

Used to enable and code ABAP enhancements. For example,

UJ_CUSTOM_LOGIC would allow you to make ABAP custom logic.- There are how to papers on this



SAP 2009

Process Overview (SM50)

If you aren’t sure if your process is actually doing something, then SM50 is the

way to see via the backend if something is running. This is BW applicationserver specific.

If you are multi-server (typically PRD and sometimes QA), then SM51 or SM66

are more useful.



SAP 2009

Apply SAP Notes (SNOTE)

Transaction that allows you to apply (or undo) application of an SAP note

- Remember the demo earlier this year

SAP notes are advanced corrections/bug fixes that can be applied to resolve

issues between support packages.

bw knowledge for bpc.pdf

Documents