READ_BAD_KEY_ALIGN abap dump

[Former Member]

Hi Guys,

after upgrading 720 kernel am getting abap dump as READ_BAD_KEY_ALIGN in st22.

solution pls.

DVKumar

[anandkarthik_raja · Accepted solution]

Hi,

Please download and apply the below notes using transaction SNOTE:

NOTE 1138346 - Runtime Error when creating a billing document 1/2
NOTE 1267192 - Runtime Error when creating a billing document 2/2

If this do not help, please also run the report mentioned in note
1610716!

[Former Member · Accepted solution]

Hi, 

i also got same issues after upgrading the kernel from 700 to 721,

i gone through the below steps and my issue has been resolved ,

after kernel upgrade i was getting dumps when i run the Tcodes  SM66, St03, ST02

Inconsistency in length of DDIC data type "SWNCGLAGGTASKTYPE".

then i applied the Note "  1610716 - Correcting runtime objects with the wrong alignmen    

after applying the Note i have executed the Report : RUT_NOTE_1610716  though SE38  with Option

PCHECK  try to run in Background,

then re-run the report with REPAIR

After Repair all Tcode are working fine,    but again i am getting dumps " READ_BAD_KEY_ALIGN " with Functional  then i have applied the below 2 Notes  after that my issues has been resolved.

1138346 - Runtime Error when creating a billing document 1/2

1267192 - Runtime Error when creating a billing document 2/2

Regards

Ravi

[jorge_velasquez]

Hi,

The issue can be solved by implementing note 1877172 - Shortdump READ_BAD_KEY_ALIGN when using VF01, VF02 or VF03

Regards.

[JPReyes]

Can you post the full short dump?

Also, notice that theres only one note (split in two) in SMP about this so read it.

Regards, Juam