Change tracking
Keeping a readable history of what changed on a record, who changed it and when — as business history rather than database journalling.
Overview
@cap-js/change-tracking Out-of-the-box change history for annotated entities.
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.
Not covered: It stops at personal data: both packages skip elements annotated with @PersonalData, which are subject to audit loggingAudit loggingRecording who touched personal or sensitive data, in a form an auditor accepts, without hand-writing it in every handler. It is often confused with application logging, which records what the code did rather than who accessed what.SAP only, and the Node.js README gives the reason, that a readable log would let users get around the audit log. On Java, changes made through native SQL, JDBC or a remote service are not tracked, and the retention of the log and the access rules on it are the application's to settle.
On ABAP a record's business history is the change document, recorded through a change document object; abap-platform-reuse-services logs the total amount and overall status of a sales order on a RAP business object and shows the changes in a Fiori elements app.
Change documents: a change document object covers the tables of a business object, fields are logged where their data element has change document logging switched on, and function modules such as CHANGEDOCUMENT_READ_HEADERS and CHANGEDOCUMENT_READ_POSITIONS read the history back with old and new values.
Not covered: At changes: in the sample checked only changes are recorded and not initial values, so a record's history starts at its first edit. An OData V4 Fiori elements app does not use the reuse display library, and the sample reads the change documents through a custom entity instead.
abap-platform-reuse-servicesabap-platform-reuse-servicesA sample sales-order RAP business object that draws its key from a number range, records field changes in a change document, and fills a PDF through SAP Forms Service by Adobe.sap official, abap is an SAP-samples repository that demonstrates change documents on a RAP business object; a sample is no presence, and core-only rests on SAP's documentation.
No community artifact is documented here.
Artifacts
Content
Show 2 more
Seen working
Details
Coverage
For your agent
- Ref
capability:change-tracking- JSON
- /capabilities/change-tracking.json
- MCP
- Connecting an agent