SAP ISP_DSPTR_CHECK_JDTDRER Function Module for
ISP_DSPTR_CHECK_JDTDRER is a standard isp dsptr check jdtdrer SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used to perform a specific ABAP function and below is the pattern details, 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 dsptr check jdtdrer FM, simply by entering the name ISP_DSPTR_CHECK_JDTDRER into the relevant SAP transaction such as SE37 or SE38.
Function Group: JVC5
Program Name: SAPLJVC5
Main Program: SAPLJVC5
Appliation area: J
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function ISP_DSPTR_CHECK_JDTDRER 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_DSPTR_CHECK_JDTDRER'".
EXPORTING
DRERZ = "
IMPORTING
OK = "
TABLES
MESSAGES = "
IMPORTING Parameters details for ISP_DSPTR_CHECK_JDTDRER
DRERZ -
Data type: JDTDRER-DRERZOptional: No
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for ISP_DSPTR_CHECK_JDTDRER
OK -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for ISP_DSPTR_CHECK_JDTDRER
MESSAGES -
Data type: RJMSGOptional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for ISP_DSPTR_CHECK_JDTDRER 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_ok | TYPE STRING, " | |||
| lv_drerz | TYPE JDTDRER-DRERZ, " | |||
| lt_messages | TYPE STANDARD TABLE OF RJMSG. " |
|   CALL FUNCTION 'ISP_DSPTR_CHECK_JDTDRER' " |
| EXPORTING | ||
| DRERZ | = lv_drerz | |
| IMPORTING | ||
| OK | = lv_ok | |
| TABLES | ||
| MESSAGES | = lt_messages | |
| . " ISP_DSPTR_CHECK_JDTDRER | ||
ABAP code using 7.40 inline data declarations to call FM ISP_DSPTR_CHECK_JDTDRER
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 DRERZ FROM JDTDRER INTO @DATA(ld_drerz). | ||||
Search for further information about these or an SAP related objects