solution manager demo

Retrofit Demo

© SAP AG 2010, ALM EMEA RIG /

ChaRM Retrofit - Motivation

Changes of a Maintenance project also should be duplicated in a

Implementation Project that will provide the same Production system of the

landscape.

The development system of the Implementation project has no connection

to the transport track. This is because of originality reason.

Formerly this post processing was performed manually.

Retrofit is the function available to perform this duplication automatically/semi

automatically.


Maintenance Landscape

QAS

Implementation Landscape

DEV TEST

Retrofit

PRD MAINT

System Landscape in the Standard Retrofit

Scenario

The Retrofit is performed for a transport request which is controlled by SAP Solution Manager

The Retrofit is part of the Change Request Management Process supported by SAP Solution Manager

The Retrofit is performed with the SAP Solution Manager


RETROFIT

SCWB with piece

list

BC-SET with piece

list

Retrofit Process Overview

QAS PRD MAINT

DEV TEST

Apply Retrofit Data at

Retrofit Time to the Upgrade Landscape

TRANSPORT REQUEST

Manual Objects

Auto Import Objects

Retrofit Objects

Create Retrofit Data at

Release Time of Transport Request

STOP

Adjust Originality of Imported Objects and

change Transport Layer of transported Packages

(performed automatically by the retrofit tool)

1

2

3


Retrofit Object Category Calculation –

An Example

QAS PRD MAINT

Maintenance Landscape

DEV

1 Modify Report RA on DEV/4.7 and release it

2 SolMan creates Retrofit Data Auto Import RA

3 SolMan Triggers Retrofit of Report RA

4 Report RB is modified on DEV/6.0

5 Lock Entry for Report RB is created on SolMan

SolMan 6 Report RB and RC are modified and released in 4.7

7 SolMan creates RFIT Data RC is Auto Import

RB is Retrofit 8 SolMan triggers retrofit RC via Auto Import

RB via SCWB

2

3

1

RA

4

RB

5

RB, RC

6

7 8

Req. Obj. Cat. Stat.

1 RA AI

2 RB NO

3 RC AI

3 RB RF


Demo System Landscape

Maintenance Project SLM.801 -> SLM.802 -> SLM.803

Implementation Project SOL.801 -> SOL.802 -> SLM.803

Solution Manager SOL.200


Demo ChaRM Project

Project ID Project type Tasklist ID

RFIT_M Maintenance project M000000285

RFIT_I Implementation project I000000284


Additional info of demo scenarios

Three options exist when the Retrofit can be done:

After functional tests

After integration test sign off

After import into production

We only use ChaRM-light in our demo scenarios, which means only tasklist is used without

any ChaRM workflow processes(NC and UC).

SLM Solution Manager 7.0

SOL Solution Manager 7.0 EHP1

The product version of maintenance project and implementation project are on different EhP

levels. Therefore we enhanced the demo scenario in following aspects:

SAP standard objects might have been changed by the upgrade, so that no auto-import

procedures can be used to transfer SAP standard objects into the higher release.

The structure of customizing tables might have been changed by the upgrade. Therefore

not all customizing changes can be transferred by auto-import procedures.

Certain business scenarios might have been completely re-designed in the new release.

Therefore changes in the lower release might not be relevant at all for the higher release, or

they must be re-designed as well.


Demo test cases

Auto-import

SCWB

BC-Set

Manual


Auto-import

- Overview

No. Description

Demo

System

System

Role Result Remark

1

Create a workbench TR in Maint. DEV

via tasklist. SOL.200 Solman

A workbech TR should be created in the

Maint. DEV with status 'Modifiable'. T-code for tasklist: SCMA

2

Create a Z repository object (package,

program, table definition, etc.) in the

Maint. DEV, store it in the TR created

in step 1. SLM.801

Maint.

DEV

The TR should contain the newly created

Z object with status 'Released'.

This object should not exist in Impl. DEV

at this moment.

3

Release the task of this TR in Maint.

DEV via transaction SE09. SLM.801

Maint.

DEV Status of the task should be released.

4 Release the TR via tasklist. SOL.200 Solman

The TR should be released in Maint. DEV.

Also, the corresponding ToC for this TR

should be generated and released in

Maint. DEV.

The target system of the ToC should be

Impl. DEV.

5

Update/Adjust the import queue of

Impl. DEV system. SOL.801

Impl.

DEV

The ToC should appear in the import

queue of the Impl. DEV.

The way of update/adjusting the import

queue: Import queue of Impl. DEV ->

Extras -> Other Requests -> Find in

other groups -> Start the job

immediately.

6

Create a workbench TR (target TR) in

Impl. DEV via tasklist SOL.200 Solman


Impl. DEV with status 'Modifiable'.

7

Start retrofit in the tasklist of Maint.

Project. SOL.200 Solman

A screen should popup, in which a list of

all the to-be retrofitted TR should be

contained.

8

Select the row of the to-be-retrofitted

TR(created in step 1), assign the target

TR (created in step 6) to it, and click on

the button 'Auto-import' at the bottom

of the screen. SOL.200 Solman

Choose 'Yes' for some popup dialog

boxes. Now the Z object should be in the

Impl. DEV and it is included in the target

TR.


Auto-import

- Create a workbench TR in Maint. DEV via tasklist

No. Description

Demo

System

System

Role Result Remark

1

Create a workbench TR in Maint. DEV



Maint. DEV with status 'Modifiable'. T-code for tasklist: SCMA


Auto-import

- Create a Z object in Maint. DEV

No. Description

Demo

System

System

Role Result Remark

2

Create a Z repository object (package,

program, table definition, etc.) in the Maint.

DEV, store it in the TR created in step 1. SLM.801

Maint.

DEV

The TR should contain the newly

created Z object with status

'Released'.

This object should not exist in Impl. DEV

at this moment.


Auto-import

- Release task in Maint. DEV via SE09

No. Description

Demo

System

System

Role Result Remark

3

Release the task of this TR in Maint. DEV via

transaction SE09. SLM.801

Maint.

DEV

Status of the task should be

released.


Auto-import

- Release the TR via tasklist

No. Description

Demo

System

System

Role Result Remark

4 Release the TR via tasklist. SOL.200 Solman

The TR should be released in Maint. DEV. Also, the

corresponding ToC for this TR should be generated

and released in Maint. DEV.

The target system of the ToC should be

Impl. DEV.


Auto-import

- Update/Adjust the import queue of Impl. DEV system

No. Description

Demo

System

System

Role Result Remark

5

Update/Adjust the import

queue of Impl. DEV system. SOL.801

Impl.

DEV

The ToC should appear in the

import queue of the Impl. DEV.

The way of update/adjusting the import queue: Import

queue of Impl. DEV -> Extras -> Other Requests -> Find

in other groups -> Start the job immediately.


Auto-import

- Create target TR in Impl. DEV via tasklist

No. Description

Demo

System

System

Role Result Remark

6

Create a workbench TR (target TR)

in Impl. DEV via tasklist SOL.200 Solman




Auto-import


No. Description

Demo

System

System

Role Result Remark

7

Start retrofit in the tasklist of Maint.


A screen should popup, in which a list of all

the to-be retrofitted TR should be contained.


Auto-import

- Auto-import the to-be-retrofitted TR

No. Description

Demo

System

System

Role Result Remark

8

Select the row of the to-be-retrofitted TR(created

in step 1), assign the target TR (created in step

6) to it, and click on the button 'Auto-import' at

the bottom of the screen. SOL.200 Solman

Choose 'Yes' for some popup dialog

boxes. Now the Z object should be in the

Impl. DEV and it is included in the target

TR.


SCWB

- Overview

No. Description

Demo

system

System

Role Result Remark

1 Create a workbench TR in Impl. DEV via tasklist. SOL.200 Solman

A workbech TR should be created in Impl.

DEV with status 'Modifiable'.

2

Change the coding of a Z report in Impl. DEV, store

the change in the TR. SOL.801

Impl.

DEV

The changed report should be included in

the TR.

* Make sure that the changed

report is also in Maint. DEV.

3

Release the task of this TR in Impl. DEV via

transaction SE09 SOL.801

Impl.


4

Release the workbench TR in Impl. DEV via

tasklist. SOL.200 Solman The TR should be released in Impl. DEV.

5 Create a workbench TR in Maint. DEV via tasklist. SOL.200 Solman

A workbech TR should be created in Maint.


6

In Maint. DEV, change the coding of the same

report which has been changed in step 2, store the

change in the TR created in step 5. SLM.801

Maint.

DEV

The changed report should be included in

the TR.

* Make sure to change the same

report which has been changed in

step 2.

7


transaction SE09 SLM.801

Maint.


8

Release the to-be-retrofitted TR (created in step 5)

via tasklist SOL.200 Solman The TR should be released in Maint. DEV.

9

Create another workbench TR (target TR) in Impl.

DEV via tasklist. SOL.200 Solman

Another workbech TR should be created in


10 Start retrofit in the tasklist of Maint. Project. SOL.200 Solman


to-be retrofitted TR should be contained.

11

Double-click on the row of the to-be-retrofitted

TR(created in step 5), choose the row of the to-be

retrofitted object(the report), press button “Compare

Source and Destination”. SOL.200 Solman

The comparison result screen should

appear.

12

Select the row of the to-be-retrofitted TR (created in

step 5), assign the target TR (created in step 9) to

it, and click on the button 'Transfer with SCWB' at


Choose 'Yes' for some popup dialog boxes,

merge the coding automatically or

manually. The changed part in Maint. DEV

should appear in the Impl. DEV, and the

report should be included in the target TR.


SCWB

- Create a workbench TR in Impl. DEV via tasklist

No. Description

Demo

system

System

Role Result Remark

1 Create a workbench TR in Impl. DEV via tasklist. SOL.200 Solman




SCWB

- Change the coding of a Z report in Impl. DEV

No. Description

Demo

system

System

Role Result Remark

2

Change the coding of a Z report in Impl. DEV, store

the change in the TR. SOL.801

Impl.

DEV

The changed report should be included in the

TR.

* Make sure that the changed

report is also in Maint. DEV.


SCWB

- Release the task in Impl. DEV via transaction SE09

No. Description

Demo

system

System

Role Result Remark

3

Release the task of this TR in Impl. DEV via

transaction SE09 SOL.801

Impl.



SCWB

- Release the workbench TR in Impl. DEV via tasklist

No. Description

Demo

system

System

Role Result Remark

4 Release the workbench TR in Impl. DEV via tasklist. SOL.200 Solman The TR should be released in Impl. DEV.


SCWB


No. Description

Demo

system

System

Role Result Remark

5

Create a workbench TR in Maint. DEV via

tasklist. SOL.200 Solman

A workbech TR should be created in Maint.



SCWB

- Change the coding of a Z report in Maint. DEV

No. Description

Demo

system

System

Role Result Remark

6

In Maint. DEV, change the coding of the same

report which has been changed in step 2, store the

change in the TR created in step 5. SLM.801

Maint.

DEV

The changed report should be included in the

TR.

* Make sure to change the

same report which has been

changed in step 2.


SCWB

- Release the task of this TR in Maint. DEV via SE09

No. Description

Demo

system

System

Role Result Remark

7



Maint.



SCWB

- Release the TR via tasklist

No. Description

Demo

system

System

Role Result Remark

8

Release the to-be-retrofitted TR (created in step

5) via tasklist SOL.200 Solman The TR should be released in Maint. DEV.


SCWB


No. Description

Demo

system

System

Role Result Remark

9

Create a workbench TR (target TR) in Impl. DEV





SCWB

- Start retrofit in the tasklist of Maint. Project

No. Description

Demo

system

System

Role Result Remark

10 Start retrofit in the tasklist of Maint. Project. SOL.200 Solman


to-be retrofitted TR should be contained.


SCWB

- Compare Source and Destination

No. Description

Demo

system

System

Role Result Remark

11

Double-click on the row of the to-be-retrofitted TR,

choose the row of the to-be retrofitted object(the

report), press button “Compare Source and

Destination”. SOL.200 Solman The comparison result screen should appear.


SCWB

- Transfer with SCWB

No. Description

Demo

system

System

Role Result Remark

12

Select the row of the to-be-retrofitted TR (created in

step 5), assign the target TR (created in step 9) to it,

and click on the button 'Transfer with SCWB' at the

bottom of the screen. SOL.200 Solman


merge the coding automatically or manually.

The changed part in Maint. DEV should

appear in the Impl. DEV, and the report should

be included in the target TR.


BC-Set

- Overview

No. Description

Demo

System

System

Role Result Remark

1 Create a customizing TR in Impl. DEV via tasklist SOL.200 Solman

A customizing TR should be created in Impl.


2

Add a new entry in a customizing table/view via

SM30 in Impl. DEV, store the change into the TR. SOL.801 Impl. DEV

The TR should contain the newly cutomizing

entry of this table/view.

* The customizing table/view should be also

available in the maintenance system.

* It could be SAP standard object or a Z one.

* Some possible tables/views: V_T005S, V024

3 Create a customizing TR in Maint. DEV via tasklist. SOL.200 Solman

A customizing TR should be created in Maint.


4

In Maint. DEV, add a new entry in the customizing

table/view via SM30 which was changed in step 2,

store the change into the TR created in step 3. SLM.801

Maint.

DEV



* Make sure to change the same customizing

table/view which was changed in step 2.

* Make sure that the key fields of the new entry

are the same as the one created in step 2,

while the other fields are different.

5



Maint.


6



7

Create another customizing TR (target TR) in Impl.


Another customizing TR should be created in

the implementation DEV system with status

'Modifiable'.

8 Start retrofit in tasklist of Maint. Project. SOL.200 Solman



9



retrofitted object(the customizing entry), press

button “Compare Source and Destination”. SOL.200 Solman The comparison result screen should appear.

10

Select the row of the to-be-retrofitted TR(created in


it, and click on the button 'Transfer with BC-Set' at



pay attention to the entries in the BC-Set

since they will overwrite the value in Impl.

DEV. Then, the changed entries should

appear in the table/view in Impl. DEV and be

included in the target TR.


BC-Set

- Create a customizing TR in Impl. DEV via tasklist

No. Description

Demo

System

System

Role Result Remark

1 Create a customizing TR in Impl. DEV via tasklist SOL.200 Solman

A customizing TR should be created in Impl.



BC-Set

- Add new entry in customizing table/view in Impl. DEV

No. Description

Demo

System

System

Role Result Remark

2

Add a new entry in a customizing table/view via

SM30 in Impl. DEV, store the change into the TR. SOL.801 Impl. DEV



* The customizing table/view should be also

available in the maintenance system.

* It could be SAP standard object or a Z one.

* Some possible tables/views: V_T005S, V024


BC-Set

- Create a customizing TR in Maint. DEV via tasklist

No. Description

Demo

System

System

Role Result Remark

3 Create a customizing TR in Maint. DEV via tasklist. SOL.200 Solman

A customizing TR should be created in Maint.



BC-Set

- Add new entry in customizing table/view in Maint. DEV

No. Description

Demo

System

System

Role Result Remark

4

In Maint. DEV, add a new entry in the customizing

table/view via SM30 which was changed in step 2,

store the change into the TR created in step 3. SLM.801

Maint.

DEV



* Make sure to change the same customizing

table/view which was changed in step 2.

* Make sure that the key fields of the new entry

are the same as the one created in step 2,

while the other fields are different.


BC-Set

- Release the task in Maint. DEV via SE09

No. Description

Demo

System

System

Role Result Remark

5



Maint.



BC-Set

- Release the to-be-retrofitted TR via tasklist

No. Description

Demo

System

System

Role Result Remark

6




BC-Set


No. Description

Demo

System

System

Role Result Remark

7

Create another customizing TR (target TR) in Impl.


Another customizing TR should be created in

the implementation DEV system with status

'Modifiable'.


BC-Set

- Start retrofit in tasklist of Maint. Project

No. Description

Demo

System

System

Role Result Remark

8 Start retrofit in tasklist of Maint. Project. SOL.200 Solman




BC-Set

- Compare Source and Destination

No. Description

Demo

System

System

Role Result Remark

9



retrofitted object(the customizing entry), press

button “Compare Source and Destination”. SOL.200 Solman The comparison result screen should appear.


BC-Set

- Transfer with BC-Set

No. Description

Demo

System

System

Role Result Remark

10

Select the row of the to-be-retrofitted TR(created in


it, and click on the button 'Transfer with BC-Set' at



pay attention to the entries in the BC-Set

since they will overwrite the value in Impl.

DEV. Then, the changed entries should

appear in the table/view in Impl. DEV and be

included in the target TR.


Manual

- Overview

No. Description Demo System System Role Result Remark

1

Create a workbench TR in Maint.



Maint. Dev with status 'Modifiable'.

2

In Maint. DEV, change the coding a

SAP standard report, store the

change into the TR. SLM.801 Maint. DEV

The coding of the report should be

changed, and the report should be included

in the TR.

* You can use report

/SDF/CMO_COLLECT_DATA_INC

for test.

3

Release the task of the TR in Maint.

DEV via SE09 SLM.801 Maint. DEV The status of the task should be released.

4

Release the to-be-retrofitted TR via

tasklist of Maint. Project. SOL.200 Solman The status of the TR should be released.

5


in Impl. DEV via tasklist. SOL.200 Solman



6

Start retrofit in tasklist of Maint.



the to-be retrofitted TR should be

contained.

7

Change the coding of the same

report in Impl. DEV manually

according to the coding in the Maint.

DEV, then store it in the target TR

(created in step 5) . SOL.801 Impl. DEV

The coding should be changed accordingly,

and the target TR should contain the

changed report.

8


TR, assign the target TR (created in

step 4) to it, and click on the button

“Additional Functions' -> “Manual

Retrofitted” at the top of the screen. SOL.200 Solman

The manually retrofitted TR could be

viewed by clicking on the button

“Retrofitted”.


Manual



1

Create a workbench TR in Maint.



Maint. Dev with status 'Modifiable'.


Manual

- Change coding of a SAP standard report in Maint. DEV


2

In Maint. DEV, change the coding a

SAP standard report, store the

change into the TR. SLM.801 Maint. DEV

The coding of the report should be

changed, and the report should be included

in the TR.

* You can use report

/SDF/CMO_COLLECT_DATA_INC

for test.


Manual



3

Release the task of the TR in Maint.

DEV via SE09 SLM.801 Maint. DEV The status of the task should be released.


Manual

- Release the to-be-retrofitted TR via tasklist


4

Release the to-be-retrofitted TR via

tasklist of Maint. Project. SOL.200 Solman The status of the TR should be released.


Manual



5


in Impl. DEV via tasklist. SOL.200 Solman




Manual



6

Start retrofit in tasklist of Maint.



the to-be retrofitted TR should be

contained.


Manual



7

Change the coding of the same

report in Impl. DEV manually

according to the coding in the Maint.

DEV, then store it in the target TR

(created in step 5) . SOL.801 Impl. DEV

The coding should be changed accordingly,

and the target TR should contain the

changed report.


Manual

- Manually Retrofitted


8


TR, assign the target TR (created in

step 4) to it, and click on the button

“Additional Functions' -> “Manual

Retrofitted” at the top of the screen. SOL.200 Solman

The manually retrofitted TR could be

viewed by clicking on the button

“Retrofitted”.


Thank you!

solution manager demo

Documents

sap solution manager

popup dialog boxes

comparison result screen

sap standard object

sap standard report

manually retrofitted tr

implementation dev system

create target tr