ISM_SD_CLAIMS_CREATE_ORDER SAP Function module - Create Order

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

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

Pattern for FM ISM_SD_CLAIMS_CREATE_ORDER - ISM SD CLAIMS CREATE ORDER

CALL FUNCTION 'ISM_SD_CLAIMS_CREATE_ORDER' "Create Order
  EXPORTING
    iv_vbeln =                  " jvbelncontract  Contract Number
    iv_posnr =                  " jposnrcontract  Item Number in Contract
    iv_issue =                  " ismmatnr_issue  Media Issue
*   iv_check_compltype =        " char01        Character Field of Length 1
    iv_compltype =              " jcompltype1   Complaint Types for Delivery
    iv_claim_quantity =         " ism_claim_quan  Complaint quantity
    iv_del_unit =               " vrkme         Sales Unit
  IMPORTING
    ev_vbeln =                  " bapivbeln-vbeln  Sales Document
    et_error =                  " bapiret2_t    Return Table
    .  "  ISM_SD_CLAIMS_CREATE_ORDER

ABAP code example for Function Module ISM_SD_CLAIMS_CREATE_ORDER

The ABAP code below is a full code listing to execute function module ISM_SD_CLAIMS_CREATE_ORDER 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_ev_vbeln  
 
 TYPE BAPIVBELN-VBELN
,
ld_et_error  
 
 TYPE BAPIRET2_T
.


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

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

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

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

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

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

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

CALL FUNCTION 'ISM_SD_CLAIMS_CREATE_ORDER'
  EXPORTING
    iv_vbeln =                   ld_iv_vbeln
    iv_posnr =                   ld_iv_posnr
    iv_issue =                   ld_iv_issue
*   iv_check_compltype =         ld_iv_check_compltype
    iv_compltype =               ld_iv_compltype
    iv_claim_quantity =          ld_iv_claim_quantity
    iv_del_unit =                ld_iv_del_unit
  IMPORTING
    ev_vbeln =                   ld_ev_vbeln
    et_error =                   ld_et_error
    .  "  ISM_SD_CLAIMS_CREATE_ORDER

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_ev_vbeln
 
 TYPE BAPIVBELN-VBELN ,
ld_iv_vbeln
 
 TYPE JVBELNCONTRACT ,
ld_et_error
 
 TYPE BAPIRET2_T ,
ld_iv_posnr
 
 TYPE JPOSNRCONTRACT ,
ld_iv_issue
 
 TYPE ISMMATNR_ISSUE ,
ld_iv_check_compltype
 
 TYPE CHAR01 ,
ld_iv_compltype
 
 TYPE JCOMPLTYPE1 ,
ld_iv_claim_quantity
 
 TYPE ISM_CLAIM_QUAN ,
ld_iv_del_unit
 
 TYPE VRKME .


ld_iv_vbeln = 'Check type of data required'.
ld_iv_posnr = 'Check type of data required'.
ld_iv_issue = 'Check type of data required'.
ld_iv_check_compltype = 'Check type of data required'.
ld_iv_compltype = 'Check type of data required'.
ld_iv_claim_quantity = 'Check type of data required'.
ld_iv_del_unit = 'Check type of data required'.