calc/require-updatecalc-off

Severity warning by default. It runs on calc-script bodies (.csc) in Rules only. A Script or a Template is a fragment that Deploy inlines into the Rule that invokes it, so the setting belongs to the Rule as a whole rather than to any one fragment, and this rule never fires on either one.

What it checks

The Rule body must contain SET UPDATECALC OFF; somewhere. Matching is case-insensitive and tolerant of extra whitespace, so set updatecalc off ; counts. Commented-out text does not count: SET UPDATECALC OFF; inside a /* */ block or after // is not a command. SET UPDATECALC ON; does not satisfy the rule either. When the command is missing, the warning is reported once at the top of the file, because there is no offending token to underline.

Why it matters

Intelligent Calculation is on by default in Essbase. With it on, the engine keeps track of which data blocks it believes are already calculated and skips them on the next pass. That is a speed optimization built for a full CALC ALL; against a database nobody touched in between. In real planning work the assumption breaks constantly: users have entered data, an earlier Rule wrote into part of the cube, or your FIX covers a slice the engine already marked as clean. The calculation then finishes quickly and successfully, and some of the numbers are still the old ones. Nothing errors and the Run succeeds, so the results are silently incomplete. Adding SET UPDATECALC OFF; at the top of the Rule makes the engine calculate every block your FIX selects, every time.

Example

This Rule body triggers the warning:

FIX("Budget", "Working", "FY26")
  CALC DIM("Account");
ENDFIX

The message reads:

Add `SET UPDATECALC OFF;`. Intelligent Calculation is ON by default, so Essbase may skip blocks it thinks are already calculated and leave this script's results incomplete.

Put the command in the header and the warning clears:

SET UPDATECALC OFF;

FIX("Budget", "Working", "FY26")
  CALC DIM("Account");
ENDFIX

Adjusting it

Change its severity or turn it off in the Validation Rules panel, or exempt one artifact with an Exception.