7 AIP Calendar Hierarchy

This chapter describes the AIP calendar hierarchy data.

AIP Calendar Data - clnd.dat or clnd.csv.dat

Table 7-1 provides information about the AIP clnd.dat file or clnd.csv.dat formats that contains AIP calendar hierarchy data.

Note: When constructing the clnd.dat file, ensure that the first day of the calendar is a Sunday. This is a requirement of the AIP-RPAS functionality.

Note: Manual creation of the calendar hierarchy should still be done in a space-separated file (clnd.dat). When the calendar hierarchy is created by the transform scripts, it will be comma separated (clnd.csv.dat).

Table 7-1 AIP Calendar Data

#	Data Entry	Description	Start	Width	Format	Example
1	DAY	Day	1	9	Dyyyymmdd	D20040104
2	DAY Label		10	120	mm/dd/yy	01/04/04
3	DOFP	Day of 4-Week Period	130	8	nn	01
4	DOFP Label		138	120	DOFP nn	DOFP 01
5	DOFN	Day of Fortnight	258	8	nn	01
6	DOFN Labe		266	120	DOFP nn	DOFN 01
7	DOW	Day of Week	386	8	Day of Week (short)	SUN
8	DOW Label		394	120	Day of Week (long)	Sunday
9	DOS	Day of Season	514	8	DOSnnn	DOS008
10	DOS Label		522	120	DOS nnn	DOS 008
11	WEEK	Week	642	8	Wnn_yyyy	W02_2004
12	WEEK Label		650	120	Week mm/dd/yy	Week 01/10/04
13	WOS	Week of Season	770	8	WOSnn	WOS02
14	WOS Label		778	120	WOS nn	WOS 02
15	WOY	Week of Year	898	8	WYnn	WY02
16	WOY Label		906	120	WOY nn	WOY 02
17	UMC1	Week Grouping - 1	1026	8	UMC1UNASSIGNED	UMC1UNAS
18	UMC1 Label		1034	120	Unassigned	Unassigned
19	MNTH	Month	1154	8	Mnn _yyyy	M01_2004
20	MNTH Label		1162	120	Mnn, FY yyyy	M01, FY 2004
21	MOY	Month of Year	1282	8	MYnn	MY01
22	MOY Label		1290	120	MOY nn	MOY 01
23	QRTR	Quarter	1410	8	Qn_yyyy	Q1_2004
24	QRTR Label		1418	120	Qn FY yyyy	Q1, FY 2004
25	YEAR	Year	1538	8	Ayyyy	A2004
26	YEAR Label		1546	120	FYyyyy	FY2004
Day of Week (short): Short form of day-of-week names (SUN, MON, TUE, WED, THR, FRI, SAT)
Day of Week (long): Long form of day-of-week names (Sunday, Monday, Tuesday, Wednesday, Thursday, Friday, Saturday)

Setting Compatible Cycles

The Day of Fortnight (DOFN) and Day of 4-week Period (DOFP) values directly relate to the order cycle values that the retailers will set up in the Data Management (DM) application. When you set up a 14- or 28-day lead time cycle, that cycle day should correspond to the AIP-RPAS DOFN and DOFP values; otherwise, the schedules shown to you in Data Management (DM) will not match the run plan and the plan days viewed in the Workbooks. To ensure the AIP-RPAS DOFN and DOFP match the Data Management (DM) cycle days, perform the following:

1. For the first day in the calendar, determine the DOFN and DOFP values by replacing the values marked by < > with an appropriate value and performing the following SQL select statement:

   MOD((TO_DATE(<FIRST CALENDAR DAY>, MM/DD/YYYY) - TO_DATE(01/02/2000, MM/DD/YYYY)), <14 FOR DOFN and 28 FOR DOFP>) +1

   For example:

   MOD((TO_DATE(04/01/2007, MM/DD/YYYY) - TO_DATE(01/02/2000, MM/DD/YYYY)), 14) +1

2. Format the cycle day (01-14 for DOFN, 01-28 for DOFP) from the SQL statement above and use it as the starting cycle day in the file.

3. Increment the DOFN value for each subsequent day to 14, then restart the count at 1. Increment the DOFP value for each subsequent day to 28, then restart the count at 1.

Notes on Manual Construction

1. The file clnd.dat must start at the beginning of a 4-5-4 fiscal year. This ensures that the day-of-week, day-of-season, and week-of-season are appropriately calculated and/or loaded.

2. AIP supports a Sunday-to-Saturday week. However, in order to enable customization, the transformation of the RMS calendar feed to clnd.csv.dat can appropriately generate the day-of-week for non-Sunday-based weeks.

   For more information, see Chapter 9, "RMS Integration and Data Mapping".

3. When manually constructing the calendar hierarchy (versus using the RMS-AIP Transformation scripts), place the clnd.dat in the $AIPDOMAIN/interface/rms/input directory.