Focused Build for SAP Solution Manager - Security Guide - 1.5

Sep 11, 2026

Security Guide for Focused Build on SAP Solution Manager ST-OST 2.0 SP 5 provides typographic conventions and structured documentation history. It defines how to interpret examples, emphasized terms, technical object names, on-screen output, exact user entries, and variable entries using standardized styles and placeholders. The guide also records support-package applicability and changes across versions, including role and persona updates, extensions, authorization objects, and enhancements aligned to specific ST-OST and ST releases.

LanguageEnglish

CategoryPresentations

FormatPDF

Pages58

Reading Time20 min

AccessFree to download

Typographic Conventions

How to Read Examples and Emphasis

Technical Names, Output, and User Entry Rules

Document History

Support Package ST-OST 200 Changes

Versioned Updates and Role/Extension Modifications

Security Guide Document Version: 1.5-2020-01-20 PUBLIC Focused Build for SAP Solution Manager ST-OST 2.0 SP 5 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. | | | | | | | | 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, | F2 | or | ENTER | . | | | | | | | | | PUBLIC Focused Build for SAP Solution Manager 2 © 2019 SAP SE or an SAP affiliate company. All rights reserved. Typographic Conventions Document History | Support Package ST-OST 200 | Date | Change | | --- | --- | --- | | | 2016-11-28 | General
· Valid for ST-OST 200, ST 720 SP03-SP04 | | SP01 | 2017-07-01 | General
· Valid for ST-OST 200 SP01, ST 720 SP05 Introduction
Adapted description
Focused Build-Requirement to Deploy Applications
Adapted description
CRM Transaction Types Renamed and adapted description
Matrix: CRM Transaction Types to Business Roles Renamed and adapted description
Main Personas New persona configurator Technical roles Adapted description Single roles New chapter added
Changes of single roles are documented in the description tab of the specific role
· Adapted single roles: SAP_OST_FB_ANALYST, SAP_OST_FB_ARCHITECT, SAP_OST_FB_DEV, SAP_OST_FB_DGP, SAP_OST_FB_PROJ_M, SAP_OST_FB_REL_M, SAP_OST_FB_TESTER,
SAP_OST_FB_TEST_M, SAP_OST_FB_TOOLLEAD, SAP_OST_JIRASYNC Composite roles
Changes of assignments of single roles are documented in the description tab of the specific role
· New roles: SAP_OST_FB_CONFIG_COMP
· Adapted roles: SAP_OST_FB_ANALYST_COMP, SAP_OST_FB_ARCHITECT_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 | Focused Build for SAP Solution Manager PUBLIC Document History © 2019 SAP SE or an SAP affiliate company. All rights reserved. 3 | Support Package ST-OST 200 | Date | Change | | --- | --- | --- | | | | Focused Build-Extensions
Deleted and new structure created for each scenario chapter
Focused Build-Standalone Extensions Change Request Management New chapter
Cross Landscape Distribution Adapted description
Change Request Management Repack Adapted description
Retrofit Automation New chapter Retrofit for BWNew chapter
Test System Refresh New chapter
Multi Tenancy New chapter
· New authorization object: /SALM/MTST
Release Batch Import New chapter Electronic Signature New chapter
Focused Build-Standalone Extensions IT Service Management
New chapter Simple IT Request Adapted description
· Adapted roles: SAP_OST_SSR_MANAGER | | | 2017-09-13 | Technical Roles
Correction of table displaying the mapping between the personas, composite roles and CRM business roles | | SP02 | 2018-07-12 | Matrix: CRM Transaction Types to Business Roles: project Manager now as well allowed to create and change S1BR

FAQs

What do the documentation typographic conventions specify?

They define how to interpret quoted screen text, emphasized expressions, technical object names, on-screen output, and exact versus variable user entries in the documentation.

What does the document version indicate?

It provides the guide’s release level, shown as Document Version 1.5-2020-01-20.

How is support-package applicability documented?

The document history lists support-package identifiers and dates and states which ST-OST and ST release ranges the changes are valid for.

Sep 11, 2026

Uploaded by Jordan Avery