SAP ISP_VERSION_CHECK Function Module for IS-M/SD: Check Whether Current Update 'Allowed'









ISP_VERSION_CHECK is a standard isp version 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 IS-M/SD: Check Whether Current Update '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 version check FM, simply by entering the name ISP_VERSION_CHECK into the relevant SAP transaction such as SE37 or SE38.

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



Function ISP_VERSION_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 'ISP_VERSION_CHECK'"IS-M/SD: Check Whether Current Update 'Allowed'
EXPORTING
* DATASET_NAME = ' ' "
* TESTLAUF = ' ' "
* CODEPAGE = 1103 "

IMPORTING
VERSION_EXP = "

EXCEPTIONS
NOT_OK = 1
.



IMPORTING Parameters details for ISP_VERSION_CHECK

DATASET_NAME -

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

TESTLAUF -

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

CODEPAGE -

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

EXPORTING Parameters details for ISP_VERSION_CHECK

VERSION_EXP -

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

EXCEPTIONS details

NOT_OK -

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

Copy and paste ABAP code example for ISP_VERSION_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_not_ok  TYPE STRING, "   
lv_version_exp  TYPE JYTVERSION, "   
lv_dataset_name  TYPE JYTVERSION, "   SPACE
lv_testlauf  TYPE JYTVERSION, "   SPACE
lv_codepage  TYPE CPCODEPAGE. "   1103

  CALL FUNCTION 'ISP_VERSION_CHECK'  "IS-M/SD: Check Whether Current Update 'Allowed'
    EXPORTING
         DATASET_NAME = lv_dataset_name
         TESTLAUF = lv_testlauf
         CODEPAGE = lv_codepage
    IMPORTING
         VERSION_EXP = lv_version_exp
    EXCEPTIONS
        NOT_OK = 1
. " ISP_VERSION_CHECK




ABAP code using 7.40 inline data declarations to call FM ISP_VERSION_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.

 
 
DATA(ld_dataset_name) = ' '.
 
DATA(ld_testlauf) = ' '.
 
DATA(ld_codepage) = 1103.
 


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!