Understanding How KPI Values are Calculated When Border Correction is Enabled

Available in: Lightning Experience Available in: Enterprise and Unlimited Editions where Consumer Goods Cloud is enabled

Here’s how a share is calculated.

• If a value belongs completely in the Read time frame, the entire value is considered.
• If a value belongs to a time frame that is partially outside the Read time frame, the system calculates the share by considering the customer category profile or weekday share profile with an equal split fallback.
• Only the share for the first and last week of the time scope of the Read KPI is calculated. For all other weeks, the KPI calculation process remains the same.

For multilevel promotion planning, when promotion border correction is enabled and the KPI values of the parent promotion are read from the promotion measure tables, the time scope of the child promotion is aligned with the parent promotion. For example, if the parent promotion reads values with a tactic shipment time scope, the child promotion must also writeback KPI values for the tactic shipment time scope.

Account KPIs are always calculated for a requested time range. To calculate accurate account-level KPIs, the system aggregates the promotion-level KPIs of all promotions that are within the scope of the account plan. Promotional KPI values are stored as week or month values. Here’s how the promotional KPI values are aggregated.

• If a week or month is completely within the requested time range, the promotional KPI values can be aggregated up to 100% of the account plan.
• Weeks or months that are completely outside the requested time range aren’t considered.
• A promotional KPI value is valid only for a part of the period if the promotion doesn’t start or end at the beginning or end of a period.
• If the promotion period lies completely within the requested time frame, the promotional KPI values are considered as 100%, even if the weekday share of the complete promotion time frame = 0.

If you use the flexible writeback structure, activate the Calculation Border Correction feature using Update Activation for the sales org.

Consider these scenarios as shown in the figure.

• Promotion 1—Week or month values can be aggregated completely for values that don’t belong to the first or last period of the requested time range.
• Promotion 2—Week or month values can be aggregated completely for values that are bound to the first period of the requested time range and start either later than or on the requested start date.
• Promotion 3—Week or month values can be aggregated for values that are bound to the last period of the requested time range and end earlier than or on the requested end date.
• Promotion 4—Week or month values can’t be aggregated without further processing for values that are bound to the first period of the requested time range and start earlier than the requested time range. A correction factor must be calculated.
• Promotion 5—Week or month values can’t be aggregated without further processing for values that are bound to the last period of the requested time range and end later than the requested time range. A correction factor must be calculated.

• Examples: Promotion Border Correction
  These examples show how promotion border correction is applied when reading values from the Weekly Promotion Measure Result and Monthly Promotion Measure Result tables. The system reads values from the Promotion Measure Result JSON table if a flexible writeback structure is used. The writeback structure stores weekly, monthly, and custom values for each product ID in JSON tables based on account plan, promotion, or tactic. To use the writeback structure, you must activate promotion border correction.