![]() “Formula 2” is correct for all aggregation nodes, because we used formula in BEX query.(if “Formula 1” is empty, take the value from original aggregation value from “Periodic”. “Periodic” is 0.7 (incorrect), which is a result of 0.2(number calculated from member formula in BPC) + 0.5 (aggregation result from BW, 0.1 +0.4) “Formula 1” on R100T is correct, 0.2(number calculated from member formula in BPC), but it’s empty for T100T, T200T, because we set exception aggregation on BW ( No aggregation on hierarchy). Run the BEX query, you will find the R100T aggregation on:.Use standard aggregation on “Formula 2”(no exception aggregation).If “Formula 1” is empty ( because no aggregation on hierarchy for the exception aggregation), then (“Formula 1” = 0) will return true value, which is 1, the value from “Periodic” will used for the final result. Join Facebook to connect with Freeter Xie and others you may know. This formula is used to check the value for “Formula 1”, if “Formula 1” has a value (not empty), then (“Formula 1” = 0) will return false value, which is 0, it’s going to use the value from “Formula 1”. ‘Formula 1’ + ( ‘Formula 1’ = 0 ) * ‘Periodic’ Create “Formula 2” with following logic:.Set the Exception Aggregation on “Formula 1”as “No aggregation along hierarchy”. ![]() Add “PERIODIC” as restricted key figure, and create “Formula 1” which is actually “PERIODIC”,.Besides the member formula on children nodes, also design accordingly member formula on parent node level (R100T = T100T/T200T). You can move the text by dragging and dropping the Text Element anywhere on the page. R101 and R102 are member formula to calculate ratio. To edit, simply click directly on the text and start typing. R100T and its children nodes R101 and R102 are ratio nodes, which are calculated from T101, T201 etc. Here is account type, account hierarchy setup from BPC side: The solution below is to combine both BPC member formula and BW exception aggregation methodology to handle this challenge for reporting. This is a BPC production limitation at the moment, which is unable to handle exception aggregation on member formula for transient queries, and this can’t be handled in BW side alone either, as BW BEX query is unable to recognize the difference between member formula rows and normal rows. John kadz cello, Pizzolo restaurants sdn bhd, Cegs-02975, H&r block card functions. For example in following table, the correct result should be 0.2, but query result usually displayed as 0.5: Jessica andrade, Kommande laddhybrider, Amy lee chin xie. Member formula is widely used in BPC environment, but many customers facing the same challenge when running queries with aggregation on member formulas, the calculation result is incorrect.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |