3731236 - inverse formulas not input-enabled for calculated kpis in specific planning scenarios

• In planning, inverse formulas on calculated KPIs do not behave as expected and the cells remain non-editable in specific input scenarios.
• The behavior affects several calculated KPIs, while a comparable KPI with a similar setup may work as expected.
• In some contexts, the table shows the message “Inverse formula is missing”.
• In some periods, the table shows the message “Exception aggregation on a formula member”.
• The issue is observed when attempting direct input on a story table.

SAP Analytics Cloud

1. Open a planning story that contains calculated KPIs with inverse formulas.
2. Navigate to the planning table where the KPIs are displayed
3. Attempt to input a value directly into a calculated KPI that has an inverse formula defined.
4. Observe that the input is disabled and/or messages such as “Inverse formula is missing” or “Exception aggregation on a formula member” appear.

• The inverse formula chain is incomplete: one or more nested dependent calculations referenced by the target formula do not have their own inverse formulas, which prevents input enablement.
• In some periods, the member is unplannable due to “Exception aggregation on a formula member”.
• Story-level calculated measures and accounts are not subject to model data locking, so editability in-table may not reflect lock status; locks are enforced at publish time.

1. Verify all nested dependencies of the calculated KPI and ensure every referenced calculated measure/account has its own inverse formula, even if it isn’t the direct target of the outer formula.
2. Add the missing inverse formulas to each dependent calculation in the chain so the inverse path is complete from the edited KPI down to plannable base data.
3. Review any members using exception aggregation on a formula member. If present, redesign to avoid applying exception aggregation on formula members for periods where input is required, or enter data at the appropriate base level.
4. Re-check input enablement in the story table after completing the inverse chain and adjusting exception aggregation as needed.
5. Consider data locking behavior: model-level data locks do not directly restrict story calculations; locks are validated at publish time. Test by publishing changes and align design accordingly.

• Refer to: Inverse Formulas | Help Portal
• Refer to: Disaggregation of Values During Data Entry (AVERAGE variants)
• Refer to: Configuring Data Locking (exceptions and restrictions)

inverse formula missing, input disabled, calculated kpi, calculated measure, nested formulas, inverse chain, planning input, exception aggregation, average aggregation, unplannable cell, story calculation, data locking, publish validation, sac planning, input-enabled , KBA , LOD-ANA-PL-DE , Data Entry and Mass Data Entry , Problem