Filling the Fields in the Program
Fill the fields and tables relevant to the change documents in accordance with the following specifications.
General Data
These are the fields that are defined in the INCLUDE program section F<K4>CDF.
● OBJECTID
Object value (key) of the object characteristic
● TCODE
Transaction with which the change process is performed
● UTIME
Time changed
● UDATE
Change date
● USERNAME
Name of the person who made the change
Object-Specific Data
These are the fields that are defined in the INCLUDE program section F<K4>CDV .
Single Case Tables
● Table *<Name of Table>or structure <Name of Old Structure> (with the structure that matches the table)
The table header line or the structure must contain the original data.
● Table <Name of Table>
The table header line must contain the changed, new data.
● Table *<Name of Ref. Table> (only if the Name of the Ref. Table was specified in the definition of the change document object)
The table header line must contain the original currencies and units.
● <Name of Ref. Table> (only if the Name of the Ref. Table was specified in the definition of the change document object)
The table header line must contain the current currencies and units.
● UPD_<Name of Table>
You use this indicator to specify the processing logic.
The following values are permitted:
○ "D" (DELETE)
For the row in *<Name of Table> or <Name of Old Structure>, a change document item must be created that is to be marked as deleted. <Name of Table> is not processed.
○ "I" (INSERT)
For the row in *<Name of Table>, a change document item must be created that is to be marked as entered/recorded. *<Name of Table> or <Name of Old Structure> are not processed.
○ "U" (UPDATE)
*<Name of Table> or <Name of Old Structure> and <Name of Table> are compared and a change document item is created for each changed field. The key of *<Name of Table> or <Name of Old Structure> and <Name of Table> must be identical.
○ " " (Space, no processing)
*<Name of Table> or <Name of Old Structure> and <Name of Table> are not processed in the update task. If there are no changes, processing can be skipped to save time.
Multiple Case Tables
These tables must be sorted according to key before they are passed. No double key may be present in the table.
● Y<Name of Table>
The table must contain the original version of the changed or deleted records. The structure is made up of the table, as specified in the definition of the change document object under the Name of Table, a processing indicator (TYPE C, Length 1), and – if necessary – the structure of the referenced current and unit table, as specified in the definition of the change document object under Name of Ref. Table. It is created during the generation of the INCLUDE objects for the change document object and stored under the name V<Name of Table> in the Dictionary.
The processing indicator can be changed from Space to "D" if it is to be processed in the application. Otherwise it has no effect.
● X<Name of Table>
The table
must contain the original version of the changed or entered records. The
structure is composed in the same way as Y<Name of Table> (see
above).
You can use the following values for the processing indicator:
○ "I" (INSERT)
Line was newly created or table row was deleted; afterwards, a line with the same key was entered in the same transaction and this is to be documented as “Change”, but as “Delete” and “Enter” (special case).
○ "U" or " " (Space) (UPDATE)
The parameter UPD_<Name of Table> (see below) is used to determine whether the line is a newly entered one or a changed one.. Only when in the parameter value "U" and the following key comparison of the two tables TABLE_OLD and TABLE_NEW two lines with the same key are found will there be a query of the processing indicator.
The processing indicators of the internal tables in the multiple case can always be filled with space, with the exception of the special case (in X<Name of Table>). The option of filling the processing indicators also with "D", "I", or "U" was set up so that the tables can also be used in the application programs for other purposes where such processing indicators can be helpful.
● UPD_<Name of Table>
You use this indicator to specify the processing logic.
The following values are permitted:
○ "D" (DELETE)
For each row in Y<Name of Table>, a change document item must be created that is to be marked as deleted. X<Name of Table> is not processed.
○ "I" (INSERT)
For each row in X<Name of Table>, a change document item must be created that is to be marked as inserted. Y<Name of Table> is not processed.
○ "U" (UPDATE)
The keys of TABLE_OLD and TABLE_NEW are compared. The following cases exist:
– 1. Rows exist in TABLE_OLD but not in TABLE_NEW: Change document items need to be created for rows in TABLE_OLD that are to be identified as deleted.
– 2. Rows exist in TABLE_NEW but not in TABLE_OLD: For the row in TABLE_NEW, a change document item must be created that is to be marked as entered/recorded.
– 3. Rows exist in TABLE_OLD as well as in TABLE_NEW: A change document item is created for every changed field that is defined in the dictionary as change-document-relevant.
○ " " (Space, no processing)
Y<Name of Table> and X<Name of Table> are not processed in the update task. If there are no changes, processing can be skipped to save time.
Text Changes:
If text changes are to be logged (according to definition of the change document object), the following fields need to be filled:
● ICDTXT_<Object>
In this structure, the change document-relevant texts are collected with the corresponding specifications:
○ TEILOBJID
Key of changed table row
○ TEXTART
Text type of changed text
○ TEXTSPR
Language key
○ UPDKZ
Change indicator for table row: D(elete), I(nsert) oder U(pdate)
● UPD_ICDTXT_<Object>
Change indicator for text table.
○ " " (Space)
Table is not considered in update task.
○ "U"
Table is not considered in update task.
Optional Parameters
You can also use the following parameters of the INCLUDE program part F<K4>CDF:
● CDOC_PLANNED_OR_REAL
With this parameter you control whether the changes to be logged are real or planned changes.
Possible values:
– |
“R” |
Real change |
|
– |
“P” |
Planned change |
|
– |
“ “(space) |
If no plan number exists |
Real change |
|
|
If a plan number exists |
Planned change |
● CDOC_UPD_OBJECT
If it is relevant for the evaluation of the change documents which action was performed during the change for the respective object, you can pass the executed action using this parameter.
Possible values:
○ “I” The object was inserted.
○ “U” The object was changed.
○ “D”: The object was deleted