ISM_SD_ISSUEMIXPLAN_DISPLAY SAP Function module - IS-M: Process Split

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

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

Pattern for FM ISM_SD_ISSUEMIXPLAN_DISPLAY - ISM SD ISSUEMIXPLAN DISPLAY

CALL FUNCTION 'ISM_SD_ISSUEMIXPLAN_DISPLAY' "IS-M: Process Split
* EXPORTING
*   display_only =              " c
*   create =                    " c
*   insert_tab =                " rjvsdblgzustab  Inserts
*   in_mix =                    " jvsdsplit     IS-M: Issue Split
*   in_donotchangeinserts = SPACE  " xfeld
  IMPORTING
    out_split =                 " rjsdadmix     IS-M: Split Identification
  EXCEPTIONS
    ISSUE_NOT_FOUND = 1         "               Media issue not found
    TEMPLATE_NOT_FOUND = 2      "
    INVALID_CALL = 3            "
    BACK = 4                    "
    .  "  ISM_SD_ISSUEMIXPLAN_DISPLAY

ABAP code example for Function Module ISM_SD_ISSUEMIXPLAN_DISPLAY

The ABAP code below is a full code listing to execute function module ISM_SD_ISSUEMIXPLAN_DISPLAY 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_split  
 
 TYPE RJSDADMIX
.


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

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

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

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

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

CALL FUNCTION 'ISM_SD_ISSUEMIXPLAN_DISPLAY'
* EXPORTING
*   display_only =               ld_display_only
*   create =                     ld_create
*   insert_tab =                 ld_insert_tab
*   in_mix =                     ld_in_mix
*   in_donotchangeinserts =      ld_in_donotchangeinserts
  IMPORTING
    out_split =                  ld_out_split
  EXCEPTIONS
    ISSUE_NOT_FOUND =            1
    TEMPLATE_NOT_FOUND =         2
    INVALID_CALL =               3
    BACK =                       4
    .  "  ISM_SD_ISSUEMIXPLAN_DISPLAY

IF SY-SUBRC EQ 0.
  "All OK
ELSEIF SY-SUBRC EQ 1. "Exception
  "Add code for exception here
ELSEIF SY-SUBRC EQ 2. "Exception
  "Add code for exception here
ELSEIF SY-SUBRC EQ 3. "Exception
  "Add code for exception here
ELSEIF SY-SUBRC EQ 4. "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_split
 
 TYPE RJSDADMIX ,
ld_display_only
 
 TYPE C ,
ld_create
 
 TYPE C ,
ld_insert_tab
 
 TYPE RJVSDBLGZUSTAB ,
ld_in_mix
 
 TYPE JVSDSPLIT ,
ld_in_donotchangeinserts
 
 TYPE XFELD .


ld_display_only = 'Check type of data required'.
ld_create = 'Check type of data required'.
ld_insert_tab = 'Check type of data required'.
ld_in_mix = 'Check type of data required'.
ld_in_donotchangeinserts = 'Check type of data required'.