ISP_GET_DISTRICTS_FROM_ROUTE SAP Function module - IS-M: Carrier Routes and Unloading Points Served by a Truck Route

ISP_GET_DISTRICTS_FROM_ROUTE is a standard SAP function module available within R/3 SAP systems depending on your version and release level. Below is the pattern details for this FM showing its interface including any import and export parameters, exceptions etc as well as any documentation contributions (Comments) specific to the object.

See here to view full function module documentation and code listing, simply by entering the name ISP_GET_DISTRICTS_FROM_ROUTE into the relevant SAP transaction such as SE37 or SE80.

Associated Function Group: JS12
Released Date: Not Released
Processing type: Normal fucntion module

Pattern for FM ISP_GET_DISTRICTS_FROM_ROUTE - ISP GET DISTRICTS FROM ROUTE

CALL FUNCTION 'ISP_GET_DISTRICTS_FROM_ROUTE' "IS-M: Carrier Routes and Unloading Points Served by a Truck Route
  EXPORTING
    in_route =                  " jrtroute-route  Truck Route
    in_date =                   " sy-datum      Shipping Date
    in_drerz =                  " rjr2003-drerz  Publication
    in_pva =                    " rjr2003-pva   Prod.Vers.
*   in_druerzart =              " rjr2003-druerzart
*   in_beablst =                " jvtlfng-beablst  IS-M: Unloading Point
  IMPORTING
    out_abladbar_tab =          " jstru_rjr2003tab
    out_ablade_tab =            " jstru_rjs0802tab
  EXCEPTIONS
    WRONG_INPUT_DATA = 1        "
    .  "  ISP_GET_DISTRICTS_FROM_ROUTE

ABAP code example for Function Module ISP_GET_DISTRICTS_FROM_ROUTE

The ABAP code below is a full code listing to execute function module ISP_GET_DISTRICTS_FROM_ROUTE including all data declarations. The code uses 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 original method of declaring data variables up front. 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).

DATA:
ld_out_abladbar_tab  
 
 TYPE JSTRU_RJR2003TAB
,
ld_out_ablade_tab  
 
 TYPE JSTRU_RJS0802TAB
.

 

SELECT single ROUTE 
  FROM JRTROUTE 
  INTO @DATA(ld_in_route).


DATA(ld_in_date) = '20210129'.


DATA(ld_in_drerz) = some text here


DATA(ld_in_pva) = some text here


DATA(ld_in_druerzart) = some text here
 

SELECT single BEABLST 
  FROM JVTLFNG 
  INTO @DATA(ld_in_beablst).

.

CALL FUNCTION 'ISP_GET_DISTRICTS_FROM_ROUTE'
  EXPORTING
    in_route =                   ld_in_route
    in_date =                    ld_in_date
    in_drerz =                   ld_in_drerz
    in_pva =                     ld_in_pva
*   in_druerzart =               ld_in_druerzart
*   in_beablst =                 ld_in_beablst
  IMPORTING
    out_abladbar_tab =           ld_out_abladbar_tab
    out_ablade_tab =             ld_out_ablade_tab
  EXCEPTIONS
    WRONG_INPUT_DATA =           1
    .  "  ISP_GET_DISTRICTS_FROM_ROUTE

IF SY-SUBRC EQ 0.
  "All OK
ELSEIF SY-SUBRC EQ 1. "Exception
  "Add code for exception here
ENDIF.

ABAP code to compare 7.40 inline data declaration with original syntax

The below ABAP code uses the older none in-line data declarations. This allows you to see the coding differences/benefits of the later inline syntax. It may also be useful if you are using an older version of SAP as some of the newer syntax above, such as the @DATA is not available until 4.70 EHP 8.

DATA:

ld_out_abladbar_tab
 
 TYPE JSTRU_RJR2003TAB ,
ld_in_route
 
 TYPE JRTROUTE-ROUTE ,
ld_out_ablade_tab
 
 TYPE JSTRU_RJS0802TAB ,
ld_in_date
 
 TYPE SY-DATUM ,
ld_in_drerz
 
 TYPE RJR2003-DRERZ ,
ld_in_pva
 
 TYPE RJR2003-PVA ,
ld_in_druerzart
 
 TYPE RJR2003-DRUERZART ,
ld_in_beablst
 
 TYPE JVTLFNG-BEABLST .



SELECT single ROUTE 
  FROM JRTROUTE 
  INTO ld_in_route.

ld_in_date = '20210129'.

ld_in_drerz = some text here

ld_in_pva = some text here

ld_in_druerzart = some text here

SELECT single BEABLST 
  FROM JVTLFNG 
  INTO ld_in_beablst.