SAP Netweaver Business Intelligence BI / BW

Symptom
The MultiProvider hint (RRKMULTIPROVHINT) can be improved.
Other terms
Query, MultiProvider, RRKMULTIPROVHINT
Reason and Prerequisites
1. A filter that is set dynamically is not evaluated.2. A test reading only occurs if there are less than 21 selection values.3. Navigation attributes are ignored.4. No optimization occurs when you use the F4 help or select a filter value (relational browse).
Solution
1. This is a minor error, which is corrected with Note 1156602. 2. The table RRKMULTIPROVHINT now contains the field MAXOR.
With this field, you can determine for each characteristic how many rows the WHERE condition of the test reading may have.
3. Furthermore, it is now possible to enter time-independent navigation attributes in the table RRKMULTIPROVHINT.
These are treated like standard characteristics with the exception that only SID conditions can be processed. Interval restrictions on compounded attributes, for example, cannot be checked. Time-dependent attributes are also ignored.
4. The hint is now also effective in the F4 mode D on the variable screen and for the filter value selection in the executed query, that is, in the relational browse.
5. The result of the test reading is now buffered as a shared object. Therefore, the database has to be accessed only after new data is loaded.
You can observe this buffer in transaction SHMM.
SAP NetWeaver 7.0 BI
Import Support Package 19 for SAP NetWeaver 7.0 BI (BI Patch 19 orSAPKW70019) into your BI system. The Support Package is available onceNote 1136884″SAPBINews BI 7.0 Support Package 19″, which describes this Support Package in more detail, has been released for customers.
SAP NetWeaver 7.1 BI
Import Support Package 06 for SAP NetWeaver 7.1 BI (BI Patch 06 orSAPKW71006) into your BI system. The Support Package is available whenNote 1126007″SAPBINews BI 7.1 Support Package 6″, which describes this Support Package in more detail, is released for customers.
In urgent cases, you can implement the correction instructions as an advance correction.
You must first read Note 875986, which provides information about transaction SNOTE.
Before you implement the correction instructions, you must carry out the following manual steps:
1. Use transaction SE11 to create and activate the data element RRHINTMAXOR with the domain INT4 and the short description: “Maximum selections to be checked (0 has the same effect as 20)”.
2. Use transaction SE11 to add the field MAXOR with the data element RRHINTMAXOR to the data type RRKMULTIPROVHINT.
3. Use transaction SHMA to create and activate the area CL_RSR_RRK0_MULTIPROV_B_AREA.
Description: “Buffering of SELDR requests”
Root Class: CL_RSR_RRK0_MULTIPROV_BUFR
Displacem. Type: Displacement Not Possible
Area Structure: No Autostart
Lifetime: Without Read Access 2.000 Minutes

————————————————————————
|Manual Pre-Implement. |
————————————————————————
|VALID FOR |
|Software Component SAP_BW Business Inform…|
| Release 700 SAPKW70015 – SAPKW70018 |
————————————————————————
1. 1. Mit SE11 ist das Datenelement RRHINTMAXOR mit Dom鋘e INT4 und Kurzbeschreibung: ‘Maximal zu pr黤ende Selektionen ( 0 wirkt wie 20)’ anlegen und aktivieren.
2. 2. Mit SE11 dem Datentyp RRKMULTIPROVHINT das Feld MAXOR mit Datenelement RRHINTMAXOR anf黦en und aktivieren.
3. 3.Mit der Transaktion SHMA das Gebiet CL_RSR_RRK0_MULTIPROV_B_AREA anlegen und aktivieren.
Beschreibung: ‘Pufferung der Seldr Anfragen’
Wuzelklasse: CL_RSR_RRK0_MULTIPROV_BUFR
Verdr鋘gungsart: Nicht verdr鋘gbar
Gebietsaufbau: Kein Autostart
Lebensdauer: ohne Lesezugriff 2.000 Minuten4. Generieren Sie nun die Gebietsklasse CL_RSR_RRK0_MULTIPROV_B_AREA mittels Funktion ‘Gebietsklasse generieren’(STRG + F3). Diese finden sie auf dem Start-Screen der Transaktion SHMA