BADI_DEFbadi· MM-PUR-2CL
MEOUT_BAPI_CUST in SAP Cloud ERP: what replaces it?
Custom code that reads or writes MEOUT_BAPI_CUST (BADI_DEF) has to move to a released successor before it runs on SAP Cloud ERP or in ABAP Cloud. SAP names 7 successors: MEOUT_BAPI_CUST_MAP2E_DATA, MEOUT_BAPI_CUST_MAP2I_DATA, MEOUT_BAPI_CUST_OUTBOUND, MEOUT_BAPI_DETERMINE_GROS_COUT, MEOUT_BAPI_HANDLE_EXT_REF +2.
- Last verified:
- Data source
- Knowledge snapshot #3 · 33e0865dc811
Use instead of MEOUT_BAPI_CUST
- MEOUT_BAPI_CUST_MAP2E_DATABADI_DEFReleased
- MEOUT_BAPI_CUST_MAP2I_DATABADI_DEFReleased
- MEOUT_BAPI_CUST_OUTBOUNDBADI_DEFReleased
- MEOUT_BAPI_DETERMINE_GROS_COUTBADI_DEFReleased
- MEOUT_BAPI_HANDLE_EXT_REFBADI_DEFReleased
- MEOUT_BAPI_MAP2E_EXTENSIONOUTBADI_DEFReleased
- MEOUT_BAPI_MAP2I_EXTENSIONINBADI_DEFReleased
SAP successor classification: multipleObjects
Migration steps
- List every place your custom code reads or writes MEOUT_BAPI_CUST; the ABAP Test Cockpit cloud-readiness checks report these usages.
- Replace each access with one of MEOUT_BAPI_CUST_MAP2E_DATA, MEOUT_BAPI_CUST_MAP2I_DATA, MEOUT_BAPI_CUST_OUTBOUND, MEOUT_BAPI_DETERMINE_GROS_COUT, MEOUT_BAPI_HANDLE_EXT_REF +2; pick the successor whose fields match the usage.
- All 7 successors are marked “Released” in the official release data, so the new code can use them in ABAP Cloud.
- Re-run the cloud-readiness check on the changed code against your target release.
Release state of MEOUT_BAPI_CUST 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 evidenceTerms 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.