SAP ISM_N_ISSUES_READ_FORWARD Function Module for









ISM_N_ISSUES_READ_FORWARD is a standard ism n issues read forward 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 ism n issues read forward FM, simply by entering the name ISM_N_ISSUES_READ_FORWARD into the relevant SAP transaction such as SE37 or SE38.

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



Function ISM_N_ISSUES_READ_FORWARD 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 'ISM_N_ISSUES_READ_FORWARD'"
EXPORTING
PUBLICATION = "
* WEEKDAY_FLAGS = "
* EDITION = "
MIX_TYPE = "
* ORDER_PERIODICITY = "
KEY_DATE = "
* XEXCL_KEY_DATE = "
* INCL_COMB_ISSUES = ' ' "
NR_OF_ISSUES = "
* INCL_WEEKDAY_CHECK = "

IMPORTING
N_TH_ISSUE = "

TABLES
* ALL_ISSUES = "

EXCEPTIONS
INTERNAL_ERROR = 1 NOT_ENOUGH_ISSUES_FOUND = 2 ILLEGAL_NR_OF_ISSUES = 3
.



IMPORTING Parameters details for ISM_N_ISSUES_READ_FORWARD

PUBLICATION -

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

WEEKDAY_FLAGS -

Data type: RJYWEEKDAYS
Optional: Yes
Call by Reference: Yes

EDITION -

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

MIX_TYPE -

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

ORDER_PERIODICITY -

Data type: TJD09-BEZPER
Optional: Yes
Call by Reference: No ( called with pass by value option)

KEY_DATE -

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

XEXCL_KEY_DATE -

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

INCL_COMB_ISSUES -

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

NR_OF_ISSUES -

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

INCL_WEEKDAY_CHECK -

Data type: XFELD
Optional: Yes
Call by Reference: Yes

EXPORTING Parameters details for ISM_N_ISSUES_READ_FORWARD

N_TH_ISSUE -

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

TABLES Parameters details for ISM_N_ISSUES_READ_FORWARD

ALL_ISSUES -

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

EXCEPTIONS details

INTERNAL_ERROR -

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

NOT_ENOUGH_ISSUES_FOUND -

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

ILLEGAL_NR_OF_ISSUES -

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

Copy and paste ABAP code example for ISM_N_ISSUES_READ_FORWARD 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:
lt_all_issues  TYPE STANDARD TABLE OF JDVVA, "   
lv_n_th_issue  TYPE JDVVA, "   
lv_publication  TYPE JDTDRER-DRERZ, "   
lv_internal_error  TYPE JDTDRER, "   
lv_weekday_flags  TYPE RJYWEEKDAYS, "   
lv_edition  TYPE JDTPVA-PVA, "   
lv_not_enough_issues_found  TYPE JDTPVA, "   
lv_mix_type  TYPE JDTBEZTYP-BEZTYP, "   
lv_illegal_nr_of_issues  TYPE JDTBEZTYP, "   
lv_order_periodicity  TYPE TJD09-BEZPER, "   
lv_key_date  TYPE D, "   
lv_xexcl_key_date  TYPE JPSD_XFELD, "   
lv_incl_comb_issues  TYPE JDBZ_RELEVANCE, "   ' '
lv_nr_of_issues  TYPE I, "   
lv_incl_weekday_check  TYPE XFELD. "   

  CALL FUNCTION 'ISM_N_ISSUES_READ_FORWARD'  "
    EXPORTING
         PUBLICATION = lv_publication
         WEEKDAY_FLAGS = lv_weekday_flags
         EDITION = lv_edition
         MIX_TYPE = lv_mix_type
         ORDER_PERIODICITY = lv_order_periodicity
         KEY_DATE = lv_key_date
         XEXCL_KEY_DATE = lv_xexcl_key_date
         INCL_COMB_ISSUES = lv_incl_comb_issues
         NR_OF_ISSUES = lv_nr_of_issues
         INCL_WEEKDAY_CHECK = lv_incl_weekday_check
    IMPORTING
         N_TH_ISSUE = lv_n_th_issue
    TABLES
         ALL_ISSUES = lt_all_issues
    EXCEPTIONS
        INTERNAL_ERROR = 1
        NOT_ENOUGH_ISSUES_FOUND = 2
        ILLEGAL_NR_OF_ISSUES = 3
. " ISM_N_ISSUES_READ_FORWARD




ABAP code using 7.40 inline data declarations to call FM ISM_N_ISSUES_READ_FORWARD

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_publication).
 
 
 
"SELECT single PVA FROM JDTPVA INTO @DATA(ld_edition).
 
 
"SELECT single BEZTYP FROM JDTBEZTYP INTO @DATA(ld_mix_type).
 
 
"SELECT single BEZPER FROM TJD09 INTO @DATA(ld_order_periodicity).
 
 
 
DATA(ld_incl_comb_issues) = ' '.
 
 
 


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!