The table/view TVDIR has no generated maintenance dialog

[Former Member]

We have an interesting issue.

We are in a ECC 6.0 Development Environment with BASIS release 700. We created a table and also a table maintenance for it. When releasing the transport containing the table with the maintenance we get the error:

The table/view TVDIR has no generated maintenance dialog
Message no. SCPR028

Diagnosis
You tried to read data/information about a table/view which should have a generated maintenance dialog (see "Table/View Maintenance Transactions": SM30/SE54). This maintenance dialog does not exist, or it is incomplete (there is no entry in the table TVDIR).

This probably indicates an inconsistency in the view.


Procedure
Inform your system administrator or SAP.

TVDIR DOES contain the appropriate entry. SM30 works on the z table.

We then deleted the entry from TVDIR via SM30 and the release worked.

We created a 2nd table without table maint and release worked.

It's almost as if the code is incorrect (reversed) for checking the existence of the table maint. It should DEFINITELY have failed after I deleted the TVDIR entry manually..but it succeeded. SAP Notes search turns up nothing.. Anyone seen this?

[former_member1007904]

looks like its an issue during table maintenance generation.... try deleting the table maintenance and regenerate... theres a button for regeneration in se11

[Former Member]

We've attempted that. In fact this issue has occurred on several "test" custom tables and the same issue results.

[Former Member]

Hi,

The error message looks like the program is trying to access the table TVDIR. What kind of table have you created? As in, delivery class? Client-dependency?

After you generated a maintenance dialogue for your table, did you try testing it via SM30? Did it work?

How did you add the changes to a transport request? Was it via the automatic transport that gets popped-up?

It is not advisible at all, to manually handle the data in TVDIR table.

Regards,

Rekha

[Former Member]

What kind of table have you created? As in, delivery class? Client-dependency?

It's a customizing table, client dependent

After you generated a maintenance dialogue for your table, did you try testing it via SM30? Did it work?

Yes, and yes

How did you add the changes to a transport request? Was it via the automatic transport that gets popped-up?

Yes, via the automatic pop-up

It is not advisible at all, to manually handle the data in TVDIR table.

Data in a table is just that... some tables are more dangerous to modify if you don't know what you are doing (dependencies) but at the end of the day, it's just data.

[Former Member]

Hi...

lets try this ....while generating the maintainance try giving the new function group .

note: dont give the function group that u have used before while regenerating the maintainance. It should be new one.

hope this works....

reward if useful

regards

Abhimanyu

[Former Member]

Hello,

TVDIR is one such dangerous table, please do not handle data within that manually.

SE54 is a std interface available to maintain it. Any wrong data in the table can cause

inconsistencies.

Please delete and once again define a maintenance dialogue for your table via SE54.

Regards

[Former Member]

This is the response I got from SAP

The error message 'Table/View has no generated maintenance dialogue', isthrown up when the transport request contains the object R3TR TABU

TVDIR, with the keys as tables like T042A, T042B etc., which do not havemaintenance dialogues, in reality.

TVDIR is the table which contains the header information about the

existance of a maintenance dialogue.

Can you please try checking all your transport requests where the error

occcurs, and see if you have this object R3TR TABU TVDIR present in

them? If yes, can you please check of the object key contains tables

names which do not have a maintenance dialogue (no entry in TVDIR).

Please manually delete that particular key for the R3TR TABU TVDIR

objects in every such transport requests.

When you release a Task, you simply add the pool of objects to the

actual transport request. Only when you try to release a request, the

standard transport and other checks are performed for the objects

and their consistency. That is the reason why you get the error while

trying to release a transport request.

[Former Member]

Issue found in the Code for

Form READ_TVDIR

in function Group SVIX

Line #11

Code :

8	FORM read_tvdir USING table CHANGING maintview LIKE tvdir-tabname.
9	  DATA: rt_objtyp LIKE objh-objecttype,
10	        missing_tvdir_entry(1) TYPE c.
11	  SELECT SINGLE * FROM tvdir WHERE tabname EQ table.
12	  IF sy-subrc NE 0.                                   "Subviews ..
13	    missing_tvdir_entry = 'X'.
14	    IF dd25l-viewname <> table.
15	      SELECT * FROM dd25l WHERE viewname = table AND as4local = 'A'.

Variable table = TVDIR

So essentially the SAP code is looking for a view of TVDIR in TVDIR...

the variable TVDIR should = the name of the table view, but in every case it is TVDIR.

Submitting ticket to SAP to follow up.

[Former Member]

Hello,

We just upgraded to ECC 7.00, currently with kernel patch 201 and support package level 18, and we are getting the exact same error. A breakpoint in the code that you refer to definitely shows that the error is happening because TVDIR is being checked to see if there is an entry for TVDIR. I've searched a lot and can't find anything about this in an SAP note. Did you get a correction from them? Do you have a note number?

Thanks very much,

James Webster