SAP CUA_PARAMETER_READ Function Module for
CUA_PARAMETER_READ is a standard cua parameter read 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 cua parameter read FM, simply by entering the name CUA_PARAMETER_READ into the relevant SAP transaction such as SE37 or SE38.
Function Group: V00F
Program Name: SAPLV00F
Main Program:
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function CUA_PARAMETER_READ 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 'CUA_PARAMETER_READ'".
EXPORTING
BILD = "Four-digit name of the current scr
BILDGRUPPE = "Two-digit identifier of the curren
PROGRAMM = "Calling program
* TYP = ' ' "Transaction type of the calling pr
IMPORTING
CUA_PARA1 = "Transfer parameter 1 for the CUA h
CUA_PARA2 = "Transfer parameter 2 for the CUA h
CUA_PARA3 = "Transfer parameter 3 for the CUA h
CUA_PARA4 = "Transfer parameter 4 for the CUA h
CUA_STATUS = "CUA status for specifying the acti
CUA_TITEL = "Name of the CUA header line
IMPORTING Parameters details for CUA_PARAMETER_READ
BILD - Four-digit name of the current scr
Data type: T185-PANELOptional: No
Call by Reference: No ( called with pass by value option)
BILDGRUPPE - Two-digit identifier of the curren
Data type: T185-BLDGROptional: No
Call by Reference: No ( called with pass by value option)
PROGRAMM - Calling program
Data type: T185F-AGIDVOptional: No
Call by Reference: No ( called with pass by value option)
TYP - Transaction type of the calling pr
Data type: T185F-TRTYPDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for CUA_PARAMETER_READ
CUA_PARA1 - Transfer parameter 1 for the CUA h
Data type: T185V-PARA1Optional: No
Call by Reference: No ( called with pass by value option)
CUA_PARA2 - Transfer parameter 2 for the CUA h
Data type: T185V-PARA2Optional: No
Call by Reference: No ( called with pass by value option)
CUA_PARA3 - Transfer parameter 3 for the CUA h
Data type: T185V-PARA3Optional: No
Call by Reference: No ( called with pass by value option)
CUA_PARA4 - Transfer parameter 4 for the CUA h
Data type: T185V-PARA4Optional: No
Call by Reference: No ( called with pass by value option)
CUA_STATUS - CUA status for specifying the acti
Data type: T185V-STATUSOptional: No
Call by Reference: No ( called with pass by value option)
CUA_TITEL - Name of the CUA header line
Data type: T185V-CTITELOptional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for CUA_PARAMETER_READ 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_bild | TYPE T185-PANEL, " | |||
| lv_cua_para1 | TYPE T185V-PARA1, " | |||
| lv_cua_para2 | TYPE T185V-PARA2, " | |||
| lv_bildgruppe | TYPE T185-BLDGR, " | |||
| lv_programm | TYPE T185F-AGIDV, " | |||
| lv_cua_para3 | TYPE T185V-PARA3, " | |||
| lv_typ | TYPE T185F-TRTYP, " SPACE | |||
| lv_cua_para4 | TYPE T185V-PARA4, " | |||
| lv_cua_status | TYPE T185V-STATUS, " | |||
| lv_cua_titel | TYPE T185V-CTITEL. " |
|   CALL FUNCTION 'CUA_PARAMETER_READ' " |
| EXPORTING | ||
| BILD | = lv_bild | |
| BILDGRUPPE | = lv_bildgruppe | |
| PROGRAMM | = lv_programm | |
| TYP | = lv_typ | |
| IMPORTING | ||
| CUA_PARA1 | = lv_cua_para1 | |
| CUA_PARA2 | = lv_cua_para2 | |
| CUA_PARA3 | = lv_cua_para3 | |
| CUA_PARA4 | = lv_cua_para4 | |
| CUA_STATUS | = lv_cua_status | |
| CUA_TITEL | = lv_cua_titel | |
| . " CUA_PARAMETER_READ | ||
ABAP code using 7.40 inline data declarations to call FM CUA_PARAMETER_READ
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 PANEL FROM T185 INTO @DATA(ld_bild). | ||||
| "SELECT single PARA1 FROM T185V INTO @DATA(ld_cua_para1). | ||||
| "SELECT single PARA2 FROM T185V INTO @DATA(ld_cua_para2). | ||||
| "SELECT single BLDGR FROM T185 INTO @DATA(ld_bildgruppe). | ||||
| "SELECT single AGIDV FROM T185F INTO @DATA(ld_programm). | ||||
| "SELECT single PARA3 FROM T185V INTO @DATA(ld_cua_para3). | ||||
| "SELECT single TRTYP FROM T185F INTO @DATA(ld_typ). | ||||
| DATA(ld_typ) | = ' '. | |||
| "SELECT single PARA4 FROM T185V INTO @DATA(ld_cua_para4). | ||||
| "SELECT single STATUS FROM T185V INTO @DATA(ld_cua_status). | ||||
| "SELECT single CTITEL FROM T185V INTO @DATA(ld_cua_titel). | ||||
Search for further information about these or an SAP related objects