ISM_SD_CONTRACT_READ_FLOW SAP Function module

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

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

Pattern for FM ISM_SD_CONTRACT_READ_FLOW - ISM SD CONTRACT READ FLOW

CALL FUNCTION 'ISM_SD_CONTRACT_READ_FLOW' "
  EXPORTING
    in_vbeln =                  " vbeln
    in_posnr =                  " posnr
*   in_issue =                  " ismmatnr_issue
*   in_phasemdl =               " jvphasemdl
*   in_phasenbr =               " jvphasenbr
*   in_flag_read_order =        " xfeld
*   in_flag_refresh =           " xfeld
  IMPORTING
    ex_flow_tab =               " rjksddemandflowtab
    .  "  ISM_SD_CONTRACT_READ_FLOW

ABAP code example for Function Module ISM_SD_CONTRACT_READ_FLOW

The ABAP code below is a full code listing to execute function module ISM_SD_CONTRACT_READ_FLOW 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_flow_tab  
 
 TYPE RJKSDDEMANDFLOWTAB
.


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

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

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

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

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

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

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

CALL FUNCTION 'ISM_SD_CONTRACT_READ_FLOW'
  EXPORTING
    in_vbeln =                   ld_in_vbeln
    in_posnr =                   ld_in_posnr
*   in_issue =                   ld_in_issue
*   in_phasemdl =                ld_in_phasemdl
*   in_phasenbr =                ld_in_phasenbr
*   in_flag_read_order =         ld_in_flag_read_order
*   in_flag_refresh =            ld_in_flag_refresh
  IMPORTING
    ex_flow_tab =                ld_ex_flow_tab
    .  "  ISM_SD_CONTRACT_READ_FLOW

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_flow_tab
 
 TYPE RJKSDDEMANDFLOWTAB ,
ld_in_vbeln
 
 TYPE VBELN ,
ld_in_posnr
 
 TYPE POSNR ,
ld_in_issue
 
 TYPE ISMMATNR_ISSUE ,
ld_in_phasemdl
 
 TYPE JVPHASEMDL ,
ld_in_phasenbr
 
 TYPE JVPHASENBR ,
ld_in_flag_read_order
 
 TYPE XFELD ,
ld_in_flag_refresh
 
 TYPE XFELD .


ld_in_vbeln = 'Check type of data required'.
ld_in_posnr = 'Check type of data required'.
ld_in_issue = 'Check type of data required'.
ld_in_phasemdl = 'Check type of data required'.
ld_in_phasenbr = 'Check type of data required'.
ld_in_flag_read_order = 'Check type of data required'.
ld_in_flag_refresh = 'Check type of data required'.