ALV Reports Part 8: Toolbar Buttons, PF-STATUS and User Commands

📌 KEY POINTS
✅ REUSE_ALV: copy status STANDARD_FULLSCREEN (program SAPLKKBL) into your program, add buttons, set it in the FORM named in i_callback_pf_status_set.
✅ CL_GUI_ALV_GRID: add buttons in the TOOLBAR event handler and handle them in the USER_COMMAND event.
✅ Read the user's selection: rs_selfield / GET_SELECTED_ROWS, then refresh the display after changes.
⚠️ Always refresh after changing the output table, and check sy-subrc / authorization before mass actions.

━━━━━━━━━━━━━━━━━━━━
▶ WHERE WE ARE
Part 6 reacted to clicks on cells. Now users select rows and press your own buttons — e.g. "Release", "Send e-mail", "Recalculate".\n\n━━━━━━━━━━━━━━━━━━━━\n▶ 1. REUSE_ALV WITH OWN STATUS\n• SE41 (or SE80 → GUI status → copy): copy status STANDARD_FULLSCREEN from program SAPLKKBL to your report, name ZSTANDARD. It keeps all standard ALV functions.

• Add a button, e.g. function code REFRESH or RELEASE with icon and text.
• i_callback_pf_status_set = 'SET_PF_STATUS' → FORM set_pf_status USING rt_extab TYPE slis_t_extab. SET PF-STATUS 'ZSTANDARD' EXCLUDING rt_extab.
• i_callback_user_command = 'USER_COMMAND' → your codes arrive in r_ucomm.
• rs_selfield-refresh = 'X' tells the ALV to refresh after the callback.
• Selected rows: add a checkbox column or use layout box_fieldname (SLIS) with a SEL field.\n\n━━━━━━━━━━━━━━━━━━━━\n▶ 2. CL_GUI_ALV_GRID TOOLBAR EVENT\n• Handler FOR EVENT toolbar OF cl_gui_alv_grid IMPORTING e_object: APPEND a stb_button (function, icon, quickinfo, text) to e_object->mt_toolbar.
• Handler FOR EVENT user_command IMPORTING e_ucomm: CASE e_ucomm.
• go_grid->get_selected_rows( IMPORTING et_index_rows = lt_rows ) — needs sel_mode 'A' or 'D' in layout.
• go_grid->refresh_table_display( ) after changes.
• SET HANDLER before set_table_for_first_display so the toolbar event fires; or call go_grid->set_toolbar_interactive( ) afterwards.

━━━━━━━━━━━━━━━━━━━━
▶ 3. DESIGN OF ACTIONS

• Confirm destructive actions with POPUP_TO_CONFIRM.
• Process selected rows, collect messages, show them (e.g. in a message log or popup).
• Lock objects (ENQUEUE) before changes, COMMIT once at the end.

━━━━━━━━━━━━━━━━━━━━
▶ STEP BY STEP

1. Copy STANDARD_FULLSCREEN to your report as ZSTANDARD and add button REFRESH (and RELEASE).
2. Run the code example; select rows and press Release.
3. Check that the status column updates after the refresh.

✅ CHECKPOINT: users can select rows and trigger your actions from the ALV toolbar.

A credit control team released blocked orders one by one in VKM1. A custom ALV listed blocked orders with a "Release" button: users selected rows, confirmed, and the program called the release BAPI per order, collected messages and refreshed the grid.
In the first version, the grid was not refreshed and users pressed Release twice, triggering duplicate processing errors. Adding the refresh and a status column that showed "Released" solved it.

• Creating a new PF-STATUS from scratch and losing standard ALV functions.
• Forgetting EXCLUDING rt_extab.
• Not refreshing the grid after changing data.
• get_selected_rows without a selection mode in the layout.
• Mass actions without confirmation, locking or message collection.

• Copy STANDARD_FULLSCREEN and add your functions.
• Confirm destructive actions.
• Lock, process, collect messages and commit once.
• Refresh with stable scroll position.
• Keep action logic in separate routines or classes.

Questions: "How do you add a custom button to an ALV?", "How do you get selected rows?", "Which events are used in CL_GUI_ALV_GRID?"
Strong answer: REUSE_ALV — copy STANDARD_FULLSCREEN from SAPLKKBL, set it in i_callback_pf_status_set FORM, handle r_ucomm in user_command, rs_selfield-refresh; OO — TOOLBAR event to add stb_button to e_object->mt_toolbar, USER_COMMAND event with e_ucomm, get_selected_rows with sel_mode, refresh_table_display.