Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

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

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

Table of Contents

Table of Contents


Test 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.


Ui expand
titleFINAH-PPM-TransactionDetail-View

FINAH-PPM-TransactionDetail-View

Epic:  

Jira Legacy
serverITS PRO
serverIdebe8394f-6d75-344c-8d9c-717cb778a1eb
keyFINAHMAINT-893

SNOW tickets addressed: CS1076689
Added the following fields:

  • Entity
  • Entity Code
  • Entity Code and Name
  • Entity Effective End Date
  • Entity Effective Start Date
  • Entity Is Current Count
  • Entity Is Current Flag
  • Entity L1
  • Entity L1 Code
  • Entity L1 Code and Name
  • Entity L2
  • Entity L2 Code
  • Entity L2 Code and Name
  • Entity L3
  • Entity L3 Code
  • Entity L3 Code and Name
  • Financial Unit
  • Financial Unit Code
  • Financial Unit Code and Name
  • Financial Unit Effective End Date
  • Financial Unit Effective Start Date
  • Financial Unit Is Current Count
  • Financial Unit Is Current Flag
  • Financial Unit L1
  • Financial Unit L1 Code
  • Financial Unit L1 Code and Name
  • Financial Unit L2
  • Financial Unit L2 Code
  • Financial Unit L2 Code and Name
  • Financial Unit L3
  • Financial Unit L3 Code
  • Financial Unit L3 Code and Name
  • Financial Unit L4
  • Financial Unit L4 Code
  • Financial Unit L4 Code and Name



Ui expand
titleFINAH-ProjectCosts-View

FINAH-ProjectCosts-View

Epic:  

Jira Legacy
serverITS PRO
serverIdebe8394f-6d75-344c-8d9c-717cb778a1eb
keyFINAHMAINT-696

SNOW tickets addressed: CS0853271

*Changing field type.  Transaction Number will now be a string.

Added the following fields:

  • Expenditure Invoice Approver Email Address
  • Expenditure Invoice Approver Employee ID
  • Expenditure Invoice Approver ID And Name
  • Expenditure Invoice Approver Identity AD Username
  • Expenditure Invoice Approver Name Full
  • PO Requisition First Approver Email Address
  • PO Requisition First Approver Employee ID
  • PO Requisition First Approver ID And Name
  • PO Requisition First Approver Identity AD Username
  • PO Requisition First Approver Name Full



Ui expand
titleFINAH-UCSDGeneralLedgerInterface-View

FINAH-UCSDGeneralLedgerInterface-View

Epic:  

Jira Legacy
serverITS PRO
serverIdebe8394f-6d75-344c-8d9c-717cb778a1eb
keyFINAHMAINT-885

SNOW tickets addressed: CS1044958 and CS1078692

Added the following fields:

  • Journal Created By Email Address
  • Journal Created By Employee ID
  • Journal Created By ID And Name
  • Journal Created By Identity AD Username
  • Journal Created By Name Full
  • Receipt Comment
  • Receipt Method
  • Receipt Receivables Activity



Ui expand
titleFINAH-UCSDGeneralLedger-View

FINAH-

UCSDGeneralLedgerInterface

UCSDGeneralLedger-View

Epic:  

Jira Legacy
serverITS PRO
serverIdebe8394f-6d75-344c-8d9c-717cb778a1eb
keyFINAHMAINT-892

SNOW tickets addressed: CS1078692

Added the following fields:

  • Journal Created By Email Address
  • Journal Created By Employee ID
  • Journal Created By ID And Name
  • Journal Created By Identity AD Username
  • Journal Created By Name Full



Customer Service Reminder

Warning

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

Tip
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?