SAP PFO_CREATE_LOG_ENTRY Function Module for NOTRANSL: Eintrag ins Log erzeugen
PFO_CREATE_LOG_ENTRY is a standard pfo create log entry 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: Eintrag ins Log erzeugen 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 pfo create log entry FM, simply by entering the name PFO_CREATE_LOG_ENTRY into the relevant SAP transaction such as SE37 or SE38.
Function Group: PFO_LOG
Program Name: SAPLPFO_LOG
Main Program: SAPLPFO_LOG
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function PFO_CREATE_LOG_ENTRY 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 'PFO_CREATE_LOG_ENTRY'"NOTRANSL: Eintrag ins Log erzeugen.
EXPORTING
IS_BALMSG = "Application Log: Message Data
CHANGING
CO_BAL = "CACS: Application Log
EXCEPTIONS
CX_CACS_BAL_EX = 1
IMPORTING Parameters details for PFO_CREATE_LOG_ENTRY
IS_BALMSG - Application Log: Message Data
Data type: BAL_S_MSGOptional: No
Call by Reference: Yes
CHANGING Parameters details for PFO_CREATE_LOG_ENTRY
CO_BAL - CACS: Application Log
Data type: CL_CACS_BALOptional: No
Call by Reference: Yes
EXCEPTIONS details
CX_CACS_BAL_EX - CACS: Application Log Exceptions
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for PFO_CREATE_LOG_ENTRY 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_co_bal | TYPE CL_CACS_BAL, " | |||
| lv_is_balmsg | TYPE BAL_S_MSG, " | |||
| lv_cx_cacs_bal_ex | TYPE BAL_S_MSG. " |
|   CALL FUNCTION 'PFO_CREATE_LOG_ENTRY' "NOTRANSL: Eintrag ins Log erzeugen |
| EXPORTING | ||
| IS_BALMSG | = lv_is_balmsg | |
| CHANGING | ||
| CO_BAL | = lv_co_bal | |
| EXCEPTIONS | ||
| CX_CACS_BAL_EX = 1 | ||
| . " PFO_CREATE_LOG_ENTRY | ||
ABAP code using 7.40 inline data declarations to call FM PFO_CREATE_LOG_ENTRY
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.Search for further information about these or an SAP related objects