Glossary Page Update

The Financial Accounting Standards Board (FASB) establishes financial accounting and reporting standards for public companies and not-for-profit organizations that follow Generally Accepted Accounting Principles (GAAP).

• Provide specialized functionality and are used to identify the intended usage of your natural account values to facilitate automation and enable completion of other required set up objects.
• Automatically generate fully defined initial Financial Reporting reports and Account Groups based on the enterprise structure. Examples:
  • Asset - Accounts Receivable: For receivables receipt methods
  • Liability - Accounts Payable: For Payable common options
  • Net Position - Net Position: For GL ledger options
  • Revenue - Top Revenue Parent Account: For sample reports & account groups
  • Expense - Top Operating Expenses Parent Accounts: For sample reports & account groups

The project name for the Business Transformation initiative, as well as the system name for Oracle implementation on campus.

An alternative name for the dimension member that includes the dimension member description. Use aliases to better identify a form and report label (or dimension member). For example, a financial department dimension member name is DP_FOAA00C, and its alias is DP_FOAA00C-Finance Operations and Administration C. 

A dimension member at a higher level relative to a specific member in the hierarchy.

An approver is an Aggie Enterprise user responsible for reviewing a document and approving or rejecting it.

For the Requisition document, approvers are automatically assigned to the approval workflow based on department, dollar amount, and category names selected on the document. 

Audited financial statements are those required by a third party, independent certified public accountant or firm. The three financial statements include:

• Statement of Net Position (SNP)
• Statement of Revenues, Expenses and Changes in Net Position (SRECNP)
• Statement of Cash Flows, including both the direct and indirect method

Although Automatic Purchase Order is not an "official" Aggie Enterprise term, it is used to identify a Requisition that doesn’t require buyer approval before the associated Purchase Order is created and issued to a supplier. In general, Requisitions less than $10K, not citing a capital asset or controlled substances, do not require buyer approval from Procurement & Contracting Services. 

When a CoA segment is configured as a “balancing segment” in the Oracle system, it means that the system will automatically create due to/ due from transactions between segments so that those segments are always in balance.

UC Davis has configured the Entity and Fund segments as balancing segments, ensuring that debit transactions match with credit transactions, & facilitating financial statement reporting.

A Blanket Purchase Order is a purchase requested by a department via a non-catalog Requisition for an ongoing good or service need, generally for year or longer. A blanket order can often benefit a department with better pricing, especially if the cost of goods/services is likely to increase with inflation, for example. 

For Aggie Enterprise, a “boundary system” refers to applications that interact with the university’s central financial system. These boundary applications either send information to or receive information from Aggie Enterprise.

Fiscal year that starts next July.

A buyer is a member of the UC Davis Procurement & Contracting Services team who negotiates with outside suppliers for the best options for purchasing goods and services.

A buyer oversees the Requisition process and is responsible for creating Purchase Orders for Requisitions over the Automatic Purchase Order (APO) threshold, as well as for those Requisitions requesting most services, controlled substances, and other restricted purchases. 

Large square or rectangular button that opens different Planning pages, forms, or reports.

Carryfoward in a particular fiscal year represents the net position from the prior fiscal year.

Catalog purchasing allows shoppers in Aggie Enterprise to purchase items, both supplies and capital assets, directly from multiple suppliers. Items include office, computer, custodial, hardware, medical, and scientific and lab products.  These catalogs are based on university agreements with each of the suppliers, ensuring the best pricing and terms and conditions. 

There are two catalog types in Aggie Enterprise:

• Hosted:  Catalogs available directly in the Aggie Enterprise system.  The only hosted catalogs in Aggie Enterprise are those provided by AggieSupply (Scientific Store, Central Storehouse, Maintenance, Repair, and Operations (MRO) Store).
• Punch-Out: Catalogs for which the shopper is taken to a dedicated site to shop and then return their items to the Aggie Enterprise system

Catalog purchasing is the recommended way to procure goods most quickly, with the most advantageous terms.  Learn how to catalog purchase in Aggie Enterprise.

The Common Chart of Accounts (CCoA) is the systemwide chart structure developed by UCOP to establish consistency in the UC accounting system and practices. The segment definitions and values in the CCoA provide a framework for each UC campus to develop their local Chart of Accounts.

The combination of chart segment values for recording financial transactions.

A dimension member that is immediately below a specific member in a hierarchy.

See Posting Level

Cleared is a payment term that indicates that a check has been issued to and cashed by the supplier/payee.  

The various services available in the Oracle financial system.

A group of cards. A cluster looks like a card and is identified by three dots below the card icon.

The Chart of Accounts (CoA) is the basic structure that UC Davis, comprised of defined segments and values to provide the foundation for recording and reporting financial transactions at UC Davis. It creates a common language for financial information. 

The new UC Davis CoA replaces the current Full Accounting Unit (FAU). It aligns UC Davis with the CCoA structure required by UCOP and also serves as the foundation for Oracle Cloud Financials implementation.

CoA is also a work stream under the Aggie Enterprise initiative.

(Natural) Account is a segment of the new UC Davis Chart of Accounts. During the Aggie Enterprise initiative, the use of the word "Natural" will help distinguish between the new CoA Account segment and the former FAU Account. The approved definition for (Natural) Account is:
The Account segment classifies the nature of the transaction as a specific type of revenue, expense, asset, liability or net position.

Visit the CoA Segment Design and Definitions webpage for more information, including micro-learning videos and supplemental resources.

Activity is a segment of the new UC Davis Chart of Accounts. The approved definition for Activity is:
The Activity segment will track significant transactions which are recurring and take place at a point in time.

Visit the CoA Segment Design and Definitions webpage for more information, including micro-learning videos and supplemental resources.

Entity is a segment of the new UC Davis Chart of Accounts. The approved definition for Entity is:
The Entity segment identifies a major organizational unit within the UC system. The Entity is responsible for all of the financial activities and results of all Financial Departments, Programs, Projects, and Activities within the Entity’s hierarchy.

Visit the CoA Segment Design and Definitions webpage for more information, including micro-learning videos and supplemental resources.

Financial Department is a segment of the new UC Davis Chart of Accounts. The approved definition for Financial Department is:
The Financial Department segment represents an academic or operating unit identified with an ongoing business objective, aligned with the UC Davis organization structure.

Visit the CoA Segment Design and Definitions webpage for more information, including micro-learning videos and supplemental resources.

Fund is a segment of the new UC Davis Chart of Accounts. The approved definition for Fund is:
The Fund segment identifies funding resources. These resources, or “pots of money” are classified based on designations and restriction types. This classification also supports external reporting of net position.

Visit the CoA Segment Design and Definitions webpage for more information, including micro-learning videos and supplemental resources.

The new Chart of Accounts includes two Future segments.
Based on lessons learned from other Higher Education institutions, and at the request of UCOP, the Future segments are reserved for UCOP’s future use.

Although users will see these segment in Oracle, they will NOT require data entry until criteria is defined and put into use. Until that time, a default value will be system-generated.

Inter-Entity is a segment of the new UC Davis Chart of Accounts.
The Inter-Entity segment is recommended by Deloitte to support the Balancing Segment functionality. UC Davis intends to designate the Entity and Fund segments as Balancing Segments.
Although users will see this segment in Oracle, it will NOT require data entry. It will have default values, generated by the Oracle system.

Program is a segment of the new UC Davis Chart of Accounts. The approved definition for Program is:
The Program segment records revenue and expense transactions associated with a formal, ongoing system-wide or cross-campus/location academic or administrative activity that demonstrates UC Davis’ mission of teaching, research, public service and patient care.

Visit the CoA Segment Design and Definitions webpage for more information, including micro-learning videos and supplemental resources.

Project is a segment of the new UC Davis Chart of Accounts. The approved definition for Project is:
The Project segment tracks financial activity for a ‘body of work’ that often has a start and an end date that spans across fiscal years.

Visit the CoA Segment Design and Definitions webpage for more information, including micro-learning videos and supplemental resources.

Purpose is a segment of the new UC Davis Chart of Accounts. The approved definition for Purpose is:
The Purpose segment is the functional classification of expenses for financial statements and other functional reporting, or for classifying revenues reflecting the mission of the university. Purpose supports federal and other external reporting requirements.

Visit the CoA Segment Design and Definitions webpage for more information, including micro-learning videos and supplemental resources.

Implemented in 2021, the Common Operating Fund Initiative (COFI) reduced complexity in the financial management of unrestricted campus resources. The focus is on campus resources that support the core academic investment and general institutional operations.

The automated process of setting funds aside for the PPM Project or Charge Account string when a Requisition is fully approved.

The commitment is automatically released when the associated Purchase Order is created.

If a fully-approved Requisition is canceled before a Purchase Order is created, the commitment is automatically released at that time.

A status that can be assigned to invoices in the Aggie Enterprise Billing module. An invoice set to Complete will post to the General Ledger during end of night processing.

As it relates to the Aggie Enterprise initiative, configuration refers to optimizing our use of Oracle cloud services by reviewing, analyzing and updating current business processes. Contrary to the past practice of customizing a system to meet us where we are, we will instead realign our processes with the industry best practices embedded in Oracle, making the best use of the system.

The portion of total award costs that is not paid or reimbursed by the sponsor of the contract or grant, and thus the unpaid portion is covered by the university or a third party. Cost sharing includes all contributions, cash and in-kind, that a recipient makes to an award.

See knowledgebase article About Cost Sharing for more information.

Cross Validation Rules (CVRs) are rules configured in Oracle to define whether a specific value in one chart segment can be combined with specific values in other segments. If the user enters a chart of account string into the system that violates one of the CVRs, an error message will be generated. CVRs are similar to the KFS Business Parameters such as Document Validation functionality.

Database container that stores data at the intersection of several dimensions. For example, the financial planning cube stores plan data using the Natural Account Category, Financial Department, Fund Category, Entity Category, Year, Period, Version, and Scenario dimensions.

In the following simplified example, the database cube consists of three dimensions: Period, Accounts, and Financial Departments. The Planning database consists of cubes with many more dimensions.

Current fiscal year.

As it relates to the Aggie Enterprise initiative, customization refers to the past practice of making complex system customizations to meet existing business processes. These customizations may not leverage best practices, and often result in systems maintenance challenges, including significant manual work to keep systems updated. This project will mark a culture shift in moving away from customization to configuration (see configuration definition).

Data Governance is a set of quality control disciplines for managing, using, improving, maintaining, monitoring, and protecting information across the enterprise.

Decommission refers to the process of retiring an external system that will no longer be used in the future state of Aggie Enterprise.

A dimension member that is at a lower level relative to a specific member in a hierarchy.

Data categories in a cube. Dimensions consist of members that are organized in hierarchies to indicate their relationships. For example, a Fund is a dimension, and Common Operating Funds is a dimension member within the Fund dimension. A dimension can be shared across multiple cubes.

An item or value within a dimension. For example, COFI - Common Operating Fund is a member of the All Funds dimension.

A notification sent to a customer to remind them of overdue payment.

Funds reserved for a future expense.

Enterprise Performance Management (EPM) is an Oracle implementation term. UC Davis refers to Enterprise Performance Management as the Planning module.

This module includes the following areas:

• Planning and Budget
• Forecasting
• Aggregated Labor Planning (by job code)

Enterprise Resource Planning (ERP), is Oracle's end-to-end Software-as-a-service (Saas) suite of modules that manages enterprise operations.  The ERP suite includes:

• Record to Report (See RTR), known at UC Davis as the Finance module
• Enterprise Performance Management (See EPM), known at UC Davis as the Planning module
• Project Portfolio Management module(See PPM)
• Procure to Pay (See PTP), known at UC Davis as the Supply Chain module

The Full Accounting Unit (FAU) is the mechanism currently used at UC Davis to classify the type, purpose and funding entered into KFS. The FAU will be replaced by the new Chart of Accounts on July 1, 2023*.

The FAU is comprised of three required elements and three optional elements, for a total of up to 30 characters.
The three required elements are:

• Chart (1)
• Account (7)
• Object (4)

The three optional elements are:

• Sub Account (5)
• Sub Object (3)
• Project (1-10)

*​​​​All UC locations are required to report financial transactions on the new Common Chart of Accounts beginning July 1, 2023. From July through December 2023, units will continue to transact in KFS using the FAU, while UC Davis central offices will translate KFS FAU data to the new CoA for reporting. 

On January 1, 2024, UC Davis will fully adopt the new Chart of Accounts. KFS users will transition to the Aggie Enterprise system and begin transacting with CoA values.

Values which identify groups of accounts for reporting with Oracle Business Transactional Intelligence (OBTI). Accounts tagged with expanded account types are automatically assigned a financial category.

A month in a fiscal year. Each fiscal year consists of 12 periods that approximate the days of the month, except for period 12, which remains open until the final University of California Office of the President close deadline at the beginning of August.

Note: The Office of the President requires a post-close adjustment period (period 13) for recording final financial statement adjustments. Period 13 entries are restricted to Central Finance staff.

A 12-month period used for financial reporting and budgeting. The period is from July 1 to June 30.

A grid (or spreadsheet) for entering and viewing financial data.

Financial Reporting Studio is a powerful tool for designing and
presenting analytic data in formats such as:

• cash management reports
• profit and loss statements
• balance sheets

It also allows nontraditional formats for financial or analytic data that include text boxes, grids, images, and charts, to design reports.

Generally Accepted Accounting Principles (GAAP) are a collection of uniform minimum standards and guidelines designed to govern financial accounting and reporting. Currently, the Financial Accounting Standards Board (FASB), the Governmental Accounting Standards Board (GASB) and the Federal Accounting Standards Advisory are authorized to establish these principles.

The Governmental Accounting Standards Board (GASB) establishes accounting and financial reporting standards for U.S. state and local governments that follow Generally Accepted Accounting Principles (GAAP).

The General Ledger (GL) stores, sorts and organizes summary financial data used to support financial reporting.

The Higher Education Function Code (HEFC) is a four-character attribute that indicates the specific purpose of the activity recorded in the account. HEFC is used at many universities around the United States and is defined by the National Association of College and University Business Officials (NACUBO).

HEFC information will be captured in the Purpose segment of the Chart of Accounts.

The reporting tree structure that defines the relationship between the values in each chart segment. The values share a parent-child relationship. Each subordinate level can only roll up to one value in the hierarchy, supporting a single source of truth. The hierarchy includes local values that roll up to UCOP, as well as values unique to UC Davis local needs.

A status that can be assigned to invoices in the Aggie Enterprise Billing module. An invoice set to Incomplete can be edited and will not post to the general ledger until it's status has been changed to Complete.

An invoice is a document that a seller sends to a buyer to detail a transaction. A request for payment.

• Invoice in the context of Supply Chain
• · Invoices for catalog orders in Aggie Enterprise are automatically received and processed by the Aggie Enterprise system.
  
  · Invoices for non-catalog Purchase Orders created in Aggie Enterprise are received, processed, and paid by the central Accounts Payable team.
  
  · Invoice payment requests not associated with Purchase Orders are to be processed on the Payment Request form to be submitted by the department.  Central Accounts Payable will then process the request to pay the supplier.

An Intercampus Order/ Charge (IOC) is a billing for costs between two UC Campuses or between one UC Campus and the UC Office of the President (UCOP) resulting in an expense transfer.

IOC examples include:

• Conference registrations/travel expenses
• Service department billings to Principal Investigators
• Deposits that belong to another campus that were received in error
• Transactions between campuses that involve agency accounts

Integrated Postsecondary Education Data System is a system of surveys issued by the Institute of Education Services > National Center for Education Statistics. Every post-secondary institution that receives federal student financial aid must submit basic characteristics including enrollment data, graduation rates, faculty and staff, etc. to the federal government.

An Interlocation Transfer of Funds (ITF) is a budgetary transfer of funds between UC Campuses or between a UC Campus and the UC Office of the President (UCOP).
ITFs are used by academic departments, organized research units, research centers, and programs housed at UCOP to provide funding for various purposes at other UC Campuses.
Some programs/departments that make awards through the ITF process include:

• Toxic Substances Research Program at UCD
• M.I.N.D. Institute at UCDMCUC MEXUS Program
• Center for Health Quality and Innovation (CHQI) Gift and Endowment Funds

In Aggie Enterprise, supported by Oracle Cloud Financials, the term "job role", sometimes referred to as “security role” refers to predefined sets of permissions and responsibilities that are assigned to users. Job roles define what actions users can perform within the application, including accessing specific modules, executing transactions, and viewing sensitive data.

Job roles are provisioned based on business needs, determined by unit leadership. Access requests and job role updates are facilitated by each unit’s Security Liaison.

A new chart of accounts term for a dean or vice chancellor’s entire organization, which is equivalent to the level-4 org term in AggieBudget.

Financial status assigned to a Purchase Order indicating that it has been fully approved and is open for purchasing.

Transaction description, a required and crucial component of an invoice. A memo line consists of the transaction name (a short description of the transaction), detailed description of the transaction, revenue chart string, and receivables chart string. See also KB0010927 About the Receivables Module.

This payment term indicates that a payment has been issued to, but not yet cashed by, the payee.

Net position is the residual of all other elements presented in a statement of financial position (balance sheet). The governmental accounting version of the accounting equation can be defined as (assets + deferred outflows of resources) - (liabilities + deferred inflows of resources) = net position. Net position may also be referred to as “Fund Balance” or “Retained Earnings” in some sectors.

Net position at the end of the fiscal year becomes Carryforward in the beginning of the following fiscal year.

Non-Catalog purchasing on a Requisition can be used for service procurement and when the desired item(s) is not available in one of the Aggie Enterprise catalogs.   Non-Catalog purchases can be issued to suppliers on agreements as well.  Learn how to create a non-catalog purchase in Aggie Enterprise.

Non-University Differentials (NUD) are assessments on goods or services provided to non-university customers in order to recoup indirect costs associated with providing the goods or services.

The process of setting funds aside to pay for a purchase.   This is often referred to as an encumbrance as well, but identified as an obligation in Aggie Enterprise.

When a Purchase Order is created in Aggie Enterprise, an obligation is automatically created, and the commitment previously created by the associated Requisition is released. 

When the Purchase Order is fully invoiced and/or otherwise closed, all remaining obligations are automatically removed.

Any fiscal year beyond the upcoming budget year.

A dimension member that is immediately above a specific member in a hierarchy.

An adjustment period required by the UC Office of the President that occurs after period 12. Final financial statement adjustments are recorded by Central staff during this period. Period 13 entries are restricted to Central Finance staff.

The POET chart string is used for transactions in the PPM subledger module.  

POET values map to the Chart of Accounts values in the General Ledger through Oracle’s subledger accounting process. The POET fields are: Project – Organization – Expenditure Type – Task.

POET(AF) includes the POET segments, but adds additional segments for Award Number and Funding Sources. Sponsored Research Projects, and only these projects, have awards and funding sources associated with them, so Sponsored projects will require the additional ‘AF’ elements.

Identifies the data to retrieve from the Planning database based on dimension member selections and display it in forms.

A dimension member with no children members that can store data.

The Posting Level is the lowest level in the hierarchy for a Chart of Accounts segment.  When processing financial transactions, users will enter the transaction at the Posting Level. 

(Also referred to as Zero Level)

Project Portfolio Management (PPM) is an Oracle implementation term. UC Davis also uses PPM to refer to the Project Portfolio Management module.

The PPM module is used to track projects that are too complex to be tracked in the General Ledger only, including:

• Sponsored Projects: Grant management (from funding to close) and Billing
• Capital Projects: Minor, Major, Capital Renewal, and Fabrications
• Faculty Projects: Tracking faculty managed resources, such as start-up and internal awards
• Department Projects

PPM uses a unique chart string, POET(AF), and a Task structure to assign budget and expense information.

Download the PPM Quick Reference Guide for additional information about PPM and POET(AF).

Department Kickout (DKO) projects temporarily store UCPath transactions that did not post successfully to sponsored or non-sponsored projects. Departments must periodically review the list of transactions in their DKO projects and transfer these costs to PPM projects or the general ledger.

See KBA Department Kick Out (DKO) Project Overview for more information.

A project that does not receive external funding and, therefore, does not have an associated award budget.

A project funded by an external organization, such as a government agency, company, or nonprofit organization.

The UC Davis Principles of Community is an aspirational statement that embodies our commitment to inclusive excellence and reflects the ideals we seek to uphold. Recognizing that change can often require difficult conversations and generate different opinions, the Aggie Enterprise project team recognizes the importance of keeping the Principles of Community at top of mind in all interactions within the team and across stakeholder groups.

As it relates to the Aggie Enterprise system, privilege is the ability to run a specific task or query in Aggie Enterprise.

Assigning roles to individuals in the Aggie Enterprise system.

Procure to Pay (PTP) is an Oracle implementation term. UC Davis refers to Procure to Pay as the Supply Chain module.

This module includes the following areas:

• Procurement: Requisitioning, Purchase Orders, Purchase Agreements and Supplier Management
• Payables: PO and Non-PO Invoice Processing, Disbursements and Payments, Tax Processing
• Supply Chain Execution: Inventory Management, Catalog Management, Warehouse Management and Fulfillment

The Purchase Order is the contract for goods and/or services issued to a supplier, based on a fully approved Requisition.  The Purchase Order obligates (encumbers) the funds, so that they are available for payment purposes.

PO format is UCDPO followed by eight numbers, issued sequentially by the system (e.g., UCDPO12345678) for most Purchase Orders, with the exception of AggieSupply (Central Storehouse, Scientific Store, Chemistry Store, MRO Store) orders that create an internal transfer order number in lieu of the UCDPO formatted number.

Field in the Billing section of the Requisition used to identify if a capital asset purchase is eligible for a reduced California sales tax if it will be used for research purposes in California at least 50 percent of the time.

A recharge is the cost charged to a University department, unit, activity, or project for specific goods or services provided by another University department, unit, activity, or project.

This payment term indicates that a payment has been issued to and cashed by the payee. 

An accounting process that compares two sets of data to ensure the accuracy of the information. An important practice that helps ensure the reliability of a business's financial records.

Boundary applications that are approved for integration with Oracle will be refactored, establishing the Oracle integration and allowing for continued use in the future.

Boundary applications which may be used in the future, but will be used differently, will be reimagined. A reimagined application may be one where some of the functionality of the application is addressed in an alternate option going forward (Ex: A subledger in Oracle).

Boundary applications that are refactored for future use with Oracle may need to be remediated to update any existing FAU fields to the new Chart of Accounts segments. If an application cannot be remediated, there will need to be a mapping exercise to align the existing system values with the new Chart of Accounts.

A Requester is a person on whose behalf a Requisition is created in Aggie Enterprise.  The Requester can be the same person as the one creating the Requisition, or it can be someone else.  The Requester is a field in the Delivery section of the Requisition and can also be set as a Requisition Preference.

The Requester receives automated system and email notifications when the associated Purchase Order is fully approved.  The Requester field also acts as the Attention line on the shipping label.

A Requisition is the document in Aggie Enterprise used by departments to request the purchase (catalog and non-catalog) of goods and/or services. A fully approved Requisition is used to create a Purchase Order that is issued to the supplier.

There are multiple statuses for a Requisition, indicating where the document is in routing:

• Approved: All required approvals have been secured, and no additional approvals are required.
• Canceled: Action taken by initiator of document, so document will not route and will not be approved.
• Incomplete: Requisition is in the initiator's queue and has not yet been submitted for approval.
• Pending Approval: One or more approvals are still required before the document is approved.
• Rejected:  Requisition has been returned to the initiator by one of the approvers in order for the initiator to make edits and resubmit for approval.
• Returned:  Requisition has been returned to the initiator by a Buyer in Procurement & Contracting Services in order for the initiator to make edits and resubmit for approval.
• Withdrawn: Initiator initially submitted the Requisition for approval, and then withdrew it back to their queue, in order to make edits before resubmitting.

A Requisitioner is an employee who creates and submits a Requisition in Aggie Enterprise. A Requisitioner can create and submit a Requisition based on their own purchasing needs or on behalf of a Requester. A Requisitioner may also be referred to as a Requisition initiator or preparer.

Financial status assigned to a Requisition, indicating it has been fully approved, and the funds have been encumbered, but the associated Purchase Order has not yet been created and/or fully approved and open.

Boundary applications will be retired if the business needs supported by the application no longer exist, or if those needs can be fully addressed by an alternate option (Ex: Oracle reporting).

Record to Report (RTR) is an Oracle implementation term. UC Davis refers to Record to Report as the Finance module.

This module includes the following areas:

• General Ledger (GL): Chart of Accounts (CoA), Journals, Allocations, Financial Reporting, and Intercompany
• Cash Management: Banks/ Branches/ Accounts and Bank Statement Reconciliation
• Fixed Assets: Asset Additions, Asset Transfers, Asset Retirements, Asset Reinstatements, and Depreciation
• Accounts Receivable: Revenue/ Billing, Invoices/ Statements, Credit Memos, and Receipts 

Software as a service is a way of delivering applications over the Internet—as a service. Applications run on the provider's servers, instead of installing and maintaining software. SaaS applications are sometimes called Web-based software.

A possible plan based on a specific set of conditions, such as time period and workforce rates. Two types of scenarios are available in the Planning application: Plan and Actual. The Plan scenario contains Working versions of the financial data. The Actual scenario contains data imported from the general ledger. Comparing the Plan and Actual scenarios can help you create a budget forecast.

In Aggie Enterprise, supported by Oracle Cloud Financials, the term "security role", sometimes referred to as “job role” refers to predefined sets of permissions and responsibilities that are assigned to users. These roles define what actions users can perform within the application, including accessing specific modules, executing transactions, and viewing sensitive data.

Security roles are provisioned based on business needs, determined by unit leadership. Access requests and security role updates are facilitated by each unit’s Security Liaison.

Roles under the Approver category provide the ability to approve a transaction. Aggie Enterprise has functionality in place to prevent an approver from approving their own transaction(s).

Approver roles will be assigned to individuals with authority to approve financial transactions on behalf of their unit.

Roles under the  Initiator (Transactor) category provide the ability to create or act in the system.

Initiator roles will be assigned to anyone who will create, manage, upload, enter and correct information in Aggie Enterprise.

Roles under the Inquiry category are view-only access, and do not allow user to transact or approve. This role provides full transparency into Aggie Enterprise data (like today's FIS-DS). 

Inquiry roles will be assigned to anyone who needs access to view any part of Oracle, including Faculty, Staff and Students, as appropriate.

A segment is one of the components of the chart of accounts which, when combined with other segments, will tell the unique story of each individual transaction. Each segment has a defined value set and hierarchy.

A dimension member that has the same parent as a specific member in the hierarchy.

Systems Integration Testing (SIT) refers to instances of testing end-to-end data flow to ensure that the system configuration and build works as intended. This includes boundary system integrations, as well as executing reports.

Subledger Accounting (SLA) is an automated process in Oracle that rolls detailed subledger information up to the General Ledger as a summary.

The Statement of Net Position (SNP) Presents the financial position of the governmental entity and its discretely presented component units. It is one of the basic financial statements issued by a governmental entity.

The Statement of Revenues, Expenses and Changes in Net Position (SRECNP) Presents the entity’s revenues, expenses, and other effects on net position in a manner that highlights results of operations.

The rate of return on the campus investments invested by the Treasury of the Regents in short term securities.

For more information, visit the Quarterly STIP Rates webpage.

Subledgers are systems which capture detailed transactional information, such as supplier invoices, accounts receivable, customer payments, and asset acquisitions. Summary level data from the subledgers rolls up into the General Ledger through an automated process in the Oracle system.

Known; System to system

Unknown; How deptartments are using Kuali data for their processes.

User Acceptance Testing (UAT) refers to instances of end-users testing scenarios to assess functionality and identify gaps in design.

A User story is a simple and concise way to describe the business process requirements and unique needs for different stakeholders.  User stories capture the “who”, “what” and “why”:  “As a__(role)__ I want to __(do something)__ So that I__(achieve something).”

The result of applying a set of rules to different dimension members. Members that satisfy the rules are considered valid in a form or report.

The Validation Status is one of the search results on the Manage Invoices screen.  There are several steps to invoice approval.  The Validation Status field will display Validated when the first part of the invoice approval process is completed.

When the second part of the invoice approval process is completed, the Approval Status column will display Workflow Approved. 

A unique combination of numeric or alpha-numeric characters, which is specific to a Chart of Accounts segment or POET(AF) element.  

A group of values that expresses the function of a Chart of Accounts segment. 

An iteration of a plan. Two types of versions are available in the Planning application: Working and Final. The Working version contains data that you are still entering or editing. The Final version is a snapshot of the Working version, containing actual data imported from the general ledger. In addition to the Final version, you can have other snapshots of the Working version. For example, you can create quarterly forecast versions.

This payment term indicates that the payment has been canceled (not issued to a payee).

Withdrawn is a routing status that indicates a document, including a Requisition, has been removed from the current approval process by the document initiator to make changes before resubmitting it. 

During the time a Purchase Order is being worked on by a buyer, the status of the Purchase Order may reflect Withdrawn, as the buyer works on it in their assigned queue. The status will reflect Open when it is fully approved and ready to be used by the department. 

See Posting Level