Matthias Friedrich, Torsten Sternberg

Change Request Management with SAP Solution Manager
®

Bonn � Boston

Contents
Preface ....................................................................................................... 11

1

Introduction ..............................................................................
1.1 IT Change Management and the Information Technology Infrastructure Library ................................................................... 1.1.1 Classification of IT Change Management ........................... 1.1.2 Definition of Concepts ...................................................... 1.1.3 Tasks of IT Change Management ....................................... 1.1.4 Success Factors for IT Change Management ...................... SAP Solution Manager and the Information Technology Infrastructure Library ................................................................... 1.2.1 SAP Solution Manager Functions ...................................... 1.2.2 Support of ITIL Practices Using SAP Solution Manager ...... Change Request Management with SAP Solution Manager ......... 1.3.1 Change (Request) Workflows ............................................ 1.3.2 Project Administration ...................................................... 1.3.3 Monitoring and Reporting ................................................ Summary ....................................................................................

15
15 15 18 19 20 20 21 24 28 29 30 31 31

1.2

1.3

1.4

2

Architecture of Change Request Management ........................
2.1 2.2 Elements of Change Request Management ................................. Project Administration in SAP Solution Manager ......................... 2.2.1 Solution Manager Project Types ........................................ 2.2.2 SAP Solution Manager Projects in Change Request Management .................................................................... 2.2.3 IMG Projects and CTS Projects .......................................... 2.2.4 Project Cycle and Task List ................................................ 2.2.5 cProjects .......................................................................... Transaction Types/Workflows ...................................................... 2.3.1 Service Desk Message ....................................................... 2.3.2 Change Request ............................................................... 2.3.3 Change Document ............................................................

33
33 35 35 39 41 45 50 51 53 54 58

2.3

5

C  ontents Contents

2.4

2.3.4 Normal Correction/Development Activity ......................... 2.3.5 Urgent Correction ............................................................. 2.3.6 Administration Message ................................................... 2.3.7 Test Message .................................................................... 2.3.8 Job Request ...................................................................... 2.3.9 Change Transactions for Projects ....................................... Summary ....................................................................................

59 64 65 66 67 67 68

3

Configuration of Change Request Management ......................
3.1 Preparation ................................................................................. 3.1.1 Organizational Questions ................................................. 3.1.2 Technical Questions .......................................................... 3.1.3 Prerequisites ..................................................................... 3.1.4 Available Documentation and Resources .......................... Configuration of Change Request Management .......................... 3.2.1 Standard Configuration ..................................................... 3.2.2 Extended Configuration .................................................... Defining Projects and Systems in Change Request Management .............................................................................. 3.3.1 Defining Logical Components ........................................... 3.3.2 Creating a Solution Manager Project ................................. 3.3.3 Final Check ....................................................................... Summary ....................................................................................

69
69 69 70 70 71 72 73 85 102 102 107 108 109

3.2

3.3

3.4

4

Use of Change Request Management ...................................... 111
4.1 Roles and Activities ..................................................................... 4.1.1 Requester ......................................................................... 4.1.2 Service Desk Employee ..................................................... 4.1.3 Change Manager .............................................................. 4.1.4 Change Advisory Board ..................................................... 4.1.5 Developer ........................................................................ 4.1.6 Tester ............................................................................... 4.1.7 IT Operator ...................................................................... 4.1.8 Additional User Information ............................................. 111 112 113 113 114 114 115 115 116

6

Contents

4.2

4.3

4.4

4.5

4.6

Processes and Integration Examples ............................................ 4.2.1 Example of the Urgent Correction ..................................... 4.2.2 Retrofit Process ................................................................ 4.2.3 Hot News ......................................................................... 4.2.4 Structure Elements for Change Transactions ...................... Administration ............................................................................ 4.3.1 Task List ........................................................................... 4.3.2 Extended Configuration .................................................... 4.3.3 Change Tracking ............................................................... 4.3.4 Scheduling ........................................................................ 4.3.5 Project Logistics ............................................................... Reporting and Monitoring .......................................................... 4.4.1 Solution Manager Reporting ............................................. 4.4.2 Transaction Monitor ......................................................... Work Centers .............................................................................. 4.5.1 Change Management Work Center ................................... 4.5.2 Configuration of Work Centers ......................................... 4.5.3 SAP GUI for HTML Configuration ..................................... Summary ....................................................................................

116 117 134 140 142 148 148 162 163 166 167 169 169 171 175 175 179 180 181

5

Security in Change Request Management ............................... 183
5.1 Authorizations in the SAP System ............................................... 5.1.1 Authorizations in the SAP Solution Manager System ......... 5.1.2 Authorizations in Satellite Systems ................................... 5.1.3 Work Center ..................................................................... 5.1.4 Extended Authorization Checks ........................................ Cross-System Object Lock ........................................................... 5.2.1 Functionality .................................................................... 5.2.2 Required Settings ............................................................. Critical Transport Objects ............................................................ 5.3.1 Functionality .................................................................... 5.3.2 Required Settings ............................................................. 5.3.3 Modifications ................................................................... Project Intersections ................................................................... 5.4.1 Real-Life Example ............................................................. 5.4.2 Required Settings ............................................................. Summary .................................................................................... 183 183 184 185 185 186 186 189 191 191 193 194 195 196 197 198

5.2

5.3

5.4

5.5

7

C  ontents Contents

6

Extensions of the Change Request Management Scenario ..... 199
6.1 Extended Transport Landscapes .................................................. 6.1.1 Three-System Landscape ................................................... 6.1.2 Four-System Landscape .................................................... 6.1.3 Parallel Phase Landscape .................................................. 6.1.4 Landscapes for Global Developments ............................... 6.1.5 Conclusion ....................................................................... Enhanced Transport Management ............................................... 6.2.1 Components ..................................................................... 6.2.2 TMS Configuration ........................................................... 6.2.3 Integration with Applications ........................................... 6.2.4 Landscape Scenarios ......................................................... 6.2.5 Integration of CTS+ and Change Request Management ..... 6.2.6 Conclusion ....................................................................... Extension Developments and Development Package ................... Customer-Specific Tab ................................................................. 6.4.1 Defining the Necessary Data Structures ............................ 6.4.2 Defining the Layout and Flow of the Dynpro .................... 6.4.3 Integrating the New Tab via the Screen Control ................ 6.4.4 Tabs in the Change Request .............................................. 6.4.5 Inserting the Calculation Logic .......................................... Extension of the Transaction Monitor .......................................... Extended Actions and Conditions ............................................... 6.6.1 Extended Check for Text IDs ............................................. 6.6.2 Extended Check for Partner Functions .............................. 6.6.3 Displaying Transport Requests .......................................... Summary .................................................................................... 199 199 201 203 205 206 206 208 210 214 217 225 227 227 228 228 232 235 236 237 239 241 242 247 251 255

6.2

6.3 6.4

6.5 6.6

6.7

7

Change Management in SAP Landscapes ................................ 257
7.1 Change Management Concept .................................................... 7.1.1 Maintenance — Maintenance Optimizer .......................... 7.1.2 Technical Integration ........................................................ 7.1.3 Testing .............................................................................. 7.1.4 Analysis ............................................................................ Quality Management in SAP Solution Manager ........................... 7.2.1 Functional Scope .............................................................. 257 258 260 260 261 261 261

7.2

8

.6........................................................ Index .................... 8.... Setting Up a Project Landscape ....8 8.......... 8.......................................................................................... 267 8........................................8...... Repair Flag for the Import ...........2...............................6 Adding New Systems .......................Contents 7...................................6...................................... Transports and SAP NetWeaver Business Warehouse ... Urgent Corrections in Parallel Systems ..... System and Client Copy .....5 8.......7 8................................................................................................................................... Import Subset and Import Project ........................ 9 .........4 8...............................3 8............. 8......................1 8............ 267 268 271 274 275 276 276 276 277 278 280 280 283 284 285 287 8...........................................................................3 7..............8.....3 Authorization Problems ................................2 Import All .........2 8..................................................1 Application Log ........................................... 8....................................8.......... SAP Notes .....2 Reports for Completing Project Cycles ................9 The Authors ............................. 263 265 8 Technical Notes on Usage and Troubleshooting ........1 Urgent Correction ...................................................................................... 8...............2 Prerequisites for Quality Gate Management .......................................................... Summary .......... Error Analysis ....

1 Change Request Management in SAP Solution Manager 33 .1 Elements of Change Request Management Change Request Management represents a core functional area within SAP Solution Manager. This chapter explains the various functional areas within Change Request Management and provides an initial insight into how Change Request Management fits into SAP Solution Manager.1 shows the stages of this lifecycle and the corresponding functions for each of these stages that are provided in SAP Solution Manager. and services to support the entire lifecycle of an application. you therefore need to understand these elements and how they work. To appreciate the full functional scope of Change Request Management. Implementation of SAP Solutions SAP Methods and Tools Global Rollout Customizing Synchronization E-Learning Management Test Management Solution Monitoring System Monitoring Business Process Monitoring Central System Administration EarlyWatch Alert Service Level Reporting Solution Reporting Implem en n tio ta Op at er Upgrade of SAP Solutions SAP Methods and Tools E-Learning Management Test Management Core Business Processes Service Desk Best Practices for Incident Management Integration of 3rd-Party Help Desks ions Op timiz ion at Delivery of SAP Services Onsite/Remote SAP Safeguarding Solution Manager Diagnostics Safe Remote Access Performance Measurements Logs and Dumps Traces Technical Configuration Change Request Management Follows ITIL Standards Maintenance Processes Figure 2.2 Architecture of Change Request Management Change Request Management consists of a number of individual elements in SAP Solution Manager. Figure 2. information. SAP Solution Manager provides a range of functions. 2.

which are distributed within the system landscape using the Transport Management System. SAP Solution Manager Project Administration Business Blueprint Configuration Testing System Landscape Maintenance SAP Solution Manager Project Test Cases Documentation SAP Change Manager Task List System and Transport Configuration Transport Tracking Training cProjects cProject System Landscape Service Desk SN Change Request Management CR CD Transport Management System DEV IMG Project CTS Project QAS PRD CTS Project CTS Project Figure 2. the SAP Change Manager box represents the functions specific to Change Request Management. The elements of Change Request Management are illustrated in Figure 2. These include the task list and the various transport tracking options. and monitored.2. documented. Within this cycle. In Figure 2.3. corrections of program errors) are implemented. Defining Logical Components). Information about the systems or system groups that require support is also maintained in Project Administration. and various systems grouped together in logical components as part of System Landscape Maintenance (see Section 3.2 ArchitectureofChangeRequestManagement Change Request Management is assigned to the optimization cycle. System Landscape Maintenance provides information about the systems that are to be supported. connections configured. required changes that have been detected during normal system operation (for example. EE EE 34 .2 EE Elements of Change Request Management Project Administration allows you to structure and classify change activities and the associated technical changes. The systems are defined. These technical changes result in transport requests.2.1.

It is also possible to specify in the configuration that selected areas cannot be modified. This information includes process steps. EE EE 35 . implementation. upgrade. 2. where all live processes are documented. test cases. This means that you can define processes. Detailed information about a process can be mapped in the form of a project structure within the project. The next section provides a detailed description of all of these areas and how they work. process steps. Together. 2. documentation. or Change Request Management for project organization. they represent the complete change request process.2 EE The Change Request Management box represents the two main subprocesses that make up Change Request Management. The change request and the change document each describes an organizational and technical subarea within a change. If the use of check-in/check-out functions is enabled in the Solution Directory. maintenance projects are used there also.2. and configuration/ customizing.1 Solution Manager Project Types The project types available in SAP Solution Manager are listed below: EE Implementation project This project type is used to implement new business processes in an SAP landscape with SAP Solution Manager. These serve project-related objectives in a range of scenarios. and control. documentation. for example. Maintenance project This project type is used to maintain live solutions and is used predominantly in Change Request Management. or test cases. documentation. Template project The structures of a project can be defined in a template project and then made available to other projects as templates. All maintenance activities for a solution are grouped together in this project type.2 Project Administration in SAP Solution Manager Various project types are delivered as standard with SAP Solution Manager.ProjectAdministrationinSAPSolutionManager 2. and then use these as a template for an enterprise-wide rollout.

EE Upgrade project Configuration settings required as part of an upgrade are made in an upgrade project.3 Quick Project Setup 36 . After check-out.2 ArchitectureofChangeRequestManagement Check-In/Check-Out Functions Check-in/check-out functions allow you to transfer a live business process from the Solution Directory to a maintenance project without any effect on the active process. Experienced users can also access Project Administration directly. One possible area of application for these projects arises in the context of SAP Services. which you can access with Transaction AI_SPS. which is briefly outlined below. EE EE Projects can be created quickly using a web-based wizard. Safeguarding project Safeguarding projects are used to analyze and subsequently eliminate the causes of critical situations. For example. Figure 2.3. changes can be made to the business process in the maintenance project. new process steps can be defined. Optimization project An optimization project enhances business processes or the general operation of a solution. This wizard is shown in Figure 2. You then use the check-in function to transfer the changed business process back to the Solution Directory.

which is shown in Figure 2. a detailed view of that project opens.4. All existing projects in SAP Solution Manager are displayed on the initial screen. where you combine logical systems in logical components that can then be used in various scenarios.4 Project Administration in SAP Solution Manager 2. 4. Proj. including Project Language and Project Description.ProjectAdministrationinSAPSolutionManager 2. A range of tabs is provided for this purpose. Here you can maintain various types of information that are of relevance to the project.3. 1. testing.2 Transaction SOLAR_PROJECT_ADMIN provides access to central Project Administration. Figure 2. contain various types of information that are not discussed in more depth at this point because. Scope. Here you can choose a logical component in order to select the systems belonging to an SAP product and assign these to the project. Defining Logical Components). are optional. You can also click on the Create Project button to create new projects or navigate to project analysis. The other tabs. with the exception of the information on the System Landscape tab. Team Member. System Landscape. Other information. A number of required entries need to be maintained on this tab. If you double-click on a project to select it. You define the systems for a project on the System Landscape tab. such as status values and time values. such as implementation. Milestones. the first of which is entitled General Data. these are not essential to Change Request Management (see Figure 2. and Project Standards.1. 3. or Change Request Management (see Section 3. You define a logical component in System Landscape Maintenance (Transaction SMSY). 37 .5).

Here.5 Detailed Information About a Solution Manager Project Figure 2. the fundamentals of the Change Request Management architecture. including change transports. It allows you to test all functions of Change Request Management.6 shows an example of a logical component. in the next section. together with its assigned logical systems ST4:200. 38 . Only the transport of Workbench objects cannot be simulated. ZCHARM_LANDSCAPE. owing to the cross-client validity of these objects. We will then return to the topic of Project Administration in the following sections. the logical systems are the three clients of an SAP Solution Manager system that represent a three-system landscape. The name of each logical system consists of the system ID and client. This configuration is often used during the initial setup of Change Request Management to verify locally that the setup is correct. ST4:300. Before we discuss the additional configuration options and information about the System Landscape tab in more detail.2 ArchitectureofChangeRequestManagement Figure 2. and ST4:400. This section describes other types of projects in addition to the Solution Manager projects specified above. we will briefly explain.

on the other hand.2 Figure 2.2.1. are nonrecurring. some further classifications are required from the perspective of Change Request Management.2 SAP Solution Manager Projects in Change Request Management As mentioned above. Maintenance Project Recurring Non-Recurring Figure 2. There is normally only a single project start and end date for these projects. A distinction is made among the four project types based on whether they are executed cyclically (recurring) or once only (nonrecurring). Solution Manager Project Types.6 System Landscape — Project Administration 2. Four of the project types described in Section 2.ProjectAdministrationinSAPSolutionManager 2. Implementation projects. a maintenance project is defined as recurring because it is always started again after it has been successfully completed. implementation project. As shown in Figure 2.2.7 Implementation Project Template Project Upgrade Project Recurring and Nonrecurring Projects 39 .7. template project. and upgrade projects. namely maintenance project. can be used in the Change Request Management scenario. However. template projects. and upgrade project. Solution Manager projects provide a basis for various scenarios in SAP Solution Manager.

the project cycle and task list.2 ArchitectureofChangeRequestManagement The reasoning behind this distinction has to do with the associated functional requirements of Change Request Management. A detailed explanation of IMG and CTS projects is provided below. In this case. a project management solution.2.8 illustrates the interaction between the various projects and the associated systems. namely. an IMG project is generated automatically in the development system (of the logical component). an IMG project is created in each development system defined.3. This option. you also have the option of creating a direct link to CTS projects. and the information in the Solution Manager project is stored there. IMG Projects and CTS Projects. The situation is different in projects of a nonrecurring nature. The section concludes by examining the option of integrating cProjects into Change Request Management. Other functions in SAP Solution Manager are shown here alongside the projects described above. which are discussed in more detail in Section 2. in turn.2. such as implementation projects. The project functions used are the IMG (Implementation Guide) project and the CTS (Change and Transport System) project. Figure 2. Both project functions are Basis functions and are therefore available in SAP NetWeaver or SAP Basis. A maintenance project involves maintaining processes or functions that are already used in production. If several logical components are assigned to a Solution Manager project. With IMG projects. allows you to assign all changes and therefore also all transport requests from CTS projects to the IMG project. Solution Manager projects are a prerequisite for using Change Request Management. This fundamental difference gives rise to different functional requirements. However. as well as the optional connection to cProjects. additional project functions are used in the managed systems and linked to the Solution Manager project to facilitate the monitoring of changes in these systems. Creating a Solution Manager Project). If you activate Change Request Management for a Solution Manager project (see Section 3. Project Cycle and Task List.3. followed by a discussion of the functions that are fulfilled by the project cycle and task list. 40 . a new process or function is implemented for the first time and is only used in production after the project has been successfully completed.4.2. which are discussed in more detail in Section 2. You create and manage these projects in SAP Solution Manager.

6). The option of assigning a CTS project to an IMG project means that the relevant information about transport requests can also be used in an IMG project and. EE In SAP Solution Manager.2 SAP Solution Manager Project Cycle Change Transaction Development System Logical System (System and Client) Project Cycle Task List Transport Requests IMG Project CTS Project Q P cProjects Project (Created in cProjects) Solution Manager Project D IMG Project CTS Project Q P D Figure 2.3 IMG Projects and CTS Projects As explained above. EE IMG (Implementation Guide) projects allow you to coordinate customizing activities and save the resulting changes in a project. in the Solution Manager project. you can link Solution Manager projects with IMG projects to access the systems in the IMG projects.2. The System Landscape tab shows several subcategories (you will recognize the Systems tab from Figure 2. CTS project functions for the project in question can be activated in an IMG project. IMG and CTS projects represent Basis functions and are therefore available in any SAP NetWeaver system. ultimately.ProjectAdministrationinSAPSolutionManager 2. 41 .8 Architecture of Change Request Management 2.9 shows a Solution Manager project of the maintenance project type. CTS (Change and Transport System) projects are parameters that can be used to group transport requests. Figure 2.

Figure 2.10 shows the detail view of the IMG project in the development system. If you select the IMG project and click on the Display button.9 Maintenance Project with Assigned IMG Project 1. 2. which consists of the logical systems ST4:200 (development). Figure 2. This corresponds to the development system of the demo landscape. Logical system ST4:200 is assigned to this IMG project. ST4:300 (quality assurance). and ST4:400 (production). you automatically access the IMG project view in the corresponding development system.10 IMG Project in the Development System 42 . If you select the IMG Projects tab.2 ArchitectureofChangeRequestManagement Figure 2. the assigned IMG project (CHARM01) is shown.

4.11 Selecting the Transp. you can also access information about the project data of the CTS project and information about the transport requests assigned to the CTS project (see Figure 2. select the Transp. Requests Tab in an IMG Project The Transp.11. which is shown in Figure 2. The other buttons. 3. 43 . From here. Here you can see the CHARM01 IMG project and the corresponding ST4_P00001 CTS project.13 is displayed. also display relevant information about transports. Requests tab.2 The structure and display of the IMG project are very similar to those of the Solution Manager project. If you click on the Display CTS project data button. Figure 2. Next. The only indications that this is a different project type are the type description Customizing Project at the top of the screen and the number of tabs.12). Requests tab shows information about CTS functions.12). Assigned CTS Requests and CTS Project Piece List (see Figure 2.ProjectAdministrationinSAPSolutionManager 2. the screen shown in Figure 2.

14 shows the project status switches for a CTS 44 . The final screen element to describe in relation to CTS projects is the project status switches.13 CTS Project Data 5. The project status switches for CTS projects allow you to activate or deactivate various properties for the CTS project and for the corresponding transport requests.12 The Transp. Requests Tab in an IMG Project Figure 2. Figure 2.2 ArchitectureofChangeRequestManagement Figure 2.

it controls and monitors these switches. If Change Request Management is active. task list. To use this information for a wide range of operational activities. we have described functions used by Change Request Management to gather information about changes in managed systems.1. Figure 2. an introduction to the project cycle. and integration of cProjects is provided below. 45 . Of particular relevance here are the switches for creating.4 Project Cycle and Task List Up to this point. This means you can prevent the creation of transport requests in the supported systems for change activities that are not part of Change Request Management. and importing transport requests.2 project. in Define Project Assignment for Requests as Mandatory in Section 3.2.2. Now that you are familiar with the various project types and how they interact in Change Request Management. 2.14 Project Status Switches of a CTS Project 6. a functional basis for the execution of these activities is required.ProjectAdministrationinSAPSolutionManager 2. in particular in relation to the mandatory assignment of requests to projects. such as the distribution of transports. You will find detailed information about configuration. releasing.

the Schedule Manager allows you to execute a variety of operational tasks. Go-Live. The possible phase values for a cycle. The phase values that are relevant for daily system operation are Development without release. In Change Request Management. This scheduling tool also allows you to control the lifecycle of a Solution Manager project.g. Test. which is based on the familiar Schedule Manager function for executing and monitoring recurring tasks. and GoLive. and Completed. and the individual phases with the corresponding changes. To be Closed. Figure 2. All projects have a certain lifecycle. Test. referred to as the project cycle. such as the development phase and test phase. Development with Release. divided into a number of phases. Implementation Project) Development (without and with Release) Project Cycle Test Emergency Correction Synchronization Go-Live Synchronization Development Activity Synchronization Figure 2. The scheduling tool maps project phases and the functions required during each of these.2 ArchitectureofChangeRequestManagement In Change Request Management. Emergency Correction. in turn. which is. and Changes 46 . Project Cycle. Development with Release. project cycle. including the import of transports into target systems and the creation and release of new transport requests. this basis is provided by the scheduling tool. Development without Release. These phases reflect the individual steps involved in a project. Various activities are executed within these phases over the course of a project. which are identical in all projects.15 shows the interaction between a project. Emergency Correction. There is always a 1:1 relationship between a project and project cycle. cProjects SAP Solution Manager Project (e.15 Implementation Project. are as follows: Created.

is represented by a generated task list (Schedule Manager) and a change transaction (CRM document).16 Project Cycle of a Solution Manager Project Figure 2.2 From a technical perspective.17 shows an example of a task list.17 Task List in Change Request Management 47 .3. the project cycle. The change transaction allows you to move from one project phase to the next and provides information about the transport requests belonging to the project.16. Project Cycle Change Transaction Task List Figure 2. see Section 4. Figure 2. For more detailed information about the task list. as shown in Figure 2. The task list is part of the working environment of the IT operator.ProjectAdministrationinSAPSolutionManager 2. and it indicates the current phase of the project cycle. The task list contains a list of activities and a representation of the systems supported within the project cycle. Administration.

Maintenance projects also have their own project lifecycle. These activities are divided into phases within each three-month maintenance cycle.16 could apply to an implementation project.7).18 Maintenance Project and Maintenance Cycle Maintenance projects differ from other project types in one important respect. For example. development and testing of corrections. the maintenance cycle has reached the final phase and all of the changes from the cycle as a whole are imported into the production system. The maintenance cycle can be completed after a successful import into the production system. These include. template project.18. or upgrade project. it may be necessary to import an important change or correction into the production system as quickly as possible. It is useful to recall. a permanent maintenance project for a live solution may be divided into maintenance cycles of three months each. At the end of the three months. in this case. at this point. However. most importantly. All necessary support and maintenance tasks are executed within these maintenance cycles. This continuous cycle is illustrated in Figure 2. In this case. For example. 48 . A special change transaction is therefore provided for this very typical scenario. Maintenance Project Maintenance Cycle with Phases Change Transaction Task List Figure 2. each cycle includes a development phase and a test phase. it is referred to as the maintenance cycle. Within a maintenance cycle. This change transaction is referred to as an Urgent Correction. the difference among these project types and maintenance projects (see Figure 2. and a new maintenance cycle can then be generated to manage all changes that arise over the next three months.2 ArchitectureofChangeRequestManagement The project cycle shown in Figure 2. the threemonth cycle is too long.

normal corrections for a maintenance cycle are only possible during the development phases (development with and without release). This figure also indicates the phases in which normal corrections and urgent corrections can be made and executed within the maintenance cycle.19 Maintenance Project. For a detailed description of urgent corrections.3. you can see the interaction between the maintenance project.19 illustrates the various change types in a maintenance project. Urgent Correction. and Transactions 49 . on the other hand. Maintenance Cycle. from there. As you can see. This special feature of maintenance projects sets them apart from other project types.5. independent of the phases in the maintenance cycle. normal corrections can only be transported into the quality assurance system and.2 This change transaction is only available in maintenance projects. refer to Section 2. Here. During subsequent phases.ProjectAdministrationinSAPSolutionManager 2. can be created up until shortly before the go-live to ensure their integration into the same maintenance cycle. and corresponding phases. cProjects SAP Solution Manager Project (Maintenance Project) Maintenance Cycle Development (without/with Release) Test Emergency Correction Synchronization Go-Live Synchronization Normal Correction Synchronization Urgent Correction (Independent of Maintenance Cycle) Figure 2. and enables an immediate transport of changes into the production system. Urgent corrections. maintenance cycle. once again. into the production system. Figure 2.

and display projects in graphical form as Gantt charts. you require a Solution Manager project with Change Request Management activated. It is also important to point out exactly how cProjects and Change Request Management interact. Test.2 ArchitectureofChangeRequestManagement As explained in the detailed discussion of normal corrections later in this chapter (see Section 2. It therefore provides an effective working environment for project leads (see Figure 2. This integration establishes a 1:1 link between a cProjects project and a Solution Manager project. The correct phase value must then be set in the cProjects project before it can be set in the task list or change transaction. and To be Closed. a task list must have been generated for the project. 50 . a warning is issued in the task list. 2. If not. This means that cProjects plays a leading role in terms of project organization. and deliverables. you can also create a normal correction after the development phases. roles. these will then be part of the next maintenance cycle. Go-Live. If a cProjects project is assigned to a Solution Manager project. Before you can integrate cProjects. define milestones.4. Normal Correction/Development Activity).20). if the phase changes from Development with Release to Test — a consistency check is run against the cProjects project to verify the phase value is also Test in that project. In addition. You can then use a range of functions (such as phase-based project management).2. If a new phase is selected during the Solution Manager project cycle — for example.5 cProjects Integration of the Collaboration Projects (cProjects) solution for project management into Change Request Management represents an optional enhancement.3. so that the Change Request Management process benefits from the advanced project management functions in the cProjects project. The following phase values are relevant in this case: Development without Release. Development with Release. However. indicating an inconsistency with the cProjects project. Emergency Correction. the cProjects project has the same phase values as the corresponding Solution Manager project.

From a technical point of view. These workflows are not to be confused with SAP Business Workflows. Transaction types are documents created in the CRM service process transaction.3 Figure 2. The relevant workflows were introduced in Section 1. various workflows are provided to fulfill diverse process requirements. They can be used to represent a defined process flow.3. provided that the relevant Customizing settings are configured. Change (Request) Workflows.20 cProjects with Maintenance Project 2.1. we explain various workflows that are used either directly or indirectly in Change Request Management. The transactions can be opened and edited in the service process transaction.TransactionTypes/Workflows  2. all of these workflows represent various transaction types created in the CRM service process transaction (CRMD_ORDER). 51 . Here.3 Transaction Types/Workflows In Change Request Management.

Information about the people and systems involved is stored in each transaction. In a Service Desk message. This information is stored as master data. for example.21 Transactions in Change Request Management The Service Desk message is not part of Change Request Management. refer to Section 4. but it often initiates actions in Change Request Management. These transactions are mapped by default by urgent corrections. Links between transaction types can be set by default or defined by the user in a selection field. Figure 2. The Service Desk is another functional area in SAP Solution Manager. Change Manager. Change Process Urgent Correction Change Request Normal Correction Service Desk Message Administration Test Message Figure 2. you have the option of creating a linked change request. whereas information must be maintained in the installed base (IBase) for the supported systems.1. For more detailed information about configuring Change Request Management.21 shows the possible links.2 ArchitectureofChangeRequestManagement Various transaction types (such as Service Desk messages or change requests) can be linked together to unite different processes. The change request may give rise to various follow-up transactions. Business partners need to be maintained for the people involved. which is used in the context of Incident Management. normal corrections. 52 . You can display these links by checking the document flow in Transaction CRMD_ORDER. In this way. follow-up documents and processes can be linked on the basis of the values in the selection field in the original document. and the administration message. which must be maintained in SAP Solution Manager. Test messages represent a special case because they are issued without a change request.3. This option also represents an intersection with Change Request Management because the change request is the source document for all subsequent activities in Change Request Management.

a search function for finding SAP Notes.22 Work Center for Incident Management 53 . The reply from SAP is also replicated directly to the Service Desk in SAP Solution Manager and can be processed further there. One advantage of using Service Desk functionality is the possibility of creating an SAP customer message for SAP from your own Service Desk. An example of a Work Center is provided in Figure 2. Service Desk functionality allows you to create problem messages in SAP Solution Manager directly or in a connected satellite system.TransactionTypes/Workflows  2.1 Service Desk Message The default SAP transaction type for the Service Desk message. and a direct exchange with the SAP support organization. which has the technical name SLFN.3 2. This gives the end user the option of reporting errors or problems and storing this information centrally in SAP Solution Manager. Service Desk functions include an option for switching among various organizational units.3. represents a separate functional area in SAP Solution Manager. where it can then be processed by the service organization. access to a separate solution database.22. Figure 2. A web-based interface (the Work Center) allows end users to check the current status of their Service Desk messages at any time and to respond as appropriate.

23 Creating a Change Request from a Service Desk Message 2. which can be classified as required or optional.3. Figure 2. represents the first subprocess of Change Request Management. which is referred to by the technical name SDCR in Customizing.2 ArchitectureofChangeRequestManagement If the analysis performed within the Service Desk indicates that corrective action is required. As we will see later. the Service Desk employee can create a change request from the Service Desk message. Here you can call various functions from the action list. Its main role is to document the request and all associated information. A change request can be created directly with the Create Change Document action.23 shows how a change request can be created from a Service Desk message in the service process transaction CRMD_ORDER. Note The use of the term change document in this action is somewhat confusing because the action creates a change request. Figure 2. 54 . this change request subsequently results in a change document.2 Change Request A change request.

A change type must also be selected. This specifies the transaction that is to be used to implement the change. Approved. Figure 2. Here.24 shows an extract from the service process transaction (CRMD_ORDER).TransactionTypes/Workflows  2.3 Some information is essential to ensure that no errors occur during further processing of the request in Change Request Management. This required information includes a description of the request in the text field provided. categorizations. In the case of maintenance projects. 55 . such as a description of the effects on business processes or systems. Figure 2. and additional textual information. additional user information.24 User Status in a Change Request The standard process delivered by SAP contains the following status values: To Be Approved. This status profile contains various status values. You can also attach documents to the request. the change manager). and information about the systems and users affected (for example. Rejected. and Confirmed. The optional information that can be specified in the change request includes dates. which are displayed in the change request as the user status. you can choose between a normal correction and an administration message. which includes the user status. The purpose of the change request is to have a change approved or rejected. Implemented. you also have the option of implementing an urgent correction. A status profile is provided to identify the various steps from the creation of a request to the final decision regarding the change.

template projects. and upgrade 56 . We have already introduced you to these change types at the start of Section 2. You can click on this icon to display a description of the error. Customers tend to have their own specific process for handling a change request. In other words. copy the status profile (SDCRHEAD) to the customer namespace.25 Error Message in the Change Request The change type is specified in the Subject field. In many cases. If you fail to enter required information or if you enter information incorrectly. Instead. ZDCRHEAD) to transaction type SDCR. the relevant status profile can easily be supplemented or modified. Tip: Changing the Status Profile Do not change the standard SAP status profile. the selection of a transaction type represents a required entry in a change request. we need to look again at the transaction type that must be specified in the change request. To conclude this section. Urgent Correction. a red traffic-light icon appears in the top right of the screen in the service process transaction. As stated above. For implementation projects. the change types correspond to the transaction types Normal Correction.3. The SOLMAN_CM_GENERAL IMG activity similarly advises you to always use an SAP profile as a template if you want to define your own profile. various departments or partners need to be involved to ensure that a sound decision can be made regarding the implementation or rejection of the change at the end of the change request process. Transaction Types/Workflows. where you can select from all available change types.25 shows an example of an error message text that was issued because a transaction type was not specified in the change request. Figure 2. and Administration. Figure 2. Make any necessary changes in the copied profile and then assign the new status profile (for example.2 ArchitectureofChangeRequestManagement If these status values cannot adequately map your change request process.

4. upgrade project EE EE Development/Development Activity Administration EE Maintenance project EE EE EE Normal Correction Urgent Correction Administration The selection menu for change types is shown in Figure 2.TransactionTypes/Workflows  2. Figure 2. Normal Correction/Development Activity). the term normal correction is replaced by the term development or development activity. the following change types are available: EE Implementation project. This change is made only for the purpose of greater clarity because these projects result in new developments rather than corrections. From a technical perspective. template project. When you select one of these actions in the action list of the change request. this corresponds to the Normal Correction transaction type (see Section 2.3.26 The Subject Field in a Change Request Once all of the required information has been entered in the change request.3 projects. an action to reject or authorize the request can be executed.26. To summarize. the status value is set 57 .

Normal Corrections. that is. However.2 ArchitectureofChangeRequestManagement accordingly. in the change document. If the change request is authorized. the user status Rejected is set automatically and the document is closed. the user status is set to Approved. no further activities can be executed in the change request. Change Request Management then searches for a project or maintenance cycle for the system specified in the change request. Administration. The transaction generated depends on the selection made in the Subject field. Figure 2.27 shows the action list for authorizing or rejecting a change request. Once all of these actions have been successfully executed. The Change Request Management process now continues in the follow-up transaction. As illustrated 58 . the system prompts you to select a project or maintenance cycle from a selection menu.27 Authorizing a Change Request If the change request is rejected. if several project or maintenance cycles exist for a system.3 Change Document Change document serves as an umbrella term for the transaction types for Urgent Corrections. No further changes can be made to the document as of this point. the status of the change request is set to Authorized.3. and Test Messages. additional activities are executed in the background. for example. Figure 2. it may be an urgent correction. If only one project or maintenance cycle exists for the system. First. In this case. 2. Once it has this status. a follow-up transaction is generated for the change request in the same way as for the activity between the Service Desk message and the change request. this is automatically assigned to the follow-up document.

3. Enhancements of the process and functions have given rise to the new version SDMJ. Change requests are used to document and organize requests.4 Normal Correction/Development Activity A normal correction. Most changes should be executed with this transaction type. meanwhile. which is the standard version now recommended and maintained by SAP. or upgrade product. and Administration message. it consists of all transaction types used for the technical implementation of a change request. Change Process Urgent Correction Service Desk Message Change Request Normal Correction Administration Test Message Figure 2. 2.3 in Figure 2. This is the initial version of this transaction. The focus here is on information gathering and documentation. which can still be used.TransactionTypes/Workflows 2. represents the typical process used for new or change implementations. followed by authorization or rejection of the request.28. Urgent Correction.28 Change Documents This clearly indicates once again the general division of the Change Request Management process into sub-processes. Because various processes can be used to implement a change. The technical name of the transaction type is SDMJ. you can choose here between the familiar transaction types Normal Correction. implement an approved change request. which is also referred to as a development activity as part of an implementation. Change Documents 59 . template. Change documents. The technical name SDMI indicates another transaction type called Normal Correction in SAP Solution Manager.

The change is automatically released in the development system and can then be imported into the quality assurance system. the mechanisms of the Transport Management System give rise to a situation where all test transports into the quality assurance system are also contained in the import buffer of the production system. and IT operator. to which the change will be added later. You can navigate directly from the Normal Correction document to the development system and implement the correction or development activity there. This transport request is imported only into the target system and not into the production system. During the course of a normal correction. the relevant transport request is released after the development activity is completed. Once the correction or development is ready for testing. If several transport requests are created in this way. As a result. the developer) can set the correction to In Development (see Figure 2. you can navigate directly from the 60 . see Section 4. and can then be imported into the quality assurance system. the developer may be forced to import the defective developments into the production system at the end of the cycle. where an integration test is subsequently performed during the test phase for the entire project. In version SDMI. Various users may be actively involved in a normal correction as part of the Change Request Management process. For detailed information about roles in Change Request Management. Changes can then be saved directly in the existing transport requests. If testing in the quality assurance system results in errors.29) and then generate transport requests in the development system. Roles and Activities. the original transport request remains in the development system until the correction has been tested successfully. these users (for example. the developer must create a new transport request in the development system and repeat the procedure. If the correction cannot be tested without errors by the time the project or maintenance cycle comes to an end.2 ArchitectureofChangeRequestManagement Differences Between SDMI and SDMJ The main difference between these two transaction types concerns the transfer of the correction from development to testing. Version SDMJ bypasses this problem because only one transport of copies is executed between the development and quality assurance systems.1. developer. Copies of the changes are therefore transported in a new transport request. The original transport request is only released after successful testing and can then be imported into the quality assurance system again. These are normally the change manager. After the development activities have been completed. the normal correction can be transferred to testing. tester.

the individual change documents can be completed by setting the user status from Consolidated to Production.TransactionTypes/Workflows  2. together with the import of all other change documents.29 Normal Correction If testing is unsuccessful. Technical Notes on Usage and Troubleshooting. Security in Change Request Management. Note For detailed technical information about the administration and use of Change Request Management. When all changes have been successfully imported into the production system. Figure 2. This can be done manually or with a report.3 Normal Correction document to the quality assurance system and conduct testing there. This status indicates that testing has been successful and enables an import of the change into the production system. Testing can then be evaluated as successful or unsuccessful in the normal correction. the status of the change document is reset to In Development. whereas successful testing changes the status to Consolidated. 61 . and Chapter 8. and should be executed by an IT operator. refer to Chapter 5. This import normally occurs at the end of the project or maintenance cycle.

template. any necessary improvements or corrections can be executed using a test message (see Section 2. To be Tested.7.2 ArchitectureofChangeRequestManagement The various user statuses that represent the individual steps involved in a normal correction are as follows: Created. These status values map the various steps in a normal correction.30 demonstrates that a normal correction can only be created and transported during the development phases of a project (implementation. transport requests can only be created centrally in the project task list at this point. and facilitate navigation. Production. Template. or upgrade project). Projects (Implementation. provide a general overview for users. However.3. Figures 2. and Withdrawn. Any necessary corrective action can still be implemented during the Test and Emergency Correction phases. This figure also shows that an import into the production system can only occur during the Go-Live phase. All corrections must be released or withdrawn in the development system when the project passes into the Test phase. In Development.31 show the activities that are possible in a Normal Correction document during the various phases of a project or maintenance cycle. Figure 2. Once the project has entered the Test phase.30 and 2.30 Project Phases and a Normal Correction 62 . Test Message). Consolidated. and Upgrade Project) In Development Finish Development Production Import Approval Normal Correction Request Release Phase Created Development without Release Development with Release Test Emergency Correction Go-Live Being Completed Completed O O O X X X X X X O O X X X X X X O O X X X X X X X O X X X X X X X O X X X X X Pass to Test X X O X X X X X X X X X X O X X Figure 2.

3 Figure 2. This prevents the transport of changes into the quality assurance system during the Test phase and therefore during the integration test. a normal correction can be created and edited at any stage. This means the task list can be used to create transport requests and transport these into the test system during the Test and Emergency 63 .31 shows a normal correction in a maintenance project. these corrections are integrated into the next cycle and can be transported into the production system as part of this cycle. Projects (Maintenance Project) In Development Finish Development Production Import Normal Correction Approval Request Release Phase Created Development without Release Development with Release Test Emergency Correction Go-Live Being Completed Completed O O O O O O X X X O O O O O X X X O O O O O X X X X O X X X X X X X O X X X X X Pass to Test X X O X X X X X X X X X X O X X Figure 2. once the maintenance reaches the Test phase.TransactionTypes/Workflows 2. The system behavior described here indicates the possible actions that can be executed in a normal correction document. In this case. Instead. However. normal corrections from the maintenance cycle can no longer be released from a document. The central task list of the maintenance cycle allows the IT operator or project lead to take corrective action.31 Maintenance Project Phases and a Normal Correction An export of a normal correction is only possible within the document during the Development with Release phase. any normal corrections created during this or subsequent phases are not part of the current maintenance cycle. Once the project reaches the Test phase.

and Withdrawn. transport requests are immediately generated after an urgent correction is set to In Development. In addition.2. In the Go-Live phase. It therefore gives you the option of transporting a change into the production system before the end of a maintenance cycle.32. an individual urgent correction can be transported into the production system within the document. The urgent correction. the phases of cycles determine the scope of permitted activities. particularly with regard to data consistency. Successfully Tested. the current phase of the cycle determines whether it is possible to release a normal correction or create a test message.3. This flexibility is due to the individual task list of an urgent correction. To be Tested. An urgent correction therefore has its own task list. In this way. where a large number of activities depend on the specific selections made by the user. As shown in Figure 2. which is only available in maintenance projects. 64 . which allows it to take effect independently of these restrictions. 2. Authorized for Import.5 Urgent Correction Urgent Correction. by contrast. is a transaction used when a change must be transported immediately into the target system. If changes of the normal correction. For example.2 ArchitectureofChangeRequestManagement Correction phases. which has the technical name SDHF. for example. In a normal correction. completed. However. Project Cycle and Task List. an urgent correction can be created but cannot be exported. Production. an IT operator executes this final step centrally for all corrections at the end of a project or maintenance cycle. it gives you the flexibility you need to implement essential corrections at the last minute. we will show that no problem occurs with this procedure. Note also that only the IT operator or project lead should be authorized to implement corrective action in this way. is a partly automated transaction. or administration type are executed in a project or maintenance cycle. Many activities are executed automatically in an urgent correction. In Development. Confirmed.4. As explained above in Section 2. normally only project or maintenance cycles have a task list. Later. test message. Urgent corrections may have the following user statuses: Created. an urgent correction can be created and changed at any stage up to the Emergency Correction phase. This is an option to be used in exceptional cases only. in contrast to a normal correction.

Therefore.3 Projects (Maintenance Project) In Development Release for Import into Production Approval Production Import Urgent Correction Request Release Phase Created Development without Release Development with Release Test Emergency Correction Go-Live Being Completed Completed O O O O O O X X X O O O O O X X X O O O O O X X X O O O O X X X Pass to Test X O O O O O X X X O O O O O X X X O O O O O X X Figure 2. at any point. The purpose of an administration message is to document these specific changes so that it is possible to track.TransactionTypes/Workflows 2.32 Maintenance Project Phases and an Urgent Correction 2. which users have made which changes to the system. as is the case in normal or urgent corrections. An administration message may have the following status values: Created. Confirmed. for example. quality assurance.3. Completed. changing number ranges or maintaining master data. 65 . an administration message is only ever of relevance to a selected system. In Process. rather than to the entire system group (development.6 Administration Message The administration message (technical name SDAD) is used to document activities that do not result in a transport request. and Withdrawn. an administration message offers the same functionality as a normal or urgent correction. In principle. You can navigate directly from an administration message to the relevant system and enter the relevant documentation in various text types. The only functions not available in an administration message are those relating to the Transport Management System. and production system).

2 ArchitectureofChangeRequestManagement Figure 2.33 Project Phases and an Administration Message 2.7 Test Message As already stated in Section 2.3. This transaction type (technical name SDTM) is created without reference to a change request. If this test is successful.33 shows the possible activities in an administration message in the various phases of the project cycle. Transaction Types/Workflows. the test message is completed. When the correction has been imported into the quality assurance system. the test message represents something of an exception. A tester can create a test message in Transaction TEST_CREATE during the integration test. Test messages are used for troubleshooting purposes during the integration test and can therefore only be created during the Test phase of a project or maintenance cycle. All Project Types In Development Administration Release for Import into Production Approval Request Release Phase Created Development without Release Development with Release Test Emergency Correction Go-Live Being Completed Completed O O O O O O X X X O O O X O O O O O O X X Pass to Test X O O O O O X X X X X X X X X Figure 2. the tester can conduct a new test to include the correction.3. there is no need for a change request in this case. The users involved in a test message are the developer and the tester. Because a test message refers to the correction of a change that has already been approved. 66 Production Import X X X . The developer can then create a corresponding correction in the development system and then transfer this to the tester for retesting.

and Withdrawn. Confirmed. As explained in Section 2. Corresponding job documentation is then edited and documented in a change document.8 Job Request If you already use the enhancement Job Scheduling Management with SAP Central Process Scheduling by Redwood.2. In Process. Project 67 .34.9 Change Transactions for Projects The change transactions for project cycles and maintenance cycles are mapped with transaction types SDDV and SDMN. a test message can only be created and changed during the Test phase of a project cycle. To be Retested.3 A test message may have the following user statuses: Created. A job request can be processed and approved as part of a change request.TransactionTypes/Workflows 2. as shown in Figure 2.34 Project Phases and a Test Message 2. you can also use it in conjunction with Change Request Management.4. All Project Types In Development Release for Import into Production Approval Production Import Test Message Request Release Phase Created Development without Release Development with Release Test Emergency Correction Go-Live Being Completed Completed O O O O O O X X X X O X X X O X X X X X X X O X X X X Pass to Test X X X O X X X X X X X X Figure 2.3. This gives you the option of using the Service Desk message to document a job request and to process changes to job documentation in Change Request Management. 2.3. Finally.

Emergency Correction. Test. 68 .4 Summary This chapter introduced you to the various elements of the Change Request Management functionality. Development without Release. project cycles. following the now familiar sequence of phase values: Created. The activities permitted during the various project phases can be deduced from the explanations provided above. regardless of project type. We will return again and again to these fundamental elements of Change Request Management and examine each in more detail over the course of this book. The change transaction of a project allows you to transition from one phase to the next. Development with Release.2 ArchitectureofChangeRequestManagement Cycle and Task List. Being Completed. Completed. The various transactions in Change Request Management were then described in detail. and Withdrawn. It explained how these fit into SAP Solution Manager as a whole and explained the Project Administration function and the concept of a project cycle. Go-Live. 2. consist of a generated task list and a change transaction.

153 profile. 146 Solution Directory. 59. 25 SOCM_PROCESS_ACTION. 137. 140 Action. 102 Business scenario. 171 Business process. 72 Basic setting action. 262 Business partner. 90 log. 18. 35 transaction type. 38 Attachment. 178 Change Management. 148 Administration message. 229 CRM_DNO_MONITOR. 134. 96 list. 70. 280 Application management. 99 consistency check. 56 Change Request Management. 99. 33. 76. 178 Change Request Management. 186 SOCM_CHECK_CONDITION. 100 BCOS_CUST. 129. 146 Administration. 25 Catalog. 185 object. 181 Build phase. 241 definition. 189 BC set. 64 Change Request Management. 130 Availability management ITIL. 257 ITIL. 183 user status. 175 Business Process Change Analyzer. 19. 144 Business process and interface monitoring work center. 52. 145 retrofit. 55 transaction type. 142 logical component. 94 transaction monitor. 22. 194 critical transport. 197 Browser. 61. 54. 119. 260 Business process monitoring. 136. 27 work center. 92 Categorization. 192. 173 Change advisory board. 112 Category. 191. 146 C Capacity management ITIL. 183 extended. 23. 140 Bill of material. 127 Authorization. 58 work center. 114 partner function. 96 task list. 111 Change Analysis. 252 BAdI enhancement action. 99 Basic configuration. 58. 82 Application log. 21 Approval. 167. 176. 175 B BAdI CRM_CUSTOMER_H_BADI. 65 Administrator authorization. 142. 239 CRM_ORDER_AUTH_CHECK. 113.Index A ABAP Dictionary object retrofit. 59. 261 Change document. 101. 22. 98. 97. 128. 156 Architecture. 171 role. 160 Activation cross-system object lock. 105 reporting. 76. 245 287 .

231 CRMC_MSGC. 148 business process. 29. 56. 179 Configuration management ITIL. 85. 60. 67. 225 configuration. 116 processing. 118. 154 Transport Management System. 136. 69. 134. 62. 90. 98 Change tracking. 108 retrofit. 136 Context.Index Change manager. 101 reporting. 113 Copy control. 111 project cycle. 74. 33. 29. 54. 92 group. 98 Configuration. 248 CRMC_MSGS. 267. 27 Configuration node IMG. 176. 159 Component configuration. 155 Critical transport object. 119 authorize. 187 Conflict scenario cross-system object lock. 91. 49. 48 normal. 149. 67. 72 Conflict analysis. 146 Control function change manager. 64 urgent. 105 Client copy. 272 Condition. 98 Check. 111 retrofit. 241 action profile. 131. 159 test transfer. 243 status value. 92 Completion task task list. 177. 98. 100 definition. 122 synchronization. 52. 64 process. 58. 59. 129 logical component. 113. 178 Change Request Management. 194 partner function. 72 extended. 243. 18. 97 consistency check. 87 CRMC_MAP. 45. 148 business process. 19. 146. 31 task list. 99 process. 50. 146. 105. 99. 24. 102. 248 288 . 59. 73. 16. 37. 192. 89 Consistency check. 56. 150 workbench. 47. 229. 35 request for change. 40. 101 Copying control. 162 project. 140 cProjects. 124. 103 process. 170 transaction type. 101. 59. 35. 56. 268 Client setting. 154 task list. 28. 18. 71 logical. 135 sample process. 120 creation. 52. 77 work center. 18 work center. 104. 113. 100 Condition editor action profile. 133 Change request. 139. 36 Check-out. 160 Check-in. 36 Check report. 103 RFC connection. 107. 159 type. 163 Change transaction. 55 change transaction. 162 Close coupling. 92 group profile. 90. 131. 141 management. 63 Change Request Management. 251 Correction action. 45. 117 hot news. 69. 20. 126 transaction type. 60 project administration. 30 reporting. 120. 50. 108 Client logical system. 62. 18. 54. 244. 215 Code. 120. 98. 117 partner function.

43. 22. 133 Transport Management System. 168 Customer. 102 Cutover. 219 system. 48 status. 40. 126 transport request. 124 Customizing distribution logical system. 128 Diagnostics root cause analysis. 66. 17 Execution option BC Set. 175 Dictionary object. 20. 171 Data consistency. 179 Customer-specific tab. 82 CTS Status switch project logistics. 160 number range. 207. 130 system. 60. 60. 204. 169 Event management. 209. 143 Error analysis. 160. 213 Downgrade. 223. 84 package. 137 Execution time action. 115. 41. 83. 77. 208 Domain link. 95 Default configuration. 278 Error solution ITIL. 57 E E-learning. 206 request. 225 distributed landscape. 217 transport domain. 64 Date profile. 79. 210 target system. 53 Customer namespace transaction type. 207 landscape. 114. 229 CRM_DNO_MONITOR. 163 project assignment. 186 CTS+. 26 ITIL. 228 Customizing global. 134 Display list transaction monitor. 49 project cycle. 142 material. 131. 263 Deploy service. 195 Dual-control concept. 77 user status. 153 Data collector. 52. 135 partner function. 208. 134. 221 Developer. 170. 239 CRM_ORDER_AUTH_CHECK. 134. 80 Double stack. 258 Enterprise Edition SAP Solution Manager. 126. 133 test message. 66 Development Change Request Management. 120. 143 Enhancement package. 73 Deploy phase. 207 Deploy Web Service. 99 289 . 24. 206 regional. 220 double stack landscapes. 217. 95 D Daily overview task list. 208 CTS project. 217. 80 ABAP. 71. 160 Document management cProjects. 213. 128 Duration type. 161. 112 sample process. 205 Cycle completion. 25 Evaluation criterion. 175 Document flow. 80. 95 Date type.Index CRM_CUSTOMER_H_BADI. 219 CTSDEPLOY. 91 Domain controller. 227 phase. 159. 95 Date rule. 122.

205 H Hot News. 67 Job request. 96 Flow logic. 67 work center. 277 subset. 17. 277 Inactive system. 62 Import authorization. 24 request for change. 202. 113 event management. 20 Incident management.Index Export check. 179 work center. 30. 16. 155. 35. 117. 72. 15. 26 work center. 66. 87 F Fast entry text administration. 115 project. 107 Implementation documentation. 115. 179. 175 Implementation project. 201 Functional tester. 268 Interface setting partner determination procedure. 207 Job documentation. 71 ICF. 20. 112 sample process. 52. 67 Job Scheduling Management. 60. 175 290 . 234 Follow-up document. 19 change request. 176 HP Quality Center. 18. 204. 82 error. 195 Instance profile. 55. 129. 143 lifecycle. 19 change manager. 133 Four-level system landscape. 19 monitoring. 18 IT operator. 26. 206 Global template. 180 I IBase. 16 ITIL V3. 40. 84 IMG project. 25 ITSM. 48. 42. 270 Incident Management. 18. 41. 84 Issue management. 63. 180 Interval number range. 91 change advisory board. 94 Internet service. 260 HTMLB. 18. 27. 141. 140. 17. 52 component. 132 Implementation and upgrades work center. 274 IT operator. 193 critical transport object. 175 Information predecessor/successor. 22 user status. 180 IMG activity. 15. 148 partner function. 15 J Java stack system. 73 number range. 50 Global customizing. 17. 41. 181 configuration. 115 G Gantt cProjects. 133 IT service continuity management. 39. 16. 71 IT Change Management. 57. 115. 20 ITIL. 130. 206 Global namespace. 130. 121. 180 Integration test.

204 Maintenance Optimizer. 108. 63. 234. 172 Organizational structure. 20. 31. 90. 42. 206 Navigation area work center. 84 O Object critical. 177 Maintenance unit reporting. 64. 272 logical system. 258 Maintenance cycle. 63. 159 retrofit. 104 global development. 176 Maintenance planning. 189 Logical component. 193. 69 Organizational unit. 206 regional. 162 reporting. 58. 46 SAP Solution Manager. 258 Maintenance project. 209 Note implementation.Index K Knowledge Warehouse. 48. 103 Logical system. 107. 178 Non-ABAP object. 170 transaction monitor. 40. 187 update. 87 Module. 160 completion. 49. 89 Lock information. 38. 163. 171 Object list. 103. 166 urgent correction. 134 Operations lifecycle. 173 M Maintenance activities. 267. 191 Object reporting reporting service. 157 Number range. 176 Lifecycle. 30. 16. 83 Organizational Management. 89. 194 critical transport object. 197 Object lock cross-system. 138 scheduling. 24 Optimization project. 190 scenario. 92 object. 87. 178 work center. 31 L Landscape component. 258 work center. 143 Modification. 48. 169 Change Request Management. 172 reporting. 36 Order attribute. 88 Object version. 195. 49. 188 information. 57. 186. 117 Maintenance documentation. 35. 61. 27 project cycle. 205 Layout transaction monitor. 33 Lock entry cross-system object lock. 258 Maintenance landscape. 208. 191. 139 number range. 163 extended configuration. 175 License management. 170 291 . 84 Maintenance transaction Maintenance Optimizer. 173. 84. 102. 21. 22 Optimization lifecycle. 201. 39. 106 Loose coupling. 235 Monitoring. 214 N Namespace global.

107. 180 Project Change Request Management. 165 Overview work center. 50. 138 Transport Management System. 235 Parallel phase landscape. 176 P Package. 129 Production manager. 195 Project landscape. 116 PBO. 162 SAP Solution Manager. 232 module. 113 Process. 133. 112 Production system. 151 control. 77 Profile generator. 64. 63. 128 partner function. 134. 26. 159 Project header reporting. 68 Project planning cProjects. 37 Project analysis. 167 Project monitor logistics. 175 Phase change. 64. 58. 201. 94. 149. 108. 112. 168 Project phase project cycle. 201. 22 Production user status. 238 flow logic. 203 work center. 30. 173 Partner determination procedure. 204 setup. 160 Phase landscape parallel. 30. 50 project cycle. 46. 82. 112 Process step. 148. 154. 137 system. 93. 130 Parameter transaction. 273 maintenance cycle. 68 Planning project logistics. 203 Phase value cProjects. 49. 17. 165 Project assignment. 203 Parallel system. 160 project cycle. 137 Profile parameter. 151 Controller. 108. 152. 202 Priority. 138. 61. 67. 66 complete. 275 Parallel system landscapes. 166 Project cycle. 151. 208 Postprocessing assignment. 227 PAI. 176 Project administration. 280 completion. 139 Preparation configuration. 116 partner function. 27. 143 Processor current. 234 Personalization filter work center. 156 retrofit. 28.Index Overtaker. 102 parallel. 62. 160. 91 Project status switch CTS project. 40. 150. 44 292 . 232. 163 Project category scheduling. 234 module. 46. 134 Project lead. 116. 34. 94 Partner function. 271 two-level. 61. 168 Port CTSDEPLOY. 170 Project intersection. 178 transaction monitor. 69 Preproduction system. 203 Parallel project. 173 Problem management. 273 administration message. 163. 68. 116 Process documentation. 147 Project logistics.

134. 204 function. 177 Report on side-effects. 135. 139. 177 Reporting. 111 cross-system object lock. 155 work center. 31 SAP Solution Manager. 215. 28 service. 18 Result list reporting. 259 SAP EarlyWatch Alert. 130. 137 process. 118. 105. 27 Repair flag. 201 SAP Basis. 178. 261 Quality manager. 40 SAP NetWeaver Application Server. 258. 158 configuration. 180. 179. 223 SAP note. 136. 131 partner function. 89 type. 130 object. 215 SAP NetWeaver Process Integration. 104. 175 S Safeguarding project. 60. 262 Quality Management. 263 Query work center. 170 Retrofit. 114 Release package. 112. 49. 133 Request for change change request. 80. 51 SAP Download Manager. 125 Request analysis change tracking. 17. 88 solution-independent. 134. 168 Project type. 75 Role. 274 Report work center. 23. 63. 104 293 . 263 Quality Gate Management. 135. 137. 179 for HTML. 81. 137. 39 Q Quality assurance system. 165 Requester. 24. 206 Regression test. 138 system. 111 sample process. 258 Release manager. 176 R Regional customizing. 23. 25 SAP GUI. 81. 178. 76 Root cause analysis. 284 SAP product system landscape maintenance. 200 Release. 133 Sandbox system. 169 Change Request Management. 104 configuration. 128. 40 SAP Business Workflow. 261 phases. 138 Release landscape. 174 Change Request Management. 206 Regional namespace. 138 RFC connection. 35. 215 SAP NetWeaver Portal. 89. 87. 216. 75 RFC destination.Index Project structure logistics. 260 Request own. 71 SAP NetWeaver Business Warehouse transport. 178. 21 SAP NetWeaver. 179 SAP infrastructure. 179 Role maintenance work center. 276 SAP NetWeaver Development Infrastructure. 27. 133 Quality gate. 36 Sample process. 156. 201 Release management. 181 setting.

245 SOCM_PROCESS_ACTION. 169 root cause analysis. 35 configuration. 59. 165 Service delivery work center. 22 ITIL. 283 SAP Transport Management. 175 Service Desk. 20 lifecycle. 24 Service process monitor. 117 employee. 235 Security Guide. 25. 37. 78 SMSY_SETUP. 166 solution monitoring. 86 task list. 164 Sold-to party. 73 Side effect. 133 SAP Solution Manager. 168 task. 23 Service-level management. 170 service level. 23. 34 workflow. 116 SAP variant task list. 175 Solution monitoring. 30. 18 Standard profile configuration. 142 Software Lifecycle Manager. 24 reporting. 118 Setting scenario-specific. 175 application. 54. 23. 23 Source system. 146. 28. 165 project logistics. 21 operations. 46. 52. 117. 153 Scope phase. 26 reporting. 167 Satellite system Transport Management System. 56. 53 transaction type. 53. 179 Diagnostics. 23 Solution reporting. 71 change request. 143. 67 partner function. 171 transaction monitor. 22. 136 SPPFCADM. 55. 259 Software status change tracking. 138 Split screen editor. 72. 142. 22 optimization. 47 Scheduling. 27. 92 Start condition action profile. 97 Schedule Manager. 253 Stakeholder. 260 Single transport transport strategy. 23 task list. 141 CRM. 113 message. 144. 97 294 . 51. 117 application management. 143 implementation. 72 SAP Solution Manager. 170 Solution Directory. 116.Index SAP Service Marketplace. 25 Service-level reporting. 58. 23 scheduling. 111 sample process. 112 Solution database. 171 Sequence violation overtaker. 147. 171. 35. 183 Selection criterion. 262 Screen control. 257 Solution landscape and operations setup work center. 261 enterprise edition. 52 Service level. 272 SOCM_CHECK_CONDITION. 107. 23 Service lifecycle. 29 SAP support organization. 166 analysis. 21 change document. 85. 252 Software lifecycle. 118 partner function. 53 SAPSYS. 76 Schedule condition action profile. 173 Service process transaction. 40. 206 SAP Tutor. 29.

55 transaction monitor. 102. 205 global. 153 number range. 150 Template. 270 logical. 162 project logistics. 149 Task release. 70 four-level. 269 295 . 175 System analysis. 142. 228 Table BCOS_CUST. 90. 57 Template report task list. 168 System comparison. 144 Subject. 163 change tracking. 262 plan management. 108 lock. 156 System monitoring. 24. 98 profile. 127 transport. 172 Status display retrofit. 106 parallel. 128 phase. 154. 114 Structure element. 152. 195. 151 Status value administration message. 201 maintenance. 150 Template project. 203 System landscape maintenance IBase. 48 test case. 173 Support Desk logical component. 64. 134 SMSY. 269. 84 Schedule Manager. 23 work center. 158 System add. 269 user status. 154 project cycle. 37 project administration. 103 Support package. 267 inactive. 199. 271 System administration. 55. 38. 86 Test management. 41 configuration. 175 System role. 162. 149. 50. 39. 142. 71 System logon. 205 task list. 275 virtual. 34 creation. 103. 139 three-level. 126 Task list. 134. 120 profile. 129 Test Data Migration Server. 139 Change Request Management. 155 task list. 94 Status switch. 170 System ID. 34. 42. 148. 270 System copy. 164 System change option. 37 retrofit. 139. 65 status profile. 143 test instructions. 102 System landscape. 92 Subject area. 56. 163 extended configuration. 258 import. 260 person. 94 Status property. 172 Steering committee change advisory board. 139 logical component. 189 Target system. 23 work center. 30. 86. 94 Status profile. 48. 138.Index Status transaction monitor. 135 Status management. 47 urgent correction. 268 Change Request Management. 268 System data reporting. 106 T Tab customer-specific. 35.

77 Transport strategy. 208. 278 TMWFLOW/CMSCONF. 78 Trusted RFC authorization. 172 my team(s). 155 task list. 59. 172 Transaction type. 122. 133 Test message. 193 TMWFLOW/LOCKMON. 171 extension. 171 Transport routes Transport Management System. 87. 283 U Unit test. 82 configuration. 131 creation. 95 Customizing. 76. 66 Change Request Management. 77. 66 Test Workbench. 48. 189 Track task list. 91. 155 Transport object critical. 82 registration. 95 history. 278 TMWFLOW/CMSCONF. 77 configuration. 57. 239 my department. 156 Tracking project logistics. 189 Transaction data reporting. 202 Upgrade project. 80. 210 import monitor. 168 Transaction CRMC_MAP. 81 configuration. 36. 79. 271 log. 149. 96 determination procedure. 115 functional. 39. 90. 199 Transport Management enhanced. 231 CRMC_MSGC. 193 TMWFLOW/LOCKMON. 248 SMSY_SETUP. 275 route. 95 Transaction monitor. 64. 260 Text administration. 96 Three-level system landscape. 60. 60. 111 296 . 283 connection. 155 authorization. 81 alert monitor. 243. 222 task. 190. 95 Transport check. 146 date profile. 244. 60. 115 partner function. 65. 253 TMWFLOW/CHARMCHK. 185 TMWFLOW/CHARMCHK. 51. 248 CRMC_MSGS. 156 import. 272 SPPFCADM. 70 Transport domain. 171 Transport Organizer Web UI. 204 Use Change Request Management. 30. 124 object.Index Tester. 79. 229. 210. 60. 70 Transport landscape extended. 199. 158 copy. 190. 158 reporting. 158 directory. 206 Transport Management System. 185 Trusted service. 78 Transport Management System. 155 release. 220 Transport request. 96 text type. 170 Transaction header text administration. 158 project assignment. 134. 71. 112 sample process. 121. 160 Transport control. 213. 209 history. 203 TMSADM. 52 transaction type. 191 reporting. 195. 52.

94 test message. 277 SAP1. 132 status profile. 53. 29 V Validating and Testing. 64. 136 request. 179 Workflow. 126 transport request. 51 Change Request Management. 215 W Workbench object. 275 Virtual system. 116 User status. 131 Confirmed. 118. 76. 117. 283 User group partner function. 121. 278 task list. 175. 131. 27 Variant SAP0. 67 Versioning. 128 Completed. 269. 127. 124 Work Center. 111. 85 297 .Index User SAPSYS. 55. 121. 271 Visual Administrator.

Sign up to vote on this title
UsefulNot useful