Last updated on MAY 22, 2016
Applies to:PeopleSoft Enterprise HRMS Talent Acquisition Manager - Version 9.1 to 9.1 [Release 9]
PeopleSoft Enterprise HRMS Human Resources - Version 9.1 to 9.1 [Release 9]
Information in this document applies to any platform.
***Checked for relevance on 2-Apr-2014***
During the hire process, applicant data is stored in the system. The existing inbound XML for parsing data to Recruiting Solution (RS) 9.1 uses hard coded content types. For instance: MEM, HON, LNG, DEG, COMPETENCY, LIC. Even the Instance Qualifier for COMPETENCY is hard coded. As Content Types, Primary Person Profiles, and Profile Types are configurable, the system does not restrict the use of content types and profile types to the standard delivered ones.
PeopleSoft Job Profile Management (JPM) has the flexibility and integration to other areas.
Purpose: To enable customers to customize delivered Recruiting to JPM 9.1 integration to work when the delivered content types in the delivered primary person profile type in JPM are not used.
Business Requirement: For the delivered content types, e.g. Competency, the customer may have a new custom content type NewComp created in JPM to capture and maintain the competency data. In RS 9.1, integration is delivered for content type Competency. To make RS-JPM integration work, a customization is required in RS 9.1 to capture and maintain competency data in NewComp.
Scope: This document covers only the business requirement described above. It does not cover any other scenario.
Assumption: Customers will not be using both the delivered content types and the newly created one at the same time. Since both are meant for same data, only one should be configured for use and the other should be made inactive.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms