The new buffering method makes it possible to load the public holiday calendar and factory calendar into the calendar buffer using their validity period, and not just for the entered activation interval making them available for further use. The maintenance of the activation interval for the public holiday and factory calendars is therefore unnecessary.
The new buffer handler allows the dynamic loading of individual calendars when memory is short. If the buffer is sufficiently large, all defined calendars are loaded into the buffer as a default. Furthermore, the calendar buffer was included in the buffer synchronization. This way, changes to calendar definitions as well as the creation of new calendars is synchronized systemwide.
In addition, the the change document functionality has been included in SAP calendar maintenance. You can now display all changes which affect public holidays, the public holiday calendar and the factory calendar.
none
none
none
A monitor transaction allows the monitoring of the calendar buffer. You reach this by selecting Tools -> Administration -> Monitor -> Performance, Setup/buffers -> Buffers . The detail display of the line "Calendar" (double click) provides more precise data on the utilization and quality of the calendar buffer. The size of the calendar buffer is controlled by the profile parameter "zcsa/calendar_area". The profile parameter "zcsa/calendar_ids" controls the number of available directory entries.
none
none
The following functions or activation information in the SAP calendar are no longer needed and have therefore been deleted from the user interface of the SAP calendar.
The function Display change documents (function key F8)
was included in the Edit menu of the calendar interface for
displaying the created change documents for the SAP calendar.
The procedure for creating and changing a public holiday calendar or a factory calendar has only changed in that the activation interval no longer needs to or can no longer be maintained. Consequently, the activation of public holiday and factory calendars is also inapplicable.
If a public holiday calendar or factory calendar is created again, the new calendar dates for the years entered in the validity period are also loaded into the local calendar buffer when saving the calendar. Also when saving the new calendar, the calendar buffers are synchronized on all the remaining application servers if a distributed R3 installation exists.
When changing a public holiday calendar or a factory calendar, the procedure for setting up the calendar buffer is just the same as when creating a calendar. If the calendar is saved, the changed calendar dates are loaded into the calendar buffer for the entered validity period, and the available application servers are synchronized with a distributed installation.
If a public holiday, a public holiday calendar or a factory calendar is created, changed or deleted, then change documents are automatically generated for the corresponding activity when saving.
The new function Display change documents, for displaying the change documents that are generated like this, was included in the Edit menu of SAP calendar maintenance.
If the function is called from the overview screen of the public holiday calendar, all the change documents of the public holiday calendars are displayed. In addition, it is possible to limit the display of the change documents via a dialog box according to the following criteria:
On the other hand, if the function Display change documents is called from the detail screen of the public holiday calendar, only the change documents for this public holiday calendar are displayed. Here, you also have the option of restricting the change documents to be displayed.
The same functionality for the change documents exists for public holidays and factory calendars. However, please note that the change documents for individual public holidays cannot be displayed. All the public holiday change documents are always displayed according to the required restriction.
none
none
none
When saving a public holiday calendar or a factory calendar, it checks whether the available storage area or the number of the directory entries in the calendar buffer is sufficient to include the additional or changed calendar. If this is given, the calendar buffer is completely set up again. As a result, a fragmentation of the buffer is avoided and a very efficient implementation of buffer accesses is possible. Since calendars are only changed or created within Customizing, this design decision is the most favorable.
If the storage area or the directory entries are not sufficient, the calendar buffer is reset and only the public holiday calendar and the factory calendar which are accessed from the application are rolled in. A syslog entry is written in such a case.
The two last fields of the table TCALS contain the minimum number of directory entries required as well as the minimum required data range for the currently available calendars. The values can be viewed in the transaction Tools -> ABAP/4 Workbench -> Development -> ABAP/4 Dictionary -> Test -> Data Browser.
These values can be changed by the following profile parameters: