SAP RE_TRANSACTION_GET Function Module for









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

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



Function RE_TRANSACTION_GET 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 'RE_TRANSACTION_GET'"
EXPORTING
I_KEY = "

IMPORTING
ET_FUNCTIONS = "

EXCEPTIONS
UNKNOWN_OBJECT_TYPE = 1 NAME_OF_KEY_NOT_VALID = 2 OBJECT_KEY_NOT_FOUND = 3
.



IMPORTING Parameters details for RE_TRANSACTION_GET

I_KEY -

Data type: VIREKEY
Optional: No
Call by Reference: Yes

EXPORTING Parameters details for RE_TRANSACTION_GET

ET_FUNCTIONS -

Data type: FVIOT_TP_T_FUNCTIONS
Optional: No
Call by Reference: Yes

EXCEPTIONS details

UNKNOWN_OBJECT_TYPE -

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

NAME_OF_KEY_NOT_VALID -

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

OBJECT_KEY_NOT_FOUND -

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

Copy and paste ABAP code example for RE_TRANSACTION_GET 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_i_key  TYPE VIREKEY, "   
lv_et_functions  TYPE FVIOT_TP_T_FUNCTIONS, "   
lv_unknown_object_type  TYPE FVIOT_TP_T_FUNCTIONS, "   
lv_name_of_key_not_valid  TYPE FVIOT_TP_T_FUNCTIONS, "   
lv_object_key_not_found  TYPE FVIOT_TP_T_FUNCTIONS. "   

  CALL FUNCTION 'RE_TRANSACTION_GET'  "
    EXPORTING
         I_KEY = lv_i_key
    IMPORTING
         ET_FUNCTIONS = lv_et_functions
    EXCEPTIONS
        UNKNOWN_OBJECT_TYPE = 1
        NAME_OF_KEY_NOT_VALID = 2
        OBJECT_KEY_NOT_FOUND = 3
. " RE_TRANSACTION_GET




ABAP code using 7.40 inline data declarations to call FM RE_TRANSACTION_GET

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.

 
 
 
 
 


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!