SAP TABLE_EXPORT_TO_MSACCESS_RFC Function Module for NOTRANSL: Datenexport in PC-Datenbank (MS-ACCESS)









TABLE_EXPORT_TO_MSACCESS_RFC is a standard table export to msaccess rfc SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for NOTRANSL: Datenexport in PC-Datenbank (MS-ACCESS) 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 table export to msaccess rfc FM, simply by entering the name TABLE_EXPORT_TO_MSACCESS_RFC into the relevant SAP transaction such as SE37 or SE38.

Function Group: MSDB
Program Name: SAPLMSDB
Main Program: SAPLMSDB
Appliation area: D
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:



Function TABLE_EXPORT_TO_MSACCESS_RFC 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 'TABLE_EXPORT_TO_MSACCESS_RFC'"NOTRANSL: Datenexport in PC-Datenbank (MS-ACCESS)
  EXPORTING
   DBNAME =  "PC Database Name for Download
*  LANGU =  "ABAP System Field: Language Key of Text Environment
*  FLG_APPEND = ' ' "Selection indicator
   DEST =  "Destination for Download
*  FLG_POPUP = ' ' "Selection indicator

TABLES
   DATA =  "Structure for MS Access communication char. array/ABAP type

EXCEPTIONS
   WRONG_WINSYS = 1    SYSTEM_FAILURE = 2    COMM_FAILURE = 3
.



IMPORTING Parameters details for TABLE_EXPORT_TO_MSACCESS_RFC

DBNAME - PC Database Name for Download

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

LANGU - ABAP System Field: Language Key of Text Environment

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

FLG_APPEND - Selection indicator

Data type: RC27X-FLG_SEL
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

DEST - Destination for Download

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

FLG_POPUP - Selection indicator

Data type: RC27X-FLG_SEL
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

TABLES Parameters details for TABLE_EXPORT_TO_MSACCESS_RFC

DATA - Structure for MS Access communication char. array/ABAP type

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

EXCEPTIONS details

WRONG_WINSYS -

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

SYSTEM_FAILURE -

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

COMM_FAILURE -

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

Copy and paste ABAP code example for TABLE_EXPORT_TO_MSACCESS_RFC 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:
lt_data  TYPE STANDARD TABLE OF ACCESS_COM, "   
lv_dbname  TYPE T390D-DBNAME, "   
lv_wrong_winsys  TYPE T390D, "   
lv_langu  TYPE SY-LANGU, "   
lv_system_failure  TYPE SY, "   
lv_flg_append  TYPE RC27X-FLG_SEL, "   SPACE
lv_comm_failure  TYPE RC27X, "   
lv_dest  TYPE T390D-DEST, "   
lv_flg_popup  TYPE RC27X-FLG_SEL. "   SPACE

  CALL FUNCTION 'TABLE_EXPORT_TO_MSACCESS_RFC'  "NOTRANSL: Datenexport in PC-Datenbank (MS-ACCESS)
    EXPORTING
         DBNAME = lv_dbname
         LANGU = lv_langu
         FLG_APPEND = lv_flg_append
         DEST = lv_dest
         FLG_POPUP = lv_flg_popup
    TABLES
         DATA = lt_data
    EXCEPTIONS
        WRONG_WINSYS = 1
        SYSTEM_FAILURE = 2
        COMM_FAILURE = 3
. " TABLE_EXPORT_TO_MSACCESS_RFC




ABAP code using 7.40 inline data declarations to call FM TABLE_EXPORT_TO_MSACCESS_RFC

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 DBNAME FROM T390D INTO @DATA(ld_dbname).
 
 
"SELECT single LANGU FROM SY INTO @DATA(ld_langu).
 
 
"SELECT single FLG_SEL FROM RC27X INTO @DATA(ld_flg_append).
DATA(ld_flg_append) = ' '.
 
 
"SELECT single DEST FROM T390D INTO @DATA(ld_dest).
 
"SELECT single FLG_SEL FROM RC27X INTO @DATA(ld_flg_popup).
DATA(ld_flg_popup) = ' '.
 


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!