SAP MSACCESS_STRUCT_EXPORT_RFC Function Module for NOTRANSL: Gegenstück zu msaccess_struct_export in Visual Basic









MSACCESS_STRUCT_EXPORT_RFC is a standard msaccess struct export 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: Gegenstück zu msaccess_struct_export in Visual Basic 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 msaccess struct export rfc FM, simply by entering the name MSACCESS_STRUCT_EXPORT_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 MSACCESS_STRUCT_EXPORT_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 'MSACCESS_STRUCT_EXPORT_RFC'"NOTRANSL: Gegenstück zu msaccess_struct_export in Visual Basic
EXPORTING
* DBNAME = 'SAP.MDB' "PC Database Name for Download

TABLES
TABLENAM = "DD Interface: Table Fields for DDIF_FIELDINFO_GET
ERRTEXTE = "Structure for message texts VB / Down/Upload PM/PS/QM
* PARAMETER = "Structure for MS Access Communication Parameters for 32BitVB
.



IMPORTING Parameters details for MSACCESS_STRUCT_EXPORT_RFC

DBNAME - PC Database Name for Download

Data type: T390D-DBNAME
Default: 'SAP.MDB'
Optional: Yes
Call by Reference: No ( called with pass by value option)

TABLES Parameters details for MSACCESS_STRUCT_EXPORT_RFC

TABLENAM - DD Interface: Table Fields for DDIF_FIELDINFO_GET

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

ERRTEXTE - Structure for message texts VB / Down/Upload PM/PS/QM

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

PARAMETER - Structure for MS Access Communication Parameters for 32BitVB

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

Copy and paste ABAP code example for MSACCESS_STRUCT_EXPORT_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:
lv_dbname  TYPE T390D-DBNAME, "   'SAP,MDB'
lt_tablenam  TYPE STANDARD TABLE OF DFIES, "   
lt_errtexte  TYPE STANDARD TABLE OF ACC_TEXTE, "   
lt_parameter  TYPE STANDARD TABLE OF ACCESS_PAR. "   

  CALL FUNCTION 'MSACCESS_STRUCT_EXPORT_RFC'  "NOTRANSL: Gegenstück zu msaccess_struct_export in Visual Basic
    EXPORTING
         DBNAME = lv_dbname
    TABLES
         TABLENAM = lt_tablenam
         ERRTEXTE = lt_errtexte
         PARAMETER = lt_parameter
. " MSACCESS_STRUCT_EXPORT_RFC




ABAP code using 7.40 inline data declarations to call FM MSACCESS_STRUCT_EXPORT_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).
DATA(ld_dbname) = 'SAP.MDB'.
 
 
 
 


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!