SAP-BW Development Standards Quick Guide

8/12/2019 SAP-BW Development Standards Quick Guide

1/6

2011

Dr BjarneBerg

Raj Vuppala

[SAP-BW DEVELOPMENT STANDARDS & GUIDELINES]The Purpose of this document is to provide development standards & guidelines specific to SAP-BW

based objects/solutions.


2/6

Version 1.0 SAP-BW DEVELOPMENT STANDARDS & GUIDELINES

SAP-BW Development Standards & Guidelines Page 1

The Purpose of this document is to provide development standards & guidelines specific to

SAP-BW based objects/solutions.

Note: Assign BW objects to its respective Development Package.

1)Front-End/ BEx QueriesBEx Queries Creation: All BEx Queries or Reports need to create on top of Multiprovider

[In order to have scalable/flexible administration it is advised to create BEx query or Report on

Multi-provider not directly on top of Infocube or DSO or Infoset]

[If Business requirement needs detailed reporting, then as an exception, after getting approval

from authorized contact, can create BEx Reports (for example, Drilldown to details report) on

Muliprovider created on top of DSO or Infoset]

BEx Queries should developed/created by BI Team in all environments.

BEx Queries should not be create by Non-super user or Non-BI user or team member in all

systems (BW Development, BW Quality and BW Production system)

Power users with formal Web Intelligence trainingare allowed to build ad-hoc webI reports in

Production system.

BEx workbooks are not recommended, however on approved request only to the specific

users/audience may use.

Primary user interface will be Xcelsius Dashboard; Pre delivered & formatted WEBi reports.

All shared reports will be published to the defined portal. (Need to confirm IBM Portal or SAP

Portal)

BICS connector should always connect BEx Queries never directly to InfoProviders.

[Note: Connecting InfoProviders directly with BICS will bypass BI Analytical Engine and as well as

data level security features]


3/6



2)Data Staging / ETLDatastore objects (DSO) data updates: All data loads should be updated into DSO objects

first.

First Level DSOs should always represents source system As-Is transactional data withoutany

modifications.

First Level DSOs can have derived Characteristics and Key Figures as additional fields.

Write-Optimized DSO used for high volume data for e.g. Material Movements etc.

InfoCube data updates:Always update InfoCube data from DSO.

[Do not update data from InfoCube to InfoCube]

Transformations: Data transformation always should occur from DSO to higher level objects.

Data can be updated from DSO to its subsequent higher level DSO.

Data can be updated from DSO to higher level Infocube.

Conditional update or data filtration (for example updating data for a specific Company code,

Division etc.) can be done when updating data from Level 1 DSO to subsequent higher level

objects, can be Info cube or DSO.

Storing calculated key figures or derived Characteristics (for example Master data lookup)

should occur only when updating data from Level 1 DSO to higher level objects.

Data Retention: First Level DSOs stage data (As-Is) retained for 7 Fiscalyears + CurrentFiscal year.

***HD Smith Fiscal Year = June to May


4/6



3)Data Extraction / Data AcquisitionProcess Chains: Process chains should be configured (Met chains) & approved by BW

Architect; Developers should create their own assigned Local chains.

4)Security / AuthorizationData Level security: Data access or data level security is enforced using BW authorizedobjects including BEx Queries.

Role base security should not be user specific.

5)Administration Tasks /MaintenanceAggregates creation: Aggregates should only create using proposals.

[In order to have optimized aggregates and save DB space it is advised to turn on BW statistics

and review the results at least for a week and create based on proposals.]

PSA data retention:PSA date should not retain more than max 8 weeks.

[Note: Only approved business request considered if required to retain more than 8 weeks of

PSA data.]

Process chain for PSA data cleanup (set for 14 days in general).


5/6



Technical content or BW Statistics objects: All Statistics Cube or Technical Content

needs to be activated and cleansed periodically to reduce data volume or DB space.

Technical Content or BW Statistics Process chains will be scheduled on weekend and can be

schedule after large conversion or Go-Live or whenever required.

Objects Transports: Transport requests should be segmented by object type.

[In order to minimize transport errors, it is advised to group objects and collect changes in a

single transport request and later moved insequence across landscape.]

Data ModelObject types (Group 1)

Package (Development Class) InfoAreas InfoObjects InfoObject Catalogs

InfoProvidersObject types (Group 2)

DataStore Objects InfoCubes InfoSets MultiProviders Custom tables Custom views Open Hub destination

Extract, Transform, and Load (ETL)Object types (Group 3)

ECC Extractors DataSources and Replication Transformations InfoPackages Data Transfer Processes


6/6

Documents

SAP-BW Development Standards Quick Guide