Successor
Successor object
The released SAP object that replaces a deprecated or not released one — for example a released CDS view that replaces reads of a classic table.
When SAP does not release an object for cloud development, it often names what to use instead: one successor, several successors, or a successor concept described in words.
A successor can differ by edition and release, and it can itself be deprecated later. Where several successors are listed, pick the one whose fields match your usage and check that it is released in your target release.
Where SAP names no successor, the options are to encapsulate the access in a wrapper you own or to request a released API from SAP.
In ERP Preflight
The free legacy object → cloud successor tool and the SAP object pages show successors per release exactly as SAP publishes them. The knowledge graph also links objects that share a successor.
Problems that involve Successor
- CriticalDirect read of an SAP standard table
- CriticalCall to a function module not released for cloud development
- CriticalUse of a class not released for cloud development
- MajorUse of a deprecated SAP object
- MajorReference to an object not in the released-object snapshot
- MajorType reference to a DDIC object not released for cloud development
- MajorLegacy object requires process redesign
- MajorTransaction requires process redesign or is not in the cloud catalog
Related terms
Free tools
- Legacy object → cloud successor
Which released object replaces a classic table, BAPI or function module, per release?
- Clean Core Object Lookup
Is a table, CDS view, class or function module released for ABAP Cloud?
Written for ERP Preflight · reviewed September 27, 2026
All glossary termsERP Preflight is independent and not affiliated with SAP SE. SAP, ABAP, Fiori and S/4HANA are trademarks of SAP SE.