--- schema_version: "1" id: 171898a59acf63b38c4e5649e6c9402f71923f0cec54fad1f27c86d40c65ea43 title: Important KPI Settings collection: admin version: current locale: en-us portal_url: https://docs.salesforce.com/admin/current/en-us/ind/264-0-0/concept_kpi_mechanics.md canonical_url: https://help.salesforce.com/s/articleView?id=ind.concept_kpi_mechanics.htm&release=264.0.0&type=5 source_site: help.salesforce.com content_type: documentation content_hash: 7c622ba6f962f35a8076194232fbd2b7b82cd0bab04e14ac8330c78dc54c7495 description: To ensure that KPIs are calculated correctly and show accurate figures, define KPIs with appropriate settings. For example, KPIs that are meant for planning, add the KPIs to Plan KPI Set, and define the object scope for the set as Account. products: - Consumer Goods release: "264" --- # Important KPI Settings To ensure that KPIs are calculated correctly and show accurate figures, define KPIs with appropriate settings. For example, KPIs that are meant for planning, add the KPIs to Plan KPI Set, and define the object scope for the set as Account. Learn about these important KPI settings: Scope, Calculation, and Storage and Visibility. ## Scope These are the important settings to define the scope of a KPI. - Object Scope: The object scope decides the KPI set of a KPI. For example, KPI with Promotion object scope must be added to the Promotion KPI set but not to the Funding KPI set. Add KPIs to the KPI set as listed in the table. |   | Account Object Scope | Promotion Object Scope | Promotion Tactic Object Scope | Payment Tactic Object Scope | Funding Object Scope | | --- | --- | --- | --- | --- | --- | | Plan KPI Set | Yes | — | — | — | — | | Promotion KPI Set | Yes | Yes | Yes | — | — | | Reporting KPI Set | Yes | Yes | Yes | Yes | Yes | | Rate-Based Funding KPI Set | Yes | — | — | — | Yes | | Funding KPI Set | Yes | — | — | — | Yes | | Claim KPI Set | Yes | — | Yes | Yes | — | - Time Scope: The time scope defines the time frame during which a KPI is calculated. You can edit a KPI in the P&L page only during the relevant time frame. For example, a KPI with object scope as Promotion and time scope as Complete is calculated for the complete time frame of the promotion. But, a KPI with object scope as Promotion Tactic and time scope as Shipment is calculated only during the shipment time frame of the tactic. - Time Granularity: Time granularity determines whether a KPI is calculated for a period or subperiod based on its defined formulas. For example, to calculate Revenue accurately even when prices change in the middle of a week, define the time granularity for Revenue as Sub Period. If you want the same Margin Percentage every week, define the time granularity for Margin Percentage as Period. ## Calculation The aggregation settings define how a KPI is calculated across the product hierarchy and time hierarchy. A few settings that define how a KPI is calculated are: - Merge Rule: Define how KPI values in the P&L page are merged into weekly values. If Custom Periods for Months and Quarters is enabled for the sales organization, then the Merge Rule defines how the KPI values are merged into monthly or quarterly values. - Time Rule Aggregation: Define how the calculation engine aggregates the weekly data to months. If Custom Periods for Months and Quarters is enabled for the sales organization, then the calculation engine considers only the merge rule. If the Aggregation Time Rule is defined as Formula, then the weekly values are accurately calculated for a month according to the formula defined in the Formula field. Same formula is used to calculate weekly and monthly values. If a KPI is defined to calculate weekly data and the Aggregation Time Rule is set to Aggregate, the weekly values are accurately summed up for the month considering the number of days the month is part of the promotion week. If writeback is enabled, the system stores the summed up values of the months in the Monthly table specified under the Storage Option Settings of the KPI Definition. - Rounding: Define whether a KPI value is rounded to 0 or to a more accurate decimal place. For example. Cost and Revenue can have decimals but volume must always be rounded. Rounding the numbers may cause losing precision, and the sum of the distributed KPI values may not be the correct total value. Therefore, the difference between the total value and the sum of the distributed value is added to one of the KPI values to ensure the correct total value. Here’s an example to explain how rounding works. ![Rounding example](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-ind-consumer_goods_trade_promo-264-0-0-production-enus/169b0c8b-175d-4639-bf96-610b16824687/consumer_goods_trade_promo/images/rounding_example.png) The Planned Total Volume of 1000 is distributed across three BigFootBar products. The Planned Total Volume for the individual products is 333 when rounding is enabled. But, when you add the Planned Total Volume for all three products, the Total Planned Total Volume amounts to 999 and not 1000. To fix this issue, the Planned Total Volume value for one of the products is updated to 334. ## Storage and Visibility These settings determine whether KPIs are shown on a screen and whether their values are written back to the CG processing services after calculations are done in Salesforce. #### See Also - [Example: Calculating KPIs of Subperiod Time Granularity](https://help.salesforce.com/s/articleView?id=ind.tpm_concept_enabling_kpis_at_subperiod_level_to_calculate_values_with_parameter_kpis_at_period_level.htm&release=264.0.0&type=5 "This example shows how a calculated or editable calculated KPI of time granularity subperiod is calculated when KPIs with time granularity period are included in the KPI formula.")