Glossary

• 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. 

Boundary Applications are any application or system that interfaces with our current Kuali system and/or will interface with the future Oracle Cloud Services. Whether the interface is coming into (upstream) or going out of (downstream) the system, the incoming or outgoing data crosses the “boundaries” of KFS and/or Oracle.

More than 70 applications are expected to interface with Oracle as boundary systems, and will be modified to align with the new UC Davis Chart of Accounts structure.

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.

See Posting Level

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

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