‎2009 Jul 09 3:53 PM
Hello there,
I'd like to be able to customize the fields for which change document entries are created. As change documents normally depend on setting the "change document" flag on the data element, I wonder how best to achieve this.
1. Is there a way to programmatically change the data element and re-generate the change document code when an entry in the customizing table is added/deleted?
2. Alternatively, I could flag all of my data elements as change relevant, then do the field comparison myself in my applicaton and pass to the generated FM the old values in fields for which no change should be recorded. In this case, what would be the best way to re-use the field comparison logic of the standard, so as to be consistent and not re-invent the wheel?
3. Is there any other way to do this? Maybe it's even in the standard, but I didn't find anything. I'm on a 7.00 basis.
Thanks,
Sebastian
PS: I'd also be grateful for pointers to tutorials/example coding, e. g. a class that encapsulates the calls to the generated functions.
If there's any document on the performance impact of creating change documents, I'd also be grateful to know about this.
‎2009 Jul 09 4:13 PM
This could help in some way.
http://sample-code-abap.blogspot.com/2008/02/applying-change-document-technique-on.html
Thanks,
Raj
‎2009 Jul 09 4:13 PM
This could help in some way.
http://sample-code-abap.blogspot.com/2008/02/applying-change-document-technique-on.html
Thanks,
Raj
‎2009 Nov 10 12:59 PM
question closed. I have not found a way to do what I originally wanted, but that was far too complicated anyway. Thanks for the link.