View cluster with single entry table

[robson_soares]

Hi,

I created a cluster view and I'd like to include in it a maintenance dialog for a single entry table which has only the MANDT as key field, in order to keep everything in one place.

I tried in several ways, but without success.

Could anyone tell if it's possible?

Thanks

[emanuel_klenner]

Hi Robson,

It is possible to have a maintenance dialog for a table that only has the MANDT as the key field.
The trick is to make it a two level dialog which an overview and a detail screen. When the screen first comes up it looks a little weird because the screen seems to be empty. Press the 'New Entries' button and then your detail maintenance screen will show.

[Sandra_Rossi]

I agree with emanuel.klenner, but for me, including it in a view cluster is not possible, as far as I can see (The best I can obtain in ABAP 7.52 is the error SV597 below while activating the view cluster).

Maybe you could include any dummy view or table in the view cluster, define the event 03 for the view cluster, and replace that dummy view with your table (variable VCL_AKT_VIEW).

Error when modifying dynpro xxxxxxx (dynpro was not modified)

Message no. SV597

Diagnosis

The flow logic of the screen xxxxxxx is not that of a generated view maintenance list screen. Either the screen has been considerably modified manually, or the view which it is based on has no maintainable key.

System Response

The screen has not been modified.

Procedure

Make the view cluster maintenance screen modifications required manually on the screen. See the transaction 'Generate table maintenance dialog' application help for the modifications required.

[robson_soares]

Emanuel, as Sandra said, this trick results in the SV597 error. I had already tried.

[Sandra_Rossi]

Did you try my proposal?

Maybe you could include any dummy view or table in the view cluster, define 
the event 03 for the view cluster, and replace that dummy view with your table
(variable VCL_AKT_VIEW).

[robson_soares]

But in this case it is necessary that the two views or tables are in the view cluster, right?

[Sandra_Rossi]

I realize that replacing a table or view dynamically in a view cluster is much more complex than what I thought (change all VCL_STRUC* internal tables and so on, not supported by SAP probably), so please ignore.

Maybe having a second dummy key field in the table and hiding it could be much easier to develop and maintain.