A change run updates the 'E' table of the aggregates while doing the alignment for changes in the master data.
-
True
-
False
A change run does NOT update the 'E' table of aggregates during master data alignment. The change run updates the 'M' (active) table, not the 'E' (historic/archive) table. The 'E' table contains historical data and is not affected by change run alignments.
To answer this question, we need to understand the concept of a change run and how it affects the 'E' table of the aggregates.
In SAP, a change run is a process that updates the aggregates in the Business Information Warehouse (BW) system. It aligns the aggregate data with the changes made in the master data. However, the update process of a change run does not specifically update the 'E' table of the aggregates.
The 'E' table in BW represents the exception data. It contains information about data that did not meet certain criteria or conditions during the aggregation process. The 'E' table is typically used for monitoring and analyzing exceptions or errors in the data.
Therefore, the statement "A change run updates the 'E' table of the aggregates while doing the alignment for changes in the master data" is incorrect.
Option B) False - This option is correct because a change run does not update the 'E' table of the aggregates.