<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Data Dictionary in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/data-dictionary/m-p/2733486#M634808</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&amp;lt;b&amp;gt;Value Table&amp;lt;/b&amp;gt;&lt;/P&gt;&lt;P&gt;This is maintained at Domain Level.&lt;/P&gt;&lt;P&gt;When ever you create a domain , you can enter only certain allowed values.For example, if you go to Domain SHKZG - Debit/credit indicator. Here only H or S are allowed.&lt;/P&gt;&lt;P&gt;Whenever you use this Domain, the system will force you to enter only these values.&lt;/P&gt;&lt;P&gt;This is a sort of master check.It is to be maintained as a customization object. This means if you want to enter values to this table you have to create a development request &amp;amp; transport the same.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;lt;b&amp;gt;CHECK Vs VALUE Table&amp;lt;/b&amp;gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;check table is validation at field level.&lt;/P&gt;&lt;P&gt;value table is at domain level.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Value table is defined at the domain level and is used to provide F4 help for all the fields which refer to that domain.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Check table is defined against a field in SE11 if you want the values in that field to be checked against a list of valid values. For e.g. if you are using the field matnr in a table you could define MARA as the check table.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Also while defining a check table SAP proposes the value table as check table by default. Referring to the previous example if you tried to define a check table for the matnr field SAP would propose MARA as the check table.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;1. what is the purpose / use ?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;-- so that the user can select values&lt;/P&gt;&lt;P&gt;from some master table , for that field !!!!&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;2. This is done by&lt;/P&gt;&lt;P&gt;CHECK TABLE (foreign key concept)&lt;/P&gt;&lt;P&gt;(and not value table)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;3. When we create a check table for a field,&lt;/P&gt;&lt;P&gt;then&lt;/P&gt;&lt;P&gt;some DEFAULT table is PROPOSED&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;4. that DEFAULT table is nothing&lt;/P&gt;&lt;P&gt;but PICKED up from the domain of that field,&lt;/P&gt;&lt;P&gt;and shown from the value of VALUE TABLE.&lt;/P&gt;&lt;P&gt;CHECK TABLE -it is a parent table.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;for example..&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;i have two tables ZTAB1 and ZTAB2.&lt;/P&gt;&lt;P&gt;I have one common field in both the tables,i can make any ztable to be the check table .If i make Ztab1 to be the check table then when i have to make an entry in ztab2 i will check whether ztab1 is having that value or not..&lt;/P&gt;&lt;P&gt;its also field level checking..&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Valuetable-It is nothing but default check table.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;one parent can have n number of child tables.For example&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;For ztable we have zchild1 and zchild2 tables r there.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Its domain level checking..When zchild2 uses the same domain as used by zchild1 then the system automatically generates a popup saying a check table already exists would u want to maintain it.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;go to domain and then press the value tab u can see the valuetable at the end...&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Difference between a check table and a value table &lt;/P&gt;&lt;P&gt;Value Table &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;This is maintained at Domain Level. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;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. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;When ever you use this Domain, the system will forces you to enter only these values. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;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 &amp;amp; transport the same. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Check table &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;For example you have Employee master table &amp;amp; Employee Transaction table. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;When ever an employee Transacts we need to check whether that employee exists , so we can refer to the employee master table. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;This is nothing but a Parent &amp;amp; Child relationship . Here data can be maintained at client level , no development involved. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;As per DBMS what we call foregin key table, is called as check table in SAP. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;There is 1 more important Difference in Value Table and Check Table is that: &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;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. &lt;/P&gt;&lt;P&gt;But the contents of Value Table are never used in Input Help. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The Heirarchy which decides from where to used the Input Help is: &lt;/P&gt;&lt;P&gt;1. Input help defined explicitly in ABAP Program or Dialog Module. &lt;/P&gt;&lt;P&gt;2. Input Help Attached to the referenced Database Table field. &lt;/P&gt;&lt;P&gt;3. Using the contents of Check Table as an input help if neither (1) or (2) help are there. &lt;/P&gt;&lt;P&gt;4. Input help from Fixed value or Value range given in Domain.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Please refer the links below,&lt;/P&gt;&lt;P&gt;&lt;A class="jive_macro jive_macro_thread" href="https://community.sap.com/" __jive_macro_name="thread" modifiedtitle="true" __default_attr="272137"&gt;&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;A class="jive_macro jive_macro_thread" href="https://community.sap.com/" __jive_macro_name="thread" modifiedtitle="true" __default_attr="53950"&gt;&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;A class="jive_macro jive_macro_thread" href="https://community.sap.com/" __jive_macro_name="thread" modifiedtitle="true" __default_attr="179945"&gt;&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;A class="jive_macro jive_macro_thread" href="https://community.sap.com/" __jive_macro_name="thread" modifiedtitle="true" __default_attr="209949"&gt;&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;A class="jive_macro jive_macro_message" href="https://community.sap.com/" __jive_macro_name="message" modifiedtitle="true" __default_attr="559329"&gt;&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://www.sap-img.com/abap/difference-between-a-check-table-and-a-value-table.htm" target="test_blank"&gt;http://www.sap-img.com/abap/difference-between-a-check-table-and-a-value-table.htm&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;regards,&lt;/P&gt;&lt;P&gt;srinivas&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;lt;b&amp;gt;*&lt;STRONG&gt;reward for useful answers&lt;/STRONG&gt;*&amp;lt;/b&amp;gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 06 Sep 2007 08:32:18 GMT</pubDate>
    <dc:creator>Former Member</dc:creator>
    <dc:date>2007-09-06T08:32:18Z</dc:date>
    <item>
      <title>Data Dictionary</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/data-dictionary/m-p/2733484#M634806</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;What is Value Table?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 06 Sep 2007 07:55:14 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/data-dictionary/m-p/2733484#M634806</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-09-06T07:55:14Z</dc:date>
    </item>
    <item>
      <title>Re: Data Dictionary</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/data-dictionary/m-p/2733485#M634807</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;hi monalisa,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Welcome to SDN.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;   Simple definition of the value table : The table containing set of allowed values attached to a domain.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://help.sap.com/saphelp_47x200/helpdata/en/e2/667092730811d2959500a0c929b3c3/frameset.htm" target="test_blank"&gt;http://help.sap.com/saphelp_47x200/helpdata/en/e2/667092730811d2959500a0c929b3c3/frameset.htm&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards...&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Arun.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Reward points if useful.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 06 Sep 2007 07:59:39 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/data-dictionary/m-p/2733485#M634807</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-09-06T07:59:39Z</dc:date>
    </item>
    <item>
      <title>Re: Data Dictionary</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/data-dictionary/m-p/2733486#M634808</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&amp;lt;b&amp;gt;Value Table&amp;lt;/b&amp;gt;&lt;/P&gt;&lt;P&gt;This is maintained at Domain Level.&lt;/P&gt;&lt;P&gt;When ever you create a domain , you can enter only certain allowed values.For example, if you go to Domain SHKZG - Debit/credit indicator. Here only H or S are allowed.&lt;/P&gt;&lt;P&gt;Whenever you use this Domain, the system will force you to enter only these values.&lt;/P&gt;&lt;P&gt;This is a sort of master check.It is to be maintained as a customization object. This means if you want to enter values to this table you have to create a development request &amp;amp; transport the same.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;lt;b&amp;gt;CHECK Vs VALUE Table&amp;lt;/b&amp;gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;check table is validation at field level.&lt;/P&gt;&lt;P&gt;value table is at domain level.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Value table is defined at the domain level and is used to provide F4 help for all the fields which refer to that domain.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Check table is defined against a field in SE11 if you want the values in that field to be checked against a list of valid values. For e.g. if you are using the field matnr in a table you could define MARA as the check table.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Also while defining a check table SAP proposes the value table as check table by default. Referring to the previous example if you tried to define a check table for the matnr field SAP would propose MARA as the check table.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;1. what is the purpose / use ?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;-- so that the user can select values&lt;/P&gt;&lt;P&gt;from some master table , for that field !!!!&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;2. This is done by&lt;/P&gt;&lt;P&gt;CHECK TABLE (foreign key concept)&lt;/P&gt;&lt;P&gt;(and not value table)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;3. When we create a check table for a field,&lt;/P&gt;&lt;P&gt;then&lt;/P&gt;&lt;P&gt;some DEFAULT table is PROPOSED&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;4. that DEFAULT table is nothing&lt;/P&gt;&lt;P&gt;but PICKED up from the domain of that field,&lt;/P&gt;&lt;P&gt;and shown from the value of VALUE TABLE.&lt;/P&gt;&lt;P&gt;CHECK TABLE -it is a parent table.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;for example..&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;i have two tables ZTAB1 and ZTAB2.&lt;/P&gt;&lt;P&gt;I have one common field in both the tables,i can make any ztable to be the check table .If i make Ztab1 to be the check table then when i have to make an entry in ztab2 i will check whether ztab1 is having that value or not..&lt;/P&gt;&lt;P&gt;its also field level checking..&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Valuetable-It is nothing but default check table.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;one parent can have n number of child tables.For example&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;For ztable we have zchild1 and zchild2 tables r there.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Its domain level checking..When zchild2 uses the same domain as used by zchild1 then the system automatically generates a popup saying a check table already exists would u want to maintain it.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;go to domain and then press the value tab u can see the valuetable at the end...&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Difference between a check table and a value table &lt;/P&gt;&lt;P&gt;Value Table &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;This is maintained at Domain Level. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;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. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;When ever you use this Domain, the system will forces you to enter only these values. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;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 &amp;amp; transport the same. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Check table &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;For example you have Employee master table &amp;amp; Employee Transaction table. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;When ever an employee Transacts we need to check whether that employee exists , so we can refer to the employee master table. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;This is nothing but a Parent &amp;amp; Child relationship . Here data can be maintained at client level , no development involved. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;As per DBMS what we call foregin key table, is called as check table in SAP. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;There is 1 more important Difference in Value Table and Check Table is that: &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;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. &lt;/P&gt;&lt;P&gt;But the contents of Value Table are never used in Input Help. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The Heirarchy which decides from where to used the Input Help is: &lt;/P&gt;&lt;P&gt;1. Input help defined explicitly in ABAP Program or Dialog Module. &lt;/P&gt;&lt;P&gt;2. Input Help Attached to the referenced Database Table field. &lt;/P&gt;&lt;P&gt;3. Using the contents of Check Table as an input help if neither (1) or (2) help are there. &lt;/P&gt;&lt;P&gt;4. Input help from Fixed value or Value range given in Domain.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Please refer the links below,&lt;/P&gt;&lt;P&gt;&lt;A class="jive_macro jive_macro_thread" href="https://community.sap.com/" __jive_macro_name="thread" modifiedtitle="true" __default_attr="272137"&gt;&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;A class="jive_macro jive_macro_thread" href="https://community.sap.com/" __jive_macro_name="thread" modifiedtitle="true" __default_attr="53950"&gt;&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;A class="jive_macro jive_macro_thread" href="https://community.sap.com/" __jive_macro_name="thread" modifiedtitle="true" __default_attr="179945"&gt;&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;A class="jive_macro jive_macro_thread" href="https://community.sap.com/" __jive_macro_name="thread" modifiedtitle="true" __default_attr="209949"&gt;&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;A class="jive_macro jive_macro_message" href="https://community.sap.com/" __jive_macro_name="message" modifiedtitle="true" __default_attr="559329"&gt;&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://www.sap-img.com/abap/difference-between-a-check-table-and-a-value-table.htm" target="test_blank"&gt;http://www.sap-img.com/abap/difference-between-a-check-table-and-a-value-table.htm&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;regards,&lt;/P&gt;&lt;P&gt;srinivas&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;lt;b&amp;gt;*&lt;STRONG&gt;reward for useful answers&lt;/STRONG&gt;*&amp;lt;/b&amp;gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 06 Sep 2007 08:32:18 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/data-dictionary/m-p/2733486#M634808</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-09-06T08:32:18Z</dc:date>
    </item>
    <item>
      <title>Re: Data Dictionary</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/data-dictionary/m-p/2733487#M634809</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;hi&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt; &lt;/P&gt;&lt;P&gt; Value Table &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;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.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;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.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;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.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;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.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt; reward if helpful&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;vivekanand&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 06 Sep 2007 09:33:06 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/data-dictionary/m-p/2733487#M634809</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-09-06T09:33:06Z</dc:date>
    </item>
    <item>
      <title>Re: Data Dictionary</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/data-dictionary/m-p/2733488#M634810</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Monalisa,&lt;/P&gt;&lt;P&gt; Value table shows the value with out validation means when u enter the value into table at that time it will not check where this value is already exit or not .&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Nihar swain .&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 06 Sep 2007 09:34:37 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/data-dictionary/m-p/2733488#M634810</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-09-06T09:34:37Z</dc:date>
    </item>
    <item>
      <title>Re: Data Dictionary</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/data-dictionary/m-p/2733489#M634811</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;HI&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;lt;b&amp;gt;Value table&amp;lt;/b&amp;gt;In some cases you already know when you define a domain that all the fields referring to this domain should be checked against a certain table. This information can be stored in the domain by entering a value table.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The system proposes the value table as check table when you try to define a foreign key for this field. You can override this proposal.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Entering a value table does not implement a check. The check against the value table only takes place when a foreign key is defined.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;lt;b&amp;gt;reward if usefull&amp;lt;/b&amp;gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 06 Sep 2007 14:16:29 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/data-dictionary/m-p/2733489#M634811</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-09-06T14:16:29Z</dc:date>
    </item>
  </channel>
</rss>

