What to check

When an expected value disappears after activation, start with a known business key and the exact requests affecting it. Comparing only the newest inbound row with an aggregated active result can hide overwrite rules or later records. The referenced SAP preview describes older BW/4HANA releases; check applicability before treating it as the same defect.

Troubleshooting steps

  • Record the affected key figure, complete semantic key, relevant requests, and a small example of the expected result.
  • Inspect transformation output, record sequence, update semantics, and subsequent loads through supported data previews and request administration.
  • Reproduce the sequence in a test system and correct the proven mapping or model issue, or obtain the release-specific SAP correction if required.

Confirm the result

Reconcile the value at the same grain in the active data and query result. Avoid manual table updates: they can bypass the loading history needed to explain and recover the discrepancy.

References

The SAP KBA link provides a public symptom preview; its full resolution requires SAP Support access. These diagnostic steps are independent guidance. Check the installed release before applying a correction.

SAP KBA preview 2996527 (English)

SAP documentation (English)