Runtime Error

Symptom

A structure or a table with includes
is aligned incorrectly to length 2 in the first field of an include. When you use the downward-compatible kernel 7.20 (or higher), short dumps occur when you use this type in ABAP programs (for example, short dump DDIC_TYPELENG_INCONSISTENT).

Other Terms

Alignment, SM66

Reason and Prerequisites

Note 1222907 corrected an error during the calculation of the alignment of includes: Under certain circumstances, a structure without alignment requirements was aligned to an even runtime offset. This was not required.
All of the types that were activated after the implementation of Note 1222907 no longer indicate the error. However, there may still be tables or structures that were activated before the note was implemented and that still indicate an error as a result.
This note provides the report RUT_NOTE_1610716 that finds only these objects and activates them.

Solution

This SAP Note delivers the report RUT_NOTE_1610716. This report detects and corrects the inconsistencies mentioned above. This is aone-time cleanupfor each system. Once a system is cleaned up, it will remain cleaned up even when further changes are made (for example, when transports are imported).
This report is kernel-independent. On the one hand, this means that you do not need to apply kernel 7.20 in order to be able to execute this report. On the other hand, inconsistencies may also exist if a different kernel version is used.

1. Implement this note or import the relevant Support Package. Make sure that you are using the

of this note.

2. Make sure that

is active in the system.

3. In general, we recommend that you configure the nametab buffer in accordance with Note 1398802.

4. Execute the report

in test mode

. This means that the 'Check' selection field (technical name PCHECK)

should be selected during the first run (this is also the default setting). The runtime of the report is a few minutes. There should usually be none or very few incorrect types (it is not unusual to have approximately 20 errors). If the check run finds more than 1000 errors, you should open a message under the component BC-DWB-DIC-AC.

5. The results of the check run are displayed as a list. In addition, you can use the report RADPROTA to evaluate the log. To do this, execute the report RADPROTA, enter the log name NOTE1610716* and press F8 to execute. Select the most recent log from the overview list by double-clicking.

              Example log 1 : Result of a check run with objects to be corrected

Program parameters:
Task.....................: Check and correct nametab alignment
PCHECK...................: X
REPAIR...................: space
=======================================================================
ADBOS_ECP_S_GUI_KIS1_EXT: Include EXTENDED_VALUES has wrong alignment.
SWNCAGGEXTSYSTEM: Include .INCLUDE_2 has wrong alignment.
SWNCAGGTASKTIMES: Include .INCLUDE_1 has wrong alignment.
SWNCAGGTASKTYPE: Include .INCLUDE_4 has wrong alignment.
SWNCAGGTCDET: Include .INCLUDE_1 has wrong alignment.
SWNCAGGUSERTCODE: Include .INCLUDE_2 has wrong alignment.
SWNCGLAGGEXTSYSTEM: Include .INCLUDE_2 has wrong alignment.
SWNCGLAGGTASKTIMES: Include .INCLUDE_1 has wrong alignment.
SWNCGLAGGTASKTYPE: Include .INCLUDE_4 has wrong alignment.
SWNCGLAGGTCDET: Include .INCLUDE_1 has wrong alignment.
SWNCGLAGGUSERTCODE: Include .INCLUDE_2 has wrong alignment.
SWNCGLHITLIST: Include .INCLUDE_1 has wrong alignment.
SWNCHITLIST: Include .INCLUDE_1 has wrong alignment.
SWNCSYSLOAD: Include .INCLUDE_5 has wrong alignment.
Summary of the checks:
328020 types checked.
14 errors found.
Date, time...............: 22.07.2011, 17:50:14
Program end============================================================
              Example log 2 : Result of a check run without errors

Program parameters:
Task.....................: Check and correct nametab alignment
PCHECK...................: X
REPAIR...................: space
=======================================================================
Summary of the checks:
48108 types checked.
No errors found.
Date, time...............: 28.07.2011, 16:30:50
Program end============================================================

6.

(technical name REPAIR)

All of the types are checked during each run. During the update run, incorrect types that are found are also activated using ABAP Dictionary mass activation and are then checked again afterwards. Usually, the end of the log of the update run should look as follows:

=======================================================================
All inconsistencies repaired.
Return code..............: 0
Date, time...............: 22.07.2011, 17:22:14
Program end===========================================================

              If there are still errors in the log, open a message under the component BC-DWB-DIC-AC.

------------------------------------------------------------------------
|Manual Post-Implement.                                                |
------------------------------------------------------------------------
|VALID FOR                                                             |
|Software Component   SAP_BASIS                      SAP Basis compo...|
| Release 620          Until SAPKB62073                                |
| Release 640          Until SAPKB64031                                |
| Release 700          SAPKB70004 - SAPKB70025                         |
| Release 710          Until SAPKB71012                                |
| Release 711          SAPKB71101 - SAPKB71107                         |
| Release 701          Until SAPKB70110                                |
| Release 702          SAPKB70201 - SAPKB70209                         |
| Release 730          SAPKB73001 - SAPKB73004                         |
| Release 720          SAPKB72002 - SAPKB72005                         |
------------------------------------------------------------------------

In the original language English, the report uses the following text symbols and selection texts:

Text symbols (Symbol name, text, maximum length):
AI1  Start of mass activation of types with wrong alignment:  80
AS1  End of mass activation.                                  80
DS0  There are still inconsistent objects.                    80
DS1  Make sure that note 1222907 is applied.                  80
DS3  All inconsistencies repaired.                            80
E01  &: Include & has wrong alignment.                       80
E02  &: Internal error & occurred                             80
ET0  &: Type touched.                                        80
H01  Check and correct nametab alignment                      80
H02  Task                                                    20
LN0  &: & <> &, no touch needed.                             80
S00  Summary of the checks:                                  80
S01  & types checked.                                        80
S02  No errors found.                                        80
S03  One error found.                                        80
S04  & errors found.                                          80
S05  There was at least one internal error.                   80
S06  There were more than & errors.                          80
S07  Please contact SAP by opening a message on component
     BC-DWB-DIC-AC.                                          80
ST0  &: Starting invalidation of type user loads (touch).     80

Selection texts (parameter, text):
PCHECK Check
REPAIR Check and repair