Transport Request and Task

Hi,
Can someone explain a basic, when we transport a BI object, we see 2 things in se10/se09- one request and the other one task.
My question:
1.  What is the significance of each of them and the use?
2.  What process should be followed here and what sequence.
-TC

Ok.
Here is what I understand from youre replies above-
1.  A request can have multiple tasks and each tasks corresponds to the work that is being transported.
2. One needs to release the tasks before we can release a request.
Suppose now, I have the following scenario:
I have changed an infoobject(ZABC) being used in multiple cubes (A,B,C).  In this scenario how do I go about it.  I understand that I need to transport and import the infoobject first and then the cubes.
So if I am working on a Transport Connection in RSA1. What would be the steps?  I am writing the steps, correct me if I am wrong-
1.  I select the infoobject and drag it to the right screen.  I press the truck symbol and mention the package.
2. I drag the Cube A and press the truck symbol and mention the package
3. Same thing for other cubes.
Please let me know the optimum way.
-TC

Similar Messages

  • How could we delete transport request and task(the released one)

    Hello
    We have a released transport task(not request). Transport request is not released.
    How could we delete transport request and task(the released one). Namely we would not like to transport it to production

    Hi, never delete directly in table.
    There are more tables which depends each other...
    Here, you can find nice example how to do it: Help on ABAP: Few Tips for Transport Request Manipulation
    Using program: RDDIT076 and changing status.

  • Transport request and task releasing?

    Hi all,
    I've three systems dev,QA and prod.I'm working on dev client and I've a two reports(say A and B) under the same transport request with different tasks,If I want to release the report 'A',is it necessary that I shud be releasing th ewhoel request number or if I release the task it's enough.why a transport request will have different tasks,when the transportationof ht ese taks associated with the transport request is independent.
    I've released the task to QA and the QA sytem had some problem and did nto get he task,what I shud be doing now,release the task again or ?
    Can a report be assigned to different tasks(numbers) under the same  transport request.can the report be assiged to different transport requests.please let me know.
    thanks and regards
    Message was edited by: henry

    There is a transport route defined by your Basis Team for the transport scenarios. There, the possible ways through which request can be moved( from Dev --> QA & Dev --> Prod ) are defined.
    But it does not mean that you can't transport your request to production without transporting it to QAS.
    Furher, when you release a transport request, it does not automatically move to QAS or Production but someone from your Basis Team has to run the TP through Xn STMS, which in turn imports the objects from your Dev Request and put it on QAS / Production.
    In case of any error encountered while importing to let's say QA, you need to check whether it's a problem with the transport buffer or is it because some objects are missing from the transports or dependent transports are not moved as yet.
    Please understand that there is no concept of re-release.
    You can only ask your Basis guy to re-import it.
    According to the encountered problem, you need to decide whether you should just ask you Basis consultant to re-import the same Transport.
    Or create a new request through SE10, and include all the objects from your last request. Release it and ask your Basis guy to import it to QAS.
    Or first move the dependent transport and then ask your Basis guy to re-import your current transport.
    Or create and group the changed objects, altogether in a new transport by changing all the objects which were contained in the original request.
    Further, to your other queries, if two users are modifying the same program ( not exactly at the same time - that's not possible but one after other )then that program will be contained in two separate tasks of the same transport request.
    I hope it answers a few of your queries.
    Thanks,
    Ram

  • Regarding Transport Request and related program names

    Hi All,
    I have a issue with picking Pro<b>gram Names</b> from <b>Transport Request</b> names.
    I am using <b>E071</b> table to pick up all the <b>Objects/Program Names</b> based on <b>TR's</b>.
    But for the <b>TR's</b> which are having <b>D-Modifiable status</b> i am not getting any entries from <b>E071</b> table.
    Can anybody give me alternate table which will give us All Program names under a T<b>R</b> based on T<b>R</b> for which status is <b>D</b>.
    Thanks in advance.
    Thanks,
    Deep.

    Hi Deep,
    When the transport request is not released (i.e it is in Modifiable status) all the objects are linked to the tasks under the transport request. So if you are trying to get all the objects in the transport request(in modifiable status), first you have to get all the tasks under the transport request and get the objects under each task from E071 table.
    You can get the taskes under the transport request by selecting from E070 table
    select * from E070 where STRKORR = <your transport request numer>
    then you can get all the objects for each task .
    - Kalyan

  • Transport Request and Cross-Application techniques

    Respected Members,
    I want to know what is the difference between the transporting request and Cross-Application Technique( eg  ALE)
    Generally suppose you have made some object in development server and then a transport request will be created and through transporting to the production server same data can be transported to production server.
    Same thing we do with ALE also that we can transport the data from one server to another server or from one client to another client.
    THen what will be the difference between the transport objects and Cross-Application techniques.
    Clear this picture by giving your valuable answers.
    Thanks a Lot.
    Manish

    Hi Manish,
    The applications transferred through Transport Requests and the data passed through ALE or EDI are completely different technologies.
    The Transport requests transfer the programs and the configurations that you do within the development Server or rather the SAP system to the Production Server and then you execute them to get the desired result.
    On the other hand,ALE(Application Linking and Enabling) or EDI(Electronic Data Transfer) transfers the data or rather business documents(for example vendor payments or making the payme nt through cheques) from one system to another system,i.e different Landscapes.
    If suppose you want to transfer the data from one SAP system to another SAP system which are in completely different landscapes,then you use ALE and in case you transfer it from one SAP system to another Non-SAP system or vice-versa,you use EDI.
    Moreover,you cannot view the coding or the configuration part in case of ALE or EDI whereas you can view the same in terms of Transport requests.
    The landscape means all the clients within one SAP system.
    I hope I have made it In case you have any further clarifications,do let me know.
    Regards,
    Puneet Jhari.clear.

  • 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 main task releasing problem

    Hi friends,
    Environment is Linux, ECC5.0, Two system landscape,
    I have problem with Transport Request task releasing when I am going to release the subtask that willbe released success fully when I am trying to releasing the main task that task is not released and at that time the system wil hang( mesg on the status bar is tp is connected success fully) thats it we wait for long time then also that looks thats only no log will be generating in usr/sap/trans/log there will be a log on this one that log is
    WARNING:/usr/sap/trans/tmp/<username.LOS>is already in use (10), I'm waiting 3 sec(20070326124305). My name:pid 7265 on test(sd1adm)
    after saw the this mesg I kill the 7265 pid then also same proablem.
    I change the ownet of the request then the request is released but not uppeard in the import que. whn i am trying to import in que as manually that will appear in que but not importing when i press the import button the error is tp error 0203.
    I check the both users authorizations also bothe authorizations also same then why it wil happening ???
    then I check the nfc also that service also running ok the six services are 1.off 2.off 3.on 4. on 5.on 6.off.
    I mount the trans dir also the mounting points also ok tms configuration is also ok
    wt can i do plz help me with ur valuable suggessions
    Thankyou
    Ranjith

    Hello Ranjith,
    This is usually because the tp transport buffer lock file remains locked by the
    operating system (OS).
    You should be able to move or delete this file from the DIR_TRANS/tmp dir.
    After that the tp should run fine after.
    Thanks,
    George

  • Delete Transport request when task is released

    Hi All,
    Task is already released and i dont want this transport request.
    i am trying to delete the transport request from se10. But unable to do that. i have unlocked the object for this request and when i try to delete the object it give an error to sort and compress the task and request.
    But when i try for sort and compress for the task its says it is already released. How can we resolve and delete the request.
    Please advise.

    Is there any way we can delete it from the Object list , only the task is released not the actual request. I can see the entries in E070 table but it not recommanded to delete from this table.
    When i try to delete it says the task need to sort and compress, When i try to compress it says the task is already released.
    Any how the last option for this problem is to delete from the buffer once its released or delete the entries from the table.
    But there must be some way, as only the task is released.
    Please suggest.
    Thank You,
    SK.

  • Error within General Task: Register transport request in task list

    Dear all,
    I would like to register transports into a task list. When I try to do so I get the following error:
    Error RFC destination SPROJECT_GET_SMI_DATA_R: Projekt: ZCHARM_DQ
    Message no. /TMWFLOW/TASKLIST191
    Some one got an idea where the problem might be?
    Any help would be much appreciated.
    Best regards
    Daniel

    Hi Daniel,
    This error is reported in SDN blog /people/dolores.correa/blog/2009/07/22/change-request-management-scenario-usual-questions-and-known-errors
    in point 21
    21. Missing authorization for READ RFC connections
    Our default authorizations for remote READ RFC users (created in SMSY) do not allow us to read transport requests information. But READ RFC users are used extensively in Charm to get those information. It is a bug in SMSY which has not been fixed by now. So currently for such kind of messages we have to ask our customer to manually add appropriate authorizations (e.g. profile S_TMW_CREATE) to those READ RFC users.
    - Open transport requests are not marked as red when release them from task list.
    Note 1279558 - Red Question Mark Icon Missing from Charm Transport Release
    - "Error RFC destination SPROJECT_GET_SMI_DATA_R" when register outside transport requests into Charm.
    Please assign enough authorizations to all those READ RFC users on their DEV system (including client 000).
    - Cannot complete maintenance cycle due to "Error RFC destination /TMWFLOW/TL_COMPL_CHK_TR_WO_TL"
    Please assign enough authorizations to all those READ RFC users on their DEV system (including client 000).
    - Transport request information is missing in the result of Charm Reporting.
    Please assign enough authorizations to all those READ RFC users on their DEV system (including client 000). And after that they should re-execute background job SM:TMWFLOW_CMSSYSCOL to update those information on Solution Manager system again.
    Hope this helps,
    Dolores

  • Want to delete request and task id but by mistake released task id.

    Hi ,
             There is one request id and task id under which no object is attached.
             I dont know how it is created. I want to delete them but by mistake i have released task id and now it is not alloing me to delete task id and request id .
    Could anyone tell me how this blank task and request id created and how to delete it.
    Regards,
    Himanshu.

    -Transport requests that have been released cannot be deleted from within the
    SAP System. You can, if you wish to, delete the cofiles and datafiles that
    are generated at the OS level when a transport request is released.
    -You can even delete it from the STMS buffer and physically delete the DATA
    and the COFILE of the transport request. You can also delete the entries
    from the E071 table (NOT recomended, first step should be enough).
    Edited by: Mishra.Manas on Apr 28, 2010 11:09 AM

  • Transport request and objects

    hi experts,
    can anybody tellme how u transport requets and how u transport objects.

    hi,
    You can check all the requests in SE01 or STMS.
    You should know how STMS works at least.
    In STMS you normally select the system (DEV/QA/PRD) for which you want to look at transport requests. After selecting the relevant system, you normally get to see the 'IMPORT QUEUE'. This means the following:
    (make sure you press the REFRESH button first)
    1) transport requests in the import queue of your QA system are not imported yet. (imported ones, you can find back via the menu by selecting the 'IMPORT HISTORY'.
    So if you want to find out about requests that are already on your QA system, but NOT on your productive system, you just select PRD , and look at your import queue for this particular system. These transports that you see there are ALREADY imported on QA , but not yet on the production system.
    Case Closed I would say, not??
    The only thing that might make my statement 'uncertain' is if the company has a specific 'approval procedure'. For example, suppose you have released a new development on your development system. An automatic job imports every hour all released transports from your development system into your QA system. (ofcourse you can always manually import a request).
    Now after an hour the request is automatically imported on your QA system and you can do the necessary Unit and Integration testing.
    Now, under normal circumstances, after import of your request on the QA system, in STMS it will automatically appear in the import list of the production system.
    In case of the approval procedure however, you first might need to select tested requests, select them, approve them (via an approval button ) and run a job to release all approved requests. Only after they are released by the job, they will appear in the Import Queue of the production system.
    But ok, I only saw this in practice at one customer so far...but just that you know
    regs,
    hema.

  • Automatic Transport Requests and Support Pack Stacks using CHaRM

    Hi Experts,
    Could you please give your valueable inputs on below Requriements :
    1. All Transports Requests needs to be Automatically moved from Solution Manager using CHaRM.
    2. Automatic Support Package Stacks needs to be updated using Solman - CHaRM
    would be helpful if any one could send the documentation on above requirements.
    Regards,
    Vijaysateesh

    Hi,
    >
    > 1. All Transports Requests needs to be Automatically moved from Solution Manager using CHaRM.
    Yes. You can schedule a periodic job (say for example daily 6M) to import all released transport requests from  QAS to PRD of a maintenance cycle/project. This is the task "Import Transport Request(Backround)" given in task list (tcode-SCMA) of a maintenance cycle.

    > 2. Automatic Support Package Stacks needs to be updated using Solman - CHaRM
    I haven't done this. But this is the  task "Import Support Package" given in task list (tcode-SCMA) of a maintenance cycle.
    I hope there is no specific documents for these. It's the same documents related to ChaRM.
    Regards
    Sanjai

  • Transport request  and  Message class?

    Hi,
       How to create a transport request for the changes I made in a content of the table (eg: T100 ) so that the changes can reflect in all clients. and please mention the name of message class for the object BUS2121 or else name the message class for the messages that has been used in shopping cart email templates.
    regards,
    George.

    Hi,
    The message for SC is BBP_PD, you will find in SE91 txn. and you would need to know the message number to customize it, you can do it in SPRO-Cross-application settings-> Message control, and then select BUS2121 and add new entry to change it from standard.
    Award Pointsif helps.
    Thanks.

  • Whats the diff between copying a Transport request and Importing a request?

    Hi gurus,
    Can some one explain me the difference between copying a transport request between clients and importing transport request between clients? say for eg: difference between copying a transport request containing a datasource being copied from client 100 to client 200 and importing the same request from client 100 to client 200?... When do we follow such scenario's?
    thanks.
    kishore

    Hi Kishore,
    A request copy applies only for customizing (client dependent) objects.
    A request tracks object modifications since its last transport. if the object is created in source system and included in a transport request, when it is transported to another system, it will create the object in target system. Then if you modify the  object, it will include modifications since last transport.
    As i said, a request copy is only valid for customizing objects. This is entries in tables, you will see that you have two kind of requests, customizing and workbench. Workbench objects are client independent, so request copy doesn't applies.
    it's very important to keep the order of requests when you transport and also not to delete requests in any system.
    Hope this helps (and hope it is clear, if you have any doubt, just ask!).
    Regards,
    Diego

  • Transport request and deletion of an  object

    Hi Folks,
    1.Will it ask for a transport request when a object is deleted from
    the Development.
    2.If it asks, then whether this transport request when transported to
    quality and production will it  delete the same object from Quality and
    production too?
    3.What is the best way to delete an object having an transport request.
    4.Anyother way to make an object null and void.
    Thanks,
    K.Kiran.

    Hi,
    1.Will it ask for a transport request when a object is deleted from
    the Development.
    <b>YES</b> this is needed so that the objects are deleted from all the systems in the ladnscape. so that when you release thisrequest the objects gets deleted from the target system
    2.If it asks, then whether this transport request when transported to
    quality and production will it delete the same object from Quality and
    production too?
    <b>YES</b>
    3.What is the best way to delete an object having an transport request.
    <b>If the object exist in your quality and production the best way is to use the transport request, if that does not exist you can ask your basis guy to delete it.</b>
    4.Anyother way to make an object null and void.
    <b>Ask the basis guy to delete it</b> but to keep track its always better to delete it using the Transport reuqest.
    Regards,
    Sesh

Maybe you are looking for