Deltek 7.6 Vision Software Guide
Deltek Vision Software 7.6 is a comprehensive software solution that helps businesses manage projects, finances, and resources. The software is designed to provide a single platform for managing all aspects of a business, from project planning and execution to financial reporting and analysis.
Advertisement
Advertisement
Deltek Vision® 7.6
Custom Reports and Microsoft SQL Server®
Reporting Services
July 29, 2016
While Deltek has attempted to verify that the information in this document is accurate and complete, some typographical or technical errors may exist. The recipient of this document is solely responsible for all decisions relating to or use of the information provided herein.
The information contained in this publication is effective as of the publication date below and is subject to change without notice.
This publication contains proprietary information that is protected by copyright. All rights are reserved. No part of this document may be reproduced or transmitted in any form or by any means, electronic or mechanical, or translated into another language, without the prior written consent of Deltek, Inc.
This edition published July 2016.
© Deltek, Inc.
Deltek’s software is also protected by copyright law and constitutes valuable confidential and proprietary information of Deltek, Inc. and its licensors. The Deltek software, and all related documentation, is provided for use only in accordance with the terms of the license agreement.
Unauthorized reproduction or distribution of the program or any portion thereof could result in severe civil or criminal penalties.
All trademarks are the property of their respective owners.
Custom Reports and Microsoft SQL Server® Reporting
Services ii
Contents
Reporting Services Report Writing Tools ............................................... 7
Custom Reports Created with Microsoft SQL Server Reporting Services 2005 and 2008 ........... 34
Upgrade Custom Reports Saved in the Vision Database Using Report Administrator ............ 37
Custom Invoices Created with Microsoft SQL Server Reporting Services 2005 and 2008 .......... 42
Custom Reports and Microsoft SQL Server® Reporting Services iii
Custom Reports and Microsoft SQL Server® Reporting Services iv
Overview
Overview
Standard reports that are provided with the Deltek Vision software are designed to meet most of your business needs. In addition, you can use Microsoft SQL Server
®
Reporting Services (SSRS) and its report writing tools to create Vision custom reports.
With SSRS's Report Builder or SQL Server Data Tools – Business Intelligence Report Designer
(also known as SSDT-BI Report Designer), you can create custom reports using Vision's report model or report templates. You can also open a copy of a Vision standard report in SSDT-BI
Report Designer and modify it to create a custom report.
This guide does not apply if you use Deltek First Vision Essentials, the cloud-based edition of the Vision software. If you use Vision Essentials and you would like to create custom reports, contact your Deltek partner or Deltek Global Services at [email protected]
for assistance.
What This Guide Covers
This guide provides information for the following tasks that are necessary to create, deliver, and generate Vision custom reports:
Task Description
6
7
8
1
2
3
4
5
9
Decide which report writing tool to use to create custom reports.
Install the required SSRS report writing software.
Give the appropriate users who will create custom reports access to SSRS and its report writing software.
Load the Vision report model into SSRS. Report models are used when you create custom reports with Report Builder.
Load the Vision report templates on the workstations of the appropriate users who will create custom reports with SSDT-BI Report Designer.
Access the Vision report model in Report Builder to create custom reports.
Access the Vision report templates in SSDT-BI Report Designer to create custom reports.
Create a custom report from a copy of a Vision standard report in SSDT-BI
Report Designer.
Save custom reports to the appropriate folder on your application server.
Load custom reports into Vision via Vision Utility » Report Administration.
Set up parameters for a custom report in Vision Configuration » General » Custom
Report Options.
In Vision Role Security Configuration, set up access rights to give the appropriate
Vision users the ability to generate and print specific custom reports from the Vision
Reporting menu.
Custom Reports and Microsoft SQL Server® Reporting Services 1
Overview
Task Description
10 From the Vision Reporting menu, select a custom report, choose options, generate the report, and then preview and print it.
This guide also provides:
Descriptions of the Vision fields that are available in the report models from which you create custom reports with Report Builder.
Custom report upgrading information if upgrading is required for a release.
Specific instruction on how to create and design Vision custom reports is beyond the scope of this document. For detailed information and training on how to design a Vision report with the supported versions of Report Builder or SSDT-BI Report Designer, Deltek offers report writing classes through Deltek University. See http://www.deltek.com/services/deltekuniversity for class offerings.
Deltek Global Services provides assistance with custom reports. Contact them for more information about the services that they provide. Assistance to create custom reports is not covered by your Vision Ongoing Support Plan (OSP).
Updates to This Guide
Deltek revises documents regularly to provide the most up-to-date technical information and instructions. Visit the Knowledge Center at the Deltek Customer Care Connect site, https://support.deltek.com
, to determine whether or not your copy is the latest copy and to download the most recent copy if necessary.
Adding Custom Notes to This Guide
If you would like to add custom notes to this guide that are specific to your company, Adobe
®
Reader
®
X or greater provides this ability. If you do not already use Adobe Reader, you can download it here free from Adobe.
To add a custom note using Adobe Reader, complete the following steps:
1. On the Reader toolbar, click Comment at the far right.
2. In the Annotations pane that displays, click match the button.
Sticky Note. The cursor changes to
3. Position the cursor at the location in the guide where you want the note to appear, and click. A note icon is inserted at the location and a text box pops up.
4. Enter your information in the text box.
5. Continue adding notes as needed.
6. Save the document.
Deltek recommends that you save the document to a slightly different filename so as to keep the original file from being overwritten.
When you read the document, cursor over a note icon to see the information. Double-click a note icon to edit the information.
Custom Reports and Microsoft SQL Server® Reporting Services 2
If You Need Assistance
If You Need Assistance
If you need assistance installing, implementing, or using Vision, Deltek makes a wealth of information and expertise readily available to you.
Customer Services
For over 20 years, Deltek has maintained close relationships with client firms, helping with their problems, listening to their needs, and getting to know their individual business environments. A full range of customer services has grown out of this close contact, including the following:
Extensive self-support options through the Customer Care Connect Web portal.
Phone and email support from Customer Care analysts
Technical services
Consulting services
Custom programming
Classroom, on-site, and Web-based training
Find out more about these and other services from the Customer Care Connect site.
Customer Care Connect Site
The Deltek Customer Care Connect site is a support Web portal for Deltek customers who purchase an Ongoing Support Plan (OSP).
The following are some of the many options you have at the Customer Care Connect site:
Download the latest versions of your Deltek products
Search Deltek’s knowledge base
Ask questions, exchange ideas, and share knowledge with other Deltek customers through the Deltek Connect Customer Forums
Display or download product information, such as release notes, user guides, technical information, and white papers
Submit a support case and check on its progress
Transfer requested files to a Customer Care analyst
Use Quick Chat to submit a question to a Customer Care analyst online
Subscribe to Deltek communications about your Deltek products and services
Receive alerts of new Deltek releases and hot fixes
If you need assistance using the Customer Care Connect site, the online help available on the site provides answers for most questions.
Custom Reports and Microsoft SQL Server® Reporting Services 3
If You Need Assistance
Access Customer Care Connect
To access the Customer Care Connect site, complete the following steps:
1. Go to https://support.deltek.com
.
2. Enter your Customer Care Connect Username and Password.
3. Click Log In.
If you do not have a username and password for the Customer Care Connect site, contact your firm’s Vision administrator.
If you forget your username or password, you can click the Account Assistance button on the login screen for help.
Custom Reports and Microsoft SQL Server® Reporting Services 4
Ways to Create Vision Custom Reports
Ways to Create Vision Custom Reports
Whether you use SSRS Report Builder or SSDT-BI Report Designer to create a custom report depends on your reporting needs and report writing skill level. The following table provides information to help you determine the reporting tool to use to create custom reports.
Skill Requirements and
Reporting Capabilities
Report Builder 3.0
Use the Vision Report Model
SSDT-BI 2013 Report
Designer
Use Vision Report
Templates or Start with a
Copy of a Standard
Vision Report
Skill Requirements:
Report writing tool skill level
Relational database structure knowledge required
Reporting Capabilities:
Basic
No
Create ad hoc reports Yes
Create table, matrix, and chart reports
Yes
Yes (at design time only) Apply grouping and formulas in reports
Apply sorting Yes
No
No
Apply filtering
Apply advanced reporting features, including complex queries, advanced charting, parameters, drill downs, subreports, and so on
Combine tables, lists, and charts in the same report
Include Vision user-defined fields in reports
No
No
Yes, with Deltek customization
Advanced
Yes
No
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Custom Reports and Microsoft SQL Server® Reporting Services 5
Ways to Create Vision Custom Reports
Skill Requirements and
Reporting Capabilities
Report Builder 3.0
Use the Vision Report Model
SSDT-BI 2013 Report
Designer
Use Vision Report
Templates or Start with a
Copy of a Standard
Vision Report
Include a Sorting/Grouping tab or Columns tab on the report
Options dialog box in Vision
Reporting for custom reports
No
Create a custom report
Options dialog box to display in Vision Reporting for a custom report
No
Yes, if you modify special tags in SQL statements.
No
Access the Vision database with the reporting tool
Launch the report writing application within Vision
You access only Vision fields that are contained in the report model.
Yes.
You can add Report Builder to the Vision Navigation menu.
You access the full Vision database.
No
Deploy custom reports outside of Vision
No No
Custom Reports and Microsoft SQL Server® Reporting Services 6
Software Requirements for Creating Custom Reports
Software Requirements for Creating Custom
Reports
Microsoft SQL Server
®
Reporting Services Report Writing Tools
The following are the Microsoft SQL Server Reporting Services (SSRS) report writing tools that are supported for creating Vision 7.6 custom reports:
Report Builder 3.0
SQL Server Data Tools - Business Intelligence for Visual Studio 2013 Report Designer
(known as SSDT-BI 2013 Report Designer)
The SSDT-BI version is different from the standard SSDT version. The SSDT version does not include the BI templates and is not supported.
These report writing tools come with SSRS versions 2008 R2, 2012 and 2014. The tools produce a report file with an RDL (report definition language) 2010 schema that Vision 7.6 requires.
Install these tools on the machines from which you will create or edit Vision custom reports.
These machines are typically workstations, rather than Vision web servers.
The following are not supported for creating Vision custom reports:
Report Builder 2.0
Report Builder 1.0
BIDS 2012, which is provided with SSRS 2012
BIDS 2008 R2, which is provided with SSRS 2008 R2
BIDS 2008, which is provided with SSRS 2008
BIDS 2005, which is provided with SSRS 2005
If you try to load a custom report into Vision that was created with an unsupported version of a
SSRS report writing tool, you will receive a “SQL Report Error loading report” error message.
To determine whether or not a custom report was created with a supported report writing tool and has the supported RDL schema, open an .RDL file for a custom report, and look at the header lines. If the report has the supported RDL 2010 schema, it will have 2010 in the path. If, instead, it has 2008 in the path, it was created with BIDS 2008 (not supported). The following are header line examples:
The header line in an .rdl report file that is created with SSDT-BI Report Designer
(supported) is:
<Report xmlns:rd=" http://schemas.microsoft.com/SQLServer/reporting/reportdesigner " xmlns=" http://schemas.microsoft.com/sqlserver/reporting/2010/01/reportdefinition ">
The header line in an .rdl report file that is created with BIDS 2008 (not supported) is:
<Report xmlns:rd=" http://schemas.microsoft.com/SQLServer/reporting/reportdesigner " xmlns=" http://schemas.microsoft.com/sqlserver/reporting/2008/01/reportdefinition ">
If your custom reports were previously created with the SSRS report writing tools that create an
RDL 2005 or RDL 2008 schema, you must upgrade the reports to the RDL 2010 schema. See the
Custom Reports and Microsoft SQL Server® Reporting Services 7
Software Requirements for Creating Custom Reports
Only the users who create custom reports need Report Builder or Report Designer installed on their machines. Vision users who only need to open, generate, and print custom reports (but not create them) do not need to install these report writing tools.
To support the ability to open, generate, and print custom Vision reports, the Vision database and report servers must have one of the supported or compatible versions of Microsoft SQL
Server installed. These include SQL Server 2014, SQL Server 2012, or SQL Server 2008 R2.
For a full list of Microsoft SQL Server releases (R), service packs (SP), and cumulative updates
(CU) that are supported or compatible with Vision, see the Deltek Product Support Compatibility
Matrix. You can download this PDF document at the Deltek Customer Care Connect site: https://support.deltek.com.
Supported Report Writing Tools and Installation Information
The following table provides more information about the installation of each of the SSRS report writing tools that are supported for creating Vision 7.6 custom reports:
Supported
Microsoft SSRS
Report Writing
Tool for Vision
7.6
Report Builder
3.0
Installation Information
You can get Report Builder 3.0 as a free, stand-alone download from the following Microsoft links:
For SQL Server 2014: http://www.microsoft.com/enus/download/details.aspx?id=42301
For SQL Server 2012: http://www.microsoft.com/enus/download/details.aspx?id=29072
For SQL Server 2008 R2: http://www.microsoft.com/enus/download/details.aspx?id=6116
Report Builder 3.0 comes with the installation of Microsoft SQL Server
2014, SQL Server 2012, or SQL Server 2008 R2 Reporting Services
(SSRS).
You must use the Workgroup, Standard, Business Intelligence, or
Enterprise edition because these editions support the use of report models, which are required to create Vision custom reports.
SQL Server Express and Express with Advanced Services do not support report models, which are required to create Vision custom reports.
Report Builder is a web application that you install on one machine, and users who create custom report use a ClickOnce application to download the software from that one machine to their local machine. Report Builder
3.0 saves the RDL in 2010 format.
To create custom reports with Report Builder, users must have the following installed on their workstations:
.NET Framework 3.5
Microsoft Internet Explorer 6.0 or later
Custom Reports and Microsoft SQL Server® Reporting Services 8
Software Requirements for Creating Custom Reports
Supported
Microsoft SSRS
Report Writing
Tool for Vision
7.6 Installation Information
512 MB of RAM. Deltek recommends that the computers that run
Report Builder have 512 MB of RAM. However, depending on the complexity of the reports you run, you might want less or more
RAM.
SQL Server Data
Tools - Business
Intelligence for
Visual Studio
2013 Report
Designer
(SSDT-BI 2013
Report Designer)
SSDT-BI 2013 Report Designer is provided with SSRS 2014, SSRS 2012, and SSRS 2008 R2, but it is not installed automatically.
Use the following Microsoft link to download SSDT-BI: http://www.microsoft.com/en-us/download/details.aspx?id=42313
During this installation, select only the SQL Server Data Tools -
Business Intelligence for VS 2013 check box in the Shared Features section of the setup dialog box.
When you install the Vision 7.6 upgrade to your Vision server (web server tier), Vision 7.6 custom report business objects are installed into the
<Deltek Vision Installation Directory>\Support\SDK folder. In this folder, extract the contents from the VBReporting.exe self-extracting file to access the custom report business objects.
For a full list of Microsoft SQL Server releases (R), service packs (SP), and cumulative updates
(CU) that are supported or compatible with Vision, see the Deltek Product Support Compatibility
Matrix. You can download this PDF document at the Deltek Customer Care Connect site.
Deltek can also arrange for implementation services support from your Deltek consultant.
If you have any additional questions, please contact Deltek Customer Care at 877.457.7765.
Custom Reports and Microsoft SQL Server® Reporting Services 9
Report Builder 3.0
Report Builder 3.0
Use Report Builder 3.0 to create simple, ad hoc custom Vision reports. You can create table, matrix, and chart reports. To create a report, you select the Vision report model and then drag and drop Vision fields into the report design area. You can filter, group, and sort report data. You can add formulas and parameters to your reports.
Configure Report Builder Access
To allow users to access the SSRS report server to create custom reports via ClickOnce, you must grant them the following SSRS permissions:
At the server level, users must be system users.
At the folder level, users must be granted browser and Report Builder access.
Users who have access to your SSRS report server to create custom reports with Report Builder can access all the Vision database fields included in the Vision report model, which is a subset of the Vision database. Vision role security does not apply when accessing the Vision database to create custom reports.
Non-Domain Clients
SSRS requires Windows Integrated Authentication. Non-domain clients (clients who do not run
Active Directory or have a Windows domain) must do the following:
Create a local account on the SSRS report server for each user who creates custom reports.
Grant the necessary reporting services permissions (see the previous "Configure Report
Builder Access" section) to those who create custom reports.
How to Start Report Builder
You provide one of the following ways for users to start Report Builder from their workstations:
Start the Report Builder from the Start Menu (available if the stand-alone version is installed).
SSRS Report Manager.
Deltek does not support SharePoint Integrated Mode for SSRS Vision.
More information on how users start Report Builder is available at the following link: http://technet.microsoft.com/en-us/library/ms159221(v=sql.105).aspx
(SQL Server 2008 R2)
Add Report Builder to the Vision Navigation Menu
Individual users who will create custom reports with Report Builder can add a link to Report
Builder directly on the Vision Navigation menu.
Custom Reports and Microsoft SQL Server® Reporting Services 10
Report Builder 3.0
To add Report Builder as a separate menu item on the Vision Navigation menu, complete the following steps:
1. Open Vision, and at the bottom of the Navigation menu, click the Designer icon.
Designer icon that opens the Navigation Menu Designer dialog box
2. On the left side of the Navigation Menu Designer dialog box, right-click the Navigation menu item above or below which you want to add Report Builder.
In the following example, the Reporting menu is selected.
Custom Reports and Microsoft SQL Server® Reporting Services 11
Report Builder 3.0
3. On the shortcut menu, click Insert Before or Insert After.
In this example, the Report Builder menu item (a parent menu item) is inserted after the
Reporting menu item.
On the Navigation Menu Designer dialog box, the Menu ID field is automatically populated. Deltek recommends that you do not modify it.
4. In the Menu Label field, enter Report Builder or the name that you want to see in the
Vision Navigation menu to open the Report Builder software.
5. Leave the remaining fields on the Navigation Menu Designer dialog box as they are
(Parent should be entered in the Action field), and click OK.
The Navigation Menu Designer dialog box closes.
Custom Reports and Microsoft SQL Server® Reporting Services 12
Report Builder 3.0
6. At the bottom of the Vision Navigation menu, click the Designer icon to open the
Navigation Menu Designer dialog box again.
Now you see the Report Builder parent item listed with the other menu items on the left.
7. Repeat steps 2 through 5 to enter a Report Builder child menu item under the Report
Builder parent menu item (insert the new menu item after Report Builder, and enter the
Report Builder menu label).
At this point, you cannot change the Action field, so leave it as Parent, and click OK.
The Navigation Menu Designer dialog box closes.
8. Click the Vision Designer icon to open the Navigation Menu Designer dialog box again.
This time you see both of the Report Builder menu items.
9. Right-click the second occurrence of Report Builder, and click Indent on the shortcut menu.
This creates the child menu item.
Custom Reports and Microsoft SQL Server® Reporting Services 13
Report Builder 3.0
10. From the drop-down list in the Action field, select HTTP.
11. In the Open field in the Action Options section, enter the following:
12. In the Open Options section, select New Window.
13. Click OK to save these settings.
14. After you make the necessary changes to the Navigation tree, you may need to grant users access rights to the Report Builder menu item (in Configuration » Security »
Roles) before they can see Report Builder in the Navigation menu
.
15. Exit and restart Vision for Report Builder to display on the Navigation menu.
Custom Reports and Microsoft SQL Server® Reporting Services 14
Report Builder 3.0
To add a Report Builder menu item within the existing Vision Reporting menu item, create an indented child menu item within the Reporting parent menu item (similar to steps 8 through 14).
Report Builder and the Vision Report Model
Vision comes with a report model—DeltekVisionReportModel.smdl—that you can use in Report
Builder to create custom Vision reports. With the report model, you can create project, accounting, and Customer Relationship Management reports.
The Vision report model defines the Vision database in more user-friendly terms and eliminates the need for those who create reports to have in-depth database knowledge. The model makes it easier to find and select the information from your Vision database to include on custom reports.
When you use the report model, queries are automatically generated to retrieve data from your
Vision database.
The Vision report model contains:
Data source information that is required to connect and retrieve information from the
Vision database.
A preselected group of Vision database tables and relationships. These are Vision entities and fields that you can add to a custom report. Database fields and tables have easy-to-understand business names and are grouped in the most appropriate way to make it easy to create the reports that you need.
For descriptions of the Vision database fields that are included in the Vision report model, see the
“Contents of the Vision Report Model” section on page 61 of this guide.
The Vision report model does not include user-defined fields. If you want to include user-defined fields in your custom reports, contact [email protected]
for information about
Deltek's assistance with custom reports.
Users who have access to your SSRS report server to create custom reports with Report Builder can access all the Vision database fields included in the Vision report model, which is a subset of the Vision database. Vision role security does not apply when accessing the Vision database to create custom reports.
For more information about report models, see the following Microsoft link: http://msdn.microsoft.com/en-us/library/ms159752(v=sql.100).aspx
.
Load the Report Model onto your SSRS Report Server
You must load the Vision report model onto your SSRS report server before users can access it in Report Builder.
Because the Vision model file is large, you must first modify the Web.config file to prevent a
"Maximum request length needed" error when you load the report model.
While you load the report model, Vision users will not be able to run any reports.
To modify the Web.config file, complete the following steps:
1. Use Windows Explorer to navigate to the Web.config file on your SSRS report server at the following location:
Custom Reports and Microsoft SQL Server® Reporting Services 15
Report Builder 3.0
C:\Program Files\Microsoft SQL Server\<SQL Instance Name>\Reporting
Services\ReportServer.
2. Make a backup copy of the Web.config file.
3. Open the Web.config file in the ReportServer folder with Notepad, and navigate to the
<system.web> section of the file.
4. In the <system.web> section, navigate to the <httpRuntime execution Timeout = "9000"
/> line.
5. Add maxRequestLength="151200" to the end of the line so it now reads:
<httpRuntime executionTimeout = "9000" maxRequestLength="151200" />.
6. Save the Web.config file.
To load the Vision report model, a system administrator, completes the following steps:
1. From the Vision Navigation menu, click Utility » Report Administration.
2. Open the Load Reports tab.
The Location of Reports on Application Server field displays the path to the Vision
Reports folder on your Vision application server—C:\Program
Files\Deltek\Vision\Reports.
3. From the Type field drop-down list, select Report Models.
4. If you previously loaded a report model, select the Delete Existing Reports in Each
Folder Before Loading check box so that old models are removed first. If you did not previously load a report model, clear the Delete Existing Reports in Each Folder
Before Loading check box.
5. Click the Load Report Files button.
When the process completes, you receive a message that identifies the number of items loaded.
Custom Reports and Microsoft SQL Server® Reporting Services 16
Report Builder 3.0
This loads the report model into the SSRS database, and the appropriate files are loaded into the appropriate IIS Virtual directory that points to their installation in
C:\Program Files (x86)\Deltek\Vision\Reports\Custom.
Multiple Vision Databases
If you have multiple Vision databases and you want to use the Vision report model with each
Vision database, you must load the Vision report model for each database. In Vision, open each database, and perform the steps in the previous section of this guide to load the report in Utilities
» Report Administration.
Move a Vision Database
After you load the report model to your report server, if you move a Vision database, you must load the report model again by opening the appropriate database in Vision and loading the report model in Utilities » Report Administration.
Access the Report Model in Report Builder
The following are the steps to access the Vision report model to create a custom report with
Report Builder. These steps assume that a Vision system administrator has:
Completed the steps in the "Software Requirements for Creating Custom Reports"
section of this guide.
Loaded the Vision report model per the "Report Builder and the Vision Report Model "
section of this guide.
To access the Vision report model in Report Builder, complete the following steps:
1. Open Report Builder with a link determined by your Vision system administrator.
2. On the main Report Builder window, click , and then click New in the pane on the left.
3. In the Report Data pane on the left of the next window, click New » Data Source.
Custom Reports and Microsoft SQL Server® Reporting Services 17
Report Builder 3.0
4. On the Data Source Properties dialog box, complete the following entries, and then click
OK.
Select the Use a shared connection or report model option.
Click the Browse button to navigate to and select the Vision report model on the
Vision report server.
5. In the data region of the report, click the Table or Matrix icon to add data to the report using the wizard.
Custom Reports and Microsoft SQL Server® Reporting Services 18
Report Builder 3.0
The data region can have the following controls:
Tabular (columnar) — This creates a report with a set number of rows and columns of information.
Matrix (cross-tab or pivot table) — This creates a report with rows and columns that are determined by the data returned when you run the report.
Chart — This creates a report with a column, bar, area, line, pie, or doughnut graphic.
6. As you go through the wizard, you:
Build a query to specify the Vision data that you want from the data source.
Arrange fields to group data in rows and columns.
Select the layout for displaying subtotals and grand totals and expanding and collapsing groups.
Select styles for fonts and color schemes.
Specific instruction on how to create and design Vision custom reports is beyond the scope of this guide. For further instruction on how to design your report, see Microsoft's
Report Builder help. You can also check the Deltek Web site at http://www.deltek.com/services/deltekuniversity for custom reporting classes offered through Deltek University.
7. To save your report after you complete the wizard, click , and then click the Save As command.
8. On the Save As dialog box, enter the file name for the report.
The Save as type is Report files [*.rdl].
See the "Vision Application Server Location for Custom Reports" section on page 47 of
this guide for more information about where to save custom report .rdl files so they can be successfully loaded into Vision and accessed from the Vision Reporting menu.
Custom Reports and Microsoft SQL Server® Reporting Services 19
Report Builder 3.0
You must use the Save to File option when you save a report file in Report Builder.
Then when you use Vision's Report Administration utility, the custom report is loaded into SSRS and Vision to display on a Vision Reporting submenu.
In Report Builder, if you save a report with Save instead of Save to File, the report is deployed to SSRS, and no .rdl file is created. The report will be available in Report
Manager (SSRS's Web interface), but it will not be available in Vision.
Custom Reports and Microsoft SQL Server® Reporting Services 20
SSDT-BI Report Designer
SSDT-BI Report Designer
Use SSDT-BI 2013 Report Designer to create both simple and complicated reports. It is a fullfeatured, advanced report writing tool. You can create tabular, matrix, chart, and free-form reports. You can create complex queries, advanced charts, parameters, drill downs, and subreports. You can create expressions to specify report data.
To create custom reports with Report Designer, you must install SSDT-BI 2013 locally on a report writer's workstation (with the appropriate licensing).
To allow report writing users access to the SSRS report server, you must grant them the following
SSRS permissions:
At the server level, users must be system users.
At the folder level, users must be granted browser and Content Manager access.
Users who have access to your SSRS report server to create custom reports in Report Designer can access all fields in your Vision database. Vision role security does not apply when accessing the Vision database to create custom reports.
Non-Domain Clients
SSRS requires Windows Integrated Authentication. Non-domain clients (clients who do not run
Active Directory or have a Windows domain) must do the following:
Create a local account on the SSRS report server for each user who creates custom reports.
Grant the necessary reporting services permissions (see the previous section) to those who create custom reports.
SSDT-BI Report Designer and Vision Report Templates
Overview
Vision comes with report templates that you can use to create custom reports in SSDT-BI Report
Designer. The templates provide formatting for custom reports that is similar to the formatting of
Vision standard reports.
You copy the template files to the workstation of users who will be creating custom reports. Then when users launch Report Designer, the Vision templates display in the list of templates. Users can also create custom reports with Report Designer by using the Vision report templates located directly on your SSRS report server (without copying the template files to a workstation).
Template Files
The template files for custom reports are:
VisionTemplateAudit.rdl — U se this template to create audit trail summary reports. Info
Center audit reports, such as Client Audit and Vendor Audit, are examples of this type of report.
VisionTemplateAuditDetail.rdl — Use this template to create audit trail detail reports.
Info Center audit detail reports, such as Client Audit Detail and Vendor Audit Detail, are examples of this type of report.
Custom Reports and Microsoft SQL Server® Reporting Services 21
SSDT-BI Report Designer
VisionTemplateCustomReport.rdl — Use this template to create a custom report without any pre-defined layout.
VisionTemplateLandscape.rdl — Use this template for column selection reports that must be printed using the landscape orientation. Report properties are set for this, so you do not need to modify them.
VisionTemplatePortrait.rdl — Use this template to create column selection reports.
VisionTemplatePostingLog.rdl — Use this template to create posting log reports.
VisionTemplateSubReport.rdl — Use this only to create a sub-report. Vision billing invoices are examples of reports that use sub-reports. Each section of a single billing invoice (report) is created by using sub-reports.
VisionTemplateTransactionList.rdl — Use this template to create transaction list reports.
VisionTemplatePortrait.rdl file when you open it in Report Designer
When you install Vision, the template files are installed on your Vision application server in the following location:
C:\Program Files (x86)\Deltek\Vision\Reports\Template
Load the Templates on a Workstation
To create a custom report on the workstation of a user who writes reports with Report Designer, copy the .rdl template files (listed in the previous section) to the following location on the user’s workstation:
C:\Program Files\Microsoft Visual Studio
9.0\Common7\IDE\PrivateAssemblies\ProjectItems\ReportProject
After you copy the .rdl template files to a workstation, when you launch Report Designer and select Business Intelligence Projects, the Vision templates display in the list of templates as in the following screen shot.
Custom Reports and Microsoft SQL Server® Reporting Services 22
SSDT-BI Report Designer
Method One
One way to copy the .rdl template files to a user's workstation is to allow appropriate users access to the Templates folder on your Vision application server. You can make the Templates folder shared and accessible so that report writing users can easily copy the .rdl template files to their workstations.
Method Two
You can also load the .rdl template files to your SSRS report server from the Vision application server with the Vision Report Administration utility. When you use this utility, the .rdl template files are loaded onto your SSRS report server in C:\Program Files
(x86)\Deltek\Vision\Reports\Custom. You can then share the Custom folder so report writing users can access it and copy the template files to their workstations.
While you run the Report Administration utility, Vision users cannot access any reports.
To load the .rdl template files from your Vision application server location to your SSRS report server location, complete the following steps:
1. From the Vision Navigation menu, click Utility » Report Administration.
2. Open the Load Reports tab.
The Location of Reports on Application Server field displays the path to the Vision report location—C:\Program Files (x86)\Deltek\Vision\Reports.
3. From the Type field drop-down list, select Report Models.
Custom Reports and Microsoft SQL Server® Reporting Services 23
SSDT-BI Report Designer
4. If you select the Delete Existing Reports in Each Folder Before Loading check box,
Vision deletes all reports of the type that you selected that are currently loaded; then it loads the reports from the application server Reports folder.
5. Click the Load Report Files button.
6. When it completes, you receive a message that identifies the number of items loaded.
This loads the report templates into the SSRS database, and the appropriate files are loaded into the appropriate IIS Virtual directory that points to their installation in
C:\Program Files (x86)\Deltek\Vision\Reports\Custom.
Access the Report Templates in Report Designer
After the Vision report templates are loaded onto a workstation, when you launch Report
Designer and select Business Intelligence Projects, you see a list of the Report Designer templates from which you can create new reports.
You cannot use the Vision report templates with the Report Designer Report Wizard.
To access the Vision report templates to create a custom report, you complete three procedures to:
1. Create a solution and report server project.
2. Create the shared data source.
3. Select a Vision template and start to create a custom report.
To create a solution and report server project, complete the following steps:
1. On your workstation, open the Report Designer software by clicking Windows Start » All
Programs » Microsoft SQL Server 2014 » SQL Server Data Tools for Visual Studio
2013.
Custom Reports and Microsoft SQL Server® Reporting Services 24
SSDT-BI Report Designer
2. Click File » New » Project.
3. Select Business Intelligence Projects.
4. In the Templates section of the New Project dialog box, click Report Server Project to highlight it.
5. In the Name field, enter a name for the report server project. For example, you could name it VisionCustomReports.
A report server project contains:
A data source (information about a connection to a data source for your report).
Any custom reports that you create with the data source.
6. In the Location field, enter the path on your workstation where you want to store the report server project.
7. In the Solution Name field, enter a name for the solution in which this report server project will be contained.
Solutions can contain multiple projects.
8. Click OK.
In the Solution Explorer pane, you now see the solution that you just created. (To display the Solution Explorer pane, click View » Solution Explorer.)
To create the shared data source, complete the following steps:
1. In the Solution Explorer pane that is located below your solution, right-click Shared Data
Sources, and click Add New Data Source on the shortcut menu.
2. On the General tab of the Shared Data Source dialog box, in the Name field, enter
DefaultDataSource.
This is the name of the Vision data source.
All of the Deltek report templates look at the data source called DefaultDataSource. If you name it something else, you will receive an error when you select the Data tab of the Design window. When you receive the error, click OK and then modify the dataset to use your connection instead. You must do this for each dataset.
Also, when you rename an existing data source, if you previously used the data source for a report, the report will be broken and you need to edit the report query to reference the new data source name.
3. From the Type field drop-down list, select Microsoft SQL Server.
4. Click the Edit button beside the Connection string text box to open the Connection
Properties dialog box where you can create the connection string to your Vision database. a) Select the server on which your Vision database resides.
Deltek recommends that you use Windows authentication to log on to the server.
This prevents users from accessing information via Report Designer that they should not access. If you use SQL Authentication and save the password, the password is saved as plain text and can be seen with Notepad. b) Enter the Vision database name to connect to. c) Click OK.
Custom Reports and Microsoft SQL Server® Reporting Services 25
SSDT-BI Report Designer
5. On the Credentials tab of the Shared Data Source dialog box, enter the credential information for the data source, and click OK.
In the Solution Explorer pane, you now see DefaultDataSource.rds in the Shared Data
Sources folder within the solution.
6. On the Microsoft Visual Studio toolbar, click File » Save All.
Save your solution often to prevent losing modifications in the event that Report Designer terminates.
To select a Vision template and start to create a custom report, complete the following steps:
1. In the Solution Explorer pane, right-click the Reports folder, and click Add » New Item on the shortcut menu.
On the Add New dialog box, you see the Vision report templates.
2. Click a report template to open it and create a custom Vision report with it.
Specific instruction on how to create and design Vision custom reports is beyond the scope of this document. For detailed information and training on how to design a Vision report with Report Designer, Deltek University offers report writing classes.
See http://www.deltek.com/services/deltekuniversity for class offerings.
Classes include instruction on how to replace special tags in SQL statements. The tags make it possible to modify aspects of a query as it is passed from Vision to the Report
Server. This enables you to include a Sorting/Grouping tab or Columns tab on the report
Options dialog box in Vision Reporting for a custom report.
You can also contact [email protected]
for information about the custom report services that Deltek provides.
3. After you create a custom report and it is ready for others to use, you must save the report .rdl file to the appropriate folder on your Vision application server so it can be successfully loaded into Vision.
See the "Vision Application Server Location for Custom Reports” section on page 47 of
this guide for more information.
Deltek does not support the deployment of reports to the SSRS report server directly from within the Report Designer software. Instead, you use the Vision Report
Custom Reports and Microsoft SQL Server® Reporting Services 26
SSDT-BI Report Designer
Multilingual Companies and Report Templates
You can create custom reports in multiple languages only if you purchase and activate the Vision
Multilingual module.
If you have multilingual companies in your enterprise and you want the ability to generate a report in multiple languages from one report design, you must create custom reports with Vision report templates loaded locally on a workstation. When you create a custom report with the Vision report templates directly on your SSRS report server, the report can be generated only for the specific culture (language) from which you accessed the report template.
Create a Custom Report from a Vision Standard Report in Report
Designer
If the content of a standard report is similar or close to what you need in a custom report, you may want to start with a copy of a standard report .rdl file and then modify it in Report Designer to suit your needs.
You cannot use Report Builder to create a custom report from a Vision standard report.
Start with an .Rdl File that You Create from within Vision
One way to create a custom Vision report is to start with an .rdl file that you create when you preview a standard report in Vision Reporting.
To create an .rdl file from a previewed standard report in Vision Reporting, complete the following steps:
1. From the Vision Navigation menu, click Reporting, and then click the menu item that contains the standard report from which you want to create a custom report.
2. On the report form, click the cell in the Options column for the report that you want to start with, and then click that displays in the cell.
3. On the report Options dialog box, select the appropriate report options, and click Apply to return to the report form.
4. On the report form toolbar, click Preview.
5. On the toolbar of the report preview screen, double-click the Get Report Information
icon on the report preview toolbar.
Custom Reports and Microsoft SQL Server® Reporting Services 27
SSDT-BI Report Designer
6. On the Report Information dialog box, select Report Definition (RDL File) from the dropdown list in the View report information field, and click View.
The Report Definition (RDL File) option provides you with the exact .rdl file that was used to load the report instance as it was rendered on the report server. When you preview this .rdl file within Report Designer, it looks exactly like the one in the Vision
Reporting preview window.
7. On the File Download dialog box, click Save to save the .rdl file.
This saves the report as a new .rdl file. When you open this .rdl file in Report Designer inside of a BI project, it displays exactly as it does in the Vision Reporting preview window.
When you save the .rdl file for the new custom report, give it the .rdl file name that you want it to have within a BI project.
Do not give it the same .rdl file name as the Vision standard report that you created it from.
On the File Download dialog box, you can also click the Open button. This opens the .rdl file as XML code within Report Designer; it does not open in Report Designer as a report
Custom Reports and Microsoft SQL Server® Reporting Services 28
SSDT-BI Report Designer within the designer. You can modify the file directly in the Report Designer code view and save it.
At this point you are ready to modify the report within Report Designer to create a custom report.
Open the Custom Report .Rdl File in Report Designer
After you create and save a custom report .rdl file from a standard report, to open the custom report .rdl in Report Designer, complete the following steps:
1. Open a BI project within Report Designer.
2. Select the option to add an existing item to the project, and browse to where you saved the .rdl file to open it.
Verify that the Data Source Is Set for the Query
For custom reports that you created with a Vision standard report, you must verify that the data source is set for the query.
To check the data source, complete the following steps:
1. With the custom report .rdl file that is open in Report Designer, click the Data tab.
If you receive the following dialog box, it means that Report Designer is not able to connect to a valid data source for the selected dataset. You must fix the data source to point to the shared data source in your BI project.
If you do not receive the message, you are ready to modify the report.
To fix the data source to point to the shared data source in your BI project, complete the following steps:
1. In the Microsoft Report Designer window that indicates that the data source was not found, click OK.
2. On the Data tab, click the
Dataset dialog box:
button next to the dataset name to open the following
Custom Reports and Microsoft SQL Server® Reporting Services 29
SSDT-BI Report Designer
3. On the Dataset dialog box, from the drop-down list in the Data source field, select the data source that is used within your BI Project.
This generally has “(shared)” within the name.
At this point you are ready to work on the design of the report.
XML Code that You Must Modify
When you start with a standard Vision report to create a custom report, you must modify some of the XML code in the report's .rdl file to remove and replace items that are no longer appropriate for your custom report. If you do not make these modifications, your custom report may not function properly. You must make these modifications before you save a custom report to the application server and load it into Vision.
Report Name
When you create a custom report from a Vision standard report, the custom report design contains the name of the standard report that displays on the Vision Reporting menu.
You must replace the standard report name with the custom report name on the Layout tab in
Report Designer.
30 Custom Reports and Microsoft SQL Server® Reporting Services
SSDT-BI Report Designer
If you do not replace the standard report name with a custom report name, both the standard and custom report display on the Vision Reporting menu with the same report name.
Custom Properties
The XML section of a standard Vision report's .rdl file contains custom properties for reports that are used to:
Load the custom report using Vision's Report Administration utility.
Control Vision report options.
You must delete and modify some of the existing custom properties that no longer apply for a custom report. Your custom report will not function properly if you do not make these modifications.
Custom properties are defined between the <CustomProperties> and </CustomProperties> tags in the XML code of a report's .rdl file. You modify custom properties in a report on the Properties window of the report.
1. In the Properties list, navigate to CustomProperties.
2. Click the ellipsis button to open the Custom Properties dialog box.
The following sections of this guide identify the custom properties that you must delete or modify.
ReportBO
The ReportBO custom property is used for Vision standard reports. It is not valid for custom reports and must be deleted to prevent errors in Vision.
Delete the following section of the XML code (this example uses the standard Project List report):
<CustomProperty>
<Name>ReportBO</Name>
<Value>Deltek.Vision.ReportingProject.Server.ProjectList</Value>
</CustomProperty>
ResourceFileName
When Vision loads the standard reports, the resource file is used to change report labels to the appropriate culture. Because the custom report that you are working with already has its labels converted to a specific culture, you must delete this ResourceFileName tag.
Delete the following from the XML code (this example uses the standard Project List report):
<CustomProperty>
<Name>ResourceFileName</Name>
<Value>Project List</Value>
</CustomProperty>
OptionForm
The OptionForm custom property controls the display of the report Options dialog box in Vision
Reporting for the custom report. If you want the report Options dialog box to display, you must replace the standard report's OptionForm value with the following Vision default report value:
<Value>Deltek.Vision.Report.Client.VisionReportDialog</Value>
Custom Reports and Microsoft SQL Server® Reporting Services 31
SSDT-BI Report Designer
Example:
The original XML code in the standard Project List report:
<CustomProperty>
<Name>OptionForm</Name>
<Value>Deltek.Vision.ReportingProject.Client.dlgRepOpt_ProjectList</Value>
</CustomProperty>
Modify the XML code as follows:
<CustomProperty>
<Name>OptionForm</Name>
<Value>Deltek.Vision.Report.Client.VisionReportDialog</Value>
</CustomProperty>
For custom reports that are created with a standard Vision report, the report Options dialog box in Vision Reporting will display a General tab, a Layout tab, and if you have added report parameters in Vision Custom Report Options Configuration, a Custom Options tab.
GroupingType
The GroupingType custom property controls whether or not the Sorting/Grouping tab displays on the report Options dialog box in Vision Reporting. For custom reports that you create from a standard Vision report, delete this custom property.
Delete the following from the original XML code (this example uses the Project List report):
<CustomProperty>
<Name>GroupingType</Name>
<Value>Project</Value>
</CustomProperty>
To add a Sorting/Grouping tab to the report Options dialog box, you must modify special tags in
SQL statements. Instruction on how to do this is beyond the scope of this document. Report writing classes offered through Deltek University cover special tags. See http://www.deltek.com/services/deltekuniversity for class offerings.
UseColumnSelection
The UseColumnSelection custom property determines whether or not the Column tab displays on the report Options dialog box in Vision Reporting. This tab allows you to select the columns for a report before you generate it. For custom reports that you create from a standard Vision report, change the UseColumnSelection value from Y to N.
Custom Reports and Microsoft SQL Server® Reporting Services 32
SSDT-BI Report Designer
Example:
The original XML code in the Project List report, where the value is set to Y:
<CustomProperty>
<Name>UseColumnSelection</Name>
<Value>Y</Value>
</CustomProperty>
Modify the original XML code as follows:
<CustomProperty>
<Name>UseColumnSelection</Name>
<Value>N</Value>
</CustomProperty>
To add a Columns tab to the report Options dialog box, you must modify special tags in SQL statements. Instruction on how to do this is beyond the scope of this document. Report writing classes offered through Deltek University cover special tags. See http://www.deltek.com/services/deltekuniversity for class offerings.
Further Instructions
Further specific instruction on how to create and design Vision custom reports is beyond the scope of this document. For detailed information and training on how to design a Vision report with Report Designer, check Deltek University's report writing class offerings at http://www.deltek.com/services/deltekuniversity .
You can also contact [email protected]
for information about Deltek's assistance with custom reports.
Upload Custom Reports into Vision
Deltek does not support the deployment of reports to the Vision report server directly from within the Report Designer software. Instead, you use the Vision Report Administration utility to load
reports onto the Vision report server and into Vision. For further instructions, see the “Load
Custom Reports into Vision” section on page 47.
Custom Reports and Microsoft SQL Server® Reporting Services 33
Custom Reports Created with Microsoft SQL Server Reporting Services 2005 and 2008
Custom Reports Created with Microsoft SQL
Server Reporting Services 2005 and 2008
The information in this section also applies for upgrading the custom reports that you use to create custom invoices in Vision.
Overview
Custom reports that you created with Microsoft SQL Server Reporting Services 2005 or Microsoft
SQL Server Reporting Services 2008 have RDL 2005 and RDL 2008 schema are not supported in Vision 7.4 and later versions. You must upgrade these custom reports to change the schema to
RDL 2010 before you can use them in Vision 7.6. You must use SSDT-BI 2013 Report Designer,
Report Builder 3.0, or the Vision Report Administration utility to upgrade the reports to the supported RDL 2010 schema. See the sections below for instructions.
After you upgrade the reports, you must update report queries to revise any database table
names that have changed. Database table names that have changed are identified in the “Vision
Database Table Name Changes that Affect Custom Reports” section on page 37. There are no
database table name changes in Vision 7.1 or later versions.
Other Vision 7.6 framework changes that are applied within the report business objects may affect your custom reports after you upgrade, causing them to not work properly. If a custom report does not work properly after you upgrade and update any renamed database tables,
Deltek recommends that you recreate the custom report using Vision 7.6 and SSDT-BI 2013
Report Designer or Report Builder 3.0.
Consider the following before you recreate a custom report with SSDT-BI 2013 Report Designer or Report Builder 3.0:
Do you still need the custom report?
Are there standard reports in Vision 7.4 and later that provide the information that you need?
Is the custom report that you created with BIDS 2005, BIDS 2008, or Report Builder versions 1.0 or 2.0 based on a Vision standard report? If so, you can start with a standard
Vision report and modify it in SSDT-BI 2013 Report Designer or Report Builder 3.0 to recreate your custom report.
If you need additional assistance with custom reports, contact Deltek Global Services.
For detailed information and training on how to design a Vision report with Report Designer or
Report Builder, Deltek University offers report writing classes.
For class offerings, see http://www.deltek.com/services/deltekuniversity .
Upgrade Custom Reports Using SSDT-BI 2013 Report Designer
These instructions apply for Vision custom reports that you created with BIDS 2005 or BIDS 2008 that need to be upgraded to the RDL 2010 schema. For these upgrade instructions, you start by opening or creating a report project (instead of opening the report RDL files).
Custom Reports and Microsoft SQL Server® Reporting Services 34
Custom Reports Created with Microsoft SQL Server Reporting Services 2005 and 2008
Custom Reports that Already Have a Report Project
If a custom report already has a reporting project, use the following instructions to upgrade the report.
To upgrade Vision custom reports using SSDT-BI Report Designer to be compatible with
Vision 7.6, complete the following steps:
1. Use Report Designer to open an existing Vision custom report project.
2. Complete the wizard that starts automatically. It guides you through upgrading the report project.
3. Open a custom report in Report Designer.
4. For any Vision database tables included in the report that have new names in Vision, replace the old names with the new names.
This applies if you are upgrading to Vision 7.6 from a 6.x version. The affected tables and
instructions are included in the “Vision Database Table Name Changes that Affect
Custom Reports” section on page 37.
5. In the Report Property pane, enter a dummy value in InitialPageName property.
6. Save the report.
7. Remove the dummy value in the InitialPageName property and save the report again.
8. Repeat step 3–7 for each custom report in the report project.
9. Upload the custom reports to Vision using the Vision Report Administration utility as
described in the “Load Custom Reports into Vision” section on page 47.
If a report does not run properly, you may need to recreate it with SSDT-BI Report
Designer.
Custom Reports that Do Not Have a Reporting Project
If a custom report does not have a reporting project, you create a reporting project before you upgrade the report.
To create a reporting project and upgrade Vision custom reports to be compatible with
Vison 7.6 using SSDT-BI Report Designer, complete the following steps:
1. Open SQL Server Data Tools for Visual Studio 2013.
2. On the File menu, click New » Project.
3. In the Project types pane of the New Project dialog box, select Business Intelligence
Projects.
4. In the Templates pane, select Report Server Project.
Custom Reports and Microsoft SQL Server® Reporting Services 35
Custom Reports Created with Microsoft SQL Server Reporting Services 2005 and 2008
5. In the Name field, enter a name for the report project.
Enter a name that is related to the type of reports you will add to this project. For example, for billing reports, you could name the project “Billing.”
6. In the Location field, enter the location where the reports will be stored.
Deltek recommends that you store reports in <your Vision installation
path>\Reports\Custom.
Example: c:\Program Files (x86)\Deltek\Vision\Reports\Custom
7. On the New Project dialog box, click OK.
8. Add the RDL file for existing custom reports to the report project: a) In the Solution Explorer pane, right-click the Reports folder, and click Add » Existing
Item. b) On the Add Existing Item dialog box, navigate to an existing RDL file to add it to the report project. c) Modify the InitialPageName property of the report and add a dummy value. d) Save the report file.
When you save it, the schema of the RDL file is changed from RDL 2005 or RDL
2008 to RDL 2010. e) Remove the dummy value in InitialPageName property and save the report again. f) Repeat these steps to add RDL files for other custom reports to the report project.
9. Open a custom report in Report Designer.
10. For any Vision database tables included in the report that have new names in Vision 7.6, replace the old names with the new names.
This applies if you are upgrading to Vision 7.6 from a 6.x version. The affected tables and
instructions are included in the “ Vision Database Table Name Changes that Affect
Custom Reports” section on page 37.
Custom Reports and Microsoft SQL Server® Reporting Services 36
Custom Reports Created with Microsoft SQL Server Reporting Services 2005 and 2008
11. Save the report.
12. Repeat step 9 and 10 for each custom report.
13. Upload the reports to Vision using the Vision Report Administration utility as described in
the “Load Custom Reports into Vision” section on page 47.
If a report does not run properly, you may need to recreate it with SSDT-BI Report
Designer.
Upgrade Custom Reports Using Report Builder 3.0
These instructions apply for Vision custom reports that you created with Report Builder version
1.0 or 2.0. With these instructions, you can update a report’s RDL file directly.
To upgrade Vision custom reports to the RDL 2010 schema using Report Builder 3.0, complete the following steps:
1. Use Report Builder 3.0 to open a custom report RDL file.
2. Save the report file.
Saving it changes the schema of the RDL file from RDL 2008 or RDL 2005 to RDL 2010.
3. In Report Builder 3.0, for any Vision database tables included in the report that have new names in Vision 7.x, replace the old names with the new names.
This applies if you are upgrading to Vision 7.6 from a 6.x version. The affected tables and
instructions are included in the “Vision Database Table Name Changes that Affect
Custom Reports” section on page 37.
4. Save the report.
5. Upload the report to Vision using the Vision Report Administration utility as described in
the “Load Custom Reports into Vision” section on page 47.
If a report does not run properly, you may need to recreate it with Report Builder 3.0.
Upgrade Custom Reports Saved in the Vision Database Using
Report Administrator
Use these instructions to upgrade custom reports that are already saved in your Vision database with the RDL 2008 schema to the RDL 2010 schema that Vision 7.6 supports.
These instructions apply only if the custom reports in your Vision database have the RDL 2008 schema. You must use SSDT-BI 2013 Report Designer or Report Builder 3.0 to upgrade reports with the RDL 2005 schema.
This upgrade process opens all your custom reports, and for each report it upgrades the report schema, resaves the report in the Vision database, and uploads the report to the Vision report server.
To upgrade custom reports that are saved in your Vision database with the RDL 2008 schema to the RDL 2010 schema, complete the following steps:
1. From the Vision Navigation menu, click Utilities » Report Administration.
2. On the Report Server form, click the Custom Reports tab.
Custom Reports and Microsoft SQL Server® Reporting Services 37
Custom Reports Created with Microsoft SQL Server Reporting Services 2005 and 2008
3. On the Custom Reports tab, click the Upgrade option on the toolbar of the Load Custom
Reports grid.
The Upgrade option displays on the toolbar only if you have a saved custom report in the Vision database.
If all your existing custom reports already use the latest RDL 2010 schema, you receive the following message: "All existing custom reports stored in your database are already using the latest schema."
4. Click Yes on the dialog box that says: "This will upgrade all existing custom reports currently stored in your database to the latest schema. Would you like to continue?"
The upgrade starts.
During the upgrade, Vision backs up the custom reports that are saved in the Vision application server’s Report\Backup folder.
When the upgrade finishes, you receive the following message: "All custom reports have been successfully upgraded to the latest schema."
5. After the upgrade finishes, check the RDLProcessing.log log file that is saved in the
Vision application server's Report\Backup\<database name> folder.
The file contains the status for each processed RDL file and will identify any errors.
Upgrade Custom Reports Saved Locally Using Report
Administrator
Use these instructions to upgrade Vison custom reports that are saved on a local machine with the RDL 2008 schema to the RDL 2010 schema that Vision 7.6 supports. These instructions apply for custom reports have not been saved in the Vision database. This process is useful if you are currently working on or developing custom reports that are still in the old schema and the reports have not been uploaded to the Vision database yet.
Custom Reports and Microsoft SQL Server® Reporting Services 38
Custom Reports Created with Microsoft SQL Server Reporting Services 2005 and 2008
These instructions apply only if the custom reports on a local machine have the RDL 2008 schema. You must use SSDT-BI 2013 Report Designer or Report Builder 3.0 to upgrade reports with the RDL 2005 schema.
To upgrade custom reports on a local machine with the RDL 2008 schema to the RDL 2010 schema, complete the following steps:
1. From the Vision Navigation menu, click Utilities » Report Administration.
2. On the Report Server form, click the Custom Reports tab.
3. In the Apply Schema Update to Custom Report File section, click the Select Folder button.
4. In the Browse for Folder dialog box, scroll to and select the folder in which the custom reports are located, and click OK to close the dialog box.
5. Click the Apply button to update the reports.
6. Review the RDLProccessing.log log file that is saved in the folder where the custom reports are located.
The file contains the status for each processed RDL file and will identify any errors.
Vision Database Table Name Changes that Affect Custom
Reports
Vision database tables used in reports that had a name change in Vision 7.0 are listed below. If you are upgrading to Vision 7.6 from a version that is earlier than 7.0, then after you upgrade your custom reports, you must replace the old table names with the new names in report queries that include the affected tables. For example, if a custom report included the CFGCountry table, you must replace CFGCountry with FW_CFGCountry. If you do not update the table names, you will receive errors when you run the reports.
Custom Reports and Microsoft SQL Server® Reporting Services 39
Custom Reports Created with Microsoft SQL Server Reporting Services 2005 and 2008
There were no database table name changes in Vision 7.1 or later versions.
Vision Table Name Changes that Affect Custom Reports
Table Name in Vision 6.x
CFGCountry
CFGCurrency
CFGPhoneFormat
CFGEnabledCurrencies
InfoCenterTabHeadings
ReportPrinters
Table Name in Vision 7.0
FW_CFGCountry
FW_CFGCurrency
FW_CFGPhoneFormat
FW_CFGEnabledCurrencies
FW_InfoCenterTabHeadings
FW_ReportPrinters
To change a table name in either Report Designer or Report Builder, complete the following steps:
1. Open the report in either of the reporting tools.
2. On the Report Data pane, expand the Datasets folder.
3. Double-click ReportDataset.
4. In the Query text box in the Dataset Properties window, find mention of the old table name, and replace it with the new table name.
To quickly determine whether the query contains an affected table, you can copy the contents from the Query text box into a word processor. Then use Find in the word processor to search for the table name.
Custom Reports and Microsoft SQL Server® Reporting Services 40
Custom Reports Created with Microsoft SQL Server Reporting Services 2005 and 2008
5. Click OK.
If you receive the following message, click OK in the dialog box. You do not need to refresh the field list; you are updating the table name only.
Custom Reports and Microsoft SQL Server® Reporting Services 41
Custom Invoices Created with Microsoft SQL Server Reporting Services 2005 and 2008
Custom Invoices Created with Microsoft SQL
Server Reporting Services 2005 and 2008
Vision custom invoices are basically reports. Follow the instructions in the previous “Custom
Reports Created with Microsoft SQL Server Reporting Services 2005 and 2008” section to
upgrade custom invoices that were created with Microsoft SQL Server Reporting Services 2005 or 2008. When you upgrade them, the RDL 2005 or RDL 2008 schema of the report will be upgraded to RDL 2010.
After you upgrade custom reports to the RDL 2010 schema, review your custom invoice reports and their custom templates to make sure everything is working properly.
Custom Reports and Microsoft SQL Server® Reporting Services 42
Custom Reports Created with Actuate
Custom Reports Created with Actuate
Vision custom reports were created with Actuate prior to Vision 6.0. There is no automated process to convert custom Vision reports that were created with Actuate to SSRS reports.
If you have custom Vision reports that were created with Actuate, consider the following before you recreate the custom report with Report Builder or SSDT-BI Report Designer:
Do you still need the custom report?
Are there standard reports in Vision 7.6 that provide the information that you need?
Is the custom report that you created with Actuate based on a Vision standard report? If so, you can start with a standard Vision report and modify it in Report Designer.
For detailed information and training on how to design a Vision report with Report Builder or
Report Designer, Deltek University offers report writing classes.
See http://www.deltek.com/services/deltekuniversity for class offerings.
The Deltek Custom Development Group provides custom report services. You can contact them at [email protected]
for information about the assistance that they provide.
Custom Reports and Microsoft SQL Server® Reporting Services 43
Implementing Custom Labels in Custom Reports
Implementing Custom Labels in Custom Reports
You can implement custom labels in custom reports by using a custom resource file (a .resx file) rather than by modifying the Deltek.Vision.ReportLabels.Server.dll file. As a result, when Deltek makes a change to a standard label in Vision, it has no effect on your custom labels in custom reports.
The standard resource file for a report, lookup, or report group is used by default to replace labels. However, if you create a custom resource file, the resource labels in that custom file override the corresponding standard labels. The custom resource files only need to contain the custom labels; Vision uses the standard labels in all other cases.
Non-Multilingual Companies
If you do not use the Vision Multilingual module, Vision looks for custom resource files in this location: <Installation location>\Reports\Custom\Resource Files\en-US.
Example: C:\Program Files\Deltek\Vision\Reports\Custom\Resource Files\en-US.
The resource file name formats are the following:
Report labels: Custom_<ResourceFileName custom property from the RDL file>.en-
US.resx
Report group labels: Custom_ReportGroup_<group id>.en-US.resx
Lookup labels: Custom_Lookup_<lookup id>.en-US.resx
Examples:
Custom_Contact List.en-US.resx
Custom_Lookup_Employee.en-US.resx
Custom_EmployeeList.en-US.resx
Multilingual Companies
If you use the Vision Multilingual module, Vision looks for custom resource files in this location:
<Installation location>\Reports\Custom\Resource Files\<culture>.
Example: C:\Program Files\Deltek\Vision\Reports\Custom\Resource Files\en-GB.
Cultures are:
en-US — United States English
en-GB — International English
The resource file name formats are the following:
Report labels: Custom_<ResourceFileName custom property from the RDL
file>.<culture>.resx
Report group labels: Custom_ReportGroup_<group id>.<culture>.resx
Lookup labels: Custom_Lookup_<lookup id>.<culture>.resx
Examples:
Custom_Contact List.en-GB.resx
Custom_Lookup_Employee.en-US.resx
Custom_EmployeeList.en-GB.resx
Custom Reports and Microsoft SQL Server® Reporting Services 44
Custom Reports for User-Defined Info Centers
Custom Reports for User-Defined Info Centers
Report Type Custom Property
For any custom report that is created for a user-defined Info Center in Vision, you must add a report type custom property to the report design. This identifies the user-defined Info Center submenu under the Vision Reporting menu in which you want the custom report to display.
You must enter the value of the report type custom property as follows:
<Value>UDIC_<specific user-defined Info Center ID>_<Report name></Value>
The specific user-defined Info Center ID is based on the singular label that you entered for the user-defined Info Center when you set it up in Configuration » General » User Defined
Components. It is the singular label, without any spaces between words if you have multiple words in the label. You can see this label in the Info Center Properties dialog box when you open a user-defined Info Center in User Defined Components Configuration, and you click the Info
Center Properties on the form toolbar. The last portion of the database tablename that is specified on the dialog box also displays the singular label (with no spaces).
If you forget to add the report type custom property to a custom report, the report will not display in the Vision Reporting menu.
Example:
You have a user-defined Info Center named Potential Hires.
When you created the user-defined Info Center, you entered Potential Hire as singular label for the user-defined Info Center (the database tablename is UDIC_PotentialHire).
The Info Center Properties dialog box (that opens when you click Info Center Properties on the form toolbar in Configuration » General » User Defined Components):
You created a custom report called Potential Hires for Sales (file name is PotentialHiresSales.rdl).
You enter the following report type custom property for the report:
<CustomProperty>
<Name>ReportType</Name>
<Value>UDIC_PotentialHire_Potential Hires-Sales</Value>
</CustomProperty>
After you upload this report into Vision using the Report Administration utility, the report displays in Reporting » Potential Hires.
Custom Reports and Microsoft SQL Server® Reporting Services 45
Custom Reports for User-Defined Info Centers
Upload Custom Reports for User-Defined Info Center
When you upload a user-defined Info Center custom report into Vision using the Report
Administration utility:
If you upload the report from your Vision application server, you must place the custom report in the C:\Program Files (x86)\Deltek\Vision\Reports\Custom\My Reports\UDIC on the Vision application server.
If you upload the report from a workstation, you must select User Defined Info Center in the Location field on the Custom Reports tab.
The next section “Load Custom Reports into Vision” provides more information about uploading
custom reports.
Custom Reports and Microsoft SQL Server® Reporting Services 46
Load Custom Reports into Vision
Load Custom Reports into Vision
You use the Report Administration utility in Vision » Utilities to upload custom reports with .RDL file extensions into Vision. In the utility, there are two ways to upload custom reports, depending on where the reports are currently located:
On the Load Reports tab in Report Administration, you upload custom reports from the
Vision application server into Vision. Using this method, you must place the .RDL files in the folders on the application server that match the corresponding Vision Reporting submenus from which you want users to access the reports.
On the Custom Reports tab in Report Administration, you upload custom reports from any location on a workstation into Vision.
When you use either of these upload methods, the custom reports are copied to your Vision report server and added to a submenu under the Reporting menu in the Vision Navigation pane.
Deltek does not support the deployment of reports onto your Vision report server directly from within the Report Designer or Report Builder software.
Deltek First Vision Essentials Cloud Version
If your firm uses the Deltek First Vision Essentials cloud version, the Report Administration utility does not display unless a Vision system administrator selects the Allow RDL files to be
uploaded in Report Administration check box on the General tab in the Weblink utility. The only tab that is available in the Report Administration utility in Deltek First Vision Essentials is the Custom Reports tab.
Vision Application Server Location for Custom Reports
If you are uploading custom report files into Vision from your Vision application server, you must place the report .RDL files in the folders on the application server that match the corresponding
Vision Reporting submenus from which you want users to access the reports. Then you perform the file upload on the Load Reports tab in Vision Report Administration.
You must set up folders for the custom reports on your application server under the My Reports folder in:
C:\Program Files (x86)\Deltek\Vision\Reports\Custom\My Reports
Set up the following folders in the My Reports folder, exactly as they appear in this list:
Accounting
AccountsReceivable
Billing
Client
Consolidated GL
Contact
DataExport
Employee
GeneralLedger
Inventory
Custom Reports and Microsoft SQL Server® Reporting Services 47
Load Custom Reports into Vision
Invoice
Lead
MarketingCampaign
Opportunity
Payroll
PerformanceManagement
Project
Purchasing
ResourcePlanning
TextLibrary
Unit
Vendor
UDIC (Use this folder for custom reports for all user-defined Info Centers)
Example
You create a custom report that has employee data, and you want the report to display from the
Employee submenu under Vision Reporting.
You must put the .RDL report file in the following folder before you complete the upload steps on the Load Reports tab in the Report Administration utility:
C:\Program Files (x86)\Deltek\Vision\Reports\Custom\My Reports\Employee
When you upload the report to Vision using the Report Administration utility, the report is copied to your Vision report server and is displayed in Vision in Reporting » Employee.
Upload Custom Reports from Your Vision Application Server into Vision
After you create a Vision custom report and save the .RDL file to the correct folder on your Vision application server (as outlined in the previous section), use the Vision Report Administration utility to upload the report into Vision. During the upload process, the custom report is copied to your
Vision report server and added to a submenu under the Reporting menu in the Vision Navigation pane.
When you run the Report Administration utility to upload custom reports, Vision users cannot access any reports.
To upload custom reports from your Vision application server into Vision, complete the following steps:
1. From the Vision Navigation menu, click Utility » Report Administration.
2. Open the Load Reports tab.
The Location of Reports on Application Server field prefills with the path to the reports on the Vision application server location, which is C:\Program Files
(x86)\Deltek\Vision\Reports.
3. From the Report Type field drop-down list, select Custom.
Custom Reports and Microsoft SQL Server® Reporting Services 48
Load Custom Reports into Vision
4. In the Report Name field, enter the name of the custom report that you want to upload into Vision.
Enter the report file name without the .RDL file extension.
If you leave the Report Name field blank, all custom reports in the custom report folders on your Vision application server are loaded.
5. If you select the Delete Existing Reports in Each Folder Before Loading check box,
Vision deletes all reports of the type that you selected that are currently loaded in Vision, and then re-loads the reports from the application server Reports folder.
6. Click the Load Report Files button.
7. Click Yes on the dialog box that warns you that loading reports prevents users from running reports for a few minutes.
8. On the dialog box that informs you that reports have been loaded, click OK.
The custom report displays on the specified submenu of the Vision Reporting menu after you log out and back into Vision.
The custom reports also display in the Report Name drop-down list in Configuration »
General » Custom Report Options where you can add parameters to them.
49 Custom Reports and Microsoft SQL Server® Reporting Services
Load Custom Reports into Vision
Upload Custom Reports from a Workstation into Vision
If you have custom reports (.RDL files) saved on a workstation, follow the instructions in this section to upload them into Vision. During the upload process, custom reports are copied to your
Vision report server and Vision database. They are also added to a submenu under the Reporting menu in the Vision Navigation pane.
The copy of the report file on the report server is used when the report is accessed in
Vision by users.
The copy of the report file in the Vision database serves as a backup copy that you can download in the event that you need a copy and you cannot find the original file on your workstation.
Prerequisites:
You use the Custom Reports tab in the Report Administration utility to upload custom reports from a workstation to Vision. A Vision system administrator must have selected the Allow RDL files to be uploaded in Report Administration check box on the General tab in the Weblink utility before the Custom Reports tab displays in the Report Administration utility
.
Deltek First Vision Essentials Cloud Version
If your firm uses the Deltek First Vision Essentials cloud version, you must add a 10-digit client
ID followed by an underscore as a prefix to the .RDL file name before you upload it into Vision. If the client ID is fewer than 10 digits, add zeros to the beginning of the client ID to make a total of
10 digits. For example, if the client ID is 123456 and you want to name the file “Accounts,” then the .RDL file should be named “0000123456_Accounts.RDL.”
Subreports
If a report has multiple .RDL files (subreports), you must upload each subreport individually.
To upload a custom report from a workstation into Vision, complete the following steps:
1. From the Vision Navigation menu, click Utilities » Report Administration.
2. On the Report Administration form, click the Custom Reports tab.
3. On the Load Custom Reports grid toolbar, click Upload.
4. On the Select custom report file to upload dialog box, select an .RDL file to upload and then click Open.
Custom Reports and Microsoft SQL Server® Reporting Services 50
Load Custom Reports into Vision
5. In the Load Custom Reports grid on the Custom Reports tab, click the Location field, and from the drop-down list, select the Vision Reporting submenu from which you want users to select the report.
For custom reports for any user-defined Info Center, select User Defined Info Center.
See the previous section, “Custom Reports for User-Defined Info Centers,” for more
information about adding the appropriate report type custom property to custom reports for user-defined Info Centers before you upload them into Vision.
6. In the grid, add more reports to upload as needed by repeating the steps above.
If a custom report has subreports, you must add each subreport individually in the grid.
7. Click Save.
Custom Reports and Microsoft SQL Server® Reporting Services 51
Load Custom Reports into Vision
The custom reports are uploaded to your report server and Vision database when you click Save.
You will not see a status bar, and it may take a few minutes to upload.
8. When the reports have finished uploading, click OK on the following dialog box:
In the Load Custom Reports grid, the name of the report now displays in the Name field.
The Status field displays Synchronized, meaning that the report was successfully uploaded from the local machine to the report server and the Vision database; matching copies exist on the report server and in the Vision database.
9. Log out and log back into Vision to see the custom reports added to the submenus under the Reporting menu.
The custom reports also display in the Report Name drop-down list in Configuration »
General » Custom Report Options where you can add parameters to them. Parameters are described in the next section.
Status of a Custom Report
The following are the possible statuses that a custom report can have in the Status field in the
Load Custom Reports grid on the Custom Reports tab:
Synchronized Status — This status displays after you successfully upload a custom report using the Upload option on the Load Custom reports grid toolbar. It signifies that the custom report was uploaded successfully to your report server and the Vision database.
Missing in Report Server Status — This status signifies that the custom report is uploaded to the Vision database (as a backup copy), but it no longer exists on the report server. This could happen if you manually deleted the report on the report server or if you
Custom Reports and Microsoft SQL Server® Reporting Services 52
Load Custom Reports into Vision migrated to a new report server. Because there is a backup copy saved in the Vision database, you can click the Synchronize option on the Load Custom Reports grid menu to re-upload a copy of the backup report in the Vision database to the report server.
Missing in Database Status — This status signifies that a custom report is uploaded to the report server, but it does not have a backup copy saved in the Vision database. This can occur if you are upgrading to Vision 7.6 and you have already uploaded custom reports to the report server in earlier Vision versions—before the custom report status feature was implemented in the software. In this scenario, to upload a copy of the report to the Vision database and change the status of the report to Synchronized, you must delete the report from your report server and upload it again using the Upload option on the Load Custom reports grid toolbar on the Custom Reports tab.
Custom Reports and Microsoft SQL Server® Reporting Services 53
Parameters in Custom Reports
Parameters in Custom Reports
Parameters that you add to a report allow users to filter the report content before they generate the report. For example, you could add a parameter to a report that allows you to enter a period start and end date so that you can include data for only certain periods on the report.
Parameters that you add to a custom report design in the .rdl file, display as options on the
Custom Options tab of the report's Options dialog box in Vision Reporting if you complete both of the following:
In the custom report .rdl file, you must add the prefix "cust" to the parameter name so that it will work with Vision.
The following example shows two parameters with the names custPeriodStartDate and custPeriodEndDate within the XML code of an .rdl file in Report Designer.
After you deploy and load the custom report into Vision with Vision's Report
Administration utility, you add the report parameters to the report in Vision Configuration
» General » Custom Report Options.
To add the parameters in Vision, complete the following steps:
1. From the Vision Navigation menu, click Configuration » General » Custom Report
Options.
2. On the Report Custom Options form, select the custom report from the Report Name drop-down list.
Custom Reports and Microsoft SQL Server® Reporting Services 54
Parameters in Custom Reports
3. On the Options grid toolbar, click grid.
Insert to add a parameter to a blank row in the
4. In the Option Label field, enter the text that you want to display for the parameter on the
Custom Options tab on the Report Options dialog box in Vision Reporting.
5. In the Parameter Name field, enter the name of the parameter as it is entered in the custom report .rdl file but without the prefix "cust."
6. In the Data Type field drop-down list, select the type that matches the data that the parameter contains.
7. Complete the remaining fields in the grid as appropriate for your parameter data type.
8. When you finish, click Save.
To use the parameters before you generate a custom report, complete the following steps:
1. On the Vision Reporting menu, navigate to the custom report location.
2. On the Report form, click the cell of the custom report's Options column to display and click the icon.
Custom Reports and Microsoft SQL Server® Reporting Services 55
Parameters in Custom Reports
3. On the report Options dialog box, click the Custom Options tab to enter parameter options before you print or preview the report.
Custom Reports and Microsoft SQL Server® Reporting Services 56
Apply Role Security to Custom Reports
Apply Role Security to Custom Reports
After a custom report is created and loaded into the Vision software, a Vision system administrator applies Vision role security to allow only the appropriate users to have access to the custom report on the Vision Reporting menu.
To add a custom report to the list of reports that a role can access, complete the following steps:
1. From the Vision Navigation menu, click Configuration » Security » Roles » Access
Rights tab.
2. From the Functional Area field drop-down list, select Reports.
3. From the Report Type field drop-down list, select the type of the report (Accounting,
Accounts Receivable, and so on) for which you want to give access.
4. From the Custom Type field drop-down list, select Custom.
The custom reports for the report type display in the Available Reports pane of the tab.
5. Click the appropriate custom report in the Available Reports pane, and click the Add button to add it to the Reports for this Role pane.
6. When you finish, click Save.
Custom Reports and Microsoft SQL Server® Reporting Services 57
Get Report Information for Failed Reports
Get Report Information for Failed Reports
You use the Get Report Information icon on a previewed Vision standard report to create an .rdl file with which to create a custom report. You can also use this tool to obtain information about custom reports in general or acquire information about a report if the report fails in Vision.
If a report fails when you preview it in Vision, complete the following steps:
1. On the toolbar of the report preview screen, double-click the Get Report Information
icon.
2. Select any of the options that you need to produce the report query, the report options
(XML String), and the report .rdl file (and also an XML file), and then click View.
The options in the drop-down list accomplish the following:
Report Query — This returns the query that was executed by the report. Because the query is returned in XML format, it can be copied and pasted directly into
Microsoft SQL Server Management Studio Query window or onto the Report
Designer Data tab where it can be executed. Since the Report Designer Data tab and
Microsoft SQL Server Management Studio do not execute XML SQL directly, you need to make a few edits. It does not matter if you edit the query in your favorite XML editor or save it to a file.
In either case, you will see something that resembles the following when you view the query information:
<Query><![CDATA[SET TRANSACTION ISOLATION LEVEL READ UNCOMMITTED …
]]></Query>
To run this query within Microsoft SQL Server Management Studio, you must modify the XML to resemble the following:
SET TRANSACTION ISOLATION LEVEL READ UNCOMMITTED
After you complete this modification, the query will execute without issue.
Custom Reports and Microsoft SQL Server® Reporting Services 58
Get Report Information for Failed Reports
Report Options — This returns the options that were selected on the Vision report
Options dialog box when the report was rendered. The options are returned in XML format. This XML cannot be placed within the RDL Code.
Report Definition (RDLFile) — This provides you with the exact .rdl file that was used to load the report instance as it was rendered on the SSRS report server. When you preview this .rdl file within Report Designer, it looks exactly like the one in the
Vision Reporting preview window.
Custom Reports and Microsoft SQL Server® Reporting Services 59
SkipProcessing Custom Property
SkipProcessing Custom Property
You can set the SkipProcessing table-level custom property to Y to have the Vision framework bypass the processing of a tablix data region of a report at runtime. The tablix data region will display what you see in the report design. This custom property applies to reports that are created with either Report Designer or Report Builder. It can be helpful for troubleshooting problems with previewing reports.
Custom Reports and Microsoft SQL Server® Reporting Services 60
Contents of the Vision Report Model
Contents of the Vision Report Model
The Vision custom report model—DeltekVisionReportModel.smdl—contains data sources and
Vision database fields that allow you to create accounting, project, and customer relationship management reports with SSRS's Report Builder.
Field Icons
In Report Builder, you access the Vision report model and select an entity from which to create a report. In the following example, the General Ledger entity is highlighted in the Entities section.
The fields available in the General Ledger entity display in the Fields section below it.
Entities within the Vision report model
Fields within the entity that you selected above
General Ledger Entity and Field List
The field list for an entity displays an icon beside each field to indicate the type of field—text, number, date/time, or aggregate—as in the following example.
Custom Reports and Microsoft SQL Server® Reporting Services 61
Contents of the Vision Report Model
Field Icon Examples
The following table defines the field type icons.
Field Type Icons
Field Icon Type of Field Description a
#
Text
Number
Date/Time
Aggregate
The field contains text.
The field contains a numeric value.
The field contains a date, time, or both.
The field contains a numeric value that represents a calculation on a set of numbers.
Not applicable This displays beside an aggregate or date/time field. Click to display additional options for a field.
Not applicable This displays beside an aggregate or date/time field that you expanded. Click to close the list of additional options.
Custom Reports and Microsoft SQL Server® Reporting Services 62
Contents of the Vision Report Model
#<Vision Entity Name>
In Report Builder, the first item in the Field list for Vision entities is the entity name with a # symbol in front of it. For example, #Project Expense Data Sources displays as the first item for the Vision Project Expense entity.
Entity name is preceded with a
# symbol
When you add this field to a report, it counts the items that are used to compile the information in a row on the report.
For example, you create a project expense report with the following columns.
Project
ABC
Expense Vendor Cost
FedEx $500
Bill
$2,000
#Project Expense Data Sources
27
ABC Knecht's Survey $7,000 $15,000 9
The FedEx cost and bill amounts of $500 and $2,000 are the sum of 27 transactions. The
Knecht's Survey amounts are the sum of 9 transactions.
Aggregate Numeric Fields
In Report Builder, many fields that contain a numeric value have an Additional Options and an Aggregate icon beside them. When you click following example for Total Expense Cost Amount.
icon
, additional options display as in the
Total Expense Cost Amount Example
Each of these numeric options produce es the following content when added to a report:
Custom Reports and Microsoft SQL Server® Reporting Services 63
Contents of the Vision Report Model
Total Expense Cost Amount — This returns the total expense cost amount for all the transactions that make up the expense cost.
# Expense costAmount — This returns the number of transactions (count) used to make up the total expense cost amount.
Avg Expense Cost Amount — This returns the average value of all the transactions that make up the total expense cost amount.
Min Expense Cost Amount — This returns the minimum value of all the transactions that make up the total expense cost amount.
Max Expense Cost Amount — This returns the maximum value of all the transactions that make up the total expense cost amount.
Date/Time Fields
Fields that contain a date, time, or both have a Calendar icon beside them in the Fields list in
Report Builder.
When you click beside the Calendar icon, additional options display, as in the following example of the Expense TransDate.
Expense TransDate Example
Using the Expense TransDate example, each calendar option produces the following content when added to a report. In this example, the transaction date is August 21, 2012, which is a
Tuesday.
Expense TransDate — Returns the full date (08/21/2012).
Expense Trans Day — Returns only the day of the date (Tuesday).
Expense Trans Month — Returns only the month of the date (August).
Expense Trans Year — Returns only the year of the date (2012).
Expense Trans Quarter — Returns the quarter of the date (3).
First Expense Trans Date — Returns the first (earliest) date of all the transactions that are included on the report. This is more commonly included in a report header.
Last Expense Trans Date — Returns the last (latest) date of all the transactions that are included on the report. This is more commonly included in a report header.
Custom Reports and Microsoft SQL Server® Reporting Services 64
Contents of the Vision Report Model
The following sections describe the Vision report model entities and their fields.
When you create a report, you can include only the fields from one entity on a report. For example, when you create a report with the Project entity, you cannot include fields from the
Accounts Payable entity to the report.
Accounts Payable Entity
Use the Accounts Payable entity to create custom Vision Accounts Payable reports. When you use this entity, report content is retrieved directly from or calculated with fields from the following
Vision tables:
VE (Vendor)
VO (Voucher)
LedgerAP (Expense Detail Table — Accounts Payable)
The Accounts Payable entity provides you with the following fields to add to custom reports.
Accounts Payable Field
#Accounts Payable Data
Sources
Check Bank Code
Check Date
Check RefNo
Description
Invoice Date
Invoice Number
PWPCode
Description
When you add this field to a report, it counts the items that were used to compile the information in a row on the report.
The bank code to which vouchers were posted during transaction posting.
The date of the transaction.
The check number that is associated with this payment. This column is used for void check transactions.
The descriptive text for the line item that explains the reason for the expense, such as "travel advance" or "phone bill."
The date entered during either invoice or cash receipt transaction entry.
The billed invoice number of the transaction.
The status of each Pay When Paid (PWP) voucher:
NF — Not found. Indicates that you entered or posted the voucher and the voucher was included on a final bill for the project. This status also displays for all vouchers not marked as PWP.
NP — Not paid. Indicates that you accepted the final invoice and posted the resulting invoice file (that contains the pay when paid voucher).
PD — Paid. Indicates that you posted the cash receipt
(indicating to Vision that the client paid the bill) for the invoice that contained the voucher. The voucher is available for payment processing.
Custom Reports and Microsoft SQL Server® Reporting Services 65
Contents of the Vision Report Model
Accounts Payable Field
Total Voucher Amount
Total Voucher Balance
Total Voucher Discount
Description
The total amount of the voucher before payments and discounts are applied.
The balance owed to the vendor for all vouchers.
The amount of the discount taken to date if discounts were applied to this voucher.
All the previous payments made on the voucher.
Total Voucher Previous
Payments
Vendor
Vendor Name
Vendor Org
Vendor Pay Terms
Vendor SortName
Vendor Status
Vendor Type
Voucher
Voucher Account
Voucher Bank Code
Voucher BilledInvoice
Voucher BilledWBS1
Voucher BilledWBS2
Voucher BilledWBS3
Voucher Date
The vendor identifier. The vendor number may be up to 20 characters, including two user-defined delimiters.
The vendor's name entered in the Vendor Info Center.
The vendor's organization. Used for sorting purposes only.
This is the name of the organization within your company for which this vendor provides goods or services.
The payment terms — Next, Hold, PWP (Pay When Paid),
Partial, or Date.
A combination of the vendor number and name.
The vendor's status — A-Active, I-Inactive, or D-Dormant.
The vendor type such as Trade, Consultant, or Employee.
The voucher number assigned during transaction posting.
The account number for the Vision account that is associated with this voucher. It is specified during Transaction Entry. If the related project is a regular project, this is either a reimbursable or direct account. If the related project is an overhead project, this is an indirect account.
The code for the bank involved in the transaction.
The invoice on which the transaction was final billed.
The project to which the transaction was final billed on the invoice.
The phase to which the transaction was final billed on the invoice.
The task to which the transaction was final billed on the invoice.
The date of the voucher.
Custom Reports and Microsoft SQL Server® Reporting Services 66
Contents of the Vision Report Model
Accounts Payable Field
Voucher Desc2
Voucher LiabCode
Voucher Line
Voucher Payment Date
Voucher SubType
Voucher TransType
Voucher WBS1
Voucher WBS2
Voucher WBS3
Description
Descriptive text for the line item to explain the reason for the expense (such as "travel advance," "phone bill," and so on).
The accounts payable liability code to which this voucher was posted.
The liability code identifies the account that receives the implicit posting during Accounts Payable Voucher Posting; the liability code defines the credit posting in the General Ledger.
If your firm uses the Organization application and you maintain separate balance sheets by organization, the liability code also points to an organization code.
The line number for each item listed on the voucher.
The payment due date if the Pay Terms setting is Date.
A one-letter code that represents the transaction's sub-type (for example, A for automatic check, C for disbursement check, or V for voided check). See Transaction Types in the Accounting
Concepts help for a full listing.
A two-letter code that represents the type of transaction (for example, PP for Accounts Payable payment processing). See
Transaction Types in the Accounting Concepts help for a full listing.
The project associated with the voucher that is specified during transaction entry.
The phase associated with the voucher that is specified during transaction entry.
The task associated with the voucher that is specified during transaction entry.
Accounts Receivable Entity
Use the Accounts Receivable entity to create custom Vision Accounts Receivable reports. When you use this entity, report content is retrieved directly from or calculated with fields from the following Vision database tables:
LedgerAR (Expense Detail Table — Accounts Receivable
CFGARMap (Configuration Table — Accounts Receivable Mapping)
PR (Project)
AR (Invoice Master)
CL (Client)
BTBGSubs (Billing Terms Billing Group Subprojects)
CFGInvMap (Configuration Table - Invoice Mapping Accounts)
Custom Reports and Microsoft SQL Server® Reporting Services 67
Contents of the Vision Report Model
EM (Employee)
The Accounts Receivable entity provides you with the following fields to add to custom reports.
Accounts Receivable Field Description
#Accounts Receivable
Data Sources
Account
When you add this field to a report, it counts the items that were used to compile the information in a row on the report.
The accounts receivable account to be mapped to the Accounts
Receivable Ledger columns.
The client's billing address.
BillClAddress
BillClientID
BillContactID
ClAddress
The record number for the billing client.
The record number for the billing contact.
The client address.
ClientID
CRComment
InvComment
Invoice Description
InvoiceNumber
The number of the client that is associated with the transaction.
The full text of the cash receipt comment.
The full text of the invoice comment.
If Receipt displays in the Invoice column, Vision displays the reference number entered during Cash Receipt Transaction
Entry. This column may also display the invoice number, the year and month, and the number of postings for the accounting period against which the report is being run.
The invoice number that is associated with the transaction at the time of posting or the final invoice number assigned to the invoice during a final billing session.
The date on which the cash receipt was issued.
RecDate
RecType
RefNo
The transaction type for the cash receipt expense detail. See
Transaction Types in the Vision Accounting Concepts help for a full listing.
The reference number that is associated with the transaction during transaction entry.
Total Age 1 Amount–Total
Age 5 Amount
Fields that represent additional aging ranges on invoices. By default, Vision has the following aging columns:
Age
1
2
3
4
5
Invoice Falls in the period:
0 to 30 days
31 to 60 days
61 to 90 days
91 to 120 days
121 days and older
Custom Reports and Microsoft SQL Server® Reporting Services 68
Contents of the Vision Report Model
Accounts Receivable Field Description
Total Col 1 – Tot Col 8
Total Period
Total Post Seq
Total Rtn Amt
Total Total Amt
TransDate
WBS1
WBS1Name
WBS2
WBS2Name
WBS3
WBS3Name
The Accounts Receivable mapped amounts in Configuration »
Accounts Receivable.
The fiscal year and period for the expense detail.
The unique number assigned to the transaction during posting.
The retainage amount of the invoice not currently due.
Retainage is an amount that you withhold from billing a client, as a good faith measure to build trust in your firm, or to entice the client to hire your firm.
The total amount of the invoice and the total amount of each receipt for that invoice. The total is then distributed across the appropriate user-defined columns (customCol1-customcol15), such as the Fees, Reimb., Taxes, Interest, and Other columns. The total of these user-defined columns should equal the amount in the Total column (TotalAmt).
The date of the transaction.
The project number associated with the transaction.
The project name associated with the transaction.
The phase number associated with the transaction.
The phase name associated with the transaction.
The task number associated with the transaction.
The task name associated with the transaction.
Client Entity
Use the Client entity to create client reports. When you use this entity, report content is retrieved from or calculated with fields from the following Vision database tables:
CL (Client)
CFGClientStatus (Configuration Table — Client Status)
ClAddress (Client Address)
CFGClientType (Configuration Table — Client Types)
CFGCountry (Configuration Table — Countries)
ClientCustomTabFields (Clients Table — User-Defined Tab Fields)
The Client entity provides you with the following fields to add to custom reports.
Client Field Description
Custom Reports and Microsoft SQL Server® Reporting Services 69
Contents of the Vision Report Model
Client Field
#Client Data Sources
Billing Address
Description
Billing Address1–Billing
Address4
Billing City
Billing Country
Billing Create Date
Billing Create User
Billing Fax
Billing Mod Date
Billing Mod User
Billing Phone
Billing State
Billing Tax Country
Billing Tax Registration
Number
Billing Zip
Client Name
Client Number
Create Date
Create User
Mod Date
Mod User
Description
When you add this field to a report, it counts the items that were used to compile the information in a row on the report.
The description that is entered in the Client Info Center to identify the client's billing address, such as Company
Headquarters, Main Office, Billing Office, and so on.
The client's billing address information from Address 1 –
Address 4 lines in the Client Info Center.
The city from the client's billing address.
The country from the client's billing address.
The date on which the billing address was created in the client record.
The user ID of the person who created the billing address in the client record.
The fax number of the billing client contact.
The date on which the billing address was most recently modified in the client record.
The user ID of the last person who modified the billing address in the client record.
The phone number of the billing client contact.
The state from the client's billing address.
The tax country code from the client's billing address.
The tax registration number from the client's billing address.
The ZIP code from the client's billing address.
The name of the firm (client) for whom you are performing work.
The client identifier.
The date on which the client record was created.
The user who created the client record.
The date on which the client record was last modified.
The user ID of the person who most recently modified the client record.
Custom Reports and Microsoft SQL Server® Reporting Services 70
Contents of the Vision Report Model
Client Field Description
Notes
Primary Address Create
Date
Primary Address Create
User
Primary Address
Description
The text that is entered in the Notes field on the General tab of the Client Info Center.
The date on which the primary address was created in the client record.
The user ID of the person who created the primary address in the client record.
The description entered in the Client Info Center record to identify the client's primary address, such as Company
Headquarters, Main Office, Northeast Office, and so on.
Primary Address Mod Date
The date on which the primary address was most recently modified in the client record.
Primary Address Mod User The user ID of the last person who modified the primary address in the client record.
Primary Address1–Primary
Address4
The client's primary address information from Address 1 –
Address 4 lines in the Client Info Center.
Primary City
The city in which the client's primary address is located.
Primary Country
Primary Fax
Primary Phone
Primary State
Primary Tax Registration
Number
Primary TaxCountry
Primary Zip
Relationship
Status
Type
Website
The country in which the client's primary address is located.
The fax in which the client's primary address is located.
The phone in which the client's primary address is located.
The state in which the client's primary address is located.
The tax registration number for the client's primary address.
The tax country code for the client's primary address.
The ZIP code in which the client's primary address is located.
Your relationship with the client, such as Consultant,
Prospective, Existing.
The status of your relationship with the client (Active, Dormant, or Inactive).
The type of client such as Commercial, Government, Non-Profit, and so on.
The client firm's Internet Web site address.
Custom Reports and Microsoft SQL Server® Reporting Services 71
Contents of the Vision Report Model
Contact Entity
Use the Contact entity to create contact reports. When you use this entity, report content is retrieved from or calculated with fields from the following Vision database tables:
Contacts
CL (Client)
VE (Vendor)
The Contact entity provides you with the following fields to add to custom reports.
Contact Field
#Contact Data Sources
Active Company
Address1–Address4
Cell Phone
City
Client Address1–Client
Address4
Client City
Client Country
Client Fax
Client ID
Client Memo
Client Name
Client Phone
Client Relationship
Client State
Client Status
Client Website
Description
When you add this field to a report, it counts the items that were used to compile the information in a row on the report.
If you use the Multicompany feature in Vision, this is the company that you have open when you run a report.
Lines 1–4 of the contact's address.
The contact's cellular phone number that is entered on the
General tab in the Contact Info Center.
The contact's city.
The client's address information (street name and number, suite number, and P.O. Box number) if the contact is a client.
The client's city if the contact is a client.
The client's country if the contact is a client.
The client's fax number if the contact is a client.
The internal reference number for the Client record.
The contents of the Notes field in the Clients Info Center if the contact is a client.
The client firm's name if the contact is a client.
The client's telephone number if the contact is a client.
Your relationship (New, Existing, or Prospective) with the client.
The client's state if the contact is a client.
The client's status (A-Active, I-Inactive, or D-Dormant) that is entered on the General tab in the Client Info Center if the contact is a client.
The client's Web Site address that is entered on the General tab in the Client Info Center if the contact is a client.
Custom Reports and Microsoft SQL Server® Reporting Services 72
Contents of the Vision Report Model
Contact Field
Client Zip
Concat Client Address
Concat Vendor Address
Concatenated Address
Contact ID
Contacts Notes
Country
Create Date
Create User
Fax
First Name
Full Name
Home Phone
Last Name
Mailing Address
Mailing Address1–Mailing
Address4
Mailing City
Mailing Country
Description
The client's ZIP code if the contact is a client.
The client's address, city, state, and ZIP code (in this order in a single column on the report) if the contact is a client.
The vendor's address, city, state, and ZIP code (in this order in a single column on the report) if the contact is a vendor.
The contact's address, city, state, and ZIP code (listed in this order in a single column on the report).
Internal reference number for the contact record.
The contents of the Notes field on the General tab in the
Contacts Info Center for the contact.
The contact's country.
The date on which the contact record was created.
The user who created the contact record.
The contact's email address that is entered on the General tab in the Contact Info Center.
The contact's fax number that is entered on the General tab in the Contact Info Center.
The contact's first name that is entered on the General tab in the
Contact Info Center.
The contact's full name (first, middle, and last names), which is entered on the General tab in the Contact Info Center.
The contact's home phone number that is entered on the
General tab in the Contact Info Center.
The contact's last name that is entered on the General tab in the
Contact Info Center.
A Y or N (Yes or No) value that indicates whether or not the address is the contact's mailing address.
Address lines 1–4 from the contact's mailing address. The mailing address is entered on the General tab in the Contact
Info Center.
The city from the contact's mailing address.
The country from the contact's mailing address.
Custom Reports and Microsoft SQL Server® Reporting Services 73
Contents of the Vision Report Model
Contact Field
Mailing State
Mailing Zip
Middle Name
Mod Date
Mod User
Pager
Phone
Preferred Name
Salutation
Source
State
Status
Suffix
Title
Type
Vendor
Vendor Address
Description
The state from the contact's mailing address.
The ZIP code from the contact's mailing address.
The contact's middle name from the General tab in the Contact
Info Center.
The date on which the contact record was most recently modified.
The user who last modified the contact record.
The contact's pager number from the General tab in the Contact
Info Center.
The contact's telephone number from the General tab in the
Contact Info Center.
The contact's preferred name from the General tab in the
Contact Info Center.
The prefix, such as Mr. or Ms., used with the contact's name.
The source that is entered in the lead's Info Center record when the contact is a converted lead.
The contact's state.
The status of your relationship (Active or Inactive) with the contact, as entered on the General tab in the Contact Info
Center.
The suffix, such as Jr. or III, used with the contact's name.
The contact's job title that is entered on the General tab in the
Contact Info Center.
The type (Client or Vendor) by which the contact is classified.
The internal reference number for the vendor record.
A Y or N (Yes or No) value that indicates whether or not the address is a vendor address.
The associated vendor's' address from Address 1–Address 4.
Vendor Address1–Vendor
Adddress4
Vendor City
Vendor Country
The vendor's city if the contact is a vendor.
The vendor's country if the contact is a vendor.
Custom Reports and Microsoft SQL Server® Reporting Services 74
Contents of the Vision Report Model
Contact Field
Vendor Fax
Vendor Memo
Vendor Name
Vendor Phone
Vendor Specialty
Vendor State
Vendor Website
Vendor Zip
Zip
Description
The vendor's fax number if the contact is a vendor.
The contents of the Notes field in the Vendor Info Center if the contact is a vendor.
The vendor's name if the contact is a vendor.
The vendor's phone number if the contact is a vendor.
The vendor's business specialty (Interior Design, Security
Systems, and so on) if the contact is a vendor.
The vendor's state if the contact is a vendor.
The vendor's Web Site address if the contact is a vendor.
The vendor's ZIP code if the contact is a vendor.
The contact's ZIP code.
Employee List Entity
Use the Employee List entity to create employee reports. When you use this entity, report content is retrieved from or calculated with fields from the EM (Employee) database tables.
The Employee List entity provides you with the following fields to add to custom reports.
Employee List Field Description
#Employee Data Source
Do Not Include Labors
Active Company
When you add this field to a report, it counts the items that were used to compile the information in a row on the report.
If you use the Multicompany feature in Vision, this is the company that you have open when you run a report.
Address Line 1–Address
Line 3
Approved for use in accounting applications
Available For CRM users
The first, second, and third lines of the employee's address that are entered in the Employee Info Center.
Allow Employee to change in Timesheet
Indicates whether or not the Allow Employee to change in
Timesheet check box is selected in the Default Labor Code section of the Time tab in the Employee Info Center.
A variable that determines whether or not the employee record is approved for use when accounting transactions are processed.
A variable that allows Customer Relationship Management users to open and review the employee record.
Available to Accounting users
A variable that allows Accounting users to open and review the employee record.
Custom Reports and Microsoft SQL Server® Reporting Services 75
Contents of the Vision Report Model
Employee List Field Description
Billing Status
Check hours entered against expected
Indicates the billing status for the labor transaction. The options are:
B — Billable. Released and available for billing to the client.
D — To be deleted. The transaction is marked for deletion.
F — Final billed. Already billed to the client.
H – Held. Temporarily hold the transaction to prevent billing to the client.
M — Modified. Changed in some way from its original form.
N — Not billable.
O — Deleted. A transaction marked for deletion was included in a billing run (and has been deleted).
R — Partial Hold/Released. Part of the transaction has already been held or released.
T — Transferred. Moved from one project, phase, task, or labor code to another.
W — To be written off. Transaction has been written off, but the invoice has not been posted.
X — Written off. Transaction has been written off, and the invoice has been posted.
A Y or N (Yes or No) column that indicates whether or not Vision automatically checks the hours that are entered on an employee's timesheet and compares them to the expected hours per day setting. This check box is on the Time tab in the
Employee Info Center.
The employee's city.
City
Country
Create Date
Create User
The employee's country.
The date on which the employee record was created.
The user who created the employee record.
Default Labor Code Level 1 The level 1 default labor code for Time timesheets for an employee that is entered on the Time tab in the Employee Info
Center.
Default Labor Code Level 2 The level 2 default labor code for Time timesheets.
Default Labor Code Level 3 The level 3 default labor code for Time timesheets.
Default Labor Code Level 4 The level 4 default labor code for Time timesheets.
Default Labor Code Level 5 The level 5 default labor code for Time timesheets.
Custom Reports and Microsoft SQL Server® Reporting Services 76
Contents of the Vision Report Model
Employee List Field
Employee First Name
Employee Last Name
Employee Middle Name
Employee Name
Employee Number
Employee Organization
Name
Employee Organization
Name
Employee Salutation
Employee Suffix
Employee Type
Expense Report
Administration Approval
Expense Report
Administration Editing
Expense Report
Administration Level
Expense Report Group
Fax
Hire Date
Description
The employee's email address.
The employee's first name.
The employee's last name.
The employee's middle name.
The employee's last name, first name.
The employee's identification number.
The organization (profit center) description of the organization to which the employee belongs.
The organization (profit center) code of the organization to which the employee belongs.
The prefix (Mr., Mrs., Ms., and so on) used with an employee's name.
The suffix (Jr., III, and so on) used with an employee's name.
The employee type (Principal-P, E-Employee, M-Management, and so on) that is entered on the Accounting tab in the
Employee Info Center.
A Y or N (Yes or No) value that indicates whether or not the employee can approve, before it is posted, any expense report to which he or she has access. This column is blank if the expense report admin level is Group. This option is on the
Expenses tab in the Employee Info Center.
A Y or N (Yes or No) value that indicates whether or not the employee can edit any expense report to which he or she has access. This column is blank if the expense report admin level is
Group. This option is on the Expenses tab in the Employee Info
Center.
The expense report administrative level for an employee, which can be: Staff, Group, or System. This setting is on the Expenses tab in the Employee Info Center.
The expense report group for which this employee is able to access expense reports. This setting is on the Expenses tab in the Employee Info Center.
The employee's fax number.
The employee's hire date.
Custom Reports and Microsoft SQL Server® Reporting Services 77
Contents of the Vision Report Model
Employee List Field Description
Home Phone
Job Cost Type
Labor Billing Category
Memo
Mobile Phone
Modify Date
Modify User
Pay Type
Raise Date
Social Security Number
State
Status
Supervisor Name
Supervisor Number
Termination Date
The employee's home phone number.
The employee's job cost type (H-Hourly or S-Salaried) that is entered on the Accounting tab in the Employee Info Center.
The default category for the employee when the By Category labor billing method is used.
The Memo field on the Personal tab in the Employee Info
Center that contains comments about the employee.
The employee's mobile phone number.
The date on which the employee record was last modified.
The last user who modified the employee record.
The payroll type for the employee — Hourly or Salary.
The date of the employee's next raise that is entered on the
Personal tab in the Employee Info Center.
The employee's Social Security number that is entered on the
Personal tab in the Employee Info Center.
The employee's state that is entered on the Personal tab in the
Employee Info Center.
The employee's employment status (A-Active, I-Inactive, or
T-Terminated) that is entered on the General tab in the
Employee Info Center.
The name of the employee's supervisor that is entered on the
General tab in the Employee Info Center.
The employee number of the employee's supervisor.
The date that the employee was terminated from employment.
This is entered on the Personal tab in the Employee Info Center.
Timesheet Administration
Approval
Timesheet Administration
Editing
A Y or N (Yes or No) value to indicate whether the employee can approve, before it is posted, any timesheet to which he or she has access. This option is on the Time tab in the Employee
Info Center. This column is blank if the timesheet admin level is
Group.
A Y or N (Yes or No) value to indicate whether an employee can edit any timesheet to which he or she has access. This option is on the Time tab in the Employee Info Center. This column is blank if the timesheet admin level is Group.
Custom Reports and Microsoft SQL Server® Reporting Services 78
Contents of the Vision Report Model
Employee List Field Description
Timesheet Administration
Level
Timesheet Group
Title
Total Hours Day
Total Pay Overtime Pct
Total Pay Rate
The timesheet administrative level (Staff, Group, or System) for an employee that is entered on the Time tab in the Employee
Info Center.
The timesheet group for which this employee is able to access timesheets. This is entered on the Time tab in the Employee
Info Center.
The employee's title (job title, job function) that is entered on the
General tab in the Employee Info Center.
The number of hours per day that the employee is generally expected to work (entered on the Personal tab in the Employee
Info Center).
The percentage that is applied to the employee's payroll rate to calculate standard overtime wages.
The employee's actual pay amount per payroll period (payroll periods can be weekly, biweekly, semimonthly, or monthly).
Total Pay Special Overtime
Pct
The percentage to apply to the employee's payroll rate to calculate secondary overtime wages.
Total Period
Total Posting Seq
The fiscal period during which the posting was made.
The transaction's posting sequence number that is assigned by
Vision during the posting process.
Total Provisional Bill Ovt 2
Pct
The percentage applied to secondary overtime hours on unposted timesheet entries when labor charges are calculated at billing rates.
Total Provisional Bill Ovt
Pct
The percentage applied to overtime hours on unposted timesheet entries when labor charges are calculated at billing rates.
Total Provisional Bill Rate
The billing rate applied to unposted timesheet entries for this employee when labor charges are calculated.
Total Provisional Cost Ovt
2 Pct
The percentage applied to secondary overtime hours on unposted timesheet entries when the labor charges are calculated at cost rates.
Total Provisional Cost Ovt
Pct
The percentage applied to overtime hours on unposted timesheet entries when labor charges are calculated at cost rates.
Total Provisional Cost
Rate
The cost rate applied to unposted timesheet entries for this employee when labor charges are calculated.
Total Special Overtime
The secondary overtime percentage from the employee record
Custom Reports and Microsoft SQL Server® Reporting Services 79
Contents of the Vision Report Model
Employee List Field
Percent
Total Special Overtime
Rate
Description
that is used to derive the special overtime rate for the transaction. An employee's hourly rate is multiplied by the special overtime percentage to calculate the employee's special overtime rate.
The rate at which special overtime hours were multiplied to derive the special overtime amount for the transaction. Vision multiplies an employee’s hourly rate by the employee's secondary overtime percentage to calculate the special overtime rate.
Total Target Ratio
The percentage of an employee's time expected to be charged to regular (revenue-producing) projects (entered on the
Accounting tab in the Employee Info Center).
Total Years W Other Firms
The number of years the employee worked with other firms
(entered on the General tab in the Employee Info Center).
Trans Type
Use total hours as standard on Time Analysis
A Y or N (Yes or No) value that indicates whether or not standard hours or amounts are calculated and displayed for employees on the Time Analysis report.
Vendor Indicator
The type of transaction: TS (Timesheet transaction) or LA
(Labor adjustment transaction).
A Y or N (Yes or No) value that indicates whether or not the employee is a consultant.
Vendor Name
Vendor Number
Work Phone
Work Phone Ext
ZIP
The associated vendor's descriptive name.
The associated vendor's identification number.
The employee's work phone number.
The employee's work phone number extension.
The employee's ZIP code.
Employee Include Labor Entity
Use the Employee Include Labor entity to create custom Vision employee reports. When you use this entity, report content is retrieved directly from, or calculated with fields from, the following
Vision database tables:
EM (Employee)
LD (Labor Detail)
CFGEmployeeType, CFGEmployeeStatus, and CFGEmployeeGroup (Employee
Configuration tables)
VE (Vendor)
Organization
Custom Reports and Microsoft SQL Server® Reporting Services 80
Contents of the Vision Report Model
BTLaborCats (Billing Configuration Table — Labor Categories)
PR (Project)
The Employee Include Labor entity provides you with the following fields to add to custom reports.
Employee Include Labor
Field Description
#Employee Data Source
Include Labors
Active Company
Address Line 1–Address
Line 3
Allow Employee to change in Timesheet
Approved for use in accounting applications
Available for Accounting users
Available for CRM users
When you add this field to a report, it counts the items that were used to compile the information in a row on the report.
If you use the Multicompany feature in Vision, this is the company that you have open when you run a report.
First, second, and third lines of the employee's address from the Employee Info Center.
A Y or N (Yes or No) value that indicates whether or not the employee can modify the default labor code on timesheets. If it is set to Y, the employee can charge time to a labor code other than the default. This check box is on the Time tab in the
Employee Info Center.
Indicates whether or not the record is approved for use in transaction processing. You may not need to include this field on a report but it may be useful when you build queries.
Indicates whether or not the record is available to accounting users. You may not need to include this field on a report but it may be useful when you build queries.
Indicates whether or not the record is available to Customer
Relationship Management users. You may not need to include this field on a report but it may be useful when you build queries.
Custom Reports and Microsoft SQL Server® Reporting Services 81
Contents of the Vision Report Model
Employee Include Labor
Field Description
Billing Status
Check hours entered against expected
City
Indicates the billing status for the labor transaction. The options are:
B — Billable. Released and available for billing to the client.
D —To be deleted. The transaction is marked for deletion.
F — Final billed. Already billed to the client.
H – Held. Temporarily hold a transaction to prevent billing to the client.
M — Modified. Changed in some way from its original form.
N — Not billable.
O — Deleted. A transaction marked for deletion was included in a billing run (and has been deleted).
R — Partial Hold/Released. Part of the transaction has already been held or released.
T — Transferred. Moved from one project, phase, task, or labor code to another.
W — To be written off. Transaction has been written off, but the invoice has not been posted.
X — Written off. Transaction has been written off, and the invoice has been posted.
A Y or N (Yes or No) value that indicates whether or not Vision compares hours posted with hours expected.
If set to Y (on the Time tab of the Employee Info Center),
Vision automatically checks the hours entered on the employee's timesheet and compares them with the expected hours per day setting.
The city in which the employee resides (entered in the
Employee Info Center).
Comment
Country
Timesheet comments.
The country in which the employee resides (entered in the
Employee Info Center).
The date on which the employee record was created.
Create Date
Create User
The user who created the employee record.
Default Labor Code Level 1
Level 1 default labor code that appears on the employee's timesheet when he or she charges time to a project.
Custom Reports and Microsoft SQL Server® Reporting Services 82
Contents of the Vision Report Model
Employee Include Labor
Field Description
Default Labor Code Level 2
Level 2 default labor code that appears on the employee's timesheet when he or she charges time to a project.
Default Labor Code Level 3
Level 3 default labor code that appears on the employee's timesheet when he or she charges time to a project.
Default Labor Code Level 4
Level 4 default labor code that appears on the employee's timesheet when he or she charges time to a project.
Default Labor Code Level 5
Level 5 default labor code that appears on the employee's timesheet when he or she charges time to a project.
The employee's email address (entered in the Employee Info
Center).
Employee First Name
The employee's first name (entered in the Employee Info
Center).
Employee Last Name
Employee Middle Name
Employee Name
Employee Number
The employee's last name (entered in the Employee Info
Center).
The employee's middle name (entered in the Employee Info
Center).
The employee's last name, first name, and middle initial (if included on the employee's record).
The individual's unique employee identification number
(entered in the Employee Info Center).
Employee Organization
Name
Employee Organization
Code
Employee Salutation
Employee Suffix
Employee Type
Expense Report
The name of the organization that is associated with the employee in the Employee Info Center. This value is stored in the Name field of the Organization table. If your firm does not use the Organization application, this field does not display.
The organization number (all levels) of the employee's organization. If your firm does not use Vision's Organization application, this field does not display.
The prefix, such as Ms. or Mr., to use with this employee's name that is entered in the Employee Info Center.
The suffix , such as Jr. or Sr., to use with this employee's name that is entered in the Employee Info Center.
The description or label of the employee's employee type, such as Principal, Manager, or Employee that is entered in the
Employee Info Center. This value is stored in the Label field of the CFGEmployeeType table.
A Y or N (Yes or No) value that indicates whether or not the
Custom Reports and Microsoft SQL Server® Reporting Services 83
Contents of the Vision Report Model
Employee Include Labor
Field
Administration Approval
Expense Report
Administration Editing
Expense Report
Administration Level
Expense Report Group
Fax
Hire Date
Home Phone
Job Cost Type
Labor Billing Category
Labor Code1
LD Key
Memo
Mobile Phone
Modify Date
Modify User
Description
employee can approve, before it is posted, any expense report to which he or she has access. This column is blank if the expense report admin level is Group. This option is on the
Expenses tab in the Employee Info Center.
A Y or N (Yes or No) value that indicates whether or not the employee can edit any expense report to which he or she has access. This column is blank if the expense report admin level is Group. This option is on the Expenses tab in the Employee
Info Center.
The expense report administrative level for an employee, which can be: Staff, Group, or System. This setting is on the
Expenses tab in the Employee Info Center.
The expense report group for which this employee is able to access expense reports. This setting is on the Expenses tab in the Employee Info Center.
The employee's fax number that is entered in the Employee
Info Center.
The date on which the employee was hired.
The employee's phone number that is entered in the Employee
Info Center.
The employee's job cost type (H-Hourly or S-Salaried) that is entered on the Accounting tab in the Employee Info Center.
The label for the labor category that is entered for an employee in the Employee Info Center.
Employee's labor code for the task, phase, or project. An employee may be assigned different labor codes on different projects according to the work that the employee performs.
This is a primary key internal to the Vision LD table. Do not
add this to your report. This key is stored in the PKey field of the LD table.
The text that is entered in the Memo field on the Personal tab of the Employee Info Center.
The employee's cellular phone number that is entered in the
Employee Info Center.
The date on which the employee record was last modified.
The last user who last modified the employee record.
Custom Reports and Microsoft SQL Server® Reporting Services 84
Contents of the Vision Report Model
Employee Include Labor
Field
Pay Type
Phase
Phase Name
Project
Project Name
Raise Date
Social Security Number
State
Status
Supervisor Name
Supervisor Number
Task
Task Name
Termination Date
Timesheet Administration
Approval
Description
The pay type (Hourly or Salary) that is entered on the Payroll tab in the Employee Info Center for an employee.
The identifier of the phase for which an employee reported hours worked.
The name of the phase for which an employee reported hours worked. This is the phase's short name that is entered in the
Project Info Center.
The identifier of the project for which an employee reported hours worked.
The name of the project for which an employee reported hours worked. This is the project's short name that is entered in the
Project Info Center.
The date of an employee's last raise that is entered on the
Personal tab in the Employee Info Center.
An employee's Social Security number that is entered in the
Employee Information Center.
The state where the employee resides, that is entered in the
Employee Info Center.
An employee's status (Active, Inactive, or Terminated) that is entered in the Employee Info Center.
The name of the employee's supervisor that is entered in the
Employee Info Center.
The employee number of an employee's supervisor.
The identifier of the task for which the employee reported hours worked.
The name of the task (the task's short name entered in the
Project Info Center).
The date on which the employee last worked for your firm
(entered on the Personal tab in the Employee Info Center).
Indicates the timesheet administration approval rights of the employee. If set to Y, the employee can approve any timesheet to which he or she has access before it is posted.
Custom Reports and Microsoft SQL Server® Reporting Services 85
Contents of the Vision Report Model
Employee Include Labor
Field
Timesheet Administration
Editing
Timesheet Administration
Level
Timesheet Group
Title
Total Current Billing
Extension
Total Current Overtime
Amount
Total Current Overtime
Hours
Total Current Regular
Amount
Total Current Regular
Hours
Total Current Special
Overtime Amount
Description
A Y or N (Yes or No) value that indicates whether or not an employee can edit any timesheet to which he or she has access. This option is on the Time tab in the Employee Info
Center. This column is blank if the timesheet admin level is
Group.
The timesheet administrative level (Staff, Group, or System) for an employee that is entered on the Time tab in the Employee
Info Center.
The timesheet group for which this employee is able to access timesheets. This is entered on the Time tab in the Employee
Info Center.
The employee's title (job title) that is entered in the Employee
Info Center.
For the current accounting period, the extended amount (Hours x Rate) based on the current billing terms.
For the current accounting period, the amount calculated for overtime hours for the task, phase, or project. Vision Reporting calculates overtime costs for hourly employees differently than it does for salaried employees:
For hourly employees, the overtime amount is calculated as:
Overtime hours x Hourly labor costing rate x Overtime percentage
For salaried employees, Vision begins by calculating the employee's annualized hourly rate, using this equation:
Annual salary / Estimated annual regular hours, defined as hours per week x 52
Then it calculates the overtime amount as:
Overtime hours x Annualized hourly rate x Overtime percentage
The number of overtime hours for the task, phase, or project for the current accounting period.
For the current accounting period, the monetary amount calculated based on regular hours posted for the task, phase, or project. This amount is calculated as regular hours worked multiplied by the labor cost rate.
The number of regular hours for the task, phase, or project for the current accounting period.
For the current accounting period, the amount calculated for special overtime hours for the task, phase, or project.
Custom Reports and Microsoft SQL Server® Reporting Services 86
Contents of the Vision Report Model
Employee Include Labor
Field Description
Total Current Special
Overtime Hours
Total Hours Day
Total Job Cost Ovt 2 Pct
Total Job Cost Ovt Pct
For the current accounting period, the number of special (or secondary) overtime hours for the task, phase, or project.
Special overtime is overtime that is costed and paid at a different rate than standard overtime. If you pay separately for special overtime, you must record these hours separately on the timesheet. You set up secondary overtime on the
Accounting tab of the Employee Info Center.
The number of hours per day the employee is generally expected to work.
The percentage of the employee's hourly wage that is costed to projects when the employee works secondary overtime hours.
The percentage of the employee's hourly wage that is costed to projects when the employee works standard overtime hours.
Total Job Cost Rate
The employee's job cost rate, which is the rate at which an employee’s hours are costed to a project.
Total JTD Billing Extension
The extended amount (Hours x Rate) based on the current billing terms job-to-date.
Total JTD Overtime Amount
The job-to-date amount calculated for overtime hours.
Total JTD Overtime Hours The number of overtime hours posted job-to-date.
Total JTD Regular Amount
The job-to-date amount calculated for regular hours.
Total JTD Regular Hours
The job-to-date number of regular hours reported.
Total JTD Special Overtime
Amount
The job-to-date amount calculated for special overtime hours.
Total JTD Special Overtime
Hours
The number of special overtime hours posted job-to-date.
Total Pay Overtime Pct
The percentage applied to the employee's payroll rate to calculate standard overtime wages.
Total Pay Rate
The employee's actual pay amount per payroll period (payroll periods can be weekly, biweekly, semimonthly, or monthly).
Total Pay Special Overtime
Pct
The percentage to apply to the employee's payroll rate to calculate secondary overtime wages. This can be useful if you must pay certain overtime hours at a rate that differs from the employee's standard overtime rate.
Total Period
The fiscal period during which the posting was made.
Custom Reports and Microsoft SQL Server® Reporting Services 87
Contents of the Vision Report Model
Employee Include Labor
Field Description
Total Posting Seq
Total Provisional Bill Ovt 2
Pct
Total Provisional Bill Ovt
Pct
Total Provisional Bill Rate
The transaction's posting sequence number that is assigned by
Vision during the posting process.
The percentage that Vision applies to secondary overtime hours on unposted timesheet entries to calculate labor charges at billing rates.
The percentage that Vision applies to overtime hours on unposted timesheet entries to calculate labor charges at billing rates.
The billing rate that Vision applies to unposted timesheet entries for this employee to calculate labor charges.
Total Provisional Cost Ovt 2
Pct
The percentage that Vision applies to secondary overtime hours on unposted timesheet entries to calculate labor charges at cost rates.
Total Provisional Cost Ovt
Pct
The percentage that Vision applies to overtime hours on unposted timesheet entries to calculate labor charges at cost rates.
Total Provisional Cost Rate
The cost rate that Vision applies to unposted timesheet entries for this employee to calculate labor charges.
Total Special Overtime
Percent
The secondary overtime percentage from the employee record that is used to derive the special overtime rate for the transaction. Vision multiplies an employee's hourly rate by the special overtime percentage to calculate the employee's special overtime rate.
Total Special Overtime Rate
The rate at which special overtime hours are multiplied to derive the special overtime amount for the transaction. Vision multiplies an employee’s hourly rate by the employee's secondary overtime percentage to calculate the special overtime rate.
Total Target Ratio
The percentage of an employee's time expected to be charged to regular (revenue-producing) projects, as established in the
Employee Info Center.
Total Years W Other Firms
The number of years that the employee worked for other firms as entered in the Employee Info Center.
Total YTD Billing Extension
The year-to-date extended amount (Hours x Rate) based on the current billing terms.
Total YTD Overtime Amount The year-to-date amount calculated for overtime hours.
Total YTD Overtime Hours
The year-to-date number of overtime hours posted.
Custom Reports and Microsoft SQL Server® Reporting Services 88
Contents of the Vision Report Model
Employee Include Labor
Field Description
Total YTD Regular Amount
The year-to-date amount calculated for regular hours.
Total YTD Regular Hours
The year-to-date number of regular hours posted.
Total YTD Special Overtime
Amount
The year-to-date amount calculated for special overtime hours.
Total YTD Special Overtime
Hours
The year-to-date number of special overtime hours posted.
Trans Date
The date when the transaction was posted.
Trans Type
Use total hours as standard on Time Analysis
A Y or N (Yes or No) value that indicates whether or not standard hours or amounts for employees are calculated and displayed on the Time Analysis report:
Vendor Indicator
The type of transaction — TS (Timesheet transaction) or LA
(Labor adjustment transaction).
A Y or N (Yes or No) value that indicates whether or not the employee is a consultant.
Vendor Name
Vendor Number
Work Phone
The name of the vendor if the Vendor Indicator is Y.
The identification number of the vendor.
The employee's work phone number from the Employee Info
Center.
Work Phone Ext.
Zip
The employee's work extension.
The employee's ZIP code from the Employee Info Center.
General Ledger Entity
Use the General Ledger entity to create custom Vision general ledger reports. When you use this entity, report content is retrieved directly from or calculated with fields from the following Vision database tables:
LedgerAP (Expense Detail Table — Accounts Payable)
LedgerAR (Expense Detail Table — Accounts Receivable)
LedgerEX (Expense Detail Table)
LedgerMisc (Expense Detail Table — Miscellaneous Expense)
CFGPostControl (Configuration Table — Posting Control)
Organization
The General Ledger entity provides you with the following fields to add to custom reports.
Custom Reports and Microsoft SQL Server® Reporting Services 89
Contents of the Vision Report Model
General Ledger Field
#General Ledger Data
Sources
Account
Account Code
Account Description
Auto Entry
Bank Code
Description 1 and
Description 2
Description
When you add this field to a report, it counts the items that were used to compile the information in a row on the report.
The number of the General Ledger account.
The type of account to which detail is posted. The values are:
01 — Assets
02 — Liabilities
03 — Net Worth
04 — Revenue
05 — Reimbursable
06 — Direct
07 — Indirect
08 — Other Charges
Descriptive text that indicates the type of account to which detail is posted. The options are:
Assets
Liabilities
Net Worth
Revenue
Reimbursable
Direct
Indirect
Other Charges
A Y or N (Yes or No) value in the field indicates whether or not the transaction was an automatic posting made by Vision.
The code for the bank that is involved in the transaction.
Displays Description 1 or Description 2 for each transaction detail line. If the descriptions do not fit on a single line, the text wraps to the next line. Vision stores two types of descriptions for each transaction:
Description 1 — A general description of the transaction (for example, for an accounts payable voucher, the name of the vendor).
Description 2 — A more specific description of the transaction (for example, the description entered during
Transaction Entry for a single line item on a voucher).
Custom Reports and Microsoft SQL Server® Reporting Services 90
Contents of the Vision Report Model
General Ledger Field
PKey
Post Comment
Post Date
Organization
Reference Number
Total Amount
Total Cbamount
Total CB Credit Amount
Total CB Debit Amount
Total Credit Amount
Total Debit Amount
Total Period
Total Posting Sequence
Transaction Date
Transaction SubType
Description
Vision internal primary key.
Any comments entered during transaction posting.
The date on which the transaction posted.
The organization associated with the transaction. The organization is expressed in code form (for example, BO:AR for
Boston: Architecture).
The reference number that is assigned to the transaction during
Transaction Entry.
If this is an implicit posting or an automatic posting made by Vision, the word Auto displays in this field.
If the transaction is historical, the word History displays.
If the transaction is related to revenue generation,
REVGEN displays in this field.
The total monetary amount of the transaction.
The cash basis total monetary amount of the transaction.
The cash basis total credit monetary amount of the transaction.
The cash basis total debit monetary amount of the transaction.
The total credit amount that is posted to this account during the specified period.
The total debit amount posted to this account during the specified period.
The fiscal year and period in which the transaction was posted
(for example, 200907 for the seventh accounting period in the year 2009).
The transaction's posting sequence number that is assigned by
Vision during the posting process.
For all transactions except automatic postings, the date that is entered for the transaction during Transaction Entry.
For automatic postings, the transaction date is the periodending date for the file of transactions that generated the automatic posting.
A one-letter code that represents the transaction's sub-type.
See Transaction Types in the Accounting Concepts help for a full listing.
Custom Reports and Microsoft SQL Server® Reporting Services 91
Contents of the Vision Report Model
General Ledger Field
Transaction Type
TransTypePostControl
User Name wbs1 wbs2 wbs3
Description
A two-letter abbreviation for the type of transaction (such as TS for timesheet or XD for converted account data). See
Transaction Types in the Vision help system for a full listing.
The transaction type of the record in the posting log for a particular posting sequence and period.
The Vision username of the employee who initiated the transaction.
The project number that is associated with the transaction. If a transaction is not project-related, no project number displays.
No project number displays for Balance Sheet account transactions, except for those that affect accounts receivable.
The phase number that is associated with the transaction.
The task number that is associated with the transaction.
Custom Reports and Microsoft SQL Server® Reporting Services 92
Contents of the Vision Report Model
Lead Entity
Use the Lead entity to create Lead reports. When you use this entity, report content is retrieved from or calculated with fields from the Leads Info Center.
The Lead entity provides you with the following fields to add to custom reports.
Lead Field Description
#Lead Data Sources
Address1–Address 3
Business Fax
Business Phone
City
Company
Country
Create Date
Create User
When you add this field to a report, it counts the items that were used to compile the information in a row on the report.
The first, second, and third lines of the lead's address.
The lead's business fax number.
The lead's business phone number.
The lead's city.
The company for which the lead works.
The lead's country.
The date on which the employee record was created.
The user ID of the person who created the lead record.
Description
First Name
The lead's description.
The lead's email address.
The lead's first name.
Full Name
Home Phone
The lead's full name that includes first, middle, and last names.
The lead's home phone number.
Lead Industry Code
The code for the lead's industry.
Lead Industry Description
The description of the lead's industry.
Last Name
The lead's last name.
Lead Owner
The name of the employee at your firm who is associated with this lead.
Lead Rating
The lead's rating
Lead Record Status Code
The code of the lead's record status.
Lead Record Status
The description of the lead's record's status — Active or
Custom Reports and Microsoft SQL Server® Reporting Services 93
Contents of the Vision Report Model
Mod Date
Mod User
Pager
Prefix
Rating
Source
State
Suffix
Lead Field
Description
Lead Status Description
Description
Inactive.
The description for the lead's status (for example, New,
Qualified, or Disqualified).
Lead Status Reason Code
The code for the lead's status reason.
Lead Status Reason
Description
The reason for the lead's status.
LeadID
Middle Name
Mobile Phone
Internal reference number for the lead record.
The lead's middle name.
The lead's mobile phone number.
The date on which the lead record was last modified.
The user ID of the last person who modified the lead record.
The lead's pager number.
The prefix, such as Mr. or Ms., used with the lead's name.
The lead's rating.
The lead's source.
Title
Website
Zip
The lead's state.
The suffix, such as Jr. or III. used with the lead's name.
The lead's title, such as Director, Project Manager, and so on.
The lead's Web site address.
The lead's ZIP code.
Marketing Campaign Entity
Use the Marketing Campaign entity to create marketing reports. When you use this entity, report content is retrieved from or calculated with fields from the Marketing Campaigns Info Center.
The Marketing Campaign entity provides you with the following fields to add to custom reports.
Marketing Campaign Field Description
#Marketing Campaign
Data Sources
Mkt Audience Code
When you add this field to a report, it counts the items that were used to compile the information in a row on the report.
The code for the marketing campaign's audience.
Custom Reports and Microsoft SQL Server® Reporting Services 94
Contents of the Vision Report Model
Marketing Campaign Field Description
Campaign ID
Mkt Campaign Mgr
Number
Create Date
Internal reference number for the marketing campaign record.
The employee number of the marketing campaign's campaign manager.
The date and time when the marketing record was created.
The user who created the marketing record.
Create User
Mktg Current Action Code
The code for the current action (Develop Invitation, Follow Up
Calls, and so on) in the marketing campaign.
Description
End Date
Mktg First Action Code
The description of the marketing campaign.
The marketing campaign's end date.
The code for the first action (Campaign Kickoff, Initial Campaign
Meeting, and so on) in the marketing campaign.
Launch Date
Manager 3 Number
The marketing campaign's launch date.
The employee number ID of an additional manager who works on a campaign.
Mkt Audience Description
The description of the marketing campaign's audience.
Mkt Campaign Mgr Name
The employee name of the campaign’s manager.
Mkt Current Action
Description
Mkt First Action
Description
The description for the current action (Develop Invitation, Follow
Up Calls, and so on) in the marketing campaign.
The description of the first action (Campaign Kickoff, Initial
Campaign Meeting, and so on) in the marketing campaign.
Mkt Mgr Name
The name of the marketing manager who works on a campaign.
Mkt Mgr 3 Name
Mkt Name
The name of an additional manager who works on a campaign.
The marketing campaign's name.
The next action in the marketing campaign.
Mkt Next Action
Description
Mkt Number
The marketing campaign's number.
Mkt Objective Description
The marketing campaign's objective (goal), such as lead generation, sell products, or raise awareness.
Mkt Org Name
The name of the organization in your firm to which this marketing campaign belongs. This field displays only if your firm uses Vision Organizations.
Custom Reports and Microsoft SQL Server® Reporting Services 95
Contents of the Vision Report Model
Marketing Campaign Field Description
Mkt Status Description
Mkt Type Description
The current status of the campaign, such as Active, Completed, or Planning.
The type of campaign you plan to implement, such as Direct
Mail, Newsletter, or Seminar.
Mkt Mgr Number
Mod Date
The employee number of the campaign's marketing manager.
The date and time when the marketing record was last modified.
The user who last modified the marketing record.
Mod User
Mktg Next Action Code
Mktg Objective Code
Mktg Org Code
Project Name
Record Status
Mktg Status Code
Total Actual Cost
The next action in the campaign, such as Develop Invitation or
Follow Up Calls.
The code for the marketing campaign's objective (goal), such as lead generation, sell products, or raise awareness.
The code for the marketing campaign's organization.
The marketing campaign's promotional project.
The marketing campaign record's status.
The marketing campaign's current status — Active, Completed,
Planning, and so on.
The marketing campaign's actual cost.
Total Budget
The marketing campaign's budget amount.
Total Potential Responses
The total number of firms targeted by the campaign (the potential responses) that are entered in the Universe field on the General tab in the Marketing Campaigns Info Center.
Total Revenue
Project Number
The marketing campaign's revenue.
The marketing campaign's promotional project.
Marketing Type Code
The code for the marketing type description.
Custom Reports and Microsoft SQL Server® Reporting Services 96
Contents of the Vision Report Model
Opportunity Entity
Use the Opportunity entity to create opportunity reports. When you use this entity, report content is retrieved from or calculated with fields from the Opportunity Info Center.
The Opportunity entity provides you with the following fields to add to custom reports.
Opportunity Field Description
#Opportunity Data Sources When you add this field to a report, it counts the items that were used to compile the information in a row on the report.
Address1–Address3
City
Client ID
The first, second, and third lines of the opportunity address.
The opportunity's city.
The client number of the primary client for the opportunity.
Close Date
Contact ID
Country
Create Date
Create User
The date on which the opportunity record was closed.
The contact number of the primary contact for the opportunity
The opportunity's county.
The date and time when the opportunity record was created.
The user who created the opportunity record.
Description
Est Completion Date
Est Start Date
Mod Date
The opportunity's description.
The opportunity's estimated completion date.
The opportunity's estimated start date.
The date and time when the opportunity record was last modified.
Mod User
Open Date
Opportunity ID
Opportunity Name
Opportunity Number
Organization Name
Organization1
Primary Client
The user who last modified the opportunity record.
The date when the opportunity record was opened.
The internal reference number for the opportunity record.
The opportunity name.
The opportunity number.
The associated organization's name.
The organization associated with the opportunity.
The primary client's client number.
Custom Reports and Microsoft SQL Server® Reporting Services 97
Contents of the Vision Report Model
Opportunity Field Description
Primary Contact
Principal Name
Principal Number
Project Manager Name
Project Manager Number
Regular Project Name
Type
Zip
The primary contact's contact number.
The employee name of the opportunity's principal.
The employee number of the opportunity's principal.
The employee name of the opportunity's project manager.
The employee number of the opportunity's project manager.
The project name of the regular project created for the opportunity.
Regular Project Number
The project number of the regular project created for the opportunity.
Promotional Project Name
The project name of the promotional project created for the opportunity.
Promotional Project
Number
Source
Stage
State
Status
Supervisor Number
Supervisor Name
Total Days Open
Total Est Revenue
Total Probability
Total Weighted Revenue
The project number of the promotional project created for the opportunity.
The source of the opportunity.
The opportunity's stage of development.
The opportunity's state.
The opportunity's status (Active or Inactive).
The employee number of the opportunity's supervisor.
The employee name of the opportunity's supervisor.
The total number of days the opportunity has remained open.
The estimated revenue the opportunity is expected to generate.
The probability that the opportunity will become a project.
The product of Revenue and Weighted Revenue.
The opportunity type.
The opportunity's ZIP code.
Custom Reports and Microsoft SQL Server® Reporting Services 98
Contents of the Vision Report Model
Payroll Entity
Use the Payroll entity to create custom Vision Payroll reports. When you use this entity, report content is retrieved directly from or calculated with fields from the following Vision database tables:
EM (Employee)
LD (Labor Detail)
CFGEmployeeType, CFGEmployeeStatus, and CFGEmployeeGroup (Employee
Configuration tables)
VE (Vendor)
Organization
BTLaborCats (Billing Configuration Table — Labor Categories and Descriptions)
PR (Project)
The Payroll entity provides you with the following fields to add to custom reports.
Payroll Field Description
#Payroll Data Sources
Active Company
Address Line 1–Address
Line 3
First, second, and third lines of the employee's address from the
Employee Info Center.
Allow Employee to change in Timesheet
Indicates whether or not the employee can modify the default labor code on a timesheet. If Y, the employee can charge time to a labor code other than the default.
Approved for use in accounting applications
Indicates whether or not the record is approved for use in transaction processing. Although you may not need to include this field on a report, it may be useful when building queries.
Available for CRM users
When you add this field to a report, it counts the items that were used to compile the information in a row on the report.
If you use the Multicompany feature in Vision, this is the company that you have open when you run a report.
Available for Accounting users
BankCode
Billing Status
Indicates whether or not the record is available to Customer
Relationship Management users. Although you may not need to include this field on a report, it may be useful when building queries.
Indicates whether or not the record is available to accounting users. Although you may not need to include this field on a report, it may be useful when building queries.
The bank code used in Payroll Processing.
Indicates the billing status for the labor transaction:
B — Billable. Released and available for billing to the client.
D — To be deleted. The transaction is marked for
Custom Reports and Microsoft SQL Server® Reporting Services 99
Contents of the Vision Report Model
Payroll Field
Check hours entered against expected
CheckDate
CheckNo
City
Description
deletion.
F — Final billed. Already billed to the client.
H — Held. Transaction held to temporarily prevent billing to the client.
M — Modified. Changed in some way from its original form.
N — Not billable.
O — Deleted. A transaction marked for deletion was included in a billing run (and has been deleted).
R — Partial Hold/Released. Part of the transaction has already been held or released.
T — Transferred. Moved from one project, phase, task, or labor code to another.
W — To be written off. Transaction has been written off, but the invoice has not been posted.
X — Written off. Transaction has been written off, and the invoice has been posted.
A Y or N (Yes or No) value that indicates whether or not Vision compares hours entered on a timesheet with an employee's expected hours per day setting.
The check date entered in Payroll Processing.
The check number issued in Payroll Processing.
The city in which the employee resides that is entered in the
Employee Info Center.
Comment
Country
Timesheet comments.
The country in which the employee resides that is entered in the
Employee Info Center.
Default Labor Code Level 1 Level 1 default labor code that displays on employees' timesheets when they charge time to a project.
Default Labor Code Level 2 Level 2 default labor code that displays on employees' timesheets when they charge time to a project.
Default Labor Code Level 3 Level 3 default labor code that display on the employees' timesheets when they charge time to a project.
Default Labor Code Level 4 Level 4 default labor code that displays on the employees' timesheets when they charge time to a project.
Default Labor Code Level 5 Level 5 default labor code that displays on the employees' timesheets when they charge time to a project.
Custom Reports and Microsoft SQL Server® Reporting Services 100
Contents of the Vision Report Model
Payroll Field
Direct Deposit
Employee First Name
Employee Last Name
Employee Middle Name
Employee Name
Employee Number
Employee Organization
Code
Employee Organization
Code
Employee Salutation
Employee Suffix
Employee Type
Expense Report
Administration Approval
Expense Report
Administration Editing
Expense Report
Administration Level
Description
A Y or N (Yes or No) value that indicates whether or not a payroll payment was paid by direct deposit.
The employee's email address.
The employee's first name that is entered in the Employee Info
Center.
The employee's last name that is entered in the Employee Info
Center.
The employee's middle name that is entered in the Employee
Info Center.
The employee's last name, first name, and middle initial (if it is included on the employee's record).
The individual's unique employee identification number that is entered in the Employee Info Center.
The name of the organization that is associated with the employee (entered in the Employee Info Center). If your firm does not use Vision's Organization application, this field does not display.
The organization number (all levels) of the employee's organization. If your firm does not use Vision's Organization application, this field does not display.
The prefix (Mrs., Ms., Mr. and so on) to use with this employee's name as entered in the Employee Info Center.
The suffix (Jr., Sr., and so on) to use with this employee's name, as entered in the Employee Info Center.
The employee's employee type, such as Principal, Manager, or
Employee as entered in the Employee Info Center.
A Y or N (Yes or No) value that indicates whether or not an employee can approve (before it is posted) any expense report to which he or she has access. This setting is on the Expense tab in the Employee Info Center.
A Y or N (Yes or No) value that indicates whether or not an employee can edit any expense report to which he or she has access. This setting is on the Expense tab in the Employee Info
Center.
Indicates the expense report administrative level for the employee — Staff, Group, or System. This setting is on the
Expense tab in the Employee Info Center.
Custom Reports and Microsoft SQL Server® Reporting Services 101
Contents of the Vision Report Model
Payroll Field
Expense Report Group
Fax
Hire Date
Home Phone
Job Cost Type
Labor Billing Category
Memo
Mobile Phone
Other Pay 1 Override–
Other Pay 5 Override
Ovt Hrs Override
Payroll Run Type
Pay Type
Raise Date
Regular Hrs Override
Social Security Number
Ovt 2 Hours Override
Description
The expense report group for which this employee is able to access expense reports.
The employee's fax number that is entered in the Employee Info
Center.
The date on which the employee was hired (entered in the
Employee Info Center).
The employee's phone number that is entered in the Employee
Info Center.
The employee's job cost type (H-Hourly or S-Salaried) that is entered on the Accounting tab in the Employee Info Center.
The labor category (description) that is entered for an employee in the Employee Info Center.
The text entered in the Memo field on the Personal tab of the
Employee Info Center.
The employee's cellular phone number that is entered in the
Employee Info Center.
Any additional pay amounts added to the employee’s net pay amount for a payroll processing run that are entered in the
Other Pay , Bonus, Other Pay 3, Other Pay 4, and Other Pay
5 fields (General tab of the Payroll Processing form).
The overtime hours entered on the Employee Review tab on the
Payroll Processing form.
The payroll processing run type (Regular, Adjustment, or Bonus) that is entered on the General tab of the Payroll Processing form.
The pay type (Hourly or Salary) that is entered for an employee on the Payroll tab in the Employee Info Center.
The date of the employee's last raise that is entered on the
Personal tab in the Employee Info Center.
The regular hours that are entered on the Employee Review tab on the Payroll Processing form that override the regular hours that were entered on an employee's timesheet.
The employee's Social Security number that is entered in the
Employee Info Center.
The overtime-2 hours that are entered on the Employee Review tab on the Payroll Processing form. These override the regular
Custom Reports and Microsoft SQL Server® Reporting Services 102
Contents of the Vision Report Model
Payroll Field
State
Description
hours that were entered on an employee's timesheet.
The state where the employee resides as entered in the
Employee Info Center.
Status
Supervisor Name
Supervisor Number
Termination Date
Timesheet Administration
Approval
Timesheet Administration
Editing
Timesheet Administration
Level
Timesheet Group
Title
Total Other Pay 1–Total
Other Pay 5
An employee's status (Active, Inactive, or Terminated) that is entered on the General tab in the Employee Info Center.
The first and last name of the employee's supervisor. The supervisor's name is entered on the General tab of the
Employee Info Center.
The employee number of the employee's supervisor that is entered on the General tab of the Employee Info Center.
The date on which the employee last worked for your firm as entered on the Personal tab in the Employee Info Center.
A Y or N (Yes or No) value that indicates whether or not the employees can approve (before it is posted) any timesheet to which they have access. This option is on the Time tab in the
Employee Info Center.
A Y or N (Yes or No) value that indicates whether or not an employee can edit any timesheet to which he or she has access. This option is on the Time tab in the Employee Info
Center. This column is blank if the timesheet admin level is
Group.
The timesheet administrative level (Staff, Group, or System) for an employee that is entered on the Time tab in the Employee
Info Center.
The timesheet group for which this employee is able to access timesheets. This is entered on the Time tab in the Employee
Info Center.
The employee's job title entered in the Employee Info Center.
The total of each of the five Other pay fields on the Employee
Review tab of the Payroll Processing form.
Total Gross Amount
Total Hours/Day
Total Job Cost Ovt Pct
Total Job Cost Ovt 2 Pct
The gross amount of a pay check.
The number of hours per day that the employee is generally expected to work.
The percentage of the employee's hourly wage that is costed to projects when the employee works standard overtime hours.
The percentage of the employee's hourly wage that is costed to projects when the employee works secondary overtime hours.
Custom Reports and Microsoft SQL Server® Reporting Services 103
Contents of the Vision Report Model
Payroll Field Description
Total Job Cost Rate
Total Net Amount
The employee's job cost rate, which is the rate at which Vision applies the employee’s hours as costs to a project.
The net pay amount for the employee in the payroll processing run.
Total Ovt Hrs
Total Ovt Pay
Total Pay Overtime Pct
Total Pay Rate
The overtime hours that are posted by the employee for this payroll processing run.
The employee's overtime pay for the payroll processing run.
The percentage that is applied to the employee's payroll rate to calculate standard overtime wages.
The employee's actual pay amount per payroll period (payroll periods can be weekly, biweekly, semimonthly, or monthly).
Total Pay Special Overtime
Pct
The percentage to apply to the employee's payroll rate to calculate secondary overtime wages.
Total Period
Total Post Seq
The fiscal period during which the posting was made.
Total Provisional Bill Ovt
Pct
The transaction's posting sequence number that is assigned by
Vision during the posting process.
The percentage that Vision applies to overtime hours on unposted timesheet entries to calculate labor charges at billing rates.
Total Provisional Bill Ovt-2
Pct
The percentage that Vision applies to secondary overtime hours on unposted timesheet entries to calculate labor charges at billing rates.
Total Provisional Bill Rate
The billing rate that Vision applies to unposted timesheet entries for this employee to calculate labor charges.
Total Provisional Cost Ovt
Pct
The percentage that Vision applies to overtime hours on unposted timesheet entries to calculate labor charges at cost rates.
Total Provisional Cost Ovt-
2 Pct
The percentage that Vision applies to secondary overtime hours on unposted timesheet entries to calculate labor charges at cost rates.
Total Provisional Cost
Rate
Total Reg Hrs
The cost rate that Vision applies to unposted timesheet entries for this employee to calculate labor charges.
Total Reg Pay
The regular hours that are posted by the employee.
The employee's regular pay for the payroll processing run.
Custom Reports and Microsoft SQL Server® Reporting Services 104
Contents of the Vision Report Model
Payroll Field Description
Total Special Ovt Hrs
Total Special Ovt Pay
Total Target Ratio
Total Hours
The special overtime hours that are posted by the employee for this payroll processing run.
The employee's special overtime pay for the payroll processing run.
The percentage of an employee's time that is expected to be charged to regular (revenue-producing) projects as established in the Employee Info Center.
The total hours that are entered for the employee for this payroll processing run.
Total W2 Quarter
Total W2 Year
Select Min W2 Quarter, an additional item listed for Total W2
Quarter, to add the W2 quarter of the payroll processing run to a report.
Select Min W2 Year, an additional item listed for Total W2
Year, to add the W2 year of the payroll processing run to a report.
Total Withholding Code
Select Min Withholding Code, an additional item listed for
Total Withholding Code, to add the withholding code of the payroll processing run to a report.
Total Years W Other Firms
The number of years that the employee worked for other firms.
Use total hours as standard on Time Analysis
A Y or N (Yes or No) value that indicates whether or not standard hours or amounts for employees are calculated and displayed on the Time Analysis report:
Vendor Indicator
A Y or N (Yes or No) value that indicates whether or not the employee is a consultant.
Vendor Name
Vendor Number
Withholding Code
The name of the vendor if the vendor indicator is Y.
The vendor number if the vendor indicator is Y.
The description of the withholding code that is entered for an item in a payroll processing run.
Withholding Code Method
The withholding code type that is entered for the withholding code in Configuration » Payroll » Withholding Codes.
Work Phone
The employee's work phone number as entered in the
Employee Info Center.
Work Phone Ext.
Zip
The employee's work phone extension.
The employee's ZIP code from the Employee Info Center.
Custom Reports and Microsoft SQL Server® Reporting Services 105
Contents of the Vision Report Model
Project Expenses Entity
Use the Project Expenses entity to create project expense reports. When you use this entity, report content is retrieved from or calculated with fields from the following Vision database tables:
PR (Project)
LedgerEX (Expense Detail)
LedgerAP (Expense Detail Table — Accounts Payable)
LedgerAR (Expense Detail Table — Accounts Receivable)
LedgerMisc (Expense Detail Table — Miscellaneous Expense)
CFGChargeType (Configuration Table — Project Charge Types)
CL (Client)
CFGProjectStatus (Configuration Table — Project Status)
CFGRGMethods (Configuration Table — Revenue Generation Methods)
Organization (Configuration Table — Organization)
Contacts
CFGProjectType (Configuration Table — Project Types Code)
CFGPRResponsibility (Configuration Table — Primary Responsibility Codes)
Opportunity
EM (Employee)
The Project Expenses entity provides you with the following fields to add to custom reports.
Project Expenses Field
#Project Expenses Data
Source
Actual Completion Date
Address1–Address3
Approved for use in accounting applications
Available for Accounting
Users
Available for CRM Users
Bid Date
Description
When you add this field to a report, it counts the items that were used to compile the information in a row on the report.
For a completed project, the date on which the project finished.
The client's street address from the three lines of address text entered on the client's record.
A Y or N (Yes or No) value that indicates whether or not the record is approved for use in transaction processing. Although you may not need to include this field on a report, it may be useful when building queries.
A Y or N (Yes or No) value that indicates whether or not the record is available to accounting users. Although you may not need to include this field on a report, it may be useful when building queries.
A Y or N (Yes or No) value that indicates whether or not the record is available to Customer Relationship Management users. Although you may not need to include this field on a report, it may be useful when building queries
The date on which your firm first bid on the project.
Custom Reports and Microsoft SQL Server® Reporting Services 106
Contents of the Vision Report Model
Project Expenses Field
Bill By Default
Bill Client Name
Billable Message
Billing Contact Name
Budgeted Labor Code
Validation
BudgetedLevels
Charge Type
Description
Indicates whether or not to bill the client for certain expense charges posted to the project. The values are:
Yes — Always bill expense charges to the client, regardless of whether or not the Bill by default option is selected for the associated category in Expense
Category Configuration.
No — Never bill expense charges to the client, regardless of whether or not the Bill by default option is selected for the associated category in Expense
Category Configuration.
Category — Only bill charges to the client if the Bill by
default option is selected for the associated category in
Expense Category Configuration.
The client to be billed for the project.
Indicates whether or not to display an error message in the
Expense Report application when a user charges certain expenses to this project. The values are:
No Message — Vision does not display any message when the category bill by default method and the project bill by default method are different.
Warning — Vision displays a warning message when the category bill by default method and the project bill by default method are different. You must explicitly select to continue with the transaction if you want to process the expense charge to the project using the selected category.
Error — Vision displays an error message when the category bill by default method and the project bill by default method are different. You cannot process the expense charge to the project using the selected category.
The billing contact at the client firm.
The budgeted labor code check for timesheets. Options are:
N — None
W — Warning
E — Error
The labor code levels that employees can use to charge time to the project. The budgeted labor code level options that are available vary based on the number of labor code levels set up in Utilities » Key Formats » Labor Codes.
The project's charge type as entered on the Accounting tab in
Custom Reports and Microsoft SQL Server® Reporting Services 107
Contents of the Vision Report Model
Project Expenses Field
City
CLAddress
Client Alias
Client Billing Address
Description
the Project Info Center:
R — Regular. Regular projects are revenue-producing.
The costs charged to regular projects include direct labor, direct expense, and reimbursable expense. Detail is retained for the life of the project.
H — Overhead. Overhead projects are not revenueproducing. The costs charged to overhead projects include indirect labor and indirect expense. The total cost of these projects is distributed to regular projects during overhead allocation. Typical overhead projects include General Overhead, Vacation, or Sick Leave.
Overhead projects zero out when you initialize for a new fiscal year.
P — Promotional. Use promotional projects to track the cost of trying to acquire a job. If the job is obtained, you can create a new regular project and transfer the detail to it to be billed or tracked. A promotional project is the same as an overhead project, with this exception—
Vision does not zero out job-to-date costs at the start of each fiscal year for promotional projects.
The city where the firm is located.
The client address code, or description, associated with the project. For clients who use more than one address, this field indicates which address is associated with the project. This field displays a description of the address on the report, rather than the actual address. For example:
<Default> — The default address from the client record
Corporate HQ — The address for the client's headquarters
London — The address for the client's office in London,
UK
To see a client's full address on the report, use the Client
Address (concatenated) column.
The alternate name used in proposals to represent a client who wants to keep the firm's name confidential.
For clients who use more than one address, this field indicates the one to which you are sending bills for this project. This field displays a description of the address on the report, rather than the actual address. For example:
<Default> — The default billing address from the client record.
Corporate HQ — The address for the client's headquarters.
Custom Reports and Microsoft SQL Server® Reporting Services 108
Contents of the Vision Report Model
Project Expenses Field Description
Client Confidential
A Y or N (Yes or No) value that indicates whether or not the client firm's name is confidential and is to be excluded from all proposals. When you include the project in a proposal, the alias
(Client Alias) is substituted for the client name.
Completion Date Comment
The comment that is related to the completion date.
Contact Name
ContactID
Contract Date
Your contact at the client firm.
The contact record number for the primary contact.
The date on which the contract was awarded to your firm.
Country
County
The country where the firm is located.
The county where the firm is located.
The project location's email address.
End Date
Expense Account
The completion date for the project, phase, or task.
Estimated Completion Date The date on which the project is/was scheduled to be completed.
The account number of the account that receives the debit for the expense item.
Expense AcctName
The account name of the account that receives the debit for the expense item.
Expense BillStatus
The status of the transaction. Possible values are:
B — Billable. Released and available for billing to the client.
D — To be deleted. The transaction is marked for deletion.
F — Final billed. Already billed to the client.
H — Held. Transaction held to temporarily prevent billing to the client.
M — Modified. Changed in some way from its original form.
N — Not billable.
O — Deleted. A transaction marked for deletion was included in a billing run (and has been deleted).
R — Partial Hold/Released. Part of the transaction has already been held or released.
T — Transferred. Moved from one project, phase, task, or labor code to another.
Custom Reports and Microsoft SQL Server® Reporting Services 109
Contents of the Vision Report Model
Project Expenses Field
Expense Desc1
Expense Desc2
Expense Invoice
Expense LDKey
Expense Org
Expense RefNo
Expense SubType
Expense TransDate
Expense Transfer
Expense TransType
Expense VendName
Expense Vendor
Expense VendOrg
Expense VendUnit
Description
W — To be written off. Transaction has been written off, but the invoice has not been posted.
X — Written off. Transaction has been written off, and the invoice has been posted.
The description entered for a transaction during Transaction
Entry. If the description does not fit on a single line, the text wraps to the next line.
The description entered in the Detail field of the Expense
Report form if the transaction was entered through the Expense
Report application. If the description does fit on a single line, the text wraps to the next line.
The billed invoice number of the transaction.
Internal primary key from the PKey field of the LedgerAP table.
The organization code that is associated with the project at the time the transaction was posted.
The reference number, voucher number, or journal entry number for this transaction.
If the expense is a non-reimbursable or direct expense, this field displays "Expense."
The date on which the transaction was posted or, if the detail is from History Loading, it is the accounting period.
An asterisk in this field indicates that the transaction is an adjustment.
A two-letter abbreviation for the type of transaction (such as EX for employee expense report). See Transaction Types in the
Accounting Concepts help for a full transaction type list.
The name of the vendor who is associated with the transaction.
The vendor number.
The name of the organization (profit center) within your company for which this vendor provides goods or services.
The vendor number if the transaction type is either of the following:
AP — Accounts Payable voucher
CV — Accounts Payable disbursement
The unit number if the transaction involves units.
Custom Reports and Microsoft SQL Server® Reporting Services 110
Contents of the Vision Report Model
Project Expenses Field Description
Expense Voucher
Expense xferWBS1
Expense xferWBS2
Expense xferWBS3
The voucher number that is assigned to this voucher during posting.
For a labor adjustment, the project from which the labor adjustment transaction was transferred.
For a labor adjustment, the phase from which the labor adjustment transaction was transferred.
For a labor adjustment, the task from which the labor adjustment transaction was transferred.
ExpenseSubType
ExpenseType
Fax
Federal Project Indicator
Firm Cost Comment
Displays any comments that accompany the Firm Cost field.
Has SubLevels Turned On
A Y or N (Yes or No) value that indicates whether or not the project, phase, or task is associated with a sub-level billing term.
See Phase or Task Billing Terms in the Vision Help system for information about sub-level billing terms.
Locale
If your firm uses Vision Payroll, this field lists the state or locale that is used to determine payroll tax.
Memo
Transaction subtype for the expense detail, such as Expense or
Consultant.
The expense type, which can be Direct, Indirect, or
Reimbursable.
The fax number at the project location.
A Y or N (Yes or No) value that indicates whether the current project is a federal project.
Opportunity Description
Opportunity ID
Organization Code
Organization Name
Phase
Displays notes for the project record as entered in the Memo field on the General tab of the Project Info Center.
If the project record was created from an existing opportunity record, the name of that opportunity record displays in this field.
If the project record was created from an existing opportunity record, the number of that opportunity record displays in this field.
The unique identifier of the organization with which the project is associated.
The name of the organization with which the project is associated. Organization refers to the office within your firm that was responsible for this project.
The unique identifier for the phase.
Custom Reports and Microsoft SQL Server® Reporting Services 111
Contents of the Vision Report Model
Project Expenses Field Description
Phase Name
Phone
Primary Client
Principal Name
The name of the phase.
The project location's phone number.
The firm for which you are directly performing work on the project.
The name of the principal at the firm who is associated with this project.
Principal Number
Project
Project Long Name
Project Manager Name
The unique employee number of the principal.
The project identifier.
The project's long name as entered in the Project Info Center.
The name of the project manager at your firm who is associated with this project.
Project Manager Number
Project Name
Project Type
Proposal WBS1
The unique employee number of the project manager.
The short name of the project that is entered on the General tab in the Project Info Center.
The project type that is entered on the General tab in the Project
Info Center. Examples are Educational, Commercial, Financial,
Medical, Federal, and so on.
The promotional project that is entered for a project on the
General tab of the Project Info Center.
Referable
Responsibility
A Y or N (Yes or No) value that indicates whether or not the project can be used as a reference when you talk with potential clients.
The level of responsibility that your firm has for the project (such as Prime, Joint Venture, Consultant, and so on) that is entered on the General tab in the Project Info Center.
You define the responsibility codes available to your firm in the Project Responsibility Code Table in Code
Table Configuration.
You assign the responsibility to the project on the
General tab of the Project Info Center.
Responsibility Description
The description for the responsibility code.
Revenue Type Code
The code for the revenue type of the project that is entered on the Budget and Revenue tab in the Project Info Center. This is used to calculate revenue for a task, phase, or project.
The standard Vision revenue methods are:
Custom Reports and Microsoft SQL Server® Reporting Services 112
Contents of the Vision Report Model
Project Expenses Field Description
B — Job-to-date Billings
M — (Job-to-date Direct Labor x Multiplier) + Job-todate Reimbursable Expenses @ Cost Rates
N — No revenue generation
P — Percent Complete + Job-to-date Reimbursable
Expenses @ Cost Rates
R — Job-to-date Receipts
W — Job-to-date Billings + Work-in-Progress (WIP) @
Billing Rates
Revenue Type Description
The description of the revenue source. For example, you might see descriptions such as:
JTD Billings
JTD Billings + WIP @ Billing
(Pct Comp*Fee) + JTD Reimb Exp
Start Date
The start date of the project, phase, or task.
State
Status
Supervisor Name
Supervisor Number
Task
The state where the firm is located.
The status of the project (Active, Inactive, or Dormant) that is entered on the General tab in the Project Info Center.
The name of the supervisor at your firm who is associated with this project. This is entered on the General tab in the Project
Info Center.
The employee number of the project's supervisor.
The identifier for the task.
Task Name
Total Budgeted OH Rate
Total Compensation
Total Consultant Fee
The name of the task.
The budgeted overhead rate for the project, phase, or task
(used for regular, revenue-producing projects).
If you use the assignment method for overhead allocation, Vision uses the budgeted overhead rate for both budgeting and allocation purposes.
For all other overhead allocation methods, Vision uses the budgeted overhead rate to calculate the overhead amount only for the project budget.
The total contract value for this task, phase, or project.
Compensation is the total monetary amount your company expects to receive and should include all labor and expenses.
The project's consultant fee as entered in the Project Info
Custom Reports and Microsoft SQL Server® Reporting Services 113
Contents of the Vision Report Model
Project Expenses Field
Total Cost Rate Meth
Total Cost Rate Table No
Description
Center.
If you use Vision Payroll and you selected the Enable cost rate
tables check box in Accounting Configuration, this field displays the cost rate method for the project on the report.
The options are:
From Employee Cost Rate
From Labor Rate Table
From Category Rate Table
From Labor Code Table
None
If you use Vision Payroll and you selected the Enable cost rate
tables check box in Accounting Configuration, this field displays the cost rate table number on the report.
Total Expense Bill Amount
The monetary amount billed for the transaction.
Total Expense Cost
Amount
Total Expense Line
The monetary amount of the expense transaction that is calculated with cost rates.
Total Expense Percent
Complete
The voucher line number if the transaction is of one of the following types:
AP — Accounts Payable voucher
CV — Accounts Payable disbursement
The estimate of how much of the expense budget has been spent to date on the project, phase, or task.
The accounting period in which the transaction was posted.
Total Expense Period
Total Expense PostSeq
Total Expense Unit Billing
Rate
The transaction's posting sequence number that is assigned by
Vision during the posting process.
The amount to be charged to the client for each unit. If your firm is using date-based rates, Vision uses the billing rate in effect at the time the transaction was posted.
Total Expense Unit Cost
Rate
Total Expense Unit
Quantity
Total Firm Cost
Total Labor Percent
The cost amount per unit; the amount that should be costed to the project and general ledger expense account for each unit. If your firm uses date-based rates, Vision uses the cost rate in effect at the time the transaction was posted.
The number of units charged by the current transaction (for example, 5 pipes).
The portion of the project cost for which your firm is responsible.
The estimate of how far work has progressed on the project,
Custom Reports and Microsoft SQL Server® Reporting Services 114
Contents of the Vision Report Model
Project Expenses Field
Complete
Total Multiplier/Amount
Total Overall Percent
Complete
Total PayRateMeth
Total PayRateTableNo
Total Project Cost
Comment
Total Reimb Allowance
Total Total Project Cost
Total X Charge Method
Description
phase, or task.
The multiplier, percentage, or amount by which to increase or decrease revenue for this task, phase, or project. Revenue methods that contain a multiplier or an amount in the calculation use this field.
The weighted average percent complete that is calculated as
(All percent completes x Their budgets) divided by Total project budget.
If you use Vision Payroll and you selected the Enable payrate
tables for overriding payrate from Employee Info Center check box in Payroll Configuration, this field shows the pay rate method for the project:
From Employee Pay Rate
From Labor Rate Table
From Category Rate Table
From Labor Code Table
None
If you use Vision Payroll and you selected the Enable payrate
tables for overriding payrate from Employee Info Center option in Payroll Configuration, this field displays the pay rate table number on the report.
Any comments that accompany the Total Project Cost column.
For example, this column might contain a brief description about the cost of the project, such as "fee only," "Phase I," and so on.
The expected amount of reimbursable expense billings for this task, phase, or project.
The total cost of the project.
This field identifies the Labor Cross Charge rate or transfer price calculation method for this project, phase, or task that is entered in the Cross Charge Rate Method field on the Accounting tab of the Project Info Center. The display options are:
1 — (One) Indicates a selection of Billing Terms. This means Vision uses the project, phase, or task billing terms to calculate the rate. If none are specified, Vision uses the billing terms marked Use as Project Reporting
Default Terms Only in Billing, Billing Terms. If none are specified, Vision uses the billing terms on the Labor tab of Configuration » Billing » Default Terms.
0 — (Zero) Indicates a selection of Multiplier. This means Vision uses the multiplier entered on the
Accounting tab of the Project Info Center.
Custom Reports and Microsoft SQL Server® Reporting Services 115
Contents of the Vision Report Model
Project Expenses Field
Total X Charge Multiplier
Unit Table
XCharge
Zip
Description
The multiplier that is used when the cross charge method is
Project and the cross charge rate is Multiplier (on the
Accounting tab in the Project Info Center).
The unit table that is used as the default when billing unit charges for the project.
This field indicates which Labor Cross Charge Configuration settings currently apply to this project, phase, or task. The options are:
G — Global (the default setting). This indicates that
Vision uses the cross charge method entered on the
Cross Charge tab of Individual Organization setup.
N — None.
P — Project. This indicates that Vision uses the cross charge method specified for the project in the Cross
Charge Rate field on the Accounting tab of the Project
Info Center.
The project location's ZIP code.
Project Labor Entity
Use the Project Labor entity to create project labor reports. When you use this entity, report content is retrieved from or calculated with fields from the following Vision database tables:
PR (Project)
LD (Labor Detail)
CFGChargeType (Configuration Table — Project Charge Types)
CL (Client)
CFGProjectStatus (Configuration Table — Project Status)
CFGRGMethods (Configuration Table — Revenue Generation Methods)
Organization (Configuration Table — Organizations)
Contacts
CFGProjectType (Configuration Table — Project Charge Types)
CFGPRResponsibility (Configuration Table — Primary Responsibility)
Opportunity
EM (Employee)
The fields in the Project Labor entity are also the same fields in the Project Labor Posted Only, and Project Labor Unposted Only entities. The differences among these entities are whether or not the entities include posted, unposted, or both types of transactions (as identified in the entity name).
Custom Reports and Microsoft SQL Server® Reporting Services 116
Contents of the Vision Report Model
The Project Labor entity provides you with the following fields to add to custom reports.
Project Labor Field Description
#Project Labor Data
Sources
Actual Completion Date
Address1–Address3
Approved for use in accounting applications
Available for Accounting
Users
Available for CRM Users
Bid Date
Bill By Default
Bill Client Name
Billable Message
When you add this field to a report, it counts the items that were used to compile the information in a row on the report.
For any completed project, the date on which the project was finished.
The client's street address from the three lines of address text entered on the client's record.
A Y or N (Yes or No) value that indicates whether or not the record is approved for use in transaction processing. You may not need to include this field on a report, but it may be useful when you build queries.
A Y or N (Yes or No) value that indicates whether or not the record is available to accounting users. You may not need to include this field on a report, but it may be useful when you build queries.
A Y or N (Yes or No) value that indicates whether or not the record is available to CRM users. You may not need to include this field on a report, but it may be useful when you build queries.
The date on which your firm first bid on the project.
Indicates whether or not to bill the client for certain expense charges posted to the project. The possible values are:
Yes — Always bill expense charges to the client, regardless of whether the Bill by default option is selected for the associated category in Expense
Category Configuration.
No — Never bill expense charges to the client, regardless of whether the Bill by default option is selected for the associated category in Expense
Category Configuration.
Category — Only bill charges to the client if the Bill by
default option is selected for the associated category in
Expense Category Configuration.
The client to be billed for the project.
Indicates whether or not an error message displays in the
Expense Report application when a user charges certain expenses to this project:
No Message — Vision does not display any message when the category bill by default method and the project bill by default method are different.
Custom Reports and Microsoft SQL Server® Reporting Services 117
Contents of the Vision Report Model
Project Labor Field
Billing Contact Name
Budgeted Labor Code
Validation
BudgetedLevels
Charge Type
City
Description
Warning — Vision displays a warning message when the category bill by default method and the project bill by default method are different. You must explicitly choose to continue with the transaction if you want to process the expense charge to the project using the selected category.
Error — Vision displays an error message when the category bill by default method and project bill by default method are different. You cannot process the expense charge to the project with the selected category.
The billing contact at the client firm.
Budgeted labor code check for timesheets. The options are:
N — None
W — Warning
E — Error
The labor code levels that employees can use when they charge time to the project. The budgeted labor code level options that are available vary based on the number of labor code levels established in Utilities » Key Conversions » Labor Codes.
The type of project. The options are:
R — Regular. Regular projects are revenue-producing.
The costs charged to regular projects include direct labor, direct expense, and reimbursable expense. Detail is retained for the life of the project.
H — Overhead. Overhead projects are not revenueproducing. The costs charged to overhead projects include indirect labor and indirect expense. The total cost of these projects is distributed to regular projects during overhead allocation. Typical overhead projects can include General Overhead, Vacation, Holiday, Sick
Leave, or Civic Duty. Overhead projects zero out when you initialize for a new fiscal year.
P — Promotional. Use promotional projects when you want to track the cost of trying to acquire a job. If the job is obtained, you can create a new regular project and transfer the detail to it to be billed or tracked. A promotional project is the same as an overhead project, with this exception Vision does not zero out job-to-date costs at the start of each fiscal year for promotional projects.
The city where the firm is located.
Custom Reports and Microsoft SQL Server® Reporting Services 118
Contents of the Vision Report Model
Project Labor Field Description
CLAddress
Client Alias
Client Billing Address
Client Confidential
The client address code or description that is associated with the project. For clients with more than one address, this field indicates which address is associated with the project. This field displays a description of the address on the report, rather than the actual address. For example:
<Default> — The default address from the client record.
Corporate HQ — The address for the client's headquarters.
London — The address for the client's office in London,
UK.
If you want to see a client's full address on the report, use the
Client Address (concatenated) column.
The alternate name used in proposals to represent a client who wishes to keep the firm's name confidential.
For clients with more than one address, this field indicates the one to which you send bills for this project. This field displays a description of the address on the report, rather than the actual address. For example:
<Default> — The default billing address from the client record.
Corporate HQ — The address for the client's headquarters.
A Y or N (Yes or No) value that indicates whether or not the client firm's name is confidential and is to be excluded from all proposals. When you include the project in a proposal, the alias
(client alias) is substituted for the client name.
Completion Date Comment
User-entered comment that is related to the completion date.
Contact Name
Your contact at the client firm.
ContactID
The contact record number for the primary contact.
Contract Date
Country
County
The date on which the contract was awarded to your firm.
The country where the firm is located.
The county where the firm is located.
Description
End Date
Estimated Completion
The project's description.
The project location's email address.
The completion date for the project, phase, or task.
The date on which the project is or was scheduled to be
Custom Reports and Microsoft SQL Server® Reporting Services 119
Contents of the Vision Report Model
Project Labor Field
Date
Fax
Federal Project Indicator
Description
completed.
The fax number at the project location.
A Y or N (Yes or No) value that indicates whether or not the current project is a federal project.
Displays any comments that accompany the Firm Cost field.
Firm Cost Comment
Has SubLevels Turned On
A Y or N (Yes or No) value that indicates whether or not the project, phase, or task is associated with a sub-level billing term.
See Phase or Task Billing Terms in the Vision help system for information about sub-level billing terms.
Labor BillStatus
The status of the transaction. Possible values are:
B — Billable. Released and available for billing to the client.
D — To be deleted. The transaction is marked for deletion.
F — Final billed. Already billed to the client.
H — Held. Temporarily hold the transaction to prevent billing to the client.
M — Modified. Changed in some way from its original form.
N — Not billable.
O — Deleted. A transaction marked for deletion was included in a billing run (and has been deleted).
R — Partial Hold/Released. Part of the transaction has already been held or released.
T — Transferred. Moved from one project, phase, task, or labor code to another.
W — To be written off. Transaction has been written off, but the invoice has not been posted.
X — Written off. Transaction has been written off, and the invoice has been posted.
Labor Code
Labor Comment
Labor Employee
The labor code for the transaction.
Any timesheet comments specified appear in this field.
The individual's unique employee identification number.
Labor Employee Name
The employee's last name, first name, and middle initial from the employee record.
Labor Employee Org Code
The organization code associated with the project at the time
Custom Reports and Microsoft SQL Server® Reporting Services 120
Contents of the Vision Report Model
Project Labor Field
Labor Employee Type
Labor Period
Labor PKey
Labor PostSeq
Labor TransDate
Labor TransType
Labor XferLabor Code
Labor xferWBS1
Labor xferWBS2
Labor xferWBS3
LaborCode
Locale
Memo
Opportunity Description
Opportunity ID
Organization Code
Organization Name
Description
the transaction was posted.
The employee type, such as Principal, Manager, or Employee.
The accounting period in which the transaction was posted.
Internal Vision primary key. The PKey from the LD table.
The transaction's posting sequence number assigned by Vision during the posting process.
The date on which the transaction was posted or, if the detail is from History Loading, it is the accounting period.
A two-letter abbreviation for the type of transaction (such as EX for employee expense report). See Transaction Types in the
Accounting Concepts help for a full listing.
For a labor adjustment, the labor code from which the labor adjustment transaction was transferred.
For a labor adjustment, the project from which the labor adjustment transaction was transferred.
For a labor adjustment, the phase from which the labor adjustment transaction was transferred.
For a labor adjustment, the task from which the labor adjustment transaction was transferred.
The labor code for which the employee reported hours worked.
An employee may be assigned different labor codes on different projects, according to the work being performed.
If your firm uses Vision Payroll, this field lists the state or locale used to determine payroll tax.
Any notes for the project record, as entered in the Memo field on the General tab of the Project Info Center.
If the project record was created from an existing opportunity record, the name of that opportunity record displays in this field.
If the project record was created from an existing opportunity record, the number of that opportunity record displays in this field.
The unique identifier of the organization with which the project is associated.
The name of the organization with which the project is associated. Organization refers to the office within your firm that
Custom Reports and Microsoft SQL Server® Reporting Services 121
Contents of the Vision Report Model
Project Labor Field
Phase
Phase Name
Description
was responsible for this project.
The unique identifier for the phase.
The name of the phase.
The project location's phone number.
Phone
Primary Client
Principal Name
The firm for which you are directly performing work on the project.
The name of the principal at the firm who is associated with this project.
The employee number of the principal.
Principal Number
Project
Project Long Name
Project Manager Name
The project identifier.
The project's long name that is entered in the Project Info
Center.
The name of the project manager at your firm who is associated with this project.
The employee number of the project manager.
Project Manager Number
Project Name
Project Type
The short name of the project.
The type of project, such as Educational, Commercial, Financial,
Medical, Federal, and so on.
The promotional project linked to the project record.
Proposal WBS1
Referable
Responsibility
A Y or N (Yes or No) value that indicates whether or not the project can be used as a reference when you talk with potential clients.
The level of responsibility that your firm has for the project, such as Prime, Joint Venture, or Consultant.
You define the responsibility codes available to your firm in the Project Responsibility Code Table in Code
Table Configuration.
You assign the responsibility to a project on the General tab of the Project Info Center.
Responsibility Description
The description for the responsibility code that is entered in the
Project Responsibility Code Table.
Custom Reports and Microsoft SQL Server® Reporting Services 122
Contents of the Vision Report Model
Project Labor Field Description
Revenue Type Code
The code that is used to calculate revenue for this task, phase, or project. The standard revenue methods are:
B — Job-to-date Billings
M — (Job-to-date Direct Labor x Multiplier) + Job-todate Reimbursable Expenses @ Cost Rates
N — No revenue generation
P — Percent Complete + Job-to-date Reimbursable
Expenses @ Cost Rates
R — Job-to-date Receipts
W — Job-to-date Billings + Work-in-Progress (WIP) @
Billing Rates
Revenue Type Description
The description of the revenue source, such as:
JTD Billings
JTD Billings + WIP @ Billing
(Pct Comp*Fee) + JTD Reimb Exp
Start Date
State
The start date of the project, phase, or task.
The state where the firm is located.
Status
Supervisor Name
Supervisor Number
Task
The status of the project (Active, Inactive, or Dormant) that is entered on the General tab in the Project Info Center.
The name of the supervisor (at your firm) for a project that is entered on the General tab in the Project Info Center.
The employee number of the supervisor.
The unique identifier for the task.
Task Name
Total Budgeted OH Rate
Total Compensation
Total Consultant Fee
The name of the task.
The budgeted overhead rate for the project, phase, or task
(used for regular, revenue-producing projects).
If you use the assignment method for overhead allocation,
Vision uses the budgeted overhead rate for both budgeting and allocation purposes. For all other overhead allocation methods,
Vision uses the budgeted overhead rate to calculate the overhead amount only for the project budget.
The total contract value for this task, phase, or project.
Compensation is the total monetary amount you expect to receive; this amount should include all labor and expenses.
The project's consultant fee as entered in the Project Info
Custom Reports and Microsoft SQL Server® Reporting Services 123
Contents of the Vision Report Model
Project Labor Field
Total Cost Rate Meth
Total Cost Rate Table No
Total Expense Percent
Complete
Description
Center.
If you use Vision Payroll and you selected the Enable cost rate
tables check box in Accounting Configuration, this field displays the cost rate method for the project. The options are:
From Employee Cost Rate
From Labor Rate Table
From Category Rate Table
From Labor Code Table
None
If you use Vision Payroll and you selected the Enable cost rate
tables check box in Accounting Configuration, this field displays the cost rate table number on the report.
The estimate of how much of the expense budget has been spent to date on the project, phase, or task.
Total Firm Cost
Total Labor Bill Amount
The portion of the project cost for which your firm is responsible.
The billing amount that Vision applies to timesheet entries for this employee when calculating labor charges.
Total Labor Bill Rate
Total Labor Category
The billing rate that Vision applies to timesheet entries for this employee when calculating labor charges.
The employee's labor category, such as Principal, Project
Manager, or Architect.
Total Labor Cost Amount
The amount calculated for regular hours for the task, phase, or project. This amount is calculated as regular hours worked multiplied by the labor cost rate.
Total Labor Cost Overtime
Amount
The amount calculated for overtime hours for the task, phase, or project.
Vision Reporting calculates overtime costs for hourly employees differently than it does for salaried employees.
For hourly employees, the overtime amount is calculated as:
Overtime hours x Hourly labor costing rate x Overtime percentage
For salaried employees, Vision begins by calculating the employee's annualized hourly rate, using this equation:
Annual salary / Estimated annual regular hours, defined as
Hours per week x 52
Then calculates the overtime amount as:
Overtime hours x Annualized hourly rate x Overtime
Custom Reports and Microsoft SQL Server® Reporting Services 124
Contents of the Vision Report Model
Project Labor Field
Total Labor Cost Overtime
Rate
The cost rate Vision applies to overtime hours for this employee when calculating labor charges.
Total Labor Cost Rate
Description
percentage
Total Labor Cost Special
Overtime Amount
Total Labor Cost Special
Overtime Rate
The cost rate that Vision applies to timesheet entries for this employee to calculate labor charges.
The amount calculated for special overtime hours for the task, phase, or project.
The rate at which special (secondary) overtime hours are multiplied to derive the special overtime amount for the transaction. Vision multiplies an employee's hourly rate by the employee's secondary overtime percentage to calculate the special overtime rate.
Total Labor Overtime
Hours
Total Labor Overtime
Percent
Total Labor Percent
Complete
The number of overtime hours the employee reported for the task, phase, or project.
The rate at which overtime hours were multiplied to derive the overtime amount for the transaction. Vision multiplies an employee's hourly rate by the employee's overtime percentage to calculate the overtime rate.
The estimate of how far work has progressed on the project, phase, or task.
Total Labor Regular Hours
The number of regular hours the employee reported for the task, phase, or project.
Total Labor Special
Overtime Hours
The number of special (secondary) overtime hours the employee reported for the task, phase, or project.
Special overtime is costed and paid at a different rate than standard overtime. If you pay separately for special overtime, you must record these hours separately on the timesheet.
You set secondary overtime on the Accounting tab of the
Employee Info Center.
Total Labor Special
Overtime Percent
Total Multiplier Amount
The secondary overtime percentage from the employee record, used to derive the special overtime rate for the transaction.
Vision multiplies an employee's hourly rate by the special overtime percentage to calculate the employee's special overtime rate.
The multiplier, percentage, or amount by which to increase or decrease revenue for this task, phase, or project. Revenue methods that contain a multiplier or an amount in the calculation use this field.
Custom Reports and Microsoft SQL Server® Reporting Services 125
Contents of the Vision Report Model
Project Labor Field
Total Overall Percent
Complete
Total Pay Rate Table No
Total Pay Rate Meth
Total Project Cost
Comment
Total Reimb Allowance
Total Total Project Cost
Total X Charge Multiplier
Total X Charge Method
Unit Table
Description
The weighted average percent complete that is calculated as
(All percent completes x Their budgets) divided by the Total project budget.
If you use Vision Payroll and you selected the Enable payrate
tables for overriding payrate from Employee Info Center check box in Payroll Configuration, this field displays the pay rate table number on the report.
If you use Vision Payroll and you selected the Enable payrate
tables for overriding payrate from Employee Info Center option in Payroll Configuration, this field shows the pay rate method for the project. The options are:
From Employee Pay Rate
From Labor Rate Table
From Category Rate Table
From Labor Code Table
None
Any comments that accompany the Total Project Cost column.
For example, this column might contain a brief description about the cost of the project, such as "fee only," "Phase I," and so on.
The expected amount of reimbursable expense billings for this task, phase, or project.
The total cost of the project.
The multiplier used when the Cross Charge Method is Project, and the Cross Charge Rate is set to Multiplier on the
Accounting tab of the Project Info Center.
This field identifies the Labor Cross Charge rate or transfer price calculation method for this project/phase/task that is entered n the Cross Charge Rate field on the Accounting tab of the
Project Info Center. Display options are:
1 — (One) Indicates a selection of Billing Terms. This means Vision uses the project/phase/tasks billing terms to calculate the rate. If none are specified, Vision uses the billing terms marked Use as Project Reporting
Default Terms Only in Billing, Billing Terms. If none are specified, Vision uses the billing terms on the Labor tab of Configuration » Billing » Default Terms.
0 — (Zero) Indicates a selection of Multiplier. This means Vision uses the multiplier entered on the
Accounting tab of the Project Info Center.
The unit table that is used as the default when billing unit
Custom Reports and Microsoft SQL Server® Reporting Services 126
Contents of the Vision Report Model
Project Labor Field
XCharge
Zip
Description
charges for the project.
This field indicates which Labor Cross Charge configuration settings currently apply to this project/phase/task. Valid options are:
G — Global (the default setting). This option indicates that Vision uses the cross charge method specified on the Cross Charge tab of Individual Organization setup.
N — None
P — Project. This option indicates that Vision uses the cross charge method specified for the project in the
Cross Charge Rate field on the Accounting tab of
Project Info Center.
The project location's ZIP code.
Project Labor Posted Only Entity
Use the Project Labor Posted Only entity to create project labor reports that include only posted transactions. The fields are the same fields as those listed in the "Project Labor" section, above.
Project Labor Unposted Only Entity
Use the Project Labor Unposted Only entity to create project labor reports that include only unposted transactions. The fields are the same fields as those listed in the "Project Labor" section, above.
Project List Entity
Use the Project List entity to create project list reports. When you use this entity, report content is retrieved from or calculated with fields from the following Vision database tables:
PR (Project)
CFGChargeType (Configuration Table — Project Charge Types)
CL (Client)
CFGProjectStatus (Configuration Table — Project Status)
CFGRGMethods (Configuration Table — Revenue Generation Methods)
Organization (Configuration Table — Organizations)
Contacts
CFGProjectType (Configuration Table — Project Charge Types)
CFGPRResponsibility (Configuration Table — Primary Responsibility)
Opportunity
EM (Employee)
The Project List entity provides you with the following fields to add to custom reports.
Custom Reports and Microsoft SQL Server® Reporting Services 127
Contents of the Vision Report Model
Project List Field Description
#Project List Data Sources
When you add this field to a report, it counts the items that were used to compile the information in a row on the report.
Actual Completion Date
For any completed project, the date on which the project was finished.
Address1–Address3
Approved for use in accounting applications
The first, second, and third address lines of the client's street address entered for the client's record.
A Y or N (Yes or No) value that indicates whether or not the record is approved for use in transaction processing. You may not need to include this field on a report, but it may be useful when you build queries
Available to Accounting
Users
Available to CRM Users
Bid Date
Bill By Default
Bill Client Name
Billable Message
A Y or N (Yes or No) value that indicates whether or not the record is available to accounting users. You may not need to include this field on a report, but it may be useful when you build queries.
A Y or N (Yes or No) value that indicates whether or not the record is available to Customer Relationship Management users. You may not need to include this field on a report, but it may be useful when you build queries.
The date on which your firm first bid on the project.
Indicates whether or not to bill the client for certain expense charges posted to the project. The values are:
Yes — Always bill expense charges to the client, regardless of whether the Bill by default check box is selected for the associated category in Expense
Category Configuration.
No — Never bill expense charges to the client, regardless of whether the Bill by default check box is selected for the associated category in Expense
Category Configuration.
Category — Only bill charges to the client if the Bill by
default check box is selected for the associated category in Expense Category Configuration.
The client to be billed for the project.
Indicates whether or not to display an error message in the
Expense Report application when a user charges certain expenses to this project. The values are:
No Message — Vision does not display any message when the category bill by default method and the project bill by default method are different.
Warning — Vision displays a warning message when the category bill by default method and the project bill
Custom Reports and Microsoft SQL Server® Reporting Services 128
Contents of the Vision Report Model
Project List Field
Biller
Billing Contact Name
Budgeted Labor Code
Validation
BudgetedLevels
Charge Type
Description
by default method are different. You must explicitly choose to continue with the transaction if you want to process the expense charge to the project using the selected category.
Error — Vision displays an error message when the category bill by default method and the project bill by default method are different. You cannot process the expense charge to the project using the selected category.
The employee who is responsible for creating the Billing invoices for a project. This is entered on the General tab in the
Project Info Center.
The contact name to be billed for the project.
Budgeted labor code check for timesheets. The options are:
N — None
W — Warning
E — Error
The labor code levels that employees can use when they charge time to the project. The budgeted labor code level options that are available vary based on the number of labor code levels that you establish in Utilities » Key Conversions »
Labor Codes.
The project's charge type as entered on the Accounting tab in the Project Info Center. The options are:
R — Regular. Regular projects are revenue-producing.
The costs charged to regular projects include direct labor, direct expense, and reimbursable expense. Detail is retained for the life of the project.
H — Overhead. Overhead projects are not revenueproducing. The costs charged to overhead projects include indirect labor and indirect expense. The total cost of these projects is distributed to regular projects during overhead allocation. Typical overhead projects can include: General Overhead, Vacation, Sick Leave,
Holiday, or Civic Duty. Overhead projects zero out when you initialize for a new fiscal year.
P — Promotional. Use promotional projects to track the cost of trying to acquire a job. If the job is obtained, you can create a new regular project and transfer the detail to it to be billed or tracked. A promotional project is the same as an overhead project, with this exception—
Vision does not zero out job-to-date costs at the start of each fiscal year for promotional projects.
Custom Reports and Microsoft SQL Server® Reporting Services 129
Contents of the Vision Report Model
Project List Field Description
City
CLAddress
Client Alias
Client Billing Address
Client Confidential
The city where the firm is located.
The client address code.
The alternate name used in proposals to represent a client who wishes to keep the firm's name confidential.
For clients with more than one address, this field indicates the address to which you are sending bills for this project. This field displays a description of the address on the report, rather than the actual address. For example, you might see:
<Default> — The default billing address from the client record.
Corporate HQ — The address for the client's headquarters.
A Y or N (Yes or No) value that indicates whether or not the client firm's name is confidential and is to be excluded from all proposals. When you include the project in a proposal, the alias
(client alias) is substituted for the client name.
Completion Date Comment
User-entered comment related to the completion date.
Contact Name
Your contact at the client firm.
ContactID
The contact record number for the primary contact.
Contract Date
Country
County
The date on which the contract was awarded to your firm.
The country where the firm is located.
The county where the firm is located.
Description
The project's description.
The project location's email address.
End Date
The completion date for the project, phase, or task.
Estimated Completion Date The date on which the project is/was scheduled to be completed.
Fax
The fax number at the project location.
Federal Project Indicator
A Y or N (Yes or No) value that indicates whether or not the current project is a federal project.
Firm Cost Comment
Displays any comments that accompany the Firm Cost field.
Has SubLevels Turned On
A Y or N (Yes or No) value that indicates whether or not the project, phase, or task is associated with a sub-level billing term.
Custom Reports and Microsoft SQL Server® Reporting Services 130
Contents of the Vision Report Model
Project List Field
Locale
Memo
Opportunity Description
Opportunity ID
Organization Code
Organization Name
Phase
Phase Name
Phone
Primary Client
Principal Name
Principal Number
Project
Project Long Name
Project Manager Name
Project Manager Number
Project Name
Project Type
Proposal WBS1
Description
See Phase or Task Billing Terms in the Vision help system for information about sub-level billing terms.
If your firm uses Vision Payroll, this field lists the state or locale used to determine payroll tax.
Displays notes specified for the project record that are entered in the Memo field on the General tab of the Project Info Center.
If the project record was created from an existing opportunity record, the name of that opportunity displays in this field.
If the project record was created from an existing opportunity record, the number of that opportunity displays in this field.
The identifier of the organization with which the project is associated.
The name of the organization with which the project is associated. Organization refers to the office or profit center within your firm that was responsible for this project.
The unique identifier for the phase.
The name of the phase.
The project location's phone number.
The firm for which you are directly performing work on the project.
The name of the principal at the firm who is associated with this project.
The employee number of the principal.
The project identifier.
The project's long name entered in the Project Info Center.
The name of the project manager at your firm who is associated with this project.
The employee number of the project manager.
The short name of the project.
The type of project, such as Educational, Commercial,
Financial, Medical, or Federal.
The promotional project linked to the project record.
Custom Reports and Microsoft SQL Server® Reporting Services 131
Contents of the Vision Report Model
Project List Field Description
Referable
Responsibility
A Y or N (Yes or No) value that indicates whether or not the project can be used as a reference when you talk with potential clients.
The level of responsibility that your firm has for the project, such as Prime, Joint Venture, Consultant, and so on.
You determine the responsibility codes available to your firm in the Project Responsibility Code Table in Code
Table Configuration.
You assign the responsibility to a project on the General tab of the Project Info Center.
Responsibility Description
The description for the responsibility code entered in the Project
Responsibility Code Table.
Revenue Type Code
This is used to calculate revenue for this task, phase, or project.
Vision provides six standard revenue methods:
B — Job-to-date Billings
M — (Job-to-date Direct Labor x Multiplier) + Job-todate Reimbursable Expenses @ Cost Rates
N — No revenue generation
P — Percent Complete + Job-to-date Reimbursable
Expenses @ Cost Rates
R — Job-to-date Receipts
W — Job-to-date Billings + Work-in-Progress (WIP) @
Billing Rates
Revenue Type Description
The description of the revenue source. For example:
JTD Billings
JTD Billings + WIP @ Billing
(Pct Comp*Fee) + JTD Reimb Exp
Start Date
State
The start date of the project, phase, or task.
The state where the firm is located.
Status
Supervisor Name
The status (Active, Inactive, or Dormant) of the project.
The name of the supervisor at your firm who is associated with this project.
The employee number of the supervisor.
Supervisor Number
Task
Task Name
The unique identifier for the task.
The name of the task.
Custom Reports and Microsoft SQL Server® Reporting Services 132
Contents of the Vision Report Model
Project List Field
Total Budgeted OH Rate
Total Compensation
Total Consultant Fee
Total Cost Rate Meth
Total Cost Rate Table No
Total Expense Percent
Complete
Total Firm Cost
Total Labor Percent
Complete
Total Multiplier/Amount
Total Overall Percent
Complete
Description
The budgeted overhead rate for the project, phase, or task This is used for regular, revenue-producing projects.
If you use the assignment method for overhead allocation, Vision uses the budgeted overhead rate for both budgeting and allocation purposes.
For all other overhead allocation methods, Vision uses the budgeted overhead rate to calculate the overhead amount only for the project budget.
The total contract value for this task, phase, or project. It is the total monetary amount that your company expects to receive; it includes all labor and expenses.
The project's consultant fee that is entered in the Project Info
Center.
If you use Vision Payroll, and you have selected the Enable
cost rate tables check box in Accounting Configuration, this field displays the cost rate method for the project on the report.
The options are:
From Employee Cost Rate
From Labor Rate Table
From Category Rate Table
From Labor Code Table
None
If you use Vision Payroll and you have selected the Enable
cost rate tables check box in Accounting Configuration, this field displays the cost rate table number on the report.
The estimate of how much of the expense budget has been spent to date on the project, phase, or task.
The portion of the project's total cost for which your firm is responsible.
The estimate of how far work has progressed on the project, phase, or task.
The multiplier, percentage, or amount by which to increase or decrease revenue for this task, phase, or project. Revenue methods that contain a multiplier or an amount in the calculation use this field.
The weighted average percent complete, calculated as (all percent completes x their budgets) divided by the total project budget.
Custom Reports and Microsoft SQL Server® Reporting Services 133
Contents of the Vision Report Model
Project List Field
Total Pay Rate Meth
Total Pay Rate Table No
Total Project Cost
Comment
Total Reimb Allowance
Total Project Cost
Total X Charge Method
Total X Charge Multiplier
Unit Table
XCharge
Description
If you use Vision Payroll and you selected the Enable payrate
tables for overriding payrate from Employee Info Center option in Payroll Configuration, this field shows the pay rate method for the project. The options are:
From Employee Pay Rate
From Labor Rate Table
From Category Rate Table
From Labor Code Table
None
If you use Vision Payroll, and you selected the Enable payrate
tables for overriding payrate from Employee Info Center check box in Payroll Configuration, this field displays the pay rate table number on the report.
Any comments that accompany the Total Project Cost column.
For example, this column might contain a brief description about the cost of the project, such as "fee only," "Phase I," and so on.
The expected amount of reimbursable expense billings for this task, phase, or project
The total cost of the project.
This field indicates the Labor Cross Charge rate or transfer price calculation method for this project/phase/task, as established in the Cross Charge Rate field on the Accounting tab of the
Project Info Center.
The display options are:
1 — A 1 (one) indicates a selection of Billing Terms.
This means Vision uses the project/phase/tasks billing terms to calculate the rate. If none are specified, Vision uses the billing terms marked Use as Project Reporting
Default Terms Only in Billing, Billing Terms. If none are specified, Vision uses the billing terms on the Labor tab of Configuration » Billing » Default Terms.
0 — A 0 (zero) indicates a selection of Multiplier. This means Vision uses the multiplier entered on the
Accounting tab of the Project Info Center.
The multiplier that is used when the Cross Charge Method is
Project, and the Cross Charge Rate is set to Multiplier from the Accounting tab of the Project Info Center.
The unit table used as the default when billing unit charges for the project.
This field indicates which Labor Cross Charge configuration
Custom Reports and Microsoft SQL Server® Reporting Services 134
Contents of the Vision Report Model
Project List Field
Zip
Description
settings currently apply to this project/phase/task. The options are:
G — Global (the default setting). This option indicates that Vision uses the cross charge method specified on the Cross Charge tab of Individual Organization setup.
N — None
P — Project. This option indicates that Vision uses the cross charge method specified for the project in the
Cross Charge Rate field on the Accounting tab of the
Project Info Center.
The project location's ZIP code.
Project Summary at Billing Entity
Use the Project Summary at Billing entity to create summary reports with project billing information. When you use this entity, report content is retrieved from or calculated with fields from the following Vision database tables:
PR (Project)
CFGChargeType (Configuration Table — Project Charge Types)
Client (CL)
CFGProjectStatus Configuration Table — Project Status)
CFGRGMethods (Configuration Table — Revenue Generation Methods)
Organization (Configuration Table — Organizations)
Contacts
CFGProjectType (Configuration Table — Project Charge Types)
CFGPRResponsibility (Configuration Table — Primary Responsibility)
Opportunity
EM (Employee)
The fields in the Project Summary at Cost entity are the same fields that are in the Project
Summary at Billing entity, except they use cost rates rather than billing rates.
The Project Summary at Billing entity provides the following fields to add to custom reports.
Project Summary at Billing Field Description
#Project Summary Data
Source Report at Billing
ClientID
ClientName
When you add this field to a report, it counts the items that were used to compile the information in a row on the report.
The record number (identifier) for the client record.
The name of the client for this project.
Custom Reports and Microsoft SQL Server® Reporting Services 135
Contents of the Vision Report Model
Project Summary at Billing Field Description
ContactID
ContactName
PhaseManagerName
PhaseManagerNumber
PhaseName
PhaseNumber
PhasePrincipalName
PhasePrincipalNumber
PhaseSupervisorName
PhaseSupervisorNumber
PKey
Project Charge Type
The record number (identifier) for the contact record.
The name of the contact for this project.
The name of the manager at your firm who is associated with this phase.
The employee number of the manager at your firm who is associated with this phase.
The phase name.
The phase identifier.
The name of the principal at your firm who is associated with this phase.
The employee number of the principal at your firm who is associated with this phase.
The name of the supervisor at your firm who is associated with this phase.
The employee number of the supervisor at your firm who is associated with this phase.
An internal primary key.
The charge type of the project that is entered on the
Accounting tab in the Project Info Center. The options are:
R Regular — Regular projects are revenueproducing. The costs charged to regular projects include direct labor, direct expense, and reimbursable expense. Detail is retained for the life of the project.
H Overhead — Overhead projects are not revenueproducing. The costs charged to overhead projects include indirect labor and indirect expense. The total cost of these projects is distributed to regular projects during overhead allocation. Typical overhead projects can include General Overhead,
Vacation, and Sick Leave. Overhead projects zero out when you initialize for a new fiscal year.
P Promotional — Use promotional projects when you want to track the cost of trying to acquire a job.
If the job is obtained, you can create a new regular project and transfer the detail to it to be billed or tracked. A promotional project is the same as an overhead project, with this exception - Vision does not zero out job-to-date costs at the start of each
Custom Reports and Microsoft SQL Server® Reporting Services 136
Contents of the Vision Report Model
Project Summary at Billing Field Description
fiscal year for promotional projects.
Project Revenue Type
The revenue type is the code used for calculating revenue for this project. Vision provides six standard revenue methods:
B — Job-to-date Billings
M — (Job-to-date Direct Labor x Multiplier) + Job-todate Reimbursable Expenses @ Cost Rates
N — No revenue generation
P — Percent Complete + Job-to-date Reimbursable
Expenses @ Cost Rates
R — Job-to-date Receipts
W — Job-to-date Billings + Work-in-Progress (WIP)
@ Billing Rates
ProjectManagerName
ProjectManagerNumber
The name of the project manager at your firm who is associated with this project.
The employee number of the project manager at your firm who is associated with this project.
ProjectName
ProjectNumber
ProjectPrincipalName
ProjectPrincipalNumber
The project name.
The project identifier.
The name of the principal at your firm who is associated with this project.
The employee number of the principal at your firm who is associated with this project.
ProjectSupervisorName
ProjectSupervisorNumber
The name of the supervisor at your firm who is associated with this project.
The employee number of the supervisor at your firm who is associated with this project.
Custom Reports and Microsoft SQL Server® Reporting Services 137
Contents of the Vision Report Model
Project Summary at Billing Field Description
Record Type Code
TaskManagerNumber
Internal record codes:
0 — Project Info
1 — Labor
2 — Overhead
3 — Direct expenses
5 — If charge type is R, then Reimb Expenses, otherwise, Expenses.
6 — Indirect expenses
7 — AR, Revenue
9 — Billed, Received
The description for the internal record type codes.
Record Type Description
Resource Planning Detail
Value
Resource Planning wbs level
The lowest level of the work breakdown structure that a plan has.
SubLevel1
Variable that indicates whether or not the project has phases.
SubLevel2
Variable that indicates whether or not the phase has tasks.
TaskManagerName
The value that represents the setting that is selected in the
Planning Details field on the Option tab in Planning »
Resource Management » Resource Utilization.
This setting determines how records display on the
Resource Utilization grid.
Include Numbers with Plan Names
Include Numbers with Plan Level Names
The name of the manager at your firm who is associated with this task.
The employee number of the manager at your firm who is associated with this task.
TaskName
TaskNumber
TaskPrincipalName
TaskPrincipalNumber
The task name.
The task identifier.
The name of the principal at your firm who is associated with this task.
The employee number of the principal at your firm who is associated with this task.
Custom Reports and Microsoft SQL Server® Reporting Services 138
Contents of the Vision Report Model
Project Summary at Billing Field Description
TaskSupervisorName
TaskSupervisorNumber
The name of the supervisor at your firm who is associated with this task.
The employee number of the supervisor at your firm who is associated with this task.
Total Hours Percent Complete
Select Min Amount Percent Complete, an additional item for Total Hours Percent Complete to include the project's total hours percent complete on a report.
Total Baseline Amount
The sum of all the baseline amounts (labor, expense, and unit) for a plan.
Total Budgeted Amount
Total Budgeted Hours
Total Current Amount
Total Current AR Amount
The total monetary amount budgeted for this project.
The hours budgeted for this project.
The labor amount spent for the current accounting period.
The amount billed but not yet received for the current accounting period.
Total Current Billed
Total Current Direct
Total Current Gross Margin
Total Current Hours
Total Current Net Revenue
The total amount billed (Labor + Fee + Consultants +
Expenses + Units + Interest Billed) for the current accounting period.
The total direct expenses for the current accounting period.
The gross margin for the current accounting period.
Total Revenue – (Labor + Direct + Reimbursable Amounts
Spent)
Firms that do not allocate overhead show project results on a gross margin basis.
Labor hours spent for this project for the current accounting period.
The total revenue for the project for the current accounting period.
Non-Labor Direct Expense + Reimbursable Expense
Total Current Profit
Total Current Received
Total Current Revenue
The amount of profit calculated for this project for the current accounting period.
Revenue – Spent = Profit
The amount received for this project for the current accounting period.
The amount of revenue calculated for this project for the
Custom Reports and Microsoft SQL Server® Reporting Services 139
Contents of the Vision Report Model
Project Summary at Billing Field Description
current accounting period.
Total Current Unbilled
The amount of revenue not yet billed for this project for the current period.
Revenue – Billed = Unbilled
Total EAC Amount
EAC = Estimate at Completion.
The estimate of the total monetary amount that will have been incurred at the completion of the project.
Total ETC Amount
Total Hours EAC
Total Hours ETC
Total Hours Percent Complete
The project manager’s stated percentage of work effort (total hours) completed on this project.
Total JTD Amount
Total JTD AR Amount
Total JTD Billed
The job-to-date labor amount spent.
The job-to-date amount billed but not yet received.
The job-to-date amount billed (Labor + Fee + Consultants +
Expenses + Units + Interest Billed).
Total JTD Direct
Total JTD Gross Margin
Estimate to Complete Amount
The estimate of the total additional monetary amount— beyond the spent to date—that is required to complete the work.
Estimate at Completion Hours
The estimate of the total number of hours that will have been worked at the completion of a project.
Estimate to Complete Hours
The estimate of the total additional labor hours—beyond those worked to date—that are required to complete the work.
Total JTD Hours
Total JTD Net Revenue
Total JTD Profit
The total direct expenses for the current accounting period.
The job-to-date gross margin.
JTD Total Revenue – (JTD Labor + JTD Direct + JTD
Reimbursable Amounts Spent)
Firms that do not allocate overhead show project results on a gross margin basis.
The job-to-date labor hours spent for a project.
The job-to-date revenue for a project.
Non-Labor Direct Expense + Reimbursable Expense
The job-to-date profit.
Custom Reports and Microsoft SQL Server® Reporting Services 140
Contents of the Vision Report Model
Project Summary at Billing Field Description
Revenue – Spent = Profit
Total JTD Received
Total JTD Revenue
The job-to-date amount received for a project.
The job-to-date amount of revenue calculated for a project.
Total JTD Unbilled
Total Labor Budgeted for
Overhead
The job-to-date amount of revenue not yet billed for a project.
Revenue – Billed = Unbilled
The total monetary amount of overhead budgeted for a project.
Total Planned Amount
Total Project Consultant Fee
The sum of all the plan amounts (labor, expense, and unit).
The expected amount of reimbursable consultant fees for a project. This amount includes any markups on consultant professional services.
Total Project Fee
Total Project
Multiplier/Amount
A project's total fee.
The multiplier, percentage, or amount by which to increase or decrease revenue for a project. Revenue methods that contain a multiplier or an amount in the calculation use this field.
Total Project Percent
Complete
The project manager’s stated percentage of work effort completed on a project.
Total Project Reimb Allowance
The expected amount of reimbursable expense billings for a project.
Total Rpdata
Resource Planning
Total Resource Planning
Percent Complete
Total YTD Amount
Total YTD AR Amount
Total YTD Billed
The overall percent complete for the cost budget (from the
PctComplete field in the RP Plan table.
The year-to-date labor amount spent.
The year-to-date amount billed but not yet received.
Total YTD Direct
Total YTD Gross Margin
The year-to-date amount billed (Labor + Fee + Consultants
+ Expenses + Units + Interest Billed).
The year-to-date direct expenses.
The year-to-date gross margin.
YTD Total Revenue – (YTD Labor + YTD Direct + YTD
Reimbursable Amounts Spent)
Firms that do not allocate overhead show project results on
Custom Reports and Microsoft SQL Server® Reporting Services 141
Contents of the Vision Report Model
Project Summary at Billing Field Description
a gross margin basis.
Total YTD Hours
Total YTD Net Revenue
Total YTD Profit
The year-to-date labor hours spent for a project.
The year-to-date revenue for a project.
Non-Labor Direct Expense + Reimbursable Expense
The year-to-date profit.
Revenue – Spent = Profit
Total YTD Received
Total YTD Revenue
Total YTD Unbilled
The year-to-date amount received for a project
The year-to-date amount of revenue calculated for a project.
The year-to-date amount of revenue not yet billed for a project.
Revenue – Billed = Unbilled
The project to which the summary belongs.
Project Number
Phase Number
Task Number
The phase to which the summary belongs.
The task to which the summary belongs.
Project Summary at Cost Entity
Use the Project Summary at Cost entity to create summary reports with project costing information.
The fields in the Project Summary at Cost entity are the same fields that are in the Project
Summary at Billing entity, except they use cost rates rather than billing rates. See the "Project
Summary at Billing" section on page 135 of this guide for the list of fields.
Vendor Entity
Use the Vendor entity to create vendor reports. When you use this entity, report content is retrieved from or calculated with fields from the following Vision database tables:
VE (Vendor)
VEAddress (Vendor Table - Addresses)
CFGfAPDiscount (System Setup Table - Accounts Payable Discount Codes)
CFGBillTaxes (Billing Setup Table - Tax Codes)
CFGCountry (System Setup Table - Countries)
CFGPrimarySpecialty (System Setup Table - Employee Primary Specialties)
CFGVendorStatus (System Setup Table - Vendor Status)
CFGVendorType (System Setup Table - Vendor Types)
Organization
Custom Reports and Microsoft SQL Server® Reporting Services 142
Contents of the Vision Report Model
The Vendor entity provides you with the following fields to add to custom reports.
Vendor Field Description
#Vendordata Sources
AccountNumber
Active Company
AddrCreatDate
AddrCreateUser
Address
Address1–Address4
AddrModDate
AddrModUser
Category
CategoryLabel
CheckPerVoucher
City
Country
CreateDate
CreateUser
DefaultTaxCode
DefaultTaxCodeLabel
DisadvBusiness
When you add this field to a report, it counts the items that were used to compile the information in a row on the report.
The account number of your customer account with this vendor.
If you use the Multicompany feature in Vision, this is the company that you have open when you run a report.
The date and time when the vendor address record was created.
The user who created the vendor address record.
The vendor's address code.
The first, second, third, and fourth lines of the vendor's address.
The date and time when the vendor address record was last modified.
The last user who modified the vendor address record.
A letter that corresponds to the vendor type such as T (Trade),
C (Consultant), or E (Employee).
The vendor type, such as Trade, Consultant, or Employee.
A Y or N (Yes or No) value that indicates whether or not to print a separate check for each voucher for the vendor.
The vendor's city.
The vendor's country.
The date and time when the vendor record was created.
The user who created the vendor record.
The vendor's default tax code that is used when Enable tax
auditing feature check box is selected on the Tax Auditing tab of Configuration » Accounting » Company Settings.
The tax code description to print on invoices. The value is stored in the Description field of the CFGBillTaxes table.
A Y or N (Yes or No) value that indicates whether or not the vendor is a disadvantaged business.
Custom Reports and Microsoft SQL Server® Reporting Services 143
Contents of the Vision Report Model
Vendor Field Description
DiscCode
DiscCodeLabel
The default discount code for the vendor.
The description for the vendor's discount code, such as
Discounts Taken, Discounts Applied, and Discounts Ongoing.
Fax
FedID
The vendor's fax number.
The vendor's federal taxpayer identification number.
GroupKey
The vendor name and number.
HBCU or MinorityInstitution
A Y or N (Yes or No) value that indicates whether or not the vendor has an HBCU (Historically Black Colleges and
Universities) or minority institution status.
MinorityOwned
ModDate
A Y or N (Yes or No) value that indicates whether or not the vendor is a minority-owned business.
The date and time when the vendor record was last modified.
ModUser
OHAccount
Org
OrgName
PayTerms
The last user who modified the vendor record.
The default account to use for overhead projects in data entry.
The code for the vendor's organization. This is used for sorting purposes only.
The name of the vendor's organization.
A variable that indicates the default payment terms for the vendor. Options are Number of Days, Hold, Next, or PWP (Pay
When Paid).
Phone
PrimaryInd
PriorWork
Recommend
RegAccount
Req1099
SmallBusiness
The vendor's phone number.
A Y or N (Yes or No) value that indicates whether or not the address is the vendor's primary address.
A Y or N (Yes or No) value that indicates whether or not the vendor has done prior work for the organization.
A Y or N (Yes or No) value that indicates whether or not the vendor has been recommended to do work for the organization in the future.
The default account to use for regular projects in data entry.
A Y or N (Yes or No) value that indicates whether or not a 1099 form is required for the vendor.
A Y or N (Yes or No) value that indicates whether or not the
Custom Reports and Microsoft SQL Server® Reporting Services 144
Contents of the Vision Report Model
Vendor Field
Specialtydesc
State
Status
StatusLabel
TaxCountryCode
TaxCountryCodeLabel
TaxRegistrationNumber
Total Disc Pct
Total Disc Period
Total Last Year 1099
Total This Year 1099
Market
TypeLabel vememo
Vendor
VendorName
Website
WomanOwned
Description
vendor is a small business.
The description of the vendor's business specialty that is entered on the General tab of the Vendor Info Center.
The vendor's state.
The vendor's status (code). Options are A—Active, I—Inactive, and D—Dormant.
The label for the vendor's status—Active, Inactive, or Dormant.
The value is stored in the Label field of the CFGVendorStatus table.
The two-character tax code for the country in which the vendor is located.
The name of the country in which the vendor is located. This value is stored in the Country field of the CFGCountry table.
The vendor's tax registration number.
The discount percent for the vendor.
The number of days within which payment must be received for the discount to apply.
The 1099 amount for last year. The 1099 form for the vendor should match this amount.
The amount paid to the vendor since the last 1099 initialization.
The two-digit code for the vendor's primary specialty as entered in the Specialty field of the Vendor Info Center. The value is stored in the Type field of the VE table.
The description of the vendor's selected specialty as defined in the Description field of the Vendor Primary Specialty Code table. The description value is stored in the Description field of the CFGPrimarySpecialty table.
Any notes that are entered for the vendor record.
The vendor number.
The vendor name.
The vendor's Web site address.
A Y or N (Yes or No) value that indicates whether or not the vendor is a woman owned business.
Custom Reports and Microsoft SQL Server® Reporting Services 145
Contents of the Vision Report Model
Vendor Field
Zip
Description
The vendor's ZIP code.
Custom Reports and Microsoft SQL Server® Reporting Services 146
Deltek is the leading global provider of enterprise software and information solutions for professional services firms, government contractors, and government agencies. For decades, we have delivered actionable insight that empowers our customers to unlock their business potential. Over 14,000 organizations and 1.8 million users in approximately 80 countries around the world rely on Deltek to research and identify opportunities, win new business, optimize resource, streamline operations, and deliver more profitable projects. Deltek – Know more. Do more.
® deltek.com
Download
Public link updated
The public link to your chat has been updated. You may view and manage your chat links after registration here.
Document public link
Advertisement
Key features
Project Management
Financial Management
Resource Management
Reporting and Analytics
Integration with Microsoft SQL Server Reporting Services
Frequently asked questions
Deltek Vision Software 7.6 is a comprehensive software solution that helps businesses manage projects, finances, and resources. It provides a single platform for managing all aspects of a business, from project planning and execution to financial reporting and analysis.
To create custom reports, you need to install either Report Builder 3.0 or SQL Server Data Tools - Business Intelligence for Visual Studio 2013 Report Designer (SSDT-BI 2013 Report Designer) on your machine. These tools come with SSRS versions 2008 R2, 2012 and 2014.
Before you can access the Vision report model in Report Builder, you must load it onto your SSRS report server. You can do this by following the steps in the "Report Builder and the Vision Report Model" section of this guide.
