Hierarchy
SAP_BASIS (Software Component) SAP Basis Component⤷
BC-I18 (Application Component) Internationalization (I18N)⤷
SCP (Package) SAP Code Pages
Basic Data
| Data Element | DBSABYTES |
| Short Description | General Bytes for I18N_SEARCH |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | DBSOTEXT | |
| Data Type | CHAR | Character String |
| Length | 40 | |
| Decimal Places | 0 | |
| Output Length | 40 | |
| 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 | Bytes |
| Medium | 15 | Bytes |
| Long | 20 | Bytes |
| Heading | 40 | Bytes |
Documentation
Definition
You can search for arbitrary bytes or byte sequences by using this option. The input is interpreted as byte(s) or as byte pattern. Bytes must be entered in hexadecimal notation.
Note: The search and the replacement of bytes in systems using an MDMP or blended code page configuration is dangerous because bytes are ambiguous in these systems, i.e. they represent different characters depending on the logon language.
Internally the search is mapped to the ABAP statement <text> in <sel_opt>, where <text> is the hexadecimal representation of the content of a character like field and <sel_opt> are the selection options given by the user. All bytes are found in <text> up to the maximum length of 65535 bytes.
Use
Dependencies
Example
- Search for byte patterns
Input is
*616263*: Find all table fields which contain the byte pattern 0x616263.Input is
61*: Find all table fields which start with byte 0x61. - Search for bytes
Input is
616263: Find all table fields for which the complete content is 0x616263
History
| Last changed by/on | SAP | 20051219 |
| SAP Release Created in |
