Business Process Redesign in SAP Solution Manager Application Lifecycle Management

Business Process Long-Term Redesign

Copyright
© 2011 by SAP AG. Neither this document nor any part of it may be copied or reproduced in any form or by any means, or translated into another language, without the prior consent of SAP Active Global Support. All rights reserved. SAP, R/3, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP Business ByDesign, and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and other countries. Business Objects and the Business Objects logo, BusinessObjects, Crystal Reports, Crystal Decisions, Web Intelligence, Xcelsius, and other Business Objects, products and services mentioned herein, as well as their respective logos, are trademarks or registered trademarks of Business Objects S.A. in the United States and in other countries. Business Objects is an SAP company. All other product and service names mentioned are the trademarks of their respective companies. Data contained in this document serve informational purposes only. National product specifications may vary. These materials are subject to change without notice. SAP AG and its affiliated companies („SAP Group“) provide these materials for informational purposes only, without representation or warranty of any kind, and SAP Group shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP Group products and services are those that are set forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warranty.

© 2011 SAP AG Dietmar Hopp 16 D-69190 Walldorf

Title: Long-Term Implementation Version: 2.0 Date: 23.08.2011

Page 2 of 59

Business Process Long-Term Redesign
Index
Copyright .............................................................................................................................................. 2 1 2 Introduction .................................................................................................................................... 5 General Explanation ..................................................................................................................... 5 2.1 2.2 2.3 2.4 2.5 2.6 2.7 2.8 2.9 2.10 Projects and Solutions ......................................................................................................... 5 Template Project ................................................................................................................... 6 Implementation Project ........................................................................................................ 6 Maintenance Project............................................................................................................. 7 Upgrade Project for Existing Systems ............................................................................... 7 Projects and Solutions Dependencies ............................................................................... 8 Business Process Design .................................................................................................... 8 Business Process Assignments ....................................................................................... 12 Document Management .................................................................................................... 13 Procedures for Solution Documentation ......................................................................... 16 Interface Scenarios..................................................................................................... 18

2.10.1 3

Building Long-Term Projects ..................................................................................................... 19 3.1 3.2 3.3 3.4 3.5 Document Management in a Long-Term Project ........................................................... 21 Methodology for Long-term Project (Roadmap) ............................................................ 21 Testing in the Long-Term Project ..................................................................................... 22 Training Materials ............................................................................................................... 22 Go-Live and Maintenance ................................................................................................. 23

4

Change Request Integration ..................................................................................................... 23 4.1 ChaRM in a Maintenance Project .................................................................................... 23 Method .......................................................................................................................... 23 Change Types ............................................................................................................. 24 Phase Change (Task List) ......................................................................................... 24 Business Process Integration for Document Management .................................. 25

4.1.1 4.1.2 4.1.3 4.1.4 4.2

ChaRM in Long-Term Project ........................................................................................... 25 Method, Change Types and Phase changes (Task list) ....................................... 25

4.2.1 5 6

Organizational Aspects for Long-Term Projects in SAP Solution Manager ...................... 25 Authorizations .............................................................................................................................. 27 6.1 Projects................................................................................................................................. 27 Title: Long-Term Implementation Version: 2.0 Date: 23.08.2011 Page 3 of 59

© 2011 SAP AG Dietmar Hopp 16 D-69190 Walldorf

Business Process Long-Term Redesign
6.2 7 Document Management .................................................................................................... 27 Setup/Configuration and Procedures ...................................................................................... 29 7.1 General Configuration ........................................................................................................ 29 Definition of System Landscape – SMSY ............................................................... 29 Project Standards ....................................................................................................... 33 Definition of Document Types ................................................................................... 34 Definition of Status Schema ...................................................................................... 36 Adjustments to Blueprint Document ........................................................................ 40 Structure/Object Attributes ........................................................................................ 42 Customer Attributes for Documents ......................................................................... 45

7.1.1 7.1.2 7.1.3 7.1.4 7.1.5 7.1.6 7.1.7 7.2

Long-Term Project Creation .............................................................................................. 48 Compare & Adjust: From Maintenance to Long-Term project ............................ 53 Testing in the Long-Term Project ............................................................................. 54 Learning Map............................................................................................................... 56 Go-Live and Delta Adjustment to the Solution ....................................................... 57 Post Go-Live Maintenance ........................................................................................ 58

7.2.1 7.2.2 7.2.3 7.2.4 7.2.5

© 2011 SAP AG Dietmar Hopp 16 D-69190 Walldorf

Title: Long-Term Implementation Version: 2.0 Date: 23.08.2011

Page 4 of 59

Business Process Long-Term Redesign
1 Introduction
The SAP Solution Manager is positioned as an Application Management Platform for SAP centric solutions. The major focus of SAP Solution Manager is on solution operation and optimization. It also functions as a collaborative infrastructure between the customer and SAP. This includes remote support as well as collaborative scenarios between the customer operation and the SAP service organizations. Apart from solution operation, the SAP Solution Manager platform also provides an infrastructure for overall application management: from requirement/change request management, through design, build, test, deploy, and operation/optimization, with a major focus on change control. Depending on the scope of the SAP Solution Manager processes being implemented and depending on the structure of the company, the SAP Solution Manager can be an easy setup or an implementation project by itself. The following content describes one of the Application Lifecycle Management (ALM) possibilities in SAP Solution Manager for an example of a long-term project (which performs changes to productively used business processes which are stored in a solution). This includes references to test capabilities, Business Process Monitoring, and Change Request Management (ChaRM).

2 General Explanation
2.1 Projects and Solutions
As shown in the picture below, projects and solutions are simply overviews of business process information. A project in SAP Solution Manager provides information on the future use of business processes: this includes business process redesign and new business process implementation.

Figure 2-1 Project and Solution

© 2011 SAP AG Dietmar Hopp 16 D-69190 Walldorf

Title: Long-Term Implementation Version: 2.0 Date: 23.08.2011

Page 5 of 59

In the following chapters (2. In case several SAP Solution Manager systems are being used in parallel. when used in several projects.5) the different project types are described. descriptions. The more content prepared in the template. test cases. It is also possible to translate the content of the documents within the Knowledge Warehouse (KW) functionality in which they are stored. changes all other assignments like: documents.3 Implementation Project Implementation projects can be used to implement business processes in an SAP landscape.Business Process Long-Term Redesign A solution. configuration and development assignments as well as predefinitions of test cases and training material. Definition and documentation of global business processes and their preparation for rollouts. documents. or base it on any one of the following: o one or several templates o existing project(s) o scenarios and configuration structures delivered by SAP (Business Process Repository) o an existing production solution landscape for long-term changes to productively-used business scenarios © 2011 SAP AG Dietmar Hopp 16 D-69190 Walldorf Title: Long-Term Implementation Version: 2. Its assigned objects (documentation. contains information on the current use of business processes in a productive environment. The preparation of the global processes can comprise business process flow. Typical Use Case in ALM: A template project can be used for: 1. processes and business process steps). A project structure has to be created for the business processes.2-2. Test cases will be done in SAP Solution Manager.08. 2. development and training material) are available to other projects as templates. Additionally.2 Template Project A template project can be used to create and distribute a template. IMG objects. templates can be transported from one central system (where the structures and assignments are defined) to another system.2011 Page 6 of 59 . This use case can be combined with the rollout use case. A template defines a project structure. transaction assignments. As business process library connected to a modelling tool to manage changes and redesigns of business processes. the template project offers the possibility to translate the project structure (consisting of business scenarios. IMG activities.0 Date: 23. Template projects are especially suited to SAP Partner Solutions or Global Rollouts. 2. 2. You can either create a new project structure. Except for the business process flow. Templates can be locked against changes. or parts of it. the easier the rollout from a documentation perspective. on the other hand. completely or partially.

4 Maintenance Project The maintenance project can be used to keep track of changes in the productive environment (solution). Typical Use Case in ALM: Assignment to a solution with activated Check Out/In functionality can be used to reflect all changes made to productively used business processes and their documentation.Business Process Long-Term Redesign Typical Use Case in ALM: An implementation project can be used for two typical use cases: 1. Types of possible changes: o Urgent correction: errors and hot fixes. this usually does not have an impact on the business process documentation (back to designed behavior). during the maintenance cycles. These changes are reflected in business process documentation. 2. Normal implementation without template predefinitions (manual business process creation and documentation). Long term changes to productively used business processes stored in a solution.2011 Page 7 of 59 . These are typically small transactional corrections or configuration tasks. 2.5 Upgrade Project for Existing Systems In an upgrade project you can: o upgrade the customization: upgrade existing functions and/or o delta the customization: copy additional functions © 2011 SAP AG Dietmar Hopp 16 D-69190 Walldorf Title: Long-Term Implementation Version: 2. This typically involves minor reconfiguration or additional small developments (no business process redesign). Predefined business processes from a template project. Those business processes can be redesigned in this project (without system upgrade) and afterwards all deltas are handed over to the solution. These changes are then performed in a maintenance project linked directly to the solution. o Normal corrections: pertains to all changes to a business process or a business process step which can be completed within a short of the maintenance cycle. redocumentation/changes from the Solution Directory. Implementation of new business processes.08. o in Check Out/In for business processes. 2. b. based on: a. where the scope can be defined. the business processes can be created and changed independently during the implementation. o in Change Request Management. Predefined business processes can be changed according to global attributes defined in the template. The project contains all maintenance activities and urgent corrections of a solution.0 Date: 23. Here.

This affects future use of the content for purposes like testing or Business Process Monitoring. or module-oriented business processes can be combined into end-to-end business scenarios. The information flow is depicted in Figure 2-2. Figure 2-2 Information Flow between different Projects and a Solution The same content (business process and attached information) is reused and passed on to typical project phases. By choosing the wrong design. As such.0 Date: 23.7 Business Process Design Proper business process design and appropriate grouping into scenarios are key decisions when starting ALM in SAP Solution Manager. Please refer to the chapter Business Process Design. Here.2011 Page 8 of 59 . realization. such as: design. 2. 2. reusability is impaired. The upgrade project is typically based on a solution with the latest up-to-date process documentation. test. below. and go-live and also between the different project types and the solution. the requirements on the business process design can be very complex. Business processes should be organized in business scenarios. moduleoriented scenarios can be used.08. © 2011 SAP AG Dietmar Hopp 16 D-69190 Walldorf Title: Long-Term Implementation Version: 2.6 Projects and Solutions Dependencies Using application management in SAP Solution Manager creates information flow and data exchange between a project and its operational areas.Business Process Long-Term Redesign Typical Use Case in ALM: Redesign of business processes and their documentation caused by a technical upgrade of the system(s) on which they are running.

2. Process and Step o A business process step is most commonly related to a transaction. It is recommended to use structure attributes or custom attributes for documents when organizing the business process documentation in relation to SAP modules.7. However.08. you have to answer the question what “end-toend” means for your business unit(s).2011 Page 9 of 59 . templaterelated). SAP module or other kinds of grouping (e. Sometimes it makes sense to also document some activities within the business process flow.g. and is mostly connected to organizational aspects (user access.). grouped according to a certain criterion like business content or SAP modules. o A business process is a collection of business process steps.Business Process Long-Term Redesign Below. test capabilities.or End-to-End oriented).1.7.2 End-to-End Oriented Business Process Design In designing end-to-end business processes. The SAP Note 1345599 describes the restrictions to size for business scenarios. a web UI or similar system activities. interface documentation and Business Process Monitoring. 2. Visibility and reporting capabilities can be improved through structure attributes. organization of monitoring etc.0 Date: 23. for designing business processes in SAP Solution Manager. two methods are described (SAP module. o A business scenario is a collection of business processes to be executed one by one resulting in the execution of an operational procedure. This difficulty shows up at the start of business process documentation. Scenarios can be organized by business unit. a background job.1. Figure 3-1 End-to-End Oriented Business Process Design © 2011 SAP AG Dietmar Hopp 16 D-69190 Walldorf Title: Long-Term Implementation Version: 2. this is the most reusable business process model for documentation purposes.1 Definitions of Business Scenario.

a better option is to document the connections to other business processes. Figure 3-2 Module-Oriented Business Process Design Advantages: o Clear separation of processes by SAP Module (mostly combined with module-based business scenarios) Disadvantages: o o Additional work to build test-related business processes Without “interfaces” to other business processes. it is recommended to represent preceding or succeeding steps also (documentation of Interface Scenarios) as shown in the following graphic. as shown in the following Figure 3-3.0 Date: 23.2011 Page 10 of 59 . highlighting interfaces.1. no possibility to document system interfaces Therefore. to increase the quality and the number of further possibilities in SAP Solution Manager. © 2011 SAP AG Dietmar Hopp 16 D-69190 Walldorf Title: Long-Term Implementation Version: 2. However.3 Module-Oriented Business Process Design In a module-oriented business process you typically describe business process steps that belong together and that are executed one after the other in a single module.08.7.Business Process Long-Term Redesign 2.

structure attributes can be adjusted with the Compare & Adjust function using the transaction SA_PROJECT_UPGRADE.0. How business scenarios are organized also determines how to roll them out using templates (Template as Information Provider). testing. 2.1. you can compose end-to-end business scenarios from a mixture of module-oriented business processes. These are executed one after the other in order to perform a business activity. use the Graphic tab at scenario level to document the order in which the business processes are to be executed. The biggest advantage of structure and object attributes is that they can be copied together with the structure. Figure 3-4 Business Scenario Execution To do so. Structure attributes can support all types of filtering or reporting capabilities during typical project phases like blueprint.4 Business Scenario Definition To combine both models.7.Business Process Long-Term Redesign Figure 3-3 Extended Module-Oriented Business Process Design 2. Once assigned.7.1. or after go-live in maintenance. it is possible to define and use structure and object attributes.08.2011 Page 11 of 59 .0 Date: 23. configuration.5 Structure Attributes As of support package 15 (EHP 1) for SAP Solution Manager 7. This ensures that all changes made to © 2011 SAP AG Dietmar Hopp 16 D-69190 Walldorf Title: Long-Term Implementation Version: 2. whenever the structure is reused (template  Rollout  Solution  Maintenance).

Test Case Descriptions: The testing prescriptions for a business process step are assigned to appropriate structures (using the test object results in a transaction assigned to the business process step).Business Process Long-Term Redesign attributes and their assignment to the business processes or business process steps are current at all times throughout the entire business process lifecycle.2011 o o o © 2011 SAP AG Dietmar Hopp 16 D-69190 Walldorf Page 12 of 59 . Business Process Monitoring. in the managed system. 2. assigned to the configuration tab of a business process or a business process step. the test case descriptions can be selected and brought into the test scope as a test case (together with assigned transactions). These have to be maintained to ensure that the business process/step runs. Configuration Objects: all objects. like: o Transactions: the assignment of transaction information to the business process steps determines which transaction(s) will be used to perform a certain business process step.8 Business Process Assignments Apart from documenting the business process structure in the template project.08. document the customizing views. and is reused for testing. Title: Long-Term Implementation Version: 2. Development Objects: all modifications are documented as an assignment of the developed object to the business process/step for which the modification was created. This information is usually defined during the blueprint stage. as designed during the blueprint stage. Additionally. business process change analysis and other functions. During the creation of a test plan. you can also document technical objects.0 Date: 23. Figure 3-5 Business Scenario Execution Show how this procedure is executed in SAP Solution Manager. technical documentation for the modifications and extensions can be assigned and connected to the development object directly.

2 Document Management” (Authorization). the documentation of business scenarios. all relevant forms and templates can be uploaded into SAP Solution Manager to make them available for later documentation during the blueprint or configuration project phase. These documents can be used to create Learning Maps and distribute them to end user groups. The assignment of documents to structures and to a specific tab is customer specific. Status Schema Some document types require specific status values assigned to the document for specific situations. To this end.0 Dietmar Hopp 16 Date: 23. To do so. Document Types SAP Solution Manager uses predefined document types to document business processes and steps. However. Show how this procedure is executed in SAP Solution Manager. Recommendation: Define and use customer-specific document types created in a customer name space (Z* or Y*). processes or steps can start. This assignment can be used as a filtering criterion for Learning Map creation. which describe how a transaction is to be used by end users in the context of the business process.2011 D-69190 Walldorf . a few rules should be followed concerning document assignment: Title: Long-Term Implementation © 2011 SAP AG Page 13 of 59 Version: 2. This simplifies the handover procedure to the solution after go-live of a rollout project. you can create new documents on several tabs in transactions SOLAR01/02 based on the document types. End User Groups: To document which business process step is used by which group predefined end user groups can be assigned. This folder (folder group) is used to check the authorization for all documents stored inside. Reusable document types can be predefined centrally by uploading document templates into SAP Solution Manager.08. Show how this procedure is executed in SAP Solution Manager. You can assign exactly one status schema to exactly one document type. Please refer to the chapter “6. can be assigned to the business process step on the Training tab. Recommendation: All status schemas should end with a common released status.9 Document Management Document management in SAP Solution Manager uses the Knowledge Management (KM) functionality with additional functions specific to SAP Solution Manager. This is enabled through the status schema. Possible assignments Using the structure of the document types. o 2. All documents are physically organized in so-called KW Folders.Business Process Long-Term Redesign o Training Materials: The training documents.

All document types use the same or different status schema(s). Reuse of documents by links. Additional documents describing the differences can be assigned to the occurrence selectively. Training Materials: All kinds of training documents which will be made available to end users (simulations.2011 Page 14 of 59 . you can link documents to the same business process steps used in different business processes (basic documentation). Description Business Process Description Functional Specification Configuration Description Authorization Technical Specification Test Case Description User Training Interface Description Structure Business Process Business Process/Step Business Process/Step Business Process/Step Business Process/Step Step Step Interface Step Tab Gen/Project. Authorization Roles…) Development Tab: All developments needed to run the transaction ME31L (Technical specifications.Business Process Long-Term Redesign o The lower the level of the information the better. In order to decrease the number of documents. functional specification or additional documentation…) Project Documentation Tab: project related documentation for ME31L Configuration Tab: document describing the configuration needed for transaction ME31L (Configuration objects and descriptions.0 Date: 23. development forms…) Test Case Tab: Test case descriptions. Additionally.08./Project Documentation Configuration Configuration Development Test Cases Training Material Gen. presentations) o Use of a common final status value for all document types (documents). Every status schema ends with the same common final status value. test data documents can be assigned at business process level. All types of functional tests can be represented by different document types./Project Documentation o Document Type ZBPD ZFSP ZCON ZAUT ZTSP ZTCD ZUT ZINT © 2011 SAP AG Dietmar Hopp 16 D-69190 Walldorf Title: Long-Term Implementation Version: 2. Documentation Gen. Business Process Step Example: Create purchasing scheduling agreement (transaction ME31L) General Documentation Tab: contains documents describing the design of transaction ME31L ( in case template management was used. This means that the more granular a document the better suited it is to be reused.

08.Business Process Long-Term Redesign Above document types are examples. © 2011 SAP AG Dietmar Hopp 16 D-69190 Walldorf Title: Long-Term Implementation Version: 2. Different document types can be created to suit different requirements. Show how this procedure is executed in SAP Solution Manager.2011 Page 15 of 59 .0 Date: 23.

8. the business processes have to be copied into an SDA analysis project (3). the data have to be converted to an XML format. the data can be uploaded easily using report RS_SA_PROJECT_IMPORT (2) into an existing implementation or template project. you can upload business process descriptions. logical components (in which the transaction is executed). This conversion from excel into xml format is a consulting solution. and test cases to the appropriate tabs (please refer to the previous chapter “2. To do so.10 Procedures for Solution Documentation The information about current productively used business processes can be collected centrally by business process owners or from existing documents into an excel file (1). After these steps have been performed. In the same file. an assignment of transaction codes to business process steps. the business process structure is created. In this file.2011 Page 16 of 59 .08. © 2011 SAP AG Dietmar Hopp 16 D-69190 Walldorf Title: Long-Term Implementation Version: 2.0 Date: 23. Figure 4-1 Business Process migration After the migration content has been uploaded into SAP Solution Manager and extended by additional assignments.Business Process Long-Term Redesign 2. and links to all relevant documents which have to be migrated to SAP Solution Manager are created. configuration views. the data can be entered directly into SAP Solution Manager using SOLAR01/02 where additional data like development objects. you can start verifying it using the Solution Documentation Assistant (SDA).1 Document Management”). In the 7. Typically. this possibility is provided in the standard version.1 release of SAP Solution Manager. After all data relevant to migration have been collected into an excel file. or structure / document attributes can be assigned to the structure. Afterwards. specifications.

all documents will turn into “Copy of…” and will get initial document status. where documentation and further assignments can be adjusted. However. © 2011 SAP AG Dietmar Hopp 16 D-69190 Walldorf Title: Long-Term Implementation Version: 2. you can use the BAdI interface IF_EX_SOLAR_DOCUMENTS. the business processes cannot be changed in a solution. the logical components can be replaced by those representing the maintenance landscape. If necessary. These redesigns of productively used business processes can be performed in so-called long-term projects. business process flow changes cannot be performed in a maintenance project.2011 Page 17 of 59 . Once the verification is completed and has yielded positive results (which means that all transactions used for business process documentation are executed in managed systems). the Change Request functionality can be activated for this maintenance project. Show how this procedure is executed in SAP Solution Manager. o Content Maintenance: To perform planned changes to the productive content. Since the business processes were created based on the experience of business process owners and/or on existing documents. Content copy from Project into Solution: It is recommended to use the work center to copy the business processes from the rollout project into the solution. Before each maintenance cycle. the planned normal corrections can also be reflected in the checked out structures. Optionally.Business Process Long-Term Redesign This copy will take business process structures with all assigned transaction/report information from the Transaction tab. A few tasks need to be performed during the content copy of the documentation project into a solution: o o Creation of a Solution: The business processes and their entire documentation will be stored in the solution after go-live. the content can be copied into a solution (4). If no further checking rules are assigned to the business processes in the analysis. it is recommended to create and assign a maintenance project to the solution. Once the content is copied. By activating Check In/Out. the system will analyze the business processes based on the statistics for actively used transactions in the managed systems. All other objects will be copied from the project into the solution directly (together with structure and document attributes).08. no red alerts should appear (a red alert means that the transaction has not been executed).0 Date: 23. To fix this. Show how this procedure is executed in SAP Solution Manager. but exclusively in the maintenance project assigned to it (5+6).

you can specify the sending and receiving system. However. and the content is used to build a solution. Interfaces can be specified in a specific interface scenario structure. evaluating which interface is used for which process becomes very easy. For each interface. the interfaces can be documented and described. the type and technology.10. Once the interfaces are documented.Business Process Long-Term Redesign In case the maintenance project is also used for change request management purposes. After this. This assignment of one interface can be done several times for several business processes. In this case. Once the interface is assigned to a business process in a documentation project. the original information is still in the documentation project. © 2011 SAP AG Dietmar Hopp 16 D-69190 Walldorf Title: Long-Term Implementation Version: 2. On the documentation tabs.08.2011 Page 18 of 59 . it is recommended to resolve the external interface thereby copying the original interface into the solution. you can assign them to the appropriate business processes on the Graphics tab. the interface information is still represented on the Graphics tab. 2.0 Date: 23.1 Interface Scenarios SAP Solution Manager provides the possibility to document interfaces between systems. all logical components collected in the solution have to follow the same maintenance cycle.

0 this has to be done manually. in the release 7. the content can be checked in into the solution (4) and all changes made during the maintenance cycle will become visible in the solution as well. After the maintenance cycle is finished. Title: Long-Term Implementation © 2011 SAP AG Page 19 of 59 Version: 2. and the maintenance is in progress.1 you can make use of an extended Compare & Adjust functionality which detects these changes automatically. In the SAP Solution Manager release 7. This demands a specific procedure for the creation of a long-term project.0 Dietmar Hopp 16 Date: 23. To ensure that during the redesign. In case new documents were created. While the maintenance cycles are being performed. the Compare & Adjust should be performed on the long-term project separately (3+3). or new assignments were made to the business process with a maintenance project. you can start using the long-term method to redesign business processes.Business Process Long-Term Redesign 3 Building Long-Term Projects Once the business processes are documented in a solution. the business processes which are to be redesigned can be copied into the projects (1). the long-term project changes the business processes by assigning new content (5) or by completely redesigning the business processes using the old content as a starting point. Figure 5-1 Creation of Long-term Project and Change Reflection It could happen that during long-term project redesign of the business process the same business process content is changed in the maintenance project (2 + 2). the long-term project should be created in a different KW enhancement. The changes to the documents available during the process copy are immediately reflected in the long-term project documentation (because all documents are linked). Choose the option “Refer Documents” to ensure that changes to existing maintenance documents are reflected in the long-term project. Once this has been done.2011 D-69190 Walldorf . all changes to the business process documentation are also reflected in the long-term project.08.

the appropriate business processes can be checked out into the maintenance project (6). This is also the case for process structures and their assignments (7). © 2011 SAP AG Dietmar Hopp 16 D-69190 Walldorf Title: Long-Term Implementation Version: 2. All changes to documents can be merged into existing documents (this is the only way to ensure that the new information will be visible automatically in other projects which may run in parallel).2011 Page 20 of 59 . Afterwards. Newly created documents can be signed additionally with document attributes which show in which project the document was created. reconfiguration in the development system and testing of the content have to be prepared for deploy. the consolidation of the changes can be performed (7). Show how this procedure is executed in SAP Solution Manager. After redesigning business processes.0 Date: 23. Using this procedure ensures that current productive documentation is not changed unintentionally. The extended Compare & Adjust functionality can be run (Release 7.1) against the business process source: the solution.Business Process Long-Term Redesign Figure 5-2 Long-Term Go-Live When the old documents have to be adjusted (4). As soon as all deltas are adjusted. In the maintenance project. the system will create a copy (due to the different KW enhancement).08. the business processes can be retested (in case of dual system landscape). After the changes to the content have been detected. all business processes can be checked in at the end of the maintenance cycle together with the normal maintenance content.

where new information can be stored. In case other parallel projects are using the same business processes as those in consolidation. To highlight all new documents. tasks. Additionally. So. Show how this procedure is executed in SAP Solution Manager. This happens because the long-term project was created in a different KW Enhancement (the system does not allow bidirectional links between two projects which are in different KW Enhancements). For all business processes which have to be redesigned existing documentation can be reused. Within transaction RMMAIN. and accelerators can be provided (documentation on how to proceed with the phase. These documents will not be a part of ALM (will not be handed over to the solution). Roadmaps. In this case. customer-specific phases. in which the document was created/changed. it will cause the document to be copied automatically. the documents are merged with the original documents. whenever the process documentation is changed in maintenance. You can also define and create your own Roadmaps in SAP Solution Manager. you can use the Roadmap functionality. © 2011 SAP AG Dietmar Hopp 16 D-69190 Walldorf Title: Long-Term Implementation Version: 2. you can use the customer attributes for documents to assign the project ID. task or activity).08. you have access to standards like ASAP or Upgrade Roadmaps which SAP delivers. you can use the extended Compare & Adjust functionality to detect business process deltas and “new” documents. the changes will be reflected automatically in the long-term project as all documents are linked.2 Methodology for Long-term Project (Roadmap) To document the methodology of a long-term project.2011 Page 21 of 59 . as soon as an existing document is clicked in change mode. You will be informed about the creation of the copy by a popup. all the redesigned processes have to be reflected in the solution content. the BAdI interface IF_EX_SOLAR_DOCUMENTS can be used to prevent the title changing to “Copy of…” and to pre-fill the document attributes for documents. which are assigned at a later point in time to the long-term project.0 Date: 23. From now on.Business Process Long-Term Redesign 3. During the go-live. 3. However. and activities can be described and customized. The newly created copy will have the same content.1 Document Management in a Long-Term Project Using a different KW Enhancement for the long-term project than for the other projects/solutions has an important advantage: an initial link is established between the business process documentation (which was originally stored in the solution) and the documents available in the long-term project. using transactions RMDEF and RMAUTH. but will be a physically independent object. can be used to store all document types which help to manage a project (such as meeting minutes).

When redefining or redesigning a business process. and assign the entities to the tester. If the training information was assigned to the business processes in the solution. or you can rebuild business processes for specific test types. the structure attributes can easily be used to filter business processes which may be tested or regrouped separately. the assigned test case descriptions have to be adjusted or rewritten after the new developments are implemented. 3. In so-called test sequences. Show how this procedure is executed in SAP Solution Manager. Thus. tailor it into testable entities (test packages).08.0 Date: 23. All training materials collated in the Learning Map will be shown to the end user in display mode. The end user will get access to the documents provided in his Learning Map.Business Process Long-Term Redesign 3. You can build a test plan based on the corrected test case descriptions and the technical business process step information (transaction). you can rearrange the order in which test activities are to be performed.4 Training Materials After successfully testing the implemented business scenarios. Show how this procedure is executed in SAP Solution Manager. © 2011 SAP AG Dietmar Hopp 16 D-69190 Walldorf Title: Long-Term Implementation Version: 2. the information is available there and is kept in sync with maintenance tasks. when taking the business processes into the long-term project. without needing a user in the SAP Solution Manager. The Learning Map functionality gives you the possibility to create end user group specific Learning Maps and distribute or publish them in a specific knowledge-transfer area.3 Testing in the Long-Term Project As the test case descriptions were uploaded into SAP Solution Manager. they are already part of the solution. the training materials can be adjusted and published/distributed using Learning Maps in SAP Solution Manager. the end user needs to be trained. To this end. and if some business processes were redesigned during the long-term project.2011 Page 22 of 59 .

and status reporting. This transaction type is used for approval workflow tasks.2011 D-69190 Walldorf - .5 Go-Live and Maintenance o Adjustments after Maintenance Cycles: All changes to the business scenario/process and step content which were made during maintenance should also be reflected in the long-term project. 4. and then approved or rejected by a change manager. This means that when a change necessity is detected (possible integration into SAP Solution Manager service desk). Change Request Management in SAP Solution Manager consists of three main areas: Change Administration: Management of all change requests.1.0 Dietmar Hopp 16 Date: 23. the Compare & Adjust functionality can be used to roll all changes made in maintenance cycles into the long-term project.Business Process Long-Term Redesign 3. o Show how this procedure is executed in SAP Solution Manager. project documentation. To this end. change categorization.1. transport scheduling (seamless integration into TMS) and transport tracking. During the workflow. you can use the Change Request functionality.1 ChaRM in a Maintenance Project Activating the ChaRM flag for your maintenance project allows the system to control all changes planned for the maintenance system landscape in so-called maintenance cycles. Once the change has been approved. This functionality can be used for the maintenance work and the appropriate landscape as well as for long-term projects. 4. 4 Change Request Integration To manage all changes made to all relevant development systems. This type of document is used to perform all development activities aligned to the approved change request. Combinations of these three topics allow full control over the landscape and all changes made to it.1 Method After configuring and activating the standard ChaRM functionality in your system. you can use the workflow-based functionality. the change is categorized (see 4. like customizing or development specifications and test management Change Logistics: Customizing and Development realization.08. The following descriptions roughly explain the procedures of ChaRM use during maintenance and for long-term projects. the change can be requested using the Change Request. approval workflow. Project Management: project planning.2 Change Types). Typical tasks are: Creation of a transport request Logon to relevant system to develop/test/validate the requested functionality Testing Title: Long-Term Implementation © 2011 SAP AG Page 23 of 59 Version: 2. the system will create another transaction type (based on the categorization) called the change document.

delivered in the standard version. You can track all transport requests from the system where they are created to the systems/clients into which they are imported.1): This type is used during testing. for corrective development. The task list can be used for:  Creating transport requests and tasks  Scheduled and/or on demand import  Transporting copies  Security functionalities like Cross System Object Lock and Critical Objects Check  Retrofit for n+1 landscape  Reporting capabilities  Transporting non-ABAP objects though the integration with CTS+ The Change Tracking function of Change Request Management allows you to track everything that relates to changes within the context of a Solution Manager or an IMG project.Business Process Long-Term Redesign Organization of transport (depending on change type) 4. the satellite IMG project. Activating Change Request Management for the long-term project on the ChaRM tab in the transaction SOLAR_PROJECT_ADMIN creates a task list in the background. Normal correction workflow has a strong dependency on the maintenance cycle phase. © 2011 SAP AG Dietmar Hopp 16 D-69190 Walldorf Title: Long-Term Implementation Version: 2. can be used by default (as a copy of the SAP origin): Normal Correction: This process is used to make regular corrections in your maintenance landscape and to implement planned features into your development landscape. You can also navigate into the Solution Manager project. An example would be number range.1. or the CTS project. Urgent Correction: This process is used to make an urgent correction in your production system. Test Message (Defect Correction as of 7.3 Phase Change (Task List) Maintenance cycles can be managed and switched in a task list.0 Date: 23. This task list records. all transport requests that belong to a particular project can be tracked across all the systems in the project landscape.1. You can navigate into the transport logs and import queue as well as into the corresponding service transaction or task list.2011 Page 24 of 59 . Administration Changes: This type is used for all system changes which cannot be included in a typical transport request. collects. - - 4.2 Change Types Four main Change Types. and manages all changes made to the managed system(s) or clients. In contrast to normal correction.08. The task list is a collection of all typical activities during the maintenance cycle. urgent correction gives you the possibility to implement the correction into your production system independently of the maintenance cycle. This transaction is only permitted within a maintenance landscape. Within the project context.

1. This includes ChaRM-specific customizing (activation or standard ChaRM customizing) as well as system landscape information in SAP Solution Manager. This method allows you to combine the technical work with documentation tasks by linking the Change Request Management directly to the business process documentation.2 Change Types (not „urgent correction‟) and 4. Once you decide to perform a long-term project and you copy the necessary business processes into it. 4. 4. you create a change request which is directly related to a business process or its steps. 5 Organizational Aspects for Long-Term Projects in SAP Solution Manager The use of SAP Solution Manager as an implementation tool also brings about the need to ensure the quality of all activities performed in this tool. but especially in connection to a solution embedded in a check out/in procedure. So the information about existing change requests will be available not only in the business process structure. Please refer to the descriptions in the chapters 4. In this way. Following this procedure ensures that the change documentation is always in sync with the technical realization. however. The Context tab can also be used to check out the business processes into the maintenance project (taking into maintenance) directly and to check it back after successful testing.0 Dietmar Hopp 16 Date: 23.3 Phase Change (Task list).2 ChaRM in Long-Term Project It is also possible to activate the Change Request Management for long-term projects. you can choose between three different change documents (normal change. you will be able to assign the appropriate business process or business process step to the Context tab of the normal correction. the connection between the changes and the documentation is guaranteed.2.Business Process Long-Term Redesign 4. that using Change Request Management requires additional configuration of SAP Solution Manager. target. admin change and test message). By using this variant. The quality assurance team should have Title: Long-Term Implementation © 2011 SAP AG Page 25 of 59 Version: 2. and production.1. There are several areas where governance is needed: System Landscape: The system landscape information is the foundation for nearly all SAP Solution Manager functionalities. For this project type. Change Types and Phase changes (Task list) All necessary redesign tasks will be reflected by normal corrections which take longer than the normal maintenance cycle. It should be noted.1. A proven method is to establish a quality assurance team which ensures that all basic activities in SAP Solution Manager are performed correctly. but also in “Change Request” and thus also in “Change Document” on the Context tab. Urgent corrections are not necessary as you are implementing a new functionality (all fixes for production will be performed by maintenance).2011 D-69190 Walldorf o .4 Business Process Integration for Document Management Change Request Management can be used not only in a maintenance project. such as the definition of logical systems: the source.1 Method.08.

 Standards Review. Assurance that all new projects have the same design and follow the same procedures to allow reuse in ALM. project type and so on). be authorized to create and change managed systems. These logical components are used for all current and future projects.  Business Process Design Consulting. Every new project team has to be trained on how to use SAP Solution Manager functionalities: especially on how to handle documents. decisions concerning building of the ALM in SAP Solution Manager. and to the decisions on which nonSAP tools have to be used for ALM purposes. status schemas. Possible reuse of existing business processes or documents should be discussed. structures. the quality assurance team could discuss with Project Management how to perform the project and how SAP Solution Manager can support them for this purpose.  Project Creation. The systems can then be grouped into logical components. and document attributes. This will also ensure the quality of performed tasks. o Standard and Design Definitions: To ensure the consistency of all standards used in the projects like document types. While keeping the business processes granular (please refer to the chapter “Business Process design”).2011 Page 26 of 59 .Business Process Long-Term Redesign access to this area. and also be able to create all necessary RFCs for all appropriate clients. This central team is the main contact point for all requests regarding SAP Solution Manager functionalities. the team should also attend to design questions. and clarify customizing tasks. SAP can offer to take over central activities in SAP Solution Manager like creating a project or assigning a project landscape. Definition of quality control points (Quality Gate) and regular checks of business processes and documentation quality. All customizing and/or development activities have to be approved and activated by this team. o o © 2011 SAP AG Dietmar Hopp 16 D-69190 Walldorf Title: Long-Term Implementation Version: 2. correct assignment handling has to be guaranteed as well. As a service to the project team. make developments.  Knowledge Transfer.0 Date: 23.  SAP Solution Manager Consulting. Before a new project starts. The aim of this team should also be to ensure the correctness and quality of the business process design. Possible services for incoming projects:  Project Consulting (which processes.08.

0 Date: 23. you prepare the object S_PROJECT for several users (one group has PROJECT_ID = I* and the other PROJECT_ID =T*).08. Other team members can only open the tab in display mode. for example. One KW Folder can be assigned to exactly one folder group. and go to the menu Settings  Folder Groups. You need to change the authorization for the tab (authorization object AI_SA_TAB) to enable assigned team members to work in the tab. 2) Work with a predefined name space for the projects (e. for the area SAP Solution Architect.2011 Page 27 of 59 © 2011 SAP AG Dietmar Hopp 16 D-69190 Walldorf . If you check this box. 6. template projects with T). Afterwards. In this view. only team members who are assigned in the Administration tab can work on the nodes of a project structure. you can create a folder group for the new folder. Title: Long-Term Implementation Version: 2. Authorization object S_PROJECTS and S_PROJECT can be found.1 Projects Concerning restrictions. Restrictions within a Project (Structure): The setting "Restrict changes to nodes in project to assigned team members" can be activated in SOLAR_PROJECT_ADMIN on the Team Members tab and allows changes to nodes in SOLAR01/02 where the user is assigned. Implementation Projects begins with I. in the role SAP_SOLAR_PM. you could: 1) Assign the authorization for specific projects to the object (PROJECT_ID  Project name) to which the user has access. Please follow the description below to set these up in your system.g. All other nodes will only be in display mode. you have two options: Restrictions between Projects: You could use the authorization object S_PROJECT.. Depending on the number of implementation projects.2 Document Management Standard Solution: Restrictions within a Project This solution is based on a standard functionality of SAP Solution Manager which restricts the ability to change nodes in a project to assigned team members. 1) Please start transaction SI23. This flag can be set in transaction SOLAR_PROJECT_ADMIN on the tab Project Member. Using additional KW Folders You can use different KW folders within one project. Please copy the role and set it up. The authorization for all included documents is checked against this folder group.Business Process Long-Term Redesign 6 Authorizations 6.

otherwise it will not be possible to change the folder group). start transaction SI80 and select the folder in which the folder group will be changed. Now you should be able to choose the folder group (created in step 1). using the Attribute popup of the document and the button “Replace Folder”. you should be able to move special "top secret" documents to the newly created folder.Business Process Long-Term Redesign 2) Afterwards. using KW function modules. The parameter IWB_FLDGRP is usually equal to the project name of the folder created by the system. the assignment is also possible when saving the document in Method HANDLE_EXIT_BEFORE_SAVE in Class CL_SA_IO_DOC. Afterwards. Alternatively. 3) Alternatively. The folder group can be assigned to the authorization object S_IWB.2011 Page 28 of 59 .08. using F4-help.0 Date: 23. during project creation. Go to the menu Folder  Attributes  Change (the context where you currently are should be equal to the origin context in the attributes of the folder. © 2011 SAP AG Dietmar Hopp 16 D-69190 Walldorf Title: Long-Term Implementation Version: 2. you can create a new KW folder and assign the folder group to it.

What to do Screen Display Select system and client from SMSY in SAP Solution Manager For a new client.Business Process Long-Term Redesign 7 Setup/Configuration and Procedures 7.08. The following instructions describe how to create RFC connections between SAP Solution Manager and the Managed System. © 2011 SAP AG Dietmar Hopp 16 D-69190 Walldorf Title: Long-Term Implementation Version: 2.2011 Page 29 of 59 . Select the client and click button „Generate RFC with Assistant‟.1 Definition of System Landscape – SMSY SAP Solution Manager is the central access point for your landscape. some basic configuration needs to be executed in transaction SMSY either manually or automatically.1. If a new Managed System is to be included. please refer to the basic configuration guide of SMSP (Solution Manager Starter Pack).0 Date: 23. For details on how to maintain a system in SAP Solution Manager.1 General Configuration 7. no RFC connections are established.

08.2011 Page 30 of 59 . Select „Continue‟.Business Process Long-Term Redesign Follow the wizard and use default values for creating RFC connections.0 Date: 23. © 2011 SAP AG Dietmar Hopp 16 D-69190 Walldorf Title: Long-Term Implementation Version: 2.

select „Continue‟. Create users for RFC connection.2011 Page 31 of 59 . select „Continue‟.Business Process Long-Term Redesign Create users for RFC connection. © 2011 SAP AG Dietmar Hopp 16 D-69190 Walldorf Title: Long-Term Implementation Version: 2.08.0 Date: 23.

Select „Continue‟.2011 Page 32 of 59 . © 2011 SAP AG Dietmar Hopp 16 D-69190 Walldorf Title: Long-Term Implementation Version: 2.0 Date: 23.08.Business Process Long-Term Redesign Select „Continue‟.

2 Project Standards To use document management in SAP Solution Manager. The system logon screen will appear. some adjustments and customization is needed.08. © 2011 SAP AG Dietmar Hopp 16 D-69190 Walldorf Title: Long-Term Implementation Version: 2.2011 Page 33 of 59 .Business Process Long-Term Redesign Select „Continue‟. (Please refer to SMSP configuration guide for details) 7. Input the user name and password to generate the RFC connection.0 Date: 23.1. Note: this user should have authorization for RFC creation as well as for Trusted RFC.

1.08.0 Date: 23. template project…) Select Documentation Type Tab © 2011 SAP AG Dietmar Hopp 16 D-69190 Walldorf Title: Long-Term Implementation Version: 2.Business Process Long-Term Redesign 7.3 Definition of Document Types At least the following document types should be available in the customer system (example): o o o o o o o ZBPD: Business Process Description ZCON: Configuration Description ZFSP: Functional Specification ZTSP: Technical Specification ZUT: User Training ZUAT: User Acceptance Test ZAUT: Authorization Where to configure/how to do: What to do Screen Display Document Types (transaction SOLAR_PROJ ECT_ADMIN menu Goto  Project Template  Implementation Project.2011 Page 34 of 59 .

08.0 Date: 23.2011 Page 35 of 59 .Business Process Long-Term Redesign Define Documentation Type (here: ZBPD) Upload the template into the Documentation Type New template has to be released in order to be available for later use © 2011 SAP AG Dietmar Hopp 16 D-69190 Walldorf Title: Long-Term Implementation Version: 2.

Where to configure/how to do: © 2011 SAP AG Dietmar Hopp 16 D-69190 Walldorf Title: Long-Term Implementation Version: 2. several assignments possible.2011 Page 36 of 59 .4 Definition of Status Schema Document types are assigned to customer specific status schema(s). 7. relevance for Blueprint document or status schema assignment.1. All status schemas contain customer defined status values like: o o o o Z_NEW Z_PROGRESS Z_APPROVAL Z_RELEASED Status value Z_RELEASED shall be included into the table for Read Authorization.0 Date: 23.08. Please create one common Release status value for all status schemas.Business Process Long-Term Redesign Possible corrections on the Documentation template Further settings for the Documentation Type like: global availability.

08.Business Process Long-Term Redesign What to do Screen Display Status Value Definition (transaction SPRO) Press “New Entries” and create Values Save and record in a transport Assign Status Values to Read Authorization © 2011 SAP AG Dietmar Hopp 16 D-69190 Walldorf Title: Long-Term Implementation Version: 2.2011 Page 37 of 59 .0 Date: 23.

08.Business Process Long-Term Redesign Select from the list of available Status Values Definition of Status Schema Create the Status Schema by pushing “New Entry” © 2011 SAP AG Dietmar Hopp 16 D-69190 Walldorf Title: Long-Term Implementation Version: 2.2011 Page 38 of 59 .0 Date: 23.

2011 Page 39 of 59 .0 Date: 23.Business Process Long-Term Redesign Decide which entries shall be part of Status Schema Assign Status Schema to Documentation Types Make Documentation Type available for project type Return to topic content © 2011 SAP AG Dietmar Hopp 16 D-69190 Walldorf Title: Long-Term Implementation Version: 2.08.

© 2011 SAP AG Dietmar Hopp 16 D-69190 Walldorf Title: Long-Term Implementation Version: 2.0 Date: 23. Using it. Where to configure/how to do: What to do Screen Display Download of SOLARBLUEPRINT .2011 Page 40 of 59 .5 Adjustments to Blueprint Document The functionality for creating the Business Blueprint is provided for all project types in SAP Solution Manager.Business Process Long-Term Redesign 7.1.08.DOC and correction (replacement of Logo). you can create the blueprint document based on the content of all blueprint-relevant documents collected for the rollout project (process description. functional specification or similar). The template of the blueprint document can be adjusted in customizing as shown.

© 2011 SAP AG Dietmar Hopp 16 D-69190 Walldorf Title: Long-Term Implementation Version: 2. where it was changed From now on the customer version will be used to create a blueprint document.Business Process Long-Term Redesign Change the template Upload the template from the storage location.2011 Page 41 of 59 .08.0 Date: 23.

0 Date: 23.08. rollout projects. Where to configure/how to do: What to do Screen Display Customization in transaction SPRO Creation of Structure/Object attribute “Area” © 2011 SAP AG Dietmar Hopp 16 D-69190 Walldorf Title: Long-Term Implementation Version: 2. in a solution.2011 Page 42 of 59 .1. custom-defined tables can be used with a defined range of possible input values.Business Process Long-Term Redesign 7. For this.6 Structure/Object Attributes Structure attributes are typically used for filtering purposes in templates. test plans and also as a reporting help.

Business Process Long-Term Redesign Decide which entries will be used for the attribute (table assignment) Assign attribute Z_SAP_AREA to objects Attribute will be available for structure nodes © 2011 SAP AG Dietmar Hopp 16 D-69190 Walldorf Title: Long-Term Implementation Version: 2.08.0 Date: 23.2011 Page 43 of 59 .

2011 Page 44 of 59 .Business Process Long-Term Redesign Assign attribute Z_COMPONENT to object Project and Solution Node Set the other options Result: the attribute is available for business process structures Return to topic content © 2011 SAP AG Dietmar Hopp 16 D-69190 Walldorf Title: Long-Term Implementation Version: 2.08.0 Date: 23.

0 Date: 23. Where to configure/how to do: What to do Screen Display Create an attribute through transaction SPRO Create an attribute “Project ID” © 2011 SAP AG Dietmar Hopp 16 D-69190 Walldorf Title: Long-Term Implementation Version: 2.7 Customer Attributes for Documents To improve reporting of documents in the design or configuration phase of your project.Business Process Long-Term Redesign 7. This means that those attributes will be passed to all document copies of the original documents. The customization described below is done with the example of Project ID as an attribute.1. The information on who changed the attribute and when it was changed will be logged in the history of the document.08. it is possible to create customer attributes for documents.2011 Page 45 of 59 . The advantage of these attributes is their ALM accomplishment. One possibility for such an attribute is the Project ID under which the document was created/changed.

08.2011 Page 46 of 59 .0 Date: 23.Business Process Long-Term Redesign Assignment of a table and field to which the attribute will relate Activate the attribute Record changes in a package Assign the newly created custom attribute to PHIO class SOLARGENSRC_V © 2011 SAP AG Dietmar Hopp 16 D-69190 Walldorf Title: Long-Term Implementation Version: 2.

The same activities can also be performed for the attribute “SAP Component” to detect which documents belong to which SAP area. the new customization has to be activated Result in SOLAR01/02 for document After creating the attributes.08.2011 Page 47 of 59 . it might be necessary to refresh the buffer on servers (transaction SE33 for context IWB_CLASS_PROPS).Business Process Long-Term Redesign New attribute has to be assigned to instance attributes After saving. © 2011 SAP AG Dietmar Hopp 16 D-69190 Walldorf Title: Long-Term Implementation Version: 2.0 Date: 23.

Transactions .0 Date: 23.2 Long-Term Project Creation To use the long-term project in SAP Solution Manager. there are several steps to be maintained in the system: o o o o Project Creation in different KW Enhancement System landscape maintenance Business process structure copy Behavior of assignments: .08.Business Process Long-Term Redesign 7.2011 Page 48 of 59 .Configuration .Structure Attributes .Document .Document Attributes Screen Display What to do long-term Project Creation Enter the T-Code SOLAR_PROJEC T_ADMIN and then you will go to the project administration screen where you can start to create the project. Maintain Mandatory Fields and Save You can assign the solution to the project when the project deals with the same system landscape © 2011 SAP AG Dietmar Hopp 16 D-69190 Walldorf Title: Long-Term Implementation Version: 2.

0 Date: 23. Navigate to the business blueprint screen b.Business Process Long-Term Redesign During saving.08. select the Source: “Solution” and use F4 Help to copy business scenarios or processes from the solution © 2011 SAP AG Dietmar Hopp 16 D-69190 Walldorf Title: Long-Term Implementation Version: 2.2011 Page 49 of 59 . Go to the structure tab. the KW Enhancement has to be changed from KWCUST 620 to any other one Business Process Assignment a.

0 Date: 23.08.2011 Page 50 of 59 .Business Process Long-Term Redesign Choose the option: “Refer to Documents” System landscape will be copied from the solution into the long-term project Business Process Assignments a. Business processes will be copied into the project: © 2011 SAP AG Dietmar Hopp 16 D-69190 Walldorf Title: Long-Term Implementation Version: 2.

together with all assignments on all tabs Document Management in a long-term project a.2011 Page 51 of 59 .08. The picture shows a change to a document in the maintenance project assigned to the solution.0 Date: 23. Document attributes are changed (project ID) © 2011 SAP AG Dietmar Hopp 16 D-69190 Walldorf Title: Long-Term Implementation Version: 2. All Documents are linked from the solution into the project.Business Process Long-Term Redesign b.

08. the system will create a copy.0 Date: 23. As soon as the document is changed.2011 Page 52 of 59 .Business Process Long-Term Redesign b. At the end of the long-term project. the document content is merged with the original document stored in the solution (through maintenance). Changes made to this document will not be reflected in the solution/ maintenance documentation. Changes made in maintenance will also be reflected in the long-term project c. This will be visible in all other potential longterm projects Return to topic content © 2011 SAP AG Dietmar Hopp 16 D-69190 Walldorf Title: Long-Term Implementation Version: 2.

2.0 Date: 23.Business Process Long-Term Redesign 7.1 Compare & Adjust: From Maintenance to Long-Term project Use the Compare & Adjust procedure after every maintenance cycle: What to do Screen Display New Documentation is created during maintenance Start Compare & Adjust (transaction SA_PROJECT_UPGR ADE) for the longterm project © 2011 SAP AG Dietmar Hopp 16 D-69190 Walldorf Title: Long-Term Implementation Version: 2.08.2011 Page 53 of 59 .

Afterwards. the test phase is prepared. Test Case Assignment in a Project In a long-term project. or to assign test descriptions to business scenarios. test plans and test packages can be generated according to business processes and the progress of testing and reporting can be tracked. Existing test cases (coming from the solution) can be reused or redesigned.Business Process Long-Term Redesign Results will be displayed in the implementation project. Adjustment can be started. These test documents can be reused for test plan creation.0 Date: 23.08. Return to topic content 7.2.2011 Page 54 of 59 . Afterwards. © 2011 SAP AG Dietmar Hopp 16 D-69190 Walldorf Title: Long-Term Implementation Version: 2. select „Copy‟ and „Complete‟. ECATT scripts. it is possible to assign or redesign test cases. You can adjust all changes or select changes you want to take over (depending on global attributes).2 Testing in the Long-Term Project During the project implementation phase. business processes or business process steps.

Test Workbench Test Workbench is embedded in SAP Solution Manager for Test Management.08.2011 Page 55 of 59 . Return to topic content © 2011 SAP AG Dietmar Hopp 16 D-69190 Walldorf Title: Long-Term Implementation Version: 2. on tab Test Case. After the assignment of test documents. a test plan can be generated in the Test Workbench and test packages can be created for different Testers.0 Date: 23.Business Process Long-Term Redesign Assign test documents to a business process step.

2.Business Process Long-Term Redesign 7.0 Date: 23.2011 Page 56 of 59 .3 Learning Map Screen Display What to do Create a Learning Map using transaction SOLAR_LEARNING_ MAP Create Chapter and Units Search for training material and assign these to the units.08. © 2011 SAP AG Dietmar Hopp 16 D-69190 Walldorf Title: Long-Term Implementation Version: 2.

2011 Page 57 of 59 .4 Go-Live and Delta Adjustment to the Solution Screen Display What to do For the handover of redesigned Business Processes.Business Process Long-Term Redesign Send to End User Return to topic content 7. the extended Compare &Adjust can be used © 2011 SAP AG Dietmar Hopp 16 D-69190 Walldorf Title: Long-Term Implementation Version: 2.2.0 Date: 23.08.

0 Date: 23.Business Process Long-Term Redesign Take over changes Return to topic content 7.08. Maintenance Project To change the business process structure in a solution. and then enable the „Checkout/Check-in‟ functionality.2. From now on.5 Post Go-Live Maintenance A solution is created after go-live.2011 Page 58 of 59 . all operations and maintenance are executed on the solution instead of the project. © 2011 SAP AG Dietmar Hopp 16 D-69190 Walldorf Title: Long-Term Implementation Version: 2. it is recommended to use a maintenance project instead of making changes directly to the solution Assign a maintenance project to a solution.

to perform post go-live maintenance. or landscape directly in the solution. The maintenance project for this solution can be checked in into the Solution Directory. it is no longer possible to change the business structure.0 Date: 23. document.08. Any necessary changes will be checked-out into the maintenance project and checked-in after changes. Use the „Checkin/Check-out‟ button in the Solution Directory and maintenance project.Business Process Long-Term Redesign Check-In / Check-Out After the maintenance project is assigned to one solution. Return to topic content © 2011 SAP AG Dietmar Hopp 16 D-69190 Walldorf Title: Long-Term Implementation Version: 2.2011 Page 59 of 59 .

Sign up to vote on this title
UsefulNot useful

Master Your Semester with Scribd & The New York Times

Special offer: Get 4 months of Scribd and The New York Times for just $1.87 per week!

Master Your Semester with a Special Offer from Scribd & The New York Times