Financial views

Security
Built-in filters

Financial views help you create dynamic financial statements that you can view in the HD view or generate in report form for deeper analysis of your financial data. Each financial view can be filtered by calendar, by year, and by period and you can include or exclude unmerged entries which are not on hold. Views which explicitly include account numbers can also be filtered by account number.

Planning is vital to a great financial view. AccountingWare suggests that you design the financial view on paper before undertaking the design in ActivityHD. You may be able to use existing rollups to group information for financial reports, or you may need to create new rollups.

The rows in a financial view can report over all accounts in the chart of accounts or over specified segments and/or rollups. The columns in a financial view are defined by choosing a column name, financial view function, and depending on the function selected, by specifying an items expression.

How the financial view is defined determines what information is available for financial reports based on the financial view.

The following image shows a sample financial view in the HD view:

Click here to view a table comparing financial views and financial designs.

A financial view defined on only one segment or one rollup is called a single-item financial view. While other financial views are limited to the items that appear in the chart of accounts, single-item financial views can show segment items or rollup items before the chart of accounts is modified to include them.

Extras\General Ledger\Trial Balance Financial View.xml
×

Financial views security

Common accesses available on financial views

Access A user with this access can...
Change Use the mass change action on financial views.
Custom Fields Create and edit custom fields for financial views.
Data Have read-only access to financial views from anywhere in the software (e.g., field validations, filters, date expressions).
Delete Delete financial views.
Edit Edit financial views records.
Export Export financial views records from ActivityHD.
Import Import financial views records into ActivityHD.
New Create new financial views records.
Read Have read-only access to financial views records.
Report Run reports with financial views information.
Report Designs Create and edit report designs with financial views information. This access enables the Report Designs button on the Output tab of report dialogs.
Shared Answers Create and edit action profiles and report profiles related to financial views.
Shared Filters Create and edit shared filters on financial views.
Visible View the Financial Views folder in the Navigation pane.

Special accesses available on financial views

Access A user with this access can...
Activate Activate a financial view. Its folder becomes visible in the Navigation pane.

 

×

Financial views filters

The following built-in filters are available for financial views:

Filter Name Effect
Active Financial Views Lists active financial views only.
Inactive Financial Views Lists inactive financial views only.

 

×

Financial designs and financial views compared

  Financial Designs Financial Views
Structure Financial statement. Loads data into an Excel spreadsheet with cell locations the user predefines to hold totals such as assets, liability, equity, revenue, and expenses, as well as other values. Financial report. Loads data into the HD view of a special ActivityHD folder. The columns in the HD view are based on financial functions; the rows correspond to the segments and rollups selected for reporting. Useful for interactive investigation. Provides data for dynamic reporting of sections of the chart of accounts. The data in this "view" can also be fashioned into a financial report.
Flexibility Freeform Tabular
Setup Tool MS Excel Financial View edit window
Viewing Tool MS Excel ActivityHD folder
Reporting Tool MS Excel Crystal Reports
Financial Functions Similar (Balance, Activity, etc.) Similar (Balance, Activity, etc.)
Period Expressions Similar (Current - 1, etc.) Similar (Current - 1, etc.)
Other Functions Excel functions Crystal Reports functions

 

×

Account Conditions

Condition Expression

If the account mask you specified in the field that accompanies the Condition field is too broad or too narrow to capture the accounts you need, enter a SQL condition statement here to exclude or include accounts. Accounts are included which satisfy both the condition and the account mask.

If you entered a condition in the underlying field, it is carried over into this text box.

Alternatively, you can use the table below to describe the conditions you need and ActivityHD will build and add the conditions to this text box.

Conditions table
Use this table to construct the conditions you need in order to accurately select accounts.
Item
From the drop-down list, select the account, segment, rollup, or attribute to define a range or mask on.
Mask
Enter a mask for the account number, segment item, rollup item, or attribute item when the items you need to select have common characters but are not in a particular order.
Begin
Enter the first account number, segment item, rollup item, or attribute item in the range of items you need to select. Use a range when the items are in a defined order.
End
Enter the last account number, segment item, rollup item, or attribute item in the range of items you need to select. Use a range when the items are in a defined order.
Check Conditions button
Click this button to check for SQL errors in the condition statement.

 

×

Fully qualified naming convention

When specifying arguments in conditional expressions, it is important to eliminate any ambiguity so that ActivityHD can correctly evaluate the expressions. To do this, we refer to the element we are specifying a condition on by its fully qualified name. In general, the fully qualified name has the following form:

<Two-character package ID>.<entity name>.<item name>

Ambiguity can arise in a couple of ways:

  • If you have a GL segment named "Account", it can conflict with the GL account entity. In order to eliminate the ambiguity, refer to the account entity as GL.Account and to the segment as GL.Segment.Account.
  • If you are using financial functions which are not GL-specific, you may need to distinguish segment/rollup names from attribute names, or from entity names from other packages. If a segment/rollup name is the same as the attribute or entity name, an ambiguity can occur.

    Example

    POAmountYTD is a function that is not GL-specific. Suppose you have a GL segment named "Dept" and an attribute with PO usage named "Dept". To distinguish between them in the arguments of the POAmountYTD function, specify GL.Segment.Dept or GL.Attribute.Dept.

    Fully-qualified names are not necessary for GL-specific functions such as Activity, Balance, YearToDate, etc.; however, there's no harm in using them.

    When the GL segment or rollup name is the same as the... GL segment or rollup name format Subsidiary item name format
    Payroll employee code

    GL.Segment.<segment name>

    GL.Rollup.<rollup name>

    PR.Employee.<employee code>
    Payroll PRCode

    GL.Segment.<segment name>

    GL.Rollup.<rollup name>

    PR.PRCode.<PRCode name>
    Payroll segment item

    GL.Segment.<segment name>

    GL.Rollup.<rollup name>

    PR.Segment.<segment item name>
    Attribute name when attribute has Payroll usage

    GL.Segment.<segment name>

    GL.Rollup.<rollup name>

    GL.Attribute.<attribute name>
    Purchasing department

    GL.Segment.<segment name>

    GL.Rollup.<rollup name>

    PO.Department.<department name>
    Purchasing product

    GL.Segment.<segment name>

    GL.Rollup.<rollup name>

    PO.Product.<product name>
    Purchasing unit of measure

    GL.Segment.<segment name>

    GL.Rollup.<rollup name>

    PO.UnitOfMeasure.<unit of measure name>
    Purchasing vendor

    GL.Segment.<segment name>

    GL.Rollup.<rollup name>

    PO.Vendor.<vendor name>
    Attribute name when attribute has PO usage

    GL.Segment.<segment name>

    GL.Rollup.<rollup name>

    GL.Attribute.<attribute name>

 

×

Financial View Column Arguments

Depending on the function selected, none, one, or a combination of the following argument types may be prompted for.

Period Expression
Enter a period expression to describe the reporting period. Period expressions are optional arguments.

Items Expression

Enter a conditional expression to describe the information to include. The conditions you can apply depend on the function selected. If you selected a General Ledger function, you can define conditions based on account numbers, segment items, or rollup items. If you selected a Purchasing function, you can define conditions based on any of the General Ledger options plus departments, products, units of measure, vendors, or attributes with PO usage. If you selected a Payroll function, you can define conditions based on any of the General Ledger options plus employees, PRCodes, payroll segment items, or attributes with employee and/or distribution usage. In general terms, conditional expressions allow you to limit information by any available attribute that makes sense in the context of the selected function.

Example

Consider the PRExpense function. Any expression used to limit the PRExpense function can limit by any attribute within the context of PRExpense. Since the PRExpense function summarizes check distributions, the attributes available to limit by include GL segments, GL rollups, employees, payroll segments, employee attributes (and rollups), and distribution attributes (and rollups).

When writing conditional expressions it is important to avoid ambiguity in identifying the item you want ActivityHD to evaluate. When ambiguity is possible, you should fully qualify the item name.

Examples

To distinguish the GL account entity from a GL segment named "Account", use "GL.Account" for the entity and "GL.Segment.Account" for the segment.

If you have a GL segment named "Dept" and an attribute with PO usage named "Dept", either or both could be referred to in the context of the POAmountYTD function. To resolve the ambiguity, use "GL.Segment.Dept" for the GL segment and "GL.Attribute.Dept" for the attribute.

Items expressions are optional arguments.

Press F2 to open the Account Conditions dialog box where you can build and verify a conditional statement.


Custom Field

Select the name of the custom field for which to include information. Custom fields are required arguments.

Press F3 to look up the value.


Segment
From the drop-down list, select the GL segment for which to include information. Segments are required arguments.
×

Account Conditions

Condition Expression

Enter a SQL condition statement here to exclude or include information from the financial view. Alternatively, you can use the table below to describe the conditions you need and ActivityHD will build and add the conditions to this text box.

Conditions table
Use this table to construct the conditions you need in order to accurately select information for the financial view.
Item
From the drop-down list, select the account entity, or the segment, rollup, attribute, department, product, unit of measure, vendor, employee, or PRCode to define a range or mask on. The items in the dropdown are filtered based on the selected function and are represented by their fully qualified names.
Mask

Enter a mask for the selected item values when the values you need to select have common characters but are not in a particular order.

Press F3 to look up the value.

If a value is already selected, you can press F4 to open the record in its native editor.

Begin

Enter the first value in the range of item values you need to select. Use a range when the values are in a defined order.

Press F3 to look up the value.

If a value is already selected, you can press F4 to open the record in its native editor.

End

Enter the last value in the range of item values you need to select. Use a range when the values are in a defined order.

Press F3 to look up the value.

If a value is already selected, you can press F4 to open the record in its native editor.

Check Conditions button
Click this button to check for SQL errors in the condition statement.

 

 

×

Report Email dialog

From
The email account from which to send the email. Valid options are:
  • Windows user default account. Sends email using the user's Windows default email account. For most users, this is the account configured in Outlook or another email client application.
  • Server personal. Sends email using the email configuration for the system or company server and the email address on the current user's authorized user record. The authorized user record must have a confirmed email address.
  • Server generic. Sends email using the email configuration and "from" address for the system or company server. This option requires "Send generic" access to the Server Email resource.
To
The email address(es) to which to send the email. Separate email addresses with semi-colons.
CC
The email addresses to copy on the email. Separate email addresses with semi-colons.
BCC
The email addresses to blind copy on the email. Separate email addresses with semi-colons.
Subject
The subject line.
Text box
The body of the email.