SAP CO_VA_APPLOG_APPEND_SYFIELDS Function Module for NOTRANSL: schreibe SY-Felder in das Anwendungslog









CO_VA_APPLOG_APPEND_SYFIELDS is a standard co va applog append syfields 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: schreibe SY-Felder in das Anwendungslog 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 co va applog append syfields FM, simply by entering the name CO_VA_APPLOG_APPEND_SYFIELDS into the relevant SAP transaction such as SE37 or SE38.

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



Function CO_VA_APPLOG_APPEND_SYFIELDS 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 'CO_VA_APPLOG_APPEND_SYFIELDS'"NOTRANSL: schreibe SY-Felder in das Anwendungslog
EXPORTING
* I_TYPE = "Messages, Message Type
* I_ID = "Messages, Message Class
* I_NUMBER = "Messages, Message Number
* I_MESSAGE_V1 = "Messages, Message Variable
* I_MESSAGE_V2 = "Messages, Message Variable
* I_MESSAGE_V3 = "Messages, Message Variable
* I_MESSAGE_V4 = "Messages, Message Variable
.




Customer Function user exits

Below is a list of CUSTOMER FUNCTION exit user exits that are available within this program and maybe relevant for this FM.
EXIT_SAPLCOVA_001 DE-EN-LANG-SWITCH-NO-TRANSLATION
EXIT_SAPLCOVA_002 DE-EN-LANG-SWITCH-NO-TRANSLATION
EXIT_SAPLCOVA_003 DE-EN-LANG-SWITCH-NO-TRANSLATION
EXIT_SAPLCOVA_004 DE-EN-LANG-SWITCH-NO-TRANSLATION
EXIT_SAPLCOVA_005 DE-EN-LANG-SWITCH-NO-TRANSLATION
EXIT_SAPLCOVA_006 DE-EN-LANG-SWITCH-NO-TRANSLATION

IMPORTING Parameters details for CO_VA_APPLOG_APPEND_SYFIELDS

I_TYPE - Messages, Message Type

Data type: SY-MSGTY
Optional: Yes
Call by Reference: Yes

I_ID - Messages, Message Class

Data type: SY-MSGID
Optional: Yes
Call by Reference: Yes

I_NUMBER - Messages, Message Number

Data type: SY-MSGNO
Optional: Yes
Call by Reference: Yes

I_MESSAGE_V1 - Messages, Message Variable

Data type: SY-MSGV1
Optional: Yes
Call by Reference: Yes

I_MESSAGE_V2 - Messages, Message Variable

Data type: SY-MSGV2
Optional: Yes
Call by Reference: Yes

I_MESSAGE_V3 - Messages, Message Variable

Data type: SY-MSGV3
Optional: Yes
Call by Reference: Yes

I_MESSAGE_V4 - Messages, Message Variable

Data type: SY-MSGV4
Optional: Yes
Call by Reference: Yes

Copy and paste ABAP code example for CO_VA_APPLOG_APPEND_SYFIELDS 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_type  TYPE SY-MSGTY, "   
lv_i_id  TYPE SY-MSGID, "   
lv_i_number  TYPE SY-MSGNO, "   
lv_i_message_v1  TYPE SY-MSGV1, "   
lv_i_message_v2  TYPE SY-MSGV2, "   
lv_i_message_v3  TYPE SY-MSGV3, "   
lv_i_message_v4  TYPE SY-MSGV4. "   

  CALL FUNCTION 'CO_VA_APPLOG_APPEND_SYFIELDS'  "NOTRANSL: schreibe SY-Felder in das Anwendungslog
    EXPORTING
         I_TYPE = lv_i_type
         I_ID = lv_i_id
         I_NUMBER = lv_i_number
         I_MESSAGE_V1 = lv_i_message_v1
         I_MESSAGE_V2 = lv_i_message_v2
         I_MESSAGE_V3 = lv_i_message_v3
         I_MESSAGE_V4 = lv_i_message_v4
. " CO_VA_APPLOG_APPEND_SYFIELDS




ABAP code using 7.40 inline data declarations to call FM CO_VA_APPLOG_APPEND_SYFIELDS

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 MSGTY FROM SY INTO @DATA(ld_i_type).
 
"SELECT single MSGID FROM SY INTO @DATA(ld_i_id).
 
"SELECT single MSGNO FROM SY INTO @DATA(ld_i_number).
 
"SELECT single MSGV1 FROM SY INTO @DATA(ld_i_message_v1).
 
"SELECT single MSGV2 FROM SY INTO @DATA(ld_i_message_v2).
 
"SELECT single MSGV3 FROM SY INTO @DATA(ld_i_message_v3).
 
"SELECT single MSGV4 FROM SY INTO @DATA(ld_i_message_v4).
 


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!