Category: BW

Debug startroutine in BI 7.0

Within BI 3.x it was quite easy to debug your startroutine. Pressing the sequence F7 -> F6 -> F5 brought you directly to the startroutine (code). Within BI 7.0 the “F7->F6->F5” trick doesn’t work anymore. To debug a startroutine in BI 7.0, the following steps need to be executed: 1)...

More

Hierarchy on navigational attribute decreased query performance

A multiprovider, based upon 5 different infoproviders and 2 infoobjects, was causing a performance drain whenever a query was executed. Every query, based upon this multiprovider, contained a hierarchy on a navigational attribute of an infoobject.Eg. Infoobject A –> navigational attribute B –> Hierarchy C.To make sure that the hierarchy...

More

Making an added function module (to a function group) visible in SE80

After creating an (additional) function module within a function group, it wasn’t visible within SE80 after it was transported to another BW system.When displaying the function group, via transaction SE80 –> Function Group, the newly created function module WAS NOT visible, even though the import/transport ended without errors.The trick, to...

More

Create or maintain currency translation types

A currency translation type is a combination of different parameters that establish how the exchange rate for the translation is determined. Currency translation types can be created or maintained via transaction RSCURFor more info regarding currency translation types, click here

More

Find out if R/3 field is already transferred to BW

When executing a fit/gap analysis (are all necessary R/3 fields already extracted and transferred to BW), table RSOLTPSOURCEFIE can be used.Within the selection screen you can enter, for example, R/3 field MATNR if you want to know in which datasources MATNR is used.The screenshot below shows the overview of all...

More

Prevent automatic migration of 3.x queries to version 7.0

Once you’ve migrated a 3.x query to version 7.0, you can’t alter it anymore within a 3.x query designer, as a 7.0 query is not downward compatible. (Even though you can still execute a migrated 7.0 query with a 3.x BEx Analyzer/Query designer, you aren’t able to alter it anymore)...

More