how to guide solman bulding

SAP Solution Manager

Document Core Business Processes How-To Guide

Applicable Releases:

Solution Manager 7.0 EhP1

Target groups:

Technology Consultants

Application Consultants

Version 1.0

March 2009

Document History Document Version Description

1.0 First draft

Typographic Conventions Icons Type Style Description IconDescription

Example Text Words or characters quoted from the screen.

Caution

These include field names, Screen titles, pushbuttons

labels, menu names, menu paths, and menu options.

Note or Important

Example

Recommendation or Tip

Example text Emphasized words or phrases in body text, graphic titles, and table titles

Example text File and directory names and their paths, messages, names of variables and parameters, source text, and names of installation, upgrade and database tools.

Example text User entry texts. These are words or characters that you enter in the system exactly as they appear in the documentation.

brackets indicate that you

replace these words and characters with appropriate entries to make entries in the system.

EXAMPLE TEXT Keys on the keyboard, for example,F2 orENTER.

Table of Contents

1. Introduction.......................................................................................................................... 1

2. Background Information..................................................................................................... 2

3. Pre-requisite......................................................................................................................... 4

4. Step-by-Step Procedure...................................................................................................... 5

4.1 Create an Implementation Project ................................................................................ 5

4.2 Document core business processes ............................................................................ 8

4.3 Import Business Processes into the Solution ............................................................. 16

5. Additional Information ...................................................................................................... 19

How to Document Core Business Process

March 2009 Page 1

1. Introduction

Management of an SAP solution requires comprehensive and up-to-date knowledge of the solution.

SAP calls this knowledge a Single Source of Truth. It is a structured, comprehensive, and reliable

collection of information about the state of all your current projects and productive SAP applications,

which is the foundation of well-grounded and fact-based decisions and actions along the entire

lifecycle.

SAP Enterprise Support is a holistic offering which supports your business processes

comprehensively, thus protecting your IT investment and sustaining your IT solution throughout the

entire lifecycle. The concept of Single Source of Truth is implemented through the SAP Solution Manager, enterprise edition which is available to customers with an SAP Enterprise Support contract.

Key prerequisite for a single source of truth is the clear definition of processes, responsibilities, SLAs,

and KPIs to measure the fulfillment of the service levels. SAP has defined standards and best

practices that can help customers set up and run end-to-end solution operations, for their SAP-centric

solutions. These cover not only applications from SAP but also applications from independent

software vendors (ISVs), OEMs, and custom-code applications integrated into the customers solution

landscape.

Out of the 16 standards defined by SAP for solution operations, Solution Documentation Standard defines the required documentation and reporting regarding the customer solution. For functionality

developed by customers or third-party software providers, the availability of required documentation is

not ensured. Therefore, additional requirements regarding solution documentation exist for such

custom developments. The standard Solution Documentation for Custom Development describes the content of the required documentation as well as tools and formats to be used to deliver it. At least

the specification of the development project, a list of all related code objects, and of the required

configuration settings has to be available. This helps both customer support organizations and SAP

Active Global Support to deliver support for custom developments effectively.

The procedure how to document is described in the following Document Core Business Processes How-to Guide. It starts with the background information on the different types of documentation and value of solution documentation. In the next section, it provides the details on the pre-requisites for

core business process documentation. The final section presents minimum requirements of the core

business processes documentation and covers the three main procedures of the documentation

process. Overall, this guide focuses on the minimum documentation required for the customer in order

to adhere to the Solution Documentation Standard and hence get access to specific SAP Enterprise

Support and SAP Solution Manager Capabilities.


March 2009 Page 2

2. Background Information

In order to fully exploit the value of Solution Manager Enterprise Edition and achieve the required transparency of IT Solution, you need solution documentation that includes an accurate and complete description of solution landscape itself with all business process and custom modifications. The solution documentation could be divided into three types of documentation.

The Figure 1 below shows the three fundamental kinds of documentation and the functions they enable.

Figure 1 Different types of Solution Documentation

The technical landscape documentation (Item 2 in Figure 1) is already covered by the basic configuration of SAP Solution Manager in its minimum required level. The documentation comprises of:

availability of system data of all productive systems in the System Landscape Directory (SLD)

availability of one or more solution landscapes which contain the productive systems as logical components

Business Process documentation (Item 3 in Figure 1) comprises of availability of all your core business process in the Business Blueprint and imported into the Solution Directory. If you document your core business processes in a Business Blueprint you can use this information not only when support is needed but throughout the entire software life-cycle. This increases the value of internal communication as there is always a relation to (core) business processes, i.e. the relevance of a requirement or problem is always visible.


March 2009 Page 3

You can re-use the documentation of business processes e.g. with the following SAP Solution Manager processes:

Test Management

Business Process Monitoring and Interface Monitoring

Job Scheduling Management

Upgrade and maintenance projects

Issue and Top Issue Management

The minimum requirements for the documentation of core business processes are a complete list of all process steps, the assignment of individual process steps to the systems they are executed on, a list of the transactions (or other entry points as URLs or background jobs) which are called via actions, and used interfaces.

Modification documentation (Item 4 in Figure 1) comprises of a short description of the development and its related development objects, e.g. programs in the customer name space. This documentation is especially important for the following reasons. First of all, modifications are not subject to SAP quality checks. Secondly, they can be lost in an upgrade when implemented improperly. Thirdly, the actual usage is often not checked after some time but modifications cause unnecessary maintenance cost and performance losses as so called dead coding.


March 2009 Page 4

3. Pre-requisite

To meet the pre-requisite for the documentation of core business processes within the Enterprise Edition of SAP Solution Manager, you have to run the guided procedure of transaction SOLMAN_SETUP (Item 1 in Figure 1 Install and Connect to SAP)

As a result of the guided procedure of transaction SOLMAN_SETUP, you will have already realized the technical documentation and all relevant system connections (RFCs) and logical components in place.

With respect to the timeline, basic configuration of SAP Solution Manager requires approximately three days. Once this basic configuration is completed, documentation of core business process does not require any additional configuration. The Figure 2 below highlights the time required to configure SAP Solution Manager. The zero days signifies core business process documentation steps can be started directly immediately after the basic configuration is done and does not require any additional configuration steps.

Figure 2 Configuration effort and exploitation strategy for efficient life cycle management.


March 2009 Page 5

4. Step-by-Step Procedure

The following procedure presents the minimum set of steps required for the documentation of core business processes. The procedure consists of three parts:

1. Create an implementation project

2. Document a core business process (including documentation of custom code and interfaces)

3. Create a solution and import business processes into the solution

Note

The procedure described below is applicable when no documentation for business process of your solution is available. Also, the project type selected is an Implementation Project. There are several types of projects such as Template Project, Upgrade Project, Optimization project etc. You could re-use the documentation created using the below steps for other types of project as well.

4.1 Create an Implementation Project 1. In the SAP Solution Manager Implementation / Upgrade Work Center

(SOLMAN_WORKCENTER transaction), Go to Plan sub-view and select Create or Maintain Project link (SOLAR_PROJECT_ADMIN transaction).

2. In the Project Administration Application, Choose (Create Project)


March 2009 Page 6

3. In the dialog box, enter a project name, for example ICSALES.

4. In the Type field, select Implementation Project.

5. Leave the Solution field empty. Since the Solution Creation is done at a later stage in the

Solution Documentation. Choose (Continue).

6. Enter a title, for example IC Sales Order - Implementation Project. 7. On the General Data tab, select the preferred project language, for example English.

8. To assign logical components to the Project, go to the System Landscape Tab,

9. Choose the input help (F4) in the Logical Component column.

10. In the selection screen, select the appropriate logical component. For example, select check

Box Z_E2ECC_CRM with SAP CRM 5.0 product version. Choose (Continue).

11. Depending on your project requirements, choose other relevant logical components similarly using the input help.

12. To activate Development Tab in the Business Blueprint (SOLAR01 transaction) application, go to Project Standards Tab and select the Tabs view.


March 2009 Page 7

Note

This step will enable you to documentation of custom code and programs for business processes. As the custom developments are mainly documented the configuration phase of a project, the default value is invisible in the Business Blueprint (SOLAR01 transaction) and visible in the Configuration (SOLAR02 transaction), only.

13. In the Tabs View, change the Blueprint Visibility column for Development row from Invisible to Visible.

14. Save your settings

15. A dialog box appears. To confirm the Knowledge Warehouse (KW) context for documents,

choose (Continue).


You have successfully created the implementation project to document core business processes.


March 2009 Page 8

4.2 Document core business processes 1. In the SAP SOLUTION MANAGER Implementation / Upgrade Work Center, go to Plan

sub-view and select Define Business Blueprint link (SOLAR01 transaction).

2. In the Business Blueprint Application, select the Business Scenario node in the Business Blueprint Structure and go to Structure Tab.

3. To select the relevant business scenario from the Business Process Repository, choose the input help (F4) in the Scenario Name column

4. For example, select IC Sales with ERP Sales Order ( SAP ECC 6.0, SAP CRM

5.0 product versions )

Choose (Continue).


March 2009 Page 9

The IC Sales with ERP Sales Order business scenario has two business processes

a. Inbound Telesales with ERP Sales Order

b. Outbound Telesales with ERP Sales Order

The business process includes various business processes steps which in turn includes transactions. Please refer to the following figure for the Business Process Hierarchy.


March 2009 Page 10

In the next few steps, we present the method to view SAP delivered documents, upload

documents and view graphics at a business process level.

5. Select the Outbound Telesales with ERP Sales Order node within the business process structure.

6. To access the business process documentation delivered by SAP, go to General Documentation Tab and mark the Outbound Telesales with ERP Sales Order row, and

choose (Display)

7. To add business process related project specific documentation, go to Project Documentation Tab and choose (Add).

8. In the Add Document dialog box, enter the document details including Title. For example,

Outbound TeleSales Business process definition

9. In the Documentation Type field, select Additional Documentation

10. In the Status field, select Released

11. To upload a file, choose Upload File radio button and choose (Continue).

12. In the Upload Document window, select the document you wish to upload and choose Open. Now, the document could be viewed within Project Documentation Tab.

13. To select the graphical view of Outbound Telesales with ERP Sales Order business process,

go to the Graphic Tab and view the various business process steps within CRM and ERP logical components.

In the next few steps, we present the method to include a custom transaction and custom program for a business process step and upload custom documentation. 14. Select a Business Process Step, For example - Manage call lists and go to the

Transaction tab.

15. To add custom code related documentation, go to Project Documentation Tab and choose (Add)

Business Scenario

IC Sales with ERP Sales Order

Business Process

Process Step

Outbound Telesales with ERP Sales Order

Transaction / User Entry

Manage call lists

CRMD TM CLDI

Call List


March 2009 Page 11

16. In the Add Document dialog box, enter the document details including Title. For example, ZCRU-Custom code description



19. To upload a file , choose Upload File radio button and choose (Continue)


21. To add a custom transaction, use the drop down options for the Type column and select the

type Transaction. The logical component is automatically selected for transaction type

.

22. Choose the input help (F4) for Object column.

23. In the Find Transactions dialog box and type Z* and choose (Continue) to search for relevant custom transaction in the selected logical component systems.

Note In this step, SAP Solution Manager connects to the managed system using the RFC connection to fetch the custom objects. Hence, RFC destination and logical component mapping to appropriate system role is a pre-requisite for the step (Refer to section 3 Pre-requisite).

24. In the search results, select the relevant custom transaction. For example, ZCRU Create additional users.


March 2009 Page 12

25. Similarly, you can document other relevant transactions, background jobs, long URLs and Web addresses

26. To add a custom program, go to the Development tab.

27. In this Tab, use the drop down options for the Type Column and select the type Program. The

logical component is automatically selected for program type.

28. Choose the input help (F4) for Object column

29. In the Find Programs dialog box and type Z* and choose (Continue) to search for custom program in the selected logical component systems.

30. In the search results, select a custom program. For example, Z_RESET_FLAGS_IN_SMODILOG


March 2009 Page 13

31. Similarly, you can document other relevant programs, function modules etc. In the next few steps, we present the method to document Interfaces using the Business Blueprint Application. 32. To create an Interface Scenario, go to the Interface Scenarios node in the Business Blueprint

Structure. Select the Structure Tab.

33. In the Interface Scenario column, enter the name of the Interface scenario. For example, IC Sales Interfaces.


35. Expand the Interface Scenarios node and select the IC Sales Interfaces node.

36. In the Structure Tab Interface column, enter the name of the interface. For example CRM->ERP

37. In the same row, select the relevant values for Sending Logical Component (Z_E2ECC_CRM), Receiving Logical Component (Z_E2ECC_ERP), Technology (RFC asynchronous) and Type (Asynchronous) columns.

38. To add Interface attribute, choose the (Attribute).

39. In the Attribute Maintenance dialog box and SAP Attributes Tab, select the Quality of Service (exactly once) and Responsible Person (Henrik)


March 2009 Page 14

40. In the Technical Attributes Tab, use the input help (F4) to select the Technology Object (CREDITOR_GET_KTOKK), Business object (CREDITOR_MASTER_DATA), Caller program (GET_DATA_FOR_CONTACTS), Transfer mode (Delta) and Trigger mode (Dialog).

41. To add Interface related custom documentation, go to Project Documentation Tab and choose (Add)

42. In the Add Document dialog box, enter the document details including Title. For example,

CRM-ERP Interface Documentation



45. To upload a file , choose Upload File radio button and choose (Continue)



Note For more information on interface documentation, please access the below link.

48. Expand the IC Sales Interfaces node and select the CRM->ERP node.

49. In the Structure Tab Interface Step column, enter the name of the interface step. For example

Prepare data

50. In the Logical Component column, select the appropriate logical component. For example Z_E2ECC_CRM

51. Similarly, enter the other interface steps( For example: Send Data , Process Data ) and select the appropriate logical components


March 2009 Page 15

52. To assign the created Interface to appropriate business process, select the business process node in the Business Blueprint Structure. For example, select Outbound Telesales with ERP Order business process

53. Go to the Graphic Tab and right click on the link that associates two business process steps across different logical components. For example, select the association between System guides agent and Process Sales Order in Interaction Center business process step.

54. In the pop-up menu, select the Assign Interface option.

55. In the Interface Selection Help dialog box, select the relevant Interface. For example,

CRM->ERP

56. Choose (Continue)

57. Similarly, assign other relevant Interfaces to business process steps.


You have now documented your core business processes, custom code and interfaces.


March 2009 Page 16

4.3 Import Business Processes into the Solution In the next few steps, we present the method to create a solution and import the business process documentation into the solution

1. In the SAP Solution Manager SAP Solution Manager Administration Work Center, go to Solutions sub-view and select New button.

2. In the Create Solution window, enter the solution name. For example, ICSales01

3. In the Language field, select English

4. For the Lead System Role column, select the Production System radio button.

5. Save the solution

6. To assign logical components to the solution, go to the Solution Landscape Tab.

7. Choose Add Existing Logical Component button


March 2009 Page 17

8. In the Select Logical Component dialog box, select the relevant logical component using the input help. For example, Z_E2ECC_CRM

9. Select the button to add the logical component to the solution.

10. Similarly, select the other relevant logical components for the solution. For example : Z_E2ECC_ERP

11. Save the solution.

12. To view the created solution, go to Solutions sub-view and choose Refresh. The solution appears in the list of solutions of the SAP Solution Manager Administration Work Center


March 2009 Page 18

13. To access the Solution Directory, click on the solution link. For example click on ICSales01

link in the solution list.

14. In the Solution Directory, expand the Solution Structure and select the Business Scenarios node

15. To import Business Scenario from the project , choose (Change)

16. Go to the Structure Tab and use the input help (F4) for the column Scenario Name.

Make sure the Source is the Project.

17. In the selection help screen, select the relevant Project/Business Scenario. For example,

IC Sales with ERP Sales Order

18. Choose Copy to continue


March 2009 Page 19


20. Expand the Business Scenario node in the Solution Structure to view the business processes that are imported into the Solution Directory.

You have successfully imported your Business Scenario into Solution Directory.

5. Additional Information

1. SAP Solution Manager: http://service.sap.com/solutionmanager >> SAP Solution Manager Enterprise Edition

2. SAP Solution Manager e-learning material: http://service.sap.com/rkt-solman >> SAP Solution Manager 7.0 - Enhancement Package 1 (EHP1)

3. Enterprise Support: http://service.sap.com/enterprisesupport

4. E2E Integration Testing: http://service.sap.com/supportstandards

5. Solution Documentation FAQs:

how to guide solman bulding

Documents