HCM Integrations

Appendix: HCM Integrations

This chapter discusses how to:

Set up PeopleSoft Human Capital Management (HCM) and PeopleSoft Services Procurement person integration.
Set up and use the HCM terminology integration.
Set up the PeopleSoft Recruiting Solutions and PeopleSoft Services Procurement integration.

Understanding the PeopleSoft Services Procurement and Human Capital Management Integration

Many PeopleSoft applications offer seamless integration with other selected products. PeopleSoft Services Procurement customers can now integrate with PeopleSoft HCM. When you install both Supply Chain Management (SCM) and HCM database structures, you can configure the system to use the HCM database as the system of record and initiate consistent terminology between the PeopleSoft Services Procurement and PeopleSoft HCM applications.

Note. You must register services procurement administrators, approvers, requesters, and service coordinators in the HCM database first. Once you register these users in the HCM database, you can then register them in the SCM database.

Note. You cannot enable the HCM integration if you've already selected the MSP Installation option on the Services Procurement Installation Options page.

See Also

PeopleSoft Enterprise HRMS Application Fundamentals 9.0 PeopleBook

Prerequisites

In order to use the HCM and Services Procurement integration, you must first install both the HCM and SCM databases.

Common Elements Used in This Chapter

Login Profile	Operator profile or user profile.
HCM Person	A person within the HCM system that has a unique employee ID. This person could be an employee or a contingent worker.
Services Procurement Person	A user who is registered in Services Procurement. A Services Procurement person entry is created for Service Coordinators, Service Provider Contacts and Service Providers type of users.
HCM User	An administrator that has access to the HCM database.
SCM User	An administrator or other user who has access to the SCM database.
Job Family	Grouping of jobs to make it easier to assign a competency or competency cluster to similar jobs.
Job Function	Used to create function categories that can then be assigned to job codes.
Job Code	In HCM, jobs are identified by job codes. Job Codes are used to maintain information about jobs independent of the person of group performing that job. For example, salary grades and standard hours are assigned to a job regardless of who holds that job.
Job Profile	Identifies a set of competencies, subcompetencies, and responsibilities that apply to employees in the same job or job family.
Establishment	A country specific option for USA or France. Note. This option is only visible when the regulatory region is USA or France.
Labor Agreement	This is a country-specific required field for Spain. Note. This option is only visible when the regulatory region is Spain.
Job Posting	Job requirement defined within the HCM Recruiting Solutions product and sent to Services Procurement for fulfillment.

Setting Up the PeopleSoft HCM and Services Procurement Person Integration

This section discusses how to:

Set up installation options.
Set up business unit definitions.
Set up service operations - incremental synchronization.
Set up service operations - full-table synchronization.
Activate full-table publish rules.
Register enterprise service administrators, approvers, requesters, and service coordinators.
Register service provider contacts.
Register service providers.
Use the Service Operations Monitor.

Understanding the PeopleSoft HCM and Services Procurement Person Integration

When you implement both PeopleSoft Services Procurement and HCM applications, you can configure HCM as the system of record to maintain user details. When the HCM Person Integration installation option is selected on the Services Procurement Installation Options page, the enterprise administrators can register a Services Procurement user as an HCM person with a unique employee ID and create unique operator login profiles within the HCM database.

The following six users are either registered in the HCM database with a unique Person ID, or they are created in the SCM database without a Person ID. Each user has a specific role that enables them to perform specific tasks within the application:

Service Procurement Administrator: This user can register all other users in the Services Procurement system, as well as perform basic application setup.

This user is created in the HCM database as an HCM person with a unique employee ID.
Approver: This enterprise user may be designated as requisition, work order, or time and progress log approver.

This user is created in the HCM database as an HCM person with a unique employee ID.
Requester: This enterprise user determines specific requirements for a resource and creates a requisition listing those requirements.

The requester might designate a service coordinator to source the requisition and handle the fulfillment process. This user is created in the HCM database as an HCM person with a unique employee ID.
Service Coordinator: This user may work for the enterprise or the supplier.

He or she handles the sourcing of requisitions to different suppliers and also handles supplier bids to ensure that the request is filled with the most qualified resource. This user is created in the HCM database as an HCM person with a unique employee ID.
Service Provider Contact: This is a non-enterprise user who manages a team of service providers and handles bidding with the service coordinator.

This user is registered in SCM database and does not have a corresponding HCM person ID and a unique employee ID.
Service Provider: This supplier resource is submitted as a potential candidate for a sourced requisition.

The service provider is registered in the SCM database and has a unique services procurement person ID. Once this user is registered in the SCM database, personal data is sent back to the HCM database, where a new person entry and operator login profile is created for the service provider.

See PeopleSoft Enterprise HRMS Application Fundamentals 9.0 PeopleBook

Pages Used to Set Up the PeopleSoft HCM and Services Procurement Person Integration

Page Name	Object Name	Navigation	Usage
Services Procurement Installation Options	INSTALLATION_SP	Set Up Financials/Supply Chain, Install, Installation Options, Services Procurement	Define PeopleSoft Services Procurement installation options.
Services Procurement Business Unit Definition	BUS_UNIT_TBL_SP	Services Procurement, Define Services Procurement, General Setup, Business Unit Definitions, Services Procurement Definitions	Define PeopleSoft Services Procurement business units. Define your own consolidation structures for accounting and reporting purposes.
Services User Setup	SPB_USER_SETUP_PG1	Services Procurement, Maintain Users, Services User Setup	Maintain user setup for requesters, service coordinators, service providers, and service provider contacts.
Services User Setup	SPB_USER_SETUP_PG2	Click the Create a New Services User button, and then click the requester user button.	Determine whether the new user has an existing user profile or needs a new profile, add new users as requesters, and establish security and user preferences for the new user.
User Profile Information	SPB_USR_PROFILE_PG	Click the User Profile link on the Services Procurement Setup page.	Enter user ID and password information for the new requester.
Requester Setup	REQUESTOR_TBL	Click Go on the Services User Setup page to add the new user as a requester on the Requester Setup page.	Define requisition and catalog defaults for the requester.
Business Unit Security by User ID	SEC_BU_OPR	Click the Unit by User ID link on the Services User Setup page.	Set up business unit access by user ID.
TableSet Security by User ID	SEC_SETID_OPR	Click the TableSet by User ID link on the Services User Setup page.	Set up TableSet access by user ID.
User Preferences	PV_OPR_LINKS	Click the User Preference link on the Services User Setup page.	Define overall and procurement preferences for the requester.
Maintain Service Coordinator	SPB_PERSON_PAGE	Click the Person ID link on the Services User Setup page.	Define personal information for the service coordinator.
Service Coordinator Information	SPB_COORDINATOR_PG	Click the Service Coordinator Information link on the Maintain Service Coordinator page.	Define employee and user ID information.
Maintain Service Coordinator - Phone and Email Details	SPB_USR_PH_EM_PAGE	Click the Phone and Email Details link on the Maintain Service Coordinator page.	Enter telephone and email details for the service coordinator.
User Login Information - User Profile Information	SPB_PERSLGN_SEC_PG	Click the Create User Profile button on the Service Coordinator Information page.	Define login information for the service coordinator.
Maintain Provider Contact	SPB_SP_PERS_PAGE	Click the Add button on the Services User Setup page.	Define personal information for the provider contact.
Provider Contact Information	SPB_PROV_CNTCT_PG	Click the Provider Contact Information link on the Maintain Provider Contact page.	Define supplier, location code, and create user profile.
Maintain Provider Contact - Phone and Email Details	SPB_USR_PH_EM_PG2	Click the Phone and Email Details link on the Maintain Provider Contact page.	Enter telephone and email details for the provider contact.
Maintain Service Provider	SPB_PERS_PROV_PAGE	Click the Add button to add a new Person ID on the Services User Setup page.	Define personal information for the service provider.
Service Provider Information	PB_INDP_PROV_PG	Click the Service Provider Information link on the Maintain Service Provider page.	Define work status, project role, supplier, years of experience, and other parameters to define the service provider.
Maintain Service Provider - Phone and Email Details	SPB_USR_PH_EM_PG3	Click the Phone and Email Details link on the Service Provider Information page.	Enter telephone and email details for the service provider.
Service Provider Skills	SPB_PROV_SKILL_PG	Click the Provider Skills link on the Service Provider Information page.	Select appropriate competencies for the service provider.
Services	IB_SERVICEDEFN	PeopleTools, Integration Broker, Integration Setup, Services	Define services.
Service Operations	IB_SERVICE	PeopleTools, Integration Broker, Integration Setup, Services Operations	Define service operations and associate them to services.
Routing Definitions	IB_ROUTINGDEFN	PeopleTools, Integration Broker, Integration Setup, Routings	Define routings associated with service operations.
Queue Definitions	IB_QUEUEDEFN	PeopleTools, Integration Broker, Integration Setup, Queues	Define queues to be used with the HCM integration.
Monitor Overview	IB_MONITOR_OVRVIEW	PeopleTools, Integration Broker, Service Operations Monitor, Monitoring, Asynchronous Services	Use this page to ensure that all service operations are set up and active.

See Also

Enterprise PeopleTools 8.48 PeopleBook: Integration Broker

Setting Up the Installation Options

Access the Services Procurement Installation Options page.

HCM Person Integration Enabled

Select to enable the integration with HCM for person information. When you select this option, basic person and job data is synchronized between the HCM and Services Procurement systems.

Setting Up Business Unit Definitions

Access the Services Procurement Business Unit Definition page.

If you select the HCM Person Integration Enabled option on the Services Procurement Installation Options page, the HCM Integration group box and relative HCM field values are available on this page.

Regulatory Region	Select a regulatory region.
Company	Select the company.
Business Unit HR (business unit human resources)	Enter the human resource business unit.
HCM Administrator	Select the name of the human resource administrator responsible for entering user information in the HCM database.

Note. Many of the HCM default values from the Services Procurement Business Unit Definition come from the requisition and work order components.

See Also

Setting Up Business Unit Definitions

Setting Up Service Operations - Incremental Synchronization

PeopleSoft Services Procurement utilizes PeopleSoft Integration Broker to integrate PeopleSoft Services Procurement tables with PeopleSoft HCM. The service operations are delivered with a default status of Inactive. You must activate each service operation before attempting to publish service operation or subscribe to service operations between databases. You must activate these service operations in the HCM and SCM databases.

To begin using PeopleSoft Integration Broker, you must enable the publishing of service operations in PeopleSoft HCM and SCM and the subscribing to those service operations in PeopleSoft HCM and SCM. The publish and subscribe rules may also be incremental or full table synchronization for each service operation.

The following table contains the Incremental Synchronization Service Operations that update the PeopleSoft Services Procurement applications every time a user changes data in HCM that is relevant to the integration. These service operations are published from HCM.

Note. You must activate these service operations and queues in the PeopleSoft Services Procurement and HCM databases.

Service Operation	Queue
DEPT_SYNC	ENTERPRISE_SETUP
DEPT_SYNC_EFF	ENTERPRISE_SETUP
COMPANY_SYNC	PERSON_ISE_SETUP
LOCATION_SYNC_EFF	ENTERPRISESETUP
LOCATION_SYNC	ENTERPR _SETUP
BUS_UNIT_HR_SYNC	HR_SETUP
JOBCODE_SYNC	PERSON_SETUP
REGULATORY_REGION_SYNC	PERSON_SETUP
ESTAB_TBL_SYNC	PERSON_SETUP
ESTAB_ LOC_US_SYNC	PERSON_SETUP
HR_LABOR_AGRMNT_S	PERSON_SETUP
PERSON_BASIC_SYNC	PERSON_DATA
WORKFORCE_SYNC	PERSON_DATA
USER_PROFILE	USER_PROFILE

After you activate these service operations, every subsequent change to data in any of the records associated with these service operations triggers the publication and subscription of the new or deleted data. As a result, PeopleSoft Services Procurement reflects the change within a few seconds.

These SYNC service operations are published from HCM. You must activate the subscriptions to these service operations in the SCM system in order to update the data in SCM.

See Also

Enterprise PeopleTools 8.48 PeopleBook: Integration Broker

Setting Up Service Operations - Full-Table Synchronization

Full-table synchronization is more data-destructive than incremental synchronization. Incremental synchronization service operations modify, delete, or add the data that a user has affected in performing an individual transaction. Full-table synchronization service operations delete all data in the target record first and then loads a copy of the source record.

Full-table synchronization is generally used at the beginning of an implementation to get the data synchronized between databases. After that point, it should be used sparingly.

The following table lists full-table synchronization service operations. You should carefully consider the effect of activating any of these service operations.

Warning! Do not activate any service operations that are identified as FULL_SYNC or FULLSYNC unless you are absolutely certain that you want to overwrite all of the data in the records that are associated with the service operation in the database. Understanding how Full Synchronization Service Operations work is especially important if you have a different list of departments or locations in the Services Procurement database than you have in the HCM database. For example, synchronizing the departments using a FULLSYNC service operation would overwrite all of the Services Procurement departments with the HCM departments.

Note. When using Full Synchronization service operations, the primary concern is that you do not inadvertently overwrite valid data. To prevent this problem, you should generally avoid activating Full Synchronization service operations for any record that receives input from more than one database.

Service Operation	Queue
DEPT_FULLSYNC	ENTERPRISE_SETUP
COMPANY_FULLSYNC	PERSON_ISE_SETUP
LOCATION_FULLSYNC_EFF	ENTERPRISESETUP
LOCATION_FULLSYNC	ENTERPR _SETUP
BUS_UNIT_HR_FULLSYNC	HR_SETUP
JOBCODE_FULLSYNC	PERSON_SETUP
REGULATORY_REGION_FULLSYNC	PERSON_SETUP
ESTAB_TBL_FULLSYNC	PERSON_SETUP
ESTAB_ LOC_US_FULLSYNC	PERSON_SETUP
HR_LABOR_AGRMNT_FULLSYNC	PERSON_SETUP

You should activate the following two service operation and service operation subscription to synchronize the SetIDs and tableset information from the HCM database to the SCM database.

Service Operation	Queue
SETID_INITIALIZE	TBLSET_CONTROL
TBLSET_CONTROL_INITIALIZE	TBLSET_CONTROL

See Also

Enterprise PeopleTools 8.48 PeopleBook: Integration Broker

Activating Full-Table Publish Rules

Full-table service operations in PeopleSoft Integration Broker are delivered with a status of Inactive. The publishing rules must be activated. When the appropriate service operations are activated, information that is shared by the SCM, and PeopleSoft HCM databases is updated properly.

For example, PeopleSoft publishes (Full Table Publish) data from HCM. Table BUS_UNIT_TBL_HR is populated with new data from PeopleSoft HCM, and all old data is deleted. The data from this table is published in the service operation BUS_UNIT_HR_FULLSYNC.

Use the following service operations to send the service provider information from the SCM database to the HCM database. You should activate the service operation and routings in both the HCM and SCM databases to enable the integration.

Service Operation	Queue
HCR_ADD_PERSON This service operation is published from SCM to HCM when a work order is released. The service operation contains the service providers personal information that is required by HCM for creating an HCM person. The service operation also contains job information for creating a job assignment in HCM.	PERSON_DATA
HCR_ADD_PERSON_ACK This service operation is published from HCM after processing the HCR_ADD_PERSON service operation. This acknowledgement service operation contains information of whether the HCM person, job and user profile have been created in HCM.	PERSON_DATA
HCR_ADD_JOB This service operation is published from SCM when a service provider who is currently associated to a work order is also associated to another work order. This service operation contains job information for creating a job assignment in HCM.	PERSON_DATA
HCR_ADD_JOB_ACK This service operation is sent from HCM after processing the HCR_ADD_JOB message. This service operation contains info of whether the job assignment was created in HCM.	PERSON_DATA
HCR_CAN_JOB This service operation is published from SCM when a work order is canceled, closed or terminated. This service operation contains the job information for terminating the job assignment in HCM.	PERSON_DATA

See Also

Enterprise PeopleTools 8.48 PeopleBook: Integration Broker

Registering Enterprise Administrators, Approvers, Requesters, and Service Coordinators

The following list details the required steps for registering administrators, approvers, requesters, and service coordinators.

The enterprise administrator registers the user in the HCM database.

The HCM system creates a new HCM person of type Employee.
The enterprise administrator creates an operator login profile for the user.

Note. The new user employee ID is associated with the operator login profile.
The PERSON_BASIC_SYNC service operation publishes the person and job assignment information from the HCM database to the SCM database.

The USER_PROFILE service operation publishes the user profile information from the HCM database to the SCM database.
The enterprise administrator registers the new user in the PeopleSoft Services Procurement application.
For service coordinators, the service procurement person ID is associated to the user profile. In SCM, the required roles are associated to the users when they are added as administrators, approvers, requestors or service coordinators

Registering Service Provider Contacts

The service provider contact is a supplier person of interest user that does not require registration in the HCM database.

Registering Service Providers

The following list details the required steps for registering a service provider.

Note. The HCM Integration option must be enabled to complete this process effectively.

The enterprise or supplier administrator registers the service provider in the PeopleSoft Services Procurement application.

Once the service provider is successfully registered, the system creates a unique Services Procurement Person ID.
Once the service provider is registered with his own unique Person ID, the service provider contact sources the candidate, the candidate qualifies and accepts the position, and then the work order is created and approved.
After a work order is released, the SCM system sends the service provider information to HCM to create an HCM person of type Contingent Worker.

This information is sent to HCM in the form of an asynchronous service operation.
Once in HCM, a new HCM person entry and login profile is created for the service provider.
The Services Procurement application receives a response back from HCM.

This information includes, but is not limited to the HCM employee ID, Work Order Business Unit, Work Order ID, and the Services Procurement person ID.
Services Procurement stores the HCM employee ID as a cross-reference in the SCM database.
The PERSON_BASIC_SYNC service operation synchronizes the person and job assignment information from the HCM database to the SCM database.

The USER_PROFILE service operation synchronizes the user profile information from the HCM database to the SCM database. When creating the user profile, the HCM system uses the employee ID as the user ID and password. The user has the option of changing the password when they log in into Services Procurement.

The following service provider data is sent to the HCM database from the SCM database using asynchronous service operations:

Services Procurement Person ID
First Name
Middle Name
Last Name
Person Organization
Email ID
Primary Phone Number

The following job data information is also sent to the HCM database from the SCM database:

Work Order Business Unit
Work Order ID
Sequence Number
Effective Date
Employee ID
Regulatory Region
Company
Business Unit
Department
Location
Job Code
Establishment
Labor Agreement

Once the data is received and processed in the HCM database, the following information is sent back to SCM from the HCM database using the PERSON_BASIC_SYNC and USER_PROFILE service operations:

Services Procurement Person ID
Work Order Business Unit
Work Order ID
HCM Employee ID
Employee Record Number
Sequence Number

Note. Once an administrator registers a service provider in PeopleSoft Services Procurement, all updates to personal data must be performed in the HCM database.

See Also

Maintaining Users and Team Setup

Using the Service Operations Monitor

Use the Services Operations Monitor menu to ensure that all service operations are set up and active. You can also use this menu to monitor asynchronous and synchronous service operations.

See Also

Enterprise PeopleTools 8.48 PeopleBook: Integration Broker

Setting Up the HCM Terminology Integration

This section discusses how to set up installation options.

Understanding the HCM Terminology Integration

When the HCM Terminology installation option is selected on the Services Procurement Installation Options page, the current service and service type labels are replaced with job code and job family labels throughout the PeopleSoft Services Procurement system. Since the job family and job function terms are widely used throughout the HCM application, you can now configure the system to use HCM terminology consistently across both the SCM and HCM databases.

The following table lists the new terminology for PeopleSoft Services Procurement when the HCM integration is selected.

Note. When you enable the HCM Terminology integration, all service and service type labels change into job family and job code labels respectively.

Page Name in Services Procurement	Page Name When HCM Terminology is selected	Search Pages
Service Type	Job Family	Service Type changes to Job Family
Service	Job Code	Services changes to Job Code
Project Role	Job Code	Services changes to Job Code

Pages Used to Set Up the HCM Terminology Integration

Page Name	Object Name	Navigation	Usage
Services Procurement Installation Options	INSTALLATION_SP	Set Up Financials/Supply Chain, Install, Installation Options, Services Procurement	Define PeopleSoft Services Procurement installation options.
Existing Service Type/Service	SP_SERVICETYPE_WK	This page automatically populates if you do not have the correct job code/job family relationship.	Fix the job code and job family relationship before you enable the Use HCM Terminology option on the Services Procurement Installation Options page. Note. You can only have job family associated to a job code.

Page Name

Object Name

Navigation

Usage

Services Procurement Installation Options

INSTALLATION_SP

Set Up Financials/Supply Chain, Install, Installation Options, Services Procurement

Define PeopleSoft Services Procurement installation options.

Existing Service Type/Service

SP_SERVICETYPE_WK

This page automatically populates if you do not have the correct job code/job family relationship.

Fix the job code and job family relationship before you enable the Use HCM Terminology option on the Services Procurement Installation Options page.

Note. You can only have job family associated to a job code.

Setting Up Installation Options

Access the Services Procurement Installation Options page.

Use HCM Terminology

Select to modify HCM terminology throughout Services Procurement. When you select this option, all current Service and Service Type labels change to Job Code and Job Family labels.

If selected, the MSP Installation option is disabled.

Note. When you enable this option, the system validates the relationship between the existing the job family and job codes. HCM allows only one Job Family per Job Code, while Services Procurement allows multiple service types per service. Due to this restriction from HCM, you cannot enable this option if there are services present with more than one related service type. If this situation occurs, you will receive a secondary page that informs you of the service and service type relationships that do not meet the criteria. In order to continue with the conversion to HCM terminology, you must remove the additional relationships.

Setting Up the PeopleSoft Recruiting Solutions and Services Procurement Integration

This section discusses how to:

Set up installation options.
View the PeopleSoft Recruiting Solutions and Services Procurement Integration process flow.
View service operations.

Understanding the PeopleSoft Recruiting Solutions and Services Procurement Integration

When you implement both PeopleSoft Services Procurement and Recruiting Solutions (eRecruit) applications, you can create a requisition in the Recruiting Solutions application and then use service operations to pass that requirement data to Services Procurement for fulfillment.

When the Recruiting Solutions Integration Enabled installation option is selected on the Services Procurement Installation Options page, users can create a job posting in Recruiting Solutions, send that data back to Services Procurement with pre-populated data, approve, source, and fulfill the requisition, create a work order, and send that data back to the Recruiting Solutions application for further processing.

With this integration, you can send service operations back and forth between applications by using the PeopleTools Integration Broker to support the following activities:

Create a Recruiting Solutions job requirement and route it to Services Procurement with the appropriate data mapping.
Route updates or cancellations from the Recruiting Solutions requirements to Services Procurement with the appropriate data mapping.
Send candidate information from services procurement to Recruiting Solutions after work order approval.
Send candidate confirmation from Recruiting Solutions to Services Procurement after on boarding process is complete.

Pages Used to Set Up the PeopleSoft Recruiting Solutions and Services Procurement Integration

Page Name	Object Name	Navigation	Usage
Services Procurement Installation Options	INSTALLATION_SP	Set Up Financials/Supply Chain, Install, Installation Options, Services Procurement	Define PeopleSoft Services Procurement installation options.
Create Requisition	SPF_REQ_INFO_PG	Services Procurement, Create Requisition	Enter basic service requisition information.
Services	IB_SERVICEDEFN	PeopleTools, Integration Broker, Integration Setup, Services	Define services.
Service Operations	IB_SERVICE	PeopleTools, Integration Broker, Integration Setup, Services Operations	Define service operations and associate them to services.
Routing Definitions	IB_ROUTINGDEFN	PeopleTools, Integration Broker, Integration Setup, Routings	Define routings associated with service operations.
Queue Definitions	IB_QUEUEDEFN	PeopleTools, Integration Broker, Integration Setup, Queues	Define queues to be used with the PeopleSoft Recruiting Solutions integration.
Monitor Overview	IB_MONITOR_OVRVIEW	PeopleTools, integration Broker, Service Operations Monitor, Monitoring, Asynchronous Services	Use this page to ensure that all service operations are set up and active.

Setting Up Installation Options

Access the Services Procurement Installation Options page.

See Defining Services Procurement Installation Options.

Recruiting Solutions Integration Enabled	Select to enable the integration with Recruiting Solutions. When you select this option, all requisitions created in the Recruiting Solutions product are passed to Services Procurement for fulfillment.
Recruiting Solutions/HCM Nodename	Enter the HCM node location where the work order service operation is sent.

Viewing the PeopleSoft Recruiting Solutions and Services Procurement Integration Process Flow

The following sections describe the process flow for the Recruiting Solutions and Services Procurement integration.

Job Posting Process

The following steps outline the job posting process.

User creates a job posting in Recruiting Solutions and sends that data to the Services Procurement application.

A service operation is created in the HCM and sent to SCM in the format of the PositionOpening HR-XML service operation.
The SCM Integration Broker receives the PositionOpening, and transforms it into the PeopleSoft service operation JOB_POSTING.
The Services Procurement code will examine the service operation for the authentication data originally sent in the HR-XML envelope.

If authenticated, a unique identifier HOLDING_ID is generated and data from the JOB_POSTING service operation is inserted into the Job Posting table.
A URL that points to the Services Procurement requisition is generated, which includes the HOLDING_ID identifier.

The URL is added to the JOB_POSTING response service operation.
The SCM Integration Broker receives the JOB_POSTING service operation and converts it into the HR-XML envelope format, which is all that is needed for the response to the PositionOpening.
HCM receives the response XML, extracts the Services Procurement URL, and creates a new browser window that points to the URL.
Services Procurement requisition examines the unique identifier and then loads matching data from the holding table into the appropriate fields on the requisition.
The user completes the requisition, submits it for approval, and continues on with the fulfillment process within Service Procurement.

Note. You can also sent updates from Recruiting Solutions to Services Procurement to modify or cancel job posting that were sent previously.

Work Order Process

Once the requisition is filled and the related work order is generated, the following steps outline the work order process:

The Work Order is approved, and the Work Order process initiates.

This process is kicked-off by the service coordinator manually.
Service operation SP_WORK_ORDER is created with current work order data.

This service operation is sent asynchronously to the HCM database. The service coordinator sees that the posting is in progress, and continues with work as usual. The Work Order is then marked as Published in HCM.
The SCM Integration Broker receives the SP_WORK_ORDER service operation and converts it into the HR-XML Candidate format.
The HCM application receives the Candidate XML service operation and begins the onboarding process.

After the onboarding process is complete in HCM side, an asynchronous service operation is sent to SCM to respond to the Candidate XML.
The SCM Integration Broker receives the XML Candidate format service operation and converts it into the PeopleSoft SP_WORK_ORDER format.
Services Procurement code updates the work order to specify that it is acknowledged and processed by HCM.

Viewing Service Operations

When the user is transferred to the Services Procurement requisition, they see the requisition fields filled with the data from Recruiting Solutions.

The following table lists the mappings of the Position Opening XML from Resource Management to Services Procurement.

Recruiting Solutions Position Opening Element Name	Services Procurement Field Label
PositionProfile.ProfileId.IdValue	Job Code
PositionProfile.PositionDetail.Competency.NumericValue	Experience
PositionProfile.PositionDetail.Competency.CompetencyEvidence. EvidenceId.id	Educational Level
PositionProfile.PositionDetail.Competency.name	Competencies
PositionProfile.PositionDetail.RemunerationPackage.BasePay.currencyCode	Currency
PositionProfile.PositionDateInfo.ExpectedEndDate	End Date
PositionProfile.PositionDetail.PositionTitle	Job Title
PositionProfile.PositionDetail.PhysicalLocation.Name	Location
PositionProfile.PositionDetail.RemunerationPackage.BasePay.BasePayAmountMax	Rate
PositionProfile.PositionDetail.FormattedPositionDescription.Value	Scope of Work
PositionProfile.PositionDetail.PositionTitle	Service
PositionProfile.PositionDetail.JobCategory.CategoryCode	Service Type
PositionProfile.PositionDateInfo.StartDate	Start Date
PositionProfile.PositionDetail.RemunerationPackage.BasePay.baseInterval	Unit of Measure

The following table lists the mappings from the Service Procurement tables (work order, service provider, and related tables) to the ‘Candidate’ XML service operation for Recruiting Solutions.

Services Procurement Record	Services Procurement Field Label	Recruiting Solutions Candidate Element Name
NA	JobOpeningID	RelatedPositionPostings.PositionPosting.Id.IdValue.name
PV_EXT_XREF_HDR	KEY1FLDVAL	RelatedPositionPostings.PositionPosting.Id.IdValue
SPF_WORDERREC	JOB_TITLE	RelatedPositionPostings.PositionPosting.Id.Title
SPB_PERSON_TBL	FIRST_NAME	Resume.StructuredXMLResume.ContactInfo.PersonName.GivenName
SPB_PERSON_TBL	MIDDLE_NAME	Resume.StructuredXMLResume.ContactInfo.PersonName.MiddleName
SPB_PERSON_TBL	LAST_NAME	Resume.StructuredXMLResume.ContactInfo.PersonName. FamilyName
SPB_PERSON_TBL	TITLE	Resume.StructuredXMLResume.ContactInfo.PersonName.Affix
NA	familyNamePrefix	Resume.StructuredXMLResume.ContactInfo.PersonName.Affix.type
SPB_PERS_PHONE	COUNTRY_CODE (where PHONE_TYPE=Home)	Resume.StructuredXML.Resume.ContactInfo.PersonName.ContactMethod.Telephone.InternationalCountryCode
SPB_PERS_PHONE	PHONE (where PHONE_TYPE=Home)	Resume.StructuredXMLResume.ContactInfo.PersonName.ContactMethod.Telephone.SubscriberNumber
SPB_PERS_PHONE	COUNTRY_CODE (where PHONE_TYPE=Cellular)	Resume.StructuredXML.Resume.ContactInfo.PersonName.ContactMethod.Mobile.InternationalCountryCode
SPB_PERS_PHONE	PHONE(where PHONE_TYPE=Cellular)	Resume.StructuredXMLResume.ContactInfo.PersonName.ContactMethod.Mobile.SubscriberNumber
SPB_PERS_PHONE	COUNTRY_CODE(where PHONE_TYPE=FAX)	Resume.StructuredXML.Resume.ContactInfo.PersonName.ContactMethod.FAX.InternationalCountryCode
SPB_PERS_PHONE	PHONE(where PHONE_TYPE=FAX)	Resume.StructuredXMLResume.ContactInfo.PersonName.ContactMethod.FAX.SubscriberNumber
SPB_PERS_EMAIL	EMAIL_ADDR	Resume.StructuredXMLResume.ContactInfo.PersonName.ContactMethod.InternetEmailAddress