Import of Calendar

A Calendar is imported as a set of buckets and each bucket contains a start date, an end date, and a name.

Buckets represent start date that is inclusive and end date that is excluded. Consequently, a subsequent bucket starts on the same date as the end date of the previous bucket.

These field mappings are applicable for importing the calendar:


Mapped Field	Description
Bucket Start	Bucket start date (Inclusive)
Bucket End	Bucket end date (Exclusive)
Bucket Name	Bucket Name

Note: The Bucket name must be unique across all buckets available in the calendar.

Process

These processes are followed during the import of resources:

All existing buckets in the calendar including the existing quantity are deleted.
For each row to be imported, a bucket is created using the values specified for Bucket Name, Bucket Start and Bucket End.
When buckets are created for all rows, the planning horizon is set to all buckets in the entire calendar.

Validation rules

These validation rules are applicable for importing calendars:

Each bucket must have an end date greater than the start date. Else, the import process fails with this error message:
```
APACS248=Bucket {0} start date {1} is after end date {2}.
```
Where, {0} = Bucket name, {1} = Start date of bucket, {2} = End date of bucket.
The imported calendar must not contain an interval in dates between buckets. Else, the import process fails with this error message:
```
APACS247=Gap between bucket {0} end date {1} and bucket {2} start date {3}. They should be the same.
```
Where, {0} = First bucket name, {1} = End date of first bucket, {2} = Second bucket name, {3} = Start date of second bucket.
The imported calendar must not contain overlapping of bucket start date and end date. Else, the import process fails with this error message:
```
APACS246=Bucket {0} end date {1} overlaps with bucket {2} start date {3}. They should be the same.
```
Where, {0} = First bucket name, {1} = End date of first bucket, {2} = Second bucket date, {3} = Start date of second bucket.
The imported buckets must not contain the same name. Else, the import process fails with this error message:
```
APACS260=Bucket name {0} is duplicated in multiple buckets.
```
Where {0} = The first duplicated bucket.

Validation message

A summary message containing information such as the number of buckets successfully imported, and the duration of the import is reported on the completion of the import process. For example:

APACS108=Imported {0} buckets (duration {1}).

Where {0} = Number of buckets successfully imported, {1} = Duration of import in H:mm:ss format.

Example

This table describes the mapping example and the import values for the calendar:


Bucket Name	Bucket Start	Bucket End
FY19 W01	31-DEC-2018	07-JAN-2019
FY19 W02	07-JAN-2019	14-JAN-2019

In this example, two weekly buckets (each 7 days in length) are created. When the import process is completed, two buckets are selected in the planning horizon.