Business Process Configuration. Solution Management Application Lifecycle Management

(1)

Business Process Configuration

Solution Management

(2)

Disclaimer

This presentation is a preliminary version and not subject to your license agreement

or any other agreement with SAP. This document contains only intended strategies,

developments, and functionalities of the SAP product and services and is not

intended to be binding upon SAP to any particular course of business, product

strategy, and/or development. Please note that this document is subject to change

and may be changed by SAP at any time without notice.

(3)

Note:

Re-use of existing configuration possible.

Translation or process structure can be triggered using SAP standard translation tools.

Overview of Configuration Activities

Legend:

IMG –> SAP Implementation Guide BC Set -> Business Configuration Set CATT -> Computer Aided Test Tool

Configuration

Configure processes using predefined IMG activities

Create and assign BC Sets

Development

Assign global customer-specific

developments (programs, transactions etc.)

Test Cases

Record sample / master data as CATTs Create standard test cases (test case description, CATTs, eCATTs )

(4)

Business Process Documentation

Project documents

Business blueprint provides the capability to store and manage project documents (unstructured

content) at various level within the business process hierarchy

 Documents can be assigned to specific process

structure element such as scenario, process or process step

 Document templates delivered by SAP such as business process procedure, configuration guides

 Self-defined templates can be developed

 Full-text search based on TREX (separate installation) is supported for all uploaded documents

 Change history and versioning of documents

 Digital signature based authorizations to protect documents

Functionality

Benefits

 No real time collaboration and flexible document distribution

Limitations

Based on process element relevance,

project documentation can be uploaded using the “Proj. Documentation” tab

Standard templates

by SAP _Custom

developed templates

 Central platform to store and manage all project documentation e.g. configuration guides, manual test cases, business requirement documents

 Improves transparency and access to all project documentation

(5)

Business Process Documentation

Project documents

Business blueprint provides the capability to store and manage project documents (unstructured

content) at various level within the business process hierarchy

 Documents can be assigned to specific process

structure element such as scenario, process or process step

 Document templates delivered by SAP such as business process procedure, configuration guides

 Self-defined templates can be developed

 Full-text search based on TREX (separate installation) is supported for all uploaded documents

 Change history and versioning of documents

 Digital signature based authorizations to protect documents

Functionality

Benefits

 No real time collaboration and flexible document distribution

Limitations

Based on process element relevance,

project documentation can be uploaded using the “Proj. Documentation” tab

Standard templates

by SAP _Custom

developed templates

 Central platform to store and manage all project documentation e.g. configuration guides, manual test cases, business requirement documents

 Improves transparency and access to all project documentation

(6)

Custom Development Documentation

Integrate custom development into Solution Documentation. Keep track of development

progress. Handover of essential information to support organization to ensure business

continuity.

Scope

 Document custom code including specifications

 Explain business relevance of custom code

 List owner of custom code

Benefits

 Complete documentation of entire solution including custom code

 Handover of essential data (Owner of custom code and specification) to support organization

 Integrated in other SAP Solution Manager capabilities enabling efficient housekeeping, controlled change of custom code and complete business process monitoring

(7)

Business Process Documentation

Documentation of test cases

 The following type of test cases could be assigned

 Test documents

 Manual test cases in SAP script

 External applications

 Automatic test cases

 Function module tests

 Manual test cases can be linked to transaction of program

Benefits

 Improves transparency of test cases by providing structured and centralized storage

 Serves as basis for process oriented test management functionalities of SAP Solution Manager

Solution Configuration allows assignment of new or existing test cases to a process structure element.

Features

Test case type selection

Test cases are assigned using Test cases tab

Note

 The Test Cases tab might be not relevant if you organize tests with the SAP Quality Center by HP. It can be hidden in this case

(8)

Business Process Documentation

Configuration documentation

Benefits

Solution Configuration allows access to various customizing tools to make system settings or store

preconfiguration. It is central starting point for making system settings for your implementation project.

Features

Configuration type selection Configuration information is assigned using Configuration tab

 Transparency through central storage of all documented customer-specific developments

 Single point of entry to all

configuration-relevant information

 Pre-configuration allows time-efficient and standardized customizing

 Central and predefined access to managed system allows time-efficient customizing without reiterative logon

 SAP pre-defined implementation content

 Automated pre-configuration via BC Sets

 Perform/fine-tune configuration

 Develop and document customer-specific developments

(9)

Briefly: BC Sets are snapshots

of Customizing settings

Pre-configuration Using BC Sets

What Are BC Sets?

A Business Configuration Set (BC Set) is a set of Customizing settings



Which are grouped according to logical, business management criteria to a unit



For documentary, quality assurance and re-use purposes



Which is independent of the original Customizing tables/views

(10)

Pre-configuration Using BC Sets

BC Set Attributes Objects

Standard



Data are treated analogous to data in a transport request

Restricting customizing (Attribute

fix)



Certain customizing must not be changed by subsidiaries



This set of settings is defined by global headquarters



Subsidiaries cannot change these settings in local system (repairs are

possible)



Fix attribute is only active in activation system

Flexible customizing production (Attribute variable)



Org. units in global and local systems may differ



Option to change these values during activation

No copy option



Select if a dedicated column should not be copied into the BC Set.



This will delete the attribute icon and the column from display

(11)

Pre-configuration Using BC Sets

Objects Valid for BC Set Creation

Data you can record in BC Sets



Customizing Data



All IMG activities based on Extended Table/View Maintenance (SM30/34), including tables, views, view

clusters, view variants and view cluster variants. Additionally processing of piece lists in individual

transactions.



Further exceptions



Customizing transactions which are not based on the Extended Table/View Maintenance (SM30/34)

can in some cases not yet be put in BC Sets. The use of the fix attribute is restricted in such (individual)

transactions.

Data you cannot record in BC Sets



Master data



To avoid overwriting critical data



Transaction data



Repository objects



Further exceptions



Dummy objects

(12)

Pre-configuration Using BC Sets

Distribution of BC Sets – Two Alternative Options

Transport Request

BC Set upload/download

(13)

Pre-configuration Using BC Sets

BC Set Types

Simple BC Set

Hierarchical BC Set

BC Set from Transport

Request

(14)

Comparison and Distribution of Customizing

Customizing Synchronization - Overview

Comparison between systems

and clients

No automated customizing

adjustments

Use to control customizing

before and after distribution

CUSTOMIZING SCOUT

Comparing Customizing

Distributing Customizing

From one to multiple target

systems and components

Automated customizing

distribution possible

Use to distribute defined set

of customizing between

components

CUSTOMIZING DISTRIBUTION

Goals



Ensures that customizing of certain objects is in sync across systems



Reuses customizing (e.g., of SAP R/3, SAP ECC) in other systems of other components

