SAP RPY_TABLE_INSERT Function Module for









RPY_TABLE_INSERT is a standard rpy table insert 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 rpy table insert FM, simply by entering the name RPY_TABLE_INSERT into the relevant SAP transaction such as SE37 or SE38.

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



Function RPY_TABLE_INSERT 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 'RPY_TABLE_INSERT'"
EXPORTING
* LANGUAGE = SY-LANGU "
TABLE_NAME = "
* WITH_DOCU = ' ' "
* DOCUTYPE = 'T' "
* TRANSPORT_NUMBER = ' ' "
* DEVELOPMENT_CLASS = '$TMP' "
TABL_INF = "
* TABL_TECHNICS = ' ' "

TABLES
TABL_FIELDS = "
* DOCU_TABLE_USER = "Table of documentation in free format
* DOCU_TABLE_TECH = "

EXCEPTIONS
CANCELLED = 1 ALREADY_EXIST = 2 PERMISSION_ERROR = 3 NAME_NOT_ALLOWED = 4 NAME_CONFLICT = 5 DB_ACCESS_ERROR = 6
.



IMPORTING Parameters details for RPY_TABLE_INSERT

LANGUAGE -

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

TABLE_NAME -

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

WITH_DOCU -

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

DOCUTYPE -

Data type: RGLIF-DOCUTYPE
Default: 'T'
Optional: Yes
Call by Reference: No ( called with pass by value option)

TRANSPORT_NUMBER -

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

DEVELOPMENT_CLASS -

Data type: RGLIF-DEVCLASS
Default: '$TMP'
Optional: Yes
Call by Reference: No ( called with pass by value option)

TABL_INF -

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

TABL_TECHNICS -

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

TABLES Parameters details for RPY_TABLE_INSERT

TABL_FIELDS -

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

DOCU_TABLE_USER - Table of documentation in free format

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

DOCU_TABLE_TECH -

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

EXCEPTIONS details

CANCELLED -

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

ALREADY_EXIST -

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

PERMISSION_ERROR -

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

NAME_NOT_ALLOWED -

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

NAME_CONFLICT -

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

DB_ACCESS_ERROR -

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

Copy and paste ABAP code example for RPY_TABLE_INSERT 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_language  TYPE SY-LANGU, "   SY-LANGU
lv_cancelled  TYPE SY, "   
lt_tabl_fields  TYPE STANDARD TABLE OF RPY_FIEL_U, "   
lv_table_name  TYPE RPY_TABL-TABLNAME, "   
lv_already_exist  TYPE RPY_TABL, "   
lt_docu_table_user  TYPE STANDARD TABLE OF RPY_OBJTAB, "   
lv_with_docu  TYPE RGLIF-WITH_DOCU, "   SPACE
lt_docu_table_tech  TYPE STANDARD TABLE OF TLINE, "   
lv_permission_error  TYPE TLINE, "   
lv_docutype  TYPE RGLIF-DOCUTYPE, "   'T'
lv_name_not_allowed  TYPE RGLIF, "   
lv_name_conflict  TYPE RGLIF, "   
lv_transport_number  TYPE RGLIF-TRKORR, "   SPACE
lv_db_access_error  TYPE RGLIF, "   
lv_development_class  TYPE RGLIF-DEVCLASS, "   '$TMP'
lv_tabl_inf  TYPE RPY_TABL, "   
lv_tabl_technics  TYPE RPY_TBTECH. "   SPACE

  CALL FUNCTION 'RPY_TABLE_INSERT'  "
    EXPORTING
         LANGUAGE = lv_language
         TABLE_NAME = lv_table_name
         WITH_DOCU = lv_with_docu
         DOCUTYPE = lv_docutype
         TRANSPORT_NUMBER = lv_transport_number
         DEVELOPMENT_CLASS = lv_development_class
         TABL_INF = lv_tabl_inf
         TABL_TECHNICS = lv_tabl_technics
    TABLES
         TABL_FIELDS = lt_tabl_fields
         DOCU_TABLE_USER = lt_docu_table_user
         DOCU_TABLE_TECH = lt_docu_table_tech
    EXCEPTIONS
        CANCELLED = 1
        ALREADY_EXIST = 2
        PERMISSION_ERROR = 3
        NAME_NOT_ALLOWED = 4
        NAME_CONFLICT = 5
        DB_ACCESS_ERROR = 6
. " RPY_TABLE_INSERT




ABAP code using 7.40 inline data declarations to call FM RPY_TABLE_INSERT

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 LANGU FROM SY INTO @DATA(ld_language).
DATA(ld_language) = SY-LANGU.
 
 
 
"SELECT single TABLNAME FROM RPY_TABL INTO @DATA(ld_table_name).
 
 
 
"SELECT single WITH_DOCU FROM RGLIF INTO @DATA(ld_with_docu).
DATA(ld_with_docu) = ' '.
 
 
 
"SELECT single DOCUTYPE FROM RGLIF INTO @DATA(ld_docutype).
DATA(ld_docutype) = 'T'.
 
 
 
"SELECT single TRKORR FROM RGLIF INTO @DATA(ld_transport_number).
DATA(ld_transport_number) = ' '.
 
 
"SELECT single DEVCLASS FROM RGLIF INTO @DATA(ld_development_class).
DATA(ld_development_class) = '$TMP'.
 
 
DATA(ld_tabl_technics) = ' '.
 


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!