90317151 Charm Config

Change Requst management configurationFirst creat three clients as existing system landscap

DEV:100 -->QUA:200 -->PRD:300

Configure STMS

In Standard Transport Layer tab: ensure you enter the client 100, (client with customizing role for the development box,

Create the consolidation transport routes to SMM:200,

From development system to quality system you need at least two consolidation routes, SAP and ZXXX.

create the Delivery transport route from SMM:200 to SMM:300, delivery routes are always from quality to Production systems.

RFC connections from Solution Manager to DEV, QUA and PRD system, don’t forget to create also SM_..._TMW connection to all satellites DEV, QUA and PRD, to clients with customizing, test and production roles, in our example, we will create the RFC connection to 100, 200 and 300. .In transaction SMSY:

Create a maintenance project to use SOLAR_PROJECT_ADMIN

In SPRO go to Scenario-Specific Settings-->Change Management -->Change Request Management -->Standard Configuration --> General Activities

2.1. Run “Activate Integration with Change Request Management”After this check in SM30 that view BCOS_CUST has the following entries:CHARM W NONE CUST620 1.0CHARM_DEST W NONE CUST620 1.0This means that Charm configuration has been done in this client.

2.2. Activate BC Sets: Check note 903527Bc Set for Charm: SOLMAN40_CHARM_BASICFUNC_001

In Change Request tab: Select “Activate Change Request Management”Select Create Task List

Note: Choose Lock/Unlock Grroup/Subsequent Groups to unlock the tasks in the task list.If all is working correctly a Task List and a Maintenance transaction type (called Service Desk Transaction) is being created.

Activate Domain LinksUse

In this IMG activity, you define inter-domain links.If multiple transport domains are used and projects in the Solution Manager have been defined as cross-domain projects, you must define inter-domain links between the transport domains, regardless of whether change requests are moved between domains or not. If, for example, the Change Request Management system is in domain A , but the satellite systems between which requests are transported is in domain B, Change Request Management has to trigger transports in a foreign domain. This is only possible by means of domain links

In the transport tracks where the software distribution is controlled by Change Request Management, you must deactivate the QA approval procedure in the TMS, since this procedure is incompatible with the approval procedure in Change Request Management. Additionally, you have to activate the "Single transports" strategy. This prevents you from accidentally executing "Import All". All transports within the system landscape of Change Request Management must be processed by project imports.

Activate Extended Transport ControlUseIn this IMG activity, you activate extended transport control in the Transport Management System. For more information, see the online documentation in transaction STMS by choosing Help -> Application Help.Activities1. Call transaction STMS.2. Choose Overview -> Systems.3. Double-click each system.4. The Display TMS Configuration: System <system ID> screen appears.5. Select the Transport Tool tab page.6. If the entry CTC does not appear in the Parameters column, enter it there, and then in the Value column, enter 1.7. Save your entries.

Generate RFC Destinations to Client 000UseSince Change Request Management reads important information about the system landscape (such as the transport routes) from the individual domain controllers, you must make sure that you generate RFC destinations from the Change Request Management system to client 000 of all domain controllers in the system landscape.






Set Project Assignment of Requests as MandatoryUseFor each system where you want transport requests to be created, you have to set the project assignment of requests as mandatory.Note that if you set the project assignment of requests as mandatory, you cannot release transport requests without projects. In a transition period during which projects are set up, it may be necessary to create dummy projects so that developments that were made prior to the availability of Change Request Management can still be transported.RequirementsAt least one project has been activated for Change Request Management in transaction SOLAR_PROJECT_ADMIN.If this is not yet the case, perform this IMG activity at a later stage.Activities

1. Call transaction /TMWFLOW/CMSCONF.2. Check the entries in the Proj. Assignment column.3. If you need to change an entry for a system, double-click the entry.

Maintain Number RangesUseIn this IMG activity, you maintain number ranges for Change Request Management.Activities1. Specify the object /tmwflow/m.2. Choose Number Ranges.3. Choose Change Intervals and then Insert Interval.4. For the new interval, enter 01, and use the F4 Help function to select a value for the From Number field.The system returns 000000001 to 999999999.5. Choose Insert, and then Save.6. Repeat steps 1 through 5 for the number range objects /tmwflow/d and /tmwflow/v.

Check Installation ActivitiesUseMake sure that you have performed the iBase IMG acitivities before you proceed with the Change Transaction IMG activities: SAP Solution Manager -> Basic Settings -> SAP Solution Manager System -> Service Desk -> iBase.

Create Business Partner Using Transaction BP_GEN1. Choose User list -> Add system.2. Select a system from which you want to create business partners.3. Select users.4. Choose Edit -> Create Business Partner.5. Confirm your entries.




Check Assignment of Action ProfileUseIf you want to enable users to create change requests directly from a Service Desk Message, you have to choose an action profile for the transaction type that you use in the Service Desk. In this IMG activity, you check the assignment of the action profile to the standard transaction type SLFN.RequirementsYou use the standard transaction type SLFN.Activities1. Select the transaction type SLFN.2. Check whether the action profile SLFN0001_ADVANCED has been assigned to the transaction type SLFN. If not, do so now.

Define Action Profile for Service DeskUseIf you want to enable users to create change requests directly from a Service Desk Message, you have to choose an action profile for the transaction type that you use in the Service Desk.In this IMG activity, you choose an action profile for the standard transaction type SLF1.If you use the standard transaction type SLFN, see Check Assignment of Action Profile.RequirementsYou use the standard transaction type SLF1.Activities1. Double-click the action profile SMSD_SERVICE_ORDER_DNO.2. Choose Action Definitions.3. Create a new action definition that has the properties Executable in Dialog and Display in Toolbox.4. Enter a technical name and short text of your choice.5. Make sure that the sort number of the new entry is as high as possible so that the action is displayed at the bottom of the dialog.6. For the processing type, select the method call SOCM_COPY_DOCUMENT.7. Save the action definition.8. Navigate to the Transportable Start Conditions on the initial screen of transaction SPPFCADM.9. Schedule the new action that you just created.



PurposeYou use this process to create a maintenance cycle for your regular and urgent corrections. You can also apply this process to test messages and administration tasks.Process Flow 1. A user creates a maintenance cycle. When the cycle is created, its status is Created. Urgent corrections and regular corrections can only be created as change transactions. Their status also has to remain as Created until the corresponding task list has been activated by the administrator. 2. The change manager sets the status of the maintenance cycle to Development wo Release. When this status is set, corrections can be developed, and transport requests and transport tasks can be created. Exports, however, are not permitted (except in the case of urgent corrections). Urgent corrections are permitted in every phase except for the Go Live phase. 3. If the change manager switches the status of the maintenance cycle from Development wo Release to Development w Release, transport requests can be released from within a regular correction. The administrator uses the task list to import all released corrections into test systems. 4. If any regular corrections exist whose status has not yet been set to Tested Successfully when the maintenance cycle phase is changed from Development w Release to Test, the system issues a warning. These corrections are then excluded from the integration test and cannot be released. 5. During the test phase, errors are detected in the test systems, and are reported to the relevant developers by means of test messages. The developers correct these errors. If all error messages have been closed, the maintenance cycle proceeds to the emergency correction phase. 6. If changes still have to be made after the test phase has been completed, transport requests and tasks can be created and released as part of the Emergency Correction phase, but only by using the task list of the Schedule Manager. 7. The Go-Live phase is reserved for importing the entire project buffer into the production system. Neither transport requests nor urgent corrections can be released during this phase. 8. If there are still any open transport requests, you have to return to the Development w Release phase and repeat the process including the test phase to ensure that any open requests can be released and transported. 9. If there are no open transport requests, you can close the maintenance cycle by setting the status to To be closed. You can subsequently create a new maintenance cycle.

Workflow for Regular Corrections

You use this process to make regular corrections in your maintenance landscape and to implement features in your development landscape. Process A user detects a problem in a system.The user (requester) creates a Support Message and documents the problem in this message.A change request is generated in the Service Desk.The change request is assigned to a change manager, who decides to approve or reject the change request (using the transaction CRMD_ORDER). The change manager assigns the change request to a developer.If the change request is approved and the subject is set accordingly, a change transaction of the type Regular Correction will be generated.The change document is forwarded to the designated developer, who sets the status to In Development (using the transaction CRM_DNO_MONITOR).The developer creates a transport request in the development system by means of an action in the change document ( Actions Create Transport Request ).The developer logs on to the development system directly ( Actions System Logon ).When the correction has been developed, the developer releases his task in the transport request in the development system. This is done by calling transaction SE09.The transport request is released by the IT Operator from within the Schedule Manager (transaction SCMA).If the purpose of the change request has been fulfilled and all the corresponding transport requests have been released, the developer sets the status to Correction Completed.An IT operator calls transaction CRM_DNO_MONITOR, selects the change order, and opens the related task list ( Actions Go to Task List ). The IT operator imports the transport request with the task manager into the Quality Assurance System, for example. Select the method Import Transport Request (Background), then click Schedule in the context menu.A tester (or another developer with a test user role) logs on to the SAP Solution Manager system and checks whether or not there are documents assigned to him. The tester selects the change order and performs the testing.If the test was successful, the tester sets the status of the change document to Actions Confirm Successful Test to indicate that the new function has been tested and can be imported into the production system. If the test was not successful, the tester sets the status of the transaction to Actions Reset Status to 'In Development' .The tested change transaction is forwarded to its developer. In case of a successful test, he sets the status to Complete Development (using the transaction code CRM_DNO_MONITOR Actions Complete Development ). In case the test was not successful, this workflow is repeated from step 7 on.An IT operator calls transaction CRM_DNO_MONITOR, selects the corresponding document, and opens the related task list in the document Normal Correction ( Actions Go to Task List ).The IT operator imports the transport request into the Production System. Within the Solution Manager (SCMA), the operator executes the method Import Transport Request (Background).Go back to the change request document (press F3) and execute Actions Set Production Status .Go back to the task list ( Actions Go To Task List ) and click the Phase pushbutton. Switch to Change mode in the dialog box and set the task list phase to Go Live. Return to the node of the Production System by selecting the method Import Transport Request, then click Execute in the context menu.The status can only be set to Production Status when the regular correction has been imported into the production system along with all the other regular corrections that belong to the maintenance cycle. You can choose to set this status for all imported regular corrections at the end of a maintenance instance by scheduling the batch job CRM_SOCM_SERVICE_REPORT.

Workflow for Urgent Corrections

You use this process to make an urgent correction in your production system. This transaction is only permitted within a maintenance landscape. Process A problem is detected by an end user in a system.The user (requester) creates a Support Message and documents the problem in this messageA change request is generated in the Service Desk.The change request is assigned to a change manager, who decides to approve or reject the change request (using the transaction CRMD_ORDER). The change manager assigns the change request to a developer.If the change request is approved and the subject is set accordingly, a change transaction of the type Urgent Correction is generated.The change document is forwarded to the designated developer, who sets the status to In Development (using the transaction CRM_DNO_MONITOR).Simultaneously, a specific urgent correction task list containing the necessary tasks to execute the urgent correction is generated in the background in the Schedule Manager.The developer logs on to the development system directly ( Actions System Logon ).The developer makes the urgent correction in the assigned development system and releases his task in the transport request in the development system. This is done by calling transaction SE09.An IT operator calls transaction CRM_DNO_MONITOR, selects the urgent correction, and forwards the urgent correction to testing ( Actions Pass Correction To Test ).The Pass Correction To Test from the previous step creates a transport request. The developer now releases the transport request. Note that no Transport of copies transport request is created as in the Normal Correction scenario.The IT operator imports the transport request into the Quality Assurance System. The change document is now in status To be tested.The tester (or another developer with a test user role) logs on to the designated test system to check whether or not the urgent correction works.If the correction contains no errors, the tester sets the status of the change transaction to Actions Confirm Successful Test . The change manager can now change the status of the urgent correction to Released for Production and forwards the change transaction to an IT operator.If errors occurred during testing, the tester returns the change transaction to the developer so that the urgent correction can be changed. This new correction has to be tested again.The change manager approves the urgent correction for import into the production system and forwards the change transaction to an IT operator.The operator imports the urgent correction into the production system and sets the status of the urgent correction to Productive.The requester (or the tester, or the change manager) confirms that the correction has been made by setting the status of the change request to Complete Correction. In situations where the landscape is complex, the transport request for the urgent correction needs to be transported to training and other systems. The administrator needs to use the task list of the urgent correction document to import the transport requests to other systems. If the correction is marked “Complete”, the administrator will no longer be able to import the transport requests to other systems in the landscape.After the transport request of the urgent correction document is imported to the QA and production systems, the transport request remains in the import buffer so that the changes are not overwritten by other transport requests in the normal correction cycle. If you want to set multiple change transactions to the next status (from "Approved for Import" to "Productive", for example), execute the batch job CRM_SOCM_SERVICE_REPORT.

In addition to the tasklist for the whole project, there is a separate task list for the urgent correction. These two task lists are independent from each other. The SAP basis component can use the task list for the urgent correction to import the transport requests to other systems in a complex landscape (please note that the urgent correction process fast tracks the import of transport requests to QA and to production systems without looking into other systems in the landscape) The task list always represents the transport track and will include all systems configured in TMS.











Making User Settings for Change Request Management (SAP Library - Change Request Management)

UseBefore you start to use the Service Desk for the Change Request Management scenario, you may want to make some personal settings.Procedure 1. Call transaction CRMD_ORDER. 2. Choose with the quick info text Settings. 3. Select the Specific tab page. 4. Make the following entries:In the Pushbutton 1 field, enter SDCR.In the Pushbutton 2 field, enter SDTM.In the Pushbutton 3 field, enter SLFN. 5. Select the ObjctServices tab page. 6. Select everything except for Actions. 7. Save your entries.



All change requests and change documents are displayed as worklists. Depending on user authorizations, these worklists can be accessed by using the following transactions:Transaction CodeMenu Path on SAP Easy Access ScreenS_SMC_47000018 Requests for Change →Change Requests Created by MeS_SMC_47000019 Requests for Change →My Non-Completed Change RequestsS_SMC_47000020 Requests for Change →Non-Completed Change RequestsS_SMC_47000021 Documents for Change →Change Documents Created by MeS_SMC_47000022 Documents for Change →Change Documents to be Processed by MeS_SMC_47000023 Documents for Change →Change Documents to be ProcessedS_SMC_47000024 Documents for Change →Change Docs. To Be Proc. w/o PrcssrYou can open any change request or change document by double-clicking it in the relevant worklist. The system then opens the request or document in the Service Desk (transaction CRMD_ORDER).

Creating a Change Request

UseA problem has been detected in a system. No support message has been created, but you want to create a change request anyway.PrerequisitesYou have been assigned the SAP_CM_REQUESTER role.Procedure 1. Call transaction CRMD_ORDER. 2. Choose Change Request. If this pushbutton is not visible, see Making User Settings for Change Request Management. 3. Make an entry in the following fields: a. Description b. Sold-to Party c. Requester d. IBase component (which you defined in Customizing for SAP Solution Manager → Basic Settings →SAP Solution Manager System →Service Desk →iBase) 4. In the Subject field, select Urgent Correction, for example. 5. In the lower right-hand screen area, select Change Description in the dropdown list box. 6. Enter a description of the change that you want to be implemented. 7. On the Context tab page, optionally enter additional information (see Adding/Changing Context Information). 8. In the Change Manager field, enter the Business Partner (user) of the change manager who is responsible for approving or rejecting the change request. 9. Choose Save.ResultA change request has been created and assigned to a change manager for approval. The status of the change request is To Be Approved.

The system sets the status of the change request to Approved. A change document of the corresponding type has been created in the background. You can navigate to this document by choosing Document Flow.




Troubleshooting (SAP Library - Change Request Management)

If a change transaction has a red or yellow icon on the Service Desk interface, the transaction contains errors and cannot be processed until you remove the cause of the errors.If you click the red or yellow icon with the quick info text Display/Close Messages, the system displays the corresponding error messages.There are four error types:• A status is incorrect (inconsistent), which means that the subsequent action cannot be performed.• The system rejects a status change.• An action cannot be performed in the current phase of the maintenance cycle• An unexpected technical exception was triggered.The first three types of error can be resolved by system users; the fourth type has to be analyzed by a system administrator.Type 1: There is at least one error message (red icon). The subsequent action cannot be selected. You may have to perform a specific action in the maintenance landscape (release a task, for example). If this action can be performed directly, you see an entry in the Action exists column (next to the message text). You can perform the action by double-clicking the message. After you have performed the action, save the change transaction. The system checks the status again and the change transaction no longer contains any errors. If there is no entry in the Action exists column, choose Actions → Recheck Correction in the toolbar.Type 2: Only warning messages exist. One message indicates that the current status was set by the system due to a possible error. The other warnings explain the error itself. Since no actual error exists as far as the status set by the system is concerned, the subsequent action can be performed.Type 3: There is at least one error message (red icon) indicating that an action cannot be processed in the current phase of the maintenance cycle. The subsequent action cannot be selected. No action can be performed by double-clicking the message. Choose Actions → Recheck Correction in the toolbar. The system checks the current status of the change transaction and deletes the error message if the system determines that the current status is consistent. Subsequently, the change transaction can be processed as soon as the phase of the maintenance cycle has changed accordingly.In many cases, the long text of the message provides additional information about the cause of the problem and how to solve it. The application log in the task list provides additional information if the error was caused by a task not being executed completely or correctly.Sometimes the system displays an error because certain asynchronous processes have not been completed yet. If you want to check whether an action was completed successfully, check the task list. You can do this by choosing Actions → Go To Task List. If all processes have been completed in the task list, navigate back to the change transaction and save it again. The system checks the status again and the change transaction no longer contains any errors.The function Actions → Recheck Correction is always available; even if an error has been corrected, the error message does not always disappear (especially if you used the task list to correct the error).If you cannot resolve an error, make sure that you run the report SOCM_CRM_SERVICE_CHECK, which checks important configuration prerequisites.



Making Manual Changes to a Task List (SAP Library - Change Request Management

The task lists that are used as part of Change Request Management are always generated by the system at your request. When task lists are generated, the settings for the project in SAP Solution Manager (such as system role type, system roles, and logical systems) are taken into consideration. The tasks that are generated for each system depending on the system role type are provided by SAP in the form of Customizing. If necessary, you can change the Customizing settings in the IMG under the following paths:SAP Solution Manager → Scenario-Specific Settings → Change Request Management → Extended Configuration → Schedule Manager → Define Additional Tasks for Task ListsSAP Solution Manager → Scenario-Specific Settings → Change Request Management → Extended Configuration → Schedule Manager → Create Customer-Specific Header and Footer TasksIf you make changes in the Solution Manager project or in the IMG, these changes apply to all new task lists that are generated from then on.If you have to make changes to an existing task list, there are certain constraints involved; however, these changes affect one task list only, and do not affect any future or other existing task lists.If you need to delete tasks and task groups in a task list, you can do so by using the secondary mouse button. You can also add tasks to a task list by using the secondary mouse button. You may want to add a task to the header or footer of the task list or for a system, for example. In these cases, certain program parameters are are generated in the background. To develop your own task, you require the template report /TMWFLOW/SCMA_REPORT_TEMPLATE. You can copy this report into your namespace and adjust it to suit your needs. The report ensures that you can see the correct status, job log, and spool list in the task list, and also entries in the application log.Another example of when this procedure could be used is if you need to add a whole system with all corresponding tasks to a task list. For urgent corrections, for example, only those systems would appear in the task list that are actually required for transporting a transport request from the maintenance system to the production system by the quickest route possible. If you want to add another system (a test system or a training system, for example), that is also specified in the maintenance project of SAP Solution Managers but that has not been included in the task list, you have to choose Add System. You cannot choose which system to insert where in a task list; you have to use the F4 Help to select a system that actually exists for the corresponding project in SAP Solution Manager, and then this system is automatically inserted into the task list in the correct place. Simultaneously, information that is required by the system for running the corresponding programs is generated in the background. If the system contains a background program as a task, a variant that does not actually exist is displayed initially (DUMMY). Only when you save the task list does the system create a correct variant with a generated name.Since certain information that is required for running the programs for each task and task group is stored in the system, some of the standard functions of the Schedule Manager for Change Request Management are then no longer available. The following constraints apply:You can move a task within a task group, but you cannot move it to a different task group or hierarchy level.You cannot create a general task group (except a task group for a system as described above).You cannot copy and paste tasks and task groups.



In Standard Transport Layer tab: ensure you enter the client 100, (client with customizing role for the development box,

create the Delivery transport route from SMM:200 to SMM:300, delivery routes are always from quality to Production systems.

RFC connections from Solution Manager to DEV, QUA and PRD system, don’t forget to create also SM_..._TMW connection to all satellites DEV, QUA and PRD, to clients with customizing, test and production roles, in our example, we will create the RFC connection to 100, 200 and 300. .In transaction SMSY:

In SPRO go to Scenario-Specific Settings-->Change Management -->Change Request Management -->Standard Configuration --> General Activities

2.1. Run “Activate Integration with Change Request Management”After this check in SM30 that view BCOS_CUST has the following entries:CHARM W NONE CUST620 1.0CHARM_DEST W NONE CUST620 1.0This means that Charm configuration has been done in this client.

2.2. Activate BC Sets: Check note 903527Bc Set for Charm: SOLMAN40_CHARM_BASICFUNC_001

In Change Request tab: Select “Activate Change Request Management”Select Create Task List

Note: Choose Lock/Unlock Grroup/Subsequent Groups to unlock the tasks in the task list.If all is working correctly a Task List and a Maintenance transaction type (called Service Desk Transaction) is being created.











Set Project Assignment of Requests as MandatoryUseFor each system where you want transport requests to be created, you have to set the project assignment of requests as mandatory.Note that if you set the project assignment of requests as mandatory, you cannot release transport requests without projects. In a transition period during which projects are set up, it may be necessary to create dummy projects so that developments that were made prior to the availability of Change Request Management can still be transported.RequirementsAt least one project has been activated for Change Request Management in transaction SOLAR_PROJECT_ADMIN.If this is not yet the case, perform this IMG activity at a later stage.Activities

1. Call transaction /TMWFLOW/CMSCONF.2. Check the entries in the Proj. Assignment column.3. If you need to change an entry for a system, double-click the entry.





























































