The user can utilize the program ZFIND_UPDATE_ORPHANS, and he will notice incomplete update records with update modules for the function modules primarily meant for creating the change documents. The affected function modules are known as <OBJECT>_WRITE_DOCUMENT. In this scenario, , <OBJECT> denotes the name of a change document object, such as ADRESSE3, LIEFERUNG, NRINTERVAL, or alike.
Solution
A user can usee the function modules for creating the change documents.
User must verify
- whether the change document already exists
- whether the modification which is to be documented in this change document, has been made, as its not obvious which error led to these incomplete update records.
A change document primarily documents a change to one (or more) table(s).
Use t-code SM13 for checking the data of the affected update requests.
Procedure:
- All the canceled update requests in transaction SM13 are displayed.
- By double-clicking an entry, brings the user to the view for updating modules. Incase a function module <OBJECT>_WRITE_DOCUMENT is affected, choose 'Goto -> Update module' in the menu for displaying the corresponding update data (interface parameters of the function module).
- First, OBJECTID, UDATE, and UTIME are critical in this case.
- The parameters UDATE and UTIME comprise of the date and the time of the change. This parallels to the time at which the update request was initially created.
- The name of the function module encompasses the name of the change document object, which is mainly the object class (for example, for ADRESSE3_WRITE_DOCUMENT, the object class is ADRESSE3).
- User should verify whether an entry exists in the table CDHDR (transaction SE16) for the values in OBJECTCLASS, OBJECTID, and UDATE. Incase, there are many entries, then user should also compare the time (UTIME).
- The data of the function module is in the database, incase a corresponding entry exists in the table CDHDR.
- The table CDHDR comprise of the header data of the change documents.
- User is not required to update the change document.
- If no corresponding entry exists, user should verify if the change to be documented has been made.
The interface parameters of the function module change contain, all the information of the function module. - In this scenario, the values for the table entries are controlled in the affected transfer tables (several) or in the transfer structures. User can utilize these before and after values for reproducing the change.
- User must perform this check in the application which utilizes the change document object. The interface parameter TCODE lists all the additional information about the origin of the change.
- User can update the corresponding update requests in case he has ensured that the change documents to be created does not yet exist in the system, and that the change to be documented has actually been made.
- This is applicable only to the change document function module.
- User can update the record for THIS function module.
- However, all the owners of the other function modules of the same update record should agree to this subsequent posting.