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 | DIP2308 |
| Short Description | Type of matchcode analysis |
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 | Update |
| Medium | 15 | Update |
| Long | 20 | Update type |
| Heading | 30 | U |
Documentation
Definition
The update type classifies the matchcodes according to their type and how they are constructed.
If the data in one of the tables contained in a matchcode ID changes, the matchcode records have to be adjusted. The update type defines at what time this adjustment should take place. IDs with different update types can be selected for a matchcode object.
The following update types are currently supported:
- A (asynchronous matchcode structure)
- S (synchronous matchcode structure)
- P (program-controlled matchcode structure)
- I (transparent matchcodes with views and indexes)
- K (matchcode in classification system)
Matchcodes of update types A, S and P are also called physical matchcodes because the matchcode data is implemented here redundantly as its own table in the system.
Matchcodes of update types I and K, on the other hand, are called logical matchcodes because the matchcode records in this case are set up temporarily at the moment of the access to the matchcode.
Use
Procedure
Please observe 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 |
