SAP Note 662441 Solution Manager: SAP Notes for Support Packages

Note Language: English
29.08.2008

Version: 156

Validity:

Valid Since

Summary
Symptom
You want to import individual Support Packages or a Support Package stack for the SAP Solution Manager, and want to check first if there are already important notes for these Support Packages or this stack.

Other terms
Software component ST ST-SER ST-PI ST-SUP TMWFLOW ST-ICO SAP_BASIS SAP_ABA BBPCRM CPRXRPM Description Solution Manager Tool Solution Manager Service Tools Solution Tools Plug-In Solution Manager Service Desk Change Request Management Solution Manager Implementation Content SAP Basis Component SAP Application Basis BBP / CRM cProjects and others

Reason and Prerequisites Solution
This composite note 662441 refers to both selected notes and information that is relevant to importing Support Packages for the software components listed above into a SAP Solution Manager system. Herein referenced notes are recommended to be implemented because they deal often with possible short dumps, possible runtime errors, possible data inconsistencies, or even possible data loss, etc. Target group for this note are users who implement Support Packages in a Solution Manager system or system administrators of these systems. How to understand and work with composite note 662441 ? o You can either read this note entirely, or search for terms that you have found in transaction SPAM, such as technical names of the Support Packages you want to import, or the names of the software components in question (search terms can appear more than once in this note). For the software components 'SAP_BASIS', 'SAP_ABA' and 'BBPCRM', only the notes that are directly related to the SAP Solution Manager function are mentioned. These notes are listed below by SAP Solution Manager software component. The notes are selected shortly after the Support Packages released. Notes written after this time are only included are important, i.e. if they correspond to the above given categories. This is not a complete list of all notes that implemented for individual Support Packages. are if they error can be

o

o

06.09.2010

Page 1 of

21

SAP Note 662441 Solution Manager: SAP Notes for Support Packages
o The notes listed here are usually not relevant for subsequent Support Packages. However, in some cases, you should check if a note has been revised, and a new version is once again valid. This composite note does not list notes that refer to installation packages and upgrade packages. These are dealt with in the implementation guide for the release in question (see the SAP Service Marketplace, quick link "/solutionmanager", area "Installation Guides" or SAP Service Marketplace, quick link "/instguides", area "SAP Components", "SAP Solution Manager").

o

Are there similar scenario related composite notes ? o For certain usage scenarios of SAP Solution Manager there are additional composite notes which indicates corrections particularly relevant for these scenarios: SAP Note 1024932 949220 896632 1059350 949292 949293 907768 770693 930747 1061383 1010428 o Usage Scenario Maintenance Optimizer Implementation Testworkbench Quality Center Service Desk Solution Monitoring Change Request Management (Release 7.0) Change Request Management (Release 3.2) Delivery of SAP Services SM Diagnostics (Release 7.0, from SP 13) SM Diagnostics (Release 7.0, prior SP 12)

These additional notes focus on a wider range of corrections than note 662441. They refer to a greater extent to functional correctness of the corresponding scenario. Therefore also the target group for these notes is extended by for example - project leads or scenarios responsibles. There is one further composite note with optional cross-secenario information: 948871.

o

o

Where to find information on changes for system configuration ? o Note 903274 and its attachment indicate the IMG activities that have changed with a new support package. This would help in deciding if your system confiuration would need to be changed with the new support package.

Notes related to Support Packages for SAP Solution Manager software components:

SAP Solution Manager 7.0 (cross-component notes)
o Support Package Stack 17 (08/2008) 06.09.2010

To be able to send Service Desk messages to SAP please
Page 2 of 21

if this has not been done already. You can find installation and upgrade packages on the SAP Service Marketplace under the path: http://service. o Support Package Stack 13 (10/2007) For software component CPRXRPM there is a Conflict Resolution Transport (CRT) that needs to be implemented together with SP 13 of SAP_ABA 700. please be aware that this will take some time. you must upgrade software component ST-SER to the current release using transaction SAINT. search term "SAPKITLOLB". SAPKITLOO1 should be included.sap. Before this upgrade you need to implement note 1042866 (see below at SAPKITL422 for more details). The note implementation triggers the generation of many repository objects. search term "SAPKITLONB".com/swdc. Since a CRT can not be included in a support package stack you need to download CRT "CPRXRPM 400: CRT for SAPKA70013" (SAPK-400C4INCPRXRPM) separately before you download the stack.09.sap. o Support Package Stack 15 (01/2008) Stack 15 has been released. o Support Package Collection 07 and Support Package Stack 06 (08/2006) With note correction 973995 Service Desk messages can be again Page 3 of 21 06. - o Support Package Stack 12 (06/2007) Before you can import all Support Packages from Stack 12. The note correction is valid for SAP_ABA 700 SP 14 (SAPKA70014) which is required by SP15 and part of the stack. which is required by SP 13 of SAT 400 (SAPKITL423). Your system will not be downgraded. You can find installation and upgrade packages on the SAP Service Marketplace under the path: http://service. Search for all Categories. Implement note 1128026 to your Solution Manager system after having loaded ST 400 SP15 (SAPKITL425). Search for all Categories. The current ST-SER release is: ST-SER 700_2008_1 (SAPKITLONB). The current ST-SER release is: ST-SER 700_2007_1 (SAPKITLOLB).SAP Note 662441 Solution Manager: SAP Notes for Support Packages implement note 1165980 after you have implemented SP 16 of SAP_ABA (SAPKA70016). and load at the same time SP 4 of ST-SER 700_2007_1 (SAPKITLOM4). Before you can import all Support Packages from Stack 15. if this has not been done already. If you load SP 13 of SAP_ABA 700 (SAPKA70013). If you have already installed SAPKITLOM6 into your system you will receive a waring during import of SAPKITLONB: Equivalence SP level not reached. you must upgrade software component ST-SER to the current release using transaction SAINT. You can ignore this warning. Please notice also note 1042866 which is mentioned below two time.2010 . This correction is necessary to work within service sessions.com/swdc. you need to implement note 1075012.

09. and Issue Management note 946961 has to be implemented to avoid a short dump while creating or changing messages. This correction is also indirectly valid for older ST 400 Support Packages (SAPKITL415. You can ignore this generation error. o Support Package Stack 02 (02/2006) With SAP_BASIS 700 Support Package 06 (SAPKB70006). SAPKITL414. The correction is valid for CRM 5. Change Request Management.2010 . o Support Package Collection 03 (03/2006) For Change Request Management note 909236 prevents possible data inconsistency. o Support Package Stack 06 (08/2006) and prior Note 954496 delivers a correction for Post Processing Framework (PPF) which avoids a runtime error.0 Support Package 02 (SAPKU50002) which is required by ST400 SP02 (SAPKITL412).SAP Note 662441 Solution Manager: SAP Notes for Support Packages created correctly after having ST 400 SP07 (SAPKITL417) loaded or having Note 963002 implemented. SAPKITL411). Support Package SAPKU50003 is required by ST400 SP03 (SAPKITL413). The correction is valid for CRM 5. This note is valid for SAP_BASIS 700 Support Package 08 (SAPKB70008) which is required by ST 400 SP06 (SAPKITL416). You can identify the generation error by the keywords "CL_DPR_SC_SERVICES" and "/RPM/CL_BUCKET_O".0 Support Package 05 (SAPKU50005) which is required by ST 400 SP06 (SAPKITL416) which again is required by ST 400 SP07 (SAPKITL417). The correction is valid for SAP_ABA 700 Support Package 08 (SAPKA70008) which is required by ST 400 SP06 (SAPKITL416).0 Support Package 04 (SAPKU50004) which is required by ST400 SP05 (SAPKITL415). Note 948129 prevents a short-dump that can occur while calling directly or indirectly the Service Session Workbench. Support Package SAPKU50002 is required by ST400 SP 02 (SAPKITL412) Page 4 of 21 - - 06. SAPKITL413. deletions were delivered that lead to generation errors when you import CPRXRPM 400 SP02 (SAPK-40002INCPRXRPM) in Transaction SPAM. Note 725658 prevents a possible short dump. SAPKITL412. The correction is valid for CRM 5. Implementation of note 964651 prevents occurance of possible inconsistencies while creating Servcie Desk Messages. Correction is valid for SAP_BASIS 700 Support Package 09 (SAPKA70009) which is required by SP07. - o Support Package Collection 05 (05/2006) For Service Desk.0 Support Package 03 (SAPKU50003). if you use SPAM to activate the generation.0 SP02 (SAPKU50002) into the Solution Manager. Note 905469 provides a language package which should be re-imported after importing CRM 5. This correction is valid for CRM 5. or issues. change requests.

Delete your SPAM-QUEUE by pressing the Display/Define button within SPAM. Select ST-SER 700_2008_1 or higher and press Continue button All neccessary component packages will automatically be included into a valid SAINT-queue o ST 400 SP15 (SAPKITL425) With SP15 (SAPKITL425) SAP strictly recommends to upgrade your ST-SER to the release 700_2007_1 or higher.2010 .0 (Software component ST 400) o ST 400 SP16 (SAPKITL426) With SP16 (SAPKITL426) SAP strictly recommends to upgrade your ST-SER tothe release 700_2008_1 or higher. Call transaction SAINT and press Start button. SAP Solution Manager 7. If you try to patch your system via SPAM and your ST-SER release is 700_2007_1 or less you will receive one of the following information within SPAM during phase ADDON_CONFLICTS_?: a) Conflicts Between Add-On ST-SER 700_2005_2 and Support Packages SAPKITL426 Include CRT b) Conflicts Between Add-On ST-SER 700_2006_1 and Support Packages SAPKITL426 Include CRT c) Conflicts Between Add-On ST-SER 700_2006_2 and Support Packages SAPKITL426 Include CRT c) Conflicts Between Add-On ST-SER 700_2007_1 and Support Packages SAPKITL426 Include CRT Please be aware there is no physical Conflict Resolution Transport (CRT) available to solve this conflict (it is not planned to provide such a CRT). If you try to patch your system via SPAM and your ST-SER release is 700_2006_1 or less you will receive one of the following Page 5 of 21 06. 2.0. 3. also SAPKITL40G). You have to patch your system via SAINT not via SPAM: 1. The primary Support Package is Support Package 01 from ST 400 (SAPKITL411.09. Therefore use transaction SAINT instead of transaction SPAM to patch your system to SAP Solution Manager 7. Download all ST-SER Delta-Upgrade packages from the Software Download Center into your EPS-Inbox. 4. Therefore use transaction SAINT instead of transaction SPAM to patch your system to SAP Solution Manager 7.0 Stack 15 (01/2008).SAP Note 662441 Solution Manager: SAP Notes for Support Packages o Support Package Collection 01 (12/2005) Note 908186 provides Ramp-Up customers with an overview of selected notes relating to the target configuration of the upgrade to the new release.

09.com/solutionmanager" -> "Medie Library" -> "Technical Papers" -> "Development News SAP Solution Manager SPS15". The workcenters are released for Page 6 of 21 - 06. Solution Landscape & Operation Setup. transaction SPRO).SAR - - Notes 1128453 This note summarizes some corrections with regard to the Implementation Guide in the Solution Manager system (SAP Reference IMG. 4. You have to patch your system via SAINT not via SPAM: 1. and System Landscape Management.2010 . For details please see the Development News for SP15 in SAP Service Marketplace at link "http://service. With SP15 (SAPKITL425) so called workcenters are introduced to SAP Solution Manager. Do consider this note in case you start configuration activities based on SP 15. Job Scheduling Management. Service Delivery.SAR into your <DIR_TRANS> directory and extract it with SAPCAR -xvf AITL412. Delete your SPAM-QUEUE by pressing the Display/Define button within SPAM.sap. Change Lifecycle Management.SAP Note 662441 Solution Manager: SAP Notes for Support Packages information within SPAM during phase ADDON_CONFLICTS_?: a) Conflicts Between Add-On ST-SER 700_2005_2 and Support Packages SAPKITL425 Include CRT b) Conflicts Between Add-On ST-SER 700_2006_1 and Support Packages SAPKITL425 Include CRT c) Conflicts Between Add-On ST-SER 700_2006_2 and Support Packages SAPKITL425 Include CRT Please be aware there is no physical Conflict Resolution Transport (CRT) available to solve this conflict (it is not planned to provide such a CRT). Call transaction SAINT and press Start button. Download all ST-SER Delta-Upgrade packages from the Software Download Center into your EPS-Inbox. Currently only these workcenters are released to customers with SP15: Implementation & Upgrade. 2. 3. Select ST-SER 700_2007_1 or higher and press Continue button All neccessary component packages will automatically be included into a valid SAINT-queue Applying SAPKITL425 together with SAPKITL422 within 1 SAINT/SPAM queue To avoid following error message during main import: duplicate key error during insert into table AGSTWB_RSTAT_VAL occured download the attached Allowfile AITL422. System Monitoring. System Administration. Incident Management.

1138049 (Issue Management) Please implement these notes in case you are using transaction SOLMAN_ISSUE_MGMT (additional key word Collaboration Platform). Note 1140822 After implementing SP15 (SAPKITL425).2010 . Notes 1137739. (Scenario specific note 949293 lists more workcenter relevant functional corrections for the Solution Monitoring scenario.0 Support Package Level. The note describes deviations and enhancements to the IMG and KW documentation. who likes to import ERP Enhancement Packages using the Maintenance Optimizer. Notes 1137338 (Expertise on Demand) Please implement this note in case you are using the Expertise on Demand functionality of Issue Management.09. and 1137683 (Maintenance Optimizer): Implement note 1130172 after having loaded SP15 (SAPKITL425). This causes error message AI_SC_EN097 "SAP customer number for installation number &1 not known". The note lists required correction notes to be implemented in addition to a certain Solution Manager 7. Notes 1138350 (Change Request Management) Note 1138350 is an urgent correction for the Change Request Management scenario. the functionality for managing several SAP customer numbers is active. The Page 7 of 21 06. Implement note 1140822. Notice prerequisites describes in this notes. 1122966. Note 1128026 (Service Level Reporting) Implementing this note prevents a run-time error for SL reporting. Note 1136916 (Workcenter) With implementation of note 1136916 on top of SP15 (SAPKITL425) solutions are created from within a workcenter in the logon language. This transaction is part of the user menu of role SAP_SMWORK_BASIC. - - - - - o ST 400 SP14 (SAPKITL424) Note 1106236 Implementation of Note 1106236 is required if you use the Change Request Management of the Solution Manager. to deactivate this functionality. These additional notes correct problems that are concidered less server. 1138046.SAP Note 662441 Solution Manager: SAP Notes for Support Packages being called by transaction SOLMAN_WORKCENTER. the three other entries of this user menu are not released for being used. Note 1137683 provides customers using Maintenance Optimizer with an overview of selected notes relating to the Configuration and Usage of Software Lifecycle Manager. Note 1122966 is relevant for every customer.) Notes 1130172.

o ST 400 SP12 (SAPKITL422) Note 1077050 Before importing SP12 to your Solution Manager system please check whether or not you would import the updated EPS file for SP12 (EPS file name: CSR0120031469_0027444. SAPKITL420) Note 1012979 Page 8 of 21 06. - - - - o ST 400 SP11 (SAPKITL421) Note 1042815 This note correction prevents writing SMSY data back to the System Landscape Directory (SLD).2007. This note correction prevents an error that might occur while reading these settings.07. o ST 400 SP13 (SAPKITL423) Note 1084173 With SP13 the background job scheduling for Central System Administration has been changed. Importing an older EPS file for SP12 together with previous Support Packages for ST 400 might result in errors during import. the termination #Syntax error in program "RDSVASASPLI_CBP____________062" might occur when opening #Business Process Details# in the Solution Directory. o ST 400 SP09 to SP10 (SAPKITL419. please implement the coding correction of SAP Note 1042866 if you are on ST-SER 700_2006_2 and before implementing ST-SER 700_2007_1. Note 1059271 From several scenarios of SAP Solution Manager the Global Settings from Transaction SOLUTION_MANAGER are read.09.PAT) which is available for download since 23.SAP Note 662441 Solution Manager: SAP Notes for Support Packages condition check regarding successfull export of transport requests has to be corrected by this note after you've imported SP14. Please process the activities described in SAP note 1084173 after SP13 implementation. To avoid this dump. Note 1042866 If ST 400 SP12 (SAPKITL422) or higher has been installed. Note 1067602 The interface between the Maintenance Optimizer and SAP Service Marketplace has to be extended by implementing SAP Note 1067602. If you are about to import a different EPS file for SP12 than this updated one please see Note 1077050 which gives an overview on how to proceed. Note 1052319 This correction prevents a short dump for System Monitoring.2010 . This extension is necessary for calculating which Support Packages have to be downloaded and for generating a stack XML file for installing Enhancement Packages.

Note 1008717 Solution Manager features that use HTML Viewer Control (such as Issue Management and Maintenance Optimizer) won't work without this note. when you save at this point the original Check names will be overwritten. You would need to apply note 1012979 only in case you have implemented note 987122 with SP06. SP07. o ST 400 SP06 to SP10 (SAPKITL416. SAPKITL417. o ST 400 SP03 to SP05 (SAPKITL413. SAPKITL418) Note 1012979 This note prevents a possible data inconsistency between SMSY data and solutions. o ST 400 SP05 (SAPKITL415) Note 946605 Issue Management requires implementation of this note to avoid a short dump that occurs during issue status refresh. o ST 400 SP06 (SAPKITL416) Note 966398 This note correction prevents a short dump that could occure while you perform the "Initial Data Transfer for IBase" in transaction SOLUTION_MANAGER. SAPKITL418. SAPKITL420) Note 1015744 This note correction prevents the loss of settings for System Monitoring which might occur under specific circumstances: in this case for all Checks the same name will be displayed. if SAP_BASIS 700 note 975872 or SP10 (SAPKB70010) had been implemented and SAP GUI 640 Patch Level 22 is being used. Note 1011376 Customers using Service Desk for Service Providers and action profile AI_SDK_STANDARD need to implement this note to be able to create and save messages. or SP08.2010 .SAPKITL414. Note 1006711 Without this note data loss is possible if a system is not available during data refresh in transaction SMSY.SAP Note 662441 Solution Manager: SAP Notes for Support Packages This note prevents a possible data inconsistency between SMSY data and solutions. o ST 400 SP09 (SAPKITL419) Note 1005323 This note prevents a run time error in job "SM:CSA SESSION REFRESH". and changes to the settings for System Monitoring will not be taken over. SAPKITL415) Page 9 of 21 06. SAPKITL419. - - - o ST 400 SP06 to SP08 (SAPKITL416. SAPKITL417.09.

SAPKITL413) Note 929928 Without this correction the Issue contexts get lost for Issue from Solution Manager 3. 910177 These Notes provide corrections for the use of solutions. SAP Solution Manager 7. top issues.0. an error during test import will occur: Function DSWP_BPMO_STXT_GET (DSWP_BPM_FUNH 04) does not fit into the existing function group ((DSWP_BPMO 12)) Ignore this error by using SAINT functionality in menu "Extras" -> "Ignore test import errors" 06.SAP Note 662441 Solution Manager: SAP Notes for Support Packages Note 948644 This note prevents a run time error within the Solution Directory. - - SAP Solution Manager 7.2010 Page 10 of 21 . expertise on demand.0 (Software component ST-SER) o ST-SER 700_2007_1 SP01 (SAPKITLOM1) If you import Supportpackage SAPLITLOM1 and Delta Upgrade Pacakge SAPKITLOLB together within 1 SAINT queue. This note delivers a correction for this optimization. o ST 400 SP01 to SP03 (SAPKITL411. Notes 919790. issues. - o ST 400 SP02 (SAPKITL412) Note 917896 This note prevents a short dump. 912618. and the Business Process Monitoring. The note must be imported before the migration of the solutions from Release 3.1 to 7.2 after upgrade. Note 906340 SP02 provided a performance improvement when working with solutions. Note 928985 Implement this note to prevent a runtime error while creation of Service Desk messages.0 (Software component ST-ICO) o ST-ICO 150 SP10 (SAPK-1507AINSTPL) The installation of this package requires minimum R3trans version from 2007/06/11. SAPKITL412. o ST 400 SP03 (SAPKITL413) Note 919790 This note has an additional correction for SP03.09.

This correction is also indirectly valid for older ST 320 Support Packages (SAPKITL322. SAPKITL321). This correction is valid for CRM 3. The note can be implemented with Support Package 12 from BBPCRM 310 (SAPKU31012). SAPKITLC54. Change Request Management (Support Package 11 for TMWFLOW 320. SAPKITL314. reissued EPS file. SAPKITL317. Implementation of note 964651 prevents occurance of possible inconsistencies while creating Servcie Desk Messages. SAPKITL321.1 Support Package 12 (SAPKU31012) which is required (indirectly) by ST-SUP 320 SP13 (SAPKITLC53) which again is required by ST-SUP 320 SP14 (SAPKITLC54). o Support Package Stack 10 (10/2005) This stack contains Support Package 10 (SAPKITL320) for ST 320. SAPKITL311). Correction is valid for SAP_BASIS 620 Support Package 60 (SAPKA62060) which is required by SP14.2 (cross-component notes) o Support Package Stack 15 (12/2006) and prior Implementation of note 964651 prevents occurance of possible inconsistencies while creating Servcie Desk Messages.1 Support Package 12 and 13 (SAPKU31012. This affects Service Desk (Support Package 11 for ST-SUP 320. The correction is also valid for SAP_ABA 620 Support Package 59 (SAPKA62059) which is required by ST 320 SP13 (SAPKITL323). SAPKITLC51). SAPKITL318. o Support Package Collection 11 (12/2005) Note 902804 makes it possible once again to save texts from CRM transactions. SAPKITL316. SP14. SAPKITL313. which. - o Support Package Stack 13 (06/2006) and prior Note 948129 prevents a short-dump that can occur while calling directly or indirectly the Service Session Workbench. SAPKU31013) which are required by ST-SUP 320 SP13. in its first version. SAPKITL315.09. Refer to Note 888413 for the EPS file name of the corrected. This correction is valid for CRM 3. o Support Package Collection 07 and Support Package Stack 13 (06/2006) With note correction 973995 Service Desk messages can be again created correctly after having ST 320 SP14 (SAPKITL324) loaded or having Note 963002 implemented. SAPKITL320.SAP Note 662441 Solution Manager: SAP Notes for Support Packages SAP Solution Manager 3. can lead to data loss during the import. SAPKITLC55).2010 . o Support Package Stack 08 (06/2005) Before you import Support Packages from Stack 08. SAPK-32011INTMWFLOW) and issues (Support Package 11 for ST 320. SAPKITL319. and SP15 (SAPKITLC53. you must upgrade software components to the current release using Page 11 of 21 06. SAPKITL312.

SAPKITL323) Note 948644 This note prevents a run time error within the Solution Directory. SAPKITL317.2". and changes to the settings for System Monitoring will not be taken over.1 to 3. SAPKITL314. Search for all Categories: "SAP Solution Manager 3. SAPKITL323. SAPKITL325) Note 1015744 This note correction prevents the loss of settings for System Monitoringwhich might occur under specific circumstances: in this case for all Checks the same name will be displayed. SAPKITL319 SAPKITL320. SAPKITL317. SAP Solution Manager 3. SAP Solution Manager 3. SAPKITL318.sap. This is not necessary if you have already implemented this note in Release 3. o ST 320 SP11 (SAPKITL321) Note 917896 This note prevents a short dump.2 (start configuration: ST 310 with Support Package level 16 to 16 [inclusive]). when you save at this point the original Check names will be overwritten. and SAPKITL30A or SAPKITL30B) Note 900891 To upgrade your SAP Solution Manager 3. You can find the installation and upgrade packages on the SAP Service Marketplace under the path: http://service. Node Plug-In Satellite System for ST-A/PI. You can also do this later. SAPKITL321.2 (Software component ST) o ST 320 SP12 to SP15 (SAPKITL322. - o ST 320 SP01 to SP11 (SAPKITL311. SAPKITL316.2 Note 901063 This note corrects an error in the function "Expertise on Demand". SAPKITL315. o ST 320 SP12 to SP13 (SAPKITL322. SAPKITL313. SAPKITL324.SAP Note 662441 Solution Manager: SAP Notes for Support Packages Transaction SAINT.2010 . SAPKITL315.1 before carrying out the upgrade.2 (Installation): open the node content for ST-SER. o ST 320 SP04 to SP12 (SAPKITL314. The note must be imported before migrating the solutions from Release 3.com/swdc. SAPKITL312. SAPKITL319. you must implement this note after the upgrade. Page 12 of 21 06. These current releases are: ST-SER 620_2005_1 (SAPKITLO8B) and ST-A/PI 01F_CRM315 (SAPKITAC27).1 to Version 3. SAPKITL318. if this has not been done already. The corrections also include ST-SUP 320 SP11 (SAPKITLC51).09. SAPKITL322) Note 928985 Implement this note to prevent a runtime error while creation of Service Desk messages. SAPKITL320. SAPKITL321. SAPKITL316.

For performance reasons. dependent systems are unintentionally deleted in solutions. This note. SAPKB62053. 863398. SAPKB62047. which can be implemented automatically. Refer to Note 888413 for the correct file name. Roadmaps. SAPKB62050. it is advisable to import Support Package 10 or higher if you want to work with test plans. SAPKB62046. 863101. This note prevents this loss of data. SAPKITL314. SAPKITL320 and SAPKITL321) Note 896632 This note contains a collection of notes that solve known problems in test plans in Solution Manager. This note can be implemented in a system with Solution Manager 3. you can possible to create new solutions again. Note 900005 If you delete certain data in Transaction SMSY. SAPKITL313. SAPKITL312. o ST 320 SP08 (SAPKITL318) Note 847366 The note contains the corrected template and the macro used to generate the test report documents with MSWord 2000. reissued EPS file to import Support Package 10.09. - o ST 320 SP08 to SP11 (SAPKITL318. SAPKB62051. Reporting). The note corrects this behavior. It can be implemented in Solution Manager 3. SAPKITL315. 869438 These notes prevent errors in specific Solution Manager functions (E-Learning Management.SAP Note 662441 Solution Manager: SAP Notes for Support Packages Note 900585 After you generate test plans for Solution Manager projects. Projects.2010 Page 13 of 21 . SAPKITL316 also SAPKITL30A or SAPKITL30B) Note 824893 It is possible that only a new start EWA is created instead of a following EWA. SAPKB62056. use the corrected.2 up to and including Support Package 57 for SAP_BASIS 620 (SAPKB62045. SAPKB62055. o ST 320 SP01 to SP06 (SAPKITL311. o ST 320 SP10 (SAPKITL320) Note 888413 Since the first version of Support Package 10 can cause data to be lost. 868998. SAPKB62052. Note 877547 After you have implemented this note. prevents this from occurring. SAPKB62048. SAPKITL319. SAPKB62054. SAPKB62049. 865684. data may be lost in the corresponding test packages. SAPKB62057). 06.2 and Support Package 52 for SAP_BASIS (SAPKB62052). - o ST 320 SP09 (SAPKITL319) Notes 866280.

o ST 320 SP02 (SAPKITL312) Note 794704 Certain system data may not be displayed correctly in the Solution Manager Operations and in the Solution Directory. errors may occur in Transaction DSWP in connection with the internal data model. SAPKITL319) o TMWFLOW 320 SP04.2010 Page 14 of 21 . o TMWFLOW 320 SP06 (SAPK-32006INTMWFLOW) 06.09. Notes 783317 and 783189 After you import Support Package 01. SAPK-32005INTMWFLOW. SAPKITL316) Note 826080 Data may disappear from the display in sessions in the SAP Solution Manager. - - SAP Solution Manager 3. o ST 320 SP04 (SAPKITL314) Note 809311 After you save a project in the configuration phase of Solution Manager.SAP Note 662441 Solution Manager: SAP Notes for Support Packages o ST 320 SP05 and SP06 (SAPKITL315. Both notes prevent this. The data still exists in the database. This note prevents these and can be automatically implemented. SP05. As a result you cannot save the solution. The note describes manual preparations and contains correction instructions that can be automatically implemented.2 (Software component TMWFLOW) o TMWFLOW 320 SP09 (SAPK-32009INTMWFLOW) Note 866051 This note corrects an error that can occur when working with projects in the Solution Manager. an error message appears advising you to enter an installation number. SAPK-32008INTMWFLOW) Note 770693 For Change Request Management you must read Note 770693.(ST 320 SP09. SP08 (SAPK-32004INTMWFLOW. a runtime error may occur in Transaction DSWP. but the current processing is not available. o ST 320 SP01 (SAPKITL311) Note 788295 After you import Support Package 01. when you migrate a solution into the solution directory. short dumps can occur. A manual correction prevents this error. The note describes a manual correction for this problem. Note 783225 After you save a solution in the system infrastructure that contains non-ABAP components.

SAPKITLC44. - - SAP Solution Manager 3.SAP Note 662441 Solution Manager: SAP Notes for Support Packages Note 826750 An incorrect RFC type was used to determine the RFC destination for the remote programs. also SAPKITLC3A and SAPKITLC3B) Note 845433 With this correction. Note 804821 If the highest Support Package you have imported is 48 (SAPKA62048) for the software component SAP_ABA.09. SAPKU31011). since an online RFC connection was used.2 (Software component ST-SER) o ST-SER 620_2005_1 SP03 (SAPKITLO93) 06. SAPKU31010. SAPKITLC43. The translations are customizing entries in a BC set. o ST-SUP 320 SP01 to SP06 (SAPKITLC41. SAPKITLC46. Notes 817289. Service Desk messages can no longer be created correctly.2010 Page 15 of 21 . This can lead to the termination of a background program.SAPKITLC44. SAPKITLC42. o ST-SUP 320 SP08 (SAPKITLC48) Note 863679 After you import the package ST-SUP 08. SAPKITL319). also SAPKITLC3A and SAPKITLC3B) Note 832810 This note contains missing translations for the Service Desk and Change Request Management.2 up to and including SP 11 for BBPCRM 3. 817518 and 815999 Implement these notes after you import TMWFLOW 320 SP05. SAPKITLC47. SAPKITLC45. SAP Solution Manager 3. SAPKITLC46. SAPKITLC43.SAPKITLC50. SAPKITLC45. o ST-SUP 320 SP09 (SAPKITLC49) Note 870063 This note contains Customizing for Issues (ST 320 SP09. SAPKITLC42. SAPKITLC49.2 (Software component ST-SUP) o ST-SUP 320 SP11 (SAPKITLC51) Note 901063 This note corrects an error in the function "Expertise on Demand". CRM transactions (CRM messages) can no longer be deleted if they are linked to a basis message. This note can be applied in Solution Manager 3. o ST-SUP 320 SP01 to SP10 (SAPKITLC41. SAPKITLC48.. follow Note 804821. The correction also includes ST 320 SP11 (SAPKITL321).1 (SAPKU31009.

You can implement the note with Support for BBPCRM 310 (SAPKU31012). SAPKITLO92. If you want to run multilingual SAP Solution Manager sessions in Chinese or Japanese. the termination RAISE_EXCEPTION OBJECT_TYPE_NOT_FOUND occurs in the Early Watch Alert processing in the background job SM:EXEC SERVICES.SAP Note 662441 Solution Manager: SAP Notes for Support Packages Support Package 03 offers multilingual options (Chinese. SAP Solution Manager 3. after you have imported Support Package 03. - SAP Solution Manager 3. o ST-ICO 140 SP01 (SAPK-14001INSTPL) Note 826586 The ASAP implementation roadmap delivered with ST-ICO 140 is not displayed correctly.09. execute Report RSLANG20 to delete the old language load and to activate the new load. This affects Service Desk (Support for ST-SUP 310. o ST-SER 620_2005_1 SP01 to SP03 (SAPKITLO91.2. Package 12 o Support Package Stack 24 (06/2005) Before you import the Support Packages from Stack 24. ST-PI 2005_1_620 (SAPKITLQGB) und Page 16 of 21 06. Support Package 03 contains the relevant language package delivery.2 (Software component ST-ICO) o ST-ICO 150 SP10 (SAPK-1506AINSTPL) The installation of this package requires minimum R3trans version from 2007/06/11.1 (cross-component Notes) o Support Package Collection 27 (DEC/2005) Note 902804 makes it once again possible to save the CRM transactions. use Transaction SAINT to update some software components to the current release. if you have not done so already. SAPKITLO93) Note 863853 This note contains important corrections for representing issues in sessions and reports. o ST-SER 320 SP01 (SAPKITLO71) Note 787314 If ST 310 SP16 (SAPKITL28) or higher has been installed. The current releases are: ST-SER 620_2005_1 (SAPKITLO8B). The note prevents this termination. ST-A/PI 01F_CRM315 (SAPKITAC27). texts from Package 10 310. The report in the corrections fixes the problem. SAPKITLC20) and issues (ST 27 for ST SAPKITL297).2010 . ST-SER 320 was triggered by ST-SER 620_2005_1. English and Japanese) for different sessions in SAP Solution Manager 3.

SAPKITL284. o ST 310 SP15 (SAPKITL285) Note 769465 After you have imported Support Package 43 (SAPKB62043) for SAP_BASIS 620 software component in the Solution Manager system. SAPKITL281. You only need to implement the note once. SAPKITL295. Reporting). SAPKITL273. o ST 310 SP 25 (SAPKITL295) Notes 866280. SAPKITL277.1". SAPKITL283. SAPKITL292. SAPKITL287.1 (Software component ST) o ST 310 SP20 to SP28 (SAPKITL290. when you create a test plan.2010 .09. SAPKITL293. SAPKITL279. Page 17 of 21 06. SAPKITL286) o ST 310 SPO2 SAPKITL275. SAPKITL278. SAPKITL276. You can implement the note automatically. Roadmap. SAPKITL280. Search for all Categories: "ST-A/PI". SAPKITL282. through SP16 (SAPKITL272. o ST 310 SP16 to SP26 (SAPKITL286.com/swdc. SAPKITL292. SAPKITL289. SAPKITL293. SAPKITL294. SAPKITL296) Note 900891 You must implement this note before you upgrade your Solution Manager from Version 3. SAPKITL294.SAP Note 662441 Solution Manager: SAP Notes for Support Packages PI_BASIS 2004_1_620 (SAPKINBA7A).sap. SAPKITL296. o ST 310 SP20 (SAPKITL290) Note 822082 After you have imported Support Package 20. a short dump may occur. Search for all Categories: "SAP Solution Manager 3. SAPKITL291. 868998 and 869438 These notes prevent errors in specific of Solution Manager functions (E-Learning Management. SAPKITL285. SAPKITL295. you cannot create support notifications in the Solution Manager. SAPKITL298) Note 928985 Implement this note to prevent a runtime error while creation of ServiceDesk messages. Alternatively import Support Packages 44 (SAPKB62044) and 45 (SAPKB62045). SAPKITL290. SAP Solution Manager 3. implement Note 822082. SAPKITL288. To solve this error. Test Workbench or in Transaction NOTIF_CREATE.1 (Installation): open the node content for ST-SER.1 to a higher release. SAP Solution Manager 3. "PI_BASIS". SAPKITL274. the system is deleted from the solution. SAPKITL297. - Note 775159 After you delete a server in Transaction SMSY. "ST-PI". You can find these installation and upgrade packages on the SAP Service Marketplace under the path: http://service. SAPKITL291. or the field "System Role" cannot be selected.

o ST-SER 620_2005_1 SP01 to SP03 (SAPKITLO91.1 (SAPKU31006. ST-SER 311 was replaced by ST-SER 320. This note can be applied to Solution Manager 3.2. SAPKITLC16. SAPKITLC12. SAP Solution Manager 3. If you want to process the multi-language SAP solution manager sessions in Chinese or Japanese. SAPKU31008. generation errors may occur when you import Support Packages. SAPKU31007. SAPKU31009. SAPKU31010.09. SAP Solution Manager 3. - - 06. SAPKITLC14.1 (Software component ST-SER) o ST-SER 620_2005_1 SP03 (SAPKITLO93) Support Package 03 provides multi-language options (Chinese. SAPKITLC17.1 (Software component ST-SUP) o ST-SUP 310 SP01 to SP09 (SAPKITLC11. The note prevents this termination from occurring. SAPKITLC15. SAPKITLO93) Note 863853 The note contains important corrections for displaying issues in session and reports. You only need to implement the note once. SAPKITLO92. ST-SER 320 has been replaced by ST-SER 620_2005_1. SAPKITLC13. Support package 03 contains the language delivery.2010 Page 18 of 21 . SAPKITLC18. a short dump occurs when you call the Operations Set Up for the solution.SAP Note 662441 Solution Manager: SAP Notes for Support Packages o ST 310 SP05 (SAPKITL275) Note 673106 After you have imported Support Package 05. o ST-SER 320 SP01 (SAPKITLO71) Note 787314 If ST 310 SP16 (SAPKITL28) or higher has been installed. start the report RSLANG20 after importing support package 03 to delete the old language load and activate the new load. SAPKU31011). also SAPKITLC10) Note 845433 When you implement this correction. English and Japanese) for various sessions for the SAP Solution Manager 3. the termination RAISE_EXCEPTION OBJECT_TYPE_NOT_FOUND occurs in the background job SM:EXEC SERVICES in the Early Watch Alert processing. Note 611536 If you have not loaded any service definitions from SAPOSS for a long time. CRM transactions (CRM messages) can no longer be deleted if they are linked to a basis message.1 up to and including SP11 for BBPCRM 3.

The report is an SAP expert tool that can be used by SAP Support if required.SAP Note 662441 Solution Manager: SAP Notes for Support Packages SAP Solution Manager 3. - Header Data Release Status: Released on: Master Language: Priority: 06. Not relevant for SAT-PI 003C_46B SP02 (SAPKITLPN2). ST-PI 003C_610 SP02 (SAPKITLPQ2). If the reports are missing the Batch job dumps and if you do not implement this note you will receive shortdumps every hour in an SAP System connected to an ORACLE database o o ST-PI 003C_40B SP02 (SAPKITLPL2).640] SP 06. Note 766425 This note contains a correction for Report /SDF/RSORAVSE. ST-PI 003C_640 SP01 (SAPKITLPS1). ST-PI 003C_45B SP02 (SAPKITLPM2). ST-PI 003C_46D SP02 (SAPKITLPP2). The report in the corrections to this note solves it. ST-PI 003C was triggered by ST-PI 2005_1. If you do not implement this correction when the report is executed.09.1 (Software component ST-ICO) o ST-ICO 150 SP10 (SAPK-1506AINSTPL) The installation of this package requires minimum R3trans version from 2007/06/11. ST-PI 003C_46C SP02 (SAPKITLPO2). you will lose the historical database performance data provided by Oracle. Report /SDF/RSORAVSE collects once an hour statistical data from Oracle statistics table V$SYSTEM_EVENT via Batch Job 'BTCH_RSORAVSH' and report /SDF/RSORAVSH displays these data. o - SAP Solution Tools Plug-In (Software component ST-PI) o This software component is relevant for the solution manager system and for connected satellite systems. ST-PI 2005_1_[46C.620. o ST-ICO 140 SP01 (SAPK-14001INSTPL) Note 826586 The ASAP implementation roadmap delivered with ST-ICO 140 is not displayed correctly.2010 Released for Customer 29. ST-PI 2005_1_[700] SP 04 and ST-PI 2005_1_[710] SP02 Note 1049478 This note contains both reports /SDF/RSORAVSE and /SDF/RSORAVSH. ST-PI 003C_620 SP02 (SAPKITLPR2).2008 14:43:15 English Correction with high priority Page 19 of 21 .08.

SAP Note 662441 Solution Manager: SAP Notes for Support Packages Category: Primary Component: Secondary Components: BC-UPG-ADDON Upgrade Add-On Components (IS) SV-SMG-OP Solution Directory SV-SMG-SER SAP Support Services SV-SMG-IMP-BIM Business Blueprint / Implementation SV-SMG-TWB-PLN Test Plan Management SV-SMG-SUP Service Desk / Incident Management SV-SMG-SYS Solution Manager System Landscape Program error SV-SMG Solution Manager Valid Releases Software Component ST ST ST-PI ST-PI ST-PI ST-PI ST-PI ST-PI ST-PI ST-PI ST-PI ST-SER ST-SER ST-ICO ST-SUP TMWFLOW Release 620 700 40B 45B 46B 46C 46D 610 620 640 700 620 700 620 620 310 From Release 220 400 003C_40B 003C_45B 003C_46B 003C_46C 003C_46D 003C_610 003C_620 003C_640 2005_1_70 0 310 700_2005_ 2 100 310 320 To Release 320 400 2005_1_40 B 2005_1_45 B 2005_1_46 B 2005_1_46 C 2005_1_46 D 2005_1_61 0 2005_1_62 0 2005_1_64 0 2005_1_70 0 620_2005_ 2 700_2005_ 2 140 320 320 and Subsequent X X X X X X X X X X X X X X X X Support Packages 06.2010 Page 20 of 21 .09.

2010 Page 21 of 21 .09.0 to Solution Manager 7. SAP Solution Manager 4.20 Attachments File Type SAR File Name AITL422.0 SAP CQC Going Live Support Maintenance Optimizer: Can not select product version Solution Manager: Solution Monitoring Related SAP Note Solution Manager: Service Desk Related SAP Notes Solution Manager: Implementation Scenario Related SAP Notes Service Delivery on SAP Solution Manager (Recommended Notes) General note for Change Request Management ST 400 General note about Change Request Management 3.SAR Language E Size 1 KB 06.SAP Note 662441 Solution Manager: SAP Notes for Support Packages Support Packages ST-PI Release 2005_1_46C Package Name SAPKITLQD6 Related Notes Number 1161294 1149742 1022797 949293 949292 949220 930747 907768 770693 Short Text Name chg.

Sign up to vote on this title
UsefulNot useful