SAP RH_OM_GET_OMDETAIL_COLUMNS_APP Function Module for
RH_OM_GET_OMDETAIL_COLUMNS_APP is a standard rh om get omdetail columns app 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 get omdetail columns app FM, simply by entering the name RH_OM_GET_OMDETAIL_COLUMNS_APP into the relevant SAP transaction such as SE37 or SE38.
Function Group: RHOMDETAIL_APPL
Program Name: SAPLRHOMDETAIL_APPL
Main Program: SAPLRHOMDETAIL_APPL
Appliation area: H
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function RH_OM_GET_OMDETAIL_COLUMNS_APP 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_GET_OMDETAIL_COLUMNS_APP'".
EXPORTING
COL_KEY = "
TREE_HANDLE = "
* BEGDA = "
* ENDDA = "
TABLES
TREE_OBJECTS = "
TREE_STRUCTURE = "
COLUMN_CONTENT = "
* LEGEND_ICON_TEXT = "
IMPORTING Parameters details for RH_OM_GET_OMDETAIL_COLUMNS_APP
COL_KEY -
Data type: TV_ITMNAMEOptional: No
Call by Reference: No ( called with pass by value option)
TREE_HANDLE -
Data type: CL_GUI_ALV_GRIDOptional: No
Call by Reference: No ( called with pass by value option)
BEGDA -
Data type: DATSOptional: Yes
Call by Reference: Yes
ENDDA -
Data type: DATSOptional: Yes
Call by Reference: Yes
TABLES Parameters details for RH_OM_GET_OMDETAIL_COLUMNS_APP
TREE_OBJECTS -
Data type: TREE_OBJECOptional: No
Call by Reference: No ( called with pass by value option)
TREE_STRUCTURE -
Data type: TREE_STRUCOptional: No
Call by Reference: No ( called with pass by value option)
COLUMN_CONTENT -
Data type: ORGNODECONOptional: No
Call by Reference: No ( called with pass by value option)
LEGEND_ICON_TEXT -
Data type: TREELEGENDOptional: Yes
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for RH_OM_GET_OMDETAIL_COLUMNS_APP 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_col_key | TYPE TV_ITMNAME, " | |||
| lt_tree_objects | TYPE STANDARD TABLE OF TREE_OBJEC, " | |||
| lv_tree_handle | TYPE CL_GUI_ALV_GRID, " | |||
| lt_tree_structure | TYPE STANDARD TABLE OF TREE_STRUC, " | |||
| lv_begda | TYPE DATS, " | |||
| lt_column_content | TYPE STANDARD TABLE OF ORGNODECON, " | |||
| lv_endda | TYPE DATS, " | |||
| lt_legend_icon_text | TYPE STANDARD TABLE OF TREELEGEND. " |
|   CALL FUNCTION 'RH_OM_GET_OMDETAIL_COLUMNS_APP' " |
| EXPORTING | ||
| COL_KEY | = lv_col_key | |
| TREE_HANDLE | = lv_tree_handle | |
| BEGDA | = lv_begda | |
| ENDDA | = lv_endda | |
| TABLES | ||
| TREE_OBJECTS | = lt_tree_objects | |
| TREE_STRUCTURE | = lt_tree_structure | |
| COLUMN_CONTENT | = lt_column_content | |
| LEGEND_ICON_TEXT | = lt_legend_icon_text | |
| . " RH_OM_GET_OMDETAIL_COLUMNS_APP | ||
ABAP code using 7.40 inline data declarations to call FM RH_OM_GET_OMDETAIL_COLUMNS_APP
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