SUSOauthorization object· PM-2CL
I_EAM_OM in SAP Cloud ERP: what replaces it?
Custom code that reads or writes I_EAM_OM (SUSO) has to move to a released successor before it runs on SAP Cloud ERP or in ABAP Cloud. SAP names 3 successors: I_EAM_MJPB, I_VORG_MEL, I_VORG_ORD.
- Last verified:
- Data source
- Knowledge snapshot #3 · 33e0865dc811
Use instead of I_EAM_OM
- I_EAM_MJPBSUSO
- I_VORG_MELSUSOReleased
- I_VORG_ORDSUSOReleased
Migration steps
- List every place your custom code reads or writes I_EAM_OM; the ABAP Test Cockpit cloud-readiness checks report these usages.
- Replace each access with one of I_EAM_MJPB, I_VORG_MEL, I_VORG_ORD; pick the successor whose fields match the usage.
- Not marked “Released” in the official release data: I_EAM_MJPB. Check the release state of this successor for your target release before you migrate.
- Re-run the cloud-readiness check on the changed code against your target release.
Release state of I_EAM_OM per edition
- SAP Cloud ERP Private:Releasedas of SAP Cloud ERP Private — latest release · released since SAP S/4HANA 2022
- 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 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.