34 Interactive classical reports

In SAP ABAP, an Interactive Classical Report allows users to interact with a "Basic List" (the first output screen) to trigger "Secondary Lists" (subsequent detailed screens). While a standard classical report is a single static list, an interactive report can maintain one basic list and up to 20 secondary lists. Key Interactive Events ---------------------- These events allow the program to react to user actions: AT LINE-SELECTION: Triggered when a user double-clicks a line or presses the F2 key. AT USER-COMMAND: Occurs when a user clicks a button or menu item in a custom GUI Status (transaction SE41). TOP-OF-PAGE DURING LINE-SELECTION: Used to define a specific header for secondary lists, as the standard TOP-OF-PAGE event only applies to the basic list. Core Commands & System Fields ----------------------------- HIDE field: This statement is critical for passing data between lists. It stores the value of a field from the currently selected line into a system buffer so it can be retrieved during the AT LINE-SELECTION event. SY-LSIND: A system field that stores the index of the current list level (Basic list = 0, first secondary list = 1, etc.). SY-UCOMM: Stores the function code of the user command (e.g., 'BACK', 'EXIT', or custom button IDs). GET CURSOR: Used to identify the exact field or position the user clicked on the screen. Implementation Workflow Selection Screen: Define user input parameters (e.g., SELECT-OPTIONS). Basic List: Fetch and display summary data using START-OF-SELECTION. Use HIDE on key fields (like EBELN or MATNR) during the WRITE loop. Interaction: Implement AT LINE-SELECTION to read the hidden values and fetch detailed data for the secondary list. Formatting: Use TOP-OF-PAGE DURING LINE-SELECTION to keep users oriented as they drill down into data.