SAP ISP_JVTFEHLER_MISSING_INFO_GET Function Module for IS-M/SD: Find Drop-Off for a Shipping Problem Message
ISP_JVTFEHLER_MISSING_INFO_GET is a standard isp jvtfehler missing info get 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: Find Drop-Off for a Shipping Problem Message 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 jvtfehler missing info get FM, simply by entering the name ISP_JVTFEHLER_MISSING_INFO_GET into the relevant SAP transaction such as SE37 or SE38.
Function Group: JV40
Program Name: SAPLJV40
Main Program: SAPLJV40
Appliation area: J
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function ISP_JVTFEHLER_MISSING_INFO_GET 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_JVTFEHLER_MISSING_INFO_GET'"IS-M/SD: Find Drop-Off for a Shipping Problem Message.
EXPORTING
TRTYP = "
VTFEHLER = "
* XDIALOG = ' ' "
IMPORTING
BEABLST = "
VKORG = "
VRSNDDATUM = "
FEHLPAKETE = "
PKTTEILER = "
BEZIRK = "
BEZRUNDE = "
DRERZ = "
DRUCKEREI = "
FEHLEXEMPL = "
LFARTLOG = "
PVA = "
ROUTE = "
EXCEPTIONS
NOT_CORRECT = 1 NOT_UNIQUE = 2
IMPORTING Parameters details for ISP_JVTFEHLER_MISSING_INFO_GET
TRTYP -
Data type: TJ180-TRTYPOptional: No
Call by Reference: No ( called with pass by value option)
VTFEHLER -
Data type: JVTFEHLEROptional: No
Call by Reference: No ( called with pass by value option)
XDIALOG -
Data type:Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for ISP_JVTFEHLER_MISSING_INFO_GET
BEABLST -
Data type: JVTFEHLER-BEABLSTOptional: No
Call by Reference: No ( called with pass by value option)
VKORG -
Data type: JVTFEHLER-VKORGOptional: No
Call by Reference: No ( called with pass by value option)
VRSNDDATUM -
Data type: JVTFEHLER-VRSNDDATUMOptional: No
Call by Reference: No ( called with pass by value option)
FEHLPAKETE -
Data type: JVTFEHLER-FEHLPAKETEOptional: No
Call by Reference: No ( called with pass by value option)
PKTTEILER -
Data type: JRTABLG-PKTTEILEROptional: No
Call by Reference: No ( called with pass by value option)
BEZIRK -
Data type: JVTFEHLER-BEZIRKOptional: No
Call by Reference: No ( called with pass by value option)
BEZRUNDE -
Data type: JVTFEHLER-BEZRUNDEOptional: No
Call by Reference: No ( called with pass by value option)
DRERZ -
Data type: JVTFEHLER-DRERZOptional: No
Call by Reference: No ( called with pass by value option)
DRUCKEREI -
Data type: JVTFEHLER-DRUCKEREIOptional: No
Call by Reference: No ( called with pass by value option)
FEHLEXEMPL -
Data type: JVTFEHLER-FEHLEXEMPLOptional: No
Call by Reference: No ( called with pass by value option)
LFARTLOG -
Data type: JVTFEHLER-LFARTLOGOptional: No
Call by Reference: No ( called with pass by value option)
PVA -
Data type: JVTFEHLER-PVAOptional: No
Call by Reference: No ( called with pass by value option)
ROUTE -
Data type: JVTFEHLER-ROUTEOptional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
NOT_CORRECT -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
NOT_UNIQUE -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for ISP_JVTFEHLER_MISSING_INFO_GET 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_trtyp | TYPE TJ180-TRTYP, " | |||
| lv_beablst | TYPE JVTFEHLER-BEABLST, " | |||
| lv_not_correct | TYPE JVTFEHLER, " | |||
| lv_vkorg | TYPE JVTFEHLER-VKORG, " | |||
| lv_vrsnddatum | TYPE JVTFEHLER-VRSNDDATUM, " | |||
| lv_fehlpakete | TYPE JVTFEHLER-FEHLPAKETE, " | |||
| lv_pktteiler | TYPE JRTABLG-PKTTEILER, " | |||
| lv_bezirk | TYPE JVTFEHLER-BEZIRK, " | |||
| lv_vtfehler | TYPE JVTFEHLER, " | |||
| lv_not_unique | TYPE JVTFEHLER, " | |||
| lv_xdialog | TYPE JVTFEHLER, " SPACE | |||
| lv_bezrunde | TYPE JVTFEHLER-BEZRUNDE, " | |||
| lv_drerz | TYPE JVTFEHLER-DRERZ, " | |||
| lv_druckerei | TYPE JVTFEHLER-DRUCKEREI, " | |||
| lv_fehlexempl | TYPE JVTFEHLER-FEHLEXEMPL, " | |||
| lv_lfartlog | TYPE JVTFEHLER-LFARTLOG, " | |||
| lv_pva | TYPE JVTFEHLER-PVA, " | |||
| lv_route | TYPE JVTFEHLER-ROUTE. " |
|   CALL FUNCTION 'ISP_JVTFEHLER_MISSING_INFO_GET' "IS-M/SD: Find Drop-Off for a Shipping Problem Message |
| EXPORTING | ||
| TRTYP | = lv_trtyp | |
| VTFEHLER | = lv_vtfehler | |
| XDIALOG | = lv_xdialog | |
| IMPORTING | ||
| BEABLST | = lv_beablst | |
| VKORG | = lv_vkorg | |
| VRSNDDATUM | = lv_vrsnddatum | |
| FEHLPAKETE | = lv_fehlpakete | |
| PKTTEILER | = lv_pktteiler | |
| BEZIRK | = lv_bezirk | |
| BEZRUNDE | = lv_bezrunde | |
| DRERZ | = lv_drerz | |
| DRUCKEREI | = lv_druckerei | |
| FEHLEXEMPL | = lv_fehlexempl | |
| LFARTLOG | = lv_lfartlog | |
| PVA | = lv_pva | |
| ROUTE | = lv_route | |
| EXCEPTIONS | ||
| NOT_CORRECT = 1 | ||
| NOT_UNIQUE = 2 | ||
| . " ISP_JVTFEHLER_MISSING_INFO_GET | ||
ABAP code using 7.40 inline data declarations to call FM ISP_JVTFEHLER_MISSING_INFO_GET
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 TRTYP FROM TJ180 INTO @DATA(ld_trtyp). | ||||
| "SELECT single BEABLST FROM JVTFEHLER INTO @DATA(ld_beablst). | ||||
| "SELECT single VKORG FROM JVTFEHLER INTO @DATA(ld_vkorg). | ||||
| "SELECT single VRSNDDATUM FROM JVTFEHLER INTO @DATA(ld_vrsnddatum). | ||||
| "SELECT single FEHLPAKETE FROM JVTFEHLER INTO @DATA(ld_fehlpakete). | ||||
| "SELECT single PKTTEILER FROM JRTABLG INTO @DATA(ld_pktteiler). | ||||
| "SELECT single BEZIRK FROM JVTFEHLER INTO @DATA(ld_bezirk). | ||||
| DATA(ld_xdialog) | = ' '. | |||
| "SELECT single BEZRUNDE FROM JVTFEHLER INTO @DATA(ld_bezrunde). | ||||
| "SELECT single DRERZ FROM JVTFEHLER INTO @DATA(ld_drerz). | ||||
| "SELECT single DRUCKEREI FROM JVTFEHLER INTO @DATA(ld_druckerei). | ||||
| "SELECT single FEHLEXEMPL FROM JVTFEHLER INTO @DATA(ld_fehlexempl). | ||||
| "SELECT single LFARTLOG FROM JVTFEHLER INTO @DATA(ld_lfartlog). | ||||
| "SELECT single PVA FROM JVTFEHLER INTO @DATA(ld_pva). | ||||
| "SELECT single ROUTE FROM JVTFEHLER INTO @DATA(ld_route). | ||||
Search for further information about these or an SAP related objects