BAPIRETURN
Two questions, two answers. The level D above answers the clean core target question — what this object is worth in an ABAP Cloud target. Whether classic ABAP may still call it is a separate property, and it is the right-hand column.
ABAP Cloud view
Deprecated
Still listed, but SAP has marked it for removal. Anything built on it has a shelf life.
objectReleaseInfo
Classic view
Not listed
The classification file does not mention it, so it says nothing either way.
objectClassifications_SAP
Deprecated, with no successor named — check this one. SAP marks this object for removal but names no replacement. That is a check to run against the current release notes, not a finished verdict — the level reads the missing successor in the strictest way it can.
BAPIRETURN has no released API successor in the SAP Cloudification Repository.
No released successor is named in SAP's data for this object. Custom code using it cannot simply be re-pointed — assess alternatives for your target release: a released API, the standard, or retiring the code. This is an honest limitation, not an omission.
See how your code uses BAPIRETURN
This is the object-level answer. To see, per object, whether your actual ABAP can move to the successor or needs an architect — with evidence — run a free ABAP static code analysis.
Analyze free at clean-core.ioRelated
More from SAP Basis Components
Application component: BC-MID-API
All Basis Components objects →