Calendar Schema
A calendar schema specifies which days should be considered during the aggregation to weekly, monthly, quarterly, or yearly values. In this way you can ensure that only values from the days are considered which, for example, the factory calendar shows as being workdays.
In the Central Performance History (CPH) of the monitoring architecture, average values for minutes, quarter hours, and hours are read from the monitoring segment of the monitoring architecture. These values are aggregated into a coarser granularity in accordance with the rules of the relevant collection and reorganization schema and then the data for the finer granularity is deleted. In this way, for example, 24 values (one per hour) are aggregated to one value (one per day).
This aggregation can be performed with a simple average value calculation, however using day schemata and calendar schemata, you can use only certain values for the aggregation that are relevant for you. In this way, you can, for example, use the calendar schema to ensure that weekends and public holidays are not considered during the aggregation of daily values to a coarser granularity.
Calendar schemata are used during all reorganizations in which daily data is aggregated.
For an explanation of this table display, see Collection and Reorganization Schema.
Every rule of a calendar schema can also contain a day schema. This can be useful, for example, during the aggregation of daily values with at least an hourly granularity to any aggregate with a daily granularity, for example, if different working times apply on different days.
To map a working week in which the employees work from Monday-Thursday from 08:00 to 18:00, and on Friday from 08:00 until 15:00 (and you only want to consider these values during aggregation of the performance values), create the following calendar schema:
| Day | Day schema | Discard During Reorganization |
|---|---|---|
|
Monday - Thursday |
08:00 - 18:00 |
no |
|
Friday |
08:00 -15:00 |
no |
|
Saturday - Sunday; Public holidays |
No schema |
yes |
Special Case: Minimum/Maximum
The day schemata with the endings MIN and MAX are a special case (see: Day Schema). You can use these schemata to determine the largest and smallest values that are reached during the course of a day. If you assign these schemata to a rule for a calendar schema, it is not the average value of the measurements that is used for the aggregation, but rather the smallest or largest value of the values before the aggregation is determined.
These special day schemata are less useful for the reorganization. They are primarily for use in reporting and analysis (see Creating Reports with the Central Performance History).
Daily aggregates with an hourly granularity should be aggregated to a monthly aggregate with a daily granularity. The valid calendar schema contains only one rule, which contains the day schema SAP_AVG_MAX and only considers workdays during the reorganization. As a consequence, a value is calculated for each month. This is the maximum of the values that was collected during the hours that fell on a workday.
SAP delivers two calendar schemata by default:
- · SAP_CAL_INTERNATIONAL
The schema is based on the international factory calendar (ID 99); as part of this, the values from weekends (Saturday and Sunday) and the following international public holidays are not considered or displayed in reports:
New Year's Day
Easter Monday
Christmas Day
Good Friday
Whit Sunday
Boxing Day
Easter Sunday
Whit Monday
New Year's Eve
- · SAP_CAL_NO_WEEKENDS
This schema simply discards the values for weekends. Public holidays are regarded as normal workdays.
See also:
Creating and Editing a Calendar Schema
Central Performance History of the Monitoring Architecture start page