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.
Version 1.0
SAP-BW DEVELOPMENT STANDARDS & GUIDELINES
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 Queries
BEx 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]
SAP-BW Development Standards & Guidelines
Page 1
Version 1.0
SAP-BW DEVELOPMENT STANDARDS & GUIDELINES
2) Data Staging / ETL
Datastore objects (DSO) data updates: All data loads should be updated into DSO objects
first.
First Level DSO’s should always represents source system “As-Is” transactional data without any
modifications.
First Level DSO’s 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 DSO’s stage data (“As-Is”) retained for 7 Fiscal years + Current
Fiscal year.
***HD Smith Fiscal Year = June to May
SAP-BW Development Standards & Guidelines
Page 2
Version 1.0
SAP-BW DEVELOPMENT STANDARDS & GUIDELINES
3) Data Extraction / Data Acquisition
Process Chains: Process chains should be configured (Met chains) & approved by BW
Architect; Developers should create their own assigned Local chains.
4) Security / Authorization
Data Level security: Data access or data level security is enforced using BW authorized
objects including BEx Queries.
Role base security should not be user specific.
5) Administration Tasks /Maintenance
Aggregates 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).
SAP-BW Development Standards & Guidelines
Page 3
Version 1.0
SAP-BW DEVELOPMENT STANDARDS & GUIDELINES
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 Model – Object types (Group 1)
 Package (Development Class)

InfoAreas

InfoObjects

InfoObject Catalogs
InfoProviders – Object 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
SAP-BW Development Standards & Guidelines
Page 4
Version 1.0
SAP-BW DEVELOPMENT STANDARDS & GUIDELINES

ABAP programs/functions used by transformations

Open Hub Destinations (ETL only)
Process Chains – Object types (Group 4)
 Process variants

Process chains
BEx Queries – Object types (Group 5)
 ABAP programs/functions used by query exits, or other front-end components.

Queries and Query Elements

Workbooks
BI System Performance Reviews: BI System Performance review should be executed at
least in every 6 months. This Review will occurred by March & September.
BI System Performance review includes Index checks, DB Stats check and Aggregates check by
reviewing early watch reports.
Fiscal Year Closing Schedules: Resource intensive System Jobs will be suspended during
Fiscal year freeze/close.
SAP-BW Development Standards & Guidelines
Page 5