CMS_API_NOTES_MAINTAIN_INLINE SAP Function module - Maintain notes with Inline functionality

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

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

Pattern for FM CMS_API_NOTES_MAINTAIN_INLINE - CMS API NOTES MAINTAIN INLINE

CALL FUNCTION 'CMS_API_NOTES_MAINTAIN_INLINE' "Maintain notes with Inline functionality
  EXPORTING
    i_str_notes_key =           " cms_str_notes_key_maint_inline  Notes key for entities
*   i_title = SPACE             " cms_dte_title  Title for the notes
    i_flg_display = SPACE       " cms_dte_display_flg  Flag to Indicate whether the Object is to be Displayed
    i_tab_txt_inline =          " cms_tab_txt_tline  Text lines
  IMPORTING
    e_flg_changed =             " cms_dte_flg   Indicator
    e_tab_rc =                  " cms_tab_msg_col_message  Return Code and corresponding Message
    .  "  CMS_API_NOTES_MAINTAIN_INLINE

ABAP code example for Function Module CMS_API_NOTES_MAINTAIN_INLINE

The ABAP code below is a full code listing to execute function module CMS_API_NOTES_MAINTAIN_INLINE 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_e_flg_changed  
 
 TYPE CMS_DTE_FLG
,
ld_e_tab_rc  
 
 TYPE CMS_TAB_MSG_COL_MESSAGE
.


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

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

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

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

CALL FUNCTION 'CMS_API_NOTES_MAINTAIN_INLINE'
  EXPORTING
    i_str_notes_key =            ld_i_str_notes_key
*   i_title =                    ld_i_title
    i_flg_display =              ld_i_flg_display
    i_tab_txt_inline =           ld_i_tab_txt_inline
  IMPORTING
    e_flg_changed =              ld_e_flg_changed
    e_tab_rc =                   ld_e_tab_rc
    .  "  CMS_API_NOTES_MAINTAIN_INLINE

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_e_flg_changed
 
 TYPE CMS_DTE_FLG ,
ld_i_str_notes_key
 
 TYPE CMS_STR_NOTES_KEY_MAINT_INLINE ,
ld_e_tab_rc
 
 TYPE CMS_TAB_MSG_COL_MESSAGE ,
ld_i_title
 
 TYPE CMS_DTE_TITLE ,
ld_i_flg_display
 
 TYPE CMS_DTE_DISPLAY_FLG ,
ld_i_tab_txt_inline
 
 TYPE CMS_TAB_TXT_TLINE .


ld_i_str_notes_key = 'Check type of data required'.
ld_i_title = 'Check type of data required'.
ld_i_flg_display = 'Check type of data required'.
ld_i_tab_txt_inline = 'Check type of data required'.