CPE_GUI_SET_LOG_BUTTON_STATUS SAP Function module - Set traffic light and tooltip of error log button

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

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

Pattern for FM CPE_GUI_SET_LOG_BUTTON_STATUS - CPE GUI SET LOG BUTTON STATUS

CALL FUNCTION 'CPE_GUI_SET_LOG_BUTTON_STATUS' "Set traffic light and tooltip of error log button
* EXPORTING
*   it_cpe_msg_log =            " cpet_msg_com_tab  CPE - Log: Communication Table for Messages
*   iv_doc_guid =               " cpet_guid     CPE - Object GUID
*   iv_docitem_guid =           " cpet_guid     CPE - Object GUID
*   iv_cond_type =              " cpet_cond_type  CPE: Condition Type for Commodity Pricing
  CHANGING
    cs_log_button =             " smp_dyntxt    Menu Painter: Program interface for dynamic texts
    .  "  CPE_GUI_SET_LOG_BUTTON_STATUS

ABAP code example for Function Module CPE_GUI_SET_LOG_BUTTON_STATUS

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

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

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

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

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

CALL FUNCTION 'CPE_GUI_SET_LOG_BUTTON_STATUS'
* EXPORTING
*   it_cpe_msg_log =             ld_it_cpe_msg_log
*   iv_doc_guid =                ld_iv_doc_guid
*   iv_docitem_guid =            ld_iv_docitem_guid
*   iv_cond_type =               ld_iv_cond_type
  CHANGING
    cs_log_button =              ld_cs_log_button
    .  "  CPE_GUI_SET_LOG_BUTTON_STATUS

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_cs_log_button
 
 TYPE SMP_DYNTXT ,
ld_it_cpe_msg_log
 
 TYPE CPET_MSG_COM_TAB ,
ld_iv_doc_guid
 
 TYPE CPET_GUID ,
ld_iv_docitem_guid
 
 TYPE CPET_GUID ,
ld_iv_cond_type
 
 TYPE CPET_COND_TYPE .


ld_cs_log_button = 'Check type of data required'.
ld_it_cpe_msg_log = 'Check type of data required'.
ld_iv_doc_guid = 'Check type of data required'.
ld_iv_docitem_guid = 'Check type of data required'.
ld_iv_cond_type = 'Check type of data required'.