SAP CCM09_LOG_ISSUE_MESSAGE Function Module for NOTRANSL: Fehlermeldung aus CALO Log ausgeben
CCM09_LOG_ISSUE_MESSAGE is a standard ccm09 log issue message SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for NOTRANSL: Fehlermeldung aus CALO Log ausgeben processing and below is the pattern details for this FM, showing its interface including any import and export parameters, exceptions etc. there is also a full "cut and paste" ABAP pattern code example, along with implementation ABAP coding, documentation and contribution comments specific to this or related objects.
See here to view full function module documentation and code listing for ccm09 log issue message FM, simply by entering the name CCM09_LOG_ISSUE_MESSAGE into the relevant SAP transaction such as SE37 or SE38.
Function Group: CCM09
Program Name: SAPLCCM09
Main Program: SAPLCCM09
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function CCM09_LOG_ISSUE_MESSAGE pattern details
In-order to call this FM within your sap programs, simply using the below ABAP pattern details to trigger the function call...or see the full ABAP code listing at the end of this article. You can simply cut and paste this code into your ABAP progrom as it is, including variable declarations.CALL FUNCTION 'CCM09_LOG_ISSUE_MESSAGE'"NOTRANSL: Fehlermeldung aus CALO Log ausgeben.
EXPORTING
* IV_INIT = 'X' "Checkbox
EXCEPTIONS
LOG = 1 ERROR = 2
IMPORTING Parameters details for CCM09_LOG_ISSUE_MESSAGE
IV_INIT - Checkbox
Data type: XFELDDefault: 'X'
Optional: Yes
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
LOG - DE-EN-LANG-SWITCH-NO-TRANSLATION
Data type:Optional: No
Call by Reference: Yes
ERROR - DE-EN-LANG-SWITCH-NO-TRANSLATION
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for CCM09_LOG_ISSUE_MESSAGE Function Module
The ABAP code below is a full code listing to execute function module POPUP_TO_CONFIRM including all data declarations. The code uses the original data declarations rather than 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 newer method of declaring data variables on the fly. 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), which i why i have stuck to the origianl for this example.| DATA: | ||||
| lv_log | TYPE STRING, " | |||
| lv_iv_init | TYPE XFELD, " 'X' | |||
| lv_error | TYPE XFELD. " |
|   CALL FUNCTION 'CCM09_LOG_ISSUE_MESSAGE' "NOTRANSL: Fehlermeldung aus CALO Log ausgeben |
| EXPORTING | ||
| IV_INIT | = lv_iv_init | |
| EXCEPTIONS | ||
| LOG = 1 | ||
| ERROR = 2 | ||
| . " CCM09_LOG_ISSUE_MESSAGE | ||
ABAP code using 7.40 inline data declarations to call FM CCM09_LOG_ISSUE_MESSAGE
The below ABAP code uses the newer in-line data declarations. This allows you to see the coding differences/benefits of the later inline syntax. Please note some of the newer syntax below, such as the @DATA is not available until 4.70 EHP 8.| DATA(ld_iv_init) | = 'X'. | |||
Search for further information about these or an SAP related objects