20210812 FINAH Production Release Notes

Hello FINAH Developers - The below fields are now available for you in Production. 

Our August release for the Financial Activity Hub includes improved logic and data for the Project Costs View.  In order to provide this enhancement, it is necessary to load a volume of new data to our underlying activity table. While and until this data loads, you will notice the following impact:

  • Activity Code and all associated Activity fields will be null
  • The following fields will default to the value from the task DFF when available (general projects) and otherwise be null:
    • Function and all fields starting with the word Function
    • Fund and all fields starting with the word Fund
    • Program and all fields starting with the word Program
    • Location and all fields starting with the word Location

As the data loads these fields will populate. We expect the load process to complete over the weekend.

We appreciate your patience as we strive to enhance the Financial Activity Hub to meet your analytic needs.

As always, feel free to reach out to us at busintel@ucsd.edu with any questions or concerns.


Table of Contents


Renaming and Deprecating

As we've adapted the FINAH views to your needs, we have found changing field names is painful for both report developers and our team due to the name change breaking reports, data integrations and packages / data sources.  In an effort to avoid this pain, we are going to introduce a new name change strategy. 

  1. ITS-BIA will release new fields with the revised field name in the views that contain the field to be renamed, or where a view is to be renamed ITS-BIA will release as a new view the view with the revised name.

  2. ITS-BIA will allow a transition period for report developers to repoint their reports at the new fields / views.

  3. ITS-BIA will remove the data from the old fields / views and allow a second transition period.  This will not break the report but will highlight where the fields / views are still in use as they will become blank.

  4. ITS-BIA will deprecate the fields / views.  Any reports the have not transitioned by this point will break.

We'll be using this new strategy on the following items that require name changes.  Last release we introduced the new fields, this release we've set the old fields to null.

Additional details here: 20210709 FINAH Start UAT Release Notes

  • 'Fiscal Period Beginning Balance' will be replaced by 'Fiscal Year To Date Beginning Balance' with the partner field being 'Fiscal Year To Date Ending Balance'
  • 'Fiscal Period Beginning Balance Entry Type' will be replaced by 'Fiscal Year To Date Beginning Balance Entry Type ' with the partner field being 'Fiscal Year To Date Ending Balance Entry Type'
  • 'Fiscal Period Beginning Balance Entry Type Code' will be replaced by 'Fiscal Year To Date Beginning Balance Entry Type Code' with the partner field being 'Fiscal Year To Date Ending Balance Entry Type Code'
  • 'Fiscal Period Beginning Balance Sign' will be replaced by 'Fiscal Year To Date Beginning Balance Sign' with the partner field being 'Fiscal Year To Date Ending Balance Sign'
  • 'Fiscal Period Beginning Credit Balance' will be replaced by 'Fiscal Year To Date Beginning Credit Balance' with the partner field being 'Fiscal Year To Date Ending Credit Balance'
  • 'Fiscal Period Beginning Debit Balance' will be replaced by 'Fiscal Year To Date Beginning Debit Balance' with the partner field being 'Fiscal Year To Date Ending Debit Balance'
  • 'Fiscal Period Beginning Signed Balance' will be replaced by 'Fiscal Year To Date Beginning Signed Balance' with the partner field being 'Fiscal Year To Date Ending Signed Balance'
  • 'Fiscal Quarter To Date Balance' will be replaced by 'Fiscal Quarter To Date Beginning Balance' with the partner field being 'Fiscal Quarter To Date Ending Balance'
  • 'Fiscal Quarter To Date Balance Entry Type' will be replaced by 'Fiscal Quarter To Date Beginning Balance Entry Type ' with the partner field being 'Fiscal Quarter To Date Ending Balance Entry Type'
  • 'Fiscal Quarter To Date Balance Entry Type Code' will be replaced by 'Fiscal Quarter To Date Beginning Balance Entry Type Code' with the partner field being 'Fiscal Quarter To Date Ending Balance Entry Type Code'
  • 'Fiscal Quarter To Date Balance Sign' will be replaced by 'Fiscal Quarter To Date Beginning Balance Sign' with the partner field being 'Fiscal Quarter To Date Ending Balance Sign'
  • 'Fiscal Quarter To Date Credit Balance' will be replaced by 'Fiscal Quarter To Date Beginning Credit Balance' with the partner field being 'Fiscal Quarter To Date Ending Credit Balance'
  • 'Fiscal Quarter To Date Debit Balance' will be replaced by 'Fiscal Quarter To Date Beginning Debit Balance' with the partner field being 'Fiscal Quarter To Date Ending Debit Balance'
  • 'Fiscal Quarter To Date Signed Balance' will be replaced by 'Fiscal Quarter To Date Beginning Signed Balance' with the partner field being 'Fiscal Quarter To Date Ending Signed Balance'
  • 'Project To Date Balance' will be replaced by 'Project To Date Beginning Balance' with the partner field being 'Project To Date Ending Balance'
  • 'Project To Date Balance Entry Type' will be replaced by 'Project To Date Beginning Balance Entry Type ' with the partner field being 'Project To Date Ending Balance Entry Type'
  • 'Project To Date Balance Entry Type Code' will be replaced by 'Project To Date Beginning Balance Entry Type Code' with the partner field being 'Project To Date Ending Balance Entry Type Code'
  • 'Project To Date Balance Sign' will be replaced by 'Project To Date Beginning Balance Sign' with the partner field being 'Project To Date Ending Balance Sign'
  • 'Project To Date Credit Balance' will be replaced by 'Project To Date Beginning Credit Balance' with the partner field being 'Project To Date Ending Credit Balance'
  • 'Project To Date Debit Balance' will be replaced by 'Project To Date Beginning Debit Balance' with the partner field being 'Project To Date Ending Debit Balance'
  • 'Project To Date Signed Balance' will be replaced by 'Project To Date Beginning Signed Balance' with the partner field being 'Project To Date Ending Signed Balance'
  • 'Expense Dist Receiver GL Accounting Period' will be replaced by 'Expenditure Dist Accounting Period'
  • 'Expense Dist Receiver PA Accounting Period' will be replaced by 'Expenditure Dist Accounting Period'
  • 'Expense Dist Provider PA Fiscal Period Full' will be replaced by 'Expenditure Dist Fiscal Period Full '
  • 'Expense Dist Receiver GL Fiscal Period Full' will be replaced by 'Expenditure Dist Fiscal Period Full '
  • 'Expense Dist Receiver PA Fiscal Period Full' will be replaced by 'Expenditure Dist Fiscal Period Full '
  • 'Expense Dist Provider PA Fiscal Period Number' will be replaced by 'Expenditure Dist Fiscal Period Number'
  • 'Expense Dist Receiver GL Fiscal Period Number' will be replaced by 'Expenditure Dist Fiscal Period Number'
  • 'Expense Dist Receiver PA Fiscal Period Number' will be replaced by 'Expenditure Dist Fiscal Period Number'
  • 'Expense Dist Provider PA Fiscal Period Short' will be replaced by 'Expenditure Dist Fiscal Period Short'
  • 'Expense Dist Receiver GL Fiscal Period Short' will be replaced by 'Expenditure Dist Fiscal Period Short'
  • 'Expense Dist Receiver PA Fiscal Period Short' will be replaced by 'Expenditure Dist Fiscal Period Short'
  • 'Expense Dist Provider GL Special Fiscal Period Count' will no longer be needed
  • 'Expense Dist Provider PA Special Fiscal Period Count' will no longer be needed
  • 'Expense Dist Receiver GL Special Fiscal Period Count' will no longer be needed
  • 'Expense Dist Receiver PA Special Fiscal Period Count' will no longer be needed
  • 'Expense Dist Provider GL Special Fiscal Period Flag' will no longer be needed
  • 'Expense Dist Provider PA Special Fiscal Period Flag' will no longer be needed
  • 'Expense Dist Receiver GL Special Fiscal Period Flag' will no longer be needed
  • 'Expense Dist Receiver PA Special Fiscal Period Flag' will no longer be needed


Your Requested Enhancements

Items marked with an asterisk (*) are report breaking enhancements if you have these fields in your report and you have not take the appropriate remediation steps.