Transport layer SAP between development & quality

Should we have to use two transport layers ( SAP& ZDEV(created )) between the development & quality system as their consolidate route ?
Transport layer
SAP- Transport layer for SAP standard objects
ZDEV- Transport layer between Devlopment & quality systems
I assigned the consolidate route ZDEV between the Development & quality systems.Now ,How can I assign the transport layer SAP between the both systems as a consolidate route. Help me with your steps..

HI,
Z<SID> and SAP both are consolidation route as well as transport layer having different characteristic.
->A transport routes can be either a consolidation route or a delivery route. For a standard three-system
landscape, the transport routes are as follows:
-> A consolidation route connects the development system and the quality assurance system. This
transport layer is named Z<SID>, where <SID> is the system ID of the development system.
->A delivery route is created between the quality assurance system and the production system.
->In the development system, if changes are made to objects whose development class refers to the
(standard) transport layer corresponding to a consolidation route, these changes are recorded in
requests and transported to the quality assurance system and then to the production system.
If you change SAP objects, these changes are recorded in repairs, which can be transported in the
same way but using the consolidation route "SAP".
regards,
kaushal

Similar Messages

Is transport layer ONLY for consolidate router?

I have reviewed some STMS configurations and come up with this conclusion:
Transport layers other than "SAP" are for consolidation routers ONLY.
In other wods, if there is no consolidation router, no transport layers other than "SAP" needed.
Could you confirm my conclusion is right? And if so, why?
Thanks!

The definition of a consolidation route according to the course ADM325:
A consolidation route defines the path (the successive system and/or client) that is followed by a change request immediately after the release from the development system. Typically, the consolidation route proceeds from the development system to the quality assurance system in the standard three-system landscape.
A consolidation route is created from the development system to the quality assurance system through the transport layer Z.<SID>.
A consolidation route is created from the development system to the quality assurance system through the transport layer SAP for the transport of SAP standard objects.
Hope this helps.
Kind regards,
Mark Dijsselbloem

ChaRM: Support of more than one transport layer

Hi!
We would like to implement ChaRM for the 3 tier landscape (DEV:100 --> QAS:200 --> PRD:100) with several transport layers and transport routes:
a) u201CZDEVu201D u2013 Standard transport layer
b) u201CSAPu201D u2013 SAP transport layer
c) u201CYCSTu201D u2013 transport layer for internal customizing
d) u201CZEXTu201D u2013 transport layer for external vendor
All the transport layers should be used for the transports from DEV:100 to QAS:200 within ChaRM.
Our question:
Does ChaRM support several transport layers (SAP and none-SAP)?
Or does it accept only standard transport layer
(u201CSAPu201D and u201CZDEVu201D, but it doesnu2019t support u201CYCSTu201D and u201CZEXTu201D)?
Thank you very much!
regards

Hi
ChaRM only supports one (the standard) transport layer per client. I've already told you that some days ago... You can trust me I've configured those landscapes several times for many customers.
Enclosed please find a statement from SAP:
Transports are supported in the standard transport layer of each client. When you configure transport routes, note that only consolidation routes that are assigned to the standard transport layer of the relevant exporting client are taken into consideration. For each exporting client, exactly one target client and one target group are permitted.
We recommend that you assign exactly one development system to a production system, and that these two systems are connected by exactly one unique transport track.
If a development system and a production system are connected by more than one transport track, this may lead to inconsistencies within the transport distribution. This type of transport configuration cannot be supported by Change Request Management, and may cause inconsistencies within the tools involved.
So you have to change your TMS configuration and the assignment of transport layers to development packages. e.g. use transport layer SAP and ZDEV
Then it is possible to use ChaRM and standard TMS together
regards
Andy

What's the difference between transport route and transport layer

what's the difference between transport route and transport layer,Can somebody give me some explaination? thks in advance!

Hi,
Transport Layer in ABAP Workbench
    The Change and Transport System supports the distribution of development
    work on large projects across multiple SAP Systems.
    The packages in each development system are grouped into one transport
    layer.
    The transport layer determines whether objects are assigned to a local
    or transportable change request.
Use
    Each of your SAP development systems is assigned a transport layer as
    its standard transport layer. If you use Extended Transport Control, you
    can assign different standard transport layers to certain clients.
    You can define at the most one consolidation target for each SAP System
and transport layer.
When you create a package, it is assigned the standard transport layer
of the SAP System.
If you want to assign a different transport layer to a package, you
require the administration authorization for the Change and Transport
System.
The objects in a package automatically have the transport attributes
defined for the corresponding transport layer.
o   If a consolidation route originating in their SAP System is defined,
     then the objects are assigned to a transportable request, and
     transported into the consolidation target when it is released.
o   If a consolidation route is not defined, the objects are assigned to
     a local request, and are not transported.
Customizing settings are not assigned to a package. They have the
transport attributes of the standard transport layer of the system or
client.
It is best to assign a package a standard transport layer for which a
consolidation route originating in the development system is defined.
To display and maintain the transport layers and routes, use the
Transport Management System (transaction STMS).
Only the system adminstrator can make changes.
Caution:
     The tables TSYST, DEVL, TWSYS, TASYS are no longer productive as of
     Release 4.0A and cannot be maintained.
Regards
Ben

Transporting an Object from Development to quality and then to Production

Hello SAP Friends
I want to know the step by step navigation for Transporting an Object from Development to Quality and from there to production..
Please give some detailed Navigation...

Hi Kiran,
use transport connection to collect the objects to request, rsa1->transprot connection.
use infocube as starting point to collect objects, left side choose 'object type', middle frame choose 'infocube' expand 'select objects', locate/search your infocube' and 'transfer', it will go to right side.
in right up, there are buttons, click 'mode' and choose manual, and grouping 'only necessary objects', and execute, this will collect infocube and required objects like infoobjects, infoarea, etc.
after that change grouping 'in dataflow before' and execute, this will collect update rules, ods, infosource, transfer rules, datasource assigned etc.
remember to assign source system, click yellow box with X icon and mark the source system.
after that use grouping 'in dataflow afterwards' to collect query, web template, role etc.
take a look transport docs
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/3010ba90-0201-0010-2896-e58547c6757e
http://help.sap.com/saphelp_nw2004s/helpdata/en/0b/5ee7377a98c17fe10000009b38f842/frameset.htm
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/e883de94-0501-0010-7d95-de5ffa503a86
http://help.sap.com/saphelp_nw2004s/helpdata/en/b5/1d733b73a8f706e10000000a11402f/frameset.htm
http://help.sap.com/saphelp_nw2004s/helpdata/en/57/38e1824eb711d182bf0000e829fbfe/frameset.htm
Re: Transport Organizer---
transport query (bex objects)
http://help.sap.com/saphelp_nw2004s/helpdata/en/38/5ee7377a98c17fe10000009b38f842/frameset.htm
hope this helps.
(Courtesy AHP from Re: transport)
Bye
Dinesh

How to add new package in SAP transport layer?

hello,
as part of requirement, i have to add a new package to SAP transport layer.
can anyone tell how it is done?
as in STMs,add new package is not coming.
Regards,
Chaitanya

Hi
go thru the below links
http://help.sap.com/saphelp_nw04/helpdata/en/57/38de0c4eb711d182bf0000e829fbfe/content.htm
http://help.sap.com/saphelp_sm32/helpdata/en/57/38de194eb711d182bf0000e829fbfe/content.htm
Regards
S

SAP TAO,What is the purpose of Development,Quality,Production environment?

Hi All,
What is the significance of Development,Quality,Production environment under license tab of configuration in SAP TAO.
Which environment has to be selected for better operatability of SAP TAO functions.
Thanks and Regards,
Ujwal Kandimalla

Hi,
As TAO deals with the testing aspect, a 3 system landscape is recommended:
DEV : For unit testing
QA: For system testing and integrated testing
PRD: Has to be available for production usage
You could also have a Pre-Prod for load and UAT.
Regards,
Srikishan

ChaRM taking standard SAP transport layer for a project

Hi
After creating transport request via ChaRM, we notice that the request is assigned to the transport group where standard SAP transport layer is assigned, and not to the respective project transport group.
I activated ChaRM for a project, by assigning logical component DEV-100 -
QAS-200 -
PRD-300
When creating transport request via CR, the request is created in D10-100 and assigned to /GLOBAL/ transport group instead of /PROJ01/ group. After debugging I notice that ChaRM is sending SAP transport layer and since SAP layer is assigned to /GLOBAL/, all requests are assigned to /GLOBAL/ group.
Is there any report or missing step which I should execute?
Thanks & Regards
Madhu Bommala

Hello Madhu,
To define what should be the transport layer used by Charm you should execute the report /tmwflow/set_track_generation ,
if you want to use your transport layer instead SAP layer, you should set the option NO_SAP in this report.
I hope that this information can help you.
Best Regards,
Diego Fischer

OSB: The different between transportation layer and security layer

Dear All,
Do you have any idea for compare about security on service bus between transportation layer and message layer?
Which one is better? And do you have any factor to consider which one I should use?
Best REgards,

If you are working with OSB 11g, please refer -
http://download.oracle.com/docs/cd/E17904_01/doc.1111/e15866/part_sg.htm#sthref1029
Ofcourse you would like to have both of them if you want a healthy system. If your OSB services are internet facing then it is a sensible decision to have both transport (a bare minimum) & message security. If your services are exposed to a LAN/WAN then you may have either or both of them. Remember, securitiy processing is always an overhaed to the performance so should be used as and when required only.
Regards,
Anuj

Diff. between transport route and transport layer

hi gurus,
What is the Diff. between transport route and transport layer.
Regds:
BBR.

No interview questions
Read the "Rules of Engagement"
regards
Juan

Transport Layer

Hi guyz,
I have a question. why do we need a transport layer between the Development system and the consolidation system?? It is really appreciated if someone can throw some light on "Transport Layer".
Thanx in advance.
Ashok

Ashok,
The transport layer is for capturing all the modifications, customizations that is being taking place in a development system. As a result a request is created only in a development system, so that it can be moved to quality, tested and then finally to production.
The fact that its not between quality and production is that, quality doesnt allow any new modifications as its only for testing purposes and any new customizations will obviously be done in development.
Hope i have tried to explain upto your understanding. If you still have any doubts, let me know.
Thanks and Regards,
Sailesh K

Transport ALE Configuration from Development to Production System

Hello All,
We have created ALE-IDOC scenario in the development system and its working fine. Now we want to transport it to the Production / Quality system. How can we transport the settings like logical systems, port definition, partner profiles, distribution model , RFC destinations from one system to another system??
Because the client numbers are different for development , quality and production systems.. Do we need to transport the logical system and client assignment using STMS or create directly in the target system??
Thanx in advance...

The issue with transporting the ALE distribution model is that the source and target logical system names change between the dev, test and prod environments.
Assume an ECC6 and PI landscape with dev/test/prod called E6D/E6T/E6P and PID/PIT/PIP with all systems using client 100. By default (SAP recommendation) the logical system name for E6D client 100 is E6DCLNT100 and its PI partner in the dev landscape will be PID client 100 with logical system name PIDCLNT100. In test the logical system names will be E6TCLNT100 and PITCLNT100 and in prod E6PCLNT100/PIPCLNT100.
So, when a distribution model is set up in dev with a source system of E6DCLNT100 sending messages to a target system PIDCLNT100 everything works nicely. This assumes that the PIDCLNT100 logical system partner in WE20/WE21 is mapped to a port which maps to an RFC destination pointing to client 100 of PID.
When this model is transported to the test system it won't work because the logical system names are wrong.
It is possible to create a logical system name called PISERVER in SALE and then map that, via WE20/WE21 to point to the corresponding PI instance. Thus in E6D, WE21 would map logical system PISERVER to the RFC destination for PIDCLNT100 but in E6T the mapping would link to RFC destination PITCLNT100 and in E6P to PIPCLNT100. In this way any ABAP programming trying to use the ALE distribution model would send messages to PISERVER and would be transportable.
However, setting up the source system in the same way appears to be impossible. When attempting to generate partner profiles, transaction BD82 stubbornly insists that the source system for which it will build profiles MUST be the logical system name defined for the execution client in SCC4. Theoretically, mapping similar to that for PISERVER could be performed for ECC6SERVER and the ALE distribution model could be built to send messages from ECC6SERVER to PISERVER but BD82 won't honour this source system.
This appears to make it impossible to transport an ALE Distribution Model. Can anybody provide a process to overcome this apparent architectural limitation?

Transport Layer and Objects

what is the relation between the objects of a transport request and the layers in a transport domain?

Dear Abhishek,
First of all a I have to explain packet:
Packet
A packet groups Objects of the Development. Any report or table or data element … belongs to a packet. So every repository element is connected with a packet.
Transport route
A transport route describes the direction a transport can be transported. For example if you want to transport a transport from development to a test system, you have to configure in TMS a transport rout from development to the test system.
Transport layer
A transport layer connects packets to transport routes.
The connection between packet, transport route and transport layer is:
Objects of Development (Programs or Reports or Tables …) <-> packets <-> transport layer <-> transport route <-> systems
If you develop a report in development system and want this report to be transported to the test system you need:
-to connect the report with a packet.
-to connect this packet with a transport layer
-to connect this transport layer to the transport route that is connected to the both system and describes the direction FROM(development system) TO(test system)
For an exact description see:
http://help.sap.com/saphelp_nw04/helpdata/EN/57/38de0c4eb711d182bf0000e829fbfe/content.htm
Best regards
Willi Eimler

Why transport layer has package defined for it?

I double click a transport layer on txn STMS. The popup is a "package overview", some entries show up here:
YWM                            ZTRL      Warehouse Management Repositor
YBW                            ZTRL     BI Development Package
YCRM                           ZTRL      CRM Development Class
Could you help explain:
1) how was them defined?
2) what's the purpose to do so?
I have verified that the number of the package is the same as the number of the DEV clients created after installation.
So are there any relation between them?
Thanks!

Hi,
Whenever your create some program then you have to assign a package to it like a container.
For more information, check below link:
http://help.sap.com/saphelp_sm32/helpdata/EN/57/38de194eb711d182bf0000e829fbfe/content.htm
Thanks
Sunny

Patches difference in development, quality & production

Hi,
Our Development & Quality environment is on patchlevel
SAP_ABA 700 0018
SAP_BASIS 700 0018
PI_BASIS 2005_1_700 0018
SAP_BW 700 0020
Our Production server is on
SAP_ABA 700 0019
SAP_BASIS 700 0019
PI_BASIS 2005_1_700 0019
SAP_BW 700 0021
Golive is next week. already developments and configuration are moved to quality and testing is going on.
Now i want to upgrade the patches in dev & quality to production level.
After that only i ll move the transports to production.
Please suggest us whether any problems will come in developments & configurations when the transports are moved to production.
Regards,
Raj

It's difficult to commnet on.
Best is building a Sandbox by copying production system , moving all those transports there and test. Then if everything is fine, upgrade quality and devlopment.
But in any case , do you want to downgrade production patch level if any problem occurs after moving the transports to PRD?
If the answer is NO, then you can upgrade quality first and test new patch level. If you find any problem try to solve that ( may be by applying some notes or rasing a message with SAP)
I can make sure at least PI_BASIS 2005_1_700 0018 upgrade will not pose any problem.
Regards
Anindya

Transport layer SAP between development & quality

Similar Messages

Maybe you are looking for