TMS settings

Hello,
I would like to ask you how can I configure my Test System, that the released transport requests can be brought back in my Test System?
Is there a parameter which must be set or something other?
Thank you in advance,
Noemi

Hello Noemi,
Your requirement is very peculiar. I've not seen such configuration and i think its fairly not possible.
Usually people do development and testing in different clients of same system. In this case they copy the request manually using SCC1 from the development client to the test client. This pose a drawback because workbench test is not fair.
if copying Scc1 seems time consuming then check the SCC1 batch report . Check following link :
Copy customizing on the same server
But the loop transport  being source and target the same system as per your requirement seems difficult.
Best Regards
Niraj

Similar Messages

  • TMS 14.5: Email Invitation Sends .msg Instead of .ics

    Currently the system attaches an empty .msg file rather than an .ics with the meeting details, I've searched for more information and checked the TMS settings but I must be missing something. Any help is greatly appreciated.

    Sounds like an issue between your Exchange server and Outlook client, since the web shows the correct attachment.  So TMS is sending the correct attachment, just getting converted somewhere, might be a good idea to ask your Exchange admins.  I don't know anything about Exchange, so I can't help there.

  • Logical components problem when checking project

    Hello,
    I have searched in the forum for a solution, but the people who had the same kind of problem managed to solve it with means that do not work for me.
    Here is the situation :
    - We have a three tier landscape, DEV-QAS-PRD, in transport domain DOMAIN_A, with domain controller DCA
    - We have our Solution Manager system, DCB, which is part of (and domain controller of) transport domain DOMAIN_B
    - The two transport domains are linked, as specified in SolMan prerequisites for managing systems from other transport domains. This has been tested, and transports can be forwarded and imported freely from one domain to another.
    - I have created the systems, RFC destinations, and logical component for the three tier landscape in SolMan system DCB. The RFCs are all OK.
    - I have created the domain controller DCA system in SolMan DCB, with RFC destination to client 0, as defined in the prerequisite for Change Request Management.
    - Finally, I have created a project in SolMan system DCB, with this logical component.
    When I try to do a Check on this project, in the Change Request management tab, I have green lights everywhere, except for the following :
    - In "Check logical components" : No consolidation system found for DEV-040 (our development system)
    - In "Check consistency of project" : Message from function module /TMWFLOW/CHECK_PRJ_CONS: No export system for PRD-020 (our production system)
    We have checked the TMS settings and transport routes, and everything looks OK.
    Any ideas on what to check/try would be welcome.
    Thanks,
    Thomas

    Hi,
    Check the status of the DC's in the track created in CBS.
    at following location.
    http://url:port/webdynpro/dispatcher/sap.com/tc.CBS.WebUI/WebUI
    There should be no Broken DC's in the track.
    If every thing is fine here and you still have problems then check by repairing the class path of the component.
    Hope this helps you.
    Regards,
    Nagaraju Donikena
    Regards,
    Nagaraju Donikena

  • Object dir entries reconciliation..

    Hello,
    Problem description:
    When trying to transport via transport connection, I get the error message that objects ned to be tansported separately. I have collected only necessary objects and collected automatically. This has worked for med in earlier systems, but not here.. so something is strange.
    I have switched BW development system from ABD to ABT. Some objects were transported from ABD to ABT and are hence assigned to a certain package. In ABT I have then set up a new transport layer/routes etc. and also created a new package for transportation purposes.
    So now I have a messed up system when it comes to object directory entries. Some objects seems to be assigned to the old package Z001 and some to the new Z002. Some objects have source system ABD (the old BW dev) and some have ABT. Some also have SAP.
    How can I reconcile all of this? I guess I will need all the objects to belong to Z002 with source system ABT (the new BW dev system)..
    When collecting the transport in the transport connection, and looking in "package", I don't see any package aassigned to the different objects..
    I get the error message:
    "changes cannot be made" & Object xxxx xxxxxx cannot be saved to order" (100s of objects)...
    How do I proceed?
    Br,
    F C
    Message was edited by:
            F C
    Message was edited by:
            F C

    Hello and thanks for your input!
    The old transport route was ABD --> ABT --> ABP, Now there has been a change of transport routes to ABT --> ABQ (new sys) --> ABP.
    Already in the first setting, there was a problem with the collection of transports. Therefor, I had to install parts from Business Content directly in ABT. Some was however transported from ABD.
    When everthing was in place in ABT, I deleted the old TMS settings and created new transport routes etc.
    I have confirmed that the new routes are working. However I think that there is a mix up in the object directory entry now... Do you agree?
    When looking in SE03 (object directory entry), I see that there are object entries with ABD set as original system and belonging to the old package (that was used for transports from ABD --> ABT)..
    When collecting objects in the transport organizer I get lots of errors. When looking at these objects in SE03, I see that these seem to belong to the correct package and original system (according to the new setup).. Then why don't they work?
    Any ideas on how to make this work?
    Regards,
    F C
    What is needed in order to make this work?

  • How to create Rfc for EP system in Solution manager

    Dear experts,
    I am doing ChaRM configuration for my EP system ( java only).
    I also configured CTS+ successfully but we want to integrate this with Chram in solman.
    I have done all configuration according to standard doc for ChaRM.
    But when creating project from solar_admin it is giving "   NO RFC for DEP system"
    so please suggest me how to create RFC for java system in Solution manager.
    thanks in advance
    dhiraj

    Hello,
    You need to setup an ABAP communication client and system, that's done through the TMS settings:
    For source system:
    - CTC                                              1
    - CTS_SYSTEM_TYPE                          JAVA  (others for a MDM system)
    - NON_ABAP_SYSTEM                          1
    - COMMUNICATION_SYSTEM:              (SAPSID of the ABAP communication system (e.g. the domain controller))
    - NON_ABAP_WBO_CLIENT                    (Client of the ABAP stack on which the Transport Organizer Web UI (CTS_BROWSER) is activated and will run.)
    - WBO_GET_REQ_STRATEGY                 TAGGED
    - WBO_REL_REQ_STRATEGY                 MANUAL
    For quality and production Java system (target systems):
    - CTC                                              1
    - CTS_SYSTEM_TYPE                          JAVA (others for a MDM system)
    - NON_ABAP_SYSTEM                         1
    - COMMUNICATION_SYSTEM:                 (SAPSID of the ABAP communication system (e.g. the domain controller))
    - DEPLOY_WEB_SERVICE                       CTSDEPLOY
    - DEPLOY_DATA_SHARE:
    When this is done correctly, you will see the fields ABAP communication system and client populated in SMSY.
    When ChaRM needs to operate on the non ABAP systems, it will take the RFCs for the communication system and client.
    Best regards,
    Miguel Ariñ

  • 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 with  a 2 system landscape

    Hello ,
    we have only a 2 system landscape for our ERP systems.
    When I now click on the check button on the maintainance project. I receive an error :
    No consolidation system found for DEV-001 (project TEST_CHARM)
    No track for project TEST_CHARM with log. system P23/001
    Message from function module /TMWFLOW/CHECK_PRJ_CONS: No export system for DEV-001
    TMS ( without any client  routes)
    DEV->PROD
    Any suggestions ?
    Regards

    Hi Daniel,
    we are using CHaRM in various transport landscapes with 2 and up to 5 systems. This is all working fine. Please make sure there is a consolidation transport route from DEV, also all RFC connections from Solution Manager to your Transport Landscape are set up, inlcuding 000 clients.
    TMS settings need CTC=1, and Trusted Services in STMS need to be activated.
    Other prerequsites are:
    - Systems are deined in SMSY
    - Transport Domain link between Transport domain controllers
    - Logical components defined in SMSY (with correct system roles)
    - Lofical component added to SMI project
    If this is all fine, please hit button "Shipment Routes" in SOLAR_PROJECT_ADMIN in tab page "System Landscape" => "Systems" You should see all transport routes required for this project.
    If this works, you are in a good shape.
    Best Regards,
    Holger Slomka

  • Transport target group and routes setting for 2 system landscape

    Hi!
    I have 2 system landscape (DEV with 2 Clients, 100 CUST and 200 TEST and PRD with productvie client 100).
    Currently I have the standard TMS configuration for 2 systems (with tranport layers/routes ZDEV and SAP) .
    Now I  have to set up my TMS settings client specific
    (Development in DEV 100 and transport to the DE 200 TEST and PRD 100).
    I have created tranport target group /B-DEV/ with both target goals:
    DEV 200 and PRD 100.
    <b>What are the further settings for transport routes?
    I assume, I have to delete the existing routes ZDEV and SAP?
    what are the next steps? </b>
    Thank you very much
    regards

    Ok, I have in DEV system:
    Client 100 (Customizing)
    Client 200 (Test) (it can be considered as replacement of QAS-system, because we only have 2 systems)
    PRD system
    Client 100 (Productive client)
    So we would like to set up the transport management system client specific, in order to develop in DEV 100 to test in DEV 200 and to use the transports in PRD 100.
    Thank you very for your help
    regards

  • CHARM Configuration Error - No Consolidation System

    Hi
    Im facing following errors in solution manager's CHARM.
    No consolidation system found for SSD-150 (project ZCHARM_GIL)
    No track for project ZCHARM_GIL with log. system SSD/150
    i have more queries.
    1.solar_project_admin > system Landscape>  systems i have following config
    Logical Component : SAP SOLUTION MANAGER
    Product: SAP SOLUTION MANAGER [Solution Manager ABAP Stack]
    Product Version : SAP SOLUTION MANAGER 7.0
    DEvelopment SYstem : SSD: 150 ( SSD is my solution manager SID)
    QAS : Blank
    PRD : Blank
    Do i need to maintain values GSD , GSQ , GSP (satelite system DEV, PRD, GSP)
    2. in my satelite system DOMAIN_GSD transport route
    System GSD - GSQ Transport Group - System GSQ
                 /GSQTRG
    System GSD : Transport Stratergy - Mass Transport Checked
              Transport Layer - ZGSD
    target group: /GSQTRGRP/ GSQ  200
                    GSQ  300
    System GSD : Transport Stratergy - Mass Transport Checked
              Transport Layer - NONE
    Transport Route : GSD - ZGSD/SAP - /GSQTRG - 300/200- GSQ
    Can i configure charm with above scenarion where transport groups have been defined

    Hi
    This error occurs if you dont define the client dependent tms route in satellite system.
    First visit this blog
    First steps to work with Change Request Management scenario in SAP Solution Manager 7.0
    then in spro change request management general settings....visit the img help for TMS settings of
    further
    TMS
    TMS Setup
    http://help.sap.com/saphelp_nw04/helpdata/en/14/c795388d62e450e10000009b38f889/frameset.htm
    more help
    http://wiki.sdn.sap.com/wiki/display/SM/ChangeRequestManagement
    Regards
    Prakhar

  • 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: Transport strategy

    Hi!
    We have the following system landscape:
    EO1 --> QO2  --> VO2
    EO1  --> VO3
    VO2 and VO3 are both the virtual systems.
    Between EO1 and VO3 and Q02 and VO2 we have a lot of transport routes (SAP, YABK, ZEO1, .., ZIAN).
    Now we would like to use ChaRM approach with new client specific transport routes (EO1 --> QO2 --> PO1) as well as leave the old TMS settings unchanged.
    The questions we have:
    1) Do we need standard transport route u201CSAPu201D for the ChaRM approach?
    2) Can we leave the old TMS configuration for old requests, but use ChaRM with new configuration?
    Thank you very much!
    regards
    Thom

    Thom,
    1) The suggestions I see:
        a. create a Transport Group which contains your VO3 and QAS system and create the necessary transport routes to this group. If you now setup your project for ChaRM and only specify the real systems, SolMan will recognize the correct systems (even though it will give you a full overview of STMS when clicking the button 'Shipment Routes' in the System Landscape of the project - once the Task List is created, you'll see ChaRM only mentiones the systems you've added in the System Landscape). The disadvantage of this is that all Transport Requests you release in your DEV system will be added to the import queue of QAS and VO3. This is of course only a disadvantage if both systems don't need to receive the same changes.
       b. Not 100% sure if this is technically possible. Create separate consolidation routes for VO3 and QAS from DEV. Again when you specify the correct systems in the project, SolMan will use only those.
    As far as I know, ChaRM doesn't make a choice based on type of transport route, such as 'SAP'.
    2) a. I know 'single transport' is recommended by SAP, but this is not a showstopper for the configuration of ChaRM. ChaRM also works with 'mass transport'.
        b. ChaRM needs to be client-specific, can be that here there is some interference between ChaRM and non-ChaRM.
        c. As ChaRM corrections are all assigned to a Maintenance Cycle and a Maintenance Cycle is based on a CTS project in your DEV satellite system; SolMan is in complete control of your Transport Request. What I mean with this is that if you do automatic import on your systems, only your non-ChaRM changes will be imported. Because by default ChaRM changes all status switches of the CTS project to 'inactive'. From the moment you trigger the import from a Transport Request out of ChaRM in Solution Manager; only then the necessary status switch will be activated and it will be possible to import a change into your satellite system. Periodic import of ChaRM changes is also possible, but has to be scheduled using the correct Task List out of SolMan.
    You can look and change these status switches manually in your satellite system with TA SPRO_ADMIN, select the correct project and navigate to tab Transport Request. Here is a button 'CTS Status Switches'.
    Hope this helps you a little further!
    Good luck and let me know if you have any more questions...
    Roel

  • How to display particularDefault  client while transorting in to Production

    Hi Gurus
    While importing the tp into production through  TA stms_import >selecting the Request>Click on Truck button--> in the new popup screen( synchronous/Asynchronous, client number etc)  every time it is prompting for client  with blank!
    Actually here i want to put client number  100 as a defult value for every time.
    Is this possible to set default as 100.
    I tried with personal setting available in TA STMS , still i could not able solve..
    Thanks in advance
    BALAJI

    As far as i remember you can do that by adding the "client specific settings" under "Standard transport layer" tab in "change system attributes".
    For that you have to logon to the domain controler and edit the target system configuration in STMS
    As you said is working in one of your other systems, then you can use that to compare the TMS settings.
    Regards
    Juan

  • TA SCCL - Copy in new client

    Hi,
    after a few weeks testing "SAP Netweaver 7.0 Trial" I want to start modelling in the SAP BW Workbench.
    Unfortunatley there is a problem with the Transaction "SCCL".
    After creatng a new Client via TA "SCC4" an logging in as "SAP*" i wanted to "Copy Client" via TA "SCCL".
    After one minute there is a error message  "SAP client copy cannot open log
    localhost\sapmnt\trans\log\CC000014.nsp"
    Can anyone help me or give me a hint?
    Thank you

    Arne,
    I'm guessing one of two things here. (1) Permissions, but I'm less sure of this or (2) the file path. Remember that there are 2 main SAP file systems here - /usr/sap and /sapmnt - be it UNIX or windows. Typically, /sapmnt will be followed by the SID and 3 other folders: /sapmnt/SID/exe, global and profile. 'trans' on the other hand lives under /usr/sap/ (even if it is shared across the landscape).
    I'd suggest first that you confirm this file exists i.e. can you take the path "
    localhost\sapmnt\trans\log\" and find a file called "CC000014.nsp"? If not, you may want to confirm your TMS settings as the CC functions will borrow configuration from TMS for its functions.
    If none of this works, can you tell me what OS you are running here?
    Thanks,
    Tim

  • Strange error when check a project

    Experts:
    When I check a project , I get error: Message from function module /TMWFLOW/CHECK_PRJ_CONS: No export system for PRD-010.
    1) SDN has some threads about this error. But none of them fits my case.
    2) OSS has 2 notes(e.g.1017929)  with the correction contained in SAPKITL421 and so on, but my SM has much higher level than SAPKITL421.
    Would you please share your experience on this trouble-shooting?
    I appreciate.

    HI,
    Please make sure there is a consolidation transport route from DEV, also all RFC connections from Solution Manager to your Transport Landscape are set up, inlcuding 000 clients.
    TMS settings need CTC=1, and Trusted Services in STMS need to be activated.
    Other prerequsites are:
    - Systems are defined in SMSY
    - Transport Domain link between Transport domain controllers
    - Logical components defined in SMSY (with correct system roles)
    - Logical component added to project
    You can also check this
    1) Go to Solar_project_admin
    2) System landscape
    3) Systems
    4) Click on Shipment routes
    You should see all transport routes required for this project.
    Update once done!
    Regards,
    Gagan Deep Kaushal

  • Project Plan for ChaRM implementation help

    Hi everybody,
    I am creating a Project Plan to implement ChaRM in a new project.
    This is the first time i am doing that task and i must deliver that plan to a team soon.
    So i would like to ask you about comments, idea, missing items on my current plan please
    (I voluntarily did not mention Estimated Duration, team to perform, requestor, etc..)
    Pre-Check :
    - Validate System Component and SP Level
    - Request Ids & roles on satellite systems / Build USER IDs & roles created on all satellite
    - Verify TMS settings for ChaRm
    - RFC Connection creation / RFC TEST
    - Activation of cross system Object Locking - CSOL
    Project :
    - Determin type of project for ChaRm (implementation / Maintenance)
    - Create project
    - Activate project for ChaRm
    - Activate project for task lists
    - Id's created in SolMan & satellite
    - Establish Business Partners
    - Approvals (Change Control process)
    - Test creation of Change Request
    - Test :Import transports between dev - QA  / QA to prod
    Thank you in advance
    and thx for all the things i understood with all the topics of this forum.

    Hi,
    Follow RUN SAP Roadmap for Implementing your solutions. Go through [this link.|https://websmp109.sap-ag.de/runsap] This explains Run SAP and how you can plan to implement your SAP solutions (including ChaRM).
    Run SAP has 5 phases.
    Assessment and Scoping
    Define Operations
    Setup Operations
    Handover into Production
    Operations and Optimization
    Hope this solves your problem.
    Feel free to revert back.
    -=-Ragu

Maybe you are looking for