Implementation With the Solution Manager_vedlegg Eksamen 2005

8/2/2019 Implementation With the Solution Manager_vedlegg Eksamen 2005

1/24

Implementat i on wit h the

SAP Sol ut ion Manager

Release 210


2/24

SAP Solution Manager 2

Copyright

Copyright 2002 SAP AG. All rights reserved.

No part of this publication may be reproduced or transmitted in any form or for any purpose withoutthe express permission of SAP AG. The information contained herein may be changed without priornotice.

Some software products marketed by SAP AG and its distributors contain proprietary softwarecomponents of other software vendors.

Microsoft, WINDOWS, NT, EXCEL, Word, PowerPoint and SQL Server are registeredtrademarks of Microsoft Corporation.

IBM, DB2, DB2 Universal Database, OS/2, Parallel Sysplex, MVS/ESA, AIX, S/390,AS/400, OS/390, OS/400, iSeries, pSeries, xSeries, zSeries, z/OS, AFP, Intelligent Miner,WebSphere, Netfinity, Tivoli, Informix and Informix Dynamic ServerTM are trademarks of IBM

Corporation in USA and/or other countries.

ORACLE is a registered trademark of ORACLE Corporation.

UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group.

Citrix, the Citrix logo, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame,MultiWin and other Citrix product names referenced herein are trademarks of Citrix Systems, Inc.

HTML, DHTML, XML, XHTML are trademarks or registered trademarks of W3C, World Wide WebConsortium, Massachusetts Institute of Technology.

JAVA is a registered trademark of Sun Microsystems, Inc.

JAVASCRIPT is a registered trademark of Sun Microsystems, Inc., used under license fortechnology invented and implemented by Netscape.

SAP, SAP Logo, R/2, RIVA, R/3, SAP ArchiveLink, SAP Business Workflow, WebFlow,SAP EarlyWatch, BAPI, SAPPHIRE, Management Cockpit, mySAP, mySAP.com, and otherSAP products and services mentioned herein as well as their respective logos aretrademarks or registered trademarks of SAP AG in Germany and in several other countriesall over the world. MarketSet and Enterprise Buyer are jointly owned trademarks ofSAP Markets and Commerce One. All other product and service names mentioned are thetrademarks of their respective owners.


3/24


Icons

Icon Meaning

Caution

Example

Note

Recommendation

Syntax

Typographic Conventions

Type Style Description

Example text Words or characters that appear on the screen. These include fieldnames, screen titles, pushbuttons as well as menu names, paths andoptions.

Cross-references to other documentation.

Example text Emphasized words or phrases in body text, titles of graphics and tables.

EXAMPLE TEXT Names of elements in the system. These include report names,program names, transaction codes, table names, and individual keywords of a programming language, when surrounded by body text, forexample, SELECT and INCLUDE.

Example text Screen output. This includes file and directory names and their paths,messages, source code, names of variables and parameters as well asnames of installation, upgrade and database tools.

EXAMPLE TEXT Keys on the keyboard, for example, function keys (such as F2) or theENTER key.

Example text Exact user entry. These are words or characters that you enter in thesystem exactly as they appear in the documentation.

Variable user entry. Pointed brackets indicate that you replace thesewords and characters with appropriate entries.


4/24


Implementation with the SAP Solution Manager - Background........................................................... 5Implementation with the SAP Solution Manager ................................................................................. 6Project Preparation .............................................................................................................................. 7

Project Administration ...................................................................................................................... 7Project Types................................................................................................................................ 8

General Data............................................................................................................................. 8Project Members....................................................................................................................... 9System Landscape Tab .......................................................................................................... 10Project Standards.................................................................................................................... 11

Creating the Business Blueprint (for Implementation Projects)......................................................... 12Business Blueprint.......................................................................................................................... 13Creating the Business Blueprint (for Implementation Projects) ..................................................... 14

General Documentation Tab ...................................................................................................... 16Project Documentation Tab ........................................................................................................ 17Structure Tab.............................................................................................................................. 18Administration Tab...................................................................................................................... 18Transactions Tab........................................................................................................................ 19Problem Messages Tab.............................................................................................................. 20

Realization ......................................................................................................................................... 21Configuration .................................................................................................................................. 21

Configuration Tab ....................................................................................................................... 22Create/Edit Test Cases............................................................................................................... 23

Test Organization........................................................................................................................... 23Test Plan Management............................................................................................................... 24


5/24


Implementation with the SAP Solution Manager -Background

The SAP Solution Manager focuses on the implementation of business scenarios and processes. Itprovides functionality to describe, document, customize, and test scenarios and processes.

After the implementation project, you can use the SAP Solution Manager to administer your systems.

The SAP Solution Manager provides this functionality centrally in the client system landscape, that isthere is one SAP Solution Manager for each client system landscape. The SAP Solution Manager isused for all phases of implementation and operation.

You can use the SAP Solution Manager in system landscapes whose components

have been created by SAP based on the Web Application Server

are from SAP and ARE NOT based on the Web Application Server

are not from SAP

The graphic below shows the position of the SAP Solution Manager in a heterogeneous client systemlandscape.

SolutionManagerSolutionManager

Non-SAP ComponentsNon-SAP Components

SAP Components

based on ABAP

Non-ABAP ComponentsNot based on ABAP

In the graphic, the components and systems are represented as colored circles; the green linesconnecting the components represent cross-component business scenarios and processes. Oneexample is the Bill to Cash scenario. You can configure this scenario to run in a R/3, a CRM or anAPO system. In a system landscape, the SAP Solution Manager is the system in which scenarios and

processes like Bill to Cash are described, that is, where the relationship between the business andthe system view is stored. Thus the Solution Manager contains the information about which processstep will run in which system. You can also use the SAP Solution Manager to describe scenarios andprocesses that only run in one component.


6/24


The business and the technical views are mapped using a three-tier hierarchy, consisting of thefollowing levels:

Scenario

Process

Process Step

Only the Process Step contains information about which component this step is assigned to. Thescenario and process levels are business hierarchy levels.

SAP continually provides information about the implementation of scenarios and processes for theSAP Solution Manager. This information is delivered in separate Add-Ons which can be imported intothe SAP Solution Manager system. For more detailed information about the scenarios and processes,visit the SAP Service Marketplace.

The scenarios and processes provided by SAP can be customized during the implementation phase.Simple changes to the predefined scenarios and processes, such as renaming the process steps, arejust as straightforward as replacing entire processes or even completely redefining scenarios andprocesses.

The Blueprint Phase is intended to build a complete business-oriented structure. This project structureserves as a basis for subsequent phases such as configuration and testing; this structure is notchanged but will be enhanced with information such as documentation, preconfigurations, and testcases. An implementation project with the SAP Solution Manager aims to store all the informationcreated in business-oriented structures and to make this information available to all project teammembers beyond the end of the implementation project, in the operation phase.

In addition to implementation projects, you can also use the SAP Solution Manager to develop yourown solutions. You can create preconfigurations, which in turn can serve as a starting point for newimplementation projects. One example of this type of reuse is the global rollout, where it is decided atcompany headquarters which scenarios and processes will be implemented at all the subsidiaries.With the SAP Solution Manager, a company can both create and implement the template in thesubsidiaries' projects.

Implementation with the SAP Solution Manager

Use

Using the SAP Solution Manager for evaluation and implementation

You can use the SAP Solution Manager to evaluate and implement your e-business solution.

Using SAP Solution Manager to create preconfigured content (templates)The solution you create in the SAP Solution Manager serves as a template for your implementationproject. The solution contains a package of reusable preconfigured content (documentation,preconfiguration, and test cases). The following section describes the typical process flow for animplementation project.

You can also use the SAP Solution Manager to support the operation of your systems. Formore information, see the SAP Solution Manager online documentation.

Procedure

Use the SAP menu to navigate through the SAP Solution Manager. By working through the structuresystematically, you follow the typical project phases of the ASAP methodology for implementationprojects.


7/24


Project Preparation

1. Define your project in the Solution Manager. You enter administrative data in the ProjectAdministration [Page 7] transaction, for example, details of project dates and resources.

2. Define the project scope [Page 9]. Determine which e-business solutions you will evaluate andimplement in the course of your implementation project. If you decide to use e-business solutions,

you can select one or more business scenarios as a starting point.3. Define the system landscape [Page 10] you require to implement your e-business solution.

Business Blueprint

4. Define a Business Blueprint [Page 13] by documenting the organizational units, master data,business scenarios, and business processes you require for your e-business solution. During thisstage of your project, read the documentation supplied by SAP and partners, create your ownproject documentation and assign individual process steps to transactions.

Realization5. Configure [Page 21] your business scenarios in the development systems.

6. Check the test cases delivered with your solution and assign further test cases to individualprocesses and process steps.

7. Organize tests [Page 23] using the test cases selected during configuration.

Project Preparation

UseYou perform all central activities in the project preparation transaction in order to:

Structure and organize a project

Project administration in the Solution Manager supports you during project preparation andenables you to carry out all administrative tasks relevant for the entire project.

Access standard implementation information for SAP scenarios.

Project Administration

UseAll central administrative tasks relevant for the project are carried out in the project administrationtransaction of the Solution Manager including:

Creating projects

Determining general data at the beginning and at the end of the project

Defining the project scope

Assigning project members

Defining the project language

Defining project standards (status values, documentation types, keywords)

Specifying transport request information (depending on the project type)

Any existing projects are automatically displayed in the project overview of the Solution Manager.


8/24


Access the project administration transaction with SOLAR_PROJECT_ADMIN.

Project TypesDefinition

The project types delivered with the SAP Solution Manager allow you to differentiate between differenttypes of projects. You can use the SAP Solution Manager to create the following projects:

Implementation Project

An Implementation Project is based on a selection of business processes in a mySAP.comlandscape.

There are two options for creating an implementation project:

Creating a project structure with one or more SAP or partner scenarios as a template

Creating your own project structure

Template Project

A project is used to create a template (template and solution).

SAP solutions can be used like partner solutions as templates for creating your solution. Thefollowing enhancements can be carried out when creating a project template:

Changing and adding documentation

Defining and adding preconfigured data, such as BC Sets, test cases, or IMG activities

Editing the scenario structure(s) delivered by SAP

Solution projects in contrast to implementation projects - can be transported and are ideal

for SAP partner solutions or for large enterprises carrying out a global rollout.

Integration

The project type you select for your project directly influences the edit options available to you in theindividual project phases (Business Blueprint, Realization).

General Data

Use

You enter the administrative data for your project on the General Datatab.

Prerequisites

You have defined the following data in the project administration transaction in the SAP SolutionManager:

Project

Project type

You are in the project administration transaction in change mode.

FunctionsYou can enter the following data on the General Datatab:

Person responsible


9/24


The responsible person must exist in the project administration of the SAP System. You canuse the possible entries help to change the responsible person.

Project language

When you choose a project language, all language-dependent information for this language(project documentation and status information) is made available to project members. This is

independent of the logon language of the project member.

When a project member creates a new project, the system displays the user name andthe project language for the relevant project member in the Responsible MemberandProject Languagefields. These entries are not fixed and can be changed at a later date.

Status

The default values for the status are set on the Project Standardstab.

Plan Data

This tab allows you to enter the dates for the planned project start and finish as well as the

work required in man days (MD). Actual Data

This tab allows you to enter the dates of the actual project start and finish and the actual workcarried out in man days (MD).

The planned data and the actual data represent the time plan for the entire project. Anydates entered for individual process steps in the Business Blueprint or Realization phasesmust lie within the time frame set on the General Datatab.

The remaining work required is calculated from the difference between the planned dataand the actual data and generated as a percentage in the Completedfield. You can

manually change the remaining work entry at any time.

Project Members

Use

You use this tab to create and update the list of team members for your project. Any number of projectteam members can be assigned to each project. The project leader makes this assignment in theproject administration transaction.

You can use users defined in user administration and generic users (users not created in the useradministration) for your user assignments. To check whether the project members listed on this tabare already present in the user administration of your SAP System, choose the Check against usermaster recordbutton. Team members who are not SAP users are highlighted in the list.

Prerequisites


Integration

Members of staff assigned to the project on this tab are displayed in a selection list when you entertask-specific administrative data on the Administrationtab in the Business Blueprint or configurationtransactions.


10/24


Activities

1. Enter the name of a project member in the Project Membercolumn. You can use the possibleentries help (F4) to find and assign employees you have already entered in user administration.

You can also assign employees to the project directly after you have entered them in useradministration. To go to the user maintenance transaction, double-click on the name of anemployee, or choose the User Administrationbutton. Authorization for the usermaintenance transaction and for changing user data is dependent on your project role andthe corresponding authorization profile.

2. You can enter a description of the project member in the Name/Descriptionfield. This field is onlyavailable for internal project use. You can use this field, for example, to document in % theassignment of an employee to a subproject, project group or task. If the user is recognized in theSAP System, the user name appears here by default.

System Landscape Tab

Use

You define the system landscape for a solution or mySAP.com project on the System Landscapetab.This allows you to manage all the logical systems you need for your project centrally.

The setting up of a system landscape, in other words, the maintenance of logicalcomponents AND logical systems, is highly recommended. In this way, you ensure thatonly the scenarios/processes from the Business Process Repository that also run on thecomponents you have maintained can be selected and displayed in the BusinessBlueprint and in the configuration. Release information is taken from the components atthe start of a session. In this way, you can make sure that the most current releasesuitable for your system landscape is always on offer.

As you are creating the Business Blueprint in the system role Development/Customizing,you should have maintained the data for these systems. You can add the systems forother system roles during the course of the project.

You cannot maintain the system landscape for external components (with the exception oflogical components).

Integration

The following functions are available depending on the system landscape you define:

Accessing the business content in the component systems

Depending on the logical system you have defined, it is possible to navigate during theRealization [Page 21] phase from the Solution Manager to corresponding systems, forexample, demo or development systems, to look at the available business content(transactions, BC Sets, CATTs, reports etc.). You can select the logical system in each phaseby selecting the appropriate system role.

Generate IMG projects in the component systems and distribute central project data

Generate a business process graphic

You can generate graphics at process level that clearly show in which logical components theprocess steps for a process run.


11/24


Prerequisites

You have set up both the Landscape Infrastructure Server (for systems within the transport domain)and enhanced maintenance of logical systems (for systems outside the transport domain). Thisenables you to use the possible entries help (F4) when you select your logical systems.

Activities1. Select a logical component.

2. If required, define other logical components and select them as well.

3. Select already available instances and the corresponding logical systems or redefine them.

4. Check if the system landscape is completed. You may also consider the Where-Used-List forinstances and logical systems.

5. Generate the project IMGs and distribute the central project data in the component systems.

Project Standards

Use

Standard values for status, keywords and documentation types for your project are all set in the sameway in the project administration transaction. If no values have yet been assigned to a project, theproject administrator can use the project template, which contains project-independent status values,keywords and documentation types.

The values in the project template are available to all projects. The project administrator decides whichvalues should be used and assigns values to the project from the project template.

At the time of delivery, every project type is assigned to a template containing a number of values forstatuses, priorities and documentation types. You can adapt the project template to suit your projectrequirements.

Integration

The values set on the Project Standardstab for solution and template projects are available as defaultvalues on the following tabs in the Business Blueprint and configuration transactions:

Documentation (Gen.)- documentation types and status values

Proj. Documentation- documentation types and status values

Administration- status values

Prerequisites

The project member responsible for creating and changing status values, keywords, anddocumentation types must have the corresponding project role and the S_PROJECTSauthorization.


Functions

There are three tab pages on the Project Standardstab:

Status

Documentation Types

Priorities

Status Valuestab

Status values provide you with information on the status of your project. Status values consist of a ten-character status ID and a description of the status. Status IDs should be appropriate and have someconnection to the actual status value.


12/24


The following status values are delivered:

Status Description

01 Open

02 In progress

03 Finished

04 Not relevant

All new values appear in the Unused Status Valueslist and can be assigned to the project.

Keywordstab

You can define keywords for your project, which you can search for later in the Project Analysis [Page]transaction for IMG projects (Customizing projects). Keywords should be as concise as possible.

Documentation Typestab

Various documentation types are available for all types of projects. You can use documentation typesto document the implementation, creation of templates, or upgrade of your SAP System and to

document definition of your solution. You can use the various documentation types delivered by SAPas templates to structure your project documentation. You can also create your own documentationtypes for:

Minutes or decisions

Business Blueprints

Problem or error messages

Each documentation type has a unique ID. There are two types of project documentation:

Project-specific documentation

This documentation type is only valid for the current project.

Cross-project documentation

You can identify this documentation type by the Global Doc. indicator. The indicator isavailable for all projects and appears automatically in the Project Documentation Typeslist onthe Documentation Typestab.

You can create project documentation templates for each documentation type.

Creating the Business Blueprint (for ImplementationProjects)

Use

Creating a Business Blueprint [Page 13] for the implementation of your mySAP.com solution allowsyou to document the business processes in your enterprise and decide which processes you shoulduse in your SAP-System.

You continue to use the Business Blueprint in the Solution Manager during the realization phase(configuration and testing). You reuse the project structure you created in the Business Blueprintphase for the configuration and generation of test plans. You can also display, change, and enhanceproject documentation created during the Business Blueprint phase during configuration.

Prerequisites

You want to implement a mySAP.com solution. You have completed the Project Preparation [Page 7].You have defined an implementation project and a system landscape in the project administration ofthe SAP Solution Manager.


13/24


Procedure

1. Build a Blueprint Structure using predefined parts of structures.

2. Check the Business Blueprint structure and the corresponding business scenarios, businessprocesses and process steps.

3. Decide which business scenarios, business processes, and process steps you want to include inyour Business Blueprint. If required, extend the processes and process steps or adapt the namingof individual processes to suit your enterprise.

4. Create the project documentation and file it in the Business Blueprint.

5. Assign transactions to individual process steps. This allows you to specify which transactions inthe system correspond to the process steps in your enterprise.

6. Print the Business Blueprint document.

7. When the Business Blueprint is complete, you can start to set up the development systemlandscape. The installation guide takes you step-by-step through the tasks required for the setupof the development system landscape.

ResultYou have created your Business Blueprint and set up your development system landscape. You canreuse the Business Blueprint and the project structure to configure and test your business processes.

Business Blueprint

Definition

A Business Blueprint documents the business process requirements of an enterprise.

Use

The Business Blueprint provides an enterprise with a general understanding as to how its businessprocesses should be mapped in one or more SAP Systems. The purpose of the Business Blueprint isto document in detail the scope of business scenarios, business processes, process steps, as well astaking into consideration the requirements of a mySAP.com implementation.

Structure

A Business Blueprint consists of the following structure items that are organized in a hierarchicalstructure:

Organizational units

Master data

Business scenarios

Business processes

Process steps

You assign content, for example, project documentation, Business Configuration Sets, or transactionsto individual structure items in the SAP Solution Manager.

It is also possible to create structure items for organizational units and master data belowa business scenario. You only use these structure items, if the organizational units andmaster data are relevant exclusively for the business process above them in the structure.


14/24


Business Blueprint Definition (for ImplementationProjects)

Use

Definition of the Business Blueprint allows you to document the business processes in your enterprisethat you want to use in your SAP System. You create a project structure in which relevant businessscenarios, business processes and process steps are organized in a hierarchical structure. You canalso create project documentation to assign to individual scenarios, processes or process steps. Todefine how your business processes should run in your SAP Systems, you then assign transactions toeach process step.

Definition of the Business Blueprint provides you with a detailed description of your businessprocesses and system requirements. You can also print out the Business Blueprint document. Theproject documentation and the project structure that you use during the Business Blueprint phase canalso be put to further use during configuration and test organization.

When you configure your business processes, the system displays the project structure you

created for the Business Blueprint. You can use the Business Blueprint project structure as a pointof orientation during configuration.

You can also display and edit the project documentation from the Business Blueprint phase duringconfiguration.

The project structure from the Business Blueprint forms the basis for all test plans that you createduring test organization. The transactions that you assign to process steps in the BusinessBlueprint are added to test plans during test plan generation. The transactions can be processedas manual test cases as a means of testing each transaction.

Integration

You define a Business Blueprint after you have created your project. The Business Blueprint is the

prerequisite for the realization phase in which you configure and test your business processes.

Prerequisites

You have created a project. You have set up an evaluation system landscape for the projectpreparation and Business Blueprint phases.

You can use the Implementation Guide for that purpose.

Functions

The project structure is displayed on the left screen area. The structure is organized in a hierarchy.After you have finished working on the structure, it will contain the following items:

Organizational units

Master data

Business scenario(s)

Business processes

Process steps

The structure allows you to:

Execute standard transactions that are assigned to individual process steps


15/24


Executing a transaction opens a new screen (session). Executing a transaction has noeffect on the appearance of the initial screen of the Business Blueprint transaction. Afteryou have closed the transaction, the Business Blueprint screen is unchanged.

If you create your own scenario, you have access to all the functions you need to create your ownproject structure.

The tabs on the right screen area provide you with the following functions:

General documentation

This tab displays all the documentation and/or Collaborative Business Maps delivered by SAP. Youcan reorder or download the documents, or copy them for processing to the Project Documentationtab.

For more information, see General Documentation Tab [Page 16].

Project Documentation

You can use this tab to create and edit your own documents.

See Project Documentation Tab [Page 17] for more information.

Structure

This tab allows you to add scenarios, business processes and process steps or rename existingstructure items.

See Structure Tab [Page 18] for more information on structure changes.

Administration

You can use the Administrationtab to enter general administrative data for the Business Blueprintphase, for example, project status, assigned employees, or the planned work and actual work required

for the phase.See Administration Tab [Page 18] for more information.

Transactions

On the Transactionstab, you can:

Assign or delete assignment of transactions, programs and other items to process steps

Define transactions, programs and other items as standard transactions for process steps

See Transaction Tab [Page 19] for more information on transactions.

The Configurationand Test Casestabs are not available in the Business Blueprint phase.It is possible to change the order of the tabs.

Problem messages

On the Problem Messagestab you can create, display, and edit problem messages. See ProblemMessages Tab [Page 20] for more information.


16/24


General DocumentationTab

Use

The Documentation (Gen.) tab displays documents delivered by SAP and scenario diagrams, for

example, C-Business Maps. These documents take the form of scenario descriptions, installationguides or interface descriptions.

Choose SettingsUser Specificto determine whether to display the documentation onthe General Documentationtab or in a separate window.

You can also determine which data should be saved.

If you choose the option Save Automatically, data will automatically be saved when youchange the structure element. You do not have to choose Save.

If you do not select the option Save Automatically, the data is saved provisionally but isonly saved to the database when you choose Save.

Integration

The documents delivered by SAP are stored in the Knowledge Warehouse, which is available to youafter installation and setup of the SAP Solution Manager.

Functions

This tab provides the same functionality for Template Projecttypes as the Project Documentation Tab[Page 17].

The functionality for implementation projects is limited on this tab. You can display, export, and sortdocuments. To copy general documents for further processing and use in your project documentation,select the Copy Documents to Project Documentationtab. By choosing the Where-Used Listtab, you

can check which other structure elements are assigned to a document.

In template and implementation projects, the documentation of relevant standard transactions isdisplayed at process step level. (In order to do so, however, you have to install the SAP Library. In thisway, you will also have access to the application help for the transaction in corresponding componentsystems).

Activities

To copy a document from the General Documentationto the Project Documentationtab:

1. Choose one or more documents by selecting the corresponding row(s).

2. Choose Copy Documents to Project Documentationtab.

3. Enter a documentation type for the document in the Copy Documents to Project Documentationtab.

You define valid documentation types for your project in the project administration transactionon the Project Standards [Page 11] tab.

4. Choose Copyto transfer your entries to the structure. The documents are copied to the ProjectDocumentationtab, where you can access and edit them. Any changes made to the copieddocuments have no effect on the original texts.


17/24


Project Documentation Tab

Use

You can use the Project Documentationtab to create, add, display or delete specific project

documentation on individual structure items for your implementation project.

By choosing SettingsUser Specific, you can determine whether you want thedocumentation to be displayed on the Project Documentationtab or in a separate window.

You can also determine which data you want to save.

If you choose the option Save Automatically, data will automatically be saved when youchange the structure element.

If you do not select the option Save Automatically, the data is saved provisionally but isonly saved to the database when you choose Save.

IntegrationThe documents are saved in the Knowledge Warehouse and are available to you when working withthe SAP Solution Manager.

Functions

On the Project Documentationtab, you create your project documentation. You assign a documenttype to all documents you create. Depending on the document type, a document template is called up.You can only use document types that either have a document template or a file name extensionsupported by the SAP Solution Manager. If a document type has no template or file name extension,the text editor is started.

When adding a document (Link to Solution Manager Document, Copy of Solution Manager Document,

Upload File, Web Link), all documentation types can be used regardless of whether they have atemplate or file name extension.

You can add to the documentation types delivered by SAP on the Project Standards [Page 11] tab inthe Implementation Projects Administrationtransaction.

Using the icon Insert Document, you can:

Create new documents

Link to documents whose originals are assigned to other structure elements in the SolutionManager

Copy documents whose originals are assigned to other structure elements in the SAP SolutionManager and that you can change independently of the original document

Upload a file

Create a link to a web site

To delete project documentation or assignment of documentation to a structure item, choose Delete.For documents created as a link to another document, both the row in the table and the link aredeleted. If the document to be deleted is the only instance of this document, the document owner(author) has the authorization to delete it.

To find out how many structure items a document is assigned to, choose Where-Used List. You canalso display the document attributes or export documents.


18/24


StructureTab

Use

You can use the Structuretab to create or change the project structure in which your organizational

units, master data, business scenarios, processes, and process steps are listed.

Integration

The project structure is reused for configuration and test organization. See Creating the BusinessBlueprint [Page 14] for more information.

Functions

The Structuretab allows you to:

Add new business processes and process steps

Adapt names for scenarios, business processes and process steps to suit individual enterprises

Remove scenarios, business processes and process steps from the project structure

For organizational units, master data, and process steps, you must also specify to which component inyour mySAP.com system landscape the structure item belongs.

You cannot specify a component for business processes, because some businessprocesses run across components. Assignment of components is therefore carried out onthe process step level.

AdministrationTab

Use

You can use the Administrationtab to enter current project data for each structure item in the projectstructure.

You can record the following project data:

Status

Plan Data

Start

End

Working Days (in man days - MD)

Actual Data

Start

End

Working Days (in man days - MD)

Remaining (remaining work required)

Assigned Project Members

Name/DescriptionData entered only applies for the current project phase.


19/24


A structure item in the Business Blueprint phase has the status Completed, after allactivities in this phase for this structure item have been completed. The status for thisstructure item returns to Openin the realization phase.

PrerequisitesIn the course of defining the Project Standards [Page 11] in the project administration transaction, youhave checked the status and when required adapted it accordingly. You have entered all employeesassigned to the project during Project Preparation [Page 7]. The values you have checked or adaptedare displayed on the Administrationtab as default values.

The functions available on the Administrationtab are dependent on the project role andassociated authorizations assigned to a project member.

Functions

Status

You can manually enter the status value or select a suitable value from the dropdown list.

Dates

You can enter the planned and actual dates manually or select the corresponding date from thecalendar. An error message appears, if you enter dates outside the time frame for the project. Formore information, see General Data [Page 8].

Effort

The planned and actual effort (required work) have to be entered manually.

Project MemberYou can either manually enter project members or select a project member using the possible entrieshelp. You can only assign tasks to a particular employee in the Business Blueprint and realization phases, if you have included this employee in the list of project members in the project preparationphase.

You can use the Name/Descriptionfield to enter further information on the project member, forexample, first and last name, assignment to a subproject, or degree of assignment.

Copying data to subitems

Choose the Copyicon to copy selected project data, for example, status to all subordinate structureitems.

History

This function allows you to record changes to data on the Administrationtab. The correspondingchange record is logged only after you have saved your changes.

TransactionsTab

Use

You can assign transactions, programs and other items to a process step on the Transactionstab.

This defines the process step for the SAP System.


20/24


Integration

The selected transactions are offered as test cases in the Solution Manager, when you generate a testplan.

Prerequisites

In order to be able to assign transactions to process steps, you have to define a System Landscape[Page 10] in the project administration transaction.

Functions

Assigning and executing transactions, programs, and other items for a processstep

You can assign the following to individual process steps:

Transactions

Programs

Predefined URLs from directory

You can also assign URL objects that you have predefined in the Object Navigator(Transaction SE80).

Web addresses or files

You can assign Internet/Intranet links to a process step by entering a web address and a textfor the link. You can also include URL addresses with variable query strings. Entering a filename is possible, if the browser you are using supports the application.

Double-click the transaction, program or other item to start or open it in a new session.

Setting transactions, programs, and other items in or out of scope

To include an item in the project scope, select the checkbox in the In Scopecolumn. Deselect thecheckbox to remove the items from the project scope that are no longer required.

Setting a default transaction

Select the checkbox in the Defaultcolumn to specify which transaction, program or other item shouldbe executed when you choose the Executesymbol next to the corresponding process step. If you donot set a default, the Executesymbol will start the first object in the list on the tab.

Template

The Templateindicator is activated when an item is part of an SAP or partner project. The indicator isnot activated for items you have added during the course of your implementation project.

Problem Messages Tab

Use

You can create and display problem messages on the Problem Messagestab. Create a problemmessage if you come across errors in the project documentation, configuration, or processing of testcases in the Business Blueprint [Page 14] or Configuration [Page 21] transaction.

Integration

The problem messages are all stored and processed in one system. Both the SAP Solution Manager

and the Support Line Feedback have access to this system.


21/24


Prerequisites

In order to be able to create problem messages, you have to set up a system for storing the messages(Issue Management). You can either set up an entirely separate system or administer problemmessages in the same system that the SAP Solution Manager is installed in. Further information canbe found in the note 0408398.

You can create settings for the message collection system in the Customizing transaction of the SAPSolution Manager under the tab SAP Reference IMGSAP Web Application ServerSAP Solution

ManagerSet RFC Connection for Message Collection System; Create Number Range for BasisMessage; Maintain Roles for Message System. Further information can be found in the InstallationGuide.

Functions

You can:

Display or change problem messages

Create new problem messages Attach documents to problem messages

The problem message will be forwarded to your collection system and then processed.

Realization

Use

In this project phase, settings are made and tested for the master data, organizational units and

business processes selected in the Business Blueprint phase.

Prerequisites

The Business Blueprint has been completely created and approved.

The development system (DEV) is available.

Result

You have made and tested all required system settings.

Training materials and end user documentation have been created based on the configured scenario.

Configuration

Use

This project step configures the process requirements specified in the Business Blueprint phase, in thesystem.

Prerequisites

You have selected scenarios and processes, or created your own processes using the BusinessProcess Repository, in the Business Blueprint phase.

You are now in the Realization phase and have called the Configurationtransaction.


22/24


Functions

This project task comprises the following steps:

Assign Transactions/ProgramsYou can call assigned transactions, add new ones or remove superfluous ones from the projectscope, in the Transactionstab.

Edit BC SetsDisplay the contents of the assigned BC Sets and delete superfluous BC Sets from the projectscope, in the Configurationtab.You can activate one BC Set, or all BC Sets assigned to a process.You can create new BC Sets for project or company-specific settings, which you e.g. want to usein a group rollout or to create your own solution, in the application system, and assign them in theSolution Architect.

Assign IMGYou can see the settings made by BC Sets, in the Implementation Guide, and edit the remainingsystem settings which could not be made entirely by BC Sets.

Edit test cases

You can make initial function tests after the configuration. You can also run CATTs to see how atransaction works, and create test cases.

You document the settings relevant for the configuration along the project structure, in the ProjectDocumentation [Page 17] tab.

Configuration Tab

Use

You can access the various Customizing tools from the Configurationtab to make your systemsettings or use preconfiguration.

You can create project templates and add to your own documentation using preconfiguration.

Integration

The Configurationtab is the central point of access for making system settings for your implementationproject. You can enter the transactions for editing BC Sets and the Implementation Guide or thetransaction for importing Add-Ons and maintaining CATTs.

Prerequisites

In the Implementation Project Administrationtransaction, you have created a project and defined a

system landscape [Page 10].In the Business Blueprint [Page 12] transaction, you have created a reference structure for yourproject.

Functions

In each of the application systems, you can create new BC Sets, assign a reference structure,view the content of the assigned BC Sets, and delete the assignments of BC Sets that you nolonger require.

You can activate an individual BC Set, or several assigned BC Sets.

You can view the settings made by BC Sets in the Implementation Guide (IMG), and edit theremaining system settings that could not be performed entirely by BC Sets.

You can assign CATTS to process steps in order to make your system settings or usepreconfiguration.


23/24


You can store documentation for individual configuration steps. You can also assign existingdocumentation and create new documentation.

You can also import Customizing contained in the Add-On transports to your system.

Test Cases TabPrerequisites

Various types of test cases can be assigned in this tab. The test cases assigned here can be used asthe default test organization [Page 23] value when you create test plans in an implementation project.

Procedure

Create test cases

1. Choose a component.

2. Choose the Createpushbutton.

The system calls the Test Workbench in the selected component system.

3. Enter the data required to create a new test case.

4. Save your entries.

Insert existing test case

1. Choose a component.

2. Enter the name of a test case. You can search for test cases with the F4 help.

Run test

1. Select the test case (CATT) which you want to run, in the list of test cases already assigned to a

process step.

2. Choose the RunTestsymbol.

For further information about test cases and the Test Workbench, see the Test Workbench componentin the SAP Library.

Test Organization

Use

A test organizer can create one or more test plans for the projects which are assigned to him orher. He or she can also edit test plans and assign test packages to testers.

The test organizer can get test plan status information.

The Test is performed with the Test Workbench. The Test Workbench is the SAP testenvironment and is in all SAP systems. A tester calls the Test Workbench and gets anoverview of the test cases assigned to him or her in his or her worklist. He or she canperform tests, set processing status and note open items.

Prerequisites

You must have created a Business Blueprint and configured your systems.


24/24

Procedure

Test Organization comprises the following steps:

1. Your project and any existing test plans are displayed in the Test Organization initial screen.Create test plans. When you create test plans, all test cases which were assigned to the project inthe Configurationare selected by default. You can deselect test cases from this default selection

and then generate a test plan.

2. You can also display, change, copy or delete test plans or create additional test cases ifnecessary.

3. You combine a selection of test cases into a test package and assign it to a tester.

4. Use the status info system to display, print and process test plan status analyses.

Test Workbench functionality is reused in the Solution Manager Test Organization.

Test Plan Management

Use

With this function you can:

create

change, copy or delete test plans.

IntegrationYou organize tests after you have created a Business Blueprint and made initial configurations in theRealization phase. When you create a test plan for a project, the default test plan structure is based onthe structure of the Business Blueprint which you have previously created for your project.

Prerequisites

You must have defined a project and created a Business Blueprint. You must also set up a test systemlandscape before you begin the Test Organization.