<?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 Value Table Purpose (Beyond standard SAP Documentation) in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/value-table-purpose-beyond-standard-sap-documentation/m-p/11525366#M1934734</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;So, to cover previous posts &amp;amp; documentation;&amp;nbsp;&amp;nbsp; the value table ...&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;is at Domain level&lt;/LI&gt;&lt;LI&gt;is proposed as a check table when you create a FK&lt;/LI&gt;&lt;LI&gt;does no entry check unless FK is in place.&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Given that the Value Table is not used as a check at data entry unless a FK is created, and any FK would specify the Check Table explicitly anyway ...&lt;/P&gt;&lt;P&gt;... what purpose does a value table serve ?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Is it simply to provide a 'hint' to anyone creating a new FK, as to what the check table should be ?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 28 Jan 2016 11:32:28 GMT</pubDate>
    <dc:creator>Former Member</dc:creator>
    <dc:date>2016-01-28T11:32:28Z</dc:date>
    <item>
      <title>Value Table Purpose (Beyond standard SAP Documentation)</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/value-table-purpose-beyond-standard-sap-documentation/m-p/11525366#M1934734</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;So, to cover previous posts &amp;amp; documentation;&amp;nbsp;&amp;nbsp; the value table ...&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;is at Domain level&lt;/LI&gt;&lt;LI&gt;is proposed as a check table when you create a FK&lt;/LI&gt;&lt;LI&gt;does no entry check unless FK is in place.&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Given that the Value Table is not used as a check at data entry unless a FK is created, and any FK would specify the Check Table explicitly anyway ...&lt;/P&gt;&lt;P&gt;... what purpose does a value table serve ?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Is it simply to provide a 'hint' to anyone creating a new FK, as to what the check table should be ?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 28 Jan 2016 11:32:28 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/value-table-purpose-beyond-standard-sap-documentation/m-p/11525366#M1934734</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2016-01-28T11:32:28Z</dc:date>
    </item>
    <item>
      <title>Re: Value Table Purpose (Beyond standard SAP Documentation)</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/value-table-purpose-beyond-standard-sap-documentation/m-p/11525367#M1934735</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;It provides values for F4 help.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 28 Jan 2016 11:43:53 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/value-table-purpose-beyond-standard-sap-documentation/m-p/11525367#M1934735</guid>
      <dc:creator>kakshat</dc:creator>
      <dc:date>2016-01-28T11:43:53Z</dc:date>
    </item>
    <item>
      <title>Re: Value Table Purpose (Beyond standard SAP Documentation)</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/value-table-purpose-beyond-standard-sap-documentation/m-p/11525368#M1934736</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thanks, is helpful.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Though one assumes that it would only do this if was also established as the FK ?&lt;/P&gt;&lt;P&gt;And if that were the case, could help simply not be fed with the values in the FK ?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 28 Jan 2016 11:47:15 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/value-table-purpose-beyond-standard-sap-documentation/m-p/11525368#M1934736</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2016-01-28T11:47:15Z</dc:date>
    </item>
    <item>
      <title>Re: Value Table Purpose (Beyond standard SAP Documentation)</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/value-table-purpose-beyond-standard-sap-documentation/m-p/11525369#M1934737</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 is list of values predefined to particular Domain/Data Element .&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;for example : we have field &lt;STRONG&gt;meins&lt;/STRONG&gt; field in &lt;STRONG&gt;MARA&lt;/STRONG&gt; table&amp;nbsp; i.e unit of measurement . navigate to meins field by double clicking on it , Go to value range tab at domain level , You will find a value table &lt;STRONG&gt;(T006)&lt;/STRONG&gt; at last . &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;So we can say that meins will only allow those values which are present in T006 table other than that it will not accept . and we can say that T006 is the&lt;STRONG&gt; value table f&lt;/STRONG&gt;or mara-meins .&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;While coming to&lt;STRONG&gt; check table &lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Take example of EKKO and EKPO&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;whenener you enter any PO in EKPO it first checks that value is present in EKKO or not .If PO is present in EKKO than only it will allow values otherwise EKPO will throw an error.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;here&amp;nbsp; EKPO is checking value in EKKO , we can say that EKKO is check table for EKPO.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&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;Sabir&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 28 Jan 2016 11:47:53 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/value-table-purpose-beyond-standard-sap-documentation/m-p/11525369#M1934737</guid>
      <dc:creator>sabirshah1</dc:creator>
      <dc:date>2016-01-28T11:47:53Z</dc:date>
    </item>
    <item>
      <title>Re: Value Table Purpose (Beyond standard SAP Documentation)</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/value-table-purpose-beyond-standard-sap-documentation/m-p/11525370#M1934738</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Simon,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The purpose of value table is not similar to check table, it is a value help at domain level.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Rahul&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 28 Jan 2016 11:50:36 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/value-table-purpose-beyond-standard-sap-documentation/m-p/11525370#M1934738</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2016-01-28T11:50:36Z</dc:date>
    </item>
    <item>
      <title>Re: Value Table Purpose (Beyond standard SAP Documentation)</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/value-table-purpose-beyond-standard-sap-documentation/m-p/11525371#M1934739</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;There may be scenarios where you do not want to restrict the possible values to a finite set (that defined by the foreign key).&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 28 Jan 2016 11:57:46 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/value-table-purpose-beyond-standard-sap-documentation/m-p/11525371#M1934739</guid>
      <dc:creator>kakshat</dc:creator>
      <dc:date>2016-01-28T11:57:46Z</dc:date>
    </item>
    <item>
      <title>Re: Value Table Purpose (Beyond standard SAP Documentation)</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/value-table-purpose-beyond-standard-sap-documentation/m-p/11525372#M1934740</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Yes for example the E071 table, foreign lock is defined with values space and X, but in relaity other values are in there as well.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 28 Jan 2016 12:04:49 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/value-table-purpose-beyond-standard-sap-documentation/m-p/11525372#M1934740</guid>
      <dc:creator>PeterJonker</dc:creator>
      <dc:date>2016-01-28T12:04:49Z</dc:date>
    </item>
    <item>
      <title>Re: Value Table Purpose (Beyond standard SAP Documentation)</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/value-table-purpose-beyond-standard-sap-documentation/m-p/11525373#M1934741</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Sabir,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Your example is a little misleading if I understand correctly.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You suggest that because a value table is assigned to the field/domain, that then restricts entries.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Yet SAPs own documentation states :&lt;/P&gt;&lt;PRE&gt;&lt;CODE&gt;
&lt;P&gt;"A check is not implemented by simply entering a value table. The check against the value table takes effect only when a foreign key has been defined."&lt;/P&gt;
&lt;/CODE&gt;&lt;/PRE&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 28 Jan 2016 13:14:22 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/value-table-purpose-beyond-standard-sap-documentation/m-p/11525373#M1934741</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2016-01-28T13:14:22Z</dc:date>
    </item>
    <item>
      <title>Re: Value Table Purpose (Beyond standard SAP Documentation)</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/value-table-purpose-beyond-standard-sap-documentation/m-p/11525374#M1934742</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;So in this case, you would use the Value Table to 'suggest' values to enter; but not enforce adherence to them ?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;That makes sense.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Think I could mark correct if you can confirm I'm understanding you correctly ?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 28 Jan 2016 13:44:34 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/value-table-purpose-beyond-standard-sap-documentation/m-p/11525374#M1934742</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2016-01-28T13:44:34Z</dc:date>
    </item>
    <item>
      <title>Re: Value Table Purpose (Beyond standard SAP Documentation)</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/value-table-purpose-beyond-standard-sap-documentation/m-p/11525375#M1934743</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Yes.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 28 Jan 2016 16:30:35 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/value-table-purpose-beyond-standard-sap-documentation/m-p/11525375#M1934743</guid>
      <dc:creator>kakshat</dc:creator>
      <dc:date>2016-01-28T16:30:35Z</dc:date>
    </item>
    <item>
      <title>Re: Value Table Purpose (Beyond standard SAP Documentation)</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/value-table-purpose-beyond-standard-sap-documentation/m-p/11525376#M1934744</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Simon,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Kindly Correct me , where i am going wrong .&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 29 Jan 2016 06:26:49 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/value-table-purpose-beyond-standard-sap-documentation/m-p/11525376#M1934744</guid>
      <dc:creator>sabirshah1</dc:creator>
      <dc:date>2016-01-29T06:26:49Z</dc:date>
    </item>
  </channel>
</rss>

