COBK
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. Clean-Core.io's curated mapping points to I_CostCenterActualData; that is our mapping, not SAP's. It 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
Released S/4HANA Clean Core successor for COBK.
Repository state: notToBeReleased
Source: Clean-Core.io curated (field-level), compiled for 2024.FPS02, reviewed 2026-10-12; not SAP's Cloudification Repository
See how your code uses COBK
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 Controlling
Application component: CO-OM-2CL
All Controlling objects →