ISM_SD_WERKISSUE_SELECT SAP Function module - Select Issue Plant Table (in Buffer)

ISM_SD_WERKISSUE_SELECT 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_SD_WERKISSUE_SELECT into the relevant SAP transaction such as SE37 or SE80.

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

Pattern for FM ISM_SD_WERKISSUE_SELECT - ISM SD WERKISSUE SELECT

CALL FUNCTION 'ISM_SD_WERKISSUE_SELECT' "Select Issue Plant Table (in Buffer)
* EXPORTING
*   im_demand_tab =             " rjksddemandtab  IS-M: Table Type for JKSDDEMAND with Key
*   im_werk_tab =               " rjksd_werk_range_tab  IS-M: Range Table for WERKS_D
*   im_vbeln_tab =              " rjksd_vbeln_range_tab  IS-M: Range Table for RJKSD_VBELN_RANGE
*   im_posnr_tab =              " rjksd_posnr_range_tab  IS-M: Range Table for POSNR
*   im_issue =                  " rjksd_issue_range_tab  IS-M: Range Table for ISMMATNR_ISSUE
  IMPORTING
    out_werksissue_tab =        " jksdwerksissue_type_tab  IS-M: Table Type for Plant for Contract and Issue
    .  "  ISM_SD_WERKISSUE_SELECT

ABAP code example for Function Module ISM_SD_WERKISSUE_SELECT

The ABAP code below is a full code listing to execute function module ISM_SD_WERKISSUE_SELECT 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_out_werksissue_tab  
 
 TYPE JKSDWERKSISSUE_TYPE_TAB
.


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

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

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

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

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

CALL FUNCTION 'ISM_SD_WERKISSUE_SELECT'
* EXPORTING
*   im_demand_tab =              ld_im_demand_tab
*   im_werk_tab =                ld_im_werk_tab
*   im_vbeln_tab =               ld_im_vbeln_tab
*   im_posnr_tab =               ld_im_posnr_tab
*   im_issue =                   ld_im_issue
  IMPORTING
    out_werksissue_tab =         ld_out_werksissue_tab
    .  "  ISM_SD_WERKISSUE_SELECT

IF SY-SUBRC EQ 0.
  "All OK
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_out_werksissue_tab
 
 TYPE JKSDWERKSISSUE_TYPE_TAB ,
ld_im_demand_tab
 
 TYPE RJKSDDEMANDTAB ,
ld_im_werk_tab
 
 TYPE RJKSD_WERK_RANGE_TAB ,
ld_im_vbeln_tab
 
 TYPE RJKSD_VBELN_RANGE_TAB ,
ld_im_posnr_tab
 
 TYPE RJKSD_POSNR_RANGE_TAB ,
ld_im_issue
 
 TYPE RJKSD_ISSUE_RANGE_TAB .


ld_im_demand_tab = 'Check type of data required'.
ld_im_werk_tab = 'Check type of data required'.
ld_im_vbeln_tab = 'Check type of data required'.
ld_im_posnr_tab = 'Check type of data required'.
ld_im_issue = 'Check type of data required'.