Get Example source ABAP code based on a different SAP table
Assignments in ABAP Release 7.53 ITOC
ABAP_MODIFICATION_NN Convertibility of Structures> The conversion rules for flat structures > are based on their fragment views>, where each alignment gap> is considered as a fragment. Alignment gaps arise from the alignment> requirements of the component's data types. For character-like components, the alignment requirement depends on the character representation:
For character representation UCS-2 > used by the ABAP programming language, the memory address of character-like data objects must be divisible by 2.
For other character representations there are other alignment requirements. For example, the non-Unicode character representation ASCII > has no alignment requirement while the Unicode character representation UTF-32> requires a divisibility by 4. Before only Unicode systems> were supported, the conversion rules for structures had to take all possible alignment requirements for characters into account, regardless of the actual length of a character in its character representation. Meanwhile, only Unicode systems> are supported. The system codepage is UTF-16> and its subset UCS-2> is supported in ABAP language. Any character is represented by 2 bytes and the alignment requirement is always a divisibility by 2. Because of this, the conversion rules for flat structures can be less strict than before and the new determination of possible alignment gaps was introduced in ABAP_RELEASE 7.53. For example, the following assignment between two flat structures was not possible before ABAP_RELEASE 7.53 but is possible now. ABEXA 01442 In the included substructure incl1>, the character component has the same alignment as the integer component and there is no alignment gap. But as long as non-Unicode Systems were supported, an alignment gap had to be assumed behind the included structure in order to make the program executable in Unicode systems as well as in non-Unicode Systems.
Latest notes: When downporting programs from higher to lower releases, syntax errors might occur in the lower releases because of the stricter rules there. ABAP_HINT_END