I have a custom table with a flag field which I think is not used. To confirm this I have used session, tdadv4430m000 - Print Where used Tables.

The output is a long list of scripts.

I opened the first script and searched for the table.field and it is not found. So I am wondering why the script is listed on the report?

Will someone examine the parameters that I set in session ttadv4430m000 and advise what if any changes I should make. Images of form1 and form2 are pasted in attachment.

Hmmm - I have always wondered about the print tables which are not used and not found. I usually turn those off - I wonder if somebody can explain them?

I think -

Not Found - If any of the tables have been deleted or expired at a later time.

Not Used - If you use a include which contains a list of tables, but you use only a subset of tables in your program script.

Should I execute with these two parameters unchecked?

Hi there,

as you are on unix, why not go to $BSE/application and use:

for i in p r i
do
grep -l ppmmmnnnn.ffff */*/$i*
done

If you use the field ffff of table ppmmnnnn in any single one of your program scripts, reports or includes of any package combination, it will pop up.

hth

Norbert

P.S.: If you use the field in a report without mentioning it in the report script, you should see this in ttadv334

cd $BSE/application
find . -exec grep -l 'ppmmmnnnn.ffff' {} \;
I get a list of files in the object directory. All the file names begin with "u".
I do not understand what these files are that begin with "u".
Could this be the result of writing code such as :
select ppmmmnnn.*
from ppmmmnnn

Where all fields are being brought into the query?

Hi Joy,

I haven't inspected these "u"-files in detail - your idea sounds pretty good though.
All that I knew so far about these files was:
a) They are created when a program is compiled
b) Nothing bad happens if you delete all of them :-)

regards

Norbert