GM_POPUP_STATUS_COMMENT_ENTRY SAP Function module

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

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

Pattern for FM GM_POPUP_STATUS_COMMENT_ENTRY - GM POPUP STATUS COMMENT ENTRY

CALL FUNCTION 'GM_POPUP_STATUS_COMMENT_ENTRY' "
* EXPORTING
*   i_comment =                 " gm_status_comment  Comment for Status Change
*   i_lifecycle_status =        " gm_lifecycle_status  Lifecycle Status
*   i_user_status =             " j_estat       User Status
*   i_status_profile =          " gm_status_profile  Status profile for the user states attached to system states
*   i_grant_nbr =               " gm_grant_nbr  Grant
  IMPORTING
    answer =                    "
    e_comment =                 " gm_status_comment  Comment for Status Change
  EXCEPTIONS
    TITEL_TOO_LONG = 1          "
    .  "  GM_POPUP_STATUS_COMMENT_ENTRY

ABAP code example for Function Module GM_POPUP_STATUS_COMMENT_ENTRY

The ABAP code below is a full code listing to execute function module GM_POPUP_STATUS_COMMENT_ENTRY 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_answer  
 
 TYPE STRING
,
ld_e_comment  
 
 TYPE GM_STATUS_COMMENT
.


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

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

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

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

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

CALL FUNCTION 'GM_POPUP_STATUS_COMMENT_ENTRY'
* EXPORTING
*   i_comment =                  ld_i_comment
*   i_lifecycle_status =         ld_i_lifecycle_status
*   i_user_status =              ld_i_user_status
*   i_status_profile =           ld_i_status_profile
*   i_grant_nbr =                ld_i_grant_nbr
  IMPORTING
    answer =                     ld_answer
    e_comment =                  ld_e_comment
  EXCEPTIONS
    TITEL_TOO_LONG =             1
    .  "  GM_POPUP_STATUS_COMMENT_ENTRY

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_answer
 
 TYPE STRING ,
ld_i_comment
 
 TYPE GM_STATUS_COMMENT ,
ld_e_comment
 
 TYPE GM_STATUS_COMMENT ,
ld_i_lifecycle_status
 
 TYPE GM_LIFECYCLE_STATUS ,
ld_i_user_status
 
 TYPE J_ESTAT ,
ld_i_status_profile
 
 TYPE GM_STATUS_PROFILE ,
ld_i_grant_nbr
 
 TYPE GM_GRANT_NBR .


ld_i_comment = 'Check type of data required'.
ld_i_lifecycle_status = 'Check type of data required'.
ld_i_user_status = 'Check type of data required'.
ld_i_status_profile = 'Check type of data required'.
ld_i_grant_nbr = 'Check type of data required'.