Calculated Dimension Member - aggregation error?!

Hi,
Hyperion 11.1.2.1.0.83
I have created a DynamicCalc Scenario member called 'Movements 02', which is calculated as AP02-AP01; (without two pass calculation) - where AP02 and AP01 are both Scenario members with StoreData.
This works fine for zero level members, but the aggregated member's totals are not correct, even when AP02 and AP01 are re-aggregated - though the sum of errors comes back to zero. (i.e. if one parent is -50 out then another is +50 out)
(It is possible that entities have moved parents between the original storage of AP02, AP01 and now)
Account, entity and elements (a custom dimension) are all aggregated via a standard aggregation business rule.
Anyone suggest a fix please - as the member is calculated it is not like I can run the aggregation script against it...
thanks,
Robert.

This sounds like an order-of-calculation issue. Dynamic variance scenarios usually need to be two-pass calcs. Does it change your results if you set your scenario to two-pass?
- Jake

Similar Messages

  • Help with calculated dimension member

    I am trying to create a (custom) dimension member using a simple calculation (subtraction e.g. member1 - member2) in AWM 9.2.0.4 following the example given in the Oracle OLAP DML Reference 10g (using DML). I could not find any articles relating to this for 9i. Although the custom member is easily added to the dimension, I could not populate it with the specified calculation.
    I need to enable the analytic workspace for OLAP API and BI Beans. Can anyone help?

    Hi,
    Use the formula, I have tested by creating Months column with choice, Year column as numeric and Calculated column as DateTime returned.
    =DATE(Year,IF([Months]="January", 1,IF([Months]="February",2,IF([Months]="March",3,IF([Months]="April",4,IF([Months]="May",5,IF([Months]="June",6,IF([Months]="July",7,IF([Months]="August",8,IF([Months]="September",9,IF([Months]="October",10,IF([Months]="November",11,12))))))))))),1)
    Before applying the formula few things need to be noted.
    DATE(YEAR, MONTH,DAY) will accepts three parameters all should be type numeric(integer).
    Create the Year column of type numeric
    Create the calculated column of type "DateTime" to return as date
    Please mark it answered, if your problem resolved or helpful.

  • Error selecting a dimension member in BPC EPM report - The given key was not present in the dictionary

    Hi,
    We are currently running SAP BPC 10.1 NW on Hana
    Version:
    CPMBPC  810 SP 4
    SAP_BW  740 SP 9
    HANABPC 810 SP 4
    EPM Excel Add-in 10 SP 21 .NET 4 build 9094.
    On my embedded model. I have a BEX query on a aggregation level which I access in a report using the EPM Add-in Excel .
    When I edit my report in EPM Add-in Excel , and I try to select the dimension members for a selected dimension member, I get the following error.
    "The given key was not present in the dictionary"
    Any assistance to help resolve the problem will be appreciated.
    Regards
    Gavin

    Hi Shrikant,
    I had a look at MBR_SEQ , it is a attribute on the dimension member in BW , this relates to a past version of BPC 7.5. We are currently on BPC 10.1 Embedded model , and the MBR_SEQ does not exist on any of the characteristics I have in my info cube.
    When I create a web report I am able to access the dimension members using the select dimensions options, the problem seems to be on the EPM Add-in Excel client only.
    Thanks
    Gavin

  • Error(1012016) Cannot calculate Dimension Member [CYG_BILAN] with restricted Member [CYG_BILAN].

    Hello,Below is a validated script, with generate a run time error :Error(1012016) Cannot calculate Dimension Member [CYG_BILAN] with restricted Member [CYG_BILAN].See the script below (with the error message in comment).Why can't' I calculate a member which is fixed ? Where is it documented ? How should I modify this script to make it runable ? Thanks for help Philippe Cuisset SCRIPT======/* Basculement des comptes d'actif de solde négatif vers les comptes de dettes *//* Philippe Cuisset 31/05/03 */SET MSG INFO;FIX ( @DESCENDANTS(&organisation, 0), @LEVMBRS(dev,0), @DESCENDANTS(&annee, 0), ind_financier,     @LEVMBRS(cra, 0), @LEVMBRS(geo, 0), @LEVMBRS(clifa, 0), @LEVMBRS(ana, 0), @LEVMBRS(nc, 0) )     /* Copie des données du cycle réel dans le cycle bilan */     FIX( flu_ouv, flu_mensu )          DATACOPY cyg_reel TO cyg_bilan;     ENDFIX     /* Pour le flux solde, et (chaque nature comptable (d'actif circulant) ayant un attribut bilan,                               ou chaque nature comptable de dettes financieres) */     FIX( cyg_bilan, flu_solde, @ATTRIBUTE( BILAN ), @DESCENDANTS( NC7_FINANCIERES, 0 ) )          /* Initialisation du solde mensuel du compte d'actif */          VAR var_solde_actif = 0;          /* Initialisation du solde mensuel du compte de dettes */          VAR var_solde_dettes = 0;/***** ERROR ON FOLLOWING LINE *****//***** Local/buedmt2/buedmt2/Essadm/Error(1012016))Cannot calculate Dimension Member [CYG_BILAN] with restricted Member [CYG_BILAN] *****/          cyg_bilan (                /* Si nature comptable (d'actif) avec attribut bilan */                IF ( @ATTRIBUTESVAL( BILAN ) != "" )                    /* Calcul du solde mensuel de la nature comptable d'actif */                    var_solde_actif = flu_ouv + @ACCUM( flu_mensu );                     /* Si le solde mensuel est < 0 */                    IF ( var_solde_actif < 0 )                         /* Raz du solde dans le compte d'actif */                         cyg_bilan = 0;                         /* Ajouter la valeur du compte de bilan depuis l'actif vers les dettes */                         var_solde_dettes = @MEMBER( @SUBSTRING( @ATTRIBUTESVAL( bilan ), 3) ) ;                         cyg_bilan = var_solde_dettes + var_solde_actif;                    ENDIF               ENDIF          );     ENDFIXENDFIX

    Not sure where it is documented, but you can not calculate what you are fixing on. To me it seems a bit odd, but I believe the logic is, if it is sparese and you are fixing on it, how can you fix on what might not be there? If it is sparse, fix on all the other sparse dimensions thenFix (....) CYG_BILAN ( CYG_BILAN = ....; )EndFiX;Also, if it sparse, make sure the block exists (either datacopy data into it or set 'CREATE BLOCK ON EQUATION' on - I tend to copy data into it).If it is dense, you wouldn't want to fix on it anyway.Rich SullivanBeacon Analytics

  • Error: Invalid dimension member with special character / in BPC NW 7.5 SP7

    Hi experts,
    We are encountering the following problem in our Financial Planning application.
    We are migrating our existing BPC solution from one server to another through backup and restore. The existing solution was on BPC NW 7.5 SP 5. The profit_centre dimension in the existing solutions has several member ids with special character '/' (forward slash). The dimension never threw an error when processed in the existing solution and there is planning transactional data against these member ids.
    While the entire configration , appset , files were successfully restored through UJBR on the new system (BPC 7.5 SP7) through UJBR (backup and restore), the masterdata could not be restored only for this Profit_centre (masterdata for other dimensions were processed successfullu). All the member ids with / are rejected for this dimension. The same error is thrown if processed through the admin client from the member sheet. 
    Error: Dimension member PC_FF/WS/NT is an invalid member ID
              Error in Admin module
    Is there any setting which need to be made to allow / character in member ids? Any suggestion to get around this problem would be much appreciated.
    Thanks
    Abhiman

    Hi Abhiman,
    Yes, you need to maintain the transformation file to correct all dimension member IDs. Can you please refer to the following link with a similar issue:
    conversion file formula not working
    Hope this helps.
    Rgds,
    Poonam

  • SSTemplate.xlt Error during 'Maintain Dimension Member' in BPC Admin

    Hi,
    While trying to 'maintain dimension member' in BPC administrator (BPC 7.0 Netweaver version) for a dimension,I get error message that 'C:\...Temp\SSTemplate.xlt' file could not be found.
    Due to this I am unable to maintain members for any dimension.
    If anyone has faced this issue and resolved it,could you please me out?
    Thanks in advance,
    Rinal

    Dear Rinal Parmar,
    I think that the dimension file which you mean is lose from the directory(the directory which you installed the SAP BPC). If you've backup the Appset before, please you find the dimensian file (.xlt) which is lose in the backup directory. After that, you copy paste into the exactly directory (the directory which you installed the SAP BPC). Then, You should process dimension and process application again.
    Thanks,
    Wandi

  • Processing dimension error :DUPLICATE DIMENSION MEMBER %1 IS DETECTED

    When I try to process the Account Dimension, I get an error u201CDUPLICATE DIMENSION MEMBER %1 IS DETECTEDu201D.
    However my dimension does not contain any duplicate members.
    Appreciate if someone could interpret this error message and help me resolve the issue
    Thanks,
    Sowmya
    Edited by: 281642 on Nov 10, 2011 11:34 AM

    Hi Sowmya,
    We had same error couple of times. The issue is you could have some blank rows inserted at the end of your master data. Try the following steps
    1. Maintain master data
    2. Go to the last row with valid master data
    3. Select all rows below it and right click and delete
    4. Save and process dimension
    Hopefully this should resolve your issue.
    Regards,
    Kranthi

  • BPC Error: Cannot fine dimension member sheet file

    Hi experts,
    I'm getting below error when I try to process the dimension.
    "Cannot fine dimension member sheet file; use the export dimension feature to restore it from the member file".
    Can anybody help me to resolve the error.
    Thanks in Advance

    Hi Hari,
    When you select your dimension, there will be an option "export dimension". Click on that.
    Hope this helps.

  • Error processing dimension member elements

    Hi all,
    I am trying to process IntCo and Entity dimension. The way I am doing this is as follows
    1. Copy paste the data to dimension excel file.
    2. Save it to server.
    3. Process Dimension
    But while processing the dimension it gives me follows:
    Entity value must exist in the Entity type dimension -  Member ID : [I_E1170],  Property Name : [Entity],  Property Value : [E1170]
    Please help me in finding and fixing the reason after this.
    Regards,
    Diksha.

    Hi,
    I think you have to process Entity dimension first. And then you should process Intco dimension that refers to Entity dimension via the "Entity" property. In this "Entity" property of Intco dimension, you should enter a value that exists in the Entity dimension.
    It should then work.
    Hope this will help.
    Best Regards,
    Patrick

  • Sum Aggregation Error in Physical & BMM Layer in OBIEE 11g with Essbase 11

    Hi everyone,
    I'm using OBIEE 11g with Essbase 11 as the data source. I'm using Sample Basic database from the Essbase as my data source. If I'm using the hierarchy for the measures (so I don't flatten the measures), and when I changed the aggregation in both physical and BMM layer from Aggregate_External to Sum, I can't create a report at all from the Answers.
    Does anyone encounter the same thing? Any ideas/solution about this? Please help.
    Thanks a lot!

    Hi Deepak,
    When I picked the "Basic - measure" alone, I got this error.
    Error Codes: OPR4ONWY:U9IM8TAC:OI2DL65P
    State: HY000. Code: 10058. [NQODBC] [SQL_STATE: HY000] [nQSError: 10058] A general error has occurred. [nQSError: 43113] Message returned from OBIS. [nQSError: 43119] Query Failed: [nQSError: 96002] Essbase Error: Unknown Member Basic - measure used in query (HY000)
    SQL Issued: SELECT 0 s_0, "Sample Basic"."Basic"."Basic - measure" s_1 FROM "Sample Basic".
    When I picked the "Gen1,Measures" alone from the measure dimension, I got this error:
    Error Codes: OPR4ONWY:U9IM8TAC:OI2DL65P
    State: HY000. Code: 10058. [NQODBC] [SQL_STATE: HY000] [nQSError: 10058] A general error has occurred. [nQSError: 43113] Message returned from OBIS. [nQSError: 43119] Query Failed: [nQSError: 46008] Internal error: File server\Query\Optimizer\ServiceInterfaceMgr\SIMDB\Src\SQOIMDXGeneratorGeneric.cpp, line 2610. (HY000)
    SQL Issued: SELECT 0 s_0, "Sample Basic"."Measures"."Gen1,Measures" s_1, SORTKEY("Sample Basic"."Measures"."Gen1,Measures") s_2 FROM "Sample Basic"
    But when I queried the dimensions one by one (only single dimension each), no error was shown.
    This only happens if I use Sum in the physical and BMM layer. If I use External_Aggregation, these errors do not happen. And if I flatten the measures, these errors also do not happen.

  • How can I create a dimension member formulas involving parent member?

    Hi everyone,
    I'm trying to learn BPC- Planning and I've got the following issue:
    Behind each key figure is a calculated formula which will not be calculated in the aggregated parent member ( Energie Kosten). It's a IF formula based on percentage. As far as I understood it's not possible in BPC NW 10.  to store values at parent level and parent member doesn't aggreagte child values that are calculated members. What can I do to solve the problem? The only solution will be the logic scripts?
    Any input is appreciated.
    Thank you!

    Hi Vadim,
    thank your for your answear.
    Here it's my formula:
    IIF([KENNZAHL].[S_PSTROM] = 0 , [KENNZAHL].[E_PSTROM] ,[KENNZAHL].[S_PSTROM] * ([KENNZAHL].[BELGES] *[KENNZAHL].[TAGEMON] ))
    where: S_PSTROM = percentage key figure
             E_PSTROM =  manual input key figure
             BELGES = allocation
             TAGEMON= days per month
    The formula is used to calculate the energy. If there are adjustments used then will be calculated using the percentage if there are no adjustment needed that should take automatically the manually entered values.
    It's used only a hierarchy- PARENTH1. And only the dimension without calculated members are calculated in nodes.
    Thank you a lot!

  • ORA-35563: Multiple values exist for an attribute of this dimension member

    After following the tutorial Building OLAP Cubes I was trying to make a cube with aggregation down to the day instead of down to the month.
    I created a times table pretty similar to the one used in the tutorial:
    CREATE TABLE EVENT_TIMES (
            HOUR_KEY        DATE NOT NULL,
            DAY_ID          VARCHAR2(10),
            DAY_NAME        VARCHAR2(10),
            DAY_END_DATE    DATE,
            DAY_TIME_SPAN   NUMBER,
            MONTH_ID        VARCHAR2(30) NOT NULL,
            MONTH_NAME      VARCHAR2(40),
            MONTH_END_DATE  DATE,
            MONTH_TIME_SPAN NUMBER,
            YEAR_ID         VARCHAR2(30) NOT NULL,
            YEAR_NAME       VARCHAR2(40),
            YEAR_END_DATE   DATE,
            YEAR_TIME_SPAN  NUMBER
    As you can see, instead of a DAY_KEY like in the tutorial, I now use an HOUR_KEY.
    This is a sample of the data I inserted in this table:
    select to_char(hour_key,'YYYYMMDDHH24MISS'),DAY_ID,DAY_NAME,DAY_END_DATE,DAY_TIME_SPAN,MONTH_ID,MONTH_NAME,MONTH_END_DATE,MONTH_TIME_SPAN,YEAR_ID,YEAR_NAME,YEAR_END_DATE,YEAR_TIME_SPAN from event_times;
    TO_CHAR(HOUR_KEY,'YYYYMMDDHH24MISS') DAY_ID     DAY_NAME   DAY_END_DATE DAY_TIME_SPAN MONTH_ID                       MONTH_NAME                               MONTH_END_DATE MONTH_TIME_SPAN YEAR_ID                        YEAR_NAME                                YEAR_END_DATE YEAR_TIME_SPAN
    20140104050000                       Y2014M1D4  Y2014M1D4  04-JAN-14                1 Y2014M1                        Y2014M1                                  31-JAN-14                   31 Y2014                          Y2014                                    31-DEC-14                365
    20140104060000                       Y2014M1D4  Y2014M1D4  04-JAN-14                1 Y2014M1                        Y2014M1                                  31-JAN-14                   31 Y2014                          Y2014                                    31-DEC-14                365
    I then created my TIME dimension with DAY as the lowest level.
    When I try the maintain cube option it fails at the 'LOAD NO SYNCH' step with the rejected records having an error message that says:
    ORA-35563: (XSRWLD17) Multiple values exist for an attribute of this dimension member.
    To me, this is a very cryptic message and the only explanation I find online is:
    Cause
    Multiple source table rows containing different values for a dimension attribute were found. Only the first of the multiple rows has been loaded.
    Action
    Fix the mapping or remove the rows with conflicting attribute values..
    This confuses me. In the tutorial the lowest level was day and the TIMES table contained 1 record for each day.
    In my example, the lowest level is hour and the TIMES table contains 1 record for each hour.
    Which attribute has multiple values? And which values?
    The rejected records (101) are not very clear:
    ALIAS_1 = 'MONTH_Y2014M1' AND ALIAS_3 = to_date('31JAN14') AND ALIAS_4 = 31 AND ALIAS_5 = 'Y2014M1' AND ALIAS_6 = 'Y2014M1' AND ALIAS_7 = 'YEAR_Y2014'
    If anyone can help point me in the right direction, it would be greatly appreciated.

    I have seen this recently. The issue is with the dimension load itself.  You have a hour level record table but the rules relating to hierarchy/attribute values etc are checked/reinforced during the load and this error comes up sometimes.
    I would guess that the issue seems to be with your month level information present in the higher level month columns. There are many records corresponding to a single month in ur case, month of Y2014M1. Information relating to Month level member Jan 2014 or member MONTH_Y2014M1 is present in these records: 31 (days) *24 (hours) = 744 records. The data in these 744 records for columns - MONTH_ID, MONTH_NAME, MONTH_END_DATE, MONTH_TIME_SPAN need to be exactly the same in order for the single member MONTH_Y2014M1 to have month attributes loaded with valid values.
    For e.g: if records #1 to #743 contain month_timespan=31 but for some unknown reason record #744 contains month_timespan=30 then this error will come up. OLAP does not know which value to load (31 or 30), and only 1 value can be loaded onto the month level member corresponding to month Y2014M1.
    A quick check of the data should give you the answer. Typically there may be some mistake/invalid assumptions made with the boundary records (in your case, check for values for records corresponding to hour=0 or hour=23/24) which is causing the issue.
    HTH
    Shankar

  • Syntax rules for dimension member?

    What are the rules regarding a dimension member? Is there a character limit? I keep getting an Incorrect Syntax for member error (3305).
    Error log looks like this(I know it's hard to read):
    \\Record #25621 - Incorrect Syntax For Member XTO 20 PIPELINE (USE 707702) UNIT 073919     U073919     XTO 20 PIPELINE (USE 707702) U073919 (3305)
    ETX      '
    65600     '
    EAST TX-OP '
    65600     '
    65600.0001     '
    UNIT 073919     '
    XTO 20" PIPELINE (USE 707702) UNIT 073919     '
    U073919     '
    XTO 20" PIPELINE (USE 707702) U073919'
    ('-designates end of line)

    from the dbag:
    When naming dimensions, members, and aliases in the database outline, follow these rules:
    Use no more than the maximum lengths that are specified in Appendix A, “Limits”.
    Names are not case-sensitive unless case-sensitivity is enabled. See “Setting Outline Properties” in the Essbase Administration Services Online Help.
    Do not use " (quotation marks) or tabs anywhere in a name.
    Do not place spaces at the beginning or end of a name. Analytic Services ignores spaces at the beginning or end of a name.
    Do not use the following characters at the beginning of a name:
    @ at signs
    () parentheses
    \ backslashes
    . periods
    { } braces
    + plus signs
    , commas
    - dashes hyphens, or minus
    _ underscores
    = equal signs
    | vertical bars
    < less than signs
    'single quotation marks
    Do not use the following words as dimension or member names:
    Calculation script commands, operators, and keywords. For a list of commands, see the Technical Reference.
    Report writer commands. For a list of commands, see the Technical Reference.
    Function names and function arguments. For a list of functions, see the Technical Reference.
    Names of other dimensions, members (unless the member is shared), generation names, level names, and aliases in the database.
    Any of the following words:
    Note: If you enable Dynamic Time Series members, do not use the associated generation names—History, Year, Season,
    Period, Quarter, Month, Week, or Day. See “Applying Predefined Generation Names to Dynamic Time Series
    Members” on page 436.
    Any of the following words:
    ALL
    AND
    ASSIGN
    CALC
    CALCMBR
    COPYFORWARD
    CROSSDIM
    CURMBRNAME
    DIM
    DIMNAME
    DIV
    DYNAMIC
    EMPTYPARM
    EQ
    EQOP
    EXCEPT
    EXP
    EXPERROR
    FLOAT
    FUNCTION
    GE
    GEN
    GENRANGE
    GROUP
    GT
    ID
    IDERROR
    INTEGER
    LE
    LEVELRANGE
    LOOPBLOCK
    LOOPPARMS
    LT
    MBR
    MBRNAME
    MBRONLY
    MINUS
    MISSING
    MUL
    MULOP
    NE
    NON
    NONINPUT
    NOT
    OR
    PAREN
    PARENPARM
    PERCENT
    PLUS
    RELOP
    SET
    SKIPBOTH
    SKIPMISSING
    SKIPNONE
    SKIPZERO
    TO
    TOLOCALRATE
    TRAILMISSING
    TRAILSUM
    UMINUS
    UPPER
    VARORXMBR
    XMBRONLY
    $$$UNIVERSE$$$
    #MISSING
    #MI

  • Why to open Block only with Dense dimension Member ???

    Hi All,
    I want to understand the logic behind opening the block with dense member. Generally we open the block with member of dense dimension by fixing the sparse members
    e.g. below considering C1, P1,Working,Actual are members of sparse dimension customer, product, Version, Scenario.
    Fix(C1,P1,Working,Actual)
    Jan
    IF(Some condition)
    Calculation on Account Member
    ENDIF
    Now if i change the code as below making Jan in FIX and opening the block with Actual. How it will affect the performance. The Number of iterations in total number of datacells will be same in bothe cases above and below then why to give priority to dense dimension member for opening the block.
    Fix(C1,P1,Working,Jan)
    Actual
    IF(Some condition)
    Calculation on Account Member
    ENDIF
    ENDFIX
    I know the logic behind keeping sparse dimension member in FIX but here i think keeping 'Actual' member for opening the block is also a type of fix which will tell the code to do the calculation only for blocks of 'Actual'.
    In 1st case i have fixed the number of blocks containing members C1,P1,Working,Actual and by keeping Jan for opening block means Jan is also fixed for the particular application means code will not run for feb march etc.
    Means code will run for C1->P1->Working>Actual->Jan
    In 2nd case also i have fixed C1,P1,Working,Jan and by keeping Actual for opening block means Actual is also fixed for the particular application means code will not run for other members of Scenarion dimension.
    Means code will run for C1->P1->Working>Jan->Actual
    Then what is the difference??? Why it will effect performance???

    when using an IF statement in a calc script you have to specify a member to associate it with for the calc member block. This is like temporarily assigning it to that member as a formula in the outline. In most cases calculations on dense dimensions can work faster as the block is in memory. Remember that a block statement can have multiple calculation statements in it. When this occurs, having the calculations on a dense member can speed it up as it may not have to swap blocks to do the calculation.
    Also consider that if a sparse combination of members does not exist, the block will not exist and there will be no attempt to do the calculations. If a sparse member is on the calc member block, it will cycle through all of the sparse members looking to do the calculation.

  • Creating UDA for a dimension member

    Hi All,
    when I am creating UDA for a dimension member in my planning application I get the following error.
    The associated dimension ID has not been set for this property. Do you want to create the association now?
    Can anyone please let me knwo wahts this error?
    Thanks

    I take this is an EPMA application, you have to create dimension association between the UDA property and the UDA dimension.
    Have a read of :- http://download.oracle.com/docs/cd/E17236_01/epm.1112/epma_admin/epma_create_assoc.html
    Cheers
    John
    http://john-goodwin.blogspot.com/

Maybe you are looking for