2008 May 21 8:20 AM
Hi all,
Has any one converted MATCHCODES to SERCHHELPS where the existing match codes have u201Cpooled tablesu201D instead of transparent tables. My requirement is to delete all the existing match code and replace them with search helps .The issue is that when I delete a match code then itu2019s pooled table also get deleted and hence the pooled table cannot be used as SELECTION METHOD of SEARCH HELP I am also not able to create a view which I can provide as SELECTION METHOD of SEARCH HELP as all the table are pooled tables .There is a sapnote (24860) which lists the method to carry out conversion but here the prerequisite is that the tables should be transparent table so this sapnote is not applicable in my case.
Hi all,
Has any one converted MATCHCODES to SERCHHELPS where the existing match codes have u201Cpooled tablesu201D instead of transparent tables. My requirement is to delete all the existing match code and replace them with search helps .The issue is that when I delete a match code then itu2019s pooled table also get deleted and hence the pooled table cannot be used as SELECTION METHOD of SEARCH HELP I am also not able to create a view which I can provide as SELECTION METHOD of SEARCH HELP as all the table are pooled tables .There is a sapnote (24860) which lists the method to carry out conversion but here the prerequisite is that the tables should be transparent table so this sapnote is not applicable in my case.
2008 May 21 8:29 AM
Hi,
Matchcodes
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.
A material number is to be entered in a screen field. Since the user cannot be expected to know this number, it must be possible to search for this number using the attributes of the corresponding material.
Several search paths are possible for this search. For example, you can search for the material number with the material name, the material class or the material manufacturer.
The corresponding matchcode object then comprises the fields for the material number, material name, material class and manufacturer. One matchcode ID corresponds to each search path. For example, ID A could describe the search for the material number by manufacturer. This ID only contains the fields for the material number and manufacturer.
Matchcode Object
The tables relevant for the search are included in a matchcode object. The table selection is based on one primary table. Further secondary tables can also be included, which are linked with the primary table by foreign keys. The fields of the matchcode object can then be selected from the Basis tables.
A matchcode object is not stored physically. It only describes a complete logical view on one or more tables.
Matchcode IDs
Several matchcode IDs can be created for one matchcode object. The matchcode IDs are derived from the matchcode object by projection (field selection) and selection (definition of a selection condition).
A matchcode ID must be identified within a matchcode object with one letter or digit. This means that a maximum of 36 matchcode IDs (26 letters and 10 digits) can be defined for each matchcode object.
Selection conditions can be defined for each matchcode ID. These are used as a filter for the matchcode to be built. These selection conditions can define restrictions for all the fields from the Basis tables of the relevant matchcode ID.
You can also define an Update Type. The update type defines how the data should be accessed and how the matchcode adjusts to data changes in the tables contained in the matchcode.
2008 May 21 8:39 AM
Hi jagdish,
Do you mean that all Z matchcodes also were converted to corresponding serchhelps. i cant see serchhelps for many Zmatchcodes in my client system. secondly if in my system i have both matchcode and sechhelp with same name how do i ensure that serchhelp is called(at program level) and not matchcode.
| User | Count |
|---|---|
| 3 | |
| 2 | |
| 2 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 |