Defining Change Document Objects  

Proceed as follows:

...

       1.      Call the maintenance transaction SCDO for change documents (Tools → ABAP Workbench → Development → Other Tools → Change Documents). You get an overview of change-document objects that already exist.

       2.      Choose the menu option Create.

       3.      Enter the name you want to give the change-document object.

       4.      Choose Continue. You now see a new window for entering the respective tables.

       5.      Enter a descriptive short text for the change-document object.

       6.      Enter the following specifications for each table whose changes are to be logged in the change document for this change-document object:

○       Name of the Table

Name of the table, as defined in the Dictionary

○       Indicator Transmission as Internal Table

If you wish the change data to be passed in an internal table (multiple case), select this field. If you do not select this field, the change data will be passed in a work area (single case)

○       Indicator Doc. of Individual Fields at Deletion

If you wish to have your own log record for every single field when data is deleted, select this field. If you do not select this field, the deletion of all relevant fields is entered in a document item (in the field FNAME you have ‘KEY’, field TABKEY filled).

○       Indicator Doc. of Individual Fields at Insertion

If you wish to have your own log record for every single field when data is deleted, select this field. If you do not select this field, the deletion of all relevant fields is entered in a document item (in the field FNAME you have ‘KEY’, field TABKEY filled).

○       Name of Ref. Tab. (Name of referencing table)

If currency and unit fields are not defined in the passed table, but in a reference table, you must pass the name of the reference table and the referenced field to the function modules. For this purpose, create a structure in the Dictionary as INTTAB, and then define fields for this structure that are made up of names from the corresponding reference table and the reference fields.

Then enter here the name of this structure that refers to the reference table

In the single case, the reference information is passed in the form of two additional work areas (old, new). In the multiple case, the internal tables are enhanced to include the reference structure.

In table X4711, there is a value in the field PRICE; the unit of this value is taken from the field CURR in table T001. Therefore you must must create a structure of type INTTAB that contains the field T001WAERS in the dictionary, for example, R4711.

In the program, supply the fields T001WAERS of the reference table (old and new) for the single case and the internal tables for multiple case with the value from T001-CURR.

○       Name of the Old Structure

Only possible for single case, that is, when transmitting change data in a work area. If you do not want to use the *‑workspace, specify an alternative name here for the old workspace.

       7.      After you have entered all the relevant data, choose Add Entries. The new entries are adopted in the display.

       8.      Save your entries.

Transport Change Document Object

The change document objects are included in the transport as a separate object type; the inclusion in a change task takes place when the object is created.

During transport, the generation of the object-specific update task is performed in the target system.

Transport Object for Change Document Objects

R3TR CHDO

During transport, the generation of the object-specific update task is performed in the target system during import. The object-specific update process contains generated structures, include programs, and a function group.

All manual changes to generated structures, include programs, or the function group are overwritten by the generation during import.

Never transport the generated structures, include programs, or function group directly using their own transport objects. This can cause errors when importing the change document object.

The generation is executed in its own after-import method AFTER_IMP_CHDO.