CL_BAL_LOGGING in SAP Cloud ERP: what replaces it?

Use instead of CL_BAL_LOGGING

• CL_BALI_LOGCLASReleased
• CL_BALI_LOG_DBCLASReleased

SAP successor classification: multipleObjects

Migration steps

1. List every place your custom code reads or writes CL_BAL_LOGGING; the ABAP Test Cockpit cloud-readiness checks report these usages.
2. Replace each access with one of CL_BALI_LOG, CL_BALI_LOG_DB; 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 CL_BAL_LOGGING per edition

• SAP BTP ABAP environment:Deprecatedas of SAP BTP ABAP environment — current release · deprecated since SAP BTP ABAP environment — current release
• SAP Cloud ERP Private:Deprecatedas of SAP Cloud ERP Private — latest release · deprecated since SAP S/4HANA 2022
• SAP Cloud ERP:Deprecatedas of SAP Cloud ERP — current release · deprecated since 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.

• BAL_DB_COMMIT_2ND_CONNECTIONFUNC
• BAL_DB_DELETEFUNC
• BAL_DB_DEQUEUEFUNC
• BAL_DB_ENQUEUEFUNC
• BAL_DB_LOADFUNC
• BAL_DB_SAVEFUNC
• BAL_DB_SEARCHFUNC
• BAL_LOG_CREATEFUNC
• BAL_LOG_EXCEPTION_ADDFUNC
• BAL_LOG_EXCEPTION_READFUNC
• BAL_LOG_HDR_CHANGEFUNC
• BAL_LOG_HDR_READFUNC

Terms used on this page

• Released API
• Successor
• Deprecated object
• ABAP Cloud
• Cloudification Repository