Peoplesoft Query Overview Step-1 • Creating Access Group Trees Query • Permissions Security Step-2 • Query Types Query • Query Steps Process • Links and Icons Within Query Overview Manager • Selecting Records • Fields Step-3 • Expressions Creating • Prompts New • Criteria Queries • Saving • Previewing Query Reports Step-4 • • View SQL Subquery Advanced • Having • New Union Step-5 Scheduling Step-6 Query Viewer Step-7 Query Tables
Step-1 Query Security Creating a query tree and setting up a permission list that allows access to the query trees. Within the tree all tables that the end user isallowed to view must be included. If a table is not in the query tree, then the query will not be available for the end user to run. 1. Creating Access Group Trees:- Navigate: People Tools -> Security-> Query Security->Query Access Manager Note: Query Access Manager is the Administration Tool
- CreatingCreate A New Tree or Option to retrieve an existing Tree for Modification Enter a tree name and a description, and verify that the status is active and assign Access Group Tree Created a tree with access groups allow you to set up security forSave the page after you have entered an access group different end users
Shows how records have been added to the access group folder JOB-RECORDS.- Adding Records:- Query Security Icons Icon Name Description Add Sibling Add a sibling folder Add Child Add a child folder Add Record Add a record to the folder Delete Node Delete the folder or record Cut Cut the folder or record and then it can be pasted to another node Edit Data Edit information for the access illustration shows an example of how a query tree with multiple group folder or record description folders and records may lookDo not include the PS prefix; if you want PS_JOB, you just specify JOB.Click Add when finished
Permissions:- For your end users to be able to have access to run queries and utilize the records in your tree, a permission list should be createdDevelop a strategy on how you will manage your Query Security.A hierarchy might be by module and permissions, such as AP MANAGER, AP CLERK, PAYROLL MANAGER, PAYROLL CLERK, etc Navigate :- People Tools -> Security -> Permission And Roles -> Permission List to create the permission list. - Component Permissions - Enter a name for the permission list and click Add This page allows you to give certain access to your end user Query_Admin This page allows for viewing of all queries Query Manager This page allows the creation and running of queries Query Viewer This page will only allow the end user to run queries they have access to Sched_Query This page allows for the scheduling of queries Sched_Query_Qryvw This page will allow the end user to view only the scheduled queries that they have access to
Select Access Group Permission link.:- This page is to add the trees and the access group that this permission list will include. One tree can contain many access groups. Each access group can be selected in the permission list.To save your permission list, click OK. Attach it to a role that the end user currently illustration shows the page. On this page youuses or create a new role. can force certain attributes on the queries that the end users can run. You can set parameters on how the query can be used and how it is outputted. For end users that will be able to create queries, advanced SQL options can be set. These SQL options are provided to prevent runaway queries. Unfortunately these don’t completely prevent runaway queries, so additional measures are needed. Two such additional measures are Turning on the Query Monitor option. Doing additional work at the database level. Since PeopleSoft is “database agnostic,” each database has its own ways of preventing runaway SQL.
Step-2 Query Process Overview Tree and permissions set up, you can create your first query. First you need to determine what kind of query your end user is requesting,how it will be used, and what information you require to produce the query. Query Types - Six Different Types of Queries:- Links and Icons Within Query Manager User Query - Retrieve data from the database. Reporting Query- Same User Query, except Designed used with other Reporting Tools - Crystal Reports, PS/nVision, Cube Manager, and XML Publisher. Process Query - A batch query used Application Engine and the Query API. Role Query - Used with workflow, to determine who should receive e-mails or work list entry. This query returns a list of roles. Archive Query- Used by PS Archive Manager for archiving. PS/nVision Query- Creates a specific data source for PS/nVision reports and matrix layouts. Query Steps -Seven Major Parts to Creating Query:- - Select Records Data is stored in records (tables). - Select Fields Identify the fields from the records that are needed in the query. - Using expression (optional) Expressions are new fields - fields not in records, fields combined into one field, or fields aggregate functions (for example, sums, counts). - Using prompts (optional) Requesting input from the end user (for example, Date range). - Selection criteria (optional) Applying criteria to the data selected to reduce the data returned from the database - Having criteria (optional) Another type of selection criteria, used when the field you are checking is an aggregate value (for example, only pull departments with more than five employees). - Run Query View the results of the query.
Step-3 Creating New Queries Step-2 Selecting Records - Select the Existing Record NameStep-1 Create a New Query Step-3 Select Join Type and then record to join with JOBCODE_TBL Step-4 Auto Join Criteria see screen shot
Step-5 Fields - After Auto Join Criteria selected Step-6 Fields - Selected fields in Fields Page butand review the Query page and select the field not order by Clicking Reorder/Sortrequired to display in report.Step-7 Reorder/Sort - Reorder you want display Step-8 Edit Field Properties - To edit the heading orfields in the Report . field name or to create an aggregate from this field. Select any one Aggregate - None, Sum, Count, Min, Max and Average
Step-10 Expressions - Determine the Expression Type, Length, and Step-9 Expressions – Click Add Expression Decimals setting. Enter Function Expression Test: A.Company || - || A.Paygroup Round(A.Annual_rate + B.Bonus,2)Step-11 Expressions – Redetermine the Expression Type, Length, and Step-12 Prompts – Click Add Prompts to make your query moreDecimals setting from Edit option dynamic, you may want to request information from the endEnter Function Expression Test: A.Company || - || A.PaygroupRound(A.Annual_rate + B.Bonus,2)
Step-13 Prompts – Edit Prompt Properties page define Field Step-14 Prompts – Select a field name by using the Lookup andname, Type, length and etc. selected field you want to use as a promptStep-15 Prompts – attributes were set up when the field Step-16 Prompts - Prompt page. Your new prompt will now becreated within People Tools . If you want Redefine /change listed. To edit the prompt, click Edit; this will return you to thethe selected field from Edit prompt properties. Edit Prompt Properties Three types of Edit Types: - No Table Edit, - Prompt Table and - Translate Table
Step-17 Criteria - Criteria are equivalent to the where clause in Step-18 Edit Criteria Properties - To add new criteria, click the Addan SQL statement. To subset your data, click the Criteria tab. Criteria button. This will take you to the Edit Criteria PropertiesStep-19 Criteria Select Expression - Select the Expression 1 Type. Step-20 Criteria Properties Settings - Once you are done settingIf a field is selected, Lookup icon Expression 1 box to get a list of up your criteria properties, click OK to return to the Criteriafields available for selection
There are 16 available Conditions (Condition type selected will determine what information is needed for the Expression 2 box)Between - This will check if the value of Expression 1 is between two other values. Inthe Expression 2 box you will have to give these two values. This works well with fields, Less than - This will check if Expression 1 is less than Expression 2. This works well withexpressions, and prompts. all Expression 2 types.Does not exist - This will check if Expression 1 exists in the Expression 2 value. This is Like - This will check if Expression 1 is like Expression 2. You use the wildcard ‘%’ to addgood to use with subqueries. on to partial constants.Equal - This will check if Expression 1 equals Expression 2. This works well with all Not between - This will check if the value of Expression 1 is not between two otherExpression 2 types. values. In the Expression 2 box you will have to give these two values. Works well with fields, expressions, and prompts.Exists - This will check if Expression 1 exists in the Expression 2 value. This is good touse with subqueries. Not equal to - This will check if Expression 1 does not equal Expression 2. This works well with all Expression 2 types.Greater than - This will check if Expression 1 is greater than Expression 2. This workswell with all Expression 2 types. Not greater than - This will check if Expression 1 is not greater than Expression 2. Same as less than or equal to. This works well with all Expression 2 types.In list - This will check if Expression 1 equals one of the values in the list for Expression2. This works well with all Expression 2 types. If a constant is given, it will allow you to Not in list - This will check if Expression 1 does not equal one of the values in the list forbuild a list. Expression 2. This works well with all Expression 2 types. If a constant is given, it will allow you to build a list.In tree - Compares the value to a selected set of tree nodes, uses the Select Tree NodeList page to create the list. Not in tree - Compares to a selected set of tree nodes; uses the Select Tree Node List page to create the list that it should not be in.Is not null - This will check if Expression 1 is not null. Expression 2 is not available.Normally used with dates. Effective Seq - Used with effective-dated records.Is null - This will check if Expression 1 is null. Expression 2 is not available. Normallyused with dates. After the condition type has been created, select from the Expression 2 Type. You have more choices here:- Field-This is a field within one of the records you have included in the query. Expression-This is an expression you created in the Expression tab. Constant-This is any value you key. Prompt-This is a prompt that you can create at this time, using the lookup icon or selecting one that you have already created from the prompt page. A list of prompts will be provided if you select the prompt number. Subquery-This allows you to create another query to use as validation within your current query. It will be shown in the Advanced Query topics.
Step-21 Group Criteria – Edit Group Criteria Step-22 Reorder Criteria – Since criteria can be added from multiple pages of the Query ManagerStep-23 Saving– Before we test our Query Step-24 Previewing – Now it is time to test your Query
Step-25 Run a Query from Run Page – Query Report output/ results can Download to Excel or Pdf file
Step-4 Advanced - View SQL, Subquery, Having and New UnionStep-26 Review SQL Query – from SQL query view page can Step-27 Subquery - Select field and choose expression 2 Type -Subqueryview the SQL query Statement Step-28 Subquery -Edit Expression Properties – define Expression Function
Step-28 Having - Edit Having Criteria Properties – Step-29 Having - Edit Having Criteria PropertiesDefine Expression Function condition Type Step-30 Run Query using Having function condition
Step-5 Scheduling Step-31 Schedule Query – Define Schedule Run the Query with Parameters eg- from start date to End date.
Step-6 Query Viewer Step-32 Query Viewer – From Query Viewer you enter /search the Query Name and Run the Report
Step-7 Query Tables Sl no. Query Table Query Table Description 1 PSQRYFIELD Stores all fields used in all aspects of query operation. 2 Stores high-level query definitions with version numbers. Non-English definitions are stored in PSQRYDEFN PSQRYDEFNLANG and PSQRYHEADLANG. 3 PSQRYRECORD Stores all records used in all aspects of query creation. 4 Stores all SELECT requirements by select type, including PSQRYSELECT union, sub select, join. 5 PSQRYCRITERIA Stores all criteria expressions in code format. 6 PSQRYBIND Stores runtime prompt data. 7 PSQRYEXPR Stores the text associated with each criteria expression. 8 PSQRYLINK Stores the relationships to child queries.