SAP CUOV_GET_FUNCTION_ARGUMENT Function Module for NOTRANSL: Lesen Eingangswert aus generischer Funktionsschnittstelle
CUOV_GET_FUNCTION_ARGUMENT is a standard cuov get function argument SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for NOTRANSL: Lesen Eingangswert aus generischer Funktionsschnittstelle 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 cuov get function argument FM, simply by entering the name CUOV_GET_FUNCTION_ARGUMENT into the relevant SAP transaction such as SE37 or SE38.
Function Group: CUOV
Program Name: SAPLCUOV
Main Program: SAPLCUOV
Appliation area: M
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function CUOV_GET_FUNCTION_ARGUMENT 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 'CUOV_GET_FUNCTION_ARGUMENT'"NOTRANSL: Lesen Eingangswert aus generischer Funktionsschnittstelle.
EXPORTING
ARGUMENT = "
IMPORTING
VTYPE = "Value format
SYM_VAL = "Alphanumeric value
NUM_VAL = "Numeric value
IO_FLAG = "Input/output parameter indicator
TABLES
QUERY = "Table of input and output parameters
EXCEPTIONS
ARG_NOT_FOUND = 1
IMPORTING Parameters details for CUOV_GET_FUNCTION_ARGUMENT
ARGUMENT -
Data type: CUOV_01-VARNAMOptional: No
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for CUOV_GET_FUNCTION_ARGUMENT
VTYPE - Value format
Data type: CUOV_01-ATFOROptional: No
Call by Reference: No ( called with pass by value option)
SYM_VAL - Alphanumeric value
Data type: CUOV_01-ATWRTOptional: No
Call by Reference: No ( called with pass by value option)
NUM_VAL - Numeric value
Data type: CUOV_01-ATFLVOptional: No
Call by Reference: No ( called with pass by value option)
IO_FLAG - Input/output parameter indicator
Data type: CUOV_01-ATCIOOptional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for CUOV_GET_FUNCTION_ARGUMENT
QUERY - Table of input and output parameters
Data type: CUOV_01Optional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
ARG_NOT_FOUND - Parameter not found
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for CUOV_GET_FUNCTION_ARGUMENT 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: | ||||
| lt_query | TYPE STANDARD TABLE OF CUOV_01, " | |||
| lv_vtype | TYPE CUOV_01-ATFOR, " | |||
| lv_argument | TYPE CUOV_01-VARNAM, " | |||
| lv_arg_not_found | TYPE CUOV_01, " | |||
| lv_sym_val | TYPE CUOV_01-ATWRT, " | |||
| lv_num_val | TYPE CUOV_01-ATFLV, " | |||
| lv_io_flag | TYPE CUOV_01-ATCIO. " |
|   CALL FUNCTION 'CUOV_GET_FUNCTION_ARGUMENT' "NOTRANSL: Lesen Eingangswert aus generischer Funktionsschnittstelle |
| EXPORTING | ||
| ARGUMENT | = lv_argument | |
| IMPORTING | ||
| VTYPE | = lv_vtype | |
| SYM_VAL | = lv_sym_val | |
| NUM_VAL | = lv_num_val | |
| IO_FLAG | = lv_io_flag | |
| TABLES | ||
| QUERY | = lt_query | |
| EXCEPTIONS | ||
| ARG_NOT_FOUND = 1 | ||
| . " CUOV_GET_FUNCTION_ARGUMENT | ||
ABAP code using 7.40 inline data declarations to call FM CUOV_GET_FUNCTION_ARGUMENT
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 ATFOR FROM CUOV_01 INTO @DATA(ld_vtype). | ||||
| "SELECT single VARNAM FROM CUOV_01 INTO @DATA(ld_argument). | ||||
| "SELECT single ATWRT FROM CUOV_01 INTO @DATA(ld_sym_val). | ||||
| "SELECT single ATFLV FROM CUOV_01 INTO @DATA(ld_num_val). | ||||
| "SELECT single ATCIO FROM CUOV_01 INTO @DATA(ld_io_flag). | ||||
Search for further information about these or an SAP related objects