Jul 16

Are You Properly Managing Your SAP Change Pointers Part 2 – A Simple Source of Runaway Growth

Last time, in my 50,000 foot view post, I presented an overview of the purpose, the location, and the
expected lifecycle of change pointer records.    I also briefly discussed two programs:

RBDMIDOC –  triggers IDOC distribution for ‘unprocessed’ change pointer records, and marks
those change pointer records as ‘processed’.
RBDCPCLR –   deletes the ‘processed’ change pointer records from the change pointer tables.

One obvious source of runaway change pointer table growth is never running the cleanup program RBDCPCLR.
Using transaction SM37 (batch jobs), you can determine if RBDCPCLR is running in a batch job, and how frequently it is running.
As shown in the screen shot below, enter RBDCPCLR in the ABAP Program Name box, enter a relevant date range,
and check the various job status boxes that you might be looking for.  I recommend setting a significantly wide date
range, as I have found situations where RBDCPCLR was running in a scheduled batch job a while ago, but for some
unknown reason is no longer currently running.

Pressing the EXECUTE button will produce a list of batch jobs containing RBDCPCLR.

SM37 Simple Job Selecion Screen

Avatar

About The Author

Mike Salvo consulted with DataXstream from 2006 to 2011. He remains a valued team member and mentor. For current information regarding Mike Salvo please visit his Linkedin profile.

Leave a reply

Your email address will not be published. Required fields are marked *

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.

This site uses Akismet to reduce spam. Learn how your comment data is processed.