+ sapnote_0000662441

06.09.2010 of 21

SAP Note 662441 - Solution Manager: SAP Notes for SupportPackages

Note Language: English Version: 156 Validity: Valid Since29.08.2008

Summary

SymptomYou want to import individual Support Packages or a Support Package stackfor the SAP Solution Manager, and want to check first if there are alreadyimportant notes for these Support Packages or this stack.

Other terms

Software component DescriptionST Solution Manager ToolST-SER Solution Manager Service ToolsST-PI Solution Tools Plug-InST-SUP Solution Manager Service DeskTMWFLOW Change Request ManagementST-ICO Solution Manager Implementation ContentSAP_BASIS SAP Basis ComponentSAP_ABA SAP Application BasisBBPCRM BBP / CRMCPRXRPM cProjects and others

Reason and Prerequisites

Solution

This composite note 662441 refers to both selected notes and informationthat is relevant to importing Support Packages for the software componentslisted above into a SAP Solution Manager system.Herein referenced notes are recommended to be implemented because they dealoften with possible short dumps, possible runtime errors, possible datainconsistencies, or even possible data loss, etc.Target group for this note are users who implement Support Packages in aSolution 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 thatyou have found in transaction SPAM, such as technical names of theSupport Packages you want to import, or the names of the softwarecomponents in question (search terms can appear more than once inthis note).

o For the software components 'SAP_BASIS', 'SAP_ABA' and 'BBPCRM',only the notes that are directly related to the SAP SolutionManager function are mentioned. These notes are listed below by SAPSolution Manager software component.

o The notes are selected shortly after the Support Packages arereleased. Notes written after this time are only included if theyare important, i.e. if they correspond to the above given errorcategories. This is not a complete list of all notes that can beimplemented for individual Support Packages.

06.09.2010 of 21


o The notes listed here are usually not relevant for subsequentSupport Packages. However, in some cases, you should check if anote has been revised, and a new version is once again valid.

o This composite note does not list notes that refer to installationpackages and upgrade packages. These are dealt with in theimplementation guide for the release in question (see the SAPService Marketplace, quick link "/solutionmanager", area"Installation Guides" or SAP Service Marketplace, quick link"/instguides", area "SAP Components", "SAP Solution Manager").

Are there similar scenario related composite notes ?

o For certain usage scenarios of SAP Solution Manager there areadditional composite notes which indicates corrections particularlyrelevant for these scenarios:

SAP Note Usage Scenario1024932 Maintenance Optimizer949220 Implementation896632 Testworkbench1059350 Quality Center949292 Service Desk949293 Solution Monitoring907768 Change Request Management (Release 7.0)770693 Change Request Management (Release 3.2)930747 Delivery of SAP Services1061383 SM Diagnostics (Release 7.0, from SP 13)1010428 SM Diagnostics (Release 7.0, prior SP 12)

o These additional notes focus on a wider range of corrections thannote 662441. They refer to a greater extent to functionalcorrectness of the corresponding scenario.

o Therefore also the target group for these notes is extended by -for example - project leads or scenarios responsibles.

o There is one further composite note with optional cross-secenarioinformation: 948871.

Where to find information on changes for system configuration ?

o Note 903274 and its attachment indicate the IMG activities thathave changed with a new support package. This would help indeciding if your system confiuration would need to be changed withthe new support package.

Notes related to Support Packages for SAP Solution Manager softwarecomponents:

SAP Solution Manager 7.0 (cross-component notes)

o Support Package Stack 17 (08/2008)

- To be able to send Service Desk messages to SAP please

06.09.2010 of 21


implement note 1165980 after you have implemented SP 16 ofSAP_ABA (SAPKA70016).


- Stack 15 has been released. Before you can import all SupportPackages from Stack 15, you must upgrade software componentST-SER to the current release using transaction SAINT, if thishas not been done already. The current ST-SER release is:ST-SER 700_2008_1 (SAPKITLONB). You can find installation andupgrade packages on the SAP Service Marketplace under the path:http://service.sap.com/swdc, Search for all Categories, searchterm "SAPKITLONB".

If you have already installed SAPKITLOM6 into your system youwill receive a waring during import of SAPKITLONB: EquivalenceSP level not reached. SAPKITLOO1 should be included. You canignore this warning. Your system will not be downgraded.

- Implement note 1128026 to your Solution Manager system afterhaving loaded ST 400 SP15 (SAPKITL425). The note correction isvalid for SAP_ABA 700 SP 14 (SAPKA70014) which is required bySP15 and part of the stack. This correction is necessary towork within service sessions.


- For software component CPRXRPM there is a Conflict ResolutionTransport (CRT) that needs to be implemented together with SP13 of SAP_ABA 700. Since a CRT can not be included in a supportpackage stack you need to download CRT "CPRXRPM 400: CRT forSAPKA70013" (SAPK-400C4INCPRXRPM) separately before youdownload the stack.

- If you load SP 13 of SAP_ABA 700 (SAPKA70013), which isrequired by SP 13 of SAT 400 (SAPKITL423), and load at the sametime SP 4 of ST-SER 700_2007_1 (SAPKITLOM4), you need toimplement note 1075012. The note implementation triggers thegeneration of many repository objects, please be aware thatthis will take some time. Please notice also note 1042866 whichis mentioned below two time.


- Before you can import all Support Packages from Stack 12, youmust upgrade software component ST-SER to the current releaseusing transaction SAINT, if this has not been done already.Before this upgrade you need to implement note 1042866 (seebelow at SAPKITL422 for more details). The current ST-SERrelease is: ST-SER 700_2007_1 (SAPKITLOLB). You can findinstallation and upgrade packages on the SAP ServiceMarketplace under the path: http://service.sap.com/swdc, Searchfor all Categories, search term "SAPKITLOLB".

o Support Package Collection 07 and Support Package Stack 06(08/2006)

- With note correction 973995 Service Desk messages can be again

06.09.2010 of 21


created correctly after having ST 400 SP07 (SAPKITL417) loadedor having Note 963002 implemented. Correction is valid forSAP_BASIS 700 Support Package 09 (SAPKA70009) which is requiredby SP07.

- Implementation of note 964651 prevents occurance of possibleinconsistencies while creating Servcie Desk Messages. Thiscorrection is valid for CRM 5.0 Support Package 05 (SAPKU50005)which is required by ST 400 SP06 (SAPKITL416) which again isrequired by ST 400 SP07 (SAPKITL417).

o Support Package Stack 06 (08/2006) and prior

- Note 954496 delivers a correction for Post Processing Framework(PPF) which avoids a runtime error. This note is valid forSAP_BASIS 700 Support Package 08 (SAPKB70008) which is requiredby ST 400 SP06 (SAPKITL416).

- Note 948129 prevents a short-dump that can occur while callingdirectly or indirectly the Service Session Workbench. Thecorrection is valid for SAP_ABA 700 Support Package 08(SAPKA70008) which is required by ST 400 SP06 (SAPKITL416).This correction is also indirectly valid for older ST 400Support Packages (SAPKITL415, SAPKITL414, SAPKITL413,SAPKITL412, SAPKITL411).

o Support Package Collection 05 (05/2006)

- For Service Desk, Change Request Management, and IssueManagement note 946961 has to be implemented to avoid a shortdump while creating or changing messages, change requests, orissues. The correction is valid for CRM 5.0 Support Package 04(SAPKU50004) which is required by ST400 SP05 (SAPKITL415).


- For Change Request Management note 909236 prevents possibledata inconsistency. The correction is valid for CRM 5.0 SupportPackage 03 (SAPKU50003). Support Package SAPKU50003 is requiredby ST400 SP03 (SAPKITL413).


- With SAP_BASIS 700 Support Package 06 (SAPKB70006), deletionswere delivered that lead to generation errors when you importCPRXRPM 400 SP02 (SAPK-40002INCPRXRPM) in Transaction SPAM, ifyou use SPAM to activate the generation. You can ignore thisgeneration error. You can identify the generation error by thekeywords "CL_DPR_SC_SERVICES" and "/RPM/CL_BUCKET_O".

- Note 725658 prevents a possible short dump. The correction isvalid for CRM 5.0 Support Package 02 (SAPKU50002) which isrequired by ST400 SP02 (SAPKITL412).

- Note 905469 provides a language package which should bere-imported after importing CRM 5.0 SP02 (SAPKU50002) into theSolution Manager. Support Package SAPKU50002 is required byST400 SP 02 (SAPKITL412)

06.09.2010 of 21



- Note 908186 provides Ramp-Up customers with an overview ofselected notes relating to the target configuration of theupgrade to the new release. The primary Support Package isSupport Package 01 from ST 400 (SAPKITL411, also SAPKITL40G).

SAP Solution Manager 7.0 (Software component ST 400)

o ST 400 SP16 (SAPKITL426)

- With SP16 (SAPKITL426) SAP strictly recommends to upgrade yourST-SER tothe release 700_2008_1 or higher. Therefore usetransaction SAINT instead of transaction SPAM to patch yoursystem to SAP Solution Manager 7.0. If you try to patch yoursystem via SPAM and your ST-SER release is 700_2007_1 or lessyou will receive one of the following information within SPAMduring phase ADDON_CONFLICTS_?:

a) Conflicts Between Add-On ST-SER 700_2005_2 and SupportPackages SAPKITL426 Include CRT

b) Conflicts Between Add-On ST-SER 700_2006_1 and SupportPackages SAPKITL426 Include CRT

c) Conflicts Between Add-On ST-SER 700_2006_2 and SupportPackages SAPKITL426 Include CRT


Please be aware there is no physical Conflict ResolutionTransport (CRT) available to solve this conflict (it is notplanned to provide such a CRT). You have to patch your systemvia SAINT not via SPAM:

1. Delete your SPAM-QUEUE by pressing the Display/Define buttonwithin SPAM.

2. Download all ST-SER Delta-Upgrade packages from the SoftwareDownload Center into your EPS-Inbox.

3. Call transaction SAINT and press Start button.

4. Select ST-SER 700_2008_1 or higher and press Continue button

All neccessary component packages will automatically beincluded into a valid SAINT-queue


- With SP15 (SAPKITL425) SAP strictly recommends to upgrade yourST-SER to the release 700_2007_1 or higher. Therefore usetransaction SAINT instead of transaction SPAM to patch yoursystem to SAP Solution Manager 7.0 Stack 15 (01/2008). If youtry to patch your system via SPAM and your ST-SER release is700_2006_1 or less you will receive one of the following

06.09.2010 of 21


information within SPAM during phase ADDON_CONFLICTS_?:

a) Conflicts Between Add-On ST-SER 700_2005_2 and SupportPackages SAPKITL425 Include CRT

b) Conflicts Between Add-On ST-SER 700_2006_1 and SupportPackages SAPKITL425 Include CRT


Please be aware there is no physical Conflict ResolutionTransport (CRT) available to solve this conflict (it is notplanned to provide such a CRT). You have to patch your systemvia SAINT not via SPAM:

1. Delete your SPAM-QUEUE by pressing the Display/Define buttonwithin SPAM.

2. Download all ST-SER Delta-Upgrade packages from the SoftwareDownload Center into your EPS-Inbox.

3. Call transaction SAINT and press Start button.

4. Select ST-SER 700_2007_1 or higher and press Continue button

All neccessary component packages will automatically beincluded into a valid SAINT-queue

- Applying SAPKITL425 together with SAPKITL422 within 1SAINT/SPAM queueTo avoid following error message during main import:duplicate key error during insert into table AGSTWB_RSTAT_VALoccureddownload the attached Allowfile AITL422.SAR into your<DIR_TRANS> directory and extract it with SAPCAR -xvfAITL412.SAR

-

- Notes 1128453This note summarizes some corrections with regard to theImplementation Guide in the Solution Manager system (SAPReference IMG, transaction SPRO). Do consider this note in caseyou start configuration activities based on SP 15.

- With SP15 (SAPKITL425) so called workcenters are introduced toSAP Solution Manager. For details please see the DevelopmentNews for SP15 in SAP Service Marketplace at link"http://service.sap.com/solutionmanager" -> "Medie Library" ->"Technical Papers" -> "Development News SAP Solution ManagerSPS15". Currently only these workcenters are released tocustomers with SP15: Implementation & Upgrade, SolutionLandscape & Operation Setup, Change Lifecycle Management,Incident Management, Service Delivery, Job SchedulingManagement, System Monitoring, System Administration, andSystem Landscape Management. The workcenters are released for

06.09.2010 of 21


being called by transaction SOLMAN_WORKCENTER. This transactionis part of the user menu of role SAP_SMWORK_BASIC, the threeother entries of this user menu are not released for beingused.

- Note 1136916 (Workcenter)With implementation of note 1136916 on top of SP15 (SAPKITL425)solutions are created from within a workcenter in the logonlanguage. (Scenario specific note 949293 lists more workcenterrelevant functional corrections for the Solution Monitoringscenario. These additional notes correct problems that areconcidered less server.)

- Notes 1130172, 1122966, and 1137683 (Maintenance Optimizer):

Implement note 1130172 after having loaded SP15 (SAPKITL425).

Note 1122966 is relevant for every customer, who likes toimport ERP Enhancement Packages using the MaintenanceOptimizer. The note lists required correction notes to beimplemented in addition to a certain Solution Manager 7.0Support Package Level.

Note 1137683 provides customers using Maintenance Optimizerwith an overview of selected notes relating to theConfiguration and Usage of Software Lifecycle Manager. The notedescribes deviations and enhancements to the IMG and KWdocumentation.

- Notes 1138350 (Change Request Management)Note 1138350 is an urgent correction for the Change RequestManagement scenario.

- Notes 1137338 (Expertise on Demand)Please implement this note in case you are using the Expertiseon Demand functionality of Issue Management. Noticeprerequisites describes in this notes.

- Notes 1137739, 1138046, 1138049 (Issue Management)Please implement these notes in case you are using transactionSOLMAN_ISSUE_MGMT (additional key word Collaboration Platform).

- Note 1128026 (Service Level Reporting)Implementing this note prevents a run-time error for SLreporting.

- Note 1140822After implementing SP15 (SAPKITL425), the functionality formanaging several SAP customer numbers is active. This causeserror message AI_SC_EN097 "SAP customer number for installationnumber &1 not known". Implement note 1140822, to deactivatethis functionality.


- Note 1106236Implementation of Note 1106236 is required if you use theChange Request Management of the Solution Manager. The

06.09.2010 of 21


condition check regarding successfull export of transportrequests has to be corrected by this note after you've importedSP14.


- Note 1084173With SP13 the background job scheduling for Central SystemAdministration has been changed. Please process the activitiesdescribed in SAP note 1084173 after SP13 implementation.


- Note 1077050Before importing SP12 to your Solution Manager system pleasecheck whether or not you would import the updated EPS file forSP12 (EPS file name: CSR0120031469_0027444.PAT) which isavailable for download since 23.07.2007. If you are about toimport a different EPS file for SP12 than this updated oneplease see Note 1077050 which gives an overview on how toproceed. Importing an older EPS file for SP12 together withprevious Support Packages for ST 400 might result in errorsduring import.

- Note 1067602The interface between the Maintenance Optimizer and SAP ServiceMarketplace has to be extended by implementing SAP Note1067602. This extension is necessary for calculating whichSupport Packages have to be downloaded and for generating astack XML file for installing Enhancement Packages.

- Note 1042866If ST 400 SP12 (SAPKITL422) or higher has been installed, thetermination #Syntax error in program"RDSVASASPLI_CBP____________062" might occur when opening#Business Process Details# in the Solution Directory. To avoidthis dump, please implement the coding correction of SAP Note1042866 if you are on ST-SER 700_2006_2 and before implementingST-SER 700_2007_1.

- Note 1052319This correction prevents a short dump for System Monitoring.

- Note 1059271From several scenarios of SAP Solution Manager the GlobalSettings from Transaction SOLUTION_MANAGER are read. This notecorrection prevents an error that might occur while readingthese settings.


- Note 1042815This note correction prevents writing SMSY data back to theSystem Landscape Directory (SLD).

o ST 400 SP09 to SP10 (SAPKITL419, SAPKITL420)

- Note 1012979

06.09.2010 of 21


This note prevents a possible data inconsistency between SMSYdata and solutions.

o ST 400 SP06 to SP10 (SAPKITL416, SAPKITL417, SAPKITL418,SAPKITL419, SAPKITL420)

- Note 1015744This note correction prevents the loss of settings for SystemMonitoring which might occur under specific circumstances: inthis case for all Checks the same name will be displayed, whenyou save at this point the original Check names will beoverwritten; and changes to the settings for System Monitoringwill not be taken over.


- Note 1005323This note prevents a run time error in job "SM:CSA SESSIONREFRESH".

- Note 1006711Without this note data loss is possible if a system is notavailable during data refresh in transaction SMSY.

- Note 1011376Customers using Service Desk for Service Providers and actionprofile AI_SDK_STANDARD need to implement this note to be ableto create and save messages.

- Note 1008717Solution Manager features that use HTML Viewer Control (such asIssue Management and Maintenance Optimizer) won't work withoutthis note, if SAP_BASIS 700 note 975872 or SP10 (SAPKB70010)had been implemented and SAP GUI 640 Patch Level 22 is beingused.

o ST 400 SP06 to SP08 (SAPKITL416, SAPKITL417, SAPKITL418)

- Note 1012979This note prevents a possible data inconsistency between SMSYdata and solutions. You would need to apply note 1012979 onlyin case you have implemented note 987122 with SP06, SP07, orSP08.


- Note 966398This note correction prevents a short dump that could occurewhile you perform the "Initial Data Transfer for IBase" intransaction SOLUTION_MANAGER.


- Note 946605Issue Management requires implementation of this note to avoida short dump that occurs during issue status refresh.

o ST 400 SP03 to SP05 (SAPKITL413,SAPKITL414, SAPKITL415)

06.09.2010 of 21


- Note 948644This note prevents a run time error within the SolutionDirectory.


- Note 919790This note has an additional correction for SP03.

o ST 400 SP01 to SP03 (SAPKITL411, SAPKITL412, SAPKITL413)

- Note 929928Without this correction the Issue contexts get lost for Issuefrom Solution Manager 3.2 after upgrade.

- Note 928985Implement this note to prevent a runtime error while creationof Service Desk messages.


- Note 917896This note prevents a short dump. The note must be importedbefore the migration of the solutions from Release 3.1 to 7.0.

- Notes 919790, 912618, 910177These Notes provide corrections for the use of solutions,issues, top issues, expertise on demand, and the BusinessProcess Monitoring.

- Note 906340SP02 provided a performance improvement when working withsolutions. This note delivers a correction for thisoptimization.

SAP Solution Manager 7.0 (Software component ST-ICO)

o ST-ICO 150 SP10 (SAPK-1507AINSTPL)

- The installation of this package requires minimum R3transversion from 2007/06/11.

SAP Solution Manager 7.0 (Software component ST-SER)

o ST-SER 700_2007_1 SP01 (SAPKITLOM1)

- If you import Supportpackage SAPLITLOM1 and Delta UpgradePacakge SAPKITLOLB together within 1 SAINT queue, an errorduring test import will occur:Function DSWP_BPMO_STXT_GET (DSWP_BPM_FUNH 04) does not fitinto the existing function group ((DSWP_BPMO 12))Ignore this error by using SAINT functionality in menu "Extras"-> "Ignore test import errors"

06.09.2010 of 21


SAP Solution Manager 3.2 (cross-component notes)


- Implementation of note 964651 prevents occurance of possibleinconsistencies while creating Servcie Desk Messages. Thiscorrection is valid for CRM 3.1 Support Package 12 and 13(SAPKU31012, SAPKU31013) which are required by ST-SUP 320 SP13,SP14, and SP15 (SAPKITLC53, SAPKITLC54, SAPKITLC55).

o Support Package Collection 07 and Support Package Stack 13(06/2006)

- With note correction 973995 Service Desk messages can be againcreated correctly after having ST 320 SP14 (SAPKITL324) loadedor having Note 963002 implemented. Correction is valid forSAP_BASIS 620 Support Package 60 (SAPKA62060) which is requiredby SP14.

- Implementation of note 964651 prevents occurance of possibleinconsistencies while creating Servcie Desk Messages. Thiscorrection is valid for CRM 3.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).


- Note 948129 prevents a short-dump that can occur while callingdirectly or indirectly the Service Session Workbench. Thecorrection is also valid for SAP_ABA 620 Support Package 59(SAPKA62059) which is required by ST 320 SP13 (SAPKITL323).This correction is also indirectly valid for older ST 320Support Packages (SAPKITL322, SAPKITL321, SAPKITL320,SAPKITL319, SAPKITL318, SAPKITL317, SAPKITL316, SAPKITL315,SAPKITL314, SAPKITL313, SAPKITL312, SAPKITL311).


- Note 902804 makes it possible once again to save texts from CRMtransactions. This affects Service Desk (Support Package 11 forST-SUP 320; SAPKITLC51), Change Request Management (SupportPackage 11 for TMWFLOW 320; SAPK-32011INTMWFLOW) and issues(Support Package 11 for ST 320; SAPKITL321). The note can beimplemented with Support Package 12 from BBPCRM 310(SAPKU31012).


- This stack contains Support Package 10 (SAPKITL320) for ST 320,which, in its first version, can lead to data loss during theimport. Refer to Note 888413 for the EPS file name of thecorrected, reissued EPS file.


- Before you import Support Packages from Stack 08, you mustupgrade software components to the current release using

06.09.2010 of 21


Transaction SAINT, if this has not been done already. Thesecurrent releases are: ST-SER 620_2005_1 (SAPKITLO8B) andST-A/PI 01F_CRM315 (SAPKITAC27). You can find the installationand upgrade packages on the SAP Service Marketplace under thepath: http://service.sap.com/swdc, Search for all Categories:"SAP Solution Manager 3.2", SAP Solution Manager 3.2(Installation): open the node content for ST-SER, Node Plug-InSatellite System for ST-A/PI.

SAP Solution Manager 3.2 (Software component ST)

o ST 320 SP12 to SP15 (SAPKITL322, SAPKITL323, SAPKITL324,SAPKITL325)

- Note 1015744This note correction prevents the loss of settings for SystemMonitoringwhich might occur under specific circumstances: inthis case for all Checks the same name will be displayed, whenyou save at this point the original Check names will beoverwritten; and changes to the settings for System Monitoringwill not be taken over.

o ST 320 SP12 to SP13 (SAPKITL322, SAPKITL323)

- Note 948644This note prevents a run time error within the SolutionDirectory.

o ST 320 SP04 to SP12 (SAPKITL314, SAPKITL315, SAPKITL316,SAPKITL317, SAPKITL318, SAPKITL319 SAPKITL320, SAPKITL321,SAPKITL322)

- Note 928985Implement this note to prevent a runtime error while creationof Service Desk messages.


- Note 917896This note prevents a short dump. The note must be importedbefore migrating the solutions from Release 3.1 to 3.2

- Note 901063This note corrects an error in the function "Expertise onDemand". The corrections also include ST-SUP 320 SP11(SAPKITLC51).

o ST 320 SP01 to SP11 (SAPKITL311, SAPKITL312, SAPKITL313,SAPKITL314, SAPKITL315, SAPKITL316, SAPKITL317, SAPKITL318,SAPKITL319, SAPKITL320, SAPKITL321, and SAPKITL30A or SAPKITL30B)

- Note 900891To upgrade your SAP Solution Manager 3.1 to Version 3.2 (startconfiguration: ST 310 with Support Package level 16 to 16[inclusive]), you must implement this note after the upgrade.You can also do this later. This is not necessary if you havealready implemented this note in Release 3.1 before carryingout the upgrade.

06.09.2010 of 21


- Note 900585After you generate test plans for Solution Manager projects,data may be lost in the corresponding test packages. This noteprevents this loss of data. It can be implemented in SolutionManager 3.2 up to and including Support Package 57 forSAP_BASIS 620 (SAPKB62045, SAPKB62046, SAPKB62047, SAPKB62048,SAPKB62049, SAPKB62050, SAPKB62051, SAPKB62052, SAPKB62053,SAPKB62054, SAPKB62055, SAPKB62056, SAPKB62057).

- Note 900005If you delete certain data in Transaction SMSY, dependentsystems are unintentionally deleted in solutions. This note,which can be implemented automatically, prevents this fromoccurring.

o ST 320 SP08 to SP11 (SAPKITL318, SAPKITL319, SAPKITL320 andSAPKITL321)

- Note 896632This note contains a collection of notes that solve knownproblems in test plans in Solution Manager. For performancereasons, it is advisable to import Support Package 10 or higherif you want to work with test plans.


- Note 888413Since the first version of Support Package 10 can cause data tobe lost, use the corrected, reissued EPS file to import SupportPackage 10. Refer to Note 888413 for the correct file name.

- Note 877547After you have implemented this note, you can possible tocreate new solutions again.


- Notes 866280, 868998, 863398, 865684, 863101, 869438These notes prevent errors in specific Solution Managerfunctions (E-Learning Management, Roadmaps, Projects,Reporting).


- Note 847366The note contains the corrected template and the macro used togenerate the test report documents with MSWord 2000. This notecan be implemented in a system with Solution Manager 3.2 andSupport Package 52 for SAP_BASIS (SAPKB62052).

o ST 320 SP01 to SP06 (SAPKITL311, SAPKITL312, SAPKITL313,SAPKITL314, SAPKITL315, SAPKITL316 also SAPKITL30A or SAPKITL30B)

- Note 824893It is possible that only a new start EWA is created instead ofa following EWA. The note corrects this behavior.

06.09.2010 of 21


o ST 320 SP05 and SP06 (SAPKITL315, SAPKITL316)

- Note 826080Data may disappear from the display in sessions in the SAPSolution Manager. The data still exists in the database, butthe current processing is not available.


- Note 809311After you save a project in the configuration phase of SolutionManager, short dumps can occur. This note prevents these andcan be automatically implemented.


- Note 794704Certain system data may not be displayed correctly in theSolution Manager Operations and in the Solution Directory. Thenote describes a manual correction for this problem.


- Note 788295After you import Support Package 01, a runtime error may occurin Transaction DSWP, when you migrate a solution into thesolution directory. A manual correction prevents this error.

- Notes 783317 and 783189After you import Support Package 01, errors may occur inTransaction DSWP in connection with the internal data model.Both notes prevent this.

- Note 783225After you save a solution in the system infrastructure thatcontains non-ABAP components, an error message appears advisingyou to enter an installation number. As a result you cannotsave the solution. The note describes manual preparations andcontains correction instructions that can be automaticallyimplemented.

SAP Solution Manager 3.2 (Software component TMWFLOW)

o TMWFLOW 320 SP09 (SAPK-32009INTMWFLOW)

- Note 866051This note corrects an error that can occur when working withprojects in the Solution Manager.(ST 320 SP09, SAPKITL319)

o TMWFLOW 320 SP04, SP05, SP08 (SAPK-32004INTMWFLOW,SAPK-32005INTMWFLOW, SAPK-32008INTMWFLOW)

- Note 770693For Change Request Management you must read Note 770693.

o TMWFLOW 320 SP06 (SAPK-32006INTMWFLOW)

06.09.2010 of 21


- Note 826750An incorrect RFC type was used to determine the RFC destinationfor the remote programs. This can lead to the termination of abackground program, since an online RFC connection was used.

- Notes 817289, 817518 and 815999Implement these notes after you import TMWFLOW 320 SP05.

- Note 804821If the highest Support Package you have imported is 48(SAPKA62048) for the software component SAP_ABA, follow Note804821.

SAP Solution Manager 3.2 (Software component ST-SUP)

o ST-SUP 320 SP11 (SAPKITLC51)

- Note 901063This note corrects an error in the function "Expertise onDemand". The correction also includes ST 320 SP11 (SAPKITL321).


- Note 870063This note contains Customizing for Issues (ST 320 SP09,SAPKITL319).


- Note 863679After you import the package ST-SUP 08, Service Desk messagescan no longer be created correctly..

o ST-SUP 320 SP01 to SP10 (SAPKITLC41, SAPKITLC42, SAPKITLC43,SAPKITLC44, SAPKITLC45, SAPKITLC46, SAPKITLC47, SAPKITLC48,SAPKITLC49,SAPKITLC50, also SAPKITLC3A and SAPKITLC3B)

- Note 845433With this correction, CRM transactions (CRM messages) can nolonger be deleted if they are linked to a basis message. Thisnote can be applied in Solution Manager 3.2 up to and includingSP 11 for BBPCRM 3.1 (SAPKU31009, SAPKU31010, SAPKU31011).

o ST-SUP 320 SP01 to SP06 (SAPKITLC41, SAPKITLC42,SAPKITLC43,SAPKITLC44, SAPKITLC45, SAPKITLC46, also SAPKITLC3A andSAPKITLC3B)

- Note 832810This note contains missing translations for the Service Deskand Change Request Management. The translations are customizingentries in a BC set.


o ST-SER 620_2005_1 SP03 (SAPKITLO93)

06.09.2010 of 21


- Support Package 03 offers multilingual options (Chinese,English and Japanese) for different sessions in SAP SolutionManager 3.2.Support Package 03 contains the relevant language packagedelivery. If you want to run multilingual SAP Solution Managersessions in Chinese or Japanese, after you have importedSupport Package 03, execute Report RSLANG20 to delete the oldlanguage load and to activate the new load.

o ST-SER 620_2005_1 SP01 to SP03 (SAPKITLO91, SAPKITLO92, SAPKITLO93)

- Note 863853This note contains important corrections for representingissues in sessions and reports.

o ST-SER 320 SP01 (SAPKITLO71)

- Note 787314If ST 310 SP16 (SAPKITL28) or higher has been installed, thetermination RAISE_EXCEPTION OBJECT_TYPE_NOT_FOUND occurs in theEarly Watch Alert processing in the background job SM:EXECSERVICES. The note prevents this termination.

- ST-SER 320 was triggered by ST-SER 620_2005_1.




o ST-ICO 140 SP01 (SAPK-14001INSTPL)

- Note 826586The ASAP implementation roadmap delivered with ST-ICO 140 isnot displayed correctly. The report in the corrections fixesthe problem.

SAP Solution Manager 3.1 (cross-component Notes)

o Support Package Collection 27 (DEC/2005)

- Note 902804 makes it once again possible to save the texts fromCRM transactions. This affects Service Desk (Support Package 10for ST-SUP 310; SAPKITLC20) and issues (ST 27 for ST 310;SAPKITL297). You can implement the note with Support Package 12for BBPCRM 310 (SAPKU31012).


- Before you import the Support Packages from Stack 24, useTransaction SAINT to update some software components to thecurrent release, if you have not done so already. The currentreleases are: ST-SER 620_2005_1 (SAPKITLO8B), ST-A/PI01F_CRM315 (SAPKITAC27), ST-PI 2005_1_620 (SAPKITLQGB) und

06.09.2010 of 21


PI_BASIS 2004_1_620 (SAPKINBA7A). You can find theseinstallation and upgrade packages on the SAP ServiceMarketplace under the path: http://service.sap.com/swdc, Searchfor all Categories: "SAP Solution Manager 3.1", SAP SolutionManager 3.1 (Installation): open the node content for ST-SER;Search for all Categories: "ST-A/PI", "ST-PI", "PI_BASIS".

SAP Solution Manager 3.1 (Software component ST)

o ST 310 SP20 to SP28 (SAPKITL290, SAPKITL291, SAPKITL292,SAPKITL293, SAPKITL294, SAPKITL295, SAPKITL296, SAPKITL297,SAPKITL298)

- Note 928985Implement this note to prevent a runtime error while creationof ServiceDesk messages.

o ST 310 SP16 to SP26 (SAPKITL286, SAPKITL287, SAPKITL288,SAPKITL289, SAPKITL290, SAPKITL291, SAPKITL292, SAPKITL293,SAPKITL294, SAPKITL295, SAPKITL296)

- Note 900891You must implement this note before you upgrade your SolutionManager from Version 3.1 to a higher release.

o ST 310 SP 25 (SAPKITL295)

- Notes 866280, 868998 and 869438These notes prevent errors in specific of Solution Managerfunctions (E-Learning Management, Reporting).


- Note 822082After you have imported Support Package 20, you cannot createsupport notifications in the Solution Manager, Roadmap, TestWorkbench or in Transaction NOTIF_CREATE. To solve this error,implement Note 822082.

o ST 310 SPO2 through SP16 (SAPKITL272, SAPKITL273, SAPKITL274,SAPKITL275, SAPKITL276, SAPKITL277, SAPKITL278, SAPKITL279,SAPKITL280, SAPKITL281, SAPKITL282, SAPKITL283, SAPKITL284,SAPKITL285, SAPKITL286)

- Note 775159After you delete a server in Transaction SMSY, the system isdeleted from the solution. You can implement the noteautomatically.


- Note 769465After you have imported Support Package 43 (SAPKB62043) forSAP_BASIS 620 software component in the Solution Managersystem, a short dump may occur, or the field "System Role"cannot be selected, when you create a test plan. You only needto implement the note once. Alternatively import SupportPackages 44 (SAPKB62044) and 45 (SAPKB62045).

06.09.2010 of 21



- Note 673106After you have imported Support Package 05, a short dump occurswhen you call the Operations Set Up for the solution. You onlyneed to implement the note once.

SAP Solution Manager 3.1 (Software component ST-SUP)

o ST-SUP 310 SP01 to SP09 (SAPKITLC11, SAPKITLC12, SAPKITLC13,SAPKITLC14, SAPKITLC15, SAPKITLC16, SAPKITLC17, SAPKITLC18, alsoSAPKITLC10)

- Note 845433When you implement this correction, CRM transactions (CRMmessages) can no longer be deleted if they are linked to abasis message. This note can be applied to Solution Manager 3.1up to and including SP11 for BBPCRM 3.1 (SAPKU31006,SAPKU31007, SAPKU31008, SAPKU31009, SAPKU31010, SAPKU31011).


o ST-SER 620_2005_1 SP03 (SAPKITLO93)

- Support Package 03 provides multi-language options (Chinese,English and Japanese) for various sessions for the SAP SolutionManager 3.2.Support package 03 contains the language delivery. If you wantto process the multi-language SAP solution manager sessions inChinese or Japanese, start the report RSLANG20 after importingsupport package 03 to delete the old language load and activatethe new load.

o ST-SER 620_2005_1 SP01 to SP03 (SAPKITLO91, SAPKITLO92, SAPKITLO93)

- Note 863853The note contains important corrections for displaying issuesin session and reports.

o ST-SER 320 SP01 (SAPKITLO71)

- Note 787314If ST 310 SP16 (SAPKITL28) or higher has been installed, thetermination RAISE_EXCEPTION OBJECT_TYPE_NOT_FOUND occurs in thebackground job SM:EXEC SERVICES in the Early Watch Alertprocessing. The note prevents this termination from occurring.

- ST-SER 320 has been replaced by ST-SER 620_2005_1.

- Note 611536If you have not loaded any service definitions from SAPOSS fora long time, generation errors may occur when you importSupport Packages.

- ST-SER 311 was replaced by ST-SER 320.

06.09.2010 of 21





o ST-ICO 140 SP01 (SAPK-14001INSTPL)

- Note 826586The ASAP implementation roadmap delivered with ST-ICO 140 isnot displayed correctly. The report in the corrections to thisnote solves it.

o

-

SAP Solution Tools Plug-In (Software component ST-PI)

o This software component is relevant for the solution manager systemand for connected satellite systems.

o ST-PI 2005_1_[46C,620,640] SP 06, ST-PI 2005_1_[700] SP 04 andST-PI 2005_1_[710] SP02

- Note 1049478This note contains both reports /SDF/RSORAVSE and/SDF/RSORAVSH. Report /SDF/RSORAVSE collects once an hourstatistical data from Oracle statistics table V$SYSTEM_EVENTvia Batch Job 'BTCH_RSORAVSH' and report /SDF/RSORAVSH displaysthese data. If the reports are missing the Batch job dumps andif you do not implement this note you will receive shortdumpsevery hour in an SAP System connected to an ORACLE database

o ST-PI 003C_40B SP02 (SAPKITLPL2), ST-PI 003C_45B SP02 (SAPKITLPM2),ST-PI 003C_46C SP02 (SAPKITLPO2), ST-PI 003C_46D SP02 (SAPKITLPP2),ST-PI 003C_610 SP02 (SAPKITLPQ2), ST-PI 003C_620 SP02 (SAPKITLPR2),ST-PI 003C_640 SP01 (SAPKITLPS1).Not relevant for SAT-PI 003C_46B SP02 (SAPKITLPN2).

- Note 766425This note contains a correction for Report /SDF/RSORAVSE. Ifyou do not implement this correction when the report isexecuted, you will lose the historical database performancedata provided by Oracle. The report is an SAP expert tool thatcan be used by SAP Support if required.

- ST-PI 003C was triggered by ST-PI 2005_1.

Header Data

Release Status: Released for CustomerReleased on: 29.08.2008 14:43:15Master Language: EnglishPriority: Correction with high priority

06.09.2010 of 21


Category: Program errorPrimary Component: SV-SMG Solution Manager

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

Valid Releases

Software Component Release FromRelease

ToRelease

andSubsequent

ST 620 220 320 X

ST 700 400 400 X

ST-PI 40B 003C_40B 2005_1_40B

X

ST-PI 45B 003C_45B 2005_1_45B

X

ST-PI 46B 003C_46B 2005_1_46B

X

ST-PI 46C 003C_46C 2005_1_46C

X

ST-PI 46D 003C_46D 2005_1_46D

X

ST-PI 610 003C_610 2005_1_610

X

ST-PI 620 003C_620 2005_1_620

X

ST-PI 640 003C_640 2005_1_640

X

ST-PI 700 2005_1_700

2005_1_700

X

ST-SER 620 310 620_2005_2

X

ST-SER 700 700_2005_2

700_2005_2

X

ST-ICO 620 100 140 X

ST-SUP 620 310 320 X

TMWFLOW 310 320 320 X

Support Packages

06.09.2010 of 21


Support Packages Release Package Name

ST-PI 2005_1_46C SAPKITLQD6

Related Notes

Number Short Text

1161294 Name chg, SAP Solution Manager 4.0 to Solution Manager 7.0

1149742 SAP CQC Going Live Support

1022797 Maintenance Optimizer: Can not select product version

949293 Solution Manager: Solution Monitoring Related SAP Note

949292 Solution Manager: Service Desk Related SAP Notes

949220 Solution Manager: Implementation Scenario Related SAP Notes

930747 Service Delivery on SAP Solution Manager (Recommended Notes)

907768 General note for Change Request Management ST 400

770693 General note about Change Request Management 3.20

Attachments

FileType

File Name Language Size

SAR AITL422.SAR E 1 KB

+ sapnote_0000662441

Documents