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
: A newer, more streamlined "factory" model that is easier to code but less flexible for editing. Abap Alv Oops Interview Questions And Answers
2. How do you handle events like "Double Click" or "Hotspot Click" in OOP? Core Concepts of ALV OOP : A newer,
This is a common "gotcha" question. When a user types in an editable ALV, the backend internal table is not updated until the data is validated. Calling grid->check_changed_data manually triggers the validation and synchronizes the frontend grid with your backend internal table. 5. How do you refresh the ALV after data modification? This is a common "gotcha" question
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.
: The primary class for creating editable, interactive grids.
1. What is the fundamental difference between Functional ALV and OOP ALV?