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!

Similar Messages

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.....

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

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

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

Problem with Transport Layer

Hello every body,
We are doing an upgrade from 4.6C to ECC6. we have imported a transport request from 4.6C to ECC6.
When I change the transport layer of a package that is newly imported and save it, the system prompts for a local work bench request. How do I save it in a transportable request instead of local work bench request?
Regards,
Praveen

Hi
just as I wrote that behavior should be ok, so after creating the local request (so after changing the layer)
- Run SE09 and explode the node of the local request where package is
- Place the cursor on the package and delete it from the request
- Run SE80, choose your package and change the descrption: now the system should create a transportable request.
U make sure the layer is correct for the new system
Max

Updating Transport Layer in Packages

Hi all, I have a question on Transport Layers and that set in Packages.
The situation is a system that has been copied and renamed in 4.6 (System was copied from a combined install to a new install with all the customisations kept to provide a separated system with the same functionality) and then upgraded to ECC6. Now the existing customer packages are still assigned to the old Transport layers and thus if any changes are made the system insists on a Local Change Request. I know I can individually change each package to the new Transport Layer this then wants a Local Change Request to do this which can then be modified to the right Transport layer, and the package now allows the correct Transport Layer to be used when doing further modifications.
My question is basically Is there a SAP program that will enmass change old Transport Layer assignment to a new valid Transport Layer?
Was there a step missed in the original 4.6 conversion, and can that step be executed now the system has been upgraded to ECC 6?
An example of the entries in the table TDEVC: (sorry for the horrible format)
                        OLD     .    NEW
DEVCLASS     ZCCO    . ZCO-MAIN
INTSYS            (blank) . (blank)
CONSYS          (blank) . (blank)
CTEXT              (blank) . (blank)
KORRFLAG           X     .    X
AS4USER       USER     . USER
PDEVCLASS   ZCSD     . ZFED
DLVUNIT          HOME   . HOME
COMPONENT   (blank) . (blank)
NAMESPACE /0CUST/ . /0CUST/
Where the layer ZCSD is no longer valid and ZFED is a new Layer that is functioning correctly for cross system transporting.

Hi Jason,
I am not sure if there is a program after system copy to change, from old transport layers to new transport layers.
Have you already run BDLS after the system copy. It helps you in change the logical system name and client number as required.
Also the following link provides some insite to your query:
http://help.sap.com/saphelp_nw04/helpdata/en/3d/ad5bcf4ebc11d182bf0000e829fbfe/frameset.htm
ctc stands for Client Transport Control and represents a method of configuration for transport routes.
Kindly let me know if this was helpful
Regards,
Manomeet

Package assigned to wrong transport layer

I've changed transport routes in my system from 2 to 3 systems landscape.
unfortunately somehow a package(development class) was assinged to the wrong transport layer & as a result when users release their request its taken to Local Change Request i.e. dosen't appear in the import queue of the QA system
using SE80 I assinged the package to the correct transport layer & was prompted for a change request . The request goes to the local change request queue when I try to release I get the message Not All Objects In The Request Could Be Locked
Kindly assist

Hi,
After you made changes to your TMS make sure you have updated and distrubuted the configuration.
First release the request with previous package and You create another package with the transport layer.
Regards
Ashok

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

Transport layer error when refreshing

Hello!
I don't know if this is the right place to ask my question, so forgive me, if not.
I'm facing a weird problem within excel (2007 and 2013) when I'm trying to refresh or filter data retrieved from a cube (Microsoft Analysis Server 10.0.4000.0). The message is: An error was encountered in the transport layer. The weird part of the problem is
that it does not show up every time and not for every user. I can access the cube, I can read data from it, the problem appears when I try to add or remove fields, or when I try to refresh the pivot table. And not always!
There are cases when I try to build up a new pivot table, and the message appears, when I already have selected a couple of fields as filter/row label/column label or value. In these cases sometimes I can skip the problem by deselecting one or more of the already
selected fields, select a new field, then re-select the previously deselected fields.
There are other cases when I have a saved pivot table, that can't be refreshed because of the transport layer error. However, the same file with the same user ca be refreshed on an another machine.
I already have googled around, and I actually found a few forum entries with the same problem, but none of them was answered.
To narrow down the problem I tried to exclude hardware level network problems, so saved a file, which couldn't be refreshed on my laptop, and I tried to refresh it on a PC. On the PC the refresh worked, so I moved
my laptop next to this PC, and I connected the laptop to the network using the PC's network cable, and tried to refresh the file this way on the laptop. The refresh was not successful, so I even changed the IP address on the laptop to the IP that was set on
the PC. I also stopped the antivirus (which actually is identical on the PC and laptop). This way I wanted to ensure, that there is nothing blocking the traffic between the server and the laptop.
I also tried to find out, if the problem is user related. So i tried to refresh the file, that couldn't be refreshed on my laptop on the previously mentioned PC with my user. The refresh worked. I also tried to refresh the same file on my laptop with the user
originally used on the PC. The refresh did not work.
Thank you!

Hi,
It seems a common error.
There is a note that mentions the error, and was fixed since BI addons SP 8
Note: 1267942 - Custom macro not being executed on a workbook
Download and test the latest version: bi710sp12_1200-10004472.exe
This should fix the issue.
FYI: SAPGUI 640 is not supported by SAP since 2008. If you are using this version, please download the SAPGUI 7.10 as well.
Thanks
Edward John

Imported Objects - Package has a different Transport Layer

Hi,
We imported SAP objects into our DEV environment. All the objects are in a Package where the transport layer is ZB60 which does not exist in our DEV environment. I did a Request Consistency Check on the transport and I got the error "Only edit objects from package ZIVARA_SAP in local requests". I tried to change the transport layer to what we have in our DEV system which is Z9EV but it only created a local Workbench request.
How do I go about changing it to our DEV Transport Layer (Z9EV). The objects that we imported are NOT going to be a one time import/installation. We may be making some changes to the objects in the future and we want it to be transportable just like our own SAP objects. Your reply is greatly appreciated.
Thanks.
Giscard

Dear Giscard,
Try importing the objects with Transport of Copies, then you should be able to edit them in your DEV system.
Regards
Shailesh Mamidwar

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

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

2 consolidation routes, one transport layer - not possible

Hello everyone,
I have one DEV system and two QAS systems. Some of my development need to go to both of two systems, however some of them need to go to only one of my QAS.
So I have set up two transport groups: one link to both of two QAS and another one link to one of them. Because it is not possible for 2 consolidation routes with one transport layer, so there would be much of trouble when I need to transport my own development into that one QAS------I need to manually change the object directory entry/package for it first.
So I would like to know is there any way easier to set up the landscape so that the developer can easily choose the correct transport target in our situation?
Thank you very much in advance for your help!
Best regards,
Keith

Hi Keith,
please do not mix up transport groups (systems sharing one transport directory) with transport target groups.
If you have one development system DEV and two QA-Systems QA1 / QA2 then there are 3 options: Transport from DEV to QA1 only, transport from DEV to QA2 only and transport from DEV to both QA1 and QA2. To realize this, you need three consolidation routes starting in DEV. One with transport layer (say) ZQA1 pointing to QA1, one with transport layer (say) ZQA2 pointing to QA2 and on with transport layer (say) ZALL pointing to the transport target group which in turn points to QA1 and QA2. Then you need to create 3 packages (formerly: development classes) poining to one of these three transport layers. For example ZPACKZQA1, ZPACKZQA2, ZPACKZALL. Then when you create a programm you need to specify a package. Depending on the package you choose, the program will be transported to either QA1 only, QA2 only or both QA1 and QA2.
Best regards
Thomas

Transport layer change ?

Similar Messages

Maybe you are looking for