SAP CACS_BUFFERLOG_SAVE Function Module for NOTRANSL: Prov.: Sichere aufgelaufene Nachrichten in LogFile zum Obj

Search SAP Function Modules

CACS_BUFFERLOG_SAVE is a standard cacs bufferlog save 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: Prov.: Sichere aufgelaufene Nachrichten in LogFile zum Obj 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 cacs bufferlog save FM, simply by entering the name CACS_BUFFERLOG_SAVE into the relevant SAP transaction such as SE37 or SE38.

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

Function CACS_BUFFERLOG_SAVE 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 'CACS_BUFFERLOG_SAVE'"NOTRANSL: Prov.: Sichere aufgelaufene Nachrichten in LogFile zum Obj
  EXPORTING
*  I_LOG_HANDLE =  "Application Log: Log Handle
*  I_LOG_EXTNUMBER =  "Application Log: External Identification
*  IFLG_SIMULATION = 'X' "Process should be carried out in simulation mode
*  IFLG_UPDATE_TASK =  "x = Update Mode
*  IFLG_REJECTED =  "Was the Object rejected by Process? (X = rejected)
*  IFGL_RETURN_MSSGS = ' ' "Message return? (return 'X' messages)
*  IFLG_REFRESH_BUFFER = ' ' "Reset Puffer Application Log (X = yes, space = no)

TABLES
*  CT_MSG_DATA =  "Return of all Messages for a Log

EXCEPTIONS
   LOG_NOT_FOUND = 1    SAVE_NOT_ALLOWED = 2    NUMBERING_ERROR = 3    SEVERE_ERROR = 4    MSG_NOT_FOUND = 5    LOG_HEADER_INCONSISTENT = 6 

.

IMPORTING Parameters details for CACS_BUFFERLOG_SAVE

I_LOG_HANDLE - Application Log: Log Handle

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

I_LOG_EXTNUMBER - Application Log: External Identification

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

IFLG_SIMULATION - Process should be carried out in simulation mode

Data type: CACSSIMULATION
Default: 'X'
Optional: Yes
Call by Reference: No ( called with pass by value option)

IFLG_UPDATE_TASK - x = Update Mode

Data type: BOOLEAN_FLG
Optional: Yes
Call by Reference: Yes

IFLG_REJECTED - Was the Object rejected by Process? (X = rejected)

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

IFGL_RETURN_MSSGS - Message return? (return 'X' messages)

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

IFLG_REFRESH_BUFFER - Reset Puffer Application Log (X = yes, space = no)

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

TABLES Parameters details for CACS_BUFFERLOG_SAVE

CT_MSG_DATA - Return of all Messages for a Log

Data type: CACS_T_MSG_DATA
Optional: Yes
Call by Reference: Yes

EXCEPTIONS details

LOG_NOT_FOUND - Log Not Found

Data type:
Optional: No
Call by Reference: Yes

SAVE_NOT_ALLOWED -

Data type:
Optional: No
Call by Reference: Yes

NUMBERING_ERROR - Error in number assignment

Data type:
Optional: No
Call by Reference: Yes

SEVERE_ERROR - Unknown error

Data type:
Optional: No
Call by Reference: Yes

MSG_NOT_FOUND - Message not found

Data type:
Optional: No
Call by Reference: Yes

LOG_HEADER_INCONSISTENT -

Data type:
Optional: No
Call by Reference: Yes

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

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