Skip to content
ERP Preflight

CHKVatc check· BC-DWB-CEX-CCM

ABAP_CLOUD_DEVELOPMENT_3TIER in SAP Cloud ERP: what replaces it?

Custom code that reads or writes ABAP_CLOUD_DEVELOPMENT_3TIER (CHKV) has to move to a released successor before it runs on SAP Cloud ERP or in ABAP Cloud. SAP names one successor: ABAP_CLEAN_CORE_DEVELOPMENT.

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

Use instead of ABAP_CLOUD_DEVELOPMENT_3TIER

SAP successor classification: oneObject

Migration steps

  1. List every place your custom code reads or writes ABAP_CLOUD_DEVELOPMENT_3TIER; the ABAP Test Cockpit cloud-readiness checks report these usages.
  2. Replace each access with ABAP_CLEAN_CORE_DEVELOPMENT (CHKV).
  3. The successor is marked “Released” in the official release data, so the new code can use it in ABAP Cloud.
  4. Re-run the cloud-readiness check on the changed code against your target release.

Release state of ABAP_CLOUD_DEVELOPMENT_3TIER 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 · released since SAP S/4HANA 2023 FPS02 · 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

7 release states from 7 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.

ABAP_CLOUD_DEVELOPMENT_3TIER successor for SAP Cloud ERP migration: ABAP_CLEAN_CORE_DEVELOPMENT