SAP solution Manager.pdf

MIKE STOKO [ ASUG INSTALLATION MEMBER MEMBER SINCE: 2003

BOB GAUTHIER [ ASUG ASSOCIATE MEMBER MEMBER SINCE:1998

CHRISTINA CRONE [ ASUG INSTALLATION MEMBER MEMBER SINCE: 1999

] Documenting SAP Solutions with the latest Tools: Solution Manager

Enterprise Edition and RBE Plus

Lori Sanders, Enowa Winni Hesel, Enowa Salpi Makdessian,

Bombardier Aerospace

2

[

Real Experience. Real Advantage.

Agenda

  Overview of ways to document your solution in SAP Solution Manager

  What is the Business Process Repository and what does it have to offer?

  Example: Using RBE Plus to populate your current business processes

  Stay in control: Using the Solution Documentation Assistant to keep your documented solution current

  Customer experience: How Bombardier used RBE Plus to document their business processes in Solution Manager

  Q&A 2

3

[


You are already live?

  If you are already live with one or more SAP products and you want to use certain functionality in Solution Manager such as Business Process Monitoring, Upgrade Projects, Documentation features, you have to re-document your SAP footprint in Solution Manager

  There are three ways to get your solution documented in Solution Manager:   Manually using individual process design   Manually using the Business Process Repository (BPR)   Automatically using 3rd party tools, such as

  RBE Plus (based on the BPR) - from IBIS   LiveCapture (based on menu structure) - from Intellicorp   Business Process Modeling tools, such as ARIS or Control

2007, if you already have your current business processes modeled in these tools

3

4

[


Agenda






  Q&A 4

5

[

Real Experience. Real Advantage. 5

What is the BPR?

  A repository of standard SAP business scenarios, processes and process steps including associated transactions, standard SAP documentation and configuration objects

  Included in a separate content component   Included in Solution Manager as part of the

component ST-ICO (currently on 150_700 SP15)   Can be updated separately from the rest of the SAP

Solution Manager system   Also contains roadmaps

6

[


BPR Structure

Business Scenario

BusinessProcess

ProcessStep

A Business Scenario is a set of processes that define a business task in a comprehensive and self-contained manner on a macro level

A process is a set of logically related activities performed to achieve a defined business outcome (cf. Davenport & Short, 1990)

A process step is an elementary activity performed to accomplish a process

Order to Cash

Inquiry Processing

Create Inquiry

VA11 Create Inquiry VA12 Change Inquiry VA13 Display Inquiry VA15 Inquiries list V.03 List of Incomplete Inquiries

Transactions Transactions

Transactions

7

[


Business Process Structure – Built Out

Business Scenario

BusinessProcess

ProcessStep

Componente.g. SAP ERP

Transactions Transactions

Transactions

ProjectDocs

ProjectDocs

ProjectDocs

Config Objects & Docs

DEVObjects & Docs

Config Objects & Docs

DEVObjects & Docs

Test Cases

Test Cases

8

[


How do you access the BPR?

  Two ways to access the BPR:   Project dependent - You can access the BPR from

within an implementation project or a template project

  Project independent - You can access the BPR through a WebDynpro - Follow the instructions in the IMG to activate the services and include the WebDynpro in your Favorites

8

9

[


Project-dependent view

9

Available via transaction SOLAR01 (Business Blueprint)

10

[


Project-independent view

10

Available in Solution Documentation Assistant work center or via webdynpro SM_BPR_OVERVIEW

11

[


Agenda






  Q&A 11

12

[


Challenge: Taking an Inventory

  To take a complete inventory of your business processes or to simply re-document the solution(s) in use today, the following is required:   Detailed analysis on which SAP standard transactions are

used   Detailed analysis on which custom (Z/Y-) transactions are

used   Detailed analysis on customizing, reporting use, interfaces,

developments, etc.   All of the above, across all application areas or business

scenarios and processes, and across all divisions and regions

  In multi-system landscapes: Repeat the above for each system!

12

13

[


Tool-based Approach vs. Manual

  Challenging the manual approach   Doing this manually will consume a lot of resources,

time, and money   Doing this manually may result in much less than

100% accuracy   The risk of missing important pieces is considerably

high   Senior Management will most likely not approve the

budget and resources necessary to do this

  The only viable option to support the process of taking an inventory of your SAP system usage is a tool-based approach

13

14

[


Example tool: RBE Plus

  No tool licenses needed – available as a service   Analysis ABAP programs will have to be promoted to your

production system   Analysis ABAP programs will be executed by your Basis team   These ABAP programs will create extract files   ABAP programs and extract files are typically exchanged

through a secure online project room (www.rbe-online.com)

  RBE Plus will create an XML file that can be uploaded into your Solution Manager system

  A workshop to validate and discuss analysis results is recommended

14

15

[


Reverse Business Engineering

15

  RBE Plus creates your specific process model based on SAP’s most current BPR Content

  Includes enhanced assignment of SAP transactions as well as custom transactions

  Additional reports are available that detail custom objects and use of custom transactions, etc. Production SAP

System(s)

RBE Plus

ABAP

Content Database

Reports

XML

Reporting

RBE Plus

ABAP RBE Plus

ABAP

RBE Plus Reports

Extract Files

16

[


RBE Plus - What’s extracted?

16

What’s extracted? Transaction Monitor (ST03) data, customizing, documents, master data, roles and authorizations

Reference Structures (SAP BPR)

mySAP Business Suite: Business Process Model 2005 mySAP ERP ECC 5.0/6.0

Transaction check steps All SAP standard and custom transactions

SQL Check Steps (approx. 15,000 SQL statements against tables)

ERP Accounting and Logistics approx. 4,500 ERP Production and Service approx. 2,500 ERP Project and Investment approx. 700 ERP Human Resources approx. 4,000 Quantity Structures/Basis approx. 900 SCM/APO, CRM, other approx. 1,300

Industry Solutions Public Sector, Utilities, Retail, Automotive approx. 1,100

Basis and Technical Cross-Client Customizing, Communication, Enhancements, Modifications, Roles and Authorizations

17

[


Upload AS-IS using standard SAP

17

 To load the analysis results into Solution Manager, call the standard program in Solution Manager RS_SOLAR_IMPORT_STRUCTURE_2

Includes mapping to BPR content

XML

Verify your import worked

A

B

C

18

[


Results: Automatic Scoping

18

 Based on RBE Plus results, the structure is built automatically based on SAP’s BPR with everything set to “in scope” (checkbox active) that is used in the SAP system

 Same fortransactionsin use

19

[


Automatic Population: SAP Document.

19

 After the import of the XML file, the tab “Gen. Documentation” is automatically populated with a link to SAP’s standard online documentation

20

[


Automatic Population: Config. Tab

20

 Automatically populate SAP-standard IMG objects which are mapped to business process in the BPR

21

[


Lessons Learned from > 250 Projects

  Most customers that used this approach confirmed that they saved between 40-70% of time and effort vs. the manual identification of the AS-IS   Best Practice: Regardless of the release you are on, select to map

your active processes against the BPR structure of ECC6.0   Manual effort is still required to assign custom transactions to

the BPR business processes   SAP’s BPR is not 100% complete

  There are currently more than 1,000 SAP standard transactions that SAP has not assigned to any business process in the BRP

  RBE Plus provides a report of all active (used) and not active custom transactions, as well as active SAP-standard transactions that are not assigned by SAP in the standard content, hastening the assignment process

21

22

[


Agenda






  Q&A 22

23

[


SDA - What it is and its Prerequisites

  Solution Documentation Assistant is new functionality in Solution Manager Enterprise Edition (2008 - as of SP16) that utilizes primarily transaction monitor log files to provide reports of what is still in use in your production environment

  Pre-Requisites for using the Solution Documentation Assistant   Solution Manager is connected to your production

environment using “trusted RFC’s”   You have maintained a logical component for the

system(s) to be analyzed   You have a fully populated implementation, template or

upgrade project that includes your relevant business scenarios, processes, steps and transactions

23

24

[


Steps to run an Analysis

  Check pre-requisites are met (previous slide)   Create Analysis Project and Analysis

  Use the new SDA work center in Solution Manager   Run SDA scan of your production system

  Analysis creates a job using RDSWP_RBE_EXECUTE   Our experience shows that running this with two

instances (ERP 6.0 and BI) with 2 months worth of log file data available in the transaction monitor takes a minimum of 40 min.

  Review Analysis Results   Update Solution Manager Project

  There is no automatic or direct update to the Solution Directory available

24

25

[


New Work Center

25

26

[


Create Analysis Project

26

27

[


Create & Perform Analysis

27

28

[


Review Analysis Results & Update

28

29

[


SDA - Challenges

  Very little analysis content, analysis is primarily based on transaction execution only and not on existing master data, configuration or existing documents

  No comparison of multiple analysis - always “one time shot”

  All analysis results are read-only and can not be edited before updating the original project

  Analysis structures are read-only - if a blueprint change is applied to the original project, a new analysis has to be executed

29

30

[


Agenda






  Q&A 30

[


Solution Manager Roadmap

  Implemented Solution Manager 3.2 in February 2007   Upgraded to Solution Manager 4.0 (7.0) September

2007   Currently have 4-tier landscape running on SPS 15   Enterprise Edition and Work center functionality will

be implemented Q4 2008.   Modules currently used:

  Implementation: Blueprint and Configuration   Service Desk   Test Workbench   ChaRM

[


History

  SAP Implementation background   Delivered R/3 4.7 projects using our in-house Lotus

Notes based tool   Lack of consistency when building project structure   Process modeling tool not maintained after project

delivery   Diverse Business areas: Manufacturing, After Sales and

Non-product   Delivered SAP HR ECC 6.0 to multiple sites using

Solution Manager 7.0

[


Implementation

  Contacted IBIS America for RBE Plus services   Ran Potential and Situation Analysis in December 2007   Held on-site workshops in February 2008 to assign Z

-transactions to correct Business Process nodes   Documented as-is business processes in Solution

Manager   3 different business areas   Processes were not maintained properly   Unused Z-transactions required analysis

  Built a Global template for reusability and integration

[


Key Benefits

  Facilitated the documentation of AS-IS processes which would have been time-consuming and very difficult to do manually

  Use of Standard BPR in Solution Manager   Identified all used and un-used Z-transactions for

further analysis   Provided comprehensive summary reports by SAP

module that could be used to optimize your system

35

]  Thank you.

Salpi Makdessian SAP - Application Specialist Lead SAP CC Solution Manager Team

Bombardier Aerospace [email protected]

36

]  Thank you.

Lori Sanders Practice Manager, SAP Solution Manager

Enowa LLC [email protected]

Winni Hesel Partner

Enowa LLC [email protected]

Documents

SAP solution Manager.pdf