Current Position:Home > BW SUPPORT PACK 13,14,15

BW SUPPORT PACK 13,14,15

Update:11-30Source: network consolidation
Advertisement
hi all,
can any one give some info and the link where I can find information about BW support pack 13, 14 ,15

The Best Answer

Advertisement
hi ajay,
i think these oss notes should sufficient, they contain info what error corrected, possible new errors, new features added in the support packages. do you need other info ?
Symptom
Support Package 13 for BW Release 3.5.
Other terms
SAPBWNEWS, Support Packages for 3.5, BW 3.5, BW 3.50, BW Patches
Solution
This note contains the SAPBWNews for Support Package 13 for BW Release 3.5. This note lists all the notes that describe the corrections or enhancements contained in Support Package 13 (SAPKW35013). This note is updated as soon as other notes are added.
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 Package
Errors that may occur after you import the Support Package
For general information:
This Support Package corrects the following errors
Enhancements contained in this Support Package
Support Package 13 for BW 3.5 corresponds to the technological status of Support Packages 28 for BW 3.0B (SAPBWNews 783170) and 22 BW 3.1 Content (SAPBWNews 783252).
Also see the following release and information notes
Support Package 13 SAP_UDI 350 Note 765119
Factors you must take into account when you import the Support Package:
Note that Support Package 4 is required as of NetWeaver Support Package Stack 14, that is, BW Server Support Package 14 PI_BASIS 2005. For information about upgrading to PI_BASIS 2005, refer to Note 821148.
Errors that may occur after you import the Support Package:
Querys on MultiCubes in read mode A. For information about this, read Note 896066.
Data is missing in individual aggregates.
The error is not corrected by reconstructing the aggregate. For information about this, read Note 898508.
When you display a note in the Note Assistant, the following error may occur: 'Output device A000 is not defined'. For more information, see Note 868905.
Under certain circumstances, the MultiProvider F4 help does not use aggregates that have also been used during the query execution. For more information, see Note 870557.
When you execute a MultiProvider query, a termination may occur. For more information, see Note 870505.
When you go from one query to another query or to a Web template, the system fills value variables for compound characteristics, which you can also change during query navigation, with the initial value ("#"). For more information, see Note 867616.
In certain situations when you execute a query, a termination (GETWA_NOT_ASSIGNED in SAPSRRK0 field symbol <L_S_SNID>) may occur or data may be missing from columns or structural elements. For more information, see Notes 851086 and 848340.
Some columns or structure items may remain empty in a query. For more information, see Note 863745.
When you check a query, the system may issue error message Brain A 039 (telling you that node &3 &4 does not exist in hierarchy &2 for the InfoObject &1), although the node exists and you can execute the query. For more information, see Note 855258.
A query with an exclude in the dynamic filter may not display any data under certain conditions. For more information, see Note 856495.
In some very exceptional cases, a query may terminate with error message X299(BRAIN) System error in program SAPLRRKH and form SELDER_INTERSECT_BUF-01. For more information, see Note 851754.
You can execute a query that does not use any key figures even if you do not have the necessary authorizations. For more information, see Note 856144.
List of notes:
868905
870557
870505
867616
851086
848340
855258
856495
851754
856144
This Support Package corrects the following errors:
Corrections in the end user technology area:
When you called the filter dialog in the BEx Broadcaster and the ad-hoc Query Designer, the system issued error message CX_SY_REF_IS_INITIAL. For more information, see Note 857393.
Corrections in the OLAP technology area:
In a query, some columns or structural elements remained empty. For more information, see Note 848340.
You were no longer able to create authorizations (profiles) in Transaction RSSM if the user name did not contain a period. The system ignored the authorization assignment using Transaction PFCG (roles) and the generation from ODS. For more information, see Note 849194.
When you executed a query, the ETWA_NOT_ASSIGNED runtime error occurred in the SAPSRRK0 program in the APPEND_KHANDLE_1 form; field symbol <L_S_SNID>. For more information, see Note 851086.
When you executed a query, it terminated with the X299(BRAIN) error message telling you that there was a system error in the SAPLRRKH program and the SELDER_INTERSECT_BUF-01- form. For more information, see Note 851754.
A query that contains both a fixed and dynamic restriction for a characteristic and that is evaluated on a remote cube may terminate (program SAPLRRK0; form CHECK_NAV_INIT_NEW-03- ). For more information, see Note 849969.
Corrections in the Warehouse Management area:
After you imported Support Package 12, it took a very long time to create and delete InfoPackages in a content creating BW system because Note 844739 delivered corrections for writing shadow InfoPackages, and these corrections may run for a relatively long time in several source systems that are connected to BW as well as several existing shadow InfoPackages. For more information, see Note 847030.
When you loaded data, data sometimes disappeared. Refer to Note 849857 for further information.
If you executed a where-used list for an InfoObject in the D version, a termination sometimes occurred. For more information, see Note 844007.
When you deleted master data, a termination sometimes occurred. For more information, see Note 856546.
Enhancements delivered with this Support Package:
Also refer to the Documentation Enhancements on the SAP Service Marketplace (http://service.sap.com/bi --> Documentation --> SAP BW 3.5 Documentation Enhancements), which describe the enhancements delivered with this Support Package.
Improvements in the OLAP technology area:
General performance improvements for OLAP. For more information, see Note 825396.
The performance of MultiCubes has been improved. For more information, see Notes 869487 and 903559.
Symptom
Support Package 14 for BW Release 3.5
Other terms
SAPBWNEWS, Support Packages for 3.5, BW 3.5, BW 3.50, BW Patches
Solution
This note contains the SAPBWNews for Support Package 14 for BW Release 3.5. It contains a list of all notes that describe the corrections or enhancements in Support Package 14 (SAPKW35014). The note will be updated as soon as other notes are added.
The information is divided into the following areas:
Manual activities that may be necessary:
Factors you must take into account when you import the Support Package
Errors that may occur after you import the Support Package
For general information:
This Support Package corrects the following errors
Enhancements delivered with this Support Package
Support Package 14 for BW 3.5 corresponds to the technological status of Support Packages 29 for BW 3.0B (SAPBWNews 783251) and 23 BW 3.1 Content (SAPBWNews 783253).
Also refer to the following release and information note:
SP14 SAP_UDI 350 Note 839096
Factors you must take into account when you import the Support Package:
Note that as of NetWeaver Support Package Stack 14, that is BW Server Support Package 14, you require PI_BASIS 2005 Support Package 4. For information about upgrading to PI_BASIS 2005, see Note 821148.
Note 855424 leads to syntax errors during the generation of update rules. Read the note for more information.
Errors that may occur after you import the Support Package:
A query displays additional rows or columns. For more information, see Note 901097.
Querys on MultiCubes in read mode A. For more information, see Note 896066.
The update from the PSA using the 'Update' indicator in the scheduler no longer works for normal master data that is not flexible and text DataSources that were updated using 'PSA only' - Reason: The problem is caused by the correction that is contained in Note 889160, Note 905105 corrects the problem.
A syntax error occurs in class CL_RSMD_CONVERSION, method DROP_TMPTABLES. For more information, see Note 905168.
F4 and authorization: SQL error in SAPLRSDM_F4. For more information, see Note 907337.
This Support Package corrects the following errors:
Corrections in the end user technology area:
When you go from a query to another query or to a Web template, value variables on compound characteristics, which can be changed simultaneously during the query navigation, are filled with the initial value ("#"). For more information, see Note 867616.
Corrections in the OLAP technology area:
In certain cases, when you execute a query, a termination (GETWA_NOT_ASSIGNED in the SAPSRRK0 <L_S_SNID> field symbol) occurs or data is missing in columns or structural components. For more information, see Notes 851086 and 848340.
In certain cases, when you execute a query, a termination occurs and the system issues message X299(BRAIN) 'System error: Program SAPLRRKH; form SELDER_INTERSECT_BUF-01-'. For more information, see Note 851754.
You can execute a query that does not use any key figures at all even if you do not have the necessary authorizations. For more information, see Note 856144.
When you check a query, the system may issue error message Brain A 039 (Node &3 &4 is not in hierarchy &2 for InfoObject &1) even though the node exists and you can execute the query. For more information, see Note 855258.
In certain cases, a query with an exclude in the dynamic filter may not display any data. For more information, see Note 856495.
In certain cases, the Multiprovider F4 help does not use aggregates that were also used during the query execution. For more information, see Note 870557.
A termination may occur when you execute a MultiProvider query. For more information, see Note 870505.
Corrections in the Warehouse Management area:
The UNCAUGHT_EXCEPTION runtime error occurs during the upload. For more information, see Note 855424.
Enhancements delivered with this Support Package:
Also refer to the Documentation Enhancements on the SAP Service Marketplace (http://service.sap.com/bi --> Documentation --> SAP BW 3.5 Documentation Enhancements), which describe the enhancements that are delivered with this Support Package.
Improvements in the OLAP technology area:
General performance improvements for OLAP. For more information, see Note 825396.
The runtime in the REMOVE_SELDR_0INFOPROV_NEW form is very long. For more information, see Note 887801.
Unnecessary reading of partprovider. For more information, see Note 885733.
The performance in form SAPLRRK0; loc_rechnen has been improved. For more information, see Note 884482.
Problems occur with hierarchy selections in MultiProviders. For more information, see Note 879290.
Query runtime if there are several nested formulas. For more information, see Note 872904.
Symptom
Support Package 15 for BW Release 3.5
Other terms
SAPBWNEWS, Support Packages for 3.5, BW 3.5, BW 3.50, BW patches
Solution
This note contains the SAPBWNews for Support Package 15 for BW Release 3.5. It contains a list of all notes that describe the corrections or enhancements in Support Package 15 (SAPKW35015). The note will be updated as soon as other notes are added.
The information is divided into the following areas:
Manual activities that may be necessary:
Factors you must take into account when you import the Support Package
Errors that may occur after you import the Support Package
  For general information:
This Support Package corrects the following errors
Enhancements delivered with this Support Package
Support Package 15 for BW 3.5 corresponds to the technological status of Support Packages 30 for BW 3.0B (SAPBWNews 872271) and 24 BW 3.1 Content (SAPBWNews 872273).
Also refer to the following release and information note:
Support Package 15 SAP_UDI 350 Note 839097
Factors you must take into account when you import the Support Package:
Errors that may occur after you import the Support Package:
The query displays more rows. For more information about this, see Note 901097.
This Support Package corrects the following errors:
Enhancements delivered with this Support Package:
Also refer to the Documentation Enhancements on the SAP Service Marketplace (http://service.sap.com/bi   > Documentation   > SAP BW 3.5 Documentation Enhancements), which describe the enhancements that are delivered with this Support Package.
Improvements in the OLAP technology area:
General performance improvements for OLAP. For more information, see Note 825396.
Performance improvements when you are searching for filter values. For more information, see Note 900728.
Performance improvements when you start the query. For more information, see Note 905375.
Improvements in the Warehouse Management area:
The system also issues error messages during parallel reading. For more information, see Note 905083.
  • Support Pack error in SPAM Update:10-11

    Hi I am importing a group of Support Packs into our DEV environment to bring the landscape uptodate, we are running NW04 on Windows 2003 64 bit & SQL Server 2000, I've updated to the latest SPAM and Kernel before the Support Packs. When importing in

  • Error in JSPM Support Pack update Update:10-11

    Hi, i am in the process of doing java support packs form level 9 to 14. I am doing 3 at a time After the sap-jee support pack got deployed the server0 for j2ee is not starting. Pls hlep The following is the log of disp_server0 trc file: "F:\usr\sap\B

  • Support Pack upgrade error in Import Phase Update:10-11

    Hello, Currently I am upgrading SCM system with Support pack level 12 to 20 . When i am applying Basis 12 to 20. I got an error in Import_Proper phase. Could you please help me on this? I tried and still searching solution for this..But no luck... Os

  • BSI Tax Factory Upgrade:HR Support packs Update:10-11

    Hi All, We are starting with upgrade of BSI tax Factory from 8.0 to 9.0. And as per SAP main note '1469858' for upgrade, the support pack required is 'HRSP61' but we currently have 'HRSP59'. Also, CLC 61 was applied for 2010 year end activities. So,

  • SB Audigy Series Support Pack 5.3 (02/24/2015) Update:10-11

    This software/driver pack is unofficial, not supported by Creative Labs. Use it at your own risk. Supports any model of the following Sound Blaster cards (based on Emu10kx DSP): - Audigy - Audigy 2 - Audigy 2 ZS - Audigy 4 - Audigy 5/RX For Audigy SE

  • Issues with POWL action buttons and row selection after Support Packs Update:10-11

    We recently applied ECC 603 Support Stack 16 to our environment and are having problems with some SAP standard POWL lists (example is KYKOP-OPS-MM-PO-W: Purchase Orders for Goods Receipt).  In fact all of the POWL lists that we are using are behaving

  • Open data extraction orders -  Applying Support Packs Update:10-11

    Dear All, I have done the IDES 4.6C SR2 installation. While updating the support packs, i get the message saying CHECK_REQUIREMENTS phase. Open data extraction orders There are still open data extraction orders in the system process these before the

  • SB Audigy Series Support Pack 3.1 (OUTDATED) Update:10-11

    <p align="center">[color="#ff0000"]This software/driver pack is unofficial, not supported by Creative Labs. <p align="center">[color="#ff0000"]Use it at your own risk. Supports any model of the following

  • Error during application of scm 7.0 support pack Update:10-11

    While applying support pack to our SCM 7.0 system (New Installation), We encountered a SPAM error in xpra_execution phase, due to automatic termination of job RDDEXECL scheduled by user id DDIC on client 000. The details of the error are: Message id:

  • Support Packs in Solution manager Update:10-11

    Hi, I have a query, when I am going to select patches through maintenance optimizer for solution manager I can see the source and target stack level at SMP and when I am putting the source stack(17) and the target stack as latest, solution manager 7.