SAP ISP_VSP_ZUSTELLER_REKLAMATION Function Module for IS-M/SD: Carrier Complaint Shipping Doc. Type Cat. 1 - Truck Route-Rel.

Search SAP Function Modules

ISP_VSP_ZUSTELLER_REKLAMATION is a standard isp vsp zusteller reklamation 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: Carrier Complaint Shipping Doc. Type Cat. 1 - Truck Route-Rel. 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 vsp zusteller reklamation FM, simply by entering the name ISP_VSP_ZUSTELLER_REKLAMATION into the relevant SAP transaction such as SE37 or SE38.

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

Function ISP_VSP_ZUSTELLER_REKLAMATION 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_VSP_ZUSTELLER_REKLAMATION'"IS-M/SD: Carrier Complaint Shipping Doc. Type Cat. 1 - Truck Route-Rel.
  EXPORTING
   BEZIRK =  "Carrier Route
   BEZRUNDE =  "Delivery Round
   DRKEI =  "Printing works for drop-offs
*  NEW_SPOOL = ' ' "Generate new spool request
   PRINT_COMMON =  "General printing parameters (TJV55)
*  TESTLAUF = ' ' "Print screen for creating form
   VERSANDDATUM =  "Shipping date
   WA_TJV51 =  "Work area table JV51
   WA_TROUTE =  "Work area of daily route for drop-offs

 IMPORTING
   SPOOLID =  "Spool number for print output

TABLES
   ABLADUNGEN =  "Table of Drop-Offs (JRTABLG)
   MELD_TAB =  "Table of error situations for log

EXCEPTIONS
   FORM_NOT_CLOSED = 1    FORM_NOT_FOUND = 2    FORM_NOT_OPENED = 3    FORM_NOT_STARTED = 4    PRINT_OPTIONS = 5    SYSTMESSAGE = 6    TYPE_ERROR = 7 

.

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_SAPLJV05_001 IS-M/SD: Customer Exit for Carrier Change Notification (CH)

IMPORTING Parameters details for ISP_VSP_ZUSTELLER_REKLAMATION

BEZIRK - Carrier Route

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

BEZRUNDE - Delivery Round

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

DRKEI - Printing works for drop-offs

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

NEW_SPOOL - Generate new spool request

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

PRINT_COMMON - General printing parameters (TJV55)

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

TESTLAUF - Print screen for creating form

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

VERSANDDATUM - Shipping date

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

WA_TJV51 - Work area table JV51

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

WA_TROUTE - Work area of daily route for drop-offs

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

EXPORTING Parameters details for ISP_VSP_ZUSTELLER_REKLAMATION

SPOOLID - Spool number for print output

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

TABLES Parameters details for ISP_VSP_ZUSTELLER_REKLAMATION

ABLADUNGEN - Table of Drop-Offs (JRTABLG)

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

MELD_TAB - Table of error situations for log

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

EXCEPTIONS details

FORM_NOT_CLOSED - Form for OPEN_FORM still active

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

FORM_NOT_FOUND - Form does not exist

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

FORM_NOT_OPENED - Form was not opened (no OPEN_FORM)

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

FORM_NOT_STARTED - Error in WRITE_FORM

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

PRINT_OPTIONS - Invalid parameters for printing options

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

SYSTMESSAGE - Severe error, error message in SY fields

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

TYPE_ERROR - Window area in MAIN window does not exist

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

Copy and paste ABAP code example for ISP_VSP_ZUSTELLER_REKLAMATION 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_VSP_ZUSTELLER_REKLAMATION

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