Upgrade Projects with the SAP Solution Manager.pdf

Preparatory Activities

Upgrade Projects with the SAP Solution Manager- Overview of supported activities -

SAP AG 2003, Upgrade Jour Fixe October 2003 / 2

Upgrade RoadmapUpgrade Roadmap

Central Upgrade Functions

ProjectPreparation

Specify UpgradeProject

Specify UpgradeProject

Get Current ITLandscape

Get Current ITLandscape

Create andHold DeltaTraining

Create andHold DeltaTraining

ProductionPreparation

SAP Solution ManagerSAP Solution Manager – Upgrade Support Functions

Go Liveand Support

UpgradeProductionSystems

UpgradeProductionSystems

Issue Tracking / Monitoring / ReportingIssue Tracking / Monitoring / Reporting

UpgradeBlueprint

Document TargetProcesses

Document TargetProcesses

Check TestMaterials

Check TestMaterials

UpgradeRealization

Configureand Test

New Processes

Configureand Test

New Processes

SystemLandscapeReporting

SystemLandscapeReporting

Get Release-Specific

Process/FunctionDeltas

Get Release-Specific

Process/FunctionDeltas

Create and SendE-Learning Materialsand Learning Maps

Create and SendE-Learning Materialsand Learning Maps

Identify UpgradeViews, Upgrade

Rel. Conf.Settings

Identify UpgradeViews, Upgrade

Rel. Conf.Settings

Organizeand Perform Tests

Organizeand Perform Tests

Upgrade Activities Advantages

Create an Upgrade Project Increased clarity from organizing allactivities by project

Simplified project management

Assign Upgrade Roadmap Provide all required upgrade activities(guideline)

Provide product-specific upgradeinformation

2

ProjectPreparation

Upgrade-Blueprint

UpgradeRealization


Go Live andSupport


Determine Current IT Infrastructure Automatic capture of system data by centralsystem landscape reporting

Describe Business Processes Complete documentation of the businessprocesses always available

Plan Upgrade Project Minimization of planning effort required byintegrating the Upgrade Roadmap into MSProject


Design Business Processes in the New Release Complete documentation of the businessprocesses in the target solution

Automated identification and acceptance ofchanges (functions, configuration settings)in the target solution

Define Future IT Infrastructure Quick adjustment of target landscape accordingto current data

Define Security koncept Central documentation of new/changedauthorizations

Specify Test Strategy and Planning Central test case repository

Reuse of existing test cases with fewchanges

Plan User Training and Documentation Central documentation of requirements

Reuse of existing training materials

ProjectPreparation

Upgrade-Blueprint

UpgradeRealization


Go Live andSupport

3


Upgrade Project Infrastructure Quick availability of upgraded system data byintegration of SLD/TMS

Model Business Processes in New Release Central generation of componentupgrade/delta IMG views

Reduction of configuration effort byautomatic determination of upgrade-relevant configuration settings

Central configuration and documentation ofconfiguration settings

Acceptance Tests Central organization and performance oftests in the integrated Test Workbench


Integration and System Tests Central organization and performance oftests in the integrated Test Workbench

Training and Documentation Reduced effort for the production of role-based training materials

Cost reduction by the provision of self-teaching materials instead of classroomcourses

Quick update and availability

ProjectPreparation

UpgradeBlueprint

UpgradeRealization


Go Live andSupport

ProjectPreparation

UpgradeBlueprint

UpgradeRealization


Go Live andSupport

4

Upgrade Projects with the SAP Solution Manager- Guide -

Preliminary Activities ..............................................................................................................6

1. Project Preparation.............................................................................................................8

2.Upgrade Blueprint ............................................................................................................. 11

3. Upgrade Realization ......................................................................................................... 17

4. Final Preparation for Cutover ............................................................................................ 21

UseThis guide describes interaction between the upgrade methodology (Upgrade Roadmap) and projectsupport by the SAP Solution Manager. Upgrade supports the following use scenarios:

Use scenario 1: Upgrade project based on an existing projectIf you have already carried out a project, e.g. an implementation project, with the SAP SolutionManager, it can be the starting point for a subsequent upgrade project. You can copy the followingproject types.

Implementation project

Template project

Upgrade project

Use scenario 2: New upgrade projectIf you have not yet used the Solution Manager, you can also create an upgrade project withoutprevious data.

PrerequisitesGeneral

The SAP Solution Manager has been installed and configured. For further information, seethe SAP Solution Manager installation and configuration guide in the SAP ServiceMarketplace, http://service.sap.com/http://service.sap.com/solutionmanager -> InstallationGuides.

The latest SAP Solution Manager content add-on CD has been installed (ST-ICO xx), foryou to be able to use the current SAP reference scenarios, processes and process stepsfor the target release. The current content add-on is in the SAP Service Marketplace,http://service.sap.com/swdc, SAP Support Packages Support Packages and Patches

Entry by Application Components SAP Technology Components SAP SOLUTIONMANAGER SAP SOLUTION MANAGER 3.1 or higher SAP Solution Manager

Use scenario 1

You have already saved a project in the SAP Solution Manager.

http://service.sap.com/http://service.sap.com/solutionmanager

http://service.sap.com/swdc

5

You have used SAP reference scenarios, processes and process steps, to be able todetermine changes or updates to these reference elements with the comparison report

Use scenario 2

You are using the SAP Solution Manager without having previously created a project.

The focus of the upgrade project is to adjust operative processes of the old releases to the newrelease (upgrade configuration of the processes). You can also implement new processes and theirfunctions the same upgrade project; although it is better to create a separate implementation project,so this document only refers to the upgrade configuration.

The steps are the same for both use scenarios except where indicated, and activities labelled„General“ are valid for both use scenarios.

ProcedureThe SAP Solution Manager supports the following steps, which follow the upgrade roadmap closely:

Preliminary Activities

Project Preparation

Upgrade Blueprint

Upgrade Realization

Final Perparation for Cutover

This document does not repeat the documentation of the individual SAP SolutionManager functions. For detailed information, see the SAP Solution Manager onlinedocumentation.

http://help.sap.com/ -> area Documentation, subarea -> SAP Solution Manager

http://help.sap.com/

6

Preliminary ActivitiesUseThese are activities which are performed before the upgrade roadmap. You must perform them beforeyou can use a project-specific upgrade roadmap.

ProcedureCreate an upgrade projectProject administration (transaction: SOLAR_PROJECT_ADMIN)

Use scenario 1: Copy an existing project to an upgrade project...

1. Copy an existing project to a new project of type Upgrade Project (menu: Project -> Copy).

2. Verifiy the data which is to be copied into the upgrade project. If you are in doubt, copy all data –from the header data to documents and test plans except the roadmap data, because you candelete information in the upgrade project later.

Caution:

If you have used SAP reference scenarios and processs from the BusinessProcess Repository (BPR), in your implementation project, and wantcompare with these later, choose the option Adjust Target Project toOriginal of Source Project, when you copy. Otherwise you cannot compareand adjust existing processes to changes in the new upgrade release.

From this point onwards, you only change the upgrade project; the copiedexisting project is unchanged, for documentary purposes.

If you copy documents (e.g. project documentation), from the existingproject, assign a new KW context („Document Enhancement“) for theupgrade project. This ensures that the original of your existing project is notoverwritten by changes to the documents in the upgrade project.

Use scenario 2: Create a project

1. Create a project of type Upgrade Project (menu: Project -> Create). You use a newly-createdupgrade project analogously to an implementation project.

2. If you want to copy processes from a production solution landscape, assign the solutionlandscape here.

Assign upgrade roadmapProject administration (transaction: SOLAR_PROJECT_ADMIN)

You verify the upgrade roadmap assigned automatically to the project, and deselect those variantswhich do not have the desired upgrade path (Scope/Roadmap Selection tab).

7

Tip:

Choose the variant Generic Roadmap for the desired upgrade path. Only this selectiongives you access to transactions in the SAP Solution Manager which support yourupgrade, via accelerators.

The most up-to-date content add on in the SAP Solution Manager is automatically assigned to yourupgrade roadmap.

Specify the documentation types to be used in your project, e.g. Blueprint form to define yourrequirements of business processes, or authorizations to specify your requirements of the newauthorization concept. (Project Standards/Documentation Types tab).

ResultThe upgrade project is created and assigned to the roadmap with the required upgrade path.

8

1. Project Preparation Note:

The numbering of the headings used here corresponds to the names for phases, workpackages and activities in the SAP upgrade roadmap (V 3.0).

UseIn the project preparation, you analyze the actual situation, including determining the current ITinfrastructure and processes. You also perform the first activities to determine the target of theupgrade.

ProcedureThe SAP Solution Manager Upgrade supports the following upgrade roadmap work packages:

1.1 Current IT infrastructure

1.1.1.1 and 1.1.2.1 Document software and hardware components

Accelerator: Solution Manager System Landscape (transaction: SMSY)

Use scenario 1:Prerequisites:

The system landscape in the SAP Solution Manager has already been set-up in the implementationproject. This ensures that you use the current system data.

Optional: Perform analyses

You analyze the software and hardware components of the project which you are going tocopy into your upgrade project.

You can analyze the systems of a project or for the products which you plan to upgrade, inthe system landscape, in the Utilities Analyses menu. You get the current softwarecomponents with patch level, databases with patch level, operating system software andversions, and server information.

You can export the analyses to Microsoft Excel and put it in the upgrade roadmap asproject documentation. You base the target definition on it.

Use scenario 2:

Solution Manager System Landscape (transaction: SMSY)

Capture all systems which you currently use in your solution, including systems which are not to beupgraded. This ensures that you can later model and test your complete business scenarios andprocesses.

Note:

You can copy system data which you captured with the Transport Management System(until System 3.2: Option LIS, from 4.0 TMS) or the System Landscape Directory (SLD),automatically into the SAP Solution Manager (Goto Set-Up System LandscapeMaintenance menu). Schedule a background job for initial data capture. You have alsocaptured systems which are in your upgrade project but not in SLD, manually.

Project administration (transaction: SOLAR_PROJECT_ADMIN)Logical components are comparable to an installation, i.e. they manage a related set of systems withthe same release, for development, testing or production.

SAP Solution Manager 3.1:Define the logical components and product versions which are relevant in your upgrade

9

project (System Landscape/Systems tab), whether or not their logical systems are to beupgraded.

After SAP Solution Manager 3.2:Maintain this data centrally, in the Solution Manager System Landscape (transaction:SMSY). You can still create logical components in the project administration. Double-clickon them to go to the logical component landscape maintenance, where you assign yourcomponent systems and their use as logical systems (Current System Assignments tab).

Optional: You can now perform the analyses described in use scenario 1.

1.2 Description of the business processesUse scenario 2:

Tip:

Start straight away with the Upgrade-Blueprint rather than analyzing the businessprocesses. You can analyze and define the target of the business processes at the sametime.

The rest of section 1.2 applies to:use scenario 1:

1.2.1 Determination of the business processesAccelerator: SAP Solution Manager: Bus. Blueprint ((transaction: SOLAR01)

Check the existing processes in the Business Blueprint for completeness (Structure tab).

1.2.1 Determination of the business processes – 1.2.1.1 Creating the business process catalogOptional:

Catalog the business processes and process steps by their upgrade-relevance (Administration tabsubtab Keywords). Possible keywords are in the upgrade roadmap. Cataloging creates filters, withwhich you can restrict the process structure to upgrade-relevant processes. You can then analyzeprojects (transaction: SOLAR_EVAL) upgrade-specifically for the cataloged business processes.

1.2.1 Determination of the business processes – 1.2.1.2 Documentation of business processesVerify the existing project-specific documentation (Project Documentation tab), includingdocumentation of modifications and user developments, to ensure central access for existingdocumentation.

1.2.2 Determination of All Customer Developments and ModificationsAccelerators: SAP Solution Manager: Configuration (SOLAR02)

Check the customer-specific user developments and modifications, assigned for documentarypurposes (Development tab). This creates a consistent picture of your own developments anddocumentation.

1.3 Pre-Upgrade AnalysisPerform a high-level analsysis to determine the target of the upgrade.A detailed conceptional realization can be achieved in the SAP Solution Manager in the subsequentUpgrade-Blueprint-Phase.

1.4 General Project Management (Project Preparation Phase)

1.4.3 Project plan started

1.4.3.3 Project schedule

Optional:There are two ways of planning projects, activities, budgets and resources:

10

1. To maintain project activities along the Upgrade Roadmap, you can download the roadmapinto MS Project. Choose: Roadmap -> Download -> MS Project, maintain the planning data,and upload the resulting activity plan into the Roadmap (Projektdokumentation tab).

Difference from option 2:

You can assign resources in the roadmap, and download it with the roadmapstructure.

You can download just part of the roadmap structure by positioning on the structurenode under which you want to generate the structure as (sub)project plan.

Note:

Subsequent resource assignment changes in the roadmap CANNOT be copiedautomatically into the MS Project project plan.

2. Use of Accelerator: Model project plan upgrade roadmap German/English: You can downloadthe accelerators delivered, into MS Project, edit and update them, and upload them into theupgrade roadmap again (Project Documentation tab), for resource and project planning, sothat the plan is available to all project team members.

ResultThe business processes are captured in their actual status, documented and cataloged.

All project-specific plans are in the upgrade roadmap.

11

2.Upgrade BlueprintUseWhen you have analyzed the status for Use Scenario 1, adjust the business processes in the targetrelease.

For Use Scenario 2, perform the analysis and adjustment to the target release in one step.

Procedure2.1 Design of business processes in the new releaseYou automatically get the following support to determine new business processes and their scope.

Caution:

The prerequisites for the following functions must be fulfilled.

Supporting functionality Use scenario 1 Use scenario 1

Compare project (comparisonreport) Get changes, newdevelopments and deletions inthe process structure /functionsin the new release

Further Information

Can be used if you use SAPreference processes from theBPR. Cannot be used if youcreated the process structureonly from self-definedprocesses or a solutionlandscape.

Cannot be used

Determine and flag upgrade-relevant IMG activities in theproject

Get upgrade-relevant IMGactivities for the project

Further Information

Unrestricted use Can be used if IMGactivities, which can becompared, were assigned inthe project, in the analysis

Unused IMG objects in theproject:Get missing upgrade-relevantIMG activities for the project

Further Information

Unrestricted use Unrestricted use

2.2.1 Redesign of business processesAnalyze your business processes for validity in the new release (Structure tab).

Optional: If you have specified filters, you can restrict the process structure to the upgrade-relevantbusiness processes.

Use scenario 1:Comparison reports to determine changes to BPR business processes for the new release.

Prerequisites

In Project Administration (transaction: SOLAR_PROJECT_ADMIN):

1. You have defined or checked all logical components which are required to run the currentsolution with your scenarios, in the business process determination (system information fromthe implementation project).

2. You have used BPR SAP reference processes in your implementation project. Only thesestructure elements are compared with changed (new or deleted) business processes.

12

3. You have chosen the option Compare Target Project with Original of Source Project,when copying the implementation project into the upgrade project.

You have also defined the logical components with product versions, i.e. target releases, to which youwant to upgrade (System Landscape/Systems tab).

You can decide which business processes to copy, from the release notes or Statementof Directions.

If you do not know the target components for the upgrade, you can determine themas follows:

1. Open the BPR possible entries help in the Structure tab in the Business Blueprinttransaction (SOLAR01).You get information about all scenarios and their available versions.

2. Check the releases required by the scenarios, starting with the leading solution,e.g. SAP CRM 5.0. If scenarios are not highlighted, the system landscaperequired to run the scenario is not yet complete.

3. Copy the target releases found into the system landscape, as logicalcomponents (transaction: SOLAR_PROJECT_ADMIN, SystemLandscape/Systems tab).The logical components in your product versions must match the scenarioversions found.

You can also successively adjust your landscape to the current landschaft when thecomparison report has run, i.e. the reduce the target release versions of dependentlogical components, e.g. SAP ECC or SAP BW. The minimum release required by thescenario or business process may not be able to run, because it is below the releaselimit, e.g. a new transaction from SAP ECC 5.0, which is not yet in release SAP R/34.6C.

You can read the assignment texts, i.e. the names of transactions and IMG activities,from the connected system, at any time, in the Environment -> Refresh AssignmentTexts menu. If the objects do not exist, the first (but not complete) indication is that thereis no text name.

13

Procedure

1. Call the transaction Upgrade Project (until 3.2) or Compare Project (from 4.0)(SA_PROJECT_UPGRADE).

2. Choose at least the following selection options in the initial screen:

Structure to get changes in the process structure, e.g. new or deleted business processesor process steps

Transactions to get new functions to show how business processes are modelled in theSAP system

Gen. Documentation to get added or deleted SAP documentation

Configuration to get upgrade-relevant configuration documentation and new and deletedIMG activities

Comparison report results

Differences in your status analysis compared to the target release are indicated in the BusinessBlueprint (SOLAR01) and in the Configuration (SOLAR02), in both the structure and the tabs, by thefollowing symbol , if you have selected adjustment mode (Settings User-Specific...) .

Tip:

If you use a product more than once in your project, e.g. you have variousSAP R/3 systems with different releases in different places, you specify theproduct version against which you want to compare, in a prompt. Choosethe logical component with the target release of the upgrade (i.e. productversion), against which you want to compare.

If you copy new functions or changes into your project, you are promptedagain for verification.

Using the comparison report results/adjusting the business processes

You can compare these changes selectively per tab, with the Compare with Original pushbutton ,and copy them with the Adjust Sel. Entries pushbutton.

14

Notes:

In compare and adjust mode, you see the changes in a new version of the original, e.g. a newversion of a BPR process, and the changes made to the structure element in theimplementation project.

Changes to the contents of objects, e.g. changes in a BC Set or documenten, are NOTchecked.

You can prevent unwanted changes being made, with the Complete pushbutton, the Symbol disappears.

The comparison report does not handle new scenarios, which are added in the ProjectAdministration (transaction SOLAR_PROJECT_ADMIN).

Use scenario 2:

Analyze the status of your business processes in the target release (Structure tab) based on:...

1. SAP reference processes of the current release, from the SAP business process catalog (BPR)(SAP-recommended procedure)

Tip:

Always try to select business processes and scenarios for new solutions from the BPRfirst, and change and enhance them as required under this name, so that the referenceto the original BPR element is retained. You can only compare these structure elementsin subsequent upgrade projects.

2. existing processes in a solution landscape

3. customer-specific processes

4. processes in other projects

Document all relevant information as described under Describe Business Processes.

General (use scenarios 1 + 2)

SAP Solution Manager: Business Blueprint (SOLAR01)

Complete the project documentation with:

15

the requirements of new business processes (e.g. using the documentation type BlueprintForm)

Information about how you want to handle customer developments and modifications inthe upgrade. You can, for example, note in the existing project documentation, whether thenew functionality allows modifications to be discarded.

2.3 Definition of the future IT infrastructure

2.3.1 Definition of software components/ 2.3.2 Definition of hardware componentsProject analysis (transaction: SOLAR_EVAL)

You have already made a picture of your current IT landscape with the Documentation of the SoftwareComponents/Definition of Hardware Components. Adjust the list created in this step, to the targetrelease. Save the data as a reference in the upgrade roadmap project documentation

Project administration (transaction: SOLAR_PROJECT_ADMIN)

If you have not yet specified logical components of your upgrade project to your target release, do sonow (System Landscape/Systems tab):

You must use a second logical component, for example one component for the current release SAPCRM 4.0, and one for the target release SAP CRM 5.0 (and any associated components), becauseyou can no longer change the product version of logical components which are already used inprojects or solutions.

To use the comparison reports which check IMG activities for their upgrade-relevance, translate thescenarios and processes in your project structure into the new logical components: in the BusinessBlueprint (transaction: SOLAR01), menu: Edit Replace Log. Comp.

2.6. Security policySAP Solution Manager: Business Blueprint (transaction: SOLAR01)

Prerequisites:

You have created a new documentation type für authorizations/roles, in the project administration(Project Documentation tab).

Put authorizations for changed or new functions in your security concept. The SAP Solution Managerlets you describe authorization changes along the process structure using the previously createddocumentation type.

You can extract and verify the defined authorizations as an overall document, from theSAP Solution Manager, with the blueprint document functionality.

2.7 Test planningPerform high-level scoping of the test cases which you want to use for upgrade-relevant tests. Checkthe extent to which test cases from the old release are required, and need to be adjusted:

Are the test cases stored centrally (in the SAP Solution Manager) or decentrally (in thecomponent system to be upgraded)?

If decentral: Are the test cases only relevant for the new release so that they can be adjustedfor it?

If central: The Solution Manager can store manual and automatic test cases (eCATTs)centrally.

Use scenario 1: If a test case is valid for various releases, you can use it in the new release aswell, without any additional effort. If it needs to be changed, plan to copy and adjust theexisting test cases and link the new test cases in the SAP Solution Manager.

16

The SAP Solution Manager supports the updating of test catalogs and test plans in the configurationphase. See: Test strategy and planning in detail.

2.7 Planning of user training and documentationSAP Solution Manager: Business Blueprint (transaction: SOLAR01)

Use scenario 1:

You have assigned training materials in the previous project, which you now verify and use as thebasis to design upgrade delta training contents (Project Documentation tab).

Use scenario 2:

Create an upgrade delta training materials requirements catalog, along the process structure (ProjectDocumentation tab).

Use an extra documentation type to document the requirements. You can obtain a hard copy of therequirements catalog and training concept paper, with the blueprint document function for thisdocumentation type. This concept is the basis for creating training materials.

ResultThe business processes and required adjustments in the target release are documented for yourentire solution. Concepts for the temporary use of systems during the upgrade have been created.Authorization and training concepts and the test strategy have been specified.

17

3. Upgrade RealizationAfter the technical upgrade, preconfigure the business processes in the functional upgrades, and testthem in several test cycles.

Procedure3.2 Upgrade of the project infrastructure

3.2.3 Upgrade of non-production systems - 3.2.3.9 Carrying out technical post-processingactivities

Solution Manager system landscape (transaction: SMSY)

After the technical post-processing , assign the physical systems required for customizingin thefollowing actions:

1. Verify the validity of the RFCs (Client tab).

2. If you use SLD, and the system data has already been updated, first update the system data inthe SAP Solution Manager system landscape, in the background (SMSY, menu: Goto -> Set-Uup System Landscape). If you have maintained the system data completely manually, makethe changes manually or read the data by Read RFC (System Data Remote Read pushbutton)

3. Check whether the system is in the landscape components under the new product category,and with the correct product version, e.g. SAP ECC 5.0 instead of SAP R/3 4.6C. You mustassign the product version installed with the upgrade, manually in completely manuallymaintained systems, so that the system appears in the correct product category (InstalledProduct Versions pushbutton).


To be able to make automatic proposals for the configuration of business processes in the targetrelease, perform the following steps:

4. Specify the logical components for the target release if this has not yet been done.(See Define software and hardware components)

5. Link the logical systems of the upgraded component systems for the system role DevelopmentSystem, to the target component.

SAP Solution Manager 3.1:Project Administration, Systemlandschaft/Systeme tab

Starting with SAP Solution Manager 3.2:From the Project Administration to the Solution Manager System Landscape,Current System Assignments tab, by double-clicking on the logical component

6. Create upgrade views in the technically upgraded component systems (System Landscape/IMG Projects tab).

7. Replace the old logical components (source components) with the upgrade target components,e.g. SAP CRM 4.0 components with SAP CRM 5.0 components (tab: SystemLandscape/Systems, pushbutton Replace Log. Components). All scenarios, businessprocesses and process steps in the process structure are automatically set to the new release.You can now begin upgrade and delta customizing of your processes.

3.3 Mapping of business processes in the new release

3.2.1 Upgrade and delta information


SAP Solution Manager: Analysis (transaction: SOLAR_EVAL)

SAP Solution Manager: Configuration (transaction: SOLAR02)

18

Prerequisites

For option a. and b.: You have assigned the IMG activities which implement the existing businessprocesses, (e.g. by copying the IMG activities from the copied project, or manually).

Tip:

If you have already assigned IMG activities to your project, perform the optionsconsecutively.

a.

Determine and flag upgrade-relevant IMG activities in the project:You can automaticallycompare which of the IMG activities in the selected project view are relevant for theupgrade (transaction: SOLAR_PROJECT_ADMIN, System Landscape/IMG Projects tab,Distribute Upgrade Flag pushbutton).

Relevant IMG activities are automatically preselected for you in the configuration phase,in the Upgrade Flag column. If you do NOT want to copy the results automatically, youcan find the relevant IMG activities in option b. (No upgrade-relevant IMG activities werefound in the following screen-shot).

19

Note:

If you have also selected a configuration structure in the upgrade project, it is alsoautomatically compared.

b. Project views -> Assignment of IMG objects in project viewsThis report determines the upgrade-relevant IMG activities in the selected view which arealready in your upgrade project. The result is formatted in the project structure. Youcannot copy the comparison results from the report into the project automatically (ProjectAnalysis transaction: SOLAR_EVAL).

c. Project views -> Compare with views:This report determines the upgrade-relevant IMG activities in the selected project view,which are NOT in your upgrade project. These IMG activities are potentially relevant foryour upgrade project. You can check whether IMG activities have been forgotten for yourproject, and must be assigned, with this report (Project analysis transaction:SOLAR_EVAL).Assign the missing IMG activities to the processes to be configured.


Configure the upgrade-relevant IMG activities (Configuration tab).

Test planning

2.7.1 Creation of a test catalog


Use scenario 1:

Check the extent to which the test cases from the initially copied project satisfy the test strategy ofyour upgrade project. Change them if necessary, or add new ones (Test Cases tab).

Use scenario 2:Aassign test cases to your scenarios, processes or process steps, depending on the granularity, orcreate new ones, along the process structure. You can also upload existing test cases into yourproject (Test Cases tab).

20

2.7.2 Creation of a test plan

Test plan administration (transaction: STWB_2)

1. Create detailed plans for function, integration and performance tests in the integrated TestOrganizer.

2. Break these test plans into test packages to be performed by testers.

3. Assign the testers to the test packages.

You can divide up test plans and test packages so that applications, interfaces and the migrated dataused by the application can be tested.

The test packages are performed in acceptance tests.

2.7.3 Definition of the requirements of the test environmentProject Administration (transaction: SOLAR_PROJECT_ADMIN)

Assign the logical systems for quality assurance measures, now at the latest, to the system role:Quality Assurance).

SAP Solution Manager 3.1:Project Administration, System Landscape/Systems tab

Starting with SAP Solution Manager 3.2:From the Project Administration in the Solution Manager System Landscape (transaction:SMSY), Current System Assignments tab, by double-clicking on the logical component.The quality assurance system assigned appears automatically in your project landscape.

You use them in Acceptance tests.

3.4 Performance of acceptance testsAccelerators:


Tester work list (transaction: STWB_WORK)

The testers verify the business processes by working through their work lists. They can record sourcesand causes of errors in the integated problem message system, as well as returning a status.

The following functions give you an overview and accept the test results:

Status of upgrade project test results in the SAP Solution Manager: Analysis (transaction:SOLAR_EVAL): Test -> Analyze Project Status. You can export the status results to MSExcel.

Analysis across all test plans and test plan results used in the upgrade project, in the SAPSolution Manager: Analysis (transaction: SOLAR_EVAL): Test -> Analyze Project Status. Youare in the status info system.

Status analyse of test plans (in status info system Analyze Status pushbutton):You can create a list of relevant test plan results and information, such as test casedescriptions, notes, messages and the status change history, to accept the test (HierarchyList, menu: Settings -> Additional Information). You can also download this test data and use itfor acceptance.

ResultThe business processes have been configured for the new release and subjected to acceptance tests.

21

4. Final Preparation for CutoverUseYou prepare the production system upgrade here. The SAP Solution Manager supports integrationtests and training.

Procedure4.2 Integration and system test

4.2.1 Final integration testAccelerators:


Tester work list (transaction: STWB_WORK)

Perform integration tests by arranging test plans and test packages so that they cover completebusiness scenarios, reporting, interfaces, enhancements and background and output processing .

Proceed as described under Test strategy and planning and Acceptance tests.

4.3 Compilation of documentation and provision of trainingSAP Solution Manager: Configuration (transaction: SOLAR02)

Enhance existing training materials, or create new ones, based on the requirement concept createdunder Planning user training and documentation. You could use the documentation type Training. Putthe training materials which you create, in role-specific learning maps, and distribute them to the endusers.

Prerequisites:

To be able to create learning maps role-specifically, you have created roles for end users in the HROrg model.

1. Assign training materials along the process structure in the training materials tab.

2. Assign end user roles, i.e. positions or organizational units, to your processes or scenarios.

3. Put the training materials in Learning Maps.

4. Distribute the Learning Maps by role, to the end users.

5. Analyze Learning Map user feedback.

ResultThe final integration tests and end user training fulfill the prerequisites for upgrading the productionsystems.

Documents

Upgrade Projects with the SAP Solution Manager.pdf