VBAK
The level depends on what your code does with it. Reading an object SAP will not release uses an internal SAP object: level C, with a check against SAP's changelog before each upgrade. Writing to it directly is level D. SAP names I_SALESDOCUMENT as its successor; that says where to look, not that it is a drop-in replacement.
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
Not listed
The classification file does not mention it, so it says nothing either way.
objectClassifications_SAP
SAP names as successor
I_SALESDOCUMENT
From objectReleaseInfo — SAP names this as the released replacement.
Released S/4HANA Clean Core successor for VBAK.
Repository state: notToBeReleased
Source: SAP official (Cloudification Repository)
See how your code uses VBAK
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 Sales and Distribution
Application component: SD-SLS-2CL
- CL_PRC_RESULT_FACTORY
- CL_SD_DOCFLOW_UTIL
- CL_SD_DOCUMENT_FLOW_RT
- C_BILLGDOCITMPRCGELMNTBSCDEX
- C_BILLINGDOCUMENTITEMBASICDEX
- C_SALESDOCITMPRCGELMNTDEX
- C_SALESDOCUMENTITEMDEX
- C_SALESDOCUMENTSCHEDLINEDEX