Great note for those tuning BW parameters
912367 - Composite Note: RSADMIN Parameter
Showing posts with label bw. Show all posts
Showing posts with label bw. Show all posts
Friday, December 05, 2014
Thursday, April 24, 2014
Two very important SAP Notes for BW Authorizations
These two notes can solve a lot of problems, or at least give a good start ...
150315 - BW-Authorizations for Remote-User in BW and OLTP
161292 - Authorization templates for user roles and tasks
150315 - BW-Authorizations for Remote-User in BW and OLTP
161292 - Authorization templates for user roles and tasks
Tuesday, January 29, 2013
BPC load 0CALMONTH from BW
Tuesday, July 03, 2012
BW dataflow examples for HR masterdata
It happens quite often, source data comes from a single infotype, but users want informations coming from different subtypes moved to different infoobjects on the same row (i.e. one row per employee per time period), this usually requires some ABAP but there is a trick.
You can use infosets to differentiate logically between rows of the infotype, see below:
This example is quite specific for time dependend masterdata attributes (think 0EMPLOYEE).
It's like having the ability to run different transformations from the same source to the same target according to different values of one column.
Something like inverted rule groups, which are great at turning data in a long row into data in different columns:
An example of rule group usage:
PERNR LGA01 BET01 LGA02 BET02 etc
turned into:
PERNR LGA01 BET01
PERNR LGA02 BET02
which can fit nicely into an infocube.
You can use infosets to differentiate logically between rows of the infotype, see below:
This example is quite specific for time dependend masterdata attributes (think 0EMPLOYEE).
It's like having the ability to run different transformations from the same source to the same target according to different values of one column.
Something like inverted rule groups, which are great at turning data in a long row into data in different columns:
An example of rule group usage:
PERNR LGA01 BET01 LGA02 BET02 etc
turned into:
PERNR LGA01 BET01
PERNR LGA02 BET02
which can fit nicely into an infocube.
Friday, May 04, 2007
SAP BW, IF for your BEx formulas
Have you ever felt the need for an IF in your BEx formulas? Didn't find it? That's because SAP expects you to know about boolean math ...
See, we are subtracting two quantities and we want our result to be shown as 0 if the actual result is negative, the trick is very simple, look at this example:
The first block will evaluate to 1 when GR quantity is greater than PO quantity and to 0 when it's smaller, so the result will be something like:
GR quantity: 6
PO quantity: 4
(( 6 - 1) > 0) * (6 - 4) will turn into 1 (true) * (6 - 4) = 2
The other case:
GR quantity: 4
PO quantity: 7
(( 4 - 7) > 0) * (4 - 7) will turn into 0 (false) * (4 - 7) = 0
See, we are subtracting two quantities and we want our result to be shown as 0 if the actual result is negative, the trick is very simple, look at this example:
( ( 'GR quantity' - 'PO quantity' ) > 0 ) * ( 'GR quantity' - 'PO quantity' )
The first block will evaluate to 1 when GR quantity is greater than PO quantity and to 0 when it's smaller, so the result will be something like:
GR quantity: 6
PO quantity: 4
(( 6 - 1) > 0) * (6 - 4) will turn into 1 (true) * (6 - 4) = 2
The other case:
GR quantity: 4
PO quantity: 7
(( 4 - 7) > 0) * (4 - 7) will turn into 0 (false) * (4 - 7) = 0
Subscribe to:
Posts (Atom)

