BAPI_ROOT_CAUSE_IMPORT
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 listed
The release file does not mention it, so it says nothing either way.
objectReleaseInfo
Classic view
noAPI
SAP classifies it as not intended for customer use.
objectClassifications_SAP
BAPI_ROOT_CAUSE_IMPORT has no released API successor in the SAP Cloudification Repository.
SAP classifies this object as noAPI — not intended for customer use — and names no replacement. Custom code calling 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 BAPI_ROOT_CAUSE_IMPORT
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
Application component
Application component: EHS-SUS-IM