ChaRM: Retrofit

Hi Retrofit,
The new functioanlity "Retrofit" is available in Sol Man EHP1. What is retrofit functioanlity? How is the benefit of this functioanlity?
Your input will be very much appreciated
Thnaks
Kumar

Hi Khalil,
Request for your input to set up the logical component for retrofit functionality.
I am considering two possible ways to implement retrofit.
1. Create one logical component LC1 and the follwoing systems in the logical component:
LC1: SJ1:100 (System Role: DEV), SJ1:200 (System Role:QA), SJ1:300(System Role:PRD), SJ1:400 (System Role: Post Processing).
Note: Post Processing system is a retrofit system.
2. Create two logical componets like LC1 & LC2 with the folowing systems in the logical component
LC1: SJ1:100 (System Role: DEV), SJ1:200 (System Role:QA), SJ1:300(System Role:PRD), SJ1:400 (System Role: Post Processing).
LC2: SJI:400 (System Role: DEV), SJ1:200 (System Role:QA), SJ1:300(System Role:PRD).
Which option will be best to go for retrofit functionality.
Note: Post Processing system is a retrofit system. All the clients are within the same system.
Thanks for the input
Kumar

Similar Messages

Using ChaRM Retrofit?

Greetings, Solution Manager experts.
My company is considering implementing an N + 1 ERP environment: 1 stream for maintenance, and 1 for project work.
At this time, I am trying to assess if ChaRM Retrofit is being widely used in the industry, and what benefits and problems companies have seen with it. From what I can tell, there is not much documentation available on this topic.
Are you using ChaRM Retrofit in an N + 1 SAP landscape?
If so, has your company see a benefit to using this product?
Can you offer any tips or watchouts to implementation?
Thanks in advance for your help.

Hi,
Here are the information i collected about his topic. (hard to find information about that) :
Prerequisites :
A retrofit system must exist in the Maintenance Project (role type : Post Processing system). It should be a development system of an other project, for exemple an implementation project.
The task list of the maintenance project will now have two new tasks :
--> general tasks --> Assign Post Processing system to development system
--> Track section --> Post Processing --> retrofit systems --> start retrofit
I wish i could give clues for further research
Regards

ChaRM:Retrofit system level

Hi Team,
I am implementing retrofit functionality in ChaRM. Currently i am using Sol Man EHP1 ST Level: SAPKITL433. I am working with ECC landscape (ECC 5.) to test retrofit functionality (DEV,QA,PRD & Retrofit). What is the software component level required in the ECC systems to implement retrofit?
Regards
PSK

According with note 1040612, you can use this function with the following SAP_BASIS releases.
     SAP_BASIS
          SAP Basis component
                                               710          - 710
                                               700          - 700
                                               610          - 640
                                               46A          - 46D
Check this note too
1066123

Cross System Object Lock with ChaRM Retrofit

Hi-
I need to know if there is the ability to have a cross system object lock while utiliziing Retrofit within ChaRM. For example I am working with an N, N1 landscape. When I release a transport request in N I need the object to be locked in the N, and N1 (after retrofit) landscapes.
Will this be supported with both Workbench and Customizing requests?

I dont believe this is possible at the moment. As you must be already aware, that SAP releases the locks from the objects as soon as the transport request is released from the Development System. Unless, this locking mechanism is extended to various systems first (DEV and QAS) and later to parallel landscapes (eg:- Project landscapes) it would be difficult to bring in this feature.
Rgds,
Abhijeet Bhagat

ChaRM:Retrofit:TMS set-up

Hi team,
In STMS, How to set-up transport path for retrofit client? I have already set-up transport path for DEV, QA and PRD to activate standard ChaRM. Is the existing transport path to be modified to include retrofit client?
Note: I am working with ECC sandbox to test retrofit (within ECC sandbox system, i am creating four clients DEV,QA, PRD & RETROFIT)
Thank you
PSK

hi
chk this link
[http://help.sap.com/saphelp_smehp1/helpdata/en/a3/0aae435a1342e8a56998d83a797161/content.htm|http://help.sap.com/saphelp_smehp1/helpdata/en/a3/0aae435a1342e8a56998d83a797161/content.htm]
jansi

Charm Retrofit Test in SM 7.1

When in 'To be Tested' state, 'Confirm Successful Testing', it prompts the following warning message, and status remains in 'To be Tested state.
1) Status was reset by system
2) No import into test system has taken place
3) Transport request is not flagged for import into production
Please suggest the Correct note or Steps to solve this errors

Hi,
Can you tell us if your transport imported with error in QAS system?
If yes,then in SCMA you can click on 'Correct import(repair flag)' button. It will give you the list of transports that went in error for all (*) users in QAS or PRD systems. Then you can select the transports one by one and click 'error corrected' button.
After this you can try again to change the status of CD to 'Successfully Tested'.
If No,please check the job log of collector job SM:TMWFLOW_CMSSYSCOL and see if it is running fine.
The production import queue doesn't get updated with QAS transports due to failure of mentioned job,so when you are scheduling import job it may not be getting any transport to import.
Also, if you have 5 system landscape and you are moving the changes to QAS system of N+1 landscape, and because of ChaRM configuration, changes are not yet allowed to go in import queue of N landscape ,then we get such warnings.
Hope this helps.

Not able to create a Task List for Charm Retrofit

Hi All,
we are trying to implement retrofit for our client. Created two projects one for implementation and one id maintenance and defined the system landscape for both.
I have checked the RFC connection for all the systems involved and all works fine. IMG projects are created successfully for both.
Problem comes when we are creating a maintanance cycle or task list after activating the change request management. We always get a logon screen after giving the name of task list and press ok. First we thought it could be the trusted RFC issue but trusted RFC for the current user is working fine.
Could anyone know what is the problem and if you faced the same issue pls share your experience what all did you try to rectify it.
Thanks
Tripti

Hi,
BC sets are active. I have already checked, it ended up in warning but its general we can avoid it. One thing which we found out was thi error when I am checking the application log for the project
System cancel RFC destination SM_GTDCLNT020_TMW, Call TMW_SET_PROJECT_SWITCHES: No authorization to change file /usr/sap/gttrans/a ctlog/GTDZP000XX.GTD
I don't understand what exactly is this error about but informed the authorization team regarding this.
Any idea?
Thanks,
Tripti

ChaRM Scenario: Workbench and Customizing CR in the same Change Document

We use the ChaRM scenario of Solution Manager 3.2 to manage the transport request for the R/3 landscape.
We have two different project with two different landscape:
- the first one is used for customizing purpose ED1/010 - EQ1/010 - EP1/010
- the second one is for workbench purpose ED1/011 - EQ1/010 - EP1/010
We usually assign a Change Request each Change Document.
Assigning the Change Document to a maintenance cycle (owned by a SolMan Project) to assigne the CD/CR to the right source client.
Sometime we need to create a Change Document that contains two CR one for customizing purpose the other one for workbench purpose.
Is this possible using ChaRM standard features ?
Regards,
Giampaolo

Hi Martin,
Solmaniacs' assumptions are correct. You can have as many source clients as you want.
As long as
- STMS configuration (transport routes, and domain links) are consistent
- SMSY configuration (logical components are declared properly with assigning the right role types to systems/clients)
- Project declaration are done correctly (so that from Solman solar_project_admin you can read the STMS as confiured in the distant STMS domain)
- IMPORTANT: those configuration GO ALONG with each other !! (SMSY should nt contradict STMS for example...)
The tasklist that is generated for each Solman project will be as follow
- Node 1: Header Tasks (commun to all systems)
- Node x: Corresponding to track x declared in Project (each Source System will have his own node with the corresponding track under)
- Node x+1
- Node ...
- Last Node : Tasks for Tasklist closure - checks on scma consistancy and CTS projects closure
So you'll always have n+2 nodes in your tasklist; n beeing the number of declared source (=dev) systems in project
For each action launched from change docuemnts like creation of TR, release of TR or Retrofit (as Solmaniac said) you'll have an additional pop-up that will appears letting you choose the system you want to use for the action
Hope its helpful
Regards
Khalil

Retrofit issue

Hi Experts,
We have created TR in SE2:300 (SE2K900212) and after releasing it, we have got Transport Of Copies (SE2K900214). Now object which is relevant with Zpackage25 under this TR, we want that to move to SE2:200 client through automatic retrofit process, which we are trying to do.
But while doing this, it prompts us for error message saying TR in SE2:200 (SE2K900215) –“Choose a change request with target system SE2.400 “ and after checking logs it says- “However, the objects you edit can only be recorded in change requests with the target system SE2.400.
The correct target system is determined from the package and transport layer to which the object concerned belongs”
We don’t want target system of 200 to be changed to 400, 120 is correct client, but I believe Zpackage25 or relevant Transport layer having some issue in not recognizing this package ,
Can you please let me know how I will be able to take care of this?
Thanks,
Asad

Hi,
This is the complete scenario:
Our Solution Manager system DM2 is on Solution Manager 7.1 SP 07.We
have Connected our Solution Manager system to Satellite system SE2(ECC
System) and we have configured ChaRM in this Landscape for SE2
satellite system.
In our SE2 Satellite system, we have built "Implementation Landscape"
and "Maintenance Landscape" as below for Prototyping "Retrofit
Scenario".
Maintenance Landscape:
SE2/200(Dev) -> SE2/120(QA) -> SE2/110(Pre-Prod) -> SE2/100(Prod)
Implementation Landscape:
SE2/300(Dev) -> SE2/400 -> SE2/100(Prod)
We have followed the below steps for recreating "Auto-Import" Scenario
in Retrofit
1) Create a Transport Request in SE2/300 from Task List and save some
Example Objects in the same. The Task List has been created from the
Project containing the Logical Components of both "Implementation
Landscape" and "Maintenance Landscape" with SE2/200 being identified as
the "Retrofit" system.
2) Release the task of this Transport Request from the Satellite system.
3) Release this Transport Request from the Task List.At this stage,
Transport of Copies(ToC) is generated.
4) Create Transport Request in SE2/200 from the Task List.
5) Start "Retrofit" from the Task List.When performing this task,we are
receiving the following Error message after selecting the "Retrofit"
Transport request in SE2/200.
"Choose a Change Request with Target system SE2/400".
This is the error we are getting:

Using Charm at cutover to handle deleted objects

Hello experts,
System landscape contains of dual landscap meaning one project ladnscape and one maintenance landscape.
Project: D01>T01>Q01 ( no charm )
Maint: DEV>QAS>PRD ( charm is used )
At project Go Live cutover is done från Project line Q01 to Maint DEV.
All transports imported in Q01 is added manually to import queue of Maint DEV and imported.
After that 1 WB request and 1 Cust. request is created via charm and all objects from the
cutover transports imported are added to those chamr transports. Then charm handles the
transport process through the maint landscape up to production.
Problem
=======
If cutover transports contains deletion of objects, the transports are imported to DEV maint, object is deleted.
When including all objects from cutover transports into the two charm transports it will then ofcourse fail during
releae of the transports on the deleted objects as they no longer exist in DEV maint. This is of course not a specific
charm problem but a TMS problem. Or not even a problem it is as it should be.
Question
========
Is there any way of handling this scenario, can charm in any way handle this ?
Thanks,

I checked the link you provided and that descibes as you say a dual landscape but i don't think it will solve this problem.
As i understand you setup the retrofit process one-way and that would be Maint DEV --> Project DEV.
That is all fine keeping all changes done in maintenance landscape in synk with project landscape.
But the cutover process is manual, as also the drawing states, meaning adding project landscape transports
to Maint DEV system import queue and import them. But if a transport contains objects with the delete flag it will be
deleted in the Maint DEV system. All fine that far. But when you then inlcude all cutover transports objects into a charm transport it will not check if object still exist in Maint DEV system ( wich it does not anymore ), it will include evertyhing that is part of the cutover transports. Meaning you include objects with delete flag on it. When you release this now in Maint DEV system what it does is to check if object exist in TADIR, it does not. You can fool this release process by manually create an entry in TADIR, release the transport, then delete the entry in TADIR. But if you have cutover transports with many deletions, then this is not the way to go.
So please explain how the retrofit procedure would help in the scenarion at cutover and delete flag.
Thanks.

Has anyone implemented ChaRM in a 4-tier or 5-tier landscape?

Iu2019ve setup ChaRM with a 3-tier landscape DV1-QA1-PRD and everything works as advertised. I used the transport route, DV1/120 -c- /QA1/ (clients 149/150) -QA1 -d- PRD/150. Where -c- is a consolidation route and -d- is a delivery route.
Now I need to do a proof of concept to see if I can get CHaRM to work with our current landscape. We have a dual development path and need to make sure we sync our DEV and QA systems. The lanscape Iu2019m trying to use is DV1-QA1-PRD-DV2. The transport route Iu2019m trying is DV1/120 -c- /QA1/ (clients 149/150) -QA1 -c- PRD/150 -d- DV2/120. Iu2019ve tried various combinations and the only way I can get it to work is DV1/120 -c- /QA1/ (clients 149/150) -QA1 -d- PRD/150 -d- DV2/120. When I release and import into PRD it goes to both PRD and DV2. While this gets the transport to my support dev box I need to have another step in the workflow. What Iu2019m looking for is the workflow to act like dev-qa-qa-prd.
Has anyone setup a 4-tier or 5-tier landscape with release and import steps between each system? If so what did you use for your transport route and were they other config changes needed after the route?
Thanks for your time.
Jeff

Hi Jeff
Have a look at these
http://help.sap.com/saphelp_smehp1/helpdata/en/a3/0aae435a1342e8a56998d83a797161/content.htm
/people/dolores.correa/blog/2009/08/27/change-request-management-scenario-retrofit-functionality
Hope it helps
Santosh

ChaRM: usage of ChaRM and none-Charm transport strategy

Hi ChaRM-TMS Gurus!
We have the following [SAP system landscape |http://www.file-upload.net/view-1086963/SDN_TMS_Ist_Soll.jpg.html] and would like to use ChaRM approach simultaneously.
What are the minimal requirements concerning transport layers/routes, which settings should be changed?
How much and which transport layer/routes does ChaRM need?
a) 1 any new transport layer/route
b) standard transport layer, transport layer "SAP" and others
Should all the standard transport layer/routes from virtual systems to real QAS and PRD systems or can I start as follows:
1) Leave the current TMS settings unchanged
2) Activate the extended transport control
Result: the current setting will be client specific and all the old transport requests will be moved to client specific transport routes
3) change the transport strategy (from mass transport to single transport)
3) Define new transport layer
4) Define new transport route for SAP objects from DEV to QAS
and assign the transport layer from 3) (client specific)
5) Define new transport route ZXXX from DEV to QAS
and assign the transport layer from 3) (client specific)
6) Define the delivery transport route from QAS to PRD (client specific)
7) activate and distribute the settings
Thank you very much indeed!
Thom

Hi Martin,
Solmaniacs' assumptions are correct. You can have as many source clients as you want.
As long as
- STMS configuration (transport routes, and domain links) are consistent
- SMSY configuration (logical components are declared properly with assigning the right role types to systems/clients)
- Project declaration are done correctly (so that from Solman solar_project_admin you can read the STMS as confiured in the distant STMS domain)
- IMPORTANT: those configuration GO ALONG with each other !! (SMSY should nt contradict STMS for example...)
The tasklist that is generated for each Solman project will be as follow
- Node 1: Header Tasks (commun to all systems)
- Node x: Corresponding to track x declared in Project (each Source System will have his own node with the corresponding track under)
- Node x+1
- Node ...
- Last Node : Tasks for Tasklist closure - checks on scma consistancy and CTS projects closure
So you'll always have n+2 nodes in your tasklist; n beeing the number of declared source (=dev) systems in project
For each action launched from change docuemnts like creation of TR, release of TR or Retrofit (as Solmaniac said) you'll have an additional pop-up that will appears letting you choose the system you want to use for the action
Hope its helpful
Regards
Khalil

ChaRM for a 5 system landscape

Hi all,
we got a requirement to implement charm for 5 system landscape. but the problem is
currently the scenario followed for the rollout is
1. AA(DEV-proj)--> BB(QUA - proj)
Then the TR is forwarded from BB system to the maintenance landscape
DEV>QUA> PROD
they don't want to implement retrofit functionality.
is there any way we can mapp this scenario to charm.
kindly advice in this regard.
Thanks,
Subhashini.

Hi Ragu,
Thanks for the reply.
currently a two systems are separated from the maintenance landscape.
they are forwarding the TRs to the development system.
is there any way we create 2 tracks.
1. AA-BB-DEV-QUA-PROD
2. DEV-QUA- PROD
again i not having a clear idea on how to differentiate the tracks as both leads to the same production system.
or is there any way develop a custom method for forwarding this TR to the DEV system.
kindly sugggest on how to go about.
Thanks ,
Subhashini.

Query on ChaRM control on BAU v/s Project landscapes

We have Business-as-Usual landscape(DEV, QAS, PRD) which is controlled by ChaRM (maintenance project). To this environment, we plan to add a project landscape with Dev(P) and QA(P) systems for project activities.
Can we use BAU Solution Manager - where ChaRM is configured - to control developments in project landscape and later cutover respective project transports to BAU landscape?
Thanks in advance,
Shaji

Hi Invycktus,
Thank you very much for your quick reply. I have seen the blog on retrofit functionality. The retrofit procedure assists in moving BAU changes to project landscape.
My query is on sort of "reverse retrofit" I mean, can I create an Implementation Project in BAU Solution Manager as follows?
Dev(Prj) --> QA(Prj) --> Test(Project) --> DEV --> QAS --> PRD
Please note, DEV --> QAS --> PRD is already controlled by a Maintenance Project for BAU support. Can the implementation project and maintenance project co-exist on same Solution Manager for same SIDs?
Thanks again,
Shaji

Do your company use Retrofit function in ERP Landscape

Hi Charm experts,
I work in Vendor company and one of our customer plans to start using Retrofit during ERP Ehp upgrade project.
We both like to know does someone have experience how Retrofit works in real world. If you are using Retrofit could you share your experience:
- does it help when you do dual development maintenance
- does it save time?
- Have you got problems with it?
- Do you recommend it to us?
- Who will use Retrofit, developer?
Thanks very much if you have time to write you experiences.
Best Regards,
Leena Nissilä

Hi Nilanjan,
I tried it in Default logic and also in UJKT. Did you successfully use this function before? If so, can you please explain how you used it?
Thanks
Sankar

ChaRM: Retrofit

Similar Messages

Maybe you are looking for