SAP Netweaver Business Intelligence BI / BW

Symptom

Support Package 22 for BI Release 7.00
Other terms

SAPBINEWS, Support Packages for 7.00, BW 7.00, BW Patches, BI, BI 7.00, SAPBINews, NW7.00, NetWeaver 7.00, 7.0

Solution

This note contains the SAPBINews for Support Package 22 of BI Release 7.00. Here, you will find a list of all notes describing corrections or enhancements in Support Package 22. This note will be updated when other notes are added.
Note that BI 7.0 ABAP Support Package 21 is a part of SAP NW 7.0 Support Package Stack 20.
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:This Support Package corrects the errors below.Enhancements delivered with this Support Package

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 objects are displayed in the SAP namespace in the “Transportable Objects” section, you are not allowed to import any Support Packages. 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 todelete objects from the transport requestbecause this may destroy the imported Support Package. Note 822379 describes the correct procedure.

Obtain information about the most recent SAP Notes that you should take into account and, if necessary, implement, after you import Support Package 22. In the search function in the notes database or on SAP Service Marketplace, use search term: ‘SAPKW70022′, and under ‘Search Criteria–> Extended Search Criteria–> Priority’, select: “HotNews” and “Correction with high priority”. You can also restrict the search to a specific component by entering the relevant specifications in the ‘Application area’ field, for example BW-WHM*.
When you import a Support Package, syntax errors may occur for technical reasons. This is because notes that were already installed have been partly overwritten. In this case, you must install the inconsistent notes using transaction SNOTE. You can then continue with Support Package Manager (SPAM) processing. After you have completely imported a Support Package queue, transaction SNOTE should not display any inconsistent notes. If there are inconsistent notes in your system, it will not be able to function correctly.

Import the SNOTE corrections first and read the composite SAP Note 875986, which contains important notes about Note Assistant.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:

Only DB2 for z/OS Version 8: Aggregate creation terminates with SQL error -440. Implement the correction instructions contained in Note 1320150.X299 BRAIN in CL_RSR_RRK0_MULTIPROV_BUFH; _GET_PROVBIT-01- Refer to Note 1372208Extractor 0TCT_DSA1 does not write correct object names. For more information, see Note 1374627.Follow-on correction 1358049 – Refer to Note 1381638An MDX query runs for a very long time, however, it selects only a small amount of data. For more information, see Note 1383354.

Errors corrected in this Support Package:
Decimal place problem during certain exception aggregations For more information, see Note 1339773.

X299 BRAIN in CL_RSR_RRK0_MULTIPROV_BUFH; _GET_PROVBIT-01- Refer to Note 1372208.
Enhancements delivered with this Support Package