SAP S/4HANA · Released CDS view
I_JournalEntry
Released · C1Over ACDOCA / BKPFGeneral Ledger (FI-GL)
The journal entry header — one row per accounting document. This released view is the semantic equivalent of BKPF: document type, dates, currency, and who posted it. Join it to the item views to put header context on every line.
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). |
| AccountingDocument | Document number (BELNR). |
| FiscalYear | Fiscal year (GJAHR). |
| AccountingDocumentType | Document type (BLART) — what kind of posting. |
| DocumentDate | The document date (BLDAT). |
| PostingDate | The posting date (BUDAT). |
| JournalEntryCreatedByUser | Who created the document. |
| Ledger | The ledger (RLDNR). |
◆How it relates to the model
| Object | Holds | Joined / related on |
|---|---|---|
| BKPF | The header table this view is the semantic equivalent of | document |
| I_GLAccountLineItem | The line-item view it joins to | company code · document |
| ACDOCA | The Universal Journal the lines live in | document |
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_JournalEntry 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_JournalEntry?
We build document-journal and audit reporting on this released header view joined to the lines — on your cloud, and you own the code.
Terms on this page
- Document type (BLART)
- Classifies a posting — vendor invoice, payment, G/L, etc.
- Document header
- One record per document — date, type, currency, status.
- 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.