Model / CROSS / CDHDR

CROSS — Cross-Application Foundation

CDHDR

14 fields · 4 key · 2 foreign keys · sourced from leanx.eu

Change document header — the audit-trail record the ledger's provenance claim depends on: who changed what business object, in which transaction, and when. Every change captured by SAP's change-document service writes one CDHDR row per change session, with the field-level detail in CDPOS underneath it. SAP's real CDHDR carries all its fields; this definition carries the table complete.

Hover a canonical name to see the legacy SAP field name

Canonical nameConceptDescriptionData elementTypeCheck table
CLI keycliensClientMANDTCLNT 3T000
OBI_CLS_GEN keyobiectum classis genusObject class — groups the business object type being auditedCDOBJECTCLCHAR 15
OBI_VAL_CLV keyobiectum valor clavisObject value — the key of the changed business object instanceCDOBJECTVCHAR 90
DOC_NUM_CLV keydocumentum numerus clavisDocument change number — the key CDPOS items join back onCDCHANGENRCHAR 10
USR_NOM_PSNusor nomen personaUser name of the person responsible in change documentCDUSERNAMECHAR 12
DIE_DMUdies documentum mutationisCreation date of the change documentCDDATUMDATS 8
TMP_MUTtempus mutatusTime changedCDUZEITTIMS 6
TCODETransaction in which a change was madeCDTCODECHAR 20TSTC
NUMnumerusPlanned change numberPLANCHNGNRCHAR 12
NUM_DOC_CREnumerus documentum creatusChange number of the document created by this changeCD_CHNGNOCHAR 10
SGNsignumFlag that changes were generated from planned changesCD_PLANNEDCHAR 1
OBI_GENobiectum genusApplication object change type (U, I, E, D)CDCHNGINDHCHAR 1
LNG_CLVlingua clavisLanguage KeyLANGULANG 1
CMPcampus3-Byte fieldCHAR3CHAR 3

Foreign keys

FieldCheck tableCheck field
MANDANTT000MANDT
TCODETSTCTCODE

View CDHDR.yaml in the repository