abap-matchcode id

[Former Member]

how to create matchcode ids

[Former Member]

Hi Naga,

F4 Help is used to give the Possible values for the Particular Field.

To create a F4 help,

Step1 : Go to Se11 and Select Search Help and Enter One Name and Click Create.

Step2 : Enter your Table name in 'Selection Method' Field.

Step3 : Enter the field Name and tick the Flags Imp and Exp and Type 1 and 2 in Lpos,

Spos fields.

Step4 : Save it and In se38 Write the Code Like This,

data Empname like Zemp-empname matchcode object [enter name that u Created].

Thanks.

Note : Reward If helpful.

[Former Member]

Hi,

Refer the Following Thread,

Hope it is Helpful.

Regards,

Padmam.

[Former Member]

HI

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

Reward if helpfull

Regards

Pavan

Message was edited by:

pavan praveen