SAP OBJECT_NUMBER_GET_RU Function Module for
OBJECT_NUMBER_GET_RU is a standard object number get ru 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 ru FM, simply by entering the name OBJECT_NUMBER_GET_RU into the relevant SAP transaction such as SE37 or SE38.
Function Group: BORU
Program Name: SAPLBORU
Main Program:
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function OBJECT_NUMBER_GET_RU 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_RU'".
EXPORTING
RUECK = "Confirmation Number
RMZHL = "Confirmation Counter
IMPORTING
OBJNR = "General Object Number
IMPORTING Parameters details for OBJECT_NUMBER_GET_RU
RUECK - Confirmation Number
Data type: IONRA-RUECKOptional: No
Call by Reference: No ( called with pass by value option)
RMZHL - Confirmation Counter
Data type: IONRA-RMZHLOptional: No
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for OBJECT_NUMBER_GET_RU
OBJNR - General Object Number
Data type: ONR00-OBJNROptional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for OBJECT_NUMBER_GET_RU 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_rueck | TYPE IONRA-RUECK, " | |||
| lv_rmzhl | TYPE IONRA-RMZHL. " |
|   CALL FUNCTION 'OBJECT_NUMBER_GET_RU' " |
| EXPORTING | ||
| RUECK | = lv_rueck | |
| RMZHL | = lv_rmzhl | |
| IMPORTING | ||
| OBJNR | = lv_objnr | |
| . " OBJECT_NUMBER_GET_RU | ||
ABAP code using 7.40 inline data declarations to call FM OBJECT_NUMBER_GET_RU
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 RUECK FROM IONRA INTO @DATA(ld_rueck). | ||||
| "SELECT single RMZHL FROM IONRA INTO @DATA(ld_rmzhl). | ||||
Search for further information about these or an SAP related objects