Application Server Tier Type Libraries

After an HsvSession object is instantiated, the client can initiate tasks such as consolidations, data entry, and so on. When a task runs, subordinate objects of the HsvSession object are used on the application server tier.

The following table lists the type libraries that contain these subordinate objects and the features to which the libraries correspond.

Table 1. Features Exposed by HsvSession’s Subordinate Objects

Type Library

Corresponding Features

HsvMetadata

Metadata for an application; used to get dimension member properties.

HsvData

Data in an application; used to get and set data.

HsvCalculate

Calculations, consolidations, and translations.

HsvJournals

Journal-related features of Financial Management.

HsvSecurityAccess

Security definition features of Financial Management.

HsvSystemInfo

Various features; used to get and set application names, get the application server name, and get and set other system-related information.

HsvProcessFlow

Process Management-related features of Financial Management.

HsvReports

Reporting-related features of Financial Management.

HsvICM

Intercompany transaction features of Financial Management.

HsvMDArrays

Provides helper methods for working with data, transaction data generated by statutory consolidations, and intercompany transactions.

HsvDataCubes

Provides access to data at the subcube level. This library’s objects are subordinate to the HsvData object.

Note:

The objects in these type libraries are introduced in About the Type Libraries and Objects. The chapter includes a brief description of each object’s properties and methods.

The following figure illustrates the relationship between the application server type libraries.

Type Library Relationships—Application Server Libraries

Note:

The HsvMDArrays type library is not directly related to these objects. The type library provides various helper methods, but technically is not a branch of the hierarchy pictured above. Also, the HsvStarSchemaACM library is omitted from the diagram because the HsvStarSchemaACM object is not a child of the HsvSession object; instead, HsvStarSchemaACM instances are associated with HsvSession instances using HsvStarSchemaACM.SetSession.