PackagePackagetypeA library you install and call yourself.See every one →What this type is →by SAPby SAPoriginPublished by SAP itself. A visible facet, never an input to a reading — a dormant official plugin reads exactly like a dormant independent one.See every one →

com.sap.cds:cds-feature-change-tracking

Records who changed which annotated field on a CDS entity and when, as a queryable change log for CAP Java, covering every modifying CQN statement but not native SQL or JDBC.

Adds change tracking to a CAP Java service, part of the cds-services-bom release line. It tracks the changes of all modifying operations executed via CQN statements, whether triggered by a protocol adapter or by custom code, and stores each addition, modification or deletion in a flat sap.changelog.Changes entity. Changes made through native SQL, JDBC or anything else that bypasses the CAP Java runtime, or that is forwarded to a remote service, are not tracked. An entity opts in by being extended with the changelog.changeTracked aspect and marking the elements to log with @changelog; the Node.js counterpart, @cap-js/change-tracking, is documented for the same plugin under its own runtime. The dependency is added to srv/pom.xml with runtime scope, or compile scope when a handler needs to read the change log entries itself.

Facts

LicenceSAP DEVELOPER LICENSE AGREEMENT for CAP

Where it sits

Lives in
Provides
Change trackingCAPChange trackingcapabilityKeeping a readable history of what changed on a record, who changed it and when — as business history rather than database journalling.
Flavors

What it declares

Every artifact

Type
Package
Origin
By SAP
Runtime
Java

As a package

Where it runs
does not say
Distributed through
does not say

Connections1

Change tracking
  1. @cap-js/change-trackingChange history for annotated CAP entitiesfrom CAP
  2. cdsmbt01CDS plugin for OData change tracking in CAP applicationsfrom CAP

Details

Sources1
Added by handdiscovered herechecked

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
runtimesjava
discovered viaAdded by hand
first seen in the atlas
ecosystem and domaincap, security-and-compliance
Flavors1
Java
“Changes made through the native SQL, JDBC, or other means that bypass the CAP Java runtime or that are forwarded to the remote services aren't tracked.” — Change Trackingchecked
History in the atlas2
  1. Tracks the changes of all modifying operations executed via CQN statements and stores each addition, modification or deletion in a flat change log entity that a projection can expose on an object page.
  2. First seen.
For your agent
Ref
artifact:cap-java-cds-feature-change-tracking
JSON
/artifacts/cap-java-cds-feature-change-tracking.json
MCP
Connecting an agent