Calendar Hierarchy File

File name: clnd.hdr.csv.dat

File format: comma-separated values file

The following table describes the fields in this file.

Name	Label	Hierarchy Type	Parent
DAY	Day	Main	None
WEEK	Week	Main	DAY
MNTH	Month	Main	WEEK
QRTR	Quarter	Main	MNTH
HALF	Half	Main	QRTR
YEAR	Year	Main	HALF
HLDY	Holiday	UDA	WEEK
EVNT	Event	UDA	WEEK
WOYR	Week of Year	Alternate	WEEK
STDB	STD/BTA	UDA	WEEK

Example:

day,day_label,week,week_label,mnth,mnth_label,qrtr,qrtr_label,half,half_label,year,year_label,hldy,hldy_label,evnt,evnt_label,woyr,woyr_label,stdb,stdb_label
20170129,1/29/2017,w01_2017,2/4/2017,m01_2017,Feb FY2017,q01_2017,Quarter1 FY2017,h1_2017,Half1 FY2017,a2017,FY2017,0,None,0,None,1,Week 01,0,0
20170130,1/30/2017,w01_2017,2/4/2017,m01_2017,Feb FY2017,q01_2017,Quarter1 FY2017,h1_2017,Half1 FY2017,a2017,FY2017,0,None,0,None,1,Week 01,0,0
20170131,1/31/2017,w01_2017,2/4/2017,m01_2017,Feb FY2017,q01_2017,Quarter1 FY2017,h1_2017,Half1 FY2017,a2017,FY2017,0,None,0,None,1,Week 01,0,0
20170201,2/1/2017,w01_2017,2/4/2017,m01_2017,Feb FY2017,q01_2017,Quarter1 FY2017,h1_2017,Half1 FY2017,a2017,FY2017,0,None,0,None,1,Week 01,0,0

Note:

Though RPASCE supports a string for position IDs, for calendar position week, it is preferred to use the date format YYYYMMDD. If the customer uses RAP integration to get the data, the day and week position IDs at which the data needs to be stored are in YYYYMMDD format.

Note:

For non-template customers, it is also recommended to align with the GA Calendar Hierarchy structure for the dimension names for day, week, mnth, qrtr, half, and year so that they can upgrade/implement other GA solutions in a multi-app environment. They can use different labels. The lowest dimension should be day and it is mandatory. The rest of the dimensions are optional and their equivalents should be named accordingly.