SAP TR_RECORD_OBJ_CHANGE_TO_REQ Function Module for









TR_RECORD_OBJ_CHANGE_TO_REQ is a standard tr record obj change to req 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 tr record obj change to req FM, simply by entering the name TR_RECORD_OBJ_CHANGE_TO_REQ into the relevant SAP transaction such as SE37 or SE38.

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



Function TR_RECORD_OBJ_CHANGE_TO_REQ 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 'TR_RECORD_OBJ_CHANGE_TO_REQ'"
EXPORTING
IV_REQUEST = "
* IT_OBJECTS = "Objects for Processing (Correction Interface)
* IT_KEYS = "Table Keys for Processing (Correction Interface)
* IT_E071K_STR = "
* IT_OBJ_ENTRIES = "

IMPORTING
EV_NO_RECORDING = "
ET_TADIR = "Object Directory

EXCEPTIONS
CANCEL = 1
.



IMPORTING Parameters details for TR_RECORD_OBJ_CHANGE_TO_REQ

IV_REQUEST -

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

IT_OBJECTS - Objects for Processing (Correction Interface)

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

IT_KEYS - Table Keys for Processing (Correction Interface)

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

IT_E071K_STR -

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

IT_OBJ_ENTRIES -

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

EXPORTING Parameters details for TR_RECORD_OBJ_CHANGE_TO_REQ

EV_NO_RECORDING -

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

ET_TADIR - Object Directory

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

EXCEPTIONS details

CANCEL -

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for TR_RECORD_OBJ_CHANGE_TO_REQ 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_cancel  TYPE STRING, "   
lv_iv_request  TYPE TRKORR, "   
lv_ev_no_recording  TYPE TRBOOLEAN, "   
lv_et_tadir  TYPE SCTS_TADIR, "   
lv_it_objects  TYPE TREDT_OBJECTS, "   
lv_it_keys  TYPE TREDT_KEYS, "   
lv_it_e071k_str  TYPE E071K_STRTYP, "   
lv_it_obj_entries  TYPE CTS_OBJ_ENTRIES. "   

  CALL FUNCTION 'TR_RECORD_OBJ_CHANGE_TO_REQ'  "
    EXPORTING
         IV_REQUEST = lv_iv_request
         IT_OBJECTS = lv_it_objects
         IT_KEYS = lv_it_keys
         IT_E071K_STR = lv_it_e071k_str
         IT_OBJ_ENTRIES = lv_it_obj_entries
    IMPORTING
         EV_NO_RECORDING = lv_ev_no_recording
         ET_TADIR = lv_et_tadir
    EXCEPTIONS
        CANCEL = 1
. " TR_RECORD_OBJ_CHANGE_TO_REQ




ABAP code using 7.40 inline data declarations to call FM TR_RECORD_OBJ_CHANGE_TO_REQ

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!