PeopleSoft Enterprise Campus Solutions (9.

0) & PeopleSoft Human Capital

Management (9.1) – Database Split Considerations

Overview

Oracle’s PeopleSoft Enterprise Campus Solutions (CS) and PeopleSoft Enterprise Human Capital
Management (HCM) have historically utilized the same underlying database; this shared instance
is currently available to Release 9.0, and is used exclusively by Higher Education (HE) institutions.

However, with the adoption of the Continuous Delivery Model and the release of HCM 9.1,
institutions will be required to run separate production instances, which will allow development,
deployment and upgrades of the two applications independently. The strategy also allows for new
CS functionality to be rolled out via Feature Packs without the need for a major upgrade.

The Heartland Highe

History and Challenges of a Shared Database
Heartland’s Higher Education vertical has been
CS and HCM functionality share a variety of features and processes, with the ‘Person’
talent. being
Our higher education consultants are ex
reliable, and accountable.
principal to both applications. Most HE institutions have a significant number of individuals who
are either simultaneously or consecutively students, employees, and alumni.Our Therefore, the allows
collaborative style shared you to leverage
deliver true institutional benefits and solutions.
person record was a deliberate design decision based on this knowledge of Higher Education
At Heartland we focus on understanding the re
business practices.
those needs. We deliver results and guide cha

▪ Listening to your needs and customizing o

The Campus Community module was produced to strengthen and build upon the already existing
▪ Leveraging your existing resources while b
Personal Data configurations in HCM. The key factor was that the Person could then have a single
identity, the EMPLID, to identify them, as both a student and employee at the▪ institution.
Delivering incremental results

▪ Ensuring self-sufficiency through knowledg

However, customers often struggled with data ownership: which department owned the person’s
information? With so many individuals being tracked as both students and employees, who
Office: (855) 208 5973 had
(toll free)
responsibility for the information? While adaptations were made to ease some of these concerns,
the issues continued to present a challenge for many HE institutions.

With the separation of CS and HCM, these issues should no longer be a concern; increased
flexibility and a further ability to tailor the applications to that particular institution’s needs are some
of the benefits derived from independently run databases.

 
Hardware/Software Implications

The primary step in separating the two

databases will be to clone the HCM/CS 9.0
database, thereby creating two identical
copies – all objects and data will exist in both,
requiring both archives to be independently
maintained. Institutions will need to complete
an evaluation to determine if any additional
hardware is needed, e.g. server space.

Since the separation is solely based on

existing PeopleTools functionality, there is no
need for additional software.

Integration Options: Direct Integration vs. Hub-based Integration

Before commencing the integration of your separate instances of CS and HCM, you must
determine what data you will need to coordinate between the models. For example, it might be
important at your institution that individuals have the ability to update their own data in HCM or CS,
and that these updates are able to move between systems.

Most significantly, the structure of your CS/HCM integration comes down to one point: do you want
to integrate your databases directly, or do you want to make use of a hub-style solution as part of a
broader organization of individual records on campus?

A direct integration solution adopts a point to point style model, running CS and HCM in separate
instances, in a way that can still maintain a single EMPLID for each person. No additional
middleware is being used; you simply want to move information between CS and HCM using
PeopleTools.

Hub-model integration makes use of Master Data Management (MDM). MDM acts as a data core,
collecting and storing data from multiple locations on campus and feeding it back out to those
same sources. If the only requirement you have is the integration of CS and HCM, the cost and
effort of a hub-based solution is probably not right for you.

Contact us today to learn how Heartland can assist your Database Split project.

www.heartlanditc.com ■ inquiries@heartlanditc.com ■ Tel: (855) 208-5973 (toll free)