matchcode

[Former Member]

Hei,

By being in the search help of a transaction How can I get the name of the match code.

Plz help

[Former Member]

Hi

For many entry fields, but not all, SAP provides a search function called a Matchcode. Matchcodes allow you to select a value from a list or search for a value by categories of data if there are many possibilities.

Types of Matchcodes

Matchcodes fall into three basic categories:

1) Short list or hit list

The values are listed on one screen. For longer lists, you may need to scroll down to see all the values.

2) Restrict Value Range

Many entries are available for the field. A number of tabbed screens with different categories display so that you can enter your search criteria.

3) Calendar search

A calendar-type dialog box is displayed so that you can select day, month, and year. This is used in date fields such as invoice posting date.

Matchcodes were replaced with Search Helps starting with Release 4.0. Please use search helps to assign an input help to a field.

Existing matchcodes were automatically converted to search helps. A matchcode object is hereby converted to a collective search help with the same name. Each matchcode ID of the matchcode object is converted into an elementary search help with the same name and assigned to the collective search help created from the matchcode object.

A matchcode is a means of finding data records stored in the system. The matchcode is defined in the ABAP Dictionary in two steps:

You first define the relevant tables and fields for the search in a matchcode object. A matchcode object describes the set of all possible search paths for a search string.

You then create one or more matchcode IDs for a matchcode object. A matchcode ID describes a special search path for a search string. The matchcode ID defines the fields or field combinations to be used in the search.

[Former Member]

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.

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 matchcode

tables. In addition, it was impossible to search in a pool matchcode for any

but 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)

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.

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

Regards,

Pavan

[Former Member]

Hi , Would you mind to tell me ... Where can I Find all matchcodes for SAP FI, I have a lot of them non-updated thanks