BAPI_QNOTIFICAT_CREATE in SAP Cloud ERP: what replaces it?

Use instead of BAPI_QNOTIFICAT_CREATE

• I_QLTYNOTIFICATIONTPBDEFReleased

SAP successor classification: oneObject

Migration steps

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

Objects with the same successor

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

• BAPI_QUALNOT_ADD_DATAFUNC
• BAPI_QUALNOT_CREATEFUNC
• BAPI_QUALNOT_DEL_DATAFUNC
• BAPI_QUALNOT_MODIFY_DATAFUNC
• BAPI_QUALNOT_SAVEFUNC
• QM05_CREATE_NOTIFICATIONFUNC

Terms used on this page

• Released API
• Successor
• ABAP Cloud
• Cloudification Repository