CNV_CDOP_PROTOCOL_CREATE_LOG SAP Function module - Create Application Log

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

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

Pattern for FM CNV_CDOP_PROTOCOL_CREATE_LOG - CNV CDOP PROTOCOL CREATE LOG

CALL FUNCTION 'CNV_CDOP_PROTOCOL_CREATE_LOG' "Create Application Log
  EXPORTING
    iv_proj =                   " cnvcdop_projects-project_id  CDOP - Project ID
    iv_activity =               " cnvcdop_img-activity_id  CDOP - Activity ID
    iv_sysid =                  " sy-sysid      Logical destination (specified in function call)
    iv_repid =                  " sy-repid      ABAP program, current main program
  IMPORTING
    ev_log_handle =             " balloghndl    Application Log: Log handle
    ev_extnumber =              " bal_s_log-extnumber  Application Log: External ID
  EXCEPTIONS
    APPL_LOG_ERROR = 1          "               Unable to create Application Log
    .  "  CNV_CDOP_PROTOCOL_CREATE_LOG

ABAP code example for Function Module CNV_CDOP_PROTOCOL_CREATE_LOG

The ABAP code below is a full code listing to execute function module CNV_CDOP_PROTOCOL_CREATE_LOG 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_ev_log_handle  
 
 TYPE BALLOGHNDL
,
ld_ev_extnumber  
 
 TYPE BAL_S_LOG-EXTNUMBER
.

 

SELECT single PROJECT_ID 
  FROM CNVCDOP_PROJECTS 
  INTO @DATA(ld_iv_proj).

 

SELECT single ACTIVITY_ID 
  FROM CNVCDOP_IMG 
  INTO @DATA(ld_iv_activity).


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

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

CALL FUNCTION 'CNV_CDOP_PROTOCOL_CREATE_LOG'
  EXPORTING
    iv_proj =                    ld_iv_proj
    iv_activity =                ld_iv_activity
    iv_sysid =                   ld_iv_sysid
    iv_repid =                   ld_iv_repid
  IMPORTING
    ev_log_handle =              ld_ev_log_handle
    ev_extnumber =               ld_ev_extnumber
  EXCEPTIONS
    APPL_LOG_ERROR =             1
    .  "  CNV_CDOP_PROTOCOL_CREATE_LOG

IF SY-SUBRC EQ 0.
  "All OK
ELSEIF SY-SUBRC EQ 1. "Exception
  "Add code for exception here
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_ev_log_handle
 
 TYPE BALLOGHNDL ,
ld_iv_proj
 
 TYPE CNVCDOP_PROJECTS-PROJECT_ID ,
ld_ev_extnumber
 
 TYPE BAL_S_LOG-EXTNUMBER ,
ld_iv_activity
 
 TYPE CNVCDOP_IMG-ACTIVITY_ID ,
ld_iv_sysid
 
 TYPE SY-SYSID ,
ld_iv_repid
 
 TYPE SY-REPID .



SELECT single PROJECT_ID 
  FROM CNVCDOP_PROJECTS 
  INTO ld_iv_proj.


SELECT single ACTIVITY_ID 
  FROM CNVCDOP_IMG 
  INTO ld_iv_activity.

ld_iv_sysid = 'Check type of data required'.
ld_iv_repid = 'Check type of data required'.