ChaRM: usage of several transport layers in different maintenance projects

Hi!
I have heared on SAP TechED about the following possibility:
it should be possible to have several maintenance projects with different standard transport layers.
Can some one of you confirm or reject this statement?
Our problem is we work in same client in DEV system and transport in same client in QAS system and have several transport layers. All of them should be used by ChaRM.
Other question:
which new functions will be come with SPS 18 in ChaRM?
Thank you very much!
Holger Thomasson

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

Similar Messages

  • 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

  • ChaRM with several transport layers/routes

    Hi!
    We have a very comprehensive transport landscape where more than one transport layer is necessary.
    The reasons therefore:
    we implement none-SAP software and need an extra transport layer therefore
    the developers still need an extra transport layer because of they assigned them their packages
    Currently we have one and the same client in DEV system where all the transport layers reside.
    Now we are thinking to implement ChaRM for all the transport layers.
    1) Approach of splitting transport layers and working with different DEV clients
    We split the transport layer and assign them the different standard layer
    transport layer ZDV1: client 100
    transport layer ZDV2: client 200 
    transport layer ZDV3: client 300
    Question:
    Is that possible to have here one maintenance project with more that one DEV system
    (DEV:100, DEV:200 and DEV:300)?
    Any helpful information will be very appreciated.
    Thom

    Hi Thom..
    transport layer ZDV1: client 100
    transport layer ZDV2: client 200
    transport layer ZDV3: client 300
    Why you have 3 Transports Layer???...
    if you have
    DEV100                QAS100    PRD100
    DEV200
    DEV300
    Usually you have only 1 Layer from DEV100 to QAS100 (Consolidation Type)
    To move from DEV100 to DEV200/300 use SCC1
    IF you have
    DEV100     -
    > QAS100   -
    >   PRD100
    DEV200                QAS200 
    DEV300
    You create 1 transport group
    DEV100 -
    > QAS100 ---> PRD100
                     |-->QAS200
    Thanks
    Wen

  • ChaRM with several transport layers

    Hi!
    We would like to use Solman ChaRM approach.
    According to SPRO-documentation ChaRM only supports consolidation routes from standard transport layer.
    We have besides the standard transport layer other transport layer and have the following question
    1)What will happen when the developer try to change and import into QAS system object assigning to none-standard transport layer?
    1a) ChaRM does not allow to change this object and the appropriate pop up window comes up
    1b) ChaRM integrate this transport layer as standard transport layer
    Any helpful information will be very appreciated
    Thank you very much!
    regards
    Thom

    Hello Thom,
    I think, your question is almost independent from CHaRM. This is handled by the transport management system (TMS). If your developer changes the object assignment to a transport layer, and there is a transport track for this layer to the (same) QAS it should work. But if this QAS is not configured in CHaRM as a target system (in SOLAR_PROJECT_ADMIN), SolMan will probably raise an error message.
    Also if the transport layer assignment / dev package not valid for this transport track, you will not able to release the transport -> SolMan is just using TMS mechanism and this will bring up an error message in CRMD_ORDER.
    Unfortunately you can't see the transport logs in CRMD_ORDER directly, so the answer to 1a) is: In case of trouble releasing the transport you will get an error, but not the full error message.
    1b) ChaRM cannot change a transport layer to a standard transport layer, this must be done using STMS on the transport daimn controller.
    Regards,
    Holger

  • ChaRM: usage of ChaRM and none-Charm transport strategy

    Hi ChaRM-TMS Gurus!
    We have the following [SAP system landscape |http://www.file-upload.net/view-1086963/SDN_TMS_Ist_Soll.jpg.html] and would like to use ChaRM approach simultaneously.
    What are the minimal requirements concerning transport layers/routes, which settings should be changed?
    How much and which transport layer/routes does ChaRM need?
    a) 1 any new transport layer/route
    b) standard transport layer, transport layer "SAP" and others
    Should all the standard transport layer/routes from virtual systems to real QAS and PRD systems or can I start as follows:
    1) Leave the current TMS settings unchanged
    2) Activate the extended transport control
    Result: the current setting will be client specific and all the old transport requests will be moved to client specific transport routes
    3) change the transport strategy (from mass transport to single transport)
    3) Define new transport layer
    4) Define  new transport route for SAP objects from DEV to QAS
    and assign the transport layer from 3) (client specific)
    5) Define  new transport route ZXXX from DEV to QAS
    and assign the transport layer from 3) (client specific)
    6) Define the delivery transport route from QAS to PRD (client specific)
    7) activate and distribute the settings
    Thank you very much indeed!
    Thom

    Hi Martin,
    Solmaniacs' assumptions are correct. You can have as many source clients as you want.
    As long as
    - STMS configuration (transport routes, and domain links) are consistent
    - SMSY configuration (logical components are declared properly with assigning the right role types to systems/clients)
    - Project declaration are done correctly (so that from Solman solar_project_admin you can read the STMS as confiured in the distant STMS domain)
    - IMPORTANT: those configuration GO ALONG with each other !! (SMSY should nt contradict STMS for example...)
    The tasklist that is generated for each Solman project will be as follow
    - Node 1: Header Tasks (commun to all systems)
    - Node x: Corresponding to track x declared in Project (each Source System will have his own node with the corresponding track under)
    - Node x+1
    - Node ...
    - Last Node : Tasks for Tasklist closure - checks on scma consistancy and CTS projects closure
    So you'll always have n+2 nodes in your tasklist; n beeing the number of declared source (=dev) systems in project
    For each action launched from change docuemnts like creation of TR, release of TR or Retrofit (as Solmaniac said) you'll have an additional pop-up that will appears letting you choose the system you want to use for the action
    Hope its helpful
    Regards
    Khalil

  • ChaRM: Several maintenance cycles in one maintenance project?

    Hi!
    We are working with urgent correction within ChaRM and thinking about to implement the normal corrections as well.
    Our ChaRM workflow for normal corrections is characterized by:
    a)corrections with different Life cycle (those who will be processed within 1 week, other with 2 week, etc.)
    Questions:
    1) Is it possible to have several maintenance cycles for one maintenance project to handle condition u201Ca)u201D?
    2) What will happen with all the normal corrections and urgent corrections that have a long life cycle (status: in development, test, etc.) when the charm manager set the status of maintenance cycle in u201CGo liveu201D?
    Thank you  very much!
    H. Thomasson

    Hi Holger,
    Maintenance cycle and SMI project is a 1:1 relationship.
    In status GoLive you will be able to continue developement/work on normal corrections but you will not be able to release any transport requests/create transport of copies so your testings in QA will be limited.
    In phase GoLive you are able to import requests into production.
    Normal Corrections which have not been released yet are not lost. Depending on your scenario you may switch phases back to "in dev with rel." after you imported into production. It is not necessary to close and recreate maintenance cycles if you use one project for daily/weekly maintenance.
    /cheers

  • Is there a way to order several different iPhoto projects at one time, on the same order? (to avoid paying shipping on each individual project?)

    Is there a way to order several different iPhoto projects at one time, on the same order? (to avoid paying shipping on each individual project?)

    No, unless they're all prints.
    (117535)

  • Transport Layers and sharing of transport directories

    Hello Experts,
    We are on R/3 4.7 Enterprise extension set 1.10 with oracle 9i .
    In a three tier architecture in R/3 with development , quality and production , how do we assign transport layers and how many transport layers do we need at the time of TMS configuration ?
    Secondly in our R/3 three tier landscape , we hv transport directories (trans ) on every system on all the three systems ,then how are they shared with each other , i mean on wt basis do they recognise each other and transport continues frm DEV to QUA and then to production
    Requested to revert at earliest as this is very urgent . points guaranteed .
    Regards,
    Somya

    Hi ,
    1) sap and Zdev are transport layers....which will be assigned by default when you configure TMS.
    what does SAP and ZDEV do ?you can take it like this..standard programs..will go through sap...and customized like (Z or Y programs )will go thorough Zdev path.
    the program routing is taken care automatically..(just for your info)
    you never need to define transport layer between QA and PRD unless you want add one more Sandbox system for more quality testing..(normally in 3 system landscape you dont configure transport layers between QA and PRD
    2) as of now in your scenerio ..its not being shared..
    if you plan your DEV as transport domain controller..then in QAS system execute STMS-->system Overview >QAS double click>Communication (change transport domain to Domain controller transport domain) and also transport tool >transdir>(should poing to
    <domain controller>\sapmnt\trans)
    save the changes..
    on the domain controller . in TMS you will see a system waiting for inclusion onto domain ..approve that..and follow the same procedure to add PRD system also..
    then all the systems will share the same transport directory..
    (Caution: once you setup the landscape like this ..changes to any system using STMS like QAS and DEV  has to be done only on Domain controller.)
    Cheers
    Kamal

  • Collapse multiply layers with different transparency into a single solid filled layer

    Hi,
    I want to collapse a complex scene with all different layers and different transparency into a single layer (or as few as possible) to optimize the flash file for online (were experince proformance issues).
    I have tried the combine and manually copying pasting into one layer but it cuts the fill below and replace with transparent fill. I want to have a end file that is 100% solid.
    Is this possible?
    Thank you
    Darren

    You can create groups and then paste all your groups in a single layer. That won't 'cut' them into each other and the transparency should be maintained. It won't help you with performance though, since the complexity remains the same.
    If you have tons of complex vector shapes, it might be a good idea to create a transparent PNG bitmap from illustrator.
    That may increase your filesize but it will give you a tremendous performance boost.

  • Transportable tablespace accross different oracle versions

    Hi
    Do I need same oracle versions if I want to transport tablespaces ?
    i.e Can I transport tablespaces from oracle9i to oracle 11g ? or from oracle 10g to oracle 11g ?
    I read the documents however Im still confused.

    Thanks, I have read the document and notice that from oracle 10g and onwards I can transport tablespaces accross different oracle versions.
    I think we can change the endian format via rman hence no need to have same endian format
    "Beginning with the Oracle10g database, a tablespace can always be transported to a database with the same or higher compatibility setting, whether the target database is on the same or a different platform."

  • Transports between 2 different versions of SAP

    We are developing a product on ECC 6.0 (IDES) system and I'm trying to figure out how we can delivery the product to our customers.  We have our own development namespace in SAP.  Some of our customers are on ECC 6.0 and some are still on 4.7.  Can we send a transport that was created in ECC 6.0 to a 4.7 system?
    Thank you,

    Hi,
    It is possible to transport between 2 different versions but it is dangerous : you have to know exactly what you are transporting and the dependencies with standard SAP code.
    So, it is much safer to recreate your source code in a developement system of the new version and create new transport orders from there...
    Regards,
    Olivier

  • 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

  • Charm: Registering an External Transport

    Hello,
    Can one take an transport from and external system and register it with ChaRM and move the transport through the landscape?
    I see in SAP note 1150426 that one can register a transport, but it appears that the transport must be modifiable. One must be able to set the attributes SAP_CTS_PROJECT with the value of the change request (M000*). This can not be done for a transport from outside.
    Can one use ChaRM for external transports?

    Hi
    it's not possible to register external (or already released) transports for ChaRM or to transport them with ChaRM.
    I recommend to transport them manually. Maybe you can documentate this in an admin change
    What is possible but has cons:
    -Import tranport into Dev manually
    -Include all objects in a ChaRM transport
    Cons:
    -You need the same transport layer
    -it is not 100% the same than importing the original transport
    regards

  • HT201263 After attempting to restore my iPhone several times on two different laptops, I have not success.  My iPhone is locked with a passcode and I must enter it.  The wrong passcode is what disabled my iPhone.  What can I do?

    I cannot restore my iPhone after several attempts on two different laptops.  This is the message, "iTunes could not connect to the iPhone because it is locked with a passcode.  You must enter your passcode on the iPhone before it can be used with iTunes."  I don't have that option on my  iPhone because I locked myself out, it reads "iPhone is disabled, connect to iTunes" what can I do?

    Place your phone in DFU mode (search Google) and restore.  You will lose all data on the phone.

  • Is it possible to link up several macs, all with different login details, to an apple TV 2 all at the same time?

    Is it possible to link up several macs, all with different login details, to an apple TV 2 all at the same time?

    You can stream from multiple libraries but they must all be using the same home-sharing ID

Maybe you are looking for