Frequently Asked Questions - Technical

Where do I get a list of converted employee IDs?

June 2019 Update:  The information below was most relevant in March, right around Go-Live time.  While the information is still available in the Box folder, please keep in mind that the information in the Box folder is good to use, represent the initial conversion, but will will have some duplicate IDs that have since been cleaned up.  The more up to date, ongoing source of Legacy/Path IDs in available in Cal Answers using the "Employee Crosswalk" Dashboard.


To facillitate cutover/conversion activities, a mapping file of UCPath Empl ID to PPS Empl ID mapping is available.

PRODUCTION Environment

A csv file of all converted UCPath Employee ID to PPS Employee ID mapping is available in a file named UCB_PPSID_EMPLID_CUTOVER_327.csv.csv.  This file contains all employees converted;  these are the final production values, including new values added as of March 27.  

TEST Environment

Additional files that were used to facilitate Testing efforts during the Testing Phase remain in the UCPath_ID Conversion Box folder for reference.  

To gain access to the files, send an email to eis-support@berkeley.edu.  In the email, please request for access to the UCPath ID conversion folder.  This will generate a Service Now incident in which you can use to track progress on the request.

 

What's new in LDAP to support the UCPath Project?

Many applications use LDAP as a means to authenticate to their application systems.   While new attributes were added to facilitate testing throughout the various UCPath testing stages,  the final Production LDAP attributes, and the expected values in the attributes during the cutover/conversion period are as follows:

LDAP Attribute Description
berkeleyEduHCMID Always populated if there is current or historical HCM Record for the person, including Person Of Interest (POI) and Contingent Worker (CWR) type records 
berkeleyEduUCPathID Always populated if there is current or historical UCPath Record for the person, including POI and CWR type records
employeeNumber

Populated with the following data in the order listed:

  1. Legacy HRMS Employee ID, if they existed in HRSM as a past employee and were not migrated/converted to HCM or UCPath
  2. Legacy HCM Employee ID, if they existed in HCM as a past employee and were not migrated/converted to UCPath
  3. UCPath Employee ID, if it exists in UCPath as a past or present employee
  4. Not populated (Empty), if they were a HCM employee and transitioned to a UCPath POI or Contingent Worker
berkeleyEduAffID

Multi-Valued;  May be populated with legacy UAS IDs and/or ADVCON Ids 

  1. Will also be populated with Legacy HCM ID affiliate ID if they existed in HCM as a past POI or Contingent Worker and were not migrated/converted to UCPath

  2. Will also be populated with UCPath affiliate ID if they exist in UCPath as a past or present POI or Contingent Worker

Timeline

UCPath Employee Ids will be added to the employeeNumber attribute in Mid-March for Test-LDAP, and around March 20th for production LDAP.  Check the UCPath Cutover Dashboard for PROD-LDAP confirmation.

For additional questions, please send an email to calnet-admin@berkeley.edu(link sends e-mail)

=================================Archive Information============================
---Current State, Before Go-Live---

employeeNumber = HCM Employee Number
berkeleyEduHCMID = HCM Employee Number
berkeleyEduUCPathID Not present

Testing Attributes

New attributes were added to LDAP to facilitate the various test phases of UCPath:

LDAP Attributes for UCPathIDs in TEST-LDAP

  • berkeleyEduUCPathID
  • berkeleyEduUCPathITID
  • berkeleyEduUCPathUATID

We expect that berkeleyEduUCPathID = berkeleyEduUCPathITID  during Integration Testing, and for it switch to berkeleyEduUCPathID = berkeleyEduUCPathUATID during UAT

 

LDAP Attributes for UCPathIDs in DEV-LDAP

  • berkeleyEduUCPathID
  • berkeleyEduUCPathDevID

 We expect berkeleyEduUCPathID = berkeleyEduUCPathDevID

What's new in CALDAP to support the UCPath Project?

CALDAP is the database version view of LDAP, and is downstream from LDAP.  The attributes in CALDAP mirror those of LDAP except for addition of employeeID.

While new attributes were added to facilitate testing throughout the various UCPath testing stages,  the final Production CALDAP attributes, and the expected values in the attributes during the cutover/conversion period are as follows:

CALDAP Production Attributes

---After Go-Live---

  • employeenumber = UCPath Employee Number
  • HCMID = Legacy HCM Employee Number
  • UCPathID = UCPath Employee Number
  • employeeID = UCPath if converted, Legacy HCM if not converted

---Before Go-Live---

  • employeenumber = HCM Employee Number
  • HCMID = HCM Employee Number
  • UCPathID not present

CALDAP Testing Attributes

Attributes for UCPathIDs in CALDAP_TEST

  • UCPathID
  • UCPathITID
  • UCPathUATID

We expect that UCPathID = UCPathITID  during integration testing, and for it switch UCPathID = UCPathUATID  during UAT

Attributes for UCPathIDs in CALDAP_DEV

  • UCPathID
  • UCPathDevID

We expect UCPathID = UCPathDevID

CALDAP changes, while in DEV and TEST, will be updated once a day, at 7 am PST.

For additional questions, please contact the Database Team at dbticket@berkeley.edu.

Which production data snapshots will be used during UAT?

During UAT (User Acceptance Testing), the production snapshots used during PPT3 (Payroll Parallel Test) are expected to be in effect during UAT.  The snapshot dates are listed below:

  1. Monthly 
    1. October 23:  Legacy PeopleSoft HCM 
    2. October 24:  PPS 
  2. Bi-Weekly
    1. November 6:  Legacy PeopleSoft HCM 
    2. November 7:  PPS