ASSIGN_BASE_WRONG_ALIGNMENT is an ABAP runtime error which you may come across when using or developing within an SAP system. See below for the standard details explaining what it means and how you can avoid or fix this runtime error.
Short Dump Classification: A - ABAP Programming Error
You can view further information about a runtme error by using transaction code ST22 which will show you this and all runtime erros that have happen in your SAP system.
Also check out the Comments section below to view or add related contributions and example screen shots.
You might be able to avoid the error by using a different offset.
The following must apply: Offset = n * <runtime parameter>, n >= 0
Please see abap error for more details about the possible cause of this runtime error and how it could be avoided.
Please see search hints for more details about the possible cause of this runtime error and how it could be avoided.
Please see send to sap for more details about the possible cause of this runtime error and how it could be avoided.
Error in ASSIGN assignment in program <runtime parameter>.
Please see abap error for more details about the possible cause of this runtime error and how it could be avoided.
In the current program <runtime parameter>, an error occurred when setting the field
symbol <runtime parameter> with ASSIGN or ASSIGNING (maybe in the combination with the
CASTING addition).
When converting the base entry of field symbol <runtime parameter> (number in base
table: <runtime parameter>), the system detected that the target type requires memory
alignment <runtime parameter>.
The source data object has an invalid memory alignment however, as it
is not divisible by <runtime parameter>.
If you want to assign a subfield of a structure to a field symbol for
example, the offset from the start of the structure should be a
multiple of <runtime parameter>. The structure should also contain a type that has at
least the alignment <runtime parameter>.
Please see abap error for more details about the possible cause of this runtime error and how it could be avoided.