Configuration Guide CUSTOMER

Focused Build for SAP Solution Manager

Document Version: 1.00 – 2019-04-22

Focused Build for SAP Solution Manager 7.2

ST-OST 200 SP 2
Typographic Conventions

Type Style Description

Example Words or characters quoted from the screen. These include field names, screen titles,
pushbuttons labels, menu names, menu paths, and menu options.
Textual cross-references to other documents.

Example Emphasized words or expressions.

EXAMPLE Technical names of system objects. These include report names, program names,
transaction codes, table names, and key concepts of a programming language when they
are surrounded by body text, for example, SELECT and INCLUDE.

Example Output on the screen. This includes file and directory names and their paths, messages,
names of variables and parameters, source text, and names of installation, upgrade and
database tools.

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

<Example> Variable user entry. Angle brackets indicate that you replace these words and characters
with appropriate entries to make entries in the system.

EXAMPLE Keys on the keyboard, for example, F 2 or E N T E R .

CUSTOMER Focused Build for SAP Solution Manager 7.2

2 © 2018 SAP SE or an SAP affiliate company. All rights reserved. Typographic Conventions
Document History

Version Date Change

1.00 2019-04-22 Initial Version

Focused Bild for SAP Solution Manager CUSTOMER

Document History © 2018 SAP SE or an SAP affiliate company. All rights reserved. 3
Contents

Typographic Conventions.................................................................................................................... 2

Document History ................................................................................................................................ 3

1 Introduction............................................................................................................................. 6
1.1 Objective................................................................................................................................................. 6
1.2 System Pre-requisites........................................................................................................................... 6

2 Deployment of Focused Build Requirement-to-Deploy ........................................................ 9

2.1 Manual Activities - Part I ....................................................................................................................... 9
2.1.1 Transaction Types ................................................................................................................ 9
2.1.2 Maintaining Number Ranges................................................................................................ 9
2.1.3 Activating Services ............................................................................................................. 10
2.1.4 Maintaining the Table HTTPURLLOC ................................................................................. 11
2.1.5 Activation of Virus Scan Profiles......................................................................................... 11
2.1.6 Maintaining System Roles ...................................................................................................12
2.1.7 Multilevel Categorization .....................................................................................................13
2.1.8 Configuring Project Management.......................................................................................16
2.1.9 Configuring Test Suite Extensions .....................................................................................18
2.1.10 Release Management ..........................................................................................................19
2.2 Automatic Activities - Part II ............................................................................................................... 22

3 Background Processing .........................................................................................................23

3.1 Objective............................................................................................................................................... 23
3.2 Import Control in Requirement to Deploy ......................................................................................... 23
3.3 Data Extraction for Solution Readiness Dashboard ......................................................................... 25
3.4 Data Extraction for Test Management Dashboard ........................................................................... 29

4 Project Preparation............................................................................................................... 30
4.1 Objective............................................................................................................................................... 30
4.2 Prerequisites ........................................................................................................................................ 30
4.2.1 Content related prerequisites ............................................................................................ 30
4.3 Create Solution with Branches, System Landscape and Document-Type assignment ............... 32
4.3.1 Create Solution.................................................................................................................... 32
4.3.2 Setup up branches .............................................................................................................. 33
4.3.3 Setup system landscape .................................................................................................... 36
4.3.4 Related Documentation...................................................................................................... 40
4.3.5 Considerations, if process management is already in use .............................................. 40
4.3.6 Create and assign Document Types to Solution ...............................................................41
4.3.7 Adjust Customizing for Document KPI Framework ......................................................... 45
4.3.8 Configure E-Mail Notifications on Document Status Change ......................................... 47
4.3.9 Import Best Practice Content into Import Branch ........................................................... 49
4.3.10 Release Scope-relevant Processes into Design-Branch ..................................................51
4.3.11 Create Change Control Landscape ................................................................................... 53

CUSTOMER Focused Build for SAP Solution Manager 7.2

4 © 2018 SAP SE or an SAP affiliate company. All rights reserved. Contents
 4.3.12 Define Branch Mapping (SPRO).........................................................................................54
4.4 Setup Release Management ...............................................................................................................56
4.4.1 Release Planning .................................................................................................................56
4.4.2 Define Release Profile Mapping .........................................................................................62
4.5 Project Setup........................................................................................................................................62
4.5.1 Create Projects ....................................................................................................................62
4.5.2 Assign Release to Projects .................................................................................................64
4.5.3 Assign sub projects to master project...............................................................................65
4.5.4 Maintain project data (optional) ........................................................................................66
4.5.5 Define Wave Relationships between Master and Build Projects ..................................... 67
4.5.6 Link Q-Gates of Master and Build Projects .......................................................................69
4.5.7 Maintain Project Milestones ............................................................................................... 71
4.5.8 Release Q-Gate(s) ............................................................................................................... 73
4.5.9 Assign dedicated Release Numbers to Waves (optional)................................................ 74
4.5.10 Prepare first Wave and Sprint ............................................................................................ 76

5 Appendix ................................................................................................................................. 77
5.1 Useful SAP Notes ................................................................................................................................. 77
5.2 Adjust Category Schema .................................................................................................................... 77
5.3 Mandatory Standard Configuration for Test Suite ........................................................................... 79
5.3.1 Test Classification ............................................................................................................... 79
5.3.2 Analytics for Test Suite ...................................................................................................... 80
5.3.3 Analytics for ITSM .............................................................................................................. 80
5.3.4 Context menu for Test Steps missing in Solution Documentation................................. 81
5.4 Language Settings ............................................................................................................................... 81
5.5 Delete of obsolete projects .................................................................................................................82
5.6 Adapting Project Reasons ...................................................................................................................82
5.7 User Roles, Authorizations and Business Partners ..........................................................................83
5.7.1 Authorization Roles and Users in SAP Solution Manager System..................................83
5.7.2 Authorization Roles and Users in Systems Belonging to the Project .............................84
5.7.3 Defining Business Partners ................................................................................................85

Focused Bild for SAP Solution Manager CUSTOMER

Contents © 2018 SAP SE or an SAP affiliate company. All rights reserved. 5
1 Introduction

This document describes the configuration steps of Vale's Focused Build Requirement-to-Deploy scenario for
SAP Solution Manager required to deploy the Solution to the Production Environment.

1.1 Objective

This document targets support consultants who plan to perform the deployment of the component ST-OST 200
Focused Build Requirements-to-Deploy scenario to the Production Environment.

1.2 System Pre-requisites

The following pre-requisites must be checked before the deployment of Focused Build Requirements-to-Deploy:

The Mandatory Configuration must be completed upfront

1. Call transaction SOLMAN_SETUP.
2. Go to Scenarios > Cross Scenario Configuration > Mandatory Configuration > System Preparation:

3. Check the status scenarios are green:

4. Go to Scenarios > Cross Scenario Configuration > Mandatory Configuration > Infrastructure:

CUSTOMER Focused Build for SAP Solution Manager 7.2

6 © 2018 SAP SE or an SAP affiliate company. All rights reserved. Vale - Deplyment Guide of Focused Build Requirement to Deploy
5. Check the status scenarios are green:
6. Go to Scenarios > Cross Scenario Configuration > Mandatory Configuration > Basic Configuration:

Configuration of Embedded Search

1. Call transaction SOLMAN_SETUP.
2. Go to Scenarios > Cross Scenario Configuration > Embedded Search:

3. Check if all steps have been implemented:

Focused Build for SAP Solution Manager CUSTOMER

Vale - Deployment Guide of Focused Bild Requirement to Deploy © 2018 SAP SE or an SAP affiliate company. All rights reserved. 7
 CUSTOMER Focused Build for SAP Solution Manager 7.2
8 © 2018 SAP SE or an SAP affiliate company. All rights reserved. Vale - Deplyment Guide of Focused Build Requirement to Deploy
2 Deployment of Focused Build
Requirement-to-Deploy

2.1 Manual Activities - Part I

Caution
It is important that you follow the sequence of set-up steps described in the following sections.

2.1.1 Transaction Types

Focused Build uses the following transaction types:

Transaction Type Description Usage

S1MR Release Release Cycle Document

S1BR Requirement Business Requirement

S1IR Scope Change Change scope request

S1IT Work Package Work Package

S1MJ Work Item Work Item with transport requests

S1CG Work Item Work Item without transport requests

S1RK Risk

SLFI Issue

S1TK Task

S1TR Test Request

S1DM Defect Message Report of a defect

S1TM Defect Correction Correction of a defect during testing

2.1.2 Maintaining Number Ranges

To maintain the number ranges, perform the following steps:

Focused Build for SAP Solution Manager CUSTOMER

Vale - Deployment Guide of Focused Bild Requirement to Deploy © 2018 SAP SE or an SAP affiliate company. All rights reserved. 9
1. Call transaction SNRO.
2. Create the following number ranges for the object CRM_SERVIC.

Range From To Transaction Type

85 8500000000 8599999999 S1MR - Release

31 3100000000 3199999999 S1IR - Change Scope

32 3200000000 3299999999 S1BR - Requirement

33 3300000000 3399999999 S1IT - Work Package

61 6100000000 6199999999 S1MJ - Work Item

62 6200000000 6299999999 S1CG - Work Item

15 1500000000 1599999999 S1RK - Risk

16 1600000000 1699999999 SLFI - Issue

17 1700000000 1799999999 S1TK - Task

71 7100000000 7199999999 S1TR - Test Request

72 7200000000 7299999999 S1DM - Defect Message

73 7300000000 7399999999 S1TM -Defect Correction

2.1.3 Activating Services

Activate all services for IT Service Management, Change Request Management, and Product and Portfolio
Management.
1. Call transaction SICF_INST and activate the following services:
o SM_CHARM
o SM_CRM_UI

CUSTOMER Focused Build for SAP Solution Manager 7.2

10 © 2018 SAP SE or an SAP affiliate company. All rights reserved. Vale - Deplyment Guide of Focused Build Requirement to Deploy
 If the services are activated successfully, you see a green traffic light icon.
2. Go to transaction SICF and activate all of the services below the /default_host/sap/bc/bsp/salm and
/default_host/sap/bc/webdynpro/salm nodes.
3. Activate all services in /default_host/sap/bc/ui5_ui5/salm.
4. Activate all services in /default_host/sap/bc/ui5_ui5/stdf/libs
5. Activate all services in /default_host/sap/bc/webdynpro/rpm.
6. Activate all services in /default_host/sap/opu/odata/salm.
7. Activate the UI5 library services /default_host/sap/bc/bsp/stdf/ui5 and libs.

2.1.4 Maintaining the Table HTTPURLLOC

Go to transaction SE16 and maintain the new /WEBDYNPRO/SALM/* entry in table HTTPURLLOC.
Depending on the current configuration in table HTTPURLLOC, a new entry needs to be maintained to open Web
Dynpro applications of Focused Build with the correct URL.
If the table is maintained, add the new /WEBDYNPRO/SALM/* entry after the entry /WEBDYNPRO/SAP/*, but
before entry /*.

2.1.5 Activation of Virus Scan Profiles

Desactivate the virus protection in your development system.

Focused Build for SAP Solution Manager CUSTOMER

Vale - Deployment Guide of Focused Bild Requirement to Deploy © 2018 SAP SE or an SAP affiliate company. All rights reserved. 11
Go to transaction /IWFND/VIRUS_SCAN, search and desactivate the virus scan profile
/UI5/UI5_INFRA_APP/REP_DT_PUT.

2.1.6 Maintaining System Roles

Create additional (or adjust) system roles via transaction MAINT_ROLES:

System Role Source Type of Role Description

C SAP D - Source System Development System

T SAP O - Target System Quality Assurance System

P SAP P - Production System Production System

V SAP S - Single System Evaluation System

0 CUSTOMER O - Target System Pre-Production System

2 CUSTOMER R - Post-Processing System Retrofit System

3 CUSTOMER O - Target System Pre-Deploy System

4 CUSTOMER O - Target System Maintenance Development System

5 CUSTOMER O - Target System Maintenance Quality Assurance System

6 CUSTOMER O - Target System Maintenance Pre-Production System

CUSTOMER Focused Build for SAP Solution Manager 7.2

12 © 2018 SAP SE or an SAP affiliate company. All rights reserved. Vale - Deplyment Guide of Focused Build Requirement to Deploy
2.1.7 Multilevel Categorization

Multilevel categorization lets you sort business transactions into as many as four levels. It integrates functions
such as auto-completion and item determination based on categories, and searches for related problems,
knowledge articles, and change requests.

To set up multilevel categorization for Focused Build proceed as follows:

1. Call transaction SM_CRM

2. Choose Service Operations and then Categorization Schemas.

Focused Build for SAP Solution Manager CUSTOMER

Vale - Deployment Guide of Focused Bild Requirement to Deploy © 2018 SAP SE or an SAP affiliate company. All rights reserved. 13
3. Create a new categorization schema and call it FOCUSED_BUILD.

4. Assign the application areas as follows:

o Application ID: Service Order

o Parameter: Transaction Type / Catalog Category
o Choose all S1*/D except S1TR/D (test requests) and save your selection.
5. Assign the application areas as follows:

CUSTOMER Focused Build for SAP Solution Manager 7.2

14 © 2018 SAP SE or an SAP affiliate company. All rights reserved. Vale - Deplyment Guide of Focused Build Requirement to Deploy
 o Application ID: Service Request
o Parameter: Transaction Type / Catalog Category
o Choose S1DM/D and save your selection.
6. Download the project template XML files from SAP Note

SAP Note Description

2624412 Central Note for Focused Build 2.0 SP02 for SAP Solution Manager 7.2

7. Upload the categorization schema FB_General.txt:

o Call transaction CATEGOTOOL and import the schema.

o Import the uploaded schema into the schema previously created in the WebClient UI.

o In transaction SM_CRM, navigate to the categorization schema search and choose FOCUSED_BUILD.

o Choose a future date and time, and then release the schema.
8. Repeat steps 1–4 to create a second categorization schema and call it FOCUSED_BUILD_TESTING for S1TR
(test requests). Also repeat step 5 but upload the categorization schema FB_TESTING_EN.txt.

Focused Build for SAP Solution Manager CUSTOMER

Vale - Deployment Guide of Focused Bild Requirement to Deploy © 2018 SAP SE or an SAP affiliate company. All rights reserved. 15
2.1.8 Configuring Project Management

Creating Projects Templates

1. Download the project template XML files from SAP Note

SAP Note Description

2624412 Central Note for Focused Build 2.0 SP02 for SAP Solution Manager 7.2

2. To start Project Management, on the SAP Solution Manager Launchpad, choose My Projects.
3. Choose Projects and then choose Import Project.
4. In the Application field, select XML File.

5. In the File field, choose Browse to navigate to the file that you want to import.
6. Choose Import Selected Data.
7. Under Data for Import, select Structures and Resources.
8. Choose Check.
9. Choose Import.

10. After uploading all XML project files, convert them into a project template.
11. In the Project Management, go to Portfolio and Project Administration and choose Project Management
Templates. Then create template derived from the imported files:
12. On the left navigation pane, choose Project Management Templates.

CUSTOMER Focused Build for SAP Solution Manager 7.2

16 © 2018 SAP SE or an SAP affiliate company. All rights reserved. Vale - Deplyment Guide of Focused Build Requirement to Deploy
13. Choose Project Administration in the top navigation area.
14. Choose Create.
15. Enter the following settings to create your template project:

Field Value

Proj. Template [FB SP02] Single Project

Template Type Project

Template FB_SINGLE_SP02

New Checklist Templates None

Original Language English

16. Release the project template by setting the status to released.

Focused Build for SAP Solution Manager CUSTOMER

Vale - Deployment Guide of Focused Bild Requirement to Deploy © 2018 SAP SE or an SAP affiliate company. All rights reserved. 17
17. After the creation of the templates you can delete the previously uploaded projects again. Please refer to
chapter 5.5 Delete of obsolete projects.

2.1.9 Configuring Test Suite Extensions

Activation of BEx-Queries
1. Call transaction RSOR .
2. Open the BI content.
3. Display the Object Types.
4. Expand the Query Elements. Under Query, choose Select Objects.
5. Select all BEx queries (Business Explorer queries) with the technical name /SALM/SMT*:
Navigate to SAP Solution Manager → Test Management → Test Management MultiProvider.
Display the technical name by choosing (Technical Name off/on) ( F 7 ).
Select the following entries:

Entry Technical Name

Defect Status /SALM/SMT_DF_STATUS

Defect Status Detail /SALM/SMT_DF_STATUS_DETAIL

Defect Status Progress /SALM/SMT_DF_STATUS_PROGRESS

Test Package Status Detail /SALM/SMT_TG_STATUS_DETAIL

Test Plan Status /SALM/SMT_TP_STATUS

Test Plan Status Detail /SALM/SMT_TP_STATUS_DETAIL

Test Plan Status Progress /SALM/SMT_TP_STATUS_PROGRESS

To transfer the selected entries, choose Transfer ( F 2 )

The queries should be listed in the right area of the window.

6. When all queries are selected for installation, choose Install and then Install in Background.

CUSTOMER Focused Build for SAP Solution Manager 7.2

18 © 2018 SAP SE or an SAP affiliate company. All rights reserved. Vale - Deplyment Guide of Focused Build Requirement to Deploy
 Recommendation
Use the installation in the background because the option Install might fail.

2.1.10 Release Management

To use the enhanced Release Management functionalities of Focused Build, you have to perform the following
steps:
In the customizing of SAP Solution Manager, choose SAP Solution Manager → Capabilities → Change Control
Management → Change Request Management Framework → Change Cycles → Configure Transaction Type for
Sublandscapes and maintain your Solution Sublandscape ID with the relevant cycle transaction type; e.g.

Focused Build for SAP Solution Manager CUSTOMER

Vale - Deployment Guide of Focused Bild Requirement to Deploy © 2018 SAP SE or an SAP affiliate company. All rights reserved. 19
Check Definition of Release Management Profiles
If a new release management profile is required, perform the following customizing activity:
1. In customizing for SAP Solution Manager, choose SAP Solution Manager → Focused Build → Release
Management Configuration → Define Release Management Settings.
2. Choose the Define Release Management Profiles activity.

3. Check if all entries are available (if no entries are available check chapter Error! Reference source not found.)

Define Release Profile Mapping

If you are creating a new release component or change control landscape, you have to define a release profile
mapping.
1. In customizing for SAP Solution Manager, choose SAP Solution Manager → Focused Build → Release
Management Configuration → Release Management Configuration. → Define Release Management Settings.
2. Choose the Define Release Profile Mapping activity.
3. You map the release type together with the release component.

4. Use F4 help to select Solution Name and Branch Type. For the Branch Type you have the following options:
o MASTER - Production Branch (Used for Production Branch mapping)
o MAINT - Maintenance Branch (Used for Maintenance Branch mapping)
o STD - Standard Branch (Used for all other branch mapping like development, design or import branch)
5. Use F4 help to select Release Profile
o /SALM/MAINT for Releases in the Maintenance Branch

CUSTOMER Focused Build for SAP Solution Manager 7.2

20 © 2018 SAP SE or an SAP affiliate company. All rights reserved. Vale - Deplyment Guide of Focused Build Requirement to Deploy
 o /SALM/STANDARD for Standard Branches like development branch
6. Use F4 help to select Batch Import
Var(iant) which should be used if you execute the Release Import from task list.
7. Use F4 help to select Collective Import Var(iant) which should be used if you execute the Collective Import
from task list.

Activation of Cross-System Lock for Development Clients for the dedicated development system (maintenance
and project development systems), you should switch on CSOL (Legacy CSOL). To do so, go to SAP Solution
Manager Launchpad:

Note

Prerequisites:
RFC Connections (incl. CSOL_BACK RFC Destination) are generated,
Required entry in table BCOS_CUST on the managed development system has been created

Focused Build for SAP Solution Manager CUSTOMER

Vale - Deployment Guide of Focused Bild Requirement to Deploy © 2018 SAP SE or an SAP affiliate company. All rights reserved. 21
2.2 Automatic Activities - Part II

Please import the following transport requests below (functional transport requests):

Transport Request Description

SMDK903857 OHASII - Focused Build Pre-Requisites - PART I - Test Suite

SMDK903863 OHASII - Focused Build Setup - PART I

SMDK903861 OHASII - Focused Build Setup - PART I

CUSTOMER Focused Build for SAP Solution Manager 7.2

22 © 2018 SAP SE or an SAP affiliate company. All rights reserved. Vale - Deplyment Guide of Focused Build Requirement to Deploy
3 Background Processing

3.1 Objective

This chapter targets jobs used to perform background processing.

3.2 Import Control in Requirement to Deploy

The Import Control in requirement-to-release scenario provides various options for mass deployment. Standard
Import Customizing defines deployment rules for imports executed from a task list that import normal changes as
preliminary import status and urgent changes.
Batch Import Customizing defines deployment rules for imports in a release context.
/SALM/BATCH_IMPORT_TRIGGER manages the import of normal changes.
After successfully activating the piece list you can continue with adjustments of the standard customization and
maintaining the system related data. The following import variants has been created basead Vale's scenario:
• ZPRD_PD_PQ
For Project imports into QAS Quality Assurance System (a.k.a. Torres and Project Specific).
• ZPRD_PQ_PY
For Project imports into PDY Pre-Deploy System (a.k.a. Torres and Project Specific).
• ZPRD_PY_MD
For Project imports into MDV Development System Maintenance (a.k.a. Torres and Project Specific).
• ZPRD_MD_MQ
For Project imports into MQA Quality Assurance System Maintenance (a.k.a. Torres and Project Specific).
• ZPRD_MQ_MR
For Project imports into MPP Pre-Production System Maintenance (a.k.a. Torres and Project Specific).
• ZPRD_MR_MQ
For Project imports into MPR Production System Maintenance (a.k.a. Torres and Project Specific).

Proceed as follows:
1. If you like to execute /SALM/BATCH_IMPORT_TRIGGER regularly, check the automatic rescheduling flag and
define the frequency.
2. Go to transaction SE38, execute /SALM/BATCH_IMPORT_TRIGGER. Afterwards select relevant Release to
Import.

Focused Build for SAP Solution Manager CUSTOMER

Vale - Deployment Guide of Focused Bild Requirement to Deploy © 2018 SAP SE or an SAP affiliate company. All rights reserved. 23
 Note
The first release in the context of your release component is always the active one. Completed releases
are not shown in this list.
3. The next step is to select the relevant Import Variant.

4. Repeat the previous step for all required variants.

CUSTOMER Focused Build for SAP Solution Manager 7.2

24 © 2018 SAP SE or an SAP affiliate company. All rights reserved. Vale - Deplyment Guide of Focused Build Requirement to Deploy
3.3 Data Extraction for Solution Readiness Dashboard

/SALM/DATA_EXTRACTION_PPMITSM extracts data for the dashboard. We recommend that you run this job daily,
or manually before meetings. If project activity is high, run the job hourly.
As a 2nd step in this background job you should add /SALM/FILL_SRD_CACHE because
/SALM/DATA_EXTRACTION_PPMITSM invalidates the caches after each run.
There are several data options which can be selected for extraction and refill of the
caches. The selection can be saved as variant.

You can use the following variants as of SP02:

Variant Description

Focused_Build1 With Project and trend data without

Portfolio

Focused_Build2 With Project but without trend data and

portfolio

Focused_Build3 With projects and portfolio as well as

trend data creation

R2D Without PPM and trend data

Before you can configure easily as shown below:

Focused Build for SAP Solution Manager CUSTOMER

Vale - Deployment Guide of Focused Bild Requirement to Deploy © 2018 SAP SE or an SAP affiliate company. All rights reserved. 25
 CUSTOMER Focused Build for SAP Solution Manager 7.2
26 © 2018 SAP SE or an SAP affiliate company. All rights reserved. Vale - Deplyment Guide of Focused Build Requirement to Deploy
For the Solution Readiness Dashboard trend (or historical) data is required. Select the relevant variant and
schedule the report in background as recommended earlier.
Extraction Job run modes
• Normal mode (Use simple process mode disabled, Use Multi process mode disabled). This is the standard
execution mode (sequential execution).
• Simple process mode (Use simple process mode enabled, Use multi process mode disabled). The extraction
job is separated into two “blocks”.

Focused Build for SAP Solution Manager CUSTOMER

Vale - Deployment Guide of Focused Bild Requirement to Deploy © 2018 SAP SE or an SAP affiliate company. All rights reserved. 27
 o PPM extraction: Projects related data extraction. (Is executed in a dialog process if there is one dialog
process available else it will execute in normal mode)
o CRM extraction: CRM object data extraction. (Is always executed in normal mode)
• Multiple process mode (Use simple process mode: Any, use multi process mode enabled).
o The extraction job is separated into two “blocks”.
o PPM extraction: Projects related data extraction. (Is executed in a dialog process if there is one dialog
process available else it will execute in normal mode)
We fragment the data depending on: PPM length of data fragment(Parameter), Maximum PPM
threads allowed(Parameter), Available dialog process number (Variable),Total data length (Variable)
and we execute the data fragment in a dialog process. If there is no dialog process available, we
switch to normal mode.
o CRM extraction: CRM object data extraction. (Is always executed in normal mode)

Additionally, it is recommended to run a data compression for the trend data on monthly, quarterly and yearly
basis. Therefore, schedule a job for /SALM/DATA_EXTRACTION_DELETE avoiding performance impacts.

Additional Job for Release Dashboard

With SP01 we are introducing 2 additional jobs which are triggered by the event SAP_EXTRACTOR_EXTENT thrown
by /SALM/DATA_EXTRACTION_PPMITSM:
• /SALM/FILL_SRD_CACHE
• /salm/transport_buffer_fill
This job reads all open transports contained in the transport buffer.
• /salm/create_release_cache
After the job /SALM/DATA_EXTRACTION_PPMITSM has run, all caches are invalidated. The scheduling of this
job is optional because it could run quite long, and it is just required if you require very high performant
dashboards.

CUSTOMER Focused Build for SAP Solution Manager 7.2

28 © 2018 SAP SE or an SAP affiliate company. All rights reserved. Vale - Deplyment Guide of Focused Build Requirement to Deploy
3.4 Data Extraction for Test Management Dashboard

Schedule /SALM/TSD_DATA_EXTRACTION daily by utilizing transaction SM36 Job Wizard.

ABAP program name: /SALM/TSD_DATA_EXTRACTION

Date/time: <end of day> (recommended after the W

extractor)

Period: daily

Focused Build for SAP Solution Manager CUSTOMER

Vale - Deployment Guide of Focused Bild Requirement to Deploy © 2018 SAP SE or an SAP affiliate company. All rights reserved. 29
4 Project Preparation

4.1 Objective

This chapter targets master data used to prepare the Proof-of-Concept of Focused Build.

4.2 Prerequisites

4.2.1 Content related prerequisites

Required customer master data for planned Focused Build Project.

The data should be the results of conceptual discussion with the customer on how Process Management /
Solution Documentation and Landscape as well as Release Management and Project definition should look like.

Solution

Name Vale

Technical Name VALE

Branches Production

Maintenance

Development

Design

Import

Document Types and templates (BPD) Business Process Description

(CG) Configuration Guide

(FIT) Functional Integration Test

(FS) Functional Specification type WRICEF

(FS) Functional Specification type Gap

(FS) Functional Specification type Interface

(SFT) Single Functional Test

(TD) Technical Design

(UAT) User Acceptance Test

CUSTOMER Focused Build for SAP Solution Manager 7.2

30 © 2018 SAP SE or an SAP affiliate company. All rights reserved. Vale - Deplyment Guide of Focused Build Requirement to Deploy
 (UC) Use Case

(UG) User Guide

(MO) Mock-up

(TM) Training Material

Best Practices SAP Best Practices for ECC 6.0 EhP 7

SAP Mining Best Practices for ECC 6.0 EhP7

Involved Systems / Landscape (Logical Log Comp System Role SID Client
Component Group(s), Technical Grp.
Systems)
S4HANA Sandbox <SID> <CLNT>

Development <SID> <CLNT>

Quality <SID> <CLNT>

Assurance

Pre- <SID> <CLNT>

Production

Production <SID> <CLNT>

Release Management

Number of planned Releases 2

Duration in days 180

Go-Live Date for 1st Major Release October 1st 2017

Project Management

Project Templates Lean or Activate Roadmap based template

Master Project e.g. S/4HANA

Build Project 1 e.g. Financials

Build Project 2 e.g. Logistics

Number of Waves per Project 2

Start date of 1st wave April 1st 2017

Duration of waves 90

Number of Sprints per Wave 3

Project/Wave/Release Mapping Project Wave Release Number

Build Project 1 Wave 1 1.0

Wave 2 1.0

Build Project 2 Wave 1 1.0

Focused Build for SAP Solution Manager CUSTOMER

Vale - Deployment Guide of Focused Bild Requirement to Deploy © 2018 SAP SE or an SAP affiliate company. All rights reserved. 31
 Wave 2 1.0

4.3 Create Solution with Branches, System Landscape and

Document-Type assignment

4.3.1 Create Solution

Definition:
The solution is the sum of a company’s systems, applications and processes. It acts as a container for versions of
solution documentation, one of which is the production version.

The general recommendation is to use only one solution to reflect the entire system landscape and its
documentation also for large and interconnected companies.

Assumption:
The customer is not using any Solution yet in his SAP Solution Manager system. At the end of this
section, we describe how to deal with customers, who are already using Solution(s) in their system.

How to create a Solution:

1. Enter “Solution Administration” either via transaction code SOLMADM or via the SAP Solution Manager
Launchpad (Section “Project and Process Management” => Solution Documentations). See screenshot
below.

Figure 1 - Navigating to Solution Administration

CUSTOMER Focused Build for SAP Solution Manager 7.2

32 © 2018 SAP SE or an SAP affiliate company. All rights reserved. Vale - Deplyment Guide of Focused Build Requirement to Deploy
2. To create a Solution, click on the “Global Functions” icon on the appearing screen and select “Create
Solution”.

3. To finalize the Solution creation, provide a name (and technical name) and confirm.

4. Now the Solution is created and always accessible via transaction SOLADM or the SAP Solution Manager
Launchpad.

4.3.2 Setup up branches

Definition: A branch represents a version of the solution documentation containing processes, libraries and
systems.

With the branch concept, it is e.g. possible to distinguish between documentation, which describes productive
processes and documentation, which describes processes currently in design or build.

Typically, a solution contains a production branch, a maintenance branch and a development branch.

The production branch represents the productive version of the entire solution documentation.
The maintenance branch represents the editable version of the productive solution documentation. It provides a
safe environment for performing changes.
The development branch represents the documentation of a future solution documentation.

For a S/4HANA implementation, we recommend the following branch structure.

Focused Build for SAP Solution Manager CUSTOMER

Vale - Deployment Guide of Focused Bild Requirement to Deploy © 2018 SAP SE or an SAP affiliate company. All rights reserved. 33
 Caution
The development branch must be enabled for Change Control.

Production branch
Production branch represents the productive solution
Operations branch
Operations branch to apply monitoring instrumentation
For a new implementation the Operations branch is not required during the implementation project.
Maintenance branch
Maintenance branch to change the productive solution
For a new implementation the Maintenance branch is not required during the initial implementation project. But it
will be anyway created with the creation of a new Solution.
Innovation branches
Import branch to import new best-practice processes
Design branch to design customer target operating model
Development branch to build the actual operating model

The design is the branch to be used during Build Design Support.

How to create the best practice branch structure?

1. Ensure that you are in the correct Solution in transaction SOLADM.
2. Click on tab “Branches”. The below screen will appear showing the production and maintenance branch.

CUSTOMER Focused Build for SAP Solution Manager 7.2

34 © 2018 SAP SE or an SAP affiliate company. All rights reserved. Vale - Deplyment Guide of Focused Build Requirement to Deploy
3. Mark the Production Branch and click on “Create”
The below screen will appear will appear, confirming the parent branch (in this case Production branch).
Select the usage as Development branch and not Operation branch (Operation would be used for Business
Process and Interface Monitoring), and as name of the new branch “Development” (Technical Name
“DEVELOPMENT”.

Figure 2 - Branch Creation 1

4. Enable Change Control for Development branch

Figure 3 – Activate Change Control for Development Branch

Focused Build for SAP Solution Manager CUSTOMER

Vale - Deployment Guide of Focused Bild Requirement to Deploy © 2018 SAP SE or an SAP affiliate company. All rights reserved. 35
5. To create the Design branch, mark the development and click again on Create. In the appearing pop up
window, ensure that the Development branch is displayed as parent branch. Then enter as name Design and
provide a technical name.

Figure 4 - Branch Creation 2

6. Repeat Step 5 to create the Import branch with the Design Branch as parent.

7. Finally, the branches for the Solution should look like in the below screenshot.

Please note: For Focused Build Setup it is mandatory that you create at least one additional branch (e.g. Design)
below Development branch.

4.3.3 Setup system landscape

Certain functions of SAP Solution Manager (like Solution Documentation) is referring to certain system (e.g. the
documentation of a S/4 process in the Design branch refers to a S/4 sandbox system). In the SAP Solution
Manager logical component groups and logical components are used to model the system landscape for the use
of SAP Solution Manager functions like Solution Documentation.

Definitions:
A logical component group (LCG) is a high-level view on an application. It is a group of logical components which
contain systems of a kind e.g. S/4HANA, ERP Logistics, ERP Human Resources, CRM or PORTAL.
LCGs are used to depict the execution runtime of e.g. process steps. The LCG is a release independent
placeholder for concrete systems

CUSTOMER Focused Build for SAP Solution Manager 7.2

36 © 2018 SAP SE or an SAP affiliate company. All rights reserved. Vale - Deplyment Guide of Focused Build Requirement to Deploy
A logical component (LC) refers to the concrete technical systems of a system track typically belonging to the
same transport landscape and having the same product version.

The technical systems assigned to logical components are classified according to their system role e.g.
development system, quality assurance system.

Assumption:
For the prototype we use a Demo landscape which is a simulation of transport landscape using different clients in
the same system. Creating of Demo Landscape is described in the appendix.

How a to create a Logical component group (LCG)?

1. Ensure that you are in the correct Solution in transaction SOLADM.

2. Click on tab “System Landscape”. The branches created will be displayed (see below).
3. Click on “Maintain Logical Component Groups”

4. A screen appears showing all LCGs, which are available for this Solution. Click on “Create” to create a new
LCG for the S/4HANA landscape.

5. In the next screen, provide a name and description of the logical component group to be created. Also select
the technical system type. For a S/4HANA system the ABAP Application server is applicable.

Focused Build for SAP Solution Manager CUSTOMER

Vale - Deployment Guide of Focused Bild Requirement to Deploy © 2018 SAP SE or an SAP affiliate company. All rights reserved. 37
6. Close the next screen.
The result is a logical component group, which is assigned to all branches of the Solution. See below.

7. With this you can already implement best practice content.

How to assign a system?

At the beginning of a S/4HANA project, the customer might not have built up the full system landscape yet. But
the customer will most probably have a S/4HANA sandbox to perform the fit-gap analysis. That means the
Sandbox system would be the relevant system for the activities to be documented in the branches Import and
Design.

In this example, we assume that a system S4H / client 100 acts as S/4HANA sandbox. In order to assign the
system, it must be known to SAP Solution Manager. That means the system must exist in LMDB and an RFC
exists (preferable the managed system setup was executed).

For the prototype we use the Demo Landscape instead of a S/4HANA system
1. Ensure that you are in the correct Solution in transaction SOLADM.
2. Click on tab “System Landscape”. The branches and the logical component group created will be displayed
(see below).
3. Click on “Assign Technical Systems”

CUSTOMER Focused Build for SAP Solution Manager 7.2

38 © 2018 SAP SE or an SAP affiliate company. All rights reserved. Vale - Deplyment Guide of Focused Build Requirement to Deploy
4. In the following screen, select the Import branch and as logical component “Import-Global”. Then navigate to
the field Sandbox System and open the search help to get related system/client for Sandbox role. .

5. Click OK and then again 'Assign Technical Systems'

6. For the Design branch we assign the same system/client like for sandbox.

7. On the previous window click “OK”.

Focused Build for SAP Solution Manager CUSTOMER

Vale - Deployment Guide of Focused Bild Requirement to Deploy © 2018 SAP SE or an SAP affiliate company. All rights reserved. 39
8. Repeat steps 4 to 6 for all branches according to the systematic of this table and the input from customer's
landscape entered in chapter 4.2.1

Logical Component System:Client (Role)

Import SMD:900 (Sandbox)

Design SMD:900 (Sandbox)

Development SMD:901 (Development)

SMD:902 (QA)

SMD:903 (Preproduction)

Production SMD:904 (Production)

9. In our example, the result looks like this:

4.3.4 Related Documentation

For more information about SAP Change Request Management, go to SAP Help Portal at
https://help.sap.com/viewer/p/SAP_Solution_Manager, select version 7.2 SPS 7. Open the application help and
select Change Request Management.
For more information about assigning roles, see the security guides for SAP Solution Manager at
https://help.sap.com/viewer/p/SAP_Solution_Manager.

4.3.5 Considerations, if process management is already in

use

If the customer is already using process management in SAP Solution Manager, there will be already a Solution,
which is actively used by the customer. In the very beginning there should be a discussion with the customer, if
the same – already created Solution – should be used for the S/4HANA implementation. Keeping the definition of
the Solution in mind, it’s very likely that the S/4HANA project will use the (or an) already existing Solution.

CUSTOMER Focused Build for SAP Solution Manager 7.2

40 © 2018 SAP SE or an SAP affiliate company. All rights reserved. Vale - Deplyment Guide of Focused Build Requirement to Deploy
If there are good reasons to create a separate Solution, the steps described in the previous sections are
completely valid.
If an existing Solution should be used the following general considerations apply. If you are unsure, what is the
best approach on how to deal with the Solutions/branches in a certain customer situation, please reach out to
MCC to request support.
Branch Setup
Basically, we recommend separating the S/4HANA implementation from other implementation project or the
maintenance of the current Solution. That means that we recommend a branch structure “Development” =>
“Design” => “Import” (as described in xxx) as a child of the production branch. That can co-exist with other –
already existing – child branches to the production branch.
The screenshot below shows an example, how such a branch structure could look like.
In green is an example for two branches, which were already existing, and which are used by the customer for
maintenance and other projects than the S/4HANA implementation project.
In red is the branch structure for the S/4HANA implementation project.
Both branch structures release their content to the production branch. If the same processes, process steps or
other objects are changed in different branches at the same time, there must be a conflict resolution latest when
releasing the changes. As the S/4HANA implementation is working with a different set of systems, there shouldn’t
be the need to invest much efforts in conflict resolution.

Setup system landscape

There are not too much differences compared to the greenfield situation. Basically, there is the need for a logical
component group(s) for the S/4HANA landscape(s), including logical components and systems.
If those are already created by the customer, they should be re-used. If not they must be created as it is described
in section xxx.
Import Best Practice Content
No changes compared to the greenfield situation, the best practice import should be done in the import branch.

4.3.6 Create and assign Document Types to Solution

In order to ensure a smooth transition to Build Execution, all results documents should be available (and uploaded
to Solution Manager) at the end of the FitGap / Delta Design. The management of these documents obviously
becomes easier if…

Focused Build for SAP Solution Manager CUSTOMER

Vale - Deployment Guide of Focused Bild Requirement to Deploy © 2018 SAP SE or an SAP affiliate company. All rights reserved. 41
• All necessary document types are available
• There is no ambiguity in regard to which document type to use
• It is clear where a document of a type should be stored.
• The correct templates for each document type are readily available.
• Examples for Docu Types and Templates are shipped in the name range '0SAP_XX'

Description Document Type Status Schema

Functional Specification type Gap 0SAP_01 SAP Default Status Schema

Functional Specification type WRICEF 0SAP_02 SAP Default Status Schema

Functional Specification type Interface 0SAP_03 SAP Default Status Schema

Use Case 0SAP_11 SAP Default Status Schema

Technical Design 0SAP_20 SAP Default Status Schema

Configuration Guide 0SAP_25 SAP Default Status Schema

Single Functional Test 0SAP_30 SAP Default Status Schema

Functional Integration Test 0SAP_31 SAP Default Status Schema

Business Process Description 0SAP_40 SAP Default Status Schema

User Guide 0SAP_41 SAP Default Status Schema

Mock-up 0SAP_42 SAP Default Status Schema

Training Material 0SAP_50 SAP Default Status Schema

To create your own document types based on standard types:

Go to Solution Administration → ‘Global Functions’ → Document Type Administration:

CUSTOMER Focused Build for SAP Solution Manager 7.2

42 © 2018 SAP SE or an SAP affiliate company. All rights reserved. Vale - Deplyment Guide of Focused Build Requirement to Deploy
Reduce the list of document type by entering '0SAP' in the search field and press Enter. Right click on the entry to
be copied and select “Copy”:

In the pop-up enter target document type (e.g. ZSAP_XX) and related description and confirm with OK:

Repeat this for all standard Document Types (0SAP_XX)

Enter search term that reflects you naming convention (e.g. ZSAP), press Enter, select one of the listed entries
and choose 'edit' button

Focused Build for SAP Solution Manager CUSTOMER

Vale - Deployment Guide of Focused Bild Requirement to Deploy © 2018 SAP SE or an SAP affiliate company. All rights reserved. 43
Choose the 'Upload' button to upload your own document template for the selected document type.

Use pop-up to browse for the document template and select 'Upload'

Switch back to view mode (click on the glasses symbol) to save the new document type.
Repeat the upload for all customer Document Types (ZSAP_XX)
When done exit the 'Document Type Administration' and continue in 'Solution Administration' screen while
selecting the 'Document Type' tab. Ensure that 'All' is selected on the right side, enter the search term based on
your naming convention (e.g. ZSAP), press Enter and select all relevant entries to put into the scope for your
Solution:

CUSTOMER Focused Build for SAP Solution Manager 7.2

44 © 2018 SAP SE or an SAP affiliate company. All rights reserved. Vale - Deplyment Guide of Focused Build Requirement to Deploy
4.3.7 Adjust Customizing for Document KPI Framework

To be able to use the KPI reporting for the created document types you need to adjust the related customizing. To
do so start SPRO and open the IMG note for Document KPI Framework:

For following KPIs the Document Types need to be changed from 0SAP_XX to the new types created in the
previous chapter:

KPI

FSSPEC

SFTEST

TSPEC

1. Select entry of KPI and then double-click on 'Define relevant transaction types'

Focused Build for SAP Solution Manager CUSTOMER

Vale - Deployment Guide of Focused Bild Requirement to Deploy © 2018 SAP SE or an SAP affiliate company. All rights reserved. 45
2. Select transaction type and then double-click on 'Define Classification Mapping'

3. Select the first entry and choose 'Copy' button

4. Adjust Doc. Type entry and press 'Enter'

5. Scroll up the table and delete the original entry with '0SAP_XX' Doc. Type

CUSTOMER Focused Build for SAP Solution Manager 7.2

46 © 2018 SAP SE or an SAP affiliate company. All rights reserved. Vale - Deplyment Guide of Focused Build Requirement to Deploy
6. Repeat steps 3-5 for all Classifications in this table so it looks like this

7. Repeat steps 1 - 6 for KPI 'SFTEST'

8. Repeat steps 1 - 6 for KPI 'TSPEC' for each transaction type S1CG and S1NC

4.3.8 Configure E-Mail Notifications on Document Status

Change

Note
The E-Mail notification will be sent to the E-Mail address which is being maintained in business partner.
Use the transaction b p for Business partner in your system. Search for the user and check the E-Mail in
“Communication” part of Business partner form.

Focused Build for SAP Solution Manager CUSTOMER

Vale - Deployment Guide of Focused Bild Requirement to Deploy © 2018 SAP SE or an SAP affiliate company. All rights reserved. 47
1. Start the customizing of E-Mail notification by using the transaction spro. Click on SAP Reference IMG
button and follow the path: SAP Solution Manager – Focus Build - Documentation - Activate BAdI for Email
Notification, then select the first checkmark.

2. Select the next option Configure E-Mail Notifications on Document Status Change.
In the table you see the document type, the document status and who should be notified – the owner or the
responsible. Therefore, the customizing table “Configure E-Mail Notification on Document Status Change”
contains the parameter:
o Solution Name
o Document Type
o Document Status
o Notified Role

CUSTOMER Focused Build for SAP Solution Manager 7.2

48 © 2018 SAP SE or an SAP affiliate company. All rights reserved. Vale - Deplyment Guide of Focused Build Requirement to Deploy
3. Here you can create and save the new customizing parameter, by clicking New Entries button. The F4-
Help/Contextual Help is implemented for all input fields.

Note
o The creator of the documents are always the owner of the new created document.
o The E-mail notification will be sent successfully, triggered by status change of the document. It may
take some time.
o The E-mail notification contains the document name and link to the document in MyDocuments
app.

4.3.9 Import Best Practice Content into Import Branch

With the steps described above the best practice content can be imported. It is not mandatory to have technical
system assigned to the logical component and logical component group. It is enough, if a suitable LCP exists.
Furthermore, it is mandatory that SAP note 2194123 is implemented.
How a to create import best practice content?
1. Ensure that you are in the correct Solution in transaction SOLADM or go via Launchpad group Focused Build -
Tool Lead → Solution Administration

Focused Build for SAP Solution Manager CUSTOMER

Vale - Deployment Guide of Focused Bild Requirement to Deploy © 2018 SAP SE or an SAP affiliate company. All rights reserved. 49
2. Select tab "Imports" and then "Import” on the left side.

3. In the next screen, select the appropriate best practice package and click “Next”.

4. In the next screen, please select the right branch to import the best practice content to (that’s the Import
branch), select 'New deployment' and provide a name for the deployment for your first deployment.

CUSTOMER Focused Build for SAP Solution Manager 7.2

50 © 2018 SAP SE or an SAP affiliate company. All rights reserved. Vale - Deplyment Guide of Focused Build Requirement to Deploy
5. Click in “Import”. A background job will be triggered to perform the actual import.

6. A success message indicates that the import was successfully done.

4.3.10 Release Scope-relevant Processes into Design-Branch

1. First, let’s look at what we just imported. From the SAP Solution Manager Launchpad (“Focused Build -
Architect”) click the “Solution Documentation” Tile.

Focused Build for SAP Solution Manager CUSTOMER

Vale - Deployment Guide of Focused Bild Requirement to Deploy © 2018 SAP SE or an SAP affiliate company. All rights reserved. 51
2. The top of the screens indicates which solution/branch is selected. Make sure you are looking at the Import
branch of the newly created solution. To switch to another solution, click ‘Global Functions’ → Solution. To
switch to a different branch in the selected solution, use the branch dropdown field.

3. Once a package is imported into Solution Manager you will see a folder called SAP Best Practice Import –
under the folder Business Processes. Within the folder there is a scenario per package – in case you imported
multiple best practices. All packages are listed here, the name of the scenario is the name of the best practice
package. You can now browse the content by going through the processes (so called scope items) which have
a 3-letter code e.g. BD9 and name. For each process you can open the process diagram or navigate to the
linked documents, like test cases and configuration guides.
4. Expanding the Import branch’s content (Business Processes → Best Practices Import → <Best Practice
Package> → <Best Practice Process> → Process Step) reveals the imported best practice content. In the
lower half of the screen the elements of the selected item are displayed. Here you can find for example all
executables/transactions and configuration relevant for a process but also assets such as process diagrams
or links to documentation including test scripts which can be used in scope of the solution validation
workshops.

Scenario / Best
Practice Elements (Configuration,
Business Process
Package Diagrams, Executables,

Documentation, Links, …)

5. Once the imported best practice processes have been scoped and it is clear, which are relevant for the
customer they can be released to the DESIGN branch (The IMPORT branch is merely a staging area for
scoping purposes, nothing is changed or modeled here).

CUSTOMER Focused Build for SAP Solution Manager 7.2

52 © 2018 SAP SE or an SAP affiliate company. All rights reserved. Vale - Deplyment Guide of Focused Build Requirement to Deploy
 Right click

Figure 5 - Release to Design Branch

6. To do so, right click on a relevant best practice process, then chose “Subtree Changes” → “Release Changes”
and confirm the popup. The selected process has now been released to the DESIGN branch, where gaps will
be documented, and best practice process can be adjusted.

4.3.11 Create Change Control Landscape

Create Change Control Landscape in SOLADM:

1. Select right solution and the tab Change Control Landscape
2. Right-click on empty area in the table and select new in the drop-down menu

3. Enter name and technical name

Focused Build for SAP Solution Manager CUSTOMER

Vale - Deployment Guide of Focused Bild Requirement to Deploy © 2018 SAP SE or an SAP affiliate company. All rights reserved. 53
4. Assign Logical Component Group which is reflected by the Change Control Landscape while selecting the
check box 'scope'.

4.3.12 Define Branch Mapping (SPRO)

Except for the maintenance branch and the production branch, all branches are standard type branches.
Therefore, you have to define the design and development branch of your solution sub landscape:
1. In the Customizing of SAP Solution Manager, choose SAP Solution Manager → Focused Build →
Documentation → Define Branch Mapping.
2. Select 'New Entries'

CUSTOMER Focused Build for SAP Solution Manager 7.2

54 © 2018 SAP SE or an SAP affiliate company. All rights reserved. Vale - Deplyment Guide of Focused Build Requirement to Deploy
Focused Build for SAP Solution Manager CUSTOMER
Vale - Deployment Guide of Focused Bild Requirement to Deploy © 2018 SAP SE or an SAP affiliate company. All rights reserved. 55
4.4 Setup Release Management

4.4.1 Release Planning

1. Select Release Management tile in the Launchpad

2. In the navigation area select 'Focused Build' → Release Planning

3. Select Create → Major and Minor Releases

4. Select created Change Control Landscape assign Major Release to Development Branch enter further
relevant data

CUSTOMER Focused Build for SAP Solution Manager 7.2

56 © 2018 SAP SE or an SAP affiliate company. All rights reserved. Vale - Deplyment Guide of Focused Build Requirement to Deploy
5. Check Major Release schedule and select 'Release Versions' you want to create Release Cycles for

6. Select Create → Release Cycles

7. Confirm creation of Release Cycle

8. Navigate to Release Cycle while clicking on the related entry in the release table

Focused Build for SAP Solution Manager CUSTOMER

Vale - Deployment Guide of Focused Bild Requirement to Deploy © 2018 SAP SE or an SAP affiliate company. All rights reserved. 57
9. Select Business Role of Release Manager

10. Change to Edit Mode and confirm to assign your Business Partner

11. Select Actions → Switch to "Prepare Phase"

CUSTOMER Focused Build for SAP Solution Manager 7.2

58 © 2018 SAP SE or an SAP affiliate company. All rights reserved. Vale - Deplyment Guide of Focused Build Requirement to Deploy
12. Confirm to create the task list

13. Click next and check status of prerequisites

14. Check that Task List Variant is 'S1RL', branch is Development, assign development system, transport
landscape and continue with Next

Focused Build for SAP Solution Manager CUSTOMER

Vale - Deployment Guide of Focused Bild Requirement to Deploy © 2018 SAP SE or an SAP affiliate company. All rights reserved. 59
15. To complete Task List creation select 'Create'

16. Check message that Task List has been created and Release has been switched to "Prepare" Phase.

17. Select 'Edit' and then 'Related Transactions' tab and click on the create Task List entry in the column
'Transaction ID'.

CUSTOMER Focused Build for SAP Solution Manager 7.2

60 © 2018 SAP SE or an SAP affiliate company. All rights reserved. Vale - Deplyment Guide of Focused Build Requirement to Deploy
18. In the Task List drill down to node 'Track (Source System…)', select it, and select 'Lock/Unlock Group'

19. Check that status is unlocked for Task Group 'Track'

20. Close screen and then Save and close also previous screen

Focused Build for SAP Solution Manager CUSTOMER

Vale - Deployment Guide of Focused Bild Requirement to Deploy © 2018 SAP SE or an SAP affiliate company. All rights reserved. 61
4.4.2 Define Release Profile Mapping

4.4.3 Please refer to chapter Configuring Project

Management

Creating Projects Templates

21. Download the project template XML files from SAP Note

SAP Note Description

2624412 Central Note for Focused Build 2.0 SP02 for SAP Solution Manager 7.2

22. To start Project Management, on the SAP Solution Manager Launchpad, choose My Projects.
23. Choose Projects and then choose Import Project.
24. In the Application field, select XML File.

25. In the File field, choose Browse to navigate to the file that you want to import.
26. Choose Import Selected Data.
27. Under Data for Import, select Structures and Resources.
28. Choose Check.
29. Choose Import.

CUSTOMER Focused Build for SAP Solution Manager 7.2

62 © 2018 SAP SE or an SAP affiliate company. All rights reserved. Vale - Deplyment Guide of Focused Build Requirement to Deploy
30. After uploading all XML project files, convert them into a project template.
31. In the Project Management, go to Portfolio and Project Administration and choose Project Management
Templates. Then create template derived from the imported files:
32. On the left navigation pane, choose Project Management Templates.

33. Choose Project Administration in the top navigation area.

34. Choose Create.
35. Enter the following settings to create your template project:

Field Value

Proj. Template [FB SP02] Single Project

Template Type Project

Template FB_SINGLE_SP02

New Checklist Templates None

Original Language English

Focused Build for SAP Solution Manager CUSTOMER

Vale - Deployment Guide of Focused Bild Requirement to Deploy © 2018 SAP SE or an SAP affiliate company. All rights reserved. 63
36. Release the project template by setting the status to released.
37. After the creation of the templates you can delete the previously uploaded projects again. Please refer to
chapter 5.5 Delete of obsolete projects.

4.4.4 Configuring Test Suite Extensions

Activation of BEx-Queries
38. Call transaction RSOR .
39. Open the BI content.
40. Display the Object Types.
41. Expand the Query Elements. Under Query, choose Select Objects.
42. Select all BEx queries (Business Explorer queries) with the technical name /SALM/SMT*:
Navigate to SAP Solution Manager → Test Management → Test Management MultiProvider.
Display the technical name by choosing (Technical Name off/on) ( F 7 ).
Select the following entries:

Entry Technical Name

Defect Status /SALM/SMT_DF_STATUS

Defect Status Detail /SALM/SMT_DF_STATUS_DETAIL

Defect Status Progress /SALM/SMT_DF_STATUS_PROGRESS

Test Package Status Detail /SALM/SMT_TG_STATUS_DETAIL

Test Plan Status /SALM/SMT_TP_STATUS

Test Plan Status Detail /SALM/SMT_TP_STATUS_DETAIL

Test Plan Status Progress /SALM/SMT_TP_STATUS_PROGRESS

To transfer the selected entries, choose Transfer ( F 2 )

The queries should be listed in the right area of the window.

CUSTOMER Focused Build for SAP Solution Manager 7.2

64 © 2018 SAP SE or an SAP affiliate company. All rights reserved. Vale - Deplyment Guide of Focused Build Requirement to Deploy
43. When all queries are selected for installation, choose Install and then Install in Background.

Recommendation
Use the installation in the background because the option Install might fail.

Release Management.

4.5 Project Setup

For the prototype example, we create:

• 1 master project
• 2 build projects

Focused Build for SAP Solution Manager CUSTOMER

Vale - Deployment Guide of Focused Bild Requirement to Deploy © 2018 SAP SE or an SAP affiliate company. All rights reserved. 65
4.5.1 Create Projects

Following template projects can be used for setting up the project structure of the prototype:

1. From Solution Manager Launchpad select group ‘Focused Build - Project Manager’ and then tile ‘My Project –
Project Management’

2. In the Project Management app select Create Project

Maintain Project ID, Project Name and select Project Type and Template, as well as the Start Date. In addition, you
could select the End Date and the Project Language. Also, a Project Description could be maintained. At the end
click Create.

CUSTOMER Focused Build for SAP Solution Manager 7.2

66 © 2018 SAP SE or an SAP affiliate company. All rights reserved. Vale - Deplyment Guide of Focused Build Requirement to Deploy
3. Repeat step 2 for all projects required for the prototype

4.5.2 Assign Release to Projects

1. Assign Actual Release to Build Projects and Master Project. In Project Management app click on Detail while
the root node is selected.

Afterwards the Detail(s) area opens on the left-hand side. Here you should maintain the Actual Release by
clicking the edit pencil on the lower right corner.

Focused Build for SAP Solution Manager CUSTOMER

Vale - Deployment Guide of Focused Bild Requirement to Deploy © 2018 SAP SE or an SAP affiliate company. All rights reserved. 67
 In this area you maintain the Component (Change Control Landscape) and the (release) Number.

4.5.3 Assign sub projects to master project

In the Project Management app select 1 or several build projects which you like to assign to a certain master
project by clicking Assign Master.

CUSTOMER Focused Build for SAP Solution Manager 7.2

68 © 2018 SAP SE or an SAP affiliate company. All rights reserved. Vale - Deplyment Guide of Focused Build Requirement to Deploy
In the following pop-up you see the available master projects. Select one and click Assign.

This procedure is also working the other way around. If you select a master project first you click Assign Build
instead of Assign Master and the following pop-up will display the available build projects.

4.5.4 Maintain project data (optional)

The template build projects are shipped with 2 Waves and 3 Sprints which should be fine for a prototype. If you
would like to have additional waves, please follow the following optional procedure
1. In each build project copy an existing wave that you get 4 waves with 3 sprints each. To copy a wave, select an
existing wave and select  in the lower right corner.

Focused Build for SAP Solution Manager CUSTOMER

Vale - Deployment Guide of Focused Bild Requirement to Deploy © 2018 SAP SE or an SAP affiliate company. All rights reserved. 69
2. Maintain the mandatory fields * and click create. The newly created wave will be inserted after the previously
selected wave (copy template).

If you need to change the wave sequence, it can be realized via adjustment of the Sort Number.

CUSTOMER Focused Build for SAP Solution Manager 7.2

70 © 2018 SAP SE or an SAP affiliate company. All rights reserved. Vale - Deplyment Guide of Focused Build Requirement to Deploy
3. Repeat step 1-2 until you have got the desired wave number per build project.

4.5.5 Define Wave Relationships between Master and Build

Projects

1. In master project select the root project node in structure and click on Wave Relationship in the top right
corner.→ Wave in Header area and then add Waves from Sub Projects to the related wave in Master Project

2. In the following Wave Relationship pop-up, you can see in the Header area the available waves in the current
master project. If you like to add wave relationships click in the 'add-sign' on the right-hand side of the Details
area.

3. In the next pop-up Assign Project Waves to Current Wave click on Search. If you would expect a long search
result you can also restrict the search. Within the Search Result check all waves in scope. For instance if you

Focused Build for SAP Solution Manager CUSTOMER

Vale - Deployment Guide of Focused Bild Requirement to Deploy © 2018 SAP SE or an SAP affiliate company. All rights reserved. 71
 are in the course of creating a relationship for wave 1 select all wave(s) 1 of all build projects assigned to the
master project and click OK.

4. Once you are finished with the creation of the relationships you can Save it.

5. Define further relationships according to this table

Master Project Sub Project

Wave 1 BUILD 1 - Wave 1

BUILD 2 - Wave 1

Wave 2 BUILD 1 - Wave 2

BUILD 2 - Wave 2

Cross Wave All Waves from all sub projects

6. [Optional] Check Start / End dates and duration of related waves between master and sub projects and
adjust if needed

CUSTOMER Focused Build for SAP Solution Manager 7.2

72 © 2018 SAP SE or an SAP affiliate company. All rights reserved. Vale - Deplyment Guide of Focused Build Requirement to Deploy
4.5.6 Link Q-Gates of Master and Build Projects

1. To Link Q-Gates from Build Projects to Master Project select the relevant Milestone Task in Master Project →
Create → - Same Level – Mirrored Task

2. Select ‘Assign Original Task by Project’, enter Project ID and then select ‘Find Task’

Focused Build for SAP Solution Manager CUSTOMER

Vale - Deployment Guide of Focused Bild Requirement to Deploy © 2018 SAP SE or an SAP affiliate company. All rights reserved. 73
3. Drilldown and select corresponding Q-Gate from Build Project and select OK

4. Adjust Name of Mirrored Task and Save

CUSTOMER Focused Build for SAP Solution Manager 7.2

74 © 2018 SAP SE or an SAP affiliate company. All rights reserved. Vale - Deplyment Guide of Focused Build Requirement to Deploy
5. Repeat step 1-4 for all Q-Gates from Sub Projects that should be visible to Master Project

4.5.7 Maintain Project Milestones

If the Solution Readiness Dashboard should provide meaningful data regarding overdue, the related dates for the
milestones should be maintained.
Single update of milestone
1. This can be done for each milestone separately while navigating in the structure to the related milestone

Mass update of milestones

1. To update multiple milestones in a table view, select view 'Table' and then the 'List Display' button in the 'old'
PPM UI.

2. As the table contains many columns we need to create a view to simplify the maintenance via 'Settings'
button

3. Select view 'Milestone Due Date Maintenance'

Focused Build for SAP Solution Manager CUSTOMER

Vale - Deployment Guide of Focused Bild Requirement to Deploy © 2018 SAP SE or an SAP affiliate company. All rights reserved. 75
4. Now you see just the relevant columns to be able to enter / adjust the milestone dates

5. To make it even more simple you can select a filter for the table that you only see milestones

CUSTOMER Focused Build for SAP Solution Manager 7.2

76 © 2018 SAP SE or an SAP affiliate company. All rights reserved. Vale - Deplyment Guide of Focused Build Requirement to Deploy
4.5.8 Release Q-Gate(s)

To get the date for the next Q-Gate visible in the Solution Readiness Dashboard you need to change the status of
that Q-Gate to ‘Released’.

4.5.9 Assign dedicated Release Numbers to Waves (optional)

This chapter is only relevant if you have several waves per project and you would like to deploy to production after
end of a wave instead of end of the project.

Standard approach without the need of Wave / Release Number mapping

Focused Build for SAP Solution Manager CUSTOMER

Vale - Deployment Guide of Focused Bild Requirement to Deploy © 2018 SAP SE or an SAP affiliate company. All rights reserved. 77
Special Approach that requires Wave / Release Number mapping

To define Wave / Release Number mapping for this special approach please execute following steps:
1. In the Build Project select the root Project Element in the Structure → 'Work Package' → Schedule

2. Open search help of field Release Number for the relevant Wave and select corresponding Release Number
entry in the list.

CUSTOMER Focused Build for SAP Solution Manager 7.2

78 © 2018 SAP SE or an SAP affiliate company. All rights reserved. Vale - Deplyment Guide of Focused Build Requirement to Deploy
3. New assignment of Release to Wave

4.5.10 Prepare first Wave and Sprint

To be able to start Wave or Sprint execution the related Wave and Sprint need to be released in the project
structure. To do so please follow the describe procedure below:
1. Navigate to the related Wave / Sprint in the project structure

2. Open the Details view and select Release in the drop-down list
3. Wave / Sprint is now released so Work Packages / Work Items can be handed over to development.

Focused Build for SAP Solution Manager CUSTOMER

Vale - Deployment Guide of Focused Bild Requirement to Deploy © 2018 SAP SE or an SAP affiliate company. All rights reserved. 79
5 Appendix

5.1 Useful SAP Notes

SAP Note No. Description

1384598 Information about the new remote infrastructure

1803899 Report /RPM/CUST_TABLES_COPY deletes customizing entries

907768 Change Request Management: Information about the required support package levels of
managed systems

2257213 Information about authorizations for SAP Solution Manager RFC users

1483276 Use of Customizing Parameters in DNO_CUST04, AGS_WORK_CUSTOM and

ICT_CUSTOM

1604651 Bad Performance when loading runtime repositories

1586185 Project selection fails for some transaction types

2447548 Report for Replacing Ibase component in documents

2456627 Document Type Administration Dump Object Types with Namespace

5.2 Adjust Category Schema

1. Launch Change and Release Management

2. Select Service Operations → Categorization Schemas

CUSTOMER Focused Build for SAP Solution Manager 7.2

80 © 2018 SAP SE or an SAP affiliate company. All rights reserved. Vale - Deplyment Guide of Focused Build Requirement to Deploy
3. Search for Schema ID: 'FOCUSED_BUILD', select the active one and then Create Version button

4. Select parent category you would like to create a new category for, then 'New'. Adjust new Category ID
following existing naming convention and enter Name and Description.

5. To activate new version, select the root ID of the Schema, enter Valid-From Date and Time and set Status to
released.

Focused Build for SAP Solution Manager CUSTOMER

Vale - Deployment Guide of Focused Bild Requirement to Deploy © 2018 SAP SE or an SAP affiliate company. All rights reserved. 81
The Schema will be available for new documents starting from specified Valid-From Date and Time.

5.3 Mandatory Standard Configuration for Test Suite

In order to use Test Suite as part of the Requirement-to-deploy scenario in Focused Build ensure that at least
following standard configuration tasks have been completed successfully.

5.3.1 Test Classification

CUSTOMER Focused Build for SAP Solution Manager 7.2

82 © 2018 SAP SE or an SAP affiliate company. All rights reserved. Vale - Deplyment Guide of Focused Build Requirement to Deploy
5.3.2 Analytics for Test Suite

5.3.3 Analytics for ITSM

This is required to get the data for Defect Management into BW.
1. Call transaction: SOLMAN_SETUP
2. Select Scenario IT Service Management
3. Step 4.1

4. Step 4.2

Focused Build for SAP Solution Manager CUSTOMER

Vale - Deployment Guide of Focused Bild Requirement to Deploy © 2018 SAP SE or an SAP affiliate company. All rights reserved. 83
5.3.4 Context menu for Test Steps missing in Solution
Documentation

After the setup is done you navigate to Solution Documentation and try to create or assign a Test Case of type
Test Steps. You open the context menu but cannot find the entries “Test Steps (Create)” or “Test Steps
(Assign)”.

Make sure that the piece list was activated properly (see chapter 3)
Clear SMUD Buffer with report RSMUDA_MODEL_BUFFER_RESET

Afterwards the context menu for Test Steps can be found in Solution Documentation:

5.4 Language Settings

Ensure that the default language for your browser is English:

CUSTOMER Focused Build for SAP Solution Manager 7.2

84 © 2018 SAP SE or an SAP affiliate company. All rights reserved. Vale - Deplyment Guide of Focused Build Requirement to Deploy
5.5 Delete of obsolete projects

After initially creating the project templates, the used projects can be deleted that they don’t appear in the
Solution Readiness Dashboard.
A prerequisite for deletion of projects is that the project is still in status CREATED.
Just enter the project in Read only modus, select the top node of the project tree and press Delete.

5.6 Adapting Project Reasons

In project management, you can select various project reasons:

Focused Build for SAP Solution Manager CUSTOMER

Vale - Deployment Guide of Focused Bild Requirement to Deploy © 2018 SAP SE or an SAP affiliate company. All rights reserved. 85
You can configure the project reasons in Customizing. To adapt project reasons, do the following:
1. In the Customizing for SAP Solution Manager, choose SAP Customizing Implementation Guide → SAP
Portfolio and Project Management → Project Management → Structure. → Define Project Reason.
2. Change the reasons for projects.

5.7 User Roles, Authorizations and Business Partners

5.7.1 Authorization Roles and Users in SAP Solution

Manager System

Each employee who is involved in the Requirement-to-Deploy process needs an own user in the SAP Solution
Manager system to be able to access the system.
It must be clarified with the customer who (customer himself or partner or you as delivery team) will create and
configure the needed authorization roles and users.
Further information about the definition of users and authorization roles for Focused Build can be found in the
Focused Build for SAP Solution Manager Security Guide.
Authorization Roles
With Focused Build the following composite roles get delivered for the Requirement-to-Deploy process:
SAP_OST_FB_ARCHITECT_COMP
SAP_OST_FB_ ANALYST_COMP
SAP_OST_FB_DEV_COMP
SAP_OST_FB_PROJ_M_COMP
SAP_OST_FB_REL_M_COMP
SAP_OST_FB_TESTER_COMP
SAP_OST_FB_TEST_M_COMP
SAP_OST_FB_TOOLLEAD_COMP
Beside below exceptions all these composite roles, including the single roles have to be copied into the customer
(Z*) namespace.
Exceptions: From the included single roles the following ones are ‘only’ used as navigation roles and should not be
copied but to be used as they are:
SAP_BPR_PPM
SAP_OST_SM_CRM_UIU_ARCHITECT
SAP_OST_SM_CRM_UIU_DEV
SAP_OST_SM_CRM_UIU_PROJ_M
SAP_OST_SM_CRM_UIU_REL_M
SAP_OST_SM_CRM_UIU_SM_PRO
SAP_OST_SM_CRM_UIU_TEST_M
SAP_OST_SM_CRM_UIU_TESTER
SAP_OST_SM_CRM_UIU_TOOLLEAD

CUSTOMER Focused Build for SAP Solution Manager 7.2

86 © 2018 SAP SE or an SAP affiliate company. All rights reserved. Vale - Deplyment Guide of Focused Build Requirement to Deploy
Use transaction PFCG to
• copy the roles
• generate the profiles (leave configuration as is).

Users
Transaction BP_USER_GEN can be used to create further users if they already exist in another system. Within this
transaction, the users created in chapter Error! Reference source not found. can be used as template user to
create further users.

5.7.2 Authorization Roles and Users in Systems Belonging to

the Project

Dependent on his role, each employee who is involved in the Requirement-to-Deploy process might need an own
user in the different systems involved in the project. Which authorizations / roles the different users need
depends on the project, role and application.

User Dev Test Maint QA PreProd Prod

Architect X X X X X X

Analyst X X X X X X

Developer X X X X X

Project Manager X X X X X x

Release Manager X X X X X X

Focused Build for SAP Solution Manager CUSTOMER

Vale - Deployment Guide of Focused Bild Requirement to Deploy © 2018 SAP SE or an SAP affiliate company. All rights reserved. 87
 User Dev Test Maint QA PreProd Prod

Tester X X

Test Coordinator X X X X X

Tool Lead X X X X X X

Which authorizations the users get in which of the respective systems has to be verified with the project team.

5.7.3 Defining Business Partners

For each party that is involved in the CRM based transactions of the Requirement-to-Deploy process a business
partner is needed. For the employees, the business partners can be created using transaction BP_GEN (a variant
of transaction BP_USER_GEN).
Create business partners to the template users created in chapter Authorization Roles and Users in SAP Solution
Manager System → Template Users:
1. Run transaction BP_GEN
2. Choose RFC Destination NONE
3. Using multiple selection, select the template users
4. Choose Execute to create the business partners

5. If the protocol of the test run indicates no errors, go back to the selection screen, remove the check mark to
Test Mode, and execute it again
6. Repeat the same for each relevant RFC destination (pointing to the systems involved with the project – see
also chapter Authorization Roles and Users in SAP Solution Manager System → Template Users) with the
same users

CUSTOMER Focused Build for SAP Solution Manager 7.2

88 © 2018 SAP SE or an SAP affiliate company. All rights reserved. Vale - Deplyment Guide of Focused Build Requirement to Deploy
The business partners can be checked and manually adapted in transaction BP. For Requirement-to-Deploy it is
important that the business partner exists with the BP roles Business Partner (Gen.), Contact Person and
Employee:

In BP role Business Partner (Gen.) on tab Identification, entries to all systems in which the user should be able to
create requirements, test defects, etc. are shown. Entries have to be maintained according to the following
specifications:
IDType CRM001
Identification Number <SysID><blank><installation number><blank><client><blank><user>

Focused Build for SAP Solution Manager CUSTOMER

Vale - Deployment Guide of Focused Bild Requirement to Deploy © 2018 SAP SE or an SAP affiliate company. All rights reserved. 89
www.sap.com/contactsap

© 2018 SAP SE or an SAP affiliate company. All rights reserved.

No part of this publication may be reproduced or transmitted in any
form or for any purpose without the express permission of SAP SE
or an SAP affiliate company.
SAP and other SAP products and services mentioned herein as well
as their respective logos are trademarks or registered trademarks of
SAP SE (or an SAP affiliate company) in Germany and other
countries. All other product and service names mentioned are the
trademarks of their respective companies. Please see http://www.
sap.com/corporate-en/legal/copyright/index.epx#trademark for
additional trademark information and notices.