General Application Notes

· Describe the effect of activating or deactivating application options such as account for lock, journal or server options.

Option	Effect
Driver	Controls the type of database used. Hyperion Enterprise databases can be file or SQL based.
Application Calendar	Controls the calendar file used. Calendar files determine the periods applications store data for.
Error Log Options	Controls error log behaviour. Append Current Session to Log appends the current sessions error log to the last sessions error log. Erase Previous Session from Log erases the error log each time you exit Hyperion Enterprise.
Ownership by Period and Category	Controls whether each period and category combination can have different organization structures.
Periodic Consolidation	Controls whether the calculation of Consolidation methods and Translation methods is periodic or category to date. The calculation of Chart methods is controlled by the data view of the category.
Input Shares	Controls whether shares are input as units or percentages.
Consolidation Detail	Controls what consolidation detail is stored.
Use Statutory Consolidation Engine (ACE)	Controls whether the Statutory Consolidation Engine is used.
Share Subaccount Signatures	Controls whether subaccounts with the same id in different tables share attributes.
Use Child Rate Accounts	Controls whether non-global exchanges rates can be used.
Impact Future Categories	Controls whether changes to a prior linked category impact periods in the current category.
Number Journals Automatically	Controls whether journals are automatically numbered.
Application Load Optimization	Optionally set the number of accounts, entities, categories, and reports in an application. If set allows the system to optimise the first loading of application elements from the configuration files.

· Describe the attributes of the Load.per file.

Calendar files specify the periods of time that applications store financial data for. Hyperion Enterprise 5 has 13 standard calendar files which define the number of days, weeks, months, quarters, trimesters, and half-years within a year. In the standard calendar files, a year has 260 workdays, 52 weeks, 12 months, 4 quarters, 3 trimesters, and 2 half-years.

Calendar files are separated into frequency sections. Each frequency section begins with a header that defines the frequency. Beneath the frequency header are the definitions for each period within the frequency. The frequency sections appear in order from the frequency with the most periods per year to the frequency with the fewest periods per year.

· Describe the effect of actions such as account moves (shared signatures) and period changes (org by period).

See Accounts and Entities sections.

· Identify where various .INI files (e.g. REPENG, HYPENT, RW, HPADDONS) are located.

File	Location	Purpose
REPENG.INI	C:\Windows	Hyperion Reporting configuration file.
HYPENT.INI	C:\Windows	Hyperion Enterprise configuration file.
RW32.INI	C:\Windows	Hyperion Reporting recent files list.
HPADDONS.INI	C:\Windows	Hyperion Addons (ACE, Allocations and LedgerLink) configuration file.

· Describe why an .INI file setting would cause the issue presented in the exhibit. Given a problem situation, identify the .INI file setting to change to correct the problem. Identify and describe the settings in the [DEFAULT] section of HYPENT.INI and their effects on Hyperion Enterprise applications.

Setting	Description	Effect
AppID	Application ID	Application you want to open when you use Hyperion Enterprise. If you do not specify a application you select an application each time you start Hyperion Enterprise.
UserID	User ID	Default user ID for Hyperion Enterprise. If you do not specify a default user the User ID field is blank when you start Hyperion Enterprise.
HPDRVn	Hyperion Driver	The .DLL files for database drivers.
HPDRVCNT	Hyperion Driver Count	The number of database drivers on the machine.
AppDefPath	Application Default Path	Default application path different if you do not want to store your applications in the program directory.

· Describe the record layout, the order of the sections and how to use system load and extract to do system maintenance.

Application extract/load files are split into sections that start with a keyword in square brackets, for example [CODES]. Each line in the section is a record and the default delimiter for fields is an exclamation mark.

· Describe what the Conversion Utility does.

The conversion utility is used to convert Hyperion Enterprise SE applications to Hyperion Enterprise v5 applications.

· Describe Common Logon.

Hyperion Common Logon loads automatically when you open a Hyperion application that supports Hyperion Common Logon. Once you enter your Hyperion user ID and password, you can launch successive Hyperion applications without logging on again. When Hyperion Common Logon is loaded, either a system tray icon (Windows 95/NT) or desktop icon (Windows NT 3.11) is displayed. To access the Hyperion Common Logon menu, position the cursor over the Hyperion Common Logon system tray icon or desktop icon and single-click the right mouse button.

· Describe what directory rights are needed for successful network installation of Hyperion Enterprise.

[]

· Describe the directory rights needed for successfully running Hyperion Enterprise applications on a network.

[]

· Describe what set-up options would need to be made (and the sequence) to install programs on a network and client workstation.

[]