Dispatching ALE IDocs for Change Pointers

Change pointers must be processed by an ABAP, e.g. RBDMIDOC.

The actual distribution of documents from change pointers must be done by an
ABAP, which reads the change pointers and processes them. The standard ABAP
for that is RBDMIDOC. For recurring execution it can be submitted in a scheduled
job using SM35 .

It then calls dynamically a function module whose name is stored in table TBDME
for each message type.

Call Function Tbdme-Idocfbname
Exporting
Message_Type = Mestyp
Creation_Date_High = Date
Creation_Time_High = Time
Exceptions
Error_Code_1.

Example :

A complex example for a function module, which collects the change pointers, can
be examined in:

MASTERIDOC_CREATE_SMD_DEBMAS .

This one reads change pointers for debtors (customer masters). During the
processing, it calls the actual IDoc creating module

MASTERIDOC_CREATE_DEBMAS .

To summarize the change pointer concept

• Change pointers record relevant updates of transaction data
• Change pointers are written separate from the change documents, while at the
same time
• Change pointers are evaluated by a collector run

BDCPS : Change pointer: Status

BDCP : Change pointer

BDCPV : A view with BDCP and BDCPS combined: Change pointer with status

TBDA2 :

Declare activate message types for change pointers with view V_TBDA2.or
transaction BD50 or .

SALE -> Activate change pointers for message types

TBD62 : The view V_TBD62 defines those fields which are relevant for change pointer
creation. The table is evaluated by the CHANGE_DOCUMENT_CLOSE function.
The object is the same used by the change document. To find out the object name,
look for CHANGE_DOCUMENT_CLOSE in the transaction you are inspecting or
see table CDHDR for traces.

Tables involved in change pointers processing :

Object
Table name
Field
DEBI
KNA1
NAME3
DEBI
Kann1
ORT01
DEBI
Kann1
REGIO

(71)

RELATED POSTS