SAP ISP_DSPTR_TOUCHED_BY_INTERVALL Function Module for IS-M: Planning Trigger for Publs/Edits That Touch Specified Time Interval









ISP_DSPTR_TOUCHED_BY_INTERVALL is a standard isp dsptr touched by intervall 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: Planning Trigger for Publs/Edits That Touch Specified Time Interval 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 dsptr touched by intervall FM, simply by entering the name ISP_DSPTR_TOUCHED_BY_INTERVALL into the relevant SAP transaction such as SE37 or SE38.

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



Function ISP_DSPTR_TOUCHED_BY_INTERVALL 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_TOUCHED_BY_INTERVALL'"IS-M: Planning Trigger for Publs/Edits That Touch Specified Time Interval
  EXPORTING
*  DRERZ = '        ' "Publication
*  DRKEI = '    ' "Plant
*  LFART = '  ' "Delivery Type
*  PVA = '        ' "Edition
*  ZEITRAUMBIS = '00000000' "
*  ZEITRAUMVON = '00000000' "

 IMPORTING
   DSPTR_FOUND =  "

TABLES
   DSPTR_TAB =  "
   MESSAGES =  "
.



IMPORTING Parameters details for ISP_DSPTR_TOUCHED_BY_INTERVALL

DRERZ - Publication

Data type: JVTDSPTR-DRERZ
Default: ' '
Optional: Yes
Call by Reference: No ( called with pass by value option)

DRKEI - Plant

Data type: JVTDSPTR-DRKEI
Default: ' '
Optional: Yes
Call by Reference: No ( called with pass by value option)

LFART - Delivery Type

Data type: JVTDSPTR-LFART
Default: ' '
Optional: Yes
Call by Reference: No ( called with pass by value option)

PVA - Edition

Data type: JVTDSPTR-PVA
Default: ' '
Optional: Yes
Call by Reference: No ( called with pass by value option)

ZEITRAUMBIS -

Data type: JDTGENTR-GENZRBIS
Default: '00000000'
Optional: Yes
Call by Reference: No ( called with pass by value option)

ZEITRAUMVON -

Data type: JDTGENTR-GENZRVON
Default: '00000000'
Optional: Yes
Call by Reference: No ( called with pass by value option)

EXPORTING Parameters details for ISP_DSPTR_TOUCHED_BY_INTERVALL

DSPTR_FOUND -

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

TABLES Parameters details for ISP_DSPTR_TOUCHED_BY_INTERVALL

DSPTR_TAB -

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

MESSAGES -

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

Copy and paste ABAP code example for ISP_DSPTR_TOUCHED_BY_INTERVALL 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_drerz  TYPE JVTDSPTR-DRERZ, "   ' '
lt_dsptr_tab  TYPE STANDARD TABLE OF JVTDSPTR, "   
lv_dsptr_found  TYPE JVTDSPTR, "   
lv_drkei  TYPE JVTDSPTR-DRKEI, "   ' '
lt_messages  TYPE STANDARD TABLE OF RJMSG, "   
lv_lfart  TYPE JVTDSPTR-LFART, "   ' '
lv_pva  TYPE JVTDSPTR-PVA, "   ' '
lv_zeitraumbis  TYPE JDTGENTR-GENZRBIS, "   '00000000'
lv_zeitraumvon  TYPE JDTGENTR-GENZRVON. "   '00000000'

  CALL FUNCTION 'ISP_DSPTR_TOUCHED_BY_INTERVALL'  "IS-M: Planning Trigger for Publs/Edits That Touch Specified Time Interval
    EXPORTING
         DRERZ = lv_drerz
         DRKEI = lv_drkei
         LFART = lv_lfart
         PVA = lv_pva
         ZEITRAUMBIS = lv_zeitraumbis
         ZEITRAUMVON = lv_zeitraumvon
    IMPORTING
         DSPTR_FOUND = lv_dsptr_found
    TABLES
         DSPTR_TAB = lt_dsptr_tab
         MESSAGES = lt_messages
. " ISP_DSPTR_TOUCHED_BY_INTERVALL




ABAP code using 7.40 inline data declarations to call FM ISP_DSPTR_TOUCHED_BY_INTERVALL

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 JVTDSPTR INTO @DATA(ld_drerz).
DATA(ld_drerz) = ' '.
 
 
 
"SELECT single DRKEI FROM JVTDSPTR INTO @DATA(ld_drkei).
DATA(ld_drkei) = ' '.
 
 
"SELECT single LFART FROM JVTDSPTR INTO @DATA(ld_lfart).
DATA(ld_lfart) = ' '.
 
"SELECT single PVA FROM JVTDSPTR INTO @DATA(ld_pva).
DATA(ld_pva) = ' '.
 
"SELECT single GENZRBIS FROM JDTGENTR INTO @DATA(ld_zeitraumbis).
DATA(ld_zeitraumbis) = '00000000'.
 
"SELECT single GENZRVON FROM JDTGENTR INTO @DATA(ld_zeitraumvon).
DATA(ld_zeitraumvon) = '00000000'.
 


Search for further information about these or an SAP related objects



Comments on this SAP object

What made you want to lookup this SAP object? Please tell us what you were looking for and anything you would like to be included on this page!