Creating Functions Manually

See Microsoft documentation and support site for information about character and other Excel function limitations.

To create a function manually:

  1. In Excel, click the cell in which you want to enter the function.
  2. Enter an equals sign (=).
  3. Enter the function name; for example, enter HsSetValue
  4. Enter parameters for the function according to rules described in Example 25-1, using the information specific to each function in Function Descriptions.
  5. To refresh the worksheet, from the Oracle Smart View for Office menu, select Refresh.

    Functions are validated only when you refresh them.

Example 25-1 Syntax Guidelines

See Function Descriptions for the syntax of individual functions.

  • To work with a shared connection, you must add to the function the WSFN identifier, which specifies a workspace function, along with a connection string. The format is:

    "WSFN|ProviderType|Server|Application|Database","POV"

    For example, in the HsGetValue function for a shared connection to an Oracle Essbase data source, the WSFN identifier and connection string is added to the function as follows:

    =HsGetValue("WSFN|Essbase|myserver|Sample|Basic","Market#South")

    For ProviderType , use one of the following case-sensitive strings:

    • Essbase (for Essbase on-premises only; Oracle Analytics Cloud - Essbase requires private connection syntax)

    • HFM (for Oracle Hyperion Financial Management)

    • HP (for Oracle Hyperion Planning, Planning, Planning Modules, Financial Consolidation and Close, Tax Reporting)

    For Financial Management, the Database parameter can be omitted, or it can be the same as the Application parameter. For consistency, Oracle recommends entering the application name for the Database parameter.

  • Private connection parameters can have these values:

    • Empty: the default connection

    • HsActive: the active associated connection

    • The user-defined name for a private connection

    If you specify a private connection, it must precede the POV.

  • The POV is composed of dimension#member pairs, for example:

    Entity#Connecticut
  • Parent-child relationships are designated by a period, (.); for example:

    Entity#UnitedStates.Maine
  • The connection and each POV dimension#member pair can be split into separate function parameters, each parameter enclosed in quotation marks, ("), and separated by a comma, (,); for example:

    "My_connection","Entity#UnitedStates","Account#Sales"

    Alternatively, the connection can be separated from the POV by a comma, (,), with the entire POV enclosed in quotation marks, ("), and with each dimension#member pair separated by semicolon, (;); for example:

    "My_connection","Entity#UnitedStates;Account#Sales"
  • Do not mix a dimension name and its aliases in functions. However, for members, you can either use the member name or its alias from the selected alias table.