Integration with PeopleSoft HCM, PeopleSoft Campus Solutions or Third-Party HR Data

The Person Basic EIPs form the foundation of the CDM integrations. They are responsible for creating the Person object that is the building block of the CDM. Additional duties include the populating and updating of personal biographical data, National ID, and names. Finally, all creation and maintenance of contact methods (address, email, phone) are processed through the Person Basic EIPs.

Adding Contact Methods Across Roles

Person Basic EIPs provide only the Individual role when a person is created. Additional roles such as Worker or Consumer are added to persons later by the other CDM EIPs that rely on the Person object having already been created. Despite this, Person Basic Sync is responsible for the subsequent contact method maintenance across all roles held by the person.

When Person Basic Sync receives a request to add a new contact method of a particular contact method type (address, email, phone) for an existing person, it uses the configuration on the Contact Method Type definition to determine which roles the contact method will be added to if they exist for the person. Available roles are Individual Consumer, Worker, and POI (person of interest).

This example illustrates the Contact Method Type page.

When a new contact method is created, it cannot have a start date that predates the established role to which it is to be associated. The start date of the contact method will be adjusted accordingly upon creation if necessary. This table lists several examples:

Person Basic Sync Run Date	Inbound Contact Method Start Date	Role Exists?	Role Start Date	Resulting Contact Method Start Date
5/30/2010	5/01/2010	Yes	1/1/2010	5/01/2010
5/30/2010	5/01/2010	Yes	5/15/2010	5/15/2010
5/30/2010	5/01/2010	No	5/30/2010	5/30/2010
5/30/2010	7/01/2010	Yes	1/1/2010	7/01/2010

Note: Contact methods that are entered manually into CRM are not maintained by Person Basic Sync.

See Contact Method Type Page.

The Workforce EIPs are another important part of the CDM EIP structure. They are responsible for importing job and employment data for persons from PeopleSoft HCM or PeopleSoft Campus Solutions into CRM. Workforce is dependent on the Person Basic EIPs having already created the Person object for which the job and employment data is being synchronized. Workforce Fullsync is for initial load of job data and the incremental Workforce Sync handles updates and additions going forward.

Besides importing POI data, Workforce EIPs affect the CDM in two ways. First, they create the Worker role for the Person object if it does not already exist. Second, when the Worker role is added, any existing contact methods for that person are cloned and added to the Worker role. This is the only contact method interaction for Workforce EIPs; all subsequent changes or additions are processed through Person Basic Sync.

For import of employee job data from non-PeopleSoft third-party systems, the Worker Sync EIP is used.

PeopleSoft Campus Solutions maintains multiple EIP integrations with CRM to add and maintain student and prospective student data. Not all of these EIPs interact with the CDM, though a select few do (see the CDM Message Summary session below). These messages are dependent on the Person Basic EIPs having already created the Person object for which the data is being synchronized.

The Campus Solutions EIPs create the Consumer role for the Person object if it does not already exist. Also, when the Consumer role is added, any existing contact methods for that person are cloned and added to the Consumer Role. This is the only contact method interaction for Campus Solutions EIPs; all subsequent changes or additions are processed through Person Basic Sync.

The Pers POI EIP is an important part of the CDM EIP structure. It is responsible for importing POI data for persons from PeopleSoft HCM or PeopelSoft Campus Solutions into CRM. Pers POI Sync is dependent on the Person Basic EIPs having already created the Person object for which the data is being synced.

Pers POI Sync creates the POI role for the Person object if it does not already exist. Also, when the POI role is added, any existing contact methods for that person are cloned and added to the POI role. This is the only contact method interaction for Pers POI Sync; all subsequent changes or additions are processed through Person Basic Sync.

Due to the interdependent nature of the EIPs which are creating and modifying CDM information, it is vital that CRM receives and processes them in the correct order. Because the Person Basic EIPs create the foundation Person object, those messages must always be received and processed before subsequent Workforce or Campus EIPs for that same person. Failure to do so can result in data loss, inconsistent data between the CRM and the source system, or both.

To ensure that the messages are received and processed in the correct order, the EIPs are delivered in a single ordered message queue. Messages should not be removed from this queue.

You should perform FULLSYNC messages at implementation time to set up your PeopleSoft CRM database correctly.

To set up your database with FULLSYNC messages (recommended sequence):

1. Before you run the main EIPs, run these common EIPs:

   1. Country

   2. State

   3. Currency

   4. SetID Initialization

   5. Table Set Control Initialization

   6. Location

   7. Business Unit

2. Run the Person Basic Sync EIP.

3. Run the Workforce EIP group.

   1. Department

   2. Job Code

   3. Workforce

4. Run the Person Competencies EIP group.

   1. CM_TYPE

   2. Rating Model

   3. Competency

   4. Person Competency

5. Inactivate the FULLSYNC messages and activate the corresponding SYNC messages.

SYNC messages always originate in PeopleSoft HCM or a third-party system and publish to PeopleSoft CRM. Thus, any field in PeopleSoft CRM that an EIP populates must be maintained from the originating source database, whether it is PeopleSoft HCM or a third-party system.