About the significance of ESM in HCM - CS Split

1. HCM – CS Split &
External Search Match
Lessons from Implementation

2. Why the Split?
 Customers requested an approach that allowed for independent upgrades
and maintenance of HCM and CS.
 Allows Oracle to prioritize and deliver HCM and CS features independently.
 Provides better service and more features in an incremental adoption.
Feature Packs for CS.

3. How Will “The Split” Affect My
Institution?

4. Integrating after the Split
 Reference Data (Setup)
Important to support transactional Integrations
 Person-Constituent Data
Several Models available for Integrating Person data between the two environments
 Transaction Data – Job
HCM Job Data to feed Instructors/Advisors to CS.
 Application Security
Roles, Permissions, User Profiles-Provisioning
 Integrations to Other Systems
Systems that feed the combined system will need to be configured to feed both systems.

5. Data Quality and Synchronization – Things to
take care
 Will your Institution systems have accurate person-information, for items such
as Emergency management systems during a critical event.
 Are you multiplying your efforts by dealing with data quality in each of your
integrations to third-party systems (rather than in a Hub)
 Complex and effort-intensive process to clean up duplicates once they have
transactional data and have been provisioned in n systems
 How good are reports, analytics and longitudinal analysis if the underlying
core person data is not reliable?

6. Integration Options
 Distinct Ownership (EMPLID Sync)
 Owner Subscriber (One consistent person record)
 Subscriber Only
 Full Bi-Directional (HECH)

7. Distinct Ownership

8. Owner Subscriber

9. Owner Subscriber Model
Benefits Constraints/challenges
• Reduces the likelihood of adding
duplicates
• Consistent person record, shared
between CS and HCM
• Handles large volume, batch loads
of Persons who enter through CS.
• Self-Service Personal data changes
in HCM would be disabled.
• Data for Recruiting solutions would
not be integrated to CS, requiring
some manual intervention.
• CS person components do not
provide row level security
available in HCM; hence all admin
users will have the same row-level
access
Pros and Cons

10. Subscriber Only Model
Benefits Constraints/challenges
• Provides minimal disruption to existing
business processes
• Ensures a single EMPLID for each
person across instances
• Allows for full batch load capability
(internal search/match, batch publish
of core Person bio-demo data)
• Allows full usage of HCM self-service,
eRecruitment, etc.
• “Last Wins” architecture. A
simultaneous or near-simultaneous
update in competing systems can result
in out-of-sync data, as can messages
that error out.
• No data governance or survivorship
rules.
• Requires additional (incremental) IT
involvement to setup and monitor
Integration points.
Pros and Cons

11. Setup Data
 Important to synchronize setup elements if Transactional data will be
integrated.
 Enterprise Integration Points (EIP) Available to synchronize one way.
 Some items now owned by CS, others will be managed by HCM.
 Setup Data is integrated independent of the Person Data Integration Model
selected.

12. Reference (Setup)
Data Delivered Integrations

13. Application Security
Integration and Other Considerations
 Delivered Integration Points for Security
User Profiles, Roles (including Dynamic roles), and Operator
defaults can be synchronized by enabling these EIPs.
 Data Elements in Subscribing Systems should be made Read-Only
This can prevent users from inadvertently changing, say Adding
a Name Type that will not be replicated to the other system.
 Navigation Links can be created in between environments
Help streamline business processes, particularly if a Portal is
not available for all user groups.
 Single Sign-on should be setup between environments.
 Provisioning to other systems such as LDAP should be considered in the
integration model

14. Business Process Impacted
 Search/Match
 Processes resulting in new person record
 Processes resulting in updated person record
 HR Recruiting processes
 Work-study students
 Self-service impacts (CS and HR)
 Student refunding
 Reporting

15. Integrating Campus
Solutions with Human
Capital Management

16. Quick Look on
 Integrate person data.
 Integrate using External Search/Match.
 Integrate using the higher education constituent hub (HECH).
 Integrate setup data.

17. Integrating Person Data
 Publish and subscribe to person data.
 Review integrated person data.
 CS-to-HCM integrated environment, the person record is physically separated.
 FP 4 has the tools
 Transferred by the PERSON_BASIC_SYNC
(Core data + Extension data like FERPA)

18. Owner-Subscriber Example One

19. Owner-Subscriber Example Two

20. Distinct Ownership Example One

21. Distinct Ownership Example Two

22. Distinct Ownership HECH Example

23. Publishing and Subscribing to Person
Data
 PERSON_BASIC_SYNC
 PERSON_DIVERSITY_SYNC
 PERSON_VISA_CITIZEN_SYNC
 PERSON_DISABILITY_SYNC
 WORKFORCE_SYNC

24. Integrated Person Data
Owner Subscriber Model
Names Gender Disability
Addresses Birthdate Ethnicity/Diversity
Phones Date of Death Citizenship
Email Addresses Marital Status Passport
National IDs FERPA Flag Visa/Permits
Job HR Operator Defaults User Profiles
Distinct Ownership Model
EmplID
Addresses
Names
Email Addresses
FERPA Flag
VA Benefit

25. Understanding HCM-to-CS Setup Data
Address Types
National ID Types
Ethnic Groups
HCMBusinessUnits
Currency Codes
Company Codes
MajorSubjectCodes
Country Codes
State Codes
Departments
Holiday Date
Schedules
JobCodes
Locations
Name Titles
Name Types
Name Prefixes
Name Royal Prefixes
Name Royal Suffixes
Name Suffixes
NameFormats
POITypes
Regulatory Regions
SetIDs
TableSetControls
U.S.StandardOccupational Codes
VisaPermitTypes
VisaPermitDocuments

26. Understanding EIP’s
And many more…

27. External Search Match
Setup and Use

28. What is it?
 Like the internal SM
 Integrates with any External System
 Search and import records against CC

29. Searchable Types
 Applicant (Not Enabled)
 Person
 Organization

30. Online Search Process

31. Auto Search Process

32. Setting UP ESM
 External Core Data Integration
Set Up SACR, Install > External Core Data Install
 External System Search Match Options
Set Up SACR, System Administration > Utilities > Search/Match > Search Match
with External Sys

33. Configuring External Core Data
Integration
 Set Up SACR > Install > External Core Data Install

34. Pages for Integrated Search
 Campus Community,Personal Information,Search/Match Integrated,Search
Criteria
 Set Up SACR, SystemAdministration,Utilities, Search/Match,Search/Match
Integrated,Search Criteria
+
Many more…

35. Importing the SM Result

36. Importing SM Result

37. IB Services
 SCC_SM_FETCH (Search/Match fetch service).
 SCC_SM_SERVICE (External Search/Match service).

38. Understanding External Search/Match
Web Services
 Internal Search/Match, External Search/Match, or both.
 XML message that contains all of the fields to search

39. Match Request Message
 The Match Request XML message exposes:
All of the search order numbers that can potentially return matching candidates.
Search fields.
Search data.
Search/Match configuration information.

40. Match Response Message
 The Match Response XML message (SCC_SM_SERVICE_RESP.V1) from the
external system contains:
Search order number/rule that found results.
Matching candidates.
Score.
Universal ID/cross reference.
Person data.

41. Fetch Request Message
 The Fetch Request XML message (SCC_SM_FETCH_REQ.V1) to the external
system contains the universal ID for which the Import or Detail buttons were
selected.

42. Fetch Response Message
 The Fetch Response XML message (SCC_SM_FETCH_RESP.V1) from the external
system contains the
 full constituent record

43. What Import Does?
1. The CS system creates an EmplID.
2. The CS system populates the SCC_HUB_MAP table with the EmplID and its
Universal ID.
3. The CS system publishes the PERSON_BASIC_SYNC message.
4. The CS system publishes an outbound constituent message (which includes the
Universal ID).
5. Using the Universal ID, the external system updates the constituent’s
reference table with a new EmplID.

44. Still Duplicates?
 Custom way to identify the duplicates
 Example: Duplicate Report

45. Appendix
 Implementing Integration of Set Up Data between CS and HCM on My Oracle
Support
 Implementing Person Bio-Demo Data Integration between CS and HCM on My
Oracle Support
 Implementing External Search/Match between CS and HCM on My Oracle
Support
 Implementing CS Integration with the Higher Education Constituent Hub on My
Oracle Support
 Implementing Portal Navigation aggregation for CS and HCM Integration on My
Oracle Support

46. Thank You!