SAP RFC_GET_STRUCTURE_DEFINITION Function Module for









RFC_GET_STRUCTURE_DEFINITION is a standard rfc get structure definition 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 rfc get structure definition FM, simply by entering the name RFC_GET_STRUCTURE_DEFINITION into the relevant SAP transaction such as SE37 or SE38.

Function Group: RFC1
Program Name: SAPLRFC1
Main Program: SAPLRFC1
Appliation area: S
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:



Function RFC_GET_STRUCTURE_DEFINITION 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 'RFC_GET_STRUCTURE_DEFINITION'"
EXPORTING
TABNAME = "Table name
* UCLEN = "

IMPORTING
TABLENGTH = "Length of the table in bytes

TABLES
FIELDS = "Field names and features

EXCEPTIONS
TABLE_NOT_ACTIVE = 1
.



IMPORTING Parameters details for RFC_GET_STRUCTURE_DEFINITION

TABNAME - Table name

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

UCLEN -

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

EXPORTING Parameters details for RFC_GET_STRUCTURE_DEFINITION

TABLENGTH - Length of the table in bytes

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

TABLES Parameters details for RFC_GET_STRUCTURE_DEFINITION

FIELDS - Field names and features

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

EXCEPTIONS details

TABLE_NOT_ACTIVE - Table does not exist actively

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

Copy and paste ABAP code example for RFC_GET_STRUCTURE_DEFINITION 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_fields  TYPE STANDARD TABLE OF RFC_FIELDS, "   
lv_tabname  TYPE X030L-TABNAME, "   
lv_tablength  TYPE RFC_FIELDS-INTLENGTH, "   
lv_table_not_active  TYPE RFC_FIELDS, "   
lv_uclen  TYPE UNICODELG. "   

  CALL FUNCTION 'RFC_GET_STRUCTURE_DEFINITION'  "
    EXPORTING
         TABNAME = lv_tabname
         UCLEN = lv_uclen
    IMPORTING
         TABLENGTH = lv_tablength
    TABLES
         FIELDS = lt_fields
    EXCEPTIONS
        TABLE_NOT_ACTIVE = 1
. " RFC_GET_STRUCTURE_DEFINITION




ABAP code using 7.40 inline data declarations to call FM RFC_GET_STRUCTURE_DEFINITION

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 TABNAME FROM X030L INTO @DATA(ld_tabname).
 
"SELECT single INTLENGTH FROM RFC_FIELDS INTO @DATA(ld_tablength).
 
 
 


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!