Skip to content
ERP Preflight

BADI_DEFbadi· QM-QN-2CL

NOTIF_EVENT_POST in SAP Cloud ERP: what replaces it?

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

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

Use instead of NOTIF_EVENT_POST

SAP successor classification: oneObject

Migration steps

  1. List every place your custom code reads or writes NOTIF_EVENT_POST; the ABAP Test Cockpit cloud-readiness checks report these usages.
  2. Replace each access with BADI_QQM_NOTIF_EVENT_POST_CLD (BADI_DEF).
  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 NOTIF_EVENT_POST per edition

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

Release history and evidence

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