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

Data Dictionary

Former Member
0 Likes
887

Hello,

Can anybody please explain me cleary?

(a) Field Checking at Data Element Level

(b) Field Checking at Domain Level

With regards to Domains & Data Elements

4 REPLIES 4
Read only

Former Member
0 Likes
573

Hi,

Domain is used for value range.

Means you can give set of value ranges at domain level.

data dictionary level means we can give a table as check table for entry help.

the values passed to the field are should be in check table.

Regards,

Read only

0 Likes
573

Domain illustate technical attributes and we can restrct the values with range...

Data element is the name that will be appearing on screen which you given in field label..

Regards,

Anand Lokineni,

Reward if it is useful...

Read only

Former Member
0 Likes
573

hi,

A combination of fields of a table is called a foreign key if this field combination is the primary key of

another table.

A foreign key links two tables.

The check table is the table whose key fields are checked. This table is also called the referenced table.

An entry is to be written in the foreign key table. This entry must be consistent with the key fields of the

check table.

The field of the foreign key table to be checked is called the check field.

Foreign keys can only be used in screens. Data records can be written to the table without being checked using an ABAP program.

In the ABAP Dictionary, the same domain is required for the check field and referenced key field of the

check table so that you do not compare fields with different data types and field lengths. Domain

equality is essential. Different data elements can be used, but they must refer to the same

domain.

The requirement for domain equality is only valid for the check field. For all other foreign key fields, it is

sufficient if the data type and the field length are equal. You nevertheless should strive for domain

equality. In this case the foreign key will remain consistent if the field length is changed because the

corresponding fields are both changed. If the domains are different, the foreign key will be inconsistent if

for example the field length is changed.

If the domain of the check field has a value table, you can have the system make a proposal with the

value table as check table. In this case a proposal is created for the field assignment in the foreign key.

Hope this helps, Do reward.

Read only

Former Member
0 Likes
573

Thaks