BPC : Using Dimension Property in Formula of a Conversion File

Hi,
I want to export data using Package Export from Fact Table. I have transformation and conversion files.
I want to use the property of a dimension in Formula Column of a Conversion file.
I want to lookup the property and based on property I want to either skip record or have internal value.
I am looking for something like follows..
=iif([%external%].TYPE = WBS,*SKIP,D2113)
So if my Dimension 's TYPE property is WBS , I would like to skip that record else I want the value from fourth column.
I am running the Export from Fact Table with various combinations in formula column , but it is only returning null in the export file.
Please let me know how I can make this work.
Thanks,
Sanjay

Sadi,
You can write if Statement in transformation not conversion.
Look at this docs,
How to Import Master Data and Hierarchies into SAP BusinessObjects BPC 7.5 from SAP NetWeaver BW
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/c02d0b47-3e54-2d10-0eb7-d722b633b72e?QuickLink=index&…
Thanks

Similar Messages

Row Axis using dimension property

Dear All,
I have a property on the Currency dimension, say "R_Acct", that identifies the R_Account ID each Currency memebr should post into. For example:
R_account:
ID Desc
UK UK Inflation
US Us Inflation
Eur Euro Inflation
Currency:
ID Desc R_acct
GBP Pound Sterling UK
USD US dollar US
Euro Euro CUrrency Eur
My requirement is to build an input sheet with the R_account and Currency dimensions expanded on the row axis. However, i want to fetch the corresponding R_acct for each currency member to replace the EPMOlapMemberO for the the R-Account dimension. Using the EPMMemberProperty only makes it a local member and does not make it an axis. And when i tried "EPMOlapMemberO(E19,"[R_ACCOUNT].[PARENTH1].[US]","US","","000") the first parameter does not move with the expansion. Kindly help me with this as am not sure which EPM function enables it.
I appriciate all your inputs. We are on EPM 10.0 SP 12 Patch 9
Regards
Seyi Obabiyi

Hi Seyi,
You dont require any local members.
First column will represent the CURRENCY dimension.
In the second column, get the R_ACCOUNT dimension. In the memberset of this dimension, select "Dimension Property", then select the dimension as CURRENCY, and then select the property as R_ACCT.
Hope this helps.

Formula Field in Conversion File

Hi,
I have a scenario where I need to multiply the values of accounts of a particular entity (say entity External "9000", Internal "EntityA"). I have created a Conversion File as shown below
External Internal Formula
9000 EntityA Value*0.371996
Now when I upload the data file using this conversion file the data of 9000 directly goes into EntityA without the formula being applied. Why is that so? What is then the use of the Formula Column?
Thanks,
Prasanth.

Hi Patrick,
I did what you said. I added the following in the options section of the transformation file
CONVERTAMOUNTWDIM=LEGALENTITY
In the Conversion section I already had the reference to the conversion file as follows
Legalentity=entityconversion.xls
I add the second line
Amount=entityconversion.xls
When I process the transformation file with a datafile I get the following error messaga
"Index was outside the bounds of the array"
When I remove the line Amount=entityconversion.xls from the conversion section, the transformation file gets validated succesfully but the Formula value is not getting applied.
Any idea what could be wrong?
Thanks,
Prasanth.

BPC 10.0- Creating report using dimension property filter

Hi,
I created a new report in EPM addin for excel using the 'Filter Members by Properties' feature in the EPM Member Selector Window.
My requirement is as I add new members to my dimension with that property value , the report has to refresh and display the new member in the report.
The feature met my requirement and I saved the report.When I reopen the report, the filter that I had earlier used to create the report is hard coded with the members with those properties in the EPM selector Window.
As a result, when I add new Members to the dimension with that property , the report does not recognise that new member and my requirement does not meet.
Eg: I create report with Entity dimension across row axis and Product Dimension -filter on category = New across column axis
and save the report.
When I reopen the report, I see that in the EPM Member selector window, across column axis the members with Property Value Category= Y - Product A,Product B, Product E are hard coded and the filter has been auto removed.
So when I add a new member to my product dimension Product N with property Category= New, the report does not recognise this member.
Please help on how can I use this feature to meet my requirement.
Regards,
Sowmya

Hi,
It should work for newly created members which meets the requriement in member selector.
Member filtering by properties:
Select property, operator and Value and click Add Dynamic filter then in the right window you will be able to see as follows:
Member name Relation ship
<property>=<Value> Property
Hope it works,
Thanks,
Raju

How to use dimension property in REC statement?

Hi,
In dimension ACCOUNT I have created additional property ZACC where I store "alternative" account numbers.
After I load actuals from BW to "regular" accounts I want to copy values to "alternative" accounts.
Regular accounts are hierarchy nodes and alternative are base members.
ACCOUNT dim values looks like that:
ID     ZACC
A1     A.1
A2     A.2
A.1
A.2
etc.
I wrote code below for that but when I validate I get message:
UJK_VALIDATION_EXCEPTION:Invalid dimension "ACCOUNT].[ZACC" in model ZXC
*XDIM_MEMBERSET TIME=2012.01
*XDIM_MEMBERSET ZKEYFIGURE=ZBALANCE
*SELECT(%ACC%,"[ID]",ACCOUNT,"[ZACC]<>' '")
*FOR %AC%=%ACC%
*WHEN ACCOUNT
*IS BAS(%AC%)
*REC(ACCOUNT=[ACCOUNT].[ZACC])
*ENDWHEN
*NEXT
Can you suggest me how to fix my code?
Thanks,
Andrzej
Message was edited by: A Ksik

Hi Andzej,
I will try to explain in details. If we are talking about target member override in REC like:
*REC(EXPRESSION=%VALUE%,SOMEDIM=TARGETMEMBER,...)
TARGETMEMBER can be:
1. Some fixed single member
2. Variable like %VAR%, but this %VAR% will get the value from FOR/NEXT loop (simply duplicating lines of code).
Something like:
*WHEN SOMEDIM
*FOR %VAR%=MEM1,MEM2,MEM3 //lines between FOR and NEXT are duplicated
*IS %VAR%
*REC(EXPRESSION=%VALUE%,SOMEDIM=PREFIX%VAR%SUFFIX)
*NEXT
*ENDWHEN
Where PREFIX%VAR%SUFFIX - is the target containing fixed prefix or suffix and contents of %VAR%
The result of code processing this code will be evaluated to:
*WHEN SOMEDIM
*IS MEM1
*REC(EXPRESSION=%VALUE%,SOMEDIM=PREFIXMEM1SUFFIX)
*ENDWHEN
*WHEN SOMEDIM
*IS MEM2
*REC(EXPRESSION=%VALUE%,SOMEDIM=PREFIXMEM2SUFFIX)
*ENDWHEN
*WHEN SOMEDIM
*IS MEM3
*REC(EXPRESSION=%VALUE%,SOMEDIM=PREFIXMEM3SUFFIX)
*ENDWHEN
This code is VERY slow and ineffective!
In you case the code can be:
*FOR %AC%=%ACC% //list of nodes
//or *XDIM_MEMBERSET ACCOUNT=BAS(%AC%)
*WHEN ACCOUNT
*IS BAS(%AC%) //or * if XDIM
*REC(EXPRESSION=%VALUE%,ACCOUNT="PREFIX%AC%")
*ENDWHEN
*NEXT
but you will need special coding for target to support PREFIX
3. Member property containing correct member ID, like
SOMEDIM.SOMEPROPERTY
In this case the member property of the current record of WHEN/ENDWHEN loop will be used as a target.
Hope it's clear!
B.R. Vadim

Script logic using Dimension.Property

Hello, Gurus!
I have next problem with script logic:
Dimension Company
Company1
Company2...
Dimension Document
Document1
Document2...
Dimension Document has property PCompany, where there is Company ID.
I need to summation all data for Company=Company2 (for example).
How can I choose records from Dimension Document for PCompany=Company2 with BPC script logic?
Thanks!
Regards,
Svetlana.

Hello Gersh!
Thank you very much. It's worked.
I should clarify the question
I have several company which I choose with property of Company (for example, INTERCOMP=Y)
So, I have :
*SELECT(%COMPANY%,ID,COMPANY,INTERCOMP=Y)
*WHEN Document.PCompany
*IS %COMPANY%
*ENDWHEN
This construction doesn't work.
Regards,
Svetlana.

BPC Conversion File - Same External ID for different Dimensions

Hello Experts,
I hope you can help me.
We are running BPC NW V10.0 SP13
I have a Conversion File for External to Internal Mapping on the DATASRC Dimension.
See Image 01
I would now like to use the same 'External ID' to identify the mapping rules for two Dimensions, DATASRC and CATEGORY Member ID
See Image 02
The rules that determine how the External ID is mapped are subjective rather than derived from patterns present in ID. This means I cannot use any conditional logic to determine the mapping rules. For example, I cannot assume that all IDs that start with 99Z19 will need to be mapped the same way.
So the CATGORY Member ID needs to be hard-coded somehow.
Although it is simple enough to copy the entire worksheet and hold the mapping for each Dimension as separate w/sheets, this duplicates the amount of ongoing maintenance and turns 80 rules into 160 (a number which will rise!)
Is there a way of using javascript in the Formula column to identify the Internal Member ID for the CATEGORY Dimension.
If so, how would the Transformation File reference this?
Any help would be much appreciated

Sorry Vadim, I was having problems uploading the actual files.
So I have had to screenshot instead...............
Transformation File
Conversion File
As you can see, the Trans file assumes the CATEGORY is fixed to one Member.
But I want to use the External ID in the the DATASRC Conversion w/sheet and specify different CATEGORY Member IDs.

Using Dimension Formulas to sum data based on different criteria

Hi all,
I am trying to use a u201CDimension Formulau201D to perform the following calculation:
We have an account dimension which has 2 important properties:
1.     CRITERIUMTYPE: This property can have 3 different values: u201CWERKu201D, u201CINVu201D OR u201CLIQu201D
2.     ACCTYPE: This property can have 2 different values: u201CEXPu201D or u201CINCu201D
The client wants to have a report that sums data based on these 2 properties. An example will help to clarify this:
ACCOUNTS     CRITERIUMTYPE     ACCTYPE     VALUE
ACCOUNT A         WERK                          EXP               100 u20AC
ACCOUNT B         WERK                          INC               150 u20AC
ACCOUNT C         WERK                          EXP               200 u20AC
ACCOUNT D         WERK                          INC               300 u20AC
ACCOUNT E         INV                          EXP               50 u20AC
ACCOUNT F         INV                          INC               100 u20AC
ACCOUNT G         INV                          EXP               200 u20AC
ACCOUNT H         INV                          INC               500 u20AC
The clients wishes to see this data in the following way:
CRITERIUMTYPE     ACCTYPE     VALUE
   WERK                         EXP              300 u20AC
                                    INC              450 u20AC
   INV                         EXP              250 u20AC
                                 INC              600 u20AC
In order to achieve this I have created several new accounts, one for each combination e.g.: Account WERKEXP is used to sum the data on the combination CRITERIUMTYPE=WERK and ACCTYPE=EXP. I have created a dimension formula in my account dimension but this is where I am stuck. I have created the following formula to calculate the account WERKEXP:
IIF([BUDGETPOSITIE].CURRENTMEMBER.PROPERTIES("ACCTYPE")="EXP",IIF([BUDGETPOSITIE].CURRENTMEMBER.PROPERTIES("CRITERIUMTYPE")="WERK",[BUDGETPOSITIE].CURRENTMEMBER,0),0)
The problem with this formula is the following:
The formula will add all amounts that meet the 2 criteria mentioned in the formula, EXP and WERK, but as soon as it finds an accounts that does not match the 2 criteria it will set the account WERKEXP back to 0. I need to know if there is a way, using dimension formulas, of adding these values together without the new account being set to 0 as soon as one of the accounts it needs to check does not meet 1 of the 2 criteria.
We are working on SAP BPC 7.5 for NW with SP04
All help is very much appreciated!
Kind regards,
Stefano

Hi,
You can also use ParentHn property to have different grouping of accounts within the dimension.
So in your case rather using the member formula you can have four accounts and add them in the Parenthn property for grouping it.
1. The Solution proposed by Nilanjan is specific for a Report/IS and Performance will be good
2. My solution will be global something similar to MDX formula, but performance may be slightly lesser than using excel function.
Hope this helps,
Regards,
G.Vijaya Kumar

Expand Dimension using another dimension Property

Hi guys,
My template has Product in the Rows (User Defined) and Time in the Collums.
The Entity dimension is changed at the context, but I want Currency to show the value of the property "Currency" of Entity dimension.
I've tryed to do this putting Currency at the collum, and trying to filter it by Dimension Property, but I didnt succeed.
Any thoughts?
Thanks in advance.
Adriano Frossard

Hi Adriano,
Simply put currency in the page axis and in the EPMOlapMemberO formula use formula to get a property of entity. Read here: Static report in BPC NW 10
Vadim

Dimension property in Distribution List - BPC 7.0

Hi,
In BPC v7.0 MS, I would like to select members with an dimension property in Publishing range.
For example, with ACCOUNT dimension, I use the range : "ACCTYPE=EXP"
Is it possible ?
Regards,
Morgann

A Simple Answer is yes,
I have used SQL query to mbrAccount table.
Select * form mbrAccount where ACCTYPE ='exp'
If you need to get the data out some other way then please explain what is your need and how are you planning to use the data.
Hope this helps.
Sam

EAS7.1 aso dimension property change using rule file.

I have a outline having 1 dimension "Terms" as a account type and data storage as "data store".Now i am trying to load members using rule file.
Outline: ABC (Active Alias Table: Default)
Scenario Stored <2>
Currency Stored
Terms Accounts
Now i have ceated a rule file using source file like
"Terms","T1","Terms Hierarchies","~O","",""
"T1","TOT"," ","~O","",""
"T1","OTH","","~O","",""
"OTH","Loaded Days","","~","",""
"OTH","Loaded FX","","~","","Loaded.FX",""
"TOT","R99"," ","~ "," "," "
"R99","R90","","+ "," "," "
"R90","R901","","+ "," "," "
i am using parent child relationship and i hav cheched the option s
like "allow property changes" and allow formula changes....in dimension build settings..the rule shows valid ..but during dimension member load it is giving me the folowing error
"\\Outline verification errors:
\\Member Terms has no value source. Aggregate storage outlines require non level-0 members in accounts dimension to be either non-stored members or have internal/external formula.
\\Member [Terms] has an unspecified error.
but if i am removing "~O" property with "O" only in data source file then the dimension member load is suuccessful...
wat i feel is anyhow the "dimension property change is not being set"...
can any one please tellme wat option i m missig to check in rule file..??
your opinion and suggestion will be highly appreciated.....

The documentation explains the difference with examples, now I was going to post the link but I might as well post the info from the link.
Joining Fields
You can join multiple fields into one field. The new field is given the name of the first field in the join. For example, if a data source has separate fields for product number (100) and product family (-10), you must join the fields (100-10) before loading them into the Sample.Basic database.
Creating a Field by Joining Fields
You can join fields by placing the joined fields into a new field. This procedure leaves the original fields intact. Creating a field is useful if you need to concatenate fields of the data source to create a member.
For example, if a data source has separate fields for product number (100) and product family (-10), you must join the fields (100-10) before you load them into the Sample.Basic database. If, however, you want to preserve the two existing fields in the data source, you can create a field (100-10) using a join. The data source now includes all three fields (100, -10, and 100-10).
For other rule options read - http://download.oracle.com/docs/cd/E17236_01/epm.1112/esb_dbag/ddlfield.html
Cheers
John
http://john-goodwin.blogspot.com/

Script Logic: Using a property in MDX *REC statement (BPC NW)

Hi,
Is it possible to use a Property in an MDX statement without using *LOOKUP() function? I have script successfully working but it takes 15 minutes to execute and would like to speed it up.
I understand that [DIMENSION].[MEMBER].Property is not valid syntax, and do not believe NW has any other functions to resolve the issue, except *LOOKUP which takes a long time.
Specific Example is below:
I have a piece of script that successfully splits JV Expense by customers. A Profit Share planning driver determines the percentage that each customer is entitled to. Typically this will be 100%, but could be 50% between two customers.
The PROFIT SHARE planning drivers records, and PARTNER_INCOME transactional records are below:
ACCOUNT
ENTITY
PARTNER
SIGNED DATA
PROFIT_SHARE
UK_001
PARTNER_A
0.5
PROFIT_SHARE
UK_001
PARTNER_B
0.5
PROFIT_SHARE
UK_002_PLANNING_DRIVERS
PARTNER_B
1.00
PARTNER_INCOME
UK_001
NO_PARTNER
$5,000
PARTNER_INCOME
UK_002
NO_PARTNER
$5,000
UK_001 has two partners that are each entitled to 50% of the $5,000 NET PROFIT.
For UK_002, one one single Partner is entitled to 100% of the $5,000 NET PROFIT.
Using script logic, you can scope the Profit Share account (PROFIT_SHARE) - , and use a *REC statement to multiply this by the driver. It would look like:
*XDIM_MEMBERSET ACCOUNT = PROFIT_SHARE
*WHEN ACCOUNT
IS *
*REC (EXPRESSION = %VALUE% * ([ACCOUNT].[PROFIT_SHARE],[PARTNER].[NO_PARTNER]), ACCOUNT = PARTNER_PROFIT_SHARE)
*ENDWHEN
This wouldn't be a problem if the Planning Driver is always stored on the same Entity that the Income is stored on, but for UK_002, the planning driver is stored on another Entity - which is stored in a the PLAN_DRIVER_REF property of the entity. It should use UK_002_PLAN_DRIVERS
ID (Entity)
PLAN_DRIVER_REF
UK_001
UK_002
UK_002_PLAN_DRIVERS
UK_002_PLANNING_DRIVERS
In this scenario, we need to switch out the Entity used in the MDX, however I do not believe you can use a property in MDX - can anyone confirm?
I have currently implemented the *LOOKUP functionality to loop through, changing each *LOOKUP partner for each loop.
Lookup:
*LOOKUP PLANNING_JV_US
*FOR %LOOP_ASLS% = %ASL_LOOKUP_LOOP_VARIABLE%
*DIM LOOK_%LOOP_PARTNERS%:ACCOUNT = "PROFIT_SHARE"
*DIM LOOK_%LOOP_PARTNERS%:PARTNER= %LOOP_PARTNERS%
*NEXT
*DIM ENTITY = ENTITY.PLAN_DRIVER_REF                   //   Use PLAN_DRIVER_REF Property of Entity
*ENDLOOKUP
Scope and *REC:
*XDIM_MEMBERSET ACCOUNT = PROFIT_SHARE
*WHEN ACCOUNT
IS *
*FOR %LOOP_PARTNERS% = %PARTNER_LOOKUP_LOOP_VARIABLE%      // 1000 Partners
*REC(EXPRESSION = %VALUE% * LOOKUP(LOOK_%LOOP_PARTNERS%), PARTNER= %LOOP_PARTNERS%, ACCOUNT = TCOJVSHAR_CALC, AUDIT_ID = PP_EXPENSE_BY_PARTNER)
*NEXT
*ENDWHEN
The problem with the above, is that because the Lookup is being generated for every single Partner, there are significant numbers of loops.
Does anyone know of another way this can be implemented in Script Logic? Otherwise we'll need to explore BAdI route.
Thanks,
Nick

Hi Nick,
Use property in LOOKUP - will dramatically speed up the calculation without FOR/NEXT.
Vadim

Using dimension type u2018Subtableu2019 in BPC

Does anyone know about using dimension type u2018subtableu2019? Has anyone ever used it?
Thanks in advance
Nitin

The sort answer is - No - you need not use it if you don't want to.
In the application, the normal transactions would have some u2018catch allu2019 dimension member such as u2018noaccountu2019 assigned to them for this subtable dimension. You donu2019t have to use this subtable dimension since the same can be achieved by using other regular dimensions as well. However if you are not using the stored procedure, you can write SQL logic to accomplish the same. Alwyn Berkhout has given a good example of one such SQL code in an earlier thread in this forum. It is as follows:
*SELECT(%OPENINGACCOUNTS%,"ID",ACCOUNT,OPENINGACCOUNT_PROPERTY'')
*XDIM_MEMBERSET TIME = 2006.DEC
*XDIM_MEMBERSET SUBTABLES = F_CLO
*XDIM_MEMBERSET ACCOUNT = %OPENINGACCOUNTS%
*WHEN SUBTABLES
*IS "F_CLO"
*WHEN ACCOUNT
*IS %OPENINGACCOUNTS%
*REC(FACTOR=1,TIME="2006.JAN",SUBTABLES="F_OPE"
*ENDWHEN
*ENDWHEN
*COMMIT
You can read more about this at Carry forward opening balances
Regards
Pravin

BPC: Conversion File Formulas

Hi all,
Would appreciate your help with the following scenario...
I have a conversion file that converts account ID's, however if it has a certain External account number I would like to use a formula to go pick up a property from the Entity Dimension and use that property value as the Internal Account.
I am hoping I can use the Formula column, but currently I have limited expericence with entering formulas on Conversion files.
I am very appreciative of any formula samples.
Many Thanks,
Brian

Brian,
Unless another user has the correct script and I have never used it, I don't think the process you have in mind is an available conversion technique. Since the conversion file is basically a 2 column replacement process sheet, you should be able to copy the members into the conversion sheet, execute a property lookup using evpro, and then copy-paste-value to convert the properties to text that would be used in the conversion process. The only downside is that this would need to be performed after any property changes or updates to the dimension file.
In addition, I would suggest logging this as an enhancement request with support; I think that this has been requested in the past, but if it is a very useful tool, then product development should see a case for adding the functioality to BPC
Thanks.

Master data loading - Dimension Property value incorrect

Hi,
I have a dimension in BPC which has an attribute amount.
When am trying to load the master data from BW, the number is truncated and displayed with a * if the number has more than 6 digits.
If this is a problem with the delimited - comma - then it should not bring in the values even with one punctuation (e.g. 6,000) but strangely it's happening only for 6 digits or more.
e.g. 19,605,500.00 -> *05500.00
This is master data (estimate field) and is not used for calculations/planning.
I tried the following but nothign worked.
1) Removing commas using a script in the conversion file
js:%external%.toString().replace(",","")
2) Removing the delimiter in the transformation file and making comma as decimal point.
DELIMITER =
AMOUNTDECIMALPOINT = ,
Let me know if you have any ideas to resolve this.
Thanks,
Vasu
Thanks,
Vasu

Hi Vasu,
The field in your BW is 17,2 which I am assuming is a decimal value of 17 digits long with 2 digits after the decimal point. Your property of 40 characters should have plenty of room to fit any value so something else is wrong. Can you please validate the transformation and conversion files with this data?
I highly recommend validating the transformation and conversion files with the new external data. In my experience most of the time when there is a problem in mapping the external data the transformation and/or conversion files do not validate successfully and they generate useful diagnostics.
Regards,
Leila Lappin

BPC : Using Dimension Property in Formula of a Conversion File

Similar Messages

Maybe you are looking for