Profiling for SAP - Analysis and redocumentation of SAP ERP

Overview of the solution offering “Profiling for SAP®”
for the analysis, re-engineering and re-documentation of
SAP® ERP systems
TransWare Software Solutions AG

Scenarios and Use-Cases

Release change and • Identify customer modifications in SAP systems
functional SAP upgrades • Eliminate or replace not used customized SAP objects like transactions or reports

• Consolidate different SAP systems or clients
System consolidation • Customizing and usage comparison of SAP systems or clients
• Process analysis for identification of Best-Practice processes

EhP-upgrades und • Analysis of system usage and customer modifications
• Identification of process bottlenecks
process optimization

BPO - business process • Re-documentation of processes to be outsourced
outsourcing • Identification of process interfaces

• Functional and organizational analysis
Splitting of SAP systems • Process analysis of system usage

AMS - application • Reverse engineering of system usage
management services • Re-documentation of SAP systems

• Review of SAP authorization management
Access control and company • SoD analysis and reviews
compliance • Monitoring of SAP access

SAP® Services Partner delivering expertise for SAP® Solution Manager and SAP
Page  2 NetWeaver® technologies with ASAP, Run SAP and BPM methodologies

Some typical questions of an SAP® person in charge
? ? ?

 Who is actively using SAP®, and in which way?
 Is the current number of existing, customer-specific “Z”
transactions and reports actually needed?
 Which areas should I focus my training efforts on?
 Do we have to update our customer-specific transactions
and reports to the latest SAP® release?
 Do I have a problem with authorizations concerning
Segregation of Duties (SoD)?
 Where shall I concentrate my validation efforts?
 Where I can increase efficiency of corporate SAP® usage?
 In the context of a system consolidation, which processes
from individual SAP® systems are to be used in the future
as Best Practice processes in the new SAP® system?


The aspects of SAP® analysis, re-engineering and re-
documentation with Profiling for SAP®
Technical Functional & Process
analysis org. analysis analysis

TransWare AG has developed a comprehensive software solution for
process and configuration analysis based on business intelligence, SAP®
NetWeaver, SAP® Solution Manager and SAP® methodologies:

1) Technical analysis
 Customer transactions and reports, user exits, development object modifications
 Authorizations management (roles, profiles, authorization objects, customizing,…); analysis of
arbitrary SAP® configuration data

2) Functional and organizational analysis
 Functional usage of the SAP® system (transactions, reports, RFC calls (from portals, external
applications), document types)
 Configuration of the technical organization levels, HR info types

3) Business process analysis
 Capture of the customer-side SAP®-supported business processes
 Creation of SAP® Solution Manager Blueprint descriptions (projects)


Analytic reports as work results of Profiling for SAP®

Output formats of the analyses:
Vergleiche
 Web-based reports, Excel reports, business charts
 Blueprint projects in SAP® Solution Manager
Profiling für SAP®  BPM modeling format

Content-related examples of analyses:
 Which transactions and reports are used within the
organizations most frequently?
 Usage of customer-specific Z, Y transactions and reports
 Organizational and authorization analyses
 Comparison of the system usage and configuration across
several SAP® clients, system roles and systems
 Activity of the SAP® users, in view of license usage
monitoring and optimization


Use and benefits through Profiling for SAP®

 Lower costs through automated procedure, as compared to manual documentation
 Cost reduction in the creation of an SAP® development object inventory, analysis of transaction usage,
customer-specific transactions and reports, user authorizations, document type usage, …
 Cost reduction for As-Is process documentation including the semi-automatic creation of SAP® Business
Blueprints for process modeling, analysis and optimization
 Reduced expenditure of time for data capture; quicker results
 Automated inventory list creation instead of conventional approach with audits and workshops
 Creation of process models from existing SAP® reference models out of the SAP® BPR, scoping of the
models by means of the inventory list data
 Via precise snapshots of the inventory, profiling of the temporal development are possible
 Higher quality; reproducible results
 Accurate usage data for transactions, reports and RFC-enabled function modules; comprises Y, Z, and
customer namespace objects, customer extensions and exits
 Accurate information on the customizing status of transactions, reports, rights configuration
 Inclusion of authorization roles, profiles, user accounts permits Governance-Risk-Compliance (GRC)
analyses like access control or 4/6-eye-principle checking (SoD)
 Easily repeatable steps with maximum reproducibility of the results



Improving the software support and maintenance of SAP®

TECHNICAL ANALYSIS

Overview: Technical analysis

Technical analysis delivers basic statements in the profiling of SAP® systems.
SAP® development objects like programs, function modules, classes,
transactions etc. are read out from SAP®. In addition, the entire
authorizations management including roles, profiles, authorization objects
and user accounts is read from SAP® into the profiling SQL database.
The data baseline from the technical analysis permits a comparison of different
SAP® systems in the context of system consolidations, or to check the
configuration of individual SAP® system roles like production, test and
development.
Further analyses permit the optimization of authorizations for the streamlining
of the authorizations management, access checking as well as SoD
analyses.


Overview of the SAP® modifications of an SAP® system
as a 3D chart

Analysis of the miscellaneous adoptions of the SAP® system’s development objects:
 Z, Y, /customer-namespace/ for SAP® transactions and reports
 SAP® modifications
 User exits

Example of an SAP® ECC 6.0 Modification types
with SAP ® modifications:
Anzahl

SAP® module


Modification types for a given SAP® module

Distribution of the SAP® modification types for a given module like e.g. SAP® MM

Critical code modifications
without modification assistant

Drill-down into object types like e.g. “programs modified”

Critical, modified
program objects


SAP® modules for a given SAP® modification type

SAP® SD
Distribution of e.g. critical SAP® code modifications
“Program changes without modification assistant”

Drill-down into object types like e.g. “programs modified”

Critical, modified
program objects

SAP® modules


Analysis of authorizations management including the use
of SAP® transactions

Analyses on different levels:
 Anonymous analyses (without user account reference)
 Analyses with SAP user account reference

Call count

SAP® objects like transactions including descriptions

Authorization objects (roles and profiles, hierarchy)



Improving the efficiency and utility of SAP®

FUNCTIONAL & ORG. ANALYSIS

Overview: Functional and organizational analysis

Functional and organizational analysis utilizes the data from the technical
analysis, and combines them with data on the usage of transactions,
reports, RFC function modules, document history and document flow,
organizational levels (of technical org units) as well as (optionally) HR info
types.
SAP® usage can be correlated with accounts, authorizations or organizational
units. Further, modifications of the standard can be identified with reference
to SAP® usage. Hence detailed statements arise as to the system usage
characteristics of the organization, as well as to license optimization.
A comparison of the usage with the customizing of SAP® across the time
frame investigated provides detailed assertions concerning the real use of
adapted objects. This way, the deconstruction of customized objects is
facilitated, as well as the upgrade of systems.


Functional and organizational analysis:
“What is used within SAP®, and by whom?”

Detailed usage analysis of SAP®
transactions on an organizational level
like e.g. business areas

Usage frequency of SAP® objects like
e.g. transactions and reports per
SAP® module


Savings potential with functional SAP® upgrades

 355 customer-specific transactions, 312 thereof
unused (about 88% unused)
 2.783 customer-specific reports, 2376 thereof
unused (about 85% unused)

 Estimation for the “functional upgrade” scenario:
Reduce by up to 50% of unused transactions and
Reduce
reports

 0.5 days needed for upgrade & validation per
transaction; 0.25 days per report; EUR 800.- per day

 Typical cost reduction:
50% (312 / 2 + 2376 / 4) * 800 = EUR 300,000.-


License optimization

168 users have been
inactive within the
analysis timeframe

Detailed analysis of
SAP® usage in different
contexts like org. units,
roles, user accounts

Minor (or no) usage

e.g. usage with reference to
module and user account


Pre-configured reports for the analysis of all aspects of
transactions, organizational levels, document types, etc.

Statistics, analytical reports Master data and organizational data

Document types, doc. flow and history



Optimizing SAP® business processes

PROCESS ANALYSIS

Overview: Process analysis of SAP®

Process analysis is based on the data from the functional and organizational
analysis, in combination with business process reference models. Those
reference models may be customer-specific, or originate from the SAP®
reference model or from Blueprint projects in SAP® Solution Manager.
By means of a specified methodology, the quality of the generated process
models – according to the SAP® systematic – is improved via workshops
with process owners.
Through an interface, the process models and their associated SAP®
transactions can be loaded into the SAP® Solution Manager process
repository which is structured into projects. These process models, as a so-
called SAP® Business Blueprint, form the basis of a detailed documentation
of the customizing of an SAP® solution.


SAP® Solution Manager Blueprint Project including
the used SAP® Transactions

 The Process Analysis has 3 sub-phases:
1. SAP® analysis and re-engineering to upload
SAP® Transactions to SAP Solution Manager
1) Analysis & 2) As-Is / to-be 3) To-be 2. As-Is Process Documentation, the business
Reengineering Process Models Blueprint process analysis for the optimization of to-be
business processes
3. Mapping the to-be processes to SAP Objects
for the SAP® Blueprint

 The Profiling for SAP® solution is a part of the
initial analysis phase and delivers the input for
the following process documentation and
optimization phases
 Transactions are loaded into the SAP® Solution
Manager project with a structure based on
existing Blueprints or Reference Models
 Profiling for SAP® comes with a methodology to
SAP® Solution Manager Blueprint Project with improve generated process maps
Business Scenarios, Processes and Process-Steps
including assigned Transactions


Profiling for SAP® for the process documentation and
blueprinting with SAP® Solution Manager (SSM)

(1) Re-engineering and (2) As-Is and To-Be (3) To-Be SAP® Blueprint
analysis processes models

SAP landscape

SAP® As-Is
Profiling for SAP® As-Is business
process maps SSM Blueprint To-Be models
process models project with SAP® objects

Development
template:

SSM As-Is project Optimized To-Be Optimized SSM
process models Blueprint project

SAP® business process overview

Corporate business processes on the basis
of the SAP® system specifications (excerpt)
Business scenario level

Process level

Unused process Active process in
with respect to the company
SAP® standard


Process level with process steps (activities) and assigned
SAP® transactions

Process steps (activity executed)

Transaction (inactive)

Process steps (activity
SAP® module not executed)

Transaction (active)

Roles or
profiles


Modeling methodologies, Best Practice and governance
for BPM in SAP® projects

Modeling methods
 are compliant with SAP® standards and conventions
 are aligned to the SAP® process meta-model
 safeguard the compliance of the SAP® Solution Manager repository business logic
“BPM Best Practice” for BPM
 employs SAP® reference models from the SAP® Business Process Repository (BPR)
 describes the connection between SAP® processes and end-to-end business processes
 specifies the application of business process architectures within SAP® projects
BPM governance
 assures BPM project progress as well as the workflows among the actors
 defines the end-to-end process of modeling using SAP® Solution Manager
 matches the BPM procedure to the course of action within the SAP® project


Profiling for SAP® for a comprehensive configuration, usage
and process analysis of complex SAP® landscapes

TECHNICAL CONFIGURATION

Solution components and information flow
SAP® system landscape SAP® Solution Manager

Profiling for SAP®
SAP® Business Process
Results Repository, reference models

Business intelligence, BPM tool SAP® Solution Manager
web-based reporting

SQL

SAP® projects and
Reporting templates Process models process repository

Three alternatives for the execution of Profiling for SAP®
for system landscape analysis
Variant 1: Execution of a job Variant 2: Execution of Profiling Variant 3: Profiling as
on the SAP® systems on SAP® Solution Manager a SaaS offering

No SAP® Solution Manager is used. ABAP 700 application server is used. Within this variant, the Profiling solution
Installation of an ABAP report and Profiling installed on a central server, is used as Software as a Service (SaaS).
execution as a job on the SAP® system analysis of the satellite systems via The analysis takes place across a
RFC. SAP® Router connection.
External service
provider
Solution Manager
Customer – SAP®
Customer – SAP®
landscape

SAP ECC 5.0, 6.0 R/3 4.6, 4.7, ECC, CRM, SCM, ... R/3 4.6, 4.7, ECC, CRM, SCM, ...


Summary
 Safety, simple use
 Central installation of the analysis software needed on an SAP® application server >700
 No software installation needed on the productive SAP® ERP systems
 Variety of supported target systems: R/3, ECC5, ECC6 as well as new SAP® modules (CRM, SCM,
PLM, SRM, ...)

 Access to the full potential of the SAP® system
 Support for a migration towards SAP® standards, employing the latest SAP® reference models
 Employment of automatically created process models where they are actually needed (SAP®
Business Blueprints in the Solution Manager, SOLAR01), in implementation/upgrade projects

 Easy processing and publishing of inventory data and process models
 BI analysis tools for the inventory data catalogs; publishing as MS Excel, HTML, etc.
 Creation of process models in the BPM format, for subsequent processing in BPM tools and viewing
by users from a business process perspective
 Access to SAP® usage, process, and configuration data without the need for technical SAP®
knowledge


Solutions by TransWare

TransWare Software Solutions AG
Fritz-Wunderlich-Str. 49
66869 Kusel
Germany

Phone: +49-(0)6381-916-0
Email: info@transware.de
Web: www.transware.de

All product, service and company names mentioned herein are for identification purposes only and may be
trademarks or registered trademarks of their respective owners


Profiling for SAP - Analysis and redocumentation of SAP ERP

Recommended

Recommended

More Related Content

What's hot

What's hot (20)

Similar to Profiling for SAP - Analysis and redocumentation of SAP ERP

Similar to Profiling for SAP - Analysis and redocumentation of SAP ERP (20)

More from TransWare AG

More from TransWare AG (8)

Recently uploaded

Recently uploaded (20)

Profiling for SAP - Analysis and redocumentation of SAP ERP