2008 Jul 28 8:45 AM
hi
is there any tcode or table which displays all the new devlopment done by a particular devloper ?
regards
darshan shah
hi
is there any tcode or table which displays all the new devlopment done by a particular devloper ?
regards
darshan shah
2008 Jul 28 8:46 AM
hi,
all programs will be stored in table TADIR.
use TRDIR view or TADIR table.
goto that table give the developer name and give date period that u wanted to check,u will get all new programs devloped by tht devloper in tht period.
Edited by: gautham chakraverthi on Jul 28, 2008 3:48 AM
2008 Jul 28 8:47 AM
HI,
Check the entries of table TADIR by specifying the AUTHOR.
Hope this would help you.
Regards
Narin Nandivada
2008 Jul 28 8:49 AM
2008 Jul 28 8:51 AM
hiii
you can find it by using TADIR table...it is having fields for selecting date so give that period and you will get all development between that period.
regards
twinkal
2008 Jul 28 8:52 AM
Hi Darshan,
As also told by others the table is TADIR,
also refer to the link :
http://help.sap.com/saphelp_40b/helpdata/en/57/38e06c4eb711d182bf0000e829fbfe/content.htm
With luck,
Pritam.
2008 Jul 28 9:12 AM
Object Directory (TADIR)
The object directory (TADIR) is a directory of all Repository objects on which the R/3 System is based.
These include the following:
ABAP report programs
Module pools
Function groups
ABAP Dictionary objects (domains, data elements, tables)
The object directory contains R/3 standard objects that already exist in a newly installed R/3 System as well as your own objects, which you create while working with the ABAP Workbench.
When you create an object, the corresponding object directory entry is also created.
Various Repository objects consist of several sub-objects, which can be edited separately in the ABAP Workbench.
These sub-objects do not have their own object directory entry. It is only the complete objects that are listed in the directory.
Object attributes are also entered in the object directory. They are important for organizing development in the ABAP Workbench and for coordinating the distribution of developments between R/3 Systems. The most important object attributes are the following:
Development class
Every object is assigned to a development class. When the object is created, the development class is queried by the R/3 System. The development classes are used to structure the R/3 Repository and assign the objects to the various R/3 components. It controls the recording and transport of object changes by the CTO.
Original system
The original system of an object is the R/3 System in which the object was created and in which the object is edited for further developments and error corrections. The original system is unique for each object within a system group. This prevents competing changes to the same object in various R/3 Systems from resulting in conflicts after transports. The original system of an object can be changed by a relocation transport.
Person responsible for object
Each object is assigned a user as the person responsible. This means that when there are questions concerning functions or if problems arise - even in an R/3 System other than the original system - the relevant contact person can be determined quickly.
Original language
Objects with language-specific components, such as text elements, have an original language. This is the logon language in which the object was created. It is needed to control the translation process, if you are developing in more than one language in your R/3 System. The original language can be changed when the object is edited in another logon language and this is confirmed explicitly.
Generation flag
In many application areas of the R/3 System, in particular in the Customizing transactions, ABAP programs, ABAP Dictionary objects, or other objects are generated automatically from user entries, and are used later in productive operation of the R/3 System. Such objects are flagged as "generated" in the object directory.
Repair flag
In problem situations, it may be necessary to change an object in an R/3 System that is not the original system. Such a change is referred to as a "repair". This object is flagged as "repaired" in the object directory.
There are various access points for displaying and editing object directory entries. The most important are:
When an object is created, the development class is prompted. The current user is proposed as the person responsible. When the ABAP Workbench is accessed using a predefined development class (Repository Browser ® Development class ® Display), the development class is not prompted.
In the Organizer Tools (transaction SE03), there are various selection reports under the Object directory node, with which you can edit directory entries of selected objects or change the person responsible for the objects.
From most ABAP Workbench object editors and from the WBO request overview (Overview ® Workbench Organizer ® Display ® Edit ® Expand), you can display the directory entry with Goto ® Obj. directory entry or Object ® Obj. directory entry.
In the object overviews of the ABAP Workbench Repository Browser (SE80), you can change the development class to which individual or selected objects belong with the Reassign function.