SAP OBJECT_KEY_GET_EK Function Module for NOTRANSL: Ermittlung des Objektkeys zur Erzeugniskalkulation
OBJECT_KEY_GET_EK is a standard object key get ek SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for NOTRANSL: Ermittlung des Objektkeys zur Erzeugniskalkulation 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 ek FM, simply by entering the name OBJECT_KEY_GET_EK into the relevant SAP transaction such as SE37 or SE38.
Function Group: BOEK
Program Name: SAPLBOEK
Main Program:
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function OBJECT_KEY_GET_EK 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_EK'"NOTRANSL: Ermittlung des Objektkeys zur Erzeugniskalkulation.
EXPORTING
OBJNR = "General Object Number
IMPORTING
BZOBJ = "Reference Object
KALNR = "Cost Estimate Number - Product Costing
KALKA = "Costing Type
KADKY = "Costing Date (Key)
TVERS = "Costing Version
BWVAR = "Valuation Variant in Costing
KKZMA = "DE-EN-LANG-SWITCH-NO-TRANSLATION
E_IONRA = "
EXCEPTIONS
NOT_FOUND = 1 WRONG_OBART = 2
IMPORTING Parameters details for OBJECT_KEY_GET_EK
OBJNR - General Object Number
Data type: ONR00-OBJNROptional: No
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for OBJECT_KEY_GET_EK
BZOBJ - Reference Object
Data type: CK_OBJOptional: No
Call by Reference: Yes
KALNR - Cost Estimate Number - Product Costing
Data type: CK_KALNR1Optional: No
Call by Reference: Yes
KALKA - Costing Type
Data type: CK_KALKAOptional: No
Call by Reference: Yes
KADKY - Costing Date (Key)
Data type: CK_KADKYOptional: No
Call by Reference: Yes
TVERS - Costing Version
Data type: CK_TVERSOptional: No
Call by Reference: Yes
BWVAR - Valuation Variant in Costing
Data type: CK_BWVAROptional: No
Call by Reference: Yes
KKZMA - DE-EN-LANG-SWITCH-NO-TRANSLATION
Data type: CK_KKZMAOptional: No
Call by Reference: Yes
E_IONRA -
Data type: IONRAOptional: No
Call by Reference: Yes
EXCEPTIONS details
NOT_FOUND - Object Not Found
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
WRONG_OBART - DE-EN-LANG-SWITCH-NO-TRANSLATION
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for OBJECT_KEY_GET_EK 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_bzobj | TYPE CK_OBJ, " | |||
| lv_objnr | TYPE ONR00-OBJNR, " | |||
| lv_not_found | TYPE ONR00, " | |||
| lv_kalnr | TYPE CK_KALNR1, " | |||
| lv_wrong_obart | TYPE CK_KALNR1, " | |||
| lv_kalka | TYPE CK_KALKA, " | |||
| lv_kadky | TYPE CK_KADKY, " | |||
| lv_tvers | TYPE CK_TVERS, " | |||
| lv_bwvar | TYPE CK_BWVAR, " | |||
| lv_kkzma | TYPE CK_KKZMA, " | |||
| lv_e_ionra | TYPE IONRA. " |
|   CALL FUNCTION 'OBJECT_KEY_GET_EK' "NOTRANSL: Ermittlung des Objektkeys zur Erzeugniskalkulation |
| EXPORTING | ||
| OBJNR | = lv_objnr | |
| IMPORTING | ||
| BZOBJ | = lv_bzobj | |
| KALNR | = lv_kalnr | |
| KALKA | = lv_kalka | |
| KADKY | = lv_kadky | |
| TVERS | = lv_tvers | |
| BWVAR | = lv_bwvar | |
| KKZMA | = lv_kkzma | |
| E_IONRA | = lv_e_ionra | |
| EXCEPTIONS | ||
| NOT_FOUND = 1 | ||
| WRONG_OBART = 2 | ||
| . " OBJECT_KEY_GET_EK | ||
ABAP code using 7.40 inline data declarations to call FM OBJECT_KEY_GET_EK
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 OBJNR FROM ONR00 INTO @DATA(ld_objnr). | ||||
Search for further information about these or an SAP related objects