Key figure diffrence in Dev and Pro

Hi Experts,
I have one cube in Dev and Production but key figure Current Price out put is difference in both
like dev it comes 30.12 and in production getting like 30,12.
but make sure i am using same keyfigure.
Thanks
David

Check the user default settings in SU01D tcode in dev and pro.
SU01D -> enter ur user id -> goto Default tab and check the decimal notation.
I guess it is 1,234,567.89 in DEV and 1.234.567,89 in PRO.
Please make sure that this setting is same in DEV and PRO.
you can ask your basis consultant to changes the settings....
--- Thanks...

Similar Messages

  • Key Figure format in Years and Months..

    Hi,
    Is there any Key figure similar to 0SRVCLENKYF (Length of Service (in Years)) part of Headcount and Personnel Actions, which should give me value in Years and Months..?
    Thanks in Advance,
    Thanks,
    Madhu.

    For curiousity sake...if you use the FIMA_DECIMAL_MONTHS_AND_YEARS Function Module, the output that you'll get is a months and years in fractional amounts. So, how are you going to get the Years and Months from this?
    For example, if the from date is 20000101 and the to date is 20090914, the results from this Function Module will be Months = 116.42740 and Years = 9.70228. If you do use this, I'd suggest taking the whole number from passed value for years (9 in this example) and then calculate months by taking the franctional amount of the passed value for years and multiple it by 12 (0.70228 * 12), you end up with 9 Years, 8 Months (8.42736 to be exact, but you're going to want to truncate it to 8 so that when it goes above 8.5, the value doesn't become 9 when it still should be 8).

  • Key Figure's Result Summation and SUMGT

    Goal: I need to capture the report’s  Results for KF1 and KF2 to use it in the same report for further calculations. However, the report should include into Results calculations only the records that have KF1 or KF2 with values greater than 0.
    Potential Solution: Create a Formula that uses Function SUMGT (or SUMCT, SUMRT) on the desired key figures and use conditions at the query level.
    KF1 Property:     Calculate Result As SUMMATION
    KF2 Property:     Calculate Result As SUMMATION
    Report with No Conditions:
    Year      KF1     SUMGT’KF1’     KF2     SUMGT’KF2’
    2001     10        70                         10        90
    2002     20        70                         20        90
    2003     0          70                         30        90
    2004     40        70                         30        90
    Result   70        70                         90        90
    Report with Conditions:
    KF1 > 0
    or
    KF2 > 0
    Year     KF1     SUMGT’KF1’     KF2     SUMGT’KF2’
    2001    10         70                        10         90
    2002    20         70                        20         90
    2004    40         70                        30         90
    Result  70         70                        60         90
    Problem: When Conditions apply the SUMGT (as well as SUMCT and SUMRT) do not take them into consideration and includes in its calculations the excluded records as well.
    Questions:
    1. How can I make SUMGT (or any of the other tow) return a result that take into consideration the specified conditions?  For KF2 the Result should be 60 and NOT 90.
    2. Is there any other way I can capture the Results for KF1 and KF2 when the above specified conditions are implemented?

    I think No of repair days is a characteristic..
    What you can do is create a formula variable with user input. User will enter no of repair days in it.
    Now create a variable on no of repair days of type customer exit.
    In the exit read the value of the formula variable and assign it to that variable.
    Restrict your key figure no of completed orders with that variable...

  • Problems with key figure quantities between ODS and PSA

    We have some key figures which are part of the purchasing transactional load.  The key figure in some cases is showing the correct total value for the ordering unit in the PSA but incorrect in the ODS (there is no transformation logic).  This seems to happen when an ordering unit exists but a base unit of measure does not exist? Has anyone had similar and how to resolve? Thanks

    Hi, thanks for the quick reply. I forgot to mention that. As I wrote before, this percentage is given to us directly in the file that is loaded on the system, but since there were problems when taking away a characteristic from the table, I created a formula which should give us the same data. The formula is Percentage = "Products Sold / Total Products" (I used the Percentage part operator, so it looks like this "Products Sold %A Total Products"). The TOTALS value is validated with the person in charge of giving us the file to load.
    A sample data record:
    DATE--SHOP_ID-DEPT-PRODUCTS-SOLD---PCT.
    20080101--125020--
    40
    Edited by: Pedro Olvera on Aug 1, 2008 12:21 PM

  • Integrated Planning and Non-cumulative key figure

    Hi
    I´m creating an Integrated Planning application and a problem has occurred. The users want to plan on inflow and outflow and at the same time have a row with the total sum in the same layout (they are planning on 0CALMONTH and 0ORGUNIT) This can e.g. be solved through use Web Application Designer with one planning query and one traditional query.
    Any way. I have created a non-cumulative key figure with an inflow- and an outflow key figure. The problem is that the non-cumulative key figure starts working first when I change the planning mode from plan status to load status. I could use function modules, to change the status, behind the save button but there are several users who are planning at the same cube at the same time and I don´t want to lock the others from planning.
    How to solve this?
    - Is it possible to restrict the switching, from plan to load, by setting some kind of filter at the users org.unit? (0ORGUNIT is an authorization object)
    - Is it possible to create a process chain and then load the data to another cube for reporting at just this key figure? And also here have a filter at the org.unit
    I will gladly get all kind of idea and input to solve this problem. Maybe there is some other way to go than using non-cumulative key figureu2026

    Thanks for your answers
    I have tried different scenarios and I will use a u201Dsave-buttonu201D. In the save-button I use the commands SAVE_DATA and EXECUTE_PROCESS_CHAIN. The command u201CEXECUTE_PROCESS_CHAIN starts a process chain that switches from plan mode to load mode and then back to plan mode again.
    One new problem has arisen. The non-cumulative key figure is updating if an existing value (inflow- or outflow) is changed. But if an input is made to an empty cell, without value, nothing happen when I press on the start-button. BUT if I refresh the browser the non-cumulative value is updated!!!
    Is there any command in WAD that refresh the whole page? If so I can include it in my start-button.
    If not, any sugestion on how to solve the problem?
    Best regards
    Mikael

  • COPA calculated key figures and scheme on R/3 side

    We have created calculated key figures on the R/3 side and inputted formula (which is essentially the scheme/basic formula in transaction KER1) for this key figure.  We then checked off this key figure in the COPA datasource.  These key figures are only adding and subtracting certain elements for a particular record.  In RSA3 on the R/3 side, this key figure is calculated correctly.  In BW, in the PSA, it's calculated correctly.  The problem is when it goes to the ODS.  It gets no values.  All 0's.
    Does anyone have any ideas?  It's straight forward mapping and I'm thinking it's a bug, but wanted to check if there was anyone that had this problem before and some "hidden" config had to be done.
    Thanks,  Mark.

    Anyone have any ideas?

  • Sort the Key Figure and put a count on it

    Hi Experts,
    I have a  situation where I have to sort the value of the Key Figures in ascending order and put a count on them.
    Kindly elaborate me a little on this.
    Thanks in advance,
    Kannan

    Hi Kannan,
        If you want to do this setting at the Query Designer level, then select the Properties section for the
    desired Key figure say K1.then select the "Calculations " tab.  Under the Local calculations for "Calculate Results as" select "Counter for all detailed values".Save the query.
    Open the query (say) at Bex Analyzer. From  the context menu for the key figure K1, select "Properties"-->then under Sorting tab select the required order.
    The options mentioned above, i.e  "calculations" and "Sort" is available on web too in the context menu for the key figure.
    The above mentioned setting wil be a display setting>You can modify it as per your requirement at Query Designer.
    NOTE:
    If your requirement is such that K1, should always display the counter , then while creation of the K1 itself , you can select the Exception Aggregation of Type "Counter(all values)". Then, the setting will be permanent.(design time)
    Hope the information helps!
    Best Regards,
    Akshata
    Edited by: Akshata Shenoy on Jun 2, 2009 12:25 PM
    Edited by: Akshata Shenoy on Jun 2, 2009 12:27 PM

  • Difference between cumulative and non-cumulative key figures

    Hi,
    What is the difference between cumulative and non-cumulative key figures and under what conditions they are used. What is snapshort and where it is used.

    Hi.............
    Basically the key figures are of two types cumulative and non cumulative.
    Cumulative are the normal one which you use always and they always bring the new values of the key figures in the delta that is if suppose A has value 10 and after change the new value is 20 then you will use cumulative key figures there, and your delta( new value) will bring 20.
    but suppose your key figures field only the change in the prior value that is in this case the delta in the key figure value will bring 10 (20-10- change of 10 )as new value in the key figure A then you will have to model it through the non cumulaitve key figures.
    Now
    1) Cumulative is for the first case that is if the key figure alwyas brings the new values of the key figure and not the change sin the key fiures value.
    2)NCum. value with NCUM value change:
    In this case ther is only one field which brings the changes for a particualr key figure and you ahve to define that key figure as non cumulative.
    Ex: In case of stock only one filed brings both ingoing value and outgoing value so 10 ,-4,100,-34.....
    In this case you will this option and use the key figure here in the space provided.
    3) In this case you haev two separate key figures one for the inflow of stocks and one for the outflow of the stocks.
    you use one key figure for the inflow and one key figure for the outflow.
    The main key figure autiomatically takes care of the logic and gives the correct output upon the summation
    net value of stocks( inflow- outflow).
    Also do remember in this case the key figure for inflow and out flow are the basic key figures that is cumulative key figures.
    A non-cumulative is a non-aggregating key figure on the level of one or more objects that is always displayed in relation to time. Examples of non-cumulatives include headcount, account balance and material inventory. here the aggregation of key figure is based on the another info object
    There are two different ways to define non-cumulative key figures:
    • Non-cumulative key figure with non-cumulative changes:
    Before you can define the non-cumulative key figure, an additional cumulative key figure containing the non-cumulative change must exist as an InfoObject.
    • Non-cumulative key figure with inflows and outflows
    There has to be two additional cumulative key figures as InfoObjects for non-cumulative key figures - one for inflows and one for outflows. The cumulative key figures have to have the same technical properties as the non-cumulative key figure, and the aggregation and exception aggregation have to be SUM.
    Features of non-cummulative key figures
    A non-aggregating key Figure.
    Records are not summarized for Reporting
    Exception Aggregation is being applied on these key figures on the level of one or more info objects usually with time .
    Examples: Head Count, Account balance, Material stock
    consider simple senario
    Date Net Stock Quantity Sales Revenue
    01.02.2005 40 1000
    02.02.2005 50 2000
    03.02.2005 25 3000
    this is the query output if stock quantity has treated as cummulative and non-cummulative key figures
    if stock quantity taken as a cummulative key figure
    Date NET STOCK QUANTITY SALES REVENUE
    01.02.2005 30 1000
    02.02.2005 50 2000
    03.02.2005 20 3000
    RESULT 100 6000
    in the above result the key figure has aggregated to the total value that wont give sense to the net stock quantity
    if stock quantity taken as non-cummulative key figure
    Date Net Stock Quantity (LAST) Sales Revenue
    01.02.2005 30 1000
    02.02.2005 50 2000
    03.02.2005 20 3000
    RESULT 20 6000
    Hope this helps you..............
    Regards,
    Debjani................
    Edited by: Debjani  Mukherjee on Sep 15, 2008 7:22 AM

  • APODPDANT and Auxiliary Key Figures

    Hi All,
    Please help me when i am creating planning book how can i add APODPDANT Key Figures and tell me what is Auxiliary Key Figures how can i use this in planning book.

    Hi
    IF u want to add the apodpdant keyfigure in to planning book forst it has to be defined in the planning area that u create.
    please look at /sapapo/msdp_admin --->planning area -->details.IF u dnt find it add it in planning area then to planning book.
    Auxilary key figures are used when u want to perform some calculations and store for temporary basis.Use it again to display the final key figure.Mostly auxilary key figures are used in macors and in statistical forecsting techniques.
    For ex:
    U have to calculate total demand for forecast +  corrected forecast + additional forecast. Then u use this key figure as total demand and use for further calculations.
    The data in auxillary key figures are not saved in demand planning.U can add this key figure in data view as auxillary keyfigure tab with necessary description
    HOpe am clear
    Thanx

  • Key figure Explaination in SNP planning books 9ASNP94

    Dear Experts ,
    I am curious to know regarding SNP planning books key figures
    when i am exploring sap standard  Planning book
    9ASNP94
    Data view : SNP94(1)
    I can able to see many KEY FIGURES  Please refer below
    I AM NOT SURE how they are used in planning , i mean  what is clear definition of those key figures and i see some key figures are grey out and some or open for entry
    how to find those detail information
    when i go  to T code SDP84 - define planning book
    i can able to see those descrption and infocubes but not sure how to understand clearly , would be more thankful if some give me a clear explaination of it
    Forecast     TXT                                                                                                                   
    Sales Order     TXT                                                                                                                   
    Distribution Demand (Planned)     TXT                                                                                                                   
    Distribution Demand (Confirmed)     TXT                                                                                                                   
    DistrDemand (TLB-Confirmed)     TXT                                                                                                                   
    Dependent Demand     TXT                                                                                                                   
    Total Demand     TXT                                                                                                                   
    Distribution Receipt (Planned)     TXT                                                                                                                   
    Distribution Receipt (Confirmed)     TXT                                                                                                                   
    Distribution Receipt (TLB-Confirmed)     TXT                                                                                                                   
    In Transit     TXT                                                                                                                   
    Production (Planned)     TXT                                                                                                                   
    Production (Confirmed)     TXT                                                                                                                   
    Manufacture of Co-Products     TXT                                                                                                                   
    Total Receipts     TXT                                                                                                                   
    Stock on Hand     TXT                                                                                                                   
    Supply Shortage     TXT                                                                                                                   
    Safety Stock     TXT                                                                                                                   
    Reorder Point     TXT                                                                                                                   
    Target Days´ Supply     D                                                                                                                   
    Target Stock Level     TXT                                                                                                                   
    Days´ Supply     D                                                                                                                   
    ATD Receipts     TXT                                                                                                                   
    ATD Issues     TXT                                                                                                    
    Many thanks & Regards
    Raj

    Hi
    Please find below the short summary of each key figures.
    Forecast TXT  :- FCST which has been released from APO DP to APO SNP
    Sales Order TXT :- Sales order transferred from ECC to APO via CIF.
    Distribution Demand (Planned) TXT :- Dependent demand coming from other location to this location for same product. Network planning
    Distribution Demand (Confirmed) TXT :- In case deployment , we confirm the Distribution Demand (Planned) will appear her.
    DistrDemand (TLB-Confirmed) TXT :- Mainly used in case of TLB.
    Dependent Demand TXT :- Dependent demand coming from parent product in case of BOM
    Total Demand TXT :- The sum of all above demands is called as Total Demand.
    Distribution Receipt (Planned) TXT :- SNP created Purchase req will appear in this key figure.
    Distribution Receipt (Confirmed) TXT :- In case of deployment Distribution Receipt (Planned) will be get confirmed in the Distribution Receipt (Confirmed) key figure.
    Distribution Receipt (TLB-Confirmed) TXT :- Mainly used in case of TLB.
    In Transit TXT :- In will contain the in transit stock which will transfer for ECC via CIF.
    Production (Planned) TXT :- Planned order will get created via SNP in case of domestic mfg.
    Production (Confirmed) TXT :- In case of SNP deployment Production (Planned) will be get confirmed in the Production (Confirmed)) key figure.
    Total Receipts TXT  :- Total of all the receipt elements as been used.
    Stock on Hand TXT :- Stock has transferred from ECC or R3 via CIF.
    Supply Shortage TXT :- This will be calculated with macro based on total demand and total receipt.
    Safety Stock TXT :- Based on SNP master data, safety stock will get calculated during planning run.
    Reorder Point TXT :- Based on SNP master data, Reorder Point will get calculated during planning run. . There are different methods of calculating safety stock.
    Target Days´ Supply D :- The safety stock defined in number of days appears based on SNP master data in APO.
    Target Stock Level TXT :- Get calculated by macro  based on Target Days´ Supply D and total demand in future.
    ATD Receipts TXT :- Mainly used for Deployment.
    ATD Issues TXT :- Mainly used for Deployment
    If you require any specific information for any key figure please do let me know.
    I hope this will be useful for you.
    Thanks
    Amol

  • Key Figure Restrictions in Query

    Hi all,
    I've got this scenario on hand:
    I want to display a Bex report with the a particular key figure (Actuals) restricted to only specific value COMBINATIONS of two characteristics (Cost Centre and Cost Element). i.e. The restrictions should only apply for each individual combination of the characteristics (e.g for Cost centre = S0561 and Cost Element = 70400 , another combination could be for Cost Centre = S0352 and Cost Element = 70610 ).
    The challenge here is that if you restrict the key figure based on the individual characteristics (say, for Cost Centre = S0561 , S0352 and for Cost Element = 70400 , 70610) then it blocks off other figures from characteristic combinations that are should be allowed (e.g. Cost centre = S0561 and Cost Element = 70610 ,  and another combination of Cost Centre = S0352 and Cost Element = 70400).
    Any suggestions on how to handle this, typically from a previous experience, will be appreciated.
    Regards,
    Uche

    Hi Uche,
    A workaround for this scenario would be to include a hidden keyfigure for every characteristic combination. (If there are not many combinations)
    For e.g.
    Hidden KF1  Restricted on Cost centre = S0561 and Cost Element = 70400
    Hidden KF2  Restricted on Cost Centre = S0352 and Cost Element = 70610
    Then another final key figure, which is visible and is a formula KF
    Actuals     Formula = Hidden KF1 + Hidden KF2 + ..
    Best Regards,
    Dabre

  • Key figure schema in CO-PA reporting

    Hallo SAP Gurus,
    Is there any method to copy the key figure schema created in one operating concern to other operating concern in the same client?
    In our company, we have 18 operating concerns for 18 company codes.
    I have created one key figure schema for one of the operating concern ( Since as per my knowledge, key figure schema can be created only at the operating concern level. )
    Now, since the schema is common to all the operating concerns, I want to copy the same to the other 17 operating concerns.
    Expecting your help since creating key figure schema 18 times and updating any changes is very much time consuming.
    regards,
    Viswanathan T R

    Hi Vishwanathan,
    I have a same requirement, I want to do KECP because this is asking us to give the transport request and I know when we create key figure scheme we save it under a transport request.
    Did KECP help you in doing that? If not, please let me know how did you copy key figure scheme from one operating concern to other.
    Thanks
    Srinath

  • Adding a new key figure to Info Cube

    Can I add a new key figure to an existing Info cube in which data is loaded?
    Assume that In Info Cube we have the following.
    Stu Id -- Characteristic
    Maths , Physics , Chemistry -- Key figures
    These are the info objects which are already available and transfer rules are already available for the same in the infosource.
    Could any one let me know how to add one more new key figure (total ) , which is the sum of the three marks to the Info Cube and populate the data in to the same.
    I have tried the following steps ,  but could not get the solution.
    1). Create a new key figure info object (total).
    2). Add the same to the communication and pull the same into transfer rules of the existing info source and activate the same.
    3). Add the new key figure to the info cube.
    4). Open transfer rules for the info cube and change the mode from NO updation to Addition for the particular key figure (total).
       When I perform the 4th step it is giving a red symbol beside the key figure in update rules and I'm not able to activate the same.
    Any help on how to add key figures to update rules and transfer rules is highly appreciated and points would be assigned.
    Thanks

    1.add new Keyfigure to Infocube.
    2.Go to Update rules> go to update type of that Keyfigure>selct formula in update method>create new formula>here you can add up your 3 keyfigures-->OK.
    activate update rules and InfoProvider.Check all are active or not..
    by using Export generate datasouce ,you populate data(historical data)  to new keyfigure as well.Then you have to delete historical data requests.
    or iyou can create formula in query designer as well as srinivas suggested.that would be better option.

  • Some key figures are not being correctly reversed in the Change Log

    Hi Experts,
    I'm working with the BI 7 (SP 15) and I have created an ODS with Overwrite option (Record Mode equal to ' ') and a Cube receiving data from this ODS.
    Whenever I have a change in one existing record in R/3 side (already previously loaded to BW), it comes perfectly to the ODS and overwrite the record in the Active Data. However, in the change log table, the before image record is not reversing all the key figures, there is one (Quant type) which is not working and it is being doubled in the cube. All the other key figures are Amount type and are working fine. PLease see below some examples of the Change Log behavior:
    First time the record comes - Change log content:
    Material   Valid Dt   Cost Value      Quantity Rec. Mode      Req. ID
    1234     May/01   $  100.00       10          'N'     1
    Second time when the record changes the Date:
    Material     Date      Cost Value      Quantity Rec. Mode      Req. 1234     May/29   $  100.00       10          '  '     2
    1234     May/01   $  -100.00       10          'X'     2
    Then the final result in the cube, after it is compressed, is:
    Material     Date      Cost Value      Quantity
    1234     May/29   $  100.00       20      
    Also, I have a Counter in the transformation to the Cube which is a constant equal to 1, it is also being aggregated erroneously. I could create a routine to check the record mode coming, but I'm not sure it is the best solution.
    Can anybody help me to figure this out, please?
    Thanks in advance.

    Hi Rajkumar,
    Actually it is a generic extractor (customized) and the ODS active data is getting the delta records correctly. After I extract from R/3 and activate the ODS, the active table has correct results, but the change log table has the problem described before. All the fields comes from one single extractor.
    The 0RECORDMODE that I mentioned is about the setting in the transformation to the ODS. You have the Technical rule group where you can set the 0RECORDMODE, in my case it is set to ' ' (blank) which means it will receive After-Images from the extractor (which I think is correct in my case). The most curious is that it is working for almost all key figures (all amount type), except for the Price Unit which is Quantity type.
    Any other ideas?
    Thanks.

  • Subtraction of two key figures normalized to result not working as expected

    Hello SAP Community!
    I am having problems with getting the right result from a subtraction of two KFs which are "normalized to results" which means the KFs really have values expressed as percentages. The substraction that should be performed is of two percentages (e.g.: 87.298% - 85.527% = 1.77%) but my report prints out the result as "number of units" instead (e.g.: 87.298% - 85.527% = 71,514.00 EA). The two normalized KFs actually "point" to two stock KFs, hence the "number of units".
    In order to explain the problem I am facing please analyze below text:
    1) Let's assume I have below data:
    LOAD MONTH  PLANT    MATERIAL HORIZON MONTH     FORECAST UNITS
    200805         PLANT-A  MAT-1            200805         510,235.00
    200805         PLANT-B  MAT-1           200805          74,240.00
    200805         PLANT-A  MAT-1           200806         438,721.00
    200805         PLANT-B  MAT-1           200806          74,240.00
    200805         PLANT-A  MAT-1           200807         356,981.00
    200805         PLANT-B  MAT-1           200807          74,240.00
    200806         PLANT-A  MAT-1           200805               0.00
    200806         PLANT-B  MAT-1           200805               0.00
    200806         PLANT-A  MAT-1           200806         510,235.00
    200806         PLANT-B  MAT-1           200806          74,240.00
    200806         PLANT-A  MAT-1           200807         438,721.00
    200806         PLANT-B  MAT-1           200807          74,240.00
    2) Then, assume I have a comparison report, restricted by load month for two months May and June 2008 (filter restricted by two month variables) with FORECAST units spread accross columns for whole horizon (two months also in this case).
    Material  Plant                                 2008/06     2008/07
    ===================================================================
    MAT1      PLANT-A  
                       Base Units (May 2008)        438,721.00  356,981.00
                       Comparison Units (June 2008) 510,235.00  438,721.00
              PLANT-B  
                       Base Units (May 2008)         74,240.00   74,240.00
                       Comparison Units (June 2008)  74,240.00   74,240.00
              TOTALS   Base Units                   512,961.00  431,221.00
                       Comparison Units             584,475.00  512,961.00
    3) Now, let's suppose we want to know the proportions (%) of Base vs Comparison units, so
    we normalize forecats to results an we get the below report:
    Material  Plant                                 2008/06     2008/07
    ===================================================================
    MAT1      PLANT-A  
                       Base Units (May 2008)        438,721.00  356,981.00
                       Base Units % (May 2008)      85.527%     85.527%
                       Comparison Units (June 2008) 510,235.00  438,721.00
                       Comparison Units %(Jun 2008) 87.298%     82.784%
              PLANT-B  
                       Base Units (May 2008)         74,240.00   74,240.00
                       Base Units % (May 2008)       14.473%     15.702%
                       Comparison Units (June 2008)  74,240.00   74,240.00
                       Comparison Units %(Jun 2008)  12.702%     17.216%
              TOTALS   Base Units                   512,961.00  431,221.00
                       Comparison Units             584,475.00  512,961.00
    4) Finally, let's suppose we want to know the deltas (differences) of Base vs Comparison
    units, for both number of units and %. The report now look as below:
    Material  Plant                                 2008/06     2008/07
    ===================================================================
    MAT1      PLANT-A  
                       Base Units (May 2008)        438,721.00  356,981.00
                       Base Units % (May 2008)      85.527%     85.527%
                       Comparison Units (June 2008) 510,235.00  438,721.00
                       Comparison Units %(Jun 2008) 87.298%     82.784%
                       Delta base vs. comp. units %  1.77%       2.74%
                       Delta base vs. comp. units    71,514.00  81,740.00
              PLANT-B  
                       Base Units (May 2008)         74,240.00   74,240.00
                       Base Units % (May 2008)       14.473%     15.702%
                       Comparison Units (June 2008)  74,240.00   74,240.00
                       Comparison Units %(Jun 2008)  12.702%     17.216%
                       Delta base vs. comp. units %  -1.77%      -2.74%
                       Delta base vs. comp. units         0.00        0.00
              TOTALS   Base Units                   512,961.00  431,221.00
                       Comparison Units             584,475.00  512,961.00
    5) PROBLEM:
    In my report, the "Delta base vs. comp. units %" is not working as expected and
    calculates number of units just as "Delta base vs. comp. units" does instead of calculating the % difference.
    So my report looks as follows:
    Material  Plant                                 2008/06     2008/07
    ===================================================================
    MAT1      PLANT-A  
                       Base Units (May 2008)        438,721.00  356,981.00
                       Base Units % (May 2008)      85.527%     85.527%
                       Comparison Units (June 2008) 510,235.00  438,721.00
                       Comparison Units %(Jun 2008) 87.298%     82.784%
                       Delta base vs. comp. units %  71,514.00  81,740.00 <<<WRONG!!
                       Delta base vs. comp. units    71,514.00  81,740.00
              PLANT-B  
                       Base Units (May 2008)         74,240.00   74,240.00
                       Base Units % (May 2008)       14.473%     15.702%
                       Comparison Units (June 2008)  74,240.00   74,240.00
                       Comparison Units %(Jun 2008)  12.702%     17.216%
                       Delta base vs. comp. units %       0.00        0.00
                       Delta base vs. comp. units         0.00        0.00
              TOTALS   Base Units                   512,961.00  431,221.00
                       Comparison Units             584,475.00  512,961.00
    The formulas are:
    a) Delta base vs. comp. units %
      Delta base vs. comp. units % = Comparison Units % - Base Units %
    b) Delta base vs. comp. units
      Delta base vs. comp. units = Comparison Units - Base Units
    The KFs
    - Comparison Units %
    - Base Units %
    Are RESTRICTED key figures (restricted to Base and comparison month variables) which
    are setup as:
    1) Calculate Result As:  Summation of Rounded Values
    2) Calculate Single Value as: Normalization of result
    3) Calculate Along the Rows
    The KFs
    - Delta base vs. comp. units %
    - Delta base vs. comp. units
    are FORMULAS setup to:
    1) Calculate Result As:  Nothing defined
    2) Calculate Single Value as: Nothing defined
    3) Calculate Along the Rows: user default direction (grayed out)
    Thanks for the time taken to read in detail all of this. Long text but necessary to understand what the problem is.
    Any help is highly appreciated.
    Thank you.
    Mario

    Hi,
    The subraction will be carried out before doing the normalization of your KF's. So, it is displaying "number of units". Create a calculated keyfigure and subtract the KF's and in the properties of this calculated keyfigure, change the enhancement as "After Aggregation".
    I hope this will solve your issue.
    Regards,
    S P.

Maybe you are looking for