Oracle Customer Hub (UCM) Master Data Management Reference > Configuring Oracle Higher Education Constituent Hub >

Scenarios for Using Oracle Higher Education Constituent Hub

This topic gives the following example of how Oracle Higher Education Constituent Hub might be used. You might use Oracle Higher Education Constituent Hub differently, depending on your business model.

• Adding a New Constituent in Oracle Higher Education Constituent Hub
• Updating a Constituent Record in Oracle Higher Education Constituent Hub
• Searching a Constituent Record in Oracle Higher Education Constituent Hub

Adding a New Constituent in Oracle Higher Education Constituent Hub

An administrator using a source application, such as Oracle's PeopleSoft Campus Solutions, adds a new constituent record. The constituent has different names, addresses, phone numbers, and email addresses. At the time the record is saved, a create message is published to Oracle Higher Education Constituent Hub. Oracle Customer Hub (UCM) accepts the create message and processes it through the matching and survivorship rules, resulting in either the creation of a new constituent or a link and update of an existing constituent. The response message is sent synchronously to the requester. In parallel, a create-and-update person message is published to the subscribing systems.

Updating a Constituent Record in Oracle Higher Education Constituent Hub

A campus solutions user updates a constituent record. The updated record is then sent to Oracle Higher Education Constituent Hub. It evaluates the update and applies the survivorship rules prior to updating the constituent's best version record. The updated record is then sent back to the requesting system. In parallel, the update person message is published to all other subscribing systems.

Searching a Constituent Record in Oracle Higher Education Constituent Hub

Prior to creating a new constituent record in campus solutions, an administrator searches Oracle Higher Education Constituent Hub to avoid creating a duplicate ID. The search results return information from the Name, Address, Phone, Email types, or Effective Start Date fields. The match request is sent to the Higher Education Constituent Hub with the search parameters. Oracle Higher Education Constituent Hub returns a list of candidates with the matching scores for the user to select. A query request is then sent to Oracle Higher Education Constituent Hub for selected candidates, and the candidate details are returned. If the candidate already exists in the requesting system, the cross-ref ID (for Campus Solutions, the ID is EMPLID) is returned. If the candidate does not exist in the system, the user can choose to import the data from Oracle Higher Education Constituent Hub in to the requesting system (Campus Solutions) and continue working on the new constituent.