Here, the frontend or the MDX processor sends the data request to theOLAP processor.Importing I_TH_REQ_FREE: This table contains the drilldown characteristics of thenew list. C_THX_SLICER: This table contains the dynamic filter. As in tableSELDR>, equal conditions, intervals and hierarchynodes are stored in separate components. However, not all combinationsare permitted here. Check:
- Whether the dynamic filter is correct
- Whether, particularly in component SLICER-NODE, the
hierarchy> has been filtered and expandedcorrectly (FROM_TLEVEL and TO_TLEVEL ).Process In the forms 'read_init_0' and 'read_init_1', mandatory drilldowncharacteristics are added. In the forms 'read_init_2' and 'read_init_3', hierarchy nodes are dealtwith again. The tables REQ_FREE and SLICER are now transformed into thetable L_TSX_FF. In the form 'authority_list', the authorization for this list ischecked. In the form 'get_qcube_buffer', the system tries to read this datarequest from the cache. If this is not possible, the data must be readagain. In the form 'read', the dynamic request L_TSX_FF is merged with thefixed filter condition. The system creates the local internal tables-SELDR and <(><<)>G_SX_RTO>-SFC for this. After the data has been read, all presentation hierarchies involved areaggregated to the highest level in the form 'hiera_aggre_spid'. Some internal calls also take place from function group RRK0 itself,for example, for normalizing, for selecting constants or for expandinga hierarchy node.
|