SAP CVD1_ACTLOG_APPEND Function Module for NOTRANSL: EHS: Anhängen einer Nachricht an das Aktion-Log









CVD1_ACTLOG_APPEND is a standard cvd1 actlog append 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: EHS: Anhängen einer Nachricht an das Aktion-Log 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 cvd1 actlog append FM, simply by entering the name CVD1_ACTLOG_APPEND into the relevant SAP transaction such as SE37 or SE38.

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



Function CVD1_ACTLOG_APPEND 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 'CVD1_ACTLOG_APPEND'"NOTRANSL: EHS: Anhängen einer Nachricht an das Aktion-Log
EXPORTING
I_RECN = "Report Shipping Order
* I_TRACE_LEVEL = 2 "Check level
I_MSGTY = "Message Type
* I_MSGID = IC_MSGID "
I_MSGNO = "Notification Number
* I_MSGV1 = ' ' "
* I_MSGV2 = ' ' "
* I_MSGV3 = ' ' "
* I_MSGV4 = ' ' "
* I_FLG_COMMIT = TRUE "

EXCEPTIONS
NO_APPL_IDENT = 1 NO_APPL_MSG = 2
.



IMPORTING Parameters details for CVD1_ACTLOG_APPEND

I_RECN - Report Shipping Order

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

I_TRACE_LEVEL - Check level

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

I_MSGTY - Message Type

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

I_MSGID -

Data type: CVDMESSAGE-MSGID
Default: IC_MSGID
Optional: Yes
Call by Reference: No ( called with pass by value option)

I_MSGNO - Notification Number

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

I_MSGV1 -

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

I_MSGV2 -

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

I_MSGV3 -

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

I_MSGV4 -

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

I_FLG_COMMIT -

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

EXCEPTIONS details

NO_APPL_IDENT -

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

NO_APPL_MSG -

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

Copy and paste ABAP code example for CVD1_ACTLOG_APPEND 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_i_recn  TYPE CVDDH-RECN, "   
lv_no_appl_ident  TYPE CVDDH, "   
lv_i_trace_level  TYPE SY-TABIX, "   2
lv_i_msgty  TYPE CVDMESSAGE-MSGTY, "   
lv_no_appl_msg  TYPE CVDMESSAGE, "   
lv_i_msgid  TYPE CVDMESSAGE-MSGID, "   IC_MSGID
lv_i_msgno  TYPE CVDMESSAGE-MSGNO, "   
lv_i_msgv1  TYPE CVDMESSAGE-MSGV1, "   SPACE
lv_i_msgv2  TYPE CVDMESSAGE-MSGV2, "   SPACE
lv_i_msgv3  TYPE CVDMESSAGE-MSGV3, "   SPACE
lv_i_msgv4  TYPE CVDMESSAGE-MSGV4, "   SPACE
lv_i_flg_commit  TYPE ESP1_BOOLEAN. "   TRUE

  CALL FUNCTION 'CVD1_ACTLOG_APPEND'  "NOTRANSL: EHS: Anhängen einer Nachricht an das Aktion-Log
    EXPORTING
         I_RECN = lv_i_recn
         I_TRACE_LEVEL = lv_i_trace_level
         I_MSGTY = lv_i_msgty
         I_MSGID = lv_i_msgid
         I_MSGNO = lv_i_msgno
         I_MSGV1 = lv_i_msgv1
         I_MSGV2 = lv_i_msgv2
         I_MSGV3 = lv_i_msgv3
         I_MSGV4 = lv_i_msgv4
         I_FLG_COMMIT = lv_i_flg_commit
    EXCEPTIONS
        NO_APPL_IDENT = 1
        NO_APPL_MSG = 2
. " CVD1_ACTLOG_APPEND




ABAP code using 7.40 inline data declarations to call FM CVD1_ACTLOG_APPEND

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.

"SELECT single RECN FROM CVDDH INTO @DATA(ld_i_recn).
 
 
"SELECT single TABIX FROM SY INTO @DATA(ld_i_trace_level).
DATA(ld_i_trace_level) = 2.
 
"SELECT single MSGTY FROM CVDMESSAGE INTO @DATA(ld_i_msgty).
 
 
"SELECT single MSGID FROM CVDMESSAGE INTO @DATA(ld_i_msgid).
DATA(ld_i_msgid) = IC_MSGID.
 
"SELECT single MSGNO FROM CVDMESSAGE INTO @DATA(ld_i_msgno).
 
"SELECT single MSGV1 FROM CVDMESSAGE INTO @DATA(ld_i_msgv1).
DATA(ld_i_msgv1) = ' '.
 
"SELECT single MSGV2 FROM CVDMESSAGE INTO @DATA(ld_i_msgv2).
DATA(ld_i_msgv2) = ' '.
 
"SELECT single MSGV3 FROM CVDMESSAGE INTO @DATA(ld_i_msgv3).
DATA(ld_i_msgv3) = ' '.
 
"SELECT single MSGV4 FROM CVDMESSAGE INTO @DATA(ld_i_msgv4).
DATA(ld_i_msgv4) = ' '.
 
DATA(ld_i_flg_commit) = TRUE.
 


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!