SAP STU3_ADMIN_CREATE_REMOTE_TABLE Function Module for Creates a table clone on a remote database









STU3_ADMIN_CREATE_REMOTE_TABLE is a standard stu3 admin create remote table SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Creates a table clone on a remote database 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 stu3 admin create remote table FM, simply by entering the name STU3_ADMIN_CREATE_REMOTE_TABLE into the relevant SAP transaction such as SE37 or SE38.

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



Function STU3_ADMIN_CREATE_REMOTE_TABLE 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 'STU3_ADMIN_CREATE_REMOTE_TABLE'"Creates a table clone on a remote database
EXPORTING
* CON_NAME = "Logical name for a database connection
* TAB_NAME = "Name of ABAP Dictionary Object
* COMMIT = "Single-Character Flag
* DO_NOT_CLOSE_CON = "General Flag

CHANGING
* CON_REF = "Database Connection

EXCEPTIONS
TABLE_NOT_IN_DDIC = 1 ERROR_CREATING_STATEMENTS = 2 ADBC_SQL_ERROR = 3 TABLE_EXISTS_ALREADY = 4 NO_VCAT_FOR_STOGROUP = 5 CANNOT_CREATE_LOB = 6
.



IMPORTING Parameters details for STU3_ADMIN_CREATE_REMOTE_TABLE

CON_NAME - Logical name for a database connection

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

TAB_NAME - Name of ABAP Dictionary Object

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

COMMIT - Single-Character Flag

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

DO_NOT_CLOSE_CON - General Flag

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

CHANGING Parameters details for STU3_ADMIN_CREATE_REMOTE_TABLE

CON_REF - Database Connection

Data type: CL_SQL_CONNECTION
Optional: Yes
Call by Reference: Yes

EXCEPTIONS details

TABLE_NOT_IN_DDIC -

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

ERROR_CREATING_STATEMENTS -

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

ADBC_SQL_ERROR -

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

TABLE_EXISTS_ALREADY -

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

NO_VCAT_FOR_STOGROUP -

Data type:
Optional: No
Call by Reference: Yes

CANNOT_CREATE_LOB -

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for STU3_ADMIN_CREATE_REMOTE_TABLE 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_con_ref  TYPE CL_SQL_CONNECTION, "   
lv_con_name  TYPE DBCON-CON_NAME, "   
lv_table_not_in_ddic  TYPE DBCON, "   
lv_tab_name  TYPE DCOBJDEF-NAME, "   
lv_error_creating_statements  TYPE DCOBJDEF, "   
lv_commit  TYPE CHAR1, "   
lv_adbc_sql_error  TYPE CHAR1, "   
lv_do_not_close_con  TYPE FLAG, "   
lv_table_exists_already  TYPE FLAG, "   
lv_no_vcat_for_stogroup  TYPE FLAG, "   
lv_cannot_create_lob  TYPE FLAG. "   

  CALL FUNCTION 'STU3_ADMIN_CREATE_REMOTE_TABLE'  "Creates a table clone on a remote database
    EXPORTING
         CON_NAME = lv_con_name
         TAB_NAME = lv_tab_name
         COMMIT = lv_commit
         DO_NOT_CLOSE_CON = lv_do_not_close_con
    CHANGING
         CON_REF = lv_con_ref
    EXCEPTIONS
        TABLE_NOT_IN_DDIC = 1
        ERROR_CREATING_STATEMENTS = 2
        ADBC_SQL_ERROR = 3
        TABLE_EXISTS_ALREADY = 4
        NO_VCAT_FOR_STOGROUP = 5
        CANNOT_CREATE_LOB = 6
. " STU3_ADMIN_CREATE_REMOTE_TABLE




ABAP code using 7.40 inline data declarations to call FM STU3_ADMIN_CREATE_REMOTE_TABLE

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 CON_NAME FROM DBCON INTO @DATA(ld_con_name).
 
 
"SELECT single NAME FROM DCOBJDEF INTO @DATA(ld_tab_name).
 
 
 
 
 
 
 
 


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!