Value Table

[Former Member]

Hi Everybody ,

Can anyone say where we use VALUE TABLE Exactly in Detail..

Regards ,

Raju.

[Former Member]

hi,

value table is nothing but the value range that u maintain at the domain level.

whenever u create a doamin, u can specify the values to rstrict the data by specifying in value range tab.

regards,

madhu

[Former Member]

Raju,

just refer:

Amit.

[Former Member]

Letu2019s take an example:

Suppose you have created a custom table ztab1 with MATNR as key field.

Now you want to create a domain whose possible values should be that material that is stored in the custom table ztab1. So while creating the domain, you should specify the value table as ztab1.

Reward if usefulu2026

- Tushar

[Former Member]

Hi raju

greetings

we use value table to store the Domain values.

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.

A check is not implemented by simply entering a value table! The check against the value table only takes effect when a foreign key has been defined.

thnx

prashant

[Former Member]

Hii!

Value table is defined at domain level. The value range of a field can also be defined by specifying a value table in the domain.

In contrast to fixed values, however, simply specifying a value table does not cause the input to be checked. There is no input help either.

If you eneter a value table, the system can make a proposal

for the foreign key definition.

A value table only becomes a check table when a foreign key is defined. If you refer to a domain with a value table in a field,

but no foreign key was defined at field level, there is no check.

Regards

Abhijeet Kulshreshtha

[Former Member]

this will help u

[Former Member]

Hi Raju.

Your question extremely valid and important.

According to me,

In some cases you can see when you define a domain that all the table fields or structure components referring to this domain should be checked against a certain table.

This information can be stored in the domain by entering a value table.

The system recommends the value table as check table when you try to define a foreign key for the field or component. We can go pass this requirement by overriding.

A check is not implemented by simply entering a value table. The check against the value table only takes effect when a foreign key has been defined.

The very best EXAMPLE is :

Domain S_CARR_ID (data type CHAR, length 3) in the flight model describes the three-place code of the airlines. All the airlines are listed together with their codes in table SCARR. It is generally advisable to check fields referring to domain S_CARR_ID against table SCARR. SCARR is therefore entered as value table for domain S_CARR_ID. If you want to define a foreign key for a field referring to S_CARR_ID, SCARR is proposed as the check table.

If you find this information usefull, I will be very glad.

If you need more clarification, feel free to discuss with me.

Reward points if you find this information usefull.

Regards Harsh.

Edited by: Harsh Dave on Jun 27, 2008 6:23 PM

[Former Member]

Hello raju,

We already have a good thread on sdn where you can get a good answer to your query,

Check this out...

[;

For an overview of value table..

[http://help.sap.com/saphelp_nw70/helpdata/en/e2/667092730811d2959500a0c929b3c3/content.htm]

Hope it really helps you,

Best of luck,

bhumika..

Revert if any issues

[Former Member]

Hi,

When you want to display possible values for a field then you can maintain those possible values at domain level.

We can give Fixed values,value table, value ranges to for a field. To do this we have to maintain all these at domain level.

When you have some possible values you can enter it in Fixed values.

When you have some ranges then go for value ranges.

If we have many possible values to display then store all thes possible values in a table. Then you can use this table as value table for that field .Enter the value table name at the domain level.

Then these values will be displayed for that field when you press F4 .

[Former Member]

Hi raju,

Value table is maintained in the domain level of a database table field used to restrict its values.

In some cases you can see when you define a domain that all the table fields or structure

components referring to this domain should be checked against a certain table. This information

can be stored in the domain by entering a value table.

Reward if found helpful.

Anirban Bhattacharjee

[Former Member]

Hi,

Value table is to restrict the user's input by provsing the use with only a few values allowed. When ever you try to create the domain then you can give either value ranges or bvalue table.

InValue ranegs , we can provide only with some values but in value table we can provide more number of values.

For ex when you create the domain as Gender- the posible values are FEMALE or MALE.

this can be provided at value ranges tab.

Ex for VALUE TABLE:

When ever a company is into manufacturing they willb be usign some material to maufacture a product. Here the material list to get a finished product is predefined. Every Manufactuing uint maitnains the list of matierails to be used to produce a product. This list of matierial numbers in maitnained in a Table called Values table. here the user cant enter other matieril that is not htere in t

the Value table. here we are validating the matierial.

Sometiems Both Chektable and value table refers to same table.

Reward if helpful.

Best Wishes,

Chandralekha

[Former Member]

Hi,

Value Table gives a list of possible values at Domain level. It is defined in the Domain and is used for domain level checking or validation.

Regards

Kiran Kumar V