Problem with Change Pointers

[Former Member]

Hi All,

I have a doubt regarding IDOCs. I don't want the change pointers to be written to BDCPS for the segments that I deselected in IDOC reduction (BD53). How can I do this?

I don't want the changes to Customer Sales Area Text to be transferred so I deselected the relevant segment using BD53. The IDoc does not process the change pointers on text from BDCPS. So the flag is not set to processed in BDCPS. This part is ok. The problem is that I don't want these changes to be written to BDCPS in the first place because the IDoc does not process these changes and the status is never set to processed. There are lot of unwanted entries in BDCPS which is increasing the IDoc processing time. Can anyone help me on how to avoid the change pointers from being written to BDCPS or point me to some maintenance program to delete these entries.

Thanks in Advance!!

sckr

[Former Member]

You can maintain the list of fields captured as change pointers via BD52.

[Former Member]

Hi Michael,

I checked BD52. The fields related to customer sales area texts is not entered against KNVV table. But the change pointers are still being written. Any other suggestions?

Thanks,

sckr

[Former Member]

I was looking into this for MATMAS a while back and found that it automatically captured sales text for materials, if the reference message type in BD60 was MATMAS. You might find that DEBMAS works in a similar fashion. Try using a custom message type, if you're not already, and change the reference message from DEBMAS to your custom message.

[Former Member]

If you step through the customer update code, you will come to a call to function CUSTOMER_TEXTS_CP_CREATE which is called in update task. One of the first things the function does is call REFMSGTYPE_GET_REDUCE_MSGTYPES. This function selects a list of message types from TBDME (the table behind BD60) baed on reference message type DEBMAS. This is how it works for MATMAS as well. The option I provided in my previous post should work for you in this case as well.

[Former Member]

Michael,

It Worked!! Thanks a lot

sckr