Matchcode

[Former Member]

Hello friends,

What is the specific use of matchcode in search help compared to if we give only name of the field?

Regards

Ashish

[Former Member]

Hi,

Check the Following Link.

[MATCH CODE |http://help.sap.com/saphelp_40b/helpdata/en/cf/21ef7a446011d189700000e8322d00/content.htm]

Note Match object is Not supported in SAP ECC 6.0.

Match code Creates Pooled Table in Background.

Alternate is Search Helps .

Search Helps

[Search Helps |http://help.sap.com/saphelp_nw04/helpdata/en/cf/21ee2b446011d189700000e8322d00/content.htm]

Regards,

Balakumar.G

Reward Points if helpful.

[Former Member]

hi,

refer to the link

http://help.sap.com/saphelp_40b/helpdata/en/cf/21ef1f446011d189700000e8322d00/content.htm

http://help.sap.com/saphelp_40b/helpdata/en/cf/21ef1f446011d189700000e8322d00/content.htm

regards,

sreelakshmi

[Former Member]

hi,

refer to the thread

regards,

sreelakshmi

[dhruv_shah3]

HI,

Use [http://help.sap.com/saphelp_nw04s/helpdata/en/41/f6b237fec48c67e10000009b38f8cf/frameset.htm]

[;

HTH

Regards,

Dhruv Shah

[Former Member]

Matchcodes are an SAP technique to help users find information, normally in connection with the F4 key on an input field. Information from one or more tables can be combined and queried on using various search criteria: for example, all companies whose name starts with "TATA" and whose location is"INDIA."

Traditionally, matchcodes were implemented as redundant collections of data in pool tables, as illustrated in the following:

Company header table Company detail table Matchcode pool table (TAB1) (TAB2) (M_POOL)

The advantage of the old pool matchcodes was a quick and easy search, as long as the significant fields were entered by the end user (in this case, company name and location). The disadvantage was that for every change in the master tables, the system had to make redundant updates in the matchcodetables. In addition, it was impossible to search in a pool matchcode for anybut the significant fields, i.e., it would have been very CPU intensive to search for all companies in San Francisco.

This limitation led to the creation of matchcodes (more precisely, in SAP terms, "matchcode IDs") for every possible query you could expect from end users (one with company name as the significant field, one with location, yet another with customer number, and so on). Customers with a very high number of debitors, for example, soon found that their pool matchcode tables

grew to unmanageable sizes.

As of release 2.1, it is now possible to define so-called transparent or view matchcodes. Transparent matchcodes are implemented by defining a database view for the information that should be queried. Database views are not redundant containers of data, but are merely definitions of paths to obtaining that data. In the example:

Company header table Company detail table Database view:

(TAB1) (TAB2) (M_VIEW)

Advantage

The advantage of this new technique is that it is no longer necessary to maintain redundant matchcode data: a view takes only a small amount of database dictionary space. Using this technique, the query is converted by the database to a query against the original tables, so it becomes very important that access be supported by the proper indexes.

How to create

Macro Choosefields (&Fieldname [Choose)... [Copy EndMacro

/SE11 "ABAP Data Dictionary

<Object name "the name of the Match Code Object

*Matchcode objects

[Create ><Short Text ><Primary Table

[Tables

[Yes "Save before terminating Editing?

<Development Class [Save

[Choose Sec. Tab. "presents candidate list

(&Tablename [Choose)... [Copy

[Fields

[Yes "Save before terminating Editing?

[Enter

(&Tablename [Choose Fields #Choosefields)..

[Save [Back [Activate

"Match Code Object is now created and activated.

CHECK THIS LINK

http://help.sap.com/saphelp_40b/helpdata/en/cf/21ef46446011d189700000e8322d00/content.htm

http://web.mit.edu/sapr3/docs/webdocs/dontindex/pdf/mcqc.pdf

Reward if useful