SAP RH_OM_DETAILSCREEN_GETDATA Function Module for









RH_OM_DETAILSCREEN_GETDATA is a standard rh om detailscreen getdata 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 rh om detailscreen getdata FM, simply by entering the name RH_OM_DETAILSCREEN_GETDATA into the relevant SAP transaction such as SE37 or SE38.

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



Function RH_OM_DETAILSCREEN_GETDATA 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 'RH_OM_DETAILSCREEN_GETDATA'"
IMPORTING
SCENARIO = "
CHANGEMODE = "
REFR = "
TABTYPE = "
SELMODE = "
DATES_CHANGED = "
INPUT_DONE = "
TABCHANGED = "
EXIT_COMMAND = "
* SVECT = "Status Vector
DISP_CDOCS = "
CLASS_KEY = "
MAIN_OBJECT = "
RELAT_OBJECT = "
DATE = "
FUZZY_BEGDA = "
FUZZY_ENDDA = "
FUZZY_ENDDA_OV = "
DETAIL_DATE = "

TABLES
* LOC_VALUES = "
.



EXPORTING Parameters details for RH_OM_DETAILSCREEN_GETDATA

SCENARIO -

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

CHANGEMODE -

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

REFR -

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

TABTYPE -

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

SELMODE -

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

DATES_CHANGED -

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

INPUT_DONE -

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

TABCHANGED -

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

EXIT_COMMAND -

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

SVECT - Status Vector

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

DISP_CDOCS -

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

CLASS_KEY -

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

MAIN_OBJECT -

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

RELAT_OBJECT -

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

DATE -

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

FUZZY_BEGDA -

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

FUZZY_ENDDA -

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

FUZZY_ENDDA_OV -

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

DETAIL_DATE -

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

TABLES Parameters details for RH_OM_DETAILSCREEN_GETDATA

LOC_VALUES -

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

Copy and paste ABAP code example for RH_OM_DETAILSCREEN_GETDATA 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_scenario  TYPE HROMSCEN, "   
lt_loc_values  TYPE STANDARD TABLE OF HROMGENRED, "   
lv_changemode  TYPE OMACTMODE, "   
lv_refr  TYPE FLAG, "   
lv_tabtype  TYPE HRTABTYPE, "   
lv_selmode  TYPE OMSELDATEM, "   
lv_dates_changed  TYPE FLAG, "   
lv_input_done  TYPE FLAG, "   
lv_tabchanged  TYPE FLAG, "   
lv_exit_command  TYPE FLAG, "   
lv_svect  TYPE SVECT, "   
lv_disp_cdocs  TYPE FLAG, "   
lv_class_key  TYPE OMCLASSKEY, "   
lv_main_object  TYPE OBJEC, "   
lv_relat_object  TYPE OBJEC, "   
lv_date  TYPE SY-DATUM, "   
lv_fuzzy_begda  TYPE SY-DATUM, "   
lv_fuzzy_endda  TYPE SY-DATUM, "   
lv_fuzzy_endda_ov  TYPE SY-DATUM, "   
lv_detail_date  TYPE SY-DATUM. "   

  CALL FUNCTION 'RH_OM_DETAILSCREEN_GETDATA'  "
    IMPORTING
         SCENARIO = lv_scenario
         CHANGEMODE = lv_changemode
         REFR = lv_refr
         TABTYPE = lv_tabtype
         SELMODE = lv_selmode
         DATES_CHANGED = lv_dates_changed
         INPUT_DONE = lv_input_done
         TABCHANGED = lv_tabchanged
         EXIT_COMMAND = lv_exit_command
         SVECT = lv_svect
         DISP_CDOCS = lv_disp_cdocs
         CLASS_KEY = lv_class_key
         MAIN_OBJECT = lv_main_object
         RELAT_OBJECT = lv_relat_object
         DATE = lv_date
         FUZZY_BEGDA = lv_fuzzy_begda
         FUZZY_ENDDA = lv_fuzzy_endda
         FUZZY_ENDDA_OV = lv_fuzzy_endda_ov
         DETAIL_DATE = lv_detail_date
    TABLES
         LOC_VALUES = lt_loc_values
. " RH_OM_DETAILSCREEN_GETDATA




ABAP code using 7.40 inline data declarations to call FM RH_OM_DETAILSCREEN_GETDATA

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 DATUM FROM SY INTO @DATA(ld_date).
 
"SELECT single DATUM FROM SY INTO @DATA(ld_fuzzy_begda).
 
"SELECT single DATUM FROM SY INTO @DATA(ld_fuzzy_endda).
 
"SELECT single DATUM FROM SY INTO @DATA(ld_fuzzy_endda_ov).
 
"SELECT single DATUM FROM SY INTO @DATA(ld_detail_date).
 


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!