What are Tyler Reporting Services views

What are TRS views and how to identify them?

• Tyler Reporting Services

• Custom Reporting

• SSRS, Crystal Reports

• SaaS, OnPrem hosted clients

• Enterprise ERP(MUNIS)

Informational

Tyler Reporting Services (TRS) views are database objects in Enterprise ERP that provide secure, role-based access to data for custom reporting through SSRS. By joining multiple base tables, they simplify complex schemas and present data in an easily consumable, human-friendly format suitable for common business intelligence tools. TRS views enforce role-based access control by verifying user permissions for each ERP module, enhancing data interpretation and analysis.

All TRS views follow a naming convention, which help report builder distinguish them from other database objects. All TRS views(with some exceptions) are named using the following template:

1. Starts with a 2 letter lower case module code.

2. Followed by an underscore.

3. Ends with a human-friendly name in lowercase.

In addition to naming convention, all TRS views are available in dbo schema. However, the following are some exceptions:

1. All views in AccountsReceivableReportingServices schema are also considered TRS Views. 

2. Some views pertaining to Tax and Revenue module start with a 4 letter code instead of 2 letter code.

3. Views in PayrollAuditReportingServices schema are also considered TRS Views, these views provide auditing information for payroll module.

Some examples of TRS views are:

• ap_checks

• pr_employee_master

• gl_detail

• ut_consumption

Examples of some view in dbo schema that are not TRS views:

• premppay

• premppay_all

• arbilhdr

• utsvcmst

For custom reporting, it is highly recommended to use TRS views in-lieu of base tables and deprecated views. If any information is not presented through any TRS views, an enhancement request can be submitted using the following instructions:

How to submit enhancement request in Enterprise ERP