Maintenance Screen - CHAR255 field to be displayed in 2 lines

Hi,
I have a field Comments in my z-table which is 255 char long. Inspite of my extending the field width to max the end user wants it to be displayed in 2 lines. Is this possible thru maintenance screen?
Thank You,
SB.

Hi
I suppose you're speaking about Maintenance Screen for SM30?
If it's so, no it can't, but you can generate the single screen and then change this screen in order to display that field on 2 lines, i.e to split that field into 2 fields.
Max

Similar Messages

  • How do I troubleshoot an ipad screen that goes black or displays crazy white lines?

    My Ipad has recently gone dark. when I reset it using the power/home thing it sometimes displays white lines that appear to be crossing he screen really really fast.  I cant get my ipad working.....

    IT looks like that is not a software issue but more on the hardware. are you covered by limited warranty or apple care? If you are you can bring it to the apple store for repair. Else you might be paying for an out of warranty repair. However, diagnosis is free so you can still go there for a free diagnostic test. It might be a display/ screen issue

  • Fields only to be displayed for last line item

    I copied WESCHEINVERS3( goods receipt form) script to zxxxx and placed some fields  in Main window using Perform statement. When i am displaying the output these fields are getting displayed under each line item. but i want them to be displayed under last line item.Please suggest how can i do this.
    Thanks
    K Srinivas

    data: v_cnt1 type i, v_cnt2 type i.
    count the number line item using describe lines statement in V_cnt1
    and in the table loop count the number of item into V_cnt2.
    place the field that you want at the end of all line item in the footer of the table and put  a condition in the condition tab v_cnt1 = v_cnt2.

  • Material Master - Error M3 826 Maintenance status of field ... to screen

    Hi Experts of the Material Master,
    I am getting the error M3 826 "Maintenance status of field MARA-BEHVO does not correspond to status of screen K" when all screens are selected in the Create Material Master transaction.
    Here is my situation: I have added the fields MARA-BEHVO and MARA-TEMPB both of status L (Storage) to a screen called "Phys. Characteristics", which has status K (Basic data).
    This produces  the error message above in standard SAP. I didn't want to change the customizing of the screen to allow L, because this screen is also used by other material types.
    I had to copy the screen MGD1 2701 (Phys. Characteristics) to my custom program for Material Master screens anyhow, as the number of fields and their descriptions had to be adjusted.
    The program was created using the activity "Create Program for User Subscreens" in SPRO.
    in the coding of ZMGD1 screen 2701 I have added this code behind the standard module FELDAUSWAHL to manipulate the standard logic that would blend out L fields on a K screen.
    LOOP AT SCREEN.
    *   Material Type
        IF mara-mtart = 'ZPNT'.
    *     Screen-Names of the 3 fields
          IF screen-name = 'MARA-TEMPB' OR
             screen-name = 'MARA-BEHVO'.
            screen-active      = 1.
            screen-invisible   = 0.
            screen-output      = 1.
    *       Change or Create transaction
            IF sy-tcode = 'JP27' OR sy-tcode = 'JP28'.
              screen-input       = 1.
              screen-required    = 1.
            ENDIF. "transaction code JP27 or JP28
            MODIFY SCREEN.
          ENDIF. "screen-name
        ENDIF. "Material Type ZPNT
      ENDLOOP.
    It all works fine when only a number of screens (but including the modified) screens are selected for creation.
    But it fails with the message above on the modified screen when all screens are selected.
    Any ideas?
    Ralf

    from the message, it appears that ZZKUNNR is a custom field attached to your MARA table. So, it is your System specific.  I don't see ZZKUNNR available in MARA.  If you look at the transaction code OMT3B (configuration for material master data screens), you can find K - Basic Data Screen in Maintenance Status field.
    You may look in this area to fix your issue. Because yours is a custom field, its tough to analyse further.
    Reward points, if it helps!
    Regards

  • F4 help for fields in maintenance view resp. generated maintenance screen

    Hello,
    I’m new to ABAP and I have to deal with the following requirement:
    I have a maintenance view V1 what from a maintenance screen was generated automatically by the maintenance screen generator.
    Now I have to add a search help for one field F1 of the maintenance screen. The values for the search help of F1 depend on a specific value of a second field F2 of the maintenance screen. So I need value of F2 as import parameter for f4-help. F1 and F2 come from different tables.
    As I’m new to ABAP I have several questions or thoughts:
    - I’m not able to easily add a search help to F1 because I’m using the maintenance view V1 and that’s why it is not possible to assign the import parameter F2 to the search help – right?
    - In general, its not that easy to add search help to views than tables or structures - why?
    - I’m not able to just modify the generated objects because further automatic generation of the maintenance screen will delete it – right?
    - The generated function module provides user includes to add user specific coding. Is there any chance to add a f4-help to field F1 and assign value of F2 to that search help as import parameter with coding in user include?
    - any other ideas? I did not expect this topic to be so complicated as the requirement to change f4-help in a maintenance view resp. screen isn't very special.
    can anyone help me?
    Thank You!
    Regards
    Fabian

    Hi Fabian,
    Phew! Thats quite a few questions in one... I'll try to answer them to best of my knowledge..
    You can definitely have an external Search Help for a field of a Maintenance View, by calling it directly in the Screen Action Flow, using a PROCESS ON VALUE-REQUEST (like PAI or PBO). While defining such custom code on a generated screen, always make sure you do not write the coding inside the generated includes (SVIM* or <FUGR>TOP, <FUGR>DAT, etc..). Define new includes, or use those which are not generated by View Maintenance. This way, even if the dialogue is regenerated, your custom code will not vanish.
    This will answer your questions 1 and 2 generally, and your question 3 also.
    A Maintenance View, is something where values are read and populated purely at run-time. It does not have an Entry Help or such options, as it depends on the underlying tables. I hope this further helps with questions 1 and 2.
    Coming to your question 4 and 5, which form the main question - pre-filling value of F2 while calling search-help for F1 - yes, it is possible. On the view maintenance screen, there are standard structure variables (like EXTRACT TOTAL etc), which will give you the field values of the current record. But, it can no way assure that when you call the help for F1, the field F2 is already filled!
    For this, I can suggest that you programmatically implement a check to see if F2 value is filled, and read if it is. Or, if it is not filled, maybe you can shoot a Pop-up for F2, take the value at run-time, find help for F1 and get value, and also fill the F2 value (from your implementation) into the currect screen F2 value! (Phew...it is complex...)
    But am sorry, there is no other way, wherein you can gaurentee that F2 value is pre-filled always, when you can help for F1. (You could try making F2 as obligatory on screen, but it still doesnt necessarily solve this purpose..!).
    Hope it helps. Get back to me by e-mail if you need more help, or simple post a reply.
    Regards,
    Rekha

  • Module Pool Programming - Radio Buttons & Screen Field Invisible or Display

    Hi,
    I have 2 radio buttons in my screen and both of them are checked or on. Not sure how to make one of them is on and other is off at a time. If A is off, i need to make few screen fields invisible or display. if A is on, i need to make the screen field invisible or input enabled.
    Can  you please suggest me a suitable way to accomplish this task.
    Appreciate Your Help in Advance.
    Thanks,
    Kannan

    hi
    try this
    go to SE38 create a program of type M
    go to SE51,give a screen no (ex : 0800) and click on create
    then click on Layout in se51
    in the Layout select the Radiobutton icon and drag/drop it on the layout
    Define them as by double clicking on the radiobutton icon
    First Radiobutton name : RB1, Groups : u can see 4 boxes,in the first box give group as G1
    do the same for the Second Radiobutton RB2.
    Now select both the radiobuttons RB1,RB2 both at a time and right click the cursor
    Radiobutton - Define.
    Then drag and drop a i/o field name : wk_name. save & activate the layout.
    in se51
    PBO
    Module_status_0800.
    Module_screen_modif.
    PAI
    Module_user_command_0800.
    in se38
    data : wk_name(10) type c.
    data : rb1,rb2.
    Module_screen_modif_o/p.
    if RB1 = 'X'.
    LOOP AT SCREEN.
    IF SCREEN-NAME = 'WK_NAME'.
    SCREEN-INPUT = '1'.
    SCREEN-INVISIBLE = '0'.
    MODIFY SCREEN.
    ENDIF.
    ENDLOOP.
    if RB2 = 'X'.
    LOOP AT SCREEN.
    IF SCREEN-NAME = 'WK_NAME'.
    SCREEN-INPUT = '0'.
    SCREEN-INVISIBLE = '1'.
    MODIFY SCREEN.
    ENDIF.
    ENDLOOP.
    endmodule.
    Module_user_command_0800.
    case sy-ucomm.
    when 'EXIT' or 'BACK' or 'CANCEL'.
    LEAVE PROGRAM.
    endcase.
    Endmodule.
    Regards

  • Maintenance screen

    Hi all,
    My requirement is to have a maintenance screen - similar to the one in SM30 for a custom table .This screen should appear as the output of an ABAP program after certain validations. I think its possible to CALL transaction SM30 with the table name and skip first screen. But i also require to
    1. Download the contents displayed in the maintenance screen to an excel spreadsheet
    2. To provide F4 help for fields even not  using SAP Standard fields. For instance , i have some custom fields in this table A,B of type say CHAR10. I require to provide F4 help for this field in the maintenance screen.
    Please let me know if any suggestions.
    Thanks in advance,
    Asha

    Hi,
    You can do it.
    Go to SM30 in your development client and open the table.
    Then go to , System -> Status -> and double click on the screen number. It will take you to Screen painter.
    Now you can modify the code there, create a subroutine and do the necessary validations.
    If you want F4 for a custom field you can populate the entries in an internal table and call the FM F4IF_INT_TABLE_VALUE_REQUEST. But for this you have to capture the F4 event through a method by declaring a class and assigning it to the field.
    Check
    https://forums.sdn.sap.com/click.jspa?searchID=888648&messageID=1366986
    this also.
    Regards
    Subramanian

  • New ALV field is not displaying

    Hi
    I have added the currency field in the existing ALV report.
    The final internal table having the currency field and it has value. Curreny field is not displaying in output. Pls help
    Below is my ALV code for currency.
    PERFORM FILL_FIELDCAT USING
    'WAERS' SPACE SPACE 'CURRENCY' 'CURRENCY' 'CURRENCY'.
    READ TABLE GIT_FIELDCAT INTO LX_FIELDCAT
              WITH KEY FIELDNAME = 'WAERS' .
      LX_FIELDCAT-OUTPUTLEN = 5.
      LX_FIELDCAT-JUST       = 'L'.
      MODIFY GIT_FIELDCAT FROM LX_FIELDCAT INDEX SY-TABIX.
    FORM FILL_FIELDCAT USING    P_FIELDNAME
                                P_NO_OUT
                                P_DO_SUM
                                P_SELTEXT_S
                                P_SELTEXT_M
                                P_SELTEXT_L.                    "#EC *
      DATA: LX_FIELDCAT TYPE SLIS_FIELDCAT_ALV.
      CLEAR LX_FIELDCAT.
      LX_FIELDCAT-TABNAME    = 'GIT_LIST'.
      LX_FIELDCAT-FIELDNAME  = P_FIELDNAME.
      LX_FIELDCAT-NO_OUT     = P_NO_OUT.
      LX_FIELDCAT-DO_SUM     = P_DO_SUM.
      LX_FIELDCAT-SELTEXT_S  = P_SELTEXT_S.
      LX_FIELDCAT-SELTEXT_M  = P_SELTEXT_M.
      LX_FIELDCAT-SELTEXT_L  = P_SELTEXT_L.
      APPEND LX_FIELDCAT TO GIT_FIELDCAT.
    ENDFORM.                               " FILL_FIELDCAT

    You have to [maintain maintenance dialog|http://help.sap.com/SAPHELP_NWPI71/helpdata/EN/a7/513484407a11d1893b0000e8323c4f/frameset.htm] as described in the link.
    Regards,
    Raymond

  • Adding Amount field in BSEG table and display it single line item?

    hi experts,
           I am doing credit / debit form now my requirement is
                                               According to BELNR , GJAHR,BUKRS i want to find credit amount for this selection cretiria.
                         so i want to add all the lines of amount filed for a particular BELNR and display it as single line.
    so i am getting data from print program like this
    SELECTION-SCREEN BEGIN OF BLOCK b0 WITH FRAME TITLE text-001.
    SELECTION-SCREEN SKIP 2.
    PARAMETERS: p_belnr LIKE bkpf-belnr OBLIGATORY,
                p_bukrs LIKE bkpf-bukrs OBLIGATORY,
                p_gjahr LIKE bkpf-gjahr OBLIGATORY.
    SELECTION-SCREEN END OF BLOCK b0.
    SELECT SINGLE *
                   FROM bkpf
                   INTO  i_bkpf
                   WHERE belnr = p_belnr
                         AND ( blart = 'DG' OR blart = 'ZG' )
                         AND bukrs = p_bukrs
                         AND gjahr = p_gjahr.
    IF sy-subrc = 0.
        SELECT  *
              FROM bseg
              INTO  table it_bseg
              WHERE belnr = i_bkpf-belnr .
      ENDIF.
      CALL FUNCTION 'SSF_FUNCTION_MODULE_NAME'
        EXPORTING
          formname                 = 'Z_CREDIT_DEBIT'    " p_name
      VARIANT                  = ' '
      DIRECT_CALL              = ' '
        IMPORTING
          fm_name                  = v_form_name
    EXCEPTIONS
      NO_FORM                  = 1
      NO_FUNCTION_MODULE       = 2
      OTHERS                   = 3
      IF sy-subrc <> 0.
    MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
            WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
      ENDIF.
    CALL FUNCTION v_form_name
    EXPORTING
      ARCHIVE_INDEX              =
      ARCHIVE_INDEX_TAB          =
      ARCHIVE_PARAMETERS         =
      CONTROL_PARAMETERS         =
      MAIL_APPL_OBJ              =
      MAIL_RECIPIENT             =
      MAIL_SENDER                =
      OUTPUT_OPTIONS             =
      USER_SETTINGS              = 'X'
    IMPORTING
      DOCUMENT_OUTPUT_INFO       =
      JOB_OUTPUT_INFO            =
      JOB_OUTPUT_OPTIONS         =
      TABLES
        i_bkpf                     = i_bkpf
        i_bseg                     = i_bseg
    EXCEPTIONS
      FORMATTING_ERROR           = 1
      INTERNAL_ERROR             = 2
      SEND_ERROR                 = 3
      USER_CANCELED              = 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.
    so my I_BSEG containing all line items of particular BELNR . with the field SHKZG  iam  getting only credit line items .
      now i want to do is add all credited amount and display like this in a table.
    against ref#  (BSEG-REBZG) ! details (BSEG-SGTXT)!  amount
    124569                                   10%discount                950.00(total amount ie sum of all lines amount for a BELNR)
                                                                                    10.00(total tax amt ie sum of   all lines of tax amount for a BELNR)                                                                               
                                                                                    960.00

    hi arun,
             i used collect in smartform my procedure is like this .
                   i am getting data into i_BSEG because i declared like this in TABLES parameter
                      i created a loop .
                             in that i mentioned like I_BSEG into WA_BSEG.
                                   then i created a program lines here i mentioned like this.
                                                  COLLECT WA_BSEG INTO IT_BSEG.
               but because of BUZEI "Number of Line Item Within Accounting Document .it is not same it is varying for every credited time that means for every line of BELNR. thats why it is not adding it is just appending .
    so pls tell me any other chance to find sum .
    because i want to sum up all credted amount and display it in single line
    ie first column REBZG "Number of the Invoice the Transaction Belongs to(against ref) i want to display once .
    And Second column  SGTXT "item text(details) for amount once and for tax amount once
    And Third column Amount first line consists total amount & second line consists total for tax amount
    regards,
    satheesh.
    [email protected]
    any doubts chat me regarding this post.

  • PO - Service tab gross price field is in display mode

    Dear all,
    My client requires
    Contract relase order with reference to Service contract, the price for the service codes which is adopted from the service contract, it is picking and displaying it contract release PO. But the gross price is in changeable mode. But i need the gross price field is in display mode. it should be in display mode while creating realse orders for contract.
    Expecting your earlier response
    Thanks in advance
    Raman

    Hi Raman,
    If you follow the steps mentioned in the note 30316 you will be able to find why the price in the contract is in changeable mode...and then we will be able to change the price to display mode.
    Note: 30316
    1.  In Transaction SE37, display function module MEX_FELDAUSWAHL and set
        a break point at the first statement.
    2.  Start the program where you suspect a problem with field selection.
        The program should stop at the break point set above. Copy the
        import fields I_AUSWAHL0, I_AUSWAHL1, I_AUSWAHL2, I_AUSWAHL3,
        I_AUSWAHL4, I_AUSWAHL5, and I_AUSWAHL6 to the list of field names.
        The corresponding field contents show the field selection reference
        keys that are composed as follows:
    3.  You can check the field selection reference keys found in
         Customizing. For purchase requisitions, the Transaction code is
         OMF2, for purchase orders it is OMF4, for contracts OMFA, for
         scheduling agreements OMF7, for requests for quotation it is OME8.
        Or
        Tcode: OLME  Contract  Define Screen Layout at Document Level
    4.  All keys from the AUSWAHLn fields are used to determine the field
         selection and their status. They are set according to the following
         matrix.
         See the matrix in the note
    Alternatively, the following can be stated:
         o  Field status 'Hidden' takes highest priority. This means that if
            a reference key has defined the field as 'Hidden', all other
            reference keys are overruled.
         o  Then follow statuses 'Display', 'Mandatory', and finally
            'Optional'. Accordingly, a field is assigned the attribute
            'Optional' only if all reference keys for the field are set to
            'Optional'.
    I hope this information helps you to resolve behaviour.
    Best Regards,
    Gabriela

  • HR ABAP: LOOP AT SCREEN: Multiple Fields Disabling.

    Experts,
    Am a new member in the world of SAP ABAP!
    Need ur advice regarding.
    Have coded following for disabling a field in PBO based on subtypes.
        IF p9235-subty = GC_AICTD.
          IF screen-name = 'P9235-ZZ_RC_MDE'.
            screen-active = 0.
            MODIFY SCREEN.
          ENDIF.
        ENDIF.
    This disables the particular field mentioned in the screen name.
    If i want more than on field names to be disabled under single validation, then what should i do?
    Your help to this fresher would be appreciated!
    Points will be definitely rewarded for your help and time...
    Thank you.
    Sundar.

    *&      Module  display  OUTPUT
          text
    MODULE display OUTPUT.
    *break-point.
    loop at screen.
    if create = 'X'.
      if screen-group1 = 'XXX'.
      screen-input = 1.
      modify screen.
      endif.
    endif.
    if display = 'X'.
      if screen-group2 = 'YYY'.
    screen-input = 0.
      modify screen.
      endif.
    endif.
      endloop.
    ENDMODULE.                 " display  OUTPUT
    but declare the group!

  • RoboHelp HTML v7to9 Migrate issue, Screen Tip field in images' properties w/DHTML Drop-down hotspot

    Hey all, thanks in advance for any info you can provide.  All the RoboHelp references below relate to us using the respective version of RoboHelp HTML, and on my XP SP3 pc.
    For various reasons, we tried migrating our data from RoboHelp v7 directly to RoboHelp v9, but noticed this same issue also occurred when we tried to migrate our data from RoboHelp v7 to RoboHelp v8, as this was one of the reasons we did not use RoboHelp v8 as our production "version".
    I noticed that RoboHelp v9 (and RoboHelp v8) will not populate the "Screen tip:" area/field of the image's properties window with the existing Screen tip text, even though it is in the html code of the page and when viewing the page within RoboHelp (Ctrl-W) or through a browser like IE6 or IE8, the Screen tip text will display when hovering the mouse over the picture.  Only the RoboHelp v7 will properly display the text info in the Screen tip area.
    Please note, we have most of our images inserted in a DHTML Drop-down hotspot and use buttons associated with a java script to "Show All Images" (or "Hide All Images") and these examples are the ones that the "Screen Tip:" field in the image's properties did not populate in RoboHelp v9.
    Is there any easy way to get the ALT text to appear in the actual "Screen tip:" area/field of the image's properties window in RoboHelp v9, or must they be manually entered?  Otherwise, currently it shows up as all blank, as though we neglected to fill it in.  Is there an actual fix for this?  Thanks in advance for any info you can provide.

    Create a one topic project. See the Contact page on my site and send the project as instructed there. Do make sure you include a link to this thread and please do not email the project direct.
    I will open the project in Rh10 and generate webhelp.
    See www.grainge.org for RoboHelp and Authoring tips
    @petergrainge

  • How to change width of table maintenance screen in sm30

    Hi,
    I want to change the width of table maintenance screen in sm30 of a view. I am trying to change it through screen painter.
    But its giving me error - screen or window limit reached. I want to increase the widht to show all the fields at once.
    Is there any way for this?
    Also, earlier in table maintenance generator of view, there was one step selected. I changed it to two steps and re-generated the TMG. But again Its showing only one screen in sm30.
    Kindly tell me which step I have missed out.
    Regards,
    Seema Naharia

    I guess the links below should help in your problem ..
    http://www.saptechies.com/how-to-create-table-maintenance-generator/
    Window size on SM30
    If these do not please tell ..
    Regards,
    Manthan

  • Work Order field define and display in Operation TAB

    I have a question about the user field define in work order's operation:
    I define the user field in the standard IMG for operation's Enhancemen use. but the field can only display in the operation's details' Enhancemen Screen. 
    What I want is the User field can display in the Operation list screen.
    BTW:what does the Equipment numnber in Operation TAB 's   meaning
    thanks  a lot

    Duplicated [here|Work Order field define and display in Operation TAB;

  • AT SELECTION-SCREEN-ON FIELD  event IN ALV

    Hai all,
               Is there any event in ALV similar to AT SELECTION-SCREEN-ON FIELD  .
    if so how can this be achieved ,pls give me an example .
    Regards,
    Dev

    Sap provides a set of ALV (ABAP LIST VIEWER) function modules which can be put into use to embellish the output of a report. This set of ALV functions is used to enhance the readability and functionality of any report output. Cases arise in sap when the output of a report contains columns extending more than 255 characters in length. In such cases, this set of ALV functions can help choose selected columns and arrange the different columns from a report output and also save different variants for report display. This is a very efficient tool for dynamically sorting and arranging the columns from a report output. The report output can contain upto 90 columns in the display with the wide array of display options.
    The commonly used ALV functions used for this purpose are;
    1. REUSE_ALV_VARIANT_DEFAULT_GET
    2. REUSE_ALV_VARIANT_F4
    3. REUSE_ALV_VARIANT_EXISTENCE
    4. REUSE_ALV_EVENTS_GET
    5. REUSE_ALV_COMMENTARY_WRITE
    6. REUSE_ALV_FIELDCATALOG_MERGE
    7. REUSE_ALV_LIST_DISPLAY
    8. REUSE_ALV_GRID_DISPLAY
    9. REUSE_ALV_POPUP_TO_SELECT
    The different steps used for getting the above function modules into use are:
    Step 1
    DATA DECLARATION
    Sap standard type pools: SLIS , KKBLO .
    Sap standard tables types taken from the type pools are: SLIS_LAYOUT_ALV ,
    SLIS_T_FIELDCAT_ALV,
    SLIS_T_LISTHEADER,
    SLIS_T_EVENT,
    SLIS_SELFIELD.
    Internal tables to used in the program declared based on the above table types
    DATA: I_LAYOUT TYPE SLIS_LAYOUT_ALV,
    I_FIELDTAB TYPE SLIS_T_FIELDCAT_ALV,
    I_HEADING TYPE SLIS_T_LISTHEADER,
    I_EVENTS TYPE SLIS_T_EVENT.
    TYPES: KKBLO_SELFIELD TYPE SLIS_SELFIELD.
    Step 2 (Optional)
    SELECTING THE VARIANTS FOR INITIAL LIST DISPLAY (DEFAULT VARIANT)
    The variants in the list display can be both user-specific and general. The user can programmatically set the initial (default) variant for list display.
    The default variant can be found using the function module 'REUSE_ALV_VARIANT_DEFAULT_GET'.
    Sample code:
    CALL FUNCTION 'REUSE_ALV_VARIANT_DEFAULT_GET'
    EXPORTING
    i_save = variant save condition ( A=all, U = user-specific )
    CHANGING
    cs_variant = internal table containing the program name (and the default variant---optional )
    EXCEPTIONS
    not_found = 2.
    The user can also choose from the list of existing variants using the function module ‘REUSE_ALV_VARIANT_F4’.
    Step 3
    DEFININING OUTPUT CHARACTERISTICS: PREPARING DISPLAY FIELDS CATALOG
    A field catalog is prepared using the internal table (I_FIELDCAT) of type SLIS_T_FIELDCAT_ALV. Field catalog containing descriptions of the list output fields (usually a subset of the internal output table fields).
    A field catalog is required for every ALV list output to add desired functionality (i.e. Key, Hotspot, Specific headings, Justify, Col. position etc) to certain fields of the output. If not mentioned specifically, then the defaults are taken. The possible values and defaults are listed below.
    The field catalog for the output table is built-up in the caller's coding. The build-up can be completely or partially automated by calling the REUSE_ALV_FIELDCATALOG_MERGE module.
    The minimal field catalog is documented below. This can be done in a routine using a local variable. The user can use the other optional parameters to assign output attributes to different fields in the output, which differ from the default.
    A field catalog need not be built-up and passed explicitly only under the following conditions:
    1. The internal table to be output has the same structure as a Data Dictionary structure which is referred to in the internal table declaration using LIKE or INCLUDE STRUCTURE. In this case the attributes of the different fields is taken directly from the table and the attributes (key fields, length, texts etc) need to state explicitly.
    2. all fields in this structure are to be output
    3. The structure name is passed to ALV in the parameter I_STRUCTURE_NAME of the function module REUSE_ALV_LIST_DISPLAY.
    All the values entered in the catalog is specific to the particular field whose name is entered in the fieldname FIELDNAME of the fieldcat structure. The name of the table is also entered in the corr. Fieldname TABNAME of the structure.
    The different possible attributes are:
    • Row_pos (row position): Only relevant if the list output is to be multi-line (two or three lines) by default. So, this attribute can be used maintain certain level of alignment in the output.
    Value set: 0, 1 – 3
    • Col_pos (column position): This parameter is relevant when the fields in the output are to be different from the sequence of the fields in the internal table used for display. The parameter specifies the relative column position of the field in the list output. The column order can be changed interactively by the user. If this parameter is initial for all field catalog entries, columns appear in the internal table field sequence.
    Value set: 0, 1 – 60
    • Fieldname (field name): This is the name of the internal table field for which the parameters are passed in the catalog.
    Value set: internal output table field name (required parameter)
    • Tabname (internal output table): Name of the internal output table that contains the field FIELDCAT-FIELDNAME above.
    Value set: SPACE, internal output table name.
    • Ref_fieldname (reference field name): Name of the Data Dictionary field referred to. This parameter is only used when the internal output table field described by the current field catalog entry has a reference to the Data Dictionary (not a program field), and the field name in the internal output table is different from the name of the field in the Data Dictionary. If the field names are identical, naming the Data Dictionary structure or table in the FIELDCAT-REF_TABNAME parameter is sufficient.
    Value set: SPACE, Data Dictionary field name.
    • Ref_tabname (reference table/structure field name): Structure or table name of the referred Data Dictionary field. This parameter is only used when the internal output table field described by the current field catalog entry has a Data Dictionary reference (not a program field).
    Value set: SPACE, name of a Data Dictionary structure or table
    Link to currency unit
    • Cfieldname (currency unit field name): This is used for currency fields that have a reference to any unit field. This is only relevant for amount columns with associated unit. This parameter contains the Name of the internal output table field containing the currency unit associated with the amount field FIELDCAT-FIELDNAME. The field in FIELDCAT-CFIELDNAME must have its own field catalog entry.
    Value set: SPACE, output table field name
    • Ctabname (internal currency unit field output table): Name of the internal output table containing the FIELDCAT-CFIELDNAME field.
    Value set: SPACE, output table field name.
    Link to measurement unit
    • Qfieldname (measurement unit field name): Only relevant for quantity columns with unit link. Name of the internal output table field containing the measurement unit associated with the quantity field FIELDCAT-FIELDNAME. The field in FIELDCAT-QFIELDNAME must have its own field catalog entry.
    Value set: SPACE, output table field name.
    • Qtabname (internal measurement unit field output table): Name of the internal output table containing the FIELDCAT-QFIELDNAME field.
    Value set: SPACE, output table field name.
    • Outputlen (column width): This parameter is used if the desired output length for a field is desired to be different from the internal output table field. For fields with a Data Dictionary link this parameter can be left initial. For fields without a Data Dictionary link (program field) the parameter must be given the value of the desired field list output length (column width).
    Initial = column width is the output length of the referred Data Dictionary field (domain).
    N = column width is n characters.
    Value set: 0 (initial), n.
    • Key (key column): By default, the system makes some fields in the output as key fields, provided the fields are key fields in their referencing table. Using this parameter, fields other than key fields of the referencing table can be made key field. This parameter is most important if the output needs to contain some field which are not scrollable or cannot be hidden.
    If the internal output table contains fields that are key fields from different tables, then all those fields in the report output becomes unscrollable and cannot be hidden. So, the fields in the output internal table should not be referenced from tables in which they are key fields. Instead, they should be referenced to the tables in which they are not key fields, incase they are not desired as key field in the output.
    'X' = key field (key field output in color) and Key fields can not be interactively hidden. Parameter FIELDCAT-NO_OUT must be left initial.
    Value set: SPACE, 'X'.
    • Key_sel (hideable key column): This parameter is only relevant for the fields which are made key fields using FIELDCAT-KEY = 'X'. Using this parameter the Key field can be hidden interactively.
    The key column sequence cannot be changed interactively by the user. The output is controlled by the FIELDCAT-NO_OUT parameter analogously to non-key fields.
    Value set: SPACE, 'X'.
    • No_out (field in field list): This parameter is used to remove certain fields from the output during initial display. The user can however interactively choose the field for output from the field list in the display variant.
    'X' = field is not displayed in the current list.
    Value set: SPACE, 'X'.
    • Tech (technical field): This parameter is used to make certain field display only in the field catalog. The fields with this parameter set cannot be output in the list nor can they be displayed interactively from the catalog.
    'X' = technical field.
    Value set: SPACE, 'X'.
    • Emphasize (highlight columns in color): As name suggests, this field parameter is used to highlight certain field with chosen colors.
    Value set: SPACE, 'X' or 'Cxyz' (x:'1'-'9'; y,z: '0'=off ,'1'=on).
    'X' = column is colored with the default column highlight color.
    'Cxyz' = column is colored with a coded color:
    - C: Color (coding must begin with C)
    - X: color number
    - Y: bold
    - Z: inverse
    • Hotspot (column as hotspot): This parameter is used to make certain field appear as hotspot i.e. a hand is displayed if the cursor is positioned on the field value. Single click on such fields cause the PICK OR F2 events to happen.
    Value set: SPACE, 'X'.
    'X' = column cells are output as hotspots.
    • Fix_column (fix column): This parameter is used to fix certain columns in the output. All columns to be fixed must have this flag, starting from the left. If a column without this flag is output, only the columns to the left of this column are fixed. The user can change the column fixing interactively.
    Value set: SPACE, 'X'.
    'X' = column fixed (does not scroll horizontally).
    • Do_sum (sum over column): the user can also call this function interactively.
    Value set: SPACE, 'X'.
    'X' = a sum is calculated over this internal output table field.
    • No_sum (sums forbidden): No sum can be calculated over this field, although the data type of the field would allow summing.
    Value set: SPACE, 'X'.
    • Icon: The parameter displays certain column contents as icons. The internal output table column contents must be valid icon strings.
    Value set: SPACE, 'X'.
    'X' = column contents to be output as an icon.
    • Symbol: The internal output table column must be a valid symbol character.
    Value set: SPACE, 'X'
    'X' = column contents are to be output as a symbol.
    • Just (justification): This parameter is used for alignment of the contents of the output table. This is only relevant for CHAR or NUMC fields in the output internal table. The justification of the column header always follows the justification of the columns. Independent justification of the column header is not possible.
    Value set: SPACE, 'R', 'L', and ‘C’.
    ' ' = Default justification for this data type
    'R' = right-justified output
    'L' = left-justified output
    'C' = centered output.
    • Lzero (leading zeros): By default ALV outputs NUMC fields right-justified without leading zeros. Using this parameter only the NUMC fields can be displayed with leading zeroes.
    Value set: SPACE, 'X'.
    'X' = output with leading zeros.
    • No_sign (no +/- sign): This parameter is used to suppress the signs of the output fields. It is only relevant for the value fields.
    Value set: SPACE, 'X'.
    'X' = value output without +/ sign.
    • No_zero (suppress zeros): Only relevant for value fields.
    Value set: SPACE, 'X'.
    'X' = suppress zeros.
    • Edit_mask (field formatting): To apply the report output formatting options same as in the WRITE statement in report writing.
    Value set: SPACE, template.
    The following parameters are used for customizing the texts in the heading of the output of the columns. The texts are taken from the Data Dictionary for fields with a Data Dictionary reference. If this is not desired, the text parameters can also be specified. The Data Dictionary texts are then ignored.
    If the user changes the column width interactively, the column header text with the appropriate length is always used.
    The interactive function 'Optimize column width' takes account of both the field contents and the column headers: if all field contents are shorter than the shortest column header, the column width depends on the column header.
    The 'long field label' is also used in display variant definition,
    Sort, etc. Popup.
    • seltext_l (long field label)
    • seltext_m (medium field label)
    • seltext_s (short field label)
    • reptext_ddic(header) Analogous to the Data element main header
    • Ddictxt (specify text) : You can specify with values 'L', 'M', and 'S', the keyword that should always be used as column header. If the column width changes, no attempt is made in this case to find an appropriate header for the new output width.
    Value set: SPACE, 'L', 'M', and ‘S’.
    Sample code:
    Suppose I_PO_DETAILS is an internal table containing two fields EBELN (PO number) and EBELP (PO item no).
    DATA: L_FIELDCAT TYPE SLIS_FIELDCAT_ALV. “Local variable to hold the parameters
    for a particular field of the field catalog
    CLEAR L_FIELDCAT.
    L_FIELDCAT-TABNAME = 'I_PO_DETAILS'.
    L_FIELDCAT-FIELDNAME = 'EBELN'.
    L_FIELDCAT-KEY = 'X'. “The PO no is made the key field,
    “Colored and non scrollable
    L_FIELDCAT-HOTSPOT = 'X'. “The po no becomes a hotspot
    L_FIELDCAT-SELTEXT_S = ‘P.O No’.
    L_FIELDCAT-SELTEXT_M = 'P order No'.
    L_FIELDCAT-SELTEXT_L = 'Purchase order No'.
    APPEND L_FIELDCAT TO I_FIELDTAB.
    CLEAR L_FIELDCAT
    L_FIELDCAT-TABNAME = 'I_PO_DETAILS'.
    L_FIELDCAT-FIELDNAME = 'EBELN'.
    L_FIELDCAT-KEY = 'X'. “The po item no is made the key field,
    “Colored and non scrollable
    L_FIELDCAT-SELTEXT_S = 'Item No'.
    L_FIELDCAT-SELTEXT_M = 'Item No`.
    L_FIELDCAT-SELTEXT_L = 'PO Item No'.
    APPEND L_FIELDCAT TO I_FIELDTAB.
    CLEAR L_FIELDCAT
    Thus the catalog for the report output is prepared.
    Step 4
    The next step is to build an event table, which are used for firing both user commands and the system dependent events i.e. top of page, end of page etc.
    A list of possible events is populated into an event table (I_EVENTS) when this table is passed to the function module REUSE_ALV_EVENT_NAMES_GET. The return table from this function module contains all the possible events.
    The function module contains following import and export parameters.
    IMPORTING PARAMETERS: I_LIST_TYPE
    This parameter has possible values from 0-4.
    The parameter I_LIST_TYPE is of TYPE SLIS_LIST_TYPE and is DEFAULT 0 .
    EXPORTING PARAMETERS: I_EVENTS table.
    This table is of TYPE SLIS_T_EVENT and returns to the program the name of all the possible events.
    The table structure contains the fields:
    I_EVENTS-NAME: Name of the Callback event.
    I_EVENTS-FORM: Name of the form routine that should be called in the calling program at the event.
    Only events with a form routine name are processed.
    The I_EVENTS table returns with the following possible constants:
    1. Slis_ev_item_data_expand TYPE slis_formname VALUE 'ITEM_DATA_EXPAND'.
    Only relevant for hierarchical-sequential lists using the layout parameter IS_LAYOUT-EXPAND_FIELDNAME of the structure IS_LAYOUT. Exit for passing item entries (ITEM table) for a header record that was expanded interactively by the user.
    2. Slis_ev_reprep_sel_modify TYPE slis_formname VALUE 'REPREP_SEL_MODIFY'.
    RS_SELFIELD-TABINDEX contains the header table index for which the item entries are to be put in the global item output table (T_OUTTAB_SLAVE). The Callback is only called if ALV has no items for a header that is to be expanded.
    RFLG_ALL is passed with 'X' if the user shows all items. The application must ensure that entries are not repeated in the item table.
    RS_SELFIELD is initial in this case.
    3. Slis_ev_caller_exit_at_start TYPE slis_formname VALUE 'CALLER_EXIT'.
    Is called at the beginning of the function module to make special settings. It is not usually used.
    4. Slis_ev_user_command TYPE slis_formname VALUE 'USER_COMMAND'.
    As this is a frequently-used Callback event, the form routine can also be passed directly in the interface by passing the user command in the IMPORTING parameter I_CALLBACK_USER_COMMAND.
    5. Slis_ev_top_of_page TYPE slis_formname VALUE 'TOP_OF_PAGE'.
    Equivalent to the list processing TOP-OF-PAGE event.
    6. Slis_ev_top_of_coverpage TYPE slis_formname VALUE 'TOP_OF_COVERPAGE'.
    The selection information and list status are output together (if they exist) on a separate page by default
    7. Slis_ev_end_of_coverpage TYPE slis_formname VALUE 'END_OF_COVERPAGE'.
    Analogously to TOP_OF_COVERPAGE the user can add other information
    to the information output by ALV (selection information, list status) at this event.
    8. Slis_ev_foreign_top_of_page TYPE slis_formname VALUE ‘FOREIGN_TOP_OF_PAGE'.
    The Top-of-page event is always processed in ALV and is only passed to the caller via the Callback mechanism. This is still the case if the caller, e.g. by a user action, processes a branch list which was not formatted by ALV (e.g. a popup with additional information about the list record selected and displayed by ALV).
    In this case, top-of-page cannot be formatted by ALV analogously to the basic list, it must be handled completely by the caller. The event top-of-page still occurs in ALV. When ALV notices a top-of-page which was not caused by an ALV output, the form routine in FOREIGN_TOP_OF_PAGE is called.
    9. Slis_ev_foreign_end_of_page TYPE slis_formname VALUE 'FOREIGN_END_OF_PAGE'.
    The event end-of-page is always processed in ALV and only passed to the caller via callback. This is still the case, e.g. when the caller processes a details list which was not formatted by ALV (e.g. a popup with further information about selected list records which were displayed by ALV).
    In this case, end-of-page cannot be formatted by ALV analogously to the basic list, it must be handled completely by the caller. The event end-of-page still occurs in ALV. When ALV notices an end-of-page that was not caused by an ALV output, the form routine in FOREIGN_END_OF_PAGE is called.
    10. Slis_ev_pf_status_set TYPE slis_formname VALUE 'PF_STATUS_SET'.
    If a user list status is to be set, it must be done in the form routine assigned to this event. The ALV function codes, which must not be active, are in the Parameter RT_EXTAB. This table must be passed with the SET PF-STATUS command (with inactive user function codes as well, if necessary).
    The STANDARD status of the function group SALV should be used as a template for a user-specific status. As this is a frequently used Callback event, its form routine can also be passed directly in the interface in the IMPORTING parameter I_CALLBACK_PF_STATUS_SET.
    11. Slis_ev_list_modify TYPE slis_formname VALUE 'LIST_MODIFY'.
    LIST_MODIFY USING R_TABNAME TYPE SLIS_TABNAME
    R_INDEX LIKE SY-TABIX
    R_INDEX_ITEM LIKE SY-TABIX
    R_INDEX_SUM LIKE SY-TABIX.
    12. Slis_ev_top_of_list TYPE slis_formname VALUE 'TOP_OF_LIST'.
    Information output at the start of the list
    13. Slis_ev_end_of_page TYPE slis_formname VALUE 'END_OF_PAGE'.
    Information output at the end of a page. This is only called for printing.
    14. Slis_ev_end_of_list TYPE slis_formname VALUE 'END_OF_LIST'.
    Information output at the end of the list
    15. Slis_ev_after_line_output TYPE slis_formname VALUE 'AFTER_LINE_OUTPUT'.
    Output information after each output line. Should only be used in justified cases because it costs a lot of performance.
    16. Slis_ev_before_line_output TYPE slis_formname VALUE 'BEFORE_LINE_OUTPUT'.
    Output information before each output line. Should only be used in justified cases because it costs a lot of performance.
    17. Slis_ev_subtotal_text TYPE slis_formname VALUE 'SUBTOTAL_TEXT'.
    This event table (I_EVENTS) is now checked with the desired constants. If the desired constant is found, then the corresponding field for the FORM NAME is populated with the name of the routine containing the corresponding event.
    Sample code :
    FORMNAME_TOP_OF_PAGE TYPE SLIS_FORMNAME VALUE 'TOP_OF_PAGE',
    FORMNAME_END_OF_PAGE TYPE SLIS_FORMNAME VALUE 'END_OF_PAGE', FORMNAME_USER_COMMAND TYPE SLIS_FORMNAME VALUE 'USER_COMMAND'.
    DATA: L_I_EVENT TYPE SLIS_ALV_EVENT.
    CALL FUNCTION 'REUSE_ALV_EVENTS_GET'
    EXPORTING
    I_LIST_TYPE = 0
    IMPORTING
    ET_EVENTS = I_EVENTS.
    READ TABLE I_EVENTS WITH KEY NAME = SLIS_EV_TOP_OF_PAGE
    INTO L_I_EVENT.
    IF SY-SUBRC = 0.
    MOVE FORMNAME_TOP_OF_PAGE TO L_I_EVENT-FORM.
    APPEND L_I_EVENT TO I_EVENTS.
    ENDIF.
    READ TABLE I_EVENTS WITH KEY NAME = SLIS_EV_END_OF_PAGE
    INTO L_I_EVENT.
    IF SY-SUBRC = 0.
    MOVE FORMNAME_END_OF_PAGE TO L_I_EVENT-FORM.
    APPEND L_I_EVENT TO I_EVENTS.
    ENDIF.
    CLEAR L_I_EVENT.
    READ TABLE I_EVENTS WITH KEY NAME = SLIS_EV_USER_COMMAND
    INTO L_I_EVENT.
    IF SY-SUBRC = 0.
    MOVE FORMNAME_USER_COMMAND TO L_I_EVENT-FORM.
    APPEND L_I_EVENT TO I_EVENTS.
    ENDIF.
    This will prepare the events table for the report.
    The report will contain three forms for the above events:
    1. FORM TOP_OF_PAGE : This form will contain the top of page event for the report i.e header etc
    Using the function module ‘REUSE_ALV_COMMENTARY_WRITE’, the internal table containing the headings for top of page event can be passed to the list output. Also, any logo specific to the report can be passed to the function module.
    2. FORM END_OF_PAGE : This form will contain the end of page event for the report i.e footer etc
    3. FORM USER_COMMAND : This form will contain the desired user command i.e pick/line selection
    Step 5
    A layout is build for the report output list description USING the internal table declared above (I_LAYOUT).
    Output list description structure.
    The parameters are described under the following heads:
    • Display options
    • Exceptions
    • Totals
    • Interaction
    • Detail screen
    • Display variants (only for hierarchical-sequential lists)
    • Color
    • Other
    The layout table is of type slis_layout_alv_spec and has the following fields:
    Display options
    1. Colwidth_optimize (1) TYPE c: This parameter optimizes the length of the different columns in the output. The width of the different col. now depends on the max. Length of the data in the column.
    Value set: SPACE, 'X'
    'X' = optimizes the column width so that all contents are displayed completely.
    2. No_colhead(1) TYPE c : This parameter suppresses the column headings
    Value set: SPACE, 'X'.
    'X' = column headers are not output
    3. No_hotspot(1) TYPE c : The heading of the report output are not output as hotspot.
    Value set: SPACE, 'X'.
    'X' = column headers are not output as hotspot
    4. Zebra(1) TYPE c : The report is output in the striped pattern.
    Value set: SPACE, 'X'.
    'X' = striped pattern (e.g. for wide lists)
    5. No_vline(1) TYPE c : The report output contains columns only separated by space and no lines. It is not relevant for: hierarchical-sequential lists and multiple-line lists.
    Value set: SPACE, 'X'.
    'X' = columns separated by SPACE
    6. No_min_linesize(1) TYPE c : The report line size is equal to the width of the list. It is not relevant for block lists.
    Value set: SPACE, 'X’.
    'X' = line size depends on list width
    ' ' = Line size is set to 80 or MIN_LINESIZE (if > 0) .
    7. Min_linesize LIKE sy-linsz: The report output contains a minimum possible length of line. If initial min_linesize is set to 80 by default, then this parameter is used to customize it. The prerequisite for this is that the parameter no_min_linesize should be ' '.
    Value set: 0, 10 - 250
    If the list is wider, the format uses the list width (maximum 250 or MAX_LINESIZE (if > 0)).
    8. Max_linesize LIKE sy-linsz: The default max. Linesize is 250. To change this default value, this parameter can interactively-define the maximum list width setting.
    Value set: 0, 80 - 1020
    9. Window_titlebar LIKE rsmpe-tittext: To set the titlebar on the report output.
    10. No_uline_hs(1) TYPE c.
    Exceptions
    11. Lights_fieldname TYPE slis_fieldname: Internal output table field containing the codes of exceptions to be output.
    Output table field code: '1' = red traffic light
    '2' = yellow traffic light
    '3' = green traffic light Fieldname for exception
    Value set: SPACE, internal output table field name.
    12. Lights_tabname TYPE slis_tabname: Name of the internal output table that contains the field in the parameter LIGHTS_FIELDNAME. If LIGHTS_FIELDNAME is not empty, this field must also be filled for hierarchical-sequential lists. Only relevant for hierarchical-sequential lists.
    . Value set: SPACE, internal output table name.
    13. Lights_rollname LIKE dfies-rollname: The documentation of this data element is displayed when you call F1 help for an exception column.
    Value set: SPACE, data element name.
    14. Lights_condense(1) TYPE c : If a list record is output with 'red traffic light', each
    Subtotal that includes this record is also output with 'red traffic light'.
    Value set: SPACE, 'X'
    'X' = the 'maximum' exception of the items in the subtotal is output at subtotal level.
    Sums
    15. No_sumchoice(1) TYPE c : This parameter allows the choice for summing up
    Only by fieldcatalog.
    Value set: SPACE, 'X'
    'X' = fields which are to be summed, passed by the calling program (FIELDCAT-DO_SUM = 'X'). The user should not be able to change this value interactively.
    16. No_totalline(1) TYPE c : Removes the option of having totals after sub-totals.
    Value set: SPACE, 'X'
    'X' = no total record is to be output. Subtotals can still be calculated and output. The fields in the subtotals are flagged DO_SUM = 'X' in the field list.
    17. No_subchoice(1) TYPE c : Does not allow the user to interactively change the field chosen for subtotals.
    Value set: SPACE, 'X'
    'X' = value whose change triggers subtotals, provided by the calling program. The user should not be able to change this value interactively.
    18. No_subtotals(1) TYPE c : No subtotals possible
    Value set: SPACE, 'X'
    'X' = no subtotals.
    19. Numc_sum(1) TYPE c : Totals only possible for NUMC-Fields.
    20. No_unit_splitting TYPE c: No separate total lines by inh.units
    21.totals_before_items TYPE c: Display totals before the items
    22. Totals_only(1) TYPE c : Show only totals
    Value set: SPACE, 'X'
    'X' = only total records are output.
    23. Totals_text(60) TYPE c : Text for 1st col. in totals
    Value set: SPACE, string (max.60)
    ' ' = The first column in the total record contains an appropriate number of '*'s to indicate the total by default. If the first column is wide enough, the string 'Total' is output after the asterisks.
    'String’ = The string passed is output after the total indicated by '*', if the column is wide enough.
    24. Subtotals_text(60) TYPE c : Texts for subtotals
    Value set: SPACE, string (max.60)
    ' ' = In the first column of subtotal records, the subtotal is indicated by an appropriate number of '*' by default. If the first column is not a subtotal criterion, the string 'Total' is output after the asterisks, if the column is wide enough.
    'String’ = the string passed is output after the subtotal indicated by '*', if the column is wide enough and the first column is not a subtotal criterion. If it is a subtotal criterion, its value is repeated after the total, if the column is wide enough.
    Interaction
    25. Box_fieldname TYPE slis_fieldname: Fieldname for checkbox in the report output. If the list has checkboxes at the start of records (for selecting several records), this parameter contains the internal output table field name indicated by the checkbox selection column. The field is a checkbox at the start of list records without a list header.
    Value set: SPACE, internal output table field name
    26. Box_tabname TYPE slis_tabname: Name of the internal output table that contains the field in the parameter BOX_FIELDNAME. If BOX_FIELDNAME is not empty, this field must also be filled for hierarchical-sequential lists.
    Value set: SPACE, internal output table name.
    27. Box_rollname LIKE dd03p-rollname: rollname for checkbox
    28. Expand_fieldname TYPE slis_fieldname: fieldname flag ‘expand’. The user can show or hide the items by clicking on the folder symbol (hotspot). If the items for a header entry are only to be read by the calling program and passed to ALV when a header has been expanded interactively, this can be controlled via the CALLBACK event 'ITEM_DATA_EXPAND'.
    29. Hotspot_fieldname TYPE slis_fieldname: Used to make the fieldname flag hotspot.
    30. No_input(1) TYPE c : The fields are only display fields.
    Value set: SPACE, 'X'
    'X' = all ready-for-input fields in a list are displayed as not ready-for-input. (Record selection checkboxes and fields which can be made ready-for-input via the field list parameter FIELDCAT-INPUT = 'X')
    31. F2code LIKE sy-ucomm: To assign an ALV standard function code to double-click (F2), assign the function code to this parameter. Ex.: to assign the ALV standard function 'Detail' ('&ETA') to F2.
    => LAYOUT-F2CODE = '&ETA'.
    Value set: SPACE, function code
    32. Confirmation_prompt: confirm. Prompt when leaving
    Value set: SPACE, 'X'
    'X' = if one of the functions ‘Back (F03)', ‘Exit (F15)' or ‘Cancel (F12)' occurs, a confirmation prompt appears.
    33. Key_hotspot(1) TYPE c : The key fields are displayed as hotspot. The columns defined in the field catalog as key fields (FIELDCAT-KEY = 'X') are output as hotspots, i.e. clicking on a key column (highlighted in color in the list) calls the function under F2.
    Value set: SPACE, 'X'.
    34. Reprep(1) TYPE c : report report interface active.
    35. Group_buttons(1) TYPE c : group-buttons for COL1 - COL5 . Group output fields via FIELDCAT-SP_GROUP in the field list, and pass the group name to the list module in the interface parameter IT_SPECIAL_GROUPS.
    Value set: SPACE, 'X'.
    36. No_keyfix(1) TYPE c : Used to make the key fields scrollable.
    Value set: SPACE, 'X'.
    ' ' = The key columns defined in the field catalog by FIELDCAT-KEY = 'X' are fixed in the list output. These columns do not scroll horizontally. The item table key columns are fixed in hierarchical-sequential lists. The header table key fields are not considered here.
    'X' = key columns not fixed
    37. Get_selinfos(1) TYPE c : To read selection screen.
    Value set: SPACE, 'X'.
    If the calling program is a report with an ABAP/4 selection screen, setting this parameter makes ALV read the selection screen again. If the selections are read successfully, a pushbutton, via which the user can call a popup which lists the report selections in a simple form, becomes active on the results list output by ALV.
    38. group_change_edit(1) TYPE c : Settings by user for new group
    Value set: SPACE, 'X'
    'X' = the user can enter a format option for each sort criterion in the sort/subtotal popup, for the list format when this value changes (e.g. new page or underline).
    39. No_scrolling(1) TYPE c : Does not allow scrolling of the list to the right.
    Value set: SPACE, 'X'.
    40. Expand_all(1) TYPE c : Expand all positions
    Detailed screen
    40. Detail_popup(1) TYPE c : show detail in popup.
    Value set: SPACE, 'X'
    ' ' = List record detail display in full-screen mode, with top-of-page.
    'X' = list record detail display in popup (without top-of-page).
    41. Detail_initial_lines(1) TYPE c : show also initial lines
    Value set: SPACE, 'X'
    ' ' = Only fields whose contents are not initial are output in the detail view.
    'X' = initial field contents are also output in detail.
    41. detail_titlebar(30) type c : Titlebar for detail screen
    Value set: SPACE, string (max.30)
    ` ' = ' Detail: Display' is output as the title of the detail window.
    'String’ = the string passed is output as the title of the detail window.
    Display variants
    42. Header_text (20) TYPE c: Text for header button. Only relevant for hierarchical-sequential lists. You can toggle between display field and field list views via pushbuttons in the display variant definition popup for hierarchical-sequential lists. The views refer to the hierarchy level of the fields. This is technically a toggle between the header table and item table fields.
    Value set: SPACE, CHAR (20)
    ' ' = The header table field pushbutton text is 'Header' by default.
    CHAR (20) = header table field pushbutton text.
    43.item_text(20) TYPE c : Text for item button. Only relevant for hierarchical-sequential lists. You can toggle the view between the display fields and the field list via pushbuttons in the display variant definition popup for hierarchical-sequential lists. The views refer to the hierarchy level of the fields. This is technically a toggle between the header table and item table fields.
    Value set: SPACE, CHAR (20)
    ' ' = The pushbutton text for the item table fields is 'Item' by default.
    CHAR (20) = item table field pushbutton text.
    44.default_ item(1) TYPE c : Items as default. Only relevant for hierarchical-sequential lists.
    Value set: SPACE, 'X'
    ' ' = The header table fields are displayed by default in the display variant definition popup. The user can switch to the item table fields interactively.
    'X' = the item table fields are displayed by default in the display variant Definition Popup. The user can switch to the header table fields interactively.
    Colour
    45. Info_fieldname TYPE slis_fieldname: infofield for listoutput. A whole list record can be colored individually using a color code in a column of the internal output table for the record. Assign the name of the field containing the color code to this parameter.
    Value set: SPACE, internal output table field name
    The internal output table field must be of type CHAR(3).
    The code must have the following syntax: 'Cxy':
    C = color (all codes must start with 'C')
    X = color number ('1'-'9')
    Y = bold ('0' = off, '1' = on)
    46. Coltab_fieldname TYPE slis_fieldname: Cells can be colored individually using a color code which is contained in a column of the internal output table for the record containing the cell. Assign the name of the field to this parameter.
    Others
    47. List_append(1) TYPE c : no call screen. It is only useful to output block-lists without specifying the above modules if the number of list blocks exceeds, or may exceed, the maximum number specified in the block module documentation. These operations are not possible for user-defined block lists.
    Example code :
    I_LAYOUT-f2code = ws_fcode.
    I_LAYOUT-zebra = 'X'.
    I_LAYOUT-colwidth_optimize = 'X'.
    I_LAYOUT-no_keyfix = 'X'.
    I_LAYOUT-get_selinfos = 'X'.
    I_LAYOUT-no_hotspot = 'X'.
    I_LAYOUT-no_input = 'X'.
    I_LAYOUT-hotspot_fieldname = FIELDNAME.
    I_LAYOUT-no_input = ‘X’.
    I_LAYOUT-no_vline = `X’.
    I_LAYOUT-no_colhead = ‘ ‘.
    I_LAYOUT-lights_condense = ` `.
    I_LAYOUT-totals_text = ` `.
    I_LAYOUT-subtotals_text = ` `.
    I_LAYOUT-totals_only = ` `.
    I_LAYOUT-key_hotspot = ‘X’.
    I_LAYOUT-detail_popup = ‘X’.
    I_LAYOUT-group_change_edit = ‘X’.
    I_LAYOUT-GROUP_BUTTONS = ‘X’.
    Step 6
    This step is required to get the selection screen information in the report output.
    The prerequisite for this is to set the parameter LAYOUT-GET_SELINFOS of the IMPORTING structure.
    The parameters to be passed in the IS_SEL_HIDE table are:
    o mode: 'R' = only the entries passed in the internal table IS_SEL_HIDE-T_ENTRIES
    Are output in the pop up. Selection info, which the list tool read in the selection screen (when called by a report with a selection screen), is replaced by the values passed.
    'S' = the selection info which the list tool read in the selection screen of the calling report are modified by the entries in the table IS_SEL_HIDE-T_ENTRIES.
    o t_entries: Selection info table
    o t_entries-mode: 'A' = output the selection info for the current table record in the info popup.
    'D' = do not output select option or SELNAME parameter selection info in the popup.
    o t_entries-selname: (only used in t_entries-mode = 'D') : Name of the select option or parameter.
    The following table fields are only used in t_entries-mode = 'A'. They contain the selection information to be added.
    • t_entries-field: DDIC field name of the field for which selection information is to be output.
    • t_entries-table: DDIC table names of t_entries-field.
    • t_entries-stext: Field name in info popup.
    • If t_entries-field and t_entries-table have been entered, this text is taken from DDIC.
    • t_entries-valuf: Selection condition 'from' value (external format)
    • t_entries-valut: Selection condition 'to' value (external format)
    • t_entries-sign0: (I)nclusive (E)xclusive
    • t_entries-option: All values of the select options Option field allowed.
    Step 6
    The Table IT_SORT is populated with the sort criteria for the different fields.
    The caller specifies the sorting and/or subtotaling of the basic list in the internal table IT_SORT.
    This internal table has the following fields:
    o spos : Sort sequence
    o fieldname : Internal output table field name
    o tabname : Only relevant for hierarchical-sequential lists. Name of the internal output table.
    o up : 'X' = sort in ascending order
    o down : 'X' = sort in descending order
    o subtot : 'X' = subtotal at group value change
    o group : '* ' = new page at group value change ,'UL' = underline at group value change
    Step 7
    The final step in the output of the report is the use of two ALV functions modules.
    1. REUSE_ALV_FIELDCATALOG_MERGE
    2. REUSE_ALV_LIST_DISPLAY
    The first function module is used to pass the field catalog to the report output and merge it with the internal output table.
    FUNCTION reuse_alv_fieldcatalog_merge.
    ""Lokale Schnittstelle:
    *” IMPORTING
    *" VALUE(I_PROGRAM_NAME) LIKE SY-REPID OPTIONAL
    *" VALUE(I_INTERNAL_TABNAME) TYPE SLIS_TABNAME OPTIONAL
    *" VALUE(I_STRUCTURE_NAME) LIKE DD02L-TABNAME OPTIONAL
    *" VALUE(I_CLIENT_NEVER_DISPLAY) TYPE SLIS_CHAR_1
    *" DEFAULT 'X'
    *" VALUE(I_INCLNAME) LIKE TRDIR-NAME OPTIONAL
    *" CHANGING
    *" VALUE(CT_FIELDCAT) TYPE SLIS_T_FIELDCAT_ALV
    *" EXCEPTIONS
    *" INCONSISTENT_INTERFACE
    *" PROGRAM_ERROR
    Import parameters
    I_PROGRAM_NAME: Program in which the internal output table is declared and populated
    I_INTERNAL_TABNAME: Internal output table name
    I_STRUCTURE_NAME: Structure name (structure, table, and view)
    I_CLIENT_NEVER_DISPL: Hide client fields default ‘X’
    I_INCLNAME: Data declarations include name
    CHANGING parameter
    CT_FIELDCAT: Field catalog with field descriptions
    The variant based on a program-internal table should only be used for rapid prototyping since the following restrictions apply:
    1. Performance is affected since the code of the table definition must always be read and interpreted at runtime.
    2. Dictionary reference are only considered if the keywords LIKE or INCLUDE STRUCTURE (not TYPE) are used.
    Step 8
    The other function module is used to display the internal output table with the contents
    FUNCTION reuse_alv_list_display.
    ""Lokale Schnittstelle:
    *” IMPORTING
    *" VALUE(I_INTERFACE_CHECK) DEFAULT SPACE
    *" VALUE(I_CALLBACK_PROGRAM) LIKE SY-REPID DEFAULT SPACE
    *" VALUE(I_CALLBACK_PF_STATUS_SET) TYPE SLIS_FORMNAME
    *" DEFAULT SPACE
    *" VALUE(I_CALLBACK_USER_COMMAND) TYPE SLIS_FORMNAME
    *" DEFAULT SPACE
    *" VALUE(I_STRUCTURE_NAME) LIKE DD02L-TABNAME OPTIONAL
    *" VALUE(IS_LAYOUT) TYPE SLIS_LAYOUT_ALV OPTIONAL
    *" VALUE(IT_FIELDCAT) TYPE SLIS_T_FIELDCAT_ALV OPTIONAL
    *" VALUE(IT_EXCLUDING) TYPE SLIS_T_EXTAB OPTIONAL
    *" VALUE(IT_SPECIAL_GROUPS) TYPE SLIS_T_SP_GROUP_ALV
    *" OPTIONAL
    *" VALUE(IT_SORT) TYPE SLIS_T_SORTINFO_ALV OPTIONAL
    *" VALUE(IT_FILTER) TYPE SLIS_T_FILTER_ALV OPTIONAL
    *" VALUE(IS_SEL_HIDE) TYPE SLIS_SEL_HIDE_ALV OPTIONAL
    *" VALUE(I_DEFAULT) DEFAULT 'X'
    " VALUE(I_SAVE) DEFAULT SPACE
    " VALUE(IS_VARIANT) LIKE DISVARIANT
    " STRUCTURE DISVARIANT DEFAULT SPACE
    " VALUE(IT_EVENTS) TYPE SLIS_T_EVENT OPTIONAL
    " VALUE(IT_EVENT_EXIT) TYPE SLIS_T_EVENT_EXIT OPTIONAL
    " VALUE(IS_PRINT) TYPE SLIS_PRINT_ALV OPTIONAL
    " VALUE(IS_REPREP_ID) TYPE SLIS_REPREP_ID OPTIONAL
    " VALUE(I_SCREEN_START_COLUMN) DEFAULT 0
    " VALUE(I_SCREEN_START_LINE) DEFAULT 0
    " VALUE(I_SCREEN_END_COLUMN) DEFAULT 0
    " VALUE(I_SCREEN_END_LINE) DEFAULT 0
    " EXPORTING
    " VALUE(E_EXIT_CAUSED_BY_CALLER)
    " VALUE(ES_EXIT_CAUSED_BY_USER) TYPE SLIS_EXIT_BY_USER
    " TABLES
    " T_OUTTAB
    " EXCEPTIONS
    " PROGRAM_ERROR
    Import parameters
    I_INTERFACE_CHECK: Interface consistency check log output.
    I_CALLBACK_PROGRAM: Name of the calling program
    I_CALLBACK_PF_STATUS_SET: Set EXIT routine to status.
    I_CALLBACK_USER_COMMAND: EXIT routine for command handling
    I_STRUCTURE_NAME: Internal output table structure name
    IS_LAYOUT: List layout specifications
    IT_FIELDCAT: Field catalog with field descriptions
    IT_EXCLUDING: Table of inactive function codes
    IT_SPECIAL_GROUPS: Grouping fields for column selection
    IT_SORT: Sort criteria for first list display
    IT_FILTER: Filter criteria for first list output
    IS_SEL_HIDE : Selection information modification
    I_DEFAULT: Initial variant active/inactive logic
    I_SAVE: Variants can be saved
    IS_VARIANT : Variant information
    IT_EVENTS: Table of events to perform IT_EVENT_EXIT : Standard fcode exit requests table
    IS_PRINT: Print information
    IS_REPREP_ID: Initialization keys for Re/Re interface
    I_SCREEN_START_COLUMN: Coordinates for list in dialog box
    I_SCREEN_START_LINE: Coordinates for list in dialog box
    I_SCREEN_END_COLUMN: Coordinates for list in dialog box
    I_SCREEN_END_LINE: Coordinates for list in dialog box
    IT_EVENT_EXIT: Standard fcode exit requests table
    IS_PRINT: Print information
    IS_REPREP_ID: Initialization keys for Re/Re interface
    I_SCREEN_START_COLUMN: Coordinates for list in dialog box
    I_SCREEN_START_LINE: Coordinates for list in dialog box
    I_SCREEN_END_COLUMN: Coordinates for list in dialog box
    I_SCREEN_END_LINE: Coordinates for list in dialog box
    Export parameters
    E_EXIT_CAUSED_BY_CALLER: Delete list in CALLBACK_USER_COMMAND
    ES_EXIT_CAUSED_BY_USER: How the user left the list Tables
    T_OUTTAB: Table with data to be displayed ---mandatory
    Example Code
    WS_REPNAME = SY-REPID.
    CALL FUNCTION 'REUSE_ALV_FIELDCATALOG_MERGE'
    EXPORTING
    I_PROGRAM_NAME = WS_REPNAME
    I_INTERNAL_TABNAME = Internal output table field name
    I_INCLNAME = WS_REPNAME
    CHANGING
    CT_FIELDCAT = I_FIELDTAB.
    IF SY-SUBRC <> 0.
    WRITE: 'SY-SUBRC: ', SY-SUBRC, 'REUSE_ALV_FIELDCATALOG_MERGE'.
    ENDIF.
    CALL FUNCTION 'REUSE_ALV_LIST_DISPLAY'
    EXPORTING
    I_CALLBACK_PROGRAM = WS_REPNAME
    I_STRUCTURE_NAME = Internal output table field name
    IS_LAYOUT = I_LAYOUT
    IT_FIELDCAT = I_FIELDTAB
    I_DEFAULT = 'A'
    I_SAVE = 'A'
    IS_VARIANT = 'X'
    IT_EVENTS = I_EVENTS[]
    IT_SORT = I_SORT
    IS_SEL_HIDE = I_SELINFO
    TABLES
    T_OUTTAB = Internal output table field name.
    IF SY-SUBRC <> 0.
    WRITE: 'SY-SUBRC: ', SY-SUBRC, 'REUSE_ALV_LIST_DISPLAY'.
    ENDIF
    THIS IS THE POP UP TO ALLOW THE USER TO DYNAMICALLY SELECT THE FIELDS FOR DISPLAY. HE CAN CHOOSE FROM THIS FIELDS ACC. TO REQUIREMENT AND HIDE THE OTHER FIELDS
    Example report output based prior to selection of the field
    THE USER HAS HIDDEN SOME OF THE FIELD FROM THE TOTAL FIELDS TO CUSTOMIZE THE REPORT OUTPUT
    Example report output after hiding some of the fields
    USER CAN CHOOSE A PARTICULAR SET OF FIELD FROM THE OUTPUT AND CAN SAVE IT AS VARIANTS
                                                                                    Using other function module 'REUSE_ALV_GRID_DISPLAY’ can help us get list output in the form of a grid and also attach logos to the report output.
    Sample code
    1 Simple list output:
    REPORT Y_DEMO_ALV NO STANDARD PAGE HEADING.
    Data to be displayed
    DATA: I_SFLIGHT TYPE TABLE OF SFLIGHT.
    Selection
    SELECT * FROM SFLIGHT INTO TABLE I_SFLIGHT.
    Call ABAP List Viewer (ALV)
    CALL FUNCTION 'REUSE_ALV_LIST_DISPLAY'
    EXPORTING
    I_STRUCTURE_NAME = 'SFLIGHT'
    TABLES
    T_OUTTAB = I_SFLIGHT.
    2.Simple grid output:
    REPORT Y_DEMO_ALV_1.
    Data to be displayed
    DATA: I_SFLIGHT TYPE TABLE OF SFLIGHT.
    Selection
    SELECT * FROM SFLIGHT INTO TABLE I_SFLIGHT.
    Call ABAP List Viewer (ALV)
    CALL FUNCTION 'REUSE_ALV_GRID_DISPLAY'
    EXPORTING
    I_STRUCTURE_NAME = 'SFLIGHT'
    TABLES
    T_OUTTAB = I_SFLIGHT.
    3. Demo for 'REUSE_ALV_POPUP_TO_SELECT'
    REPORT y_demo_alv_3.
    TYPE-POOLS: slis.
    DATA: BEGIN OF i_outtab OCCURS 0.
    INCLUDE STRUCTURE sflight.
    DATA: w_chk TYPE c. "For multiple selection
    DATA: END OF i_outtab.
    I_OUTTAB TYPE SFLIGHT OCCURS 0,
    DATA: i_private TYPE slis_data_caller_exit,
    i_selfield TYPE slis_selfield,
    W_exit(1) TYPE c.
    PARAMETERS: p_title TYPE sy-title.
    START-OF-SELECTION.
    SELECT * FROM sflight INTO TABLE i_outtab.
    CALL FUNCTION 'REUSE_ALV_POPUP_TO_SELECT'
    EXPORTING
    i_title = p_title
    i_selection = 'X'
    i_zebra = 'X'
    I_SCREEN_START_COLUMN = 0
    I_SCREEN_START_LINE = 0
    I_SCREEN_END_COLUMN = 0
    I_SCREEN_END_LINE = 0
    i_checkbox_fieldname = 'W_CHK'
    I_LINEMARK_FIELDNAME =
    I_SCROLL_TO_SEL_LINE = 'X'
    i_tabname = 'I_OUTTAB'
    i_structure_name = 'SFLIGHT'
    IT_FIELDCAT =
    IT_EXCLUDING =
    I_CALLBACK_PROGRAM =
    I_CALLBACK_USER_COMMAND =
    IS_PRIVATE = I_PRIVATE
    IMPORTING
    es_selfield = i_selfield
    e_exit = w_exit
    TABLES
    t_outtab = i_outtab
    EXCEPTIONS
    program_error = 1
    OTHERS = 2.
    IF sy-subrc <> 0.
    MESSAGE i000(0k) WITH sy-subrc.
    ENDIF.
    *****the internal table is modified with a cross sign for marking the
    ***rows selected
    LOOP AT i_outtab WHERE w_chk = 'X'.
    WRITE: / i_outtab-carrid, i_outtab-price.
    ENDLOOP.
    4. Demo for ALV output using field catalog and layout:
    REPORT y_demo_alv NO STANDARD PAGE HEADING.
    ALV related data declaration
    TYPE-POOLS: slis.
    DB-Table
    TABLES sflight.
    Includes
    INCLUDE &lt

Maybe you are looking for

  • 10g installation problem

    Hi! In the step Linking 'Oracle Database 10g 10.2.0.1.0' I receive an error:Error in invoking target 'utilities ctx_on' of makefile (...)/db_1/rdbms/lib/ins_rdbms.mk. See [logfile name] for detailsThe tail of the logfile is:INFO: ms/lib/rfsxc.o  -lsn

  • ABAP code in update rules to convert the date

    Hi, Could any one send me the ABAP code that is written in the update rules to convert the date (DD/MM/YYYY  -- lenght 10) to YYYYMMDD ---  length 8  format. Also please let me know where I should write this code; while creating update rules or while

  • Flex 3.1 and 3.0 SDK Download links are Broken

    Flex 3.0 and 3.1 SDKS are not available in ADOBE site for download ,  It displays all the SDK versions , But when we click on the link for 3.0 and 3.1  it will not Download it says URL not found ,  But where as you will be able to Download only the 3

  • When I updated my Iphone to ios it wouldnt activate. it kept saying the server is temporarilay unavailable and idk why

    When I updated my Iphone to ios it wouldnèt activate, it just kept saying the server was unavailable and idk why.

  • Locockpit

    hi bw experts, can you please answer these questions 1, what happen in background , when you generate the locockpit datasource 2, what is the reason is not created on aggregates on ods 3, what is the diff between process chain vs infopackage groups.