Exporting Table Statistics to the Productive System
The table usage statistics is representative for the time when the update is performed. In particular, it's important to consider the time
when business users are working on the bridge subsystem.
Context
An ideal dataset covers a period of time with all activities and business processes, such as the time in the week when SUM performs the update.
To export table size information, make sure that the database statistics are up-to-date. Outdated database statistics can result in
inaccurate size values.
Procedure
Call transaction SUMTOOLBOX.
Execute the tool Export data for Impact Analysis to export the statistics to the file
ZDIMPANA.ZIP.
Check for periods that are not flagged as Contains Imports to avoid false positives in impact
analysis.
For example, if you perform daily imports into the productive system, you cannot select a period. In this case, you must
continue with the selection of periods that are flagged as Contains Imports.
If you export a large period of time, such as a month or more, it is possible that you also export statistics about table
accesses that are not necessarily relevant to the business processes needed during the runtime of the bridge subsystem.
Provide the exported file ZDIMPANA.ZIP to the save subdirectory of the SUM directory.
Note that the save subdirectory is only created by the Software Update Manager during the
Preprocessing roadmap step.