System landscape changes after activating charm

I need to change the system landscape on a maintenance project. I need to add an additional QA client to the project landscape. I have open change requests that I can not move to production yet so I can not complete the project. I have created another project and tested forcing the cycle closed and creating a new cycle, but the change docs are associated to the old cycle number. I have followed the steps in the charm FAQ for closing inconsistent project cycles (note 933705), but I couldnu2019t re-associate the change docs with the new cycle or project. I would think the need to change the landscape when you have open change docs would come up fairly often. If someone has successfully done this would you please provide the steps?
Thanks
Jeff

Hi Jeff,
ChaRM supports the logical component changes and also with modifiable transport orders.
Please take a look at the following link:
Change Request Management scenario: Usual questions and known errors
/people/dolores.correa/blog/2009/07/22/change-request-management-scenario-usual-questions-and-known-errors
6. Changes in the logical components of a project where Charm is already activated
8. Completing a task list
A task list can be closed even with modifiable transport orders according to note 1071412 "Completing a task plan with changeable transport requests".
Then when you create a new cycle, the system automatically assigns these processes and objects to the new cycle. This is also logged in application log. To display the log entries, you can use transaction /TMWFLOW/MAINTINST. Navigate to the tab with your project type (usually the maintenance project) and choose 'Create...' and 'Execute'. Then select the required project and choose 'Messages at Time of Creation'.
Other related notes: 1354638, 1344191 and 1158885.
Best Regards
Fernando

Similar Messages

Six system landscape configuration in SAP ChaRM

Hi,
Our requirement is such that we need to connect six system 3 developments, 2 testing and one production to the charm configuration.
DEV1---> DEV2 -
> DEV3 -
> QUA1 ---> QUA2 -
> PRD
How to achive to achive this, we donot want to add simply the systems in the task list. How to modify the standard message status in CHaRM flow so that a change request created in DEV1 reaches DEV2 only when it is released and we get message status as "transported to DEV2 " and simillarly for all the other systems.
Advance thanks for all those reply.
Best regards,
Vin

Hi Nesimi,
Thanks for your reply,
We want the system options to be displayed in the change request status message itself.What i mean is once development is completed in DP1, we should get a option in the change request to " move to dp2 ". Simillarly we have two quality systems after complete development, we desire to have the option of selecting the quality system in the change request action tab itself
Best regards,
Vin

Can an ODSs DB Tablespace Assignment be Changed AFTER Activation.

Is it possible to change the DB Tablespace Assignment for an ODS once that ODS has been activated and data loaded to it ? I know this can be done for an InfoCube. I realize that all previously loaded data would have to be deleted, and then reloaded after the reassignment.
Thanks for your input !

We have some of our large ODS's in separate tablespaces. The creation predates my involvement so I'm not sure whether they were created in a separate tablespace originally or not. I would doubt they were just because I don' think during the originally setup, anyone had an idea of data volumes for any particular ODS to have made the decision to put it in a separate tablespace.
The DBAs should be able to move the table to the new tablespace. Question is what needs to happen on the SAP DDIC side. You need to be able to change the tablespace settings for the ODS but not cause any sort of impact to the table.
When I get back to the office I'll check a few things.
Message was edited by: Pizzaman
BR*SPACE should allow you to move the reorg the table to another tablespace. SAPDBA for older systems.
http://oraclesvca2.oracle.com/owsf_2003/40041_Klokkers.ppt
SE14 allows you to change the Technical Settings for the tablespace - won't alter the space, but will allow you to make sure the SAP DDIC settings agree with where the table actually is.

ChaRM - Mainenance Cycle in two system landscape - possible?

Hi Experts,
we are trying to create a maintenace cycle with two systems.
We have a system defined as "Evaluation System" and the second is defined as "Production System".
Generally Question
Is it possible to create a maintenace cycle for a two-system-scenario?
Specific Question - Erorrs/Warnings
While checking the project we got several errors/problems:
1 Differences between BC Set SOLMAN40_CHARM_BASICFUNC_001 and database
2 Differences between BC Set SOLMAN40_SDESK_BASICFUNC_000 and database
3 No consolidation system found for EID-800 (project Z_CRM_T)
4 No track for project Z_CRM_T with log. system EID/800
5 Message from function module /TMWFLOW/CHECK_PRJ_CONS: No export system for CBI-001
CTS
The transport system is configured correct - Check in STMS is OK
Question:
The comparison checks seem to be OK - is it necessary to reactivate the BC Sets?
Kind regards
Tom

Hi,
the system role for your client/systems in the logical component is very important:
- The development system needs to be defined as a Source System.
- If you don't have a QA, leave all target systems empty. If there are one or more consolidation/integration/regression systems, assign them to system role Target System.
- Your production system uses system role Production System.
The defined Development client needs a client dependent (TMS parameter CTC=1) consolidation track to the QA, or in a 2 Tier landscape to the production system. In a 3 Tier landscape you need a delivery track from QAS client to your production client. But as you wrote, TMS has been set up already. I just would like to mention all steps....
Check that all RFC connections have been set up correctly. Especially the Trusted RFC. Don't forget the Trusted RFC to client 000 ot the TMs domain controller.
In tab Systems ( transaction code SOLAR_PROJECT_ADMIN => System Landscape ):
Make sure you see all clients of your logical component. If not hit button System Role Assignment and add your System role.
Then still in the same tab: Hit button Shipment Routes and make sure, you see the complete transport track and only this track here!
After correct setup of TMS, RFCs, logical components and assignment of LC to your project:
First perform a Refresh and a Check in transaction code SOLAR_PROJECT_ADMIN => System Landscape => Change Requests. Then please recreate the maintenance cycle (and task list).
Regards,
Holger

Warning: Problems occurred during synchronization of the system landscape

Hello
I have created systems in system landscape, TMS is working fine, all the configuration steps are completed successfully.
am working in Solution Manager 4, in project change -SOLAR_PROJECT_ADMIN - Project Administration - in 'System Landscape' tab  Change request and when I activate change request management I am getting following messages:
1. Warning: Problems occurred during synchronization of the system landscape
2. The project is not released. Hence cycle can not be created.
Its bit urgent as I m in middle of this activity, please assist me on the same
Thanks
Sharmishtha

Hello Jason & Prakhar
Thanks for your quick response. I am basis person, and configuring this change request management for one of the project.
Jason:
Will you please check with your basis person about these settings and let me know the same. I have set the settings as follows
C= Development (source system)
T = Quality
P = Production
Prakhar:
I have checked with all RFC connections are working fine, authorizations are also properly given.
I didnt get your point No correctly defined maintenance project exists, I have already created project in project administration transaction, assigned the system landscape, I have activated project IMG in IMG Project and then going in change request tab to activate the change request management, where its giving me above error.
More over, as you have mentioned I am getting following message in SLG1:
Project CHARM_GBW not found in the project administration table
This is asking me to do following things:
Synchronize the project in Change Manager with the Solution Manager. Call the Solution Manager with the transaction SOLAR_PROJECT_ADMIN, and go to the 'System Landscape' tab, and then the 'Project Cycle' tab. Select the 'Change Request Management' field, and choose 'Refresh'. Project CHARM_GBW should then be available.
Where do I have to make entry for this? I can see the entry in /TMWFLOW/PROJMAP table too. I dont know what more I need to do for this.
Problem is I cant see Project Cycle tab in System Landscape. Prakhar, frankly I am not able to find any step wise document on this part. So will you please help me with some documents on this? I am from technical side thus there is bit difficulty to understand this scenario from functional view.
I will be grateful for your help,
Thanks
Sharmishtha

Project landscape and system landscape

hi all
what is thifference between system landscape and project landscape??
anil

Hi Anil,
System landscape:
They system landscape basically is the set-up or arrangement of your SAP servers. Ideally, in an SAP environment, a three-system landscape exists. A three-system landscape consists of the Development Server-DEV, Quality Assurance Server-QAS and the Production Server-PROD. This kind of set-up is not primarily designed to serve as server clusters in case of system failure, the objective to enhance "configuration pipeline management".
A Typical SAP Three-System Landscape.
At this juncture, it is important to state that a test system - Sandbox can also exit separately. The essence of the sandbox is to test the configuration of the business processes of a company, especially at the inception of the project (before the Business Blue Print is signed). It can also serve as a practice environment, even after go-live.
Pipeline is the environment where the configuration in the development system is moved to the quality assurance system and finally to the production system. The whole idea is to ensure that the configuration of these systems is in sync at any point in time. Suffice to say that, configuration/changes are first made in the Development system, thoroughly tested in the Quality Assurance system before been loaded into the production (Live) system.
This approach throws up the transport management system concept. Transport management system is the coordination of the movement of objects and configuration changes from the development system to the Quality Assurance system and then to the Production system. At times, this sequence of movement is not possible, especially in cases where an SAP note mandates that changes be made directly on the production system.
In such rare cases, objectively confirm that the change transport cannot be performed. Very likely, your system must have been configured to "not modifiable" (a system locking strategy that enforces the three-system landscape change transport rule); unlock the system by changing the global setting option to "modifiable" using transaction SE03. After you have done that, effect the change(s) on the system. Immediately lock the system back by changing the global setting option to "not modifiable" using transaction SE03. Replicate the changes on the other system. Note that transaction SCC4 can also be used to lock the system so that client dependent and independent configuration changes are not carried out directly on the production system.
By and large, the SAP system landscape ensures that the integrity of data is enhanced via enforcing a controlled configuration changes effect on the target system - production.
Project landscape:
It's about the kind of soultion customer would be implementation in his project. Like CRM, SCM, ERP.
Reward points if it helpful.
Thanks & Regards
Sasikanth.Ch

Best practice: Webdynpro in a large system landscape

Dear Sirs,
I have a few questions about using Webdynpro (WD) in a large system landscape. After doing some research I understand there are a few alternatives, and I would like to get your opinions on the issue and links to any relevant documentation. I know most of my questions do not have a single answer, but I hope we can get a disussion, which will highlight the pro/cons.
My landscape consists of a full set of ECC and portal servers (DEV, QA, P) , where using WD to fetch BABIs from the backend and present them in the portal is a likely scenario.
Deploy the WD components on portal servers or on separate servers?
Would you deploy the WD components on the portal WAS or would you advice having a (or a number) of servers dedicated to running WD.
The way I see it, when you are having a large number of developers, giving away the SDM password to the portal server (DEV) in order for them to test WD applications is not advisable (or perhaps more true, not wanted by the basis). So perhaps a separate WAS for development of WD is advisable, and then let basis deploy them into the portal QA and PROD server. I do not think that each developer having its own local J2EE for testing is likely.
How about performance?, will any solution be preferable over an other. Will it be faster/slower to run WD on separate WAS.
Transporting the WD components
How should one transport the components and keep them pointing to the right JCO connections (as you have different JCO connections for (DEV, QA, P)), I have seen example with threads where you opt for a dynamic setting of the JCO connections through parameters. Is this the one to prefer?
Any documentation on this issue would be highly appreciated. (Already read: System Landscape Directory, SAP System Landscape Directory on SAP Web AS Java 6.40)

Look into using NWDI as your source code control (DTR) and transport/migration from dev through to production. This also will handle the deployment to your dev system (check-in/activate).
For unit testing and debugging you should be running a local version (NWDW). This way once the code is ready to be shared with the team, you check it in (makes it visible to other team members) and activate it (deploys it to development server).
We are currently using a separate server for WD applications rather than running them on the portal server. However, this does not allow for the WD app to run in the new WD iView. So it depends on what the WD app needs to do an have access to. Of course there is always the Federated Portal Network as an option, but that is a whole other topic.
For JCo connections, WD uses a connection name and this connection can be set up to point to different locations depending on which server it is on. So on the development server the JCo connection can point to the dev back-end and in prod point to the prod back-end. The JCo connections are not migrated, but setup in each system.
I hope this helps. There is a lot of documentation available for NWDI to get you started. See: http://help.sap.com/saphelp_erp2005/helpdata/en/01/9c4940d1ba6913e10000000a1550b0/frameset.htm
-Cindy

URGENT: Changing System Landscape in ChaRM

Ok...here is our situation:
We use ChaRM with a 3 tier system landscape (DEV > USER > PROD).
Out USER system has been down for a month (maintenance) so we went live with ChaRM as follows:
DEV > PREPROD >PROD
Our USER system is now back up and running so we have replaced the Logical Component on the project to reflect this. This has worked ok but the task list is still showing the old system landscape. i.e. its showing PREPROD still instead of USER. How do I resolve this?
Do I have to complete the existing cycle and then create a new one? This would be fine except I would lose all the jobs I have scheduled in the task list (schedule every 15min EVERY day....took me ages).
Any suggestions?
Thanks!!!!!!!!!!!!

Hi,
About this issue, there is a detail information about this in blog point 6 u201CChanges in the logical components of a project where Charm is already activatedu201D.
This is the link: http://www.sdn.sap.com/irj/scn/weblogs?blog=/pub/wlg/15116
So, you have to change the transport route accordingly and then close current maintenance cycle and generate a new one.
Following is the steps.
1: please import all the transport requests which were associated in the current maintenance cycle task list by STMS manually import.
1: change transport route from DEV > PREPROD >PROD to DEV > USER > PROD on the domain controller system.
2: close current maintenance cycle.
3: change the system landscape to DEV > USER > PROD in solar_project_admin.
4: generate a new maintenance cycle.
Thanks
Regards,
Vikram

ChaRM with 4 system Landscape.

Hi, 
We are trying to implement ChaRM in a four system landscape 
 
AFD --> AFQ --> AFI --> AFP 
 
defined logical components, project, created maintenance cycle. U'gent correction works fine. 
 
but for regular correction, we are able to create TRs release it, but not getting imported into AFQ and of course further steps are not happening. When the status is "Development Completed", we perform "Log on to system", this pops up with a dialogue with options 
 
AFQ 200 
AFI 100 
 
to logon to system. 
 
This is the only clue we got. 
 
When we perform the actions, the status keeps changing and goes to status "Production". It doesn't obey the phases maintenance cycle as well, irrespective of the phases the status keeps changing and goes to status "Production" 
We are missing some minor thin's. 
 
Have we defined the system roles properly? IF not, how does the flow works perfectly fine with respect to U'gent correction. 
 
Please help. 
 
 
Regards, 
Ragu 
 

Hi Ragu,
I have a few questions here:
1. What normal correction type are you using - SDMI or SDMJ
2. What roles are assigned to the systems in Logical Components? I believe they are setup as Target Systems and thats why you get the pop-up with both systems when you execute 'Logon action' after 'Development Completed'
3. What is the STMS setup for this landscape?
4. Urgnt should behave properly coz it takes the shortest route to production. Can you check the tasklist of Urgnt and see if there are only 3 systems there?
Regards,
Kriti Bhalla

Charm configuration for a 4 system landscape

Hi Experts,
We are planning to implement charm for a 4 system landscape: Development Server, Integration Server, Quality Server and Production Server.
We could configure TMS related steps, activated Charm in Solution Manager, created a maintenance project in solar_project_admin.
However, the standard delivered transaction types like Normal correction and Urgent Correction are not working in a 4 system landscape. They are only working for 3 systems (DEV, QAS and PRD).
Are there any documents or blogs that would specially explain all the steps required for 4 systems? Any kind of help would be highly appreciated.
Thanks,
Ravali

Development --> Integration --> Quality --> Production.
First, I will import the transport of copies into integration
Yes, and you test the changes here.
Second, the whole transport is released and imported to Integration - in the Test phase of the maintenance cycle and NC status being consolidated.
Third - Now, keeping the maintenance cycle in the TEST phase and NC phase in consolidated, will I be able to schedule the transport into quality server?
Nope. You consolidate your normal correction, which releases your original transport and import them into Integration, and then immediately into Quality (you already proved it worked in Integration) BEFORE you set the phase to Test. Otherwise the original transports are NOT released. And if you set your phase to Test before importing the originals, you'll get a message that you cannot import transports into Quality during this phase.
If you need to get transports into Quality for break fixes during the Test phase you need to use a Test Message and these are imported during Go-live as well.
Fourth - if the above process works, I will then change the MC to Go Live and schedule the import to Production.
With the corrected process mentioned above, yes, you will then change the phase to Go-live and it will import everything that was brought into Quality.
Hope this helps.

ChaRM in two system landscape

Hello Everyone,
I want to implement ChaRM for BIW systems which is a two system landscape: BIWDEV and BIWLIVE . Is it posible to implement ChaRm in a two system landscape /we need three system landscape only for it.I started the ChaRM configuration work but faced certain issues over which i was told tat Charm needs three systems for implementation. Kindly plz suggest and confirm.
Regards,
Somya

Hey Somya,
2 system landscape will also work with CHARM.
CHARM can also be configured in single system landscape.
But the bottomline is you require in all 3 clients to realize charm.
These three clients can belong to same or diffrent systems altogether.
For you i would say, u will require 2 clients in BIWDEV system ( Say BIWDEV:100 as development cleint and BIWDEV:200 as Test client ).
Now you have BIWLIVE system which is our production system, so you require 1 client BIWLIVE system..
So your 3 clients are ready and Change Request management can be realized..
Please Reward with points if this postv was usefull..
Revert For ne clarifications ..
Regards,
Suzzane

Change Request Flow In a Three System Landscape --- PLZ DO REPLY

Hi Experts,
I am new to SAP and have this doubt;
Suppose we have a three system landscape with DEV, QTY and PRD systems in it.
Say we create a new change request in DEV system. So to transport it to QTY we will release that request from DEV using T code se01 .
Now the request will come in QTY systems queue and we will login to the appropriate QTY client and import this request into the QTY system.
No my basic doubt is, after the testing in QTY how do we move this request to PRD system ?
Do we again release this request from QTY system using se01 or we need to go at the OS level in the QTY system and manually add this change request in the PRD system buffer ? ( Please send if any reference link is there)
I will really appreciate any info in this regard.
Thanks in advance.
Regards,
Mandeep

Hai Mandeep,
 First Thing,
 -->If you are maintaining a common transport directory,the released change
 request will be exported in that common transport directory..
 --->Now you just enter in to the server(which is Transport Domain
 Controller).
 --->In that go to Import Overview,now your QA server has one import req.
 you just click the req. and import that req..
>Now if you want to import the same req int o PRD.,Enter in to PRD
 server.Go to tcode STMS_IMPORT, In the top go to
 Extras>Other req.>add..click this and add that particular
 req.that you want to import in to PRD server..
 --->select that req and import that req...
Thanks & Regards,
Gopinathan.T

4 System Landscape // ChaRM // No Export System found

Hi Folks,
I got some problems with a 4 system landscape in ChaRM.
The error message I get when doing a consistency check within my SMI project is:
Message from function module /TMWFLOW/CHECK_PRJ_CONS: No export system for NWA-303
Message no. /TMWFLOW/TRACK_N159
Transport route should be as follows:
DEV -> QAS -> INT -> PRD
Since I am still in testing phase I used clients instead of real systems in my configuration (TMS, Logical component,....)
My configuration looks like this:
NWA client 300 -> 301, transport layer ZCHM, transport layer SAP, consolidation
NWA client 301 -> 302, delivery
NWA client 302 -> 303, delivery
Logical Component defined as follows:
Developement System (Source: SAP): NWA:300
Type of Role: D Source System
Quality Assurance System (Source: SAP): NWA:301
Type of Role: O Target System
Integration System (Source: User): NWA:302
Type of Role: O Target System
Production System (Source: SAP): NWA:303
Type of Role: P Production System
Anyone got an idea what is wrong? did I miss anything?
The same configuration works for a 3-tier Landscape (without Integration System).
Any help is appreciated.
Thanks.

Hi Raquel,
Ours problems with RFC and with connections had be corrected with the note below:
1833778 - Activate Change Request management - Check error
Thank you very much!!
Adriana

CHARM with a 2 system landscape

Hello ,
we have only a 2 system landscape for our ERP systems.
When I now click on the check button on the maintainance project. I receive an error :
No consolidation system found for DEV-001 (project TEST_CHARM)
No track for project TEST_CHARM with log. system P23/001
Message from function module /TMWFLOW/CHECK_PRJ_CONS: No export system for DEV-001
TMS ( without any client routes)
DEV->PROD
Any suggestions ?
Regards

Hi Daniel,
we are using CHaRM in various transport landscapes with 2 and up to 5 systems. This is all working fine. Please make sure there is a consolidation transport route from DEV, also all RFC connections from Solution Manager to your Transport Landscape are set up, inlcuding 000 clients.
TMS settings need CTC=1, and Trusted Services in STMS need to be activated.
Other prerequsites are:
- Systems are deined in SMSY
- Transport Domain link between Transport domain controllers
- Logical components defined in SMSY (with correct system roles)
- Lofical component added to SMI project
If this is all fine, please hit button "Shipment Routes" in SOLAR_PROJECT_ADMIN in tab page "System Landscape" => "Systems" You should see all transport routes required for this project.
If this works, you are in a good shape.
Best Regards,
Holger Slomka

4 system landscape - ChaRM

We are implementing ChaRM in Solution Manager with 4 system landscape.Our requirement is :
Client need staging between quality system & production system.
Dev ---> Quality -
> Staging -
> Production system.
My query is : Once we create this staging system what needs to be done from technical side. Do we need any workflow customization or BAdi implementation.
Please provide some information.

Hi Raquel,
Ours problems with RFC and with connections had be corrected with the note below:
1833778 - Activate Change Request management - Check error
Thank you very much!!
Adriana

System landscape changes after activating charm

Similar Messages

Maybe you are looking for