How write a class in abap

Hi abap experts,
I want to write a class with abap, a simple calculator class for example,
how can I start to write..
The steps are what ?
Thanks.

Hi
Defining class
A class is a set of objects that have the same structure and the same behavior. A class is
therefore like a blueprint, in accordance with which all objects in that class are created.
The components of the class
are defined in the definition
part. The components are
attributes, methods, events,
constants, types, and
implemented interfaces. Only
methods are implemented in
the implementation part.
<b>CLASS CLASSNAME DEFINATION.
ENDCLASS
CLASS CLASSNAME IMPLEMATION
ENDCLASS</b>
The CLASS statement cannot be nested, that is, you cannot define a class within a class.
REWARD IF USEFULL

Similar Messages

How to find classes in ABAP

Hi experts,
In java it is easy to find related classes for our requirement based on package and related methods by using API.But how to find that these are the classes are existing for this particular requirement in ABAP.In
se24 we can find existed classes but can not identified properly for our requirement.
Can anybody help me in this regard.
Thanks in Advance.

Hi,
As far as I know, SE24/se84 is the place where we can find the information about the global classes available in the system, to find the appropriate class for your requirement, you need to search using the wild card search and go thro' the documentation provided by SAP as SAP has provided a very good documentation(In most of the cases) on classes.
Rgds,

How to use classes in ABAP report

I have classes
1. CL_HRRCF_CANDIDATE_BUPA_BL:-
to get the name of the candiidate
to get the add of the candiidate
to get the telephone no of the candiidate
2. CL_HRRCF_CANDIDATE_INFOTYPE_BL
to get the education data of the candiidate
but i don't know hw to get data from these classes,
so pls help me outwith an example
thanks.

Try this sample code,
DATA: lr_cdcy                    TYPE REF TO cl_hrrcf_candidacy_bl,
        lr_cand                    TYPE REF TO cl_hrrcf_candidate_bupa_bl,
        stru_requisitions          TYPE if_componentcontroller=>element_requisitions ,
        lt_h_cdcy_list             TYPE rcf_t_list_candidacies_x,
        ls_h_cdcy_list             TYPE rcf_s_list_candidacies_x,
        lt_cdcy_list               TYPE if_componentcontroller=>elements_candidate,
        ls_cdcy_list               TYPE if_componentcontroller=>element_candidate,
        lt_addr                    TYPE rcf_t_addressdata_bp,
        ls_addr                    TYPE rcf_s_addressdata_bp,
        lt_email                   TYPE rcf_t_emaildata_bp,
        ls_email                   TYPE rcf_s_emaildata_bp.
get all declared attributes
parent_element->get_static_attributes(
    IMPORTING
      static_attributes = stru_requisitions ).
CALL METHOD cl_hrrcf_candidacy_bl=>get_instance
    RECEIVING
      return = lr_cdcy.
CALL METHOD cl_hrrcf_candidate_bupa_bl=>get_instance
    RECEIVING
      return = lr_cand.
Hole Kandidatur-Informationen der Kandidaten
TRY.
      lr_cdcy->get_candidacy_list_x(
        EXPORTING
          ps_req_hrobject = stru_requisitions-hrobject
   ps_cand_hrobject =
   ps_appl_hrobject =
   p_exclude_draft = 'x'
        IMPORTING
          pt_candidacies_x = lt_h_cdcy_list
    CATCH cx_hrrcf .
ENDTRY.
Ergänzen der Informationen mit BusinessPartner-Infos
LOOP AT lt_h_cdcy_list INTO ls_h_cdcy_list.
    TRY.
        lr_cand->get_contact_data(
          EXPORTING
            ps_cand_hrobject = ls_h_cdcy_list-cand_hrobject
          IMPORTING
            pt_addressdata   = lt_addr
   pt_telefondata   =
   pt_faxdata       =
            pt_emaildata     = lt_email
      CATCH cx_hrrcf .
    ENDTRY.
    READ TABLE lt_addr INDEX 1 INTO ls_addr.
    READ TABLE lt_email INDEX 1 INTO ls_email.
    MOVE-CORRESPONDING ls_h_cdcy_list TO ls_cdcy_list.
    ls_cdcy_list-postcode1 = ls_addr-postl_cod1.
    ls_cdcy_list-city1 = ls_addr-city.
    ls_cdcy_list-email = ls_email-e_mail.
    APPEND ls_cdcy_list TO lt_cdcy_list.
ENDLOOP.
CALL METHOD node->bind_table
    EXPORTING
      new_items = lt_cdcy_list.
ENDMETHOD.
Regards,
Pavan

What is meant by Local Class and how we can create local classes in abap?

Hi Friends
what is meant by Local Class and how we can create local classes in abap?
Regards,
Sree

Hi
Local classes are the classes which we declare and use using the SE38 ABAP editor
Global classes are the classes which we find in SE24 and call the methods of them into our program.
see the sample code
REPORT zs_class.
SELECTION SCREEN
SELECTION-SCREEN BEGIN OF BLOCK b1 WITH FRAME.
PARAMETERS:p_var TYPE i,
p_var1 TYPE i.
SELECTION-SCREEN END OF BLOCK b1.
CLASS d_class DEFINITION
CLASS d_class DEFINITION.
PUBLIC SECTION.
METHODS:
add,
sub.
PROTECTED SECTION.
DATA : var2 TYPE i.
ENDCLASS. "d_class DEFINITION
CLASS d_class IMPLEMENTATION
CLASS d_class IMPLEMENTATION.
METHOD add.
var2 = p_var + p_var1.
WRITE:/ var2.
ENDMETHOD. "add
METHOD sub.
var2 = p_var - p_var1.
WRITE:/ var2.
ENDMETHOD. "sub
ENDCLASS. "d_class IMPLEMENTATION
START-OF-SELECTION
START-OF-SELECTION.
DATA: obj TYPE REF TO d_class.
CREATE OBJECT: obj .
CALL METHOD: obj->add,
Regards
Anji

How do i write UTF convertor in ABAP sample code for ABAP please

How do i write UTF convertor in ABAP
Regards,
Jagrut BharatKumar Shkla

you want to convert a string to utf format?
try this code
app_type = 'text/xml; charset=utf-8'.
call function 'SCMS_STRING_TO_XSTRING'
exporting
    text     = xml_string
    mimetype = app_type
importing
    buffer   = xl_content.
concatenate cl_abap_char_utilities=>byte_order_mark_utf8
             xl_content
             into xl_content in byte mode.

Urgent: how to import or transport abap class from dev to q

How to import/transport custom abap class from dev to q.
Any suggestions points will be awarded.
Thanks in advance.
MK

hi M K,
try SE24, your class, and go to menu 'Go to' -> object directory entry,
click pencil icon and give your package name, will raise request.
SE10 to release and STMS from prod to import.
hope this helps.

How To write Immutable Class

Hi All
can We write Immutable Class. If yes Then How.
In my View It can be through final Keyword.

An immutable class is simply a class whose internal
data can't be changed once it's created. All fields
will be declared private and no externally accessible
methods will change them. That's all that's required.
It's probably a good idea to declare the fields in
the class as final, but it's not essential.
Instead of mutator methods you typically have methods
that create a new instance with some part of the data
changed.Note that "final" has two meanings:
1) a field must be set inside the constructor and nowhere else
2) a method / class cannot be inherited
You MUST forbid inheritance, or a subclass might override the methods and reenable mutability. This would have really nasty sideeffects.

Interactive Scripting Editor (ISE) how to write a class for an action?

Hi - I need to write a class for an action in the interactive scripting editor. The class will create a new case (case management) and return the number. I have created a class with a method that does this and has been fully tested but we cannot get it to work as part of an action within the ISE. Are there any guidelines for writing classes for the ISE. Or has anyone done this? Do I need a super class? I have searched every where but can find nothing on this. Many thanks.

Hi Nigel,
I am also looking for the answer to this. Please let me know when you find a solution.
Kind Regards,
Andrew Griffin.

Why and how to use events in abap objects

Dear all,
Please explain me why and how to use events in abap objects with real time example
regards
pankaj giri

Hi Pankaj,
I will try to explain why to use events... How to use is a different topic.. which others have already answered...
This is same from your prev. post...
Events :
Technically speaking :
" Events are notifications an object receives from, or transmits to, other objects or applications. Events allow objects to perform actions whenever a specific occurrence takes place. Microsoft Windows is an event-driven operating system, events can come from other objects, applications, or user input such as mouse clicks or key presses. "
Lets say you have an ALV - An editable one ...
Lats say - Once you press some button you want some kind of validation to be done.
How to do this ?
Raise an Event - Which is handled by a method and write the validation code.
Now you might argue, that I can do it in this way : Capture the function code - and call the validate method.
Yes, in this case it can be done.. But lets say .. you change a field in the ALV and you want the validation to be done as soon as he is done with typing.
Where is the function code here ? No function code... But there is an event here - The data changed event.
So you can raise a data changed event that can be handled and will do the validation.
It is not user friendly that you ask the user to press a button (to get the function code) for validation each time he enters a data.
The events can be raised by a system, or by a program also. So in this case the data changed event is raised by a system that you can handle.
Also, Lets say on a particular action you want some code to trigger. (You can take the same example of validation code). In this case the code to trigger is in a separate class. The object of which is not available here at this moment. (This case happens very frequently).
Advantage with events : Event handlers can be in a separate class also.
e.g : In the middle of some business logic .. you encounter a error. You want to send this information to the UI (to user - in form of a pop up) and then continue with some processing.
In many cases - A direct method call to trigger the pop up is not done. Because (in ideal cases) the engine must not interact with UI directly - Because the UI could be some other application - like a windows UI but the error comes from some SAP program.
So - A event is raised from the engine that is handled in the UI and a pop up is triggered.
Here -- I would have different classes (lets say for different Operating Systems). And all these classes must register to the event ERROR raised in application.
And these different classes for different Operation systems will have different code to raise a pop-up.
Now you can imagine : If you coded a pop-up for Windows (in your application logic) .. it will not work for Mac or Linux. But of you raise a event.. that is handled separately by a different UI classes for Win, Linux or Mac they will catch this event and process accordingly.
May be I complicated this explanation .... but I couldn't think of a simpler and concrete example.
Cheers.
Varun.

How to call Webservice in abap Program

Hi Guys,
How can i call a abap webservice located in another server(CRM) in Bpc BADI.Is this web service is thing is possible??

Hi,
For calling a web service first you have to Create Proxy object using web service URL or WSDL file.
and create logical port for that URL.
This will generate Class and method in your system.
After that you can use this class and method to call this web service.
Regards,
Arpit

How to make output of ABAp query interactive(drill down)..?

Hi All,
I have developed one ABAP query which shows the output in which there is a coloumm 'order number'.
I want to make this coloumn interactive ,that means after double clicking on any row of this colomn ,it should go to transaction KO02.
Where do i have to write the code in ABAP query ?
I am very new to ABAP query..this is the first query i have deloped till now.
points will be rewarded.
Thnks in advance.
Regards,
Sanjay.

<b>The below sample code is one such example of Drill down reporting...
Make the necessary modifications, change the statement CALL TRANSACTION to whatever you want to CALL. Proceed further.</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.
          ENDIF.                       " IF SY-SUBRC EQ 0.
      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.
      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

How to do coding in abap-query

Hi friends,
Please help me how to write the coding in abap-query.
Regards,
Bhavani

hI
There are certain exit points available in the query, these can be accessed in SQ02 - Infoset editor. Click 'Extras', then the 'Coding' tab. There is a drop down to access different coding sections, e.g. DATA, GET, etc.
It is not always clear where and when they execute so you may need to experiment with some 'break-point' statements to start with, run the query to find out where the breaks are then go back to SQ02 to enter some code at that section.
http://www.thespot4sap.com/Articles/SAP_ABAP_Queries_FunctionalAreas_LogicalDB.asp

How to call Biztalk through ABAP-DYNPRO

Hi All ,
I want to call a function module which in BIZTALK Server through
ABAP-DYNPRO ( by service call) . for this I require Destination details ( in service call ) .
Can anyone please send me the Destination details or the approach to follow for calling the Biztalk ?
Thanks in advance ..
Regards
Rahul

Run a search on Web service calls from WDA.
This topic has been addressed on numerous occassions.
You can call BIZ-TALK using a web service.
You could also call it using straight HTTP .
There are classes in ABAP to allow you to write an HTTP client app if required.
If possible go the Webservice route.
IE have you Biztalk guy generate a WSDL for the call.
The follow instructions on numerous threads on calling web services.
Cheers
Phil.

How we can see the abap memory data

How we can see the abap-memory data
fine the code below
import lsind
         report_title
         table_name
         report_field
         change_display
         show_hide
         conversion_exits
         table_description
         form_program
         select_form
         update_form
         line_size
         line_count
         records[]
         fields[]
         header_fields[]
         select_fields[]
         xrep[]
         from memory id 'LZUT5U11'.
Regards
santhosh
mail-id : [email protected]

Dear Santosh,
ABAP MEMORY:
A logical memory model illustrates how the main memory is distributed from the view of executable programs. A distinction is made here between external sessions and internal sessions .
An external session is usually linked to an R/3 window. You can create an external session by choosing System/Create session, or by entering /o in the command field. An external session is broken down further into internal sessions. Program data is only visible within an internal session. Each external session can include up to 20 internal sessions (stacks).
Every program you start runs in an internal session.
All "squares" with rounded "corners" displayed in the status diagram represent a set of data objects in the main memory.
The data in the main memory is only visible to the program concerned.
CALL TRANSACTION and SUBMIT AND RETURN open a new internal session that forms a new program context. The internal sessions in an external session form a memory stack. The new session is added to the top of the stack.
When a program has finished running, the top internal session in the stack is removed, and the calling program resumes processing.
The same occurs when the system processes a LEAVE PROGRAM statement.
LEAVE TO TRANSACTION removes all internal sessions from the stack and opens a new one containing the program context of the calling program.
The ABAP memory is initialized after the program is called. In other words, you cannot transfer any data to a program called with LEAVE TO TRANSACTION via the ABAP memory.
SUBMIT replaces the internal session of the program performing the call with the internal session of the program that has been called. The new internal session contains the program context of the called program with which it is performed.
When a function module is called, the following steps are executed:
A check is made to establish whether your program has called a function module of the same function group previously.
If this is not the case, the system loads the associated function group to the internal session of the calling program as an additional program group. This initializes its global data.
If your program used a function module of the same function group before the current call, the function module that you have called up at present can access the global data of the function group. The function group is not reloaded.
Within the internal session, all of the function modules that you call from the same group access the global data of that group.
If, in a new internal session, you call a function module from the same function group as in internal session 1, a new set of global data is initialized for the second internal session. This means that the data accessed by function modules called in session 2 may be different from that accessed by the function modules in session 1.
You can call function modules asynchronously as well as synchronously. To do so, you must extend the function module call using the addition STARTING NEW TASK ''. Here, '' is a symbolic name in the calling program that identifies the external session, in which the called program is executed.
Function modules that you call using the addition STARTING NEW TASK '' are executed independently of the calling program. The calling program is not interrupted.
To make function modules available for local asynchronous calls, you must identify them as executable remotely (processing type: Remote-enabled module).
There are various ways of transferring data between programs that are running in different program contexts (internal sessions). You can use:
(1) The interface of the called program (standard selection screen, or interface of a
subroutine, function module, or dialog module)
(2) ABAP memory
(3) SAP memory
(4) Database tables
(5) Local files on your presentation server.
For further information about transferring data between an ABAP program and your presentation server, refer to the documentation for the function modules WS_UPLOAD and WS_DOWNLOAD.
Function modules have an interface, which you can use to pass data between the calling program and the function module itself (there is also a comparable mechanism for ABAP subroutines). If a function module supports RFC, certain restrictions apply to its interface.
If you are calling an ABAP program that has a standard selection screen, you can pass values to the input fields. There are two options here:
By using a variant of the standard selection screen in the program call
By passing actual values for the input fields in the program call
If you want to call a report program without displaying its selection screen (default setting), but still want to pass values to its input fields, there is a variety of techniques that you can use.
The WITH addition allows you to assign values to the parameters and select-options fields on the standard selection screen.
If the selection screen is to be displayed when the program is called, use the addition: VIA SELECTION-SCREEN.
Use the pattern button in the ABAP Editor to insert a program call via SUBMIT. The structure shows you the names of data objects that you can complete with the standard selection screen.
For further information on working with variants and further syntax variants for the WITH addition, see the key word documentation in the ABAP Editor for SUBMIT.
You can use SAP memory and ABAP memory to pass data between different programs.
The SAP memory is a user-specific memory area for storing field values. It is available in all of the open sessions in a user's terminal session, and is reset when the terminal session ends. You can use its contents as default values for screen fields. All external sessions can access SAP memory. This means that it is only of limited use for passing data between internal sessions.
The ABAP memory is also user-specific, and is local to each external session. You can use it to pass any ABAP variables (fields, structures, internal tables, complex objects) between the internal sessions of a single external session.
Each external session has its own ABAP memory. When you end an external session (/i in the command field), the corresponding ABAP memory is released automatically.
To copy a set of ABAP variables and their current values (data cluster) to the ABAP memory, use the EXPORT TO MEMORY ID statement. The (up to 32 characters) is used to identify the different data clusters.
If you repeat an EXPORT TO MEMORY ID statement to an existing data cluster, the new data overwrites the old.
To copy data from ABAP memory to the corresponding fields of an ABAP program, use the IMPORT FROM MEMORY ID statement.
The fields, structures, internal tables, and complex objects in a data cluster in ABAP memory must be declared identically in both the program from which you exported the data and the program into which you import it.
To release a data cluster, use the FREE MEMORY ID statement.
You can import just parts of a data cluster with IMPORT, since the objects are named in the cluster.
In the SAP memory, you can define memory areas (SET/GET parameters, or parameter IDs), which you can then address by a name of up to 20 characters.
You can fill these memory areas either using the contents of input/output fields on screens, or using the ABAP statement:
SET PARAMETER ID '' FIELD .
The memory area with the name now has the value .
You can use the contents of a memory area to display a default value in an input field on a screen.
You can also read the memory areas from the SAP memory using the ABAP statement GET PARAMETER ID FIELD . The field then contains the value from parameter .
The link between an input/output field and a memory area in SAP memory is inherited from the data element on which the field is based. You can enable the set parameter or get parameter attributes in the input/output field attributes.
Once you have set the Set parameter attribute for an input/output field, you can fill it with default values from SAP memory. This is particularly useful for transactions that you call from another program without displaying the initial screen. For this purpose, you must activate the Set parameter functionality for the input fields of the first screen of the transaction.
You can:
(1) Copy the data that is to be used for the first screen of the transaction to be called to the parameter ID in the SAP memory. To do so, use the statement SET PARAMETER immediately before calling the transaction.
(2) Start the transaction using CALL TRANSACTION or LEAVE TO
TRANSACTION . If you do not want to display the initial screen, use the AND
SKIP FIRST SCREEN addition.
(3) The system program that starts the transaction fills the input fields that do not already have default values and for which the Get parameter attribute has been set with values from SAP memory.
The Technical information for the input fields in the transaction you want to call contains the names of the parameter IDs that you need to use.
Parameter IDs should be entered in table TPARA. This happens automatically if you create them via the Object navigator.
Programs that you call using the statements SUBMIT , LEAVE TO TRANSACTION , SUBMIT AND RETURN, or CALL TRANSACTION run in their own SAP LUW, and update requests receive their own update key.
When you use SUBMIT and LEAVE TO TRANSACTION , the SAP LUW of the calling program ends. If no COMMIT WORK statement occurred before the program call, the update requests in the log table remain incomplete and cannot be processed. They can no longer be executed. The same applies to inline changes that you make using PERFORM … ON COMMIT.
Data that you have written to the database using inline changes is committed the next time a new screen is displayed.
If you use SUBMIT AND RETURN or CALL TRANSACTION to insert a program and then return to the calling program, the SAP LUW of the calling program is resumed when the called program ends. The LUW processing of calling and called programs is independent.
In other words, inline changes are committed the next time a new screen is displayed. Update requests and calls using PERFORM ... ON COMMIT require an independent COMMIT WORK statement in the SAP LUW in which they are running.
Function modules run in the same SAP LUW as the program that calls them.
If you call transactions with nested calls, each transaction needs its own COMMIT WORK, since each transaction maps its own SAP LUW.
The same applies to calling executable programs, which are called using SUBMIT AND RETURN.
The statement CALL TRANSACTION allows you to
Shorten the user dialog when calling using CALL TRANSACTION USING .
Determine the type of update (asynchronous, local, or synchronous) for the transaction called. For this purpose, use the addition CALL TRANSACTION USING UPDATE 'update_mode', where update_mode can have the values a (asynchronous), L (local), or S (synchronous).
Combining the two options enables you to call several transactions in sequence (logical chain), to reduce their screen sequence, and to postpone processing of the SAP LUW 2 until processing of the SAP LUW 1 has been completed.
When you call a function module asynchronously using the CALL FUNCTION STARTING NEW TASK ' ' statement, it runs in its own SAP LUW.
Programs that are executed with a SUBMIT AND RETURN or CALL
TRANSACTION statement starts their own LUW processing. You can use these to perform nested (complex) LUW processing.
You can use function modules as modularization units within an SAP LUW.
Function modules that are called asynchronously are suitable for programs that allow parallel processing of some of their components.
All techniques are suitable for including programs with purely display functions.
Note that a function module called with CALL FUNCTION STARTING NEW TASK is executed as a new logon. It, therefore, sees a separate SAP memory area. You can use the interface of the function module for data transfers.
Example: In your program, you want to call a display transaction that is displayed in a separate window (amodal). To do so, you encapsulate the transaction call in a function module, which you set as to Remote-enabled module. You use the function module interface to accept values that you write to the SAP memory. You then call up the transaction in the function module using CALL TRANSACTION AND SKIP FIRST SCREEN. You call the function module itself asynchronously.
Type ‘E' locks for nested program calls may be requested more than once from the same object. This behavior can be described as follows:
Lock entries from function modules called synchronously increment the cumulative counter, And are therefore successful.
Lock entries from programs called with CALL TRANSACTION or SUBMIT
AND
RETURN is refused. The object to be locked by the called program is displayed as already Locked by another user.
Programs that you call using SUBMIT or LEAVE TO TRANSACTION cannot come into conflict with lock entries from the calling program, since the old program ends when the call is made. When a program ends, the system deletes all of the lock entries that it had set.
Lock requests belonging to the same user from different R/3 windows or logons are treated as lock requests from other users.
Regards,
Rajesh.
Please reward points if found helpful.

Can u explain me how to work with OOPs ABAP

Hi,
Can u explain me how to work with OOPS Abap, If possible pls send me some sample programs regarding OOps concept used in Realtime.
Thanks.

hii,
Please check this online document (starting page 1291).
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCABA/BCABA.pdf
Also check this links as well.
http://help.sap.com/saphelp_nw2004s/helpdata/en/ce/b518b6513611d194a50000e8353423/frameset.htm
http://www.sapgenie.com/abap/OO/
http://www.futureobjects.de/content/intro_oo_e.html
http://www.sap-img.com/abap/business-add-in-you-need-to-understand-abap-oo-interface-concept.htm
/people/ravikumar.allampallam/blog/2005/02/11/abap-oo-in-action
What is Object Orientation?
Object orientation (OO), or to be more precise, object-oriented programming, is a problem-solving method in which the software solution reflects objects in the real world.
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
An object is a section of source code that contains 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.
Polymorphism
Identical (identically-named) methods behave differently in different classes. Object-oriented programming contains constructions called interfaces. They enable you to address methods with the same name in different objects. Although the form of address is always the same, the implementation of the method is specific to a particular class.
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.
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
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
/people/thomas.jung3/blog/2004/12/08/abap-persistent-classes-coding-without-sql
/people/sap.user72/blog/2005/05/10/a-small-tip-for-the-beginners-in-oo-abap
/people/ravikumar.allampallam/blog/2005/02/11/abap-oo-in-action
/people/thomas.jung3/blog/2005/09/08/oo-abap-dynpro-programming
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 basic stuff......
abap oops
http://esnips.com/doc/5c65b0dd-eddf-4512-8e32-ecd26735f0f2/prefinalppt.ppt
http://esnips.com/doc/2c76dc57-e74a-4539-a20e-29383317e804/OO-abap.pdf
http://esnips.com/doc/0ef39d4b-586a-4637-abbb-e4f69d2d9307/SAP-CONTROLS-WORKSHOP.pdf
http://esnips.com/doc/92be4457-1b6e-4061-92e5-8e4b3a6e3239/Object-Oriented-ABAP.ppt
http://esnips.com/doc/448e8302-68b1-4046-9fef-8fa8808caee0/abap-objects-by-helen.pdf
http://esnips.com/doc/39fdc647-1aed-4b40-a476-4d3042b6ec28/class_builder.ppt
http://help.sap.com/saphelp_nw04/helpdata/en/c3/225b5654f411d194a60000e8353423/frameset.htm
ABAP Business Development and Service Provisioning/ABAP Objects
General information
What is Object Orientation?
some blogs
A small tip for the beginners in OO ABAP
Object Oriented ABAP (OO-ABAP)
and others wiki OO Abap
cheers,
sharad
Edited by: sharad narayan on Apr 29, 2008 12:19 PM

How write a class in abap

Similar Messages

Maybe you are looking for