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 RepositoryCloudification RepositorySAP's list of released APIs for SAP Cloud ERP, with the successors of the objects that are not released — the content the ABAP test cockpit's cloud readiness and clean core checks are pointed at.sap official, abap 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
Where it sits
Who is behind it
In the atlas: maintains 7, contributes to 8@Xexermaintainer
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
Connections
Defining entities, their relations and the views services consume
Download
README
quoted from Xexer/abap-cds-field-mapping, readCDS Field Mapping
Searching for a mapping ...
Others providing
Compare all 9 on the Data modelling page →- ABAP CDSABAP CDSThe modelling layer of ABAP Cloud — view entities, projections and annotations defined above database tables, delivered with the platform rather than installed.sap official, abapModelling layer of ABAP Cloud above database tablesfrom ABAP
- cds-numberrange-plugincds-numberrange-pluginA CAP plugin that fills an annotated CDS element with the next number from a named range, optionally with prefix, suffix and padding, keeping the counter in a database entity it adds to the model.independent, capFills a CDS element from a database-backed number rangefrom CAP
- cdsanalysercdsanalyserA 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.independent, abapMaps database tables and fields to the CDS views exposing themfrom ABAP
- com.sap.cds:cds-services-bomcom.sap.cds:cds-services-bomThe Maven bill of materials for CAP Java, pinning every com.sap.cds module in a release, from the API and core runtime to the Spring Boot starters and the CQN engine, to the same version.sap official, capMaven bill of materials pinning CAP Java module versionsfrom CAP
- @sap/cds-common-content@sap/cds-common-contentISO-standard content for CAP's common definitions — countries, languages, currencies and timezones — so a project does not seed those tables itself.sap official, capISO content for CAP's countries, languages, currencies and timezonesfrom CAP
- @sap/cds-compiler@sap/cds-compilerCompiles CDS models to CSN, EDMX and database schemas.sap official, capCompiler from CDS models to CSN, EDMX and database schemasfrom CAP
- @sap/cds@sap/cdsThe CAP Node.js runtime, which compiles the CDS model, serves the services declared in it, answers generic requests before any handler runs, and loads every cds-plugin.sap official, capCAP Node.js runtimefrom CAP
- cap-user-infocap-user-infoResolves the createdBy and modifiedBy of a managed entity to a stored user record of email, given name and family name, and renders the two fields as links with a quickview.independent, capUser details and quickview links for createdBy and modifiedByfrom CAP
Details
Sources
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
History in the atlas
- 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.
- 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.
- First seen.
For your agent
- Ref
artifact:xexer-cds-field-mapping- JSON
- /artifacts/xexer-cds-field-mapping.json
- MCP
- Connecting an agent