I think there is a little confusion about change pointers and change documents. Change documents are written every time when a field of a DDIC table is modified, if and only if the underlying data element has the field LOGFLAG (in DDIC: DD04D-LOGFLAG) is ticked. You can inspect this by browsing table DD04D or via transaction SE11 for the data element in question.
The ALE model ignores the CDHDR/CDPOS entries. Rather it uses an own definition of what has to recorded and used as change pointer trigger. These information is defined in tables:
* TBDA1 ? general activation
* TBDA2 ? message types relavent for change pointers
* TBD62 ? relevant fields for change pointers
The logic for this is coded in function:
Which is in turn called by:
Dig Deeper on SAP ABAP
Related Q&A from Axel Angeli
An SAP user wants to know how to upload data into SAP R/3 when SAP Scripting is not enabled. Continue Reading
An SAP user is receiving an error message while integrating SAP iDoc PORDCR1 for a purchase order. Continue Reading
An SAP user is having difficulty with PERNR iDoc while transporting data from SAP to an external system. Continue Reading
Have a question for an expert?
Please add a title for your question
Get answers from a TechTarget expert on whatever's puzzling you.