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




From: Parnell, Sarah <saparnell@ucsd.edu>
To: Financial-Analytics-COP-l (Financial-Analytics-COP-l@ucsd.edu) <Financial-Analytics-COP-l@ucsd.edu>
Cc: ITS-BIA <its-bia@ucsd.edu>; ITS-DataIntergrationServices <ITS-DataIntergrationServices@AD.UCSD.EDU>; Kilburn, Erin <ekilburn@ucsd.edu>; Baker, Beverly <b3baker@UCSD.EDU>; Virgil, Laura <lsvirgil@ucsd.edu>; Kim, Elliot <etkim@ucsd.edu>
Subject: FINAH enhancements - UAT available - due March 17

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 March 17” so we can address it prior to the Thursday, March 18 release to Production. 

FINAH UAT in alignment with Oracle Reporting

Currently, Oracle Reporting only displays transactions that have posted.  FINAH was originally released including all transactions: non-posted and posted.  This has caused some confusion as FINAH-UCSDGeneralLedger-View reports have not matched Oracle reports.  In order to bring FINAH in alignment with Oracle reporting, we have removed all non-posted transactions from FINAH.  These non-posted transactions are also know as pre-posted, unposted, not approved transactions, not posted, and/or un-processed costs.  In FINAH these transactions have appeared with null transaction dates. 

You will see the change in UAT for FINAH-UCSDGeneralLedger-View only at this time.  If we receive no objections to this alignment then we will push this enhancement into FINAH Production.  Reports that are already filtered to remove these non-posted transactions will continue to work as no fields will be removed, only the non-posted transactional rows are being removed.

Please be sure to point your reports at the UAT data sources or packages in order to view the results of removing non-posted transactions from FINAH.  If you see any issues or have any concerns please email busintel@ucsd.edu right away with the subject line “FINAH UAT due March 17” so we can address it prior to the Thursday, March 18 release to Production.  Those with a business need to view non-posted transactions can continue to do so using Oracle Reports.

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

FINAH-Task-View users:

  • As we've adapted the FINAH views to your needs, all of the fields from FINAH-Task-View have been added to the FINAH-ProjectCost-View.  If you are using the FINAH-Task-View, please repoint your report at the FINAH-ProjectCost-View.  We would like to retire the FINAH-Task-View once everyone has moved their reports.

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.

How to test the new enhancements:

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

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

ViewEnhancementEpic
Note on Project Organization and Financial UnitIn FINAH the fields "Project Organization" and "Financial Unit" are available to you.  In most cases these fields will be the same, but in Oracle and FINAH these fields are physically not the same.  When the "Project Organization" does not match "Financial Unit" you will see a value populated for "Project Organization" but all of the "Financial Unit" related fields will be null.



FINAH-Project-View
  • Added "Financial Unit L1 Code and Name"
  • Added "Financial Unit L2 Code"
  • Added "Financial Unit L2"
  • Added "Financial Unit L2 Code and Name"
  • Added "Financial Unit L3 Code"
  • Added "Financial Unit L3"
  • Added "Financial Unit L3 Code and Name"
  • Added "Financial Unit L4 Code"
  • Added "Financial Unit L4"
  • Added "Financial Unit L4 Code and Name"
  • Added "Financial Unit Code"
  • Added "Financial Unit"
  • Added "Financial Unit Code and Name"
  • Added "Financial Unit Effective Start Date"
  • Added "Financial Unit Effective End Date"
  • Added "Financial Unit Is Current Flag"
  • Added "Financial Unit Is Current Count"
FINAHCORE-910
FINAH-ProjectCosts-View
  • Added "Task Manager Employee ID"
  • Added "Task Manager Name Full"
  • Added "Task Manager ID And Name"
  • Added "Task Manager Email"
  • Added "Financial Unit L1 Code"
  • Added "Financial Unit L1"
  • Added "Financial Unit L1 Code and Name"
  • Added" Financial Unit L2 Code"
  • Added "Financial Unit L2"
  • Added "Financial Unit L2 Code and Name"
  • Added "Financial Unit L3 Code"
  • Added "Financial Unit L3"
  • Added "Financial Unit L3 Code and Name"
  • Added "Financial Unit L4 Code"
  • Added "Financial Unit L4"
  • Added "Financial Unit L4 Code and Name"
  • Added "Financial Unit Code"
  • Added "Financial Unit"
  • Added "Financial Unit Code and Name"
  • Added "Financial Unit Effective Start Date"
  • Added "Financial Unit Effective End Date"
  • Added "Financial Unit Is Current Flag"
  • Added "Financial Unit Is Current Count"
FINAHCORE-851
FINAH-UCSDGeneralLedger-View
  • Added "Project Manager Employee ID"
  • Added "Project Manager Name Full"
  • Added "Project Manager ID And Name"
FINAHCORE-903

If you cannot view the FINAHCORE links, please request access to Jira here:  https://ucsdservicedesk.service-now.com/its?id=sc_cat_item&sys_id=9af5d148db514450008c9837db96190b

To unsubscribe from this mail list

  1. Enter https://mailman.ucsd.edu/mailman/options/Financial-Analytics-COP-l/YourEmailAddress into a browser
  2. Locate the Unsubscribe section on your screen and click Unsubscribe.
  3. You will receive an e-mail with "confirm" in the subject line.  Follow the email's instructions to complete the unsubscribe process.
  4. For more information go here: https://blink.ucsd.edu/technology/email/services/lists/subscriber/index.html

Thanks!

Sarah Parnell

Analytics Community of Practice Manager

Business Intelligence & Analytics | Information Technology Services | UC San Diego

saparnell@ucsd.edu

work cell: 858-354-9709

My pronouns [https://www.mypronouns.org/]: she/her/hers

“My job is to make your job easier.  Where do you want to start?” - Sarah

  • No labels