Peoplesoft Campus Solutions 9.0 Statement of Direction Fy 2011

July 2010
PeopleSoft Campus Solutions 9.0

Statement of Direction FY 2011
Oracle Statement of Direction—PeopleSoft Campus Solutions 9.0
Disclaimer
This document in any form, software or printed matter, contains proprietary information that is the exclusive
property of Oracle. Your access to and use of this confidential material is subject to the terms and conditions
of your Oracle Software License and Service Agreement, which has been executed and with which you agree
to comply. This document and information contained herein may not be disclosed, copied, reproduced or
distributed to anyone outside Oracle without prior written consent of Oracle. This document is not part of
your license agreement nor can it be incorporated into any contractual agreement with Oracle or its
subsidiaries or affiliates.
This document is for informational purposes only and is intended solely to assist you in planning for the
implementation and upgrade of the product features described. It is not a commitment to deliver any material,
code, or functionality, and should not be relied upon in making purchasing decisions. The development,
release, and timing of any features or functionality described in this document remains at the sole discretion
of Oracle.
Due to the nature of the product architecture, it may not be possible to safely include all features described in
this document without risking significant destabilization of the code.
Oracle Statement of Direction—Campus Solutions 9.0
Purpose ............................................................................................. 1
Introduction ........................................................................................ 2
PeopleSoft Campus Solutions Drivers ............................................... 3
PeopleSoft Campus Solutions: The Year in Review........................... 3
Campus Community – Prior Year Updates .................................... 3
Contributor Relations – Prior Year Updates ................................... 5
Recruiting and Admissions – Prior Year Updates........................... 6
Student Records – Prior Year Updates .......................................... 8
Academic Advisement – Prior Year Updates ............................... 10
Student Financials – Prior Year Updates ..................................... 10
Financial Aid – Prior Year Updates .............................................. 11
SAIP: Student Administration Integration Pack ............................ 13
Constituent Relationship Management – CRM for Higher Education13
Master Data Management for Higher Education .......................... 13
PeopleSoft Campus Solutions: Planned Features............................ 14
Campus Community..................................................................... 14
Contributor Relations Planned Features ...................................... 15
Admissions and Recruiting Planned Features .............................. 16
Student Records Planned Features ............................................. 17
Academic Advisement Planned Features ..................................... 19
Student Financials Planned Features........................................... 19
Financial Aid Planned Features ................................................... 20
Campus Solutions – Focus on the Enterprise .................................. 21
Planned Integration Between PeopleSoft HCM and Campus Solutions 9.0

..................................................................................................... 21
Business Challenges for Industry and Key Requirements ............ 22
Integration Approach .................................................................... 24
Scope of Data to be exchanged ................................................... 28
Tools to support CS to HCM Integration....................................... 30
Documentation ............................................................................. 31
Conclusion ................................................................................... 31
Graduation Processing..................................................................... 32
Campus Solutions Warehouse (An EPM 9.1 Solution) ..................... 32
Campus Solutions Warehouse – Planned Features ..................... 34
The Longer Range Roadmap ........................................................... 34
Conclusion ....................................................................................... 35
Purpose
This document provides an overview of features and enhancements included in
PeopleSoft Campus Solutions Release 9.0. It is intended solely to help you assess the
business benefits of upgrading to 9.0 and/or planning for the implementation of the
product features described.
The purpose of this document is to provide an annual update to the PeopleSoft

Enterprise Campus Solutions customers about activities impacting their use of the
Campus Solutions applications and related products. The document will provide an
overview to the enhancements and other updates that have been delivered since the last
Statement of Direction document, as well as an overview of features and enhancements
planned for the Campus Solutions codeline within the next 12 months. It is intended
solely to help you assess the business benefits of applying new maintenance and
planning for the implementation of the product features described.
Oracle plans to issue this document annually, targeting the second quarter of each year.
Additional, more detailed documentation will accompany the actual release of new
features.
1
Introduction
Global economic uncertainty continues to impact the behavior, goals and demographics
of individuals seeking a post-secondary education. At the same time, deepening budget
challenges and increased regulations have impacted how institutions of higher education
are responding to and managing the changes they need to make to deliver learning more
effectively and flexibly.
Several seemingly conflicting requirements emerge in what institutions need from

technology:
• More flexibility but lower costs
• Increased collaboration but more security
• Comprehensive yet open and standards-based solutions
• Single, reliable source of data but ability to support multiple systems and diverse
business processes
Technology investments institutions make must be strategic and provide measurable

value and return on investment not only to the institution, but to all its constituents—
prospects, applicants, students, faculty, alumni, donors and other funding organizations.
In response to customer and market demands, Oracle continues to lead and innovate—
creating products, features, and functions that set the foundation for supporting the
unique academic mission of each of its higher education customers. As a result,
PeopleSoft Campus Solutions 9.0 enhancements planned for the next 12 months are
expected to build on the innovations in earlier releases by advancing functional
excellence, adding powerful business intelligence, and extending the services framework
to enhance integration.
This statement of direction describes planned enhancements in Campus Solutions for the
next 12 months.
2
PeopleSoft Campus Solutions Drivers

Today’s higher education institutions face increased pressures and demands for flexible learning
models, real-time access to information and analysis, transparency of operations, and the ability
to quickly adapt to change. At the same time, resources are more constrained than ever before.
Therefore, IT organizations need to be able to establish metrics and produce valid results that
prove they are deriving the greatest possible value out of their technology investments.
The ongoing enhancement of the Campus Solutions 9.0 applications represents a continued
commitment to excellence and quality. Leveraging evolving technologies, the Higher Education
team at Oracle delivered many new capabilities in three Feature Packs during the last 12 months
that will be discussed in more detail in the following sections.
All these delivered enhancements supported customer requests for more flexible and adaptable
systems through web services. This direction places the ability in the hands of the institution to
choose and configure functionality to meet their specific needs or requirements.
Subsequent Feature Packs are expected to include the results of our continued efforts to identify,
design and add the additional services that will allow Campus Solutions, and our customers, to
collaborate, communicate, and integrate with other applications.
Planned enhancements to other products in the Oracle family to support Higher Education over
the next 12 months include the Campus Solutions Warehouse and Fusion Intelligence. In
addition to planned integration efforts, the Campus Solutions team expects to evaluate and
prioritize incorporation of features from the PeopleTools 8.5 and 8.51 releases into the CS 9.0
applications. Our stated policy (adjusted after the Alliance 2010 conference, based on customer
feedback) requires customers to be current on PeopleTools 8.5 or higher by July 2011. We do
not expect to release new features or functionality supported by Tools 8.5 until that time.
In this issue of the annual Statement of Direction document, Oracle is providing information
about significant updates to the product delivered during the previous 12 months as well as
looking forward to planned enhancements and regulatory updates for the next 12 months.
PeopleSoft Campus Solutions: The Year in Review

This section of the Statement of Direction document provides descriptions of features and
functionality that Oracle delivered for Campus Solutions over the prior fiscal year. Please refer to
the Bundle documentation on My Oracle Support for more detail about a specific feature.
Campus Community – Prior Year Updates

To continue to modernize and evolve the Campus Solutions suite of products, we are focused on
a service oriented approach to the way the products are architected. We have already introduced
a Web Services Framework for Campus Solutions 9.0; this includes an extensible framework
3
created using PeopleCode application classes and Integration Broker to make building
integrations simpler.
In Feature Pack 1, the focus was squarely on the constituent: how to share data about the
constituent, how to find the constituent and how to enrich what you know about the constituent.
Specifically, we addressed the need for a web service that supports core person data: the
Constituent Web Service. In addition, we introduced a much more powerful way to track an
individual’s relationship with your institution, in the new Affiliations feature. Finally, we
enhanced the Campus Solutions Search/Match feature so you can search against an external
system, such as a data hub.
Constituent Web Service Scope
The constituent business object is the profile of a person or external organization of interest to a
higher education enterprise. The Constituent Service is an entity service that exposes the
constituent business object. This means that it supports both the maintenance of the constituent
business object from external sources and notifies these sources when changes are made in
Campus Solutions. In other words, external systems can access and modify constituents in
Campus Solutions, and changes in Campus Solutions can drive similar changes in external
systems.
External Search/Match
The new Search/Match interface in Feature Pack 1 leverages the Constituent Web Service.
Oracle enabled the new Search/Match interface to search against Campus Solutions (as you do
now) or in conjunction with an external search engine (e.g., the Higher Education Constituent
Hub). One of the common external Search/Match scenarios will be from Campus Solutions to
the MDM product, the Higher Education Constituent Hub, which was released in 2009.
Therefore, we designed the External Search/Match to work in this scenario. See the Planned
Features section for plans for use of External Search/Match with Oracle PeopleSoft HCM 9.0
and 9.1 to CS 9.0 integration.
Affiliations
Institutions need to know all the “relationships” or “affiliations” an individual or organization

has with them. Is this person a student? Undergraduate or graduate? Are they also an employee?
Maybe they are also an alumni…and generous donor! The better the institution understands the
complete picture of relationships a person has with the institution over time, the better and more
precise service the institution can provide. Knowing the relationship an individual has with your
institution should help you provide:
• Enhanced personal interactions and communications
• Accurate information
• Appropriate, timely access and privileges
4
Central to this feature, from a customer standpoint, is the ability to define and track unique
affiliations and affiliation structures. Once an institution is tracking affiliations you would expect
to:
• Easily see that set of relationships in all the places where you store data about that person (so you
can provide the right service).
• Use that relationship to drive changes in other systems, most notably in an Identity Management
system. Changes to affiliations should be the key events or triggers to changes in access,
authentication and provisioning.
• Create processes that allow both manual and event-based automatic update and maintenance of
those affiliations.
• Use affiliations to determine who has access to maintain data (e.g., if the person has an active
employee role, regardless of other roles they have, HR may be the only department allowed to
update that person’s address).
Additionally, we delivered some enhancements to Affiliations in Feature Pack 3 (July 2010)
including:
• Update of the affiliation framework to process messages that end a current affiliation.
• Simplification of the management of error messages when processing affiliations. A new
component “View Affiliation Exceptions” was delivered.
• New functionality that allows you to automatically update the value in Status Description of
affiliations as part of tracking.
3C Delete - Batch
Another significant enhancement delivered in the prior year for Campus Community was the
first phase of the 3C Delete project. Phase 1, which included the Batch delete capability, was
shipped in the April 2010 bundle.
The Delete Communications component enables you to define high-level parameters for
removing communications from the system. For example, the institution might want to purge
old communication records that are no longer required, or might need to correct a
communications assignment made in error. You can delete entire categories, or further define the
parameters by letter code or specific date ranges. Population Selection functionality enables you
to target specific subsets of IDs within your deletion parameters. Security is enforced at the
category level based on the user’s 3C Group security.
Contributor Relations – Prior Year Updates

Contributor Relations provides support for the constituent, focused on the status associated with
the alumni or friend of the institution. Of course, the reach of the Contributor Relations
5
application extends beyond the traditional alumni to support the comprehensive ability to fund-
raise and friend-raise.
Some of the more significant enhancements delivered in the prior year include:
• Capability to configure how the Name Display appears on Contributor Relations Administrative
pages (level 0 sub-pages)
• Options include updating the Style, Country format, use of Name Parts and punctuation
Note: See the Feature Pack 3 documentation (July 2010) for more information on the Names Display
enhancements.
• Ability to process Security Codes (also known as CVV, CVV2, CVC2, or CID). CR will not store
the Security Code after verifying the credit card.
• Communication Generation; multiple language support and other issues addressed
Recruiting and Admissions – Prior Year Updates

Delivered with Feature Pack 3, the Admission Applications Web Services provided:
• A set of web services designed to fully support the deployment and capture of data from an
online “form” that an applicant saves and/or submits to a staging table.
• New User Registration web services that support an uninterrupted user experience and
provisioning for the applicant to create, save, and return to an incomplete application for
completion and submission.
• Comprehensive staging tables and posting processing that accommodate both constituent and
application transactions with the flexibility required for managing admissions applications.
• Processing that applies configurable search/match rules (including external search/match ability)
and that moves data from single applications or multiple applications from external data sources
into core tables.
• A delivered component that allows the administrative user to view, modify and reconcile staged
application data.
• Support for administrative data entry on online application forms.
• The ability to use a tool of choice to build the UI “front end” application form with appropriate
institution specific attributes. (“brand-able”, user defined fields, etc.)
• Utilizing the File Parser feature, the ability to map and import admission applications from
external sources to the staging tables associated with AAWS.
• Ability to capture, store, and view application attachments: - e.g. documents, images, video, and
audio files.
6
• Administrative setup components that provide business logic for configuring admissions
applications including: assignment of Application Center, Existing Data Update Rules, and
Prospect creation from saved or posted applications.
• Integration with PeopleSoft Enterprise CRM for prospect and applicant data.
For details on Feature Pack 3, Admission Applications Web Services, please refer to PeopleSoft Campus
Solutions Feature Pack 3 Release Value Proposition available on My Oracle Support Document ID
1134435.1.
Other projects included:
• Tier 4 Points-Based Immigration (UK)
• Ability to collect data for Confirmation of Acceptance for Studies (CAS) requests.
• Bulk upload of CAS requests to the Sponsor Management System (SMS) at the UK
Borders Agency (UKBA).
• Bulk import of assigned CAS details from the SMS.
• Bulk update of CAS fees details to the SMS.
• Bulk report of non-attending students to the SMS.
• Revised GRE Record Layout (8.9, 9.0)
Layout changes for the GRE included:
• Adding new fields and modifying existing fields as specified by the testing agency.
• Modifications to External Test Score Load Run Control to accommodate processing
changes specified by the testing agency.
• Modifications to the GRE Suspense Pages to accommodate processing changes specified by
the testing agency.
• Modifications to Search/Match/Post Test Scores Run Control to accommodate GRE
changes which included Phone Type, Populate Email Address and Email Type added for
Post Processing Parameters
• Provided the ability to use Academic Interest Mapping if defined for GRE
• For Release 9.0 only, layout changes included:
• Program/Plan/Subplan Mapping can be used for GRE
• Email and Telephone will be included in the bio/demo updates
• CRM Messages updated to support new data
• Revised EOS (Educational Opportunity Service) Record Layout
• Removed and added fields and updated load process to accommodate specifications from
testing agency.
7
• Enhanced AMCAS, LSAT/LSDAS test loads to support IPEDS (US) Race and Ethnicity
requirements (8.9 and 9.0)
• Test Score Processing Update(8.9, 9.0)
• When Search/Match criteria is set to ‘Ignore’ for any search match level or No Match
Found, the process will no longer set the test suspense record to a post processing value of
‘Purge’ so the record can be retained for reprocessing.
• Enhancements to Create Prospects From Test Scores Enhancements (9.0)
• Admit Term Mapping
• Program/Plan/Subplan Mapping
• Bio/Demo Updates
• Test Score Load Enhancements (9.0) to accommodate integration with CRM for Higher
Education:
• Create suspect and prospect data capured from the Campus Solutions External Test Score
Post process directly to Enterprise CRM.
• Create prospect and suspect records in both Campus Solutions and Enterprise CRM.
Student Records – Prior Year Updates

Working with the Student Records Product Advisory Group and many individual user
institutions, Oracle Campus Solutions recognized and responded to important suggestions that
emerged from the upgrade to Campus Solutions 9.0, Alliance Conferences, and industry trends.
Some of these included:
• The ability to use test scores as conditions in enrollment requisites (9.0)
• Define the Test IDs that are valid for use in requisites.
• Define how long a test score is valid for use in a requisite.
• Select which test scores to use by default (for example, highest test score).
• Override the maximum age and default best score.
• Select which test scores to use from multiple “sittings” of the same test.
• Average test scores taken.
• Define the valid data sources for the test scores to be used in requisites.
• Textbook Information for Class Sections (For 8.9 and 9.0)
• Delivered a record designed to store appropriate textbook and supplemental information
textbook including ISBN and Retail Price
• Deployed a new component to be used for entering the basic data for administrative
textbook entry
• Provided ability to copy textbooks from one class to another
8
• Delivered ability to display textbook information on class detail within Class Search
• Provided appropriate display of text book information for users in Self Service.
-Faculty Center - My Class Schedule
-Student Self Service – My Class Schedule
-Enabled Advisor access to advisee textbook summary (student view)
• Enabled Student Services Center access to student textbook summary (student view)
• Provided printer friendly version of textbook summary
• Enabled Prior Term Copy to include textbook assignments
• Faculty Center Design and Configuration (9.0)
• Faculty Center added as a functional area to the Navigation Tab Setup component allowing
configuration in a tab and sub-tab structure.
• Advisor Center became part of the tab structure along with Faculty Center, Search and
Learning Management.
• Provided consistent navigation methods and display of information for the Faculty Center.
• Repeat Configuration Enhancements
• Provided ability to limit grades processed in repeat checking
• Provided ability to ‘freeze’ repeat codes
• Expanded the Configurable matching priority
• Added Same Grade Repeat Code assignment
• XMLP Transcript Improvements
• Provided template redesign to control column and page breaks on the transcript template
• Provided country - correct formatting for addresses on the transcript
• Transfer Credit Component Enhancements
• Added tab structure to equivalent course grid (Course Credit – Automated Component)
• Added Detail fields (Unit, Grade, Repeat Data) to tab structure grid (Course Credit –
Automated Component)
• Added Detail fields (Repeat Code and Requirement Designation) to Equivalent Course
Section(Course Credit – Manual Component)
• Added additional search fields to Transfer Subject Area to enhance rule search
• Updated sort features and increased field lengths to Transfer Evaluation Summary report
9
Academic Advisement – Prior Year Updates

Over the past year, Oracle Campus Solutions and the Academic Advisement Product Advisory
Group have worked together on defining the issues that appear to be of significant concern to
the advisement community. Many of the identified issues have come from institutions during
upgrades, Alliance Conference sessions, the list serve, and the HEUG Online Issue Tracker.
Some of the more significant enhancements or updates delivered in the prior year are listed
below.
• The ability to use test scores in academic advisement. The test scores can be used as
preconditions or conditions, including dynamic conditions. Setup options included:
• Define the Test IDs that are valid for use in advisement.
• Define the valid data sources to be used (Educational Testing Service, for example).
• Define how long a test score is valid for use in a degree requirement.
• Ability to select which test scores to use by default (for example, highest test score).
• Override the maximum age and default best score.
• Select which test score to use from multiple “sittings” of the same test.
• Calculate the average of test scores taken.
• The ability to update My Academic Requirements in real time without the use of
synchronization options (triggers).
• Provide a "trigger" to update My Academic Requirements based on exceptions and overrides.
• Configurable graduation program/degree update option.
Student Financials – Prior Year Updates

Last year saw some significant updates in the Student Financials module, both within the module
itself and in integration efforts with E-Business GL and third party payment providers.
Additional Accounting Date Option and Line Validation
Student Financials currently stamps an accounting date in Accounting Line transactions based on
the Accounting Date Option setup for the Item Type. The system did not allow the user to
provide a specific Accounting Date for a Term or a combination of Term and Session. An
enhancement was delivered that allows the user to setup a specific Accounting Date for a Term
or a combination of Term and Session and provide the ability to set up multiple accounting dates
for association with an item type.
A new audit report was delivered to validate existing ChartField setup to determine the
combinations are still valid. The report can be run on demand and provides the user with
information to correct invalid ChartField combinations prior to the GL Interface process being
run.
10
Integration to Oracle E-Business Suite General Ledger
Student Financials integrates completely with PeopleSoft Enterprise Financials. With the delivery
of Feature Pack 2 in 2009, we delivered integration from Student Financials with Oracle E-
Business Financials General Ledger.
Hosted Payment for ePayments (Credit Cards and eChecks)
Hosted Payments for ePayments provides the ability to not require Campus Solutions to collect,
store or transmit any sensitive information to/from the service provider. The sensitive
information is collected by the service provider's hosted page and a unique transaction reference
is sent back to Campus Solutions which Campus Solutions will store for any follow-on
transactions. This business process is extremely attractive to institutions since it minimizes what
an institution needs to undergo by way of a PCI compliance audit and places the responsibility
with the Hosted Payment vendor. The Feature Pack 2 update provided exit points from different
components that accept electronic payments such as Self Service Payments, Miscellaneous
Purchases, and Cashiering. The context of the transaction is saved before making a transition to
the third-party hosted site. The third-party hosted site collects the sensitive payment information,
receives response from the third-party processor and provides a mechanism to post the payment
transaction. Under this payment model, we will discontinue storage of any sensitive information
in Student Financials while storing the last four digits of the account number and credit card or
bank account type for reporting or servicing students.
Integration Broker Support for ePayment Processing
With the release of Feature Pack 2 in November, 2009, we enhanced our support for the current
payment processing business model. The enhanced features for Integration Broker support
moved away from the existing Business Interlink ePayment integration to a more flexible
ePayment API using Integration Broker to authorize, settle and perform credits for credit cards
and electronic checks.
Credit Card - Card Verification Value (CVV) Support
To round out our ePayment processing support we provided the ability to process Security
Codes (also known as CVV, CVV2, CVC2, or CID). We do not store the Security Code after
verifying the credit card.
Financial Aid – Prior Year Updates

Financial Aid provides support for automating federal and institutional financial aid processing to
ensure more efficient operations. Many regulations are built into the software, so your institution
has the tools to obtain and remain in compliance. Some of the more significant enhancements
delivered in the prior year include:
11
Year-Round Pell updates
PeopleSoft Campus Solutions Financial Aid implemented Year-Round Pell for the 2009-2010
processing year. The published regulations cover Year-Round Pell beginning July 1, 2010 for the
2010-2011 processing year.
The opportunity to make changes for Year-Round Pell also afforded us the opportunity to
enhance summer processing. Also, part of the Year Round Pell update enhanced the awarding of
Pell Grants across award periods to include Non-Standard Terms. You can award Pell Grants in
either a Leading Summer or Trailing Summer term.
Perkins Loan Master Promissory Note (MPN) updates
The Office of Management and Budget (OMB) previously approved the revised Federal Perkins
Loan Program Master Promissory Note (Perkins MPN) and authorized its use through June 30,
2009. We delivered the required updates to the MPN based on the technical specifications from
the U.S. Department of Education.
College Scholarship Service (CSS) XML Profile support
CSS/Financial Aid PROFILE® is the financial aid application service of the College Board. The
format changed from a flat file structure to Extensible Markup Language (XML). We now
support the change to XML for the Profile data loads.
Financial Aid Regulatory Updates
No one needs to be reminded that Financial Aid is a heavily regulated part of our industry.
Therefore, Campus Solutions maintains a rigorous schedule of updates, endeavoring to enable
timely compliance by our customers. We work with our customers to determine which regulatory
and legislative updates are the highest priority and attempt to support the required timing of
those changes.
Regulatory Updates are delivered in each of the four scheduled maintenance bundles per year:
• October Bundle – Regs 1: ISIR load, INAS-IM, PROFILE, Return of Title IV
• January Bundle – Regs 2: Database Match and Eligibility updates, NSLDS, Verification, COD
Processing updates for Direct Lending, Pell Grants, ACG/Smart
• April Bundle – Regs 3: Redeliver INAS-FM, Pell Schedules, Commonline Updates
• July Bundle – Regs 4: FISAP, Satisfactory Academic Progress
We also post additional individual updates, as required:
• Pell Schedule Updates (twice this year)
• INAS-FM (multiple technical updates from College Board)
• Perkins and Direct Lending promissory note updates
12
SAIP: Student Administration Integration Pack

SAIP delivers integration from Campus Solutions for persons, courses, and course enrollments
which can then be consumed by a third-party system, e.g., a Learning Management System (LMS)
or an LDAP directory. Many of our customers have a range of academic support systems, all of
which need to consume the data the SAIP provides—which students are enrolled in which class
this term.
Multi-consumer integration
We updated the SAIP functionality so it can support multi-consumer integration. The goal is to
provide the ability for the institution to support the appropriate provisioning of course and user
data to more than one LMS and/or LDAP directory. This needs to happen in a way that not
every consumer takes all the information at the same time. The delivered capability supports the
appropriate level of control for which systems and data should be maintained: the institution
level, academic organization level, class section level, or elsewhere.
Constituent Relationship Management – CRM for Higher Education

Oracle’s PeopleSoft Enterprise CRM for Higher Education Release 9.1 provides institutions with
new and enhanced capabilities for managing and enhancing their relationships with all
constituents across the full lifecycle. Special areas of focus were extending CRM Marketing and
Sales components to make CRM the system of record for the recruiting process. A new Events
Management module was introduced, which is integrated with recruiting data and campaigns.
Finally, support for retention efforts was strengthened through new integrations with Campus
Solutions, providing CRM with additional data to build audiences and create targeted
interactions. A new Service Center for Higher Education was delivered so institutions will have
the ability to manage both service cases and IT help desk cases that are designed specifically for
the higher education industry. Also delivered was a new Constituent 360 Degree View that
provides institutions with a single, consolidated view of the constituent, displaying key data and
statuses from both CRM and Campus Solutions.
Supporting the CRM 9.1 release, Campus Solutions provided enhanced EIPs, enabling stronger
integration between Campus Solutions and CRM for Higher Education in Feature Pack 2. See
more detail in the release notes for CRM 9.1.
Master Data Management for Higher Education

Today’s Higher Education institutions face critical issues with constituent data quality and
preventing duplicate records. The problem is compounded as the volume of data grows and the
number of disparate systems, where this data is collected, tracked, and monitored, increases.
Institutions urgently need a way to maintain an accurate, single source of constituent data across
the enterprise. Master Data Management (MDM) is a modern architecture designed to eliminate
poor data quality within heterogeneous IT application landscapes. It employs tools such as data
13
survivorship engines, data quality rules engines, data standardization, and data synchronization. It
interfaces with third party data augmentation and address standardization providers and builds
cross-references for federated data and golden records for centralized data.
A data hub is a MDM technology that supports better data quality for persons and organizations,
prevents duplication and provides better support for integration of core bio-demo data about
persons and organizations across your institution. Oracle delivered a new product offering, the
Higher Education Constituent Hub (HECH), in 2009. This solution has been described as the
'person model on steroids' because it is not only intended to manage transactions and data
coming from within Oracle applications, but will also incorporate information coming from
external applications such as your library, book store, and housing systems. The key concept
here is that the HECH allows a “single source of truth” for core bio-demo data, which is then
shared, based on your rules, with all the systems on campus that need that information.
The HECH is tailored for Higher Education, with the addition of specific attributes, such as
support for Effective Dating, Seasonal Addresses, Campus ID, etc. The design of this new hub
supports the ability to complete a constituent search in HECH from a page within Campus
Solutions, using the delivered feature External Search/Match. This should have a significant
impact on the ability of an institution to reduce the number of duplicate person records they
create in Campus Solutions.
PeopleSoft Campus Solutions: Planned Features

PeopleSoft Campus Solutions planned features represent an ongoing commitment to provide
best-in-class products that provide real business value. This Planned Features document serves to
provide descriptions of features and functionality that Oracle expects to provide in Campus
Solutions over the next twelve months.
Campus Community
Feature Pack 1 focused on Constituent Management and evolved from a set of requirements that
have one thing in common: improving the management of data that identifies a person or an
organization as it travels through the campus community of systems. Other high priority
requirements Oracle plans to address in the future as part of the Constituent Management
initiative include:
• Provide supported integration for bio-demographic data between separate instances of Campus
Solutions 9.0 and PeopleSoft HCM 9.0 and HCM 9.1
• Provide supported integration between Campus Solutions and the MDM solution, the Higher
Education Constituent Hub (HECH). The HECH solution provides support for a single source
of truth about student/organization data so that data can be shared with other campus systems.
14
NOTE: See the section “Campus Solutions – Focus on the Enterprise” later in this document for information
on the PeopleSoft HCM and CS Integration initiative.
Additional Campus Community Planned Features
Some of the expected enhancements targeted for FY 2011 include:

• SEVIS II Support (specifics to be determined once final specifications are received from the US
Government)
• 3C Delete - a planned feature is the ability to have the system identify “aged” populations of
Communications, Checklists and Comments and purge those from the database according to
your parameters. Using the Policy Manager would eliminate the need for multiple run controls,
requiring manual intervention to update the run control parameters and date ranges. With the
planned Policy Manager, the actual process can be scheduled to run behind the scenes at the
institutions’ desired frequency (every day, once every week etc). The planned process would scan
the 3C tables, looking for the 3Cs which meet the policy manager conditions and then delete
those records.
We are evaluating the need to create an individual delete capability for Checklists and Comments
(to mirror the delivered functionality for Communications).
• Enhancements to “Name” functionality; increased configurability, display choices, personal
salutations.
Note: This enhancement was delivered for the Contributor Relations Administrative pages. We will continue to work
with our customers to prioritize the modules to be targeted for this update.
Contributor Relations Planned Features

Contributor Relations customers are keenly interested in Constituent Management and the
ramifications of maintaining accurate, enriched, non-duplicated information on all constituents.
As such, they will benefit from the features described in the Campus Community section above.
Some of the enhancements targeted for FY 2011 include:
• Enhancements to Name Display functionality – we will work with the customer community to
determine the priority of providing the enhancement delivered in Feature Pack 3 to include self-
service pages in Contributor Relations
• 3C Delete - a planned feature is the ability to have the system identify “aged” populations of
Communications, Checklists and Comments and purge those from the database according to
your parameters. Using the Policy Manager would eliminate the need for multiple run controls,
requiring manual intervention to update the run control parameters and date ranges. With the
planned Policy Manager, the actual process can be scheduled to run behind the scenes at the
institutions’ desired frequency (every day, once every week, etc.). The planned process would
15
scan the 3C tables, looking for the 3Cs which meet the policy manager conditions and then
delete those records.
We are evaluating the need to create an individual delete capability for Checklists and Comments
(to mirror the delivered functionality for Communications).
Admissions and Recruiting Planned Features

Additional features related to the Admission Application Web Services are planned. These
include:
• Admissions Application Fee Web Service
Many institutions will require an application fee and to verify the availability of funds in order
to process an online admissions application. Typically, electronic payments for the application
fee must be authorized at the time the application is completed and submitted. So that
schools will not be faced with PCI Compliance issues inherent in such electronic payment
processing, we plan to provide the capability to connect with a third party host that will
perform the electronic data collection and storage. Proposed features are:
• Calculation of the admissions application fee, when required.
• Invoke Hosted Payment for payment of the Admissions Application Fee (AAWS), when
required.
• Update of staging record with outcome of payment
• Provide ability to send revenue directly to the General Ledger Summary
• Admissions Application Fee Waivers
Institutions that require an application fee will typically manage a process for waiving the fee
following an applicant request accompanied by the appropriate supporting information.
Proposed design features include:
• Ability to configure an admission application transaction to require an application fee or a
waiver request at the point that an online application is submitted.
• Ability to configure an admission application transaction not to require an admission fee or
a waiver request to allow an applicant the ability to submit an application without
interruption.
• Add logic to delivered submit processing that will recognize the Application Fee/Waiver
Configuration.
• On the Application Transactions staging component, allow administrative users to search
for those applications from applicants requesting a waiver utilizing appropriate Application
and Fee statuses for waivers approvals and further processing.
Additional updates targeted in Admissions and Recruiting for FY 2011 include:
• Revised ACT Electronic Record Layout (8.9, 9.0)
16
To accommodate specifications from the testing agency, updated Layout changes are targeted
for the following items:
o Race/Ethnicity
o Disability
o Major
o Occupation
o Family Income
o Religious Affiliation
To accommodate specifications from the testing agency, we are targeting the following new
data items
o Type of Telephone
o Mother/Guardian 1 Education Level
o Father/Guardian 2 Education Level
o Race/Ethnicity - IPEDS
• Universities and Colleges Admissions Service (UCAS) Updates and Enhancements (UK)
o Support for the 2011 admissions cycle for UCAS and Graduate Teacher
Training Registry (GTTR).
o Additional staging data pages to view and correct imported applicant and
application data.
o Application Center security added to decision processing pages.
• Studielink 3.1 (NLD)
o Legislative updates regarding the “NLD Continuous Enrollment” education
model.
Student Records Planned Features

In response to customer recommendations, Student Records projects are planned for the next 12
months. Oracle Campus Solutions continues to engage with the Student Records Product
Advisory Group and other customers to identify and consider important enhancements. At the
time of publication of this document, some of the updates targeted for FY 2011 include:
• Post Enrollment Pre-requisite checking (9.0)
While current functionality allows students to enroll in classes without having met pre-
requisites satisfied by in-progress coursework, the Student Records community has
consistently requested a delivered method for re-checking and managing non-compliance.
Planned features for post enrollment pre-requisite checking include:
17
o A new administrative component to display requisite data with the ability to

re-evaluate each enrolled students for compliance.
o Ability to identify and view students who have not complied with class
section prerequisites.
o Provide appropriate level of information about the student who is not in
compliance.
o Ability to review and decide which students who are not in compliance are to
be dropped from the class section.
o Ability to assign an administrative drop from a class section for students
who have not complied with the pre requisite(s).
o Ability to batch drop students from a class section determined to be
ineligible.
o Ability to notify students who have been dropped from a class due to non-
compliance.
• Administrative Class Schedule and Roster Updates (9.0)
o Administrative Class Roster Updates: Bring administrative class roster in line
with the self service class roster including the notify feature.
o Administrative Class scheduling: To assist with ease of use, display class units
on the administrative schedule of classes component. Identify and display
related class sections within the class associations component.
• Higher Education Statistics Agency Updates (UK)
o Updates for the 2010/11 Student, Aggregate Offshore and Initial Teacher
Training (ITT) returns.
o Flat file creation for Destination of Leavers from Higher Education (DLHE)
return.
• BRON BVE –Professional Education (NLD) Updates
Important technological alignment and updates concerning enhanced configurability are
planned for Basis Register Onderwijs BVE including:
o Migrate BRON process to current technology standards (application package
& application engine)
o Introduction of Population Selection to process run control (improved
performance and user control)
o Expand current configurable set-up to minimize hard coded processing and
add user control for data selection
o Add configurable set-up to control triggering of BRON mutations
o Prepare interface for move from delivery method ASCII file to delivery
method XML messaging
18
o Provide a single source of code for BRON process and BRON Snapshot
Compare
Academic Advisement Planned Features

Campus Solutions continues to engage with an active user community and with the Academic
Advisement Product Advisory Group to identify and consider important modifications and
improvements for Academic Advisement functionality. At the time of publication of this
document, some of the targeted updates for FY 2011 include:
• Ability to link course attributes of the course catalog to course list.
o Provide a derived course list that points to course attribute values.
• Equivalent courses: removed from the display of available courses
o When a given course has been used to satisfy a specific degree requirement,
remove its equivalent from the list of available courses.
• Text-only rules
o Enhance existing functionality for displaying informational text.
o Make optional the display of the status indicators, Satisfied or Unsatisfied.
o Design to work with existing print and reporting controls.
Student Financials Planned Features

Student Financials provides support for billing and collecting tuition and fees along with other
related student charges, payment plans, refunds, global invoicing, and workflows. A key part of
managing student receivables is disbursing financial aid.
A number of projects planned for the upcoming year involve Student Financial enhancements in
support of other business functionality. Some of the planned enhancements for FY 2011
include:
• AP direct deposit to support Student refunding; this is a long standing customer request, which
improves the refunding solution for AP and supports the CS-HCM integration solution
o Enhance AP refunding to include direct deposit
o Enhance SF Self Service to allow students to enter bank information for
direct deposit
o Provide SF administrative components for AP direct deposit
• Application Fee and Payment; this functionality supports the delivered Admissions Application
Web Services feature
o Assessment of online application fee
o Integration with Hosted Payment
19
o Process to send application fee revenue to General Ledger

• Graduation Application Fee and Payment; this functionality supports the planned Graduation
Processing feature
o Assessment of on line application fee
o Integration with Hosted Payment
o Process to send application fee revenue to General Ledger
• 1098T Delivery (annually in July)
Financial Aid Planned Features

Financial Aid professionals live in an ever-changing world of highly regulated compliance while
striving to most efficiently deliver financial aid to students - all the while counseling students and
parents on financial options.
Regulatory Updates are delivered in each of the four scheduled maintenance bundles per year:
• October Bundle – Regs 1: ISIR load, INAS-IM, PROFILE, Return of Title IV
• January Bundle – Regs 2: Database Match and Eligibility updates, NSLDS, Verification, COD
Processing updates for Direct Lending, Pell Grants, ACG/Smart
• April Bundle – Regs 3: Redeliver INAS-FM, Pell Schedules, Commonline Updates
• July Bundle – Regs 4: FISAP, Satisfactory Academic Progress
There are often additional updates we deliver, based on mandates from the US ED or other
country’s legislative changes.
Some of the enhancements (in addition to annual regulatory updates) planned for FY 2011
include:
• Enhancements to the Population Selection/Update Process
o Ability to insert, update and delete user edit messages. Updating the status
field can be used to turn off the edit during disbursement processing.
Deleting edits can be used for fixing mistakes. This is a new Population
Select process.
o Provide a pop select/pop update process to update loan period start/end
dates and academic year start/end dates on loan origination record.
o Add the VERIF_STATUS_CODE to Population Update. In using
Population Update Setup, the field VERIF_STATUS_CODE is not available
on the STDNT_AID_ATRBT table however, VERIFICATION_STATUS
is available. Customers would like to be able to update both fields. Also, we
plan to enable Population Update to access the Budget Duration field.
20
• SAP – Enhancing SAP feature to give users ability to add or modify their own app engine
libraries. This gives customers flexibility to create and manage their own rules or calculations for
SAP.
• DL Loan Counseling – the Direct Lending Loan Counseling file has changed from flat file to
XML. It is now part of the COD process. Schools must ensure students do an entrance loan
counseling before any federal funds are disbursed. They must also make sure the student does
exit loan counseling when they leave the institution.
• Two planned phases of delivery:
o Phase 1 – load the new XML files to the COD staging tables (delivered in
May 2010 with Regs 4)
o Phase 2 - update the loan counseling application tables with the information
in the files. A new process needs to be completed to read from the COD
staging tables and do some additional logic based on new fields in the XML
file. We are working with the FA PAG on the requirements for this new
process.
Campus Solutions – Focus on the Enterprise

As mentioned earlier in this document, an important strategy for Oracle Higher Education is to
provide solutions to support the broader campus ecosystem, including academic support,
reporting and analytics, master data management and constituent relationship management. This
section highlights the planned enhancements in these areas for Oracle’s Fiscal Year 2011.
Planned Integration Between PeopleSoft HCM and Campus Solutions 9.0

Today, Campus Solutions applications (e.g., Student Administration, Contributor Relations) and
the HCM applications (e.g., HRMS, Talent Management, Payroll, Benefits) share a single
database, as well as core Person data. This means that both applications must upgrade an
instance at the same time which means the release schedules, and to some extent, the
maintenance schedules, need to be operated in lock-step. In order to provide the flexibility of
ongoing, less disruptive updates through a continuous delivery model, Campus Solutions (CS)
needs to be independent from the large upgrade event. Therefore, the Campus Solutions 9.0
codeline is not delivering an upgrade to a 9.1 release with the rest of the PeopleSoft product
families (e.g, HCM, Financials, CRM). Because Campus Solutions plans to deliver new features
and functionality on the 9.0 base, it is intended that CS will exist in a separate instance from
HCM 9.1.
The primary objective of this initiative is to allow Higher Ed customers to implement CS and
HCM in separate production database instances; Oracle plans to deliver integration to support
functionality equivalent to what is available in the existing combined products. The long term
benefits we expect customers will realize include the enhanced ability for the Campus Solutions
team to create a Higher Ed person model and structures that are tailored just to our industry.
21
This independence increases the options for the Campus Solutions team to chart our own course
to the next generation technology and application functionality. This Section covers the details of
this planned integration.
Business Challenges for Industry and Key Requirements

The PeopleSoft Enterprise Campus Solutions and HCM product lines reside in the same physical
database. CS and HCM functionality share a variety of data elements and processes, with the
Person being central to both applications. At the time PeopleSoft first developed CS products,
integration technologies were not advanced enough to develop the product line in a database
separate from HCM without relying on rudimentary batch file processes for integration of core
person data.
As early as 1999, pressure from higher education customers began for PeopleSoft to deliver the
Student Administration and HRMS applications in separate databases for numerous reasons. The
“tight coupling” of the applications created product management issues; customers cited
concerns over scheduling for application of maintenance (when could both systems be brought
“down” for maintenance), physical security, performance constraints and the size and complexity
of upgrades as chief reasons for wanting the product lines to be in separate databases.
With the HCM/CS 8.9 release, CS was logically separated (unique namespace, defined interfaces)
from HCM, but the product lines continued to be released in the same physical database. The
HCM/CS 9.0 release continued the support for logical separation of the applications, with
enhancements to the Person Model and services defined to support this Model. The impending
availability of the HCM 9.1 upgrade as well as the pressures to provide a more nimble, flexible
way to keep the CS product current pushed the Higher Ed team to move to the next phase of the
physical separation/logical integration.
Key Functional Requirements
Customers appreciate the core principle of “one person/one ID” built into the shared instance
of HCM/CS. In fact, the desire to know an individual by one identifier, regardless of their
relationship with the institution was one of the reasons PeopleSoft originally created the Student
Administration application within the HCM application; Campus Community is the result of this
design. Most institutions have many individuals who have multiple affiliations with the
institution simultaneously and across time: as an applicant (for either academic work or
employment), as a student, as an employee, as an alumnus. The structure of the single ID per
person (i.e., EMPLID in HCM/CS) is a high priority requirement, as is the complementary
ability to prevent adding that same individual to the database, using a different ID, a second or
third time (the dreaded “duplicate”!). As we have worked with customers on this initiative, we’ve
identified other important functional requirements for the solution supporting separate instances.
While not all of these requirements will be completely realized in the first phase of this project,
our efforts were guided by the following objectives:
22
• Assign one EMPLID per individual through time and across HCM and CS
• Prevent duplicates
• Synchronize core biographic-demographic data, security profiles and shared set up table values
• Maintain distinct population (the respective HRMS and Student departments maintain control of
the data for “their” population)
• Ability to use application-specific navigation
• Minimize impact on existing business processes
• Minimize financial impact to institution (e.g., new licenses)
• Minimize application of HCM maintenance to the CS instance
Primary Use Cases to be supported
Customers need support for the basic, everyday occurrences of individuals’ records existing on
more than one application. They need to know that they can trust they will see consistent
information about that individual when they access a person by their unique identifier (e.g. the
EMPLID), whether they are accessing him in HCM or CS.
The following use cases represent the primary functional integration points between existing CS
and HCM features. We consider support for the following use cases to be the basic requirements
for this initiative. Note that support for some use cases will be delivered in later phases of this
effort.
USE CASES PLANNED TO BE SUPPORTED
USE CASE DESCRIPTION PLANNED AVAILABILITY
Search for an Existing Person (Search / Perform Search / Match with results that include FY 2011
Match) both CS and HR persons
Add a Person in CS (applicant / student / Add a new Person in CS with that Person available FY 2011
alumni) when needed in HR transactions
Add an Employee Add a new Person with that Person available in FY 2011
HCM and, when needed, in CS transactions
Update Student personal information Update core personal data for a Student, e.g. an FY 2011
Address change
Update Employee personal information Update core personal data for an Employee, e.g. FY 2011
and Address change
Refund a Student Issue refund via HR Payroll or AP to a CS Student FY 2011

(AP may be preferred solution)
23
Hire a Student Hire a CS Person as an Employee (add FY 2011

Employment Instance)
FinAid Work Study Assign a work study job to an approved CS Future

Student. View Job and Earnings summary
Add a Faculty / Advisor in CS Identify an HCM Employee as a Faculty or Advisor FY 2011

in CS
Integration Approach
In designing this integration approach, the Campus Solutions team took a step back to evaluate
the elements of integration that provide the best functional support as well as minimize the
investment of effort for the IT staff. We didn’t assume the goal was to exactly replicate all the
synchronization that exists now in the shared instance. We were also aware that full bi-directional
syncing between separate instances – mimicking the shared instance functionality of an update to
Person data being immediately “available” to HCM and CS - was extremely difficult to achieve
using PeopleTools. Also, many of our customers struggle with controlling the ownership of
specific pieces of data, such as Driver’s License; they may not want to replicate all the data
sharing that exists today. Finally, customers want an uninterrupted business process flow, but
they don’t want to be constrained by one application in a database being unavailable, resulting in
all applications being unavailable. The preferred solution appears to be one which facilitates a
near real-time, asynchronous approach.
The key technical requirements we are attempting to address include:
• Provide standard integration points customers can utilize across a variety of business processes
• Provide a loosely-coupled solution, to minimize down-time
• Handle conflicts with shared data between HCM and CS
• Design supporting the flexibility to integrate with HCM releases (9.0, 9.1, 9.2) and, potentially,
other HCM products, such as the new Fusion products
• Introduce release independence, allowing future Higher Education specific enhancements to the
Person Model
These are the key technical requirements we want to support; beyond these, we found that
institutions have a wide range of business practice and technology solutions surrounding their
shared person model.
Continuum of Support for Person Integration
The Campus Solutions customer base, while largely using a shared single instance of HCM and
Campus Solutions, contains many examples of schools which have chosen to implement these
two applications in separate instances. Their approaches to integration fall along a continuum;
24
from no synchronization of person data to efforts to keep all the bio-demo data about the
individual synchronized between (or among) the key systems of HCM and Campus Solutions.
Therefore, we think the greatest benefit we can provide our customers is to approach building
this solution as a continuum of support, giving customers flexibility and choice.
Conceptual model of continuum of Person Integration
Physical approaches to the synchronization effort vary widely too; from nightly flat file updates,
to database links, to asynchronous messages to manual data entry.
One size doesn’t fit all. Oracle’s planned approach is to ensure customers are aware of the tools,
the utilities and the integration options available to them. Then, customers can determine which
model of integration best supports their business. Our approach can be captured as providing:
• Flexibility to support each institution’s unique business process requirements
• No prescribed solution
• Tools and Frameworks
• Capability for institutions to configure the way they need to do business
• Design patterns and best practices documents to provide guidance and assistance
The result needs to allow customers to run CS and HCM in separate database instances, with
delivered integration points such that equivalent product functionality is maintained and that
functional integration, data integrity, and consistency of processing is maintained.
Customer Profiles and Supported Integration
As noted, most customers today run a single combined CS and HCM instance in production.
There are a number of customers who have, on their own, separated production instances of CS
and HCM, and have defined their own custom integration to support this. As part of this
initiative, we plan to consider the following customer scenarios:
• Combined HCM/CS 9.0 - Existing customers running in a single combined HCM 9.0 instance.
These customers are expected to plan upgrades to HCM 9.1 at some point in the future.
• Custom separated CS and HCM - Existing customers running separated instances with custom
integration. These may be CS 8.9 and HCM 8.9, or CS 9.0 and HCM 9.0, or other similar
combination. These customers are expected to plan upgrades to CS 9.0 (if not there already),
and HCM 9.0 or HCM 9.1.
• New Installs - New customers implementing CS and HCM for the first time (9.0 or 9.1).
25
Customers are making plans to upgrade to HCM 9.0 (or 9.1) taking into account the Oracle
Lifetime Support Policy dates for those releases. Remember, the CS 9.0 release is on a
“perpetual” support schedule; each January, the support date for CS 9.0 is pushed forward
another 12 months.
Which instances of HCM and CS are included in this initiative? The proposed support for
separated instances includes:
• HCM 9.0 to CS 9.0
• HCM 9.1 (released in Q4 2009) to CS 9.0
• CS 8.9 to HCM 9.0 is not planned
• CS 8.9 to HCM 9.1 is not planned
• Integration of multiple CS 9.0 instances to HCM 9.0 (or 9.1) is not planned
The following caveats and some exceptions should be noted in the course of developing these
solutions:
• Some business process changes may be required to achieve the equivalent functionality in the
context of separated instances.
• Support for equivalent functionality may require several Phases of this initiative to deliver.
• Some functionality may not be supported in all solutions.
• Not all integrations will be mandatory - Customers may have some choice about what
integrations they want to implement.
Solution Architecture Approach
The existing shared instance enables a user to update biographic or demographic data on an
individual in one place (Campus Community or HCM person components) and those changes
are immediately reflected elsewhere in the online system; a single record for person data is
maintained. To achieve similar functionality when you have separate instances, you’d need to
deploy bi-directional integration. This means that when data is changed in either instance, the
other instance is synchronously updated. This synchronicity demands a tightly-coupled
environment, which has the same limitations in terms of independence that we are attempting to
overcome in this initiative. There is some risk inherent in synchronous integration; one of the
most concerning is the likelihood that data will get out of sync between the two instances. In
that case, the IT staff and user community have to deploy processes to ensure data is
synchronized. Because PeopleTools row-set based messaging architecture would not robustly
support bi-directional integration without undue or unsupportable risk of data de-
synchronization, Oracle chose to leverage a robust Master Data Management product, the
Higher Education Constituent Hub, to provide a full bi-directional solution for customers.
26
NOTE: The Higher Education Constituent Hub (HECH) is a separate product available from Oracle. You
can get more information about this product earlier in this document and on My Oracle Support.
On the other end of the continuum from bi-directional, synchronous integration, some
customers are leveraging batch file updates on a frequency dictated by the critical nature of the
information being synced. They follow data ownership policies which dictate which
department’s update will “rule” and update the other instance accordingly. For some business
processes, this hourly, nightly or weekly syncing of bio-demo data is deemed appropriate.
To this end, we will document and provide support for three approaches to synchronizing core
person data (and supporting tables and security profiles) between HCM 9.0 and 9.1 to CS 9.0.
Since Oracle has delivered a solution for bi-directional support (the HECH), the Campus
Solutions team focused our attention on aspects of the continuum that leverage “direct”
integration.
Three Approaches to support integration
Oracle plans to deliver tools, utilities and documentation to support the integration of core bio-
demo data and set up table information. Customers will have choice as to how much or how
little integration they feel they need to support. Our goal is to provide enhancements to the tools
(e.g., delivered services and handlers) and create comprehensive user guides to allow the
customer to implement the integration that fits for them. After considerable technical analysis
and conversation with customers, we plan to support three approaches to integration:
Distinct Ownership
In this approach, the customers will add and update core Person data in the respective databases
(duplicate instance maintenance); we plan to assure a single EMPLID is assigned via External
Search/Match in both instances.
• Person is added and personal data updated in the “appropriate” (CS or HCM) database
• External Search/Match used in both HCM and CS to support using a single EMPLID for each
person (shared across both databases)
• Minimal integration of person data; customer has to duplicate data maintenance in both instances
Owner/Subscriber
The second approach has Campus Solutions as the system of record for most Person data while
HCM is the system of record for the set up tables.
• Point to Point integration: CS as Owner/HCM as Subscriber
• Use of PeopleTools integration capabilities
• Person_Basic_Sync is the integration mechanism for “core” Person integration
27
Higher Education Constituent Hub (HECH)
In the third approach, the customer uses the HECH to manage true bi-directional data flow
between CS and other campus systems.
• Based on the Siebel UCM Master Data Management product
• Comprehensive solution for full campus integration, including CS and HCM
• Single point of truth for person bio-demo data
• Optional embedded Data Quality and Address Cleansing engines
• Customers license separately and create integration to CS, HCM and other campus systems
More information about these specific approaches will be included in the Release Value
Proposition for the Feature Pack including this functionality.
Scope of Data to be exchanged

The data represented in the planned CS to HCM integrations can be summarized into the
following five general categories:
• Core Person (Name and Contact information)
• Constituent Data (extended person related information)
• Payroll (objective is the potential for support of Student Refunding and Financial Aid work
study)
• Job data
• Setup data (HRMS setup tables)
These are the data elements planned to be included in messages to support integration of core
bio-demo data as well as User profiles (security):
• Person
• Person Name
• Person Address
• Person Phone
• Person Email
• Person National ID
• Person Diversity
• Person Historical Data (Marital Status, Veteran, Country specific, Photo)
• Person Identification Data
28
• Person Citizenship
• Person Visa Data
• Search/Match
• Payroll (specific elements TBD)
• Job
• User Profiles
These are the data elements planned to be included in messages to support integration of set up
table values:
• Country Table
• States Table
• HCM Business Units
• Company Codes
• Departments
• Job Codes
• Locations
• Regulatory Regions
• SetIDs
• TableSet Controls
• National ID Types
• Address Types
• Name Prefixes
• Name Suffixes
• Name Titles
• Name Types
• Name Formats
• Visa Permit Types
• Visa Permit Documents
• Citizenship Status
• Ethnic Groups
29
• Holiday Schedules
• Major Codes
• POI Type, Person POI Type
• Job Position
• Occupational Codes
• Person Org Assignments
Student Refunding
Customers using PeopleSoft Payroll for refunding to their student population can continue to do
so as long as they maintain North American Payroll in the CS instance. This means that
customers will need to apply Payroll maintenance to the CS instance.
We also plan to support student refunding through Accounts Payable; we plan to deliver the
capability to handle direct deposit within A/P for customers moving to the separate instances.
Tools to support CS to HCM Integration

There are a number of web services and other utilities that the CS and HCM teams plan to
deliver to support the integration. Some of these tools already exist; others are being enhanced.
The chart below lists some of the tools that customers either have available now or which Oracle
plans to deliver.
The categories of these tools include:
• Person Basic Sync – this is the core service that enables publish and subscribe for Person data
• External Search/Match Services – these services, delivered in CS 9.0 FP1 enable searching
against a separate instance of HCM or against a data hub, such as HECH
• HECH services – these services, including Constituent Web Service, delivered with CS 9.0 FP1,
enable publish and subscribe to person data, as it is used by the Higher Education Constituent
Hub
• Set up Table EIPs - these services support publication of the data values in the core set up tables
needed by both HCM and CS
PLANNED TOOLS TO SUPPORT HCM / CS INTEGRATION
TOOL DESCRIPTION PLANNED AVAILABILITY
Person Basic Sync Core person data between CS and HCM FY2011
Workforce Sync Workforce related data between CS and HCM FY2011
30
HCM set up messages Set up tables, one-way integration FY2011
External Search / Match Finds existing person records in separate database FY2011
Application Portal Aggregate navigation for HRMS and CS FY2011
Application Portal Related Content functionality (embedded With Tools 8.5

navigation support for HCM and CS)
Extended Person data messages Extensions to Core person data (e.g., Driver’s HCM Future
License
Constituent Web Service / Affiliations Core person data with SA extensions, sourced FY2011
from CS
HECH Master Data Management solution that supports bi- Now

directional update
HECH-specific transformation, routings Support for CS – HECH integration FY2011

and logic
Reconciliation reports and utilities Assist with reconciliation efforts Future
Documentation
In addition to updated PeopleBooks, we plan to create several Developer Guides that will
provide support for customers implementing the integration between CS and HCM. The intent
is that these Guides will provide a comprehensive outline of how to use the various services and
utilities from Oracle to achieve the desired integration configuration. The Guides we plan to
deliver are:
• Connecting the Higher Education Constituent Hub to Campus Solutions
• Connecting Separate Instances of Oracle PeopleSoft HCM to Oracle PeopleSoft Campus
Solutions: Owner/Subscriber Model
• Connecting Separate Instances of Oracle PeopleSoft HCM to Oracle PeopleSoft Campus
Solutions: Distinct Ownership Model
• Configuring PeopleSoft Enterprise or Application Portals for Aggregate Navigation for Oracle
PeopleSoft HCM and PeopleSoft Campus Solutions
Conclusion
Customers will want to evaluate the level of integration that is needed for their business. The
business owners on campus will need to coordinate the analysis and decisions about how they
should best manage the Person data on campus: Which data must be kept in sync, if any? Who
is the “owner” of each Person data element, considering the affiliation of the person to the
31
institution? How many other systems on campus need to know that particular data? How should
EMPLIDs be managed? Our intent is that the Guides we plan to produce will assist customers as
they make the individual decisions that will then point to the desired level of integration. From
that point, they can deploy the services and other tools to realize that integration level.
With the adoption of the continuous delivery model, allowing CS to operate independently of an
HCM instance is fundamental to the future of Campus Solutions and to the new release model.
Achieving this separation and resulting integration permits customers and the CS team to
develop, deploy and upgrade new functionality independently. Oracle’s goal is to maintain
equivalent functionality for business process while creating the infrastructure for growing the
student and alumni product of the future.
Graduation Processing
Colleges and Universities are always looking for ways to automate processes and improve their
efficiency. One of the key Higher Education business processes is the graduation process. Oracle
plans to deliver new functionality to enable schools to support this key business process,
including:
• Incorporation of Population Selection in the graduation review processes to identify potential
graduation candidates based on institution determined qualifications.
• Expansion of the existing self-service graduation process and providing self-service graduation
fee payment.
• Delivery of new processes to track the candidate’s status thru the graduation review process
from potential degree candidate to the awarding and posting of degrees.
• Delivery of new processes to support the review and clearance of potential candidates as well
as the finalization and posting of the degree and graduation statuses.
Campus Solutions Warehouse (An EPM 9.1 Solution)

PeopleSoft Campus Solutions Warehouse provides a powerful foundation for making more
informed, strategic decisions about your recruiting efforts, course offerings, and student
population. PeopleSoft Campus Solutions Warehouse is comprised of four content-specific data
marts which, when deployed together, constitute a comprehensive, integrated analytic platform.
These data marts can also be deployed modularly to accommodate your specific business or
budgetary requirements. The four data marts are: Admissions and Recruiting, Student Records,
Campus Community and Student Financials.
During the last twelve months, several content enhancements were added in the different data
marts. All the content enhancements were customer driven and the goal of adding the new
content was to allow more deep and detailed analysis. The content enhancements described in
32
this document were delivered both on top of 9.0 and on 9.1 releases. These delivered
enhancements to the Admissions and Recruiting data mart included:
• Enhancements on Applications test score analysis
A new table was added in the warehouse to facilitate analysis of test score when the
information needs to be linked to applications. The table was added in the Admissions and
Recruiting data mart and added in the Oracle Business Intelligence Enterprise metadata (.rpd
file) that is included in the Fusion Campus Solution Intelligence product.
• New CSW Admissions and Recruiting dashboards
A new Oracle Business Intelligence Enterprise Edition Admissions and Recruiting dashboard
that includes several new reports was delivered in Fusion Campus Solution Intelligence.
The Admissions and Recruiting dashboard is designed for director-level staff members who
manage the overall admissions processes and oversee admissions officers and counselors. With
the Admissions and Recruiting dashboard the school can:
• Obtain a comprehensive view of recruiting and admissions for your institution.
• Identify and correct negative trends in recruiting and admissions.
• Measure inefficiencies in recruiting and admissions.
The new dashboard includes 5 new dashboard pages:
• Admissions and Recruiting Dashboard - Overview Page (which includes an Admissions
Funnel Report that provides a birds eye view of the Prospect to applicant to admit and
enrollees numbers, ratios and yields for an institution.
• Admissions and Recruiting Dashboard - Recruiting Effectiveness Page
• Admissions and Recruiting Dashboard - Admission/Application Process Page
• Admissions and Recruiting Dashboard - Diversity Analysis Page
• Admissions and Recruiting Dashboard - Admissions Trend Analysis Page
Note: for more information regarding the delivered dashboard and report, please refer to the PeopleSoft
Fusion Campus Intelligence 9.1 PeopleBooks.
• New ethnicity table
A new ethnicity dimension was added in the Campus Solution Warehouse to accommodate the
changes introduced in PeopleSoft CS to support the new race and ethnicity IPEDS
requirements. The new dimension table allows Institutions to report the new ethnicity values.
• Campus Solution Warehouse 9.1 release and certification of IBM WebSphere DataStage 8.1
In April 2010, PeopleSoft EPM 9.1 became generally available. PeopleSoft EPM 9.1 is
delivered and certified with IBM WebSphere DataStage Server Edition 8.1. PeopleSoft EPM
9.0 continues using DataStage 7.5.x.
33
Note: For more details regarding PeopleSoft EPM 9.1 please refer to PeopleSoft EPM 9.1 release notes.
Campus Solutions Warehouse – Planned Features

During the next 12 months, Oracle plans to deliver:
• CRM for Higher Education Analytics: New content and new analytics will be delivered in the
Campus Solutions Warehouse. Oracle plans to deliver a new funnel report that will take data
from PeopleSoft CRM and will combine that information with data from PeopleSoft CS. That
new report will be incorporated in the Campus Solution warehouse and Fusion Intelligence
products. Additional analytics will also be delivered to support measuring Marketing Campaign
effectiveness and Recruiting effectiveness.
• Snapshot capabilities to support Institutional Research/Planning office needs: Oracle
also plans to include additional functionality in the warehouse to better support snapshot
capabilities, which is needed to satisfy Institutional Research needs.
• Certification of Oracle Business Intelligence Enterprise Edition 11g: Oracle plans to
certify PeopleSoft Fusion Campus Solution Intelligence with the new version of Oracle Business
Intelligence Enterprise Edition (OBIEE 11g).
The Longer Range Roadmap

In the past few years, higher education institutions around the globe have begun to use Campus
Solutions to improve their operations and to gain efficiencies in the delivery of services to their
students and faculty. Many of these institutions have different requirements and processes for
enrolling than in the U.S. Many times, these students enroll into a prescribed set of classes based
on their Program of Study and the particular year or stage, of enrollment. This model is also used
in the U.S. and other countries for a variety of programs and cohorts, including some vocational
and professional programs. Oracle has an initiative underway to enhance the Campus Solutions
enrollment processes to support this more structured enrollment process.
34
Conclusion
Oracle continues to listen to its higher education customers and has responded to their
requirements by providing integrated solutions to help them meet the increased need for
transparency, meet regulatory demands, improve performance and reduce costs. In addition,
Oracle knows that higher education institutions must make technology investments that are
strategic and provide measurable value and return on investment not only to the institution, but
to all its constituents—prospects, applicants, students, faculty, alumni, donors and other funding
organizations.
In response to customer needs, PeopleSoft Campus Solutions 9.0 and its planned enhancements
for the next 12 months are expected to build on the innovations in earlier releases by advancing
functional excellence, adding powerful business intelligence, and extending the services
framework to enhance integration.
35
Campus Solutions 9.0
August 2010
Copyright © 2009, Oracle and/or its affiliates. All rights reserved. This document is provided for information purposes only and
the contents hereof are subject to change without notice. This document is not warranted to be error-free, nor subject to any other
Oracle Corporation
warranties or conditions, whether expressed orally or implied in law, including implied warranties and conditions of merchantability or
World Headquarters
fitness for a particular purpose. We specifically disclaim any liability with respect to this document and no contractual obligations are
500 Oracle Parkway
formed either directly or indirectly by this document. This document may not be reproduced or transmitted in any form or by any
Redwood Shores, CA 94065
means, electronic or mechanical, for any purpose, without our prior written permission.
U.S.A.
Worldwide Inquiries: Oracle is a registered trademark of Oracle Corporation and/or its affiliates. Other names may be trademarks of their respective
Phone: +1.650.506.7000 owners.
Fax: +1.650.506.7200
oracle.com 0110

Peoplesoft Campus Solutions 9.0 Statement of Direction Fy 2011

Hochgeladen von

Dokumentinformationen

Originalbeschreibung:

Originaltitel

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

Peoplesoft Campus Solutions 9.0 Statement of Direction Fy 2011

Hochgeladen von

Copyright:

Verfügbare Formate

July 2010

PeopleSoft Campus Solutions 9.0

Planned Integration Between PeopleSoft HCM and Campus Solutions 9.0

The purpose of this document is to provide an annual update to the PeopleSoft

Several seemingly conflicting requirements emerge in what institutions need from

• More flexibility but lower costs

• Increased collaboration but more security

• Comprehensive yet open and standards-based solutions

Technology investments institutions make must be strategic and provide measurable

PeopleSoft Campus Solutions Drivers

PeopleSoft Campus Solutions: The Year in Review

Campus Community – Prior Year Updates

Constituent Web Service Scope

Institutions need to know all the “relationships” or “affiliations” an individual or organization

Contributor Relations – Prior Year Updates

Recruiting and Admissions – Prior Year Updates

Student Records – Prior Year Updates

Academic Advisement – Prior Year Updates

Student Financials – Prior Year Updates

Additional Accounting Date Option and Line Validation

Integration to Oracle E-Business Suite General Ledger

Hosted Payment for ePayments (Credit Cards and eChecks)

Integration Broker Support for ePayment Processing

Credit Card - Card Verification Value (CVV) Support

Financial Aid – Prior Year Updates

Year-Round Pell updates

Perkins Loan Master Promissory Note (MPN) updates

College Scholarship Service (CSS) XML Profile support

Financial Aid Regulatory Updates

SAIP: Student Administration Integration Pack

Constituent Relationship Management – CRM for Higher Education

Master Data Management for Higher Education

PeopleSoft Campus Solutions: Planned Features

Additional Campus Community Planned Features

Some of the expected enhancements targeted for FY 2011 include:

Contributor Relations Planned Features

Admissions and Recruiting Planned Features

Student Records Planned Features

o A new administrative component to display requisite data with the ability to

Academic Advisement Planned Features

Student Financials Planned Features

o Process to send application fee revenue to General Ledger

Financial Aid Planned Features

Campus Solutions – Focus on the Enterprise

Planned Integration Between PeopleSoft HCM and Campus Solutions 9.0

Business Challenges for Industry and Key Requirements

Key Functional Requirements

Primary Use Cases to be supported

USE CASES PLANNED TO BE SUPPORTED

USE CASE DESCRIPTION PLANNED AVAILABILITY

Refund a Student Issue refund via HR Payroll or AP to a CS Student FY 2011

Hire a Student Hire a CS Person as an Employee (add FY 2011

FinAid Work Study Assign a work study job to an approved CS Future

Add a Faculty / Advisor in CS Identify an HCM Employee as a Faculty or Advisor FY 2011

Continuum of Support for Person Integration

Conceptual model of continuum of Person Integration

Customer Profiles and Supported Integration

Solution Architecture Approach

Three Approaches to support integration

Higher Education Constituent Hub (HECH)

Scope of Data to be exchanged

Tools to support CS to HCM Integration