Integrating with PeopleSoft HRMS

This chapter provides an overview of PeopleSoft eProcurement and PeopleSoft Human Resources Management System (HRMS) integration and discusses how to set up HRMS integration:

Understanding PeopleSoft eProcurement and HRMS Integration

PeopleSoft eProcurement enables you to use employee information that is stored in the PeopleSoft HRMS database to create requesters and automatically update PeopleSoft eProcurement, based on changes to the employee data. The integration is accomplished with PeopleSoft Integration Broker, which enables you to receive service operations sent by PeopleSoft HRMS. When changes are made to the record in HRMS, they are automatically received by eProcurement.

The service operations are delivered with a status of Inactive. You must activate each service operation before attempting to publish or subscribe. The service operations that are sent by PeopleSoft HRMS must be activated in that database, and the messages to which PeopleSoft eProcurement receives must be activated in the PeopleSoft FDM database.

The integration between PeopleSoft HRMS and PeopleSoft eProcurement enables you to preform these tasks:

• Send new user data from HRMS to eProcurement.

• Automatically create requesters if a user contains a role that is predefined in Supply Chain Management as having access to the component.

• Automatically inactivate a requester when a user account is locked out.

When updating information between databases, PeopleSoft Integration Broker imposes these outbound and inbound rules:

• Full Table Publish (outbound)

  This rule erases all data from the target table and replaces it with data from the source table.

• Incremental Table Publish (outbound)

  This rule captures the addition, change, or deletion of data that is performed in the source database and either inserts a new row of data, or deletes, or updates the corresponding row of data in the target database.

Note. PeopleSoft eProcurement receives data changes from the PeopleSoft HRMS database. It does not send data to PeopleSoft HRMS (except for the USER_PROFILE service operation). Also, PeopleSoft eProcurement does not receive any full table user profile data changes. It only receives incremental data changes.

Setting Up HRMS Integration

This section discussed how to:

• Set up the human resource management service operations.

• Set up defaults for automatic creation of users and requesters.

Pages Used to Set Up HRMS Integration

Setting Up the Human Resource Management Service Operations

PeopleSoft delivers the service operations in PeopleSoft Integration Broker with a default status of Inactive. You must activate each service operation before attempting to send or receive data from a third-party source or another PeopleSoft system, such as CRM. To setup this service operation:

1. Define the requester role in eProcurement.

2. Setup within PeopleSoft Integration Broker and Enterprise Components:

   Use the information in this table and refer to the setup instruction in the PeopleSoft Supply Chain Management Integrations 9.1 PeopleBook, "Implementing Integrations" chapter, Setting Up Service Operations section.

Warning! The JOBCODE_FULLSYNC and the PERSON_BASIC_FULLSYNC should not be activated unless the organization is performing an initial implementation and no actual data exists in the PeopleSoft FSCM database.

If you change the status of these service operations to Active, the data in the PeopleSoft FSCM database will be overwritten. Do not activate the FULL_SYNC versions in PeopleSoft HRMS or PeopleSoft FSCM unless you intend to overwrite all the data in the target tables.

See Also

Enterprise PeopleTools PeopleBook: Integration Broker

Setting Up Defaults for Automatic Creation of Users and Requesters

Access the Requester Integration Defaults page (eProcurement, Administer Procurement, Maintain System Users and Roles, Requester Integration Defaults).

For the purpose of integrating with HRMS, you only need to define the fields within the User Preferences and the Requester Defaults group boxes.

The user profile defaults are used to enable automatic creation of users who do not exist when using the requester integration.