Data Warehousing Reference Guide Warehousing – Reference Guide ... Quick Start on Running an Existing Report

Confidential Property of Celerant Technology Page 1 of 93

Data Warehousing

Reference Guide

Data Warehousing – Reference Guide


Data Warehousing TABLE OF CONTENTS

Introduction ............................................................................................................................................. 4

What is Data Warehousing? ................................................................................................................... 4 What can Data Warehousing Do? ........................................................................................................... 4

Benefits ........................................................................................................................................... 4

What are Data Warehousing Hurdles? .................................................................................................... 5 Trade-Offs ....................................................................................................................................... 5

Suggestions .......................................................................................................................................... 5 Users Available ..................................................................................................................................... 6

How Data is Updated with Celerant Command ........................................................................................ 6 Understanding the Terminology ............................................................................................................. 6

Getting Started ........................................................................................................................................ 8

Connection Information ......................................................................................................................... 8 Logging In ............................................................................................................................................ 8

Data Warehousing Project Home Screen ................................................................................................ 9 Quick Start on Running an Existing Report............................................................................................ 11

Quick Start on Selecting Report Prompts .............................................................................................. 13

Quick Start on Creating Reports ........................................................................................................... 14 Adding Attributes ........................................................................................................................... 16

Adding Metrics ............................................................................................................................... 16 Adding a Filter ............................................................................................................................... 18

Adding a Prompt ............................................................................................................................ 19 Saving and/or Running a Report ..................................................................................................... 20

Preferences Within MicroStrategy Data Warehousing............................................................................. 23

Understanding Your Data ...................................................................................................................... 24 Understanding Attribute/Metric Compatibiliity Grid ................................................................................ 24

Attribute Folders ............................................................................................................................ 24 Metric Folders ................................................................................................................................ 24

Inventory Store vs. Sales Store ............................................................................................................ 26

Style vs. Product Attributes .................................................................................................................. 26 Using Dates Within Data Warehousing ................................................................................................. 28

Combining Metrics with Date Types in Data Warehousing ...................................................................... 30 Simple Metrics Classification ........................................................................................................... 30

Daily Inventory Metrics Classification .............................................................................................. 31 Weekly Inventory Metrics Classification ........................................................................................... 31

Sales Period To Date Metrics Classification ...................................................................................... 32

Sales Prior Period Metrics Classification ........................................................................................... 32 Combining Metric Types ................................................................................................................. 32

Inventory Transaction Metric Types ................................................................................................ 33 Understanding the Hierarchies of Data ................................................................................................. 34

Reporting ............................................................................................................................................... 36

Adding a Fiscal Day Range Prompt ....................................................................................................... 36 Editing an Existing Report in Design Mode ............................................................................................ 38

Editing an Existing Report in Display Mode ........................................................................................... 41 Add an Attribute/Metric .................................................................................................................. 42

Add a View Filter ........................................................................................................................... 42

Defining a Page-By ........................................................................................................................ 43 Adding Totals and Sub-Totals ......................................................................................................... 43

Sorting Data .................................................................................................................................. 44 Add a Calculated Metric .................................................................................................................. 44

Changing the Attribute Form Display ............................................................................................... 45 Rename an Attribute/Metric Header Name....................................................................................... 46

Pivoting an Attribute/Metric ............................................................................................................ 47



Drilling Down ................................................................................................................................. 48

Exporting to Excel .......................................................................................................................... 48 Displaying a Graph ......................................................................................................................... 49

General Formatting ........................................................................................................................ 50 Emailing Reports ................................................................................................................................. 50

Advanced Topics .................................................................................................................................... 52

Scheduling Reports ............................................................................................................................. 52 Report List Scheduling ................................................................................................................... 52

Display Screen Scheduling .............................................................................................................. 53 Creating Documents ............................................................................................................................ 55

Thresholds Within Data Warehousing ................................................................................................... 59 Creating a Top XX Report .................................................................................................................... 62

Creating an “OR” Filter ........................................................................................................................ 63

Removing Unnecessary Objects ........................................................................................................... 65 Filtering on Fiscal Month vs. Fiscal Month of Year .................................................................................. 65

Beginning and Ending Inventory .......................................................................................................... 66 Filtering on Metrics .............................................................................................................................. 66

Setting Up a Difference Column ........................................................................................................... 69

Creating Custom Groups for Time Periods ............................................................................................ 70 Creating Custom Groups for Stores ...................................................................................................... 75

Appendix A ............................................................................................................................................. 80 Attribute Definitions ............................................................................................................................ 80

Metric Definitions ................................................................................................................................ 85 Production Reports .............................................................................................................................. 89

Appendix B ............................................................................................................................................. 90

MicroStategy Data Warehousing User License Chart .............................................................................. 90 Appendix C ............................................................................................................................................. 93

MicroStategy Data Warehousing Drilling Hierarchies .............................................................................. 93



INTRODUCTION:

WHAT IS DATA WAREHOUSING?

Data Warehousing is a process that reviews and analyzes the volumes of raw data in a data warehouse, and

extracts or “mines” information from that info to create viewable, usable analytic reports. In addition, a Data

Warehouse is a secure server where data is centralized and held for data warehousing in which case the main

purpose of Data Warehousing is to provide the end-user with aggregated, analyzable data intended for making

management and strategic decisions. This reporting tool is different from the reports designed under Celerant

Command in that reports generated through the front-end are for operational purposes which is intended to allow

users to view and process specific transactions, and do not provide the same level of analytical data as Data

Warehousing.

Data that is stored in a relational database can be sorted, categorized, analyzed and summarized to user specifications for

a report or document. This information can include operational data (such as sales, inventory or accounting info) and

meta data (data that is about the contained data, such as definitions, database structure or design). Generating analytical

reports through Data Warehousing requires the industry-standard product provided by MicroStrategy in order for the user

to enhance the reporting functionality.

WHAT CAN DATA WAREHOUSING DO?

Data Warehousing reports can categorize and summarize data from a variety of levels and perspectives, and

generate various views of that information to highlight trends and patterns. This helps the view to make

stronger, more informed decisions on ways to improve sales, profit margin and performance.

Data Warehousing allows the analysis of info to determine and highlight relationships between data – whether store

location, customer or demographic info, sales $ or units, inventory info, or date/date range. It creates powerful reports

to improve retail performance from a better understanding of buying patterns, sales and inventory movement, geographic

location. These reports can be created to run a high-level analytics, and also allow the user the “drill down” on a

specific summarization to see the detail below it.

Depending on your preference, reports can be returned in a variety of formats, from spreadsheet-like layouts to graphs.

Benefits:

Customization – The most important benefit of Data Warehousing is the ability to customize specific reports

including the ability to filter data based off various filtering methods, and formatting data in a way that

relates to your specific business, all within user-friendly software.

Drilling Down – The user has the ability to review data at a summarized level such as Department; however,

if more detail is required the user can easily drill down further, such as a Type and all the way down to the

product level if needed without having to run multiple reports.

Graphing – Data Warehousing offers the ability to generate different types of graphs based off the report

generated ranging from pie graphs, line charts, and bar graphs to name a few.

Dashboards – The ability to display multiple reports on one screen in a dashboard display is available for

customization as needed. This includes the ability to have a report display along with the associated graph if

needed.

Reporting through the Web – Data Warehousing offers the ability to generate reports through the web as

long as there is connection to the report server such as a secure VPN and does not require Celerant

Command to be loaded on the device generating the report.



WHAT ARE DATA WAREHOUSING HURDLES?

Given the vast amount of data and hundreds of different options and configurations that can be created, it can be

time-consuming and quite frustrating to learn how to best to harness your information into constructive reports

that are in useful, manageable and readable formats.

The same data can be reconfigured in hundreds of ways, depending on how a report is put together – and then

that report can be even further manipulated into a new format with new data.

It will take some time to become familiar with the Data Warehousing software, the variables that are available, how they

interact with the data, and how best to create an informative and useful report. You need to think about both the data

you are sourcing and the format in which you would like the data to appear.

Trade-Offs:

Hardware – In order to fully utilize Data Warehousing a “Report Server” is required in order to house the data

from Celerant Command on a server other than the “Production” server due to PCI Standards. In addition,

processing data warehousing reports on the same server as the “Production” server will directly affect the

performance of the production server if one server is housing both functions.

Uploading Data – Using Data Warehousing requires the data from the production server to be uploaded on a

nightly basis. Therefore, the data is not real time if trying to compare data from reports generated through

the Front-End.

SUGGESTIONS:

Be patient! When a new report is designed, or an existing report is manipulated, save the report with a

different name so that the changes are not lost as you work through the design process. If a report doesn’t

work and comes back with “no data available,” double-check the structure and parameters selected to see if

the report request is valid with the information you have in the data warehouse.

It will take time and some trial-and-error work to see what reports work best for you and your business;

however, once the report is saved additional modifications will be simple.

Sketch out a framework of the report you want to construct, along with the fields of info and where you want to place

them. Having a visual may be helpful in crafting all the elements of the report.

Look to the Shared Folder called Production Reports; these are pre-built reports that can be the base for

learning about data Warehousing, to become familiar with report structure and what elements are needed, and get a

better understanding about how data and structure work together to create reports. If a Production Report gives 80% of

what you need, save a copy of the report with a different name for a base, and begin manipulating it as needed.

Utilize the MicroStrategy Help Tool offered by selecting “Help” when logged into Data Warehousing for more information.



USERS AVAILABLE:

Data Warehouse licensing allows for multiple types of users, with different levels of access to the reports. Please contact your salesperson for pricing on additional users. The types of users available are as follows:

Consumer User – This type of user will allow the ability to run existing reports, print, drill using pre-defined

hierarchies, sort, choose grid or graph format, schedule or immediately send reports via email or to a file server

or a printer. This is typically associated with users that will simply run reports based off prompts and filters that

have already been established on the report where no advanced formatting is required. Please see Appendix B for additional information.

Analyst User – This type of user will allow the same features as the Consumer User, however, the addition of

drilling anywhere outside the pre-defined hierarchies, edit totals, pivot reports, hide or unhide fields from a report, create derived metrics, and create limited ad hoc queries through the Report Builder. This is typically

reserved for more advanced users that may be required to generate reports with advanced formatting such as moving fields on a report, hiding fields from the report, or drilling down across different Attribute types. Please

see Appendix B for additional information.

Power User – This type of user will allow the same features as the Consumer User and Analyst User, along with

additional advanced features such as designing scorecards, dashboards, and operational reports in design mode. These users also have the ability to create documents, add or remove all available objects from a report, and are

typically reserved for the users that are involved in developing or customizing reports for the end users. Please see Appendix B for additional information.

HOW DATA IS UPDATED WITH CELERANT COMMAND:

Celerant WorkstationLocal App Server

Production Server Report Server

Data Communicates Scheduled Upload Populate Data

MicroStrategyReports

When using Data Warehousing, the standard configuration of updating the Local App Server, then communicating with

the Production Server will not change. In order to utilize Data Warehousing, the data from the Production Server will be

scheduled to upload on a nightly basis to the Report Server in which case the end-users will be able to generate the desired reports through Data Warehousing. There is some flexibility to the schedule, however, by default Celerant

Technology Corp will define a scheduled start time of around 12:30am.

What does this mean? The data populated in Data Warehousing will not be in real time, but instead will be as of the end of the previous day’s business. For example, if a report is run that contains a Month-to-Date (MTD) figure, this figure will be MTD as of the last

time the data was uploaded. Therefore, since the Report Server was updated overnight, the MTD figures will be as of yesterday at the end of business. This has been taken into consideration when dealing with Last Year (LY) figures in that

if a comparative report for This Year To Date and Last Year To Date is needed, both figures will be as of the end of business the day before.

UNDERSTANDING THE TERMINOLOGY:

Attributes – Attributes are types of categories in which case the data can be broken down by. This tends to be

non-quantitative data which consists of data such as dates, inventory brands, departments, etc. Attributes are

data that can be rolled up for summaries or drilled down upon for detail, but is not actual numbers that

calculations can be generated from.

Metrics – Metrics are types of quantitative data that provide such data as sales dollars, prices, costs, quantities,

etc. Metrics are what will be used when totaling various figures and can be used in generating a new calculated column on a report. Therefore, metrics consist of the numbers found within the database which can be filtered by

the associated attributes that make up the numbers.



Prompts – Prompts are user-defined filters based off the available data in which case when the report is ran, the

user will be prompted for specific data. The benefit of the Prompt is that each time the report is ran, the user will

have the option to change the filter and run a report for the data that is desired at that time. Therefore, if a report is desired for different Brands depending on what data is needed at a particular time, a Prompt on the

Brand attribute may be the best solution when designing the report. Filters – Filters are similar to Prompts in that the system is filtering on the defined data, however, Filters will not

be prompted each time the report is ran. Instead, a Filter will automatically narrow the data down based off how

the Filter was defined every time the report is run. Therefore, if a report is desired for one specific Brand no

matter when it’s ran, a Filter on that particular Brand may be the best solution when designing the report.

Hierarchies – Hierarchies are the paths defined in Data Warehousing in which case the user can drill down on

specific attributes. Hierarchies will be described in further detail under the Understanding Your Data section below.

Documents – Documents are also known as Dashboards in which case a user can define multiple reports to one

document for easy reference. This would be useful when trying to review data that is not directly related and cannot be displayed in one report; however, the user would like to see different data on one screen.

Fiscal Dates – When utilizing Data Warehousing with regards to Celerant Command data, the dates in which

case an attribute can be run will be based off the Fiscal Calendar setup within Celerant’s Front-End under Settings > Options > Fiscal Calendar. The Fiscal Dates will be described in further detail under the Understanding Your Data section of this guide. If the Fiscal Calendar is not setup, this will cause inaccurate dates when utilizing the

PO Dates attributes. For example, a “Cancel Date” is defined on a PO as 1/31/13, and the user is generating a

report through Data Warehousing that contains the “Cancel Date” attribute. If the Fiscal Calendar is not defined for 2013, the report will display a date of 1/1/1900 instead of what was defined through the Front-End due to not

being accurately defined in Data Warehousing. Celerant Technology recommends the Fiscal Calendar be defined for any historical year where sales or purchase data is required, as well as, at least one year in the future in order

to prevent this confusion. In addition, if there is a change to the Fiscal Calendar or creation of a new Fiscal

Calendar through Celerant Command’s front-end, Celerant Support will need to be notified in order to update the data within Data Warehousing.



GETTING STARTED:

CONNECTION INFORMATION:

Once MicroStrategy is installed on the Report Server and Data Warehousing is configured, Celerant Technology Corp. will provide the connection information (Web address) including the User Name and Password in order to log into Data

Warehousing.

WEB ADDRESS: ___________________________________________________________

USER NAME: ___________________________________________________________

PASSWORD: ___________________________________________________________

LOGGING IN:

Launce a Web Browser (Firefox, Internet Explorer), and enter the Web Address provided by Celerant Technology Corp. as

shown below.

NOTE: Data Warehousing can be accessed remotely, as long as the user has connection to the network that is housing

the Report Server. Therefore, this may require the appropriate security access such as VPN connection in order to access and run reports remotely.

The next window will bring up folders of your available data warehousing projects:

Click on the Data Warehousing Projects folder for your Company, and enter your User Name and Password when

prompted.



Depending on the level of access that employees are assigned which are described above under the Users Available

section, employees may be restricted from certain functions

DATA WAREHOUSING PROJECT HOME SCREEN:

Once logged in, the Data Warehousing Project Home Screen will open with various options which the commonly used

selections are described below:



Selecting Shared Reports will open the list of

Shared Directories defined within Data Warehousing.

Within the Shared Reports, users can save new

reports under specific directories, or use the standard

reports provided by Celerant Technology Corp which

are described in further detail under the Appendix A

section.

When a report is generated, the

user has the option to add the report to the

History List for easy reference, or if a report

was generated based off a defined

schedule, can review the report without

requiring Data Warehousing re-populate the

values. Selecting History List will open the

list of these reports which can be reviewed or managed accordingly.

Selecting My Reports will open the

list of reports the particular employee has

saved under their Username/Password.

These reports will not be available for

others unless they are saved under the

Shared Reports as well.

Selecting My Subscriptions will open the list of

reports that are assigned to specific subscriptions such

as History List Subscriptions or Email Subscriptions

(depending on your user licensing). From this screen,

the user can unsubscribe specific reports, edit the

reports, or review the reports as needed.



Selecting Create Report will

allow the user to design a customized

report based off the available

Attributes, Metrics, defined Prompts,

and Filters.

Other navigational options available include:

Star: Returns you to the Main Menu screen.

Home: Returns you to the Main Menu screen.

Arrows: Moves Back to screen previously viewed screen, or Forward to the previously viewed screen.

Folder: Moves to the folder prior (or above) to the current session.

QUICK START ON RUNNING AN EXISTING REPORT:

To begin, click on Shared Reports using either the Menu Bar or the View Button shown below.

Once the Shared Reports Directory is opened, the default folder or Production Reports should be listed. Double-click the

folder in order to display the sub-folders of the available reports Celerant Technology Corp has designed and loaded on

the Data Warehousing Server.



Each sub-directory listed will offer different reports based of the data the user is requesting. Definitions and examples of

each production report offered can be found under Appendix A below. Once the desired sub-directory is selected, the list

of available reports will be listed. In order to run the desired report to the screen, the user can either select the Name of

the report or right-click on the Name and select Run . . . .

In addition, if the user would like the desired report to run oustide of the Web browser (PDF, Excel, etc.), the user can

select one of the following options listed under the Actions column.

Note: If you are not sure the selected report is the correct report, you can generate the

report on the screen through the Web browser, in which case once you determine this is



the desried report, you can run it outside of the Web browser and use the same options as the Actions column.

Depending on if the report selected has Prompts assigned, the user may be presented the Prompt screen, otherwise the

report will generate through the Web browser as shown below.

QUICK START ON SELECTING REPORT PROMPTS:

If a report that is selected is defined with Prompts, the user will have the option to select specific data in order to narrow

down the results displayed on the report. Prompts and Filters are very important features with Data Warehousing, since

there is the potential to have thousands of records, and Data Warehousing is limited to 32,000 records before erroring

out. Therefore, Prompts and Filters will allow you to zero in on areas that analysis is required without getting a lot of

unnecessary data. Below is an example of a Prompt Screen that may appear when generating a report.

Index – This will

list the prompts

assigned to the

report.

Available – This

will list the

available elements

for selection

within the prompt

(Example:

Department).

Selected – This

will list the

elements

selectioned that

will be used to

generate the report.



Options:

Allows the user to manually type the desired selection from the list of available

options within the prompt.

Single Arrows – Moves the selected option from the Available side to the Selected side or visversa.

Double Arrows – Moves all options from the Available side to the Selected side or visversa.

Some Prompts will have more elements available than will display in the

Available field. If this is the case, the user has the ability to scroll through the

elements to display more options.

Once the prompts are completed, select the Run Report button in order to generate the report. Note: Since there

is the potential to have thousands of records Data Warehousing is limited to 32,000 records before erroring out.

Please keep this in mind when making selections during the prompting process.

QUICK START ON CREATING REPORTS:

To begin, creating a new report can be performed through various options depending on the screen you are in. Click on

one of the following options.

From the Menu Bar

From the Data Warehousing Projects Home Screen

From the Shared Documents or My Documents Directories

This will open the Create Report screen. Click on in order to open the Design Mod: Blank Report screen.



This is your working screen to create a new report; you will select elements from the left hand column options, and drag

them onto the grid:

For a simple report, begin by selecting report elements from Attributes and Metrics folders in the Objects Browser column

on the left-hand side of the screen. Click on the folder to expand the contents into a drop-down format for additional

options. Highlight to select your report options, and drag them onto the report format grid. As a general rule, every

report should have at least one attribute and at least one metric that relate to one another. There is the ability to have



multiple types of attributes; however, each attribute must have a relationship to the metrics being used. For example,

sales metrics do not have a relationship with Purchase Order attributes, and trying to generate a report with this

combination would cause the report to error out. Please refer to the Attribute/Metric Compatibility Matrix chart found

under the Understanding Your Data section of this guide.

Adding Attributes

Expanding the Attributes folder found within the Objects Browser will provide a list of sub-folders in which case

individual attributes are classified. The list of available attributes along with definitions can be found under Appendix A

below. Once the desired attribute is found, click on the attribute and drag it to the design portion of the screen. Repeat

this step for all other desired attributes.

Example: Create a report with the Department and Brand as the attributes.

Adding Metrics

Similar to the Attributes folder, expanding the Metrics folder found within the Objects Browser will provide a list of sub-

folders in which case individual metrics are classified. The list of available metrics along with definitions can be found



under Appendix A below. Once the desired metric is found, click on the metric and drag it to the design portion of the

screen. Repeat this step for all other desired metrics.

Example: Add the metrics to the Department and Brand attributes for Sales – Retail and Sales – COGS.

Once the attributes and metrics are added to the report in the Design Mode, you can click and drag the different objects

in order modify where each field will display when the report is generated.



If an attribute or metric is added to the report that is not necessary, you can right-click on the specific object and

remove it from the report or remove it from the grid.

Remove from Grid – This option should be used if the metric or attribute should not display on the grid, but

still needs to be included on the report. This would be for incidents when the user added a new metric in

which case it is a calculation of two or more other pre-defined metrics. The user may not want to see the

individual fields on the report, but if the fields are not on the report the calculation will not be accurate.

Remove from Report – This option should be used if there is an attribute or metric that is not needed on the

report since it is not part of a calculation or needs to display on the report.

Adding a Filter

In order to prevent Data Warehousing from returning an error due to exceeding the 32,000 records available, filtering

can be used to narrow the reports output. Filtering can performed on attributes or metrics, but will not prompt the user

each time the report is generated. Once the object is determined that requires filtering, right-click on the object and

select Add to Filter.

Once the filter is added to the report, you can either define a qualitative filter (Equals to, Less than, Greater than, etc.),

or a selective filter based off what is available under the selected field.

Example: For the report created with Department, Brand, Sales, and COGS, a time period is needed. Selecting

the attribute under the Fiscal Transaction Date of “Month Ago” will filter the report based of how many months



ago to include sales and COGS. In order to generate the report for the current month, the Month Ago can be set

to “0” in which case every time this report is ran; the sales and COGS will be as of the current month. If the

Month Ago filter is set to “1”, then every time this report is run, the sales and COGS will be as of one month ago.

In this example, the filter is changed to a Selective filter in which case “0” is the selected filter. Once the filter is

defined, select the sign to apply the filter. If a filter needs to be removed, select the sign instead.

Once the filter is applied, the view will adjust accordingly in order to list how exactly the data is being filtered.

NOTE: It is very important that filters or prompts are used in order to prevent Data Warehousing from returning an error

due to exceeding the 32,000 records that can be used to populate the reports.

If additional filters are required, find the desired element and repeat the above steps of adding a filter.

Adding a Prompt

In addition to a filter, the user can add a prompt which will prompt the user for a selection each time the report is ran.

This feature is beneficial if the same report will be run for different data every time the report is generated instead of

the same data when the report is generated. Once the object is determined that requires a prompt, right-click on the

object and select Add Qualification Prompt To Filter or Add Element Prompt To Filter.

Add Qualification Prompt to Filter - A qualification prompt is the ability to manually type a value when prompted

based off the object that is being prompted. Typically qualification prompts will be utilized when the user needs

to define a range of data, either numerical or descriptive values. For example, if the attribute being prompted is

a number value such as zip codes, the qualification prompt will allow the user to select a range. If the attribute

being prompted is a description such as a promotion, the user may use the “Begins With” or “Ends With”

qualification prompt to filter the appropriate data.



Add Element Prompt To Filter – An element prompt is the ability to select one or more values that are available

under the defined object. This would typically be used for attributes in which case the data is already defined

with specific elements.

Once the prompt is added to the report, the Report Filter section will include the information regarding the prompt that

is added.

Example: For the report created with Department, Brand, Sales, and COGS, for the time period of 0 Months Ago,

the user may want to only display certain Departments when this report is ran. By adding the Department as a

prompt, each time the report is generated, the user will be able to select the desired departments which will

filter out unnecessary data.

Saving and/or Running a Report

Once the report design is complete, it is highly recommended that you save the report before running the report in

order to avoid losing the current work if there would be some sort of problem when generating the report. If the report

is already saved or saving is not necessary, but is being accessed through the design screen, click on in order to run

the report without having to save the report.

In order to save a report, click on the sign on the menu bar which will open the Save As… window. If there are

prompts associated with the report, you can pre-define the prompts or simply click on Save on the bottom of the screen.

Once the Save As screen is displayed, select the location in which the report should be saved and enter the desired

name associated with the report.

NOTE: Under the “Advanced Options” section of the Save As screen, there is a prompt labeled “Set the current prompt

answers to be the default prompt answers”. If this is enabled/checked, the prompt answers defined on the previous

screen will be defaulted, while disabling/unchecking this flag will prompt the user with no default selections.

Once the saving information is completed, select “OK” in order to save the report.



Once the report is saved, the user will be prompted to run the newly saved report.

If the report contains a prompt, select the desired elements of the prompt from the list of Available selection in order to

move them to the Selected section. Once the prompts are completed, click on Run Report.



After processing, Data Warehousing will then display the desired report in which case advanced formatting can be

performed, modifying of the report can be performed, or printing or exporting of the report can be performed.



PREFERENCES WITHIN MICROSTRATEGY DATA WAREHOUSING:

Preferences within MicroStrategy can be based off a user/password level and vary from report formatting defaults to how

Data Warehousing is presented when designing and displaying reports. It is recommended that only advanced users with

proper security access modify the defaulted preferences. For more information on how the preferences affect Data

Warehousing, please uutilize the MicroStrategy Help Tools offered by selecting when logged into Data Warehousing

for more information.

To begin reviewing the preferences, click on either the Menu Bar link or the Tools Button shown below.



UNDERSTANDING YOUR DATA:

UNDERSTANDING ATTRIBUTE/METRIC COMPATIBILITY GRID:

Celerant Technology Corp has provided specific data from the production database and populated the associated tables

within MicroStrategy’s Data Warehousing in order to generate customizable analytical reports. Once the data is populated

under MicroStrategy’s Data Warehousing, the various Attributes and various Metrics will be grouped into folders of similar

types for easy of finding and utilizing each object. For example, in the Attribute/Metric Compatibility Grid below, the

Attributes column is a list of the folders available when searching for the desired attribute while the list of Metric Folders

are listed across the top row (Sales Metrics, Inventory Metrics, Purchase Order Metrics).

Due to how Data Warehousing functions, a relationship between the desired attributes and the desired metrics must be

present, otherwise Data Warehousing will return an error if a relationship cannot be determined. Therefore, the

Attribute/Metric Compatibility Grid below was designed in order to give a clear understanding of how the relationships

between the various attributes and metrics can be used to produce the desired outcome.

Attribute Folders:

o Buyer – This folder will provide the Buyer’s information assigned to a Purchase Order.

o Customer – This folder will provide the Customer’s information which can be used for analyzing sales.

o Fiscal Transaction Date – This folder will provide the various Fiscal Time Periods that are tied to each

transaction and is described in further detail below.

o Inventory Store – This folder will provide the Store’s information for the store that was affected with

the movement of inventory.

o Product – This folder will provide the Inventory’s data such as Style, Department, etc.

o Promotion – This folder will provide the Promotional data associated with sales data.

o Purchase Order – This folder will provide the Purchase Order data such as Order Date, Cancel Date,

Received Date, etc.

o Sales Markdown Percent – This folder will provide the Markdown data associated with sales that fall

within 5%, 10%, or the exact percent.

o Sales Person – This folder will provide the Salesperson data associated with sales data.

o Sales Store – This folder will provide the Store’s information for the store that was recorded as the

selling store.

o Sales Time of Day – This folder will provide the Time of Day selections associated with sales.

o Transaction Type – This folder will provide the type of transaction that was used during the inventory

transactions.

o Vendor – This folder will provide the Vendor information associated with the purchase order data.

Metric Folders:

o Sales Metrics – This folder will provide the sales metrics for a defined time period and does not include

calculated metrics that use beginning or ending values.

o Daily Inventory – This folder will provide the daily inventory values as of the beginning of the business

day.

o Weekly Inventory – This folder will provide the weekly (or period if Fiscal Month, Quarter, or Year is

filtered) values that include beginning values, ending values, or calculated values that utilize beginning or

ending values. Note: These metrics can only be used when a Fiscal Week or higher is selected as a time

period.

o Inventory Transactions – This folder will provide the type of transactions that took place that affect

Inventory.

o Purchase Order – This folder will provide the Purchase Order data for the associated purchase order

attributes.



Attribute / Metric Compatibility Grid

Attributes Sales

Metrics

Inventory Metrics Purchase Order

Metrics Daily Inventory Weekly Inventory Inventory Transactions

Buyer - - - - YES

Customer YES - - - -

Fiscal Transaction Date YES YES

YES (Week and Higher Level Attributes) YES YES

Inventory Store YES YES YES YES YES

Product YES YES YES YES YES

Promotion YES - - - -

Purchase Order - - - - YES

Sales Markdown Percent YES - - - -

Sales Person YES - - - -

Sales Store YES - - - -

Sales Time of Day YES - - - -

Transaction Type - - - YES -

Vendor - - - - YES

Example:

Buyer and Vendor Attributes can only be used with Purchase Order Metrics and cannot be used on Sales or

Inventory Metrics.

Promotion Attributes can only be used with Sales Metrics and cannot be used on Inventory or Purchase Order

Metrics.

Fiscal Transaction Dates Attributes can be used for all Metrics (Sales, Inventory, and Purchase Order).

If an Attribute is selected with a Metric that does not have a relationship, the report can either error out, or the data that

is returned will be inaccurate due do the system not knowing how to handle the relationships.



INVENTORY STORE VS. SALES STORE:

Within the list of Attributes, there are two sub-folders for Inventory Store and Sales Store that appear to have the same

objects, but may provide varying data due to what information is desired.

Inventory Store – The Inventory Store will represent the

store the item’s quantity was adjusted from, which may not always

be the same as the sales store. For example, if a web store is

defined as Store 10 but pulls the merchandise from the

warehouse, Store 99, then the Inventory Store would be recorded

as Store 99 since that is where the quantity is being adjusted

under.

Sales Store – The Inventory Store will represent the

store the item was sold through which may not be the same as the

store that adjusted the quantity. This is typically used when

processing web stores in which case the inventory is being fulfilled

through another store, but the sales should be recorded under

another store. For example, if a web store is defined as Store 10

but pulls the merchandise from the warehouse, Store 99, then the

Sales Store would be recorded as Store 10 since that is where the

sales were generated.

STYLE VS. PRODUCT ATTRIBUTES:

Within the list of Attributes, there is a sub-folder labeled Product which represents the various attributes for the Inventory

Item. From this folder, the user has the ability to select Product of if they select Next 30 item(s)… can select Style in

order to add the attribute to the report. The following is the difference between Product and Style:



Product – The Product attribute will display the item on a Sku level

instead of the Style level, meaning even if the user does not have Attr1(color)

or Size included on the report, the item could display multiple times since

there may be multiple Sku's. This may be confusing when trying to retrieve a

report on the Style level as opposed to the product level. By default, the

Product will display the Style, but the user can right-click on the attribute

during the Display screen and select Attribute Forms in order to change the

way the Product is displayed by using the Sku instead of the Style. This is

shown below under the Changing the Attribute Form Display section of this

manual.

Style – The Style attribute is basically a roll up of the Products in

which case the Style will only display once. This attribute would be the

ideal attribute if the report desired only needs to be at a style level

instead of a product/sku level.



USING DATES WITHIN DATA WAREHOUSING:

Data Warehousing works off your company’s Fiscal Calendar, whether set up in a 4-4-5- or 4-4-5 calendar format. From

there, the system will break down those months into specific weeks, which can better reflect the data. The Fiscal Month

in Data Warehousing refers to a specific fiscal month in a specific fiscal year - for example: 201107 relates to fiscal year

2011, in fiscal month 7.

The dates available within Data Warehousing are referred to as Fiscal Dates, which is based off the Fiscal Calendar

defined through Celerant Command’s front-end under Settings > Options > Fiscal Calendar. Therefore, the majority of

the date selections are going to be based off the Fiscal Calendar as opposed to a Gregorian calendar. However, the ability

to select a specific date range for certain metrics is available by using a Fiscal Date Range prompt as described under the

Reporting section of this guide.

The main time hierarchy is: Fiscal Year Fiscal Quarter Fiscal Month Fiscal Week Fiscal Day

All of the date attributes are based on the client’s fiscal calendar as defined in TB_FISCAL_CAL.

Day/Week/Month/Quarter/Year Ago – The “Ago” attributes

will provide metric data based off a specified number of

days/weeks/months/quarters/years ago which is based off the

Fiscal Calendar. For example, if Year Ago is set to “0”, the metrics

data would display for the current year. If the Year Ago is set to

“1”, the metric data would display for one year ago instead of the

current year.

Fiscal Day – The Fiscal Day will allow the user to filter or prompt

for metric data for a particular date, or group of dates if needed.

This is not the same as a Fiscal Date Range selection, but allows

selection of exact dates. Example: Jan 2011 Sat: 1/1/11.

Fiscal Day of Week – The Fiscal Day of Week would be used to

filter or prompt for specific days of the week such as Monday,

Tuesday, Wednesday, etc. and would not be actual calendar dates.

Fiscal Month – The Fiscal Month would be used to filter or

prompt for specific Fiscal Months based off the Fiscal Calendar.

This would display with the associated Fiscal Year as well since

each year has Fiscal Months 1-12. Example: 2011 FM1: 12/27/10.

Fiscal Month of Year – Similar to the Fiscal Day of Week, the Fiscal Month of Year would be used to filter or

prompt for specific months of a year such as FM1, FM2, FM3, etc.

Fiscal Quarter – The Fiscal Quarter would be used to filter or prompt for specified Fiscal Quarters within a

specific year. This would be similar to the Fiscal Month. Example: 2011 FQ1:12/27/10.

Fiscal Week – Similar to Fiscal Month or Fiscal Quarter, the Fiscal Week would be used to filter or prompt for a

specific Fiscal Week based off the Fiscal Calendar. This would display with the associated Fiscal Year since each

year has Fiscal Weeks 1-52. Example: 2011 FW7: 2/7/11

Fiscal Week of Year – Similar to the Fiscal Day of Week or Fiscal Month of Year, the Fiscal Week of Year would

be used to filter or prompt for specific weeks of a year such as FW1, FW2, FW3 . . . . FW52.

Fiscal Year – The Fiscal Year would be used to filter or prompt on a specific Year with a specific starting date

based off the Fiscal Calendar. Example: 2011:12/27/10.

When utilizing Fiscal Date selections as filters, prompts, or report columns/rows, Fiscal Transaction Dates may need to be

run for multiple elements. For example, if the metrics required need to be reported on based off the Fiscal Day of Week,



you may want to include an additional filter/prompt for the desired Fiscal Months or Fiscal Year so that the data returned

is not displaying since the beginning of time on each item. In addition, the same data can be obtained depending on the

Fiscal Transaction Date used within the report. For example, Month Ago = “0” will provide the same data as if the Fiscal

Month for the current month was selected as a filter.

NOTE: Weekly Inventory Metrics will only be accurate for period attributes of Fiscal Weeks or higher (Fiscal Month, Fiscal

Quarter, Fiscal Year), and will not be accurate for Fiscal Day attributes.

Special Attributes

Filter Attributes Core Attributes

Fiscal Year

ExampleID: 2011

Displays: 2011 4/4/2011

Fiscal Quarter

ExampleID: 20112

Displays: 2011 FQ2 7/4/2011

Fiscal Month

ExampleID: 201106

Displays: 2011 FM6 8/29/2011

Fiscal Week

ExampleID: 201123

Displays: 2011 FW23 9/5/2011

23

Fiscal Day

ExampleID: 9/6/2011

Displays: 06 Sep 2011 TUE

Year Ago

Quarter Ago

Month Ago

Week Ago

Day Ago Fiscal Day of Week

Fiscal Month of Year

Fiscal Week of Year

Celerant Data WarehouseFiscal Date Attributes

These are integer attributes that are always relative to the current date. Day Ago = 0 is today, Day Ago = 1 is yesterday, Year Ago = 0 is current fiscal year, etc.

Their primary usage is in report filters to make sure a report is always as of the desired period

These are the main date-based attributes. They are based on the fiscal calendar as defined in TB_FISCAL_CAL. The lower level attributes incorporate the upper level attributes. In other words, the Fiscal Quarter attribute is not a generic Q2, but Q2 of a specific year.

They are used in the report grid to display specific periods.

These are date attributes related to higher level attributes.

For example, fiscal week of year is the week number WITHOUT reference to a given year.

These can be used for filtering – for instance, when you want to see Month 6 of current year vs. Month 6 of prior year.



COMBINING METRICS WITH DATE TYPES IN DATA WAREHOUSING:

As described above, Metrics are types of quantitative data that provide such data as sales dollars, prices, costs,

quantities, etc. in which case different metrics fall under different classifications.

Simple Metrics Classification:

Simple Metrics are metrics that are simply aggregates of transactions, with no date logic built into the metric. Examples include Purchase Order metrics, Inventory Transaction metrics, and some Sales metrics (Sales - Cogs, Sales -

Retail, Sales - Units). Simple Metrics will filter & prompt easily on any time-scale you choose (Fiscal Day, Fiscal Week, Fiscal Month, etc.), and can break-down by any time attribute desired.

Filters & Prompts: Any of the date filters and prompts will work with these metrics such as filtering on Month Ago

= “0”, prompting on Fiscal Month and selecting the desired month, or prompting on a Fiscal Day Range in order

to report on a specific series of days.

If you filter or prompt on any of the “xxx Ago” metrics, you should include the related “Core” attribute on the

report. In other words, if you filter on “Week Ago”, you should include “Fiscal Week” on your report for easy reference when reviewing the data.

Example:

In this example, we use “Month Ago” in the filter to

make sure the report always shows the current month and

the prior 3 months listed with the actual “Fiscal Month” in the

report grid. The report also

breaks down by “Fiscal Day of Week” based off the Sales for

the selected Fiscal Months. If we put “Fiscal Day” in the

report instead of “Fiscal Day of

Week”, each date would be separated within the grid

instead of aggregating by Sunday, Monday, Tuesday,

etc.



Daily Inventory Metrics Classification: Daily Inventory Metrics are found under Metrics Inventory Daily

Inventory Metrics and should be used in conjunction with some sort of Fiscal time period. All daily inventory metrics are drawn from the

daily snapshot inventory table, and will aggregate at the day level based off the Fiscal time period defined. By default, these metrics will

populate the report with the values as of the last day of the defined time period which may or may not be the current values.

If the Fiscal time period includes the current day in the filter,

the Daily Inventory Metrics would be current values based off

the last time the upload from the production server was

complete. If the Fiscal time period does not include the current day in

the filter such as 1 month ago, the Daily Inventory Metrics

would not be current values, but rather the values of the last day of the previous month (1 month ago).

Weekly Inventory Metrics Classification: Weekly Inventory Metrics are found under Metrics Inventory Weekly

Inventory Metrics and should be used with a Fiscal Week, Fiscal Month, Fiscal Quarter or Fiscal Year time period. These metrics aggregate on a

weekly level, and using the Weekly Inventory Metrics with a Fiscal Date Range prompt will generate an error since Beginning and Ending Values

are not tracked on a daily basis. In addition, the GMROI, Inventory Turns, Sell Thru, and Supply are all calculations which also require at least a

Fiscal Week time period to calculate correctly. Note, that although the

name of the metric says “Weeks”, the system is actually calculating based of the time period in the report which may be Week, Month, Quarter, or

Year. You can filter or prompt at a higher level than a single week – month, quarter, or year. In those cases, the Beginning of Period metrics

will show the weekly snapshot for the first week in the period, and the

End of Period metrics will show the weekly snapshot for the most recent date in the period.

NOTE: There are some metrics that are calculated based on other

metrics. Examples are metrics like Turns and Sell Thru. Those metrics normally take the same filters and rules as the metrics they are based on.



Sales Period To Date Metrics Classification: Sales Period To Date Metrics are found under Metrics Sales

Sales Period to Date Metrics are providing various metrics that show Year To Date (YTD), Quarter To Date (QTD), Month To Date

(MTD), and Week to Date (WTD) sales data. These metrics are hard-coded to calculate as of the current date or the same day last

year if the Last Year (Sales LY Period to Date Metrics) metrics are used. They ignore any other date filtering, and they aggregate at

the level they are defined at.

Sales Prior Period Metrics Classification: Under the Sales Folder Metrics, there are a few metrics that specifically

calculate as of a prior period. They include metrics with –LM, -LY, and -

Previous in their names. These metrics are relative to the other date information in the report.

So, for instance, if you run a report that filters on “Month Ago” =

1, the “Sales Retail” metric will show last month’s sales, and the “Sales

Retail –LM” metric will show the month before that. It aggregates at the month level.

The –LY metrics show prior year. It aggregates and filters based

on the other metrics and filters in the report. If your report filters on the current fiscal month, the –LY metric will show the same month in the

previous year.

If your report filters on the current week, the –LY metric will show

the same week in the previous year. The –Previous metrics show the previous period, based on the

lowest level aggregation on the report. For instance, if your report

aggregates at a Day level, the –Previous metric will show previous day. If your report aggregates at a –Quarter level, the –Previous metric will show

previous quarter. Therefore, if the Fiscal Year is selected along with –LY

and –Previous, the LY and Previous values would be the same.

Combining Metric Types:

Combining metrics of different types can cause unexpected results. All the metrics will aggregate at the level of the lowest level metric on the report. So if you are trying to run a report with Current Inventory metrics (which aggregate at

the day level), and sales by weeks, you need to be careful that you are getting the result you expect.

Suggestion – If the need to combine metrics from different metric folders, it is recommended that you generate

a test report with each metric separately and compare the combined report to confirm that the combined report

is aggregating the data in the way you expect.



Inventory Transaction Metric Types: Inventory Transaction Metrics can be found under Metrics Inventory Inventory Transaction Metrics in which case

these metrics are associated with the movement of actual inventory. Inventory Transaction Metrics are different from other metrics by the following:

Inventory Transaction Metrics Sales will display as a

negative value when sold and a positive value when

returned due the fact that the system is showing a reduction or increase in inventory.

The values may be change somewhat when comparing a

report that uses Inventory Transaction Metrics for sales

versus a Sales metric due to how the data is populated. The inventory transaction metrics use the date the

inventory was deducted, rather than the date the sale was closed. Therefore, the same date range may populate

different sales due to when the merchandise was reduced

and when the sale was actually closed. This may be more common with web sales that have multiple shipments.

Inventory Transaction Metrics exclude non-inventory items

due to not tracking the actual quantity of the items. In order to include non-inventoried items, the Sales Metrics

should be used since non-inventoried items are included in those metrics.



UNDERSTANDING THE HIERARCHIES OF DATA:

Data Warehousing provides the ability to generate a summarized report in which case the user can drill down in order to

see more detail within the selected attribute’s element. This feature is extremely helpful when analyzing inventory data in

which case the report starts on a Department or Brand level and the user wants to drill down to a Style, or possibly a SKU

level on the screen.

Depending on the licenses purchased, there are two types of drilling available with Data Warehousing

Drill-In: This allows the user to drill into a pre-defined hierarchy that includes current attributes. Appendix C is a

list of the available hierarchies with each row representing a Drill-In Hierarchy.

o Example: Product Taxonomy Hierarchy can drill into Department > Type > Subtype1 > Subtype2 >

Subtype3 > Product, but cannot drill into Brand since Brand is not part of the defined hierarchy.

Drill-Across: This allows the user to drill across to another pre-defined hierarchy as long as there is a common link

between attributes. Note: The Drill-Across feature will still only allow drilling into attributes that are defined within

the pre-defined hierarchies which can be found in Appendix C.

o Example: Since Department is part of the Product Taxonomy Hierarchy, the user can then drill into Brand,

then Style, then Product as well since those attributes are available in the Product Brand Style Hierarchy.

In order to get a clear understanding of the Hierarchies, the user can review All Objects and expand Hierarchies > Data

Explorer. From this list the user can expand the Hierarchy (Product Brand Style) then Attribute (Brand) in order to select

the next level element (1000 FT. Above Sea). The next Attribute level will display (Style) in which case the desired

element can be selected (114115…). The list will continue until the lowest level available is displayed (Product) with the

final element desired (Nylon Jacket…). In addition to the list of Hierarchies and the ability to add the desired elements to

the filter, the user can also drill down when viewing the generated report. Please see Appendix C for a list of available

Hierarchies.



If a report is being reviewed, and the attribute displays as a hyperlink, the user can drill down by selecting the desired

attributes, all the way to the lowest level similar to the Hierarchy list described above.



REPORTING:

ADDING A FISCAL DAY RANGE PROMPT:

Most reports generated through Data Warehousing will require a specific date range in order to avoid pulling all history which can be performed by using the pre-defined Fiscal Transaction Date Attribute such as Fiscal Week, Fiscal Month, etc.

If a specific date range is needed that does not fall within a pre-defined Fiscal Week, Month, or Year, Data Warehousing

does have the ability to set a Fiscal Day Range as a prompt. NOTE: If using the Fiscal Day Range, please remember that Weekly Inventory Metrics will not be able to be included on the report since the lowest level available is Fiscal Weeks. If

the user attempts to combine the Weekly Inventory Metrics along with the Fiscal Date Range prompt, Data Warehousing will return an error when trying to generate the report.

Adding a Fiscal Day Range – Locate the desired report that requires editing from the list of Shared Reports (Production Reports) or from My Reports (newly saved reports), or begin creating a new blank report as

described above. Once the report is found, right-click on the Name and select Edit or simply select the sign from the list of Actions.

Once the Design Mode is displaying, under the All Objects section select Public Objects > Shared Filters. The

folder will display a list of pre-defined filters that Celerant Technology Corp has generated within Data

Warehousing in order to customize reports easier. In order to add the Fiscal Day Range, find the desired filter,

and click and drag it to the “Report Filter” section of the design area. Once this is complete, the “Report Filter”

section will display informing the user of the added prompt.



The other option in order to add the Fiscal Day Range prompt

to the report is by right-clicking on the Shared Filter and select

Add to Filter. If the right-click method is used, there is the

option to Add Prompt to Filter; however, this is not necessary

since the filter is already defined as a prompt. Therefore, the

user should always select Add to Filter if a Fiscal Day Range

prompt is required on a specific report.

Once a report is ran with the Fiscal Day Range defined as a Report

Filter, the user will be prompted to select a Starting Date and an

Ending Date for the report being processed. During the prompt, the

user can either manually type the date selection, or use the

button for a date selector. Once the desired dates are selected along

with any other prompts, select in order to generate the

report.



EDITING AN EXISTING REPORT IN DESIGN MODE:

Reports generated through Data Warehousing have a wide range of options available in order to customize the report to

fit the desired needs by the end-user. These options include formatting changes, adding/removing of specific data, or

defined calculations based off available metrics. Therefore, editing an existing report can be performed through various methods:

Editing a Report in Design Mode – Locate the desired report that needs editing from the list of Shared Reports (Production Reports) or from My Reports (newly saved reports). Once the report is found, right-click on

the Name and select Edit or simply select the sign from the list of Actions.

If there are prompts defined on the report, you will be able to select the desired prompts before editing the report, then select Edit in Design Mode in order to open the report in Design Mode.



From the Design Mode, the user can add, remove, or modify filters, prompts, attributes, and/or metrics a number

of different ways.

Add a Filter or Prompt – Find the desired attribute or metric from the

Report Objects or All Objects section similar to how a filter would be added to a new report described above. Once the desired object is found,

right-click and select Add to Filter or Add Prompt to Filter.

Remove from Filter or Prompt – Filters can be removed by selecting for all filters, or

beside the unwanted filter.

Modify a Filter or Prompt – The Report Filter will display the object being filtered as well as how the data

will be filtered, either by the qualification or by the selected elements. In order to modify an existing filter, select the hyperlinked list or qualification to display the detail of the filter and make the appropriate changes.

Once the changes are made select the sign to apply the filter.

Add an Attribute/Metric – From the Design Mode, the user can find the desired object through the Report

Objects or All Objects and either right-click on the object and select Add to Grid or simply click and drag the

object to the report design section. NOTE: Refer to the Understanding Your Data section to verify any

attributes or metrics you add are compatible with the other objects defined on the report.



Remove an Attribute/Metric – The removing of an attribute or metric can also be performed using

different methods. The user can right-click on the desired object and select Remove from Grid or Remove

from Report, select the object and drag it from the design section to the objects section, or can find the

object under Report Objects right-click and select Remove from Report.

o Remove from Grid – This will simply remove the object from the grid, but not the report. This would

be used if the object is required in a calculated metric that is defined on the report.

o Remove from Report – This will remove the object from the list of Report Objects which would be

used if the object is not necessary to the end user and should not be on the report at all.

Modify an Attribute/Metric – Modifying the format of a metric is typically performed through the report

display screen instead of the design mode, however, the user does have the ability to change the location of

the metric by either right-clicking and selecting Move > Left/Right or by simply clicking on the desired metric

and dragging it to the new location on the grid.

Once the desired changes are made, save the changes and run the report or select the sign in order to run

the report without saving.



EDITING AN EXISTING REPORT IN DISPLAY MODE:

Editing a Report from the Display Screen – At times the user may need to run the report to see what data is

currently available before knowing if changes are needed. Therefore, Data Warehousing will allow the user to edit

the report from the Display Screen once the report is generated. First, locate the desired report that needs

generated before any changes are made from the list of Shared Reports (Production Reports) or from My Reports

(newly saved reports). Once the report is found, select the Name of the report or right-click on the Name and

select Run.

If there are prompts defined on the report, you will be able to select the desired prompts before editing the

report, then select Edit in Design Mode in order to open the report in Design Mode.



Add an Attribute/Metric – Once the report is displayed, select the Tools tab, and then the All Objects button

in order to display the Objects List on the left side of the screen. From this list, the user can locate the desired

missing attribute or metric right-click and select Add to Grid, or the user can simply click on the object and drag it

to the displayed grid. NOTE: Refer to the Understanding Your Data section to verify the attribute or metric being

added will be compatible with the other attributes/metrics defined on the report.

Add a View Filter – The View Filter is different from the Report Filter defined in the Design Mode in that the

Report Filter will have to be added, removed, or modified through the Design Mode, while the View Filter will

allow the user to filter the viewable data based off what objects are already defined on the report. In order to

add a View Filter, select the Tools tab, and then the View Filter button in order to display the View Filter section.

From this section, the user can select the Add Condition button in order to select the object to filter, or if the

object is already displayed on the report, right-click on the column header and select Filter On… Once the filter is

entered, select the sign to apply the filter



Defining a Page-By – A Page-By axis will allow the user to define an attribute as a dropdown selection in order

to see only the selected attribute’s data without having to generate separate reports. This feature is especially

nice with multiple stores in which case the user can easily select the desired store to display. In order to set a

Page-By axis, determine the attribute the Page-By should be performed on, right-click on the attribute, and select

Move > To Page-by Axis.

Example: The desired Page-by is based off Inventory Type, in which case the report will provide a list of

Inventory Types that are associated with the report (based off prompts and filters). In order to display

the totals in the Page-By, the Totals for the selected Page-By must be setup within the report.

Adding Totals and Sub-Totals – Totals for the defined metrics are available by selecting the Data tab, then

the Show Totals button. If the Sub-Totals need to be defined, the user can select the Edit Totals button instead

and define what totals or sub-totals are needed.

Example: The Page-By described above did not originally have the totals based off Type. Select the Edit

Totals button, then continue to the Advanced tab in order to select the Type level. Next, select Apply,

then OK in order to display the totals as either a Page-By or sub-total on the grid.



Sorting Data – Data Warehousing has the ability to sort the report on multiple levels, such as Department,

Subtype1, and finally Sales-Retail. In order to define the desired sorting, the user will select the tab,

and then the button. This will open the Sort window in which case the user can define the sorting based off

the Row or Column. Once the sorting is defined select the button and button in order to apply the

sorting to the report.

Add a Calculated Metric – Within Data Warehousing, the user has the ability to add a new metric based off a

defined calulation of existing metrics or various equations. The best way to add a calculated metric is to first

generate the report to determine what is missing and what calculations are desired. Adding a new metric can be performed by either right-clicking on an existing metric header and selecting Insert Metric > New … or by

selecting the tab, and then the button. Selecting either option will open the “Insert New Metric” screen in which case the user can define the Name and Definition (calculation) based off the Available Metrics.

Example: Under the “Name” field, enter the desired name of the new metric such as “Gross Profit

Percentage”. Once the name is defined, under the “Definition” area, enter the desired equation. In order

to populate the “Definition” area with an existing Metric on the report, select the metric then the

button in order to add it to the equation. Once the “Definition” is defined, select the button and

button in order to add the new metric to the report.



The newly added metric may need to be moved in which case the user can right-click on the

metric header and move the column to the right or left, or the user can select the metric header and drag the column to the desired location.

Once the metric is added, it may require additional formatting such as $ or % formating in

order to display properly. This can be accomplished by selecting the tab.

Changing the Attribute Form Display – Some Attributes such as Store, Style, Fiscal Date have various Attribute Forms which determines how the data will be displayed on the report. Typically, there will be an ID form

along with a Description form in which case each user may want to change how the report is displayed. For

example, the Style Attribute has an ID (Style #) and a DESC (Description) of the style. If the user reviewing the report does not need the Style #, the user can right-click on the Attribute’s header and select Attribut Forms > ID in order to remove the Style # from the report. This would be similar with Stores in that a user may not want the full Store Name and only the Store Number. If the Store Attribute is listed on the report, the user can right-click

on the Store header then select Attribute Forms > Name in order to remove the Store’s name from the report and only display the store number.



Rename an Attribute/Metric Header Name – Due to the customization features in Data Warehousing, the

user has the ability to rename the system defaulted Header Name in order to reference easier. This feature can be performed by simply right-clicking on the desired header that needs renamed, and select Rename/Edit… This

will open the “Rename/Edit Objects” window in order for the user to overwrite the “Name” field with the desired

change. Once the “Name” is changed, select the button and button in order to update the name of

the attribute or metric on the report.

Example: The system’s default for Retail Sales is “Sales – Retail”. If the user rather the header list as

“Sales” or “Sales $”, right-click on the header and select Rename/Edit… in order to rename the header.



Pivoting an Attribute/Metric – There are times when a report requires the attribute to be listed across the

top of the report as opposed to the left side of the report and vis versa. Data Warehousing allows the user to pivot the desired attribute/metric in order to display the data in a format that is desired by the end user. In order

to adjust the Attribute or Metric, the user must first display the pivot buttons by selecting the tab, then

selecting the button. Once the “Pivot” button is selected, each row will dislpay the available options such as

move to a column, move to a row, move right, move left, page-by a specific field, or remove the column from the grid.

Example: Originally the Department was along the left side as the first column. Since there are only two departments listed, the user may want to pivot the

Department to a row in order to get a clearer comparison of both departments. In

order to perform this action, the user will select the button to display the pivot

selections, then select the button listed under the Department header.



Drilling Down – As described under the Understanding Your Data section, Data Warehousing has the abiltiy to

drill down on the data that is displayed on the report based off the Hierarchy of Data. Drilling down can be performed throught various methods when reviewing a report. The user can simply select the desired element as

long as there is a hyperlink such as Brand, the user can right-click on the desired element and select Drill in

order to select the next level of data available, or the user can select the tab and then select the

button to list the Drill options.

Exporting to Excel – Reports generated in Data Warehousing have the ability to be exported to Microsoft Excel

in which case the user can perform additional functions or save as a .csv file or a formatted Excel file. In order to

perform this function, the user will select the tab, and then select the button. This will open a new

Data Warehousing window with the available exporting options. From this screen the user will be able to define if

the file should be exported as a plain text file, .csv file, formatted Excel file, etc. Once the selections are defined,

select in order for Data Warehousing to export the report. Once Export is selected, Windows may

prompt to Open the file, Save the file with the defined name, or Save As a different name.



Displaying a Graph – Once a report is created, the user has the ability to have Data Warehousing manipulate

the data and display the results in only a report format, only a graph format, or display both the report and

graph. This can be performed by selecting the tab, then selecting (report only), (graph only), or

(graph and report). By selecting any of these buttons, the screen will display the data in the desired format. If

a graph display is desired and the default graph is not exactly what the user wants, the user can simply right-click

on the graph and select Format… in order to adjust the type of graph, how the data is displayed, or even the

axes values.

Example: A report is generated with two Departments (Men’s and Women’s) in which case the sales and

cost of goods sold are the metrics. The report below is an example of how the data will be presented if

both the report and graph are desired.



General Formatting – In addition to the functions described above, the user can also modify the formatting of

the data with the standardized options such as alignment, lines, decimals, etc. These options can be found under

the tab in which case most options are similar to those found under Microsoft Word or Excel.

EMAILING REPORTS:

Once a report is generated, the user has the ability to email the report directly from the display screen if needed. In order

to perform this function, the user will select the tab, and then select the button in order to open the Send Now window.

From this window, the user can select who to send the report to

from the list dropdown of established emails. If the recipient

of the email is not listed, the

client can select the

button in order to open the Recipients Browser window.

From the Recipients Browser window, the

user can define multiple recipients under the

“To:” address, “Cc:” address, or “Bcc:” address. In addition, if the recipient is not

listed, the user can add the Address Name, Physical Address, and select the Device then

click on . Once the recipients are defined, the user will select

to return to the Send Now window.



Once the recipients are determined, the user can set the appropriate Send method, Delivery Format, change the Subject,

and enter a Message to the recipient before selecting and emailing the report.



ADVANCED TOPICS:

SCHEDULING REPORTS:

At times, a report is required on a regular basis in which case the user would like to have the desired reports scheduled.

Scheduling a report through Data Warehousing can be performed various ways and can either be scheduled for an email or send to a History List in which case the user can access the report from the list. The reason the History List is

beneficial is so that the data is generated when no one is working on the server which would ultimately slow down the response time of other reports being generated.

In order to schedule a report, the user can perform this function before the report is run from the Report List, or from the Report Display screen. The method of using the report display screen will also allow the user to define thresholds and

reformat data so that particular data stands out when reviewing the report.

Report List Scheduling

Once the desired report is found, the user can select the button in order to open the Subscriptions screen for

that particular report.

From the Subscriptions screen, the user can add a History, Mobile,

Email, File, or Print subscription based off the licensing purchased.

For example, if a user would like to

add an Email Subscription, the user would go under the Email section

and select in order to open the E-mail Subscription setup screen.



Once the E-mail Subscription setup screen is displayed, the user can define the Name, the Schedule, the

Recipient, the Send method, the Delivery Format, the Subject, and a Message within the body of the email.

o Schedule – Due to the MicroStrategy licenses defining the schedules must be performed by Celerant Technology Corp. Please contact Celerant with the list of schedules desired and they will be setup on

your system. Note: Schedules cannot be set to run during the pre-defined time period when the data is being updated from the “Production” server.

o To – The dropdown selection provided will be a list of recipients defined within Data Warehousing. In

order to add more email recipients, select the button in order to open the Recipients Browser screen as described above under Emailing Reports.

Once the initial setup is complete, if the report has any prompts, the user will be able to determine the specific

prompts that will be applied each time the report is ran on the schedule. Once the subscription is complete, the

user will select to begin processing the subscription.

Display Screen Scheduling If the user runs a report and finds that the generated report is something that needs to be re-run on a scheduled

basis, the user can define an email subscription on the specific report without having to return to the Report List Display. In addition, the user can define a threshold in order to display specific data with a different format.

In order to set an email subscription from the Display

Screen, the user will right-click on the header of a desired Metric. From there, the user will select Alerts > Email Notification…



Once the Alerts Editor window is open, the user can define a threshold filter based off the available Metrics and

Attributes. For example, if the user would like for those Brands that have Sales-Retail that are greater than $20,000 stand out, the user would filter on Sales-Retail with the qualifier set to “Greater than or equal to 20000”.

Once the filter is defined, select in order to apply the filter.

The user can then select the button in order to open the Format window and change the Font, Alignment, Color, etc. Once the changes are made, the example will adjust with the format for those figures that greater

than or equal to $20,000.

Once the threshold filter is defined, the user can then continue to the Delivery Settings section of the Alerts Editor

screen in order to define the Name, Schedule, Recipient, Send method, Delivery Format, Subject , and Message

that is included in the body of the email. Once the Alert is completed, select to begin processing the subscription.

o Schedule – Due to the MicroStrategy licenses defining the schedules must be performed by Celerant

Technology Corp. Please contact Celerant with the list of schedules desired and they will be setup on your system. Note: Schedules cannot be set to run during the pre-defined time period when the data

is being updated from the “Production” server. o To – The dropdown selection provided will be a list of recipients defined within Data Warehousing. In

order to add more email recipients, select the button in order to open the Recipients Browser screen as described above under Emailing Reports.



CREATING DOCUMENTS:

Creating Documents, otherwise known as Dashboards, can be beneficial for users that would like to get a snap shot of data from multiple reports which is unable be combined on one single report. Therefore, Data Warehousing offers the

ability to create a Document which can be a combination of reports, graphs, or charts from a list of templates depending on what data is needed.

In order to begin creating a Document, the user must determine

what existing reports are going to be used along with any the creation of

any new reports that is required. The generating of existing reports,

formatting, graphing, and creation

of new reports are all covered in the above sections. Once the reports

needed for the Document are determined, the user will then select

Create Document from the

MicroStrategy Data Warehousing Projects Home Screen, or select

from the menu bar.

Once selected, the Create Document screen will display in which case the user can select a Blank Document or a Dashboard Template. In the below example, 08 One Content Top Two Contents Bottom is selected in order to add three

different reports. Once selected, the Design Screen will open in order to begin defining what reports should be added to the dashboard.



From the Design Screen, the user can either select the

button under the Dataset Objects in order to add the

report to the Document. Note: adding the Report to the

Dataset Object will not necessarily add the report to the document display, but will allow the user to then click

and drag the report to the desired area on the document. Once the desired report is found, select

to add the report to the Document.

In addition to adding the report to the Dataset Objects list and dragging the report to the desired location, the user can

select the button under the area in which case the individual report will display. This will then dropdown

with a list of options in which case the user can select in order to open the Select Dataset window and select the desired report.



Once all the desired reports are added to the document, the Dataset Objects list will display the reports listed on the

Document and the Design section will display how the data will be presented. In the example below, the top area will display a bar graph of Month To Date Sales by Store, while the bottom left area will display a pie graph with the Year To

Date Sales by Store, and the bottom right will display a grid of the Week To Date Sales by Store. Once the Document is

created, select the button in order to save the Document and display the finished Document.



Once the Document is saved, the user will be prompted to Return to Design Mode or Run newly saved document, in

which case the user can review the final Document.



THRESHOLDS WITHIN DATA WAREHOUSING:

Thresholds are beneficial when analyzing large amounts of data by using different formats, colors, or symbols for

data that falls within or outside a user defined range. Once a report is generated, the user has the ability to apply

simple thresholds to the data by using the Quick Threshold feature, or more complex thresholds using the Visual

Threshold or Advanced Threshold features under the tab. In addition, the user defined conditions can

vary in complexity depending upon the type of threshold that is required. Note: MicroStrategy’s Help link can

provide additional information regarding thresholds as well.

Example: A report generated that displays Sales-Retail by Brand for a specific Department may want to

be analyzed with the top 20% and bottom 20% standing out in order to determine which Brands are

successful and which ones are unsuccessful. This can be performed by using the threshold features

found under the tab. First, the user must select the header field of the

metric that is having the threshold applied.

Once the header is selected, in this case Sales-Retail, the user

can select the button in order to apply a quick

threshold that is already pre-defined. The dropdown will

provide the list of available displays such as background color,

font color, or symbols. Depending on the threshold format

selected, the default will affect the top 20% and bottom 20%,

then possibly the middle 60% if applicable.

Once a threshold is applied, the user can toggle between displaying the data with or without the

threshold by selecting the button. Below is an example of how the background threshold would

display.



In addition to the default threshold, the user can also select the button in order to use the Visual

Threshold Editor. Once selected the Visual Threshold Editor will display and allow the user to select what

metric the threshold is being applied towards, along with the ability move the threshold based off the

threshold bar.



In addition to being able to move the threshold bar, the user

can place the cursor on the threshold area in order to display

the options such as format, clear format, add threshold, or

delete the threshold. If the user would like the format to be

modified, select the button will open the Format window in

which case the user can change the font, replace the data with

text, adjust the alignment, or adjust the colors associated with

the fields. Once the changes are made, select and

then in order to apply the changes to the threshold.

In addition to the Visual

Threshold Editor, the user can

select the button in order to

open the Advanced Threshold

Editor screen in which case the

user can manipulate an existing

threshold, or create a new

threshold without utilizing the

Visual Threshold Editor bar.



CREATING A TOP XX REPORT:

Creating a Top XX Report can be beneficial when analyzing data. Data Warehousing provides this feature and can be setup through the Report Design screen or the Report Display screen as needed. In order to setup a report with ranking,

the user must first have all the desired attributes, metrics, and filters established. Once that is complete, the user can add the ranking through either screen.

Once the user determines what metric the ranking is desired on, the user can right-click on the metric and select Insert Metric > Rank > Break by …. > Ascending or Descending. In the example below, the Break by option is

listed for None, Department, and Brand based off the attributes included on the grid.

o None – If the user breaks by None, the ranking is across all Departments and all Brands. o Department – If the user breaks by Department, the ranking is within the Departments listed.

o Brand – If the user breaks by Brand, the ranking is within the Brands listed. o Ascending – This indicates that the higher values get a higher ranking number, so the product with

the highest value is ranked number 100.

o Descending – This indicates that the higher values get a lower ranking number, so the product with the highest value is ranked number 1.

Once the user has added the ranking metric, the user will have to generate

the report in order to set a filter on

the top XX. If the user does not want to use the Design Report screen, the

user can run the report and right-click on the desired metric the ranking is

required on and select Insert Metric > Rank > Break by … > Ascending or Descending as described above.

Once the Ranking is added to the report, the user

can right-click on the new metric header and select Filter On > Top N… in order to set the ranking.

This will open the Filter on Metric window in which case the user can define how the ranking should be filtered.

For example, if the ranking was based off Ascending, the Highest 10 would provide a list of the top ten Brands with the highest Sales-Retail.



Once the report has the ranking, the user can right-click on the

ranking metric, in this case Rank (Sales-Retail) Break by (Department) and select Remove from Grid in order to remove this column from the report. Do not select Remove from Report, because Remove from Report will not only remove the column from the grid, but also remove the ranking filter as well.

CREATING AN “OR” FILTER: Typically when multiple filters are required, each filter will narrow the

results further in order to generate the desired report. In these instances,

each transaction must match ALL of the filters in order to be included in

the report. There are exceptions to this filtering in which case the user

may want to include transactions that passes EITHER ONE of two filters.

In these instances, the user can use the “OR” filter instead of the system

defaulted “AND” filter.

Example: In order to make sure all Sales-Units are displayed

when filtering on Current On Hand > 0, the user could define an

“OR” filter on both Current On Hand > 0 OR Sales-Units > 0. In

order to perform this function, edit the report in Design Mode in

which case the Report Filter section will display. From the All

Objects list, find the Attributes or Metrics that you would like to

filter the data on and right-click then select Add to Filter.



Once the object is added to the Report Filter, the user will be able to define the qualitative filter, or

selection filter as described above. In this example, notice the Sales-Units is a qualitative filter in order to

include sales that are greater than 0. Once the filter is defined select the button to apply the filter.

Also notice the system defaulted the filter to “AND” and listed it at the end of the already defined filters.

Once the filter is defined, use the button to move the filter under the other filter you are applying the

“OR” statement towards.

Once the filters are next to each other, select the

hyperlink in order to display the OR, AND

NOT, and OR NOT options available.

Once the desired option is selected, the

hyperlink will then change to the selected

hyperlink such as informing the user of the

modified filter. When using the OR filter, Data

Warehousing will connect the two filters that are

beside one another and indent the group as a

visual display of how the filter will function.



REMOVING UNNECESSARY OBJECTS:

Each time a Data Warehousing report is generated, the system will go through the Report Objects in order to pull

the appropriate data. It is recommended that if an attribute or metric is not needed on the report, either as an

actual displayed field or as part of a calculated field, is removed from the list of Report Objects in order to avoid

misleading data from the aggregating Data Warehousing performs and to speed up the response time when

generating the report. In order to review what attributes and metrics are being used, the user can select the

tab, and then select the button in order to display the Report Objects list.

Once the Report Objects list is displayed, the user

will be able to determine which attributes and

metrics are not currently used within the report.

Attributes and Metrics that are in the report but

not in the grid show up in dark lettering such as

Daily Invt-Average Cost, while Attributes and

Metrics that are displayed in the grid will display

on the Report Objects list in a gray color such as

Brand.

In order to an Attribute or Metric, the users can

right-click on the unwanted object and select

Remove from Report. Once the unnecessary

objects are removed, it is recommended that the

user save the report which may speed up the time

it takes to generate the report the next time it is

ran.

FILTERING ON FISCAL MONTH vs. FISCAL MONTH OF YEAR: When filtering on Fiscal periods, Celerant has defined Fiscal Month and Fiscal Month of Year as two different

attributes. The reason for this is to allow reports to be generated for a specific month including the year, or a

specific month number which may need to be combined with a Fiscal Year selection. This would be similar to

Fiscal Week and Fiscal Week of Year as well.

Example: Fiscal Month will display as 2011 FM7:10/3/2011 while Fiscal Month of Year will display as FM7

and may need to be combined with another attribute such as Fiscal Year or Fiscal Year Ago.



BEGINNING AND ENDING INVENTORY:

Beginning and Ending Inventory Metrics can be found under

Metrics > Inventory > Weekly Inventory Metrics. However, in

order for Data Warehousing to display the results the Attribute

of a fiscal time period of a Fiscal Week or higher must be used

otherwise Data Warehousing will return with an error.

Therefore, utilizing the Weekly Inventory Metrics with a Fiscal

Day Range prompt will produce an error. The fiscal time period

must be based off a Fiscal Week, Fiscal Month, Fiscal Quarter,

or Fiscal Year. This includes the pre-defined calculations found

under the Weekly Inventory Metrics as well.

FILTERING ON METRICS: Data Warehousing will allow the user to filter data based off Attributes as well as Metrics, however, when filtering by

Metrics is a little more complex than attributes. Celerant recommends that the user verify what objects are added to the

report in order to understand what level the metrics are aggregating at so they are sure that the filter is providing the

desired results.

Examples of situations where a user might need to filter on metrics are as follows:

1. Show only styles that have more than $25,000 in Sales.

2. Show products that have an On-hand quantity.

Data Warehousing will aggregate the values first, and then filter based on the totals. In addition, Data

Warehousing will always aggregate at the lowest level of detail included in the report. Therefore, if the report

has both style and product attributes, the system will include only products that fit the criteria. This applies to all

attributes included in the report objects, whether or not they are displayed in the grid.

Below is an example intended to show sales for only styles that have an on-hand quantity. Unfortunately, when

the report was run, some sales were not included due to the report displaying on the Style level, but aggregating

at the Product (sku) level. Some sku’s within the a style may have sales that should be included, however, they

do not contain an on-hand quantity so those skus’ sales are not included in the total sales of the style.

Example: In the below example, the report is displaying the Brand and Style Attributes as well as the End of

Period On Hand-Units and Sales-Units for the current Year (Year Ago = 0). Notice there is an additional filter for

the End of Period On Hand-Units in order to filter out items with zero On Hand. Also, notice the Sales-Units is

currently displaying 125 units.



Next, review the Report Objects for this particular report. Notice

there is the Product object which is one level further than the Style

level based off the hierarchy of the data.

Since the Product attribute is included on the report and there is a filter on the End of Period On Hand-Units of

“Greater Than 0”, the Sales-Units may be misleading due to the filter on a metric. The reason for this is because

the Sales-Units are

aggregating on a Product

level since the Product

object is included on the

report. Therefore, a product

(sku) of this particular style

is not included in the overall

Sales-Units if the End of

Period On Hand-Units is not

greater than 0. Shown is an

example of the Product

Detail of the same report as

above that makes up the

Sales-Units of 125 units.

In order to retrieve a more accurate Sales-Units

figure, the users could right-click on the Product

object under the Report Objects and select Remove

from Report in order to remove how the data is

being aggregated on the Product level.



Once the Product attribute is removed from the report, notice the Sales-Units quantity has increased to 160 units.

The reason for this is that the system is now aggregating the Sales-Units on the Style level as opposed to the

Product level, meaning the filter on the End of Period On Hand-Units is being performed on the entire style.

Therefore, even though some product of that particular style has a zero on hand quantity, the filter determines

the overall style has an on hand quantity greater than zero and will display the units sold for the entire style.

If the user then tries to drill down to the Product level with the filter defined on the End of Period On Hand-Units

metric, the Product detail may not agree with the Style detail. Therefore, if a filter on a metric is desired, it is

recommended that the user

determine what level of

data is needed in order to

determine how the data is

being aggregated.



SETTING UP A DIFFERENCE COLUMN:

Creating a Difference Column on a report may be difficult when trying to compare one year’s monthly figures to a previous year’s monthly figures. In the example below, the user wanted to see 3 years of sales with a new calculated

column displaying the differences one year over the next. Therefore, the process of creating a Difference Column is described below.

First, the Metrics defined on the report must have a –LY (Last Year) Metric. The –LY Metrics use the same time frame as defined on the report, just simply one year prior. For example, the report below is providing the Cost of Goods Sold for

the first fiscal month of the previous 3 years by Brand. Therefore, the –LY Metric must be included in the Report Objects, but it does not have to be included in the Report Grid. Therefore, the first step is to design the report with the specific

filters, attributes, and metrics.

In the example below, the Metrics

added to the report are Sales-COGS and Sales-COGS-LY-Fiscal. Since the

desired result is to have a Difference Column on the report, there is no need

to have Sales-COGS-LY-Fiscal included

on the grid; however, in order to provide the necessary calculation, the Sales-COGS-LY-Fiscal Metric must be included on the Report. In order to

perform this function, the user will right-click on the Sales-COGS-LY-Fiscal metric and select Remove from Grid

(NOT Remove from Report).

This will result in the Sales-COGS metric being included in the grid while the

Sales-COGS-LY-Fiscal metric will only be included in the Report, but not the Grid.

In addition, please note that the Fiscal Year attribute is below the Metrics which causes the metric to show the 3 years based off the filter before showing the difference column that will be added. Once the report is designed, the user can

save and run the report or simply run the report if saving is not necessary.

Once the report is

displayed, the user can right-click on the metric

(Sales-COGS), and select Insert Metric > New … This

will open the Insert New Metric window in order to define the difference

column desired.

From the Insert New Metric window, the user can define the Name and the Definition based off the metrics available in

the report. NOTE: Even though the Sales-COGS-LY-Fiscal metric is not displayed on the grid, the new metric can use this

value in defined calculations. The user can select the desired metric from the Available side and use the button to move the metric to the Definition side. In addition, the user will need to manually type the calculation symbol (+, -, *, /)

between the metrics. Once the Definition is complete, the user can select then in order to add the new



metric to the grid. NOTE: Once the metric is added, the user may need to move the metric to the desired location on the

grid as well as adjust the format accordingly.

CREATING CUSTOM GROUPS FOR TIME PERIODS: Custom groups are a powerful tool for making MicroStrategy reports more meaningful by allowing the user to define

customized groupings of attribute values. Once the desired Custom Groups are defined, the user can then add the group

to a report in the same manner as an attribute, however, the data returned on the report will be grouped together accordingly. Some examples of Custom Groups include time periods where the user wants to analyze one time periods

data versus another time periods data on one report such as year-over-year, or month-over-month. Another example which is described in further detail under the Creating Custom Groups for Stores is the ability to group specific stores

together. This would be ideal for those users that have different websites record sales under different stores, but want to be combined when analyzing sales data.

In order to begin creating a Custom Group, the user must be under the Shared Reports directory or My Reports directory.

From there, the user will select the button in order to open the Custom Group Editor window.



Once the Custom Group Editor window is opened, the user can

define the Custom Group Name and Description which will be the reference once the Custom Group is saved and added to a report.

This can be entered by simply selecting the various fields and

typing the desired name and description.

Once the Custom Group Name and Description are defined, select in order to add a

new element to the Custom Group. This option will open the Condition Editor window in which case the user will select

the Browse… option to find the desired attribute to group.



In this example, the user would like to list sales for a specific date range with the current year

(2012) compared to the previous year (2011),

and does not want to use the standard Fiscal Calendar. In this case, the user would select the

Fiscal Transaction Date attribute, which would list all the available attributes found under that

directory. From there, the user would select the Fiscal Day attribute in order to define the group

element.

Once the desired attribute is selected, the Condition Editor will display the selected attribute along with the available

options in order to set the conditions of the group element.

In List – Selecting “In List” will present a list of the available data in the selected attribute in order to select

what specifically is grouped in the defined group element. Any element that is selected will be included in the

Group Element once the group is saved and added to a report. Not In List – Selecting “Not In List” will present a list of available data in the selected attribute in order to

select what specifically should NOT be included in the defined group element. Therefore, any element that is

selected will NOT be included in the report when the Custom Group is added. ID – Selecting “ID” will display a list of qualitative options such as Equals, Greater Than, Less Than, Between,

etc. Depending on the type of data that is being grouped, selecting a qualitative action will display a field to

type the values, or a calendar selection if dealing with a date.

DESC – Selecting “DESC” will display a similar list of qualitative options in which case the user will enter the

desired values that will represent the group element.



In this example, the “ID” option will be selected with the “Between” qualitative option with the beginning date of Jan. 1,

2011 and an ending date of Dec. 31, 2011. Note: The user can select the Month or Year to jump to a specific date, or can

use the right and left arrows to scroll through the months in order to select the desired date. Once the condition is

defined, select to

apply the element to the

Custom Group. In addition,

the user can then select the

“Element 1” title and rename

the element accordingly (in

this example “Year 2011”).

Once the first group element is defined, the

user can select New custom group element in

order to add any additional elements under

the defined group. In this example, the user

needs to compare 2011 sales to 2011 sales, in

which case the are two Group Elements

labeled “Year 2011” and “Year 2012”. Once all the group elements are defined,

select to open the Save As window for the Custom Group. The

user can then save the Custom Group under the Shared Reports or My Reports

directory as needed. Once the desired location is set, select to save the

Custom Group.



Once the Custom Group is saved, the user can then create a new report or edit an existing report in order to add the

newly created Custom Group in the same manner as a normal attribute. For example, the user would like to see the Sales

Retail by Brand for sales that took place between 1/1/2012 – 7/31/2012 compare to the same date period in 2011. In this

case, the Custom Group was saved under My Reports which has been added to the report along with two filters on the

Fiscal Day attribute, one for transactions between 1/1/2011 – 7/31/2011 and the other for transactions between 1/1/2012

– 7/31/2012. The outcome of this report will list the Brand along with the retail sales for the defined dates, but list under

the Custom Group Elements of Year 2011 and Year 2012.



CREATING CUSTOM GROUPS FOR STORES:

As discussed above, Custom groups are a powerful tool for making MicroStrategy reports more meaningful by allowing

the user to define customized groupings of attribute values. In this example, the user has multiple stores in which case

two stores represent sales entered through two different websites. When analyzing the sales data, the user would like to

list the individual stores, however, the user would like the web stores combined instead of listed separately. In order to

accomplish this, the Custom Groups feature will be used to group the Web Stores and group the traditional Retail Stores.

Once the desired Custom Group is defined, the user can then add the group to a report in the same manner as a pre-

defined attribute.

In order to begin creating a Custom Group, the user must be under the Shared Reports directory or My Reports directory.

From there, the user will select the button in order to open the Custom Group Editor window.

Once the Custom Group Editor window is opened, the user can define the Custom Group Name and Description

which will be the reference once the Custom Group is saved and added to a report. This can be entered by

simply selecting the various fields and typing the desired name and description. In this example, the Custom

Group will be named “Web Stores”.

Once the Custom Group Name and Description are defined, select in order to add a

new element to the Custom Group. This option will open the Condition Editor window in which case the user will select the Browse… option to find the desired attribute to group.



In this example, the user would like to generate a report that lists the sales by store, but would like

to combine the two web stores, in this case Store

5 and store 10. The first Group Element will represent the two web stores, while the second

Group Element will represent the traditional retail stores. In order to accomplish this, the user will

need to find the Sales Store directory and select the Store attribute. Once the Sales Store is

selected, the Condition Editor screen will list the

various options and elements associated with the attribute in order to add the desired condition.



In this example, since the first Group Element will represent the combination of the two web stores, Store 5 and Store 10,

the user can select the “In List” conditional option in order to select the two desired stores. Once the selections are made,

the user will select the button to create the Group Element.

Once the Group Element is defined, the user can rename the Element, in this case “Web Store” which will then be used on the report. In addition, when the user hovers over the group element, the following three icons in the top right will

display . The button will open the Element Options screen in which case the user can select one of the following options. In this example, since the user only wants Store 5 and Store 10 listed as “Web Store”, the user will

want to select Display element name only (Default).



Display element name only (Default) – This will only

display the Group Element name only. In this example,

only “Web Store” will display on the report. Display individual items only – This will show the

individual items that make up the Group Element. In this

example if set, Store 5 and Store 10 would display separately on the report.

Display element name and individual items – This

will display both the Group Element name as well as the individual items that make up the Group Element. In this

example if set, “Web Store” and Store 5 and Store 10

would display on the report if the Custom Group is used.

Once the “Web Store” is setup, the next Group Element needed is the additional Retail Stores. This can be accomplished by selecting

in which case the Condition Editor screen will display. In this example, the user will select the Sales Store directory and select the Store attribute. Once the Sales Store is selected, the Condition Editor screen will list the various options

and elements associated with the attribute in order to add the desired condition. Once the desired attribute is selected, the user

will need to select the conditional option. In this example since this Group Element being created is for the Retail Stores, the

conditional option can be set to “Not In List”, in which case the

user can select Store 5 and Store 10 which should not be included in the Retail Store element. Once the condition is defined, select

to create the group element.

Once the Condition Editor is defined for the stores excluding Store 5 and Store 10, the user can rename the group

element, in this case “Retail Store” for reference when using the Custom Group on a report. In addition, the user can

hover over the Group Element and select in order to set the Element Options. If the user wants to combine all the

Retail stores, then the user will want to select Display element name only (Default). If the user wants to list the individual

retail stores separately, then the user will want to select Display individual items only. In this example, Display individual

items only is selected. Once the desired option is set along with the desired Custom Elements, the user will select

in order to save the Custom Group in the desired location.



Once the Custom Group is saved, the user can then create a new report or edit an existing report in order to add the

newly created Custom Group in the same manner as a normal attribute. For example, the user would like to see the Sales

Retail and Sales COGS for a specific date range by Store. However, instead of listing each store separately, the user

would like to combine the web stores, in this case Store 5 and Store 10. In order to accomplish this, the Custom Group

created above was saved under My Reports which has been added to the report along with the other metrics and filter

desired. Once the design of the report is setup, the user can run the report and produce the desired report as shown

below.

NOTE: The “Web Stores” column is listing both “Web Store” and Retail Store” based off the Custom Group defined. Also

notice the column to the right of “Web Store” is blank, while the column to the right of “Retail Store” has the actual store

numbers. This is due to the “Web Store” element being set with Display element name only (Default) while the “Retail

Store element is set to Display individual items only as described above.



APPENDIX A:

ATTRIBUTE DEFINITIONS:

ATTRIBUTE GROUP ATTRIBUTE NAME DEFINITION

BUYER

Buyer Buyer's name assigned to a PO

Buyer City City entered under Buyer's Employee record

Buyer Commission Rate Commission rate if applied to Buyer

Buyer Company Name Company assigned to Buyer

Buyer Country Country assigned to Buyer

Buyer Employee Type

Label Buyer's Employee Type

Buyer Hire Date Date the Buyer was hired

Buyer is Fulltime Flag if Buyer is full-time employee

Buyer is Manager Flag if Buyer is a manager

Buyer is Terminated Flag if Buyer was terminated

Buyer State or Province

Code State/Province entered under Buyer's Employee Record

Buyers Years of Service Buyer's years of service

Buyer Zip Code Zip Code entered under Buyer's Employee Record

CUSTOMER Can Email Flag if can email customer

Can Mail Flag if can send mail to customer



CRM Club Label Customer's CRM club

Custom Category 1 Client-defined Custom Category 1




Customer Customer name

Customer City Customer's city

Customer Country Customer's country

Customer Gender Customer's gender

Customer Price Code Customer price code

Customer State or

Province Code Customer's state/province

Customer Type Customer's type

Customer Zip Code Customer zip code

Has Account Flag if customer is an AR/On Account Customer

Has Buy Club Flag if customer has a Buy Club

Is Employee Flag if customer is an employee

Is Wholesale Flag if customer is wholesale

FISCAL

TRANSACTION

DATE

Day Ago

Represents the number of Days Ago. (0 = Current Day, 1 = 1 Day

Ago, 2 = 2 Days Ago, etc.)

Fiscal Day Fiscal Day is the actual date. (15 Sep 2012 SAT:9/15/12)

Fiscal Day of Week Fiscal Day of Week is the day of a week (Sunday, Monday, Tuesday, Wednesday, etc.)

Fiscal Month

Fiscal Month is the actual month based off the Fiscal Calendar.

(2012 FM7: 10/1/2012)

Fiscal Month of Year

Fiscal Month of Year is the fiscal month based off the year selected.

(FM 1, FM 2, FM 3, etc.)

Fiscal Quarter Fiscal Quarter is the actual fiscal quarter. (2012 FQ3: 10/1/2012)

Fiscal Week Fiscal Week is the actual fiscal week. (2012 FW18: 7/30/2012:18)

Fiscal Week of Year Fiscal Week of Year is the fiscal week based off the month or year selected. (FW 1, FW 2, FW 3, etc.)

Fiscal Year

Fiscal Year is the actual year based off the Fiscal Calendar. (2012:

4/4/2012)

Month Ago

Represents the number of Months Ago. (0 = Current Month, 1 = 1

Month Ago, 2 = 2 Months Ago, etc.)

Quarter Ago Represents the number of Quarters Ago. (0 = Current Quarter, 1 = 1 Quarter Ago, 2 = 2 Quarters Ago, etc.)

Week Ago

Represents the number of Weeks Ago. (0 = Current Week, 1 = 1

Week Ago, 2 = 2 Weeks Ago, etc.)

Year Ago

Represents the number of Years Ago. (0 = Current Year, 1 = 1

Year Ago, 2 = 2 Years Ago, etc.)

INVENTORY

STORE

Inventory Store Inventory store's # and name.

Inventory Store City Inventory store's city.

Inventory Store Company

Name Inventory store's company name.

Inventory Store Country Inventory store's country.

Inventory Store Custom

Field 1 Client-defined inventory store custom field 1.

Inventory Store Custom Field 2 Client-defined inventory store custom field 2.

Inventory Store Custom Field 3 Client-defined inventory store custom field 3.








Franchise Name Inventory store's franchise name if assigned.

Inventory Store Region Inventory store's region name if assigned.

Inventory Store State or

Province Code Inventory store's state/province.

Inventory Store Zip Code Inventory store's zip code.

PRODUCT

Attribute1 Item's attr1 / color

Attribute2 Item's attr2

Brand Item's brand

Department Item's department

Is Active Item Flag if item is active

Is Firearm Item Flag if item is a firearm

Is Sales Store Active Flag if active in sales store

Is Sales Warehouse Active Flag if active in sales warehouse

Open Field 1 Client-defined inventory OF1




















Primary Barcode Item's primary barcode

Product Sku Record of item

Size Item's size

Style Item's style #

Subtype1 Item's taxonomy sub-type1



Type Item's taxonomy type

PROMOTION

Promotion Name Promotion Name

Promotion Begin Date Promotion Begin Date

Promotion End Date Promotion End Date

Promotion Type Promotion Type

PURCHASE

ORDERS

PO Arrival Date (day/week/month/quarter

/year) PO Arrival Date (day/week/month/quarter/year)

PO Cancel Date

(day/week/month/quarter PO Cancel Date (day/week/month/quarter/year)



/year)

PO Last Received Date

(day/week/month/quarter

/year) PO Last Received Date (day/week/month/quarter/year)

PO Order Date

(day/week/month/quarter

/year) PO Order Date (day/week/month/quarter/year)

PO Ship Date

(day/week/month/quarter/year) PO Ship Date (day/week/month/quarter/year)

PO Brand PO Brand

PO Closed PO Closed Status

PO Drop Ship PO Drop Ship Flag

PO is Distro PO is Distro Flag

PO Season PO Season

PO Ship Term PO Ship Term

PO Special Order PO Special Order

PO Type PO Type

Vendor PO # Vendor PO #

SALES MARKDOWN

%

Five Range Markdown percentages in 5% increments

Percent Exact Markdown percentages

Ten Range Markdown percentages in 10% increments

SALES PERSON

Sales Person Salesperson's name

Sales Person City Salesperson's city

Sales Person Commission

Rate Salesperson's commission rate

Sales Person Company

Name Salesperson's company

Sales Person Country Salesperson's country

Sales Person Employee

Type Label Salesperson's employee type

Sales Person Hire Date Salesperson's hire date

Sales Person is Fulltime Flag if salesperson is fulltime

Sales Person is Manager Flag if salesperson is a manager

Sales Person is Terminated Flag if salesperson is a terminated

Sales Person State or

Province Code Salesperson's state/province

Sales Person Store # Salesperson's store #

Sales Person Years of Service Salesperson's years of service

Sales Person Zip Code Salesperson's zip code

SALES STORE

Sales Store Sales Store

Sales Store City Sales Store City

Sales Store Country Sales Store Country

Sales Store Custom Field 1 Client-defined sales store custom field 1.





Sales Store Franchise

Name Sales Store Franchise Name

Sales Store Region Sales Store Region

Sales Store State or Province Code Sales Store State or Province Code



Sales Store Zip Code Sales Store Zip Code

SALES TIME OF DAY

Sales AM PM Sales that took place in the AM or PM

Sales Hour Sales Hour (07 AM, 08 AM, 03 PM, etc.)

Sales Time of Day Actual Time of Day the sale took place (16:29 = 4:29PM)

Sales Time Range 12 Hourly Time Range using a traditional 12 hour time (02:00 - 02:59 PM, 08:00 - 08:59 AM, etc.)

Sales Time Range 24

Hourly Time Range using a 24 hour time period (14:00 - 14:59,

08:00 - 08:59, etc.)

TRANSATION

TYPES Transaction Type

Transaction Type (Back Office Markdown, Inventory Transfer -

Outbound, Inventory Adjustment, Inventory Sold, Receive

Inventory From Vendor, etc.) for any inventory transaction that affects inventory

VENDOR

Always Discount Always Discount

Discount Percent Discount Percent

Net Net

Net2 Net2

Vendor Vendor

Vendor City Vendor City

Vendor Country Vendor Country

Vendor ID Vendor ID

Vendor State or Province

Code Vendor State or Province Code

Vendor Zip Code Vendor Zip Code



METRIC DEFINITIONS:

METRIC GROUP METRIC NAME DEFINITION

DAILY INVENTORY

METRICS

Daily Invt - Average Cost Avg Cost of last day of selected date range

Daily Invt - Committed - Cost Value Cost Value of committed inventory qty of last day of selected date range

Daily Invt - Committed - Retail Value Retail Value of committed inventory qty of last day of selected date range

Daily Invt - Committed - Units Committed qty of last day of selected date range

Daily Invt - First Price First Price of the inventory.

Daily Invt - First Rcvd Date First Received Date of the inventory

Daily Invt - In Transit - Cost Value In-Transit cost value based off the last day of the selected date range

Daily Invt - In Transit - Retail Value In-Transit retail value based off the last day of the selected date range

Daily Invt - In Transit - Units In-Transit units based off the last day of the selected date range

Daily Invt - Last Cost Last Cost based off the last day of the selected date range

Daily Invt - Last Mkdn Date Last Mkdn Date

Daily Invt - Last Received Date Last Received Date

Daily Invt - Last Sold Date Last Sold Date

Daily Invt - Max Quantity Maximum qty defined on the item



Daily Invt - Min Quantity Minimum qty defined on the item

Daily Invt - Need Quantity Calculated qty needed based off Min/Max

Daily Invt - On Hand - Cost Value On Hand cost value based off the last day of the selected date range

Daily Invt - On Hand - Retail Value On Hand retail value based off the last day of the selected date range

Daily Invt - On Hand - Units On Hand units based off the last day of the selected date range

Daily Invt - On Order - Cost Value On Order cost value based off the last day of the selected date range

Daily Invt - On Order - Retail Value On Order retail value based off the last day of the selected date range

Daily Invt - On Order - Units On Order units based off the last day of the selected date range

Daily Invt - Reorder Cost $ Reorder cost dollars

Daily Invt - Reorder $ Reorder retail dollars

Daily Invt - Reorder Quantity Reorder qty

Daily Invt - Selling Price Selling Price

Daily Invt - Store Price Store Price

Daily Invt - Style Last Rcvd Date Style last received date

Daily Invt - Suggested Price Suggested price

INVENTORY TRANSACTIONS

Invt Trans - BO Inventory Markdown - Cost Back office markdown cost

Invt Trans - BO Inventory Markdown - Retail Back office markdown retail

Invt Trans - BO Inventory Markdown - Units Back office markdown units

Invt Trans - Interstore Transfer - Inbound Option 1 - Cost

Invt Trans - Interstore Transfer - Inbound Option 1 - Retail

Invt Trans - Interstore Transfer - Inbound Option 1 - Units

Invt Trans - Interstore Transfer - Inbound Option 2 - Cost

Invt Trans - Interstore Transfer - Inbound Option 2 - Retail

Invt Trans - Interstore Transfer - Inbound Option 2 - Units

Invt Trans - Interstore Transfer - Outbound - Cost Outbound transfer cost

Invt Trans - Interstore Transfer - Outbound - Retail Outbound transfer retail

Invt Trans - Interstore Transfer - Outbound - Units Outbound transfer units

Invt Trans - Interstore Adjustment - Cost Transfer In/Out Cost

Invt Trans - Interstore Adjustment - Retail Transfer In/Out Retail

Invt Trans - Interstore Adjustment - Units Transfer In/Out Units

Invt Trans - Interstore Sold - Cost

Invt Trans - Interstore Sold - Retail

Invt Trans - Interstore Sold - Units



Invt Trans - POS Inventory Markdown - Cost POS Markdown Cost

Invt Trans - POS Inventory Markdown - Retail POS Markdown Retail

Invt Trans - POS Inventory Markdown - Units POS Markdown Units

Invt Trans - Receive Inventory from Vendor - Cost Receiving Cost

Invt Trans - Receive Inventory from Vendor - Retail Receiving Retail

Invt Trans - Receive Inventory from Vendor - Units Receiving Units

Invt Trans - Cost Value Cost Value

Invt Trans - Retail Value Retail Value

Invt Trans - Units Units

WEEKLY INVENTORY

METRICS

Begin of Period On Hand - Cost Value Cost Value at the beginning of the selected time period (lowest level of Fiscal Week)

Begin of Period On Hand - Retail Value Retail Value at the beginning of the selected time period (lowest level of Fiscal Week)

Begin of Period On Hand - Units On Hand Units at the beginning of the selected time period (lowest level of Fiscal Week)

End of Period On Hand - Cost Value Cost Value at the ending of the selected time period (lowest level of Fiscal Week)

End of Period On Hand - Retail Value Retail Value at the ending of the selected time period (lowest level of Fiscal Week)

End of Period On Hand - Units On Hand Units at the ending of the selected time period (lowest level of Fiscal Week)

Weeks GMROI Calculated GMROI for the defined time period (lowest level of Fiscal Week)

Weeks Inventory Turns Calculated Inventory Turns for the defined time period (lowest level of Fiscal Week)

Weeks Sell Thru Calculated Sell Thru for the defined time period (lowest level of Fiscal Week)

Weeks Supply Calculated Weeks Supply for the defined time period (lowest level of Fiscal Week)

PURCHASE ORDERS

PO Cost Cost on PO

PO Ordered Cost PO Ordered Cost

PO Ordered Price PO Ordered Price

PO Price PO Price

PO Quantity Ordered PO quantity ordered

PO Quantity Received PO quantity received

PO Received Cost Received Cost

PO Received Price Received Price

SALES

Sales LY Period to Date Metrics (MTD / QTD / WTD / YTD - COGS, Retail + Units)

LY (Last Year) will provide the data for one year ago based off the time period defined

Sales Period to Date Metrics (MTD / QTD / WTD / YTD - COGS, Retail + Units)

Period to Date will provide the data for the current time period defined

Sales Prior Period to Date Metrics (MTD / QTD / WTD / YTD - COGS, Retail + Units)

Prior to Date will provide the data for one period prior to the time period defined

Sales - BO Markdown Back office markdowns for the defined time period



Sales - COGS Cost of goods sold for the defined time period

Sales - Item Unit Price Item unit price for the defined time period

Sales - Mkdn Markdown for the defined time period

Sales - Mkdn % Markdown % for the defined time period

Sales - POS Mkdn POS markdown for the defined time period

Sales - Profit Profit for the defined time period

Sales - Profit Margin Profit margin for the defined time period

Sales - Retail Retail sales for the defined time period

Sales - Retail with No Mkdns Retail sales with no markdown for the defined time period

Sales - Retail with No POS Mkdn Retail sales with no POS markdown for the defined time period

Sales - Store Price Store price

Sales - Sugg Price Suggested price

Sales - Units Quantity sold for the defined time period

Count Receiptlines Number of receipts entered during the defined time period

Sales - Avg Unit Price Per Line Item Average unit price per line item for the defined time period



PRODUCTION REPORTS:

Accounting: Promotions:

Monthly Ledger Detail Discounts by Employee

Weekly Ledger Detail Discounts by Employee (alternate view)

Manual Discounts Reasons Report

Customer / CRM: Manual Discounts (by salesperson)

Sales by Zip by Dept

Purchase Orders:

Inventory: Monthly Cost & Retail by Store

BOY Cost Value - YOY On Order Report by Brand

Current Inventory – Dept / Size On Order Report by Vendor

Current Inventory – Dept / Size (by Region)

Current Inventory – Dept / Size (by Store) Sales:

Current Invt Value – Brand/Dept/Store Daily Sales and Tax Dollars by Department

Inventory Analysis by Type – Month Sales by Customer Type

Inventory Analysis by Type – Week Sales by Day of Week (TY/LY)

Inventory Unit Sales – Last 12 Weeks Sales by Hour by Salesperson

Inventory Unit Sales – Last 6 Months Sales by Salesperson by Hour

Inventory Unit Sales – Last 6 Months (Type) Sales by Salesperson by Store Ranked

Invt Qty by Size and Color – Type/Subtype (Sales YTD) Sales by Salesperson Ranked

Invt Qty by Size – Dept/Type/Subtype (Date Range) Sales by Time of Day TY/LY

Price List by Brand Same Store Sales YOY

Price List by Store Store Sales by Ranking

Top 10 Stores

Merchandising: Top 10 Stores (Last 3 Years)

Current On Hand, Last Month Sold Top 20 Stores (Last 3 Years)

Department – Type (YOY Compare) Top 25 Products – Dept/Type

Department TW/LW Sell-Thru Top Stores TY

Inventory Retail Sales (Last 12 Weeks) TYLY Store Sales

Inventory Retail Sales (Last 6 Months) Units Sold by Store Report (Across)

Invt and Sales/Mkdn – Dept/Type (Date Range) Units Sold by Store Report (Page By)

Invt and Sales/Mkdn – Dept/Type (MTD) Week Sales – WK Desc (Graph)

Invt and Sales/Mkdn – Dept/Type (YTD)

MTD Sales OH%

On Hand, Sold, On Order

On Hand, Sold, On Order – Style

Sales Last 4 Weeks

Turns by Week TY


APPENDIX B:

MICROSTRATEGY DATA WAREHOUSING USER LICENSE CHART:

Consumer/Web Reporter - Provides a Web browser interface to run, view, print, and export reports and scorecards, personalized reports through prompts, drill down, sort data, choose grid or graph format, and schedule to receive reports via email, file, or printer.

Analyst/Web Analyst - Provides a Web browser interface with the Consumer/Web Reporter capabilities as well as to perform investigative analysis, drill anywhere, edit totals, pivot reports, hide to or unhide fields from a report, and create derived metrics.

Power User/Web Professional - Provides a Web browser interface with the Consumer/Web Reporter and Analyst/Web Analyst capabilities as well as to perform advanced formatting, create calculations, design scorecards, dashboards, and operational reports using the MicroStategy Design Mode.

CLASSIFICATION MICROSTRATEGY DATA WAREHOUSING FEATURES CONSUMER/

WEB REPORTER

ANALYST/ WEB ANALYST

POWER USER/ WEB

PROFESSIONAL

INTELLIGENCE SERVER PRODUCTS

Intelligence Server Universal Option (Basic Server Engine)* X X X

Distribution Services (E-Mail Distribution of Reports)** X X X

Report Services (Reporting Engine)*** X X X

Intelligence Server Module X X X

Web Reporter Module X X X

Web Universal Option X X X

OLAP Services (Additional Analytic Tools)**** X X

Web Analyst Option X X

Web Professional Option

X

REPORTING

Create Folder for Saved Reports X X X

Generate Pre-Defined Reports X X X

Answer Pre-Defined Prompts X X X

Display Report in Grid Format X X X

Display Report in Graph Format X X X

Display Report in Grid/Graph Format X X X

Print Reports X X X

Export Reports to Excel X X X

Export Reports to PDF X X X

Display Report in Full Screen Mode X X X



Email Reports X X X

Copy Existing Reports X X

Save Existing Reports with Modifications X X

Create Limited Ad Hoc Queries Through Report Builder X X

Move Existing Reports X

Delete Existing Reports X

Rename/Edit Existing Reports X

Create Documents X

Convert Report to Document X

Create Prompts/Filters/Custom Groups X

Create New Reports X

Edit Reports through Design Mode X

TOOLS

Schedule Report Delivery to History List X X X

Maintain History List (Remove from List, Rename) X X X

Maintain Subscription List (Edit Options, Unsubscribe) X X X

Add Notes to a Report X X X

View/Run Related Reports X X X

View/Select Existing Page-By X X X

View Limited Report Details X X X

Define/Maintain Email Subscriptions X X X

Set Email Notification Alerts on Reports X X

Add Report to History List X X

Edit Report Notes X X

View Advanced Report Details X X

Display/Add Current View Filters X X

View/Use Pivot Buttons X X

Move Columns to Page-By X X

Filter on Selections X X

Display/Add Report Filters (Prior to Report Execution) X

DATA

Toggle Defined Thresholds X X X

Toggle Display of Attribute Form Names X X X

Utilize Outline Capabilities X X X

Drill-In Pre-Defined Hierarchies X X X

View Report Objects X X



Hide/Unhide Report Objects X X

Insert New Calculated Metrics from Report Metrics X X

Rename/Edit Displayed Report Objects on View X X

Select Displayed Attribute Forms X X

Show/Edit Totals X X

Use Visual Thresholds X X

Drill-Across Pre-Defined Hierarchies X X

Insert New Metrics with Ranking X X

Filter on Top Number X X

View All Available Objects X

Add/Remove All Available Objects X

Utilize Advanced Threshold Editor X

Add/Remove Attribute/Metrics from Report (Not just Grid) X

Edit Links to other Reports X

Edit Attribute Forms X

FORMATTING

Sort by Column/Row X X X

Edit Color Scheme X X X

Apply Banding X X X

Merge Column/Row Headers X X X

Lock Column/Row Headers X X X

Auto Fit Context X X X

Swap Columns/Rows X X

Utilize General Formatting (Type - $, %, Date, etc.) X X

Move Columns/Rows X X

General Graph Formatting X X

Selection of Graph Type (Pie, Bar, etc.) X X

Advanced Formatting of Reports (Alignment, Font, etc.) X

Advanced Graph Formatting (Number Formatting, Axis, etc.) X

*Intelligence Server - Provides a scalable, secure, robust platform for the core data access, analytical processing, and job management for all BI applications. **Distribution Services - Provides a proactive information delivery server that distributes personalized business information to users via email, printers, file services, SMS, and mobile

devices.

***Report Services - Provides the enterprise reporting engine for scorecards, dashboards, and operational reports in a Pixel-Perfect™ format.

****OLAP Services - Provides an analytic extension to Intelligence Server's OLAP capabilities through the use of Intelligent Cubes™.



APPENDIX C:

Data Warehousing Drilling Hierarchies

>>>

Dri

ll-A

cro

ss <

<<

>>> Drill-In >>> Customer Geography

> Customer Country

> Customer State or Province Code

> Customer City > Customer Zip Code

> Customer

Fiscal Transaction Date

> Fiscal Year > Fiscal Quarter > Fiscal Month > Fiscal Week > Fiscal Day

Inventory Store Geography

> Inventory Store Country

> Inventory Store State or Province Code

> Inventory Store City

> Inventory Store Zip Code

> Inventory Store

Product Brand Style

> Brand > Style > Product

Product Taxonomy > Department > Type > Subtype1 > Subtype2 > Subtype3 > Product

Promotion > Promotion Type > Promotion

Sales Markdown Percentage

> Ten Range > Five Range > Percent

Sales Person Geography

> Sales Person Country

> Sales Person State or Province Code

> Sales Person City

> Sales Person Zip Code

> Sales Person

Sales Store Geography

> Sales Store Country

> Sales Store State or Province Code

> Sales Store City

> Sales Store Zip Code

> Sales Store

Sales Time of Day > Sales AM PM > Sales Hour > Sales Time of Day

Sales Time of Day > Sales Hour > Sales Time of Day