SAP RE_INTERFACE_DOCUMENT_VIA_BI Function Module for









RE_INTERFACE_DOCUMENT_VIA_BI is a standard re interface document via bi 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 re interface document via bi FM, simply by entering the name RE_INTERFACE_DOCUMENT_VIA_BI into the relevant SAP transaction such as SE37 or SE38.

Function Group: FVFI
Program Name: SAPLFVFI
Main Program: SAPLFVFI
Appliation area: F
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:



Function RE_INTERFACE_DOCUMENT_VIA_BI 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 'RE_INTERFACE_DOCUMENT_VIA_BI'"
EXPORTING
* I_AWTYP = 'REACC' "
* I_AWKEY = "
* I_MAP_CREATE = "
* I_MAP_NAME = 'REACC-BI' "
* I_MAP_KEEP = "

IMPORTING
E_TCODE = "

TABLES
BDC_BSSBKPF = "
BDC_BSSBSEG = "
BDC_BSSPARA = "
BDC = "

EXCEPTIONS
ERROR = 1
.



IMPORTING Parameters details for RE_INTERFACE_DOCUMENT_VIA_BI

I_AWTYP -

Data type: ACCHD-AWTYP
Default: 'REACC'
Optional: Yes
Call by Reference: No ( called with pass by value option)

I_AWKEY -

Data type: BKPF-AWKEY
Optional: Yes
Call by Reference: No ( called with pass by value option)

I_MAP_CREATE -

Data type: VVIS_SOPTI-CHECKBOX
Optional: Yes
Call by Reference: No ( called with pass by value option)

I_MAP_NAME -

Data type: APQI-GROUPID
Default: 'REACC-BI'
Optional: Yes
Call by Reference: No ( called with pass by value option)

I_MAP_KEEP -

Data type: APQI-QERASE
Optional: Yes
Call by Reference: No ( called with pass by value option)

EXPORTING Parameters details for RE_INTERFACE_DOCUMENT_VIA_BI

E_TCODE -

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

TABLES Parameters details for RE_INTERFACE_DOCUMENT_VIA_BI

BDC_BSSBKPF -

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

BDC_BSSBSEG -

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

BDC_BSSPARA -

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

BDC -

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

EXCEPTIONS details

ERROR -

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

Copy and paste ABAP code example for RE_INTERFACE_DOCUMENT_VIA_BI 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_error  TYPE STRING, "   
lv_e_tcode  TYPE SY-TCODE, "   
lv_i_awtyp  TYPE ACCHD-AWTYP, "   'REACC'
lt_bdc_bssbkpf  TYPE STANDARD TABLE OF BSSBKPF, "   
lv_i_awkey  TYPE BKPF-AWKEY, "   
lt_bdc_bssbseg  TYPE STANDARD TABLE OF BSSBSEG, "   
lt_bdc_bsspara  TYPE STANDARD TABLE OF BSSPARA, "   
lv_i_map_create  TYPE VVIS_SOPTI-CHECKBOX, "   
lt_bdc  TYPE STANDARD TABLE OF BDCDATA, "   
lv_i_map_name  TYPE APQI-GROUPID, "   'REACC-BI'
lv_i_map_keep  TYPE APQI-QERASE. "   

  CALL FUNCTION 'RE_INTERFACE_DOCUMENT_VIA_BI'  "
    EXPORTING
         I_AWTYP = lv_i_awtyp
         I_AWKEY = lv_i_awkey
         I_MAP_CREATE = lv_i_map_create
         I_MAP_NAME = lv_i_map_name
         I_MAP_KEEP = lv_i_map_keep
    IMPORTING
         E_TCODE = lv_e_tcode
    TABLES
         BDC_BSSBKPF = lt_bdc_bssbkpf
         BDC_BSSBSEG = lt_bdc_bssbseg
         BDC_BSSPARA = lt_bdc_bsspara
         BDC = lt_bdc
    EXCEPTIONS
        ERROR = 1
. " RE_INTERFACE_DOCUMENT_VIA_BI




ABAP code using 7.40 inline data declarations to call FM RE_INTERFACE_DOCUMENT_VIA_BI

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 TCODE FROM SY INTO @DATA(ld_e_tcode).
 
"SELECT single AWTYP FROM ACCHD INTO @DATA(ld_i_awtyp).
DATA(ld_i_awtyp) = 'REACC'.
 
 
"SELECT single AWKEY FROM BKPF INTO @DATA(ld_i_awkey).
 
 
 
"SELECT single CHECKBOX FROM VVIS_SOPTI INTO @DATA(ld_i_map_create).
 
 
"SELECT single GROUPID FROM APQI INTO @DATA(ld_i_map_name).
DATA(ld_i_map_name) = 'REACC-BI'.
 
"SELECT single QERASE FROM APQI INTO @DATA(ld_i_map_keep).
 


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!