SAP FI_WT_ALV_INTERFACE Function Module for Interface to the ALV
FI_WT_ALV_INTERFACE is a standard fi wt alv interface SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Interface to the ALV processing and below is the pattern details for this FM, 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 fi wt alv interface FM, simply by entering the name FI_WT_ALV_INTERFACE into the relevant SAP transaction such as SE37 or SE38.
Function Group: FQSRTOOL
Program Name: SAPLFQSRTOOL
Main Program: SAPLFQSRTOOL
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function FI_WT_ALV_INTERFACE 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 'FI_WT_ALV_INTERFACE'"Interface to the ALV.
EXPORTING
IM_METHOD = "Print or Customize
* IM_INFO_ERROR = "Info about table TB_ERROR
* IM_CALLING_PROGRAM = "Calling ABAP program
* IM_HEADER_1 = "Standard title
* IM_HEADER_2 = "Standard title
* IM_BATCH_HEADING = "Batch-Heading
* IM_BH_BUKRS = "Company code for Batch-Heading
* IM_INFO_CC_DATA = "Info about table TB_CC_DATA
* IM_INFO_PARTNER = "Info about table TB_PARTNER
* IM_INFO_FI_DOC = "Info about table TB_FI_DOC
TABLES
TB_CC_DATA = "Output Table: Company Code Data
TB_PARTNER = "Output Table: Vendor / Customer
TB_FI_DOC = "Output Table: FI line item
TB_ERROR = "Output Table: Error information
IMPORTING Parameters details for FI_WT_ALV_INTERFACE
IM_METHOD - Print or Customize
Data type: COptional: No
Call by Reference: Yes
IM_INFO_ERROR - Info about table TB_ERROR
Data type: TAX_ALV_INFOOptional: Yes
Call by Reference: Yes
IM_CALLING_PROGRAM - Calling ABAP program
Data type: SYREPIDOptional: Yes
Call by Reference: Yes
IM_HEADER_1 - Standard title
Data type: NORMTITELOptional: Yes
Call by Reference: Yes
IM_HEADER_2 - Standard title
Data type: NORMTITELOptional: Yes
Call by Reference: Yes
IM_BATCH_HEADING - Batch-Heading
Data type: XFELDOptional: Yes
Call by Reference: Yes
IM_BH_BUKRS - Company code for Batch-Heading
Data type: BUKRSOptional: Yes
Call by Reference: Yes
IM_INFO_CC_DATA - Info about table TB_CC_DATA
Data type: TAX_ALV_INFOOptional: Yes
Call by Reference: Yes
IM_INFO_PARTNER - Info about table TB_PARTNER
Data type: TAX_ALV_INFOOptional: Yes
Call by Reference: Yes
IM_INFO_FI_DOC - Info about table TB_FI_DOC
Data type: TAX_ALV_INFOOptional: Yes
Call by Reference: Yes
TABLES Parameters details for FI_WT_ALV_INTERFACE
TB_CC_DATA - Output Table: Company Code Data
Data type:Optional: No
Call by Reference: Yes
TB_PARTNER - Output Table: Vendor / Customer
Data type:Optional: No
Call by Reference: Yes
TB_FI_DOC - Output Table: FI line item
Data type:Optional: No
Call by Reference: Yes
TB_ERROR - Output Table: Error information
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for FI_WT_ALV_INTERFACE 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_im_method | TYPE C, " | |||
| lt_tb_cc_data | TYPE STANDARD TABLE OF C, " | |||
| lv_im_info_error | TYPE TAX_ALV_INFO, " | |||
| lt_tb_partner | TYPE STANDARD TABLE OF TAX_ALV_INFO, " | |||
| lv_im_calling_program | TYPE SYREPID, " | |||
| lt_tb_fi_doc | TYPE STANDARD TABLE OF SYREPID, " | |||
| lv_im_header_1 | TYPE NORMTITEL, " | |||
| lt_tb_error | TYPE STANDARD TABLE OF NORMTITEL, " | |||
| lv_im_header_2 | TYPE NORMTITEL, " | |||
| lv_im_batch_heading | TYPE XFELD, " | |||
| lv_im_bh_bukrs | TYPE BUKRS, " | |||
| lv_im_info_cc_data | TYPE TAX_ALV_INFO, " | |||
| lv_im_info_partner | TYPE TAX_ALV_INFO, " | |||
| lv_im_info_fi_doc | TYPE TAX_ALV_INFO. " |
|   CALL FUNCTION 'FI_WT_ALV_INTERFACE' "Interface to the ALV |
| EXPORTING | ||
| IM_METHOD | = lv_im_method | |
| IM_INFO_ERROR | = lv_im_info_error | |
| IM_CALLING_PROGRAM | = lv_im_calling_program | |
| IM_HEADER_1 | = lv_im_header_1 | |
| IM_HEADER_2 | = lv_im_header_2 | |
| IM_BATCH_HEADING | = lv_im_batch_heading | |
| IM_BH_BUKRS | = lv_im_bh_bukrs | |
| IM_INFO_CC_DATA | = lv_im_info_cc_data | |
| IM_INFO_PARTNER | = lv_im_info_partner | |
| IM_INFO_FI_DOC | = lv_im_info_fi_doc | |
| TABLES | ||
| TB_CC_DATA | = lt_tb_cc_data | |
| TB_PARTNER | = lt_tb_partner | |
| TB_FI_DOC | = lt_tb_fi_doc | |
| TB_ERROR | = lt_tb_error | |
| . " FI_WT_ALV_INTERFACE | ||
ABAP code using 7.40 inline data declarations to call FM FI_WT_ALV_INTERFACE
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.Search for further information about these or an SAP related objects