FMFGCCR_MESSAGE_ISSUE SAP Function module - Issue messages with exception (for batch processing)

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

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

Pattern for FM FMFGCCR_MESSAGE_ISSUE - FMFGCCR MESSAGE ISSUE

CALL FUNCTION 'FMFGCCR_MESSAGE_ISSUE' "Issue messages with exception (for batch processing)
  EXPORTING
    i_msgid =                   " symsgid       Message Class
    i_msgty =                   " symsgty       Message Type
    i_msgno =                   " symsgno       Message Number
*   i_msgv1 =                   " symsgv        Message Variable
*   i_msgv2 =                   " symsgv        Message Variable
*   i_msgv3 =                   " symsgv        Message Variable
*   i_msgv4 =                   " symsgv        Message Variable
  EXCEPTIONS
    ERROR_MESSAGE = 1           "
    .  "  FMFGCCR_MESSAGE_ISSUE

ABAP code example for Function Module FMFGCCR_MESSAGE_ISSUE

The ABAP code below is a full code listing to execute function module FMFGCCR_MESSAGE_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_i_msgid) = 'some text here'.

DATA(ld_i_msgty) = 'some text here'.

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

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

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

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

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

CALL FUNCTION 'FMFGCCR_MESSAGE_ISSUE'
  EXPORTING
    i_msgid =                    ld_i_msgid
    i_msgty =                    ld_i_msgty
    i_msgno =                    ld_i_msgno
*   i_msgv1 =                    ld_i_msgv1
*   i_msgv2 =                    ld_i_msgv2
*   i_msgv3 =                    ld_i_msgv3
*   i_msgv4 =                    ld_i_msgv4
  EXCEPTIONS
    ERROR_MESSAGE =              1
    .  "  FMFGCCR_MESSAGE_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_i_msgid
 
 TYPE SYMSGID ,
ld_i_msgty
 
 TYPE SYMSGTY ,
ld_i_msgno
 
 TYPE SYMSGNO ,
ld_i_msgv1
 
 TYPE SYMSGV ,
ld_i_msgv2
 
 TYPE SYMSGV ,
ld_i_msgv3
 
 TYPE SYMSGV ,
ld_i_msgv4
 
 TYPE SYMSGV .


ld_i_msgid = 'some text here'.
ld_i_msgty = 'some text here'.
ld_i_msgno = 'Check type of data required'.
ld_i_msgv1 = 'Check type of data required'.
ld_i_msgv2 = 'Check type of data required'.
ld_i_msgv3 = 'Check type of data required'.
ld_i_msgv4 = 'Check type of data required'.