2008 Mar 06 4:18 PM
hi all
I am trying to do the code inspector check on an ABAP query. I am getting an error
" The TADIR entry for AQZZZDEMO===ZDEM_MD= is missing ."
AQZZZDEMO===ZDEM_MD= is the name of program which is getting generated automatically
for the query .
Can anyone help me out with this.
Thanks .
hi all
I am trying to do the code inspector check on an ABAP query. I am getting an error
" The TADIR entry for AQZZZDEMO===ZDEM_MD= is missing ."
AQZZZDEMO===ZDEM_MD= is the name of program which is getting generated automatically
for the query .
Can anyone help me out with this.
Thanks .
2008 Mar 06 5:25 PM
Hi,
The error is being returned by the code inspector/extended program check because table TADIR is also being checked. I see the same message when using extended check on any ABAP Query program. The error shows up because there is not an entry in table TADIR for your ABAP Query program. I think this might be normal for ABAP Query programs. However, the message itself is certainly misleading because there truly is a TRDIR entry for your ABAP Query program. The message should state that there is a missing TADIR entry in my opinion.
You can see where TADIR is being checked by setting a break-point in CL_SLIN as follows:
(1) Transaction SE24
(2) Enter class CL_SLIN
(3) Search gloabally in the class for "TADIR"
(4) Within include program SLIN_PROG_IMPL and method PROGTADIRATTR you will find a select single from TADIR
(5) Set your break-point here and try the code inspector again.
(6) You should hit your break-point and see that the select on TADIR fails, leading to the extended program check error.
(7) From here you can single-step through the debugger to watch how the message is added to the error listing.
I believe this is probably a defect in the SAP standard code. At a minimum the error message should actually state that the TADIR entry is missing (instead of TRDIR which does exist).
I wouldn't worry about this message too much, but if it is causing you problems then maybe an SAP message is needed. You should of course search for SAP Notes that already address this first.
Bottom line is that your message is not being caused by anything that you have done.
Best Regards,
Jamie
| User | Count |
|---|---|
| 3 | |
| 2 | |
| 2 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 |