Rp Hcmrs Upgrade Supplemental

Recruiting Solution

By: Jamuna Dinnepati, Sonu Nayar, Benjamin Harr, Vinay VSundaresan, Nancy Li, Donald Knapp

PeopleSoft Red Paper Series

s 8.9 Upgrade Supplemental

egunta, Satish Sallakonda, Malathy , Darren Guilbert, Michael Kennedy

April 2005

Recruiting Solutions 8.9 Upgrade Supplemental

Copyright © 2005, Oracle. All rights reserved. The information contained in this document is proprietary and confidential to Oracle. No part of this document may be reproduced or transmitted in any form or by any means, electronic or mechanical, including photocopying and recording, for any purpose without the express written permission of Oracle. This document is provided for information purposes only and the contents hereof are subject to change without notice. This document is not warranted to be error-free, nor subject to any other warranties or conditions, whether expressed orally or implied in law, including implied warranties and conditions of merchantability or fitness for a particular purpose. We specifically disclaim any liability with respect to this document and no contractual obligations are formed either directly or indirectly by this document. This document may not be reproduced or transmitted in any form or by any means, electronic or mechanical, for any purpose, without our prior written permission. Oracle, JD Edwards, and PeopleSoft are registered trademarks of Oracle Corporation and/or its affiliates. Other names may be trademarks of their respective owners.

.

Table of Contents

TABLE OF CONTENTS........................................................................................................................................................... 3

CHAPTER 1 - INTRODUCTION............................................................................................................................................ 5 Structure of this Red Paper....................................................................................................................................................... 5 Related Materials ....................................................................................................................................................................... 5

APPLICANT MANAGER ........................................................................................................................................................ 7 Tables mapping old to new schema .......................................................................................................................................... 7

APPLICANT TRACKING ..................................................................................................................................................... 11 Tables mapping old to new schema ........................................................................................................................................ 11

BUSINESS OBJECTS ............................................................................................................................................................. 15 Table/Field mapping old to new schema................................................................................................................................ 15

INTERVIEWS.......................................................................................................................................................................... 17 Tables mapping old to new schema ........................................................................................................................................ 17

JOB OPENING ........................................................................................................................................................................ 22 Tables mapping old to new schema ........................................................................................................................................ 22

OPEN INTEGRATION FRAMEWORK .............................................................................................................................. 26 Tables mapping old to new schema ........................................................................................................................................ 26

COMMON COMPONENTS................................................................................................................................................... 32 Table/Field mapping old to new schema................................................................................................................................ 32

COMMON COMPONENTS: APPROVALS........................................................................................................................ 36 Approval Value Mapping....................................................................................................................................................... 36

Table/Field mapping old to new schema................................................................................................................................ 36 Approval Tables Deleted in 8.9 ............................................................................................................................................. 36

EMPLOYEE REFERRAL PROGRAM (ERP) .................................................................................................................... 37 Table/Field mapping old to new schema................................................................................................................................ 37

APPENDIX 1: IMPORTANT NOTES .................................................................................................................................. 40

3

Recruiting Solutions 8.9 Upgrade Supplemental 8/4/2006

SYNCHRONIZING COUNTERS.......................................................................................................................................... 40 MANAGE HIRES.................................................................................................................................................................... 40 OFFERS.................................................................................................................................................................................... 40 STATUSES MAPPING ........................................................................................................................................................... 41 SITE SECURITY..................................................................................................................................................................... 41 APPLICANT NAME ............................................................................................................................................................... 41 APPLICATION LAST UPDATED BY.................................................................................................................................. 41 FIND APPLICANTS ............................................................................................................................................................... 41 APPLICANT PHONES........................................................................................................................................................... 42 APPLICANT ID....................................................................................................................................................................... 42 CONTRACT DATA APPLICATION DATE........................................................................................................................ 42 JOB OPENING SECURITY................................................................................................................................................... 42 DEFAULT JOB POSTING TEMPLATES ........................................................................................................................... 42 LOCATIONS AND SETID/BUSINESS UNIT...................................................................................................................... 45 FILE ATTACHMENTS .......................................................................................................................................................... 46 POSTING TO THIRD PARTY JOB BOARDS.................................................................................................................... 47


Chapter 1 - Introduction

This Red Paper is a practical guide for technical users, installers, system administrators, and programmers who implement, maintain, or develop applications for your PeopleSoft system. In this Red Paper, we hope to provide some insight and guidance into the upgrade to Recruiting Solution 8.9; in part, this paper was developed because of the scope of change between RS 89 and previous versions of the product. Every table has been modified or renamed, so as opposed to many releases, the upgrade involves significantly more than just a straightforward record-to-record mapping. One benefit of this renaming is that every table that is owned by Recruiting Solutions is now prefixed with “HRS_” (e.g., HRS_APPLICANT). This makes understanding the domain of the RS tables much easier and the relationship between tables more clear.

The scope of change at the table level stems from the wide scale architectural and functional changes implemented in RS 89, which in turn will provide significant benefits in usability, performance, and overall quality of the Recruiting Solutions product.

RS 89 was developed using the concept of Componentization; that is, the use of discrete components or modules that encompass specific data, transactions and/or business processes. These components exchange data both between themselves (internal to the product) and with outside entities (other applications) through clearly defined and contracted interfaces, whether those are simple SQL views or a more complex mechanism like application messages. Though the structures handling the data (tables, etc.) may change, these interfaces do not change – this allows for a much more stable environment, easier to maintain and more extensible.

We would recommend that this Red Paper be reviewed prior to beginning the upgrade process, and then used as a resource throughout the process. We hope that it will be useful, and have made it as inclusive and accurate as possible as of the time of this writing.

STRUCTURE OF THIS RED PAPER

This Red Paper is divided (more or less) by Component (see section above), with each section containing some introductory information or notes about the component and a grid showing table (and in some cases table.field) mappings.

At the end of the paper, an Appendix includes several important Notes that give further details about several specific areas of upgrade. Please review the Appendix carefully as the information contained in it will contribute to the success of your upgrade.

RELATED MATERIALS

The Recruiting Solutions development staff have also authored a number of other technical Red Papers that, while not specific to Upgrade, may also be beneficial to you in understanding the new architecture and functionality of Recruiting Solutions 8.9

Primary among them is the Recruiting Solutions 8.9 Technical Overview, which provides details about the overall architecture of RS 89 as well as delving into specifics about each component.

Other papers include:

Recruiting Solutions 8.9 Application Class Registry Red Paper

Recruiting Solutions 8.9 Approvals Framework Red Paper

Recruiting Solutions 8.9 Autoscreening Red Paper

Recruiting Solutions 8.9 Creating A New Transaction Group Red Paper

© Copyright Oracle Corporation 2005. All rights reserved. 5


Recruiting Solutions 8.9 Data Mapping Red Paper

Recruiting Solutions 8.9 Globalizations Red Paper

Recruiting Solutions 8.9 Hire Integration Customization Red Paper

Recruiting Solutions 8.9 HRXML Mappings Red Paper

Recruiting Solutions 8.9 Integrations Setup Red Paper

Recruiting Solutions 8.9 Online Letter Generation Red Paper

Recruiting Solutions 8.9 Payroll for NA Integration Set Up Red Paper

Recruiting Solutions 8.9 Status Effects Red Paper

Recruiting Solutions 8.9 Verity Red Paper

These papers are or will shortly be available in Customer Connection. In addition, customers may want to request the Entity Relationship Diagrams (ERDs) for RS 89, available through GSC.

Please note that this paper is not a general introduction to Recruiting Solutions functionality, PeopleTools, or environment tuning and we assume that our readers are experienced IT professionals, with a good understanding of PeopleSoft’s Internet Architecture. To take full advantage of the information covered in this document, we recommend that you have a basic understanding of system administration, basic Internet architecture, relational database concepts/SQL, and how to use PeopleSoft applications.

The functionality of Recruiting Solutions 8.9 is discussed in the following PeopleSoft PeopleBooks:

• PeopleSoft Enterprise Talent Acquisition Manager 8.9

• Peoplesoft Enterprise Candidate Gateway 8.9

Many of the fundamental concepts related to PIA are discussed in the following PeopleSoft PeopleBooks:

• PeopleSoft Internet Architecture Administration (PeopleTools|Administration Tools|PeopleSoft Internet Architecture Administration)

• Application Designer (Development Tools|Application Designer)

• Application Messaging (Integration Tools|Application Messaging)

• PeopleCode (Development Tools|PeopleCode Reference)

• PeopleSoft Installation and Administration

• PeopleSoft Hardware and Software Requirements



Applicant Manager

The Applicant Manager component handles data related to applicants and their applications. Among the significant changes in Recruiting Solutions 8.9:

• Applicants can now apply multiple times on the same day using different applicants (in previous version, only one application per day could be saved, and any changes would overwrite previous applications for that day)

• Applicant profile information (name, address, phone, email) is decoupled from applications, so that profile information only need be entered once; via the Careers page (Apply On-Line), Applicants can create a profile without applying. This allows applicants to save a profile for later use while making use of utilities such as job search agent

• Applicants can “apply” without applying for a specific job opening; that is, they can simply submit a resume or application in order to “get into the system”

• See Appendix 1 for other notes around the upgrading of applicants and applications.

TABLES MAPPING OLD TO NEW SCHEMA

Key table changes are listed here. All other table changes are a result of the rename or high-level key change.

Table Name Description New/Modify

HRS_APPLICANT Previously APPLICANT. Replace/Modify

HRS_APP_ACMDIAG Previously APP_ACCOM_DIAG Replace/Modify

HRS_APP_ACMOPTN APP_ACCOM_OPTN Replace/Modify

HRS_APP_ACMP APP_ACCOMPS Replace/Modify

HRS_APP_ACMRQST APP_ACCOM_RQST Replace/Modify

HRS_APP_ACM_LNG APP_ACCOMP_LNG Replace/Modify

HRS_APP_ADDRESS APPLICANT_DATA Replace/Modify

HRS_APP_ANSWER ER_APP_ANSWERS Replace/Modify

HRS_APP_AOP_LNG APP_ACM_OPT_LNG Replace/Modify

HRS_APP_AREASDY APP_ED_AREA_SDY Replace/Modify

HRS_APP_ATTACH ER_APP_ATTACH Replace/Modify

HRS_APP_BNKACCT APP_BANKACCT Replace/Modify

HRS_APP_CAN APPL_DATA_EFFDT Replace/Modify

HRS_APP_CEV_LNG APP_CM_EVAL_LNG Replace/Modify

HRS_APP_CHE APPL_DATA_EFFDT Replace/Modify



HRS_APP_CITSHIP APP_CITIZENSHIP Replace/Modify

HRS_APP_CMP APP_COMPS Replace/Modify

HRS_APP_CM_EVAL APP_CM_EVALS Replace/Modify

HRS_APP_CNTRACT APP_CNT_DATA Replace/Modify

HRS_APP_CNT_CLS APP_CNT_CLAUSE Replace/Modify

HRS_APP_CPS_LNG APP_CIT_PSP_LNG Replace/Modify

HRS_APP_CZ_PSPT APP_CITIZN_PSPT Replace/Modify

HRS_APP_DIS APP_DISABILITY Replace/Modify

HRS_APP_DIS_CHE APP_DISABL_CHE Replace/Modify

HRS_APP_DIS_ESP APP_DISABL_ESP Replace/Modify

HRS_APP_DIS_FRA APP_DISABL_FRA Replace/Modify

HRS_APP_DIS_GER APP_DISABL_GER Replace/Modify

HRS_APP_DIS_NLD APP_DISABL_NLD Replace/Modify

HRS_APP_DIS_NZL APP_DISABL_NZL Replace/Modify

HRS_APP_DIV APP_DIVERSITY Replace/Modify

HRS_APP_DIV_ETH APP_DIVER_ETHNC Replace/Modify

HRS_APP_DIV_REL APP_DIVER_RELIG Replace/Modify

HRS_APP_DSTNCT ER_APP_DISTINCT Replace/Modify

HRS_APP_EFFDT No Source Table New

HRS_APP_EMAIL No Source Table New

HRS_APP_ESP No Source Table New

HRS_APP_FRA No Source Table New

HRS_APP_GER No Source Table New

HRS_APP_HST No Source Table New

HRS_APP_ITA No Source Table New

HRS_APP_JPN No Source Table New

HRS_APP_NAMES No Source Table New

HRS_APP_NAT_GER No Source Table New

HRS_APP_NID No Source Table New

HRS_APP_ORIG_CH No Source Table New



HRS_APP_PHONE No Source Table New

HRS_APP_PRF_VER DELETED

HRS_APP_PROFILE No Source Table New

HRS_APP_PROXY DELETED

HRS_APP_PWE_LNG APP_PRWK_EX_LNG Replace/Modify

HRS_APP_REF No Source Table New

HRS_APP_REFCRSP No Source Table New

HRS_APP_REF_LNG APP_REFRNCE_LNG Replace/Modify

HRS_APP_REG No Source Table New

HRS_APP_RES No Source Table New

HRS_APP_SCHL No Source Table New

HRS_APP_SCH_LNG APP_SCHEDUC_LNG Replace/Modify

HRS_APP_TRAIN No Source Table New

HRS_APP_USA No Source Table New

HRS_APP_VPM_LNG APP_VSA_PMT_LNG Replace/Modify

HRS_APP_VSA_DAT No Source Table New

HRS_APP_VSA_SPT No Source Table New

HRS_APP_WRK_EXP No Source Table New

HRS_APP_ZONE No Source Table New

HRS_AP_APP_TMP No Source Table New

HRS_AP_EDU_TMP No Source Table New

HRS_AP_PHN_TMP No Source Table New

HRS_AP_WRK_TMP No Source Table New

HRS_ATTACHMENTS No Source Table New

HRS_ATT_TYP_TBL No Source Table New

HRS_DPTPOP_AET No Source Table New

HRS_DUP_APP_AET No Source Table New

HRS_DUP_APP_SET DUPLCT_APP_SET Replace/Modify

HRS_DUP_APP_TAO No Source Table New

HRS_DUP_CMNDT ER_DUP_COMMONDT Replace/Modify



HRS_DUP_RECS ER_DUP_RECORDS Replace/Modify

HRS_DUP_SET_TBL DUPLICATE_SET Replace/Modify

HRS_HRAM_COUNT No Source Table New

HRS_PL_STATE No Source Table New

HRS_RESTMPL_LNG ER_RES_TMPL_LNG Replace/Modify

HRS_RES_OPTN No Source Table New

HRS_RES_SECTION No Source Table New

HRS_RES_TMPL No Source Table New

HRS_RES_TMPL_PG No Source Table New



Applicant Tracking

The Applicant Tracking component handles data around an applicant’s status in relation to a job opening on the continuum of statuses; this includes statuses related to routing, interview, offer, screening, etc.

One important change in statuses in Recruiting Solutions 8.9 is the addition of a new status, 071 – Offer Accepted. This status has been added to allow for a transitional stage between Offer and Ready to Hire; in previous releases, a Ready to Hire status meant that an applicant could be handled by an HR specialist and hired. The new Manage Hire functionality in release 8.9 requires a status prior to Ready to Hire that indicates to a recruiter that an applicant has accepted the offer but in which stage the applicant’s data is still editable, as Ready to Hire triggers an application message to HRMS and makes the applicant data view-only. To accommodate this requirement, during the upgrade process applicants with a status of 080-Ready to Hire will be upgraded to a status of 071-Offer Accepted, which provides the equivalent functional status.

For more information, please see Appendix 1. For more information on the upgrade of the Manage Hire functionality, please see the Business Objects chapter. Tables mapping old to new schema




HRS_ANS_LNG Previously ER_ANSWER_LNG Replace/Modify

HRS_ANS_TBL ER_ANSWER_TBL Replace/Modify

HRS_APP_CHK_LNG APP_CHECK_LANG Replace/Modify

HRS_APP_EXP APP_EXPENSES Replace/Modify

HRS_APP_RTE APPLICATN_ROUTE Replace/Modify

HRS_APP_RTE_DTL APPLICATN_ROUTE Replace/Modify

HRS_CHKLST No Source Table New

HRS_CHKLST_ITM No Source Table New

HRS_CHKLST_LNG No Source Table New

HRS_EVAL_CATG ER_INTVW_EVAL ER_INTERVIEW

New

HRS_EVL_DFN_LNG ER_INT_EVL_LNG Replace/Modify

HRS_G_PR_LNG GVT_PRIO_LANG Replace/Modify

HRS_G_PR_PL_TBL GVT_PRIO_TBL Replace/Modify

HRS_G_VTPRF_LNG GVT_VETPREF_LNG Replace/Modify

HRS_G_VTPRF_TBL GVT_VETPREF_TBL Replace/Modify



HRS_HRAT_COUNT No Source Table New

HRS_INTEVLCT_LG ER_INT_EVLCT_LG Replace/Modify

HRS_INTEVLRN_LG No Source Table New

HRS_INTEVLRT_LG ER_INT_EVLRT_LG Replace/Modify

HRS_INT_ATCH No Source Table New

HRS_INT_CTG_TBL ER_INT_EVL_CATG Replace/Modify

HRS_INT_EVAL ER_INTVW_EVAL ER_INTERVIEW

Replace/Modify

HRS_INT_EVL_CTG ER_INT_EVL_CATG Replace/Modify

HRS_INT_EVL_DFN ER_INT_EVL_DEFN Replace/Modify

HRS_INT_EVL_RMD ER_INT_EVL_RCMD Replace/Modify

HRS_INT_EVL_RSN ER_INT_EVL_RSNS Replace/Modify

HRS_INT_EVL_RTG ER_INT_EVL_RTG Replace/Modify

HRS_INT_LTR ER_INTERVIEW Replace/Modify

HRS_INT_LVL_LNG No Source Table New

HRS_INT_LVL_TBL No Source Table New

HRS_INT_NOTE No Source Table New

HRS_INT_RTG_TBL ER_INT_EVL_RTG Replace/Modify

HRS_INT_SCHED ER_INTVW_SCHED ER_INTERVIEW

Replace/Modify

HRS_INT_SEQ No Source Table New

HRS_INT_STS ER_INTVW_STATUS ER_INTERVIEW

Replace/Modify

HRS_LAUNCH_TMP No Source Table New

HRS_OFFER OFFER JOB_REQUISITION

Replace/Modify

HRS_OFFER_STA HR_OFFER_STA Replace/Modify

HRS_OFF_ATCH No Source Table New

HRS_OFF_CMPNT OFFER_CMPNT_TBL Replace/Modify

HRS_OFF_C_LNG OFFER_CMPNT_LAN Replace/Modify

HRS_OFF_DTL

OFFER JOB_REQUISITION OFFER_DTL

Replace/Modify



HRS_OFF_LTR No Source Table New

HRS_OFF_NOTE

OFFER JOB_REQUISITION OFFER_COMM

Replace/Modify

HRS_OFF_NOT_LNG No Source Table New

HRS_OFF_STS

OFFER JOB_REQUISITION OFFER_STATUS

Replace/Modify

HRS_OFF_STTS No Source Table New

HRS_OFF_SUB_WL No Source Table New

HRS_OFF_TP_LNG OFFER_TYPE_LANG Replace/Modify

HRS_OFF_TYPES OFFER_TYPE_TBL Replace/Modify

HRS_QSET_QSTN ER_QSTNSET_QSTN Replace/Modify

HRS_QSTNSET_LNG ER_QSTN_SET_LNG Replace/Modify

HRS_QSTN_ANS ER_QSTN_ANS_TBL Replace/Modify

HRS_QSTN_LNG ER_QUESTION_LNG Replace/Modify

HRS_QSTN_SET ER_QSTN_SET_TBL Replace/Modify

HRS_QSTN_TBL ER_REQ_QUESTNS Replace/Modify

HRS_RCMNT POSN_APPLIEDFOR Replace/Modify

HRS_RCMNT_JOB GVT_APPL_CONSID GVT_PSN_APPLFOR

Replace/Modify

HRS_RCMNT_LTR POSN_APPLIEDFOR Replace/Modify

HRS_RCMNT_STS ER_POSN_STATUS Replace/Modify

HRS_RCM_INT ER_INTERVIEW Replace/Modify

HRS_RCM_JOB_STS No Source Table New

HRS_RCM_LTR_LNG No Source Table New

HRS_REC_STATDEC No Source Table New

HRS_REC_STS_TBL REC_STATUS_TBL Replace/Modify

HRS_RTE_DTL_STS ER_ROUTE_STATUS Replace/Modify

HRS_RTE_STS APPLICATN_ROUTE ER_ROUTE_STATUS

Replace/Modify

HRS_RUN_CE RUN_CNTL_PRT_CE Replace/Modify

HRS_RUN_CR_JOB No Source Table New



HRS_RUN_EC RUN_CNTL_PRT_EC Replace/Modify

HRS_RUN_PRI_PLC No Source Table New

HRS_RUN_SCR No Source Table New

HRS_SCR_HIST No Source Table New

HRS_SCR_RSLT ER_SCR_RESULTS Replace/Modify



Business Objects

The Business Objects component handles data that intersects directly with HRMS. In particular, this component controls the integration with HRMS via the Manage Hire functionality.

In previous releases, applicants were, in a sense, “hired” from within the Recruiting Solutions product, and HRMS tables were updated directly.

In Recruiting Solutions 8.9, the Hire process marks the boundary between Recruiting Solutions and HRMS (Develop Workforce). An applicant progress through statuses until they reach Ready for Hire. When an applicant is moved to the Ready for Hire status, an application message notifies HRMS (via integration broker), and the applicant is hired via the Manage Hires component in Developer Workforce; when that process is complete, HRMS notifies Recruiting Solutions. Thus, the actual Hire functionality now takes place entirely within the HRMS functional domain, as is appropriate based on standard business processes.

Please see Appendix 1 for further information about the implications of this architectural change.

TABLE/FIELD MAPPING OLD TO NEW SCHEMA



HRS_HIRE

Hire Table.

HRS_HIRE is a new table. This table contains recruitment data for applicants in Ready To Hire status

HRS_RCMNT and HRS_JOB_OPENING tables are the source tables for HRS_HIRE upgrade.

Applicants in “ 90- Ready to Hire” Status are selected from HRS_RCMNT and HRS_JOB_OPENING tables and inserted in to HRS_HIRE table during upgrade.

APPLICANT_TYPE and HIRE_TYPE fields are updated from HRS_APPLICANT table.

APPLICANT_TYPE is set to ‘E’ and HIRE_TYPE is set to ‘W’ where APP_PER_STATUS is ‘A’ or ‘N’ in HRS_APPLICANT table

New



APPLICANT_TYPE is set to ‘I’ and HIRE_TYPE is set to ‘H’ where APP_PER_STATUS is ‘E’ in HRS_APPLICANT table

The EMPLID is updated from HRS_APPLICANT table for the corresponding HRS_PERSON_ID in HRS_RCMNT table.

HRS_HIRE_CNTR

Hire Counter table

Counter table for Hire sequence.

New

HRS_HIRE_HST This is the archive table for HRS_HIRE table. New

HRS_MNG_HIR_STP Manage Hire Setup table. Supports hire setup to choose what data can be transferred to HR during Hire New



Interviews

The structure of Interviews (part of the Applicant Tracking component) was modified to align with the new architecture of Recruiting Solutions in Release 8.9. This necessitated, among other things, a remapping of some old statuses/values to new values being used in Release 8.9. The table below documents those changes.

In additions, changes in the structure Interviews between release 8.0 and releases 8.3/8.8 necessitated differences in the upgrade path. Unless otherwise noted, the upgrade path described is from Release 8.3/8.8.


Key table changes are listed here.

Table Name (Path)

Description New/Modify

HRS_RCM_INT (8)

Recruitment Interview table.

HRS_RCM_INT is a new table.

INTERVIEW, UPG_ER_STATUS, HRS_RCMNT, HRS_APPLICANT and HRS_APP_PROFILE are the source tables for HRS_RCM_INT upgrade.

Interviews are selected from INTERVIEW and inserted into HRS_RCM_INT with a status code of ‘010’ during the upgrade.

Only the most recent interview row from INTERVIEW is retained if there are multiple interviews with a RECOMMENDATION of Y for the same APPLID, APP_DT and JOB_REQ_NBR.

New

HRS_INT_LTR (8)

Recruitment Interview Letter table

INTERVIEW, HRS_RCMNT, HRS_APPLICANT and HRS_APP_PROFILE are the source tables for HRS_RCM_INT upgrade.

New



HRS_INT_SCHED (8)

APP_INTVW_TIMES, HRS_RCMNT and HRS_APPLICANT are the source tables for HRS_INT_SCHED upgrade.

New

HRS_INT_EVAL (8)

INTERVIEW table RATING is set to ‘2’ if it is blank before this table is upgraded.

INTERVIEW, HRS_RCMNT, HRS_APPLICANT and HRS_RCM_INT are the source tables for HRS_INT_EVAL upgrade.

If INTVW_RATING_OVER = ‘3’ then it is set to ‘3’



If RECOMMENDATION = ‘F’ Then set RECOMMENDATION = ‘3’

If RECOMMENDATION = ‘I’ Then set RECOMMENDATION = ‘4’

If RECOMMENDATION = ‘O’ Then set RECOMMENDATION = ‘5’

If RECOMMENDATION = ‘R’ Then set RECOMMENDATION = ‘2’

New

HRS_INT_STS (8)

Interview Status Table.

INTERVIEW, HRS_RCMNT, HRS_APPLICANT and UPG_ER_STATUS are the source tables for HRS_INT_STS upgrade.

Previous STATUS_CODE values are mapped as per the data entered on the upgrades page UPG_ER_STATUS

New



HRS_EVAL_CATG (8)

Interview Evaluation Categories Ratings

HRS_INT_EVAL is the source table for HRS_EVAL_CATG upgrade.

Replace/Modify

HRS_INT_EVL_DFN

Interview Evaluation Template

ER_INT_EVL_DEFN is the source table for HRS_INT_EVL_DFN upgrade.

Replace/Modify

HRS_INT_EVL_RMD

Interview Evaluation Recommendation

ER_INT_EVL_RCMD is the source table for HRS_INT_EVL_RMD upgrade

Replace/Modify

HRS_INT_CTG_TBL

Interview Categories Setup Table

ER_INT_EVL_CATG is the source table for HRS_INT_CTG_TBL upgrade.

Gets descriptions from ER_INT_EVL_CATG where SELECTED = ‘Y’

Replace/Modify

HRS_INT_EVL_CTG

Interview Evaluation Categories table

ER_INT_EVL_CATG and HRS_INT_CTG_TBL tables are the source tables for HRS_INT_EVL_CTG upgrade.

Replace/Modify

HRS_INT_EVL_RSN

Interview Evaluation Reasons

ER_INT_EVL_RSNS is the source table for HRS_INT_EVL_RSN upgrade.

ER_INT_EVL_RSNS rows are selected where SELECTED = ‘Y’

Replace/Modify



HRS_INT_RTG_TBL

Interview Rating Setup Table

ER_INT_EVL_RTG is the source table for HRS_INT_RTG_TBL upgrade.

Get Descriptions and Rating from ER_INT_EVL_RTG where SELECTED = ‘Y’

Replace/Modify

HRS_INT_EVL_RTG

Interview Evaluation Template Ratings

ER_INT_EVL_RTG and HRS_INT_RTG_TBL are the source tables for HRS_INT_EVL_RTG upgrade

Rows are selected where ER_INT_EVL_RTG SELECTED = ‘Y’

Replace/Modify

HRS_EVL_DFN_LNG

Interview Evaluation template related Lang

ER_INT_EVL_LNG is the source table for the HRS_EVL_DFN_LNG upgrade

Replace/Modify

HRS_INTEVLCT_LG (8.8 only)

Setup Interview Categories Related Lang

ER_INT_EVLCT_LG LNG is the source table for the HRS_INTEVLCT_LG upgrade

Replace/Modify

HRS_INTEVLRT_LG (8.8 only)

Interview Rating Setup Related Lang

ER_INT_EVLRT_LG and HRS_INT_EVL_RTG are the source tables for the HRS_INTEVLRT_LG upgrade.

Replace/Modify

HRS_RCM_INT

Recruitment Interview Table

ER_INTERVIEW, HRS_RCMNT, HRS_APPLICANT and HRS_APP_PROFILE are the source tables for the HRS_RCM_INT upgrade.

New



HRS_INT_LTR

Interview Letters

ER_INTERVIEW, HRS_RCMNT, HRS_APPLICANT and HRS_APP_PROFILE are the source tables for the HRS_INT_LTR upgrade

New

HRS_INT_SCHED

Interview Schedule

ER_INTVW_SCHED, HRS_RCMNT and HRS_APPLICANT are the source tables for the HRS_INT_SCHED upgrade.

Replace/Modify

HRS_INT_EVAL

Interview Evaluations

ER_INTVW_EVAL, HRS_RCMNT and HRS_APPLICANT are the source tables for the HRS_INT_EVAL upgrade

Replace/Modify

HRS_INT_STS

Interview Status

ER_INTVW_STATUS, HRS_RCMNT and HRS_APPLICANT are the source tables for the HRS_INT_EVAL upgrade

Replace/Modify

HRS_EVAL_CATG

Interview Evaluation Categories Ratings

ER_INTVW_EVAL, HRS_RCMNT, HRS_APPLICANT and HRS_INT_EVAL are the source tables for HRS EVAL_CATG upgrade.

New



Job Opening

The Job Opening component handles data related to job openings and screening.

In Recruiting Solutions 8.9, the concept of a job requisition has been expanded to allow for more flexibility in the definition, tracking and filling of an “open job.” This now includes not only standard job requisitions, but also continuous job openings for positions that are constantly in need of filling or in which turnover is consistently high and recruiters do not want to constantly open new requisitions. In addition, a job opening can now support multiple positions.

Screening has also been opened up in Recruiting Solutions 8.9, so that many of the concepts and functionality that previously were only available to Federal/government installations of Recruiting Solutions are now available to commercial installations as well.

Note that row-level security around Job Openings has changed significantly. Please see Appendix 1 for further information




HRS_JOB_OPENING

Job Opening table.

Previously JOB_REQUISITION.

Job opening type is added to support non-requisition based openings.

Field JOB_REQ_NBR is converted from a char(6) to number(15).

Replace/Mod

HRS_JO_POSN

Job Opening Positions.

Previously GVT_RQSN_POSN.

This table supports multiple positions for each job opening.

Replace/Mod

HRS_JO_LOC

Job Opening Locations.

Previously GVT_RQSN_OPNGS.

This table supports multiple locations for each job opening.

Replace/Mod

HRS_JO_RQMT Job opening standard requirements. Replace/Mod



Previously GVT_RESN_JOBCD

HRS_JO_CMP

Job opening competency requirements.

Previously JOB_RQMT_COMP.

Requirements are now associated with the job opening rather than the screening level.

Replace/Mod

HRS_JO_ACMP Job opening accomplishment requirements.

Previously JOB_RQMT_ACCOMP. Replace/Mod

HRS_JO_EDUC_EXP Job opening education and experience requirements.

Previous JOB_REQ_EDUC_EX. Replace/Mod

HRS_JO_QSTN Job Opening Question.

Previous ER_REQ_QUESTNS. Replace/Mod

HRS_JO_ANS Job opening answers requirements.

Previous ER_REQ_ANSWERS. Replace/Mod

HRS_SCREEN_TBL Screening setup including scoring methodology including transmutation and percentage calculation. New

HRS_JO_SCR_SUMM

Partially represents JOB_RQMT_TBL and GVT_RQSN_JOBCD. The recruitment template defaults the screening levels from the screening template into this table. It allows overwriting of the scoring methodology.

It is not necessary to have a job code or a job opening to perform screening. This allows screening to be done for job postings that do not have a job code defined. It also allows for the flexibility of defining screening criteria without a job opening, which can be used when applicants apply generically, and not to any specific jobs.

Replace/Mod

HRS_JO_SCR_LVL

Associates screening levels to template.

Previously JOB_RQMT_TBL, ER_STS_FSCR_TBL and, GVT_RQSN_JOBCD

Replace/Mod

HRS_JO_SCR_CMP Job opening competency screening criteria.

Previously JOB_RQMT_COMP. Replace/Mod



HRS_JO_SCR_ACMP Job opening accomplishment screening criteria.

Previously JOB_RQMT_ACMP. Replace/Mod

HRS_JO_SCR_EDEX

Job opening education and years of experience screening criteria.

Previously JOB_REQ_EDUC_EX.

Replace/Mod

HRS_JO_SCR_QSTN Job opening screening questions for screening criteria.

Previously ER_REQ_QUESTNS. Replace/Mod

HRS_JO_SCR_ANS

Job opening answers to screening questions in screening criteria.

Previously ER_REQ_ANSWERS.

Replace/Mod

HRS_JO_POSTING Previously JOB_REQUIS_TYP and also merges in federal record GVT_JOB_POSTING. You can have multiple posting entities.

Replace/Mod

HRS_JO_DSC_TYP Job Opening Description Types.

Previously ER_REQ_DESCR_TP. Replace/Mod

HRS_JO_PST_DSCR Previously JOB_REQ_DESCRS. This is no longer identified directly with the job opening. Instead it is linked to the posting.

Replace/Mod

HRS_JO_PST_DST Previously JOB_REQUIS_TYP. This is no longer identified directly with the job opening. Instead it is linked to the posting.

Replace/Mod

HRS_JO_TMPL_SCT Job opening template sections.

Previously ER_REQ_TMPL_PGS Replace/Mod

HRS_JO_TMPL_PG Job opening template pages.

Previously ER_REQ_TMPL_PGS Replace/Mod

HRS_JO_PST_TMPL Posting template for job opening.

Previously GVT_VA_OPTIONS. Replace/Mod

HRS_JO_TMPL Job opening template.

Previously ER_REQ_TMPL_TBL. Replace/Mod

HRS_RCRT_TMPL Recruitment template.

Previously ER_RCRT_TMPL. Replace/Mod

HRS_SCR_TMPL Screening template used to default into job opening screening summary. New



HRS_JO_TEAM

Captures team members for interview, hiring manager, recruiter, and interested party teams. ER_REQ_INTVW_TM and JOB_REQ_STATUS will be upgraded to this table.

Replace/Mod

HRS_TEAM Team description New

HRS_TEAM_MEMBER Team members of the team New

HRS_JO_NOTE Notes for the job opening New

HRS_JO_ATCH Attachments for the job opening New

HRS_JO_NAME Candidate name requests for the job opening.

Previously GVT_RQSN_NAMES Replace/Mod

HRS_JO_STS Job Opening Status.

Previously ER_REQ_STATUS Replace/Mod

HRS_G_JO_PRI Job Opening Priority Placement.

Previously GVT_RQSN_PRI_PL Replace/Mod

HRS_JO_RPL Job Opening Replacements.

Previously ER_REQ_POST_RPL Replace/Mod

HRS_JO_EXP Job Opening Expenses.

Previously ER_JOB_REQ_EXP Replace/Mod



Open Integration Framework

The Open Integration Framework is new to Recruiting Solutions 8.9, and provides a flexible, consistent method for integrating with external vendors. In the past, this integration had to be “hardcoded” so that customers either used the delivered integration/vendor, or had to customize to integrate with a different vendor.

With Recruiting Solutions 8.9, customers have the choice of which vendor they would like to use for Resume Extraction, Job Boards, and PreEmployment Checks. XML files and transformation layers provide the mapping from vendor systems into Recruiting Solutions, and a configuration file (produced by the vendor) allows for vastly simplified and faster vendor integration set up.




HRS_AL_LOG

Resume Extraction Log Table.

Previously group of Resume Queue tables RP_QUEUE_APP

RP_QUEUE_PHN

RP_QUEUE_WRKEXP

RP_QUEUE_EDU

PS_HRS_AL_LOG E HRS_AL_LOG_ID is a new key field. For each Resume number row in RP_QUEUE_APP a new HRS_AL_LOG_ID value is added

Replace/Mod

HRS_AL_LOG_RES

Resume Extract Log Resolution table. Tracks Resolution Statuses of Logs. HRS_AL_LOG_RES_ID is the key field For each row of HRS_AL_LOG_ID in HRS_AL_LOG table new HRS_AL_LOG_RES_ID is added. On Upgrade HRS_RESOLUTION field value is set to ‘30’ – Unresolved with error.

Replace/Mod



HRS_AL_LOG_SRCE

Resume Extraction Log Source. HRS_SUBSOURCE_DESC is a new field which was previously SPECIFIC_REFER_SRC on ER_REFERRAL.

Replace/Mod

HRS_APP_PREMPLD

Applicant pre employment status table. Contains summary status information for pre-employment subrequests for applicants. Previously ER_APP_PREEMPLD

HRS_PREMPL_PERS_ID is new Key field

Replace/Mod

HRS_APP_PREMPLH

Contains summary status information for pre-employment requests for applicants.

Previously ER_APP_PREEMPLH

HRS_PREMPL_PERS_ID is new Key field

ADJUDICATION_STS field size is increased from 1 to 50 characters.

The ‘N’ status is upgraded to ’Fail’ and ‘Y’ status is upgraded to ‘Pass’

Replace/Mod

HRS_MERCH_ACCT

Merchant accounts table

Stores information about accounts that are tied to merchants.

Previously MERCHANT_ACCT

Replace/Mod

HRS_SUBSOURCE

Referral Sub Source Table. Previously PS_ER_REF_SUBCAT

New numeric Filed HRS_SOURCE_ID is added and Previous REFERRAL_SOURCE value is upgraded to corresponding numeric values

Replace/Mod

HRS_SUBSRCE_LNG Sub Source Language table

Previously ER_REFSBCAT_LNG Replace/Mod

HRS_ACTYPE_LNG New

HRS_ACTYPE New

HRS_AL_LOG_EXTR RE Log Extractor Tracking New



HRS_AL_LOG_MAIL Resume extraction Log Mail table New

HRS_AL_LOG_NOTI Resume extraction Log Notification table New

HRS_ASCREEN_LNG AutoScreen Table New

HRS_ASCRN_APCLS AutoScreening AppClass New

HRS_ASCRN_SCRN Auto Screening - Screening New

HRS_AUTOSCREEN AutoScreen Table New

HRS_DM_CAT DataMapping Category New

HRS_DM_CAT_LNG DataMapping Category Language New

HRS_DM_KEY Data mapping Key Table New

HRS_DM_KEY_LNG Data mapping Key Language Table New

HRS_DM_MAPDEFN Data Mapping Definition Table New

HRS_DM_MAPD_LNG Data Mapping Definition Language table New

HRS_DM_RUNCTL Datamapping Run control table New

HRS_DM_UNMAPPED New

HRS_DM_VAL_SUGG New

HRS_DUPE_CRIT New



HRS_DUPE_MAP New

HRS_DUPE_MPRCS Duplicate Merge Process New

HRS_DUPE_PERSON Duplicate Set Person Matches New

HRS_DUPE_PRCS Duplicate Find/Merge Process New

HRS_DUPE_SET Duplicate Set New

HRS_EMAIL_ATTCH New

HRS_EMAIL_SETUP Email Setup New

HRS_EXTPOST_STS External Posting Status New

HRS_EXTPST_HIST External Posting History New

HRS_GVA_TRK_HST USA Job Tracking Table New

HRS_G_VA_TRK USA Job Tracking Table New

HRS_HROI_COUNT Unique ID Counter Table New

HRS_HROI_LOG Integration Log Table New

HRS_HROI_LOG_2 New

HRS_HRXML_PSTLI New

New HRS_HRXML_PSTLO New



HRS_JBBRD_VNDR Job Board Vendor Extensions New

HRS_OI_VALMAP Integration Values New

HRS_POST_LOG Job Board Transaction Log New

HRS_PREMPL_VNDR New

HRS_REGCODE_TBL New

HRS_RESLOAD New

HRS_RESLOAD_JOB New

HRS_RESLOAD_RES New

HRS_RESLOAD_SRC New

HRS_RESMAIL_RC New

HRS_RESUME_VNDR Vendor Resume Extension New

HRS_SOA_SRV SOA Service View New

HRS_SOURCE_SITE New

HRS_SUP_INFO New

HRS_TGROUP New

HRS_TGROUP_LNG New



HRS_TG_SERVICE New

HRS_VENDOR Vendor Table New

HRS_VENDOR_LNG Vendor-Transaction Language Table New

HRS_VNDR_TRANS Vendor-Transaction Table New

HRS_XML_STRING New

HRS_XSLT XSLT Table New

HRS_G_RCR_DSCR Recruiting Standard description table. Previously GVT_RECR_DESCR Replace/Mod



Common Components

The Common Components component handles data and transactions that intersect or interact with all or multiple other components through the Recruiting Solutions system; it includes Search (including automatch and job agent), Approvals (see next chapter), Applicant Lists as well as installation data.

General notes:

1. Job Agent results from 8.8 are not upgraded (Job Agent Profiles are). Due to extensive changes in Job openings and the search engine itself – any job agents will be re-run after upgrade, thus refreshing all results and will notify applicants of any matches to establish a new baseline.

2. Automatch search from 8.3/8.8 has been incorporated into Recruiter Find Applicants search (and Automatch no longer exists under Setup)

3. All searches in 8.9 are associated with an owner (either an EMPLID or an HRS_PERSON_ID) and all searches must have a name

4. 8.9 introduces the concept of Applicant lists. Saved applicant search results from any previous release will be upgraded to a new list.

5. Please see Appendix 1 for a note about Counters

TABLE/FIELD MAPPING OLD TO NEW SCHEMA Key table changes are listed here.


HRS_HRS_COUNTER

Common Components Counter table

New

HRS_AM_JO

Automatch Job opening table

This table links searches to job openings.

JOB_REQUISITION, ER_SRCH_SAVED and ER_AM_REQ_TBL are the source tables for HRS_AM_JO upgrade.

New



Rule 1:

For each Automatch search that does NOT have a search name associated, a new row will be created using a constructed search name of ‘UPG89’ + Job opening number and the owner will be the Recruiter of the Job Requisition.

Rule 2:

For each Automatch search that DOES have a search name associated, a row will be created using the search name and the owner will be the Recruiter of the Job requisition.

Rule 3:

For each Automatch search that does NOT have a search name associated NOR a Recruiter on the job Requisition, a row will be created using a constructed search name of ‘UPG89’ + Job opening number and a search owner as specified on the upgrades defaults page.

Rule 4:

For each Automatch search that DOES have a search name associated but does NOT have a Recruiter on the job Requisition, a row will be created using the search name and a search owner as specified on the upgrades defaults page.

This logic also applies to the creation of rows in HRS_SRCH_SAVED.

HRS_SRCH_SAVED

Saved Search Table

JOB_REQUISITION, PSOPRDEFN and ER_AM_REQ_TBL are the source tables for HRS_SRCH_SAVED upgrade.

New



Rows are upgraded with a new key based on the logic above in HRS_AM_JO.

HRS_AM_RSLT

Automatch Results table

ER_AUTOMTCH_RES, JOB_REQUISITION, HRS_APPLICANT, PS_HRS_APP_PROFILE and HRS_APP_NAMES are the source tables for the upgrade of HRS_AM_RSLT


Replace/Modify

HRS_PRF_STS

Status Code Preferences table

ER_AUTOMTCH_RES, ER_AM_STS_TBL and JOB_REQUISITION are the source tables for upgrade of HRS_PRF_STS.


New

HRS_LIST

Applicant Lists table

ER_SRCH_RSLTAPP and ER_SRCH_RSLTS are the source tables for the upgrade of HRS_LIST.

Rows are selected from ER_SRCH_RSLTS Where AUTOMATCH_IND = ‘N’ (as these are the saved search results)

Replace/Modify

HRS_LIST_APPL

Applicant List Entries table

ER_SRCH_RSLTAPP, HRS_LIST and HRS_APPLICANT are the source tables for the upgrade of

Replace/Modify



HRS_LIST.

HRS_SRCH_RSLTJO

Job Openings tied to Search Results

ER_SRCH_RSLTREQ and ER_SRCH_RSLTS are the source tables for the upgrade of HRS_SRCH_RSLTJO.

Replace/Modify

HRS_AGNT_PROF

Job Agent Profile

ER_AGNT_PROFILE, HRS_APPLICANT and

ER_APP_REGISTER are the source tables for the upgrade of HRS_AGNT_PROF.

Replace/Modify

HRS_PRF_JOBCODE

Job Agent Jobcode Preferences table

ER_PRF_JOBCODE, HRS_APPLICANT and ER_APP_REGISTER are the source tables for HRS_PRF_JOBCODE upgrade.

As ALL searches in 8.9 must have a name, the name of the applicant job agent search upgraded will be defaulted to the first 20 characters of the applicants email address.

Replace/Modify

HRS_PRF_LOC

Job Agent Location Preferences table

ER_PRF_LOC, HRS_APPLICANT and

ER_APP_REGISTER AR are the source tables for HRS_PRF_LOC upgrade.

As ALL searches in 8.9 must have a name, the name of the applicant job agent search upgraded will be defaulted to the first 20 characters of the applicants email address.

Replace/Modify



Common Components: Approvals

In Recruiting Solutions 8.9, a new approvals framework has been introduced, in order to increase functionality and flexibility in the approval process for job openings and offers. Because there is a large differential between the previous approvals structure and the new structure, Approval in progress will not be upgraded to a corresponding status but will simply be moved to Open (Approved). Per the Enterprise HRMS Upgrade documentation and the steps below, customers should approve or deny any approval in progress prior to upgrade.

Approval Value Mapping

The approval status values below will be converted into the following 8.9 status codes.

APPROVAL STATUS (PRE 8.9)

Status Code 8.9

NEEDS APPROVAL

Open (Approved)

IN APPROVAL PROCESS

Open (Approved)

1. Prior to running upgrade, either approve or deny all Needs Approval and In Approval Process approval requests.

2. Run upgrade process. Any approval requests that are still in Needs Approval and In Approval Process will be converted to Open (Approved) status.


Approval Tables Deleted in 8.9

The following tables were used in the approvals process as it existed in previous releases. Because of the wholesale change in the approval process and the adoption of the Approvals Framework, these tables do not have a corollary in Recruiting Solutions 8.9 and the data is not upgraded as it is no longer relevant.

Table Name Description New/Modify/Deprecated

HR_OFFER_DAT Contains workflow status information for the HR Offer Request transaction

Deprecated

HR_OFFER_STA Job Offer Approvals table

This record is a child of HR_OFFER_DAT and is used to store data about each step of the workflow approval process for an Offer Request.

Deprecated

HR_DEV_REQ_STA Job Requisition approvals table Deprecated



Employee Referral Program (ERP)

The ERP component handles data related to the tracking of employee referrals of applicants to job openings and awards associated with successful referrals. The primary changes in ERP are related to modifications made to bring it into alignment with the new Recruiting Solutions architecture.

The integration of ERP with North American Payroll (for awards) via Integration Broker remains essentially similar to past versions. For further information about setting up that integration, please see the Red Paper Recruiting Solutions 8.9 Payroll for North America Integration Setup, available on Customer Connection.


Key table changes are listed here.

Record Field Map to Record Field

JOB_REQUISITION HRS_JO_I

BUSINESS_UNIT BUSINESS_UNIT

CLOSE_DT CLOSE_DT

COMPANY COMPANY

DEPTID DEPTID

DESIRED_START_DT DESIRED_START_DT

ENCUMB_DT_INDC ENCUMB_DT_INDC

JOBCODE JOBCODE

LOCATION LOCATION

JOB_REQ_NBR HRS_JOB_OPENING_ID

OPENINGS_CNT OPENINGS_CNT

OPENINGS_TARGET OPENINGS_TARGET

OPEN_DT OPEN_DT

POSITION_NBR POSITION_NBR

PROJECTED_FILL_DT PROJECTED_FILL_DT

SETID_DEPT SETID_DEPT

STATUS_CODE STATUS_CODE

STATUS_DT STATUS_DT



WC_COUNCIL_ID WC_COUNCIL_ID

JOB_REQUIS_TYP HRS_JO_POST_I

JOB_REQUIS_DT_TYP HRS_JO_PST_TYPE

JOB_REQ_NBR HRS_JOB_OPENING_ID

REQ_OPEN_DT OPEN_DT

REQ_CLOSE_DT CLOSE_DT

POSITION_DATA HRS_POSN_DTA_I2


CLASS_INDC CLASS_INDC

COMPANY COMPANT

CONFIDENTIAL_POSN CONFIDENTIAL_POSN

DEPTID DEPTID

EFFDT EFFDT

EFF_STATUS EFF_STATUS

FTE FTE

JOBCODE JOBCODE

JOB_SHARE JOB_SHARE

KEY_POSITION KEY_POSITION

LOCATION LOCATION

ORGCODE ORGCODE

ORGCODE_FLAG ORGCODE_FLAG


POSITION_POOL_ID POSITION_POOL_ID

POSN_STATUS POSN_STATUS

REG_REGION REG_REGION

REG_TEMP REG_TEMP

SHIFT SHIFT

UNION_CD UNION_CD

JOB HRS_JOB_I2

ACTION ACTION



ACTION_REASON ACTION_REASON

BAS_GROUP_ID BAS_GROUP_ID

BEN_STATUS BEN_STATUS


COMPANY COMPANY

DEPTID DEPTID

EMPL_CLASS EMPL_CLASS

EMPL_STATUS EMPL_STATUS

EMPL_TYPE EMPL_TYPE

FTE FTE

FULL_PART_TIME FULL_PART_TIME

GRADE GRADE

JOBCODE JOBCODE

JOB_INDICATOR JOB_INDICATOR

LOCATION LOCATION

PAYGROUP PAYGROUP


REG_REGION REG_REGION

REG_TEMP REG_TEMP

STD_HOURS STD_HOURS

EMPLOYMENT HRS_EMPLOYMT_I

HIRE_DT HIRE_DT

LAST_DATE_WORKED LAST_DATE_WORKED

REHIRE_DT REHIRE_DT

TERMINATION_DT TERMINATION_DT



Appendix 1: Important Notes

SYNCHRONIZING COUNTERS

Recruiting Solutions 8.9 makes use of counters in a number of tables to provide unique key values. The current or starting value of these counters is tracked on the Last Assigned Ids page (HRS_INST_CNTRS). It is important that the values on the Last Assigned Ids page accurately reflect the current maximum counter value; otherwise, it may be possible for the system to attempt to insert duplicate counter values as the value autoincrements.

To synchronize the values on the Last Assigned Ids page with the current maximum values in the tables:

1. Navigate to Set Up HRMS>Install>Product and Country Specific>Recruiting Installation and click on the Last Assigned Ids tab.

2. At the bottom of the page, click the Fix Counters button.

This will set counter values either to the maximum current value existing, or to 1000, whichever is higher. (Counter values below 1000 are reserved for Recruiting Solutions system data.)

MANAGE HIRES

In Recruiting Solutions 8.9, the Hire process has changed significantly; it now makes use of application messages and the Integration Broker. In order for applicants that are ready to be hired to appear in the Workforce Administration Manage Hires functionality, therefore, the appropriate setup must be completed, including:

• set up and activation of gateway, nodes, message channels, domains, etc.

• setup of (or use of delivered) role queries and Hire notifications

For details about setting up Hire functionality, please refer to the Peoplesoft Enterprise Talent Acquisition Manager 8.9 PeopleBooks and Peoplesoft Enterprise PeopleTools PeopleBooks.

OFFERS

Customers upgrading from HRMS 8.01 will need to create an Offer Component and Offer Component Type of BASE in order for upgraded offers to be visible. This is because the concept and structures for Offer Components and Offer Component Types was introduced in HRMS 8.3; in 8.01, an offer only consisted of a single “component.” Offers upgraded from HRMS 8.01 have been given the Offer Component and Component Type of BASE.

For more information on setting up Offer Components and Offer Component Types, please refer to the Peoplesoft Enterprise Talent Acquisition Manager 8.9 PeopleBooks.



STATUSES MAPPING

In Recruiting Solutions 8.9, a new status has been delivered: 071 – Offer Accepted. An applicant in this status has indicated they have accepted the offer, and the applicant is ready for hire processing.

Because of the changes in the Hire process in RS 8.9, this interim status is necessary so that a Recruiter or other administrator can make any adjustments prior to setting the applicant to Ready to Hire status. Once in Ready to Hire status, the applicant information is pushed to the HRMS system via application messaging; in RS, the data can no longer be modified, and in PS HRMS 8.9, the applicant will appear in the Manage Hires component (for more information on the Manage Hires process, please consult PeopleBooks).

In previous releases, this functional status was indicated by 080-Ready to Hire. Because in RS 8.9 the data for an applicant in 080-Ready to Hire status is no longer editable, status 080-Ready to Hire has been mapped to 071-Offer Accepted as part of the upgrade process.

SITE SECURITY

The Recruiting Solutions 8.9 Careers page, through which applicants can search and apply for jobs, makes use of the concept of Sites. This includes Site row level security, which will determine which job openings are visible to an applicant utilizing a particular Site. As part of System Data, a default Site (SITE ID = 1) is delivered; this site definition has a delivered value for Row Security that will probably not be valid for your installation. For information on setting up Sites and Site security, please refer to the Peoplesoft Enterprise Candidate Gateway 8.9 PeopleBooks.

APPLICANT NAME

In Recruiting Solutions 8.9, only one Applicant Name per application is allowed; users cannot enter multiple, effective dated rows for each application. Therefore, in the upgrade process, the current effective date name is used as the Applicant Name.

APPLICATION LAST UPDATED BY

In Recruiting Solutions 8.9, Manage Applicants functionality, the last user to update an application is displayed in the Last Updated By field. This information was not captured in previous releases. For rows coming into 8.9 via the upgrade, the value presented here will be the userid that is used for access during the upgrade process.

FIND APPLICANTS

In Recruiting Solutions 8.9, applicants will only be visible in the results of an applicant search (Recruiting>Find Applicants) if they have a recruitment row; that is to say, if they have submitted an application or resume (the application or resume need not be tied to a specific job opening). Applicants who only have profile information (name, address, phone and/or email address) will not be visible in the results of a Find Applicant search.



APPLICANT PHONES

In previous releases, an applicant’s phone number might be stored in one of two places, depending on where the information was entered. When entered via Self Service, the number was stored in APPLICANT_DATA.PHONE; no phone type was associated with this number. If the number was entered via administrative pages (e.g., Recruit Workforce>Applicant Data), it was stored in APPLICANT_PHONE.PHONE along with a phone type (Home, Office, etc.). However, the two tables were not kept synchronized in any fashion, so it was possible to have numbers in APPLICANT_DATA not reflected in APPLICANT_PHONE and vice versa.

Because there is no phone type associated with the number in APPLICANT_DATA, and the possibility of overwriting data needed to be avoided, in the 8.9 upgrade logic the system will first look to see if, for each row (applicant) in APPLICANT_DATA, a row exists in APPLICANT_PHONE. If the applicant has one or more rows in APPLICANT_PHONE, the number in APPLICANT_DATA is not moved over to the new record (HRS_APP_PHONES). If no row exists for that applicant in APPLICANT_PHONE, the number in APPLICANT_DATA is added to HRS_APP_PHONES with a phone type of Home.

APPLICANT ID

Recruiting Solutions 8.9 makes use of the new, more flexible field HRS_PERSON_ID; this is the primary ID field for applicants, and the previous field APPLID is no longer used. As part of the upgrade process, applicants will be issued a new HRS_PERSON_ID; however, the field has been included on the record HRS_APPLICANT, and the value from previous releases populated there, for those customers who may have a need for this historical information. The value is not used elsewhere in the Recruiting Solutions application.

CONTRACT DATA APPLICATION DATE

In previous releases, the application date associated with an applicants Contract Data (APP_CNT_DATA.APP_DT) was populated from the application date of the application itself and was not an editable field. However, post-release of Recruit Workforce 8.3 opened this field and made it editable and non-required (in 8.8, the field was again not editable). This can lead to situations where the value of APP_CNT_DATA.APP_DT is left blank (NULL), an invalid value in 8.9.

To alleviate this situation, the upgrade process will populate HRS_APP_CNTRACT.APP_DT with the value from APP_CNT_DATA.APP_DT. If the value there is NULL, the HRS_APP_CNTRACT.APP_DT will be populated with the most recent application date value for that Applicant.

JOB OPENING SECURITY

Recruiting Solutions 8.9 provides row level security on Job Openings; users can only see Job Openings for which they have row level security access via one of the documented methods. The set up and implementation of row level security in HRMS and Recruiting Solutions has changed significantly in Release 8.9. For detailed information on how to set up Job Opening security, please refer to the Peoplesoft Enterprise Talent Acquisition Manager 8.9 PeopleBooks.

DEFAULT JOB POSTING TEMPLATES



In previous releases, the Recruitment Template included values for several other templates (Requisition Template, Resume Template, etc.). In 8.9, the concept of the Job Opening Posting Template has been significantly expanded and has been included as one of the values on the Recruitment Template.

Because this data did not exist in previous releases to be upgraded, a value of ‘1000’ has been defaulted for Job Opening Posting ID on the Recruitment Template page:

This Job Opening Posting Template has the following set up:



In some cases, the Posting information from the previous release cannot be dynamically mapped to the new Job Opening Posting Template; specifically, the previous Posting has a section that does not map to one of the selected Requisition Pages to Include in the template. When that occurs, the data is not lost, but the Description Type in the Job Posting Information displays as Invalid Value (since the value that it is attempting to display is not activated for that template).

The correct this situation, simply modify the Template to include that section by selecting the appropriate checkbox for that value. The value for the job posting in question can be found in the record.field HRS_JO_PST_DSCR.HRS_JO_DESCR_TYP. Navigating to the Job Opening Posting Template being used by this job posting, the correct sections can be selected.

The description for each description type is:

HRS_JO_DSC_TYP

HRS_JO_DESCR_TYP Description



B Basis of Rating

C Closing Statement

D Department Marketing Statement

E Equal Employment Opportunity

H How To Apply

I Other Information

L Conditions of Employment

M Major Duties

O Org Marketing Statement

P Pay,Benefits, & Work Schedule

Q Qualifications

R Responsibilities

T How CTAP &/or ICTAP May Apply

V How to Claim Vet Preference

W Who May Apply

LOCATIONS AND SETID/BUSINESS UNIT

When defining a location, SetID is included as part of the key and as a required field in the setup. In previous versions when adding a location to an application (as a Desired Geographic Location or Preference), the user selects a Business Unit (required) and then selections a location. However, there is no referential integrity enforced between the selected Business Unit and Location, so that one is able to enter a Location that is not tied to the same SetID to which the Business Unit is tied.

For example:



In the above, you can see that Business Unit GBIBU has been selected, which is associated with SetID SHARE. However, the locations noted are tied to SetID TQGEN; GBIBU does not have a relationship with SetID TQGEN.

Because this referential integrity is enforced in RS 8.9, only those Desired Geographic Preferences that meet that integrity displayed. Although the data is brought over in the upgrade so as not to be lost, it is not considered valid data and so is not displayed for use in the application.

It is recommended that analysis be performed on the relationship between APPLICANT_DATA.BUSINESS_UNIT and APPLICANT_DATA.DESIRED_LOCATN1 and APPLICANT_DATA.DESIRED_LOCATN2 prior to upgrade to ensure that referential integrity requirements are met.

FILE ATTACHMENTS

The URL field is only pertinent if you are using Mohomine Resume Processing. In this release, resume attachments will be stored in one location regardless of whether the resume came from Resume Processing, Apply Online, or was attached in Applicant Data. This location is specified in Set Up HRMS, Product Related, Recruiting, Attachment Types, under the Resume Attachments type. For conversion purposes, enter the actual URL you will be using for the Resume Attachments Type in the URL field.

In this release, the destination of your attachments cannot be changed. For example, if in the previous release, attachments are stored on a ftp server, then in this release the attachment destination should also be an ftp server.

For Mohomine attachments, Navigate to Setup HRMS > Upgrade > Define Defaults > Product Defaults. Setup the URL on the recruiting page before running the upgrade process. The upgrade process will move all the Mohomine attachments to this URL destination.

If you have non-Mohomine attachments on an ftp server and require them to be relocated, manually copy your attachments to the new ftp location, which should be same as the URL setup on the upgrade defaults page for Mohomine resume attachments. Navigate to PeopleTools > Utilities > Administration > URLs. Set the URL “HRS_APP_ATCH” to point to this new ftp location.

Once the migration process is completed on the production environment, you will have to manually delete attachments from the old ftp location.



POSTING TO THIRD PARTY JOB BOARDS

Previous releases of Talent Acquisition Manager allowed for the one-way posting of Job Opening information to (external) third party job boards. Once posted, the job postings existed in isolation from the PeopleSoft Job Requisition management system. Candidates could then view these job postings at the third party sites and obtain information about the jobs in which they were interested as well as the manner in which these jobs could be applied for. The posted job information included details (a URL) describing how to access the Applicant homepage of the Enterprise installation so the entire third party application process could be seamless.

When upgrading from previous releases to Oracle Enterprise Talent Acquisition Manager Release 8.9 and higher there is no support for the automatic upgrade of job posting information transferred to third party job boards in terms of earlier release functionality. It will be necessary to manually un-post all active postings prior to upgrade commencement and then re-post them in accordance with the Customer's Open Integration Framework configuration after upgrade completion.


Date post:	21-Feb-2015
Category:	Documents
Upload:	carol-howell-dahlin
View:	428 times
Download:	9 times

Rp Hcmrs Upgrade Supplemental

Documents