Setting a PF status using ALV oops concept

[former_member353794]

Hi All,

I am trying to build a grid display using OOPs concept. I am facing a problem to set the PF status. I copied a standard PF status STANDARD_FULLSCREEN from the standard program SAPLSLVC_FULLSCREEN into my program PF status 'ZSTATUS'. Using the CL_GUI_ALV_GRID->set_table_for_first_display, I have displayed the ALV grid. But in the final output I can see that the grid container has a PF status by default just above the grid display and this status works fine. The PF status I created: ZSTATUS is also seen in the application toolbar. But this status does not do any standard functionality. For example: If we display the ALV grid using REUSE_ALV_GRID_DISPLAY function module and pass this PF status ZSTATUS, then we do not have to explicitly code for the user commands as it takes care of all the functionalities (like pressing the back button or exit button). Everything is taken care of without being coded for in our custom program. Do we have the same provision in ALV concept where the PF status behaves appropriately without coding for it in the PAI module?

[former_member353794]

Hi All,

I am trying to build a grid display using OOPs concept. I am facing a problem to set the PF status. I copied a standard PF status STANDARD_FULLSCREEN from the standard program SAPLSLVC_FULLSCREEN into my program PF status 'ZSTATUS'. Using the CL_GUI_ALV_GRID->set_table_for_first_display, I have displayed the ALV grid. But in the final output I can see that the grid container has a PF status by default just above the grid display and this status works fine. The PF status I created: ZSTATUS is also seen in the application toolbar. But this status does not do any standard functionality. For example: If we display the ALV grid using REUSE_ALV_GRID_DISPLAY function module and pass this PF status ZSTATUS, then we do not have to explicitly code for the user commands as it takes care of all the functionalities (like pressing the back button or exit button). Everything is taken care of without being coded for in our custom program. Do we have the same provision in ALV concept where the PF status behaves appropriately without coding for it in the PAI module?

[Former Member]

Hi Jean,

Please refer to the below link .....

http://wiki.sdn.sap.com/wiki/display/Snippets/ALV-Editing+and+saving+the+edited+values+in+Database%2...

Hope his will help .....

Regards,

AKS

[former_member353794]

Hi Amit,

Thanks for the help. But the problem i am facing with PF status is this: If I have created status ZSTATUS which is a copy of STANDARD_FULLSCREEN and used this status in the PBO of my screen (SET PF-STATUS 'ZSTATUS'). When i see my report output, I can see the ZSTATUS and another default stuatus just above my grid. Both these GUI statuses have most of the buttons(icons) in common except for the BACK, CANCEL and EXIT buttons. The ZSTATUS has BACK, CANCEL and EXIT button whereas the default status on my grid container does not have these button. Also, no button on the ZSTATUS works like the way it works if we have passed this status to the ICALLBACK_STATUS of the REUSE_ALV_GRID_DISPLAY function module. In case of using the function module, we do not have to explicitly code for the icons. But here I guess we have to code for every button. What I do not understand is that where is the other default status coming from? Is it the standard functionality of ALV oops concept?

[Former Member]

Hi Jean,

when displaying grid using OOP, we have to code the PF-status in PAI to make it functional.

Thanks

Vivek