SAP OBJECT_NUMBER_GET_I2 Function Module for









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

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



Function OBJECT_NUMBER_GET_I2 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_GET_I2'"
EXPORTING
MANDATEID = "

IMPORTING
OBJNR = "

EXCEPTIONS
NUMBER_ALREADY_EXISTS = 1
.



IMPORTING Parameters details for OBJECT_NUMBER_GET_I2

MANDATEID -

Data type: REOBJECTKEYS-MANDATEID
Optional: No
Call by Reference: Yes

EXPORTING Parameters details for OBJECT_NUMBER_GET_I2

OBJNR -

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

EXCEPTIONS details

NUMBER_ALREADY_EXISTS -

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

Copy and paste ABAP code example for OBJECT_NUMBER_GET_I2 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 REOBJECTKEYS-OBJNR, "   
lv_mandateid  TYPE REOBJECTKEYS-MANDATEID, "   
lv_number_already_exists  TYPE REOBJECTKEYS. "   

  CALL FUNCTION 'OBJECT_NUMBER_GET_I2'  "
    EXPORTING
         MANDATEID = lv_mandateid
    IMPORTING
         OBJNR = lv_objnr
    EXCEPTIONS
        NUMBER_ALREADY_EXISTS = 1
. " OBJECT_NUMBER_GET_I2




ABAP code using 7.40 inline data declarations to call FM OBJECT_NUMBER_GET_I2

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 REOBJECTKEYS INTO @DATA(ld_objnr).
 
"SELECT single MANDATEID FROM REOBJECTKEYS INTO @DATA(ld_mandateid).
 
 


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!