CDS_STOBcds view· FI-CA-INV
I_CABILLGDOCINVCGDOC in SAP Cloud ERP: what replaces it?
Custom code that reads or writes I_CABILLGDOCINVCGDOC (CDS_STOB) has to move to a released successor before it runs on SAP Cloud ERP or in ABAP Cloud. SAP names 2 successors: I_CAINVCGDOCHEADER, I_CAINVCGDOCITEM.
- Last verified:
- Data source
- Knowledge snapshot #3 · 33e0865dc811
Use instead of I_CABILLGDOCINVCGDOC
- I_CAINVCGDOCHEADERCDS_STOBReleased
- I_CAINVCGDOCITEMCDS_STOBReleased
SAP successor classification: multipleObjects
Migration steps
- List every place your custom code reads or writes I_CABILLGDOCINVCGDOC; the ABAP Test Cockpit cloud-readiness checks report these usages.
- Replace each access with one of I_CAINVCGDOCHEADER, I_CAINVCGDOCITEM; pick the successor whose fields match the usage.
- All 2 successors are marked “Released” in the official release data, so the new code can use them in ABAP Cloud.
- Re-run the cloud-readiness check on the changed code against your target release.
Release state of I_CABILLGDOCINVCGDOC per edition
- SAP Cloud ERP Private:Not releasedas of SAP Cloud ERP Private — latest release
Objects with the same successor
These objects have the same official successor, so their usages can be migrated in the same change.
Release history and evidence
3 release states from 3 official sources, last verified October 12, 2026.
Full release history and evidenceTerms used on this page
ERP Preflight is independent and not affiliated with SAP SE. SAP, ABAP, Fiori and S/4HANA are trademarks of SAP SE.