Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 5 Current »

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 Sept 15” so we can address it prior to the Thursday, September 16 release to Production. 

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 set the old fields to null, this release we will be deleting the out-going fields.

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


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.

Follow our Enhancement Testing Steps

Use this UAT time to adjust your reports as needed prior to the Production release where your customers will be able to see any issues these enhancements cause. 
  • Cognos: Use the packages in Cognos DEV > Financial Activity Hub > Financial Activity Hub Packages UAT to build your report and select Hana QA.  Do not select Hana Prod as the report will fail.  Using Hana QA will allow you to see the below enhancements with Oracle Production data. 
  • Tableau: Sign into Tableau on your Tableau desktop tool and open your report.  Add a new data source with the same name and -QA at the end of the title.  Using this data source will allow you to see the below enhancements with Oracle Production data.
  • Hana QA:  FINAH data in Hana QA is production Oracle data loaded daily, just like in Hana PROD.

If you find an issue, please include in your email to busintel@ucsd.edu the following:

  • What browser are you using?
  • What environment are you using?  Cognos DEV, QA or PROD?  Or Tableau?
  • What data source / package are you using?
  • What results were you expecting? 
  • No labels