topic Re: When is Value table called? in Application Development and Automation Discussions

When is Value table called?

Former Member — Thu, 27 May 2010 12:02:18 GMT

Hi,

I have created a z table , with two fields pernr & kostl .

I have kept pernr as primary key. For kostl field I have created same name for data element and domain "zkostl".

Inside domain zkostl i have defined value table zcsks where 1 record exist.

when i execute the table , kostl field there is no input help from value table (zcsks).

What is the use of value table ?

can we keep value table and check table differrent ?

if so, which will be called first?

Regards,

Rachel

Edited by: Rachel on May 27, 2010 2:02 PM

Re: When is Value table called?

MarcinPciak — Thu, 27 May 2010 12:17:18 GMT

Hi Rachel,

Please refer our discussion on value table . You will get the anwser.

Regards

Marcin

Re: When is Value table called?

Former Member — Fri, 28 May 2010 06:36:00 GMT

Hi ,

"The check table must have a key field which has the same domain as the check field of the foreign key table."

the above means that when I use domain(which contains value table ) the same domain must be there in check table .

So that means value table and check table are always same .

By defining only value table i cannot get input help , i have to have check table .

Then what is the use of value table ?

whlile creating z field i can directly use a check table without defining a value table in domain.

Kindly explain me the use of value table in terms of adding zfield .

Regards,

Rachel

Re: When is Value table called?

MarcinPciak — Fri, 28 May 2010 07:12:44 GMT


"The check table must have a key field which has the same domain as the check field of the foreign key table."
the above means that when I use domain(which contains value table ) the same domain must be there in check table .

Yes, the domain must be the same for check field (some field in ztable which you want input help for) and for key field of check table (which we match with check field).

I.e. when you look at table SPFLI you can see field CARRID (this is check field ) . Click on it and select Foreign keys (key icon button). You will see SCARR (this is check table ) and matching keys MANDT and CARRID (foreign keys for them are SPFLI-MANDT and SPFLI-CARRID). Then you go to check table SCARR and look at field CARRID.

The domain must be equal for check field (SPFLI-CARRID) and corresponding check table field (SCARR-CARRID). Only then the input help will be provided correctly.


So that means value table and check table are always same .

Not necessarly, but most often yes. This is because value table serves only the purpose of providing default table for foregin key relationship (when you want to define one), but you are allowed to change that assignment during relationship creation. No other "value" comes with using value table


By defining only value table i cannot get input help , i have to have check table

Correct!


Then what is the use of value table ?

As explained above, only for developer to have proposed this value table as a check table during foreign key definition.


whlile creating z field i can directly use a check table without defining a value table in domain.

Yes, you can. Nevertheless you will have to provide check table yourself. System will not suggest one.


Kindly explain me the use of value table in terms of adding zfield .

No sure if correctly understand you here. ZFIELD can use value table, but without check table it is useless. It will not provide you any input help, nor will check entry for that field when used i.e. on the screen.

If you still feel not good with above explanations please refer [Value table|http://help.sap.com/saphelp_bw/helpdata/en/e2/667092730811d2959500a0c929b3c3/frameset.htm] and [Creating foreign keys|http://help.sap.com/saphelp_bw/helpdata/en/e2/667092730811d2959500a0c929b3c3/frameset.htm]

Regards

Marcin

Re: When is Value table called?

Former Member — Fri, 28 May 2010 09:25:26 GMT

You have beautifully expained ...in a very systematic & logical way....

I have found the below differrence in many places....

Value table - It's a field in a domain it helps in domain level data validation.

Check table - unlike value table it helps in feild level data validation.

i would like to understand what is domain level validatiation ....& when it is used ?

Regards,

Rachel

Re: When is Value table called?

Former Member — Fri, 28 May 2010 09:29:31 GMT

Thanks Marcin .

You have beautifully expained in a very systematic & logical way.

I have found the below differrence in many places....

Value table - It's a field in a domain it helps in domain level data validation.

Check table - unlike value table it helps in feild level data validation.

i would like to understand what is domain level validatiation ....& when it is used ?

Regards,

Rachel

Edited by: Rachel on May 28, 2010 11:30 AM

Re: When is Value table called?

MarcinPciak — Fri, 28 May 2010 10:41:16 GMT

According to this [link|http://www.sap-img.com/abap/difference-between-a-check-table-and-a-value-table.htm]


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

system will not allow us to enter value out of range (not in value table). But for me this is untrue. The proof


PARAMETERS pa_conn type s_conn_id.

S_CONN_ID uses domain S_CONN_ID which has value table SPFLI . There is neither check made when you enter data to that field, nor any input help provided.

Basically what I found in BC430 course about value table is


- 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 F4 help either.
- If you enter 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.

So this follows our discussion and understanding of input help provider.

so if you say


Value table - It's a field in a domain it helps in domain level data validation.

I think this is untrue. There is no mechanism in SAP which provides such kind of validation . The true is (and what author most probably meant) that value table defines the range of possible values for field which uses that domain. This is similar to saying "here are the values which you should use only, but unless you provide check table for that field, I am unable to verify your entry".

Domain itself describes technical attributes. If you create an empty domain without value restriction of type INT1, you in fact are defining a range for (only integer values less then 255). Then use that domain in any zdata element and type parameter in the screen with that. You will see that you are only allowed to enter val < 255, otherwise system will shout. In contrary when you maintain value range you are allowed to enter any value, but if you use it on i.e. listbox, you will be restricted only to these values.

The value table seems to don't work in any of these cases (no validation, no input help). So this is just a matter of being aware that only values from this value table are allowed, nothing else I think.