SAP DPICB_LOG_INITIALIZE Function Module for Initialize application logging









DPICB_LOG_INITIALIZE is a standard dpicb log initialize SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Initialize application logging 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 dpicb log initialize FM, simply by entering the name DPICB_LOG_INITIALIZE into the relevant SAP transaction such as SE37 or SE38.

Function Group: DPICB_LOG
Program Name: SAPLDPICB_LOG
Main Program: SAPLDPICB_LOG
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:



Function DPICB_LOG_INITIALIZE 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 'DPICB_LOG_INITIALIZE'"Initialize application logging
EXPORTING
IS_LOG_OBJ = "Application Log: Log header data

IMPORTING
EV_LOG_HANDLE = "Application Log: Log Handle

EXCEPTIONS
LOG_HEADER_INCONSISTENT = 1 DEFAULTS_INCONSISTENT = 2 LOGGING_ERROR = 3 NOT_AUTHORIZED = 4
.



IMPORTING Parameters details for DPICB_LOG_INITIALIZE

IS_LOG_OBJ - Application Log: Log header data

Data type: BAL_S_LOG
Optional: No
Call by Reference: Yes

EXPORTING Parameters details for DPICB_LOG_INITIALIZE

EV_LOG_HANDLE - Application Log: Log Handle

Data type: BALLOGHNDL
Optional: No
Call by Reference: Yes

EXCEPTIONS details

LOG_HEADER_INCONSISTENT -

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

DEFAULTS_INCONSISTENT -

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

LOGGING_ERROR -

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

NOT_AUTHORIZED -

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

Copy and paste ABAP code example for DPICB_LOG_INITIALIZE 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_is_log_obj  TYPE BAL_S_LOG, "   
lv_ev_log_handle  TYPE BALLOGHNDL, "   
lv_log_header_inconsistent  TYPE BALLOGHNDL, "   
lv_defaults_inconsistent  TYPE BALLOGHNDL, "   
lv_logging_error  TYPE BALLOGHNDL, "   
lv_not_authorized  TYPE BALLOGHNDL. "   

  CALL FUNCTION 'DPICB_LOG_INITIALIZE'  "Initialize application logging
    EXPORTING
         IS_LOG_OBJ = lv_is_log_obj
    IMPORTING
         EV_LOG_HANDLE = lv_ev_log_handle
    EXCEPTIONS
        LOG_HEADER_INCONSISTENT = 1
        DEFAULTS_INCONSISTENT = 2
        LOGGING_ERROR = 3
        NOT_AUTHORIZED = 4
. " DPICB_LOG_INITIALIZE




ABAP code using 7.40 inline data declarations to call FM DPICB_LOG_INITIALIZE

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



Comments on this SAP object

What made you want to lookup this SAP object? Please tell us what you were looking for and anything you would like to be included on this page!