topic Re: OBJECT-ORIENTED ABAP in Application Development and Automation Discussions

OBJECT-ORIENTED ABAP

Former Member — Mon, 16 Jul 2007 10:56:24 GMT

HI ALL

WHAT IS OBJECT-ORIENTED ABAP?

Re: OBJECT-ORIENTED ABAP

Former Member — Mon, 16 Jul 2007 10:59:20 GMT

“The ALV Grid control is a flexible tool for displaying lists. The tool provides common list operations as generic functions and can be enhanced by self-defined options.”

The ALV Grid control is used to build non-hierarchical, interactive, and modern-design lists. As a control, it is a component that is installed on the local PC.

The ALV Grid control provides typical list functions as sorting, filtering, summing, etc... while also gives the opportunity to develop user functions where needed. It presents numerous interfaces like Excel Inplace and Crystal Reports.

The wrapper class implemented to encapsulate ALV Grid functionality is “CL_GUI_ALV_GRID”. There is another way to display lists with ALV utilizing “REUSE_ALV...” functions.

Building Blocks

While preparing a list to be displayed via an ALV grid control, we have some basic components to prepare. These are;

i. List data: Obviously, this is the data in an internal table to be listed. Standard ALV functions except sorting makes just read access to the list data. However, sorting changes state of the internal table. The internal table holding list data may be of any flat type. Deep types are only allowed when set for some functionalities of ALV Grid.

ii. Field Catalog: We use another internal table to define specifications on how the fields of our list will be displayed. This internal table is called the “field catalog”. The field catalog must comprise some technical and additional information about display options for each column to be displayed. There are three procedures to generate the field catalog as “Automatic generation”, “Semi-automatic generation”, and “Manual generation”. The internal table for the field catalog must be referenced to the dictionary type “LVC_T_FCAT”.

iii. Layout Structure: We fill a structure to specify general layout options for the grid. With this structure we can set general display options, grid customizing, totals options, color adjustments etc... The layout structure must be of type “LVC_S_LAYO”.

iv. Event Handler: We should define and implement an event handler class if we want to handle events triggered by the ALV Grid instance. After creating ALV Grid instance, we must register an instance of this event handler class to handle ALV Grid events.

v. Additional Data: To trigger some additional features of ALV Grid we can have some additional data to pass as parameters. For example, initial sorting criteria, buttons to be deactivated, etc...

<b>Sample code</b>

*"Table declarations...................................................

TABLES:

EKKO, " Purchasing Document Header

CDHDR, " Change document header

SSCRFIELDS. " Fields on selection screens

*"Selection screen elements............................................

SELECT-OPTIONS:

S_EBELN FOR EKKO-EBELN, " Purchasing Document Number

S_LIFNR FOR EKKO-LIFNR, " Vendor's account number

S_EKGRP FOR EKKO-EKGRP, " Purchasing group

S_BEDAT FOR EKKO-BEDAT, " Purchasing Document Date

S_UDATE FOR CDHDR-UDATE. " Creation date of the change

" document

*" Data declarations...................................................

"----

Field String to hold Purchase Document Number *

"----

DATA:

BEGIN OF FS_EBELN,

EBELN(90) TYPE C, " Purchase Document Number

ERNAM TYPE EKKO-ERNAM, " Name of Person who Created

" the Object

LIFNR TYPE EKKO-LIFNR, " Vendor's account number

EKGRP TYPE EKKO-EKGRP, " Purchasing group

BEDAT TYPE EKKO-BEDAT, " Purchasing Document Date

END OF FS_EBELN,

"----

Field String to hold Purchase Document Header *

"----

BEGIN OF FS_EKKO,

EBELN TYPE EKKO-EBELN, " Purchasing Document Number

ERNAM TYPE EKKO-ERNAM, " Name of Person who Created the

" Object

LIFNR TYPE EKKO-LIFNR, " Vendor's account number

EKGRP TYPE EKKO-EKGRP, " Purchasing group

BEDAT TYPE EKKO-BEDAT, " Purchasing Document Date

END OF FS_EKKO,

"----

Field String to hold Account Number and name of the Vendor *

"----

BEGIN OF FS_LFA1,

LIFNR TYPE LFA1-LIFNR, " Account Number of Vendor

NAME1 TYPE LFA1-NAME1, " Name1

END OF FS_LFA1,

"----

Field String to hold Change date and the name of the user *

"----

BEGIN OF FS_CDHDR,

OBJECTCLAS TYPE CDHDR-OBJECTCLAS, " Object Class

OBJECTID TYPE CDHDR-OBJECTID, " Object value

CHANGENR TYPE CDHDR-CHANGENR, " Document change number

USERNAME TYPE CDHDR-USERNAME, " User name

UDATE TYPE CDHDR-UDATE, " Creation date of the change

" document

END OF FS_CDHDR,

"----

Field String to hold Change document items *

"----

BEGIN OF FS_CDPOS,

OBJECTCLAS TYPE CDPOS-OBJECTCLAS," Object class

OBJECTID(10) TYPE C, " Object Value

CHANGENR TYPE CDPOS-CHANGENR, " Document change number

TABNAME TYPE CDPOS-TABNAME, " Table Name

FNAME TYPE CDPOS-FNAME, " Field Name

VALUE_NEW TYPE CDPOS-VALUE_NEW, " New contents of changed field

VALUE_OLD TYPE CDPOS-VALUE_OLD, " Old contents of changed field

END OF FS_CDPOS,

"----

Field String to hold Date Element Name *

"----

BEGIN OF FS_DATAELE,

TABNAME TYPE DD03L-TABNAME, " Table Name

FIELDNAME TYPE DD03L-FIELDNAME, " Field Name

ROLLNAME TYPE DD03L-ROLLNAME, " Data element (semantic domain)

END OF FS_DATAELE,

"----

Field String to hold Short Text of the Date Element *

"----

BEGIN OF FS_TEXT,

ROLLNAME TYPE DD04T-ROLLNAME, " Data element (semantic domain)

DDTEXT TYPE DD04T-DDTEXT, " Short Text Describing R/3

" Repository Objects

END OF FS_TEXT,

"----

Field String to hold data to be displayed on the ALV grid *

"----

BEGIN OF FS_OUTTAB,

EBELN TYPE EKKO-EBELN, " Purchasing Document Number

ERNAM TYPE EKKO-ERNAM, " Name of Person who Created the

" Object

LIFNR TYPE EKKO-LIFNR, " Vendor's account number

EKGRP TYPE EKKO-EKGRP, " Purchasing group

BEDAT TYPE EKKO-BEDAT, " Purchasing Document Date

WERKS TYPE LFA1-WERKS, " Plant

NAME1 TYPE LFA1-NAME1, " Name1

USERNAME TYPE CDHDR-USERNAME, " User name

UDATE TYPE CDHDR-UDATE, " Creation date of the change

" document

DDTEXT TYPE DD04T-DDTEXT, " Short Text Describing R/3

" Repository Objects

VALUE_NEW TYPE CDPOS-VALUE_NEW, " New contents of changed field

VALUE_OLD TYPE CDPOS-VALUE_OLD, " Old contents of changed field

END OF FS_OUTTAB,

"----

Internal table to hold Purchase Document Number *

"----

T_EBELN LIKE STANDARD TABLE

OF FS_EBELN,

"----

Internal table to hold Purchase Document Header *

"----

T_EKKO LIKE STANDARD TABLE

OF FS_EKKO,

"----

Temp Internal table to hold Purchase Document Header *

"----

T_EKKO_TEMP LIKE STANDARD TABLE

OF FS_EKKO,

"----

Internal table to hold Account number and Name of the Vendor *

"----

T_LFA1 LIKE STANDARD TABLE

OF FS_LFA1,

"----

Internal Table to hold Change date and the name of the user *

"----

T_CDHDR LIKE STANDARD TABLE

OF FS_CDHDR,

"----

Internal Table to hold Change document items *

"----

T_CDPOS LIKE STANDARD TABLE

OF FS_CDPOS,

"----

Temp. Internal Table to hold Change document items *

"----

T_CDPOS_TEMP LIKE STANDARD TABLE

OF FS_CDPOS,

"----

Internal Table to hold Data Element Name *

"----

T_DATAELE LIKE STANDARD TABLE

OF FS_DATAELE,

"----

Temp. Internal Table to hold Data Element Name *

"----

T_DATAELE_TEMP LIKE STANDARD TABLE

OF FS_DATAELE,

"----

Internal Table to hold Short Text of the Date Element *

"----

T_TEXT LIKE STANDARD TABLE

OF FS_TEXT,

"----

Internal Table to hold data to be displayed on the ALV grid *

"----

T_OUTTAB LIKE STANDARD TABLE

OF FS_OUTTAB.

"----

C L A S S D E F I N I T I O N *

"----

CLASS LCL_EVENT_HANDLER DEFINITION DEFERRED.

*" Data declarations...................................................

"----

Work variables *

"----

DATA:

W_EBELN TYPE EKKO-EBELN, " Purchasing Document Number

W_LIFNR TYPE EKKO-LIFNR, " Vendor's account number

W_EKGRP TYPE EKKO-EKGRP, " Purchasing group

W_VALUE TYPE EKKO-EBELN, " Reflected Value

W_SPACE VALUE ' ', " Space

W_FLAG TYPE I, " Flag Variable

W_VARIANT TYPE DISVARIANT, " Variant

*--- ALV Grid

W_GRID TYPE REF TO CL_GUI_ALV_GRID,

*--- Event Handler

W_EVENT_CLICK TYPE REF TO LCL_EVENT_HANDLER,

*--- Field catalog table

T_FIELDCAT TYPE LVC_T_FCAT.

"----

AT SELECTION-SCREEN EVENT *

"----

AT SELECTION-SCREEN ON S_EBELN.

Subroutine to validate Purchase Document Number.

PERFORM VALIDATE_PD_NUM.

AT SELECTION-SCREEN ON S_LIFNR.

Subroutine to validate Vendor Number.

PERFORM VALIDATE_VEN_NUM.

AT SELECTION-SCREEN ON S_EKGRP.

Subroutine to validate Purchase Group.

PERFORM VALIDATE_PUR_GRP.

"----

START-OF-SELECTION EVENT *

"----

START-OF-SELECTION.

Subroutine to select all Purchase orders.

PERFORM SELECT_PO.

CHECK W_FLAG EQ 0.

Subroutine to select Object values.

PERFORM SELECT_OBJ_ID.

CHECK W_FLAG EQ 0.

Subroutine to select Changed values.

PERFORM SELECT_CHANGED_VALUE.

CHECK W_FLAG EQ 0.

Subroutine to Select Purchase Orders.

PERFORM SELECT_PUR_DOC.

Subroutine to select Vendor Details.

PERFORM SELECT_VENDOR.

Subroutine to select Text for the Changed values.

PERFORM DESCRIPTION.

"----

END-OF-SELECTION EVENT *

"----

END-OF-SELECTION.

IF NOT T_EKKO IS INITIAL.

Subroutine to populate the Output Table.

PERFORM FILL_OUTTAB.

Subroutine to build Field Catalog.

PERFORM PREPARE_FIELD_CATALOG CHANGING T_FIELDCAT.

CALL SCREEN 100.

ENDIF. " IF NOT T_EKKO...

----

CLASS LCL_EVENT_HANDLER DEFINITION

----

Defining Class which handles events

----

CLASS LCL_EVENT_HANDLER DEFINITION .

PUBLIC SECTION .

METHODS:

HANDLE_HOTSPOT_CLICK

FOR EVENT HOTSPOT_CLICK OF CL_GUI_ALV_GRID

IMPORTING E_ROW_ID E_COLUMN_ID.

ENDCLASS. " LCL_EVENT_HANDLER DEFINITION

----

CLASS LCL_EVENT_HANDLER IMPLEMENTATION

----

Implementing the Class which can handle events

----

CLASS LCL_EVENT_HANDLER IMPLEMENTATION .

*---Handle Double Click

METHOD HANDLE_HOTSPOT_CLICK .

Subroutine to get the HotSpot Cell information.

PERFORM GET_CELL_INFO.

SET PARAMETER ID 'BES' FIELD W_VALUE.

CALL TRANSACTION 'ME23N'.

ENDMETHOD. " HANDLE_HOTSPOT_CLICK

ENDCLASS. " LCL_EVENT_HANDLER

&----

*& Module STATUS_0100 OUTPUT

&----

PBO Event

----

MODULE STATUS_0100 OUTPUT.

SET PF-STATUS 'OOPS'.

SET TITLEBAR 'TIT'.

Subroutine to fill the Variant Structure

PERFORM FILL_VARIANT.

IF W_GRID IS INITIAL.

CREATE OBJECT W_GRID

EXPORTING

I_SHELLSTYLE = 0
I_LIFETIME =

I_PARENT = CL_GUI_CONTAINER=>SCREEN0

I_APPL_EVENTS =
I_PARENTDBG =
I_APPLOGPARENT =
I_GRAPHICSPARENT =
I_NAME =
I_FCAT_COMPLETE = SPACE

EXCEPTIONS

ERROR_CNTL_CREATE = 1

ERROR_CNTL_INIT = 2

ERROR_CNTL_LINK = 3

ERROR_DP_CREATE = 4

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. " IF SY-SUBRC <> 0

CALL METHOD W_GRID->SET_TABLE_FOR_FIRST_DISPLAY

EXPORTING

I_BUFFER_ACTIVE =
I_BYPASSING_BUFFER =
I_CONSISTENCY_CHECK =
I_STRUCTURE_NAME =

IS_VARIANT = W_VARIANT

I_SAVE = 'A'

I_DEFAULT = 'X'
IS_LAYOUT =
IS_PRINT =
IT_SPECIAL_GROUPS =
IT_TOOLBAR_EXCLUDING =
IT_HYPERLINK =
IT_ALV_GRAPHICS =
IT_EXCEPT_QINFO =
IR_SALV_ADAPTER =

CHANGING

IT_OUTTAB = T_OUTTAB

IT_FIELDCATALOG = T_FIELDCAT

IT_SORT =
IT_FILTER =

EXCEPTIONS

INVALID_PARAMETER_COMBINATION = 1

PROGRAM_ERROR = 2

TOO_MANY_LINES = 3

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. " IF SY-SUBRC <> 0.

ENDIF. " IF W_GRID IS INITIAL

CREATE OBJECT W_EVENT_CLICK.

SET HANDLER W_EVENT_CLICK->HANDLE_HOTSPOT_CLICK FOR W_GRID.

ENDMODULE. " STATUS_0100 OUTPUT

&----

*& Module USER_COMMAND_0100 INPUT

&----

PAI Event

----

MODULE USER_COMMAND_0100 INPUT.

CASE SY-UCOMM.

WHEN 'BACK'.

LEAVE TO SCREEN 0.

WHEN 'EXIT'.

LEAVE PROGRAM.

WHEN 'CANCEL'.

LEAVE TO SCREEN 0.

ENDCASE.

ENDMODULE. " USER_COMMAND_0100 INPUT

&----

*& Form PREPARE_FIELD_CATALOG

&----

Subroutine to build the Field catalog

----

<--P_T_FIELDCAT Field Catalog Table

----

FORM PREPARE_FIELD_CATALOG CHANGING PT_FIELDCAT TYPE LVC_T_FCAT .

DATA LS_FCAT TYPE LVC_S_FCAT.

Purchasing group...

LS_FCAT-FIELDNAME = 'EKGRP'.

LS_FCAT-REF_TABLE = 'EKKO'.

LS_FCAT-INTTYPE = 'C'.

LS_FCAT-OUTPUTLEN = '10'.

APPEND LS_FCAT TO PT_FIELDCAT.

CLEAR LS_FCAT.

Purchasing Document Number...

LS_FCAT-FIELDNAME = 'EBELN'.

LS_FCAT-REF_TABLE = 'EKKO' .

LS_FCAT-EMPHASIZE = 'C411'.

LS_FCAT-INTTYPE = 'C'.

LS_FCAT-OUTPUTLEN = '10'.

LS_FCAT-HOTSPOT = 'X'.

APPEND LS_FCAT TO PT_FIELDCAT .

CLEAR LS_FCAT .

Name of Person who Created the Object...

LS_FCAT-FIELDNAME = 'ERNAM'.

LS_FCAT-REF_TABLE = 'EKKO'.

LS_FCAT-OUTPUTLEN = '15' .

APPEND LS_FCAT TO PT_FIELDCAT.

CLEAR LS_FCAT.

Purchasing Document Date...

LS_FCAT-FIELDNAME = 'BEDAT'.

LS_FCAT-REF_TABLE = 'EKKO'.

LS_FCAT-INTTYPE = 'C'.

LS_FCAT-OUTPUTLEN = '10'.

APPEND LS_FCAT TO PT_FIELDCAT.

CLEAR LS_FCAT.

Vendor's account number...

LS_FCAT-FIELDNAME = 'LIFNR'.

LS_FCAT-REF_TABLE = 'EKKO'.

LS_FCAT-INTTYPE = 'C'.

LS_FCAT-OUTPUTLEN = '10'.

APPEND LS_FCAT TO PT_FIELDCAT.

CLEAR LS_FCAT.

Account Number of Vendor or Creditor...

LS_FCAT-FIELDNAME = 'NAME1'.

LS_FCAT-REF_TABLE = 'LFA1'.

LS_FCAT-INTTYPE = 'C'.

LS_FCAT-OUTPUTLEN = '10'.

LS_FCAT-COLTEXT = 'Vendor Name'(001).

LS_FCAT-SELTEXT = 'Vendor Name'(001).

APPEND LS_FCAT TO PT_FIELDCAT.

CLEAR LS_FCAT.

Creation date of the change document...

LS_FCAT-FIELDNAME = 'UDATE'.

LS_FCAT-REF_TABLE = 'CDHDR'.

LS_FCAT-INTTYPE = 'C'.

LS_FCAT-OUTPUTLEN = '10'.

LS_FCAT-COLTEXT = 'Change Date'(002).

LS_FCAT-SELTEXT = 'Change Date'(002).

APPEND LS_FCAT TO PT_FIELDCAT.

CLEAR LS_FCAT.

User name of the person responsible in change document...

LS_FCAT-FIELDNAME = 'USERNAME'.

LS_FCAT-REF_TABLE = 'CDHDR'.

LS_FCAT-INTTYPE = 'C'.

LS_FCAT-OUTPUTLEN = '10'.

LS_FCAT-COLTEXT = 'Modified by'(003).

LS_FCAT-SELTEXT = 'Modified by'(003).

APPEND LS_FCAT TO PT_FIELDCAT.

CLEAR LS_FCAT.

Short Text Describing R/3 Repository Objects...

LS_FCAT-FIELDNAME = 'DDTEXT'.

LS_FCAT-REF_TABLE = 'DD04T'.

LS_FCAT-INTTYPE = 'C'.

LS_FCAT-OUTPUTLEN = '15'.

APPEND LS_FCAT TO PT_FIELDCAT.

CLEAR LS_FCAT.

Old contents of changed field...

LS_FCAT-FIELDNAME = 'VALUE_OLD'.

LS_FCAT-REF_TABLE = 'CDPOS'.

LS_FCAT-INTTYPE = 'C'.

LS_FCAT-OUTPUTLEN = '12'.

APPEND LS_FCAT TO PT_FIELDCAT.

CLEAR LS_FCAT.

New contents of changed field...

LS_FCAT-FIELDNAME = 'VALUE_NEW'.

LS_FCAT-REF_TABLE = 'CDPOS'.

LS_FCAT-INTTYPE = 'C'.

LS_FCAT-OUTPUTLEN = '12'.

APPEND LS_FCAT TO PT_FIELDCAT.

CLEAR LS_FCAT.

ENDFORM. " PREPARE_FIELD_CATALOG

&----

*& Form SELECT_PO

&----

Subroutine to select all the Purchase Orders

----

There are no interface parameters to be passed to this subroutine.

----

FORM SELECT_PO .

SELECT EBELN " Purchasing Document Number

ERNAM " Name of Person who Created

" the Object

LIFNR " Vendor's account number

EKGRP " Purchasing group

BEDAT " Purchasing Document Date

FROM EKKO

PACKAGE SIZE 10000

APPENDING TABLE T_EBELN

WHERE EBELN IN S_EBELN

AND BEDAT IN S_BEDAT.

ENDSELECT.

IF SY-SUBRC NE 0.

W_FLAG = 1.

MESSAGE S401(M8).

ENDIF. " IF SY-SUBRC NE 0

ENDFORM. " SELECT_PO

&----

*& Form SELECT_OBJ_ID

&----

Subroutine to select Object ID

----

There are no interface parameters to be passed to this subroutine.

----

FORM SELECT_OBJ_ID .

IF NOT T_EBELN IS INITIAL.

SELECT OBJECTCLAS " Object Class

OBJECTID " Object value

CHANGENR " Document change number

USERNAME " User name

UDATE " Creation date

FROM CDHDR

INTO TABLE T_CDHDR

FOR ALL ENTRIES IN T_EBELN

WHERE OBJECTID EQ T_EBELN-EBELN

AND UDATE IN S_UDATE

AND TCODE IN ('ME21N','ME22N','ME23N').

ENDSELECT.

IF SY-SUBRC NE 0.

W_FLAG = 1.

MESSAGE S833(M8) WITH 'Header Not Found'(031).

ENDIF. " IF SY-SUBRC NE 0.

ENDIF. " IF NOT T_EBELN IS INITIAL

ENDFORM. " SELECT_OBJ_ID

&----

*& Form SELECT_CHANGED_VALUE

&----

Subroutine to select Changed Values

----

There are no interface parameters to be passed to this subroutine.

----

FORM SELECT_CHANGED_VALUE .

IF NOT T_CDHDR IS INITIAL.

SELECT OBJECTCLAS " Object class

OBJECTID " Object value

CHANGENR " Document change number

TABNAME " Table Name

FNAME " Field Name

VALUE_NEW " New contents of changed field

VALUE_OLD " Old contents of changed field

FROM CDPOS

PACKAGE SIZE 10000

APPENDING TABLE T_CDPOS

FOR ALL ENTRIES IN T_CDHDR

WHERE OBJECTCLAS EQ T_CDHDR-OBJECTCLAS

AND OBJECTID EQ T_CDHDR-OBJECTID

AND CHANGENR EQ T_CDHDR-CHANGENR.

ENDSELECT.

IF SY-SUBRC NE 0.

W_FLAG = 1.

MESSAGE S833(M8) WITH 'Item Not Found'(032).

ENDIF. " IF SY-SUBRC NE 0.

ENDIF. " IF NOT T_CDHDR IS INITIAL

T_CDPOS_TEMP[] = T_CDPOS[].

ENDFORM. " SELECT_CHANGED_VALUE

&----

*& Form SELECT_PUR_DOC

&----

Subroutine to select Purchase Order Details

----

There are no interface parameters to be passed to this subroutine.

----

FORM SELECT_PUR_DOC .

IF NOT T_CDPOS IS INITIAL.

SORT T_EBELN BY EBELN.

LOOP AT T_CDPOS INTO FS_CDPOS.

READ TABLE T_EBELN INTO FS_EBELN WITH KEY EBELN =

FS_CDPOS-OBJECTID BINARY SEARCH.

IF SY-SUBRC NE 0.

DELETE TABLE T_EBELN FROM FS_EBELN.

ENDIF. " IF SY-SUBRC NE 0.

ENDLOOP. " LOOP AT T_CDPOS...

LOOP AT T_EBELN INTO FS_EBELN.

MOVE FS_EBELN-EBELN TO FS_EKKO-EBELN.

MOVE FS_EBELN-ERNAM TO FS_EKKO-ERNAM.

MOVE FS_EBELN-LIFNR TO FS_EKKO-LIFNR.

MOVE FS_EBELN-EKGRP TO FS_EKKO-EKGRP.

MOVE FS_EBELN-BEDAT TO FS_EKKO-BEDAT.

APPEND FS_EKKO TO T_EKKO.

ENDLOOP. " LOOP AT T_EBELN...

T_EKKO_TEMP[] = T_EKKO[].

ENDIF. " IF NOT T_CDPOS IS INITIAL

ENDFORM. " SELECT_PUR_DOC

&----

*& Form SELECT_VENDOR

&----

Subroutine to select Vendor details

----

There are no interface parameters to be passed to this subroutine.

----

FORM SELECT_VENDOR .

IF NOT T_EKKO IS INITIAL.

SORT T_EKKO_TEMP BY LIFNR.

DELETE ADJACENT DUPLICATES FROM T_EKKO_TEMP COMPARING LIFNR.

SELECT LIFNR " Account Number of Vendor or

" Creditor

NAME1 " Name 1

FROM LFA1

INTO TABLE T_LFA1

FOR ALL ENTRIES IN T_EKKO_TEMP

WHERE LIFNR EQ T_EKKO_TEMP-LIFNR.

IF SY-SUBRC NE 0.

MESSAGE S002(M8) WITH 'Master Details'(033).

ENDIF. " IF SY-SUBRC NE 0.

ENDIF. " IF NOT T_EKKO IS INITIAL

ENDFORM. " SELECT_VENDOR

&----

*& Form DESCRIPTION

&----

Subroutine to get the description

----

There are no interface parameters to be passed to this subroutine.

----

FORM DESCRIPTION .

IF NOT T_CDPOS IS INITIAL.

SORT T_CDPOS_TEMP BY TABNAME FNAME.

DELETE ADJACENT DUPLICATES FROM T_CDPOS_TEMP COMPARING TABNAME FNAME

SELECT TABNAME " Table Name

FIELDNAME " Field Name

ROLLNAME " Data element

FROM DD03L

INTO TABLE T_DATAELE

FOR ALL ENTRIES IN T_CDPOS_TEMP

WHERE TABNAME EQ T_CDPOS_TEMP-TABNAME

AND FIELDNAME EQ T_CDPOS_TEMP-FNAME.

IF NOT T_DATAELE IS INITIAL.

T_DATAELE_TEMP[] = T_DATAELE[].

SORT T_DATAELE_TEMP BY ROLLNAME.

DELETE ADJACENT DUPLICATES FROM T_DATAELE_TEMP COMPARING ROLLNAME.

SELECT ROLLNAME " Data element

DDTEXT " Short Text Describing R/3

" Repository Objects

FROM DD04T

INTO TABLE T_TEXT

FOR ALL ENTRIES IN T_DATAELE_TEMP

WHERE ROLLNAME EQ T_DATAELE_TEMP-ROLLNAME

AND DDLANGUAGE EQ SY-LANGU.

IF SY-SUBRC NE 0.

EXIT.

ENDIF. " IF SY-SUBRC NE 0.

ENDIF. " IF NOT T_DATAELE IS INITIAL.

ENDIF. " IF NOT T_CDPOS IS INITIAL.

ENDFORM. " DESCRIPTION

&----

*& Form FILL_OUTTAB

&----

Subroutine to populate the Outtab

----

There are no interface parameters to be passed to this subroutine.

----

FORM FILL_OUTTAB .

SORT T_CDHDR BY OBJECTCLAS OBJECTID CHANGENR.

SORT T_EKKO BY EBELN.

SORT T_LFA1 BY LIFNR.

SORT T_DATAELE BY TABNAME FIELDNAME.

SORT T_TEXT BY ROLLNAME.

LOOP AT T_CDPOS INTO FS_CDPOS.

READ TABLE T_CDHDR INTO FS_CDHDR WITH KEY

OBJECTCLAS = FS_CDPOS-OBJECTCLAS

OBJECTID = FS_CDPOS-OBJECTID

CHANGENR = FS_CDPOS-CHANGENR

BINARY SEARCH.

IF SY-SUBRC EQ 0.

MOVE FS_CDHDR-USERNAME TO FS_OUTTAB-USERNAME.

MOVE FS_CDHDR-UDATE TO FS_OUTTAB-UDATE.

READ TABLE T_EKKO INTO FS_EKKO WITH KEY

EBELN = FS_CDHDR-OBJECTID

BINARY SEARCH.

IF SY-SUBRC EQ 0.

MOVE FS_EKKO-EBELN TO FS_OUTTAB-EBELN.

MOVE FS_EKKO-ERNAM TO FS_OUTTAB-ERNAM.

MOVE FS_EKKO-LIFNR TO FS_OUTTAB-LIFNR.

MOVE FS_EKKO-EKGRP TO FS_OUTTAB-EKGRP.

MOVE FS_EKKO-BEDAT TO FS_OUTTAB-BEDAT.

READ TABLE T_LFA1 INTO FS_LFA1 WITH KEY

LIFNR = FS_EKKO-LIFNR

BINARY SEARCH.

IF SY-SUBRC EQ 0.

MOVE FS_LFA1-NAME1 TO FS_OUTTAB-NAME1.

ENDIF. " IF SY-SUBRC EQ 0.

MOVE FS_CDPOS-VALUE_NEW TO FS_OUTTAB-VALUE_NEW.

MOVE FS_CDPOS-VALUE_OLD TO FS_OUTTAB-VALUE_OLD.

READ TABLE T_DATAELE INTO FS_DATAELE WITH KEY

TABNAME = FS_CDPOS-TABNAME

FIELDNAME = FS_CDPOS-FNAME

BINARY SEARCH.

IF SY-SUBRC EQ 0.

READ TABLE T_TEXT INTO FS_TEXT WITH KEY

ROLLNAME = FS_DATAELE-ROLLNAME

BINARY SEARCH.

IF SY-SUBRC EQ 0.

MOVE FS_TEXT-DDTEXT TO FS_OUTTAB-DDTEXT.

ENDIF. " IF SY-SUBRC EQ 0.

APPEND FS_OUTTAB TO T_OUTTAB.

CLEAR FS_OUTTAB.

ENDLOOP.

ENDFORM. " FILL_OUTTAB

&----

*& Form GET_CELL_INFO

&----

Subroutine to get the Cell Information

----

--> W_VALUE Holds the value of Hotspot clicked

----

FORM GET_CELL_INFO .

CALL METHOD W_GRID->GET_CURRENT_CELL

IMPORTING

E_ROW =

E_VALUE = W_VALUE

E_COL =
ES_ROW_ID =
ES_COL_ID =
ES_ROW_NO =

ENDFORM. " GET_CELL_INFO

&----

*& Form VALIDATE_PD_NUM

&----

Subroutine to validate Purchase Document Number

----

There are no interface parameters to be passed to this subroutine.

----

FORM VALIDATE_PD_NUM .

IF NOT S_EBELN[] IS INITIAL.

SELECT EBELN " Purchase Document Number

FROM EKKO

INTO W_EBELN

UP TO 1 ROWS

WHERE EBELN IN S_EBELN.

ENDSELECT.

IF SY-SUBRC NE 0.

CLEAR SSCRFIELDS-UCOMM.

MESSAGE E717(M8).

ENDIF. " IF SY-SUBRC NE 0

ENDIF. " IF NOT S_EBELN[]...

ENDFORM. " VALIDATE_PD_NUM

&----

*& Form VALIDATE_VEN_NUM

&----

Subroutine to validate Vendor Number

----

There are no interface parameters to be passed to this subroutine.

----

FORM VALIDATE_VEN_NUM .

IF NOT S_LIFNR[] IS INITIAL.

SELECT LIFNR " Vendor Number

FROM LFA1

INTO W_LIFNR

UP TO 1 ROWS

WHERE LIFNR IN S_LIFNR.

ENDSELECT.

IF SY-SUBRC NE 0.

CLEAR SSCRFIELDS-UCOMM.

MESSAGE E002(M8) WITH W_SPACE.

ENDIF. " IF SY-SUBRC NE 0

ENDIF. " IF NOT S_LIFNR[]...

ENDFORM. " VALIDATE_VEN_NUM

&----

*& Form VALIDATE_PUR_GRP

&----

Subroutine to validate the Purchase Group

----

There are no interface parameters to be passed to this subroutine.

----

FORM VALIDATE_PUR_GRP .

IF NOT S_EKGRP[] IS INITIAL.

SELECT EKGRP " Purchase Group

FROM T024

INTO W_EKGRP

UP TO 1 ROWS

WHERE EKGRP IN S_EKGRP.

ENDSELECT.

IF SY-SUBRC NE 0.

CLEAR SSCRFIELDS-UCOMM.

MESSAGE E622(M8) WITH W_SPACE.

ENDIF. " IF SY-SUBRC NE 0

ENDIF. " IF NOT S_EKFRP[]...

ENDFORM. " VALIDATE_PUR_GRP

&----

*& Form FILL_VARIANT

&----

Subroutine to fill the Variant Structure

----

There are no interface parameters to be passed to this subroutine

----

FORM FILL_VARIANT .

Filling the Variant structure

W_VARIANT-REPORT = SY-REPID.

W_VARIANT-USERNAME = SY-UNAME.

ENDFORM. " FILL_VARIANT

Regards,

pavan

Re: OBJECT-ORIENTED ABAP

Former Member — Mon, 16 Jul 2007 11:04:31 GMT

What is Object Orientation?

In the past, information systems used to be defined primarily by their functionality: data and functions were kept separate and linked together by means of input and output relations.

The object-oriented approach, however, focuses on objects that represent abstract or concrete things of the real world. These objects are first defined by their character and their properties which are represented by their internal structure and their attributes (data). The behaviour of these objects is described by methods (functionality).

Objects form a capsule which combines the character to the respective behaviour. Objects should enable programmers to map a real problem and its proposed software solution on a one-to-one basis.

Typical objects in a business environment are, for example, ‘Customer’, ‘Order’, or ‘Invoice’. From Release 3.1 onwards, the Business Object Repository (BOR) of SAP Web Applicaton Server ABAP has contained examples of such objects. The BOR object model will be integrated into ABAP Objects in the next Release by migrating the BOR object types to the ABAP class library.

A comprehensive introduction to object orientation as a whole would go far beyond the limits of this introduction to ABAP Objects. This documentation introduces a selection of terms that are used universally in object orientation and also occur in ABAP Objects. In subsequent sections, it goes on to discuss in more detail how these terms are used in ABAP Objects. The end of this section contains a list of further reading, with a selection of titles about object orientation.

Objects
Objects are instances of classes. They contain data and provides services. The data forms the attributes of the object. The services are known as methods (also known as operations or functions). Typically, methods operate on private data (the attributes, or state of the object), which is only visible to the methods of the object. Thus the attributes of an object cannot be changed directly by the user, but only by the methods of the object. This guarantees the internal consistency of the object.

Classes
Classes describe objects. From a technical point of view, objects are runtime instances of a class. In theory, you can create any number of objects based on a single class. Each instance (object) of a class has a unique identity and its own set of values for its attributes.

Object References
In a program, you identify and address objects using unique object references. Object references allow you to access the attributes and methods of an object.

In object-oriented programming, objects usually have the following properties:

Encapsulation
Objects restrict the visibility of their resources (attributes and methods) to other users. Every object has an interface, which determines how other objects can interact with it. The implementation of the object is encapsulated, that is, invisible outside the object itself.

Inheritance
You can use an existing class to derive a new class. Derived classes inherit the data and methods of the superclass. However, they can overwrite existing methods, and also add new ones.

Polymorphism
Identical (identically-named) methods behave differently in different classes. In ABAP Objects, polymorphism is implemented by redefining methods during inheritance and by using constructs called interfaces.

Uses of Object Orientation
Below are some of the advantages of object-oriented programming:

· Complex software systems become easier to understand, since object-oriented structuring provides a closer representation of reality than other programming techniques.

· In a well-designed object-oriented system, it should be possible to implement changes at class level, without having to make alterations at other points in the system. This reduces the overall amount of maintenance required.

· Through polymorphism and inheritance, object-oriented programming allows you to reuse individual components.

· In an object-oriented system, the amount of work involved in revising and maintaining the system is reduced, since many problems can be detected and corrected in the design phase.

Achieving these goals requires:

· Object-oriented programming languages

Object-oriented programming techniques do not necessarily depend on object-oriented programming languages. However, the efficiency of object-oriented programming depends directly on how object-oriented language techniques are implemented in the system kernel.

· Object-oriented tools

Object-oriented tools allow you to create object-oriented programs in object-oriented languages. They allow you to model and store development objects and the relationships between them.

· Object-oriented modeling

The object-orientation modeling of a software system is the most important, most time-consuming, and most difficult requirement for attaining the above goals. Object-oriented design involves more than just object-oriented programming, and provides logical advantages that are independent of the actual implementation.

This section of the ABAP User’s Guide provides an overview of the object-oriented extension of the ABAP language. We have used simple examples to demonstrate how to use the new features. However, these are not intended to be a model for object-oriented design. More detailed information about each of the ABAP Objects statements is contained in the keyword documentation in the ABAP Editor. For a comprehensive introduction to object-oriented software development, you should read one or more of the titles listed below.

ABAP supports a hybrid programming model. You can use an object-oriented ("OO") programming model based on classes and interfaces, and you can use the more classic procedural and event-driven programming model based on function modules, subroutines, dialog modules, and event blocks. Both models can be used in parallel. You can use classes inside classic processing blocks or you can call classic procedures from methods. In ABAP Objects, SAP has implemented a cleanup of the ABAP language. Within the scope of this language cleanup, stricter syntax checks are performed in classes that restrict the usage of obsolete language elements.

Object orientation in ABAP is an extension of the ABAP language that makes available the advantages of object-oriented programming, such as encapsulation, interfaces, and inheritance. This helps to simplify applications and make them more controllable.

ABAP Objects is fully compatible with the existing language, so you can use existing statements and modularization units in programs that use ABAP Objects, and can also use ABAP Objects in existing ABAP programs.

Check these links

/people/thomas.jung3/blog/2005/09/08/oo-abap-dynpro-programming
/people/ravikumar.allampallam/blog/2005/02/11/abap-oo-in-action

This is good for beginners

/people/sap.user72/blog/2005/05/10/a-small-tip-for-the-beginners-in-oo-abap

Reward all helpfull answers

Regards

Pavan

Re: OBJECT-ORIENTED ABAP

Former Member — Mon, 16 Jul 2007 11:10:45 GMT

Hi,

go through the following limks...

http://help.sap.com/saphelp_47x200/helpdata/en/ce/b518b6513611d194a50000e8353423/content.htm

Classes

http://help.sap.com/saphelp_47x200/helpdata/en/c3/225b5c54f411d194a60000e8353423/content.htm

Object Handling

http://help.sap.com/saphelp_47x200/helpdata/en/c3/225b5f54f411d194a60000e8353423/content.htm

Declaring and Calling methods

http://help.sap.com/saphelp_47x200/helpdata/en/08/d27c03b81011d194f60000e8353423/content.htm

Inheritance.

http://help.sap.com/saphelp_47x200/helpdata/en/dd/4049c40f4611d3b9380000e8353423/content.htm

Interfaces.

http://help.sap.com/saphelp_47x200/helpdata/en/c3/225b6254f411d194a60000e8353423/content.htm

Trigerring and handling Events

http://help.sap.com/saphelp_47x200/helpdata/en/71/a8a77955bc11d194aa0000e8353423/content.htm

****do reward if usefull

vijay

Re: OBJECT-ORIENTED ABAP

Former Member — Tue, 21 Aug 2007 09:16:35 GMT

hi Abhi,

most of the information about oops is given by other users .

so i wud like to share some base structure of oops

in oops we make use of class.

this class can be local class or goble class

goble class in define through tranction SE24.

and can be used goblely.

local class is build in se38.

example of the same

class zcl_emp DEFINITION.

public section.

types : begin of t_emp,

no type i,

name type string,

end of t_emp.

methods:

constructor

importing zemp_no type i

zemp_name type string,

display_employee.

class-methods:

display_no_of_employee.

protected section.

class-data:g_no_of_employee type i.

private section.

data: g_employee type t_emp.

endclass.

class zcl_emp implementation.

method constructor.

g_employee-no = zemp_no.

g_employee-name = zemp_name.

g_no_of_employee = g_no_of_employee + 1.

endmethod.

method display_employee.

write:/'employee', g_employee-no ,g_employee-name.

endmethod.

method display_no_of_employee.

write:/ 'no of employee is', g_no_of_employee .

endmethod.

endclass.

*******

include zas_class.

data: g_empl1 type ref to zcl_emp, " declaration of object.

g_empl2 type ref to zcl_emp.

start-of-selection.

*initialization.

create object g_empl1

exporting zemp_no = 1

zemp_name = 'james'.

create object g_empl2

exporting zemp_no = 2

zemp_name = 'bond'.

call method g_empl1->display_employee.

call method g_empl2->display_employee.

call method g_empl2->display_no_of_employee.

hope this will help you

anuj

Re: OBJECT-ORIENTED ABAP

Former Member — Tue, 21 Aug 2007 09:31:09 GMT

Hi,

check the below links lot of info and examples r there

http://www.sapgenie.com/abap/OO/index.htm

http://www.geocities.com/victorav15/sapr3/abap_ood.html

http://www.brabandt.de/html/abap_oo.html

Check this cool weblog:

/people/thomas.jung3/blog/2004/12/08/abap-persistent-classes-coding-without-sql

http://help.sap.com/saphelp_nw04/helpdata/en/c3/225b6254f411d194a60000e8353423/frameset.htm

http://www.sapgenie.com/abap/OO/

http://www.sapgenie.com/abap/OO/index.htm

http://help.sap.com/saphelp_nw04/helpdata/en/c3/225b5654f411d194a60000e8353423/content.htm

http://www.esnips.com/doc/375fff1b-5a62-444d-8ec1-55508c308b17/prefinalppt.ppt

http://www.esnips.com/doc/2c76dc57-e74a-4539-a20e-29383317e804/OO-abap.pdf

http://www.esnips.com/doc/5c65b0dd-eddf-4512-8e32-ecd26735f0f2/prefinalppt.ppt

http://www.allsaplinks.com/

http://www.sap-img.com/

http://www.sapgenie.com/

http://help.sap.com

http://www.sapgenie.com/abap/OO/

http://www.sapgenie.com/abap/OO/index.htm

http://www.sapgenie.com/abap/controls/index.htm

http://www.esnips.com/doc/2c76dc57-e74a-4539-a20e-29383317e804/OO-abap.pdf

http://www.esnips.com/doc/0ef39d4b-586a-4637-abbb-e4f69d2d9307/SAP-CONTROLS-WORKSHOP.pdf

http://www.sapgenie.com/abap/OO/index.htm

http://help.sap.com/saphelp_erp2005/helpdata/en/ce/b518b6513611d194a50000e8353423/frameset.htm

http://www.sapgenie.com/abap/OO/

these links

http://help.sap.com/saphelp_47x200/helpdata/en/ce/b518b6513611d194a50000e8353423/content.htm

For funtion module to class

http://help.sap.com/saphelp_47x200/helpdata/en/c3/225b5954f411d194a60000e8353423/content.htm

for classes

http://help.sap.com/saphelp_47x200/helpdata/en/c3/225b5c54f411d194a60000e8353423/content.htm

for methods

http://help.sap.com/saphelp_47x200/helpdata/en/08/d27c03b81011d194f60000e8353423/content.htm

for inheritance

http://help.sap.com/saphelp_47x200/helpdata/en/dd/4049c40f4611d3b9380000e8353423/content.htm

for interfaces

http://help.sap.com/saphelp_47x200/helpdata/en/c3/225b6254f411d194a60000e8353423/content.htm

For Materials:

1) http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCABA/BCABA.pdf -- Page no: 1291

2) http://esnips.com/doc/5c65b0dd-eddf-4512-8e32-ecd26735f0f2/prefinalppt.ppt

3) http://esnips.com/doc/2c76dc57-e74a-4539-a20e-29383317e804/OO-abap.pdf

4) http://esnips.com/doc/0ef39d4b-586a-4637-abbb-e4f69d2d9307/SAP-CONTROLS-WORKSHOP.pdf

5) http://esnips.com/doc/92be4457-1b6e-4061-92e5-8e4b3a6e3239/Object-Oriented-ABAP.ppt

6) http://esnips.com/doc/448e8302-68b1-4046-9fef-8fa8808caee0/abap-objects-by-helen.pdf

7) http://esnips.com/doc/39fdc647-1aed-4b40-a476-4d3042b6ec28/class_builder.ppt

😎 http://www.amazon.com/gp/explorer/0201750805/2/ref=pd_lpo_ase/102-9378020-8749710?ie=UTF8

1) http://www.erpgenie.com/sap/abap/OO/index.htm

2) http://help.sap.com/saphelp_nw04/helpdata/en/ce/b518b6513611d194a50000e8353423/frameset.htm

Regards,

Priyanka.