Skip to content
ERP Preflight

BADI_DEFbadi· FI-LOC-FI-AR-WHT

FIWTAR_BASE_AMOUNT_CHANGE in SAP Cloud ERP: what replaces it?

Custom code that reads or writes FIWTAR_BASE_AMOUNT_CHANGE (BADI_DEF) has to move to a released successor before it runs on SAP Cloud ERP or in ABAP Cloud. SAP names a successor concept: Document and Reporting Compliance Framework”..

Last verified:
Data source
Knowledge snapshot #3 · 33e0865dc811
Cite:r/SAPINXHN

Use instead of FIWTAR_BASE_AMOUNT_CHANGE

Successor concept named by SAP: Document and Reporting Compliance Framework”.

SAP successor classification: concept

Migration steps

  1. List every place your custom code reads or writes FIWTAR_BASE_AMOUNT_CHANGE; the ABAP Test Cockpit cloud-readiness checks report these usages.
  2. Redesign the access along the successor concept named by SAP: Document and Reporting Compliance Framework”..
  3. Re-run the cloud-readiness check on the changed code against your target release.

Release state of FIWTAR_BASE_AMOUNT_CHANGE per edition

  • SAP Cloud ERP Private:Deprecatedas of SAP Cloud ERP Private — latest release · released since SAP S/4HANA 2023 FPS00 · deprecated since SAP S/4HANA 2025 FPS00
  • SAP Cloud ERP:Deprecatedas of SAP Cloud ERP — current release · deprecated since SAP Cloud ERP — current release

Release history and evidence

8 release states from 8 official sources, last verified October 12, 2026.

Full release history and evidence

ERP Preflight is independent and not affiliated with SAP SE. SAP, ABAP, Fiori and S/4HANA are trademarks of SAP SE.

FIWTAR_BASE_AMOUNT_CHANGE in SAP Cloud ERP migration: successor concept