CL_HTTP_CLIENT
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
Not to be released
SAP will not release it for ABAP Cloud. There is no level A use of this object.
objectReleaseInfo
Classic view
Classic API
SAP classifies it as an API that classic ABAP may use — level B on its own.
objectClassifications_SAP
The two files disagree here, and the release state decides. Level B means “acceptable where no level A path exists”. SAP names a successor for this object, so a level A path does exist and B would be the wrong answer — which is why the level is D and not B. The full rule, and the objects it applies to.
CL_HTTP_CLIENT 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 CL_HTTP_CLIENT
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-ICF
All Basis Components objects →