BADI_DEFbadi· FI-LOC-SRF-RUN

SRF_RPG_ACT_ON_RETRIEVE in SAP Cloud ERP: what replaces it?

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

Last verified:: October 12, 2026
Data source: Knowledge snapshot #3 · 33e0865dc811

Analyse your code for free Look up another object

Cite:r/SAP IN X HN

Use instead of SRF_RPG_ACT_ON_RETRIEVE

SRF_RPG_ACT_ON_RETRIEVE_V2BADI_DEFReleased

SAP successor classification: oneObject

Migration steps

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

Release state of SRF_RPG_ACT_ON_RETRIEVE per edition

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