SAP OBJECT_KEY_GET_TF Function Module for Get object key for Lot based Position in Futures Account
OBJECT_KEY_GET_TF is a standard object key get tf SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Get object key for Lot based Position in Futures Account 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 tf FM, simply by entering the name OBJECT_KEY_GET_TF into the relevant SAP transaction such as SE37 or SE38.
Function Group: BOTF
Program Name: SAPLBOTF
Main Program: SAPLBOTF
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function OBJECT_KEY_GET_TF 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_TF'"Get object key for Lot based Position in Futures Account.
EXPORTING
* I_OBJNR = "Object Number
IMPORTING
E_COMPANY_CODE = "Company Code
E_CLASS_ID = "Security ID Number
E_POSITION_ACCOUNT = "Futures Account for Listed Options and Futures
E_LOT_ID = "Identifier of the Lot
EXCEPTIONS
NOT_FOUND = 1 WRONG_OBART = 2
IMPORTING Parameters details for OBJECT_KEY_GET_TF
I_OBJNR - Object Number
Data type: J_OBJNROptional: Yes
Call by Reference: Yes
EXPORTING Parameters details for OBJECT_KEY_GET_TF
E_COMPANY_CODE - Company Code
Data type: BUKRSOptional: No
Call by Reference: No ( called with pass by value option)
E_CLASS_ID - Security ID Number
Data type: VVRANLWOptional: No
Call by Reference: No ( called with pass by value option)
E_POSITION_ACCOUNT - Futures Account for Listed Options and Futures
Data type: TPM_POS_ACCOUNT_FUTOptional: No
Call by Reference: No ( called with pass by value option)
E_LOT_ID - Identifier of the Lot
Data type: TPM_LOT_IDOptional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
NOT_FOUND -
Data type:Optional: No
Call by Reference: Yes
WRONG_OBART -
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for OBJECT_KEY_GET_TF 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_objnr | TYPE J_OBJNR, " | |||
| lv_not_found | TYPE J_OBJNR, " | |||
| lv_e_company_code | TYPE BUKRS, " | |||
| lv_e_class_id | TYPE VVRANLW, " | |||
| lv_wrong_obart | TYPE VVRANLW, " | |||
| lv_e_position_account | TYPE TPM_POS_ACCOUNT_FUT, " | |||
| lv_e_lot_id | TYPE TPM_LOT_ID. " |
|   CALL FUNCTION 'OBJECT_KEY_GET_TF' "Get object key for Lot based Position in Futures Account |
| EXPORTING | ||
| I_OBJNR | = lv_i_objnr | |
| IMPORTING | ||
| E_COMPANY_CODE | = lv_e_company_code | |
| E_CLASS_ID | = lv_e_class_id | |
| E_POSITION_ACCOUNT | = lv_e_position_account | |
| E_LOT_ID | = lv_e_lot_id | |
| EXCEPTIONS | ||
| NOT_FOUND = 1 | ||
| WRONG_OBART = 2 | ||
| . " OBJECT_KEY_GET_TF | ||
ABAP code using 7.40 inline data declarations to call FM OBJECT_KEY_GET_TF
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