SAP OBJECT_KEY_GET_NR Function Module for









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

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



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

IMPORTING
AUFPL_VOR = "Identification number of predecessor to a network
APLZL_VOR = "Sequential counter to distinguish database entries
AUFPL_NCH = "Identification number for successor to a network
APLZL_NCH = "Sequential counter to distinguish database entries
AOBAR = "Type of relationship
MIMAX = "Indicator as to whether maximum time is included

EXCEPTIONS
NOT_FOUND = 1 WRONG_OBART = 2
.



IMPORTING Parameters details for OBJECT_KEY_GET_NR

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_NR

AUFPL_VOR - Identification number of predecessor to a network

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

APLZL_VOR - Sequential counter to distinguish database entries

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

AUFPL_NCH - Identification number for successor to a network

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

APLZL_NCH - Sequential counter to distinguish database entries

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

AOBAR - Type of relationship

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

MIMAX - Indicator as to whether maximum time is included

Data type: IONRA-MIMAX
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_NR 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_objnr  TYPE ONR00-OBJNR, "   
lv_aufpl_vor  TYPE IONRA-AUFPL_VOR, "   
lv_not_found  TYPE IONRA, "   
lv_aplzl_vor  TYPE IONRA-APLZL_VOR, "   
lv_wrong_obart  TYPE IONRA, "   
lv_aufpl_nch  TYPE IONRA-AUFPL_NCH, "   
lv_aplzl_nch  TYPE IONRA-APLZL_NCH, "   
lv_aobar  TYPE IONRA-AOBAR, "   
lv_mimax  TYPE IONRA-MIMAX. "   

  CALL FUNCTION 'OBJECT_KEY_GET_NR'  "
    EXPORTING
         OBJNR = lv_objnr
    IMPORTING
         AUFPL_VOR = lv_aufpl_vor
         APLZL_VOR = lv_aplzl_vor
         AUFPL_NCH = lv_aufpl_nch
         APLZL_NCH = lv_aplzl_nch
         AOBAR = lv_aobar
         MIMAX = lv_mimax
    EXCEPTIONS
        NOT_FOUND = 1
        WRONG_OBART = 2
. " OBJECT_KEY_GET_NR




ABAP code using 7.40 inline data declarations to call FM OBJECT_KEY_GET_NR

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).
 
"SELECT single AUFPL_VOR FROM IONRA INTO @DATA(ld_aufpl_vor).
 
 
"SELECT single APLZL_VOR FROM IONRA INTO @DATA(ld_aplzl_vor).
 
 
"SELECT single AUFPL_NCH FROM IONRA INTO @DATA(ld_aufpl_nch).
 
"SELECT single APLZL_NCH FROM IONRA INTO @DATA(ld_aplzl_nch).
 
"SELECT single AOBAR FROM IONRA INTO @DATA(ld_aobar).
 
"SELECT single MIMAX FROM IONRA INTO @DATA(ld_mimax).
 


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!