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 3 Next »

Hello FINAH Developers - The below fields are now available for you in Hana QA.  If you find an issue, please email busintel@ucsd.edu prior to end of day Monday, August 28 so we can address it before the Thursday migration to Production.

Due to the Cognos upgrade the August UAT period will be extended until Monday, August 28, after all of the Cognos environment have been upgraded.

Keep up with our future enhancements here: FINAH Bugs and Enhancements In Progress

Table of Contents


Thank You Report Developers!

Special thanks to the report developers who submitted enhancement requests. 

  • Rehan Ahmed
  • Jonathan Matsen
  • Heather Sears


Renaming and Deprecating

As we've adapted the AH 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 strategy on the following items that require name changes. 

In the August release we have added new fields in preparation for replacing the existing fields.  We are replacing the current field because we have other User fields and the new names in FINAH will differentiate TE Users from EAH Users.

  • Active User Count will be replace by Active TE User Count
  • Active User Flag will be replace by Active TE User Flag
  • User Email Address will be replace by TE User Email Address
  • User Financial Unit Code And Name will be replace by TE User Financial Unit Code And Name
  • User Financial Unit Code will be replace by TE User Financial Unit Code
  • User Financial Unit will be replace by TE User Financial Unit
  • User Home Department Code And Name will be replace by TE User Home Department Code And Name
  • User Home Department Code will be replace by TE User Home Department Code
  • User Home Department will be replace by TE User Home Department
  • User HR Status will be replace by TE User HR Status
  • User ID And Name will be replace by TE User ID And Name
  • User ID will be replace by TE User ID
  • User Last Separation Date will be replace by TE User Last Separation Date
  • User Name First will be replace by TE User Name First
  • User Name Full will be replace by TE User Name Full
  • User Name Last will be replace by TE User Name Last
  • User Name Middle will be replace by TE User Name Middle
  • User Profile Approver Email Address will be replace by TE User Profile Approver Email Address
  • User Profile Approver Name Full will be replace by TE User Profile Approver Name Full
  • User Profile Financial Unit Code will be replace by TE User Profile Financial Unit Code
  • User Profile Financial Unit will be replace by TE User Profile Financial Unit
  • User Profile Function Code will be replace by TE User Profile Function Code
  • User Profile Function will be replace by TE User Profile Function
  • User Profile Fund Code will be replace by TE User Profile Fund Code
  • User Profile Fund will be replace by TE User Profile Fund
  • User Profile Funding Source Code will be replace by TE User Profile Funding Source Code
  • User Profile Funding Source will be replace by TE User Profile Funding Source
  • User Profile Ledger will be replace by TE User Profile Ledger
  • User Profile Location Code will be replace by TE User Profile Location Code
  • User Profile Location will be replace by TE User Profile Location
  • User Profile Primary Assignment Financial Unit Code will be replace by TE User Profile Primary Assignment Financial Unit Code
  • User Profile Program Code will be replace by TE User Profile Program Code
  • User Profile Program will be replace by TE User Profile Program
  • User Profile Project Code will be replace by TE User Profile Project Code
  • User Profile Project will be replace by TE User Profile Project
  • User Profile Supplier Code And Name will be replace by TE User Profile Supplier Code And Name
  • User Profile Supplier Code will be replace by TE User Profile Supplier Code
  • User Profile Supplier will be replace by TE User Profile Supplier
  • User Profile Task Code will be replace by TE User Profile Task Code
  • User Profile Task will be replace by TE User Profile Task
  • User Profile User Group will be replace by TE User Profile User Group
  • User Profile User Traveler Type will be replace by TE User Profile User Traveler Type
  • User Reports To Employee ID will be replace by TE User Reports To Employee ID
  • User Reports To ID And Name will be replace by TE User Reports To ID And Name
  • User Reports To Name Full will be replace by TE User Reports To Name Full
  • User System ID will be replace by TE User System ID
  • User Vice Chancellor Code And Name will be replace by TE User Vice Chancellor Code And Name
  • User Vice Chancellor Code will be replace by TE User Vice Chancellor Code
  • User Vice Chancellor will be replace by TE User Vice Chancellor

Impacted Views

  • FINAH-TE-ExpenseTransactionDetail-View
  • FINAH-TE-User-View


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.

FINAH-UCSDGeneralLedgerBalances-View

Epic:   FINAHE-1495 - Getting issue details... STATUS

SNOW tickets addressed: CS1642795

Logic addition:

  • For Annual Budget Fields – populate period 13 with the annual amount as in periods 1-12.

  • For Fiscal Year to Date Fields – populate period 13 with the amount in period 12.

  • For Fiscal Quarter to Date Fields – populate period 13 with the amount in period 12.

  • For Fiscal Period Fields – leave as is.

FINAH-PPM-TransactionDetail-View

Epic:   FINAHE-1486 - Getting issue details... STATUS

SNOW tickets addressed: CS1617386, CS1606810

Added the following fields:

  • Subaward Anticipated Total Amount

  • Subaward Available Amount

  • Subaward Invoice Total Amount

  • Subaward Number

  • Subaward Recipient Organization Code

  • Subaward Recipient Organization Name

  • Subaward Recipient Organization Name And Code

  • Task Prior Budget Period Commitment Amount

FINAH-ProjectCost-View

Epic:   FINAHE-1491 - Getting issue details... STATUS

SNOW tickets addressed: CS1633247

Added the following fields:

  • Project Budget Period Funding External Amount

  • Project Budget Period Funding Internal Amount


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.

A duty cycle has been implemented for Hana QA.  During this time, Hana QA will not be available.  Please schedule your UAT work around this duty cycle.

  • Hana QA will not be available from 7pm-5am nightly
  • Hana QA will not be available Saturday and Sunday
  • Data loads will occur from 5am-10am on weekdays

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 > Student Activity Hub > Student 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 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 Production data.
  • Hana QA:  SAH data in Hana QA is production 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