SAP RV_CONDITION_GET_CUA_REPO Function Module for NOTRANSL: Kondition: Übertragen des CUA-Status









RV_CONDITION_GET_CUA_REPO is a standard rv condition get cua repo 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: Kondition: Übertragen des CUA-Status 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 rv condition get cua repo FM, simply by entering the name RV_CONDITION_GET_CUA_REPO into the relevant SAP transaction such as SE37 or SE38.

Function Group: V130
Program Name: SAPLV130
Main Program: SAPLV130
Appliation area: V
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:



Function RV_CONDITION_GET_CUA_REPO 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 'RV_CONDITION_GET_CUA_REPO'"NOTRANSL: Kondition: Übertragen des CUA-Status
EXPORTING
PFKEY_I = "GUI Status
* TITLE_I = "
* PAR1_I = "
* PAR2_I = "
* PAR3_I = "
* PAR4_I = "

TABLES
* EXCL_I = "
.



IMPORTING Parameters details for RV_CONDITION_GET_CUA_REPO

PFKEY_I - GUI Status

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

TITLE_I -

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

PAR1_I -

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

PAR2_I -

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

PAR3_I -

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

PAR4_I -

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

TABLES Parameters details for RV_CONDITION_GET_CUA_REPO

EXCL_I -

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

Copy and paste ABAP code example for RV_CONDITION_GET_CUA_REPO 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_excl_i  TYPE STANDARD TABLE OF STRING, "   
lv_pfkey_i  TYPE STRING, "   
lv_title_i  TYPE STRING, "   
lv_par1_i  TYPE STRING, "   
lv_par2_i  TYPE STRING, "   
lv_par3_i  TYPE STRING, "   
lv_par4_i  TYPE STRING. "   

  CALL FUNCTION 'RV_CONDITION_GET_CUA_REPO'  "NOTRANSL: Kondition: Übertragen des CUA-Status
    EXPORTING
         PFKEY_I = lv_pfkey_i
         TITLE_I = lv_title_i
         PAR1_I = lv_par1_i
         PAR2_I = lv_par2_i
         PAR3_I = lv_par3_i
         PAR4_I = lv_par4_i
    TABLES
         EXCL_I = lt_excl_i
. " RV_CONDITION_GET_CUA_REPO




ABAP code using 7.40 inline data declarations to call FM RV_CONDITION_GET_CUA_REPO

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



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!