Skip to end of metadata
Go to start of metadata
 

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 which 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 work correctly in the new environment. Therefore new transaction types have been created. Those transaction types are only working on the new user interface, whereas all the old transaction types are only working 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 will display the content of the selected document.

Some highlights of Change Request Management functionalities in 7.1 are:

  • New web based user interface which 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 field-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 well as better integration between 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” which provides easier customizing options

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

1.1.1        Transition phase

 

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 with 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 shown in the figure below.

 

 

                       

During the transition phase, you should consider the following:

  • All new Change Request Management processes are created with the new object types and processed within 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 which you must not miss out. The piece list includes standard customizing for scenarios as Incident Management or Change Request

         Management. It will overwrite only SAP customizing and has no effect on existing customer configuration from the customer naming space (which must begin with 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 first 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 with the new standard configuration, also by using the comparison tables which are part of this document.

When you have finished the customizing of the transaction types, including the copy control you can move forward by configuring the new Web Client user interface and the new functionalities of Change Request Management (Assignment Blocks, …).

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

The final 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 following example describes the case that the standard Maintenance Cycle (SDMN) is used.

To launch the procedure first close the old Maintenance Cycle (SDMN) via phase switch to “Completed”.

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

Unfinished and existing change transactions will 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 first example. Unfinished and existing change transactions will 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 with 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 SMCR           

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 with 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 finalized 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 finished.

Flag “RELE” required

Confirmed

Confirmed

No Changes

 

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

 

Statusprofile SDMJ                    

Statusprofile SMMJ            

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

Withdrawn

Withdrawn

No Changes

 

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

 

Statusprofile SDHF                   

Statusprofile SMHF              

Comments                                                                                                                                                                                  

Created

Created

No Changes

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

Confirmed

Confirmed

No Changes

Completed

Completed

No Changes

Withdrawn

Withdrawn

No Changes

 

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

 

Statusprofile SDHF                  

Statusprofile SMHF               

Comments                                                                                                                                                                                 

Created

Created

No Changes

In Process

In   Process

No Changes

Completed

Completed

No Changes

Confirmed

Confirmed

No Changes

Withdrawn

Withdrawn

No Changes

 

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

 

Statusprofile SDHF                  

Statusprofile SMHF               

Comments                                                                                                                                                                                 

Created

Created

No Changes

In Process

In   Correction

Naming adjusted

To be Retested

To be Retested

No Changes

Confirmed

Confirmed

No Changes

Withdrawn

Withdrawn

No Changes

 

Statusprofile for General Change (SMCG)

 

Statusprofile SMCG                 

Comments

Created

Newly 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   was restored, Change canceled

Withdrawn

Change was withdrawn

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 finished

 

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 field is replaced with scope   assignment block for RfC.

 

SMCR_AWAITING_APPROVAL

Set   status to awaiting 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 workflow 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” without going through the   approval procedure again

 

Normal Change (SMMJ) – Normal Correction (SDMJ)

 

Action in 7.0

Action in 7.1

Comments

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 customizing. Please see section 3.1.4

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 customizing.   Please see section 3.1.4

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)

 

Action in 7.0

Action in 7.1

Comments

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 customizing. Please see section 3.1.4

CREATE_TASK

 

Replaced by button in Transport Management   Assignment Block, settings of this button can be maintained via customizing.   Please see section 3.1.4

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 customizing.   Please see section 3.1.4

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)

 

Action in 7.0                                    

Action in 7.1

Comments                                                                                                                                                   

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)

 

Action in 7.0

Action in 7.1

Comments

 

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 “Withdrawn”

SMCG_SET_KB_DELTA

Required   for TREX Search

1.3.3        Overview ChaRM-Actions

 

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

 

Action in 7.0                          

Action in 7.1                                                 

Comments                                                                                                                                            

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   whether systems are assigned

 

EXT_SCOPE         

Set scope extension flag

 

Normal Change (SMMJ) – Normal Correction (SDMJ)

 

Action in 7.0                          

Action in 7.1                                                 

Comments                                                                                                                                             

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

SET_PREDOC

SET_PREDOC

No change

RELEASE_ALL

RELEASE_ALL

No change

 

Urgent Change (SMHF) – Urgent Correction (SDHF)

 

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 web user interface →                                                                       

 transport management assignment block,   see 3.1.4                                                                                                                           

SAVE_PARTNER

SAVE_PARTNER

No change

SET_PREDOC

SET_PREDOC

No change

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

 

Admin Change (SMAD) – Admin Message (SDAD)

 

Action in 7.0              

Action in 7.1

Comments                                                                                                                                                                                                  

SET_ BO_LINKS

SET_ BO_LINKS

No change

SAVE_PARTNER

SAVE_PARTNER

No change

SET_PREDOC

SET_PREDOC

No change

 

 

Defect Correction (SMTM) – Test Message (SDTM)

 

Action in 7.0             

Action in 7.1           

Comments                                                                                                                                                                                               

SET_BO_LINKS

SET_BO_LINKS

No changes

SAVE_PARTNER

SAVE_PARTNER

No   changes

 

General Change (SMCG)

 

Action in 7.0              

Action in 7.1            

Comments                                                                                                                                                                                             

 

SET_PREDOC

New transaction   type- action similar

 

SAVE_PARTNER

New transaction type- action similar

 

Further ChaRM-Actions

Action in 7.0              

Action in 7.1

Comments                                                                                                                                                                                        

 

APP_PROC_TBA

Initializes the approval steps

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

 this   action will 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 whether 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 satisfied.

The optimization rule is a date rule and returns a date from when 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   finished

In   Implementation and error-free SMCR

SMCR_ASSIGN_SOLMAN_IBASE

On created status SMCR

-

SMCR_AWAITING_APPROVAL

On status   qualification 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 Awaiting Approval

SMCR_IT_RFC_CREATE_EMAIL_DOC

-

-

SMCR_IT_RFC_DISPATCH

-

-

SMCR_QUALIFY_CHANGE

In   Initial Status

-

SMCR_REJECTED

In Qualification

-

SMCR_RELEASE_FOR_DEVELOPMENT

Status   Approved

-

SMCR_RESET_TO_VALIDATION

Approved with or without 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 field is filled

 

SYSTEM_EXISTS

Checks if all fields for items in the   scope assignment block are filled

 

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 whether the assigned IBase is equal to the productive system of the   landscape from the project.

 

Urgent Change (SMHF) – Urgent Correction (SDHF)

 

Condition in 7.0

Condition in 7.1

Comments                                                                                                                                                                                    

NO_BUSINESS_PARTNER

NO_BUSINESS_PARTNER

No   changes

IB_CMP_OK

 

Not required in 7.1, since check is performed from   UI Framework

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

 

Normal Change (SMMJ) – Normal Correction (SDMJ)

 

Condition   in 7.0

Condition   in 7.1

Comments                                                

ALL_TASKS_RELEASED

ALL_TASKS_RELEASED

No changes

ANY_CHANGES  

ANY_CHANGES   

No   changes

BO_LINKS_COMPLETE

BO_LINKS_COMPLETE

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_BUSINESS_PARTNER

NO_BUSINESS_PARTNER 

No changes

NO_CHANGES    

NO_CHANGES     

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

RFC_DEST           

RFC_DEST           

No   changes

SAME_USER        

SAME_USER        

No changes

TASKLIST_ACTIVE             

TASKLIST_ACTIVE              

No   changes

TWB_TEST_OK

TWB_TEST_OK

No changes

 

Defect Correction (SMTM) – Test Message (SDTM)

 

Condition in 7.0                                   

Condition in 7.1                                  

Comments                                               

ANY_CHANGES  

ANY_CHANGES   

No changes

BO_LINKS_COMPLETE

BO_LINKS_COMPLETE

No   changes

IB_SYST_CHK     

IB_SYST_CHK      

No changes

NO_BUSINESS_PARTNER

NO_BUSINESS_PARTNER 

No   changes

NO_CHANGES    

NO_CHANGES     

No changes

RFC_DEST           

RFC_DEST           

No   changes

SAME_USER        

SAME_USER        

No changes

TASKLIST_ACTIVE             

TASKLIST_ACTIVE              

No   changes

TR_REQUEST      

TR_REQUEST      

No changes

 

 Admin Change (SMAD) – Admin Message (SDAD)

 

Condition in 7.0                                   

Condition in 7.1                                 

Comments                                               

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

 

 General Change (SMCG)

 

Condition in 7.0                                  

Condition in 7.1                                 

Comments

 

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. Anyway there are some BadIs that that are GUI specific. As in 7.1 we change workflow 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 was specific for GUI

CRM_DNO_MONITOR  

Enhancements for Service Process Monitor

Not usable in 7.1,Web UI because BadI was specific   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 was specific 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 following 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 when 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 ManagerCapabilities (Optional) →Change Management → Standard ConfigurationChange 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 own proxy implementation.

If you have created your own 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 want to use your own 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 own ChaRM copy control was replaced with a BadI implementation and a customizing table.

To customize the copy control two steps are required:

1)     Customize the standard copy control of CRM

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

 

    IMPORTANT: Copy Control rules for partners-functions changed from SAP Solution Manager 7.0 to SAP Solution Manager 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 which was used in the former release of SAP Solution Manager was replaced with the so called “Multi Level Categorization” - a powerful categorization functionality coming from CRM 7.

The customizing of this categorization is much easier and can be mostly be done within 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 was now replaced in CRM 7. The Subject-Profile, which was 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 field available on the user interface, but you are able to link specific categories of your categorization scheme of the multi level categorization with a specific subject profile – so in the background assignments of subject profiles are still possible. However, since this is no longer used by Change Request Management this functionality is no longer supported and only the new functionality within 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 was 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 what kind of functionalities are available can be found in section 3.1.2 of this document.

However, if you want to use the existing way of approval management also within 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 which 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 following describes the required steps:

  • Implement the corrections of note 1608118 ChaRM scenario: Approve without 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 which has the Method call 'HF_SET_STATUS' customized with the processing parameter 'USER_STATUS' and which sets the user status to approved.

 

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

 

 

 

 

 

  • Go to the relevant PPF action which rejects the scope. For the rejecting action, customize a new PPF container attribute element name = 'APPR_RESULT' with ABAP dictionary type 'CHAR1' and define initial value 'R' which represents rejected status.

 

 

  • Save your changes. Now when 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 was also changed with the new release.

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

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

Therefore with Solution Manager 7.1 the remote infrastructure is changed to a sole usage of the SMSY RFC destinations. However, 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 between 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 fields 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 fields also available for the UI configuration on the new Web Client UI.

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

You can migrate manual fields 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 fields of an extension.

A manual field is either a field created manually in the ABAP dictionary by modifying an append structure, or a field created using the Easy Enhancement Workbench (EEW). Manual fields are displayed in the AET, but you cannot edit them.

However, we cannot cover the complete migration process in this document – therefore please have a look at the following links:

 

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

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

 

  • CRM Application Help: “Migration of Manual Fields”

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

 

 

 

 

  • No labels