How to Implement SAP Change Document

Builds SAP's Change Document framework on two custom tables, ZZCUSTOMER and ZZCUSTOMER_BANK: creating the Change Document Object in transaction SCDO, then wrapping each INSERT, MODIFY and DELETE on the Z-tables together with a call to the generated WRITE method inside one ABAP class, so both commit in the same Logical Unit of Work. Because the generated method cannot read old values back from the database itself, the class reads them before the update and holds them in memory; a Managed RAP application skips this step by specifying the Change Document Object directly in its Behaviour Definition instead. This is the ABAP side of change trackingChange trackingcapabilityKeeping a readable history of what changed on a record, who changed it and when — as business history rather than database journalling.SAP and community, unassessed: a change document object logs who changed a field, and when, into CDHDR and CDPOS.