Description This report checks which settings in the system could lead to problemsbefore importing a changed extract structure. It issues correspondingmessages for the following cases:
- There should be no data in the V3 update for any of the clients for
applying the relevant extractor structures. If you are not sure, the V3update for the relevant update should be started from theCustomizing Cockpit>.
- If there is still data in central delta management, these should be
fetched from BW before importing the changed extractors.
- If a restructure has already been implemented in the target system, it
may be that the data is still available in the restructure tables.After importing the changed structure, these entries can no longer becpied into BW. The contents of the restructured tables for the relevantapplications should be deleted> in the target systemand if necessary, a new new restructure should be carried out.
- If the update log is active, the log data can no longer be read for the
relevant application after importing the changed extractor. This isonly possible after posting and overwriting of the last log entry. You can use the parameter "Delete BW logs" to delelte all update logsfor application of the selected extractor. Note that by changing the extract structure, you need to reactivate thetransfer structures in BW.
|