SAP Solution Manager
IMP Solution Manager T Codes
IMP Solution Manager T Codes
RMMAIN : Roadmaps
SOLAR_MIGRATION : Migration from Value SAP
SOLAR_PROJECT_ADMIN: Project Setup
SOLAR01 : Blueprint
SMSY : Technical SAP Solution Manager Setup
SICF : HTML Framework
SPRO : SAP Solution Manager Customizing
ASAP Implementation Roadmap
1.
Project
Preparation: (Important Transaction codes & Description)
RMMAIN : Roadmaps
SOLAR_MIGRATION : Migration from Value SAP
SOLAR_PROJECT_ADMIN: Project Setup
SOLAR01 : Blueprint
SMSY : Technical SAP Solution
Manager Setup
SICF : HTML Framework
SPRO : SAP Solution Manager
Customizing
2.
General
Project Management (Project Preparation Phase)
Phase Startup, Project Initiated, Project Plan Started, Phase Sign Off
Detail project
schedule : Storage in SAP
Solution Manager (transaction RMMAIN
or SOLAR01) ASAP and/or Roadmap
Composer and/or external
3.
Project
Strategic Framework
Project Strategic Framework, Portal
Content Program
4.
Implementation
Standards
Implementation Project Standards
- ASAP is methodology and SAP Solution Manager the tool to be used
- SAP Solution Manager needs to be positioned during Consulting Sales
Phase
- SAP Solution Manager setup before or during Project Preparation
- Create Implementation project in SAP Solution Manager
- Define project organization
- Define standards in SAP Solution Manager
Installation, Configuration (following
Config Guide for all "Usage Scenarios"), RFC connections, System
users, Transactions SMSY and SOLAR_PROJECT_ADMIN (Create Name, pick language,
define logical components) Usage of transaction RMMAIN: ASAP and/or Roadmap
Composer
Status values, Keywords and/or Project Templates
Framework for Org. Change
Management (Standards Meeting)
Define standards for project and SAP Solution Manager
Usage of transaction
SOLAR_PROJECT_ADMIN: Project documentation templates, status values (and
keywords if needed)
5.
Technical
Infrastructure Planning: (Technical Requirements and Design)
System landscape
Possible usage of transaction SMSY for
reporting (landscape overview, SP level etc)
6. Training Plans: (Project Team Skills
Development (Project Preparation Phase))
Preliminary End User Training and
Documentation Strategy
Define Training and Documentation
Strategy (eLearning Management in SAP Solution Manager)
ELearning Management in SOLAR02: Map
training content and job roles to process structure, publish Learning Map
MILESTONE: High Level Business Requirements
Completion
1.
Business
Blueprint:
SOLAR_PROJECT_ADMIN : Project Setup
SOLAR01 : Blueprint
SOLAR_EVAL : Activities Status Tracking
2.
General
Project Management (Blueprint Phase):
Phase Startup
Executing & Controlling Results
Project Plan Completed
Phase Sign Off
3. Training and Documentation Plan (Blueprint
Phase): Project Team Skills Development (Business Blueprint Phase)
End User Training and Documentation
Strategy
Define Training and Documentation
Strategy (eLearning Management in SAP Solution Manager)
eLearning Management in SOLAR02: Map
training content and job roles to process structure, publish Learning Map
4.
Solution
Business Requirements:
Business Organizational Structure: Create
organizational structure in SAP Solution Manager; Review of customer
requirements
Usage of
transaction SOLAR01: Assign organizational units to process structure and
logical component, pick pre-defined content from BPR, enhance org model if
needed
General
Settings and Master Data: Create Master data in SAP Solution Manager;
Review of customer requirements
Usage of
transaction SOLAR_01: Assign master data to process structure and logical
component, pick pre-defined content from BPR, enhance master data model if
needed
Business Scenario Definition: Review of
customer requirements
Usage of
transaction SOLAR_01: Build customer solution based on Scenarios, Business
Processes and Process Steps, Assign logical component to process steps, pick
pre-defined content from BPR, enhance process model if needed, document
processes in templates
MILESTONE: Business Scenarios Defined
1. Organizational Change Management (Blueprint
Phase): OCM - Organizational Alignment Action and Executive Sponsorship
Plans
OCM - Communication Plan
2.
Detailed
Business Requirement:
Portal Content Requirements
Portal Content Structure Design
Business
Process Requirements
Define gaps where customer
requirements are not met by SAP standard
Usage of
transaction SOLAR_01: Map customer
requirements to SAP standard solution, identify gaps and document gaps in
pre-defined documentation templates (basis for technical blueprint and/or
development specifications)
Development Requirements:
Define standards
for project and SAP Solution Manager (template for development requirement)
Usage of
transaction SOLAR_PROJECT_ADMIN:
Project documentation templates, status values (and keywords if needed)
Assemble, Review and Sign off Solution Business
Blueprint
Define and manage
Business Blueprint
Usage of
transaction SOLAR01: Process model;
possible to lock process model in transaction SOLAR_PROJECT_ADMIN
Generate Business
Blueprint based on process decomposition (table of contents) and detailed
documents (added under Project Documentation); multiple selection criteria
available to filter BBP as needed
3. Development Procedures and Conceptual
Design of Developments
Life Cycle Data
Management Strategy
Conceptual Design
of Developments
Development Capability
Approved
Development Work
Enhance project
organization (Development Team)
Usage of
transactions SU01 (create users in
SAP Solution Manager), assign users to your project (SOLAR_PROJECT_ADMIN)
4. Authorization Requirements:
Authorization
Requirements and Design
Define user roles and authorizations
Transactions defined in SOLAR01 will be useful as input to
define the end user roles; Add job roles to process structure from PP01 in
transaction SOLAR02
Portal User
Management Concept
Portal Security Concept
No comments:
Post a Comment