Skip to content
ERP Preflight

FUNCfunction module· BC-SRV-BAL

BAL_LOG_EXCEPTION_ADD in SAP Cloud ERP: what replaces it?

Custom code that reads or writes BAL_LOG_EXCEPTION_ADD (FUNC) has to move to a released successor before it runs on SAP Cloud ERP or in ABAP Cloud. SAP names 2 successors: CL_BALI_EXCEPTION_SETTER, CL_BALI_LOG.

Last verified:
Data source
Knowledge snapshot #3 · 33e0865dc811
Analyse your code for freeLook up another object
Cite:r/SAPINXHN

Use instead of BAL_LOG_EXCEPTION_ADD

SAP successor classification: multipleObjects

Migration steps

  1. List every place your custom code reads or writes BAL_LOG_EXCEPTION_ADD; the ABAP Test Cockpit cloud-readiness checks report these usages.
  2. Replace each access with one of CL_BALI_EXCEPTION_SETTER, CL_BALI_LOG; pick the successor whose fields match the usage.
  3. All 2 successors are marked “Released” in the official release data, so the new code can use them in ABAP Cloud.
  4. Re-run the cloud-readiness check on the changed code against your target release.

Release state of BAL_LOG_EXCEPTION_ADD per edition

  • SAP BTP ABAP environment:Not releasedas of SAP BTP ABAP environment — current release
  • SAP Cloud ERP Private:Not releasedas of SAP Cloud ERP Private — latest release
  • SAP Cloud ERP:Not releasedas of SAP Cloud ERP — current release

Objects with the same successor

These objects have the same official successor, so their usages can be migrated in the same change.

Release history and evidence

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

Full release history and evidence

Terms used on this page

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