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

Similar Messages

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

Imported .psd file has a different black

I have a indesign file with a 100 % black background, where I have Placed a .psd file. But when I print the document, the transparent areas of my .psd are printed as dark grey.
Does anyone know where I went wrong? It's quite frustrating, even without a deadline.

OK.
First, let me say that your file prints fine here, just as it is, on my Fiery-driven Xerox Phaser 790, both directly from InDesign and from a PDF/X-1a export in Acrobat, so I think the problem is in your workflow someplace.
There are probably a combination of things happening, but the first thing I would do is change the background color to an RGB Black rather than the default 100% K black swatch. Keeping the background and the image in the same color space will help when it's time to do any conversion, and I think you may be donig multiple conversions before the toner hits the paper. Change the flattener space to RGB, too.
This is very similar to your use of [Registration], but will generate a CMYK rich black that is actually printable, in theory, on any equipment. You may still have some trouble with fusing the toner and flakeoff if the mix is too dense, so if that happens, reduce the density of the RGB black a bit, it should still be much darker than 100%K.
If that by itself doesn't fix the problem, the next step I would try would be to export a PDF. Try both the [High Quality Print] and [PDF/X-1a] presets to start. I picked those because the first one does no color conversion or flattening (and should yeild a file with an sRGB background) and the second will convert to your CMYK profile and flatten the transparency.
Let us know what results you get at that point, and we can take more steps if necessary, but I don't want to complicate things too much before we have to.
Oh, and before I forget, you need to add a bleed and extend that black background for trimming unless your print is capable of printing all the way to the edge on that size sheet (and I'd add it anyway, even if the printer is supposed to print borderless).
Peter

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

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

RMI live object Object ID at transport layer

Hi...
On the server side, when the server object is created, the constructor of UnicastRemoteObject performs an exportObject(). Inside exportObject(), an UnicastServerRef object is instantiated and exported. It creates a live reference object (the transport layer) which contains an IP address, a TCP port number and an Object ID.
From some article i read this.
Then a mapping from the Object ID to the stub and skeleton is registered in an object table residing in the transport layer.
Could nyone plz tell me wat is this:
1.Live reference object
2.Object ID
How it relates to stub and skeleton and wat is this mapping?
I searched a lot in UnicastServerRef class's exportObj() method, it further defines some Target class object. In fact i searched all this in Util class then WeakClassHashMap, WeakHashMap, then SoftReference...But i did not understand Object ID , live reference object etc.
Any suggestion will be appreciated.
Tx in advance
Bye
Naseem Khan

1.Live reference objectAn instance of java.rmi.server.ServerRef (which extends java.rmi.server.RemoteRef). The concrete instance happens to be called LiveRef and it is defined in a sun.* package. That's all you need to know.
2.Object IDAn instance of java.rmi.server.ObjID, i.e. a unique identifier for the remote object.
How it relates to stub and skeleton and wat is this
mapping?The stub (and skeleton when you have one) contain the ObjID and it is passed to the server host along with each call. At the host there is a mapping table from ObjID which tells the RMI runtime which object to dispatch the call to.
If you want to know more you need to look at the sun.rmi.* source code. Of course this only applies to Sun's implementation and you don't need to know any of it to write RMI programs.

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

Error in BW import objects

Hello,
We're trying to import into Quality BW environments the required objects to store the information generated by SAP Data Service information.
In tx RSA1 the source system for DS has been created and check works fine, but when we import the transport order following error is showed:
Could you help us?
Thanks,
Àlex

Hi Alejandro,
Exactly this error due to the mismatch source type. May be the configured QA source system working fine but importing object from Development referring different source type.
Hope the problem will be resolved after correcting the source type.
Regards
M Ramesh

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

Hihaving a query like that who has done the Transport? How can i trace who

having a query like that who has done the Transport? How can i trace who has done the transport (Import).
I have tried with following steps but unable to find the right person.
1. Go to TMS and disply the appropriate queue.
2. Select menu path: Goto>Import History.
3. Select menu path: Edit> Dipaly More.
4. This will give the the "User" column.
But my problem is the transport has happened long back. is there any other way to find out old import request who has done the transport.
Please someone help me out on this.

Do this may it can help you.
At the last step where you had given "diaplay more"
do this inspite of that:
Extras --> Personal Settings
Check the option "Query Interval Time" and try again.
Best of luck !!!

How to create a transport layer ?

Hi expert,
a transport layer, what is ? and how is possible to create ?
tks,
bye.

Hi Roberto,
The transprt layer is nothing but creating a new system...
this can be done by Basis people.
generally the package is assigned to transport layer..
so when ever you create request or transport automatically the transport layer is assigned.
Regards,
Prabhudas

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

Transport Package doesn't show up in pending imports after Package upload.

Hello,
I am importing WPC web content (Transport package) (http://help.sap.com/saphelp_nw70/helpdata/EN/46/77da3bb8036ef0e10000000a1553f6/frameset.htm ). Transport Package doesn't show up in pending imports after Package upload. I repeated the package upload. Still its not showing under "Pending Imports"
Anything else has to be done while importing a transport package (wpc web content).
Thanks
Tony

Hi Martin
Thanks, it worked!
A note when uploading different files with "non-functional" extensions could have been nice there.
/Martin

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

Imported Objects - Package has a different Transport Layer

Similar Messages

Maybe you are looking for