Web toolWeb tooltypeA hosted utility you use at a URL, rather than run or install. May be free or paid; source_available says whether anything behind it is inspectable.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 →

CDS Field Mapping

Looks up which Core Data Services entity and field a classic dictionary table and field map to, filterable by whether the target CDS view is released.

A prototype mapping list: give it a table and a field and it returns the new field name, or go the other way from the Core Data Services name back to the table. Its README names the Cloudification Repository as the source the mapping is to come from. The repository behind the page carries the extractor class, which you copy and run in your own system, and the finished mapping file beside an unofficial one for Core Data Services that are not released; the page itself filters by release state, as All, Not released or Released.

Facts

Last push

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

XexerXexerPersonMaintains this
In the atlas: maintains 7, contributes to 8
@Xexer
maintainer

Before choosing this

Signals

LicenceNo licenseNeither the package manifest nor the repository tree declares a licence

Without a licence the default is all rights reserved. Ask the maintainer, or check for terms stated elsewhere, before depending on it.

Conditions

PracticalFunctional boundary

Marked BETA and called a first prototype on its own page, which names where it is wrong: when fields are mapped with CAST, CASE, ABS and other CDS functions there may still be errors in the fields, so a mapping that goes through one of those needs checking against the view it came from.

What it declares

Every artifact

Type
Web tool
Origin
Independently maintained

As a web tool

Access
does not say
What it sends to its vendor
does not say

Connections1

README

quoted from Xexer/abap-cds-field-mapping, read
Xexer/abap-cds-field-mapping/README.mdOn GitHub

CDS Field Mapping

Searching for a mapping ...

excerpt, no licence read, read the rest, on GitHub
Data modelling
  1. ABAP CDSModelling layer of ABAP Cloud above database tables
  2. cdsanalyserMaps database tables and fields to the CDS views exposing them

Details

Sources3
Software-Heroesdiscovered herechecked
github.com/Xexer/abap-cds-field-mappingtree, 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 viaSoftware-Heroes
first seen in the atlas
ecosystem and domainabap, data-and-persistence
History in the atlas3
  1. SAP's Cloudification Repository is in the graph, so the README's source is named by its entry rather than by a URL none of this entry's sources gave. The README's sentence is "Source will be the Cloudification Repository, where the mapping old table to new Core Data Services is listed.", so the prose reports it as what the README names and not as how the mapping file is produced today: the file in the repository comes from an extractor class you copy and run in your own system. The CAST, CASE and ABS gap is attributed to the tool's page, which is where that sentence stands, rather than to the README.
  2. Entered from software-heroes.com's tools page; its data lives in a public GitHub repository the page links as 'Extract and further information', unlike its sibling tools here which are hosted only.
  3. First seen.
For your agent
Ref
artifact:xexer-cds-field-mapping
JSON
/artifacts/xexer-cds-field-mapping.json
MCP
Connecting an agent