You are on page 1of 4

ALV - Consistency Check

Problem: Often for our ALV Programs output, we initially get a short dump or no data display or dump during sorting and rearrangement of columns. These things generally results from wrong design of Field catalog, Layout or Sorting Tables. Trac ing the error and rectifying the code definitely ta es some good amount of efforts incase it!s a comple" ALV #eport. Solution: SAP pro$ides %uite a simple and con$enient way to trace out these errors and eases the tas debugging by pro$iding a detailed description of the errors and probable solutions. of

To use this, press S&'FT ( )*ouble #ight +lic , on any empty section of the ALV output screen of the #eport as shown below in the output of the sample #eport-

The below SAP standard analysis screen opens up. This screen gi$es a detailed technical report of the ALV .rid control used in the #eport program.

below table shows how ' ha$e build my layout in the program. This can be $erified from the code also as shown below- . The short description of these errors is a$ailable along with a long description of selected errors. Sort etc. 0hen the buttons for Fcat or Layout are clic ed abo$e. For e"ample. Example sample: The e"ample here displays / errors in the #eport program in the initial display.'t has different tabs for Field+atalog. Also it displays in tabular format the detailed design of the Fcat. Layout and other tables used to build up the ALV display. Layout. indi$idual errors are displayed then. This screen basically shows a summary of errors initially. which when clic ed gi$es indi$idual analysis report.

Since it points out that field PLA7T has a wrong $alue which means that the declaration of PLA7T in the main 'nternal table. we find- 0e change 302#4S! to 02#4S5*!. Acti$ate and run the #eport and submit for analysis by using S&'FT(*ouble #ight clic . The PLA7T field is declared with a wrong *ata Type 302#4S! in the Table. where $alues of PLA7T are stored. 't should be 302#4S5*!. might be wrong. 6elow is the result. The errors got reduced to 1. which basically doesn!t e"ist in the *ata *ictionary. 0hen we loo into the Fcat code in the program. 0e loo into the declaration part of the 'nternal table. Let us loo into the 1nd displayed error- From the error description it is %uite e$ident that we ha$e used a *ata 2lement in the Fcat. .Correction of errors: This analysis report helps us to easily correct any ind of errors as done below.

.Correction of Error: 6efore change- After change Acti$ate and run the #eport and submit for analysis again. This is what we get as the analysis result now- Apart from this a lot of other information can be collected from this SAP standard analysis result. 0e can declare the ALV .rid error free only if no inconsistencies are found in this result. &ence we can conclude that this is %uite a handy tool for analy8ing the consistency of our ALV report generated.