ChaRM: Standard transport layer

Hi!
I have one question regarding transport layers for usage of ChaRM.
Which standard transport layer does the ChaRM need?
a) "SAP" transport layer
2) standard transport layer "ZDEV"
What will happen when one of this (SAP or ZDEV) will be mised or used outside of ChaRM?
Thank you very much!
regards
Thom

Thom Heinemann wrote:>
>
> Which standard transport layer does the ChaRM need?
> a) "SAP" transport layer
> b) standard transport layer "ZDEV"
Anand: ZDEV should be the standard transport layer......
All SAP standard objects will only follow SAP transport layer......irrespective of whatever standard layer is mentioned.....
> What will happen when one of this (SAP or ZDEV) will be mised or used outside of ChaRM?
Anand: Little more clarity is desired on this query....can you please be more specfic about what you meant..
Inspire ppl by rewwarding !!
Regards,
Anand....

Similar Messages

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

ChaRM: transport layer/routes used by ChaRM

Hi!
We have very complex trasport system settings and would like to implement ChaRM with parallel usage of transports in non-ChaRM environment.
We have a lot of transport routes (between DEV:100 and QAS:100) (e.g. SAP, ZDEV, ZFAD, ZGFA, YDAS).
How can we split the transport routes for ChaRM and transport routes for transports without ChaRM?
Which transport routes will be used with ChaRM?
Thank you very much!

Hi
as already mentioned in one of my replies to your last thread, ChaRM always (and only) uses the standard transport layer (route) per client.
This one and all other ones can be used for non-ChaRM transports. This is standard TMS functionality.
But you have to check if the "ChaRM check" in your project configuration accepts your TMS settings. Maybe the other transport layers/routes make waves. Then you have to change them...
regards
Andreas

ChaRM: Several Transport layers

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
The problem we have is that transports within ChaRM are supported in the standard transport layer of each client.
It means that the transport requests of transport layers u201CYCSTu201D and u201CZEXTu201D that are non-standard transport layer will be ignored by CHaRM.
Has some one of you experience with configuration of ChaRM with several transport layers and can give an advice what is the best solution in my case?
Possible solutions:
a) Creation of additional clients in DEV system and assigning them other standard transport layer (e.g. DEV:200 gets u201CYCSTu201D, DEV:300 gets u201CZEXTu201D as standard transport layer)
Then it should be possible to create three maintenance projects:
1) MP1: (DEV:100 --> QAS:200 --> PRD:100) with transport layer u201CZDEVu201D
2) MP2: (DEV:200 --> QAS:200 --> PRD:100) with transport layer u201CYCSTu201D
3) MP3: (DEV:300 --> QAS:200 --> PRD:100) with transport layer u201CZEXTu201D
b) Migration of all the non-standard layers to standard transport layer.
c) Separation of ChaRM and none-ChaRM transport layers (TMS)
It would be great to get some feedback/suggestions/input
Thank you very much indeed!
regards

Hi
Sorry for my ignorance but the Transport/Routes/Layer are releated to the Development Class.. and ChaRM dont take in count this...
At the end you have 3 Development Clients...100/200/300..you need to create 3 project..
thxs
Wence

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

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

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

Transport layer and transport package

I have a fundamental query on transport package and layer.
Objects are classified in packages depending on the project and put in $TMP or test package else they are local ? Only objects belonging to a transport package can be transported , others are not ? How transport package is defined ? All objects must be a part of transport package else can not be transported ?
ABout transport layer, I understand this is used to define which path objects will take during transport particularly when there are multiple transport routes. But what are the advantages of it ? How we can define it (trx code/menu path) ?
Is it mandatory to use transport package and layers ?

Hi Mike,
Just to clarify a few basic concepts:
A transport package (formerly called a "development class", a term you may still encounter) groups related development objects. Whenever you create a new development object (table, program, ...) you have to assign it to a package; the object is then placed into a transport request. Alternatively you can indicate it is a local object (its package is then "$TMP") but such an object is non-transportable.
A transport layer identifies the route that transportable devmt objects must follow. Typically in your system you will have two layers: a layer usually called Zxxx (with xxx = SID of your development system) is used for your own developments. Another layer called "SAP" is used for transporting SAP objects, for example changes to standard SAP code implemented via transaction SNOTE and recorded in repairs. Without the "SAP" layer in place, repairs would be non-transportable.
Each transport package belongs to a layer. You assign the layer when you create a new package in transaction SE80. You can change the layer later on, but this is rarely needed and can cause quite a few side-effects. SAP objects always have layer "SAP". The layers themselves are managed in STMS, under "Transport Routes".
Hope this clarifies things,
Rgds, Mark

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

What are the responsibilities of Transport Layer?

What are the responsibilities of Transport Layer?

1. Keeping track of the individual conversations taking place between applications on the source and destinations on the source and destination hosts. 2. Segmenting data and adding a header to identify and manage each segment. 3. Using the header information to reassemble the segments into applications data. 4. Passing the assembled data to the correct applications.

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

Transport layer change ?

Is there any function module or class methods to chnge the tansport layer of a package. I need to change the transport layer from a program.
Best Regards,
Sreeram

>
Sreeram Manoharan wrote:
> Hello Florian ,
>
> I know to change it from SE80. I have mentioned that i need to change from a program.Read the question properly.
>
> Best regards,
> sreeram
Yes Florian,
read properly! You should have known he already knows how to do it through SE80. Anyone who reads this knows it, so why don't you? We all even know why he needs to do it through a program and not through SE80.
Please hug me!

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

How to change transport layer in a package

Hi,
I would like to change transport layer wrongly assigned to the one availble in the present system without any local change request being created. Please help!!

Hi,
Go to attribute of program there is an option for object directory entry click on that go to change mode now change package assigned on that and save it will change package for that.
You can also use SE03 for this purpose.
Rewards if helpful.
Regards
Gagan

Impact of the Transport Layer changes in the package

Dear Experts,
We are in the process of the Upgrade. As a part of the upgrade from 3.1to BI7. We have two Dev systems one is with the 3.1 - BWD and the other one is with the BI7- CBD now. We have transported all the objects with the Package : ZBWD (Where the transport Layer of this Package ZBWD).
And we have introduced the new Integration system(CBQ) in the landscape now and we have changed the Package ZBWD properties(We have changed the Transport Layer of this Package from ZBWD to ZCBD).
Can anyone please tell me the consequencies of this change in the package. We are planning to move this changed package, once the upgrade is finished.
Can any one tell me the consequencies of this change and also if we dont transport this package change in the other systems, then what wil be the consequences.?
Thanks
Raman
Edited by: Raman R on Aug 12, 2008 5:42 PM

Hi,
We have the package exists in the production which is with the earlier Transport layer called ZBWD.
As we have the new development system now, we need to change the Transport layer in that same package: to ZCBD.
Can anyone tell me will there be any impact of this change on the objects in the further landscapes? and also please explain me what are all the steps which needs to be carriedout if the transport layer got changed in the package?
Thanks
Raman.....

ChaRM: Standard transport layer

Similar Messages

Maybe you are looking for