Forums
Query views
Technology Forum
Query views
Discuss how to choose system that will yield the best results, as well as how to maintain it, and how to calculate its return on investment.
This question is directed to any users of HRMS systems. Has anyone had experience with, built or used query views. What I mean is that instead of using the delivered query tables,which require an end
0
Cat:Topic ForumsForum:ForumId57
Cat:Topic ForumsForum:ForumId57Discussion:DiscussionId21779
Forums » Topic Forums » Technology Forum » Query views
|
Query views
posted at 5/1/2002 6:59 AM EDT
|
Posts: 10
First: 4/19/2002 Last: 3/19/2003 |
This question is directed to any users of HRMS systems. Has anyone had experience with, built or used query views. What I mean is that instead of using the delivered query tables,which require an end users to know table names and how to join keys, and create expressions etc... Actually built your own views (many tables already joined) allowing your end users to create their own reports by simply choosing the fields they want without having to worry about joins etc... I know this is rare as I have only seen this in one organization that absolutely supports the practice. |
|
|
Query views
posted at 5/1/2002 9:19 PM EDT
|
|
Posts: 15
First: 2/25/2002 Last: 6/20/2002 |
I know of an organisation using PeopleSoft who did exactly this kind of thing. They use Psofts custom queries (which can be quite complex regarding table names and joins etc) so they made a few 'views' (as you explained) which held most of the data that most people would want to report on. So many custom reports use these tables instead of the origin tables.
I also know of users in the same company who build custom queries in MS Access and therefore do a similar thing but using a different interface. Paul |
|
|
Query views
posted at 5/10/2002 3:04 AM EDT
|
|
Posts: 15
First: 2/25/2002 Last: 6/20/2002 |
The views that were created definitely made things easier.
I don't know exactly how much effort it was to create the views (how hard can it really be?!) - but it certainly makes creating queries based on these views much easier as people don't have to worry about getting table joins the right way around as well as all the other problems you highlighted. I passed on your details to the company concerned so they may be able to provide you with more info - I can't as I wasn't actually involved in the implementation, just the training |
|
|
Query views
posted at 5/23/2002 1:49 AM EDT
|
|
Posts: 15
First: 5/23/2002 Last: 9/25/2006 |
Oracle HRMS has the "View Only" and "Query Only" functions incorporated into their system. It is a matter of setting option in the Function for the Responsibility. The client where we are implementing requires it based on needs for different responsibilities. |
|
|
Query views
posted at 5/23/2002 3:09 AM EDT
|
|
Posts: 6
First: 5/23/2002 Last: 8/28/2002 |
There is another possibility you should consider. There are a number of Managed Query Environment (MQE) tools on the market. These tools let you create metadata definitions of your database. The metadata includes join paths, field definitions, calculations, etc. You can then use the metadata to create custom queries or ad hoc reports.
It is generally easier and more flexible to maintain the metadata in an MQE tool than it is to create and maintain views in the database. MQEs typically use drag and drop capabilities to define the metadata and to use the metadata to create new queries and reports. Administrators typically maintain the metadata. Business users can use the metadata to create their own ad hoc reports. Thus, an MQE can be used to off-load a lot of report writing from the IT staff to users. Some of the better known MQE tools on the market are from companies like Cognos, Business Objects, Brio, etc. |
|
|
Query views
posted at 7/30/2002 2:08 AM EDT
|
|
Posts: 4
First: 7/30/2002 Last: 7/30/2002 |
Generating queries by simply selecting columns is difficult in ERP systems because they are not designed to join tables together without the help of IT in most cases. On the other hand, decision support systems incorporating warehouses are specifically designed to do just that. The data is taken from the ERP systems (HRIS) as well as any other information system and combined for highly summarized as well as detailed information. The thousands of tables within the information sources have been intelligently joined and placed in the warehouse with the intent of having an HR professional select appropriate columns that have been joined and create new queries or tables that can then be used to generate reports. Some of the business intelligence vendors provide this functionality on a limited basis but are not easily created without the user having technical skills. Take a look at SAS Human Capital Management for query, reporting and analysis in a "user-friendly" format designed for HR. |
Forums » Topic Forums » Technology Forum » Query views
