Transport Request - Subtask changes

Hi All,
I have done the changes in a include and structure. But already one person is working on that include and structure. My changes are activated and created a sub task under his main request. Now he wants to move his changes to other system which inturn will move my changes also. But I dont want to move my changes now.
Plz guide me how to resolve this..
I can change the main request owner and move the subtask which is under my name alone to any of my existing request?
Thanks,
Karthik

Hi,
The only solution to your problem is to remove your changes from the include, then release the change request and re-apply your changes to the include.
Creating a new change request with your task will not resolve your problem because all the include source code will be transported with the existing change request. (new versions of includes/programs are created only if there is no unreleased change request for the object).
Regards.
Nicolas

Similar Messages

  • What's the difference between transport request and change request

    Hi, I am reading TMS part of TADM12-1 now, and confused about two terms mentioned in this book, transport request and change request.
    Is there any difference with them? Please advise. Thanks
    James

    In the context of course tadm12 transport request = change request

  • Transport request number change.

    hi
    can any one help me in this one
    i created transport req number for main program while modifying the program.after that i changed text in text-03 while saving this one it asked me the TR number unfortunately i saved this in another TR number now the problem is the text is not replacting in main program.
    it is giving error messege the task is locked.
    Plesase tell me the solution.
    by
    venkat.

    Hi,
    To delete your transport request first you have to unlock the request otherwise it will display you the message that object has been locked.
    To unlock go to SE03, enter your transport request and go with unlock.
    Now delete the entire request by selecting that request right click delete or if you want to delete object wise then select the object and go with delete.
    After deleting that TR, again save it in the request you want.
    <b>Reward if helpful</b>
    Rgds,
    Shakuntala

  • Error releasing transport request for change document object

    Hi Gurus,
    I created a new change document object for a Z-table. When i try to release the transport request in the development system it terminated with a message "Export application-defined objects       17.12.2009 11:07:45 Not yet executed". The transport request continued to be in the "Release started" status and i am not able to release it.
    I checked in the co file & data file directory for this request, The co file is available but the data file is not created.
    Could you please let me know how to solve this?
    Regards,
    Immanuel.

    It was a problem with some basis settings. Was rectified by the basis team.

  • Dependency Information for Transport Requests in Change Request Management

    If two CTS projects are not assigned to SOLMAN projects, it is possible to define a dependency successor/predecessor relation between two transport requests for the import order. For example I can state that I have to import TR 1 only after the TR 2.
    When the CTS projects are assigned to SOLMAN projects, even though you have defined the dependency relation, this is not respected and from the Change Documents you can perform the import in the order you want.
    How can I activate this check also in Change Request Management?
    Thanks
    Antonello

    Some things you could take a look on:
    1) start report /TMWFLOW/CONFIG_SERVICES --> here you can define system, client and project specific locks.
    2) Transaction /TMWFLOW/CMSCONF --> also some options for locks and definition of critical objects
    3) Transaction /TMWFLOW/LOCKMON --> monitor screen for locked objects and requests.
    This is actually not the same functionality as have it in CTS projects directly especially as the locks are removed once a request is removed. The most important thing is still missing here (or at least I haven't found a way to activate): sequence control when importing requests out of parallel projects into production (to prevent downgrading). 
    Best Regards,
    Andy

  • Transport Request while changing InfoPackage

    Hi,
    I have a 2 different info packages on 2 different infosources which are of flat file upload.
    Whenever we want to load the data, we change the file name in the External Data tab of the infopack and schedule to start immediately.
    For one infopackage, system is asking for the transport request whenever I change the source filename but for the other one system doesn't prompt for transport request. It starts loading without any message.
    Can anyone please advise what could be the reason for asking request for one infopack and not for the other one. Is there is any settings ?
    Please advise.
    Thanks
    Ramesh Ganji

    Hi,
    one got transported from development system and is assigned to a development class --> the system puts it into a request.
    the other one is not transported and just a local object --> the system does not need a request to track the changes.
    regards
    Siggi

  • How to find a transport request attached with an activity

    Hi All,
    A plant was deleted in development system and moved to quality. This is not yet moved to Production.
    I want to find with which transport request this change is moved to quality.
    I have used SE03 but no luck. I may be doing wrong. Please help.
    Thanks in advance for your help.

    Hi Friend,
    Goto the Transaction code SE01, there  in the Menu you can fine the Find request option  ,
    If you goto that screen in the next screen you can find the REQUEST TYPE and click on that , you can find the task type and their click on your Activity type and execute...
    You can able to find  TR.
    Or
    If you know the program or Function module to which the changes are applied , then it is more easy..
    In the program SE38 , in the Utilities you can find the       VERSION MANAGEMENT.
    There you can find teh TR..
    Hope it is clear, if not revert back with more details.
    regars,
    santosh

  • Regarding User and Transport request

    I have unreleased transport request still, created at old client 5XX. Now this old client 5XX does not exists.
    From the new client, I am trying to release or delete those Trans Request using User SAPUSER/DDIC.but i cannot delete.
    However if using the Old customer user id ZXXXX, who created Transport request, we are able to delete those Transport request by changing the old client to new client.
    How to solve this issue any ideas.
    regards

    Hi ,
    u can include those old transport requests into  new transport request , then do the transport.
    check tcode SE03.
    regards
    Prabhu

  • Copy Transport Request to other new transport request

    Hi Gurus,
                  I collected Info Objects, Info Areas, Application Components in on transport request. I want to split Application objects and Info Area into new transport request. So that I can have Info Objects with existing transport request and other objects in new transport request.
                I tried in SE01 to include objects but I am not sure which option I need to select. I want to select specific objects to copy to other transport.
                Appreciate your help.
    Thanks
    Ganesh Reddy.

    Ganesh,
    You can delete the Info Objects and info area from the existing transport and collect those in separate transport request by change them .
    Go to SE09 and select the Request --> Go to Task and double click --> Go to change mode and delete the info objects and info area ..
    Hope it helps ..
    Ravi

  • Standard BEx transporting Request

    Hi Dudes,
    Can u explain me with a scenario, what is this Standard BEx Transporting Request and what is the purpose of this,
    Thankyou.

    Hi,
    This is what note says:
    Symptom
    Editing of a query in Query Designer may return the various error messages concerning transport system. Query or query component can not be changed or saved.
    The following error messages are possible:
    'Query could not be saved due to a problem in transport' message R9 124;
    'BEx Transport Request XXX... is not available or not suitable. Choose an existing request';
    'Object ELEM XXX... could not be saved to order YYY...';
    'A dependent object is being locked by the transport system' message R9 113
    'The dependent objects are in different transport orders' message R9 114;
    'The upgrade is already running - you are not able to change objects'.
    In some particular cases using NW 2004s server with 3.x Query Designer
    'Operation failed, no message available from server'.
    Other terms
    Query, Query Designer, Correction and Transport System, CTS, ELEM, Transport Request, Changeability.
    Reason and Prerequisites
    The error messages rise as the result of wrong administration of Correction and Transport System (CTS).
    Transport System Mode
    Two main modes of Transport System can be used for BW system: Standard Transport System and BW Transport System. Both modes require different administration efforts.
    Standard Transport System (system default)
    Within this mode an assignment of newly created query elements is done during save procedure. System asks for appropriated Package and corresponding Transport Request within this Package. The mode allows separating of changes done in the system different users in different Transport Requests. Users must be authorized to create new Transport Requests or to write into existing Transport Requests.
    BW Transport System (recommended for handling of BEx objects)
    Within BW Transport System initial assignment of newly create query elements is done automatically to $TMP Package. This is a Package for temporary objects and does not require modifiable Transport Request. Changes of those query elements can be done without further restrictions. Further assignment to a Package and corresponding Transport Request can be performed using Transport Connection of Administrator Workbench (transaction RSA1).
    All kinds of changes for query elements which already have been assigned to any Package different from $TMP (for example, queries transported from another system) must be registered in so-called Standard BEx Request. Using Standard BEx Request all changes done to query elements can be also transported to any other system. If the old Standard BEx Request has been released, another one must be created immediately in order to allow further changes for query elements.
    The typical reason for error messages listed above is a situation when NO Standard BEx Request is available anymore in the system. The algorithm of query SAVE contains a transport systems check. If the transport system check fails, no changes are possible.
    Changeability of query elements
    The recommended setting for query element (ELEM) is 'Everything Changeable'. Using of other settings, like 'Original Changeable' or 'Nothing is Changeable', will make editing of objects not possible when the general system changeability will set to 'not changeable' (SCC4).
    Setting 'Original Changeable' allows changes only for query elements which have been created in this particular system. Quite often an ordinary query may contain, for example, variables or other reusable components created in the other systems. In this case changing of a query containing those objects will be not possible.
    Changeability of Package
    Package (Development Class) where the corresponding Transport Request has to be created must be changeable. If a Package has a property 'Package is not extendable' set to true, no requests can be created within this Package. This means no objects can be registered.
    Solution
    The following messages mainly happen if BW Transport System is activated. The existence of Standard BEx Request and correct settings for object changeability should be checked.
    'Query could not be saved due to a problem in transport';
    'BEx Transport Request XXX... is not available or not suitable. Choose an existing request';
    'Operation failed, no message available from server'.
    How to create a new Standard BEx Request?
    Start Administrator Workbench (RSA1) --> Transport Connection. Find button BEx. Under the button user is able to create/assign a new Standard BEx Request.
    How to check Changeability of object?
    Start Administrator Workbench (RSA1) --> Transport Connection. Find button 'Object Changeability'. Set property 'Everything changeable' for query elements (ELEM).
    How to check Changeability of Package?
    Start transaction SE80 --> select corresponding Package --> find properties dialog. Check whether the property 'Package is not extendable' is set to false. Assignment of query elements (R3TR ELEM) to a corresponding Package is stored in the table TADIR (field DEVCLASS). In order to obtain a list of query elements used in a definition of a particular query having problems use the function RSZ_X_COMPONENT_GET with the I_OBJVERS = 'A', I_COMPID = technical name of a query. Execute the function and copy all elements (ELTUID) from the exporting table C_T_ELTDIR. Use this selection as the input parameter for selection from TADIR table (field OBJ_NAME). Collect all Packages and check the changeability as described above.
    The following messages mainly happen if Standard Transport System is activated. The problem happens in case, when one or several objects from definition of a particular query have been already written in another modifiable Transport Request. In BW 3.x each object can be processed only within one Transport Request.
    'Object ELEM XXX... could not be saved to order YYY...';
    'A dependent object is being locked by the transport system';
    'The dependent objects are in different transport orders';
    The situation may happen, for example, if a Query A contains a variable which has been already used in another Query B assigned to different Transport Request. In this case, saving of Query A will be not possible while the Transport Request containing the shared variable is not released.
    How to find an assignment of object to a Transport Request?
    Start transaction SE03 and select 'Search for objects in requests/tasks'. Provide ELTUID of the element which can not be saved. Object type is R3TR ELEM. Search for modifiable Transport Requests containing this element. If corresponding Request is found, it can be released. After that is will become possible to save this query element into another Request.
    Changing of query elements during running upgrage is not possible. The system sets a global lock in order to prevent any change which may potentially affect the consistency of objects. In such situation users should stop the upgrade procedures and wait until the process will finish.
    Regds,
    Shashank

  • Posting Key Field Status changes - unable to generate Transport request

    Dear All,
    I did posting key field status change from suppress to optional ( P.Key 24).
    However I am unable to generate a transport request.
    Please share your inputs
    Thanks
    Sanjai 

    Hiii sanjai Babu... your client would have set automatic recording of changes in scc4... or the request would be created and yo woulnt have left the page after saving soo it might have been saved... hope it helps...
    Regards
    Abhay

  • Unable to collect the changed query elements to a transportable request

    Hi All,
    I had saved the query changes to dummy request, now I have to collect the changed qurey elements in a transportable request. This I am doing in the transport connection tab in rsa1. Now I want to collect only the changed elements of the query, & not all the elements. I have made (changes) restriction to a key figure inside the keyfigure collum. Now when I try to make a collection of this to a transport request - I am unable to find it under the query elements in the transport collection.
    Pls advice how to collect it in a transport request & move it?
    Thanks & Reagrds,
    Shreesh.

    Hi Shreesh,
             It may be collected under default request. You can collect changed objects by releasing default request.
    aftre releasing default request
    go transport connection(TX-RSOR) object type -
    >query elements -
    > Query--> collect your query.
    Grouping option as only necessary object
    then click on "Package"
    then check for your objects if not checked against your query elements(which you want to collect), plz check. at the same time check for your query name it should also be checked then only query will carry the changes.
    Hope this will help you.
    Thanks,
    Vijay.

  • ChaRM: read categorization of change docs based on transport request ID

    Hi There,
    We have ChaRM implemented with 4 level categorization. I am writing a report to find change docs and read their categorization based on a transport request attached to the change doc. Unfortunately I can't figure out the connection. Could you pls give me guidance? Thanks in advance!
    Ádám

    In the meantime I found a very useful article on the wiki: http://wiki.scn.sap.com/wiki/display/Snippets/Reading+CRM+Transaction+Categories+Hierarchy
    If you need my complete code, drop me a mail.
    Thanks,
    Ádám

  • How can i change transport request description

    I need to  change transport request description for one table
    Note:
    Considering this post as Basic and Locking it for futher postings.
    Answer: Double click on the Request and using the change option, change it's Description
    Edited by: Vijay Babu Dudla on Jun 29, 2009 7:02 AM

    Hi,
       I know I am a little to late to the party! But for all those who are going to search for this in the future there is a very good blog...i am posting the link below...
    Basically run the program RDDIT076...
    http://scn.sap.com/community/abap/blog/2015/03/12/program-to-change-transport-request-description-after-release
    Regards,
    Divaker

  • How to avoid the transport request popup when changing real-time load behav

    Hello experts,
    I'm often switching between the two loading mode, and I already worked in systems where I don't have the popup for transport request : (so I guess there is a possible tuning anywhere)
    How to avoid the "asking for a transport request" popup in BW when changing real-time load behaviour of an infocube
    Thanks in advance, I will save precious time
    Guillaume P.

    Hello Krishnan,
    i tried to switch all object types from "not changeable" to "changeable original", but still get the popup when switching cube loading mode.
    Do you know the particular object type to manage ?
    Hello Vishnu,
    same thing, whatever the option is (switch on / off standard) I have the transport popup.
    Anyway thanks for your try.

Maybe you are looking for