Percentages on the scenario dimension

This must be a common task but I cannot seem to get the right answer.In simplified terms I have various dimensions including:-Accounts with Sales, Raw Mats, Manufacturing, Distribution, Admin Exps.Scenario with Actual, Budget, Actual % of Sales, Budget % of Sales.I need to calculate each member of the Accounts as a % of Sales, to give the data to produce a report like this:--------Act--Act%Sales--Bud--Bud%SalesSales 234 100.0% 250 100.0%RawMat 117 50.0% 100 40.0%Mftg 29 12.4% 25 10.0%Dist 8 3.4% 10 4.0%Admin 48 20.5% 50 20.0% ------------------------------Profit 32 13.7% 65 26.0%What calc script do I need?Many thanks for any help

Formula for Actual%Sales:Actual%Sales;Formula for Budget%Sales:Budget%Sales;If each of these are entered as member formulas in the outline and are dynamic calc, then there is no need for a calc script.The formula's would be the same in a calc script but you would have to ensure that all other relevant values were pre-calculated. The easiest, but not necessarily the quickest or most efficient way, is to have a Calc All; before these items in the script.

Similar Messages

  • Manage Metada: add members to the Scenario dimension (ERROR)

    I tried to add a new member to Scenario ddimension, but I got error.
    How (where) can I find out what it is wrong with my input data? What procedure checks data before saving?
    Thank you!
    Zhanna

    there are some crucial and compulsory properties which you have to include to be able to add a new scenario.
    it is better to try to do it through the tree view, with the properties on the right, than the list view in my opinion.
    take a screenshot or make a note of the properties of one of your existing scenarios and create a new one copying those properties exactly to begin with, changing just the name, and then worry about changing other properties one at a time. Be sure that what you enter for default parent is a valid default parent in the tree structure.

  • Using in the workflow process the element of Scenario dimension which conta

    Good day All
    In the Scenario dimension has been created element which include as children the some store elements of the Scenario dimension (Plan, Fact ...).
    This element has been assigned as scenario element for Planning Unit Hierarchy.
    When we start the workflow process the children of its elements (Plan, Fact ...) still available for edit on work form for all users.
    Question. Work form contains several elements of Scenario. As in the workflow process close all of these elements, creating only one Planning Unit Hierarchy and run the process only once (in fact, one Scenario).
    thanks

    The total video bit rate is determined by audio & video. Depending on what rate your video file was encoded at will determine how much room is left for audio. PCM(aiff/wav) audio requires a bigger piece of the pie. Video bit rate too high means your overall(video+audio) rate is going above 9Mbps which the format won't allow. The only way to use aiff would be to lower your video file's data rate. The length of your program is also a factor in all of this.
    I had some problems in the past with using aiff instead ac3. Although there shouldn't be any issue I experienced playback issues on some players that couldn't be explained but were cleared up by ac3.  I have been using the same specs as Dave's suggestion for almost nine years and have not had any issues with mix, quality, or levels.

  • Budget to Actual Variance Formula in Scenario Dimension help

    I am trying to calculate the Budget to Actual variance by using a member formula in the Scenario dimension.
    The formula I'm using is: @VAR("Final"->"Actual" -> &CurrentYear,"Budget");
    This formula yields a value that equals the budgeted amount.
    The Variance % formula I'm using is: @VARPER("Final"->"Actual" -> &CurrentYear,"Budget")/100;
    This % formula equals 100% for most accounts, but is 200% or 300% for other accounts
    What am I missing? Many thanks in advance

    Jake,
    I'm a newbie, so I'm not sure what you mean by cross-dim. I didn't write the formula but it's up to me to figure this out. Yes, I do want to compare budget data to same year actual data.
    It is dynamic. A sample retrieve for -200% would be Total Operating Revenues:
    Actual = 2,404,789
    Budget = 2,117,250
    Variance $ = (2,117,250)
    Variance % = -200%
    A really crazy one is Benefits Rollup:
    Actual = 66,353
    Budget = 73,817
    Variance $ = 73,817
    Variance % = 500%
    I appreciate your help very much.
    Max

  • Consolidate YTD Member in Scenario Dimension

    Hi All my Peers,
    What Exactly the Purpose of " Consolidate YTD Member in Scenario Dimension. my Analysis is as bellow, please Guide me if my Thinking is Wrong and also is this Member Focus and Refer or Check or Cross Check with any other Member to Start its Execution?
    Is Consolidated Member we can say and Understand easily. How to Understand Specifically Mentioned Member Consolidate YTD.?
    By default we are using HFM For Consolidation as per our Customization.
    Where exactly this Member Importance Comes in to Picture
    Knowing to my Knowledge, Periodical data we will get every Month end from our ERP Systems
    and one more concept Periodic automatically gets YTD,and YTD Automatically gets Periodic i am not able to understand how HFM Understand and do this. But i know Rollup,Aggregation,Immediate Parent,Ultimate Parent
    I hope any of your answers will make me Clear on this attribute.

    I am attaching an extract of ther post
    The periodic or YTD consolidation of values is a matter of sequence. Note that the following discussion applies to Flow accounts (Income, Expense and Flow types).
    When ConsolidateYTD flag of the scenario dimension is checked, HFM first consolidates the YTD values of accounts and then calculates the periodic values at the consolidated (group) level.
    Conversely, when ConsolidateYTD flat is un-checked, HFM first consolidates periodic values of accounts and then at consolidated (group) level it forms the YTD amounts.
    In both cases, whether you have loaded periodic or YTD values is irrelevant. The consolidation happens with the sequence described in each case above.
    So, you think "what's the difference?". In fact there is no difference until you introduce a new subsidiary in the middle of the year. In this case you need to consolidate only the periodic values of accounts, starting on the month that the subsidiary was introduced to the group structure. If you don't the accumulated amounts from previous periods (YTD values) will consolidate, which you don't want.
    For example: you introduce a new subsidiary during March. Until March the YTD value of sales was 100. During March the periodic value is 50, therefore the YTD sales for March is 150. You don't want to consolidate 150 since you did not own the company during the previous months. You need to consolidate only 50. In order to do this you have to populate the flow accounts for at least Feb so that HFM will calculate the periodic value for March correctly. In this case the contribution of the new subsidiary to the consolidated sales account for March is 50.

  • Multiple columns from the same dimension table as row labels performing slowly

    (Working with SSAS tabular)
    I'm trying to figure out what the approach should be for the following scenario:
    Lets say we have a Customer table. The table has columns such as account number, department number, name, salesperson, account manager, number of customers, delivery route, etc
    A user of the model could want to see any permutation of that information as the row labels. How should that be handled?
    What we've been doing so far is that the user adds each column they want into the "ROWS" section in Excel. This works fine with smaller tables (for example, "Department" table with a "Department Code" and "Department Name",
    but on large tables this quickly chokes. I understand why this is happening, I just haven't found a better way to accomplish the same thing.
    I can add a calculated column to the model through VS, but obviously this is unsupportable and unscalable when each person needs their own permutations of the data. Can something similar be done in Excel? 
    This question seems to be what I need:
    http://social.msdn.microsoft.com/Forums/en-US/97d1157a-1402-4227-b96a-79524401ddcd/mdx-query-performance-when-selecting-multiple-attributes-from-same-dimension?forum=sqlanalysisservices
    However I can't find any information on how to add those properties (is it a multidimensional-only thing?)

    Thanks for the help. Sorry but i'm a self-taught developer, and i may be missing some basics :)
    Anyway i've done what you suggested but i get this error:
    [nQSError: 15011]The dimension table source Dimension Services.DM_D_SERVIZI_SRV has an aggregate content specification that specifies the level Product. But the source mapping contains column COD_PRODUCT with a functional dependency association on a more detailed level .
    where:
    - DM_D_SERVIZI_SRV is the physical alias for the Service Dimension (and the name of the LTS too)
    - COD_PRODUCT is the leaf of the hierarchy, the physical primary key, but it hasnt to be included in the hierarchy
    Do i have to add another level with the primary key and hide it to the users?
    I tried to solve this going to the logical tables source properties, on the tab contents, setting "logical level" to null for the hierarchy, but i don't know if this is correct.
    Thanks

  • Resize a layer to a percentage of the document size and position in corner

    I need to create a script that places a logo in the corner of my main document but i need the logo to be constrained to a percentage of the document size. my logos needs to live in the bottom right corner of my images and be no larger than 28 percent height and no larger than 60 percent of the width of the document. i need it to constrain proportions of the original file so if the logo is square it will remain square, or if it is more rectangular it will maintain its rectangular shape.  Heres what i've come up with so far, i am pretty inept at scripting so if disregarding my current script is more helpful than building upon it please ignore mine:
    if ( documents.length > 0 )
        var originalDialogMode = app.displayDialogs;
        app.displayDialogs = DialogModes.ERROR;
        var originalRulerUnits = preferences.rulerUnits;
        preferences.rulerUnits = Units.PIXELS;
        try
            app.activeDocument = app.documents[0];    //set active document to 2nd document   
            var docRefOne = app.documents[0];
            var refWidth = docRefOne.width;
            var refHeight = docRefOne.height;
            app.activeDocument = app.documents[1];    //set active document to 2nd document   
             var docRef = activeDocument;
            //current image dimensions
            var w = docRef.width;
            var h = docRef.height;
            activeDocument.selection.selectAll();
            docRef.selection.copy();   //Copy selection
            app.activeDocument = app.documents[0]; //set first document as active document
            var docRef = activeDocument;
            activeDocument.selection.selectAll();
           docRef.paste(true); //paste into selection
        catch( e )
        // An error occurred. Restore ruler units, then propagate the error back
            // to the user
            preferences.rulerUnits = originalRulerUnits;
           app.displayDialogs = originalDialogMode;
            throw e;
        // Everything went Ok. Restore ruler units
        preferences.rulerUnits = originalRulerUnits;
        app.displayDialogs = originalDialogMode;

    You could do something like this...
    #target photoshop
    activeDocument.suspendHistory('Logo Resize', 'main()');
    function main(){
    if(!documents.length) return;
    var startRulerUnits = app.preferences.rulerUnits;
    app.preferences.rulerUnits = Units.PIXELS;
    var myDoc = activeDocument;
    /////////////////////////////// Amend to suit /////////////////////////////////
    var Opacity = 100; /* Opacity of logo */
    //Position logo   X,Y
    var X = myDoc.width - 10; //Right side of logo
    var Y = myDoc.height - 10; //Bottom of logo
    var Logo = File(Folder.desktop + "/logo.png"); //logo
    if(!Logo.exists){
        alert("Your logo '" + decodeURI(Logo.name) + "' does not exist!");
        app.preferences.rulerUnits = startRulerUnits;
        return;
    placeFile(Logo);
    var LB = myDoc.activeLayer.bounds;
    var docHeight = myDoc.height;
    var docWidth = myDoc.width;
    var LHeight = Math.abs(LB[3].value) - Math.abs(LB[1].value);
    var LWidth = Math.abs(LB[2].value) - Math.abs(LB[0].value);  
    if(LWidth > LHeight) {//Landscape logo
    var Percent = 60; /* Resize logo to percentage of smallest side of doc */
    if(LWidth < LHeight) {//Portrait logo
    var Percent = 28; /* Resize logo to percentage of smallest side of doc */
    if(LWidth == LHeight) {//Square logo
    var Percent = 15; /* Resize logo to percentage of smallest side of doc */
    var percentageHeight = ((docHeight/LWidth)*Percent);
    var percentageWidth = ((docWidth/LWidth)*Percent);
    if(docWidth < docHeight){
    myDoc.activeLayer.resize(percentageWidth,percentageWidth,AnchorPosition.MIDDLECENTER);
    }else{  
      myDoc.activeLayer.resize(percentageHeight,percentageHeight,AnchorPosition.MIDDLECENTER);
    var LB = myDoc.activeLayer.bounds;
    X = X - LB[2].value;
    Y = Y - LB[3].value;
    activeDocument.activeLayer.translate(X,Y);
    activeDocument.activeLayer.opacity=Opacity;
    app.preferences.rulerUnits = startRulerUnits;
    function placeFile(placeFile) {
    var desc = new ActionDescriptor();
    desc.putPath( charIDToTypeID('null'), new File(placeFile) );
    desc.putEnumerated( charIDToTypeID('FTcs'), charIDToTypeID('QCSt'), charIDToTypeID('Qcsa') );
    var desc2 = new ActionDescriptor();
    desc2.putUnitDouble( charIDToTypeID('Hrzn'), charIDToTypeID('#Pxl'), 0.000000 );
    desc2.putUnitDouble( charIDToTypeID('Vrtc'), charIDToTypeID('#Pxl'), 0.000000 );
    desc.putObject( charIDToTypeID('Ofst'), charIDToTypeID('Ofst'), desc2 );
    try{
    executeAction( charIDToTypeID('Plc '), desc, DialogModes.NO );
    }catch(e){}

  • Distribution percentage in the case of multiple acct assgt

    Hello Gurus,
    While creating a PO for services, for the service line items I have a challenge to make Distribution percentage in the case of multiple acct assgt to two decimal places. Currently it is one decimal place, How do I achieve this.
    To be more to the point -
    We have a business scenario for multiple account assignments in purchase orders. The cost would need to be split into different percentages while creating the PO for service items. The customer requirement is that the percentage split needs to be up to 2 decimal places (Say 25.57, instead of 25.5 which the present SAP environment gives ). This is because the field VPROZ which governs this in the data dictionary is limited to only one decimal place. Is there a configuration to set this field to 2 decimal places?
    Regards
    SS
    Edited by: Shankar Shivappa on Mar 26, 2009 1:26 AM

    Hi!
    First some minor remark: if you are in a newer release, use a class to define the 'tab':
      class cl_abap_char_utilities definition load.
      data: l_field_seperator.
      l_field_seperator = cl_abap_char_utilities=>horizontal_tab.
    Then you have a char1 field with the tabulator.
    But looking at your code: why do you concatenate at all? You make an effort to assign % to empty fields, later you convert them back to space...
    I would use a fixed structure. If you would like to have separators, I would include as every second field a sep01, sep02, sep03... which will be filled with '|', ' ', or the tabulator (just as you like).
    Then you have a fixed field width - if you prefer to have shrinked display, just move this structure into a char255 field and use statement condense -> separatores like '|' will remain, but empty texts like ekpo-txz01 will be smaller.
    In newer releases (700?) the concatenate has an option 'respecting blanks' -> you don't need the macros any longer, even if you stay with the concatenate version.
    Regards,
    Christian

  • Hyperion Planning: Is it recommended to edit the default dimension name?

    Hi,
    We have created a new Planning application, where we have default dimensions (Account, Period, Year, Scenario, Version & Entity) created automatically.
    1. Can we edit the default dimension name as per my requirement?
    2. If so, will there be any impact if we edit?
    Note: Just created Planning application only. Database is not yet created.
    Your help will be highly appreciated.
    Thanks
    Dhamu

    But it's not recommended to change any standard dimension names in planning application.^^^Really? Why?
    Regards,
    Cameron Lackpour

  • Problem using 2 Fact tables with the same dimension

    Hi,
    I have noticed a very strange behaviour in Presentation Services / BI Administrator. I have 2 cubes (created in OWB) which are in the same business model, they are set up with foreign keys etc. and works as they should using them separately. Problem is (sometimes!) when I want to use the common dimension (Project) against both of the fact tables (Sales Order and Purchase Order).
    Scenario 1:
    If I use Project Id, Purchase Amount, Sales Amount I get either an amount in Sales Amount or in Purchase Amount, BUT if the Project Id starts with a letter (not starting with a number) it will show the correct amount for both Sales- and Purchase Amount.
    Scenario 2:
    I use Project Description (even followed by Project Id or not), Sales Amount, Purchase Amount I get the correct numbers for all projects. Project Description must come before Project Id or else it will not work.
    I only noticed this problem when using both of the Fact tables since I want to compare Sales Amount and Purchase Amount in each Project. The Dimension for Project consist of Project, Sub Project and Activity and works fine. If I only use Sales Amount or Purchase Amount with Project Id I don't get this error. Only when both numbers are used.
    I would be very happy if anyone have a good solution/explanation to this problem! Seems like could be something in the BI Server memory that goes wrong somewhere.

    The strange thing is that the results from the queries are correct running them in SQL Developer. This is one that works:
    SELECT Project.Project saw_0, "- SalesOrderFact"."Sales Amount" saw_1, "- PurchaseOrderFact"."Purchase Amount" saw_2, REPORT_SUM(saw_1 BY ), REPORT_SUM(saw_2 BY ) FROM SalesOrder ORDER BY saw_0
    SALES ORDER:
    select T3032.PROJECT_DESCRIPTION as c1,
    sum(T161.SALES_AMOUNT_LOCAL) as c2
    from
    DIM_PROJECT_V T3032,
    CUBE_SALES_ORDER T161
    where ( T161.DIM_PROJECT = T3032.DIMENSION_KEY )
    group by T3032.PROJECT_DESCRIPTION
    order by c1
    PURCHASE_ORDER:
    select T3032.PROJECT_DESCRIPTION as c1,
    sum(T3020.TOTAL_BUY_AMOUNT) as c2
    from
    DIM_PROJECT_V T3032,
    CUBE_PURCH_ORDER T3020
    where ( T3020.DIM_PROJECT = T3032.DIMENSION_KEY )
    group by T3032.PROJECT_DESCRIPTION
    order by c1
    And this will give the wrong result in Answers (correct in SQL..):
    SELECT Project."Project Id" saw_0, "- SalesOrderFact"."Sales Amount" saw_1, "- PurchaseOrderFact"."Purchase Amount" saw_2, REPORT_SUM(saw_1 BY ), REPORT_SUM(saw_2 BY ) FROM SalesOrder ORDER BY saw_0
    SALES_ORDER:
    select T3032.PROJECT_KEY_NAME_ID as c1,
    sum(T161.SALES_AMOUNT_LOCAL) as c2
    from
    DIM_PROJECT_V T3032,
    CUBE_SALES_ORDER T161
    where ( T161.DIM_PROJECT = T3032.DIMENSION_KEY )
    group by T3032.PROJECT_KEY_NAME_ID
    order by c1
    PURCHASE_ORDER:
    select T3032.PROJECT_KEY_NAME_ID as c1,
    sum(T3020.TOTAL_BUY_AMOUNT) as c2
    from
    DIM_PROJECT_V T3032,
    CUBE_PURCH_ORDER T3020
    where ( T3020.DIM_PROJECT = T3032.DIMENSION_KEY )
    group by T3032.PROJECT_KEY_NAME_ID
    order by c1
    As you can see the SQL look very familiar, and I cannot see anything in SQL that should be the cause of this error. I think the error must be in the BI Memory or something.
    Any ideas?

  • Time Dimension, i don´t bind the fact dimension and the time dimension

    Well i don´t know why my fact table don´t bind with the time dimension, i create a time table in the data base and change the key to int32 for example year(date)*10000+month(date)*100+day(date),  and create to similar in the fact table, and
    this attributes binding, when i process the dimension all result without problems, after i process the cube and all result without problems, but when i try to deployment the browser, the measures in all years are equals, please help me

    Hi franciscofelipe,
    According to your description, you find the measures shows all same value for all years of time dimension. Right?
    In this scenario, since your change the key of your time table into an integer, when pulling this dimension out in Browser, the measure will only regards those members as numeric value instead of date so that is will show an aggregate value. Even
    all the members are displayed properly in your dimension. So please change the attribute type into appropriate date type.
    If you have any question, please feel free to ask.
    Regards,
    Simon Hou
    TechNet Community Support

  • Creating scenario dimension and loading data

    Hi all,
    We have two fact tables. The first one is sales that include quantity and subtotal columns. The other one is budget that include quantity and subtotal. We are working with hyperion essbase 9.3. First of all we are creating two model. For sales model we create 7 dimensions (product, chanell, time, company, currency, customer, account) and 3 attribute dimension and for budget model we create 4 dimensions (account,company,customer,product) in metaoutline. And we create 2 application for each metaoutline. We plan to report sales vs budget but we don't know how to join sales and budget data. Everybody recommends scenario dimension. we don't know how to create sceneraio dimension and in which application Essbase integration or Essbase administration services.
    thank you.

    I agree with Cameron. The best way is to put them into one cube. Since you are using a SQL source you can manulate it to have your budget load to the same time level as your actuals. For example suppose you load actuals daily and Budget is Monthly. for consistancy, you could load the budget data into the 15th day of the month. At the Monthly level where you would compare budget to actual, the numbers will be correct. Loading into dummy members for the dimensions that don't exist for budget is a common practice when trying to sync up data. If you really want to make it easy, you could union a view to make it look like you have a single fact table (based on the combo of budget and actual) and have a single metadata outline to load everything. I prefer having two because of different load requirements, but this is an option.
    If you don't want to go this way, the next option is to partition your budget data into the actuals cube. this would keep them seperate but allow you to see them togeter. Between the two option, I prefer the single cube approach better

  • Create users and assigning them security on the Entity dimension

    Hi All,
    I’m working with Hyperion ESSBASE 11.1.1.3 and Hyperion Planning 11.1.1.3 and I have a problem related to create new users (without admin permissions) and assigning them security on the Entity dimension.
    When I access with these users to a Dataform in Planning appears these message:
    “Security and/or filtering has resulted in a required dimension not being represented on this data form”
    I have followed these steps:
    - I have created new users (Native Directory) and provision them against essbase and the planning application in Shared Services.
    - I have expanded the essbase server > security > refresh security from shared services > all users.
    - I have assigned security roles in all members of Entity dimension in Planning.
    - I have refreshed database and security filters in Planning.
    Please help
    Thanks a lot in advance

    Hi,
    You will have to apply security to all the standard dimensions and not just entity, so that will be account, entity, scenario and version.
    Cheers
    John
    http://john-goodwin.blogspot.com/

  • Scenario dimension

    Can I create a Scenario Dimension in OBIEE?
    Somethin like this:
    Scenario Dimension:
    Scenario 1
    Scenario 2
    When the user select Scenario 1 the Metric 1 should be showed and when the user select Scenario 2 the Metric 2 should be showed..
    Now I create a relationship between the fact and the dimension with (1=1) on the condition... and a calculated measure called just Metric with a case inside...
    But I have problem setting a default escenario to be displayed...
    Is this the rigth way?
    Thanks
    Edited by: user647818 on 08-03-2010 04:01 PM

    but I'm trying to create a rpd for ad-hoc queryOk then, other option: create a logical column which is calculated and uses a dimension attribute as criteria.
    CASE "Sample Sales"."D2 Market"."M04  Region" WHEN 'East' THEN "Sample Sales"."F0 Rev Base Measures"."1-01  Revenue  (Sum All)" WHEN 'South' THEN "Sample Sales"."F0 Rev Base Measures"."2-01  Billed Qty  (Sum All)" else 0 ENDResult:
    http://picasaweb.google.com/lh/photo/1Wzjw9j4tBLuQgkfHJAMTA?feat=directlink

  • Re-Order the Sparse Dimensions

    Hi,
    We have a typical scenario where in we need to change the order of sparse dimensions in the outline.The cube is already in use,however,as we got rid of few members in one of the sparse dimension and we want to change the order of sparse dimensions in the outline to enhance the performance.
    My question here is,
    1.How to change the order of the sparse dimensions in the outline?
    2.What would be the impact?
    Any quick response on this is highly appreciated !!
    Thanks,
    RNG

    1) We can improve calculation performance by changing the order of standard (not attribute) sparse dimensions in the database outline. We can Order standard sparse dimensions by the number of members they contain, placing the dimension that contains the fewest members first.
    This arrangement provides a number of possible improvements, depending on the site:
    ●The calculator cache functions more effectively, providing approximately a 10% performance improvement if you have a database outline with a very large dimension (for example, a dimension containing 1000 members).
    ●Parallel calculation, if enabled, is more likely to be used if the standard sparse dimension with the most members is the last standard sparse dimension in the outline.
    2) I think there would not be an any impact...
    JSA

Maybe you are looking for