Background

Person of Interest (POI) represents the relationship of the person to the organization.  There are several POI types used for different reasons.

The purpose of this paper will focus only on the POI Type 00100-Future Hire for 9.0 which is used for CHRS Recruiting (PageUp).  Recommendations for 9.2 and other POI types will be addressed in the future.

Organizational Relationships are created when Adding a Person in PeopleSoft. For every person brought into PeopleSoft, a specific organizational relationship such as Employee or Person of Interest type must be chosen. As stated above, this paper focuses on using POI. If a person is hired directly in Job and the organization relationship is Employee, this paper is not applicable.

As part of the integration from PageUp into PeopleSoft, a standardized method is required to complete the process. The emphasis of this paper is only applicable for campuses that use POI type 00100–Future Hires. A decision has been made to use the POI Security - Business Unit.  This ensures that the POI will be brought in and visible to the campus.  If Business Unit security is not implemented, Future Hire POIs would not be visible. This method will be used across all campuses that use POI type 00100–Future Hires.

Issue

• If Security is not set up the process cannot complete.
• The PU Integration cannot support multiple POI Security types so the interface can only be coded one way.
• Setup time depends on the number of permission lists that are granted access to this POI type; therefore, more permission lists would mean more setup time.
• If POI type 00100-Future Hire is not used at a campus and later decides to use this method, Security must be added in order for the person to be visible in the system.

Analysis

It has been determined that the Security setup effort is minimal and provides a significant benefit in return.  Additionally, it allows completion of proper setup from PageUp into PeopleSoft and less work is required for the campuses.

If this method is not followed, manual entry in PeopleSoft would be required to correct the POI default to 00000-Unknown which is the alternative. 

Recommendations

1.  Campus that use POI type 00100–Future Hire must have appropriate security set up.

   Step 1:  Go to Security Access type and confirm if security type 006 for PPLPOI is enabled. If not, check box and save.

Step 2: For any permission list that need access to the POI type 00100-Future Hire, the following Security is required:

Step 3: Run security refresh:

2. Integration will be coded to include specific parameters to bring into PeopleSoft:

   Specific coding parameters include: Security Access Type, Business Units, Effective Date, and 2 rows to include an Active and Inactive Person of Interest History. The Security Access Type will be populated based on the security.

Considerations

Row level security requirements are set up and security is assigned to appropriate permission lists.

Cross-Functional Impacts (Positive / Negative)

None

CHANGE IMPACT

To be filled out by BSA (from Change Impact Tracking log):

The following items will be answered / addressed by Change Management:

1. Areas of potential change resistance to proposed HR process / policy changes?

   Campuses may resist due to the perception that this requires a significant amount of work.  Once campuses are sufficiently informed about the amount of work involved and the fact that only one POI type is involved, the benefits will outweigh any time involved in setup.

2. Potential resource needs in order to plan, engage, prepare, and/or deploy the change?

   HRIS and/or the Security team at each campus will need to set up this access.  They will need specific information about which POI type (00100-Future Hire) and which permission list(s) need access to this POI type.

3. Associated costs relative to the scope of the change to requirements requested?

   No costs anticipated with the exception of time involved.

4. Training needs or if a straightforward change?

   None.

5. Implication on any other related process / functions?

   None.

6. Union impact?

   No reasonably foreseeable impacts within the scope of bargaining identified at the time of review.

REVISION CONTROL

Revision History

Review/Approval History

End of Article