Application Development and Automation Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
cancel
Showing results for 
Search instead for 
Did you mean: 
Read only

Problem in Selection Conditions Maintenance View

Former Member
0 Likes
1,519

Hello Gurus.

I've created a maintenance view for a ZTABLE, in this maintenance view in TABLE/JOIN Conditions i defined a relationship beetween my ZTABLE and SKAT.

Untill this point its fine. But when i go to the tab of selection conditions, there already there two automatic conditions. And i can't edit these conditions.

Why this is happening?? Anyone knows??

Thanks in advance

1 ACCEPTED SOLUTION
Read only

Former Member
0 Likes
784

Hi,

The already predefined set of relationship is due to the data integrity and foriegn key relation ship.

so we get a predefined set of relaionships if we take view of existing master table.

since SKAT is gl account master for chart of accounts and its key fields would have the set of foriegn key relations with the corresponding key tables

like

ktopl- t004 etc

Hello Gurus.

I've created a maintenance view for a ZTABLE, in this maintenance view in TABLE/JOIN Conditions i defined a relationship beetween my ZTABLE and SKAT.

Untill this point its fine. But when i go to the tab of selection conditions, there already there two automatic conditions. And i can't edit these conditions.

Why this is happening?? Anyone knows??

Thanks in advance

2 REPLIES 2
Read only

Former Member
0 Likes
785

Hi,

The already predefined set of relationship is due to the data integrity and foriegn key relation ship.

so we get a predefined set of relaionships if we take view of existing master table.

since SKAT is gl account master for chart of accounts and its key fields would have the set of foriegn key relations with the corresponding key tables

like

ktopl- t004 etc

Read only

Former Member
0 Likes
784

Hi There,

Those are the Primary fields or key fields sharing the common data,, This is required to maintain the data consistency. SAP's major strength is its data integrity...

You will not be able to edit primary keys since these values are maintained in several other tables too. changing at one place and keeping it as is in another table lead to data inconsistency.

let me know if you have further queries.

don't forget to rward pionts if found useful.

Thanks-