BVOR
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.
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
BVOR 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 BVOR
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 Financial Accounting
Application component: FI-GL-2CL
All Financial Accounting objects →