SAP RPY_EXISTENCE_CHECK_DIAL Function Module for









RPY_EXISTENCE_CHECK_DIAL is a standard rpy existence check dial 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 rpy existence check dial FM, simply by entering the name RPY_EXISTENCE_CHECK_DIAL into the relevant SAP transaction such as SE37 or SE38.

Function Group: SEUEXIST
Program Name: SAPLSEUEXIST
Main Program: SAPLSEUEXIST
Appliation area: S
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:



Function RPY_EXISTENCE_CHECK_DIAL 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 'RPY_EXISTENCE_CHECK_DIAL'"
EXPORTING
* NAME = "Object Name
* LIMU_KEY = "

EXCEPTIONS
NOT_EXIST = 1
.



IMPORTING Parameters details for RPY_EXISTENCE_CHECK_DIAL

NAME - Object Name

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

LIMU_KEY -

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

EXCEPTIONS details

NOT_EXIST - Object Does Not Exist

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

Copy and paste ABAP code example for RPY_EXISTENCE_CHECK_DIAL 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_name  TYPE TDCT-DNAM, "   
lv_not_exist  TYPE TDCT, "   
lv_limu_key  TYPE E071-OBJ_NAME. "   

  CALL FUNCTION 'RPY_EXISTENCE_CHECK_DIAL'  "
    EXPORTING
         NAME = lv_name
         LIMU_KEY = lv_limu_key
    EXCEPTIONS
        NOT_EXIST = 1
. " RPY_EXISTENCE_CHECK_DIAL




ABAP code using 7.40 inline data declarations to call FM RPY_EXISTENCE_CHECK_DIAL

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 DNAM FROM TDCT INTO @DATA(ld_name).
 
 
"SELECT single OBJ_NAME FROM E071 INTO @DATA(ld_limu_key).
 


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!