Skip to Content

Suppose we face a situation when we want to track the Plant Creation date/ Transport Request in which it is created.

Those who understand the system deeply can easily diagnose that these details cannot be easily derive from any transaction.

Thus we need to play with tables smartly in order to crack this issue 😉 .

Objective : To track the Transport Request & Creation Date of a Plant

Solution Proposed :

We need to play with Tables. T Code : SE16

/wp-content/uploads/2012/04/1_89543.png

Enter Table E071K

/wp-content/uploads/2012/04/2_89544.png

Enter R3TR in Field PGMID ,

TABU in field OBJECT & T001W in field OBJNAME.

/wp-content/uploads/2012/04/3_89545.png

Execute.

/wp-content/uploads/2012/04/4_89546.png

The main catch in this Process is the Field TABKEY which represents the combination of Client & Plant Code Created.

/wp-content/uploads/2012/04/5_89547.png

Thus if we want to know the transport request # of Plant 1116 then it can be easily derived from above screenshot (AEDK900036).

Our First Objective gets fulfilled here (i.e.. to derive a transport request of a Plant Created)

Our Second Objective is to find the Creation date of this Plant.

Copy the Request derived in above step & paste in another table E070.

/wp-content/uploads/2012/04/7_89549.png

Execute.

/wp-content/uploads/2012/04/8_89551.png

Thus our second objective also gets fulfilled here ( Details of User,Creation Date,Creation time derived) !!!! 🙂

Hope it helps  !!

To report this post you need to login first.

7 Comments

You must be Logged on to comment or reply to a post.

  1. Philip Allgaier

    There is even an easier/faster way: Use table “E070CREATE” if present. For any given transport request number (TRKORR) you can directly get the information who created when this request.

    (0) 
    1. Clemens Kopfer

      Dear Philip,

      nope. Only for not released ones.

      Upon releasing you need to check logs (at least according to my knowledge, also several threads here)

      (0) 

Leave a Reply