SAP ISU_PAYMENT_LOCK_CHECK Function Module for Check whether payment lock is set on CA or on CA for payments









ISU_PAYMENT_LOCK_CHECK is a standard isu payment lock check 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 whether payment lock is set on CA or on CA for payments 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 isu payment lock check FM, simply by entering the name ISU_PAYMENT_LOCK_CHECK into the relevant SAP transaction such as SE37 or SE38.

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



Function ISU_PAYMENT_LOCK_CHECK 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 'ISU_PAYMENT_LOCK_CHECK'"Check whether payment lock is set on CA or on CA for payments
  EXPORTING
   X_FKKVKP =  "
   X_PROID =  "

 IMPORTING
   Y_LOCK_EXIST =  "

EXCEPTIONS
   IU_ERROR = 1    SYSTEM_ERROR = 2    NOT_QUALIFIED = 3
.



IMPORTING Parameters details for ISU_PAYMENT_LOCK_CHECK

X_FKKVKP -

Data type: FKKVKP
Optional: No
Call by Reference: Yes

X_PROID -

Data type: PROID_KK
Optional: No
Call by Reference: Yes

EXPORTING Parameters details for ISU_PAYMENT_LOCK_CHECK

Y_LOCK_EXIST -

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

EXCEPTIONS details

IU_ERROR -

Data type:
Optional: No
Call by Reference: Yes

SYSTEM_ERROR -

Data type:
Optional: No
Call by Reference: Yes

NOT_QUALIFIED -

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for ISU_PAYMENT_LOCK_CHECK 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_iu_error  TYPE STRING, "   
lv_x_fkkvkp  TYPE FKKVKP, "   
lv_y_lock_exist  TYPE XFELD, "   
lv_x_proid  TYPE PROID_KK, "   
lv_system_error  TYPE PROID_KK, "   
lv_not_qualified  TYPE PROID_KK. "   

  CALL FUNCTION 'ISU_PAYMENT_LOCK_CHECK'  "Check whether payment lock is set on CA or on CA for payments
    EXPORTING
         X_FKKVKP = lv_x_fkkvkp
         X_PROID = lv_x_proid
    IMPORTING
         Y_LOCK_EXIST = lv_y_lock_exist
    EXCEPTIONS
        IU_ERROR = 1
        SYSTEM_ERROR = 2
        NOT_QUALIFIED = 3
. " ISU_PAYMENT_LOCK_CHECK




ABAP code using 7.40 inline data declarations to call FM ISU_PAYMENT_LOCK_CHECK

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!