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

Hello EAH Developers - The below enhancements are included in this month's EAH Release.

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

Learn more about the Employee Activity Hub in the EAH Quick Start Guides.

Table of Contents


Schedule

  • Thursday, February 8, end of day: release enhancements to User Acceptance Testing

  • Thursday, February 15, end of day: release enhancement to Production

  • Friday, February 16, end of day: delete QA models


Thank You Report Developers!

Special thanks to the report developers who submitted enhancement requests. 

  • Maruthi Alamuri
  • Amanda David
  • David Mandell
  • Maria Obtera
  • Heather Sears
  • Eva Thiveos


New View: EAH-ApprovalSalaryCostTransferDetails-View

In conjunction with the UCPath Reporting Team, BIA is excited to release the EAH-ApprovalSalaryCostTransferDetails-View.  This view can be used for insights into the Salary Cost Transfer Approval process.

This view will be part of the Core views and has no row level security.

Epic:   EAHE-3047 - Getting issue details... STATUS

SNOW tickets addressed: CS1787117

Unique fields include:

  • SCT Accounting Period Number
  • SCT Combination
  • SCT Combination Code
  • SCT Company Code
  • SCT Created By Display Name
  • SCT Created By User ID
  • SCT Earnings Type
  • SCT Earnings Type Code
  • SCT Fiscal Year
  • SCT High Risk By Federal Fund Maximum Increase Code
  • SCT Initiator Comment
  • SCT Line Entry Type
  • SCT OTC Indicator Code
  • SCT Pay Date
  • SCT Pay Group Code
  • SCT Pay Run Code
  • SCT Process Date
  • SCT Process Status
  • SCT Process Status Code
  • SCT Questionnaire Response 1
  • SCT Questionnaire Response 2
  • SCT Questionnaire Response 3
  • SCT Questionnaire Response 4
  • SCT Reason
  • SCT Reason Code
  • SCT SetID
  • SCT Source
  • SCT Source Code
  • SCT Status
  • SCT Status Code
  • SCT Transaction Number
  • SCT Transaction Sub Number
  • SCT CCOA Activity
  • SCT CCOA Activity Code
  • SCT CCOA Entity
  • SCT CCOA Entity Code
  • SCT CCOA FinU
  • SCT CCOA FinU Code
  • SCT CCOA FND SRC
  • SCT CCOA FND SRC Code
  • SCT CCOA Funct
  • SCT CCOA Funct Code
  • SCT CCOA Fund
  • SCT CCOA Fund Code
  • SCT CCOA Location
  • SCT CCOA Location Code
  • SCT CCOA Program
  • SCT CCOA Program Code
  • SCT CCOA Project
  • SCT CCOA Project Code
  • SCT CCOA TASK
  • SCT CCOA TASK Code
  • SCT Approve Date
  • SCT Creation Date
  • SCT Earnings Period End Date
  • SCT Pay Period End Date
  • SCT Pay Period Start Date
  • SCT Posting Pay Period End Date
  • SCT High Risk By Award End Date Count
  • SCT High Risk By Federal Fund Increase Count
  • SCT High Risk By UCPath Approval Count
  • SCT High Risk Count
  • SCT Off Cycle Count
  • SCT High Risk By Award End Date Flag
  • SCT High Risk By Federal Fund Increase Flag
  • SCT High Risk By UCPath Approval Flag
  • SCT High Risk Flag
  • SCT Off Cycle Flag
  • SCT Earnings Adjustment Amount
  • SCT Earnings Fund Amount
  • SCT Earnings New Amount
  • SCT Earnings Old Amount
  • SCT Effort Percent
  • SCT High Risk By Federal Fund Maximum Increase Amount
  • SCT Percent Of Pay

New View: EAH-SystemRole-View

In conjunction with the UCPath Reporting Team, BIA is excited to release the EAH-SystemRole-View.  This new view is a combination of limited EAH-Workforce-View fields and role information from UCPath and Oracle Financials Cloud.  This view can be used to determine what role an employee has within UCPath and Oracle Financials Cloud.  Roles from other data sources are expected to be added in the future. 

Epic:   EAHE-2654 - Getting issue details... STATUS

SNOW tickets addressed: CSTASK0028213, CS1820889

Unique fields include:

  • Business Unit Ledger
  • Purchasing Authority
  • Purchasing Authority Code
  • Purchasing Authority Code And Name
  • Role Access Level
  • Role Access Level Code
  • Role Business Area
  • Role Person Display Name
  • Role Person First Name
  • Role Person ID
  • Role Person Last Name
  • Role Person Middle Name
  • Role Person Name
  • Role Source
  • Role Source Code
  • Role System Function
  • Role System Function Code
  • User Assignment Number
  • User ID
  • User Role
  • User Role Code
  • User Role Code And Name
  • User Account Locked Count
  • User Account Locked Flag


View Your Requested Enhancements

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

EAH-LLFringeDetail-View

Epic:   EAHE-3087 - Getting issue details... STATUS

SNOW ticket(s) addressed: 

Added the following new fields:

  • LL Fringe Type
  • LL Fringe Type Code

EAH-PayrollProjectionPerMonth-View

Epic:   EAHE-3082 - Getting issue details... STATUS

SNOW ticket(s) addressed: CS1856635

Added the following new fields:

  • Position Funding CCOA FinU
  • Position Funding CCOA FinU Code

EAH-PositionBudgetComparisonSummary-View

Epic:   EAHE-3066 - Getting issue details... STATUS

SNOW ticket(s) addressed: CS1819942, CS1862139, CS1814452

Added the following new fields:

  • Position Budget Job Code
  • Position Budget Job Code Description
  • Position Budget New Hire Notes
  • Project Department Reporting Category
  • Salary Plan
  • Salary Plan Code
  • Union
  • Union Code

EAH-PositionFunding-View

Epic:   EAHE-3089 - Getting issue details... STATUS

SNOW ticket(s) addressed:  CS1862139 

Added the following new fields

  • Project Department Reporting Category


UAT - 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 User Acceptance Testing (UAT) 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? 

Reminder: QA data sources will be deleted the Friday after the enhancements are migrated to Production.

  • No labels