Metric Studio: Time Periods Stage File (.cal)

Home

Library

Main Menu

Member Menu (Login Required)

Countries

50.1%		United States
7.6%		India
7%		United Kingdom
5.1%		Australia
4.8%		Canada

Visitors

Today:	39
Yesterday:	573
This Week:	39
Last Week:	3348
This Month:	9424
Last Month:	15365
Total:	383511

Metric Studio: Time Periods Stage File (.cal)

(0 votes, average 0 out of 5)

Monday, 21 March 2011 14:56

The time_periods_stage file is used to load time periods into your custom calendar.

Ensure that your custom calendar includes only complete years because you cannot add periods to a partial fiscal year.

Time periods cannot overlap. Ranges defined by the start_time_cd and end_time_cd must be unique by level and mutually exclusive. However, gaps between time periods are allowed.

The summarization of time periods in one level to time periods in a higher level is expressed as a set of parent-child relationships. These relationships are defined by including the start_time_cd of the child in the start_time_cd to end_time_cd range of the parent.

Level_id and start_time_cd uniquely identify each period.

The time periods stage file loads the time_period_stage table. The columns in the time periods stage file are as follows.

No.	Column	Description
1	level_id	The code corresponding to the time granularity. Must match the level_id defined in the time_levels (.lvl) file. Required
2	start_time_cd	The calendar-based started date for the specified period. Value: yyyy-mm-dd hh:mm:ss (24-hour clock) Required
3	end_time_cd	The calendar-based end date for the specified period. Value: yyyy-mm-dd hh:mm:ss (24-hour clock) The end_time_cd value must be specified as the last minute of a time period. For example, 2005-01-01 23:59:00. Required
4	fiscal_year_value	The fiscal year to which a period belongs. The fiscal_year_value overrides the Metric Studio default behavior. Metric Studio uses the first time period provided with the earliest start_time_cd to derive the fiscal year values. Optional
5	period_number	The order within a parent level. For example, the period_number is 12 if it is the last month in a monthly calendar with year as the parent level. Must be unique and sequential within each parent level. Value: Depends on the defined calendar. For example, 1 to 52+ for a weekly custom calendar. The period_number overrides the Metric Studio default behavior. If period_number is not provided, Metric Studio assigns period_number based on start_time_cd order. Optional
6	language_text_id	The external object identifier for a period name. The language_text_id is used as the default period name if no period is provided in the time language text file.
7	created_dt	The date the object was created. Format: yyyy-mm-dd hh:mm:ss (24-hour clock) (hh:mm:ss values are optional) Required

Source: Metric Studio User Guide 8.4.1

www.cogknowhow.com

Login

CogKnowHow Newsletter

Polls

How many users are working on your Cognos environment?

	1 - 100 users
	101 - 250 users
	251 - 500 users
	501 - 1000 users
	1000 or more users