|Home • Trainings • Quiz • Tips • Tutorials • Functional • Cert Q's • Interview Q's • Jobs • Testimonials • Advertise • Contact Us|
Creating Change Documents for Custom tables
By Mydhili Maddala, IBM India
Business data objects are changed
frequently. It is often useful to log these changes for objects that are
critical. SAP Systems log changes to business data objects in change documents.
For standard business process like creation of Purchase Order, creation of
material, creation of delivery etc SAP provides certain change document objects.
Similarly, to keep track of the changes in any custom tables, we need to
implement change document system.
This abstract talks about the
concept of the change document object for custom tables. SAP does not
automatically keep track of the changes done to a custom table data. We need to
define it manually and activate it. The
concept of change documents should be implemented only if it is really important
that you keep track of changes made to the object.
In our project, we got a requirement of providing this
change document feature for a view cluster which consists of four tables grouped
together logically. When ever a change is done to any of these four tables, the
changes must be logged.
To meet this requirement, we
created a change document object for the view cluster using the transaction SCDO.
All the changes get stored in CDHDR and CDPOS tables.
Steps to implement Change Document functionality
To define a change document object,
proceed as follows:
The generation creates INCLUDE objects, which contain
general and specific data definitions and the program logic for the update
After defining a change document, to integrate the
change document object in our program, we need to follow the below steps.
Please send us your feedback/suggestions at webmaster@SAPTechnical.COM
©2006-2007 SAPTechnical.COM. All rights reserved.
product names are trademarks of their respective companies. SAPTechnical.COM
is in no way affiliated with SAP AG.
Graphic Design by Round the Bend Wizards