BPC: EvDre filter on dimension properties

Hy, I'm having some problem building an "aggregate" evdre.
I've to produce a report showing data from two or more entity basemembers choosed on the base of the area_manager property value, so I'm trying to generate the members list using EvEne, EvSet and EvPxr
this are my formulas:
EVSET("COAN";"TotSocieta";"EVBAS";;VERO;EVPXR("PDV";"AREA_MANAGER";"TotSocieta") & "=""RIGHINI""")
gives me this filter
Filter({Hierarchize(Descendants([PDV].[TotSocieta],999,LEAVES))},[PDV].[TotSocieta].Properties("AREA_MANAGER")="RIGHINI")
the evene (g10 refers to EVSET("COAN";"TotSocieta";"EVBAS";;VERO;EVPXR("PDV";"AREA_MANAGER";"TotSocieta") & "=""RIGHINI""") )
EVENE("COAN";C30:C31;D30:D31;G10)
EvEne returns TRUE, but when expanding it gives #NODATA.
the property name is correct and there are base members with te value specified.
Can anyone give me some suggestion?
Thankyou in advace!
Letizia

I do not understand how you're trying to do this in an EvDRE, since I see EVENE in your example.
Please see my examples here, which may help you resolve your issue.
Re: Custom EV function
and
here:
http://forums.sdn.sap.com/click.jspa?searchID=-1&messageID=9341550
Please note, if you are trying to "aggregate" you might need to do this with a parent heirarchy instead. Properties are good for to bring back all members that are flagged with a specific property, but not summarize. You likely need a parent heirarcy if you want to summarize.
Greg

Similar Messages

Script calculation for dimension properties

Dear Experts,
I am using BPC 7.0NW,
My code in Default.lgf:
*BEGIN
[P_ACCT].[#B] = [P_ACCT].[A]* [P_ACCT].[C]
*END
Now, I want to run this calculation for dimension property wise.
LIke i want to add dimension properties in above calculations.
And how do i put "IF" conditions?
Please help me ...
Thanks alot in advance.....!

Kumar,
follow next steps:
1. Create new logic file and name it "TEST" for example
2. Use next coding in it:
*XDIM_MEMBERSET P_ACCT = YOUR_P_ACCT_MEMBER
*IS "YOUR_PROPERTY_VALUE"
*REC(EXPRESSION=%VALUE%,TIME="2010.MAR")
*ENDWHEN
*COMMIT
3. Validate and save your TEST.LGF
4. Insert next coding into DEFAULT.LGF
*INCLUDE ADD.LGF
5. Validate and save DEFAULT.LGF
Put your values insted of "YOUR_P_ACCT_MEMBER", "YOUR_PROPERTY_VALUE"
This coding works for sure.
U can use ABAP in script logic. The mechanism is described here:
http://help.sap.com/saphelp_bpc70sp02/helpdata/en/a1/532226947C49A5B2E2BD32450CB2D1/frameset.htm
Hope that was helpful,
Dzmitry

SSRS MDX Query Dimension Properties Missing

I have been stumped on this for a few days thought I'd throw this out here. I've read every related article in the forum regarding MDX Queries and Dimension Properties in SSRS Report Developer and haven't found a case exactly like this with a solution that
works.
Environment is SQL 2012 SP1 Cum update 5
I am doing a rather generic query out of MS Project Servers OLAP cube and I can't get the dimension properties to show up in the flattened output for my dataset. See below.
SELECT
NON EMPTY { [Measures].[FTE est] } ON COLUMNS,
NON EMPTY {
[Value_Stream_Project].[Value_Stream_Project].ALLMEMBERS *
[Project Status_Project].[Project Status_Project].ALLMEMBERS *
DESCENDANTS([Project List].[Project List Level 02].ALLMEMBERS)*
DESCENDANTS([ProjectManager_Project].[ProjectManager_Project Level 02].ALLMEMBERS) *
[Planner_Project].[Planner_Project].ALLMEMBERS *
[Time].[Month].ALLMEMBERS
DIMENSION PROPERTIES
MEMBER_CAPTION,
MEMBER_UNIQUE_NAME,
PARENT_UNIQUE_NAME,
LEVEL_NUMBER ,
[Project List].[Project List Level 02].[Start Date],
[Project List].[Project List Level 02].[Finish Date]
ON ROWS
FROM (
SELECT ( STRTOMEMBER(@FromTime, CONSTRAINED) : STRTOMEMBER(@ToTime, CONSTRAINED) ) ON COLUMNS
FROM (
SELECT ( STRTOSET(@RBSResource, CONSTRAINED) ) ON COLUMNS
FROM (
SELECT ( STRTOSET(@ProjectStatusProject, CONSTRAINED) ) ON COLUMNS
FROM (
SELECT ( STRTOSET(@ValueStreamProject, CONSTRAINED) ) ON COLUMNS
FROM [MSP_Portfolio_Analyzer]))))
My issue is the [Project List Level 02] dimension Properties (below) are not showing up in the Query designer output, aren't being generated as fields in the dataset and can't be referenced as a property in an expression (i.e. Fields!Project_List("Start
Date") )
[Project List].[Project List Level 02].[Start Date],
[Project List].[Project List Level 02].[Finish Date]
The odd part is if I change the above two rows in my query to this :
[Project List].[Start Date],
[Project List].[Finish Date]
The Query designer shows the properties in the output but leads to 2 other issues,
1) I have to modify the generated Dataset field values to remove the [Project list Level 02] in the Level unique name like this
Before<?xml version="1.0" encoding="utf-8"?><Field xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xsi:type="MemberProperty" PropertyName="Project List - Start Date" LevelUniqueName="[Project List].[Project List Level 02]" />
After
<?xml version="1.0" encoding="utf-8"?><Field xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xsi:type="MemberProperty" PropertyName="Project List - Start Date" LevelUniqueName="[Project List]" />
2) I have to restrict my cross join to only the current level (Level 02) or it expands the results to the parent hierarchy of the Project List dimension and skews my measure summaries.
I've tested the query in SSMS directly and the properties are showing up just fine for those dimensions using the original syntax.
Any help would be appreciated.

Hi there,
Which data source provider are you using? Are the connection strings used in SSMS the same as SSRS? Doing a profiler trace against Analysis Services might point to differences in how the connection is made or query is parsed.
This may help.
http://www.sqlchick.com/entries/2011/10/23/pros-cons-of-using-the-ole-db-provider-for-ssas-100-when-rep.html
Did you try using With clause to make a friendly name for the member properties?
http://melick-rajee.blogspot.ca/2012/04/how-to-get-member-properties-in-mdx.html
cheers,
Andrew
Andrew Sears, T4G Limited, http://www.performancepointing.com

Combo box in "Filter by Custom Properties"

Hi to all,
I create some custom metadata properties properties in order to classifie the documents in KM.
This metadata properties has a set of Allowed Values, so the value is selectable with a combo-box in Detail box of KM.
Now I have to enable the Filter by Custom Properties with the combobox in place of textfields.
How to do?
Regards,
Giampaolo

What you want is not the Filter by Custom Properties but the Filter by Predefined Properties.
In you search options configuration add your properties to the predefined properties list and you'll get your combo-box.
To configure your search options go to:
System Administration -> System Configuration -> Knowledge Management -> Content Management -> User Interface -> Search -> Search Options Set

BPC7.5NW: How to increase default Dimension Properties length

Hi Experts,
May I know if it is possible to increase the maximum length of default dimension properties, such as ID and EvDescription? I know we can set the property length in "Modify Dimension Property". However, I don't see those default dimension properties under this functionality, in my case, the ID.
Please advice.
Regards,
Kenneth

Hi,
No! you can not change Ienghts of all properties. If the dimension is standard then you can not change any of the standard properties. If the dimension is user defined then you can not change ID,Description and Scaling.
Default length for ID is 20 chars and Description is 60 chars.
Regards,
Raju

Using dimension properties in LOOKUP

Hi,
I'm trying to use dimension properties in a LOOKUP, but when I execute the script the log tells me that COMPANY, SALESORG, PRODUCT and TRANSCURRENCY is not defined and therefore create a lookup on all members.
THe usage of properties in LOOKUP is described in the documentation, but somehow it doesn't seem to work for me. Can anyone help me?
*LOOKUP ACTIVITYPLAN
*DIM FCIC:ACCOUNT= "FULLCOST"
*DIM FCIC:PARTNER="I_NONE"
*DIM FCIC:COMPANY=PARTNER.ENTITY
*DIM FCIC:SALESORG=PARTNER.ENTITY
*DIM FCIC:PRODUCT=PRODUCT.PRODREF
*DIM FCIC:TRANSCURRENCY=PARTNER.CURRENCY
*DIM COUNTRY = "CO_NONE"
*DIM DATASOURCE = "INPUT"
*DIM PROFITCENTER = "YB99"
*DIM RPTCURRENCY = "LC"
*ENDLOOKUP
Regards,
Lars
Edited by: Lars Johansen on Nov 4, 2011 10:41 AM
Edited by: Lars Johansen on Nov 4, 2011 10:41 AM

Hi Gersh,
I'm getting closer. I have now tried to use the FOR/NEXT logic on 1 property and it works. I know want to include another. In this case it seems as if the LOOKUP works fine, but the WHEN/REC/ENDWHEN is not. It doesn't recognize my LOOKUP(%LOOP_CU%%LOOP_CO%).
Any suggestions have to solve this problem?
*LOOKUP ACTIVITYPLAN
*FOR %LOOP_CO% = %P_COMP%
    *FOR %LOOP_CU% = %P_CURR%
        *DIM %LOOP_CU%%LOOP_CO%:TRANSCURRENCY=%LOOP_CU%
        *DIM %LOOP_CU%%LOOP_CO%:ACCOUNT= "FULLCOST"
        *DIM %LOOP_CU%%LOOP_CO%:PARTNER="I_NONE"
        *DIM %LOOP_CU%%LOOP_CO%:COMPANY=%LOOP_CO%
        *DIM %LOOP_CU%%LOOP_CO%:SALESORG=%LOOP_CO%
        *DIM %LOOP_CU%%LOOP_CO%:PRODUCT=PRODUCT.PRODREF
    *NEXT
*NEXT
*ENDLOOKUP
*WHEN ACCOUNT
   *IS "QPURC"
               *FOR %LOOP_CU%=%P_CURR%
                   *REC(EXPRESSION=(%VALUE%*LOOKUP(%LOOP_CU%%LOOP_CO%)),ACCOUNT="529996")
                   *END
               *NEXT
*ENDWHEN

Account Dimension Properties

Hi,
I have some questions concerning Account dimension properties:
1. "EnableCustom1Aggr"--->Whether aggregation is enabled for intersections of the Account and Custom dimensions This attribute is used for special totals, not summing. Specify Y if the account can aggregate with Custom dimensions or N if it cannot. does this mean that by default summing is working?
2."EnableDataAudit"---> what does it mean to have an audited account or scenario?
3. did anyone try member name that have space character on oracle database.
4.what is the use of plug accounts.
Thanks,
foksh

does this mean that by default summing is working?
The account rollup is summing by default, but if you do not have the EnableCustomAggr checked, the Custom dimension members will show nothing.
"EnableDataAudit"---> what does it mean to have an audited account or scenario? will allow you to see changes made to that account from the Tasks Folder -> Data Audit option.
what is the use of plug accounts. R/= This are were you usually store the difference between your Intercompanies.
Using spaces in member names is not recommended, try undercores _

Description on Essbase Account Dimension Properties

Hi everyone! I am a newbie on Oracle Hyperion and Essbase. I joined a company as a trainee software developer. And my role is to support my superiors in developing Planning and Budget Applications for Plantations of our company.
I tried my best to find places in internet where I can improve my knowledge in the application but there is no place I found as free since my company is not ready to give good professional training. so I decided to choose the forum where I guess I would get help.
My first question to ask is about Account Dimensions Properties,+_ what they do, what are their uses, what for an account type is used, where time balance is used etc.
Edited by: 930603 on Apr 27, 2012 10:51 AM

Hi,
Welcome to the world of Hyperion first i suggest you to start reading the essbase dbag, it will help you to understand what exactly the product do and also help you to understand the best optimum solution for your design & implementation
for Account Dimensions Properties
http://docs.oracle.com/cd/E17236_01/epm.1112/esb_dbag/frameset.htm?dotattrs.htmlThanks,
Avneet Singh Bhatia

Dimension Properties

The Dimension Properties and the columns in Dimension members are Not in match. As I can add my own columns in the Dimension members directly.
Then why should I defined the Dimension peroperties at the first place?

You can add whatever columns into your dimension sheet but they are not going to be a dimension property that you can access from logic or member lookup. That is why you must defined property for dimension independently.

Xcelsius fileter on dimension properties

Hi,
pls let me know whether it is possible to filter dimension according dimension property in Xcelsius.
If its possible please share the steps for filtering. I want to filter data according to dimension not included in Dashboard row and column domension.
Regards
Raman

Hi,
When you are creating dimensions for your application set, the following for any one dimension is important
u2022 The maximum number of fields in a table (a dimension = 1 table) is 1024.
u2022 The maximum record size is 8064 bytes (a record = 1 row in a table)
In BPC a field equals a property. So there can be maximum of 1024 properties in a dimension. Now, the factors impacting are:
1. The number of levels defined. SQL Server creates a set of properties for each level within the dimension. if you have 10 properties and 4 levels in your dimension, your total number of fields is 40.
2. The size of the record. To determine record size you have to figure out the number of bytes (a byte equals a character) in each level. Since levels are repeated you only need to figure out the number of bytes in the first level and then multiply that number by the number of levels. To come up with the total number of bytes for a level you simply add up the field size for each field and multiply it by 2 (1 character= 2 bytes).
Hope this helps.
Edited by: nilanjan chatterjee on Feb 8, 2010 4:25 PM

BPC - EVDRE error - values on YEAR level do not appear

Hi everyone.
I have a Time dimension with YEAR, QUARTER and MONTH level.
When I do an EVDRE report and I select an especific YEAR (ex. 2011) and I set the MemberSet Expansion to SELF, it didn´t bring any value.
On the other hand, when I set SELF, DEP or even SELF,DEP,BAS, the values on the QUARTER and MONTH cells appear just fine!
PS: The Option SumParent is blank.
I've done a test with EVGET, selecting TIME:2011, and it brings the value with no problem. So this proves that the Time Hierarchy is working fine, and the problem is on EVDRE.
Any sugestions?
Thanks in advance.

Hi,
what is your BPC verion & patch ?
I also facing similar issue(bpc7.5nw sp10) i'm getting only at base level, not at parent level(quarter/year).
In your case quarter is working.

Proper formatting for dimension properties in SQL script logic

Hi all,
I'm trying to pass the time member from a property in account dimension. (Post recognized revenue by looking at deferred revenue accounts.) The dimension ACCTREV has a property called DATENAME. DATENAME refers to a valid TIME member. In 4.2 this logic worked fine. In 5.1sp3 it's not passing the correct time period (formula log indicates null value for time member).
For example: ACCTREV = 4101Billing_2008.JUN DATENAME = 2008.JUN (DATENAME is a property of ACCTREV)
Here's the logic: *REC(EXPRESSION=%VALUE%,TIME=ACCTREV.DATENAME,ACCTREV=ACCTREV.ACCT)
I've read the other post indicating brackets are required by SQL when passing parameters that contain delimiters like "." but it doesn't say how to do it!
I've tried TIME=ACCTREV.DATENAME resulting in null time members.
I've tried TIME=ACCTREV.DATENAME resulting in null time members.
I've updated the property value to 2008.JUN with TIME=ACCTREV.DATENAME resulting in null time members.
Also how do you post a thread using a bracket without turning it into a hyperlink?
Any help would be greatly appreciated.
Edited by: Ara Toroyan on Aug 5, 2008 2:24 AM

Thanks Kranthi,
It's still not working.
I believe the problem is SQL 2005 related and the DATENAME "2008.JUN."
ACCT is a property of ACCTREV and the properties refer to valid ACCTREV members.
DATENAME is a property of ACCTREV and refers to valid TIME members-- not TimeID or UserTimeID
The formula log reveals the correct ACCTs but no TIME (null values). The problem is with DATENAME. Closer inspection of the formula log below shows that Query1 doesn't load DATENAME. (Not sure why but this could be because of improper formatting.)
I've validated the existence of all property values with =EVPRO. The values are part of the dimension tables.
Here's the forumula log: (I've deleted some of the product and time members in the log for brevity.)
Number of logic calls:1
Call no. 1, logic:D:\BPC\Data\WebFolders\SecondTry\REVENUE
..\AdminApp\REVENUE\RevRec.LGX
Building sub-query 1
Query Type:0
Max members:
Region:
DIMENSION:ACCTREV
4101BILLING_2008.JUN,4201BILLING_2008.JUN,4206BILLING_2008.JUN,4207BILLING_2008.JUN,4208BILLING_2008.JUN
DIMENSION:CATEGORY
ACTUAL
DIMENSION:PRODUCT
0000,0001,0005,0010,0011,0012,0013,0020,0024,0030,0031,0040,0050,0059,0065,0066,0067,0070,0071,0075,0078,0079,0080,0099,0140,0145
DIMENSION:REVDATA
REV_AMOUNT
DIMENSION:TIME
2001.JAN,2001.FEB,2001.MAR,2001.APR,2001.MAY,2001.JUN,2001.JUL,2001.AUG,2001.SEP,2001.OCT,2001.NOV,2001.DEC,2002.JAN,2002.FEB,2002.MAR,2002.APR,2002.MAY,2002.JUN,2002.JUL,2002.AUG,2002.SEP,2002.OCT,2002.NOV,2002.DEC,2003.JAN,2003.FEB,2003.MAR,2003.APR,2003.MAY,2003.JUN,2003.JUL,2003.AUG,2003.SEP,2003.OCT,2003.NOV,2003.DEC,2004.JAN,2004.FEB,2004.MAR,2004.APR,2004.MAY,2004.JUN,2004.JUL,2004.AUG,2004.SEP,2004.OCT,2004.NOV,2004.DEC,2005.JAN,2005.FEB,2005.MAR,2005.APR,2005.MAY,2005.JUN,2005.JUL,2005.AUG,2005.SEP,2005.OCT,2005.NOV,2005.DEC,2006.JAN,2006.FEB,2006.MAR,2006.APR,2006.MAY,2006.JUN,2006.JUL,2006.AUG,2006.SEP,2006.OCT,2006.NOV,2006.DEC,2007.JAN,2007.FEB,2007.MAR,2007.APR,2007.MAY,2007.JUN,2007.JUL,2007.AUG,2007.SEP,2007.OCT,2007.NOV,2007.DEC,2008.JAN,2008.FEB,2008.MAR,2008.APR,2008.MAY,2008.JUN,2008.JUL,2008.AUG,2008.SEP,2008.OCT,2008.NOV,2008.DEC,2009.JAN,2009.FEB,2009.MAR,2009.APR,2009.MAY,2009.JUN,2009.JUL,2009.AUG,2009.SEP,2009.OCT,2009.NOV,2009.DEC
Loading ACCTREV.DATEID,ACCT
Loading TIME.TIMEID
Time to load properties:0.0 sec.
select ACCTREV,PRODUCT,TIMEID,COMPANY,CUSTOMER,DATASRC,LOCATION,MEDIAID,PRODTYPE,TRANSID,SIGNEDDATA
into #tblTempLogic_349866
from tblFactREVENUE
WHERE ACCTREV in (N'4101BILLING_2008.JUN',N'4201BILLING_2008.JUN',N'4206BILLING_2008.JUN',N'4207BILLING_2008.JUN',N'4208BILLING_2008.JUN') AND CATEGORY=N'ACTUAL' AND PRODUCT in (N'0000',N'0001',N'0005',N'0010',N'0011',N'0012',N'0013',N'0020',N'0024',N'0030',N'0031',N'0040',N'0050',N'0059',N'0065',N'0066',N'0067',N'0070',N'0071',N'0075',N'0078',N'0079',N'0080',N'0099',N'0140',N'0145',N'0154',N'0155',N'0156',N'0157',N'0161',N'0162',N'0163',N'0164',N'0165',N'0171',N'0175') AND TIMEID in (N'20010100',N'20010200',N'20010300',N'20010400',N'20010500',N'20010600',N'20010700',N'20010800',N'20010900',N'20011000',N'20011100',N'20011200',N'20020100',N'20020200',N'20020300',N'20020400',N'20020500',N'20020600',N'20020700',N'20020800',N'20020900',N'20021000',N'20021100',N'20021200',N'20030100',N'20030200',N'20030300',N'20030400',N'20030500',N'20030600',N'20030700',N'20030800',N'20030900',N'20031000',N'20031100',N'20031200',N'20040100',N'20040200',N'20040300',N'20040400',N'20040500',N'20040600',N'20040700',N'20040800',N'20040900',N'20041000') AND REVDATA=N'REV_AMOUNT'
insert into #tblTempLogic_349866 (ACCTREV,PRODUCT,TIMEID,COMPANY,CUSTOMER,DATASRC,LOCATION,MEDIAID,PRODTYPE,TRANSID,SIGNEDDATA)
select ACCTREV,PRODUCT,TIMEID,COMPANY,CUSTOMER,DATASRC,LOCATION,MEDIAID,PRODTYPE,TRANSID,SIGNEDDATA
from tblFactWBREVENUE
WHERE ACCTREV in (N'4101BILLING_2008.JUN',N'4201BILLING_2008.JUN',N'4206BILLING_2008.JUN',N'4207BILLING_2008.JUN',N'4208BILLING_2008.JUN') AND CATEGORY=N'ACTUAL' AND PRODUCT in (N'0000',N'0001',N'0005',N'0010',N'0011',N'0012',N'0013',N'0020',N'0024',N'0030',N'0031',N'0040',N'0050',N'0059',N'0065',N'0066',N'0067',N'0070',N'0071',N'0075',N'0078',N'0079',N'0080',N'0099',N'0140',N'0145',N'0154',N'0155',N'0156',N'0157',N'0161',N'0162',N'0163',N'0164',N'0165',N'0171',N'0175',N'0181',N'0182',N'0183',N'0185',N'0190',N'0200',N'0201',N'0210',N'0251',N'0275',N'0302',N'0305',N'0310',N'0802',N'1000',N'1002',N'1012',N'1016',N'1017',N'1026',N'1030',N'1033',N'1035',N'1041',N'1042',N'1054',N'1055',N'1059',N'1061',N'1062',N'1063',N'1065',N'1069',N'1073',N'1080',N'1082',N'1093',N'1100',N'1111',N'1120',N'1172',N'1210',N'1300',N'1700',N'1701',N'1800',N'1900',N'2082',N'2092',N'2110',N'2115',N'2118',N'2120',N'2121',N'2123',N'2124',N'2126',N'2136',N'2140',N'2150',N'2160',N'2170',N'2200',N'2201',N'2220',N'2225',N'2300',N'2500',N'2600',N'2611',N'2700',N'2701',N'2712',N'2715') AND TIMEID in (N'20010100',N'20010200',N'20010300',N'20010400',N'20010500',N'20010600',N'20010700',N'20010800',N'20010900',N'20011000',N'20011100',N'20011200',N'20020100',N'20020200',N'20020300',N'20020400',N'20020500',N'20020600',N'20020700',N'20020800',N'20020900',N'20021000',N'20021100',N'20021200',N'20030100',N'20030200',N'20030300',N'20030400',N'20030500',N'20030600',N'20030700',N'20030800',N'20030900',N'20031000',N'20031100',N'20031200',N'20040100',N'20040200',N'20040300',N'20040400',N'20040500',N'20040600',N'20040700',N'20040800',N'20040900',N'20041000',N'20041100',N'20041200',N'20050100',N'20050200',N'20050300',N'20050400',N'20050500',N'20050600',N'20050700',N'20050800',N'20050900',N'20051000',N'20051100',N'20051200',N'20060100',) AND REVDATA=N'REV_AMOUNT'
and SOURCE = 0
insert into #tblTempLogic_349866 (ACCTREV,PRODUCT,TIMEID,COMPANY,CUSTOMER,DATASRC,LOCATION,MEDIAID,PRODTYPE,TRANSID,SIGNEDDATA)
select ACCTREV,PRODUCT,TIMEID,COMPANY,CUSTOMER,DATASRC,LOCATION,MEDIAID,PRODTYPE,TRANSID,SIGNEDDATA
from tblFAC2REVENUE
WHERE ACCTREV in (N'4101BILLING_2008.JUN',N'4201BILLING_2008.JUN',N'4206BILLING_2008.JUN',N'4207BILLING_2008.JUN',N'4208BILLING_2008.JUN') AND CATEGORY=N'ACTUAL' AND PRODUCT in (N'0000',N'0001',N'0005',N'0010',N'0011',N'0012',N'0013',N'0020',N'0024',N'0030',N'0031',N'0040',N'0050',N'0059',N'0065',N'0066',N'0067',N'0070',N'0071',N'0075',N'0078',N'0079',N'0080',N'0099',N'0140',N'0145',N'0154',N'0155',N'0156',N'0157',N'0161',N'0162',N'0163',N'0164',N'0165',N'0171',N'0175',N'0181',N'0182',N'0183',N'0185',N'0190',N'0200',N'0201',N'0210',N'0251',N'0275',N'0302',N'0305',N'0310',N'0802',N'1000',N'1002',N'1012',N'1016',N'1017',N'1026',N'1030',N'1033',N'1035',N'1041',N'1042',N'1054',N'1055',N'1059',N'1061',N'1062',N'1063',N'1065',N'1069',N'1073',N'1080',N'1082',N'1093') AND TIMEID in (N'20010100',N'20010200',N'20010300',N'20010400',N'20010500',N'20010600',N'20010700',N'20010800',N'20010900',N'20011000',N'20011100',N'20011200',N'20020100',N'20020200',N'20020300',N'20020400',N'20020500',N'20020600',N'20020700',N'20020800',N'20020900',N'20021000',N'20021100',N'20021200',N'20030100',N'20030200',N'20030300',N'20030400',N'20030500',N'20030600',N'20030700',N'20030800',N'20030900',N'20031000',N'20031100',N'20031200',N'20040100',N'20040200',N'20040300',N'20040400',N'20040500',N'20040600',N'20040700',N'20040800',N'20040900',N'20041000',N'20041100',N'20041200',N'20050100',N'20050200',N'20050300',N'20050400',N'20050500',N'20050600',N'20050700',N'20050800',N'20050900',N'20051000',N'20051100',N'20051200',N'20060100') AND REVDATA=N'REV_AMOUNT'
select tmpTable.ACCTREV,tmpTable.PRODUCT,tmpTable.TIMEID,tmpTable.COMPANY,tmpTable.CUSTOMER,tmpTable.DATASRC,tmpTable.LOCATION,tmpTable.MEDIAID,tmpTable.PRODTYPE,tmpTable.TRANSID,sum(SIGNEDDATA) as SIGNEDDATA
from #tblTempLogic_349866 as tmpTable
group by tmpTable.ACCTREV,tmpTable.PRODUCT,tmpTable.TIMEID,tmpTable.COMPANY,tmpTable.CUSTOMER,tmpTable.DATASRC,tmpTable.LOCATION,tmpTable.MEDIAID,tmpTable.PRODTYPE,tmpTable.TRANSID
drop table #tblTempLogic_349866
Time to load Source data:2.6 sec.
29123 records to process
Time to Prepare data process:0.0 sec.
Time to initialize destination:0.0 sec.
Time to get source data:0.0 sec.
29123 scanned records
0 skipped records
29123 processed records
29123 records generated
Time to Scan data:5.5 sec.
Time to get output data:0.1 sec.
Time to prepare final strings:0.3
Total processing time:5.9
App: REVENUE - Records to be posted are 29119 (calc diff = 0)
CATEGORY,REVDATA,ACCTREV,PRODUCT,TIME,COMPANY,CUSTOMER,DATASRC,LOCATION,MEDIAID,PRODTYPE,TRANSID,SIGNEDDATA
ACTUAL,REV_AMOUNT,4101,0001,,03,2282436,INPUT,00,ZZ,NONE,MANUAL_TRANSBASED,-208.5
ACTUAL,REV_AMOUNT,4101,0010,,03,1000105,INPUT,00,20,CURR,TRANSACTION_BASED,-88
ACTUAL,REV_AMOUNT,4101,0010,,03,1000105,INPUT,00,20,HIST,TRANSACTION_BASED,-60

BPC Script Logic Multi-dimension REC Statement

Hi All BPC Experts,
The way that our data in the dimensions is setup, members in one dimension have properties that "point" to members in other dimensions.
In this case when I write the REC statement, whilst I'm just doing arithmetic on P_ACCT, when I write the final value, I also need to specifiy the members for the dimensions CUSTOMER, ENTITY, MINE, DESTINATION.
In the example below I hve hardcoded the CONTRACT and TIME dimension members, but going forward, this logic will be appllied to a number of CONTRACTS and TIMES so the members of the other dimensions need to be retrieved dynamically.
*XDIM_MEMBERSET P_ACCT = CAPACITY_REV,CAPACITY_RATE,FINAL_VOLUME
*XDIM_MEMBERSET CATEGORY=FORECAST
*XDIM_MEMBERSET P_DATASRC=Input
*XDIM_MEMBERSET CONTRACT=0005000001_10
*XDIM_MEMBERSET TIME=2009.JUL
*WHEN P_ACCT
      *IS CAPACITY_RATE
         *BEGIN
            REC(EXPRESSION=(%VALUE%[P_ACCT].[FINAL_VOLUME]),
                     CUSTOMER = CONTRACT.CUSTOMER,
                     DESTINATION = CONTRACT.DESTINATION_ID,
                     ENTITY = CONTRACT.HAUL_PC,
                     MINE = CONTRACT.MINE_ID,
                     P_ACCT = "CAPACITY_REV")
         *END
*ENDWHEN
*COMMIT
My Question is twofold:
- Can anyone see any problems with the above code, ie is this a valid way of writing the REC statement?
- Can anyone suggest another way of writing this code?
Best regards
Mark Rodrigues

Just repostoing the logic as "Code"
*XDIM_MEMBERSET P_ACCT = CAPACITY_REV,CAPACITY_RATE,FINAL_VOLUME
*XDIM_MEMBERSET CATEGORY=FORECAST
*XDIM_MEMBERSET P_DATASRC=Input
*XDIM_MEMBERSET CONTRACT=0005000001_10
*XDIM_MEMBERSET TIME=2009.JUL
*WHEN P_ACCT
*IS CAPACITY_RATE
    *BEGIN
        REC(EXPRESSION=(%VALUE%P_ACCT.FINAL_VOLUME),
                                        CUSTOMER = CONTRACT.CUSTOMER,
                                        DESTINATION = CONTRACT.DESTINATION_ID,
                                        ENTITY = CONTRACT.HAUL_PC,
                                        MINE = CONTRACT.MINE_ID,
                                        P_ACCT = "CAPACITY_REV")
    *END
*ENDWHEN
*COMMIT

Automation of updates of dimension properties/NEWID using Admin_MAKEDIM

We are trying to automate the changes to the properties to the dimension members and NEWID's to existing ID's. We have a SSIS that updates the mbrdimension table correctly but when we run the Admin_MAKEDIM from datamanager it is not applying the updates to the dimension members. But if there are new members they are updating ok.
Does Admin_Makedim process/apply changes to the dimension member properties and ID's ?
Any help is greatly appreciated.
Thanks,

Hi there,
Were you able to get this to work?
The properties and new members need to exist in your temporary table.
The contents of the temporary table are then copied to the mbr table and then the dimension is processed.
Please note that the Excel member sheet is not update so you either need to manually export the dimension member sheet (there is an option to do this in the BPC Admin module) or you can create a process in SSIS to extract the contents of the Mbr table to the member sheet in the ADMINAPP folder.
Thanks
John

BPC Evdre cell Going blank sometimes when changing server

Hi all,
This is my first post on the forum, please be gentle
I dont know if this is the right forum for BPC for microsoft , but here i go anyway
I was wondering why when you have an EVDRE template open on on server and change the server
the evdre cell just goes blank and doesnt want to refresh or do anything after that , until you close it and reopen
Is there any specific reason for this happening
Any advice would be great
another question i have is whether anyone has managed to programmatically create a parentH2 hierarchy everytime masterdata for any dimension changes

see
* Firewalls -- http://kb.mozillazine.org/Firewalls
If that does not solve the problem, also see the links at the bottom of the page.

BPC: EvDre filter on dimension properties

Similar Messages

Maybe you are looking for