Transports Landscape

Hi ,
we have three system landscape built in recently , does anyone has a procedure to setup a tranport configuration and routes between the three system landscape at the SAP level
And at the unix level what needs to be done. We have /usr/sap/trans which is not shared with the DEV and QA , how is this to be shared and configured.
Thanks,
kris

Hi Friends,
AT the SAP level to configure the transport routes, i would be doing as below
. After SAP Gui installed. (Development system is always domain controller.)
2. Logon to Client :000
User: DDIC.
Pwd: ******
3. Put a T-code (se06) in the command field.
4. Click standard installation and click post installation (yes)
5. Put a T-code (STMS) in the command field and give a description then save it.
6. Click System overview push botten, click extras option from the menu and click Distribute and activate configuration. (Yes)
7. Back to the stms main screen and click Transport routes from the push botten.
8. Click Configuration button from the Menu.
9. Click Distribute and activate from the configuration menu.
10. Now your sap system is activate in domain controller.
11. Now logon to QAS system.
12. Client: 000
User: DDIC
Pwd: ****
13. Put a T-code (se06). In the command field.
14. Click standard installation and click post installation (yes)
15. Put a T-code (STMS) in the command field.
16. Click other Configuration push butten in the bottom of appear screen.
17. Give information about development system. Example: tisdev, 00
18. Then save it. Ok
19. Now QAS is waiting for include domain controller.
20. Logon to Development system.
21. Click system overview push butten.
22. Click sap system from the menu.
23. Select the QAS systems.
24. Click Approve butten from the sap system menu.
25. Now QAS is member system of domain Controller. (Development system).
26. Suppose if you want configuring Production also, following the same step in the QAS.
development system as domain*
Unix level
We have the following file system for trans in the development
---/usr/sap/trans/PRD
In the production system, the following file system is existing ---export/usr/sap/trans/PRD
Where should i issue the mount command is it in DEV or QA or PRd and is it just mount /usr/sap/trans:host in the dev or qA. Please correct me if i am wrong.
Thanks.

Similar Messages

Unicode and Non-Unicode Instances in one Transport Landscape

We have a 4.7 landscape that includes a shared global development system supporting two regional landscapes. The shared global development system is used for all ABAP/Workbench activity and for global customization used by both regional production systems. The two regional landscapes include primarily three instances - Regional Configuration, Quality Assurance, and Production. The transport landscape includes all systems with transport routes for global and regional.
A conversion to unicode is also being planned for the global development and one regional landscape. It is possible that we will not convert the other regional landscape due to pending discussions on consolidation. This means one of the regional landscapes will be receiving global transports from a unicode-based system.
All information I've located implies no actual technical constraints. Make sure you have the right R3trans versions, don't use non-Latin_1 languages, etc. Basic caveats for a heterogenous environment ....
Is anyone currently supporting a complete, productive landscape that includes unicode and non-unicode systems? If so, any issues or problems encountered with transports across the systems? (insignificant or significant)
Information on actual experiences will be greatly appreciated ....
Many thanks in advance.

Hi Laura,
Although i do not have the live / practical experience, but this is what i can share.
I have been working on a Non-Unicode to Unicode conversion project. While we were in the discussion phase there was one such possibility of a scenario that part of the landscapes would remain non-unicode. So based on the research i did by reading and directly interacting with some excellent SPA consultants, i came to know there are absolutely no issues in transporting ABAP programs from a Unicode system to non-unicode system. In a Unicode system the ABAP code has already been checked and rectified for higher syntax checks and these are downward compatible with the ABAP code on lower ABAP versions and non-unicode systems. Hence i beleive there should not be any issues, however as i mentioned this is not from practical experience.
Thanks.
Chetan

Transport strategy for your transport landscape is inconsistent

Hello everybody,
we had 4 system landscape.
DEV>QAS>TST-->PRD.
we move the request from DDEV >QAS>TST and then forward request from TST to PRD system.
Now, we have delete the system TST from TMS, after deletion it give the warning.
Transport strategy for your transport landscape is inconsistent.
Message No. XT481
Please suggest, what is meaning of this warning and how to correct.
Thanks
Ganesh

You need to do following
1. Logon to domain controller client 000 -->STMS --> Overview System --> Select TST --> SAP System --> Delete
2. Reconfigure STMS DEV>QAS>PRD
3.STMS --> Overview Transport Routes --> Configuration --> Distribute and Activate (To All System)
Note : You should do this from Domain Controller client 000
I assumed you know Step 2. If you dont please let me know i can guide you on that as well
Cheers !
Manish

Transport landscape best practise

I'm wondering if SAP has a best practise document on transport landscape planning.
SAP Help has pretty clear description about a standard 3 system landscape. But not document is found describing complext transport landscape considerations --- multiple ABAP development/test systems, conflict resolution between project landscape and maintenance landscape.
Any feedback is greatly appreciated.

Hi. GO to http://help.sap.com/bp/initial/index.htm
There you find all about BP.
Regards, Award if helpful

Four systems transport landscape

Hi,
We have introduced pre-production environment.Now we need to configure 4 system transports.
How to configure 4 system transport landscape.
- Kristene

Hello,
You need two do 2 things:
1. Include the system into your existing transport domain.
2. Re-configure the transport routes
To include the system into your existing transport domain check the following link:
http://help.sap.com/saphelp_47x200/helpdata/en/44/b4a0c17acc11d1899e0000e829fbbd/frameset.htm
To re-configure the transport routes:
You simply need to login into the 000 client of your domain controller and re-configure your transport routes.
as described in the link given below:
http://help.sap.com/saphelp_47x200/helpdata/en/44/b4a1df7acc11d1899e0000e829fbbd/frameset.htm
Once you have re-configured the transport routes, do not forget to distribute the configuration.
Regards,
Siddhesh

Transport Landscape design??

Hi all,
Our client is saying that they require 2 Development system,2 Quality & 1 Production System.How will we design our Transport Landscape??Is it possible to have 2 development & 2 QA in one system landscape??

Hi,
This configuration is very much possible, in fact i have worked with a client with similar configuration.
Transport route can be
DEV1->QA1->PRD
DEV2->QA2->PRD
Now whenever request from DEV1 reaches production it should also simultaneously move to DEV2 and QA2.
The reverse is to be done when request from DEV2 reaches PRD, it needs to be flushed back to DEV1 and QA1
This is needed to maintain synchronization between two DEV and QA
Synchronization danger occurs in scenario when changes/enhancements of similar type are performed at same time in both dev.
Hence any changes/Enhancements planned should be checked for clash or else synchronization is extremely difficult to achieve.

Track design in a complex transport landscape

I have read the blog for <a href="/people/marion.schlotte/blog/2006/03/30/best-practices-for-nwdi-track-design-for-ongoing-development Best Practice</a>
I have read the online help for <a href="http://help.sap.com/saphelp_nw04/helpdata/en/42/f1a03611d83ee4e10000000a1553f7/content.htm">Deployment to multiple Production systems</a> and transport to mulitple systems
I am a Basis person that has set up and used NWDI before but now have a scenario that is becoming quite common in the real world.
One of our customers have a Development/QAS system for not only maintenance but small projects as well. They also have a devleopment/QAS system for large projects (and also horrifically in the near future probably also have a short term dev/QAS for a CRM implementation).
All of these Dev/QAS systems feed into a pre production QAS system that then releases to a production and training master system.
Naturally I want to know how best to set up my tracks.
My thoughts are that we can have 3 scenarios.
1. All changes made to the maintenance track are also applied to the other tracks manually. (this is SAP's recommenadation for ABAP transports)
2. All Changes to DC's in the maintenance track are manually imported into the other tracks when dev activation is successful.
3. The project track depends on the Maint track
There are complex issues with all of these so I would realy appreciate a best design dicussion for this complex matter.

Hi Sidharth,
Many many thanks for your prompt and excellent start to this. I agree this will be fruitful to all.
The structure you propose is the only logical one. The problem comes with keeping the tracks and the environments in Sync.
For this customer;
1. The changes in track 1 must also be made to 2 & 3
2. The changes in track 2 must also be made to track 3
Naturally the changes to the tracks must ensure that newer versions do not get updated with older versions. With SLD registration, assembly versioning and all 2 tracks merging into a pre prod this should be avoided from that standpoint.
My concern is that there would be some chances of versions going astray a bit depending on how they link together.
For example track 1 & 2 have version 1.1 of a DC.
In track 1 they start making a Fix to a bug and version 1.2 of a DC is created.
In track 2 they start making a large project change and version 1.3 of the DC is created.
Track 1 releases Version 1.2 into preproduction and also into track 2.
Track 2 releases version 1.3 into preproduction but this does not have the changes in version 1.2
If testing is not vigorous in pre production the fix will be backed out of in production. Now I agree that version 1.4 in track 2 will have these changes in it but there will be a time when production has the bug reversed and this will cause confusion. possible resolution I see all apears to be manual and require trust.
1. Changes to track 1 are also made manually to track 2 and 3 at the same time.
2. Changes to track 1 at dev activation time can somehow be propogated to track 2 and 3. (Can you import DC's?)
3. Release from track 2 in the above example would require version comparison along the track to ensure no new versions come from other tracks.
Apologies if I misunderstand any of the logistics, please feel free to correct any assumptions I have. It is important that transports are handled in the safest way possible.
regards
Graham

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

Transport landscape problem (cannot change the object)

Hi All,
I have problem to change my object in the integration repository.
Initially, i only have 1 XI server (dev and prod), until certain level that i have to add additional server for development. So i just install new xi in new box (fresh). and export the repository object form production and import into this new box.
But the problem is i can't change all the object. is that any workaround to change the configuration so i can use my nex box become development and later on transport back all the changes to original production box.
Appreciate if you can give me some advise.
Thank you and Best Regards
Fernand

Hi,
If you need to change anything in repository
you need to click on the software component in IR
and at the bottom of the screen you will find two checks
that will allow (or not) you to change objects
if you want to change anything in communication channel
you just need to go to change mode
you can change anything in ID
Thanks
Swarup

One Domain Controller, multiple Transport Landscapes - possible?

I would like to have ONE domain controller - configured in Solution Manager - to manage TMS configuration for ECC, BI, etc. I am looking at this domain controller to be the central point for CTS+ and ChaRM.   This means multiple Development systems and associated Quality Assurance systems.
DECC --> QECC --> PECC
DBI --> QBI --> PBI
Is this even possible?
The issue seems to be the standard '/SAP/' transport group for the 'SAP target for Default Layer'.   Is there a way to set up the standard SAP transport group to be uniquely identified in the domain controller if there are multiple SAP components supported by one domain controller?
Thanks in advance for the assistance ...

Hi Peter,
Thanks for the response.    My concern was the SAP default transport layer.   Another team member and I worked on this in more detail and I was able to successfully a specific SAP default transport layer for each of the Development systems and give each one a unique name.   I created the transport layers and transport groups and STMS accepted them, but we haven't actually used any of this yet so whether or not this is actually successful remains to be seen!    If
Regards,
Laura

How to transport a custom bapi (written by me) to another server

Hello friends,
We have a software that is integrated with SAP. To make our software work with SAP, we have some custom bapis created on SAP side. We would like to transfer them to another server that is on a different network. After reading many documents and forums here is the what I have done and the problem that I am facing. Your help will be highly appreciated.
1.Started Transaction 'SE80'.
2.Created a test package called 'ZTRANSPORTTEST'.
3.Created a function group called 'ZTRANSPORTTESTFN' under that package.
4.Created a function module under the group called 'ZTRANSFUNCTION'
NOTE: Just saved and activated without adding any code since I won't be using this function
             for anything other than to test the Transport Feature.
5. Clicked on the button that said 'Transport Organizer' and saw the list of requests including the
    EC1K900083one that I just created.
6. I tried to release it by 'RIGHT CLICKING'
   It waited for few seconds with the message....."code inspector checks running.".
   Then it failed with an error message as follows
   Error in pre-export methods for request EC1K900083
NOTE: I have made sure that everything is activated properly, since I read on a forum that this
             error may occur if something is not activated properly. So I have done this step over
             and over again making sure that everything is activated properly.
7. I then started Transaction 'SE09' and saw the request 'EC1K900083' under the released tree with a 'CHECK' Mark.
However, when I sent to /usr/SAP/trans/data and /usr/SAP/trans/Cofiles, I didn't find the transport data there.
Has anyone done this before and if so what am I doing wrong? Your suggestions or feedback will be highly appreciated.
Thanks
Ram

Hello Friends,
Thanks for all the responses. I got the following response from SAP TECH SUPPORT which is not very encouraging and so I am just closing this.
Thanks
Ram
===========================================================================
30.04.2009 - 11:40:29 EST - Reply by SAP
Dear Mr Ram,
Thanks for explaining it once again.
The package is just container for development objects that belong together, in that they share the same system, transport layer, and
customer delivery status. Please check the below link http://help.sap.com/saphelp_nw70/helpdata/en/ea/c05da3f01011d3964000a0c94260a5/frameset.htm
As I understand correctly you want to 'export' your development outside of your SAP system domain. For that either you can do it using 'Externalsystems'. 'External systems' are a special form of virtual systems. A real SAP System is used in their place to perform actions on the transport directory. They are different from virtual systems in that they have their own transport directory that you can freely choose, you can use external systems to:
-Write transport requests to exchangeable data media
-Read transport requests from exchangeable data media
-Send transports to other transport domains using an intermediate directory
-Send transports to other transport domains using an intermediate directory
If you want to transport between systems in different domains, we recommend that you link domains with 'domain links'. There must be a
permanent network connection between the systems in the two domains, similar to the connection between systems within the same domain.
I would recommend to take a look in the documentation available in SAP Online help for further information on how to setup this
complex transport landscape. I hope this information helps you to setup the transport system.
Or you simply create a transport request of type 'transport of copy' and input target system and client (which you should know) system as
target system include the objects (bapi) in the request. This ensure that requests will only be imported into that system. Other systems willnot be touched.
'Transport of copies' type transports do not get automatically added to the next buffer after they have been imported into a system. When creating a 'Transport of copies' transport the target system must be specified as this type of transport does not respect the defined transport routes outlined in TMS.
You can use this request type to transport objects to a specified SAP System using Transports of copies. The objects are transported with the version they have in the current SAP System. The original location of the objects remains unchanged. There is no delivery to another SAP System.
But we at AGS we cannot suggest, as the nature of your request indicates this is a consulting issue rather than a software error.
Customer Support's charter, under the SAP maintenance agreement, is to handle software or system defects in the standard delivered R/3 product. Please refer the note 1054121.
So you have to seek assistance from SAP's Remote Consulting Service which is billable.
I am sorry that I could not give you more positive reply in this case.
With warm regards,
Sajiv
Active Global Support - Technology
=========================================================================

Importing a transport request

Hi Expert,
In our Transport landscape some one has released a transport for QA system but the request is not reflecting in Import Queue of QA system.
Can some one advise how to import the request in QA.
Thanks
Kundan

Hi,
There might be some problems at OS level of Dev/Qua system and check the Co and Datafiles. Now execute Tcode STMS_IMPORT in Qua system. and goto following location from menu bar:
Extras-> Other Requests -> Add
Now give the Transport Request No. and Target Client.
This will add the Transport request into Import Queue of Qua system, now u can import the request.
Hope this will solve your query.
Regards
Lokendra

Transporting Developmenrts from PI DEV to PI Prod

Hi Experts,
in my PI server, when ever I do a development in the ABAP stack, I release and transport the request to Basis. And In case of developments in Java stack, I use Change Management Service - Transport Studio to move it.
Apart from these processes, what other practices / processes are done in the industry to move developments to Prod..
Regards,
Arnab

Hi,
What is CTS+ and why is is introduced:
The Change and Transport System (CTS) is a tool that helps you to organize development projects in the ABAP Workbench and in Customizing, and then transport the changes between the SAP Systems in your system landscape.
The XI use case for CTS+ introduces a new transport handling mechanism that offers tighter integration for the transport of ABAP, Java, and Integration Builder objects (Integration Repository and Integration Directory) using the Change and Transport System (BC-CTS) functionality.
As your XI system requires both the ABAP and the Java stack of the SAP NetWeaver Application Server, the following transport tools are available after installation:
u2022
The ABAP transport environment (BC-CTS)
u2022
The file export and import mechanisms or CMS integration to transport Repository or Directory objects in your transport landscape
In addition, you might also have to transport Java development objects by using the SAP NetWeaver Development Infrastructure itself.
The enhancements to CTS in combination with the SAP Solution Manager Change Request Management (ChaRM) address the following issues:
u2022
Synchronized transports for mixed systems (ABAP & Java)
u2022
A unified application for mixed system landscapes
u2022
Tracking of non-ABAP transports including Change Request Management
For your XI landscapes there will be one central transport environment with CTS+ where you can manage all XI-relevant transport objects from a single entry point.
This how-to guide describes the configuration settings you must make in the CTS+ system and XI systems. The functionality must be set up according to the release version of the integrated XI system. The two configurations will be described separately:
u2022
Configuration setup for releases prior to SAP NetWeaver 7.0 SPS12 (also for SAP NetWeaver 2004 SPS14 and higher).
u2022
Configuration setup for release SAP NetWeaver 7.0 SPS12 and higher.
Refer the link for CTS+ step by step method of transport:
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/80bbbd55-5004-2a10-f181-8bb096923cb6
http://help.sap.com/saphelp_nw04/helpdata/en/03/dcb6b6048711d3b42a00609419f767/frameset.htm
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/90d3b550-b6fb-2910-0fa5-ece5d61fb9c3
Regards,
Phani

Access Transport Logs in Report

Hello,
we want to do a simple report for our ABAP transports in NW 2004s which takes a list of transport numbers as input and gives import times and return codes for different systems. But I don't know how to access the import results of other systems in a report.
Is there a function module for it? Does anybody have a reference to similar reports?
Thanks in advance for your help,
Christoph

Hello,
this was my basic idea, too. I don't have any problem getting the local information about the transports. But the report needs to contain the import results to the other systems in the transport landscape. And I don't get where these are stored.
Do I need to access the remote systems tables? I can get information on transports of the development system on the test system in some of the E070* tables, but I don't find the import timestamp and the return code. Do I need custom remote function calls to get this information, or can I use the same way as the SAP transport organizer shows it? (There should be no changes on production if possible.)
Thanks for your help,
Christoph

Transport overwrites original - although locked in transport request

Dear all,
we have a very special system landscape and therefore a very special transport problem.
An include in the original system was overwritten by a transport although it was locked in a transport request.
To explain the circumstances:
We develop and support several releases of a pre-configured SAP Template for BW 3.5 and ERP 2004. After launching a new release we build up new systems as support stream for this release.
For example BW development system for release 3.1 was TBD, after launching of release 3.1, we copied TBD to TBE. Thus, TBE is the support system for release 3.1 and TBD becomes the development system for the next release 4.0.
Normally, a correction in release 3.1 (TBE) has to be included in 4.0 (TBD), too. Thus, all support systems are included in one transport landscape.
It happened that a developer made a correction in an include in TBE and transported it to TBD. Unfortunately, another developer had enhanced this include in TBD and didnt release the transport. So this changes were overwritten with the import from TBE although it was locked in a transport.
I investigated this case and found out, that it could be overwritten because TBD is the original system of this include and therefore it has no repair flag when its locked in a transport which protects it against overwriting.
We have to import the transport with the option Overwrite originals because in most cases a correction has to be imported in the original system.
Do you have any suggestions how we can avoid this happening?
Is there a possibility so set the repair flag in TBD manually?
Thanks in advance for your help.
Regards,
Karin.

Hi Max
I tried this already but it doesn't work.
Following system message occurred:
Cannot change task type
Message no. TR857
Diagnosis
You can only change the request type if this is permitted by the type of objects in the request.
The requirement is not met in this case.
Karin.

Transports Landscape

Similar Messages

Maybe you are looking for