SAP FINDR_TR_KEYS Function Module for

Search SAP Function Modules

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

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

Function FINDR_TR_KEYS 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 'FINDR_TR_KEYS'"
  EXPORTING
   I_APPLCLASS =  "Application class for DD objects (not used)
   I_SUBCLASS =  "Subgroup by Application Class
   I_STRATID =  "Strategy ID
   I_ENV =  "Environment for strategy
   I_REQUEST =  "Request/Task
   I_TASK =  "Request/Task
*  I_TRANSPORT_RULE_ENTRIES = 'X' "

 IMPORTING
   ETR_OBJECTS =  "Objects
   ETR_KEYS =  "Table Keys

EXCEPTIONS
   FAILED = 1 

.

IMPORTING Parameters details for FINDR_TR_KEYS

I_APPLCLASS - Application class for DD objects (not used)

Data type: TABADR-APPLCLASS
Optional: No
Call by Reference: Yes

I_SUBCLASS - Subgroup by Application Class

Data type: TABADR-SUBCLASS
Optional: No
Call by Reference: Yes

I_STRATID - Strategy ID

Data type: TABADR-ABADRSTRATID
Optional: No
Call by Reference: Yes

I_ENV - Environment for strategy

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

I_REQUEST - Request/Task

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

I_TASK - Request/Task

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

I_TRANSPORT_RULE_ENTRIES -

Data type: FLAG
Default: 'X'
Optional: Yes
Call by Reference: Yes

EXPORTING Parameters details for FINDR_TR_KEYS

ETR_OBJECTS - Objects

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

ETR_KEYS - Table Keys

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

EXCEPTIONS details

FAILED -

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

Copy and paste ABAP code example for FINDR_TR_KEYS 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.

ABAP code using 7.40 inline data declarations to call FM FINDR_TR_KEYS

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