SAP S/4HANA · Released CDS view
I_OperationalAcctgDocItem
Released · C1Over ACDOCAFinancial Accounting (FI)
The operational accounting document line item — the G/L, vendor, and customer line over ACDOCA, with clearing data. This is the released view to read when you need open vs cleared status alongside the posting: it carries the clearing document and date that drive AP and AR aging.
Released status: C1 — stable, upgrade-safe. Underlying storage: ACDOCA. Consume it as a reporting basis or extract it — never via ODP-RFC.
◆What it exposes
Semantic field names — readable, stable, and the same across every released view.
| Field | Meaning |
|---|---|
| CompanyCode | The company code (RBUKRS). |
| FiscalYear | Fiscal year (GJAHR). |
| AccountingDocument | Document number (BELNR). |
| GLAccount | The account the line posts to (RACCT). |
| AmountInCompanyCodeCurrency | Local-currency amount (HSL). |
| DebitCreditCode | Debit / credit indicator. |
| ClearingAccountingDocument | The clearing document — populated once the item is cleared. |
| ClearingDate | When the item was cleared; blank while open. |
| Supplier | Supplier, for payables lines. |
| Customer | Customer, for receivables lines. |
◆How it relates to the model
| Object | Holds | Joined / related on |
|---|---|---|
| ACDOCA | The Universal Journal — the table this view reads | company code · document · line |
| I_JournalEntryItem | The basic journal-item view it is related to | same line |
| I_GLAccountLineItem | The G/L-focused sibling view | G/L account |
Read this view, not the raw table: ACDOCA is the storage, but the released view is the stable contract — the field names will not shift under you on an upgrade.
◆Released & upgrade-safe
SAP publishes CDS views under a release contract. C1 means I_OperationalAcctgDocItem is a stable, documented API you can build a model on — SAP will not break its structure across upgrades. That is the difference between depending on a released view and depending on a raw table or an unreleased one.
Confirm the current contract on the API State tab in the system or on the SAP Business Accelerator Hub. Released views are the only safe foundation for an owned model.
◆How to consume & extract
- As a reporting basis — build your own query views on it (Analysis for Office, SAP Analytics Cloud).
- As an extract — replicate it to your warehouse via ODP-OData, SLT, or Table / Table-CDC.
- Never via ODP-RFC — SAP Note 3255746 prohibits it, and a June 2026 patch blocks it.
This is the compliant, owned-layer path: extract the released view, build the model on your cloud, reconcile to the source. See the extraction pattern →
◆Reports that use it
Building on I_OperationalAcctgDocItem?
We build AP and AR open-item and aging reporting on this released view — clearing status reconciled to your sub-ledgers — on your cloud, and you own the code.
Terms on this page
- Clearing document
- The document that settled an open item; if set, the item is cleared.
- Open item
- An unpaid line — no clearing document yet.
- Released CDS view
- A SAP-published view you can build on; its structure is a stable API.
- C1 contract
- The release level that makes a view stable and upgrade-safe to depend on.
- ACDOCA
- The Universal Journal — the table most finance views read.
- ODP-OData
- A SAP-sanctioned way to extract a released view; ODP-RFC is not allowed.