<?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: MATCH CODE in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/match-code/m-p/2498404#M564392</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;Macro Choosefields (&amp;amp;Fieldname [Choose)... [Copy EndMacro&lt;/P&gt;&lt;P&gt;/SE11 "ABAP Data Dictionary&lt;/P&gt;&lt;P&gt;&amp;lt;Object name "the name of the Match Code Object&lt;/P&gt;&lt;P&gt;*Matchcode objects&lt;/P&gt;&lt;P&gt;[Create &amp;gt;&amp;lt;Short Text &amp;gt;&amp;lt;Primary Table &lt;/P&gt;&lt;P&gt;[Tables&lt;/P&gt;&lt;P&gt;[Yes "Save before terminating Editing?&lt;/P&gt;&lt;P&gt;&amp;gt;&amp;lt;Development Class [Save&lt;/P&gt;&lt;P&gt;[Choose Sec. Tab. "presents candidate list&lt;/P&gt;&lt;P&gt;(&amp;amp;Tablename [Choose)... [Copy&lt;/P&gt;&lt;P&gt;[Fields &lt;/P&gt;&lt;P&gt;[Yes "Save before terminating Editing?&lt;/P&gt;&lt;P&gt;[Enter &lt;/P&gt;&lt;P&gt;(&amp;amp;Tablename [Choose Fields #Choosefields)..&lt;/P&gt;&lt;P&gt;[Save [Back [Activate&lt;/P&gt;&lt;P&gt;"Match Code Object is now created and activated.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Matchcodes are an SAP technique to help users find information, normally in&lt;/P&gt;&lt;P&gt;connection with the F4 key on an input field. Information from one or more &lt;/P&gt;&lt;P&gt;tables can be combined and queried on using various search criteria: for &lt;/P&gt;&lt;P&gt;example, all companies whose name starts with "TATA" and whose location is&lt;/P&gt;&lt;P&gt;"INDIA."&lt;/P&gt;&lt;P&gt;Traditionally, matchcodes were implemented as redundant collections of data &lt;/P&gt;&lt;P&gt;in pool tables, as illustrated in the following:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Company header table Company detail table Matchcode pool table&lt;/P&gt;&lt;P&gt;(TAB1) (TAB2) (M_POOL)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The advantage of the old pool matchcodes was a quick and easy search, as &lt;/P&gt;&lt;P&gt;long as the significant fields were entered by the end user (in this case, &lt;/P&gt;&lt;P&gt;company name and location). The disadvantage was that for every change in &lt;/P&gt;&lt;P&gt;the master tables, the system had to make redundant updates in the matchcode&lt;/P&gt;&lt;P&gt;tables. In addition, it was impossible to search in a pool matchcode for any&lt;/P&gt;&lt;P&gt;but the significant fields, i.e., it would have been very CPU intensive to&lt;/P&gt;&lt;P&gt;search for all companies in San Francisco.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;This limitation led to the creation of matchcodes (more precisely, in SAP &lt;/P&gt;&lt;P&gt;terms, "matchcode IDs") for every possible query you could expect from end&lt;/P&gt;&lt;P&gt;users (one with company name as the significant field, one with location,&lt;/P&gt;&lt;P&gt;yet another with customer number, and so on). Customers with a very high &lt;/P&gt;&lt;P&gt;number of debitors, for example, soon found that their pool matchcode tables &lt;/P&gt;&lt;P&gt;grew to unmanageable sizes.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;As of release 2.1, it is now possible to define so-called transparent or&lt;/P&gt;&lt;P&gt;view matchcodes. Transparent matchcodes are implemented by defining a&lt;/P&gt;&lt;P&gt;database view for the information that should be queried. Database views are&lt;/P&gt;&lt;P&gt;not redundant containers of data, but are merely definitions of paths to&lt;/P&gt;&lt;P&gt;obtaining that data. In the example:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Company header table Company detail table Database view:&lt;/P&gt;&lt;P&gt;(TAB1) (TAB2) (M_VIEW)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The advantage of this new technique is that it is no longer necessary to &lt;/P&gt;&lt;P&gt;maintain redundant matchcode data: a view takes only a small amount of &lt;/P&gt;&lt;P&gt;database dictionary space. Using this technique, the query is converted by &lt;/P&gt;&lt;P&gt;the database to a query against the original tables, so it becomes very &lt;/P&gt;&lt;P&gt;important that access be supported by the proper indexes.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;lt;u&amp;gt;&amp;lt;b&amp;gt;CHECK THIS LINK&amp;lt;/b&amp;gt;&amp;lt;/u&amp;gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://help.sap.com/saphelp_40b/helpdata/en/cf/21ef46446011d189700000e8322d00/content.htm" target="test_blank"&gt;http://help.sap.com/saphelp_40b/helpdata/en/cf/21ef46446011d189700000e8322d00/content.htm&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://web.mit.edu/sapr3/docs/webdocs/dontindex/pdf/mcqc.pdf" target="test_blank"&gt;http://web.mit.edu/sapr3/docs/webdocs/dontindex/pdf/mcqc.pdf&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Reward if helpfull&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;Pavan&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Message was edited by: &lt;/P&gt;&lt;P&gt;        Pavan praveen&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Sat, 21 Jul 2007 07:26:10 GMT</pubDate>
    <dc:creator>Former Member</dc:creator>
    <dc:date>2007-07-21T07:26:10Z</dc:date>
    <item>
      <title>MATCH CODE</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/match-code/m-p/2498402#M564390</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;     What is the use of Match code amd how can i create a mathch code. explain step by step.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thank you&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;ASHOK KUMAR&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 21 Jul 2007 07:21:19 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/match-code/m-p/2498402#M564390</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-07-21T07:21:19Z</dc:date>
    </item>
    <item>
      <title>Re: MATCH CODE</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/match-code/m-p/2498403#M564391</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Refer to these related threads&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="3548872"&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="3323794"&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="3089747"&gt;&lt;/A&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 21 Jul 2007 07:23:39 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/match-code/m-p/2498403#M564391</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-07-21T07:23:39Z</dc:date>
    </item>
    <item>
      <title>Re: MATCH CODE</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/match-code/m-p/2498404#M564392</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;Macro Choosefields (&amp;amp;Fieldname [Choose)... [Copy EndMacro&lt;/P&gt;&lt;P&gt;/SE11 "ABAP Data Dictionary&lt;/P&gt;&lt;P&gt;&amp;lt;Object name "the name of the Match Code Object&lt;/P&gt;&lt;P&gt;*Matchcode objects&lt;/P&gt;&lt;P&gt;[Create &amp;gt;&amp;lt;Short Text &amp;gt;&amp;lt;Primary Table &lt;/P&gt;&lt;P&gt;[Tables&lt;/P&gt;&lt;P&gt;[Yes "Save before terminating Editing?&lt;/P&gt;&lt;P&gt;&amp;gt;&amp;lt;Development Class [Save&lt;/P&gt;&lt;P&gt;[Choose Sec. Tab. "presents candidate list&lt;/P&gt;&lt;P&gt;(&amp;amp;Tablename [Choose)... [Copy&lt;/P&gt;&lt;P&gt;[Fields &lt;/P&gt;&lt;P&gt;[Yes "Save before terminating Editing?&lt;/P&gt;&lt;P&gt;[Enter &lt;/P&gt;&lt;P&gt;(&amp;amp;Tablename [Choose Fields #Choosefields)..&lt;/P&gt;&lt;P&gt;[Save [Back [Activate&lt;/P&gt;&lt;P&gt;"Match Code Object is now created and activated.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Matchcodes are an SAP technique to help users find information, normally in&lt;/P&gt;&lt;P&gt;connection with the F4 key on an input field. Information from one or more &lt;/P&gt;&lt;P&gt;tables can be combined and queried on using various search criteria: for &lt;/P&gt;&lt;P&gt;example, all companies whose name starts with "TATA" and whose location is&lt;/P&gt;&lt;P&gt;"INDIA."&lt;/P&gt;&lt;P&gt;Traditionally, matchcodes were implemented as redundant collections of data &lt;/P&gt;&lt;P&gt;in pool tables, as illustrated in the following:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Company header table Company detail table Matchcode pool table&lt;/P&gt;&lt;P&gt;(TAB1) (TAB2) (M_POOL)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The advantage of the old pool matchcodes was a quick and easy search, as &lt;/P&gt;&lt;P&gt;long as the significant fields were entered by the end user (in this case, &lt;/P&gt;&lt;P&gt;company name and location). The disadvantage was that for every change in &lt;/P&gt;&lt;P&gt;the master tables, the system had to make redundant updates in the matchcode&lt;/P&gt;&lt;P&gt;tables. In addition, it was impossible to search in a pool matchcode for any&lt;/P&gt;&lt;P&gt;but the significant fields, i.e., it would have been very CPU intensive to&lt;/P&gt;&lt;P&gt;search for all companies in San Francisco.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;This limitation led to the creation of matchcodes (more precisely, in SAP &lt;/P&gt;&lt;P&gt;terms, "matchcode IDs") for every possible query you could expect from end&lt;/P&gt;&lt;P&gt;users (one with company name as the significant field, one with location,&lt;/P&gt;&lt;P&gt;yet another with customer number, and so on). Customers with a very high &lt;/P&gt;&lt;P&gt;number of debitors, for example, soon found that their pool matchcode tables &lt;/P&gt;&lt;P&gt;grew to unmanageable sizes.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;As of release 2.1, it is now possible to define so-called transparent or&lt;/P&gt;&lt;P&gt;view matchcodes. Transparent matchcodes are implemented by defining a&lt;/P&gt;&lt;P&gt;database view for the information that should be queried. Database views are&lt;/P&gt;&lt;P&gt;not redundant containers of data, but are merely definitions of paths to&lt;/P&gt;&lt;P&gt;obtaining that data. In the example:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Company header table Company detail table Database view:&lt;/P&gt;&lt;P&gt;(TAB1) (TAB2) (M_VIEW)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The advantage of this new technique is that it is no longer necessary to &lt;/P&gt;&lt;P&gt;maintain redundant matchcode data: a view takes only a small amount of &lt;/P&gt;&lt;P&gt;database dictionary space. Using this technique, the query is converted by &lt;/P&gt;&lt;P&gt;the database to a query against the original tables, so it becomes very &lt;/P&gt;&lt;P&gt;important that access be supported by the proper indexes.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;lt;u&amp;gt;&amp;lt;b&amp;gt;CHECK THIS LINK&amp;lt;/b&amp;gt;&amp;lt;/u&amp;gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://help.sap.com/saphelp_40b/helpdata/en/cf/21ef46446011d189700000e8322d00/content.htm" target="test_blank"&gt;http://help.sap.com/saphelp_40b/helpdata/en/cf/21ef46446011d189700000e8322d00/content.htm&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://web.mit.edu/sapr3/docs/webdocs/dontindex/pdf/mcqc.pdf" target="test_blank"&gt;http://web.mit.edu/sapr3/docs/webdocs/dontindex/pdf/mcqc.pdf&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Reward if helpfull&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;Pavan&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Message was edited by: &lt;/P&gt;&lt;P&gt;        Pavan praveen&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 21 Jul 2007 07:26:10 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/match-code/m-p/2498404#M564392</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-07-21T07:26:10Z</dc:date>
    </item>
    <item>
      <title>Re: MATCH CODE</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/match-code/m-p/2498405#M564393</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;    Hi,&lt;/P&gt;&lt;P&gt;Match code is nothing but the Search help in Higher versions&lt;/P&gt;&lt;P&gt;It is same way from SE11 you have to create.&lt;/P&gt;&lt;P&gt;so from SE11 create it and use it.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Matchcode objects are being replaced by search helps. This is good as search helps are easy to create. However, it has caused some confusion on how best to add search helps to a selection field.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The trick that I found is to keep your newly created search helps to a 4-character name. The Matchcode object name has this old 4-character limit. This trick is not documented anywhere in the system but it has been a great time saver for me. You can expand this concept by finding existing SAP search helps that are more than 4-characters, copy them to a 4-character name and presto, you have a new matchcode object available for use&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Check this thread to get detailed info&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="3005534"&gt;&lt;/A&gt;&lt;/P&gt;&lt;P&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="3089747"&gt;&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;lt;b&amp;gt;Reward points&amp;lt;/b&amp;gt;&lt;/P&gt;&lt;P&gt;Regrads&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 21 Jul 2007 07:27:33 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/match-code/m-p/2498405#M564393</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-07-21T07:27:33Z</dc:date>
    </item>
    <item>
      <title>Re: MATCH CODE</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/match-code/m-p/2498406#M564394</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Match Code is a tool to help us to search for data records in the system. Match codes are an efficient and user-friendly search aid where &amp;lt;u&amp;gt;&amp;lt;b&amp;gt;key of  a record is unknown.&amp;lt;/b&amp;gt;&amp;lt;/u&amp;gt;	&lt;/P&gt;&lt;P&gt;        A matchcode is a tool to search for data records in the system. Matchcodes are an efficient and user-friendly search aid for cases where the key of a record is unknown.&lt;/P&gt;&lt;P&gt;       It consists of two stages one is Match code object and the other is Matchcode ID.A matchcode object describes the set of all possible search paths for a search term.Matchcode ID describes a special search path for a search term.&lt;/P&gt;&lt;P&gt;maximum number of match code Id's that can be defined for one Match code object is 36.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 23 Jul 2007 05:41:00 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/match-code/m-p/2498406#M564394</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-07-23T05:41:00Z</dc:date>
    </item>
  </channel>
</rss>

