SAP UACC_CHECK_RFC_SAVED Function Module for Check if the UACC RFC Destination and User is maintained.









UACC_CHECK_RFC_SAVED is a standard uacc check rfc saved SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Check if the UACC RFC Destination and User is maintained. 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 uacc check rfc saved FM, simply by entering the name UACC_CHECK_RFC_SAVED into the relevant SAP transaction such as SE37 or SE38.

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



Function UACC_CHECK_RFC_SAVED 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 'UACC_CHECK_RFC_SAVED'"Check if the UACC RFC Destination and User is maintained.
EXPORTING
IV_CLIENT = "Client

IMPORTING
EV_RFCDEST = "Logical destination (specified in function call)
EV_RFCUSER = "User name in user master record

EXCEPTIONS
NO_UACC_RFC_CONF_SAVED = 1
.



IMPORTING Parameters details for UACC_CHECK_RFC_SAVED

IV_CLIENT - Client

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

EXPORTING Parameters details for UACC_CHECK_RFC_SAVED

EV_RFCDEST - Logical destination (specified in function call)

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

EV_RFCUSER - User name in user master record

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

EXCEPTIONS details

NO_UACC_RFC_CONF_SAVED -

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for UACC_CHECK_RFC_SAVED 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_iv_client  TYPE MANDT, "   
lv_ev_rfcdest  TYPE RFCDEST, "   
lv_no_uacc_rfc_conf_saved  TYPE RFCDEST, "   
lv_ev_rfcuser  TYPE XUBNAME. "   

  CALL FUNCTION 'UACC_CHECK_RFC_SAVED'  "Check if the UACC RFC Destination and User is maintained.
    EXPORTING
         IV_CLIENT = lv_iv_client
    IMPORTING
         EV_RFCDEST = lv_ev_rfcdest
         EV_RFCUSER = lv_ev_rfcuser
    EXCEPTIONS
        NO_UACC_RFC_CONF_SAVED = 1
. " UACC_CHECK_RFC_SAVED




ABAP code using 7.40 inline data declarations to call FM UACC_CHECK_RFC_SAVED

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!