Answers | Abap Alv Oops Interview Questions And

The CL_SALV_TABLE class is often preferred for simple, read-only displays. It uses a "Factory" pattern ( cl_salv_table=>factory ). It is much faster to implement because it doesn't require a screen or container definition, but it is intentionally limited—it does not support cell-level editing without significant workarounds. Summary Table: Key Classes Class Name CL_GUI_CUSTOM_CONTAINER Binds the ALV to a specific area on a GUI screen. CL_GUI_ALV_GRID The engine that renders and manages the grid data. LVC_S_FCAT Structure for defining column attributes (Field Catalog). LVC_S_LAYO Structure for defining overall grid appearance (Layout).

: The primary class for creating editable, interactive grids.

At the heart of ALV OOP is the separation of the data container and the display container. Unlike functional ALV, where the system handles the screen logic, OOP ALV requires a custom container ( CL_GUI_CUSTOM_CONTAINER ) or a docking container to sit on a screen (Dynpro). Abap Alv Oops Interview Questions And Answers

: A newer, more streamlined "factory" model that is easier to code but less flexible for editing.

1. What is the fundamental difference between Functional ALV and OOP ALV? The CL_SALV_TABLE class is often preferred for simple,

: When the user clicks, the system automatically calls your method. 3. How do you make specific cells or rows editable?

ABAP ALV (ABAP List Viewer) using Object-Oriented Programming (OOP) is a cornerstone of modern SAP development. Moving away from function modules like REUSE_ALV_GRID_DISPLAY , the OOP approach leverages the CL_GUI_ALV_GRID class or the newer SALV (SAP List Viewer) model. Understanding this shift is essential for any senior ABAP developer. Core Concepts of ALV OOP Unlike functional ALV

To enable editing, you must modify the Field Catalog ( LVC_S_FCAT ). Set the EDIT field to 'X' for the desired column. Use the method set_ready_for_input on the grid instance.