SAP ISP_PROSPECT_CHECK_DEL_OK Function Module for Check Whether Deletion of Ad Pre-Print Allowed









ISP_PROSPECT_CHECK_DEL_OK is a standard isp prospect check del ok 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 Deletion of Ad Pre-Print Allowed 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 isp prospect check del ok FM, simply by entering the name ISP_PROSPECT_CHECK_DEL_OK into the relevant SAP transaction such as SE37 or SE38.

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



Function ISP_PROSPECT_CHECK_DEL_OK 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 'ISP_PROSPECT_CHECK_DEL_OK'"Check Whether Deletion of Ad Pre-Print Allowed
  EXPORTING
   PROSPECT_ID =  "

 IMPORTING
   DEL_OK =  "
   REACTION_MSG_ID =  "
   REACTION_MSG_NR =  "
   REACTION_MSG_TYPE =  "
   REACTION_MSG_VAR1 =  "
   REACTION_MSG_VAR2 =  "
   REACTION_MSG_VAR3 =  "
   REACTION_MSG_VAR4 =  "

EXCEPTIONS
   NO_VALID_STATUS_FOUND = 1    PROSPECT_NOT_FOUND = 2
.



IMPORTING Parameters details for ISP_PROSPECT_CHECK_DEL_OK

PROSPECT_ID -

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

EXPORTING Parameters details for ISP_PROSPECT_CHECK_DEL_OK

DEL_OK -

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

REACTION_MSG_ID -

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

REACTION_MSG_NR -

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

REACTION_MSG_TYPE -

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

REACTION_MSG_VAR1 -

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

REACTION_MSG_VAR2 -

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

REACTION_MSG_VAR3 -

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

REACTION_MSG_VAR4 -

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

EXCEPTIONS details

NO_VALID_STATUS_FOUND -

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

PROSPECT_NOT_FOUND -

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

Copy and paste ABAP code example for ISP_PROSPECT_CHECK_DEL_OK 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_del_ok  TYPE SY-SUBRC, "   
lv_prospect_id  TYPE JDTVAUSGB-VAUSGB, "   
lv_no_valid_status_found  TYPE JDTVAUSGB, "   
lv_reaction_msg_id  TYPE T100-ARBGB, "   
lv_prospect_not_found  TYPE T100, "   
lv_reaction_msg_nr  TYPE T100-MSGNR, "   
lv_reaction_msg_type  TYPE SY-MSGTY, "   
lv_reaction_msg_var1  TYPE SY-MSGV1, "   
lv_reaction_msg_var2  TYPE SY-MSGV2, "   
lv_reaction_msg_var3  TYPE SY-MSGV3, "   
lv_reaction_msg_var4  TYPE SY-MSGV4. "   

  CALL FUNCTION 'ISP_PROSPECT_CHECK_DEL_OK'  "Check Whether Deletion of Ad Pre-Print Allowed
    EXPORTING
         PROSPECT_ID = lv_prospect_id
    IMPORTING
         DEL_OK = lv_del_ok
         REACTION_MSG_ID = lv_reaction_msg_id
         REACTION_MSG_NR = lv_reaction_msg_nr
         REACTION_MSG_TYPE = lv_reaction_msg_type
         REACTION_MSG_VAR1 = lv_reaction_msg_var1
         REACTION_MSG_VAR2 = lv_reaction_msg_var2
         REACTION_MSG_VAR3 = lv_reaction_msg_var3
         REACTION_MSG_VAR4 = lv_reaction_msg_var4
    EXCEPTIONS
        NO_VALID_STATUS_FOUND = 1
        PROSPECT_NOT_FOUND = 2
. " ISP_PROSPECT_CHECK_DEL_OK




ABAP code using 7.40 inline data declarations to call FM ISP_PROSPECT_CHECK_DEL_OK

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 SUBRC FROM SY INTO @DATA(ld_del_ok).
 
"SELECT single VAUSGB FROM JDTVAUSGB INTO @DATA(ld_prospect_id).
 
 
"SELECT single ARBGB FROM T100 INTO @DATA(ld_reaction_msg_id).
 
 
"SELECT single MSGNR FROM T100 INTO @DATA(ld_reaction_msg_nr).
 
"SELECT single MSGTY FROM SY INTO @DATA(ld_reaction_msg_type).
 
"SELECT single MSGV1 FROM SY INTO @DATA(ld_reaction_msg_var1).
 
"SELECT single MSGV2 FROM SY INTO @DATA(ld_reaction_msg_var2).
 
"SELECT single MSGV3 FROM SY INTO @DATA(ld_reaction_msg_var3).
 
"SELECT single MSGV4 FROM SY INTO @DATA(ld_reaction_msg_var4).
 


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!