SAP ISP_JVTFEHLER_INPUT_CHECK Function Module for IS-M/SD: Check on Entries
ISP_JVTFEHLER_INPUT_CHECK is a standard isp jvtfehler input check 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: Check on Entries 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 input check FM, simply by entering the name ISP_JVTFEHLER_INPUT_CHECK 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_INPUT_CHECK 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_INPUT_CHECK'"IS-M/SD: Check on Entries.
EXPORTING
VTFEHLER = "
IMPORTING
XNBKZ = "
EXCEPTIONS
NOT_CORRECT = 1
IMPORTING Parameters details for ISP_JVTFEHLER_INPUT_CHECK
VTFEHLER -
Data type: JVTFEHLEROptional: No
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for ISP_JVTFEHLER_INPUT_CHECK
XNBKZ -
Data type: JVTFEHLER-XNBKZOptional: 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)
Copy and paste ABAP code example for ISP_JVTFEHLER_INPUT_CHECK 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_xnbkz | TYPE JVTFEHLER-XNBKZ, " | |||
| lv_vtfehler | TYPE JVTFEHLER, " | |||
| lv_not_correct | TYPE JVTFEHLER. " |
|   CALL FUNCTION 'ISP_JVTFEHLER_INPUT_CHECK' "IS-M/SD: Check on Entries |
| EXPORTING | ||
| VTFEHLER | = lv_vtfehler | |
| IMPORTING | ||
| XNBKZ | = lv_xnbkz | |
| EXCEPTIONS | ||
| NOT_CORRECT = 1 | ||
| . " ISP_JVTFEHLER_INPUT_CHECK | ||
ABAP code using 7.40 inline data declarations to call FM ISP_JVTFEHLER_INPUT_CHECK
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 XNBKZ FROM JVTFEHLER INTO @DATA(ld_xnbkz). | ||||
Search for further information about these or an SAP related objects