SAP CALENDAR_CHECK_BUFFERSIZE Function Module for Check whether buffer size is sufficient for insertion/change

Search SAP Function Modules

CALENDAR_CHECK_BUFFERSIZE is a standard calendar check buffersize SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Check whether buffer size is sufficient for insertion/change 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 calendar check buffersize FM, simply by entering the name CALENDAR_CHECK_BUFFERSIZE into the relevant SAP transaction such as SE37 or SE38.

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

Function CALENDAR_CHECK_BUFFERSIZE 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 'CALENDAR_CHECK_BUFFERSIZE'"Check whether buffer size is sufficient for insertion/change
  EXPORTING
   KIND_OF_CALENDAR =  "F=Factory calendar, H=Public holid
   KIND_OF_UPDATE =  "I=Insert, U=Update, D=Delete
   NUMBER_OF_YEARS =  "Number of years of the calendar

 IMPORTING
   ANSWER =  "Indicates whether there is enough
   BUFFERSIZE =  "Size of the pool buffer after chan
   DIRECTORYSIZE =  "Size of the directory buffer after

.

IMPORTING Parameters details for CALENDAR_CHECK_BUFFERSIZE

KIND_OF_CALENDAR - F=Factory calendar, H=Public holid

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

KIND_OF_UPDATE - I=Insert, U=Update, D=Delete

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

NUMBER_OF_YEARS - Number of years of the calendar

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

EXPORTING Parameters details for CALENDAR_CHECK_BUFFERSIZE

ANSWER - Indicates whether there is enough

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

BUFFERSIZE - Size of the pool buffer after chan

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

DIRECTORYSIZE - Size of the directory buffer after

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

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

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