ISM_SD_WERKISSUE_GET_SINGLE SAP Function module - Read Single Record from Buffer

ISM_SD_WERKISSUE_GET_SINGLE 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_GET_SINGLE 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_GET_SINGLE - ISM SD WERKISSUE GET SINGLE

CALL FUNCTION 'ISM_SD_WERKISSUE_GET_SINGLE' "Read Single Record from Buffer
  EXPORTING
*   im_werks =                  " jwerk         Plant
    im_vbeln =                  " vbeln         Sales and Distribution Document Number
    im_posnr =                  " posnr         Item Number of Sales Document
    im_issue =                  " ismmatnr_issue  Media Issue
*   im_flag_not_read_db =       " xflag
  IMPORTING
    ex_werkissue =              " jksdwerksissue  IS-M: Assignment of Plant to Contract and Issue
    ex_flag_no_data =           " xflag         No data available
    .  "  ISM_SD_WERKISSUE_GET_SINGLE

ABAP code example for Function Module ISM_SD_WERKISSUE_GET_SINGLE

The ABAP code below is a full code listing to execute function module ISM_SD_WERKISSUE_GET_SINGLE 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_ex_werkissue  
 
 TYPE JKSDWERKSISSUE
,
ld_ex_flag_no_data  
 
 TYPE XFLAG
.


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

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

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

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

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

CALL FUNCTION 'ISM_SD_WERKISSUE_GET_SINGLE'
  EXPORTING
*   im_werks =                   ld_im_werks
    im_vbeln =                   ld_im_vbeln
    im_posnr =                   ld_im_posnr
    im_issue =                   ld_im_issue
*   im_flag_not_read_db =        ld_im_flag_not_read_db
  IMPORTING
    ex_werkissue =               ld_ex_werkissue
    ex_flag_no_data =            ld_ex_flag_no_data
    .  "  ISM_SD_WERKISSUE_GET_SINGLE

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_ex_werkissue
 
 TYPE JKSDWERKSISSUE ,
ld_im_werks
 
 TYPE JWERK ,
ld_ex_flag_no_data
 
 TYPE XFLAG ,
ld_im_vbeln
 
 TYPE VBELN ,
ld_im_posnr
 
 TYPE POSNR ,
ld_im_issue
 
 TYPE ISMMATNR_ISSUE ,
ld_im_flag_not_read_db
 
 TYPE XFLAG .


ld_im_werks = 'Check type of data required'.
ld_im_vbeln = 'Check type of data required'.
ld_im_posnr = 'Check type of data required'.
ld_im_issue = 'Check type of data required'.
ld_im_flag_not_read_db = 'Check type of data required'.