AppApptypeAn application you deploy and use, installed into a system or loaded into an application as a component, rather than a library whose functions you call.See every one →What this type is →independently maintainedindependently maintainedoriginPublished by one person or a small company outside SAP. Says nothing about quality; the readings say that.See every one →

cdsanalyser

A search tool that maps SAP database tables and fields to the CDS view entities that expose them, and back, from an index a background job builds, for SAP S/4HANA on-premise or private cloud.

Finding the right CDS view for a known database table is the gap this closes: an application job, run from the template ZCDSSEARCH_BUILD_INDEX_TEMPL, analyses the CDS views in the system and stores the mapping in a dedicated database table so a later search hits an index rather than the metadata. Two ABAP packages carry it, one for the indexing core and the OData V4 service and one for the deployed Fiori BSP application, and the report ZGET_CDS_FOR_DB_FIELD gives the same lookup in SAP GUI. The index has to be built before the first search; the maintainer frames the whole tool as a Clean Core enabler, moving data access from direct table reads to CDS views.

Facts

Last pushLicenceGPL-3.0

Where it sits

Lives in
Provides
Data modellingABAPData modellingcapabilityDefining the shape of data before anything serves it: entities and their types, how they relate, and the projections and views that services and applications consume.

Who is behind it

agraeberagraeberPersonMaintains this
In the atlas: maintains 1, contributes to 1
@agraeber
maintainer

Before choosing this

Conditions

PracticalFunctional boundary

Not on the SAP BTP ABAP environment or another cloud ABAP system: the maintainer states the tool is not cloud ready, because the data sources and system tables it reads CDS metadata from are not released for cloud development. It is designed for SAP S/4HANA on-premise or private cloud, and the shipped Fiori application is configured for A4H and developer systems.

What it declares

Every artifact

Type
App
Origin
Independently maintained

As an app

Where it runs
Inside the system it serves
Distributed through
does not say

Connections1

README

quoted from agraeber/cdsanalyser under GPL-3.0, read
agraeber/cdsanalyser/README.mdOn GitHub

CDS & Table Field Search Tool (Clean Core Enabler)

This tool bridges the gap between traditional SAP database table knowledge and the modern Clean Core approach. It allows developers and consultants to find corresponding CDS View entities and fields based on familiar database tables and fields in seconds.

Caution

Cloud Readiness & Compatibility > This tool is unfortunatley NOT Cloud Ready (not for SAP BTP ABAP Environment / Steampunk).
Although it uses modern components like Application Jobs and OData V4, the underlying data sources and system tables for CDS metadata are NOT released for cloud development. It is designed for use on SAP S/4HANA On-Premise or Private Cloud environments.

Overview

As we move toward Clean Core, accessing data via CDS views instead of direct table access is essential. However, finding the right CDS view for a known DB table can be challenging. This repository provides a high-performance indexing engine and search UI to solve this.

Project Structure

The solution is organized into the following components:

  • Package ZCDS_SEARCH: Backend core, indexing logic, and OData V4 service.
  • Package ZCDS_SEARCH_BSP: Deployed Fiori BSP Application (ZCDSANALYSE).

🚀 Prerequisites & Setup

To enable the background indexing engine, the following objects are included in the repository:

  1. Application Job Catalog Entry:
    ZCDSSEARCH_BUILD_INDEX (bound to class ZCL_CDSSEARCH_BUILD_INDEX).
  2. Application Job Template:
    ZCDSSEARCH_BUILD_INDEX_TEMPL based on the catalog entry above.

🏗 Start of Analysis (Building the Index)

Before the first search, you must analyze the CDS views in your system to populate the search index.

  1. Execute the Indexer:
    • Standard: Create and execute an Application Job based on Template ZCDSSEARCH_BUILD_INDEX_TEMPL.
    • On-Premise Shortcut: Run Report ZCDSSEARCH_BUILD_INDEX_VIA_JOB to trigger the indexing process via the Application Job.
  2. Result: The tool analyzes the requested CDS views and stores the mapping results in a dedicated database table for instant access.

🔍 How to Use

Modern UI (Fiori / OData)

The primary way to consume the data is via the OData V4 Service: ZUI_CDSFIELDINDEX_V4.

  • Use the Service Preview to build your own dashboard.
  • A pre-deployed Fiori App (ZCDSANALYSE) is included (configured for A4H/Developer systems).
Classic UI (On-Premise Only)

For a quick search within the SAP GUI, use Report: ZGET_CDS_FOR_DB_FIELD.
This high-speed report allows you to:

  • Find all database fields for any given CDS view field.
  • Find the matching CDS view field for any given database table/field.

📖 Detailed Documentation

For a full technical deep dive and the story behind this tool, please refer to the SAP Community blog post:
🔗 How to find CDS views for DB table fields

GPL-3.0, read
Data modelling
  1. ABAP CDSModelling layer of ABAP Cloud above database tables
  2. CDS Field MappingMaps classic dictionary tables and fields to CDS entities and fields

Details

Sources3
Added by handdiscovered herechecked
github.com/agraeber/cdsanalysertree, pushes, contributors, CIchecked
README.mdquoted, and what the entry declareschecked

Sources are graph entities: the same page may back several entries, and an unreachable source flags every row that rests on it.

Compatibility and provenance
discovered viaAdded by hand
first seen in the atlas
ecosystem and domainabap, data-and-persistence
abaplint
issues under its own abaplint configuration35
lines703
statements407
objects39
files13
analysed, main
abaplint version2.120.84
Flavors1
Standard ABAP
“This tool is unfortunatley **NOT Cloud Ready (not for SAP BTP ABAP Environment / Steampunk)**.” — agraeber/cdsanalyser — README, Cloud Readiness & Compatibilitychecked
History in the atlas1
  1. First seen.
For your agent
Ref
artifact:agraeber-cdsanalyser
JSON
/artifacts/agraeber-cdsanalyser.json
MCP
Connecting an agent