Professional Documents
Culture Documents
It is essential that changes done in the maintenance landscape will also be applied
to the development-implementation landscape. But the changes must not be
imported directly with the transport requests because of inconsistencies between
the objects of the two different landscapes. Instead of importing the transport
request intelligent tools called 'correction workbench' and BC Sets' will be used.
The correction workbench will import an object into the target system, if it does not
exist there or whenever it can find the exact position for the new parts of the object.
For these cases it will lead to a green traffic light. If such a position cannot be
identified, the new parts of the objects will not be imported, and a yellow traffic
light will be set. For all objects which are not supported by the correction
workbench, a red traffic light will be set.
Configuration
The configurations given are valid for Solution Manager 7.0 EhP1 (SPS18) and
above.
I will be working with the test scenario described in my previous SDN blog "First
steps to work with Change Request Management scenario"
I will add to the previous landscape, Maintenance Landscape, also a
Implementation Landscape in this way:
I will run "Read System Data Remote" to refresh the system data in SMSY, after I will
create the corresponding RFC connections for this client:
And also I will create two new logical components, one for the existing Maintenance
landscape with a new system with role Retrofit:
Development System
Ongoing System
In the task list notice that you need to have two project tracks one per each source
system and a Post-Processing System: Retrofit system
You can change the assignments at any time by starting this task again. Really you
only need execute this if more than one post processing system exists.
Now unlock both your transport tracks by highlighting the line 'Project Track
<project name> Source System <system-client>' and using the right mouse click.
Now is time to work as usual with your project and corrections, see SDN Blog
"Change Request Management scenario: Working examples"
We are going to create some normal and urgent correction corrections:
1. Normal correction for a workbench change request:
SDMJ 8000001143->Created Workbench request SMMK900724->program ZTEST60
In the development system, create e new report and save it in a package which can
be exported (no local object). Use the transport request for workbench you have
just created.
Save
Save
Proceed with your normal corrections as described up to the point that the transport
orders are imported into quality system SMM:200, normal corrections in
"Consolidated" status.
At this point you will see that the available actions are:
Please select one or more systems. This depends on your retrofit strategy.
Working from the task list M*
Now search the post-processing systems in your task list. Unlock the corresponding
utmost task group via the right mouse-click.
In the following dialog you will see the transport request (which must be already
released) of the System DEV maintenance which you created before. Choose this
and enter. Now the changes of report which you created in DEV maintenance will be
transported into DEV implementation and save to the transport request which you
created in DEV implementation. You should see a green traffic light.
Execution of Retrofit-Process
You will see a dialog which shows you the transport requests of system DEV
maintenance. Assign a transport request from the retrofit system (DEV
implementation) which will contain the changes of the post processing step.
Note: In order to be able to assign a transport request from the retrofit system,
SMM:888 in our example, I created two SDMJ and two SDHF for development system
SMM:888 for the same project and created the corresponding transport requests:
- Normal correction for a workbench change request:
For a customizing change I get the two customizing transport request available:
Mark the transport request of system DEV maintenance (where you've made the
changes) and press Retrofit button:
Note: You must allow repository changes for clients in which you would like to create
BC Set for customizing changes. This is a purely prerequisite for BC Set.
This Z-BC Set is created in SMM:100 and also in SMM:888.
So, for a customizing request, we are using BC set functionality to transport the
changes. That means, if the object in this request is not supported by BC set, then
we will not be able to transport it. To check whether a object is supported by BC set
or not call transaction /nSOBJ or see table OBJH for the object type.
Select object you want to examine and double click on the selected object
On the selected TAB you can see all Activation Information for BC Set
So this object is not supported by BC Set functionality. If you try to retrofit such a
transport request that contains this object you will get an error.
And in this case you have to manually transport those changes, there is no other
solution.
On the other hand if the object is supported and still you get activation error, check
if you have performed some deletion in this request but the deletion functionality
has not been activated for BC set, activate the Deletion Functionality:
Start Transaction /nSCPR20 -> Open Menu Utilities-> Choose Menu Item "User
Settings"
Choose Tab "Maint. Transaction" (see below):
Note: If you forgot to activate deletion functionality, then the retrofit will fail. In this
case please activate deletion functionality and delete the old BC-set (and re-create
it manually by following Charm name convention) to process again.
Or manually transport those changes without using Retrofit.
If Retrofit is approved by "Yes" the retrofit Status is updated on the central
Database Table and the Retrofit-List will be refreshed after additional checks and the
Transport Request which has been successfully retrofitted has the Retrofit-Status
"Retrofitted".
For workbench requests the Correction Workbench -> /nSCWB tool is used.
Note: In SCWB, one prerequisite is the object to be modified in the target system
must have the same version as in the original system before the change. Otherwise
it will not be able to locate the places for insertion/deletion/modification. That
means for workbench request you could retrofit only once, because you can only
copy the changes one time.
See a similar screen as followed:
Note: The Critical Retrofit indicates which transport requests contain objects which
cannot be imported directly by the tools used because of:
(1) Object not found due to object check
Note: The concept of using Retrofit to transport workbench requests is to copy the
changes in source system by comparing to its original version, and insert the same
changes to the same object in target system. But there is a prerequisite to make
sure the change can be copied correctly, that is at the time when you perform the
Retrofit action, the object version in system MUST be identical to the original object
version in system before you do the changes. Otherwise there maybe
inconsistencies in the final objects in retrofit system.
(2) Object not supported for BC Set activation
(3) Object Type not supported in Correction Workbench
In a real scenario:
Read notes
1250430 Retrofit usability
1175098 Change Request Management retrofit configuration
996865 Tx SCPR20: Error SCPR 116 occurs during BC set
activation
1044741 BC set deletions
1153253 Customizing distribution - deletions by BC set activation
Retrofit documentation
It can be found in:
http://help.sap.com/saphelp_smehp1/helpdata/en/a3/0aae435a1342e8a56998d83a
797161/content.htm
Copy Changes -> Objects supported in list below
http://help.sap.com/saphelp_sm40/helpdata/EN/b6/6de59f9abc4d17a04ac6486c2e8
b84/frameset.htm
There will be important enhancement for Retrofit functionality for Solman 7.0 EhP2,
I will try to update this blog as soon as this information is available.
Check Consistency
Before you want to start the Retrofit process (post processing) you have the
possibility to check weather the transport request is consistent or not. You can
process the check by selecting an entry and use "Check Consistency" or click on the
icon in column "Retrofit critical"
The following checks will be performed when using this function:
Note Check -> Objects determined from a note in transport request. This request
contains objects from the import of a note. This can cause retrofit problems in the
target system.
The target system can have a different release, with its own note.
The target system does not recognize the changes from the note, and ignores it
because the attribute of the transport request get lost.
You should not import this transport request into the target system, to avoid these
problems. Separate requests for notes and user changes (Workbench und
Customizing).
No transport is selected for retrofit Request
Changes cannot be retrofitted without a target request. The request cannot be
processed.
Assign a request to the selected entry, and repeat the procedure
Check the transport order -> The selection of this transport request does not obey
the release sequence. This can cause inconsistencies and overwrite data because of
overtakers (premature requests) or downgrades (subsequently importing old
requests). Check and correct the selection, to avoid inconsistencies due to incorrect
release sequence. This procedure is logged in a file
Possible order conflicts can appear:
There are transport requests found which have been processed by the selected
transport request.
There are transport requests found which have not been processed by the selected
transport request.
Combinations of the above cases.
Object Check -> Checks if the objects of the transport request can be handled with
the tools the retrofit process is used (Correction Workbench and BC Set). This check
can be ignored when you use the auto import functionality. The prerequisite is that
the object is not changed in the target system (retrofit system)
The following cases prevent an automatic retrofit process:
Object not found due to object check
Object not supported for BC Set activation
Object Type not supported in Correction Workbench
Result: The outcome of this check will be displayed in a log below the retrofit list
Object-List for Transport Request
To get a detailed list of the Objects in a selected Transport Request mark an entry of
the Retrofit-List and use Function "Object-List for Transport Request" or double-click
on the entry you want to display.
Manual: Corresponds to the Category "4" of the object entry and is red colored.
Objects of this category are not supported by the retrofit process and have to
handle by the customer.
A popup appears which indicates that data is not saved if you leave the display.
Cancel: Go back to the display.
No: Leave screen without saving data.
Yes: Save data and leave screen.
Save Data
Customizing Compare
A popup appears which indicates that data will be lost if you leave the display.
Cancel: Go back to the display.
No: Go back to the display.
Yes: No data will be saved and leave screen.
Appendix C
Before EhP1 this project definition was working: