SAP OBJECT_NUMBER_READ_GENERIC Function Module for









OBJECT_NUMBER_READ_GENERIC is a standard object number read generic 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 number read generic FM, simply by entering the name OBJECT_NUMBER_READ_GENERIC into the relevant SAP transaction such as SE37 or SE38.

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



Function OBJECT_NUMBER_READ_GENERIC 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_NUMBER_READ_GENERIC'"
EXPORTING
I_OBART = "Object Type
I_OBJECTKEY = "Object Key

IMPORTING
E_OBJNR = "General Object Number

EXCEPTIONS
OBART_INVALID = 1 KEY_TOO_LONG = 2 OBJECTKEY_INVALID = 3
.



IMPORTING Parameters details for OBJECT_NUMBER_READ_GENERIC

I_OBART - Object Type

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

I_OBJECTKEY - Object Key

Data type:
Optional: No
Call by Reference: Yes

EXPORTING Parameters details for OBJECT_NUMBER_READ_GENERIC

E_OBJNR - General Object Number

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

EXCEPTIONS details

OBART_INVALID -

Data type:
Optional: No
Call by Reference: Yes

KEY_TOO_LONG -

Data type:
Optional: No
Call by Reference: Yes

OBJECTKEY_INVALID - Object key invalid

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for OBJECT_NUMBER_READ_GENERIC 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_e_objnr  TYPE STRING, "   
lv_i_obart  TYPE J_OBART, "   
lv_obart_invalid  TYPE J_OBART, "   
lv_i_objectkey  TYPE J_OBART, "   
lv_key_too_long  TYPE J_OBART, "   
lv_objectkey_invalid  TYPE J_OBART. "   

  CALL FUNCTION 'OBJECT_NUMBER_READ_GENERIC'  "
    EXPORTING
         I_OBART = lv_i_obart
         I_OBJECTKEY = lv_i_objectkey
    IMPORTING
         E_OBJNR = lv_e_objnr
    EXCEPTIONS
        OBART_INVALID = 1
        KEY_TOO_LONG = 2
        OBJECTKEY_INVALID = 3
. " OBJECT_NUMBER_READ_GENERIC




ABAP code using 7.40 inline data declarations to call FM OBJECT_NUMBER_READ_GENERIC

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



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!