FKJO_DEBUG_MSG SAP Function module

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

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

Pattern for FM FKJO_DEBUG_MSG - FKJO DEBUG MSG

CALL FUNCTION 'FKJO_DEBUG_MSG' "
  EXPORTING
    i_msg1 =                    " any
*   i_msg2 =                    " any
*   i_msg3 =                    " any
*   i_msg4 =                    " any
    .  "  FKJO_DEBUG_MSG

ABAP code example for Function Module FKJO_DEBUG_MSG

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

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

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

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

CALL FUNCTION 'FKJO_DEBUG_MSG'
  EXPORTING
    i_msg1 =                     ld_i_msg1
*   i_msg2 =                     ld_i_msg2
*   i_msg3 =                     ld_i_msg3
*   i_msg4 =                     ld_i_msg4
    .  "  FKJO_DEBUG_MSG

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_i_msg1
 
 TYPE ANY ,
ld_i_msg2
 
 TYPE ANY ,
ld_i_msg3
 
 TYPE ANY ,
ld_i_msg4
 
 TYPE ANY .


ld_i_msg1 = 'Check type of data required'.
ld_i_msg2 = 'Check type of data required'.
ld_i_msg3 = 'Check type of data required'.
ld_i_msg4 = 'Check type of data required'.