ABAP Programming Error

Category :  ABAP Programming Error

Runtime Errors: READ_REPORT_LINE_TOO_LONG

Except.: CX_SY_READ_SRC_LINE_TOO_LONG

Detail explanation of the dump: 

The internal table "\FUNCTION=K_KKB_FIELDCAT_MERGE\DATA=L_ABAP_SOURCE[]" is 72 characters wide. The program line is 81 characters wide.                                 

               

Reason:

Function REUSE_ALV_FIELDCATALOG_MERGE dumps if the program contains lines longer than 72 characters, even if the lines are comment lines. 

Solution:

An easy remedy is to turn on the switch preventing lines to be longer than 72.

(Utilities -> settings. Tab-page “ABAP-Editor”, sub tab-page “Editor”, set a check mark in the field “Downwards-Comp. Line Lngth(72)”).

SAP- Handling Errors... 1.

1. Cannot activate a table in SAP
Syntax error in SDCC, table inconsistency between ABAP Dictionary and the database, transport error 8 during the generation of ABAP Dictionary. When you call Transaction SDCC, a termination occurs due to a putative syntax error because a table is not known or active. When you check this with the ABAP dictionary (SE11), you notice, that the table is active or inactive, however it is not possible to activate it. The activation might terminate with the error message 'Inconsistency between ABAP Dictionary and database'. A check of the affected object also delivers this error.
Solution
Proceed as follows:
• Log on as user DDIC
• Call Transaction SE14
• Enter the affected table name and
• select EDIT
• In the following screen, choose Table -> Reconstruct
• Confirm the execution
• Call Transaction SE11
• Enter the affected table name
• Display
• Activate
If - after you chose EDIT -, the error message occurs that the table only exists on the database, you need to activate the source and the runtime object.
• Call Transaction SE37:
-> Function module 'DD_TABL_ACTM' -> Single test
• Under import parameter MODE, enter the number 12 and under TABNAME the corresponding table name
• -> Execute (F8) -> Export parameter ACT_RESULT must be 0
• Call Transaction SE14 again as described above.
• -> Extras -> Database object -> Check,
as well as
-> Extras -> Runtime object -> Check
inconsistencies should no longer be contained.
If you cannot switch to the EDIT mode in Transaction SE14, which means no modifications are allowed in the customer system, then proceed as follows:
• Call function module 'DD_TABL_ACTM' as described above.
• Then call Transaction SE14 again and verify that the table has been activated.
• As a result, this ensures that the SDCC can be executed.
• The menu options in Transaction SE14 are
-> Extras -> Database object -> Check,
as well as
-> Extras -> Runtime object -> Check
inconsistencies should no longer be contained.
• If this is not the case, open a CSN message under the BC-DWB-DIC-ED component.