SAP CNIF_TRACE_APPEND_MESSAGES Function Module for NOTRANSL: appends messages to a trace
CNIF_TRACE_APPEND_MESSAGES is a standard cnif trace append messages 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: appends messages to a trace 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 cnif trace append messages FM, simply by entering the name CNIF_TRACE_APPEND_MESSAGES into the relevant SAP transaction such as SE37 or SE38.
Function Group: CNIF
Program Name: SAPLCNIF
Main Program: SAPLCNIF
Appliation area: C
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:
Function CNIF_TRACE_APPEND_MESSAGES 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 'CNIF_TRACE_APPEND_MESSAGES'"NOTRANSL: appends messages to a trace.
EXPORTING
I_NAME = "Local file for upload/download
TABLES
I_MESSAGE_TABLE = "Message table for BAPIs (Project System)
EXCEPTIONS
TRACE_NOT_CREATED = 1
IMPORTING Parameters details for CNIF_TRACE_APPEND_MESSAGES
I_NAME - Local file for upload/download
Data type: RLGRAP-FILENAMEOptional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for CNIF_TRACE_APPEND_MESSAGES
I_MESSAGE_TABLE - Message table for BAPIs (Project System)
Data type: BAPI_METH_MESSAGEOptional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
TRACE_NOT_CREATED -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for CNIF_TRACE_APPEND_MESSAGES 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_name | TYPE RLGRAP-FILENAME, " | |||
lt_i_message_table | TYPE STANDARD TABLE OF BAPI_METH_MESSAGE, " | |||
lv_trace_not_created | TYPE BAPI_METH_MESSAGE. " |
  CALL FUNCTION 'CNIF_TRACE_APPEND_MESSAGES' "NOTRANSL: appends messages to a trace |
EXPORTING | ||
I_NAME | = lv_i_name | |
TABLES | ||
I_MESSAGE_TABLE | = lt_i_message_table | |
EXCEPTIONS | ||
TRACE_NOT_CREATED = 1 | ||
. " CNIF_TRACE_APPEND_MESSAGES |
ABAP code using 7.40 inline data declarations to call FM CNIF_TRACE_APPEND_MESSAGES
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 FILENAME FROM RLGRAP INTO @DATA(ld_i_name). | ||||
Search for further information about these or an SAP related objects