1 / 14

TMS and Oracle Integration for HR Records and Assignments

Learn about the integration between TMS and Oracle for HR records and assignments, including common issues, how to handle changes, and who to contact for help.

bdelacruz
Télécharger la présentation

TMS and Oracle Integration for HR Records and Assignments

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. TMS and Oracle Intersection April 13, 2016

  2. Topics TMS → Oracle • Person Record • Assignment Record • Common Issues TMS ← Oracle • Positions • Users Communication Questions

  3. TMS → Oracle • Nightly file of approved Hiring Proposals (Status: “Hired”) • New hires • New assignments (new to Employee Group or currently terminated) • NOT assignment changes • Faculty, State Classified, AP, and Postdocs

  4. TMS → Oracle • Person fields that integrate • Name • Social Security Number • Date of Birth • Demographics (including gender, race/ethnicity, disability status, and veteran status) • Home Address • Working Title

  5. TMS → Oracle • Assignment fields that integrate • Start Date • Position Number • Employee Group • Job Classification • Salary Basis (12-month or 9-month) • Employment Category (Regular/Special/Temp) • Department • FTE • Salary or Pay Rate

  6. TMS → Oracle • Assignment fields that DON’T integrate • Supervisor • Appointment End Date • Location (if not default)

  7. Oracle Action Required • Double-check data entry • Consider address update • Consider Working Title • Enter Supervisor • Enter Appointment End Date (if applicable) • Create Labor Schedule • Submit for approval (shortened process)

  8. Common Integration Issues • FTE field (range or explanation) • Mismatch between SSN and DOB or last name • Existing assignment in same employee group (assignment change required) • Change to person record on same or future effective date • Working Title too long(over 75 characters; 30 recommended) • Foreign addresses

  9. How to Handle Changes Change to start date • Alert HR Records so the assignment can be deleted • Create new Hiring Proposal Change to any other field • Two options: process above or PFD

  10. TMS ← Oracle Position fields • Status (active or inactive) • Department • Job classification • Incumbent employee • Supervisory position • Employee category (Regular/Special/Temp) • FLSA designation

  11. TMS ← Oracle User fields • Status (active or inactive) • Department • Name • Email address • Supervisor

  12. Who to Ask for Help Unknown integration errors: • HR_IS@mail.colostate.edu Corrections to Hiring Proposal and integration: • OEO@colostate.edu • HR_Records@mail.colostate.edu

  13. Communication New listserv • Daily TMS → Oracle integration report • Department, Job Classification, Working Title: success/failure message

  14. Questions for US?

More Related