Change pointer buildup over time.

[Former Member]

I am using RBDMIDOC and the change pointer message type /SAPSLL/MATMAS_SLL to call RFC /SAPSLL/MATMAS_DISTRIBUTE_R3 to get my materials transferred from R/3 to GTS.

Because I only need certian types of materials in the GTS system I have utilized user exit EXIT_SAPLSLL_LEG_PRR3_004 in which I delete out the material data that I do not want to send to the RFC call to GTS.

Unfortunatly the result is that for the materials I do not wish to transfer to GTS, the Process Indicator is never getting set to 'X' so the RBDMIDOC attempts to process these materials every time and never clears them out.

Now my process is running slower and slower, does anyone have a suggestion on how I can stop processing these entries multiple times?

[Former Member · Accepted solution]

Dear Clay,

A temporary solution could be the deletion of unwanted (obsolete) change pointers with program RBDCPCLR (transaction code BD22).

Best regards,

Christiane

Edited by: Christiane Schnellenbach on Apr 7, 2010 10:44 AM

[Former Member]

Hello Clay,

i suggest you to set up a break-point in the user exit. I am suspicious that RBDMIDOC does not call user exit EXIT_SAPLSLL_LEG_PRR3_004.

You might want to use EXIT_SAPLSLL_LEG_PRR3_002 or *003.

Regards,

Gabriel.