Change pointer issue!!

[Former Member]

Hello Guys,

I want to track the changes made in the vendor master transaction(XK02).

I want to implement change pointer for this.

Can anybody help me figure out the steps imvolved in this..??

Thanks in advance for your help.

[Former Member]

Hi

Go through the Book ALE EDI Technology by Aravind Nagpaul.

and follow the instructions.

Warm Regards,

Baburaj

[Former Member]

Hi,

Implementing change pointers is a long process,

Reduce the IDoc type Transaction Code: (BD53)

Activation at the Segment Level and Field Level.

Configuration for Change Pointers using BD61, BD50, BD52

Configuration for Transactional Data - WE20, WE21, BD64,.....

Like wise many operations are there.

Table BDCPS will have the Change Pointers triggered.

Table BDCP will have all the field related to the change pointers.

Warm Regards,

Baburaj

[Former Member]

Generally, whenever changes are done the corresponding data is been maintained in CDHDR and CDPOS tables....

Check this tables and u will find the solution.

[JozsefSzikszai]

hi Sumeet,

the changes in the vendor master are saved into table CDHDR-CDPOS automatically.

ec

[Former Member]

actually i want to capture the instance when changes are made...

CDHDR and CDPOS helps me in finding the changes and not the event..

I want to implement Change pointers for certain fields in Vendor master message type using transacion BD50, BD51 etc...

anybody has any idea about this...

[JozsefSzikszai]

OK, I see. I think you can use enhancement SAPMF02K. This runs whenever a vendor is changed. You just have to compare old and new values, and if any of them changed, than do your action...

[Former Member]

thanks for the reply,

but this does not solve my problem..

I will explain you my requirement in detail:

I need to develope a program to send a mail to user whenever there is a change in vendor master .... for this I need to capture the instance when there is a change. and that can be achieved using change pointer(I'm not very sure). Because whenver there is a change and if a change pointer is activated for that field, an idoc is sent automatically with chages.... is it so??

[JozsefSzikszai]

why does not solve your problem? The exit runs whenever a vendor is processed, you only have to check if SAVE was pressed (sy-ucomm = /SAVE or something like that) and if any field was changed, if yes, send the idoc.

About this change pointer I've never heard, but I do some research...

UPDATE:

looks like you are right, these change pointers could be helpful for you:

http://help.sap.com/saphelp_erp2005/helpdata/en/52/248d02890311d2b464006094b9c9b4/frameset.htm

Edited by: Eric Cartman on Feb 20, 2008 5:30 PM

[Former Member]

thanks all for your comments... I'll try it and if found useful, close the thread..

[Former Member]

Hi Sumeet Maheshwari

You need to make use of BOR objects LFA1, LFB1.etc and the events inside like change , create

The change documents are configured here whenever they are ttriggered.

thanks

Dany

[Former Member]

Hi Dan,

Thanks for ther reply..

I dont have any experience with BOR objects..

can you please elaborate??

Thanks again..

Sumeet...

[Former Member]

Hi,

Well- Go to to tcode: Swo1 and you need to copy the existing LFA,LFB1..etc to ZLFA1 or ZLFB1.

and in one of those events for create or change you need to write a function module/subroutine/code that keeps track of these changes into a structure depending on your methods parameters.

Your Function module /subroutine gets executed in one of the methods of the BOR object after the relevant event for vendor creation or vendor change is raised.

After this you need to configure these events in SWEC.

In this transaction, the details are available as to which events are raised and whether the input requires us to specify the change document object, object category and type of the event. Specify the trigger event by choosing the radio button for On create or On Change.

Hope this helps a little.

thanks

[Former Member]

thanks Dan, it was helpful.. I'll try.

I'm closing the thread..