Monday, April 14, 2014

BPC filter 0CALMONTH in data package

A picture is worth a thousand words ...

so that's the correct format for 0calmonth.

Friday, October 25, 2013

BPC Member formula ... devil is in the details

I've found a "non working" item in BPC ... it's member formula was something like


very nice and workend fine, but ... while cost is currency converted headcount is not ... so it was "not working" ... 

A little revision, rewriting it in order to take into account dimensions brought the desired result



Not that difficult, but I see that BPC people generally don't like to fully qualify things :(

After a while I had to change it again ... adding another bit of MDX to the game, IsLeaf and CurrentMember


Sunday, August 18, 2013

Tuesday, April 02, 2013

BPC work status setup ... APPROVALORG, a little parameter often overlooked

When setting up workstatus in BPC there is a little web parameter to setup, APPROVALORG, it's often overlooked because generally one doesn't manage more than one hierarchy for an entity ... in our case we have 3 hierarchies and hierarchy number 3 (H3) is the one used to manage read/write permissions and thus the natural candidate for controlling workstatus.
So the web parameter APPROVALORG should not be H1 in this case, or you'll get some "strange" errors, but H3, and of course H3 will also have the owner property correctly filled.

An example:

Some useful tutorials can be found on SDN.

Tuesday, January 29, 2013

BPC load 0CALMONTH from BW

As incredible as it sounds ... in BPC 7.5 NW you have to prepare a conversion to load time from 0CALMONTH to TIME dimension!
Thanks God it's not that difficult, once you know how to do it.
An example:

Time conversion file

Monday, January 28, 2013

BPC lite optimize zero elimination

Just a quick visual to add zero elimination to the light optimize package in BPC 7.5 NW, see SAP Note 1396761

Organize package list

Modify package Lite Optimize
Modify package Lite Optimize

Add task

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:


turned into:


which can fit nicely into an infocube.