cancel
Showing results for 
Search instead for 
Did you mean: 

Check table Vs Value table?

Former Member
0 Kudos

Check table Vs Value table?

can anyone pl explain in detail???

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

Hi Mayank,

Check this info.

Check Table is for Field level Validation whereas Value table is for Domain Level Validations.

Value Table proposes table for check table.

I think you are clear with this.

more elaborate.

**************************

Check Table

The Check Table is the table used by system to check if a data exist or not exist.

While creating a table if you want to be sure that a field can have some values

and these are in a certain table, you can give IT this table as CHECK TABLE.

Value Table

This is maintained at Domain Level.

When ever you create a domain , you can entered allowed values. For example you go to Domain SHKZG - Debit/credit indicator.

Here only allowed values is H or S.

When ever you use this Domain, the system will forces you to enter only these values.

This is a sort of master check . .

To be maintained as a customization object.

This mean that if you want to enter values to this table you have to create a development request & transport the same.

Differences:

1)check table will carry out the check for input values for the table field being entered in any application

and value table will provide values on F4 help for that table field.

2)The check table defines the foreign keys and is part of the table definition.

The value table is part of the domain definition.

Also Check this info.

CHECK TABLE----


VALUE TABLE

1. It works at table level.----


1. It works at a domain level.

2. It is a master table -


2. It provides a list of values

with a valid set of values.----


which will be automatically

-


proposed as a check table

-


while creating a foreign key

-


relationship.

3. The contents of this table----


3. It is a sort of master check.

will be used for input help----


for which the check table is -


assigned.----


4. It is called as foreign key----


4. It may also be maintained

table in DBMS.----


as a customization object,

-


which may require to

-


transport development request.

Value Table

The system proposes the value table as check table when you try to define a foreign key for the field or component. This proposal can be overridden.

https://www.sdn.sap.com/irj/sdn/advancedsearch?cat=sdn_help&query=value+table&adv=false&sortby=cm_rn...

Refer

Hope this resolves your query.

Reward all the helpful answers.

Regards

Answers (7)

Answers (7)

Former Member
0 Kudos

Check Table:
* T1 and T2 are two different tables.
* In T1, you planned to assign a foreign key(T1-F1). It generates proposal and finally you choose a         table and its field as Check table (T2) and its corresponding field (T2-F1) as check field.

  You can enter the values for T1-K1 what are available only in T2-F1.

Value Table:

* When we create a Domain we can assign values for the field.

* Either fixed values or a Table can be used for this purpose then the table is called Value table.
* Value table wont help during F4 Input help process

* If you try to assign foreign key for the field using this domain, it will generate the proposal for check table as the Value table of this particular domain.

dustyplanet
Active Participant
0 Kudos

Simplified,

When you create a domain, you usually know in which table you will use it for the first time... this first table is also usually the source of values for the domain, wherever it may be used subsequently. For example, whoever created the SYCURR domain knew that TCURX would be the first table to use this domain and also happens to be the master list of values for any field(in any other table) that uses this domain.

Now when we create our own tables using this domain, you will normally need to figure out which table to reference as the check table for that field. In this example, if I decide to use the SYCURR domain to create a field called, say, CURRENCY in my table, I will not know outright, which table should be used to provide value help for, and validate values for the CURRENCY field, in other words, which table should be the CHECK TABLE for this field. But when I click the "Foreign Key" Button to create a foreign key for CURRENCY, the system automatically proposes the table TCURX as the check table, this is because of the foresight of the developer of SYCURR who took the effort to set TCURX as the value table for this domain. Obviously, this takes the pain out of researching which table to use as CHECK TABLE for your own fields.

Note, however, that the value table setting has absolutely no effect on the behaviour of the field, It is incorrectly believed, that VALUE TABLEs affect F4 help. They do not influence any behaviour at all ! The only effect of having a VALUE TABLE in a domain is the assistance you are offered when you try to create a FOREIGN KEY from a field that uses the said domain.

Hope this helps...

Regards,

Dushyant Shetty

P.S. This question belongs in the ABAP Dictionary section

Former Member
0 Kudos

hi,

check table : it is a dependent table.

field table : restricting values in domain level.

Reward points if helpful.

Message was edited by:

Vinutha YV

Former Member
0 Kudos

Hi Mayank,

The Check Table is the dependent table to which the relationship is defined using foreign keys. The contents of the check table field are shown in the input help for the referenced field.

For example you have Employee master table & Employee Transaction table.

When ever an employee Transacts we need to check whether that employee exists , so we can refer to the employee master table.

This is nothing but a Parent & Child relationship . Here data can be maintained at client level , no development involved.

As per DBMS what we call foregin key table, is called as check table in SAP.

The Value table is the table attached to a field at the domain level, where the entry to the field can be only from the value table. They are not used in the Input Help.

This is maintained at Domain Level.

When ever you create a domain , you can entered allowed values. For example you go to Domain SHKZG - Debit/credit indicator. Here only allowed values is H or S.

When ever you use this Domain, the system will forces you to enter only these values.

This is a sort of master check . To be maintained as a customization object. This mean that if you want to enter values to this table you have to create a development request & transport the same.

There is 1 more important Difference in Value Table and Check Table is that:

1. The contents of the check will be used as an input help(F4 Help) for a particular field on which a check table is assigned.

But the contents of Value Table are never used in Input Help.

The Heirarchy which decides from where to used the Input Help is:

1. Input help defined explicitly in ABAP Program or Dialog Module.

2. Input Help Attached to the referenced Database Table field.

3. Using the contents of Check Table as an input help if neither (1) or (2) help are there.

4. Input help from Fixed value or Value range given in Domain.

The Check Table is the dependent table to which the relationship is defined using foreign keys. The contents of the check table field are shown in the input help for the referenced field.

The Value table is the table attached to a field at the domain level, where the entry to the field can be only from the value table. They are not used in the Input Help.

Regards,

Hemant

Former Member
0 Kudos

Hi,

The Check Table is the dependent table to which the relationship is defined using foreign keys. The contents of the check table field are shown in the input help for the referenced field.

The Value table is the table attached to a field at the domain level, where the entry to the field can be only from the value table. They are not used in the Input Help.

Check this link for few more difference between Check table and Value table

http://www.sap-img.com/abap/difference-between-a-check-table-and-a-value-table.htm

Hope this info helps.

Regards,

Kumar.

Former Member
0 Kudos

Hai,

The Check Table is the dependent table to which the relationship is defined using foreign keys. The contents of the check table field are shown in the input help for the referenced field.

For example you have Employee master table & Employee Transaction table.

When ever an employee Transacts we need to check whether that employee exists , so we can refer to the employee master table.

This is nothing but a Parent & Child relationship . Here data can be maintained at client level , no development involved.

As per DBMS what we call foregin key table, is called as check table in SAP.

The Value table is the table attached to a field at the domain level, where the entry to the field can be only from the value table. They are not used in the Input Help.

This is maintained at Domain Level.

When ever you create a domain , you can entered allowed values. For example you go to Domain SHKZG - Debit/credit indicator. Here only allowed values is H or S.

When ever you use this Domain, the system will forces you to enter only these values.

This is a sort of master check . To be maintained as a customization object. This mean that if you want to enter values to this table you have to create a development request & transport the same.

There is 1 more important Difference in Value Table and Check Table is that:

1. The contents of the check will be used as an input help(F4 Help) for a particular field on which a check table is assigned.

But the contents of Value Table are never used in Input Help.

The Heirarchy which decides from where to used the Input Help is:

1. Input help defined explicitly in ABAP Program or Dialog Module.

2. Input Help Attached to the referenced Database Table field.

3. Using the contents of Check Table as an input help if neither (1) or (2) help are there.

4. Input help from Fixed value or Value range given in Domain.

Regards,

Padmam.

Former Member
0 Kudos

value table is generated in the domain of a field

Check Table is a table which provides the number of possible entries along with the Validation(when we give primary keys)