SAP ISP_TOURS_FOR_UNLOADING_POINT Function Module for IS-M/SD: Specify Truck Routes That Serve Specific Unloading Point
ISP_TOURS_FOR_UNLOADING_POINT is a standard isp tours for unloading point 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: Specify Truck Routes That Serve Specific Unloading Point 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 tours for unloading point FM, simply by entering the name ISP_TOURS_FOR_UNLOADING_POINT into the relevant SAP transaction such as SE37 or SE38.
Function Group: JDP1
Program Name: SAPLJDP1
Main Program: SAPLJDP1
Appliation area: J
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function ISP_TOURS_FOR_UNLOADING_POINT 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_TOURS_FOR_UNLOADING_POINT'"IS-M/SD: Specify Truck Routes That Serve Specific Unloading Point.
EXPORTING
BEABLST = "
DATUM = "
* DRERZ = "
* PVA = "
WERK = "
* BEZRUNDE = "
IMPORTING
XNO_BEABLFOLGE = "
XNO_ROUTEPVA = "
XNO_TROUTE = "
XNO_RUNDE = "
TABLES
TROUTEN_TAB = "
* ALLE_ROUTEN_TAB = "
EXCEPTIONS
MISSING_BEABLST = 1
IMPORTING Parameters details for ISP_TOURS_FOR_UNLOADING_POINT
BEABLST -
Data type: JRTABLG-BEABLSTOptional: No
Call by Reference: No ( called with pass by value option)
DATUM -
Data type: SY-DATUMOptional: No
Call by Reference: No ( called with pass by value option)
DRERZ -
Data type: JRTABLG-DRERZTATOptional: Yes
Call by Reference: No ( called with pass by value option)
PVA -
Data type: JRTABLG-PVATATOptional: Yes
Call by Reference: No ( called with pass by value option)
WERK -
Data type: JRTABLG-DRUCKEREIOptional: No
Call by Reference: No ( called with pass by value option)
BEZRUNDE -
Data type: JRTABLG-BEZRUNDTATOptional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for ISP_TOURS_FOR_UNLOADING_POINT
XNO_BEABLFOLGE -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
XNO_ROUTEPVA -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
XNO_TROUTE -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
XNO_RUNDE -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for ISP_TOURS_FOR_UNLOADING_POINT
TROUTEN_TAB -
Data type: JRTTROUTEOptional: No
Call by Reference: No ( called with pass by value option)
ALLE_ROUTEN_TAB -
Data type: JRTTROUTEOptional: Yes
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
MISSING_BEABLST -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for ISP_TOURS_FOR_UNLOADING_POINT 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_beablst | TYPE JRTABLG-BEABLST, " | |||
| lt_trouten_tab | TYPE STANDARD TABLE OF JRTTROUTE, " | |||
| lv_xno_beablfolge | TYPE JRTTROUTE, " | |||
| lv_missing_beablst | TYPE JRTTROUTE, " | |||
| lv_datum | TYPE SY-DATUM, " | |||
| lv_xno_routepva | TYPE SY, " | |||
| lt_alle_routen_tab | TYPE STANDARD TABLE OF JRTTROUTE, " | |||
| lv_drerz | TYPE JRTABLG-DRERZTAT, " | |||
| lv_xno_troute | TYPE JRTABLG, " | |||
| lv_pva | TYPE JRTABLG-PVATAT, " | |||
| lv_xno_runde | TYPE JRTABLG, " | |||
| lv_werk | TYPE JRTABLG-DRUCKEREI, " | |||
| lv_bezrunde | TYPE JRTABLG-BEZRUNDTAT. " |
|   CALL FUNCTION 'ISP_TOURS_FOR_UNLOADING_POINT' "IS-M/SD: Specify Truck Routes That Serve Specific Unloading Point |
| EXPORTING | ||
| BEABLST | = lv_beablst | |
| DATUM | = lv_datum | |
| DRERZ | = lv_drerz | |
| PVA | = lv_pva | |
| WERK | = lv_werk | |
| BEZRUNDE | = lv_bezrunde | |
| IMPORTING | ||
| XNO_BEABLFOLGE | = lv_xno_beablfolge | |
| XNO_ROUTEPVA | = lv_xno_routepva | |
| XNO_TROUTE | = lv_xno_troute | |
| XNO_RUNDE | = lv_xno_runde | |
| TABLES | ||
| TROUTEN_TAB | = lt_trouten_tab | |
| ALLE_ROUTEN_TAB | = lt_alle_routen_tab | |
| EXCEPTIONS | ||
| MISSING_BEABLST = 1 | ||
| . " ISP_TOURS_FOR_UNLOADING_POINT | ||
ABAP code using 7.40 inline data declarations to call FM ISP_TOURS_FOR_UNLOADING_POINT
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.| "SELECT single BEABLST FROM JRTABLG INTO @DATA(ld_beablst). | ||||
| "SELECT single DATUM FROM SY INTO @DATA(ld_datum). | ||||
| "SELECT single DRERZTAT FROM JRTABLG INTO @DATA(ld_drerz). | ||||
| "SELECT single PVATAT FROM JRTABLG INTO @DATA(ld_pva). | ||||
| "SELECT single DRUCKEREI FROM JRTABLG INTO @DATA(ld_werk). | ||||
| "SELECT single BEZRUNDTAT FROM JRTABLG INTO @DATA(ld_bezrunde). | ||||
Search for further information about these or an SAP related objects