ISM_SD_ORDER_QUANTITY_CHANGE SAP Function module - IS-M: Quantity Changes to a Generated Media Order

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

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

Pattern for FM ISM_SD_ORDER_QUANTITY_CHANGE - ISM SD ORDER QUANTITY CHANGE

CALL FUNCTION 'ISM_SD_ORDER_QUANTITY_CHANGE' "IS-M: Quantity Changes to a Generated Media Order
  EXPORTING
    in_contract =               " vbak-vbeln
    in_posnr =                  " vbap-posnr
    in_phasemdl =               " jksddemand-phasemdl  Phase Model in Phase-Based Delivery
    in_phasenbr =               " jksddemand-phasenbr
    in_issue =                  " mara-matnr
*   in_testrun =                " bapiflag-bapiflag  Test Run
*   in_enqueue = 'X'            " xfeld         Lock Contract
*   in_update_paket_divider =   " xfeld
*   in_no_checks =              " xfeld
* CHANGING
*   return =                    " cl_ism_sd_message  IS-M: Messages
*   protocol =                  " cl_ism_sd_docking_log  IS-M: Application Log
  EXCEPTIONS
    ERROR = 1                   "               Error
    .  "  ISM_SD_ORDER_QUANTITY_CHANGE

ABAP code example for Function Module ISM_SD_ORDER_QUANTITY_CHANGE

The ABAP code below is a full code listing to execute function module ISM_SD_ORDER_QUANTITY_CHANGE 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_return) = 'Check type of data required'.

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

SELECT single VBELN 
  FROM VBAK 
  INTO @DATA(ld_in_contract).

 

SELECT single POSNR 
  FROM VBAP 
  INTO @DATA(ld_in_posnr).

 

SELECT single PHASEMDL 
  FROM JKSDDEMAND 
  INTO @DATA(ld_in_phasemdl).

 

SELECT single PHASENBR 
  FROM JKSDDEMAND 
  INTO @DATA(ld_in_phasenbr).

 

SELECT single MATNR 
  FROM MARA 
  INTO @DATA(ld_in_issue).



DATA(ld_in_testrun) = some text here

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

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

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

CALL FUNCTION 'ISM_SD_ORDER_QUANTITY_CHANGE'
  EXPORTING
    in_contract =                ld_in_contract
    in_posnr =                   ld_in_posnr
    in_phasemdl =                ld_in_phasemdl
    in_phasenbr =                ld_in_phasenbr
    in_issue =                   ld_in_issue
*   in_testrun =                 ld_in_testrun
*   in_enqueue =                 ld_in_enqueue
*   in_update_paket_divider =    ld_in_update_paket_divider
*   in_no_checks =               ld_in_no_checks
* CHANGING
*   return =                     ld_return
*   protocol =                   ld_protocol
  EXCEPTIONS
    ERROR =                      1
    .  "  ISM_SD_ORDER_QUANTITY_CHANGE

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_return
 
 TYPE CL_ISM_SD_MESSAGE ,
ld_in_contract
 
 TYPE VBAK-VBELN ,
ld_protocol
 
 TYPE CL_ISM_SD_DOCKING_LOG ,
ld_in_posnr
 
 TYPE VBAP-POSNR ,
ld_in_phasemdl
 
 TYPE JKSDDEMAND-PHASEMDL ,
ld_in_phasenbr
 
 TYPE JKSDDEMAND-PHASENBR ,
ld_in_issue
 
 TYPE MARA-MATNR ,
ld_in_testrun
 
 TYPE BAPIFLAG-BAPIFLAG ,
ld_in_enqueue
 
 TYPE XFELD ,
ld_in_update_paket_divider
 
 TYPE XFELD ,
ld_in_no_checks
 
 TYPE XFELD .


ld_return = 'Check type of data required'.

SELECT single VBELN 
  FROM VBAK 
  INTO ld_in_contract.

ld_protocol = 'Check type of data required'.

SELECT single POSNR 
  FROM VBAP 
  INTO ld_in_posnr.


SELECT single PHASEMDL 
  FROM JKSDDEMAND 
  INTO ld_in_phasemdl.


SELECT single PHASENBR 
  FROM JKSDDEMAND 
  INTO ld_in_phasenbr.


SELECT single MATNR 
  FROM MARA 
  INTO ld_in_issue.


ld_in_testrun = some text here
ld_in_enqueue = 'Check type of data required'.
ld_in_update_paket_divider = 'Check type of data required'.
ld_in_no_checks = 'Check type of data required'.