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

Version 1 Current »

Hello FINAH Developers - We are excited to release new enhancements for you to test. 

This is final UAT for September 30, October 14 and October 30 FINAH enhancements:

Due to the Cognos upgrade during October we have only released enhancements to UAT.  Hearing no critical issues, we will be releasing all of the enhancements released since September 30th into Production on November 6.  The is the final week for you to test the following enhancements.

If you find an issue, please email busintel@ucsd.edu right away with the subject line “FINAH UAT due November 5” so we can address it prior to November 6.

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.

Consumer Access:

If users want to build FINAH reports then they need to request an Oracle access role of UCSD BI Consumer JR via the Oracle and Concur Role Request form.  Users with UCSD BI Author JR, UCSD BI Modeler JR or UCSD BI Administrator JR will automatically have FINAH Report Developer access.

If consumers want to view the reports that you have built for them, then do not need to have Oracle access.  These consumers do need to be in an Active Directory (AD) group that you have provided to busintel@ucsd.edu with instructions on which folder and which data source that AD group will need to access in order to view the reports you have built for them.

Financial Measures:

Financial data lives at different levels (Award, Project, Task, more...) due to the nature of finance.  Tableau and Cognos will display the same number for multiple rows when the measure you are looking at lives at a less-detailed grain than what you have included in your report.  This is expected behavior in both tools, no a duplication in FinAH.  Tableau developers, please note that if you total these measures you see inflated numbers - this is expected Tableau functionality.  Cognos functionality allows for these totals to display the correct, unique grain value.

Tableau report developer will need to use Level of Detail (LOD) calculation to display the correct total if you choose to display measures and dimensions that live at different grains together in the same worksheet.  For example, {FIXED 'Award Number' : MIN(Measure Name)} or {FIXED 'Project Code and Name' : MIN(Measure Name)}

Cognos and Tableau are different business intelligence tools that have different strengths (https://blink.ucsd.edu/technology/bi/tools/index.html) so we encourage you to use the best tool for your specific report need.  ITS-BIA attempts to delivery the data equitably but we cannot force the tools to function the same.  If you are delivering report links to your end customers then there is no reason for end customers to be concerned with which tools the report is built in.



How to test the new enhancements:

  • Cognos: Use the packages in Cognos DEV > Financial Activity Hub > FINAH Data Sources – 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 QA 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?  Tableau QA or Prod?
  • What data source / package are you using?
  • What results were you expecting?  What departments were you approved for via the new FINAH row level security?

Items marked with an asterisk (*) are report breaking enhancements if you have these fields in your report.

ViewEnhancementEpic
FINAH-Account-View
  • Add field: CBO Account Hierarchy L1 Code
  • Add field: CBO Account Hierarchy L1
  • Add field: CBO Account Hierarchy L1 Code and Name
  • Add field: CBO Account Hierarchy L2 Code
  • Add field: CBO Account Hierarchy L2
  • Add field: CBO Account Hierarchy L2 Code and Name
  • Add field: CBO Account Hierarchy L3 Code
  • Add field: CBO Account Hierarchy L3
  • Add field: CBO Account Hierarchy L3 Code and Name
  • Add field: CBO Account Hierarchy L4 Code
  • Add field: CBO Account Hierarchy L4
  • Add field: CBO Account Hierarchy L4 Code and Name
  • Add field: CBO Account Hierarchy L5 Code
  • Add field: CBO Account Hierarchy L5
  • Add field: CBO Account Hierarchy L5 Code and Name
FINAHCORE-528
FINAH-Award-View

New view released to UAT on 9/30

  • Remove field:  "Award Funding Source Code" per user feedback
  • Remove field:  "Award Funding Source" per user feedback
  • Remove field:  "Award Funding Source Code and Name" per user feedback
  • Add field: "Award Funded by Federal Agency Count"
  • Add field: "Award Contract Document Number"
  • Add field: "Award Invoiced Amount"
  • Add field: "Award Contract LOC Number"
  • Add field: "Award Revenue Amount"
  • *Changed name: Award Budget Funding Amount to Award Budget Period Funding Amount
  • *Changed name: Award Budget Cost Amount to Award Budget Period Cost Amount
  • *Changed name: Award Budget Invoice Amount to Award Budget Period Invoice Amount
  • *Changed name: Award Budget Revenue Amount to Award Budget Period Revenue Amount
FINAHCORE-438
FINAH-Contract-ViewNew view release to UAT on 10/30FINAHCORE-468
FINAH-ContractRevenue-ViewNew view release to UAT on 10/30FINAHCORE-466
FINAH-Project-View

New view released to UAT on 9/30

Added additional fields for UAT on 10/14

FINAHCORE-374
FINAH-ProjectCosts-ViewNew view released to UAT on 10/14FINAHCORE-464
FINAH-ProjectPersonnelRole-View
  • Add field Contract 
  • Add field Contract Code
  • Add field Contract Code and Name
  • Add field Project
  • Add field Project Code
  • Add field Project Code and Name
  • Add field Role Relationship
FINAHCORE-436
FINAH-Fund-View
  • Add field: CBO Fund Hierarchy L1 Code
  • Add field: CBO Fund Hierarchy L1
  • Add field: CBO Fund Hierarchy L1 Code and Name
  • Add field: CBO Fund Hierarchy L2 Code
  • Add field: CBO Fund Hierarchy L2
  • Add field: CBO Fund Hierarchy L2 Code and Name
  • Add field: CBO Fund Hierarchy L3 Code
  • Add field: CBO Fund Hierarchy L3
  • Add field: CBO Fund Hierarchy L3 Code and Name
  • Add field: CBO Fund Hierarchy L4 Code
  • Add field: CBO Fund Hierarchy L4
  • Add field: CBO Fund Hierarchy L4 Code and Name
  • Add field: CBO Fund Hierarchy L5 Code
  • Add field: CBO Fund Hierarchy L5
  • Add field: CBO Fund Hierarchy L5 Code and Name
  • Add field: CBO Fund Hierarchy L6 Code
  • Add field: CBO Fund Hierarchy L6
  • Add field: CBO Fund Hierarchy L6 Code and Name
FINAHCORE-525
FINAH-Task-ViewNew view released to UAT on 10/14FINAHCORE-375
FINAH-UCSDGeneralLedger-View
  • Add field: CBO Account Hierarchy L1 Code
  • Add field: CBO Account Hierarchy L1
  • Add field: CBO Account Hierarchy L1 Code and Name
  • Add field: CBO Account Hierarchy L2 Code
  • Add field: CBO Account Hierarchy L2
  • Add field: CBO Account Hierarchy L2 Code and Name
  • Add field: CBO Account Hierarchy L3 Code
  • Add field: CBO Account Hierarchy L3
  • Add field: CBO Account Hierarchy L3 Code and Name
  • Add field: CBO Account Hierarchy L4 Code
  • Add field: CBO Account Hierarchy L4
  • Add field: CBO Account Hierarchy L4 Code and Name
  • Add field: CBO Account Hierarchy L5 Code
  • Add field: CBO Account Hierarchy L5
  • Add field: CBO Account Hierarchy L5 Code and Name
  • Add field: CBO Fund Hierarchy L1 Code
  • Add field: CBO Fund Hierarchy L1
  • Add field: CBO Fund Hierarchy L1 Code and Name
  • Add field: CBO Fund Hierarchy L2 Code
  • Add field: CBO Fund Hierarchy L2
  • Add field: CBO Fund Hierarchy L2 Code and Name
  • Add field: CBO Fund Hierarchy L3 Code
  • Add field: CBO Fund Hierarchy L3
  • Add field: CBO Fund Hierarchy L3 Code and Name
  • Add field: CBO Fund Hierarchy L4 Code
  • Add field: CBO Fund Hierarchy L4
  • Add field: CBO Fund Hierarchy L4 Code and Name
  • Add field: CBO Fund Hierarchy L5 Code
  • Add field: CBO Fund Hierarchy L5
  • Add field: CBO Fund Hierarchy L5 Code and Name
  • Add field: Journal ID
  • Add field: Journal Line Number

FINAHCORE-169

FINAHCORE-477

Reminder: UAT was completed when we published the General Ledger so these were moved directly into production.

ViewEnhancementEpicNote
FINAH-Account-ViewNew View with no GL measuresFINAHCORE-186Available in Tableau and Cognos
FINAH-Activity-ViewNew View with no GL measuresFINAHCORE-187Available in Tableau, will be available Cognos post upgrade on November 4
FINAH-Entity-ViewNew View with no GL measuresFINAHCORE-188Available in Tableau and Cognos
FINAH-FoundationInvestmentPool-ViewNew View with no GL measuresFINAHCORE-195Available in Tableau and Cognos
FINAH-Function-ViewNew View with no GL measuresFINAHCORE-197Available in Tableau and Cognos
FINAH-Fund-ViewNew View with no GL measuresFINAHCORE-198Available in Tableau and Cognos
FINAH-Interentity-ViewNew View with no GL measuresFINAHCORE-201Available in Tableau, will be available Cognos post upgrade on November 4
FINAH-Location-ViewNew View with no GL measuresFINAHCORE-202Available in Tableau and Cognos
  • No labels