SAP Netweaver Business Intelligence BI / BW

Symptom

Support Package 19 for BI Release 7.0
Other terms

SAPBWNEWS, Support Packages for 7.0, BW 7.0, BW 7.00, BW Patches, BI, BI 7.00, SAPBINews, NW2004s, 2004s

Solution

This note contains the SAPBINews for Support Package 19 of BI Release 7.0. Here, you will find a list of all notes describing corrections or enhancements in Support Package 19. This note will be updated when other notes are added.
Note that BI 7.0 ABAP Support Package 19 is a part of SAP NW 7.0 Support Package Stack 17.
The information is divided into the following areas:
Manual actions that may be necessary:Factors you must take into account when you import the Support PackageErrors that may occur after you import the Support PackageGeneral information:Errors corrected by this Support Package; Enhancements delivered with this Support Package.See the release and information notes.

Factors you must take into account when you import the Support Package:

Before you import the Support Package, check your system for inactive objects.
Call transaction SE80, select “Inactive objects” and enter ‘*’ in the user field.
If information is displayed in the SAP namespace in the “Transportable Objects” section, you cannot import any Support Package.
You must first activate the inactive objects.
You can restart a terminated note installation consistently by using SNOTE consulting Note 1131831.
This activates the inactive objects. Do not delete inactive objects from the transport request.
Note that you are no longer allowed to delete objects from the transport request and doing so would cause extensive subsequent problems.
Note 822379 describes the correction procedure.

Find out about the latest SAP Notes that you also have to read and perhaps implement after you import Support Package 19.
Do not just indiscriminately implement all notes available after you import the corresponding Support Package. However, always implement “Hot News” and priority 1 notes.
In the search function in the notes database or on SAP Service Marketplace, use the search term: “SAPKW70020″, and under “Additional Criteria” select “Hot News” and “Correction with high priority”.
You can also restrict the search to a specific topic by entering the relevant specifications in the “Applic. Area” field, for example, “BW-WHM*”.
After you have imported a Support Package, you usuallymustuse transaction SNOTEto make further changes. Notes that have already been implemented may become inconsistent and may causefunctions to work incorrectly or syntax errors. Call transactionSNOTEandreimplementthe notes that have become inconsistent. When you have done this, your BW system is operative and consistent again.
Import the SNOTE corrections first and read the composite SAP Note 875986, which contains important notes about Note Assistant.
You should implement Notes 932065 and 948389 before you use transaction SNOTE to implement advance corrections. Otherwise, problems may occur when you try to deimplement notes again.
If documents have already been migrated to the portal, you may have to repeat the migration. For more information, see Note 950877.
If you have questions about downloading Support Package stacks, see Note 911032 ‘FAQ – SAP Support Package Stack Download’.
For minor revisions in the BI Accelerator, see Note 1079068.

Errors that may occur after you import the Support Package:

Extracting data from a DataStore object fails with the error message “Key figure unknown in InfoProvider “. This occurs when the DataStore object, which acts as the source, contains a referencing key figure. See Note 1243987.
If you execute data transfer processes (DTPs) from the Data Warehousing Workbench and the last request was red, an endless loop occurs. For more information, see Note 1155639.
Termination BRAIN 299 “System error in program CL_RSR_CACHE_SERVICE_TIMESTMP and form GET_MAX_TIMESTMP-01-” occurs when you execute a query. For more information, see Note 1243990.
On rare occasions, the termination TEST_SELECTIONS-1- occurs when the
authorization log (RSECADMIN log) is active. For more information, see Note 1243925.
The termination LOOK_UP_STAR_VARIABLES-01- occurs during the query execution. See Note 1244842.
Executing the query results in the termination BRAIN A125 or incorrect data. For more information, see Note 1267220.
The elimination of internal business volume does not work for the elimination of all pairs of characteristics. For more information, see Note 1275193.
Endless loop (in GUI) after using F4 in variable screen. For more information, see Note 1274580.
If you use the same characteristic when generating query variables, too many numbers or numbers that are too large may be displayed when you have virtual InfoProviders (for example). For more information, see Note 1267220.
When queries have detail level = #0′ for the BI statistics in transaction RSDDSTAT, OLAP statistics data is no longer transferred to the InfoProviders of the technical content (0TCT_CA1, 0TCT_C01 and 0TCT_C02). This error occurs in connection with an optimization that was made to the technical content DataSources in Support Package 19 (see below for more details, Note 1237091) and can be corrected by implementing Note 1250182.

Errors corrected in this Support Package:

End user technology errors corrected
OLAP technology errors corrected
Warehouse Management errors corrected
Delivered transformations are deleted and can no longer be transferred from Content. The active and saved versions of the transformation are not affected.

Enhancements delivered with this Support Package:
End user technology enhancements
The use of hierarchy aggregates for MultiProvider queries is improved. For more information, see Note 1173070.
OLAP technology enhancements

Warehouse Management enhancements
The query runtime statistics in the BI Administration Cockpit/technical content have been improved by an optimization of the underlying DataSources. For more information, see Note 1237091.