SAP Function Modules

ISM_SE_SAMPLE_ADD_ISSUE SAP Function module







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

Associated Function Group: JKSEORDER13
Released Date: Not Released
Processing type: Normal fucntion module
Normal function module settings


Pattern for FM ISM_SE_SAMPLE_ADD_ISSUE - ISM SE SAMPLE ADD ISSUE





CALL FUNCTION 'ISM_SE_SAMPLE_ADD_ISSUE' "
  EXPORTING
    in_nip =                    " cl_ism_se_nip
    in_product =                " vbap-matnr
    in_next_issue_tab =         " rjkseordergennextissue_tab
    in_next_issue_failed =      " rjkseordergenissue_failed_tab
    in_add_issue_tab =          " rjkseordergenadd_tab
    in_vbeln =                  " rjksecontract-vbeln
    in_posnr =                  " rjksecontract-posnr
    in_testrun =                " char01
    in_no_success =             " char01
    in_message =                " cl_ism_sd_message
  IMPORTING
    out_issue =                 " rjkseordergenadd-issue
    out_quantity =              " rjkseordergenadd-quantity
    out_unit =                  " rjkseordergenadd-unit
  EXCEPTIONS
    NO_ISSUE_FOUND = 1          "
    .  "  ISM_SE_SAMPLE_ADD_ISSUE

ABAP code example for Function Module ISM_SE_SAMPLE_ADD_ISSUE





The ABAP code below is a full code listing to execute function module ISM_SE_SAMPLE_ADD_ISSUE 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_issue  TYPE RJKSEORDERGENADD-ISSUE ,
ld_out_quantity  TYPE RJKSEORDERGENADD-QUANTITY ,
ld_out_unit  TYPE RJKSEORDERGENADD-UNIT .

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

SELECT single MATNR
FROM VBAP
INTO @DATA(ld_in_product).

DATA(ld_in_next_issue_tab) = 'Check type of data required'.
DATA(ld_in_next_issue_failed) = 'Check type of data required'.
DATA(ld_in_add_issue_tab) = 'Check type of data required'.

DATA(ld_in_vbeln) = some text here

DATA(ld_in_posnr) = Check type of data required
DATA(ld_in_testrun) = 'Check type of data required'.
DATA(ld_in_no_success) = 'Check type of data required'.
DATA(ld_in_message) = 'Check type of data required'. . CALL FUNCTION 'ISM_SE_SAMPLE_ADD_ISSUE' EXPORTING in_nip = ld_in_nip in_product = ld_in_product in_next_issue_tab = ld_in_next_issue_tab in_next_issue_failed = ld_in_next_issue_failed in_add_issue_tab = ld_in_add_issue_tab in_vbeln = ld_in_vbeln in_posnr = ld_in_posnr in_testrun = ld_in_testrun in_no_success = ld_in_no_success in_message = ld_in_message IMPORTING out_issue = ld_out_issue out_quantity = ld_out_quantity out_unit = ld_out_unit EXCEPTIONS NO_ISSUE_FOUND = 1 . " ISM_SE_SAMPLE_ADD_ISSUE
IF SY-SUBRC EQ 0. "All OK ELSEIF SY-SUBRC EQ 1. "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_out_issue  TYPE RJKSEORDERGENADD-ISSUE ,
ld_in_nip  TYPE CL_ISM_SE_NIP ,
ld_out_quantity  TYPE RJKSEORDERGENADD-QUANTITY ,
ld_in_product  TYPE VBAP-MATNR ,
ld_out_unit  TYPE RJKSEORDERGENADD-UNIT ,
ld_in_next_issue_tab  TYPE RJKSEORDERGENNEXTISSUE_TAB ,
ld_in_next_issue_failed  TYPE RJKSEORDERGENISSUE_FAILED_TAB ,
ld_in_add_issue_tab  TYPE RJKSEORDERGENADD_TAB ,
ld_in_vbeln  TYPE RJKSECONTRACT-VBELN ,
ld_in_posnr  TYPE RJKSECONTRACT-POSNR ,
ld_in_testrun  TYPE CHAR01 ,
ld_in_no_success  TYPE CHAR01 ,
ld_in_message  TYPE CL_ISM_SD_MESSAGE .

ld_in_nip = 'Check type of data required'.

SELECT single MATNR
FROM VBAP
INTO ld_in_product.

ld_in_next_issue_tab = 'Check type of data required'.
ld_in_next_issue_failed = 'Check type of data required'.
ld_in_add_issue_tab = 'Check type of data required'.

ld_in_vbeln = some text here

ld_in_posnr = Check type of data required
ld_in_testrun = 'Check type of data required'.
ld_in_no_success = 'Check type of data required'.
ld_in_message = 'Check type of data required'.

Contribute (Add Comments)

Please help keep this info upto date and use the comments section below to add useful hints, tips and information specific to this SAP function. This will then be available for you and other users to easily find by simply searching on the object name ISM_SE_SAMPLE_ADD_ISSUE or its description.