Skip to Content
Technical Articles
Author's profile photo Kallol Chakraborty
Kallol Chakraborty
Posted on September 3, 2020 2 minute read

Easy Way to get the SAP TR/Task(Request/Task) details

Follow RSS feed
4 Likes 541 Views 11 Comments

Introduction

We generally use the Tcodes: SE01, SE09, SE10 for getting the transport details. The program called for all these Tcodes is RDDM0001. But, extracting the output in an excel sheet & doing some operations on them can be a difficult task sometimes.

So, I am writing this blogpost.

Solution

First of all, please change the below-mentioned settings of the SE16(Data Browser) of SAP GUI.

Please follow the below steps:

  1. Go to SE16
  2. Enter the table name
  3. Go to settings -> User Parameters
  4. Select the Data Browser tab (Already selected by default) & then make the changes shown in the screenshot below.

Click the radio button of ALV Grid Display & Field Label for showing the contents of the table in the ALV Grid format & with the labels of the field names.

The field name change is optional for the developers.

There are a few standard tables provided by SAP that stores these Requests/Tasks related information. (The tables mentioned in point 4 & 5 are not of much use to a functional/technical person in general.)The names of few & their descriptions are the followings:

  1. E070: Change & Transport System: Header of Requests/Tasks: If the Higher-Level Request column is empty, then the entry is for a TR else for a Task. You can filter the Requests/Tasks by Type, Status of Request/Tasks, etc.

  2. E07T: Change & Transport System: Short Texts for Requests/Tasks: This table is for only a short description of the Request/Task.

  3. E071: Change & Transport System: Object Entries of Requests/TasksThis table will provide you all the objects included in the requests/tasks. You can also get the status of the request/task from the status column.

    You can also filter the entries by the column: Obj. (Object Type)

  4. E070A: Change & Transport System: Attributes of a Request: This table is for fetching the request/task attributes.

  5. E070C: CTS: Source/Target Client of Requests/Tasks: This table is for the Source/Target Client.

That’s all 🙂

If I miss anything, feel free to add them in the comment section.

If you find this post useful, please like & share.

Also, please don’t forget to endorse me on LinkedIn. 🙂

Assigned tags

Related Blog Posts

    Related Questions

      /
      11 Comments
      You must be Logged on to comment or reply to a post.
      • Author's profile photo Karl Peham
        Karl Peham

        Well, and not forget to mention table E071K which is my favourite table in transport requests :).

        I think this table is the fastest way to find out if/when a certain customizing entry has been changed.
        e.g. “when was the customizing for delivery type ZLF changed?” ->

        voilá:

        /
      • Author's profile photo Jelena Perfiljeva
        Jelena Perfiljeva

        Thanks for sharing! Every time I go into the transport-related transactions I think how outdated they are and how difficult to use at times. We shouldn’t need to use such work-arounds.

      • Author's profile photo Suhas Saha
        Suhas Saha

        IMO, the easiest way to find objects in TRs or finding TRs in general is to use the transaction SE03 (Transport Organizer Tools).

        The tools which i use often are:

        • Find objects in requests/tasks
        • Find requests

        Why do you prefer using the workaround(s) over these standard reports?

        • Author's profile photo Kallol Chakraborty
          Kallol Chakraborty Post author

          Thanks for checking out my blog post Suhas Saha

          I think these reports are outdated that’s why I am going for the workarounds. 

          If you know the tables then, you are having better flexibility over these tcodes when it comes to extraction & manipulation.

           

          • Author's profile photo Sandra Rossi
            Sandra Rossi

            Why “outdated”? If SE03 is outdated, then all SAP reports are outdated too… I think that options not available in SE03 are more valid arguments to look directly tables (like searching transport requests by table key in table E071K).

            • Author's profile photo Kallol Chakraborty
              Kallol Chakraborty Post author

              Dear Sandra Rossi & Suhas Saha,

              Thank you for checking out my blog post. My intention is not to hurt the sentiments

              By these reports, I wanted to mean SE01, SE09 & SE10, not SE03. I think this has been misunderstood.

              At sometimes, I find these reports challenging to extract particular information in excel so, I came up with this workaround.

              Please treat this post as just a piece of information, not an essential thing. ?

              • Author's profile photo Sandra Rossi
                Sandra Rossi

                Many people access SE03 via SE01, SE09 & SE10 without knowing it’s SE03. The button “Tools” is just at the top of the initial screen of each transaction.

                Sentiments? Not me, I discuss facts :). The fact is that it’s nice to have blog posts who tell people what tools exist to search transport requests, and the limits, and the workarounds 😉

                 

          • Author's profile photo Suhas Saha
            Suhas Saha

            Sandra has resonated my sentiments.

            The use cases you have presented in your blog can be fulfilled using SE03 reports. No need to manually extract & manipulate the E07* data.