topic Re: ALV WITH OOPS in Application Development and Automation Discussions

ALV WITH OOPS

Former Member — Mon, 28 May 2007 06:06:58 GMT

hi all,

1. i wanna diff b/w standard events n custom events. if possible giv detailed description with code for those 2 events.

2. how to use 2 containers on same page for displaying two alv reports [oops alv reporting].

thanks n regards,

suresh babu aluri.

Re: ALV WITH OOPS

Former Member — Mon, 28 May 2007 06:09:19 GMT

Hi Suresh ,

You can use a splitter to display two reports in the same Container .

Regard's

Arun

Re: ALV WITH OOPS

Former Member — Mon, 28 May 2007 06:10:42 GMT

Try this transactions u ll get good examples...

SE83,DWDM & ABAPDOCU.

Thanks & Regards

Santhosh

Re: ALV WITH OOPS

Former Member — Mon, 28 May 2007 06:11:25 GMT

see the sample code for OOPS ALV

OOPs ABAP uses Classes and Interfaces which uses Methods and events.

If you have Java skills it is advantage for you.

There are Local classes as well as Global Classes.

Local classes we can work in SE38 straight away.

But mostly it is better to use the Global classes.

Global Classes or Interfaces are to be created in SE24.

SAP already given some predefined classes and Interfaces.

This OOPS concepts very useful for writing BADI's also.

So first create a class in SE 24.

Define attributes, Methods for that class.

Define parameters for that Method.

You can define event handlers also to handle the messages.

After creation in each method write the code.

Methods are similar to ABAP PERFORM -FORM statements.

After the creation of CLass and methods come to SE38 and create the program.

In the program create a object type ref to that class and with the help of that Object call the methods of that Class and display the data.

Example:

REPORT sapmz_hf_alv_grid .

Type pool for icons - used in the toolbar

TYPE-POOLS: icon.

TABLES: zsflight.

To allow the declaration of o_event_receiver before the
lcl_event_receiver class is defined, decale it as deferred in the
start of the program

CLASS lcl_event_receiver DEFINITION DEFERRED.

*----

G L O B A L I N T E R N A L T A B L E S

*----

*DATA: gi_sflight TYPE STANDARD TABLE OF sflight.

To include a traffic light and/or color a line the structure of the
table must include fields for the traffic light and/or the color

TYPES: BEGIN OF st_sflight.

INCLUDE STRUCTURE zsflight.

Field for traffic light

TYPES: traffic_light TYPE c.

Field for line color

types: line_color(4) type c.

TYPES: END OF st_sflight.

TYPES: tt_sflight TYPE STANDARD TABLE OF st_sflight.

DATA: gi_sflight TYPE tt_sflight.

*----

G L O B A L D A T A

*----

DATA: ok_code LIKE sy-ucomm,

Work area for internal table

g_wa_sflight TYPE st_sflight,

ALV control: Layout structure

gs_layout TYPE lvc_s_layo.

Declare reference variables to the ALV grid and the container

DATA:

go_grid TYPE REF TO cl_gui_alv_grid,

go_custom_container TYPE REF TO cl_gui_custom_container,

o_event_receiver TYPE REF TO lcl_event_receiver.

DATA:

Work area for screen 200

g_screen200 LIKE zsflight.

Data for storing information about selected rows in the grid

DATA:

Internal table

gi_index_rows TYPE lvc_t_row,

Information about 1 row

g_selected_row LIKE lvc_s_row.

*----

C L A S S E S

*----

CLASS lcl_event_receiver DEFINITION.

PUBLIC SECTION.

METHODS:

handle_toolbar FOR EVENT toolbar OF cl_gui_alv_grid

IMPORTING

e_object e_interactive,

handle_user_command FOR EVENT user_command OF cl_gui_alv_grid

IMPORTING e_ucomm.

ENDCLASS.

----

CLASS lcl_event_receiver IMPLEMENTATION

----

CLASS lcl_event_receiver IMPLEMENTATION.

METHOD handle_toolbar.

Event handler method for event toolbar.

CONSTANTS:

Constants for button type

c_button_normal TYPE i VALUE 0,

c_menu_and_default_button TYPE i VALUE 1,

c_menu TYPE i VALUE 2,

c_separator TYPE i VALUE 3,

c_radio_button TYPE i VALUE 4,

c_checkbox TYPE i VALUE 5,

c_menu_entry TYPE i VALUE 6.

DATA:

ls_toolbar TYPE stb_button.

Append seperator to the normal toolbar

CLEAR ls_toolbar.

MOVE c_separator TO ls_toolbar-butn_type..

APPEND ls_toolbar TO e_object->mt_toolbar.

Append a new button that to the toolbar. Use E_OBJECT of
event toolbar. E_OBJECT is of type CL_ALV_EVENT_TOOLBAR_SET.
This class has one attribute MT_TOOLBAR which is of table type
TTB_BUTTON. The structure is STB_BUTTON

CLEAR ls_toolbar.

MOVE 'CHANGE' TO ls_toolbar-function.

MOVE icon_change TO ls_toolbar-icon.

MOVE 'Change flight' TO ls_toolbar-quickinfo.

MOVE 'Change' TO ls_toolbar-text.

MOVE ' ' TO ls_toolbar-disabled.

APPEND ls_toolbar TO e_object->mt_toolbar.

ENDMETHOD.

METHOD handle_user_command.

Handle own functions defined in the toolbar

CASE e_ucomm.

WHEN 'CHANGE'.

PERFORM change_flight.

LEAVE TO SCREEN 0.

ENDCASE.

ENDMETHOD.

ENDCLASS.

*----

S T A R T - O F - S E L E C T I O N.

*----

START-OF-SELECTION.

SET SCREEN '100'.

&----

*& Module USER_COMMAND_0100 INPUT

&----

MODULE user_command_0100 INPUT.

CASE ok_code.

WHEN 'EXIT'.

LEAVE TO SCREEN 0.

ENDCASE.

ENDMODULE. " USER_COMMAND_0100 INPUT

&----

*& Module STATUS_0100 OUTPUT

&----

MODULE status_0100 OUTPUT.

DATA:

For parameter IS_VARIANT that is sued to set up options for storing
the grid layout as a variant in method set_table_for_first_display

l_layout TYPE disvariant,

Utillity field

l_lines TYPE i.

After returning from screen 200 the line that was selected before
going to screen 200, should be selected again. The table gi_index_rows
was the output table from the GET_SELECTED_ROWS method in form
CHANGE_FLIGHT

DESCRIBE TABLE gi_index_rows LINES l_lines.

IF l_lines > 0.

CALL METHOD go_grid->set_selected_rows

EXPORTING

it_index_rows = gi_index_rows.

CALL METHOD cl_gui_cfw=>flush.

REFRESH gi_index_rows.

ENDIF.

Read data and create objects

IF go_custom_container IS INITIAL.

Read data from datbase table

PERFORM get_data.

Create objects for container and ALV grid

CREATE OBJECT go_custom_container

EXPORTING container_name = 'ALV_CONTAINER'.

CREATE OBJECT go_grid

EXPORTING

i_parent = go_custom_container.

Create object for event_receiver class
and set handlers

CREATE OBJECT o_event_receiver.

SET HANDLER o_event_receiver->handle_user_command FOR go_grid.

SET HANDLER o_event_receiver->handle_toolbar FOR go_grid.

Layout (Variant) for ALV grid

l_layout-report = sy-repid. "Layout fo report

*----

Setup the grid layout using a variable of structure lvc_s_layo

*----

Set grid title

gs_layout-grid_title = 'Flights'.

Selection mode - Single row without buttons
(This is the default mode

gs_layout-sel_mode = 'B'.

Name of the exception field (Traffic light field) and the color
field + set the exception and color field of the table

gs_layout-excp_fname = 'TRAFFIC_LIGHT'.

gs_layout-info_fname = 'LINE_COLOR'.

LOOP AT gi_sflight INTO g_wa_sflight.

IF g_wa_sflight-paymentsum < 100000.

Value of traffic light field

g_wa_sflight-traffic_light = '1'.

Value of color field:
C = Color, 6=Color 1=Intesified on, 0: Inverse display off

g_wa_sflight-line_color = 'C610'.

ELSEIF g_wa_sflight-paymentsum => 100000 AND

g_wa_sflight-paymentsum < 1000000.

g_wa_sflight-traffic_light = '2'.

ELSE.

g_wa_sflight-traffic_light = '3'.

ENDIF.

MODIFY gi_sflight FROM g_wa_sflight.

ENDLOOP.

Grid setup for first display

CALL METHOD go_grid->set_table_for_first_display

EXPORTING i_structure_name = 'SFLIGHT'

is_variant = l_layout

i_save = 'A'

is_layout = gs_layout

CHANGING it_outtab = gi_sflight.

*-- End of grid setup -

Raise event toolbar to show the modified toolbar

CALL METHOD go_grid->set_toolbar_interactive.

Set focus to the grid. This is not necessary in this
example as there is only one control on the screen

CALL METHOD cl_gui_control=>set_focus EXPORTING control = go_grid.

ENDIF.

ENDMODULE. " STATUS_0100 OUTPUT

&----

*& Module USER_COMMAND_0200 INPUT

&----

MODULE user_command_0200 INPUT.

CASE ok_code.

WHEN 'EXIT200'.

LEAVE TO SCREEN 100.

WHEN'SAVE'.

PERFORM save_changes.

ENDCASE.

ENDMODULE. " USER_COMMAND_0200 INPUT

&----

*& Form get_data

&----

FORM get_data.

Read data from table SFLIGHT

SELECT *

FROM zsflight

INTO TABLE gi_sflight.

ENDFORM. " load_data_into_grid

&----

*& Form change_flight

&----

Reads the contents of the selected row in the grid, ans transfers
the data to screen 200, where it can be changed and saved.

----

FORM change_flight.

DATA:l_lines TYPE i.

REFRESH gi_index_rows.

CLEAR g_selected_row.

Read index of selected rows

CALL METHOD go_grid->get_selected_rows

IMPORTING

et_index_rows = gi_index_rows.

Check if any row are selected at all. If not
table gi_index_rows will be empty

DESCRIBE TABLE gi_index_rows LINES l_lines.

IF l_lines = 0.

CALL FUNCTION 'POPUP_TO_DISPLAY_TEXT'

EXPORTING

textline1 = 'You must choose a line'.

EXIT.

ENDIF.

Read indexes of selected rows. In this example only one
row can be selected as we are using gs_layout-sel_mode = 'B',
so it is only ncessary to read the first entry in
table gi_index_rows

LOOP AT gi_index_rows INTO g_selected_row.

IF sy-tabix = 1.

READ TABLE gi_sflight INDEX g_selected_row-index INTO g_wa_sflight.

ENDIF.

ENDLOOP.

Transfer data from the selected row to screenm 200 and show
screen 200

CLEAR g_screen200.

MOVE-CORRESPONDING g_wa_sflight TO g_screen200.

LEAVE TO SCREEN '200'.

ENDFORM. " change_flight

&----

*& Form save_changes

&----

Changes made in screen 200 are written to the datbase table
zsflight, and to the grid table gi_sflight, and the grid is
updated with method refresh_table_display to display the changes

----

FORM save_changes.

DATA: l_traffic_light TYPE c.

Update traffic light field
Update database table

MODIFY zsflight FROM g_screen200.

Update grid table , traffic light field and color field.
Note that it is necessary to use structure g_wa_sflight
for the update, as the screen structure does not have a
traffic light field

MOVE-CORRESPONDING g_screen200 TO g_wa_sflight.

IF g_wa_sflight-paymentsum < 100000.

g_wa_sflight-traffic_light = '1'.

C = Color, 6=Color 1=Intesified on, 0: Inverse display off

g_wa_sflight-line_color = 'C610'.

ELSEIF g_wa_sflight-paymentsum => 100000 AND

g_wa_sflight-paymentsum < 1000000.

g_wa_sflight-traffic_light = '2'.

clear g_wa_sflight-line_color.

ELSE.

g_wa_sflight-traffic_light = '3'.

clear g_wa_sflight-line_color.

ENDIF.

MODIFY gi_sflight INDEX g_selected_row-index FROM g_wa_sflight.

Refresh grid

CALL METHOD go_grid->refresh_table_display.

CALL METHOD cl_gui_cfw=>flush.

LEAVE TO SCREEN '100'.

ENDFORM. " save_changes

chk this blog

/people/vijaybabu.dudla/blog/2006/07/21/topofpage-in-alv-using-clguialvgrid

Reward points if useful

Regards

Anji

Re: ALV WITH OOPS

Former Member — Mon, 28 May 2007 06:13:08 GMT

go to se80 and open pakage/devlopment class SLIS there u'll find all the alv exapmles with classes only.

Re: ALV WITH OOPS

Former Member — Mon, 28 May 2007 06:15:16 GMT

http://www.sapmaterial.com/?gclid=CN322K28t4sCFQ-WbgodSGbK2g

it will definitely help u out.

regards

ravish

<b>plz dont forget to reward points if helpful</b>

Re: ALV WITH OOPS

Former Member — Mon, 28 May 2007 06:17:24 GMT

Hi Suresh ,

This is the Code Below

&----

REPORT zus_sdn_three_alv_grids.

DATA:

gd_okcode TYPE ui_func,

go_docking TYPE REF TO cl_gui_docking_container,

go_splitter TYPE REF TO cl_gui_splitter_container,

go_splitter_2 TYPE REF TO cl_gui_splitter_container,

go_cell_top TYPE REF TO cl_gui_container,

go_cell_bottom TYPE REF TO cl_gui_container,

go_cell_left TYPE REF TO cl_gui_container,

go_cell_right TYPE REF TO cl_gui_container,

go_grid1 TYPE REF TO cl_gui_alv_grid,

go_grid2 TYPE REF TO cl_gui_alv_grid,

go_grid3 TYPE REF TO cl_gui_alv_grid.

DATA:

gt_knb1 TYPE STANDARD TABLE OF knb1,

gt_vbak TYPE STANDARD TABLE OF vbak,

gt_vbap TYPE STANDARD TABLE OF vbap.

PARAMETERS:

p_bukrs TYPE bukrs DEFAULT '1000'.

----

CLASS lcl_eventhandler DEFINITION

----

CLASS lcl_eventhandler DEFINITION.

PUBLIC SECTION.

CLASS-METHODS:

handle_double_click FOR EVENT double_click OF cl_gui_alv_grid

IMPORTING

e_row

e_column

es_row_no

sender.

ENDCLASS. "lcl_eventhandler DEFINITION

----

CLASS lcl_eventhandler IMPLEMENTATION

----

CLASS lcl_eventhandler IMPLEMENTATION.

METHOD handle_double_click.

define local data

DATA:

ls_knb1 TYPE knb1,

ls_vbak TYPE vbak,

ls_vbap TYPE vbap.

CASE sender.

WHEN go_grid1.

READ TABLE gt_knb1 INTO ls_knb1 INDEX e_row-index.

CHECK ( ls_knb1-kunnr IS NOT INITIAL ).

CALL METHOD go_grid1->set_current_cell_via_id

EXPORTING

IS_ROW_ID =

IS_COLUMN_ID =

is_row_no = es_row_no.

Triggers PAI of the dynpro with the specified ok-code

CALL METHOD cl_gui_cfw=>set_new_ok_code( 'ORDERS' ).

WHEN go_grid2.

READ TABLE gt_vbak INTO ls_vbak INDEX e_row-index.

CHECK ( ls_vbak-vbeln IS NOT INITIAL ).

CALL METHOD go_grid1->set_current_cell_via_id

EXPORTING

IS_ROW_ID =

IS_COLUMN_ID =

is_row_no = es_row_no.

Triggers PAI of the dynpro with the specified ok-code

CALL METHOD cl_gui_cfw=>set_new_ok_code( 'ORDER_DETAILS' ).

WHEN go_grid3.

READ TABLE gt_vbap INTO ls_vbap INDEX e_row-index.

CHECK ( ls_vbap-matnr IS NOT INITIAL ).

SET PARAMETER ID 'MAT' FIELD ls_vbap-matnr.

CALL TRANSACTION 'MM02' AND SKIP FIRST SCREEN.

WHEN OTHERS.

RETURN.

ENDCASE.

ENDMETHOD. "handle_double_click

ENDCLASS. "lcl_eventhandler IMPLEMENTATION

START-OF-SELECTION.

SELECT * FROM knb1 INTO TABLE gt_knb1

WHERE bukrs = p_bukrs.

Create docking container

CREATE OBJECT go_docking

EXPORTING

parent = cl_gui_container=>screen0

ratio = 90

EXCEPTIONS

OTHERS = 6.

IF sy-subrc <> 0.

MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO

WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.

ENDIF.

Create splitter container

CREATE OBJECT go_splitter

EXPORTING

parent = go_docking

rows = 1

columns = 2

NO_AUTODEF_PROGID_DYNNR =

NAME =

EXCEPTIONS

cntl_error = 1

cntl_system_error = 2

OTHERS = 3.

IF sy-subrc <> 0.

MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO

WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.

ENDIF.

Get cell container

CALL METHOD go_splitter->get_container

EXPORTING

row = 1

column = 1

RECEIVING

container = go_cell_left.

CALL METHOD go_splitter->get_container

EXPORTING

row = 1

column = 2

RECEIVING

container = go_cell_right.

Create 2nd splitter container

CREATE OBJECT go_splitter_2

EXPORTING

parent = go_cell_left

rows = 2

columns = 1

NO_AUTODEF_PROGID_DYNNR =

NAME =

EXCEPTIONS

cntl_error = 1

cntl_system_error = 2

OTHERS = 3.

IF sy-subrc <> 0.

MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO

WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.

ENDIF.

Get cell container

CALL METHOD go_splitter_2->get_container

EXPORTING

row = 1

column = 1

RECEIVING

container = go_cell_top.

CALL METHOD go_splitter_2->get_container

EXPORTING

row = 2

column = 1

RECEIVING

container = go_cell_bottom.

Create ALV grids

CREATE OBJECT go_grid1

EXPORTING

i_parent = go_cell_top

EXCEPTIONS

OTHERS = 5.

IF sy-subrc <> 0.

MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO

WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.

ENDIF.

CREATE OBJECT go_grid2

EXPORTING

i_parent = go_cell_bottom

EXCEPTIONS

OTHERS = 5.

IF sy-subrc <> 0.

MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO

WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.

ENDIF.

CREATE OBJECT go_grid3

EXPORTING

i_parent = go_cell_right

EXCEPTIONS

OTHERS = 5.

IF sy-subrc <> 0.

MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO

WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.

ENDIF.

Set event handler

SET HANDLER: lcl_eventhandler=>handle_double_click FOR go_grid1.

SET HANDLER: lcl_eventhandler=>handle_double_click FOR go_grid2.

SET HANDLER: lcl_eventhandler=>handle_double_click FOR go_grid3.

Display data

CALL METHOD go_grid1->set_table_for_first_display

EXPORTING

i_structure_name = 'KNB1'

CHANGING

it_outtab = gt_knb1

EXCEPTIONS

OTHERS = 4.

IF sy-subrc <> 0.

MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO

WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.

ENDIF.

REFRESH: gt_vbak.

CALL METHOD go_grid2->set_table_for_first_display

EXPORTING

i_structure_name = 'VBAK'

CHANGING

it_outtab = gt_vbak " empty !!!

EXCEPTIONS

OTHERS = 4.

IF sy-subrc <> 0.

MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO

WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.

ENDIF.

REFRESH: gt_vbap.

CALL METHOD go_grid3->set_table_for_first_display

EXPORTING

i_structure_name = 'VBAP'

CHANGING

it_outtab = gt_vbap " empty !!!

EXCEPTIONS

OTHERS = 4.

IF sy-subrc <> 0.

MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO

WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.

ENDIF.

Link the docking container to the target dynpro

CALL METHOD go_docking->link

EXPORTING

repid = syst-repid

dynnr = '0100'

CONTAINER =

EXCEPTIONS

OTHERS = 4.

IF sy-subrc <> 0.

MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO

WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.

ENDIF.

NOTE: dynpro does not contain any elements

CALL SCREEN '0100'.

Flow logic of dynpro:

*PROCESS BEFORE OUTPUT.

MODULE STATUS_0100.

*PROCESS AFTER INPUT.

MODULE USER_COMMAND_0100.

END-OF-SELECTION.

&----

*& Module STATUS_0100 OUTPUT

&----

text

----

MODULE status_0100 OUTPUT.

SET PF-STATUS 'STATUS_0100'. " contains push button "ORDERS"

SET TITLEBAR 'xxx'.

Refresh display of detail ALV list

CALL METHOD go_grid2->refresh_table_display

EXPORTING

IS_STABLE =

I_SOFT_REFRESH =

EXCEPTIONS

OTHERS = 2.

IF sy-subrc <> 0.

MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO

WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.

ENDIF.

Refresh display of detail ALV list

CALL METHOD go_grid3->refresh_table_display

EXPORTING

IS_STABLE =

I_SOFT_REFRESH =

EXCEPTIONS

OTHERS = 2.

IF sy-subrc <> 0.

MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO

WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.

ENDIF.

ENDMODULE. " STATUS_0100 OUTPUT

&----

*& Module USER_COMMAND_0100 INPUT

&----

text

----

MODULE user_command_0100 INPUT.

CASE gd_okcode.

WHEN 'BACK' OR

'END' OR

'CANC'.

SET SCREEN 0. LEAVE SCREEN.

User has pushed button "Display Orders"

WHEN 'ORDERS'.

PERFORM customer_show_orders.

WHEN 'ORDER_DETAILS'.

PERFORM order_show_details.

WHEN OTHERS.

ENDCASE.

CLEAR: gd_okcode.

ENDMODULE. " USER_COMMAND_0100 INPUT

&----

*& Form CUSTOMER_SHOW_ORDERS

&----

text

----

--> p1 text

<-- p2 text

----

FORM customer_show_orders .

define local data

DATA:

ld_row TYPE i,

ls_knb1 TYPE knb1.

CALL METHOD go_grid1->get_current_cell

IMPORTING

e_row = ld_row.

READ TABLE gt_knb1 INTO ls_knb1 INDEX ld_row.

CHECK ( syst-subrc = 0 ).

SELECT * FROM vbak INTO TABLE gt_vbak

WHERE kunnr = ls_knb1-kunnr.

REFRESH: gt_vbap.

ENDFORM. " CUSTOMER_SHOW_ORDERS

&----

*& Form ORDER_SHOW_DETAILS

&----

text

----

--> p1 text

<-- p2 text

----

FORM order_show_details .

define local data

DATA:

ld_row TYPE i,

ls_vbak TYPE vbak.

CALL METHOD go_grid1->get_current_cell

IMPORTING

e_row = ld_row.

READ TABLE gt_vbak INTO ls_vbak INDEX ld_row.

CHECK ( syst-subrc = 0 ).

SELECT * FROM vbap INTO TABLE gt_vbap

WHERE vbeln = ls_vbak-vbeln.

ENDFORM. " ORDER_SHOW_DETAILS

Thnaks & Regards

Bhaskar Rao.M

Re: ALV WITH OOPS

Former Member — Mon, 28 May 2007 06:18:15 GMT

Hi,

some links.

www.sapgenie.com

www.abap4u.com

http://help.sap.com/saphelp_nw2004s/helpdata/en/5e/88d440e14f8431e10000000a1550b0/frameset.htm

download the PDF from following link.

http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCSRVALV/BCSRVALV.pdf

The ALV object Grid methods allow the same functionality as ALV grid report function modules but are displayed within

a screen (dialog program). SAP has provided a suit of programs which demonstrate how to For examples see standard SAP

programs as detailed below:

BCALV_EDIT_01 This report illustrates the simplest case of using an editable/noneditable ALV Grid Control.

BCALV_EDIT_02 This report illustrates how to set chosen cells of an ALV Grid Control editable.

BCALV_EDIT_03 In this example the user may change values of fields SEATSOCC (occupied seats) and/or PLANETYPE.

The report checks the input value(s) semantically and provides protocol messages in case of error

BCALV_EDIT_04 This report illustrates how to add and remove lines to a table using the ALV Grid Control and how to

implement the saving of the new data.

BCALV_EDIT_05 This example shows how to use checkboxes within an ALV Grid Control. You learn:

(1) how to define a column for editable checkboxes for an attribute of your list

(2) how to evaluate the checked checkboxes

(3) how to switch between editable and non-editable checkboxes

BCALV_EDIT_06 This example shows how to define a dropdown listbox for all cells of one column in an editable ALV

Grid Control.

BCALV_EDIT_07 This example shows how to define dropdown listboxes for particular cells of your output table.

BCALV_EDIT_08 This report implements an ALV Grid Control with an application specific F4 help. The following aspects

are dealt with:

(1) how to replace the standard f4 help

(2) how to pass the selected value to the ALV Grid Control

(3) how to build an f4 help, whose value range depend on a value of another cell.

Regards,

Priyanka.

Re: ALV WITH OOPS

Former Member — Wed, 30 May 2007 05:43:01 GMT

answered