SAP ISP_BUNDLE_NUMBERING Function Module for

Search SAP Function Modules

ISP_BUNDLE_NUMBERING is a standard isp bundle numbering 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 bundle numbering FM, simply by entering the name ISP_BUNDLE_NUMBERING into the relevant SAP transaction such as SE37 or SE38.

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

Function ISP_BUNDLE_NUMBERING 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_BUNDLE_NUMBERING'"
  EXPORTING
   DRUCKEREI =  "
   VERSANDDAT =  "
*  LFDNR_START = '0000000001' "

 IMPORTING
   LFDNR_END =  "

TABLES
   RANGE_DRERZ =  "
   RANGE_PVA =  "
   LFART_NETZ_TAB =  "
*  ABLG_TAB =  "
*  GEBINDE_TAB =  "
*  BUND_TAB =  "

EXCEPTIONS
   WRONG_INPUT = 1    NO_BUNDLE_FOUND = 2    WRONG_NUMBERING = 3 

.

IMPORTING Parameters details for ISP_BUNDLE_NUMBERING

DRUCKEREI -

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

VERSANDDAT -

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

LFDNR_START -

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

EXPORTING Parameters details for ISP_BUNDLE_NUMBERING

LFDNR_END -

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

TABLES Parameters details for ISP_BUNDLE_NUMBERING

RANGE_DRERZ -

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

RANGE_PVA -

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

LFART_NETZ_TAB -

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

ABLG_TAB -

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

GEBINDE_TAB -

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

BUND_TAB -

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

EXCEPTIONS details

WRONG_INPUT -

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

NO_BUNDLE_FOUND -

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

WRONG_NUMBERING -

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

Copy and paste ABAP code example for ISP_BUNDLE_NUMBERING 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_BUNDLE_NUMBERING

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