SAP CNV_CDOP_PROTOCOL_WRITE_LOG_DB Function Module for Write Log to database

Search SAP Function Modules

CNV_CDOP_PROTOCOL_WRITE_LOG_DB is a standard cnv cdop protocol write log db SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Write Log to database 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 cnv cdop protocol write log db FM, simply by entering the name CNV_CDOP_PROTOCOL_WRITE_LOG_DB into the relevant SAP transaction such as SE37 or SE38.

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

Function CNV_CDOP_PROTOCOL_WRITE_LOG_DB 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 'CNV_CDOP_PROTOCOL_WRITE_LOG_DB'"Write Log to database
  EXPORTING
*  IV_CLIENT = ' ' "R/3 System, client number from logon
*  IV_UPDATE_TASK = ' ' "boolean variable (X=true, -=false, space=unknown)
*  IV_SAVE_ALL = ' ' "boolean variable (X=true, -=false, space=unknown)
*  IV_LOG_HANDLE =  "Application Log: Log handle

EXCEPTIONS
   LOG_NOT_FOUND = 1    SAVE_NOT_ALLOWED = 2    NUMBERING_ERROR = 3    NOT_POSSIBLE = 4 

.

IMPORTING Parameters details for CNV_CDOP_PROTOCOL_WRITE_LOG_DB

IV_CLIENT - R/3 System, client number from logon

Data type: SY-MANDT
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

IV_UPDATE_TASK - boolean variable (X=true, -=false, space=unknown)

Data type: BOOLEAN
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

IV_SAVE_ALL - boolean variable (X=true, -=false, space=unknown)

Data type: BOOLEAN
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

IV_LOG_HANDLE - Application Log: Log handle

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

EXCEPTIONS details

LOG_NOT_FOUND - Log not found

Data type:
Optional: No
Call by Reference: Yes

SAVE_NOT_ALLOWED - Save not allowed

Data type:
Optional: No
Call by Reference: Yes

NUMBERING_ERROR - Numbering error occured

Data type:
Optional: No
Call by Reference: Yes

NOT_POSSIBLE - Error occured while saving log

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for CNV_CDOP_PROTOCOL_WRITE_LOG_DB 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.

ABAP code using 7.40 inline data declarations to call FM CNV_CDOP_PROTOCOL_WRITE_LOG_DB

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