\nRule qualifiers determine whether the range of cells need to be calculated at the leaf (N:), consolidated (C:), or at all (N:&C:) levels of the cube. The basic rule syntax is shown below:<\/p>\n
<A range of cells> = N: <Formula for N-cells> ;
\n<A range of cells> = C: <Formula for C-cells> ;
\n<A range of cells> = <Formula for N-cells & C-cells> ;<\/p>\n
The Golden Rule: N-Level Qualifiers<\/strong> Let\u2019s imagine we are reporting sales for a single entity (Figure 1) and we chose an N qualifier. This means all leaf level Products in the Products dimension will become calculated. Therefore, when data is calculated at the leaf level, PA will \u201cNaturally\u201d consolidate at C-levels of the cube.<\/p>\n Figure 2: N-Level Qualifier<\/strong><\/p>\n <\/p>\n <\/p>\n <\/p>\n <\/p>\n <\/p>\n <\/p>\n <\/p>\n <\/p>\n <\/p>\n The Exceptions: C or No-Qualifiers<\/strong> In this case, I want to override PA\u2019s ability to naturally consolidate for the price at the C-level. This will calculate the average price consolidated level only and paints a more understandable picture. Figure 4 shows how the calculation of Gross Margin % uses of no-qualifier and calculates at every intersection of the cube.<\/p>\n Figure 3: N-Level Qualifier<\/strong><\/p>\n <\/p>\n <\/p>\n <\/p>\n <\/p>\n <\/p>\n <\/p>\n <\/p>\n <\/p>\n <\/p>\n <\/p>\n <\/p>\n Figure 4: No-Qualifier<\/strong><\/p>\n <\/p>\n <\/p>\n <\/p>\n <\/p>\n <\/p>\n <\/p>\n <\/p>\n <\/p>\n <\/p>\n <\/p>\n <\/p>\n <\/p>\n <\/p>\n <\/p>\n <\/p>\n <\/p>\n <\/p>\n Overall, rules are a very powerful tool in Planning Analytics and with the right qualifiers you can harness that power and increase your organization’s analytical ability. For more articles on building efficient and effective rules, stay tuned to the QueBIT knowledge base.<\/p>\n","protected":false},"excerpt":{"rendered":" There are several factors to keep in mind when creating business rules in Planning Analytics. What are rules, you ask? Rules are dynamic calculations that enable analysts, department leads, and planners to transform their data into real-time insights. Rules are the secret sauce when reporting in PA, but with great power, comes great responsibility. Adding…<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[24],"tags":[35,36,52],"class_list":["post-3387","post","type-post","status-publish","format-standard","hentry","category-ibm","tag-development","tag-planning-analytics","tag-planning-analytics-development"],"acf":[],"yoast_head":"\n
\nPA\u2019s natural consolidation engine is extremely performant, so N-level rules should be relied upon more when creating rules instead of C or no-qualifier rules. This is the golden rule of PA. The reason why 95% percent of the rules you write will have this N qualifier.<\/p>\n![\"\"](\"https:\/\/quebit.com\/askquebit\/wp-content\/uploads\/2019\/03\/PA1-min.jpg\")
<\/p>\n
\nDid you see what happens to my prices when they are allowed to natural consolidate? The are added up. Given that we want to display an average price at the consolidated level, this is where using a C qualifier makes sense.<\/p>\n![\"\"](\"https:\/\/quebit.com\/askquebit\/wp-content\/uploads\/2019\/03\/PA2-min.jpg\")
<\/p>\n![\"\"](\"https:\/\/quebit.com\/askquebit\/wp-content\/uploads\/2019\/03\/PA3-min.jpg\")
<\/p>\n