0

I created a custom transaction code ZMB52 by copying the standard SAP transaction code MB52. In the program, I'm trying to add two custom push buttons to the ALV toolbar, but the buttons are not appearing when the ALV is displayed.

Here’s what I have done so far:

  1. Edit GUI Status 'STANDARD' in SAP GUI

    enter image description here

    I attempted to add new buttons or delete existing ones in the GUI Status.

    However, when I execute the program, the changes (additions or deletions) have no effect on the ALV toolbar.

    enter image description here

  2. I searched through the program for any specific code or form related to configuring this status, but the only relevant line I found was this:

    enter image description here

Despite editing the PF-STATUS or trying other approaches, I haven’t been able to make the new buttons appear.

Has anyone encountered a similar issue or knows how to resolve this?

Any guidance would be greatly appreciated as I’ve been stuck on this for a whole day.

Thank you!

EDIT: I realize something:

  • First, in the mb52 standard program, the GUI Status STANDARD wasn't called from any screen (the toolbar displayed is one set by default by SAP), that's why I try to change add or delete also not affect to the tool bar.
  • Second: the GUI Status must have to call by FM 'reuse_alv_.....' ==> this one in some standard program SAP they are using not a normal 'reuse_alv_grid_display', they are using 'alv_detail_func' ==> this one also has to debug to figure out.
Improve this question
2
  • (1) Copying a standard transaction code is not recommended (see the good reasons given by SAP in the note 213751 - Programs: Copying versus modification). Just do a change of the standard. (2) MB52 calls the function module 'reuse_alv_....' which you may customize to display your own GUI Status by passing the name of your own subroutine to the event PF_STATUS_SET in the parameter it_events (see the SAP documentation of 'reuse_alv_....') Commented Dec 27, 2024 at 14:17
  • Copying from a standard transaction code is generally not recommended. However, since it is a functional requirement from the client, I have no other choice in this case. Yes, this is correct, but the event PF_STATUS_SE must be debugged to figure it out. Commented Dec 28, 2024 at 14:30
Related questions
0
ABAP report toolbar is disabled
1
Why buttons added to a GUI Status are not visible or grayed out?
0
Set Parameter ID not working for custom screen
Load 5 more related questions Show fewer related questions

0

Reset to default

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.