Solman Operational Guideline Project Administration V3.1

SOLUTION MANAGER PROJECT PREPARATIONOPERATIONAL GUIDELINE PROJECT ADMINISTRATION

TABLE OF CONTENT

Table of content.............................................................................................................................................................. 1Overview.......................................................................................................................................................................... 2Required Prerequisites..................................................................................................................................................... 2Key Deliverables............................................................................................................................................................... 2Enablers............................................................................................................................................................................ 3Usage............................................................................................................................................................................... 4Project Documentation in SAP Solution Manager for Implementation Projects................................................................4Define Documentation Types............................................................................................................................................ 4Define Keywords............................................................................................................................................................. 10Keywords at document level........................................................................................................................................... 11Define Status Values...................................................................................................................................................... 12Synchronization between SAP Solution Manager status values and Project Controlling Monitoring (PCM)...................14Document Naming Conventions..................................................................................................................................... 15Authorizations Implementation Team.............................................................................................................................. 15Standard Roles available in SAP Solution Manager.......................................................................................................15Project Issue Management............................................................................................................................................. 16System Landscape & Components................................................................................................................................. 16Define System Landscape for a Implementation Project................................................................................................16Additional References.................................................................................................................................................. 18

OverviewThis Operational Guideline describes in a structured way how SAP Solution Manager can support a standard SAP implementation project (ASAP) to the best effect. This manual has been structured as follows in individual guidelines with the chapter “Usage”:

1.Define documentation types2.Define key words3.Define status values 4.Document naming conventions5.Authorizations implementation team6.Project Issue Management7.System landscape and components

Required Prerequisites

SAP Solution Manager has been installed and basic configuration has been finished by Technology consultant

Key DeliverablesSAP Solution Manager settings created for supporting a Project, e.g. Documentation Types and Templates Keywords for Filtering and Reporting Status Values schematics – for structure and documents – Users have been defined within the SAP Solution Manager Project with the appropriate authorizations. Project issue management has been implemented - optional

3.0 Configuration

& Development

4.0 Test Management

2.0 Business Blueprint

1.0 Project Administration

Enablers

Type Title Version DescriptionSAP Tool SAP Solution

Manager:

Create Implementation Project, assign standards, assign team members

7.0 TransactionsProject Administration (SOLAR_PROJECT_ADMIN)IMG for SAP Solution Manager (SPRO) PFCG (Role maintenance)SU01 (Maintain users)SU03 (Maintain authorizations)

UserAdministration

User Maintenance

PFCG (Role maintenance)SU01 (Maintain users)SU03 (Maintain authorizations)

Definition of System Landscape & ComponentsCreation of logical Components w/o systemAssignment of logical Components and Systems to Template/Roll-out project

All products and system need to be defined in Solution Manager incl. RFC. Integration of 3rd Party interfaces

TransactionSMSYSM59

SOLAR_PROJECT_ADMIN

Blueprint Documentation Templates

Inclusive How-To Fill and Examples

Templates for Blueprint Documentation

SAP Doc Explorer

cat_list_Open_Issues.xlt).

Open issue list / Templates for all phases

How To Guide to creating a Business Blueprint Concept

Provide guidance in creating a quality blueprint

Copyright/Trademark

http://www.sap.com/company/legal/copyright/index.epx

Usage

Project Documentation in SAP Solution Manager for Implementation Projects

SAP Solution Manager must be used to store all ‘solution application documentation’ for now (project duration) and later (post implementation support & development).

Other documentation can optionally be stored in SAP Solution Manager

Define Documentation TypesFor Documentation Types the following best practices are recommended to be used with SAP Solution Manager: Master Data Specification

Document to describe the requirements of all project relevant master data objects. Organizational Structure Specification

Document to describe the requirements of all project relevant organizational structure elements. Business Scenario Specification

Document to describe the high level requirements for a scenario. This includes a management summary and optionally graphical view on the scenario’s processes.

Business Process SpecificationDocument to describe the high level requirements for a business process in case, the detailed requirement specification is done at the level of process step.

Business Process Flow diagram (chart)Describe the sequence of process flow and related user roles including trigger and interfaces.

Business Process (Step) Listprocess step list is a sequence of process steps within a process or sub process. All activities in the process step list must be addressed to Input & Output and system-mapping (transaction) as well.

Copyright/Trademark


Business User Role documentDescribe business user role who executing a specific step or activity including related skills, responsibility and involved organizational units.

Technical System ArchitectureThe System Architecture describes the static system structure as a network structure with the elements of the generic product structure.

Technical Hardware ArchitectureThe HW Architecture (rough concept) presents proposals for possible HW architectures and the structure of HW units in HW components and HW modules.

Technical Software ArchitectureThe SW Architecture (preliminary design) contains proposals for possible SW Architectures and for the selected decomposition of the SW unit: dynamically into individual processes, statically into SW components, SW modules, and databases.

Scope DocumentThis document is used to document the project scope and key solution design decisions.

Development SOA RequirementsDescribes the requirements for SOA Service Identification, Definition and Structuring.

Requirements specification? Detailed requirements are often documented in respective document type (either on scenario, process or process step level).

Note: The detailed requirement analysis can either be on Process or on Process Step level.

Development Functional Specification (WRICEF)Document for the specification of all different development types (WRICEF), e.g.: Workflows Reports Interfaces Conversions Enhancements Forms

Configuration ManualDocument to describe the overall configuration for a business process. This is not the configuration documentation itself, this happens in the IMG of the satellite development system

Test Scenario DocumentDescribes the business content, master data, organizational elements of a certain test plan variant

Test Case Description of the steps, the tester has to do

Training DocumentationDocument for training purposes of the end user

Copyright/Trademark

Components of Business Blueprintdepending on specification level

Requirement Specs at Process Level

Scenario Specification

Requirement Specification

Scenario Specification

Process Specification

RequirementSpecification

Requirement Specs at Process Step Level


“Free” DocumentAn additional document for holding any additional information, relevant for the project, but not included in one of the other documents

Business Blueprint (BBP) – frozen VersionDocument to hold a frozen version of the complete BBP in pdf-format. This can be done either for the whole project or for each single scenario (depends on the size of the document created)

Overview of documentation types and relevant template settings

Document Doc. Type

Global

Several Docs.

BBP relevant

MS File type

LEVEL Templates ( ASAP Roadmap path - Reference)

Master Data Specification

ZBMD

X X .doc Project /Scenario

Business Blueprint->

Business Process

Management ->

Business Object

Modelling ->

General Settings and

Master data ->

Master Data

Specification

TEMPLATE

Organizational Structure Specification

ZBOR

X X .doc Project Business Blueprint->

Business Process

Management -

>Business Object

Modelling

->Business

Organizational

Structure ->

Organizational

Structure

Specification

TEMPLATE

Business Scenario Specification

ZBSC X X .doc Scenario Business Blueprint->

Business Process

Management ->

Business Solution

Design -> Business

Scenario Design ->

Business Scenario

Specification

TEMPLATE

Business Process Specification

ZBPR X X .doc Process Business Blueprint->

Business Process

Management ->

Business Solution

Design -> Business

Process Design ->

Business Process

Specification

TEMPLATE

Business ZBPF X X vsd Process Business Process

Copyright/Trademark


Process Flow diagram

Management->

Blueprint Approach ->

Field Service

Modelling Handbook

V04 – Guide

(ARIS/Visio)

Business Process List

ZBPS X X xls Process Business Blueprint->

Business Process

Management ->

Business Solution

Design -> Business

Process Design ->

Business Process

List TEMPLATE

Business ProcessRequirements

ZBRQ

X X Xls Process Business Blueprint->

Business Process

Management ->

Business Solution

Design -> Business

Process Requirements

-> Business

Requirements

Template

Business User Role document

ZBUR X X .doc Project Business Process

Management-

>Business Object

Modelling -> User Role

Concept ->

Business User Role

Document

TEMPLATE

Technical System Architecture

ZBTS X X . doc Project Business Blueprint->

Business Process

Management ->

Blueprint Approach -

>SolMan and Business

Process Management

-> SolMan Document

Typ.zip ->

Technical System

Architecture

Template

Technical Hardware Architect

ZBTH X X . doc Project Business Blueprint->

Blueprint Approach -

>SolMan and Business

Process Management

-> SolMan Document

Typ.zip ->

Technical Hardware

Architecture

TEMPLATE

Technical Software

ZBTC X X . doc Project Business Blueprint->

Blueprint Approach

Copyright/Trademark


Architecture ->SolMan and

Business Process

Management ->

SolMan Document

Typ.zip ->

Technical Software

Architecture

TEMPLATE

WRICEF List ZBGP X .xls Project Business Blueprint->

Business Process

Management-> Sol.

Transformation and

Design ->Solution

Gaps and Core

Enhancements->

WRICEF List

TEMPLATE

Scope Document

ZBSO X .doc Project Business Blueprint->

Business Process

Management->

Business Solution

Design ->Business

Process Design ->

Scope Key Decision

Document

TEMPLATE

Conversion Functional Specification

ZFCN X .doc Process Business Blueprint->

Business Process

Management-> Sol.

Transformation and

Design -> Solution

Gaps and Core

Enhancements -

>

Functional

Specification -

Conversions

Template

Enhancement Functional Specification

ZFEH X .doc Process Business Blueprint->

Business Process

Management-> Sol.

Transformation and

Design -> Solution

Gaps and Core

Enhancements -

>

Functional

Specification –

Enhancement

Template

Forms Functional Specification

ZFFO X .doc Process Business Blueprint->

Business Process

Management-> Sol.

Copyright/Trademark


Transformation and

Design -> Solution

Gaps and Core

Enhancements -

>

Functional

Specification –

Forms Template

Interface (ABAP) Functional Specification

ZFIA X .doc Process Business Blueprint->

Business Process

Management-> Sol.

Transformation and

Design -> Solution

Gaps and Core

Enhancements -

>

Functional

Specification –

Interface (ABAP)

Template

Report (ABAP) Functional Specification

ZFRA X .doc Process Business Blueprint->

Business Process

Management-> Sol.

Transformation and

Design -> Solution

Gaps and Core

Enhancements -

>

Functional

Specification –

Report (ABAP)

Template

Workflow Functional Specification (WRICEF)

ZFWF

X .doc Process Business Blueprint->

Business Process

Management-> Sol.

Transformation and

Design -> Solution

Gaps and Core

Enhancements -

>

Functional

Specification –

Workflow Template

Development SOA Requirements

ZFSR X .xls Process / Service

Business Blueprint->

Business Process

Management-> Sol.

Transformation and

Design -->

SOA/Composition ->

Requirements

TEMPLATE

Configuration Manual

Copyright/Trademark


Test Scenario Document

ZTSC X X . doc Scenario Project Preparation->

Project Standards->

Solution Manager

Usage Guidelines->

Templates for SolMan

documents types->

Test Scenario

Document

TEMPLATE

Test Case ZTTC X X . doc Process Project Preparation->

Project Standards->

Solution Manager

Usage Guidelines->


documents types->

Test Case

TEMPLATE

Training Documentation

ZEUT X X . doc Scenario/ Process

Project Preparation->

Project Standards->

Solution Manager

Usage Guidelines->


documents types->

Training

Documentation

TEMPLATE

“Free” Document

ZX01 X .doc All Additional

Documentation

Business Blueprint - frozen Version

ZBFX X X .pdf Project Business Blueprint

(frozen Version)

Information /Executive Summary

ZBIE X X Scenario Information Executive

Summary

Other documentation types like authorization & technical role specification, business authorization matrix, integration document or Program Handbooks like Configuration Handbook, Development Handbook, Test Handbook or Issue Handling Handbook are not covered in the following descriptions.

Assign the several documentation types in the transaction Solar_Project_Admin / TAB Project Standards:

Copyright/Trademark


Define Keywords

Keywords at document levelThe use of Keywords at document level is at least necessary to differentiate the development documents by the type of development: Enhancement Interface Forms Workflow Modification ReportsOther Keywords can be used for Assignments of test cases to certain test plan variants. This offers an easier way of creating the test plans

for test purposes. Special attributes (defined via SAP Solution Manager configuration) can be used to maintain e.g. effort

figures of development requirements for extracting them to Excel

Keywords at level Process Structure (assigned at Admin tab) can be used for Differentiation of BBP or Realization cycles Assignment of teams to process elements Assignments to specific Rollout Relevance Superior Application Module Link to Countries (FI,DE,FR…) participated - optional

Avoid having too many keywords (more than ten). This would confuse the teams when maintaining too many attributes.

The main focus for using the keywords are the reporting requirements at PM and/or team level which can be solved by using keywords. Keywords can be used also for filtering of current display area by processing working transactions Blueprint (SOLAR01), Configuration(SOLAR02) and Testing(STWB_2/WORK).

Assign Keywords in the transaction Solar_Project_Admin / TAB Project Standards:

Copyright/Trademark


Define Status Values

The status values for documents will be assigned via status schemes. The following status schemes are recommended:

Status Scheme Values Meaning Sequence No.

Following No.

BBP-Status Work In Process

Initial value when creating a new document

10 20

Completed Ready for Review 20 10/30Reviewed Document reviewed 30 20/40Released Document 40 40

Development Status Work In Process

Initial value when creating a new document

10 20

Request for Approval

Request for approval according to CR-process

20 10/30/40/50

Approved Approved by responsible unit acc. to CR-process

30 60

Declined Declined by responsible unit acc. to CR-process

40

Deferred Deferred to a later phase by responsible unit acc. to CR-process

50

Concept started

Programmer started detailed concept

60 10/70

Concept finished

Programmer finished detailed concept and starts programming

70 60/80

Realization Programming finished and 80 10/60/90

Copyright/Trademark


finished development in testAccepted Development tested by requestor

and accepted90

Create a status scheme for several documentation types in the transaction SPRO (Customizing Solution Manager). Caution the configurations are relevant to cross client.

Assign a status scheme to a document type in the transaction Solar_Project_Admin / TAB Project Standards

Copyright/Trademark


For the status at the process structure level – indicator for progress - (be maintained at the Administration tab) the following values have to be used (different ones for the BBP and Realization phase)

Status Values for Business Blueprint PhaseOpen Presetting at begin of each phase Work In Process Initial value when creating a new document Review All relevant documents of the process element are finished and the

Review process has startedReleased All relevant documents has been reviewed and released

Status Values for Realization PhaseOpen Presetting at begin of each phase Work In Process Configuration and Unit Testing startedConfigured All configuration settings done

All configuration settings documented in IMGAll configuration settings linked to SolManAll transaction codes assigned

Tested All test cases finishedProcess level successfully tested by unit tests according to test case

Synchronization between SAP Solution Manager status values and Project Controlling Monitoring (PCM)

The status values of SAP Solution Manager should be in line with the progress reported in the PCM. The following relationship allows this:

Progress PMC Meaning Status SAP Solution Manager Process Element

Status SAP Solution Manager Documents

For Business Blueprint 0 % Open10 % Activity started Work In

progress50 % Work in

ProgressWork In progress

This will be set, when the first round of Workshops are done

80 % Finished Review Review100 % Signed off, no

further actions required

Released Released

For Realization Phase 0 % Open Approved10 % Activity started50 % Work in

ProgressWork In progress

80 % Finished Configured Realization finished

100 % Signed off, no further actions required

Tested Accepted

Copyright/Trademark


Document Naming ConventionsIt is important to define a standard for identification, naming the individual documents that are stored for the project in the Knowledge Warehouse database (KW). Searching for documents in the KW require clear naming conventions. Specifically if the link of an individual document to the project structure node has (accidentally) got lost, it should be easily possible to re-establish this link by finding the appropriate document in the KW.

The individual naming conventions are discussed in the corresponding chapter of the guidelines: Blueprint relevant documentation: see Operation Guideline 2 Configuration relevant documentation: see Operational Guideline 3 Test Cases, Test Plans and Test Packages: see Operational Guideline 4

The following example could be seen as a SAP best practice proposal for process related documentation in a first way:

aa.bb.cc.dd_ZBPR*_<BPV-Name>.doc

Legend:aa = ID Business Areaaa.bb = + ID “Core Process” (BPM)aa.bb.cc = + ID “Business Process”(BPM) aa.bb.cc.dd = + ID Business Process_Variant (BPM)

ZBPR = Document type

Version / Subversion 0.1 – 0.9 is part of document header

*ZBPR = Document type – usage optional e.g. for reporting & filtering outside of Solman (Excel)<gpname>= Name of document –see recommendation above -

Non Process related Documentation like ZBTC, ZBGC, ZBUR, ZBOR, ZBOM, ZBSO and ZBSC will be stored without prefix directly as follows:

ZBOR_<Name>.doc

Authorizations Implementation TeamThis part of the Operational Guideline describes how to: Setup basic authorizations for accessing the SAP Solution Manager by the implementation team The minimum key roles that should be addressed Tips for practical use and extension of standard roles

Standard Roles available in SAP Solution Manager

SAP Solution Manager uses standard authorization concepts. Standard set of roles and authorizations are delivered with SAP Solution Manager. Single roles have been combined into, so called, composite roles.

The following composite roles are standard available and recommended to use for Implementation projects: Project manager – SAP_SOL_PM_COMP Application consultants – SAP_SOL_AC_COMP Development consultants – SAP_SOL_BC_COMP

Copyright/Trademark


Technical/Netweaver consultants – SAP_SOL_TC_COMP Test users - SAP_SOL_TESTER_COMP Display User – SAP_SOL_RO_COMP Edit/Change Documentation - SAP_SOL_KW_ALL

Changing standard rolesPlease note: standard (composite) roles should be copied to a customer name space role (for example Z_SAP_SOL_PM_COMP) before use. Authorizations should be checked that they have been activated in the system. These Z* roles can then also be adapted/enhanced to the project specific needs.

Specials considerations for enhancing these standard authorizations:

All SAP Solution Manager authorizations: SAP_SOLAR_ALL Project authorization.

In order to authorize access to individual projects, Authorization Objects: S_PROJ* are available. Please check.

Extend authorizations for SAP Solution ManagerPlease take notice of Note 834534

Each Implementation project team member, requiring authorized access to SAP Solution Manager, will get a unique user-id in SAP Solution Manager with the appropriate authorizations according to the specified composite role assigned. Maintenance can be initiated by accessing the project (Transaction SOLAR_PROJECT_ADMIN, tab page PROJ.TEAM.MEMBER and exploring USER MAINTENANCE) by the Project Manager.

Not covered in this chapter

Please note that this document does not cover the required authorizations in the satellite component systems. – see http://help.sap.com/ for more details.Please note that this document does not cover the authorizations required for Operations part of SAP Solution Manager, like Solution Monitoring, Service Desk, Change Request management etc.- see also http://help.sap.com/

Project Issue Management

The Project Issue Management can be done in SAP Solution Manager, but it is recommended to use MS-Office Excel functionality for Project Management related issues. There is a predefined XLS table available in SAP Doc Explorer (see Open Issue List - cat_list_Open_Issues.xlt). Test issues/messages, however, should be recorded and followed by using Service Desk functionality of SAP Solution Manager (see: Operational Guideline 4).

System Landscape & Components

Define System Landscape for a Implementation ProjectTransaction : SMSY and SOLAR_PROJECT_ADMINISTRATION

Copyright/Trademark


http://help.sap.com/

http://help.sap.com/

Define complete system landscape for a project: Select product and product version Assign development, quality assurance and productive systems to products Check related system landscape Non SAP Systems Make sure that the appropriate logical components have been chosen

All products and related DEV, QAS, PRD systems need to be defined in Project Administration (SOLAR_PROJECT_ADMIN)

To start with project work creation of logical components based on SAP applications like ERP, SCM, SRM, BW, and Xi (optional -3rd Party) with TC SMSY is mandatory. So far no real system needs to be connected. After this logical components need to be assigned to Template landscape. Assignment to system can be done later if systems are available.

Prior to the definition of a project system landscape, products, systems and related RFC destinations need to be created in System Landscape Maintenance transaction (SMSY)

Copyright/Trademark


Additional References SAP Solution Manager User Guide section “Project Preparation > Project Administration > Create /Change

Project > Project Standards Tab” Training material – SMI310 SAP Learning Solution SAP Solution Manager User Documentation SAP Solution Manager Configuration Guide https://websmp206.sap-ag.de/solutionmanager SAP Consulting Project Management content in the Roadmap Composer. Solution Manager Wiki ->https://wiki.sdn.sap.com/wiki/label/BPX/solution

Copyright/Trademark


https://wiki.sdn.sap.com/wiki/label/BPX/solution

https://websmp206.sap-ag.de/solutionmanager

https://pwwdf860.wdf.sap.corp/sap(bD1lbiZjPTAwMSZkPW1pbg==)/bc/bsp/sap/HCM_LEARNING/LESO.HTM?CORE=traininghome.htm

Solman Operational Guideline Project Administration V3.1

Documents

Transcript of Solman Operational Guideline Project Administration V3.1