on 08-27-2014 7:32 AM
Hi All,
we have created a univ(IDT) from a cube using SAP BW --> realtional connection --> multi source universe.
In the newly created univ we have a dimension "G/L account". which has got some numeric values
say 10001,10002 ...50000.
The requirement is i have to create new dimensions or attributes based on "G/L account"
Ex:
Dimension A if the G/L account value between 10013 to 10033
Dimension B if the G/L account value between 30023 to 30045
is it possible. please help
i am on BO 4.1 Sp4 & BW7.3
Regards,
deshmukh
Mark i have no idea whether MDX engine supports IF or CASE statements here.
Gurus - please help
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Mark
i am not very sure how this is achieved. but below is the sample of what i tried
@select ("_D_IOFIGL_C10_0GLAccount."0GL_Account")
from "_D_I0FIGL_C10_0GL_ACCOUNT" where "_D_I0FIGL_C10_0GL_ACCOUNT"."0GL_ACCOUNT" between x and y
please correct me.
GL Account has got lot of values
we are creating dimensions using it.
if the values are between xx and yy it has to be created as Dimension A
if the values are between ww and hh it has to be created as Dimension B
please help
A case statement has the construct:
CASE
WHEN TABLE.COLUMN BETWEEN '100000' and '100333' THEN 'DIM A'
WHEN TABLE.COLUMN BETWEEN '100334' and '199999' THEN 'DIM B'
...........
ELSE 'DIM Z'
END
You can add whatever extra WHEN clauses you want.
I'd still say that it's easier to achieve at the BW level - I'd always push this sort of thing back to the database/data warehouse where possible and have a column for this value.
Hi Mark,
The G/L account formula is
@catalog('FIGL01')."PUBLIC"."I0FIGL_C10"."0GL_ACCOUNT" (automatically created by univ)
i used the above formula to create my new dimension A as stated below.
SELECT: @catalog('FIGL01')."PUBLIC"."I0FIGL_C10"."0GL_ACCOUNT"
WHERE: @Select(FGL01\Accounts\G/L Account) BETWEEN '100' AND '99'
it worked. Anyways thanq for your interest towards helping me.
I'd create it at the BW layer - that way it's usable at all levels of the reporting chain.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
101 | |
13 | |
13 | |
11 | |
11 | |
7 | |
6 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.