SAP TABLE_EXPORT_TO_MSACCESS Function Module for NOTRANSL: Funktionsgruppe für FB's um Tabellen ins MS-ACCESS zu klonen
TABLE_EXPORT_TO_MSACCESS is a standard table export to msaccess 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: Funktionsgruppe für FB's um Tabellen ins MS-ACCESS zu klonen 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 FM, simply by entering the name TABLE_EXPORT_TO_MSACCESS 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): Normal Function Module
Update:

Function TABLE_EXPORT_TO_MSACCESS 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'"NOTRANSL: Funktionsgruppe für FB's um Tabellen ins MS-ACCESS zu klonen.
EXPORTING
DBNAME = "Name of ACCESS DB on PC - file name
* LANGU = SY-LANGU "Language key
DEST = "Using SM59 maintained RFC destination
TABNAME = "Name of table = ACCESS table name
* REFTABLE = ' ' "Table in ACCESS should have other name
* FLG_NO_DOWNLOAD = ' ' "Flag: buffer data, more is coming
* FLG_APPEND = ' ' "Append/delete table if exists
* FLG_POPUP = ' ' "Dialog box for destination
TABLES
DTAB = "Data table (internal R/3 table)
EXCEPTIONS
WRONG_FORMAT = 1 STRUCT_TOOLONG = 2 UNKNOWN_DATATYPE = 3 SYSTEM_FAILURE = 4 COMM_FAILURE = 5
IMPORTING Parameters details for TABLE_EXPORT_TO_MSACCESS
DBNAME - Name of ACCESS DB on PC - file name
Data type: T390D-DBNAMEOptional: No
Call by Reference: No ( called with pass by value option)
LANGU - Language key
Data type: SY-LANGUDefault: SY-LANGU
Optional: Yes
Call by Reference: No ( called with pass by value option)
DEST - Using SM59 maintained RFC destination
Data type: T390D-DESTOptional: No
Call by Reference: No ( called with pass by value option)
TABNAME - Name of table = ACCESS table name
Data type: SUBDFIES-TABNAMEOptional: No
Call by Reference: No ( called with pass by value option)
REFTABLE - Table in ACCESS should have other name
Data type: SUBDFIES-REFTABLEDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
FLG_NO_DOWNLOAD - Flag: buffer data, more is coming
Data type: RC27X-FLG_SELDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
FLG_APPEND - Append/delete table if exists
Data type: RC27X-FLG_SELDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
FLG_POPUP - Dialog box for destination
Data type: RC27X-FLG_SELDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for TABLE_EXPORT_TO_MSACCESS
DTAB - Data table (internal R/3 table)
Data type:Optional: No
Call by Reference: Yes
EXCEPTIONS details
WRONG_FORMAT -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
STRUCT_TOOLONG -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
UNKNOWN_DATATYPE -
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 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_dtab | TYPE STANDARD TABLE OF STRING, " | |||
| lv_dbname | TYPE T390D-DBNAME, " | |||
| lv_wrong_format | TYPE T390D, " | |||
| lv_langu | TYPE SY-LANGU, " SY-LANGU | |||
| lv_struct_toolong | TYPE SY, " | |||
| lv_dest | TYPE T390D-DEST, " | |||
| lv_unknown_datatype | TYPE T390D, " | |||
| lv_tabname | TYPE SUBDFIES-TABNAME, " | |||
| lv_system_failure | TYPE SUBDFIES, " | |||
| lv_reftable | TYPE SUBDFIES-REFTABLE, " SPACE | |||
| lv_comm_failure | TYPE SUBDFIES, " | |||
| lv_flg_no_download | TYPE RC27X-FLG_SEL, " SPACE | |||
| lv_flg_append | TYPE RC27X-FLG_SEL, " SPACE | |||
| lv_flg_popup | TYPE RC27X-FLG_SEL. " SPACE |
|   CALL FUNCTION 'TABLE_EXPORT_TO_MSACCESS' "NOTRANSL: Funktionsgruppe für FB's um Tabellen ins MS-ACCESS zu klonen |
| EXPORTING | ||
| DBNAME | = lv_dbname | |
| LANGU | = lv_langu | |
| DEST | = lv_dest | |
| TABNAME | = lv_tabname | |
| REFTABLE | = lv_reftable | |
| FLG_NO_DOWNLOAD | = lv_flg_no_download | |
| FLG_APPEND | = lv_flg_append | |
| FLG_POPUP | = lv_flg_popup | |
| TABLES | ||
| DTAB | = lt_dtab | |
| EXCEPTIONS | ||
| WRONG_FORMAT = 1 | ||
| STRUCT_TOOLONG = 2 | ||
| UNKNOWN_DATATYPE = 3 | ||
| SYSTEM_FAILURE = 4 | ||
| COMM_FAILURE = 5 | ||
| . " TABLE_EXPORT_TO_MSACCESS | ||
ABAP code using 7.40 inline data declarations to call FM TABLE_EXPORT_TO_MSACCESS
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). | ||||
| DATA(ld_langu) | = SY-LANGU. | |||
| "SELECT single DEST FROM T390D INTO @DATA(ld_dest). | ||||
| "SELECT single TABNAME FROM SUBDFIES INTO @DATA(ld_tabname). | ||||
| "SELECT single REFTABLE FROM SUBDFIES INTO @DATA(ld_reftable). | ||||
| DATA(ld_reftable) | = ' '. | |||
| "SELECT single FLG_SEL FROM RC27X INTO @DATA(ld_flg_no_download). | ||||
| DATA(ld_flg_no_download) | = ' '. | |||
| "SELECT single FLG_SEL FROM RC27X INTO @DATA(ld_flg_append). | ||||
| DATA(ld_flg_append) | = ' '. | |||
| "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