ABAP Events

What are the different types of ABAP events available? Can you list them in an order & give an example using all the events in a single program
Regards,
Kiran

Hi,
Classical Report Events:
initialization
at selection-screen
start-of -selection
top-of-page
end-of-page
end-of-selection
For Drill down Reports:
initialization
at selection-screen
start-of -selection
top-of-page
end-of-page
end-of-selection
set pf-status
at pf
top-of-page during line selection
at lineselection
at user-command
First event -
Initialization : triggered when the report is loaded in memory.
At selection-screen output : triggered when the selection screen is loaded in memory before being displayed.
At selection-screen : before leaving the selection screen.
start-of-selection : the first event for displaying the report.
This event keyword defines an event block whose event is triggered by the ABAP runtime environment
when calling the executable program selection screen processing of a selection screen.
In an executable program, all statements that are not declarations,
and are listed before the first explicit processing block, are assigned to this event block.
If the program does not contain an explicitly defined event block START-OF-SELECTION,
these statements form the complete event block START-OF-SELECTION.
If a program contains an explicitly defined event block START-OF-SELECTION,
these statements are added to the beginning of the event block.
If the program contains no explicitly defined event blocks,
these statements form the entire event block START-OF-SELECTION.
end-of-selection : after the start-of-selection is completed.
classiscal report events.
top-of-page : every time a new page is started in the list.
end-of-page : every time the list data reaches the footer region of the page.
interactive report events.
top of page during line selection : top of page event for secondary list.
at line-selection : evey time user dbl-clicks(F2) on the list data.
at pF<key> : function key from F5 to F12 to perform interactive action on the list.
at user-command
http://help.sap.com/saphelp_47x200/helpdata/en/56/1eb6c705ad11d2952f0000e8353423/content.htm
Please reward if useful
Thanks
Sivaparvathi

Similar Messages

  • A structured list with all ABAP events?

    Hi SDN community,
    has anyone of you a structured list with really ALL ABAP events like "INITIALIZATION" or "AT SELECTION-SCREEN OUTPUT" or "AT SELECTION SCREEN ON VALUE-REQUEST FOR xyz" and when they are triggered?
    THAT WOULD BE REALLY AWESOME !!!
    Thank you in advance,
    Marius Klaus
    Moderator message: please search for available information/ABAP documentation before asking.
    Edited by: Thomas Zloch on Oct 19, 2010 3:52 PM

    Hi Jan,
    I went to My WAN----->View all devices----->and i can IP addresses , version , location etc. and no MAC. But if i click on "Export Table" and open the file in excel i can see the list of all devices and their MAC's. So that should be the way we can have list of all devices and their correspoding MAC's.
    Or else i can click on individual device and see the same.
    Regards,
    Kanwal

  • Read internal ABAP Event Registration

    Hi Experts,
    I need to read the internal event registration table of ABAP. Any ideas how to access this?
    Thank you!
    Bodo

    Hi
    I think, for this purpose, system fills internal table or calls methods.
    Use SE30 transaction which can show you processing of internal tables and method calls  within concrete time period in the transactions, programs and function modules.

  • GP callable object waiting for abap event

    Hello expertes,
    I'd like to develop a gp process which contains a callable objects which keeps the process instance waiting until an abap function module send something like an event.
    I don't want to put too much load on the machine and block expensive JCO ressources.
    Does anyone have an idea how to solve this?
    Thanks very much
    Stefan

    Hi Shanto Aloor,
    I tried assigning a default user(using initiation defined) to the process , also tried settting the processor as "initiator", but still not working..
    I have been searching for documentation on this issue , but I couldn´t find anything..
    Any other clue?
    Thanks in advance,
    Marco.

  • Select options in web dynpro ABAP  (Event on_check)

    Hi,
    how can I raise a message in the event-handler method on check for a specifc field out of the Select-Option.
    Best regards,
    Marcus

    Hello,
    Create a new method and call it when you want to show the message.
    METHOD message_handling .
      DATA:
        lr_current_controller TYPE REF TO if_wd_controller,
        lr_message_manager    TYPE REF TO if_wd_message_manager.
      lr_current_controller ?= wd_this->wd_get_api( ).
      lr_message_manager = lr_current_controller->get_message_manager( ).
      lr_message_manager->report_t100_message(
        msgid = iv_msgid
        msgno = iv_msgno
        msgty = iv_msgty
        p1    = iv_p1
        p2    = iv_p2
        p3    = iv_p3
        p4    = iv_p4 ).
    ENDMETHOD.
    In this method, the program show a message that is declared in a mesasge class. If you look at IF_WD_MESSAGE_MANAGER there are other methods to show a message.
    And you can find more information at this blog https://www.sdn.sap.com/irj/sdn/weblogs?blog=/pub/wlg/8402. [original link is broken] [original link is broken] [original link is broken]
    Regards,

  • Sequence of events execution in ABAP reports

    can anyone explain me the Sequence of events execution in ABAP reports

    Ámit Güjärgoüd wrote:
    > search-before-post  Event Must before any posting.Else  <delete-after-input event triggered by moderator> would be trigger and thread may be going to Dump as well without ST22 information(What haapend,How to correct error) available 
    >
    > Edited by: Ámit Güjärgoüd on Oct 7, 2008 7:42 AM
    this looks perfect ABAP event sequence example.

  • Control not going from Adobe Interactive form to ABAP WD Event handler

    Hi
    I am facing an issue with adobe interactive forms and WD ABAP integration.
    The buttons in adobe interactive form when clicked is going round and round and the control is not going to the ABAP code(WD ABAP event handler code whatsoever). I have also set the debugger but the control is not moving to the ABAP code from the adobe interactive form.
    Can anyone help me what can be the issue here and how can I resolve the same?
    Thanks.
    Sid

    Hi Babi,
    In the adobe form layout library Use the Submit(which internally means submit to SAP) button from the Webdynpro Native category.
    Only this button action can connect adobe to web dynpro.
    Whenever we click on this particular button the event will be trigger in the ONsubmit event of interactive form UI element in the webdynpro.There we can write our abap code.Hope this will help you.
    Regards,
    Simi A  M
    Edited by: amsimi on Mar 22, 2011 11:37 AM

  • ABAP Program structure

    Hi,
    I wanted to know the ABAP code structure.while coding we write the code in a sequence,I just wanted to have a layout for the same.
    Thanks.

    Refer the links -
    http://www.sap-img.com/abap/events-related-to-reporting.htm
    http://www.sap-img.com/abap.htm
    Regards,
    Amit

  • Regarding events in reports

    Hi guys,
    i got a doubt in reports on events
    how many events are there in reports.....
    and what's the function of them...can any one help me plzzzz
    regards
    venu

    hi,
    events:
    http://www.sap-img.com/abap/events-related-to-reporting.htm
    Events in Classical Reports
    Initialization.
    At selection-screen.
    At selection-screen on <field>.
    Start-of-selection.
    Top-of-page.
    End-of-page.
    End-of-selection.
    Initialization.
    We can initialize the selection-screen with calculated default values under this event.
    Initialization.
    s_date-high = sy-datum.
    s_date-low = sy-datum - 15.
    Append s_date.
    At selection-screen.
    We can validate all the inputs on selection screen fields under this event.
    At selection-screen.
    If s_carrid-low is initial or s_connid-low is initial or s_date is initial.
    < ... code for validation... >.
    Endif.
    At selection-screen on <field>.
    We can validate a particular field input on selection screen under this event.
    At selection-screen on s_carrid.
    If s_carrid-low < > &#37521;H&#12539;
    <&#12539;code for validation&#12539;
    Endif.
    Start-of-selection.
    By default the program is under this event.
    If any of the other event comes before
    &#20840;elect&#12539;ndselect.&#12539;statements, then to break
    that event, we require this S-O-S event.
    Start-of-selection.
    Select * from &#12539;
    &#12539;&#12539;
    Endselect.
    Top-of-page.
    If we need some portion of the output (like
    column headings) to appear in all the pages,
    then we use this event.
    Top-of-page.
    Write:/ &#33307;arrier&#12539;10 &#33307;onnection&#12539;20 &#33337;ate&#12539;
    If there is no external output statement before
    &#31109;op-of-page&#12539;event, then this event will not
    work.
    End-of-page.
    Once the cursor reaches the last line of the
    page, automatically this event will be triggered.
    Report Zxxx line-count 25(3).
    In this case line numbers 23, 24 and 25 are
    reserved for footer.
    Once the cursor reaches 23rd line, this event
    will be triggered.
    End-of-page.
    Write:/ sy-uline(75).
    Write:/ &#31109;his is end of page:&#12539;sy-pagno.
    Write:/ sy-uline(75).
    End-of-selection.
    This event is used for concluding part of List.
    End-of-selection.
    Write:/ &#31109;his is end of the Report&#12539;
    Additional events in interactive reports
    The following additional events are applicable to secondary lists.
    Top-of-page during line-selection.
    At line-selection.
    At user-command.
    These additional events are triggered when u perform some action on the basic lists.
    example:
    REPORT zwk22671 LINE-COUNT 40(3)
    LINE-SIZE 200
    NO STANDARD PAGE HEADING.
    TABLES : mkpf , "MATERIAL DOCUMENT
    mseg , "DOCUMENT SEGMENT : MATERIAL
    t156t , "MOVEMENT TYPE TEXT
    makt. "MATERIAL DESCRIPTIONS
    *STRUCTURE OF INTERNAL TABLES
    DATA : BEGIN OF xtab,
    mblnr TYPE mkpf-mblnr , "DOCUMENT NUMBER
    mjahr TYPE mkpf-mjahr , "YEAR
    budat TYPE mkpf-budat , "POST DATE
    blart TYPE mkpf-blart , "DOCUMENT TYPE
    END OF xtab.
    DATA : BEGIN OF ytab,
    mblnr TYPE mseg-mblnr , "DOCUMENT NUMBER
    mjahr TYPE mseg-mjahr , "YEAR
    zeile TYPE mseg-zeile , "ITEM NUMBER
    bwart TYPE mseg-bwart , "MOVEMENT TYPE
    btext TYPE t156t-btext , "MOVEMENT DESCRIPTION
    matnr TYPE mseg-matnr , "MATERIAL NUMBER
    maktx TYPE makt-maktx , "MATERIAL DESCRIPTION
    meins TYPE mseg-meins , "UNIT OF MEASURE
    menge TYPE mseg-menge , "QUANTITY
    dmbtr TYPE mseg-dmbtr , "AMOUNT
    END OF ytab.
    *INTERNAL TABLE DECLARATION
    DATA : i_tab1 LIKE STANDARD TABLE OF xtab WITH HEADER LINE. "INTERNAL TABLE 1 : CONTAINS MATERIAL DETAILS
    DATA : i_tab2 LIKE STANDARD TABLE OF ytab WITH HEADER LINE. "INTERNAL TABLE 2 : CONTAINS ITEMWISE MATERIAL DETAILS
    *VARIABLES
    DATA : v_color TYPE sy-tabix , "FOR SETTING COLOR FORMATS DURING GENERATING REPORT
    v_field(20) , "FOR STORING THE CLICKED FIELD NAME
    v_value(20) , "FOR STORING THE CLICKED FIELD VALUE
    v_mblnr TYPE mkpf-mblnr , "FOR VALIDATING DOCUMENT NUMBER
    v_mjahr TYPE mkpf-mjahr , "FOR VALIDATING DOCUMENT YEAR
    v_bwart TYPE mseg-bwart , "FOR VALIDATING MOVEMENT TYPE
    v_matnr TYPE mseg-matnr . "FOR VALIDATING MATERIAL NUMBER
    **SELECTION-SCREEN
    SELECTION-SCREEN : BEGIN OF BLOCK blk1 WITH FRAME TITLE text-001.
    SELECT-OPTIONS : s_mblnr FOR mkpf-mblnr , "DOCUMENT NUMBER
    s_mjahr FOR mkpf-mjahr OBLIGATORY, "DOCUMENT YEAR
    s_bwart FOR mseg-bwart NO INTERVALS NO-EXTENSION, "MOVEMENT TYPE
    s_matnr FOR mseg-matnr . "MATERIAL NUMBER
    SELECTION-SCREEN : END OF BLOCK blk1.
    AT SELECTION-SCREEN
    AT SELECTION-SCREEN.
    PERFORM validation. "PERFORMS VALIDATION OF SELECTION-SCREEN FIELDS
    *TOP-OF-PAGE
    TOP-OF-PAGE.
    PERFORM header. "CREATES HEADER FOR THE BASIC LIST
    *END-OF-PAGE
    END-OF-PAGE. "CREATES FOOTER FOR THE BASIC AND SECONDARY LIST
    PERFORM footer.
    *START-OF-SELECTION
    START-OF-SELECTION.
    PERFORM generation_basic. "GENERATES REPORT FOR BASIC LIST WHICH CONTAINS DOCUMENT NO , DOCUMENT YEAR
    "POST DATE , DOCUMENT TYPE.
    *END-OF-SELECTION
    END-OF-SELECTION.
    PERFORM report_basic. "DISPLAY REPORT FOR BASIC LIST
    *AT LINE-SELECTION
    AT LINE-SELECTION.
    PERFORM generation_secondary. "GENERATES REPORT FOR SECONDARY LIST BASED ON THE DOCUMENT NUMBER AND DOCUMENT YEAR
    "WHICH CONTAINS DOCUMENT NO , YEAR , ITEM NO , MOVEMENT TYPE , MOVEMENT DESCRIPTION ,
    "MATERIAL NUMBER , MATERIAL DESC , UNIT OF MEASURE , QUANTITY AND AMOUNT
    *TOP-OF-PAGE DURING LINE-SELECTION
    TOP-OF-PAGE DURING LINE-SELECTION.
    PERFORM header_secondary. "CREATES HEADER FOR THE SECONDARY LIST
    *AT USER-COMMAND
    AT USER-COMMAND.
    PERFORM user_secondary. "SUBROUTINE FOR HANDLING USER EVENTS
    FORM validation .
    *VALIDATING MATERIAL DOCUMENT NUMBER
    SELECT SINGLE mblnr
    INTO v_mblnr
    FROM mkpf
    WHERE mblnr IN s_mblnr.
    IF sy-subrc NE 0.
    MESSAGE 'ENTER CORRECT DOCUMENT NUMBER' TYPE 'E'.
    ENDIF.
    *VALIDATING MATERIAL DOCUMENT YEAR
    SELECT SINGLE mjahr
    INTO v_mjahr
    FROM mkpf
    WHERE mjahr IN s_mjahr.
    IF sy-subrc NE 0.
    MESSAGE 'ENTER CORRECT MATERIAL DOCUMENT YEAR' TYPE 'E'.
    ENDIF.
    *VALIDATING MOVEMENT TYPE
    SELECT SINGLE bwart
    INTO v_bwart
    FROM mseg
    WHERE bwart IN s_bwart.
    IF sy-subrc NE 0.
    MESSAGE 'ENTER CORRECT MOVEMENT TYPE' TYPE 'E'.
    ENDIF.
    *VALIDATING MATERIAL NUMBER
    SELECT SINGLE matnr
    INTO v_matnr
    FROM mseg
    WHERE matnr IN s_matnr.
    IF sy-subrc NE 0.
    MESSAGE 'ENTER CORRECT MATERIAL NUMBER' TYPE 'E'.
    ENDIF.
    ENDFORM. " VALIDATION
    FORM header .
    WRITE :/30 'MATERIAL DOCUMENTS' COLOR 1. "TITLE OF BASIC LIST
    WRITE :/1(89) sy-uline.
    FORMAT COLOR 1.
    WRITE :/1 sy-vline ,
    3 'DOCUMENT NUMBER' ,
    23 sy-vline ,
    25 'YEAR' ,
    45 sy-vline ,
    47 'POST DATE' ,
    67 sy-vline ,
    69 'DOCTYP' ,
    89 sy-vline .
    FORMAT RESET.
    WRITE :/1(89) sy-uline.
    ENDFORM. " HEADER
    FORM footer .
    IF sy-lsind EQ 0. "CHECKS WHICH LIST IS IT BASIC LIST OR SECONDARY (AND NO. OF SECONDARY LIST)
    WRITE :/1(89) sy-uline.
    ELSEIF sy-lsind EQ 1.
    WRITE :/1(192) sy-uline.
    ENDIF.
    ENDFORM. " FOOTER
    FORM generation_basic .
    SELECT mkpf~mblnr "DOCUMENT NUMBER
    mkpf~mjahr "DOCUMENT YEAR
    mkpf~budat "POST DATE
    mkpf~blart "DOCUMENT TYPE
    INTO TABLE i_tab1
    FROM mkpf INNER JOIN mseg ON mkpfmjahr EQ msegmjahr AND
    mkpfmblnr EQ msegmblnr
    WHERE mkpf~mblnr IN s_mblnr
    AND mkpf~mjahr IN s_mjahr
    AND mseg~bwart IN s_bwart
    AND mseg~matnr IN s_matnr.
    IF sy-subrc NE 0.
    WRITE :/ 'MATERIAL DATA NOT FOUND'.
    ENDIF.
    DELETE ADJACENT DUPLICATES FROM i_tab1 COMPARING mblnr mjahr.
    ENDFORM. " GENERATION_BASIC
    FORM report_basic .
    LOOP AT i_tab1.
    v_color = sy-tabix MOD 2.
    IF v_color EQ 0.
    FORMAT COLOR 1 INTENSIFIED OFF.
    ELSE.
    FORMAT COLOR 2 INTENSIFIED OFF.
    ENDIF.
    WRITE :/1 sy-vline ,
    3 i_tab1-mblnr ,
    23 sy-vline ,
    25 i_tab1-mjahr ,
    45 sy-vline ,
    47 i_tab1-budat ,
    67 sy-vline ,
    69 i_tab1-blart ,
    89 sy-vline .
    HIDE : i_tab1-mblnr , i_tab1-mjahr. "STORING THE VALUE OF FIELDS CLICKED IN SYSTEM AREA
    ENDLOOP.
    FORMAT RESET.
    WRITE :/1(89) sy-uline.
    ENDFORM. " REPORT_BASIC
    FORM generation_secondary .
    IF sy-lsind EQ 1.
    SET PF-STATUS 'DISPLAY'.
    GET CURSOR FIELD v_field VALUE v_value. "GET THE FIELD VALUE AND NAME WHERE THE CURSOR WAS CLICKED
    CASE v_field.
    WHEN 'I_TAB1-MBLNR'. "DISPLAYS SECONDARY LIST ONLY IF DOCUMENT NUMBER IS CLICKED
    SELECT mseg~mblnr "DOCUMENT NUMBER
    mseg~mjahr "DOCUMENT YEAR
    mseg~zeile "ITEM NUMBER
    mseg~bwart "MOVEMENT TYPE
    t156t~btext "MOVEMENT DESCRIPTION
    mseg~matnr "MATERIAL NUMBER
    makt~maktx "MATERIAL DESCRIPTION
    mseg~meins "UNIT OF MEASURE
    mseg~menge "QUANTITY
    mseg~dmbtr "AMOUNT
    INTO TABLE i_tab2
    FROM ( ( mseg INNER JOIN t156t
    ON msegbwart EQ t156tbwart )
    INNER JOIN makt
    ON msegmatnr EQ maktmatnr )
    WHERE mseg~mblnr EQ i_tab1-mblnr
    AND mseg~mjahr EQ i_tab1-mjahr
    AND t156t~spras EQ sy-langu
    AND makt~spras EQ sy-langu.
    DELETE ADJACENT DUPLICATES FROM i_tab2 COMPARING mblnr mjahr.
    WHEN OTHERS.
    MESSAGE 'SELECT DOCUMENT NUMBER' TYPE 'E'.
    ENDCASE.
    LOOP AT i_tab2.
    v_color = sy-tabix MOD 2.
    IF v_color EQ 0.
    FORMAT COLOR 1 INTENSIFIED OFF.
    ELSE.
    FORMAT COLOR 2 INTENSIFIED OFF.
    ENDIF.
    WRITE :/1 sy-vline ,
    3 i_tab2-mblnr ,
    12 sy-vline ,
    14 i_tab2-mjahr ,
    19 sy-vline ,
    21 i_tab2-zeile ,
    30 sy-vline ,
    32 i_tab2-bwart ,
    40 sy-vline ,
    42 i_tab2-btext ,
    72 sy-vline ,
    74 i_tab2-matnr ,
    94 sy-vline ,
    96 i_tab2-maktx ,
    146 sy-vline ,
    148 i_tab2-meins ,
    153 sy-vline ,
    155 i_tab2-menge ,
    170 sy-vline ,
    172 i_tab2-dmbtr ,
    192 sy-vline .
    ENDLOOP.
    WRITE :/1(192) sy-uline.
    FORMAT RESET.
    ELSEIF sy-lsind EQ 2.
    GET CURSOR FIELD v_field VALUE v_value. "GET THE FIELD VALUE AND NAME WHERE THE CURSOR WAS CLICKED
    CASE v_field.
    WHEN 'I_TAB2-MBLNR'. "DISPLAYS SECONDARY LIST ONLY IF DOCUMENT NUMBER IS CLICKED
    SET PARAMETER ID : "SETTING PARAMETER ID FOR DOCUMENT NUMBER AND YEAR.
    'MBN' FIELD i_tab2-mblnr ,
    'MJA' FIELD i_tab2-mjahr.
    CALL TRANSACTION 'MB03' AND SKIP FIRST SCREEN. "CALLING TRABSACTION CODE 'MBO3'.
    WHEN OTHERS.
    MESSAGE 'SELECT DOCUMENT NUMBER' TYPE 'E'.
    ENDCASE.
    ENDIF.
    ENDFORM. " GENERATION_SECONDARY
    FORM header_secondary .
    WRITE :/50 'ITEMWISE MATERIAL DOCUMENTS' COLOR 1.
    WRITE :/1(192) sy-uline.
    FORMAT COLOR 1.
    WRITE :/1 sy-vline ,
    3 'DOCUMENT NO' ,
    12 sy-vline ,
    14 'YEAR' ,
    19 sy-vline ,
    21 'ITEM NO.' ,
    30 sy-vline ,
    32 'MOV TYP' ,
    40 sy-vline ,
    42 'MOV DESCRIPTION' ,
    72 sy-vline ,
    74 'MATERIAL NO' ,
    94 sy-vline ,
    96 'MATERIAL DESCRIPTION' ,
    146 sy-vline ,
    148 'UOM' ,
    153 sy-vline ,
    155 'QUANTITY' ,
    170 sy-vline ,
    172 'AMOUNT' ,
    192 sy-vline .
    WRITE :/1(192) sy-uline.
    FORMAT RESET.
    ENDFORM. " HEADER_SECONDARY
    *FORM user_secondary .
    IF sy-ucomm EQ 'DISPLAY'. "EXECUTES ONLY IF 'DISPLAY DOCUMENTS' ITEM IS CLICKED ON APPLICATION TOOL BAR.
    IF sy-lsind EQ 2.
    GET CURSOR FIELD v_field VALUE v_value. "GET THE FIELD VALUE AND NAME WHERE THE CURSOR WAS CLICKED
    CASE v_field.
    WHEN 'I_TAB2-MBLNR'. "DISPLAYS SECONDARY LIST ONLY IF DOCUMENT NUMBER IS CLICKED
    SET PARAMETER ID :
    'MBN' FIELD i_tab2-mblnr ,
    'MJA' FIELD i_tab2-mjahr.
    CALL TRANSACTION 'MB03' AND SKIP FIRST SCREEN.
    WHEN OTHERS.
    MESSAGE 'SELECT DOCUMENT NUMBER' TYPE 'E'.
    ENDCASE.
    ENDIF.
    LEAVE PROGRAM.
    ENDIF.
    ENDFORM. " USER_SECONDARY

  • Forbidden Statements in Web dynpro ABAP( WDA Framework )

    Hi,
    do we have documentation on what statements should not be used WDA Framework, like we have forbidden statements for ABAP Objects???

    Hi ,
    i am not aware of any such document but I can share some of them:
    Call Screen
    Call Transaction
    Leave to Transaction
    Perform
    Form
    Endform
    Include
    Report
    Module
    Endmodule
    Chain
    Endchain
    No macros are allowed
    Any FM, Search help or method involving screen call
    Get
    Get Late
    Put
    Definition
    End of Definition
    Select-Option
    parameter
    Any statement associated with selection screen / Screen or its component like, box, dropdown, checkbox, radiobutton, tab strip, table control etc.
    Write ( including any formatting tags )
    ABAP events ( start of selection, top of page, end of selection etc )
    I will share more on remembering them
    Regards
    Vishal Kapoor

  • IDM7.1- Synchronization with ABAP and JAVA

    hi all
    we are planning to Integrate EP(datasource: LDAP) and CUA/ABAP system with IDM7.1.
    Can somebody tell me How IDM takes care of CUA syncrhonization with LDAP and EP.  Synchronization is obsolete or its done by IDM internally.
    Please suggest us.
    regards

    Hi Jai,
    1) Connection establishment between LDAP, EP & ABAP.
    2) We define a Synchronization Job in IDM to sycn data between all the above
    3) When there is a change in LDAP or ABAP, Event Agents (out-of-box idm) detects the change and runs the synchronization job.
    How to define the synchronizaiton job is depends on the requirement.
    hope the above helps you.
    regards
    Anand.M

  • ABAP Extension Module and IDOC Creation

    Dear Gurus,
    I would like to send master data from SAP to IBM Websphere with the help of ABAP Extension module and populating idoc data using ABAP Event handler. Could you please let me know the flow of it. 
    Thanks in advance.
    Thanks
    Shanthi

    Hi,
       After calling MASTER_IDOC_DISTRIBUTE, you need to COMMIT. (COMMIT WORK).
       Please go through these links.
      http://help.sap.com/saphelp_erp2005vp/helpdata/en/78/21783151ce11d189570000e829fbbd/content.htm
    http://www.erpgenie.com/sapedi/idoc_abap.htm
    Regards,
    Vivek LR
    Edited by: Vivek LR on Jun 20, 2008 9:22 AM

  • Events List

    Hi all,
    Can anyone provide me all event's name with its description in ABAP                   ( ALV,Classical And Selection-screen's event) ?
    Thanks in advance......

    Hi,
        Events: Initialization
    at selection-screen
    at selection-screen on value request.
    start-of-selection
    top-of-page
    end-of-page
    at user-command
    at line-selection
    Order:
    1. Initialization
    2. at selection-screen
    3. at selection-screen on value request
    4. start of selection.
    when WRITE statement is triggered
    top-of page.
    end-of-page.
    end-of selection.
    at user-command.
    at line-selection
    Go through the following
    This is the order of execution in Classical/Interactive Report Events
    Classical Reports
    Reports which are properly formatted (header, footer, page numbers etc.,) with the help of one or more external events like top-of-page,end-of-page etc., are called as CLASSICAL REPORTS.
    Standard list.
    Output of Report program is nothing but Standard list. It consists of one continuous page of 60,000 lines.
    To restrict number of lines per page.
    Report Zxxxxx line-count 25.
    OR
    Report Zxxxxx line-count 25(3).
    ( In this case 3 lines are reserved for footer)
    To restrict Output width.
    Report Zxxxx line-size 125.
    To suppress standard page heading.
    Report Zxxxx no standard page heading
    Above all at a time:
    Report Zxxxx line-count 25(3)
    line-size 125
    no standard page heading.
    Screen Events List Events
    Initialization. Start-of-selection
    At selection-screen. Top-of-page.
    At selection-screen on <field>. End-of-page.
    End-of-selection.
    We can initialize the selection-screen with calculated default values under this event.
    Initialization.
    s_date-high = sy-datum.
    s_date-low = sy-datum - 15.
    Append s_date.
    We can validate all the inputs on selection screen fields under this event.
    At selection-screen.
    If s_carrid-low is initial or
    s_connid-low is initial or
    s_date is initial.
    < ... code for validation... >.
    Endif.
    We can validate a particular field input on selection screen under this event.
    At selection-screen on s_carrid.
    If s_carrid-low < > ‘LH’.
    <… code for validation…>
    Endif.
    If any of the other event comes before
    ‘Select…Endselect.’ statements, then to break
    that event, we require this S-O-S event.
    Start-of-selection.
    Select * from ……
    Endselect.
    If we need some portion of the output (like
    column headings) to appear in all the pages,
    then we use this event.
    Top-of-page.
    Write:/ ‘Carrier’,10 ‘Connection’ 20 ‘Date’.
    If there is no external output statement before
    ‘Top-of-page’ event, then this event will not
    work.
    Once the cursor reaches the last line of the
    page, automatically this event will be triggered.
    Report Zxxx line-count 25(3).
    In this case line numbers 23, 24 and 25 are
    reserved for footer.
    Once the cursor reaches 23rd line, this event
    will be triggered.
    End-of-page.
    Write:/ sy-uline(75).
    Write:/ ‘This is end of page:’,sy-pagno.
    Write:/ sy-uline(75).
    This event is used for concluding part of List.
    End-of-selection.
    Write:/ ‘This is end of the Report’.
    Interactive Report
    A simple report or even a classical report displays a clustered list with all the requested output at one go.
    What ever it is displayed, it is final. That means, the user can not interact with with that list.
    A simple report or even a classical report displays a clustered list with all the requested output at one go.
    What ever it is displayed, it is final. That means, the user can not interact with with that list.
    In the interactive reports, we can create as many as 21 lists.
    The first list is called ‘Basic list’ and all the successive lists are called ‘Secondary lists’. Each list is again an interactive.
    The Basic list is not deleted when secondary list is created.
    A secondary list may either overlay the basic list or appear in an additional dialog window on the same screen.
    The system variable associated with list number is ‘SY-LSIND’.
    For basic list SY-LSIND = 0 and for secondary lists, SY-LSIND varies from 1 to 20.
    User can interact with the list by the following ways.
    Double clicking or single click and pressing F2 (function key) or single click with ‘hotspot on’.
    OR
    Selecting from menu bar or from application tool bar.
    All the events used in classical reports can be used in Basic List.
    The event ‘End-of-page’ can be used in Secondary Lists also.(the other six events can not be used in secondary lists)
    You can not place ‘select-options’ in secondary lists.
    The following additional events are
    applicable to secondary lists.
    Top-of-page during line-selection.
    At line-selection.
    At user-command.
    When you double click on any field in the basic list, you will be navigating to secondary list with detailed information pertaining to clicked field.
    As such we need to store the clicked field information at some variable.
    ‘Hide’ temporarily stores the content of clicked field for later use.
    The default title of the out put is the text what we enter during creation of program.
    This title can be changed using:
    SET TITLEBAR ‘AAA’.
    GUI status includes:
    Menu bar
    Application tool bar and
    Activating standard tool bar
    GUI status can be created using
    SET PF-STATUS ‘BBB’.
    You can have 8 menus ( out of which, 2 menus are reserved for ‘System’ and ‘Help’).
    Each menu can have 15 menu items.
    Each menu item can have 3 levels of submenus.
    You can create 35 items in application tool bar.
    <i>ALV EVENTS</i>
    check these important events ...
    1.SLIS_PRINT_ALV.
    2. SLIS_T_LISTHEADER.
    3. SLIS_T_EVENT.
    4. SLIS_T_SORTINFO_ALV.
    5. SLIS_T_LAYOUT_ALV.
    6. SLIS_T_FIELDCAT_ALV.
    for more details ..check this link..
    http://www.sap-basis-abap.com/abap/events-in-alv-and-their-fm.htm
    <b>Reward points</b>
    Regards

  • About events

    What are the events of Classical Report  and Interactive report?

    HI,
    The program then follows this sequence of steps:
    It triggers the initialization event, causing the code belonging to initialization to be executed. If you have not coded an initialization event in your program, the driver program skips this step.
    It shows the selection screen for your program. (A selection screen is the screen that contains the input fields for your parameter statements.) If your program doesn't have a selection screen, it skips this step.
    It triggers the start-of-selection event, causing the code belonging to that event to be executed. If you have not coded a start-of-selection event in your program, it skips this step.
    It triggers the end-of-selection event in your program, executing all of the code belonging to it. If you haven't coded an end-of-selection, it skips this step.
    It shows the output list to the user.
    The order of execution for events is determined by the driver program, not by your program. Therefore, you can code the events in any order and the execution order will still be the same. The order of events in your program doesn't matter; they will always be triggered in the same sequence by the driver program.
    There will be different types of events in ABAP.
    So be clear what events you need ind etail.
    Some related to Classical reports, some to Interactive reports and some related to Module Pool Programming(Dialog)
    Events in Dialog Program
    PBO - Process Before Output
    PAI - Process After Input
    POH - Process on Help
    POV - Process on Valure Request.
    Events in ABAP Programming
    INITIALIZATION
    AT SELECTION-SCREEN OUTPUT
    AT SELECTION-SCREEN
    START-OF–SELECTION.
    TOP OF PAGE
    END OF PAGE
    END-OF-SELECTION.
    Control Break events related to Internal Tables:
    AT NEW FIELD
    AT END OF FIELD
    AT FIRST
    AT LAST
    Events in Interactive Report
    AT USER-COMMAND.
    AT LINE-SELECTION
    AT PF-FUNCTION KEY
    http://www.sap-img.com/abap/events-related-to-reporting.htm
    Thanks,
    Mahesh

  • Need docu on alv events with examples

    hi experts,
    Need help on docu in <b>alv events</b> with exam</b>ples
    thanks in advance.

    Hi,
    Check this link..
    http://www.sap-basis-abap.com/abap/events-in-alv-and-their-fm.htm
    go through following links......
    https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/library/abap/an%20easy%20reference%20for%20alv%20grid%20control.pdf
    Re: Performance Optimization for the following Code (URGENT & VERY IMPORTAN
    The main events in alv and their FM and why we use these:
    1. SLIS_PRINT_ALV.
    2. SLIS_T_LISTHEADER.
    3. SLIS_T_EVENT.
    4. SLIS_T_SORTINFO_ALV.
    5. SLIS_T_LAYOUT_ALV.
    6. SLIS_T_FIELDCAT_ALV.
    For more information check the following link:
    http://sap-img.com/abap/what-are-the-events-in-alv.htm
    Regards,
    Omkar.

Maybe you are looking for