ISM_N_ISSUES_READ_FORWARD SAP Function module

ISM_N_ISSUES_READ_FORWARD is a standard SAP function module available within R/3 SAP systems depending on your version and release level. Below is the pattern details for this FM showing its interface including any import and export parameters, exceptions etc as well as any documentation contributions (Comments) specific to the object.

See here to view full function module documentation and code listing, simply by entering the name ISM_N_ISSUES_READ_FORWARD into the relevant SAP transaction such as SE37 or SE80.

Associated Function Group: JD12
Released Date: Not Released
Processing type: Normal fucntion module

Pattern for FM ISM_N_ISSUES_READ_FORWARD - ISM N ISSUES READ FORWARD

CALL FUNCTION 'ISM_N_ISSUES_READ_FORWARD' "
  EXPORTING
    publication =               " jdtdrer-drerz
*   edition =                   " jdtpva-pva
    mix_type =                  " jdtbeztyp-beztyp
*   order_periodicity =         " tjd09-bezper
    key_date =                  " d
*   xexcl_key_date =            " jpsd_xfeld
*   incl_comb_issues = ' '      " jdbz_relevance
    nr_of_issues =              " i
*   incl_weekday_check =        " xfeld
*   weekday_flags =             " rjyweekdays
  IMPORTING
    n_th_issue =                " jdvva
* TABLES
*   all_issues =                " jdvva
  EXCEPTIONS
    INTERNAL_ERROR = 1          "
    NOT_ENOUGH_ISSUES_FOUND = 2  "
    ILLEGAL_NR_OF_ISSUES = 3    "
    .  "  ISM_N_ISSUES_READ_FORWARD

ABAP code example for Function Module ISM_N_ISSUES_READ_FORWARD

The ABAP code below is a full code listing to execute function module ISM_N_ISSUES_READ_FORWARD including all data declarations. The code uses 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 original method of declaring data variables up front. 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).

DATA:
ld_n_th_issue  
 
 TYPE JDVVA
,
it_all_issues  
 
 TYPE STANDARD TABLE OF JDVVA,"TABLES PARAM
wa_all_issues
 
 LIKE LINE OF it_all_issues
.

 

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_key_date) = 'Check type of data required'.

DATA(ld_xexcl_key_date) = 'Check type of data required'.

DATA(ld_incl_comb_issues) = 'Check type of data required'.

DATA(ld_nr_of_issues) = 'Check type of data required'.

DATA(ld_incl_weekday_check) = 'Check type of data required'.

DATA(ld_weekday_flags) = 'Check type of data required'.
 

"populate fields of struture and append to itab
append wa_all_issues to it_all_issues.
.

CALL FUNCTION 'ISM_N_ISSUES_READ_FORWARD'
  EXPORTING
    publication =                ld_publication
*   edition =                    ld_edition
    mix_type =                   ld_mix_type
*   order_periodicity =          ld_order_periodicity
    key_date =                   ld_key_date
*   xexcl_key_date =             ld_xexcl_key_date
*   incl_comb_issues =           ld_incl_comb_issues
    nr_of_issues =               ld_nr_of_issues
*   incl_weekday_check =         ld_incl_weekday_check
*   weekday_flags =              ld_weekday_flags
  IMPORTING
    n_th_issue =                 ld_n_th_issue
* TABLES
*   all_issues =                 it_all_issues
  EXCEPTIONS
    INTERNAL_ERROR =             1
    NOT_ENOUGH_ISSUES_FOUND =    2
    ILLEGAL_NR_OF_ISSUES =       3
    .  "  ISM_N_ISSUES_READ_FORWARD

IF SY-SUBRC EQ 0.
  "All OK
ELSEIF SY-SUBRC EQ 1. "Exception
  "Add code for exception here
ELSEIF SY-SUBRC EQ 2. "Exception
  "Add code for exception here
ELSEIF SY-SUBRC EQ 3. "Exception
  "Add code for exception here
ENDIF.

ABAP code to compare 7.40 inline data declaration with original syntax

The below ABAP code uses the older none in-line data declarations. This allows you to see the coding differences/benefits of the later inline syntax. It may also be useful if you are using an older version of SAP as some of the newer syntax above, such as the @DATA is not available until 4.70 EHP 8.

DATA:

ld_n_th_issue
 
 TYPE JDVVA ,
ld_publication
 
 TYPE JDTDRER-DRERZ ,
it_all_issues
 
 TYPE STANDARD TABLE OF JDVVA ,
wa_all_issues
 
 LIKE LINE OF it_all_issues,
ld_edition
 
 TYPE JDTPVA-PVA ,
ld_mix_type
 
 TYPE JDTBEZTYP-BEZTYP ,
ld_order_periodicity
 
 TYPE TJD09-BEZPER ,
ld_key_date
 
 TYPE D ,
ld_xexcl_key_date
 
 TYPE JPSD_XFELD ,
ld_incl_comb_issues
 
 TYPE JDBZ_RELEVANCE ,
ld_nr_of_issues
 
 TYPE I ,
ld_incl_weekday_check
 
 TYPE XFELD ,
ld_weekday_flags
 
 TYPE RJYWEEKDAYS .



SELECT single DRERZ 
  FROM JDTDRER 
  INTO ld_publication.
 

"populate fields of struture and append to itab
append wa_all_issues to it_all_issues.

SELECT single PVA 
  FROM JDTPVA 
  INTO ld_edition.


SELECT single BEZTYP 
  FROM JDTBEZTYP 
  INTO ld_mix_type.


SELECT single BEZPER 
  FROM TJD09 
  INTO ld_order_periodicity.

ld_key_date = 'Check type of data required'.
ld_xexcl_key_date = 'Check type of data required'.
ld_incl_comb_issues = 'Check type of data required'.
ld_nr_of_issues = 'Check type of data required'.
ld_incl_weekday_check = 'Check type of data required'.
ld_weekday_flags = 'Check type of data required'.