JavaEar 专注于收集分享传播有价值的技术资料

How to use REUSE_ALV_FIELDCATALOG_MERGE function module?

I'm trying to use the function module REUSE_ALV_FIELDCATALOG_MERGE to pass the field label in ddic to display in the column header of the alv report. But, that didn't work.

If I comment the I_STRUCTURE_NAME = 'TY_YNAH_CUS_OBJ_REQ' line, it give me runtime error state

The ABAP program lines are wider than the internal table.

But if I uncomment it ,the program still did not work

REPORT YALV_TEST.

        tables sscrfields. 
        type-pools : slis.

        "CREATE STRUCTURE -1 
        TYPES: BEGIN OF TY_YNAH_CUS_OBJ_REQ, 
               REQID TYPE YNAH_REQ_ID, 
               REQUESTOR TYPE YNAH_REQUESTOR,
               BUSINESS_OWNER TYPE YNAH_BUS_OWN,
               FUNCTIONAL_OWNER TYPE YNAH_FUNC_OWN, 
               REQNUM TYPE YNAH_SERVICE_REQ_NUM, 
               PROJECT_ID TYPE YNAH_PRO_ID, 
               SYSTEM_ID TYPE YNAH_SYS_ID, 
               FUNCTIONAL_AREA TYPE YNAH_FUNC_AREA,
               REQUEST_DATE TYPE YNAH_REQ_DATE,
               REQUEST_TIME TYPE YNAH_REQ_TIME,

           END OF TY_YNAH_CUS_OBJ_REQ.

        "defining internal table -2 

        DATA: IT_YNAH_CUS_OBJ_REQ type TABLE OF TY_YNAH_CUS_OBJ_REQ 
         * WA_YNAH_CUS_OBJ_REQ type TY_YNAH_CUS_OBJ_REQ.

        DATA: it_fcat TYPE slis_t_fieldcat_alv ,
         wa_fcat TYPE slis_fieldcat_alv,
         gd_layout TYPE slis_layout_alv.

        SELECTION-SCREEN BEGIN OF BLOCK menu WITH FRAME TITLE text-001.
        SELECT-OPTIONS: s_proid FOR IT_YNAH_CUS_OBJ_REQ-PROJECT_ID.
        PARAMETER p_sysid type TY_YNAH_CUS_OBJ_REQ-SYSTEM_ID.
        SELECTION-SCREEN: BEGIN OF LINE,
        pushbutton 33(8) BUT user-command search. 
        SELECTION-SCREEN END OF LINE. 
        SELECTION-SCREEN END OF BLOCK menu.

        initialization. 
        BUT = 'SEARCH'. END-OF-SELECTION.

        "execute search function when user click search button
        at selection-screen. "after processing user input 
         case SSCRFIELDS.
           when 'SEARCH'.
            SSCRFIELDS-UCOMM = 'ONLI'.
        endcase.

    "fetch data using select-4 START-OF-SELECTION. 

    SELECT * 
    FROM YNAH_CUS_OBJ_REQ "Database 
    INTO CORRESPONDING FIELDS OF TABLE IT_YNAH_CUS_OBJ_REQ "Into internal table 
    WHERE 
       PROJECT_ID in s_proid and 
       SYSTEM_ID eq p_sysid.

        CALL FUNCTION 'REUSE_ALV_FIELDCATALOG_MERGE' 
        EXPORTING
         I_PROGRAM_NAME = sy-repid
        I_INTERNAL_TABNAME ='TY_YNAH_CUS_OBJ_REQ'
        * I_STRUCTURE_NAME = 'TY_YNAH_CUS_OBJ_REQ'
        * I_CLIENT_NEVER_DISPLAY = 'X'
        I_INCLNAME = sy-repid 
        * I_BYPASSING_BUFFER = 'X' 
        * I_BUFFER_ACTIVE = CHANGING CT_FIELDCAT = it_fcat. 
        * EXCEPTIONS 
        * INCONSISTENT_INTERFACE = 1 
        * PROGRAM_ERROR = 2 
        * OTHERS = 3 
        * .
         IF SY-SUBRC <> 0. 
        ** Implement suitable error handling here 
        ENDIF.

3个回答

    最佳答案
    1. The REUSE_*ALV* function modules are unsupported. I'd suggest switching to the CL_SALV_* classes. The documentation is better, there are more sample programs (DEMO_SALV_*) and you get support.
    2. You need a dictionary structure if you want to get dictionary-based field descriptions (duh). If you assemble a structure type on the ABAP level using TYPE ... BEGIN OF ... END OF ..., as far as I know, the dictionary types for the individual fields are converted to ABAP types first and only then assembled into a structure type. Anyway, the dictionary reference of the original fields is lost. Instead of defining the structure of the output table in your code, use a dictionary structure.
  1. 参考答案2
  2. You have some mistakes you might have not known (SAP is very confusing sometimes and not transparent with error-messages). I got for you a working example of mine, have a look on it, especially on the comments.

    First, data definition:

    TYPE-POOLS slis. "import you need for REUSE_ALV_FIELDCATALOG_MERGE
    
    DATA:
      lt_fieldcat TYPE slis_t_fieldcat_alv,
    
      BEGIN OF G_IT_MATERIAL occurs 0,
        MATNR LIKE MARA-MATNR,
        MTART LIKE MARA-MTART,
        MAKTX_DE LIKE MAKT-MAKTX,
        MAKTX_FR LIKE MAKT-MAKTX,
        MAKTX_IT LIKE MAKT-MAKTX,
        ERNAM LIKE MARA-ERNAM,
        ERSDA LIKE MARA-ERSDA,
        LAEDA LIKE MARA-LAEDA,
      END OF G_IT_MATERIAL.
    

    It is absolutely necessary that you define your local structure directly with LIKE, otherwise the parser from REUSE_ALV_FIELDCATALOG_MERGE will not find it.

    Select your stuff:

     SELECT ma~matnr ma~mtart ma~ernam ma~ersda ma~laeda
     de~maktx as maktx_de fr~maktx as maktx_fr it~maktx as maktx_it
     FROM mara as ma
     LEFT JOIN MAKT as de ON de~matnr = ma~matnr AND de~spras = 'DE'
     LEFT JOIN MAKT as fr ON fr~matnr = ma~matnr AND fr~spras = 'FR'
     LEFT JOIN MAKT as it ON it~matnr = ma~matnr AND it~spras = 'IT'
     INTO CORRESPONDING FIELDS OF TABLE g_it_material
          WHERE ...
    

    Create a field catalog dynamically:

    CALL FUNCTION 'REUSE_ALV_FIELDCATALOG_MERGE'
    EXPORTING
    I_PROGRAM_NAME        = sy-repid
    
    I_INTERNAL_TABNAME    = 'G_IT_MATERIAL'
    
    I_INCLNAME            = sy-repid
    CHANGING
    ct_fieldcat            = lt_fieldcat
    EXCEPTIONS
    inconsistent_interface = 1
    program_error          = 2
    OTHERS                 = 3.
    
    IF sy-subrc <> 0.
    * MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
    *         WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
    ENDIF.
    

    Now display the ALV grid:

    CALL FUNCTION 'REUSE_ALV_GRID_DISPLAY'
    EXPORTING
    it_fieldcat   = lt_fieldcat                 "you could also give a structure
    "i_structure_name      = 'ZMM_SMATERIAL'    "here instead of the fieldcat
    TABLES
    t_outtab      = g_it_material
    EXCEPTIONS
    program_error = 1
    OTHERS        = 2.
    

    Note that the parser also needs a max linesize of 72 chars.

  3. 参考答案3
  4. There are several different text components provided by structure slis_fieldcat_alv that are used as column labels. The chosen text depends on the current column width (which itself usually depends on the length of the data displayed). Make sure that you change them all accordingly!

    The usual technique is: By passing the I_STRUCTURE_NAME, you get a field catalog corresponding to this DDIC structure (the changing parameter ct_fieldcat). You then modify this internal table according to your needs and pass that modified table to the REUSE_ALV_GRID_DISPLAY.

    In cases where I don't distinguish the different-sized text versions, I use the following macros to set all the text fields to the same value. The macros require a local work area ls_fieldcat (with the linetype of ct_fieldcat) and a local string variablelv_text` in order to work.

    define set_field.
    * Feld &1 für Anzeigefeld &2 den Wert &3 zuweisen
      ls_fieldcat-&1 = &3.
      modify ct_fieldcat from ls_fieldcat
        transporting &1
        where fieldname cp '&2'.
    end-of-definition.
    
    define set_text_direct.
      lv_text = &2.
      set_field seltext_s &1 lv_text.
      lv_text = &2.
      set_field seltext_m &1 lv_text.
      lv_text = &2.
      set_field seltext_l &1 lv_text.
    end-of-definition.