Virtual systems within Transport system landscape

Hi!
I should map the existing transport management system landscape into ChaRM approach within SOLMAN.
The existing transport management system landscape has a lot of virtual systems with virtual transport routes.
Can some one of you explain the usage of such virtual systems with their virtual transport routes?
Thank you very much!
regards
Thom

read,
http://help.sap.com/saphelp_nw04s/helpdata/en/44/b4a0db7acc11d1899e0000e829fbbd/frameset.htm
Regards
Juan

Similar Messages

Creating a virtual system for transport landscape

Hello
We have an isolated system that has transport system set to Local change Requests and would like to transport some of the transports into another system. I found in a thread here that we need to create a virtual system for creating a transport route. Can anyone tell me how to create the virtual system?
Thanks
A.

Hi Aleksandra,
You can create virtual system like below.
Make sure you have configured the domain controller.
Login to the system,client 000 and user with same authorization of sap*
Execute t-code STMS
from the menu Goto overview ->systems
You will get one entry of the domain controller.
Then from that screen from menu sap system -> create ->virtual system.
Provide the data for the sid and description and save your entry,
Then you can configure the root.
Regards
Ashok

No system in the system landscape exports transport requests

Hi gurus,
We are trying to implement the Change Request Management scenario in
Solution Manager 4.0 SP12 in a POC.
The TMS are created with Solution Manager as Controller and with the settings are correct.
We have created a Maintenance Project with the following landscape :
system1 - Client 100 as Development System - Type of Rol "Source System"
system2 - Client 200 as Quality System - Type of Rol "Target System"
system2 - Client 100 as Production System - Type of Rol "Production System"
In the Change Request tab, when we check "Activate Change Request Management" checkbox, the following error is shown:
"System system2-100 is to be changed in a Solution Manager project, but no
system in the system landscape exports transport requests which are
imported into this system."
What is happening? Any idea??
Thanks

The reason may be, that your "POC" is not valid due to the fact, that you use "clients" and not "systems" to transport
What you can try to verify that is - take out the QA client/system out of the transport route and try then to activate just with DEV --> PRD.
We wanted to setup something similar in the past and TMS failed to get configured properly - due to exact that reason.
Markus

Transport System

Hi,
I need help we are planning to upgrade our R3 to ECC 6.0 and our first step is to create a 4.6C Development system to support the 4.6C Production system. We did a copy of our Production system and configure our transport system and now we cannot change Z programs we received this message "Carry out repairs in non-original system only if they are urgent".
Thanks,

Hi Ramon,
local requests ALWAYS do not create datafiles ... they are designed for the "last system" in your landscape or for customers with a single system landscape only.
Therefore, you should typically do not use a virtual system but include it to PRD. But, the virtual system is a nice workaround as well, because this creates then the datafiles and you can use "add to buffer" and import it in PRD - unfortunately you need to be careful with this technique, because you could forget transports ...
as it is an emerngy stuff only, it should be ok.
Regards
Volker Gueldenpfennig, consolut.gmbh
http://www.consolut.de - http://www.4soi.de - http://www.easymarketplace.de

Defining more than one Target transport system

Is it possible to have more than one Target Transport systems defined for a single source System in SLD at one time?

On a similar note with a 3 tier XI landscape (DEV, QAS, PRD) which of the following two scenarios is preferable?
1. In the SLD define each DEV Business System with a target of the corresponding QAS Business System and define each QAS Business System with a target of the corresponding PRD Business System.
DEV ---> QAS ---> PRD
This means that we export ID objects from DEV and then import them into QAS. The objects then need to be exported from QAS for import into PRD
2. In the SLD define the DEV Business Systems with 2 target systems relating to corresponding QAS and PRD Business Systems.
DEV --> QAS
DEV --> PRD
This means that the same export from DEV can be used for import to both QAS and PRD.
Currently we have scenario 1 implemented but I am thinking of changing this to scenario 2 which I believe is a better solution as only one export is required and it is guaranteed that the same objects are being imported into QAS and PRD.
Any Comments?

Transport changes from test system to productive system

Dear Gurus,
My existing setup is a 3 system landscape DEV->TST->PRD and DEV is the domain controller.
We develop on DEV system and transport this developments to the TST system.
Now we want to change the developed objects in the TST system and transport this changes to the PRD system. Is this generally possible? Is this an konfiguration issue?
Regards,
Vincenzo

Hi,
Why do you want to change this since you have three system landscape? This is the standard practice which you are currently using. Technically you can transport the objects from your TST to PRD by configuring the transport routes etc.
My recommendation is to keep as it is.
Hope this helps.
Manoj

Adding one more system in existing stms landscape

Hi Gurus,
I am trying to add one sandbox system to my present landscape
configure TMS for four systems, out of which two systems (DEV1 and DEV2) are with same SID (DEV). As recommended by SAP, I understand that there can not be two systems with same SID in a transport domain.
and also my domain controller is DEV system,
please suggest how can i add DEV sand box in this landscape
Regards

Hi,
Yes, you can do that. Once cofiles and data files are generated after transport request is released in Quality system, you can import them into Sandbox system by manually adding them into import buffer.
If Sandbox system does not have common /usr/sap/trans, you have to manually copy those cofiles and data files from Quality to Sandbox /usr/sap/trans/cofiles and .../data and add the request to import buffer of Sandbox system from either STMS or OS level using tp addtobuffer command.
Please make sure STMS is configured in Sandbox system as local domain before you perform above said steps.
Hope it helps. Please let me know if you need any further info.
Thanks,
Siva Kumar
Edited by: Siva Kumar Arivinti on Nov 5, 2011 1:55 PM

Difference between transport system (file/cms)

Hi,
we would like to install XI with 3 systems (DEV, QA, PROD) and transport the java components (e.g. namespace) using file system or using change management system (CMS).
What are the differences between this possibilities?
Thanks,
Lutz

Hi
Transportation is of two types. a) File system Transport or b) CMS. If you want to use CMS then basis team should have install CMS.
Check this document for transportations using CMS and File transport:
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/f85ff411-0d01-0010-0096-ba14e5db6306
/people/sravya.talanki2/blog/2005/11/02/overview-of-transition-from-dev-to-qa-in-xi
/people/sap.india5/blog/2005/11/03/xi-software-logistics-1-sld-preparation
/people/sap.india5/blog/2005/11/09/xi-software-logistics-ii-overview
https://www.sdn.sap.com/irj/sdn/weblogs?blog=/pub/
you can use CMS or file system transport, depending on how your system is configured
if your idoc scenario is from DEV1 to XID to DEV2 in the dev landscape
and in the quas landscape is QAS1 XIQ to QAS2 then the transport target for DEV1 is QAS1 and the transport target for DEV2 is QAS2.
that means the transport target is the corresponding business system under a different landscape, (dev or qas or prod)
CMS is NW tool for transporting developments
This will help you
How to Use CMS in XI 3.0.pdf
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/43f5d790-0201-0010-2984-ff72d822b109
CMS based transport in XI
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/b8d8f7b2-0701-0010-b09a-cda4cca2c98e
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/9e76e511-0d01-0010-5c9d-9f768d644808

One SLD means rename of SAP system after transport?

On development got the situation of having naming conventions for SAP boxes like R3<b>D</b>CLNT100 within the configuration directory. Do I have to rename manually my systems after a transport to Q into R3<b>Q</b>CLNT100?

Hi Yuki
Does it matter what transport system you are using? File transport system or the CMS?
Normally, you define a business system as transport target, which is different from the business system the transport target is being defined for.
If we have the requirement to have the following transport targets:
BS_MJD (Dev) -> BS_MJQ (Tst) -> BS_MJP (Prd)
we should always define a target for that system?
Best regards,
Marco

Best configuration for Transport System

Hi everyone
I like to know what is the best way to configure my transport system.
We have 2 server QAS and PRD in two distinct machines. SERVERQAS and SERVERPRD, accessible from network.
We need what when all transport request from QAS when released, all files must be copied to PRD server, today we need to use the button to adjust queue, but we can't use this option, we need what this process is automatic.
Thks.

Hello Emerson,
You don't have Development system?
In a standard 3 system landscape, if dev, qua and prod systems are assigned with single domain controller and sharing same /usr/sap/trans then as soon as request is released from dev system, that will be available in qua buffer/import queue. Once it's successfully imported into qua system then it will be available in prod buffer/import queue for import. This is controlled by transport route.
Please read TMS configuration guide and take necessary actions.
http://help.sap.com/saphelp_nw04/helpdata/en/44/b4a0137acc11d1899e0000e829fbbd/content.htm
http://help.sap.com/printdocu/core/print46c/en/data/pdf/bcctstms/bcctstms.pdf
Thanks,
Siva Kumar

Relocating virtual disks to file systems other than dom0:/OVS/running_pool

It looks like the best approach for having multiple large file systems mounted within a domU is by:
1.) Use VM Mgr to create dummy virtual disk (within dom0:/OVS/running_pool/domU)
2.a) if size of dummy is large enough, cp it to a different file system within domU
2.b) if size of dummy is too small, create a new file on different file system within domU using dd
3.) Replace dummy virtual disk file (within dom0:/OVS...) with symbolic link that reference the new replacement file.
Are others doing this? Is there a better way?
Does it cause problems?
is there a way to update VM Mgr to show the correct size if the virt disk is enlarged from the size of the original dummy virtual disk?
Thx...
Edited by: twtuck on Mar 9, 2009 8:29 AM

You can use the /usr/lib/ovs/ovs-makerepo script to add additional repositories under the /OVS mount point. The script takes a block device as a parameter. For example, to create a new shared location on /dev/mapper/mpath1p1, you would run:
# /usr/lib/ovs/ovs-makerepo /dev/mapper/mpath1p1 1 "Shared Storage"
These repositories are then visible to Oracle VM and VM Manager. It will use the repository with the most amount of available space to create your guests for you.

Is Transport System b/w diff clients like 100 development 200 QA Possible?

Is it possible that we configure stms b/w diff clients like 100 is Dev, 200 is QA, 300 Prod and data flows through them as I have heard that this can be done

Hi Kiran,
Login to 000 client with SAP* user for the following configuration in the Transport Management System, STMS---go to Overview click on the Transport route, Your TMS configuration will be display in the window .
click on Pencil Icon or Press F5 to switch to Configuration editing mode, Click on Edit menu then click on the Transport Target Group to define the multiple client of single or multiple system which exists in your landscape.
Choose Hierarchical list Editor Mode or Graphic mode, to change from graphic mode to Hierarchical, go to setting menu click on transport route editor and select the Hierarchical List Editor Mode, setting will take effect to go to back and click on transport route again.
Switch Editing mode before continue to define the consolidate route,then go to Edit Menu, Transport Route and click on Create, Transport route window will display with the Consolidate & Deliver route options. Select the Consolidate Route and click on Extended Transport Control or F6.
Integration system is your current or development system as source system
Transport Layer Enter the default layer which has been created with your integration system.
Consolidation Targe Select your target group which was created.
Save the Configuration, activate and distribute the configuration across all systems.
system is ready to transport the requests to multiple systems and multiple clients
Cheers,
Shaym
Message was edited by:
shyam thamadapalli

Ensure that master data is unique across R/3 source systems within BW

Hello all,
I have an issue and don't have any clues for it.
I wait for your suggestions , please.
Problem: we must ensure that master data (represented by Info objects) is unique across R/3 source systems within BW
Thank you.

Hi,
Refer the below links,
http://www.sap-img.com/business/load-master-data-hierarchies-from-r3-system.htm
http://help.sap.com/saphelp_nw2004s/helpdata/en/3a/d2a165ac873b42aba04475719679c4/frameset.htm
Hope it helps you,
Regards,
Ravindra.

Source System in an ABAP Landscape

We are relatively new to SAP. Back when we initially architected the landscape we had many consultants in, including several Platinum consultants from SAP. At the time they emphasized the special nature of the "source system" in an ABAP landscape, and how it should never be refreshed and how we should not change which system in considered the source in our landscape. "Once the source always the source."
Now we are being asked to change the source system, but we do not have the background as to why the source system is so special and why it should not be refreshed or changed.
Would you be willing to share your opinion on the matter? Pros/Cons/Costs of Changing/Costs of Refreshing.
Thank you very much.

There is a SAP Note 130906 for this. Pasting few lines from note for your referance. Please ref Note for details.
Symptom
You want to copy the versions of the repository objects from one R/3 system into another, for example because you are planning to copy your production system to your development system.
Such a procedure does not correspond to the strategy recommended by SAP, to always retain the development system.

Error with Transport system not configured that may be related to CHaRM

Who has in depth knowledge on setting up SAP Solution Manager CHaRM. Had an odd problem with the transport system failing when the QA system was shut down for maintenance. Transports were not able to be created or save to. Error message was Transport System not configured. Brought up QA and re-distributed system and Transport group and transport requests started working again.

Hello,
if a system, e.g. QA system, will not be available due to a maintenance task,
we set the status of this system to "temporarily inactive" (see header data in transaction SMSY).
This status allows us, to create new transport requests in DEV-System although consolidation system QA is not available.
(Of course you have to reset the status, when QA-system ist started again.)
Hint: it is not possible to release or to import a transport request, when consolidation system is shut down.
Therefore the developer should pay attention to the messages, which raise in urgent corrections.
best regards
Horst

Virtual systems within Transport system landscape

Similar Messages

Maybe you are looking for