business blueprint generation guide 2009 v07

© 2011 SAP AG. All rights reserved. 1

G

Y

R

R

Client

Project Name

Opportunity Owner

CEM / CP

AE / AM

Date

BUSINESS BLUEPRINT GENERATION

Business Blueprint Documentation Guide

BLUEPRINT GENERATION

Subject of Business Blueprint

Blueprint Generation with Solution Manager

Customer Acceptance

Version Management


Blueprint Approach and Key Deliverables

A Blueprint is defined through a body of documents

A Blueprint is defined through a body of documents

Business ScenarioBusiness Scenario

Business ProcessBusiness Process

Business process step

Business process step

Activity/Transaction

Activity/Transaction

Business Area/ Process Group

Business Process or Variant

(Transaction e.g. VA01 )

(Data entry e.g. customer name)

Organizational Structure Req. & Design doc

Business Scenario Requirements and Design doc

Business Scenario Requirements and Design doc

Business Process Requirements and Design doc

Master Data Requirements doc

Functional Specification documents (RICEFW)

Technical Solution Doc (open)



Business ProcessFlow diagram

ProjectProject

User Role Documentation doc

Business Process List doc

Scope Key Decision Documents doc

Scope Key Decision Documents doc

Value Maps [new in 2009]

Blueprint Approach Workshop Guide doc*

* Guideline documents to facilitate Blueprinting * Guideline documents to facilitate Blueprinting

Field Service Modeling Handbook V4 [new in 2009]* or refer to the Link: SAP Process Modeling Handbook, BPX, Community Wiki site*

Blueprint Approach Guide*

Solution Manager Process Decomposition

Solution Manager Process Decomposition


Blueprint Documentation : Types and Formats for Storage in SAP Solution Manager

ZBSC Business Scenario Requirement Document Doc

ZBPR Business Process Design Document Doc

ZBPS Business Process List Xls

ZBTS, ZBTH, ZBTC Basic Documentation ( System-,Architecture-,Hard-and Software Landscape )

Doc

ZBMD Master Data Specification Doc

ZBOR Organizational Structure Design Doc

ZBUR Business User role document Doc

ZBGP Gap Document Xls

ZTTC Test Case Description Doc

ZTSC Test Scenario Document Doc

ZFED Functional Specification Doc


Blueprint Documentation : Types and Formats for Storage in SAP Solution Manager

ZFSR Development SOA Requirements Doc

ZEUT Training Document Doc

ZBSO Scope Key Decision Document Doc

ZBPF Business Process Flow Diagram VSD/ARIS

Generating the Blueprint document

When the Blueprint is generated, the process structure provides the list of contents of the document, and the actual contents are entered in the document for each structural element (contents maintained in the template). More technical topics like system landscape, data migration strategy should be entered in a comprehensive Blueprint document and then combined with the SAP Solution Manager Blueprint.




Customer Acceptance

Version Management


Assemble Business Blueprint from SAP Solution Manager

ASSEMBLE BUSINESS BLUEPRINT

Once the project team is satisfied that the Business Blueprint document is complete and the

quality of the content meets the project standards, the document can be generated from the

Solution Manager.

The Business Blueprint documents will typically need to be edited after generation, to apply

formats, logos, and pagination. This is usually achieved using Microsoft Word and/or other

desktop publishing application.

Various versions and combinations of Business Blueprint documentation can be generated

to meet the requirements of different audiences. These examples are included to provide

consultants and project managers with an understanding that the Business Blueprint can be

used for a wide variety of objectives, outside of a description of the end-state business

process model.



Executive summary

An executive summary version generated from scenario level documentation is useful

for providing senior level business managers a higher-level description of the end-state

business process model.

Complete Business Blueprint

The complete version of the Business Blueprint includes all section, from scenario level

through process steps, and also includes all of the templates used by the project team to

describe the business solution. This would include RICEFW ( Report, Interface,

Conversion, Enhancement, Form, Workflow) development specifications, organizational

change management documents, white papers, graphical process models.



Development catalogThis catalog would include a description of each WRICEF development identified during

the business requirements definition, and summarized in a Development List. This

catalog assists the project team in estimating the time and cost to completion of the

project.

Organizational impact summary

Most implementation projects will result in changes to the organization. A description of

these changes and the impact they will have on individuals or groups can be useful in

discussions with business leadership on the level of support needed to ensure success.

Technical solution / architecture

In complex environments the description of the end-state technical solution and

application architecture provides valuable information for decision-makers.


Generation Business Blueprint with SAP Solution Manager – How To -

Menu: Business Blueprint =>Generate Blueprint Document• Scope - Structure

Structure: Decide at which Level Blueprint should

be generated (Project, Scenario, Process)

Usual Scenario Level will be used for this.

Decide weather Graphic Flow of Scenarios/

Processes should be part of BP• Scope - Documents

Decide which Document Types should be part of

holistic generation of Business Blueprint

Decide weather included external Links should be

dismantled .• Only Document with Attribute “Blueprint – Relevant”

Will be considered


Creation of Business Blueprint in Solution Manager – Procedure 1/3

Procedure:

1.Start the Business Blueprint transaction, SOLAR01

2.Select Business Blueprint → Generate Blueprint Document...

3.Flag which graphics to include in the generated document (Scenarios and/or Business Processes) under the General Tab.

You can specify a shared repository or drive (under directory) for the generated blueprint document to make the blueprint document available to other project team members.

4.Specify what Structure Elements and Documents to consider in the Business Blueprint generation in the Scope Tab. You can, for example, filter by document type or status, or select from the project structure by choosing Structure.

5.In the Display Options Tab which Structure Elements and Document Attributes to include in the Business Blueprint can be selected. If a document occurs several times in the blueprint, you can either include the entire document several times, or set a link to where the document is included once. Select or deselect Insert Link under Documents Used Several Times. Enter the required data and choose Execute. All required documents are downloaded to the destination chosen and a dialog appears. Select Continue. Your text-processing (Word) program starts. A dialog box gives you information concerning a macro that should be run in Microsoft Word.



Procedure:6.Choose the menu Tools → Macro → Macros. Then select the macro SAP_BUSINESS_BLUEPRINT from the list and choose run. The Blueprint document will now appear. You can use the upload function on the Project Documentation tab to edit the Business Blueprint document further or publish it for users in the Solution Manager.

To print the document, use the print function in the text-processing program. To save the document to a local directory, use the save function. If you want to edit the Business Blueprint document or make it available to users in the Solution Manager, use the upload function in the Project Documentation tab to upload the document. Deselect the Flag “Business Blueprint Relevant” to ensure that the document is not included in the next Business Blueprint document.



Note:

Blueprint generation will download all relevant documents to your local hard disk first. Select criteria to

minimize generation time

It is recommended not to use Numbers for Titles for your document Table of Content because of

automatic Numeration during generation of Blueprint with SolMan. (see Page 17)

Not all documents linked in the Solution Manager will be embedded in the Business Blueprint

Document. Only MS Formats + Adobe will be supported. Only those documents with the documentation

attribute “Business Blueprint Relevant” set will be included in the Business Blueprint Document.

Freeze scope and locking of documents can be set in SOLAR_PROJECT_ADMIN on the Scope tab.


Creation of Business Blueprint in Solution Manager – Customizing 1/2-

Customizing for Generation of BlueprintTransaction SPRO ->Cross-Scenario Settings ->Generation of Documents ->Adjust Template Files for Generation of Business BlueprintThe system uses the following three files, which are in the Knowledge Warehouse, to create the Business Blueprint document

The initialization file BLUE.INIThis file contains generation options which allow simple parameterization. The options are described as follows in the initialization file.

SAVE DOCUMENT AFTER INCLUDING # DOCUMENTS [Choose # between 1 and 32768; Default = 50]: 50INCLUDE MS POWERPOINT DOCUMENTS [1 = All pages via Clipboard (default); -1 = First page via Clipboard; 0 = As ActiveX object]:1INCLUDE MS VISIO DOCUMENTS [1 = All pages via Clipboard (default); -1 = First page via Clipboard; 0 = As ActiveX object]:1INCLUDE MS EXCEL DOCUMENTS [1 = All sheets (default); 0 = As ActiveX object]:1NUMBER CONVERSION IN MS WORD DOCUMENTS [1 = Convert numbers to text (default); 0 = Do not convert numbers to xt]:1SYSTEM TEXT WITH GREY BACKGROUND [1 = light grey; 0 = white (default)]:0INCLUDE DOCUMENTS IN TABLE OF CONTENTS: [1 = Include documents, 0 = Do not include documents (default)]: 0NEW PAGE BEFORE INCLUDED DOCUMENT: [1 = Insert page break before including a document, 0 = Do not insert page break (default)]: 0


Creation of Business Blueprint in Solution Manager – Customizing 2/2 -

Customizing for Generation of BlueprintTransaction SPRO

The MS Word document SOLARBLUEPRINT.DOCCreate your own file, if you, for example, want to use a different header or footer in the generated document.

The MS Word document template SOLARBLUEPRINT.DOTThis document template contains the VBA macro SAP_BUSINESS_BLUEPRINT, which generates the document.

These files are loaded when the document is created in the file system of the fronted, and determine among other things the layout of the generated document.

To adjust the layout of the document to be generated, system-wide, to your requirements, create your own versions of these files in the Knowledge Warehouse.

You can adjust the macro to your requirements, but the data transfer interface is determined by the Solution Manager system.

Modifying the macro destroys the certificate which was created for the macro delivered by SAP.


Generated Blueprint in SAP Solution Manager Content (Example)




Customer Acceptance

Version Management


Generating Business Blueprint from Solution Manager

Refer to ASAP Roadmap “Generate Business Blueprint”

Compare scope to Charter and Contract (SOW) to identify differences

Managing Acceptance - Obtaining sign-off

Begin socializing the sign-off process with the customer PM and sponsor early in the BP phase

How formal is the customer about these types of sign-offs?

Push for a more formal process but recognize what their norms are

Review with “approver” for final sign-off. Use confirmation sessions, demo or Conference Room Pilots (CRP) as necessary to drive clarity and acceptance

Record exceptions/issues in issues log

Drive exceptions/issues to closure. This is the main activity after workshops

Obtain sign-off as soon as possible (do not accept a delay in customer sign off!)

Business Blueprint Acceptance and Approval


Significance of Acceptance in Legal Terms

The creation of a Business Blueprint by SAP is to be characterized as a contractual service - even if the customer has taken part in the creation of the document.Contractual services are subject to acceptance, that is, every Blueprint created by SAP must be accepted by the customer.Acceptance must be provided in writing in the form of an acceptance record (see DocExplorer for template).If acceptance is refused, the matter should be referred to Legal to arrange further action.Billing may only take place and sales shown upon receipt of formal acceptance (acceptance record as confirmation). Upon acceptance of the Blueprint, the contractual obligations of SAP are limited to those services contained in the Blueprint document and assigned to SAP.The Blueprint is the basis for subsequent change requests: All requests not included in the Blueprint can only be realized as change requests subject to additional fees.


Customer Acceptance of Blueprint

Request written acceptance of Blueprints created by SAPWhen possible: Schedule a project event for the acceptanceDon'tsBegin realization without an accepted Blueprint (if SAP did not create the

Blueprint: do not begin if the Blueprint has not been completed and received by SAP)

Too little time for the customer to check and accept the Blueprint (approx. 5 days is reasonable)

Lack of rules for dealing with open pointsIgnore the contractual rules for acceptance




Customer Acceptance

Version Management


Document Version Management & Status Proposal

Document type: Word editable

Activity Version Status Change ? Status-Change

Create/work Document

1 In work Yes

Ready for Review

1 completed Yes

Review document

1 reviewed Limited

Approval Document

1 Signed off No

Create/work Document

2 In work Yes

Ready for Review

2 completed Yes

… 2 … …

Document type: protected PDF-Data

Activity Version Status Change ?Status-Change

Create PDF Document

1 Signed off No

… 2 … …

Creation of PDF-Version after approved issue Own document type for PDF –Versions Yxxx

Create Follow up Version 2 for working after approval ( CR)

Zxxx Yxxx

After Version 1 is moved to Status ‘Signed off’, no further changes are allowed in SAP Solution Manager. For this a PDF-File will be generated. For the ongoing update of documentation (change request) during next Phases a new copy of version 1 will be created


Further information

Blueprint Approach ->Solution Manager and Business Process Mgmt ->SolMan Operational Business Blueprint Guideline

Thank You!

Contact information:

F name MI. L nameTitleAddressPhone number