Abap Alv Oops Interview Questions And Answers 〈2024-2026〉

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).

1. What is the fundamental difference between Functional ALV and OOP ALV?

Events in OOP ALV are handled by creating a local controller class. Abap Alv Oops Interview Questions And Answers

: Create a class with a method FOR EVENT double_click OF cl_gui_alv_grid .

: The physical area on a screen where the grid is rendered. Critical Interview Questions and Insights At the heart of ALV OOP is the

Functional ALV relies on passing parameters to a function module. OOP ALV is instance-based. In OOP, you instantiate a container and then an ALV object within that container. This allows for multiple ALV grids on a single screen and finer control over event handling using methods instead of form routines.

: When the user clicks, the system automatically calls your method. 3. How do you make specific cells or rows editable? What is the fundamental difference between Functional ALV

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).