SAP OBJECT_KEY_GET_T1 Function Module for Determine Object Key for Loan Object Number
OBJECT_KEY_GET_T1 is a standard object key get t1 SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Determine Object Key for Loan Object Number processing and below is the pattern details for this FM, 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 object key get t1 FM, simply by entering the name OBJECT_KEY_GET_T1 into the relevant SAP transaction such as SE37 or SE38.
Function Group: BOT1
Program Name: SAPLBOT1
Main Program: SAPLBOT1
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:
Function OBJECT_KEY_GET_T1 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 'OBJECT_KEY_GET_T1'"Determine Object Key for Loan Object Number.
EXPORTING
OBJNR = "
IMPORTING
BUKRS = "
RANL = "
EXCEPTIONS
WRONG_OBART = 1
IMPORTING Parameters details for OBJECT_KEY_GET_T1
OBJNR -
Data type: ONR00-OBJNROptional: No
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for OBJECT_KEY_GET_T1
BUKRS -
Data type: IONRA-BUKRSOptional: No
Call by Reference: No ( called with pass by value option)
RANL -
Data type: IONRA-RANLOptional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
WRONG_OBART -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for OBJECT_KEY_GET_T1 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_bukrs | TYPE IONRA-BUKRS, " | |||
lv_objnr | TYPE ONR00-OBJNR, " | |||
lv_wrong_obart | TYPE ONR00, " | |||
lv_ranl | TYPE IONRA-RANL. " |
  CALL FUNCTION 'OBJECT_KEY_GET_T1' "Determine Object Key for Loan Object Number |
EXPORTING | ||
OBJNR | = lv_objnr | |
IMPORTING | ||
BUKRS | = lv_bukrs | |
RANL | = lv_ranl | |
EXCEPTIONS | ||
WRONG_OBART = 1 | ||
. " OBJECT_KEY_GET_T1 |
ABAP code using 7.40 inline data declarations to call FM OBJECT_KEY_GET_T1
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 BUKRS FROM IONRA INTO @DATA(ld_bukrs). | ||||
"SELECT single OBJNR FROM ONR00 INTO @DATA(ld_objnr). | ||||
"SELECT single RANL FROM IONRA INTO @DATA(ld_ranl). | ||||
Search for further information about these or an SAP related objects