SAP RPY_TRANSACTION_INSERT Function Module for









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

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



Function RPY_TRANSACTION_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_TRANSACTION_INSERT'"
EXPORTING
TRANSACTION = "
SHORTTEXT = "
* CALLED_TRANSACTION = "
* CALLED_TRANSACTION_SKIP = "
* VARIANT = "Variant
* CL_INDEPENDEND = "
* EASY_WEB_TRANSACTION = "Easy Web Transaction
* PROFESSIONEL_USER_TRANSACTION = "Professional user transaction
* HTML_ENABLED = "SAPGUI for HTML
* JAVA_ENABLED = "SAPGUI for Java
* WINGUI_ENABLED = "Windows 32
* PROGRAM = "Program Name
* SERVICEFILE = "Service name of Internet Application Component
* GENFLAG = ' ' "Generation Flag
* SUPPRESS_CORR_INSERT = ' ' "Single-Character Flag
* DYNPRO = "Screen Number
* LANGUAGE = SY-LANGU "
* WITH_DOCU = ' ' "
* DOCUTYPE = 'T' "
* DEVELOPMENT_CLASS = '$TMP' "
* TRANSPORT_NUMBER = "
* TRANSACTION_TYPE = 'D' "

TABLES
* DOCU_TABLE_USER = "Table of documentation in free format
* DOCU_TABLE_TECH = "
* PARAM_VALUES = "Parameter transaction: Field name for parameter passing

EXCEPTIONS
CANCELLED = 1 ALREADY_EXIST = 2 PERMISSION_ERROR = 3 NAME_NOT_ALLOWED = 4 NAME_CONFLICT = 5 ILLEGAL_TYPE = 6 OBJECT_INCONSISTENT = 7 DB_ACCESS_ERROR = 8
.




Customer Function user exits

Below is a list of CUSTOMER FUNCTION exit user exits that are available within this program and maybe relevant for this FM.
EXIT_SAPLSEUK_001 Exit Transaction Code Maintenance (Invisible Call)
EXIT_SAPLSEUK_002 Exit Transaction Code Maintenance

IMPORTING Parameters details for RPY_TRANSACTION_INSERT

TRANSACTION -

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

SHORTTEXT -

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

CALLED_TRANSACTION -

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

CALLED_TRANSACTION_SKIP -

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

VARIANT - Variant

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

CL_INDEPENDEND -

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

EASY_WEB_TRANSACTION - Easy Web Transaction

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

PROFESSIONEL_USER_TRANSACTION - Professional user transaction

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

HTML_ENABLED - SAPGUI for HTML

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

JAVA_ENABLED - SAPGUI for Java

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

WINGUI_ENABLED - Windows 32

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

PROGRAM - Program Name

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

SERVICEFILE - Service name of Internet Application Component

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

GENFLAG - Generation Flag

Data type: TADIR-GENFLAG
Default: SPACE
Optional: No
Call by Reference: No ( called with pass by value option)

SUPPRESS_CORR_INSERT - Single-Character Flag

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

DYNPRO - Screen Number

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

LANGUAGE -

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

WITH_DOCU -

Data type: RGLIF-WITH_DOCU
Default: ' '
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)

DEVELOPMENT_CLASS -

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

TRANSPORT_NUMBER -

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

TRANSACTION_TYPE -

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

TABLES Parameters details for RPY_TRANSACTION_INSERT

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)

PARAM_VALUES - Parameter transaction: Field name for parameter passing

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

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)

ILLEGAL_TYPE -

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

OBJECT_INCONSISTENT -

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_TRANSACTION_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_cancelled  TYPE STRING, "   
lv_transaction  TYPE TSTC-TCODE, "   
lt_docu_table_user  TYPE STANDARD TABLE OF RPY_OBJTAB, "   
lv_shorttext  TYPE TSTCT-TTEXT, "   
lv_called_transaction  TYPE TSTC-TCODE, "   
lv_called_transaction_skip  TYPE CHAR01, "   
lv_variant  TYPE TCVARIANT, "   
lv_cl_independend  TYPE CHAR01, "   
lv_easy_web_transaction  TYPE S_EWT, "   
lv_professionel_user_transaction  TYPE S_PROF, "   
lv_html_enabled  TYPE S_WEBGUI, "   
lv_java_enabled  TYPE S_PLATIN, "   
lv_wingui_enabled  TYPE S_WIN32, "   
lv_program  TYPE TRDIR-NAME, "   
lv_already_exist  TYPE TRDIR, "   
lt_docu_table_tech  TYPE STANDARD TABLE OF TLINE, "   
lv_servicefile  TYPE IACSERVIC_, "   
lv_genflag  TYPE TADIR-GENFLAG, "   SPACE
lv_suppress_corr_insert  TYPE CHAR1, "   SPACE
lv_dynpro  TYPE D020S-DNUM, "   
lt_param_values  TYPE STANDARD TABLE OF RSPARAM, "   
lv_permission_error  TYPE RSPARAM, "   
lv_language  TYPE SY-LANGU, "   SY-LANGU
lv_name_not_allowed  TYPE SY, "   
lv_with_docu  TYPE RGLIF-WITH_DOCU, "   ' '
lv_name_conflict  TYPE RGLIF, "   
lv_docutype  TYPE RGLIF-DOCUTYPE, "   'T'
lv_illegal_type  TYPE RGLIF, "   
lv_development_class  TYPE RGLIF-DEVCLASS, "   '$TMP'
lv_object_inconsistent  TYPE RGLIF, "   
lv_db_access_error  TYPE RGLIF, "   
lv_transport_number  TYPE RGLIF-TRKORR, "   
lv_transaction_type  TYPE RGLIF-DOCUTYPE. "   'D'

  CALL FUNCTION 'RPY_TRANSACTION_INSERT'  "
    EXPORTING
         TRANSACTION = lv_transaction
         SHORTTEXT = lv_shorttext
         CALLED_TRANSACTION = lv_called_transaction
         CALLED_TRANSACTION_SKIP = lv_called_transaction_skip
         VARIANT = lv_variant
         CL_INDEPENDEND = lv_cl_independend
         EASY_WEB_TRANSACTION = lv_easy_web_transaction
         PROFESSIONEL_USER_TRANSACTION = lv_professionel_user_transaction
         HTML_ENABLED = lv_html_enabled
         JAVA_ENABLED = lv_java_enabled
         WINGUI_ENABLED = lv_wingui_enabled
         PROGRAM = lv_program
         SERVICEFILE = lv_servicefile
         GENFLAG = lv_genflag
         SUPPRESS_CORR_INSERT = lv_suppress_corr_insert
         DYNPRO = lv_dynpro
         LANGUAGE = lv_language
         WITH_DOCU = lv_with_docu
         DOCUTYPE = lv_docutype
         DEVELOPMENT_CLASS = lv_development_class
         TRANSPORT_NUMBER = lv_transport_number
         TRANSACTION_TYPE = lv_transaction_type
    TABLES
         DOCU_TABLE_USER = lt_docu_table_user
         DOCU_TABLE_TECH = lt_docu_table_tech
         PARAM_VALUES = lt_param_values
    EXCEPTIONS
        CANCELLED = 1
        ALREADY_EXIST = 2
        PERMISSION_ERROR = 3
        NAME_NOT_ALLOWED = 4
        NAME_CONFLICT = 5
        ILLEGAL_TYPE = 6
        OBJECT_INCONSISTENT = 7
        DB_ACCESS_ERROR = 8
. " RPY_TRANSACTION_INSERT




ABAP code using 7.40 inline data declarations to call FM RPY_TRANSACTION_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 TCODE FROM TSTC INTO @DATA(ld_transaction).
 
 
"SELECT single TTEXT FROM TSTCT INTO @DATA(ld_shorttext).
 
"SELECT single TCODE FROM TSTC INTO @DATA(ld_called_transaction).
 
 
 
 
 
 
 
 
 
"SELECT single NAME FROM TRDIR INTO @DATA(ld_program).
 
 
 
 
"SELECT single GENFLAG FROM TADIR INTO @DATA(ld_genflag).
DATA(ld_genflag) = ' '.
 
DATA(ld_suppress_corr_insert) = ' '.
 
"SELECT single DNUM FROM D020S INTO @DATA(ld_dynpro).
 
 
 
"SELECT single LANGU FROM SY INTO @DATA(ld_language).
DATA(ld_language) = SY-LANGU.
 
 
"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 DEVCLASS FROM RGLIF INTO @DATA(ld_development_class).
DATA(ld_development_class) = '$TMP'.
 
 
 
"SELECT single TRKORR FROM RGLIF INTO @DATA(ld_transport_number).
 
"SELECT single DOCUTYPE FROM RGLIF INTO @DATA(ld_transaction_type).
DATA(ld_transaction_type) = 'D'.
 


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!