Using OOPS Display ALV GRID with Interactive reporting format

[Former Member]

Hi everyone,

This is NK here,

                            I am a beginner in ABAP and I am trying to solve a requirement which is as follows.

1. )  First display a selection screen with 2 radio buttons and 2 select-options fields( one for Kunnr and other for Vbeln ). When clicked on first radio button,  the VBELN select-option should be greyed out (cannot enter values but should be visible) and vice-a-versa.

2. )  If value is entered in KUNNR and executed, the control should navigate to XD03 transaction skipping the initial screen( SKIP FIRST SCREEN ).

  2.1. )  From the second screen of XD03 when clicked on BACK(the one is application toolbar) --- the KUNNR number's , corresponding sales document numbers should be displayed in ALV GRID in next screen. And when a row  is selected in the grid, the control should navigate to VA03 application displaying its details.

2.2. )  From VA03 second screen from 'SALES' tab, when "item level details" are 'double clicked', its " Schedule Line " entrys should be displayed in ALV Grid. Now here when clicked on BACK (in application toolbar) control should Leave to list-processing

       ( NOW here control is back to selection-screen ----   2 radiobuttons and 2 fields )

3. )  If value is entered in VBELN and executed, control navigates to VA03 first and then it's corresponding Kunnr and its details are displayed in a ALV grid.

PS:- I have completed upto second point (the points in BOLD).       From 2.1.) onwards I need your help  And i have gone through BCALV* (couldn't find a relevant one).

Regards,

NK.

[Former Member]

can i ask why you are going to display sales order...double click the schedule line, display more data in an ALV...

would it not be easier for you to gather and display the specific sales order data in your own screen or grid?

It may prove a lot of effort to achieve the VA03 integration, certainly more challenging for beginner with enhancements or BADIs etc - so sometimes there is more than 1 way to skin a cat - so long as your end users can access and do what it is they need to do. So what i am saying is why not extend your current solution but take the VA03 aspect out of it (or even keep it for drill down purposes) - but provide more specific content in the context of the standalone ALV you have developed so far.

[Former Member]

Hi Steve,

                    I have gone through the requirement and its all sorted out. Thank you for giving an idea that the above req. lands in a DRILL DOWN procedure. It was helpful Steve. Thanks again.

Regards,

N Krishna.