Get Example source ABAP code based on a different SAP table
Operands in Character String and Byte String Processing ITOC
Operands in Character String Processing In character string processing, which is defined by the addition IN CHARACTER MODE in overloaded statements, and in statements that only support character string processing, the relevant operands must be character-like because the operands are processed by character and the storage of the characters in the memory depends on the code page used. This condition is vital to ensure that character string processing functions correctly. In ABAP_STANDARD , only data objects, return values, or results with the character-like data types c, n, and string, and the date/time types d and t, or structures with exclusively flat character-like components are allowed as character-like operands. Data objects with the types n, d, and t and structures with exclusively character-like components are handled like data objects with the type c.
Latest notes:
If the character-like data objects n, d, and t are used in character string processing, it must be noted that the type-compliant conversion rules do not apply to the assignment of interim results to target fields and instead the conversion rules for data type c apply.
No structures can be used as character-like operands in string expressions and string functions with named arguments. NON_V5_HINTS ABAP_HINT_END
Operands in Byte String Processing In byte string processing, which is triggered by the addition IN BYTE MODE in overloaded statements, and in the statements GET BIT and SET BIT, the relevant operands must be byte-like. This is because the operands are processed by byte.
