Ansicht
Dokumentation
IUUC_TABLE_ANALYSIS - Table analysis: determine process options for tables
SUBST_MERGE_LIST - merge external lists to one complete list with #if... logic for R3up BAL Application Log DocumentationThis documentation is copyright by SAP AG.
Purpose
This report is used to classify the DB tables of a customer system concerning the way how the table should be treated in the context of the incremental upgrade.
Basically, the following process options are used:
- Delta replay
Data changes occurring in the time period of the monitored production need to be replicated from the former to the future productive system. This is especially true for all master data and transaction tables of the application components used. As criterion, the delivery class is used. Tables assigned to the following delivery classes qualify for the delta replay:
A (application tables for master data and transaction data)
L (temporary data)
E (control tables)
Also tables for report and transaction variants and for batch processing need to be transferred.
- Delayed replay
This applies to tables for which changes should be transferred, but this can also be done after the start of the productive use of the upgraded system. This is true for the application log and system log tables and for change documents.
- Freeze
Changes of such tables must not happen during the time of the monitored production. This applies to cross-client tables and to tables of the delivery classes
S (shouldn't be changed by customers anyway)
C (customizing shouldn't be done during the monitored production)
G (customizing shouldn't be done during the monitored production)
W (contents would be transported using specific transport objects - should not happen during monitored production)
- Ignore
Changes in these tables are to be ignored. This usually applies to tables of the central basis and to upgrade shadow tables, as well as to the update tables VBDATA, VBHDR etc.
Integration
Prerequisites
Features
Selection
The processing can be restricted to specific table names or ranges of such. It can also be restricted to software components.
If checkbox "test" is active, this means that the result will not be persisted in the corresponding DB tables. In this case, the activity cannot be set to status "completed". Only a log with the classification that would be done in the productive run is created.
The relevant system for the table analysis is the system to be upgraded (the hitherto productive system). Therefore an rfc destination referring to that system should be specified.
It is indispensable to specify the rfc destination of a system where the upgrade has been performed, in order to get some specific upgrade information.
Standard Variants
Output
An application log is created. It lists al those tables that are set to process option "ignore", as such tables will not be considered further, as well as the reason why the specific process option was chosen. In case the logic applied to determine a certain process option gives an ambivalent result this is also shown.
The log also lists tables for which no object directory entry exists, or which are assigned to a non-existing package. Such tables are assigned process option "Freeze" by default.
Activities
Example
BAL Application Log Documentation PERFORM Short Reference
This documentation is copyright by SAP AG.
Length: 3552 Date: 20240531 Time: 062048 sap01-206 ( 66 ms )