Query. Training and Participation Guide Financials 9.2

Query Training and Participation Guide Financials 9.2

Contents Overview... 4 Objectives... 5 Types of Queries... 6 Query Terminology... 6 Roles and Security... 7 Choosing a Reporting Tool... 8 Working With Existing Queries... 9 Searching for and Running an Existing Query in Viewer... 9 Running a Query Via Schedule... 12 Saving an Existing Query as Private... 16 Creating Queries... 18 Creating a New Query... 18 Review Tabs... 21 Selecting Records... 21 Changing Column and Sort Order for Multiple Fields... 25 Editing Field Properties... 26 Changing Field Labels... 27 Previewing Query Results... 28 Defining Selection Criteria... 29 Criteria View... 29 Selecting Condition Types... 31 Entering Comparison Values... 36 Understanding Effective Dates... 37 Specifying Effective Date Criteria... 37 Adding Run-Time Prompts... 39 Organizing Queries... 41 Adding Queries to the My Favorite Queries List... 41 Copying a Query to Another User s List of Queries... 42 Moving a Query to an Organization Folder... 43 Renaming a Query... 44 Working with Multiple Tables... 45 Adding and Joining Multiple Records to a Query... 45 2

Record Hierarchy Join... 46 Related Record Join... 47 Any Record Join... 48 Left Outer Join... 50 Additional Query Options... 52 Aggregate Functions in Query... 52 Applying Aggregate Functions to Fields... 53 Relating Multiple Criteria... 54 Using AND OR Logical Operators... 54 Advanced Query... 55 Having Criteria... 55 Unions... 55 Sub Queries... 55 APPENDIX... 56 Frequently Used Records... 56 Useful Queries by Module... 65 3

Overview This class will introduce you to the PeopleSoft Query tool. You will learn the basic functions of Query and how to create a simple query including selecting a record, selecting specific fields, modifying column headings and how to retrieve the short or long description for a translate value, rather than the code. Once you know the basics, you will learn how to modify and retrieve information based on criteria requirements such as equal to, greater than, in list, between and like. You will also be introduced to runtime prompts. Runtime prompts give you the ability to enter specific values for a designated field. These values are then used as criteria for retrieving the information for your report. The main reason you store your business data in a database is so you can manipulate it to answer questions and solve business problems. However, getting just the information you're looking for can often be a difficult and time-consuming process. With PeopleSoft Query, you can extract the precise data you want using visual representations of your PeopleSoft database, without having to write SQL statements. The queries can be as simple or as complex as necessary, and they can be one-time ad-hoc queries or queries you'll use repeatedly. This manual explains the basic concepts of selecting data, designing simple and complex queries, and sending query results to other reporting tools. To take full advantage of the information covered in this book, users should have a basic understanding of how to use PeopleSoft applications. We recommend that you complete at least one PeopleSoft introductory training course. You should be familiar with navigating the system and adding, updating, and deleting information by using PeopleSoft windows, menus, and pages.

Objectives The objectives of this manual are for you to be able to: Recall the Navigation steps to Query Use Query Viewer to search, save, and/or schedule queries Create a query from scratch Save as Private Use Query Manager to Edit an existing query o Reorder, rename, and sort o Add Records, Prompts, and Criteria o Select fields Understand the functionality of Hierarchy Joins (outer) 5

Types of Queries PeopleSoft Query provides the following different types of queries: User queries. Create and run queries to retrieve data from the database directly from Windows-based Query Designer, or the web-based Query Manager/Query Viewer applications. These are the queries that will be discussed in this class. Reporting queries. Reporting queries are essentially the same as user queries, except that they are designed to be used by another reporting tool. Reporting queries can be used as data sources for reports, PS/nVision, or Cube Manager. Process queries. Write queries that are intended to run periodically by batch processes, most likely using PeopleSoft Application Engine and the Query API (application programming interface). Query Terminology Record Definitions: The record definitions are the design specifications that determine the structure of your PeopleSoft application data tables and online processing. In the PeopleSoft database, tables are represented as record definitions. In PeopleSoft Query, tables are also called records. Tables: The table is made up of columns (Fields) and rows (Data). Columns determine how the data will be stored. Rows represent the actual data stored in the database. SetID: Code that is used to group and share configuration data across the application. For example at FIU, we create most of our control records (i.e. Accounts, Department ID, Activity #) under SetID FIU01 and it allows the entire university to use those values. Control vs. Transactional Data Control data represents the configuration values which are agreed on and shared across the enterprise. Information that is key to the operation of a business that does not change very often. Transaction data are data describing an event (the change as a result of a transaction) and is usually described with verbs. Transaction data always has a time dimension, a numerical value and refers to one or more objects. Changes frequently. Run Control: When running a report, you must enter the parameters from which the report will be run, and eventually display data for you to view. To aid in running reports, PeopleSoft created a means to allow the user to save search parameters so he/she does not have to perform the same steps each time the report is requested. Run Control ID's are how PeopleSoft identifies saved search parameters for reports or processes. 6

Roles and Security There are several types of users that will use query functionality. There are Query Super Users who are a specific set of users that develop queries within PeopleSoft for the user community. They have the ability to save Public queries that can be accessed by any user. Then there are Query Viewers who only have the ability to run public queries but cannot develop or modify queries. Users have access to data based on security settings within Panthersoft. Any user with Query Manager Access may save a Public query as Private under a different name. 7

Choosing a Reporting Tool Here are some guidelines to consider when determining which interface to display your results. Reporting Tool HTML Description & Guidelines Online ad hoc reporting tool. Create and run queries to retrieve data from the database directly from the web-based Query Manager/Query Viewer applications. This option is useful as you refine your queries. Results display on the screen within PS. Excel Query-to-Excel Interface provides the ability to send queries from Query to a Microsoft Excel spreadsheet. Your data is sent directly from your query into a predefined spreadsheet layout. This way you can spend your time analyzing results, not typing data into your spreadsheet Use a spreadsheet to: Generate output for further analysis. Create charts or graphs of the data. Work with data in a spreadsheet format. Quickly display an ad hoc query answer with default formats. XML Schedule Not used at FIU You can choose to schedule queries so that they run in the background as opposed to your desktop. This is helpful if your query is taking too long to run or returns too many rows of data. The results of scheduled queries are routed to PeopleSoft Report Manager 8

Working With Existing Queries In Query Viewer and Query Manager, the user can run a query to different interfaces, schedule a query for future use, and save that query to favorites for faster retrieval. Searching for and Running an Existing Query in Viewer 1. If you know the Query Name, enter it in the Search Box. If not, click on Advanced Search to filter your results. Note: When using, the IN or BETWEEN operators, enter comma separated values without quotes. I.e. JOB, EMPLOYEE 9

Field Query Name Description Users Record Name* Uses Field Name* Access Group Name Folder Name Query Type Owner Description Enter the name of the query. Enter a description or partial description of the query. Enter the record with which the query is associated. Enter a field that the query uses. Enter the access group with which the query is associated. Enter the name of the folder that stores the query. Enter the query types: Role, User, Process, or Archive Enter whether the query is public or private. Below is a screen shot when entering just EX_ER in the Query Name search box. Run To options: a. Run to HTML displays the query results on your screen. b. Run to Excel displays the result in an excel spreadsheet. c. Run to XML, we do not use at FIU. 10

Please search for the Query entitled FIU_FSSS_TA_QUEUE and click HTML. When you click, HTML you might have to enter a prompt. Prompts are other information needed to narrow down the search. For instance, when performing a search to see whose approval queue a Travel Authorization may be in, that query prompts you to enter the TA#, to narrow the results down to that specific authorization. In the below example, the FIU_FSSS_TA_QUEUE requires a TA# as a prompt. Clicking HTML displays the results on your screen. RESULTS 11

Running a Query Via Schedule Running a Query via schedule allows you to capitalize on having the query process in the background, while you perform other tasks. 1. From the Query Viewer screen, Click on Schedule. 2. Name the Run Control ID The Run-Control ID is the save name for the search parameters you have selected; something that briefly explains what the query does. Once you name your query, when choosing schedule in the future, you will not have to enter the Run-Control ID again. 12

3. Write a Description of what the query does. For this example, name it Vendors List. 4. Click Apply 5. Choose PSUNX server 6. Enter the dates you would like the query to run. 7. Choose Run Date 8. Choose Type, Format, and Distribution (WEB, TXT are your standards) 9. Click OK 13

The query will then run in the background at its scheduled date and time. Do not set recurrences for queries until you have successfully completed Query Manager Advanced Query. Navigate to Process Monitor to view the results of your query. People Tools Process Scheduler Process Monitor NAVIGATION You can click the Refresh button to update the status when the query is running. The query has finished running when the Run Status is Successful and the Distribution Status is Posted. 1. Click on Details. 14

2. Click View Log/Trace 3. Click the.csv file and open it in Excel to view the results of the query. 15

Saving an Existing Query as Private In Query Viewer or Manager, you can take an existing Public query and save it for yourself and to make edits/adjustments. To save a query via Query Viewer: 1. After retrieving the Query, click edit to view the Save options at the bottom of the screen. 2. Click Save As to save a copy of the query. 3. In the Query box, enter a short name for the query (NOTE: query names should begin with FIU_; cannot have spaces. Use underscores _) 4. In the Description field, enter information that will help you to later identify the query. 5. Create or Select a Folder to file saved queries. 6. Select a Query Type. Standard queries are designated as User queries. The Archive, Process, or Role options apply to Workflow queries. NOTE: Workflow (which essentially allows you to route information to another user) is not currently implemented by FIU, so select the default option User. 7. In the Owner field, select Private. a. Private means that only the user ID that created the query can open, run, modify or delete the query. b. Public means that any user with access to the records used by the query can run, modify, or delete the query. NOTE: The ability to save a query as public will vary depending on your level of security. 8. Enter the Query Definition which can be a long description. Note: Using Save As creates another instance of the query that you can modify and save under a different name. When you select Save As, the Properties page appears, enabling you to change the name, description, and owner of the new query. You cannot save a public and a private query with the same name. Going forward, all queries must begin with a prefix of FIU_ followed by any other descriptive values (keeping in mind that a maximum of 30 characters is allowed). 16

To save a Query via Query Manager: 1. After you make your changes in Query Manager, select Save As. 2. In the Query box, enter a short name for the query (NOTE: query names should begin with FIU_; cannot have spaces. Use underscores _) 3. In the Description field, enter information that will help you to later identify the query. 4. Select a Query Type. Standard queries are designated as User queries. The Archive, Process, or Role options apply to Workflow queries. NOTE: Workflow (which essentially allows you to route information to another user) is not currently implemented by FIU, so select the default option User. 5. In the Owner field, select Private. Private means that only the user ID that created the query can open, run, modify or delete the query. Public means that any user with access to the records used by the query can run, modify, or delete the query. NOTE: The ability to save a query as public will vary depending on your level of security. 6. Enter the Query Definition which can be a long description. Note: Using Save As creates another instance of the query that you can modify and save under a different name. When you select Save As, the Properties page appears, enabling you to change the name, description, and owner of the new query. You cannot save a public and a private query with the same name. Going forward, all queries must begin with a prefix of FIU_ followed by any other descriptive values (keeping in mind that a maximum of 30 characters is allowed). 17

Creating Queries The ability to create/modify/ is done using Query Manager, whereas the ability to run/schedule/view pre-defined queries is done through Query Viewer. When creating a query, user must navigate to Query Manager in the Reporting Database. Creating a New Query 1. Navigate to the Reporting Database first. We ask all users to run their queries in the Reporting Database as to not affect Production. Information in the Reporting database is a production day behind. So if you are trying to run a query on, for example, Wednesday morning, you will be using information from Monday. The last completed day of production. Reporting Tools NAVIGATION Reporting Database Look for this to indicate that you are in the Reporting Database. 18

2. Another window pops up to navigate to the Query menu. Choose Query Manager Query Query Manager NAVIGATION The Query Manager Search page appears. 3. Click the Create New Query link to open the Find an Existing Record search page. 19

20

Review Tabs Records allows you to add records to the query via query manager Query Manual 9.2 Query Tab Shows you which records are already selected for this particular query. Expressions advanced Prompts allows user to add, edit prompts Fields allows you to select/deselect or edit fields within a record Criteria allows you to edit, view the search criteria Having advanced View SQl advanced Run- runs the query according to set parameters. Selecting Records All queries are built off records/tables, fields and data in those fields. Running a query asks the system to search the database for an answer. The database is comprised of records (tables), fields (columns), key fields, and field data (rows). The results you generate in a query will depend on the records (tables) selected. If you are unsure of a table to use see Appendix in back of this manual, or send an email to controller@fiu.edu. Example of a Table - EX_TAUTH_HDR - Travel Authorization Header Table EX_TAUTH_HDR RECORD FIELDS TRAVEL_AUTH_ID EMPLID TRAVEL_AUTH_STATUS SUBMISSION_DATE Field Data 11111 1234567 APPROVED 10/1/2014 Field Data 22222 7654321 PENDING 10/15/2014 Fields (columns) store single pieces of information for each row. (TRAVEL_AUTH_ID is a field.) Rows (data in the field) contain all the information for a unique combination of key values on the table. TA#11111 is the data in the field. For example, in the EX_TAUTH_HDR a row includes the data for these fields: TRAVEL_AUTH_ID, EMPLID, TRAVEL_AUTH_STATUS, and SUBMISSION_DATE. 21

Within these records are key fields. Key fields are unique to the record. Every record has a key field. The Key Fields for the EX_TAUTH_HDR table are Employee ID, and TA#. No employee or Travel Authorization has the same number. This information is what the query is looking at to retrieve your answer If you know the name of the record you want, enter it in the Search By box on the Find Existing Record page, and click the Search button. If you want to search for a record, leave the field blank and click the Search button to display a list of up to 300 records. By default, only the first 20 records appear on the page. To see more of the list, use the navigation buttons and links located on the header bar. To display all of the records, select the View All link, and use the scrollbar to go through the rest of the list. Helpful Search Hints Perform a partial search by entering part of a record name or description in the Search For field. Search records either by name or description, then further define your search by choosing either a begins with or a contains search type. Click the Search button to display a list of records that match your search criteria. Enter the name of the required record in the Search For box, and then click the Search button. For example: Enter the word SPEED to search for the Speed Type Table Query Manager will display the record(s) at the bottom of the page. 22

Click Add Record nest to SPEEDTYP_TBL to select the record (i.e. place it in the Query Tab) NOTE: The Show Fields link will display a list of all the fields in the record available for selection. Query Name New Unsaved Query appears in this read-only field until you change it on the Properties page. This field appears on all of the Create New Query pages. Click the Sort button once to list fields in alphabetical order. Click the button again to return to original sort. Alias Record The alias name that the system automatically assigns to the chosen records. 23

Click the Folder button to view the fields for the chosen record. Query Manager expands the record so that you can see the fields and make sure that this record has the content that you want. Click the Folder button again to hide the fields for a record. Click this link to join a child table to its parent table. Click the Delete button to delete the associated record from the query. Click this button to check all fields in the record. Once you select a field, the system automatically adds it to the query and you can view it on the Fields page. Click this button to clear all fields in the record. Fields Select the box located to the left of each field that you want to add to your query content. Indicates key fields. Related Record Join Click this link to join two records based on a shared field. For example, in the above screenshot, the SPEEDTYP_TBL record is related to the GL_ACCOUNT_TBL record by the ACCOUNT field. Click the Use as Criteria button to open the Criteria page, where you can add criteria for the selected field. 24

Changing Column and Sort Order for Multiple Fields Query Manual 9.2 Access the Edit Field Column Order page by clicking the Fields page. button on the Column Order Sort Order Direction Enter new column number to reorder columns. Columns left blank are automatically assigned a number. You cannot use the same number on multiple fields. Enter the desired sort order. Enter zero to remove a sort order. If the field is the first sort field, enter 1, and the system sorts rows based on this field first. To be the second sort field, enter 2, and so on. Select Descending to sort fields in descending order or leave blank for Ascending 25

Editing Field Properties Access the Edit Field Properties page by clicking the next to the desired field you would like to edit. button on the Fields page The below screen appears. Heading Unique Field Name Aggregate None Choose a column heading from the following: No Heading: The column does not have a heading. Text: The column heading is the text you ve entered in the text box. RFT Short: The column heading is the short name from the record definition. RFT Long: The column heading is the long name from the record definition. Used for translations. There is no need to change the default value, which is a single-letter alias for the record followed with the record field name (for example A.NAME or B.EMPLID). If you are using aggregate values, select the aggregate function value for this field. An aggregate function is a special type of operator that returns a single value based on multiple rows of data. When your query includes one or more aggregate functions, PeopleSoft Query collects related rows and displays a single row that summarizes their contents. Will not use aggregate functions. 26

Sum Count Min (minimum) Max (maximum) Average Adds the values from each row and displays the total. Counts the number of rows. Checks the value from each row and returns the lowest one. Checks the value from each row and returns the highest one. Adds the values from each row and divides the result by the number of rows. Changing Field Labels When you add a field to your query, the default name will be displayed in your results when you run it. To change the name of the field displayed in your query: 1. In Query Manager, click the Fields tab. 2. Click the button associated with the appropriate field. The Edit Field Properties page appears. 3. Over-write the value in the Heading text box and click OK. Once the query is run, the value entered above will be displayed in your query results. 27

Previewing Query Results Click on the Run Tab to access the query results. View All Rerun Query Download to Excel Click this link to view all rows and use scroll bar to navigate. Click this link to rerun your query in the preview pane. If you have made changes to your query since the last preview, you must rerun the query to see the effect of your changes. Click this link to download your query to Excel. 28

Defining Selection Criteria In this chapter, you will learn how to add criteria clauses to a query to return specific rows of data. Within these criteria clauses, you will learn how to compare fields to find data of equal values, values greater or less than the field, values in a list, values in a range, and much more. You will also learn how to use effective dates when specifying criteria. Criteria View In most cases, you don't want to retrieve every row of data in a table. Your database contains a lot of information, and a complete list of entries is unlikely to answer the question that's motivating you to write a query. To selectively retrieve just the data you want, define selection criteria. Selection criteria refine your query by specifying conditions that the retrieved data must meet. Define selection criteria using the Criteria Tab 29

To create criteria based on a field: 1. Click the Add Criteria icon next to the desired field, on the Fields or Query page. Query Manager opens the Edit Criteria Properties page with the selected field entered as Expression 1. 2. Specify the criteria for that field, and then click OK to return to the Fields or Query page. 30

Selecting Condition Types The condition type determines how Query Manager compares the values of the first (left-hand) expression to the second (right-hand) expression. The following table describes the available condition types. For each of the condition types, Query Manager offers a not option that reverses its effect. For example, not equal to returns all rows that equal to would not return. Condition Types between equal to exists greater than in list in tree is null less than like When It Returns a Row The value in the selected record field falls between two comparison values. The range is inclusive. The value in the selected record field exactly matches the comparison value. This condition is different from the others, in that it doesn t compare a record field to the comparison value. The comparison value is a subquery. If the subquery returns any data, PeopleSoft Query returns the corresponding row. The value in the record field is greater than the comparison value. The value in the selected record field matches one of the comparison values in a list. The value in the selected record field appears as a node in a tree created with PeopleSoft Tree Manager. The comparison value for this condition is a tree or branch of a tree that you want PeopleSoft Query to search. The selected record field doesn t have a value in it. You don t specify a comparison value for this condition. Key fields, required fields, character fields, and numeric fields do not allow null values. The value in the record field is less than the comparison value. The value in the selected field matches a specified string pattern. The comparison value may be a string that contains wildcard characters. The wildcard characters that PeopleSoft Query recognizes are % and _. % matches any string of zero or more characters. For example, C% matches any string starting with C, including C alone. _ matches any single character. For example, _ones matches any five-character string ending with ones, such as Jones or Cones. 31

In List The In List condition finds fields having a value that matches any one of the values in a list of values. With this option, you are prompted to create a list with the Edit List dialog box. 32

To build a list of values: 1. For each value you want to add, manually enter a value in the Value text box and click the button. The List Member grid, containing the selected value, appears when a value is selected. 2. To select from a list of values, click the button to display the Select a Constant page. Click the Lookup button to display the Look Up page. Enter part of a value in the text box. The system automatically adds a wildcard to the end of the entry, which enables you to do a partial search. 33

3. To delete a value, select the check box to the left of the appropriate List In Tree Members value and click the button. The In Tree condition type enables you to specify a tree, and within the tree, the nodes containing specific values. In Tree is used to return the records that match, or appear underneath the specified tree. Trees are used to create hierarchical structures that visually represent a set of summarization rules for a particular field. For example, a tree specifies how your manufacturing locations are summarized or rolled up for reporting purposes. Similarly, a tree shows the reporting relationships within an organization by specifying, for example, how individual departments are summarized into territories, territories into regions, and regions into countries. The summarization rules depicted in a tree apply to the detail values of a particular field departments, vendors, customers, or other values you define. These detail values are summarized into nodes on the tree. The nodes may also be organized into levels to logically group nodes that represent the same type of information or level of summarization. Some of the most commonly used trees by FIU are: ACCOUNTROLLUP ACTIVITY_HIERARCHY DEPT_ROLLUP STUFINANCIALS Student Financials in Campus Solutions Click the New Node List link in the Criteria Dialog Box to display the Select Tree page. 34

Click on Search or type in the Tree name. Only trees to which you have access are listed. Click the name of the desired tree to display the Display and Select TreeNodes page. To select tree nodes: 1. Highlight the desired tree node, and click the Add Node icon. 2. If you know the name of the desired node, enter the name of the desired node in the Manual Selection list box. 3. Remove nodes from the list by clicking the corresponding icon. 4. Display the selected tree branch by clicking the corresponding icon. This is applicable only when the tree has been branched. 5. Click OK. The selected tree SetID, tree name, effective date, and selected nodes appear in the Select Tree dialog box. 35

Entering Comparison Values The procedure for entering comparison values differs depending on what kind of value you re entering. If you re comparing one field to another, pick the second record field; if you re comparing the rows to a constant value, enter the constant. The following table describes all the available value types, the dialog boxes that appear based on each comparison type, and the fields you must complete in those dialog boxes. Value Type Field Expression Constant Subquery Prompt Action The value in the selected field is compared to the value in another field, usually a field in another record component. When you ve selected Field as the comparison value, the Select Field dialog box appears. The Record Alias field lists all the records that are part of the current query. Select the record and the field. The selected field name appears in the second Expression column of that field s row. The value in the selected field is compared to an expression you enter, which PeopleSoft Query evaluates once for each row before comparing the result to the value in the selected field. When you ve selected Expression as the comparison value, the Edit Expression dialog box appears. In the text box, enter a valid SQL expression. To add a field or user prompt to the expression, click the Add Prompt link or the Add Field link. These links display the same dialog boxes that you see when adding a field or prompt as a comparison value: the Add Prompt displays the Run-time Prompt dialog box; the Add Field link displays the Select Field dialog box. The only difference is that PeopleSoft Query adds the field or prompt to your expression rather than using it directly as the comparison value. The value in the selected field is compared to a single fixed value. When you select Constant as the comparison value the Edit Constant Value dialog box appears. In the text box, enter the value you want to compare to the first expression. The value in the selected field is compared to the data returned by a subquery. When you select Subquery as the comparison value, the Define Subquery dialog box appears. Click the Define/Edit Subquery link to move to the Records tab to start a new query. The value in the selected field is compared to a value that you enter when running the query. When you select Prompt as the comparison value, the Define Prompt dialog box appears. Click the New Prompt link to move to the Edit Prompt Properties page. 36

Understanding Effective Dates When you update existing information, you do not want to lose or overwrite the data already stored in the database. To retain history, you can add a new data row identified by the date when the information goes into effect: an effective date. Effective dates allow you to keep history, current, and future information in tables. The system categorizes effective-dated rows into three basic types: Future Current History Data rows that have effective dates greater than the system date usually today s date. There can be more than one. The data row with the greatest effective date less than or equal to today s (system) date. Only one row is the current row. Data rows that have effective dates less than the effective date of the current data row. There can be more than one. Specifying Effective Date Criteria Effective-dated tables have record definitions that include the Effective Date (EFFDT) field. This field, used throughout the PeopleSoft applications, provides a historical perspective, allowing you to see how the data has changed over time. Whenever a row of data is added to the table, you specify the date on which that data becomes effective; whenever a row of data is changed, you specify a new effective date, and the system retains the previous version of the row as history. When you re using a PeopleSoft application for day-to-day processing, you usually want the system to give you the currently effective rows of data the row where the effective date is less than or equal to today s date. You don t want to see the historic rows, which are no longer accurate, nor do you want to see future-dated rows, which aren t yet in effect. When you re querying an effective-dated table, though, you may well want to see some rows that aren t currently in effect. You might want to see all the rows, regardless of their effective dates. Alternatively, you might want to see the rows that were effective as of some date in the past. 37

To specify effective date criteria: 1. When you choose the record that has EFFDT as a key field, Query Manager automatically creates default criteria and adds that criteria to the Criteria page. These criteria are used to specify which row of data PeopleSoft Query retrieves for each item in the table. The default is the currently effective row. Defaults are as follows: Expression 1 Condition Type EffDt <= Expression 2 Effective Sequence Record Alias.EFFDT Current Date 2. If you choose one of the comparison options, choose to compare each row s effective date against today s date or a date other than today. Last Select Current Date to compare each row s effective date against today s date. Select Constant to display the Constant box so that you can enter a date. Select this option when you want to see the rows that were effective as of a past date or that will be effective on some future date. Select Expression to display the Edit Expression box so that you can enter a SQL expression that evaluates the date entered. Select this option if you want to prompt users for an effective date when they run the query. You can add a prompt to the expression you define in the Edit Expression box. Select Field to display the Select Field box so that you can select the record field that holds the date to which you want to compare effective dates. Select this option when you want to see the rows that were effective at the same time as some other record. For example, if you re reviewing the list of products on a customer order, you ll want to see the products that were effective on the date of the order. Select First Effective Date to return the row with the oldest effective date, usually the first row entered for an item. Select Last Effective Date to return the row with the latest effective date, even if that date is still in the future. Select No Effective Date to return all rows, regardless of their effective dates. 38

Note: All options (except No Effective Date) return a single row for each item on the table. If you want a subset of the rows (say, all future-dated rows or all history rows), select No Effective Date, then enter a selection criterion on the Effective Date field. Use the standard comparison operators rather than the Effective Date comparison operators. Keep in mind that the effective date operators work differently than the standard comparison operators: they always return a single effective-dated row. For example, Eff Date <= returns the one row whose EFFDT value is most recent, whereas not greater than would return the currently active row and all history rows. Adding Run-Time Prompts A run-time prompt allows you to enter values for a specific field at the time the report is executed. The report will display only those rows of information that match the value entered at the prompt. Prompts make reports more flexible. Prompt reports can be used by different departments, or individuals within the same department with different responsibilities. To define prompts: 1. Click the Add Criteria icon associated with the required field, on the Fields or Query page. Query Manager opens the Edit Criteria Properties page with the selected field entered as Expression 1. 2. From the Choose Expression 2 Type box, select Prompt. 3. In the Define Prompt box, click the New Prompt link The Edit Prompt Properties page will appear. 39

After you select a prompt field, the name of the field appears. PeopleSoft Query looks to the record definition for information about this field and completes the rest of the dialog box based on its properties. Heading Type RFT Long The long field name from the Record Editor. RFT Short The short field name from the Record Editor. Text Anything you want - you make up the label. Heading Text Unique Prompt Name Edit Type Displays the label for the text box where you enter the comparison value. To change the text, select Text from the Heading Type list box, then enter the new label in the Heading Text box. A default value generated by Query Manager for globalization. Defines the type of field edit for the specified field. Prompt Table If the edit type is Prompt Table, the value in the Field list box specifies the prompt table to use. If the edit type is Translate Table, the value in the list box determines the values used. Adding a prompt allows you to further refine a query when you run it. When you run a query with a prompt, a dialog box appears for you to specify the required value. Enter the value into the text box. 40

Organizing Queries Adding Queries to the My Favorite Queries List If you use certain queries often, you can put them in your My Favorite Queries list for easy access. This option is available through Query Manager as well as Query Viewer. To add a query to the My Favorite Queries list: 1. On the Query Manager Search Results page, select the query that you want to add to the My Favorite Queries list (click the box to the left of the query). It will appear as follows: 2. Select Add to Favorites from the Action drop-down list box. 3. Click Go. The query appears in the My Favorite Queries list group box. 41

Copying a Query to Another User s List of Queries Query Manual 9.2 The Query Manager allows you to copy a query from your list of queries to another user's list of queries. You can only copy Private queries to another user's list of queries. If the target user does not have permission to access all of the records in a copied query, that query will not appear in the target user's list of queries. Once permission has been granted, the query will then appear in the list. Navigation: Main Menu>Reporting Tools>Query>Query Manager To copy a query to another user's list of queries: 1. On the Query Manager Search Results page, select the query or queries that you want to copy. 2. Select Copy to User from the Action drop-down list box. 3. Click Go. The Enter User ID dialog box appears. 4. Enter the user ID of the user to whom you would like to copy the query. 5. Click OK. You will receive a message indicating the query was successfully copied to the designated user 42

Moving a Query to an Organization Folder Folders enable you to organize queries under a common heading. To move a query to an organization folder: 1. On the Query Manager Search Results page, select the query or queries that you want to move to an organization folder. 2. Select Move to Folder from the Action drop-down list box. 3. Click Go. The Move to Folder dialog box appears. 4. Select one of the following: 5. Click OK. Select an existing folder to move to: Select the folder from the drop-down list box to which you would like to move the queries. OR enter a folder name to move to: Enter the name for a new folder to which you would like to move the queries. 43

Renaming a Query To rename an existing query, refer to the instructions below: 1. On the Query Manager Search Results page, select the query or queries that you want to rename. 2. Select Rename Selected from the Action drop-down list box. 3. Enter the desired name of the query in the New Name box 4. Click OK You will be taken back to the Query Manager page. 44

Working with Multiple Tables In many cases, the desired output data comes from at least two different tables. In these cases, you must link the tables together to retrieve the correct output. Adding and Joining Multiple Records to a Query PeopleSoft Query enables you to create queries that include multiple-table joins. Joins allow you to retrieve data from more than one underlying table, presenting the data as if it came from one. Whenever you perform a join, the records involved are linked based on common fields. The procedure for joining tables differs depending on how the tables being joined are related to each other. PeopleSoft Query recognizes four types of joins: Record Hierarchy Join, which joins a parent table to a child table. (A child table is a table that uses all the same key fields as its parent, plus one or more additional keys). Related Record Join, which joins records from non-hierarchical records that are related by common fields. For example, description tables for common codes are related records. Any Record Join, which joins any two tables in the database. Left Outer Join, which joins any two tables in the database similar to an Any Record Join. However, in a left outer join, all rows of the first (left) record are present in the result set, even if there are no matches in the joining record. In Query, predefined joins can be generated as a Record Hierarchy Join or a Related Record Join. Since these types of joins are predefined, you do not have to add any criteria to manually link the records. If you have the Auto Join Wizard option enabled in Query Preferences, then PeopleSoft Query automatically attempts to join the new record to the existing record by looking for matching columns on the two records when you do Any Record Join or Left Outer Join. 45

Record Hierarchy Join A record hierarchy joins a parent table to a child table. (A child table is a table that uses all the same key fields as its parent, plus one or more additional keys.) To create a record hierarchy join: 1. Choose the base record for your query and select the appropriate fields and criteria. 2. From the Query page, click the Hierarchy Join link. All of the records that have a parent/child relationship with your selected record appear. 3. Select the second record for the join. In our example, we are selecting JRNL_LN. The join is reflected on the Query page. At this point, you can select any field from either table into one query. 46

Related Record Join In a related record join, you join two tables based on a shared field that isn't necessarily a key field. For example, if a field has a prompt table defined for it, then PeopleSoft Query displays a join link to the right of the shared field. To create a related record join: 1. Choose the base record for your query and select the appropriate fields and criteria. 2. From the Query page, click the required Related Record Join link and select Standard Join The join is reflected on the Query page. 47

Any Record Join The Any Record Join is typically used when you already know the name of the tables you would like to join in your query. Using Query Manager, you can create a join between two records (tables) by selecting your initial base record, defining its output fields and associated criteria, and then returning to the Record page to select the second record. If you have Auto Join Wizard option enabled, then PeopleSoft Query automatically attempts to join the new record to the existing record by looking for matching columns on the two records. For example, the LEDGER table contains no related record for the Field Business Unit. If you wanted to join the Business Unit description table (BUS_UNIT_TBL_FS) to the LEDGER Table, then you would do so by creating an any record join. To create any record join: 1. Choose the base record for your query and select the appropriate fields and criteria. 2. Return to the Record page to select the second record. The Auto Join Wizard will attempt to join the new record to the existing record by finding matching fields between the two tables. The Join is reflected on the Query page 48

49

Left Outer Join PeopleSoft Query enables you to easily create a left outer join. In a left outer join, all rows of the first (left) record are present in the result set, even if there are no matches in the joining record. This essentially allows you to retain the integrity of the data from the first table though none of those records exist in the secondary tables in your join. Unlike any of the other three joins, a left outer join will not filter any rows when the query is run. To create left outer joins: 1. Choose the base record for your query and select the appropriate fields and criteria. 2. Return to the Record page to select the second record. Also, you can select a Related Record Join Link. The Auto Join Wizard will attempt to join the new record to the existing record by finding matching fields between the two tables. 3. Click the Join Record link on the same row as the joining record. 4. Select Join to get additional fields only (Left outer join). If the Enable Auto Join preference is selected, click the record name to join with. 50

The join is reflected on the Query page. 51

Additional Query Options You will learn how to use aggregate functions in a query. Instead of returning many rows of data, perhaps you are only interested in a count of rows or a sum of a numeric field. In addition, you ll learn how to specify Having Criteria on aggregate functions. You will learn how to set-up runtime prompts. You will learn how to use logical operators when specifying criteria, and grouping it with parentheses. Aggregate Functions in Query An aggregate function is a special type of operator that returns a single value based on multiple rows of data. When your query includes one or more aggregate functions, Query collects together related rows and displays a single row that summarizes their contents. For example, suppose you have an Order table that includes (among other fields) a Customer ID and an Amount for each item ordered. You'd like to find out how much each customer has ordered, so you create a query that selects the Customer ID and Amount fields. Without any aggregate functions, this query would return the same number of rows as there were in the table: if Stuart Schumacher ordered 10 items, you'd see 10 rows with his ID in the Customer ID column. On the other hand, if you apply the aggregate function Sum to the Amount field, you'll get just one row for each Customer ID. Query takes all the rows with the same value in the non-aggregated column (Customer ID) and collapses them into a single row. The value of the Amount field in Stuart Schumacher's row would be the sum of the values from the 10 rows. The table below lists the aggregate functions you can apply to a field using Query. Aggregate Function Sum Count Min Max Average Action Adds the values from each row and displays the total. Counts the number of rows. Checks the value from each row and returns the lowest one. Checks the value from each row and returns the highest one. Adds the values from each row and divides the result by the number of rows. 52

Applying Aggregate Functions to Fields When you apply an aggregate function to a field, you re redefining how PeopleSoft Query uses the field throughout the query. Essentially, PeopleSoft Query replaces the field, wherever it occurs, with the results of the function. If you select the field as a display column, PeopleSoft Query displays the aggregate values; if you use the field as an order by column, PeopleSoft Query orders the results based on the aggregate values. To apply an aggregate function to a field: 1. In Query Manager, click the Fields tab. 2. Click the button associated with the appropriate field. The Edit Field Properties page appears. 3. Pick the aggregate function you want to use for this field, and click OK. The abbreviation for the selected function appears in the Agg column. If a function is not available for the field you ve selected, the Edit Field Properties page does not close. For example, you can t use Sum with a character field. 53

Relating Multiple Criteria Using PeopleSoft Query, you can relate multiple criteria in specific ways that you define using the AND, AND NOT, OR, and OR NOT operators. You can also group criteria using parentheses Using AND OR Logical Operators When you specify two or more selection criteria for a query, you must tell PeopleSoft Query how to coordinate the different criteria. For example, suppose you re querying the list of your customers and you ve defined two criteria: one that selects customers from the state of Washington and another that selects customers who have purchased airplanes. You may want PeopleSoft Query to return only those rows that meet both conditions (customers in Washington who ve purchased airplanes), or you may want the rows that meet either one of the conditions (all Washington customers plus all customers who ve purchased airplanes). Rows returned by AND OR When your query includes multiple criteria, link them using either AND, AND NOT, OR, or OR NOT. When you link two criteria with AND, a row must meet the first and second criterion in order for PeopleSoft Query to return it. When you link two criteria with OR, a row must meet the first or second criterion, not necessarily both. The AND NOT operator will return results on those rows that meet the first criteria and exclude the second criteria. The OR NOT operator will return results on rows that meet both criteria along with all rows that meet the second criteria. By default, PeopleSoft Query assumes that you want those rows that meet all the criteria you specify. When you add a new criterion, PeopleSoft Query displays AND in the Logical column on the Criteria tab. To link the criterion using one of the other options instead, select the required option from the dropdown list. 54

Advanced Query Having Criteria Query Manual 9.2 To specify criteria for aggregate functions, you use a SQL Having clause. Once you ve applied an aggregate function to a field, that field has been redefined and you can t use the field in your Where criteria. You need to specify Having criteria. A Where clause evaluates individual rows before they re grouped together by an aggregate function, then it evaluates Having clauses after the rows have been grouped together by an aggregate function. Unions Unions enable you to get the results from two or more separate queries at the same time. You can create an union of multiple queries only when the queries have the following common elements: The same number of selected fields. The same data types for all fields. The same display order for the columns. Sub Queries A subquery, sometimes called a sub-select, is a query whose results are used by another query. The main query uses the subquery s result set as a comparison value for a selection criterion. You create a subquery when you need to compare a field value to the results of a second query. Suppose, for example, that you want a list of employees who are not members of any professional organizations. For each employee in the PERSONAL_DATA table, you must determine whether his or her employee ID is in the MEMBERSHIP table. That is, you must compare the value in the PERSONAL_DATA.EMPLID field to the results of a subquery that selects the EMPLID values from the MEMBERSHIP table. 55

APPENDIX Frequently Used Records VENDORS VENDOR VENDOR_ADDR VENDOR_LOC VENDOR_WTHD_JUR Vendor Header Table - Main Vendor table which contains many important fields related to the vendor. (i.e. Vendor ID, Name, Address) Vendor Address - Address Information for each Vendor Vendor Location - Location Information for each Vendor Vendor Withhold Jurisdiction - Withholding Information Populated (Important in 1099 Processing) REQUISITIONS REQ_HDR REQ_LINE REQ_LINE_DISTRIB REQ_LINE_SHIP REQ_APPROVAL REQUESTOR_TBL Requisition Header - Header Record for Requisition Requisition Line - Line Record for Requisition Requisition Line Distribution - Accounting Distribution for Requisition Requisition Line Delivery Schd - Shipment Details for Requisition Requisition Approval - Approval Information for Requisition Master Requester Table - Requester Information PURCHASE ORDERS PO_HDR PO_LINE PO_LINE_DISTRIB PO_LINE_MATCHED PO_APPROVAL PO_LINE_SHIP Purchase Order Header - Header Record for Purchase Order Purchase Order Line - Line Record for Purchase Order PO Line Accounting Entries - Accounting Distribution for Purchase Order PO Line Billed Amounts - Match Information for PO (Voucher, Receipt, PO) Purchase Order Approval - Approval Information for Purchase Order PO Line Shipping Schedule - Shipment Details for Purchase Order 56

RECEIPTS RECV_HDR RECV_LN_DISTRIB RECV_LN_ASSET RECV_LN_SHIP Receiver Header - Receipt Header Table Receipt Accounting Entries - Receipt Distribution Line Receiving Asset Interface Scrl - Receipt Line Asset Information Receipt Shipping Schedule - Receipt Shipment Information ACCOUNTS PAYABLE VOUCHER VOUCHER_LINE VCHR_ACCTG_LINE DISTRIB_LINE GRP_AP TRAVEL AUTHORIZATIONS EX_TAUTH_HDR EX_TAUTH_LINE EX_TAUTH_DIST EXPENSE REPORTS EX_ACCTG_LINE EX_SHEET_HDR EX_SHEET_LINE EX_SHEET_DIST AP Voucher Header Table - Header Record for Voucher Voucher Line - Line Record for Voucher AP Accounting Entries Voucher Distribution Table - Accounting Distribution for Voucher AP Control Group Table - AP Control Group Data Travel Authorization Header - Header Record for TA Line Information - Line Record for TA Travel Authorization Dist - Accounting Distribution for TA Expenses Accounting Line expenses by accounting lines Expense Sheet Header - Header Record for Expense Report Expense Report Line - Line Record for Expense Report Expense Line Distributions - Accounting Distribution for Expense Report 57

CASH ADVANCES EX_ADV_HDR EX_ADV_LINE EX_ADV_DIST EX_ADV_APPRVR Advance Header - Header Record for Advances Advance Line - Line Record for Advances Cash Advance Distribution - Accounting Distribution for Advances Approvers - Approval Information Related to Advances EXPENSE APPROVERS EX_ADV_HDR JOB Advance Header - Header Record for Advances EE Job History - HR Manager Information PAYMENTS PAYMENT_TBL PYMNT_VCHR_XREF EX_ADVNCE_PYMNT EX_SHEET_PYMNT AP Disbursements - Detail of each payment generated from the Accounts Payable Pay Cycle. Includes fields such as Check #, Payment #, Vendor Paid, Employee ID Paid (From Expenses), Address and Method of Payment, Payment Status (i.e. Cancelled, Scheduled) Voucher Scheduled Payment - Accounts Payable Detail (i.e. Voucher ID) related to a Advance Payment - Cash Advance Detail related to a specific payment. Sheet Payment - Expense Report Detail related to a specific payment. GENERAL LEDGER (Ledger populated by GL Posting Process) JRNL_HEADER JRNL_LN LEDGER Journal Header Data - Header Record for Journal. Important Fields include the following:journal_id, JOURNAL_DATE, JRNL_HDR_STATUS,BUDGET_HDR_STATUS, DESCR254 Journal Line Data - Line Record for Journal. Important fields include the following: Journal ID, Journal Line #, Department ID and Account (and Other Chartfields), Budget Line Status, Distribution Amounts, Budget Dates, Close Flag Ledger Data - Summary of Balances by Chartfields by Fiscal Year, Accounting Period 58

STUDENT FINANCIALS ITEM_SF ITEM_LINE_SF ACCOUNT_SF SF_ACCTG_LN ITEM_TYPE_TBL GL_INTERFACE Item Record Line Items Student Financials Account Student Financials Student Financials Accounting Line Item Type Table General Ledger values for item types 59

COMMITMENT CONTROL (Populated by Budget Check process) Ledger Data - Summary of Balances by Chartfields by Fiscal Year, Accounting Period. Similar to LEDGER_KK LEDGER table with the additional field, for Budget Period. KK Budget Journal Line - Budget Transfer and KK_BUDGET_LN Budget Entry Journal Lines KK Budget Journal Header - Budget Transfer and KK_BUDGET_HDR Budget Entry Journal Header KK budget activity record - Transaction Accounting Details populated on this record when an Item is KK_ACTIVITY_LOG 'Budget Checked'.Each transaction is identified by KK Transaction ID Comm. Cntrl. Source Hdr Table - Associates the KK_SOURCE_HDR KK Transaction ID's with a more module specific Identifier, like a specific Voucher ID Comm. Cntrl. Liquidation Table - For each KK Transaction ID, the amount remaining to be KK_LIQUIDATION liquidated. (i.e. Amount of encumbrance remaining to be released for PO or TA) BUDGET PREPARATION FIU_POSTN_BUDGT LEDGER_BUDG CHARTFIELD TABLES DEPT_TBL PROJECT GL_ACCOUNT_TBL SPEEDTYP_TBL FUND_TBL CLASS_CF_TBL PROGRAM_TBL BUD_REF_TBL Position Budget Reporting - Position Budgets (Unique to FIU) Budget Ledger Data - Ledger for Last Year's Budget, Forecast and Requested budgets Departments - Department Ids Projects - Stores the Project information when a new Project is created, keyed by Business Unit (FIU01 - Grants & Construction only as of 7/1/12; FIU02 - Various) Accounts - Accounts SpeedTypes - Speedtypes Fund Table - Fund Codes:E&G, AUX, C&G, Agencies, FA, Student Related Activities, and Concessions Class of Trade Table - Class (Campus / Location) Codes: 1. Modesto A. Madique Campus 2. Biscayne Bay Campus 3. Broward 4. Pembroke Pines 5. Wolfsonian Program Table - PCS Codes \ Functional Component \ Program Codes Budget Reference Table - Budget Reference (Used by Construction ONLY as of 7/1/12) 60

ALTACCT_TBL COMBO_DATA_TBL CHARTFIELD1_TBL CHARTFIELD2_TBL Alternate Account - Alternate Accounts established by the State of Florida for state accounting ChartField Combo Data Tbl - Contains Valid CF Combinations (or Invalid depending on Rule Definition) Activity Numbers Cost PID ASSETS BOOK COST INTFC_PRE_AM INTFC_FIN ASSET DEPRECIATION ASSET_ACQ_DET ASSET_NBV_TBL Financial Book - The table has the Financial Asset Book transactions. Important fields include BU, Asset #, Book, Begin_Depr_Dt Asset Cost Transactions - The table has the Asset Cost transactions Important fields include Asset #, Book, Group_Asset_ID, Category, Cost Type, Cost Pre-Interface Table to AM - Table initially loaded with asset detail from other system. (i.e. Accounts Payable) AM Interface-Financial - Accounting Detail associated with asset initially loaded into Asset Management Asset General Information - The primary Asset table populated when an asset is created. Important fields include: Asset #, Tag, Description, Acquisition dates, Serial #, Profile Depreciation Transactions - The table has the Depreciation transactions. Important fields include the following:bu, Asset #, Book, Start_PD, End_PD, Trans_Dt Asset Acquisition Detail - Asset Acquisition Detail Asset NBV Reporting Table - Asset Net Book Value Detail 61

SUB-MODULE INTERFACE TABLES (STAGING TABLES) - Prior to Journal Generation VCHR_ACCTG_LN AP Accounting Entries - Accounts Payables (Vouchers) EX_ACCTG_LINE Expense Accounting Line - Travel & Expenses (Cash Advances \ Expense Reports) DIST_LN AM Accounting Entries - Asset Management (Assets) CA_ACCTG_LN_PC Accounting line tbl for CA/PC - Contracts (Grants Billing) BI_ACCT_ENTRY Billing Account Entry table - Billing (Grants Billing) ITEM_DST Customer Item Distribution - Receivables (Grants Receivables \ Payments) PAY_MISC_DST Non Customer Payment Distrib - Receivables (Grants Payments) SF_ACCTG_LN Student Financials Acctg Line - Student Financials (including Cashiering) HR_ACCTG_LINE Payroll Accounting Line - Payroll (PSFT HR\Payroll on 1/1/2012) JGEN_ACCT_ENTRY JrnlGen Accounting Entry Table - Pinnacle (Telecommunications) 62

GRANTS SPECIFIC CONTRACTS \ GRANTS CA_DETAIL_DST CA_CONTR_HDR PROJECT PROJ_RESOURCE GM_AWARD GM_PROPOSAL BILLING BI_HDR BI_LINE RECEIVABLES ITEM ITEM_ACTIVITY ITEM_DST Contract Distribution Detail - Links Projects to Contracts/ Awards Contract Header - Line Record for Purchase Order Projects - Stores the Project information when a new Project is created, keyed by Business Unit (FIU01 - Grants & Construction only as of 7/1/12; FIU02 - Various) Project Resources - Gives the Budget and expense Information for every project in the system Award Parent Record - Header Record for Award Grants Proposal - Header Record for Proposal Bill Header - Header record for Customer Bill Bill Lines - Line Information for customer bills Customer Items - Header Record for Receivables Items Customer Item Activity - Detail Line information for Receivables Items Customer Item Distribution - Item Chartfield Distribution 63

PAYMENTS DEPOSIT_CONTROL PAYMENT PAYMENT_ID_CUST PAYMENT_ID_ITEM Deposit Control Information - List the Customer Deposit Information (Deposit BU and Deposit ID are Keys) Payments - Payment information for the Customers (Customer Payments\Receipts) Payment Customer Identification - Payment Customer Information Payment Item Identification - Payment Item Identification CUSTOMERS CUSTOMER CUST_ADDRESS CUST_CONTACT CUST_DATA CUST_AGING Customer Header Information - Header for Customer Data Customer Address Detail - Customer Address Information Customer Contact Detail - Customer Contact Information Customer Info / Balances - Customer Details such as Customer Balance, Last Payment, Last Aged Customer Aging - Customer Details such as Aging Id, Aging Amount, Count, etc. 64

Useful Queries by Module Purchasing Requisitions Query Name FIU_REQ_ENTERED_BY REQUISITION_WORKFLOW_ROUTING FIU_REQ_APPROVER_LISTING FIU_REQ_APPROVAL_HIST_BY_DEPT FIU_PO_CATEGORY_LIST2 FIU_PO_DEPT_PYMNT_VENDOR FIU_PO_LIST_BY_VENDOR FIU_PO_TO_VENDOR Description Requistion list by Userid Requisition Routing All Approvers Assoc. To A Req Req. appr hist sourced to POs PO CATEGORY LIST (Eff/Acct) Total paid by a dept by Catego List of PO's Prompt by Vendor PO's ISSUED TO A GIVEN VENDOR 65

Purchasing Purchase Orders Query Name FIU_FSSS_APPR_REQ_NOT_SOURCED FIU_FSSS_APPROVED_REQUISITIONS FIU_FSSS_APPROVERS_FOR_REQS FIU_FSSS_MULTIPLE_PO_SRC_ISSUE FIU_FSSS_OPEN_PO_BY_ACT_PROJ FIU_FSSS_OPEN_REQS FIU_FSSS_PO_BLANK_CF2 FIU_FSSS_PO_BY_FUND FIU_FSSS_PO_BY_MDC_ZIP_CODE FIU_FSSS_PO_CAT_ASSIGNED_BUYER FIU_FSSS_PO_CATEGORY_LIST FIU_FSSS_PO_CF_FIU_DEACTIVATIO FIU_FSSS_PO_CORRECT_CF FIU_FSSS_PO_CYCLE_TIME FIU_FSSS_PO_DIST FIU_FSSS_PO_DISTRIB_SCHEDULE FIU_FSSS_PO_NON_US_SUPPLIERS FIU_FSSS_PO_REPORT_COMM_2 FIU_FSSS_PO_REPORT_COMMENTS FIU_FSSS_PO_REQUESTOR_ISSUE FIU_FSSS_PO_REV_CONTRACT FIU_FSSS_PO_REV_CONTRACT2 FIU_FSSS_PO_SPEND_MARKETING FIU_FSSS_PO_VNDR_OVER_2 FIU_FSSS_REQ_AUTO_APPR_ISSUE FIU_FSSS_REQ_BUDGET_BP FIU_FSSS_REQ_BUDGET_ISSUES FIU_FSSS_REQ_DIST FIU_FSSS_REQ_SOURCE_STATUS FIU_FSSS_REQ_WF_ORG_DEPT FIU_FSSS_REQ_WF_ORG_PID FIU_FSSS_REQ_WF_ROUT_BY_APPROV FIU_FSSS_REQS_BLANK_CF2 FIU_FSSS_REQS_BUDG_ERRORS FIU_FSSS_REQS_DISTRIB_LINE FIU_FSSS_REQS_ISSUE FIU_FSSS_REQS_ROLL_2014 FIU_FSSS_REQS_STUCK_IN_WF FIU_FSSS_STUCK_PO Description Requisition that has not sourced to an approver List of Appr Reqs by Approver Reqs Approvers and Requestors Requisitions to many POs POs by Dept or Activity or Proj Open Reqs within specific date PO for 651,652 blank CF2 View PO by FUND View PO by Miami Dade County Zip code PO Category - Assigned Buyers PO CATEGORY LIST List of POs with correct CF List of POs by Status PO_DISTRIBUTION_SCHEDULE Vndrs Classified as Foreign Location set to SEE BELOW Productivity by Fund Productivy by Fund - Voucher Specific Vendors - Catering List of negative pre-enc Reqs not captured in req roll List of Requisitions by Status Stuck Reqs in Sourcing WB Requisition Routing By Dept ID Requisition Routing By Userid Requisition Routing by User ID Apr Reqs for 651,652 blank CF2 To Identify Req in Budg Error Reqs-GL unit other than FIU01 Reqs missing GL Account List of Req Distribution Lines Requisition Routing to POTIDAL POs stuck in batch process 66

Purchase Orders cont. Query Name Description FIU_COB_REQ_PO_VOUCHER REQ workflow FSSS_REQ_AUTO_APPR_ISSUE FIU_COB_REQ_PO_VOUCHER3 REQ workflow FIU_KK3_REQ_ISSUES REQs with Duplicate Activity FIU_KK4_PO_ISSUES POs with Duplicate Activity FIU_KK5_REQ_STUCK_IN_PROCESS Requisitions Stuck In Process FIU_KK6_PO_STUCK_IN_PROCESS Purchase Ord Stuck In Process FIU_OPEN_ENC_BY_PO Open Encumbrances Prompt by PO FIU_OPEN_ENC_RPT_PO Open Encumbrance Rpt by PO FIU_ORIGINAL_BUYER_ON_PO Original Buyer Assigned to PO FIU_PENDING_REQS_FRGN_VENDORS Pending reqs with foreign suppliers FIU_PO_ALL All PO's entered in PS FIU_PO_APPROVAL_HISTORY Approval Instance by PO FIU_PO_APPROVAL_TIME TIME IT TAKES TO APPROVE A PO FIU_PO_APPROVED_VENDORS VENDORS THAT ARE APPROVED FIU_PO_APPROVED_VENDS_ALL ALL VENDORS THAT ARE APPROVED FIU_PO_APPROVER_SEC_ROLES PO Approver Roles for PS Users FIU_PO_AUTHS_NOT_REQUESTERS Apprs not setup as Requesters FIU_PO_BUDGETERRORS POS WITH BUDGET ERRORS FIU_PO_CANCELLED PO THAT ARE IN CANCELLED STATU FIU_PO_CATEGORY_ACCOUNT Category / Account Listing FIU_PO_CATEGORY_ACCOUNT_PROMPT Category / Account Listing FIU_PO_CATEGORY_LIST PO CATEGORY LIST FIU_PO_CATEGORY_LIST2 PO CATEGORY LIST (Eff/Acct) FIU_PO_CLOSE_CANCEL_BGT_ISSUES PO IS CLOSE,CANCEL & BGT ISSUE FIU_PO_CO_OPEN_OR_PENDING_APPR CO THAT ARE OPEN OR PENDING AP FIU_PO_CO_TO_BE_WORKED_ON CO THAT NEED TO BE WORKED ON FIU_PO_DEPT_PAY_VENDOR Total paid by a dept to vendor FIU_PO_DEPT_PYMNT_VENDOR Total paid by a dept by Category # 67

Accounts Payable Query Name FIU_AP_FOREIGN_VENDORS FIU_AP_VOUCHER_SEARCH FIU_PO_LOOKUP_BY_VCHR FIU_PO_APPROVED_VENDORS FIU_VENDOR_LOOKUP AP_VOUCHER_LOOKUP VOUCHER_RECEIPT VCHRS_ENTERED_BY_DATE FIU_FS_AP_LIAB FIU_FSSS_AP_BUDG_ISSUE FIU_FSSS_AP_DIST FIU_FSSS_AP_DSO_PYMT_HANDLING FIU_FSSS_AP_ERROR_ENTRY_ST_REP FIU_FSSS_AP_JRNL_LINES_IN_ERR FIU_FSSS_AP_OUTSTANDING_VCHRS FIU_FSSS_AP_PYMT_FLAGS FIU_FSSS_AP_PYMT_REGISTER_UNIT FIU_FSSS_AP_UNPOSTED_VCHRS FIU_FSSS_AP_VCHR_ACCTG_LN FIU_FSSS_AP_VCHR_ACCTG_LN_FSSS Description FIU_Foreign Vendors FIU_AP_VOUCHER_SEARCH FIND A PO USING VCHR NO VENDORS THAT ARE APPROVED Vendor Lookup AP voucher entry status List Receipts per Voucher Vourcher prompts by Acctg date Financial Statement AP Liabili AP Entry Status Error Report AP Journal lines in error Unpaid Vouchers by GL BU AP_Payment Register _FIU_Unit Vouchers Unposted by Bus Unit FIU_FSSS_AP_VCHRS_NOT_BUDGCHEC AP Vouchers not budget checked by BU# within a cretian date range FIU_FSSS_AP_VCHRS_NOT_IN_GL Vouchers using Fund 651, 652 FIU_FSSS_AP_VCHRS_NOT_POSTED Vourchers using Fund 651,652 FIU_FSSS_AP_VCHRS_NOTPOSTED FIU_FSSS_AP_VNDR_DUP_INVOICE DRAFTING QUERY IN PROGRESS FIU_FSSS_DSO_AP_PYMT_REGISTER List for specific Projects FIU_FSSS_STUCK_VCHR Voucher in Batch Process FIU_FSSS_VCHR_APPL_TO_PREPAY FSSS_APVOUCHER 68

Smart Billing Query Name Description FIU_SB_JOURNAL_LOOKUP SMB Journal by invoice # FIU_SB_LOOKUP_BY_JOURNAL_ID Invoice look-up by Journal ID FIU_SMARTBILLS View SMB status Asset Management Query Name ASSETS_BY_UNIT_AND_DEPT Description List My Department's Assets Travel and Expense Query Name FIU_FSSS_ASSOCIATED_TRAVELAUTH Description provides the Expense Report number that was attached to a Travel Authorization, includes prompt that requires a TA#. FIU_FSSS_ER_QUEUE FIU_FSSS_TE_KK_BDGT_EXCEPTIONS provides in who s queue Expense Report is residing for approval, includes prompt that requires an ER#. provides a list of TA and ERs with budget exceptions and type of budget error. 69