SAP ISP_VAS_CHECK_DSPTR Function Module for IS-M: Check Whether Issues Have Been Planned (Inc. Mix Type Definitions)

Search SAP Function Modules

ISP_VAS_CHECK_DSPTR is a standard isp vas check dsptr SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for IS-M: Check Whether Issues Have Been Planned (Inc. Mix Type Definitions) 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 vas check dsptr FM, simply by entering the name ISP_VAS_CHECK_DSPTR into the relevant SAP transaction such as SE37 or SE38.

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

Function ISP_VAS_CHECK_DSPTR 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_VAS_CHECK_DSPTR'"IS-M: Check Whether Issues Have Been Planned (Inc. Mix Type Definitions)
  EXPORTING
   DRERZ =  "
   GUEBIS =  "
   GUEVON =  "
*  INCL_JDTBZUS = ' ' "
   PVA =  "
*  INCL_LAST_DISPO_DATE = ' ' "

 IMPORTING
   XDISPO =  "
   LAST_DISPO_DATE =  "

EXCEPTIONS
   INTERVALL_ERROR = 1 

.

IMPORTING Parameters details for ISP_VAS_CHECK_DSPTR

DRERZ -

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

GUEBIS -

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

GUEVON -

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

INCL_JDTBZUS -

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

PVA -

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

INCL_LAST_DISPO_DATE -

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

EXPORTING Parameters details for ISP_VAS_CHECK_DSPTR

XDISPO -

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

LAST_DISPO_DATE -

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

EXCEPTIONS details

INTERVALL_ERROR -

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

Copy and paste ABAP code example for ISP_VAS_CHECK_DSPTR 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.

ABAP code using 7.40 inline data declarations to call FM ISP_VAS_CHECK_DSPTR

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