Hierarchy
SAP_BASIS (Software Component) SAP Basis Component⤷
BC-DWB-DIC-AC (Application Component) Activation Program, Conversion Program, DB Utility, MC, SPDD⤷
SDDX (Package) Structures and tables old info system
Basic Data
| Data Element | DIP2001 |
| Short Description | Matchcode object name |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | SELPAR | |
| Data Type | CHAR | Character String |
| Length | 30 | |
| Decimal Places | 0 | |
| Output Length | 30 | |
| Value Table |
Further Characteristics
| Search Help: Name | ||
| Search Help: Parameters | ||
| Parameter ID | ||
| Default Component name | ||
| Change document | ||
| No Input History | ||
| Basic direction is set to LTR | ||
| No BIDI Filtering |
Field Label
| Length | Field Label | |
| Short | 10 | MC object |
| Medium | 20 | Matchcode object |
| Long | 20 | Matchcode object |
| Heading | 30 | MC object |
Documentation
Definition
Matchcodes are special SAP table views. You can create a matchcode in the following ways:
- temporary, that is the matchcode is constructued at the moment when it is accessed.
- physical, that is the matchcode is constructed physically in the SAP system
Use
If you do not know the key of an object, a matchcode can act as an efficient secondary access path. It aids your search in cases where the key of an object is needed in an input field, but only certain (non-key) fields of the object are known.
Use
Procedure
Enter the name of the matchcode object observing the following input conventions:
char
All characters (apart from those mentioned below) stand for themselves, with no distinction made between upper and lower case. Upper and lower case are distinguished in text fields, such as short descriptions.
*
denotes any character string.
+
denotes exactly one character.
<>
denotes negation (applies if the specified character string does not match).
$
tests for a blank field (entering <>$ means that the system searches for all fields containing at least one character).
>
greater than.
<
less than.
&
logical AND (intersection), followed by the next character string without blanks.
or/
logical OR (union), followed by the next character string without blanks.
Priority starts at the top, i.e. & is evaluated before , but after *.
Examples
Dependencies
History
| Last changed by/on | SAP | 19970314 |
| SAP Release Created in |
