SAP CHECK_EXISTING_PREPAYMENTS Function Module for Checks Whether Advance Payments Exist for a Contract









CHECK_EXISTING_PREPAYMENTS is a standard check existing prepayments SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Checks Whether Advance Payments Exist for a Contract 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 check existing prepayments FM, simply by entering the name CHECK_EXISTING_PREPAYMENTS into the relevant SAP transaction such as SE37 or SE38.

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



Function CHECK_EXISTING_PREPAYMENTS 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 'CHECK_EXISTING_PREPAYMENTS'"Checks Whether Advance Payments Exist for a Contract
EXPORTING
BUKRS = "Key Vdarl
SARCHIV = "Key Vdarl
RANL = "Key Vdarl
* POPUP = 'X' "'X' Hinweis-Popup, wenn Vorausz. vorliegen

IMPORTING
STOP_TRANSACTION = "'X'Transaktion beenden ' 'Transaktion fortsetzen

EXCEPTIONS
RANL_NOT_FOUND = 1
.



IMPORTING Parameters details for CHECK_EXISTING_PREPAYMENTS

BUKRS - Key Vdarl

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

SARCHIV - Key Vdarl

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

RANL - Key Vdarl

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

POPUP - 'X' Hinweis-Popup, wenn Vorausz. vorliegen

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

EXPORTING Parameters details for CHECK_EXISTING_PREPAYMENTS

STOP_TRANSACTION - 'X'Transaktion beenden ' 'Transaktion fortsetzen

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

EXCEPTIONS details

RANL_NOT_FOUND - VDARL-Satz konnte nicht gefunden werden

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

Copy and paste ABAP code example for CHECK_EXISTING_PREPAYMENTS 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_bukrs  TYPE VDARL-BUKRS, "   
lv_ranl_not_found  TYPE VDARL, "   
lv_stop_transaction  TYPE VDARL, "   
lv_sarchiv  TYPE VDARL-SARCHIV, "   
lv_ranl  TYPE VDARL-RANL, "   
lv_popup  TYPE VDARL. "   'X'

  CALL FUNCTION 'CHECK_EXISTING_PREPAYMENTS'  "Checks Whether Advance Payments Exist for a Contract
    EXPORTING
         BUKRS = lv_bukrs
         SARCHIV = lv_sarchiv
         RANL = lv_ranl
         POPUP = lv_popup
    IMPORTING
         STOP_TRANSACTION = lv_stop_transaction
    EXCEPTIONS
        RANL_NOT_FOUND = 1
. " CHECK_EXISTING_PREPAYMENTS




ABAP code using 7.40 inline data declarations to call FM CHECK_EXISTING_PREPAYMENTS

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 BUKRS FROM VDARL INTO @DATA(ld_bukrs).
 
 
 
"SELECT single SARCHIV FROM VDARL INTO @DATA(ld_sarchiv).
 
"SELECT single RANL FROM VDARL INTO @DATA(ld_ranl).
 
DATA(ld_popup) = 'X'.
 


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!