SAP ISP_VA_MAX_INSETS_CHECK Function Module for

Search SAP Function Modules

ISP_VA_MAX_INSETS_CHECK is a standard isp va max insets check SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used to perform a specific ABAP function and below is the pattern details, 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 va max insets check FM, simply by entering the name ISP_VA_MAX_INSETS_CHECK into the relevant SAP transaction such as SE37 or SE38.

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

Function ISP_VA_MAX_INSETS_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_VA_MAX_INSETS_CHECK'"
  EXPORTING
*  GEOEIN =  "
*  KDGRP =  "
   LIEFERART =  "
   VA =  "
*  BEILAGENBEZIRK =  "

TABLES
   BEZIRK_TAB =  "
   BZUS_TAB =  "

EXCEPTIONS
   MISSING_BZTYP = 1    TOO_MANY_INSETS = 2    VA_NOT_FOUND = 3 

.

Customer Function user exits

Below is a list of CUSTOMER FUNCTION exit user exits that are available within this program and maybe relevant for this FM.
EXIT_SAPLJKPROM_001 IS-M/SD: Introduction Data Transfer to Customer Subscreen 0200
EXIT_SAPLJKPROM_002 IS-M/SD: Introductions, Data Transfer from Cust.Subscreen 0200
EXIT_SAPLJKPROM_003 IS-M/SD: Introductions - Modify Gifts
EXIT_SAPLJKPROM_004 IS-M/SD: Introduction - Modify Commission

IMPORTING Parameters details for ISP_VA_MAX_INSETS_CHECK

GEOEIN -

Data type: JKAPPR-GEOEIN
Optional: Yes
Call by Reference: No ( called with pass by value option)

KDGRP -

Data type: JKAPPR-KDGRP
Optional: Yes
Call by Reference: No ( called with pass by value option)

LIEFERART -

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

VA -

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

BEILAGENBEZIRK -

Data type: JKAPPR-BEZIRK_BLG
Optional: Yes
Call by Reference: No ( called with pass by value option)

TABLES Parameters details for ISP_VA_MAX_INSETS_CHECK

BEZIRK_TAB -

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

BZUS_TAB -

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

EXCEPTIONS details

MISSING_BZTYP -

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

TOO_MANY_INSETS -

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

VA_NOT_FOUND -

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

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

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