Child pages
  • EI Intermediate Results returns LESS results than Execute
Skip to end of metadata
Go to start of metadata

Intermediate Results returns LESS results than Execute

Purpose

To explain why the results differ when using Intermediate Results  v  Execute

Overview

When using multiple 'joins', the dataset is reduced at different points

Where to find the Intermediate Results option ...

When you are checking an APD, a handy method is to step through each node using the 'Intermediate Results' option. This can be found in the Context Menu of any node. You simply right-click on the node and select 'Intermediate Result. A temporary table is created with the suffix /BIC/000Axxx

Intermediate Results with a JOIN ...

 

The highlighted node in the image above is a JOIN node. As you can see, data comes into the node from more than one previous node. The join captures the data and this data gets combined for passing to the next node in the sequence. The order/sequence is indicated by the arrows. When an Intermediate Result is saved, the dataset progresses to the next node of the APD. 

When an Intermediate Result is saved, that saved dataset progresses to the next node of the APD. However, if you use multiple intermediate result tables, because each node is processed as an individual stand-alone component, the results can be distorted.

Due to the processing logic of the analysis process, the processing is pushed to the preceding nodes and hence the selection criteria used or the join condition is not taken into account. But for example, if intermediate result is calculated on the FIRST join, then it will still succeed as the processing for this node has already happened. Therefore you see that there is a discrepancy in the records. Calculations at intermediate result time should not be taken as valid for use in full execution of the analysis process. If necessary delete the temporary tables to ensure true working results in Execute mode.

Related Content

Related Notes

605208     RSCRM - Restrictions
605213     RSCRM: Performance
646699     Restrictions during the use of BW queries
751577     APD-FAQ: Data source query

  • No labels