change request management (charm) - upgrade guide 7.0 to 7.1

1/19/2014 Change Request Management (ChaRM) - Upgrade Guide 7.0 to 7.1 - SAP IT Service Management on SAP Solution Manager - SCN Wiki

http://wiki.scn.sap.com/wiki/display/SAPITSM/Change+Request+Management+(ChaRM)+-+Upgrade+Guide+7.0+to+7.1 1/18

Getting Started Newsletters Store

Search the Community

Welcome, Guest Login Register

Products Services & Support About SCN Downloads

Industries Training & Education Partnership Developer Center

Lines of Business University Alliances Events & Webinars Innovation

Added by Tobias Hauk, last edited by Mariana Sebikova on Oct 17, 2013

SAP IT Service Management on SAP Solution Manager / ITSM Wiki - IT Service Management and ChaRM Wiki Homepage/ Configuration and Administration of ITSM

Change Request Management (ChaRM) - Upgrade Guide 7.0 to 7.1

1. UPGRADE

1.1 Overview

1.1.1 Transition phase

1.1.2 Upgrade Roadmap

1.2 Options to take over open transactions

1.3 Configuration Comparison (7.0 <> 7.1)

1.3.1 Overview Status Profiles

1.3.2 Overview CRM PPF Actions

1.3.3 Overview ChaRM-Actions

1.3.4 Overview CRM PPF-Conditions

1.3.5 Overview ChaRM-Conditions

1.3.6 BadIs in Change Request Management

1.3.7 Searching old transaction types in Web Client

1.3.8 Copy Control

1.3.9 Categorization & Subject Profile

1.3.10 Customizing Approval Settings

1.3.11 Remote Connectivity for Managed Systems

1.3.12 Migration of Customer specific fields

1. UPGRADE

This chapter informs you about the configuration steps you should perform in case of an upgrade from SAP Solution Manager 7.0 to SAP Solution Manager 7.1. Furthermore, it provides an overview of

upgrade strategies and best practices for the transition phase.

1.1 Overview

With the new release of SAP Solution Manager a lot of new functionalities have been implemented for Change Request Management. One of the most important changes is the new user interface w hich is

based on the SAP Web Client.

Due to this new user interface a lot of the existing Change Request Management functionalities had to be adapted to w ork correctly in the new environment. Therefore new transaction types have been

created. Those transaction types are only w orking on the new user interface, w hereas all the old transaction types are only w orking in the former SAP GUI user interface.

The search functionalities for Change Transactions and Requests for Change in the Web Client UI are capable of displaying both: old and new documents. This means you are able to have one common

result list, containing old and new documents. Based on the selection of the user, either the new or the old user interface w ill display the content of the selected document.

Some highlights of Change Request Management functionalities in 7.1 are:

New w eb based user interface w hich is highly configurable, easy to extend and provides a common environment for the entire IT Service Management functionalities – from common search

infrastructure to transaction processing

Multiple approval procedures, that can easily be customized and assigned to different Request for Changes, either manually or automatically based on f ield-values, based on business rules

Multiple change transactions per request for Change

Better usability and transparency: Assignment blocks display more details about Transport Requests and Task of a change transaction, Overview about the system landscape and system roles as w ell

as better integration betw een backend and transaction due to the integration of Task List logs

New “general change” process, for the management of changes for IT Assets

Further improvements for Retrofit, to provide even more automation features

Introducing expert mode for “Cross System Object Lock” w hich provides easier customizing options

For an overview of the new transaction types, please check chapter 3.2.1

1.1.1 Transition phase

http://scn.sap.com/community/getting-started

http://scn.sap.com/community/newsletters

http://www.sapstore.com/

http://scn.sap.com/welcome

http://wiki.scn.sap.com/wiki/login.jsp?os_destination=%2Fdisplay%2FSAPITSM%2FChange%2BRequest%2BManagement%2B%28ChaRM%29%2B-%2BUpgrade%2BGuide%2B7.0%2Bto%2B7.1

http://wiki.scn.sap.com/wiki

http://scn.sap.com/community/downloads

http://scn.sap.com/community/developer-center

http://scn.sap.com/community/uac

http://wiki.scn.sap.com/wiki/display/~jverh8u

http://wiki.scn.sap.com/wiki/display/~100q38q7m

http://wiki.scn.sap.com/wiki/display/SAPITSM

http://wiki.scn.sap.com/wiki/display/SAPITSM/ITSM+Wiki+-+IT+Service+Management+and+ChaRM+Wiki+Homepage

http://wiki.scn.sap.com/wiki/display/SAPITSM/Configuration+and+Administration+of+ITSM

http://wiki.scn.sap.com/wiki/display/SAPITSM/Change+Request+Management+%28ChaRM%29+-+Upgrade+Guide+7.0+to+7.1



When upgrading the application Change Request Management, you should consider that the new SAP ITSM (Incident Management, Problem Management and Change Request Management) functions are

only available in the SAP WebClient w ith new business object types and there is no migration from former object types. SAP CRM one order concept is still valid therefore parts of the customizing can be

reused.

The former Change Request Management scenario can still be used after an upgrade to the SAP Solution Manager release 7.1. SAP recommends a transition phase, as show n in the f igure below .

During the transition phase, you should consider the follow ing:

All new Change Request Management processes are created w ith the new object types and processed w ithin the SAP WebClient. You can use PFCG roles to restrict the authorization for message

creation. Please note that many authorization objects have been changed due to the new object types.

Existing (old) change messages (SDCR etc.) should be processed in the Work Center or SAP GUI, until they are completed.

Only in the Work Center, you are able to search and display the new and the former incident documents.

1.1.2 Upgrade Roadmap

You have to perform the Solution Manager basic configuration, as described in section 2.1 of this guide.

Piece list activation is a step of the basic configuration w hich you must not miss out. The piece list includes standard customizing for scenarios as Incident Management or Change Request

Management. It w ill overw rite only SAP customizing and has no effect on existing customer configuration from the customer naming space (w hich must begin w ith Z or Y). If your customer

configuration is not in the customer naming space, you should copy it into this naming space before the piece list activation.

For more information on the standard transaction (SMCR) customizing and the new role concept, please refer to chapter 3 (SMCR customizing) and 2.5.3 (Business Roles and Authorizations) of this guide.

First step after the technical upgrade is to run SOLMAN_SETUP and successfully complete the basic setup of SAP Solution Manager, as shortly highlighted in the f irst chapter of this document.

After the basic setup, you should continue by copying the new transaction types into the customer namespace, before starting to take over existing configuration. You can then start to reassign existing

text-, partner- or date-profiles.

If you have used the copy report, all the action and status profiles have also been copied to the customer namespace already – you can then start to adapt the new standard profiles to your personal

needs. A good approach might be to compare the existing configuration w ith the new standard configuration, also by using the comparison tables w hich are part of this document.

When you have f inished the customizing of the transaction types, including the copy control you can move forw ard by configuring the new Web Client user interface and the new functionalities of Change

Request Management (Assignment Blocks, …).

You’ll f ind a general overview and a description of the most important settings in chapter three of this document.

The f inal step is to adjust the authorizations and roles of all the users, to enable them to use the new functionalities and user interface.



1.2 Options to take over open transactions

After the upgrade from SAP Solution Manager 7.0 to 7.1 open change transactions of type SD* are existing but no new change transactions can be created for SDMN after the upgrade.

For this purpose it is possible to take over the open transactions from the old Maintenance Cycle (SDMN) to the new Maintenance Cycle (SMMN).

Please note that the follow ing example describes the case that the standard Maintenance Cycle (SDMN) is used.

To launch the procedure f irst close the old Maintenance Cycle (SDMN) via phase sw itch to “Completed”.

After that, create a new Maintenance Cycle w ith the new transaction type SMMN.

Unfinished and existing change transactions w ill be taken over, and can be processed by using the new SMMN transaction type (see table below ).

New change transactions can be created by using the transaction type SMCR (Request for Change).

* Additional customizing might be required

If the alternative Maintenance Cycle (SDMM) is used proceed equally as in the f irst example. Unfinished and existing change transactions w ill be taken over, and can be processed by using the new SMMM

transaction type (see table below ).

* Additional customizing might be required



1.3 Configuration Comparison (7.0 <> 7.1)

Please note the information described in the upgrade roadmap chapter above, before proceeding w ith the actions described in this section.

1.3.1 Overview Status Profiles

Statusprofile for Change Request (SDCR) and Request for Change (SMCR)

Statusprofile SDCR Statusprofile SM CR Comments

To be Approved Created Approval now via approval procedure

Validation This is the initial status for the change manager to validate the change

Flag “INPR” required to indicate the user status is linked w ith system status “In Process”

To be Approved In this status the approval procedure is triggered and running.

Flag “C4AP” required for approval procedure, to indicate start of procedure.

Rejected Rejected No Changes

Extending Scope Status to extend the scope of the request, after approval

Authorized Approved Only indicator for f inalized approval. No automatic creation of change transaction – manual status change required.

Flag “CAAP” required for approval procedure, to indicate success status

Being Implemented Creation of change transactions. This status indicates that the change transactions have been created and are in process

Implemented Implemented All change transactions have been f inished.

Flag “RELE” required

Confirmed Confirmed No Changes

Statusprofile for Normal Correction (SDMJ) and Normal Change (SMMJ)

Statusprofile SDM J Statusprofile SM M J Comments

Created Created No Changes

In Development In Development No Changes

To Be Tested To be Tested No Changes

Consolidated Successfully Tested Naming adjusted

Production Imported into Production Naming adjusted

Withdraw n Withdraw n No Changes

Statusprofile for Urgent Correction (SDHF) and Urgent Change (SMHF)

Statusprofile SDHF Statusprofile SM HF Comments


In Development In Development No Changes

To Be Tested To be Tested No Changes

Successfully Tested Successfully Tested No Changes

Authorized for Production Authorized for Production No Changes

Production Imported into Production No Changes




Completed Completed No Changes


Statusprofile for Administrative Message (SDAD) and Admin Change (SMAD)



In Process In Process No Changes

Completed Completed No Changes



Statusprofile for Test Message (SDTM) and Defect Correction (SMTM)



In Process In Correction Naming adjusted

To be Retested To be Retested No Changes



Statusprofile for General Change (SMCG)

Statusprofile SM CG Comments

Created New ly created transaction

In Process Change is in process

To be Tested Change ready for test

To be Documented Change documentation

Change Analysis Change analysis

Failed Changes has failed

Restore source Change has failed, Restore source

Confirmed Change is confirmed

Canceled Source w as restored, Change canceled

Withdrawn Change w as w ithdraw n

1.3.2 Overview CRM PPF Actions

Request for Change (SMCR) – Change Request (SDCR)

Action in 7.0 Action in 7.1 Comments

APPROVED Not available in 7.1 – replaced by approval procedure



SMCR_APPROVAL_PROCEDURE_STATUS Set status according to result of approval procedure, after the approval procedure is f inished

SMCR_APPROVED_SYSTEMS Creates the follow -on transactions, based on the content of the scope assignment block

SMCR_ASSIGN_SOLMAN_IBASE Assign the IBase of the SAP Solution Manager as default IBase of the RfC transaction. IBase f ield is

replaced w ith scope assignment block for RfC.

SMCR_AWAITING_APPROVAL Set status to aw aiting approval

SMCR_CANCEL_SCOPE_EXTENSION Set status back to “Being Implemented”

SDCR_CHECK_CONTEXT_CONSISTENCE SMCR_CHECK_CONTEXT_CONSISTENCE No Change

SDCR_CHECK_STATUS SMCR_CHECK_STATUS No Change

SMCR_CHECK_STATUS_AGAIN Performs a manual check to refresh errors in the transaction

CONFIRM_CR SMCR_CONFIRM No Change

SMCR_EXTEND_SCOPE Set status to “Extending Scope”

SMCR_IT_RFC_APPROVAL_WORKFLOW Required for the SAP w orkflow integration

SMCR_IT_RFC_CREATE_EMAIL_DOC Sends an email

SMCR_IT_RFC_DISPATCH Dispatch the RfC, based on dispatching rules

SMCR_QUALIFY_CHANGE Set status to “In Validation”

REJECTED SMCR_REJECTED No Change

CREATE_CHANGE_DOC SMCR_RELEASE_FOR_DEVELOPMENT No Change

SMCR_RESET_TO_VALIDATION Set status back to “In Validation”

SDCR_SET_KB_DELTA SMCR_SET_KB_DELTA No Change

SMCR_UPDATE_SCOPE Set status to “Approved” w ithout going through the approval procedure again

Normal Change (SMMJ) – Normal Correction (SDMJ)


APPROVE_CRITICAL_OBJS_MJ SMMJ_APPROVE_CRITICAL_OBJS_MJ Inactive – replaced by button in Transport Management Assignment Block, Customizing of this button can be done

in table XYZ

CHECK_STATUS_AGAIN_MJ SMMJ_CHECK_STATUS_AGAIN_MJ

CHECK_STATUS_MJ SMMJ_CHECK_STATUS_MJ

COPY_CONTEXT_MJ Replaced by standard copy control – see section 3.2.9

CREATE_REQUEST_MJ Replaced by button in Transport Management Assignment Block, settings of this button can be maintained via

customizing. Please see section 3.1.4

CREATE_TASK_MJ Replaced by button in Transport Management Assignment Block, settings of this button can be maintained via


IN_PROCESS_MJ SMMJ_IN_PROCESS_MJ No Change

LOGON_MJ Replaced by System Landscape Assignment Block

NAVIGATE_TO_TASKLIST_MJ SMMJ_NAVIGATE_TO_TASKLIST_MJ Inactive – navigation to task list possible via Related Transactions Assignment Block

NAVIGATE_TO_TEST_MJ Replaced by System Landscape Assignment Block

ON_CREATE_MJ SMMJ_ON_CREATE_MJ No change

PRODUCTIVE_MJ SMMJ_PRODUCTIVE_MJ No change

RELEASE_REQUEST_MJ Replaced by button in Transport Management Assignment Block, settings of this button can be maintained via


RETROFIT_CRM_MJ SMMJ_RETROFIT_CRM_MJ No change

SDMJ_SET_KB_DELTA SMMJ_SET_KB_DELTA No change



TESTED_AND_NOT_OK_MJ SMMJ_TESTED_AND_NOT_OK_MJ No change

TESTED_AND_OK_MJ SMMJ_TESTED_AND_OK_MJ No change

TO_BE_TESTED_MJ SMMJ_TO_BE_TESTED_MJ No change

TRANSPORT_COPIES_MJ Replaced by button in Transport Management Assignment Block, Customizing of this button can be done in table

XYZ

TRANSPORT_TO_SANDBOX_MJ SMMJ_TRANSPORT_TO_SANDBOX_MJ No change

WITHDRAW_MJ SMMJ_WITHDRAW_MJ No change

Urgent Change (SMHF) – Urgent Correction (SDHF)


APPROVE_CRITICAL_OBJS_HF SMHF_APPROVE_CRITICAL_OBJS_HF Inactive – replaced by button in Transport Management Assignment Block, Customizing of this button can be done in

table XYZ

CHECK_STATUS SMHF_CHECK_STATUS No Change

CHECK_STATUS_AGAIN SMHF_CHECK_STATUS_AGAIN No Change

CLOSE SMHF_CLOSE No Change

CONFIRM SMHF_CONFIRM No Change

CONTEXT_TAKE_OVER Replaced by standard copy control – see section 3.2.9

COPY_CONTEXT Replaced by standard copy control – see section 3.2.9

CREATE_REQUEST Replaced by button in Transport Management Assignment Block, settings of this button can be maintained via


CREATE_TASK Replaced by button in Transport Management Assignment Block, settings of this button can be maintained via


GO_LIVE SMHF_GO_LIVE No Change

IN_PROCESS SMHF_IN_PROCESS No Change

LOGON Replaced by System Landscape Assignment Block

NAVIGATE_TO_TASKLIST SMHF_NAVIGATE_TO_TASKLIST Inactive – navigation to task list possible via Related Transactions Assignment Block

NAVIGATE_TO_TEST Replaced by System Landscape Assignment Block

ON_SAVE SMHF_ON_SAVE No Change

PRODUCTIVE SMHF_PRODUCTIVE No Change

RELEASE_REQUEST Replaced by button in Transport Management Assignment Block, settings of this button can be maintained via


RETROFIT_CRM SMHF_RETROFIT_CRM No Change

SDHF_SET_KB_DELTA SMHF_SET_KB_DELTA No Change

TESTED_AND_NOT_OK SMHF_TESTED_AND_NOT_OK No Change

TESTED_AND_OK SMHF_TESTED_AND_OK No Change

TO_BE_TESTED SMHF_TO_BE_TESTED No Change

WITHDRAW SMHF_WITHDRAW No Change

Admin Change (SMAD) – Admin Message (SDAD)


CHECK_STATUS_AD SMAD_CHECK_STATUS_AD No Change



CHECK_STATUS_AGAIN_AD SMAD_CHECK_STATUS_AGAIN_AD No Change

COPY_CONTEXT_AD Replaced by standard copy control – see section 3.2.9

FINISHED_AD SMAD_FINISHED_AD No Change

IN_PROCESS_AD SMAD_IN_PROCESS_AD No Change

LOGON_AD SMAD_LOGON_AD No Change

NAVIGATE_TO_TASKLIST_AD SMAD_NAVIGATE_TO_TASKLIST_AD No Change

OK_AD SMAD_OK_AD No Change

ON_CREATE_AD SMAD_ON_CREATE_AD No Change

SDAD_SET_KB_DELTA SMAD_SET_KB_DELTA No Change

TESTED_AND_NOT_OK_AD SMAD_TESTED_AND_NOT_OK_AD No Change

WITHDRAW_AD SMAD_WITHDRAW_AD No Change

Defect Correction (SMTM) – Test Message (SDTM)


SMTM_APPROVE_CRITICAL_OBJS_HF

CHECK_STATUS_AGAIN_TM SMTM_CHECK_STATUS_AGAIN_TM No Change

CHECK_STATUS_TM SMTM_CHECK_STATUS_TM No Change

CREATE_REQUEST_TM SMTM_CREATE_REQUEST Replaced by button in Transport Management Assignment Block, Customizing of this button can be done in table 3.1.4

CREATE_TASK_TM Replaced by button in Transport Management Assignment Block, Customizing of this button can be done in table 3.1.4

IN_PROCESS_TM SMTM_IN_PROCESS_TM No Change

LOGON_TM SMTM_LOGON_TM No Change

NAVIGATE_TO_TASKLIST_TM SMTM_NAVIGATE_TO_TASKLIST_TM No Change

ON_CREATE_TM SMTM_ON_CREATE_TM No Change

RELEASE_REQUEST_TM Replaced by button in Transport Management Assignment Block, Customizing of this button can be done in table 3.1.4

SDTM_SET_KB_DELTA SMTM_SET_KB_DELTA No Change

TESTED_AND_NOT_OK_TM SMTM_TESTED_AND_NOT_OK_TM No Change

TESTED_AND_OK_TM SMTM_TESTED_AND_OK_TM No Change

TO_RETEST_TM SMTM_TO_RETEST_TM No Change

WITHDRAW_TM SMTM_WITHDRAW_TM No Change

General Change (SMCG)

Action in 7.1 Comments

SMCG_BUILDING Set status to transaction in “In Process”

SMCG_CHANGE DOCUMENTATION Set status to “To be documented”

SMCG_FALLBACK EXECUTION Set status to “Restore source”

SMCG_TO BE TESTED Set status to “To be tested”

SMCG_CHANGE EVALUATION Set status to “Change Evaluation”

SMCG_FAILED Set status to “Failed”

SMCG_CANCELED Set status “Canceled”



SMCG_CONFIRMED Set status to “Confirmed”

SMCG_WITHDRAWN Set status to “Withdraw n”

SMCG_SET_KB_DELTA Required for TREX Search

1.3.3 Overview ChaRM-Actions

Request for Change (SMCR) – Change Request (SDCR)


SET_PREDOC SET_PREDOC No change

APP_PROC_INI Required to initialize the approval procedure

APP_SCOPE Updates the status of the items in the scope assignment block

SYSTEM_EXIST Check w hether systems are assigned

EXT_SCOPE Set scope extension f lag



SET_BO_LINKS SET_BO_LINKS No change

SAVE_PARTNER SAVE_PARTNER No change

CLEAR_EMPTY CLEAR_EMPTY No change

COPY_ALL COPY_ALL No change


RELEASE_ALL RELEASE_ALL No change


Action 7.0 Action in 7.1 Comments

CREATE_HF CREATE_HF No change

SET_BO_LINKS SET_BO_LINKS No change

CREATE_REQ No automatic creation, replaced by a manual action (button) in the w eb user interface →

transport management assignment block, see 3.1.4



RELEASE_REQU RELEASE_REQU No change

IMPORT_TEST IMPORT_TEST No change

IMPORT_PROD IMPORT_PROD No change

CLOSE_TSK_LS CLOSE_TSK_LS No change

CLEAR_EMPTY CLEAR_EMPTY No change





SET_ BO_LINKS SET_ BO_LINKS No change





SET_BO_LINKS SET_BO_LINKS No changes

SAVE_PARTNER SAVE_PARTNER No changes



SET_PREDOC New transaction type- action similar

SAVE_PARTNER New transaction type- action similar

Further ChaRM-Actions


APP_PROC_TBA Initializes the approval steps

Example Use Case: If the status “Approved” w as rejected because of a Condition, the status w ill be reset to “To be approved” –

this action w ill then also reset the approval procedure.

PROJECT_ASSIGNED

RETROFIT_WEB Starts Retrofit from Web UI

NAV_TASK_WEB Open Task List from Web UI

Only working when started via PPF action

1.3.4 Overview CRM PPF-Conditions

Schedule Conditions:

The schedule condition decides w hether an action should be scheduled for processing. An action is therefore only generated if the schedule condition is met.



Start Conditions:

The start condition is checked before the action is executed. The action is only executed if the start condition is satisf ied.

The optimization rule is a date rule and returns a date from w hen the action is relevant. No attempt to process the action is made until this date has arrived.

Example (Comparison SDCR <> SMCR):

Change Request (SDCR):

Action Definition Schedule Condition in 7.0 Start Condition in 7.0

CONFIRM_CR Application Realized -

SDCR_CHECK_CONTEXT_CONSISTENCE - -

SDCR_CHECK_STATUS - -

APPROVED Only Status ‘To be approved’ -

REJECTED Only Status ‘To be approved’ -

CREATE_CHANGE_DOC - Change Request ‘Released’

SDCR_SET_KB_DELTA - -

Request for Change (SMCR):

Action Definition Schedule Condition in 7.1 Start Condition in 7.1

SMCR_APPROVED_SYSTEMS Not f inished In Implementation and error-free SMCR

SMCR_ASSIGN_SOLMAN_IBASE On created status SMCR -

SMCR_AWAITING_APPROVAL On status qualif ication and extend scope Error-Free

SMCR_CANCEL_SCOPE_EXTENSION Status in Scope Extension -

SMCR_CHECK_CONTEXT_CONSISTENCE - -

SMCR_CHECK_STATUS Product maintenance procedure is to be rechecked -

SMCR_CHECK_STATUS_AGAIN - -

SMCR_CONFIRM Confirm SMCR -

SMCR_EXTEND_SCOPE In Implementation or Implemented -

SMCR_IT_RFC_APPROVAL_WORKFLOW - RFC Aw aiting Approval

SMCR_IT_RFC_CREATE_EMAIL_DOC - -



SMCR_IT_RFC_DISPATCH - -

SMCR_QUALIFY_CHANGE In Initial Status -

SMCR_REJECTED In Qualif ication -

SMCR_RELEASE_FOR_DEVELOPMENT Status Approved -

SMCR_RESET_TO_VALIDATION Approved w ith or w ithout errors -

SMCR_UPDATE_SCOPE Status in Scope Extension -

SMCR_SET_KB_DELTA - -

1.3.5 Overview ChaRM-Conditions

SDCR <> SMCR:

Condition in 7.0 Condition in 7.1 Comments

IB_SYST_CHK IB_SYST_CHK

MAINT_CAT MAINT_CAT

PREDOC_CAN_BE_SET Checks if predecessor document is editable and not locked

PROJECT_ASSIGNED Check if the project f ield is f illed

SYSTEM_EXISTS Checks if all f ields for items in the scope assignment block are f illed

FOLLOW_ON_GEN_OK Checks if a project is required for the current scope definition and checks if a

project is assigned and if the project cycle is in the correct phase, so that change transactions can be created.

Also it checks w hether the assigned IBase is equal to the productive system of the landscape from the project.



NO_BUSINESS_PARTNER NO_BUSINESS_PARTNER No changes

IB_CMP_OK Not required in 7.1, since check is performed from UI Framew ork

MAINT_INST MAINT_INST No changes

RFC_DEST RFC_DEST No changes

TASKLIST_ACTIVE TASKLIST_ACTIVE No changes

BO_LINKS_COMPLETE BO_LINKS_COMPLETE No changes

NO_CRTCL_OBJ NO_CRTCL_OBJ No changes

TR_REQUEST TR_REQUEST No changes

ANY_CHANGES ANY_CHANGES No changes

IMPORT_INTO_TEST_OK IMPORT_INTO_TEST_OK No changes

SAME_USER SAME_USER No changes

IMPORT_INTO_PROD_OK IMPORT_INTO_PROD_OK No changes

TASK_LIST_CLOSED TASK_LIST_CLOSED No changes

PREP_FOR_PROD PREP_FOR_PROD No changes

NO_CHANGES NO_CHANGES No changes

PREDOC_CAN_BE_SET Checks if predecessor document is editable and not locked





ALL_TASKS_RELEASED ALL_TASKS_RELEASED No changes



CHECK_ACTION_PHASE CHECK_ACTION_PHASE No changes

IMPORT_OF_COPIES_OK IMPORT_OF_COPIES_OK No changes

MAINT_INST MAINT_INST No changes



NO_CRTCL_OBJ NO_CRTCL_OBJ No changes

PREDOC_CAN_BE_SET PREDOC_CAN_BE_SET No changes

PRODUCTION_IMPORT_OK PRODUCTION_IMPORT_OK No changes




TWB_TEST_OK TWB_TEST_OK No changes





IB_SYST_CHK IB_SYST_CHK No changes






TR_REQUEST TR_REQUEST No changes



BO_LINKS_COMPLETE No changes

MAINT_INST No changes

NO_BUSINESS_PARTNER No changes

RFC_DEST No changes

SAME_USER No changes



TASKLIST_ACTIVE No changes

PREDOC_CAN_BE_SET Checks if predecessor document is

editable and not locked



PREDOC_CAN_BE_SET Checks if predecessor document is

editable and not locked

1.3.6 BadIs in Change Request Management

Most of the BadIs available for Change Request management Workflow setup are still valid and therefore reusable for the 7.1 release. Anyw ay there are some BadIs that that are GUI specif ic. As in 7.1 w e

change w orkflow processing to CRM Web UI these BadIs are no longer valid.

BadI Function Comments

SOCM_CHECK_CONDITION Checks conditions for status transition Still usable

SOCM_PROCESS_ACTION Executes an action Still usable

EVAL_SCHEDCOND_PPF PPF: Exit for Evaluation of Schedule Condition Still usable

EVAL_STARTCOND_PPF PPF: Exit for Evaluation of Start Condition Still usable

CRM_FIELD_AUTH_BADI BAdI for Fieldcheck Tool Not usable in 7.1,Web UI because BadI w as specif ic for GUI

CRM_DNO_MONITOR Enhancements for Service Process Monitor Not usable in 7.1,Web UI because BadI w as specif ic for GUI

ORDER_SAVE BADI CRM Order Save Still usable

COM_PARTNER_BADI Business Add Ins for Partner Processing Still usable

CRM_PARTNER_BADI User Exits for the CRM Shell in Partner Processing Not usable in 7.1,Web UI because BadI w as specif ic for GUI

EXEC_METHODCALL_PPF PPF: BADI for Execution of Actions Still usable

CRM_DNO_LTEXT_FILTER Add-In for Filter Function: Long Text History for Service Process Still usable

CRM_ORDER_AUTH_CHECK Authorization Check: CRM Business Transaction Still usable

1.3.7 Searching old transaction types in Web Client

The follow ing text describes how you can activate existing SD* or ZD* transaction types for the search in the new Web Client UI.

You can assign one more channels to a transaction type. If you have assigned a transaction type to certain channels, only these transaction types are proposed for selection in the input help in this

channel.

Note: If you use this function and have assigned a channel to just one transaction type, you must have assigned at least one channel for all of the transaction types used in your enterprise.

The channel is determined w hen you create a transaction type and save it in the transaction header.

Customizing Steps for Old Change Documents:

IMG → SAP Solution Manager → Capabilities (Optional) → Change Management →Standard Configuration → Transaction Types → Define Transaction Types

The channel is assigned to the new transaction types by default:



For the old transaction types there is no entry by default:

For those transaction types add channel CRM Web Client UI:

Define Proxy Class, Log Text ID & Document Type:

IMG →SAP Solution Manager →Capabilities (Optional) →Change Management → Standard Configuration →Change Request Management Framework → Assign Implementation to Change Transaction

Types

The proxy instance functions are an interface to the Schedule Manager. Every transaction type has its ow n proxy implementation.

If you have created your ow n transaction types, you need to connect the Schedule Manager to your transaction types using a standard implementation. This ensures that the key properties relevant for the

management of change requests are copied to your transaction type.

Please note that there are different kinds of classes/interfaces for each transaction type. For example if you w ant to use your ow n transaction type ZDMN you need to choose the corresponding proxy

class for cycles:



1.3.8 Copy Control

Change Request Management and IT Service Management of SAP Solution Manager 7.1 uses the standard copy control of CRM. The ow n ChaRM copy control w as replaced w ith a BadI implementation and

a customizing table.

To customize the copy control tw o steps are required:

1) Customize the standard copy control of CRM

2) Define the detail customizing for Incident, Problem and Change Request Management

IM PORTANT: Copy Control rules for partners-functions changed from SAP Solution M anager 7.0 to SAP Solution M anager 7.1. The copy of partner-functions is no longer part

of the copy-control process, the standard partner determination functionalities of CRM have to be used.

In the standard partner determination you will find new SAP delivered rules to take over the partner from the preceding document.

1.3.9 Categorization & Subject Profile

The Categorization of transactions w hich w as used in the former release of SAP Solution Manager w as replaced w ith the so called “Multi Level Categorization” - a pow erful categorization functionality

coming from CRM 7.

The customizing of this categorization is much easier and can be mostly be done w ithin the new Web Client User Interface. More information about how to configure and adapt the multi level categorization

can also be found in 3.1.11

Another functionality of CRM 5 w as now replaced in CRM 7. The Subject-Profile, w hich w as used to determine the type of change in Change Request Management, is now replaced by the “Change

Category” in the scope assignment block.

The subject profile itself still exists, but the handling is totally different. There is no standard f ield available on the user interface, but you are able to link specif ic categories of your categorization scheme

of the multi level categorization w ith a specif ic subject profile – so in the background assignments of subject profiles are still possible. How ever, since this is no longer used by Change Request

Management this functionality is no longer supported and only the new functionality w ithin the Scope Assignment Block can be used.

1.3.10 Customizing Approval Settings

The approval functionalities in SAP Solution Manager are much more sophisticated as in the former release. Where as in the past the approval w as implemented via a status change, triggered from an PPF

action, in the new release there are so called approval procedures.

More information how the approval procedures can be used, and w hat kind of functionalities are available can be found in section 3.1.2 of this document.

How ever, if you w ant to use the existing w ay of approval management also w ithin the new 7.1 release, and don’t use the approval procedures – maybe at least for a transition period – you have to perform

some extra setup. In standard 7.1 the scope items are managed by an internal status w hich is set via an approval procedure coding. If you don't use the approval procedure code, you have to customize

the information in the PPF container status.

This is an alternative approval scenario.

The follow ing describes the required steps:

Implement the corrections of note 1608118 ChaRM scenario: Approve w ithout CRM approval procedure via transaction SNOTE

Call transaction SPRO and choose the IMG activity 'Define Action Profiles and Actions' (SAP Solution Manager Implementation Guide->Capabilities (Optional)->Change Management->Standard

Configuration->Transaction Types->Transaction Types->Action Profile).

Go to the relevant Request for Change action profile to the action w hich has the Method call 'HF_SET_STATUS' customized w ith the processing parameter 'USER_STATUS' and w hich sets the user

status to approved.

For the approval action, customize a new PPF container attribute element name = 'APPR_RESULT' w ith ABAP dictionary type 'CHAR1' and define initial value 'A' w hich represents approved status.



Go to the relevant PPF action w hich rejects the scope. For the rejecting action, customize a new PPF container attribute element name = 'APPR_RESULT' w ith ABAP dictionary type 'CHAR1' and define

initial value 'R' w hich represents rejected status.

Save your changes. Now w hen approving and choosing the status 'Release for Development', the follow -on change documents are generated.

1.3.11 Remote Connectivity for Managed Systems



The connection from the SAP Solution Manager and the Managed Systems for Change Request Management w as also changed w ith the new release.

In previous releases of ChaRM and QGM the remote communication w as handled partly by the RFC destinations managed in SMSY and partly by the remote infrastructure of TMS.

This led to confusion w hich infrastructure is used for w hich action. Also for all actions using the TMS infrastructure, users in client 000 of the target system are required.

Therefore w ith Solution Manager 7.1 the remote infrastructure is changed to a sole usage of the SMSY RFC destinations. How ever, prerequisite to this usage is the availability of remote enabled APIs in the

managed systems of SAP Solution Manager.

A new remote infrastructure is now managing the queries betw een SAP Solution Manager and the Managed systems for the transport management activities. By using this new remote infrastructure

domain links are no longer required.

This also applies to Quality Gate Management

To be able to leverage the functionalities of the new remote infrastructure the ST/PI package needs to be deployed on your managed systems. Details can be found in SAP Note 1384598.

1.3.12 Migration of Customer specific fields

For f ields that have been created on SAP Solution Manager 7.0 using the Easy Enhancement Workbench of CRM it is required to do a separate migration to have those f ields also available for the UI

configuration on the new Web Client UI.

With CRM 7.0 the Easy Enhancement Workbench w as replaced by the AET (Application Enhancement Tool).

You can migrate manual f ields to the format used in the Application Enhancement Tool (AET). This function is available in the form of a guided activity that takes you through the process of migrating manual

f ields of an extension.

A manual f ield is either a f ield created manually in the ABAP dictionary by modifying an append structure, or a f ield created using the Easy Enhancement Workbench (EEW). Manual f ields are displayed in the

AET, but you cannot edit them.

How ever, w e cannot cover the complete migration process in this document – therefore please have a look at the follow ing links:

SDN Blog from Stephen Johannes: “CRM 40 to 52: CUSTOMER_H Fields”

URL: http://w w w .sdn.sap.com/irj/scn/w eblogs?blog=/pub/w lg/8442

CRM Application Help: “Migration of Manual Fields”

URL: http://help.sap.com/saphelp_crm700_ehp02/helpdata/en/2a/341deba24548059b5ec229dbc0c334/frameset.htm

No labels

Follow SCN

Contact Us SAP Help Portal

Privacy Terms of Use Legal Disclosure Copyright

http://www.sdn.sap.com/irj/scn/weblogs?blog=/pub/wlg/8442

http://help.sap.com/saphelp_crm700_ehp02/helpdata/en/2a/341deba24548059b5ec229dbc0c334/frameset.htm

http://bit.ly/SCNTwR

http://bit.ly/SCNFB

http://bit.ly/SCNyouT

http://bit.ly/SCNLnI

http://scn.sap.com/docs/DOC-18476

http://help.sap.com/

http://www.sdn.sap.com/irj/scn/policy?view=PP

http://www.sdn.sap.com/irj/scn/policy

http://www.sap.com/corporate-en/our-company/legal/impressum.epx

http://www.sap.com/corporate-en/our-company/legal/copyright/index.epx

change request management (charm) - upgrade guide 7.0 to 7.1

Documents

new user interface w

new w eb

new transaction types

old user interface w

new environment

new documents

change request management1

lot of new functionalities