SAP K_ALV_HIERSEQU_TABLES_CREATE Function Module for









K_ALV_HIERSEQU_TABLES_CREATE is a standard k alv hiersequ tables create SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used to perform a specific ABAP function and below is the pattern details, showing its interface including any import and export parameters, exceptions etc. there is also a full "cut and paste" ABAP pattern code example, along with implementation ABAP coding, documentation and contribution comments specific to this or related objects.


See here to view full function module documentation and code listing for k alv hiersequ tables create FM, simply by entering the name K_ALV_HIERSEQU_TABLES_CREATE into the relevant SAP transaction such as SE37 or SE38.

Function Group: KKBF
Program Name: SAPLKKBF
Main Program:
Appliation area: K
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:



Function K_ALV_HIERSEQU_TABLES_CREATE pattern details

In-order to call this FM within your sap programs, simply using the below ABAP pattern details to trigger the function call...or see the full ABAP code listing at the end of this article. You can simply cut and paste this code into your ABAP progrom as it is, including variable declarations.
CALL FUNCTION 'K_ALV_HIERSEQU_TABLES_CREATE'"
EXPORTING
IT_FIELDCAT = "
I_CALLBACK_PROGRAM = "
I_FORMNAME = "
I_TABNAME_HEADER = "
I_TABNAME_ITEM = "

EXCEPTIONS
GENERATE_SUB_POOL_FAILED = 1
.



IMPORTING Parameters details for K_ALV_HIERSEQU_TABLES_CREATE

IT_FIELDCAT -

Data type: SLIS_T_FIELDCAT_ALV
Optional: No
Call by Reference: No ( called with pass by value option)

I_CALLBACK_PROGRAM -

Data type: SY-REPID
Optional: No
Call by Reference: No ( called with pass by value option)

I_FORMNAME -

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

I_TABNAME_HEADER -

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

I_TABNAME_ITEM -

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

EXCEPTIONS details

GENERATE_SUB_POOL_FAILED -

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

Copy and paste ABAP code example for K_ALV_HIERSEQU_TABLES_CREATE Function Module

The ABAP code below is a full code listing to execute function module POPUP_TO_CONFIRM including all data declarations. The code uses the original data declarations rather than the latest in-line data DECLARATION SYNTAX but I have included an ABAP code snippet at the end to show how declarations would look using the newer method of declaring data variables on the fly. This will allow you to compare and fully understand the new inline method. Please note some of the newer syntax such as the @DATA is not available until a later 4.70 service pack (SP8), which i why i have stuck to the origianl for this example.

DATA:
lv_it_fieldcat  TYPE SLIS_T_FIELDCAT_ALV, "   
lv_generate_sub_pool_failed  TYPE SLIS_T_FIELDCAT_ALV, "   
lv_i_callback_program  TYPE SY-REPID, "   
lv_i_formname  TYPE SY, "   
lv_i_tabname_header  TYPE SY, "   
lv_i_tabname_item  TYPE SY. "   

  CALL FUNCTION 'K_ALV_HIERSEQU_TABLES_CREATE'  "
    EXPORTING
         IT_FIELDCAT = lv_it_fieldcat
         I_CALLBACK_PROGRAM = lv_i_callback_program
         I_FORMNAME = lv_i_formname
         I_TABNAME_HEADER = lv_i_tabname_header
         I_TABNAME_ITEM = lv_i_tabname_item
    EXCEPTIONS
        GENERATE_SUB_POOL_FAILED = 1
. " K_ALV_HIERSEQU_TABLES_CREATE




ABAP code using 7.40 inline data declarations to call FM K_ALV_HIERSEQU_TABLES_CREATE

The below ABAP code uses the newer in-line data declarations. This allows you to see the coding differences/benefits of the later inline syntax. Please note some of the newer syntax below, such as the @DATA is not available until 4.70 EHP 8.

 
 
"SELECT single REPID FROM SY INTO @DATA(ld_i_callback_program).
 
 
 
 


Search for further information about these or an SAP related objects



Comments on this SAP object

What made you want to lookup this SAP object? Please tell us what you were looking for and anything you would like to be included on this page!