SAP RIS_OBJECT_TYPE_UI_DATA_GET Function Module for RIS Object Type Integration: Get Data for UI
RIS_OBJECT_TYPE_UI_DATA_GET is a standard ris object type ui data get SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for RIS Object Type Integration: Get Data for UI processing and below is the pattern details for this FM, 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 ris object type ui data get FM, simply by entering the name RIS_OBJECT_TYPE_UI_DATA_GET into the relevant SAP transaction such as SE37 or SE38.
Function Group: RIS_OBJECT_TYPE_UI
Program Name: SAPLRIS_OBJECT_TYPE_UI
Main Program: SAPLRIS_OBJECT_TYPE_UI
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function RIS_OBJECT_TYPE_UI_DATA_GET 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 'RIS_OBJECT_TYPE_UI_DATA_GET'"RIS Object Type Integration: Get Data for UI.
IMPORTING
EO_OBJECT_DATA = "Interface for Central Object Data Model
EO_TOOL_DATA = "Interface to Administration Data of a Workbench Tool
EXPORTING Parameters details for RIS_OBJECT_TYPE_UI_DATA_GET
EO_OBJECT_DATA - Interface for Central Object Data Model
Data type: IF_WB_OBJECT_DATA_MODELOptional: No
Call by Reference: Yes
EO_TOOL_DATA - Interface to Administration Data of a Workbench Tool
Data type: IF_WB_TOOL_DATA_MODELOptional: No
Call by Reference: Yes
Copy and paste ABAP code example for RIS_OBJECT_TYPE_UI_DATA_GET 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_eo_object_data | TYPE IF_WB_OBJECT_DATA_MODEL, " | |||
| lv_eo_tool_data | TYPE IF_WB_TOOL_DATA_MODEL. " |
|   CALL FUNCTION 'RIS_OBJECT_TYPE_UI_DATA_GET' "RIS Object Type Integration: Get Data for UI |
| IMPORTING | ||
| EO_OBJECT_DATA | = lv_eo_object_data | |
| EO_TOOL_DATA | = lv_eo_tool_data | |
| . " RIS_OBJECT_TYPE_UI_DATA_GET | ||
ABAP code using 7.40 inline data declarations to call FM RIS_OBJECT_TYPE_UI_DATA_GET
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