Released CDS Views

Released analytical viewsThe compliant sourceUpgrade-safe

CDS views are SAP’s own analytical views over the underlying tables. The ones SAP marks released are the views you build reporting and extraction on — they hide the table complexity and stay stable across upgrades. This is the by-module list of the released views behind this catalog.

✓ Released — build here ✗ Compatibility views (BSIS, FAAV_*) ✗ ODP-RFC

What “released” means: SAP attaches a release contract to each view. C1 = a stable API for use inside the system (reporting, custom views); C2 = released for remote consumption (e.g. exposed as OData). A released view is SAP’s promise it will stay stable across upgrades — which is exactly why you build on it instead of a raw table or a compatibility view.

Tap a row to drill into the released views.

◆ General Ledger— 4 released views over ACDOCA: the journal, the G/L line, the operational item, the FSV tree.

Released view	What it gives you	Contract	Sits over
I_JournalEntry	The journal-entry header — document, type, dates, reference.	Released	BKPF + ACDOCA
I_GLAccountLineItem	Every G/L line — account, amount, currencies, account assignment.	Released	ACDOCA
I_OperationalAcctgDocItem	All line items by type — G/L, vendor (K), customer (D) — the operational grain.	Released	ACDOCA / BSEG
I_FinancialStatementVersionNode	The financial-statement-version hierarchy — the balance-sheet / P&L tree.	Released	FSV config (T011)

◆ Accounts Payable & Receivable— vendor (K) and customer (D) come off one operational line view; master off the Business Partner.

Released view	What it gives you	Contract	Sits over
I_OperationalAcctgDocItem	Vendor (type K) and customer (type D) line items — the open-item grain for aging.	Released	ACDOCA / BSEG
I_BusinessPartner	Supplier & customer master — one partner, surfaced through its roles.	Released	BUT000 + LFA1 / KNA1

In S/4HANA the supplier and the customer are roles on one Business Partner (FLVN / FLCU), CVI-synced to the classic LFA1 / KNA1. Read the partner from I_BusinessPartner and filter the line items by financial-account type — you do not need the old BSIK / BSID compatibility views.

◆ Fixed Assets— 4 released views; asset values read from ACDOCA, so there's no sub-ledger to reconcile.

Released view	What it gives you	Contract	Sits over
I_FixedAsset	Asset master — class, description, capitalization date.	Released	ANLA
I_FixedAssetAssgmt	Time-dependent assignments — cost center, profit center, segment.	Released	ANLZ
I_FixedAssetForLedger	The asset as seen by a specific ledger / accounting principle.	Released	ANLB / ledger
I_AssetValuationForLedger	Asset values per ledger — APC, depreciation, net book value.	Released	ACDOCA

The legacy value tables (ANEP / ANLC) are now FAAV_* compatibility views over ACDOCA — read context only, never the extraction source.

◆ Transaction Tax— the honest exception: no released view replaces BSET; read the transparent table directly.

Tax is the honest exception. There is no released CDS view that replaces BSET as the per-code tax summary — the tax code rides on the line-item views (I_GLAccountLineItem, I_OperationalAcctgDocItem), but the authoritative tax breakdown is still the transparent table BSET.

So for tax you read BSET directly (a live transparent table) and join the released line views for context — and extract it via SLT or Table/Table-CDC, the same compliant routes. Not every object has a released view; saying so is the accurate answer, not a gap.

◆ How to tell a view is released— API State C1/C2, the Business Accelerator Hub, or the ADT repository tree.

API State — in the ABAP Dictionary / ADT, a view's properties show its release contract. C1 (Use System Internally) or C2 (remote) means released.
SAP Business Accelerator Hub (api.sap.com) — browse released CDS views by line of business (Finance, etc.), with documentation per view.
ADT repository tree — released views appear under USE_IN_CLOUD_DEVELOPMENT when you browse by component and API state.

◆ Released vs compatibility views vs ODP-RFC— build on released views; never a compatibility view, never ODP-RFC.

Object	What it is	Use it to extract?
Released CDS view	SAP's stable analytical view — upgrade-safe (C1 / C2).	Yes — via released CDS + ODP-OData, SLT, or Datasphere Replication Flow.
Compatibility view	BSIS / BSID / BSIK / KNC1 / FAAV_* — looks like the old table, is a view over ACDOCA.	No — backward-compatible reads only.
ODP-RFC	The legacy RFC extraction route for third-party tools.	No — prohibited (Note 3255746), blocked June 2026.

Build on the released view or, where there isn't one (tax), the transparent table — extracted the compliant way. See the extraction pattern →

Want a model built on the released views?

We build your reporting layer on released CDS views and transparent tables — upgrade-safe, reconciled to source, extracted the compliant way — and you own the code.

Talk to us

Terms on this page

CDS view: Core Data Services — SAP's semantic layer of analytical views over the tables.
Released: A view SAP marks stable for consumption — it won't break across upgrades.
Release contract: SAP's stability classification: C0, C1, C2, C3.
C1: Released for use inside the system — reporting and custom views.
C2: Released for remote consumption — e.g. exposed as an OData service.
Virtual Data Model: SAP's organized layer of CDS views over the underlying tables.
Compatibility view: A view that mimics an old table (BSIS, FAAV_*) over ACDOCA — read only, not for extraction.
ACDOCA: The Universal Journal — the single line-item table most finance views sit over.
ODP-OData: Operational Data Provisioning over OData — a compliant extraction route.
SLT: SAP Landscape Transformation — SAP's real-time table-copy tool.
ODP-RFC: An older extraction route SAP now bans for non-SAP tools (Note 3255746).