SAP OBJECT_KEY_GET_O2 Function Module for









OBJECT_KEY_GET_O2 is a standard object key get o2 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 object key get o2 FM, simply by entering the name OBJECT_KEY_GET_O2 into the relevant SAP transaction such as SE37 or SE38.

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



Function OBJECT_KEY_GET_O2 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_O2'"
EXPORTING
OBJNR = "General Object Number

IMPORTING
BEDID = "Capacity requirement ID
BEDZL = "Sequential counter
CANUM = "Counter for KBED records

EXCEPTIONS
NOT_FOUND = 1 WRONG_OBART = 2
.



IMPORTING Parameters details for OBJECT_KEY_GET_O2

OBJNR - General Object Number

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

EXPORTING Parameters details for OBJECT_KEY_GET_O2

BEDID - Capacity requirement ID

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

BEDZL - Sequential counter

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

CANUM - Counter for KBED records

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

EXCEPTIONS details

NOT_FOUND - Object not found

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

WRONG_OBART - Incorrect object type

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

Copy and paste ABAP code example for OBJECT_KEY_GET_O2 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_bedid  TYPE IONRA-BEDID, "   
lv_objnr  TYPE ONR00-OBJNR, "   
lv_not_found  TYPE ONR00, "   
lv_bedzl  TYPE IONRA-BEDZL, "   
lv_wrong_obart  TYPE IONRA, "   
lv_canum  TYPE IONRA-CANUM. "   

  CALL FUNCTION 'OBJECT_KEY_GET_O2'  "
    EXPORTING
         OBJNR = lv_objnr
    IMPORTING
         BEDID = lv_bedid
         BEDZL = lv_bedzl
         CANUM = lv_canum
    EXCEPTIONS
        NOT_FOUND = 1
        WRONG_OBART = 2
. " OBJECT_KEY_GET_O2




ABAP code using 7.40 inline data declarations to call FM OBJECT_KEY_GET_O2

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 BEDID FROM IONRA INTO @DATA(ld_bedid).
 
"SELECT single OBJNR FROM ONR00 INTO @DATA(ld_objnr).
 
 
"SELECT single BEDZL FROM IONRA INTO @DATA(ld_bedzl).
 
 
"SELECT single CANUM FROM IONRA INTO @DATA(ld_canum).
 


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!