SAP KEY_ZU_OBJEKT Function Module for Returns key structure for SAP object









KEY_ZU_OBJEKT is a standard key zu objekt SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Returns key structure for SAP object 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 key zu objekt FM, simply by entering the name KEY_ZU_OBJEKT into the relevant SAP transaction such as SE37 or SE38.

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



Function KEY_ZU_OBJEKT 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 'KEY_ZU_OBJEKT'"Returns key structure for SAP object
EXPORTING
OBJEKT = "Linked SAP Object

IMPORTING
KEY1 = "
KEY9 = "
LEN1 = "
LEN10 = "
LEN2 = "
LEN3 = "
LEN4 = "
LEN5 = "
LEN6 = "
LEN7 = "
LEN8 = "
KEY10 = "
LEN9 = "
KEY2 = "
KEY3 = "
KEY4 = "
KEY5 = "
KEY6 = "
KEY7 = "
KEY8 = "

EXCEPTIONS
NO_OBJEKT = 1
.



IMPORTING Parameters details for KEY_ZU_OBJEKT

OBJEKT - Linked SAP Object

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

EXPORTING Parameters details for KEY_ZU_OBJEKT

KEY1 -

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

KEY9 -

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

LEN1 -

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

LEN10 -

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

LEN2 -

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

LEN3 -

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

LEN4 -

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

LEN5 -

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

LEN6 -

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

LEN7 -

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

LEN8 -

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

KEY10 -

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

LEN9 -

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

KEY2 -

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

KEY3 -

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

KEY4 -

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

KEY5 -

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

KEY6 -

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

KEY7 -

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

KEY8 -

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

EXCEPTIONS details

NO_OBJEKT -

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

Copy and paste ABAP code example for KEY_ZU_OBJEKT 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_key1  TYPE STRING, "   
lv_objekt  TYPE DRAD-DOKOB, "   
lv_no_objekt  TYPE DRAD, "   
lv_key9  TYPE DRAD, "   
lv_len1  TYPE DRAD, "   
lv_len10  TYPE DRAD, "   
lv_len2  TYPE DRAD, "   
lv_len3  TYPE DRAD, "   
lv_len4  TYPE DRAD, "   
lv_len5  TYPE DRAD, "   
lv_len6  TYPE DRAD, "   
lv_len7  TYPE DRAD, "   
lv_len8  TYPE DRAD, "   
lv_key10  TYPE DRAD, "   
lv_len9  TYPE DRAD, "   
lv_key2  TYPE DRAD, "   
lv_key3  TYPE DRAD, "   
lv_key4  TYPE DRAD, "   
lv_key5  TYPE DRAD, "   
lv_key6  TYPE DRAD, "   
lv_key7  TYPE DRAD, "   
lv_key8  TYPE DRAD. "   

  CALL FUNCTION 'KEY_ZU_OBJEKT'  "Returns key structure for SAP object
    EXPORTING
         OBJEKT = lv_objekt
    IMPORTING
         KEY1 = lv_key1
         KEY9 = lv_key9
         LEN1 = lv_len1
         LEN10 = lv_len10
         LEN2 = lv_len2
         LEN3 = lv_len3
         LEN4 = lv_len4
         LEN5 = lv_len5
         LEN6 = lv_len6
         LEN7 = lv_len7
         LEN8 = lv_len8
         KEY10 = lv_key10
         LEN9 = lv_len9
         KEY2 = lv_key2
         KEY3 = lv_key3
         KEY4 = lv_key4
         KEY5 = lv_key5
         KEY6 = lv_key6
         KEY7 = lv_key7
         KEY8 = lv_key8
    EXCEPTIONS
        NO_OBJEKT = 1
. " KEY_ZU_OBJEKT




ABAP code using 7.40 inline data declarations to call FM KEY_ZU_OBJEKT

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 DOKOB FROM DRAD INTO @DATA(ld_objekt).
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 


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!