Alignment Assumptions: 1 Alignment cycles must be contiguous. 2 Alignment cycles cannot overlap.

3 The Current Alignment Cycle is The cycle that contains The current date. 4 The previous Alignment Cycle is The cycle that has an end date prior to The current date. 5 The future Alignment Cycle is The cycle with a start date later than The current date. 6 The alignment start are provided in the alignment files (roster, alignment/hierarchy, zip-terr). 7 The alignment cycle console can be used to label the alignments (such as "Q2 2007") or to indicate which of the alignments should be processed and made available for reporting purposes (by setting the alignment active flag to "Y"). 8 All fact data will be processed for each active alignment. That means that, potentially, all 24 months of data will be duplicated for each active alignment and aligned accordingly. 9 The same data months for each data source will be included for reporting purposes. So if we have data through June for IMS and WK but have data through July for Lash, The Lash data for July cannot be included in reports since it would skew The data. The July Lash data can still be accessed through the base fact table, but will not be included in reports. 10 DW will process data for each alignment cycle based on the address lock date for that alignment cycle (picking up alignment, customer attributes as of lock date) and employee info as of the last date of the alignment cycle. The future alignment cycle does not have a freeze date and will use the most current customer and employee attributes. 11 Cross-source reports will only display data for data months common to the sources included in the report. This will prevent the data from being skewed if one or more sources has more recent data (or more historic data?). 12 For SPP Professionals and SPP Organizations, the data month will be the maximum data month within the data file. 13 For Cephalon Drop Shipment the data month will be derived from the date appended to the filename.

Questions: 1 Will the data month for SPP Professional be older than WK/IMS data month? Why? 2 Should we think about just loading FACT_LASH_WK_SPP table and FACT_AGG_SOURCES_ZIP_MO table just for common data month backwards? 3 Is the assumption is around the IMS-WK from a previous data month within the current alignment cycle for the first month valid?

Data Month Alignment Cycle Scenario 1 Current Date Current Alignment Cycle Previous Alignment Cycle Reports Display Current/Future Alignment Cycle Reports Display What happens when March WK and IMS data is received? WK IMS Lash

January Q1 2007

February Q1 2007

March Q1 2007

April Q2 2007

May Q2 2007

June Q2 2007

July Q3 2007

August Q3 2007

September Q3 2007

October Q4 2007

November Q4 2007

December Q4 2007

4/15/2007 Q2 2007 (as determined by current date) Data thru February with Q1 2007 (the most current common data month for all sources) for cross-source reports. Latest data month reports for individual sources. Same as above but with all historic data aligned to current/future alignment. It is processed into the warehouse for each active alignment.

Scenario 2 Current Date Current Alignment Cycle Previous Alignment Cycle Reports Display Current Alignment Cycle Reports Display What happens when May WK and IMS data is received? WK IMS Lash

6/15/2007 Q2 2007 (as determined by current date) Data thru February with Q1 2007 (the most current common data month for all sources) for cross-source reports. Latest data month reports for individual sources. Same as above but with all historic data aligned to current/future alignment. It is processed into the warehouse for each active alignment.

Current date is 7/11 Current alignment cycle is Q2 2007

Defined Alignments Active Y Y

IMS data received thru June (+23 previous months) The following base facts will be created for each IMS record: Q1 2007 aligned fact (Previous) Q2 2007 alligned fact (Current)

SPP data received thru July (+23 previous months) The following base facts will be created for each SPP record: Q1 2007 aligned fact (Previous) Q2 2007 aligned fact (Current) - because Q2 2007 alignment has no end date and is therefore still the current align

Fast forward to end of July Current date is 7/30 Current alignment cycle is Q2 2007 New alignment files are received with effective date of 7/1 but are not activated. IMS data received thru June (+23 previous months) The following base facts will be created for each IMS record: Q1 2007 aligned fact (Previous) Q2 2007 alligned fact (Current)

Active Y Y N

If data were reprocessed into the warehouse, the result w

SPP data received thru July (+23 previous months) If data were reprocessed into the warehouse, the result w The following base facts will be created for each SPP record: Q1 2007 aligned fact (Previous) Q2 2007 aligned fact (Current) - because Q2 2007 alignment has no end date and is therefore still the current align

Fast forward Current date is 8/15. Q3 is set to active and becomes the current alignment cycle. Q2 is end dated.

Active N Y Y

IMS data received thru June (+23 previous months) The following base facts will be created for each IMS record: Q2 2007 aligned fact (Previous) same as before Q3 2007 aligned fact (Current) new record

If data were reprocessed into the warehouse.

SPP data received thru July (+23 previous months) If data were reprocessed into the warehouse The following base facts will be created for each SPP record: Q2 2007 aligned fact (Previous) - restated from previous DW processing because new alignment was made active Q3 2007 aligned fact (Current) - new record

Defined Alignments Start Date End Date Cycle Name 1/2/2011 4/1/2011 Q1 2007 4/2/2011 Q2 2007

nd is therefore still the current alignment

Start Date End Date 1/2/2011 4/1/2011 4/2/2011 7/2/2011

Cycle Name Q1 2007 Q2 2007 Q3 2007

sed into the warehouse, the result would be the same as above

sed into the warehouse, the result would be the same as above

nd is therefore still the current alignment

Start Date End Date 1/2/2011 4/1/2011 4/2/2011 7/1/2011 7/2/2011

Cycle Name Q1 2007 Q2 2007 Q3 2007

sed into the warehouse.

sed into the warehouse

se new alignment was made active for this period.