20211217 FINAH Start UAT Release Notes
Hello FINAH Developers - The below fields are now available for you in UAT. If you find an issue, please email busintel@ucsd.edu right away with the subject line “FINAH UAT due December 21” so we can address it prior to the Wednesday, December 22 release to Production.
Table of Contents
The Managerial Reporting Account Hierarchy is Getting a Refresh
A campuswide workgroup was established to do a comprehensive review of the existing Managerial Reporting Account Hierarchy(MRAH) to ensure that account numbers are falling under the appropriate hierarchy levels. New account groupings have also been created based on reporting needs identified after a full year in the new OFC environment.
Prior to migration to Production, we are asking report developers who have built reports off of the MRAH to test their reports in OFC-Test for Oracle, Cognos-DEV using Hana-QA or Tableau using the -QA data source. Campus Budget Office will be presenting at future meetings to preview the changes and answer any questions.
High-level summary of changes
Added a new hierarchy level for Capital Assets that includes all accounts from 16000B
Added a summarized hierarchy level called Change in Net Position for Total Resources and Total Expenses
Additional levels were added to the following hierarchy levels:
External Resources:
Affiliation Agreements
External Recharge Activity
Service Agreements
Internal Resources:
Core CBO Allocations
VC/Dean Allocations
Health System Support
Health System Transitional Support
Transfer After Overhead
Other Transfers
Non-Compensation Expenses:
Equipment, Rentals, and Repairs
Non-Operating Expenses/Transfers:
Department Assessments
Overhead-IDC
Shared Services
Internal Loan
Non-Operating Transfers
Planned Operating Shortfall Transfers
Year End Fund Collapse
Updated the following parent grouping names:
Managerial Resources Available – previously Resources Expenses (Net Position)
Other Allocations – previously Resources Allocations
Internal Recharge Activity – previously Recharge (Internal)Income
Other Transfers – previously Internal Resources-Other
Supplies and Materials – previously Supplies and Other Services
Put all posting level accounts under a new level 6 hierarchy (level 26 in Oracle)
Testing Progress
The testing plan for each downstream environment is as follows:
EPBCS: The new hierarchy has been tested by Campus Budget Office, with support of new EPBCS Business Systems Analysts, in Planning-Test EPBCS Development environment. This group tested impact of structural shifts in terms of form, report and logic breakage to ensure the new hierarchy is included in FY23 Planning process which launches January 2022.
OFC: The new hierarchy is currently available in OFC-Test for testing. An overview of the changes was presented to the weekly reporting governance meeting group on 12/15/2021 to address questions about testing and potential impacts with appropriate knowledge experts.
HUBS: The new hierarchy is also available in HANA-QA as of 12/16/21 for testing via Cognos and Tableau using the BIA standard UAT process for EAH and FINAH. An overview of the changes was presented to the FINAH Steering Committee on 12/16/21 and will also be presented to the Employee Analytics Community of Practice on 12/21/21.
Our goal is to wrap up testing in both OFC and the Hubs quickly so that these changes are available in OFC-Prod 12/21/2021 and the hubs 12/22/2021 prior to 12c framework updates in OFC-Test.
How to Test your EAH and FINAH Reports
Reports pointed at the following views and using the Managerial Reporting Account Hierarchy may need to be updated.
EAH-LLFringeDetail-View
EAH-LLSalaryDetail-View
EAH-LLSalaryFringeDetail-View
FINAH-Account-View
FINAH-ChartStringCombination-View
FINAH-ProjectCosts-View
FINAH-UCSDGeneralLedger-View
FINAH-UCSDGeneralLedgerInterface-View
FINAH-UCSDGeneralLedgerBalances-View
Customer Service Reminder
Data in UAT is not ready to be shared with end customers, is not considered completely validated and can change suddenly. For optimal customer satisfaction, do not connect your production solutions to packages / data sources that are in UAT. If you choose to share UAT items with end customer, be explicit that the data and report is in UAT and can change suddenly or be broken by UAT changes.