ISM_JKSOCREATE_HELP_VAL_ADDPAY SAP Function module - IS-M: BSP Application - Value Help for Additional Payment Type

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

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

Pattern for FM ISM_JKSOCREATE_HELP_VAL_ADDPAY - ISM JKSOCREATE HELP VAL ADDPAY

CALL FUNCTION 'ISM_JKSOCREATE_HELP_VAL_ADDPAY' "IS-M: BSP Application - Value Help for Additional Payment Type
* EXPORTING
*   iv_xshow_key = SPACE        " xfeld         Checkbox Field
*   iv_delimiter = ' - '        " string
*   iv_aktsprsl = SY-LANGU      " sylangu       Current Language
*   iv_bassprsl = SY-LANGU      " sylangu       Current Language
*   iv_xdisplay_longtext = SPACE  " xfeld       Checkbox Field
  IMPORTING
    et_help_val_donation =      " shsvaltab     Business Server Pages (BSP) Value List Search Help
    et_help_val_tip =           " shsvaltab     Business Server Pages (BSP) Value List Search Help
  EXCEPTIONS
    ERROR_READING_VALUES = 1    "
    .  "  ISM_JKSOCREATE_HELP_VAL_ADDPAY

ABAP code example for Function Module ISM_JKSOCREATE_HELP_VAL_ADDPAY

The ABAP code below is a full code listing to execute function module ISM_JKSOCREATE_HELP_VAL_ADDPAY 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_et_help_val_donation  
 
 TYPE SHSVALTAB
,
ld_et_help_val_tip  
 
 TYPE SHSVALTAB
.


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

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

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

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

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

CALL FUNCTION 'ISM_JKSOCREATE_HELP_VAL_ADDPAY'
* EXPORTING
*   iv_xshow_key =               ld_iv_xshow_key
*   iv_delimiter =               ld_iv_delimiter
*   iv_aktsprsl =                ld_iv_aktsprsl
*   iv_bassprsl =                ld_iv_bassprsl
*   iv_xdisplay_longtext =       ld_iv_xdisplay_longtext
  IMPORTING
    et_help_val_donation =       ld_et_help_val_donation
    et_help_val_tip =            ld_et_help_val_tip
  EXCEPTIONS
    ERROR_READING_VALUES =       1
    .  "  ISM_JKSOCREATE_HELP_VAL_ADDPAY

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_et_help_val_donation
 
 TYPE SHSVALTAB ,
ld_iv_xshow_key
 
 TYPE XFELD ,
ld_et_help_val_tip
 
 TYPE SHSVALTAB ,
ld_iv_delimiter
 
 TYPE STRING ,
ld_iv_aktsprsl
 
 TYPE SYLANGU ,
ld_iv_bassprsl
 
 TYPE SYLANGU ,
ld_iv_xdisplay_longtext
 
 TYPE XFELD .


ld_iv_xshow_key = 'Check type of data required'.
ld_iv_delimiter = 'Check type of data required'.
ld_iv_aktsprsl = 'Check type of data required'.
ld_iv_bassprsl = 'Check type of data required'.
ld_iv_xdisplay_longtext = 'Check type of data required'.