Page Types: A Quick Reference Guide

Process

This is a job aid to help you understand the structure and function of the three types of pages in CORE. Understanding these pages is essential for efficiently completing tasks like entering transactions, referencing data, or searching for system information.

Understanding Page Types in CORE

CORE uses three main page types to display, input, and manage data for various business processes.

Reference Pages

Reference pages are a primary source of structured data in CORE.

• Function: They control the tables of information that populate dropdown menus and picklists across transaction and inquiry pages, establishing the valid values users can enter into fields.

• Access: Users typically access these pages indirectly by selecting a picklist icon or dropdown next to a field to choose from a list of valid values.

• Key Characteristic: They are generally Read-Only for most business roles. Updates are centrally maintained by authorized users.

• Examples: 

  • The Position Status reference page lists the valid options that appear in the Position Status picklist.

  • The Vendor/Customer (VCUST) table includes information about the vendor/customer, like their address, business type, and whether a vendor is subject to 1099 Reporting. 

Transaction Pages

Transaction pages are where users perform actions that create, update, or manage data in COMPAS.

• Function: They are used to initiate business processes, such as adding a new user to CORE or allocating labor.

• Interaction: Think of them as electronic forms that collect, organize, and process information within the system.

• Key Characteristic: Actions on transaction pages often route through workflow for review and approval.

• Examples: 

  • The Employee Status Maintenance (ESMT) transaction page allows users to view and enter data that will be recorded by the transaction.

  • The General Accounting Expenditure (GAX) transaction page allows a user to create a payment for a vendor. 

Inquiry Pages

Inquiry Pages allow users to search and view information that has already been processed and stored in the system.

• Function: These are read-only pages used for reporting and validation purposes.

• Common Uses: Viewing budget structures and employee profiles, or reviewing position rosters.

• Key Characteristic: They are Read-Only, summarizing information from processed transactions without allowing changes to the data.

• Example: 

  • The Employment Verification (QVER) inquiry page displays a summary of employee information pulled from multiple transactions, such as ESMT, ATTR, EMER, and DEPTD.

  • BQ190LV*: Various online inquiry pages for Budget Structure 190 for the Legal Budget per Budget Year.