If you need HR data for your system or reporting needs, you will need to access it through the Employee Data Lakehouse.
| Table of Contents | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
|
Application or Personal Access
To access the data lakehouse Access to the Employee Lakehouse will be through SQL Authentication where a user and database name will be provided to developers.
For requesting this type of access, submit a ticket to it-analytics@usf.edu with the following information included:
Server
Data Product: Employee Data LakeLakehouse
Table(s)/View(s): Provide list of available objects you need to which you need access.
Reason for Access: Provide a reason for user gaining access.
Optional: Account Name you prefer or to which you are adding access.
ACL Request
To access the objects in the data lake houseEmployee Lakehouse, you need to submit an ACL Request.
Source Information: Provide your source host name.
Server
Port: 1433
Employee Data Lakehouse Objects
Object Name
Documentation
dbo.ActionOccurencesPVO
dbo.ActionReasonsPVO
dbo.ActionsPVO
dbo.ActionTypesPVO
dbo.CitizenshipPVOViewAll
dbo.CountryPVO
dbo.DepartmentPVOViewAll
dbo.ExternaIIdentifierPVO
dbo.FLEX_BI_OrgAttributesDFF_VI
dbo.GlobalPersonPVOViewAll
dbo.LegalEmployerPVO
dbo.LookupValuesPVO
dbo.OrganizationPVO
dbo.PersonEthinicityPVOViewAll
Connection Parameters
Once access has been granted use any SQL database tools to connect to the lake house.
Provide the database name EmployeeDataLake_sdb in the connection parameters. For example in SSMS:
Employee Lakehouse Objects
Organization Structure
hcm.DepartmentPVOViewAll | |
hcm.OrganizationPVO | |
hcm.PerOrgTreeStructureBICVO | |
ita.VPAreaCollegeUnit | IT Analytics derived organizational structure, to reduce the number of joins required by end users to understand reporting structure in Oracle HCM |
Employee Information
hcm.ContactPhonesPVO | |
hcm.ContactRelshipsPVO | |
hcm.ExternaIIdentifierPVO | |
hcm.FlexBIPersonsDFFVI | |
hcm.VisaPermitPVOViewAll | |
ita.EmployeeInformation | Derived employee information data to minimize extensive joins across multiple Lakehouse objects |
Job, Position & Compensation
hcm.PositionPVOViewAll hcm.FlexBIPositionCustomerFlexVI | |
hcm.JobPVOViewAll hcm.JobExtractPVO | |
hcm.SalaryExtractPVO | |
hcm.SalaryPVO |
Employee Assignment
hcm.GlobalPersonPVOViewAll | |
hcm.PersonExtraInformationEFFBIFlattenedVO | |
hcm.PersonLegislativeInfoPVOViewAll |
hcm. |
AssignmentPVO |
dbo.SalaryPVO
ita.EmployeeAssignment | Derived assignment data to minimize the number of joins required by users querying assignment data |
Payroll
Oracle HCM Setup
hcm.ActionOccurencesPVO |
hcm. |
ActionReasonsPVO |
hcm. |
ActionsPVO |
dbo.JobPVOViewAll
dbo.VPAreaCollegeUnit
Join of dbo.OrganizationPVO and dbo.FLEX_BI_OrgAttributesDFF_VI
hcm.ActionTypesPVO | |
hcm.LookupValuesPVO | |
hcm.CountryPVO |
hcm. |
CitizenshipPVOViewAll |
hcm. |
LegalEmployerPVO |
hcm. |
PersonEthinicityPVOViewAll |
hcm. |
SalaryBasesPVO |
hcm. |
StateProvincePVO |
hcm. |
UnionPVO |