Maintenance View Cluster Configuration Problem

jens_straten2 — Tue, 15 Nov 2011 21:43:18 GMT

I am in the process of setting up some maintenance view clusters in our system. Some of them are working right away, but I am having trouble with the ones that are using text tables as a source. Here is one I can't get to work:

Table A:

MANDT - MANDT - Key

LANGU - SPRAS - Key

TEXT_ID - NUMC - Key

TEXT - CHAR

Foreign Keys A:

LANGU -> T002

Table B:

MANDT - MANDT - Key

TEXT_ID - NUMC - Key

... (6 other fields)

Foreign Keys B:

TEXT_ID -> Table A

View A:

MANDT - MANDT - Key

LANGU - SPRAS - Key

TEXT_ID - NUMC - Key

View B:

MANDT - MANDT - Key - S

TEXT_ID - NUMC - Key - S

... (6 other fields)

The table maintenance for View B contains only the key field TEXT_ID. All other fields are missing. According to the documentation from SAP it should determine the language by using the system language. What am I missing? Why don't we get all fields for View B in our table maintenance?

Since the problem only occurs when we are using text tables it appears to have something to do with that. Any help would be appreciated.

Thanks!

Re: Maintenance View Cluster Configuration Problem

jens_straten2 — Tue, 15 Nov 2011 21:54:07 GMT

Sorry, I meant to post this to the Data Dictionary forum, but now I can't move it.

One more comment:

I found that if I add a non-key field from table A to view B and only mark this field as a subset, it kind of works. The system then takes all fields and puts the non-key field on top of my maintenance view. However, the TEXT_ID key field remains in the table as display only...

Thanks!

Moved to DD

Edited by: Rob Burbank on Nov 15, 2011 4:59 PM

topic Maintenance View Cluster Configuration Problem in Application Development and Automation Discussions

Maintenance View Cluster Configuration Problem

Re: Maintenance View Cluster Configuration Problem