Enterprise Integration Point Setup Between People Soft Enterprise Campus Solutions and People Soft Enterprise CRM

An Oracle Red Paper April 2011

Enterprise Integration Point Setup Between PeopleSoft Enterprise Campus Solutions and PeopleSoft Enterprise CRM

Red Paper: EIP setup between CRM and Campus Solutions

Introduction ......................................................................................... 1 Disclaimer ....................................................................................... 1 Structure of This Red Paper............................................................ 2 Related Materials ............................................................................ 2

Overview ............................................................................................. 4 Common Terms .............................................................................. 4 Integration Process Flow................................................................. 5 EIP Summaries ............................................................................... 8 Constituent Lifecycle Status Change ............................................ 25 Profile Choices Updates................................................................ 25 EIP Setup ...................................................................................... 25 Prerequisites ................................................................................. 26

Setting up and Testing EIP Configuration on CS Database.............. 26 Verify Local Gateway Properties................................................... 26 Verify HR Local Node and Connector ........................................... 27 Setting Up PeopleSoft CRM External Node and Connector ......... 28 Activating the Service Operations ................................................. 31 Setting Queues to Run state ......................................................... 32 Activating the Domain ................................................................... 33 Setting Up Single Signon .............................................................. 34 Testing the PeopleSoft CRM Node ............................................... 34

Setting up and Testing EIP Configuration on CRM Database........... 35 Verify Local Gateway Properties................................................... 35 Verify CRM Local Node and Connector ........................................ 36 Setting Up Campus Solutions External Node and Connector ....... 38 Activating the Service Operations and Handlers........................... 40 Setting Queues to Run state ......................................................... 42 Activating the Domain ................................................................... 42 Set up single signon...................................................................... 43 Testing the PeopleSoft CS External Node .................................... 43


Defining SetID for Inbound EIP Data ............................................ 44 Publishing the Full Sync Messages .................................................. 45

Defining Full Data Publish Rules................................................... 45 Setting Service Operation Security ............................................... 54 Granting Security for App Engine Processes and Pages.............. 56 SOA Based FullSync Messages ................................................... 57 SOA –NOTIFICATION HANDLER (FOR CRM to CS) .................. 60 Running PERSON_BASIC_FULLSYNC from CS to CRM............ 62 Populating Profile Attribute Choices from CS to CRM .................. 63 Cleaning Up Profile-Related Data Integrity in the CRM Database 64 Populating Student Data from CS to CRM.................................... 65 Publishing SOA based FullSync Messages .................................. 67 Incremental Sync EIPs.................................................................. 69 Inactivate Full Sync Messages...................................................... 70

APPENDIX I – Constituent 360-Degree View and Remote Query Setup 71 APPENDIX II – Troubleshooting ....................................................... 72 APPENDIX III – FullSync Publish Sequence .................................... 74 APPENDIX IV – Tables impacted by EIPs........................................ 76 APPENDIX V – Prospective Student Import, External Sources........ 80

Sample XML.................................................................................. 80 Tables and Fields.......................................................................... 82

Validation and Feedback................................................................... 87 Customer Validation...................................................................... 87 Field Validation.............................................................................. 87

Revision History ................................................................................ 88


Introduction

This red paper is a practical guide for technical users, installers, system administrators, and programmers who implement, maintain, or develop applications for your PeopleSoft system. In this red paper, we discuss guidelines on how to set up EIPs between PeopleSoft Campus Solutions (CS) and PeopleSoft Customer Relationship Management (CRM), including some troubleshooting tips and implementation notes.

Much of the information in this document originated within the Oracle Global Support Center and is therefore based on “real-life” problems that have been encountered in the field. Although this document does not address every conceivable problem that one could encounter with EIPs setup between CS and CRM, the issues that appear in this document are the problems that prove to be the most common or troublesome.

Disclaimer

This material has not been submitted to any formal Oracle test and is published as is. It has not been the subject of rigorous review. Oracle assumes no responsibility for its accuracy or completeness. The use of this information or the implementation of any of these techniques is a customer responsibility and depends on the customer's ability to evaluate and integrate them into the customer's operational environment. While each item may have been reviewed by Oracle for accuracy in a specific situation, there is no guarantee that the same or similar results will be obtained elsewhere. Customers attempting to adapt these techniques to their own environments do so at their own risk.

Information in this red paper was developed in conjunction with use of the products specified and is limited in application to those specific hardware and software products and levels.

Oracle may have patents or pending patent applications covering subject matter in this document. The furnishing of this document does not give you any license to these patents.

1


Structure of This Red Paper

This red paper provides guidance for setting up EIPs between PeopleSoft Campus Solutions (CS) and PeopleSoft Customer Relationship Management (CRM).

Oracle updates this document as needed so that it reflects the most current feedback from the field. Therefore, the structure, headings, content, and length of this document may vary with each posted version. To see if the document has been updated since you last downloaded it, compare the date of your version to the date of the version that is posted on My Oracle Support.

Related Materials

This paper is not a general introduction to PeopleSoft Integration Broker and is written for experienced IT professionals with a good understanding of the PeopleSoft Internet Architecture. To take full advantage of the information in this document, you should have a basic understanding of system administration, basic Internet architecture, integration technologies, relational database concepts and SQL, and how to use PeopleSoft applications.

This document does not replace the PeopleTools PeopleBooks, CRM PeopleBooks, and CS PeopleBooks. Before you read this document, you should become familiar with the PeopleSoft Internet Architecture information in the PeopleTools PeopleBooks to ensure that you have a well-rounded understanding of the technology.

Note. Much of the information in this document may eventually be incorporated into subsequent versions of the PeopleBooks.

The following guides discuss many of the fundamental concepts that are related to the PeopleSoft Internet Architecture:

• PeopleTools PeopleBook: Getting Started with Enterprise PeopleTools

2


3

• PeopleTools PeopleBook: PeopleSoft Integration Broker

• PeopleTools PeopleBook: PeopleSoft Integration Broker Administration

• Enterprise PeopleTools Hardware and Software Requirements

• PeopleSoft Enterprise Customer Relationship Management 9.1 Installation Guide

• PeopleSoft Enterprise CRM for Higher Education Developer’s Guide

• PeopleSoft Enterprise Online Marketing 9.1 PeopleBook

• PeopleSoft Enterprise CRM Supplemental Installation Documentation

• PeopleSoft Enterprise CRM 9.1 Business Object Management PeopleBook: Specifically the Integration with PeopleSoft HRMS or Third-Party HR Data section. This section discusses the common EIPs such as Country, State, and SetID, which should be run before the main EIPs described in this red paper.

Additionally, you should be familiar with the documentation that is delivered with Oracle Tuxedo, Jolt, and WebLogic.


Overview

This red paper is created to help customers setting up EIPs to integrate Oracle’s PeopleSoft Enterprise Campus Solutions (CS) 9.0 Feature Pack 2 and PeopleSoft Enterprise Customer Relationship Management (CRM) 9.1.

Before you begin setting up the integration, make sure to read the PeopleBooks and documentation mentioned on the previous page. Some of the EIP setup information can be found in the following documents:

• PeopleSoft Enterprise Customer Relationship Management 9.1 Installation Guide

• PeopleSoft Enterprise CRM for Higher Education Developer’s Guide

However, to make the CS/CRM EIP setup easier, the following processes and topics are documented in this red paper:

• How to set up EIPs between CS and CRM.

• What publish method to use – Enterprise Component or SOA

• The publish sequence for full sync messages.

• A list of the incremental sync messages with a brief functionality description.

• Navigation/path to the components from where the incremental sync messages are published.

Common Terms

The following table provides definitions for some of the common terms that are used in this guide.

COMMON TERMS

TERM DEFINITION

Enterprise Integration Point (EIP)

Commonly referred to as “EIPs,” these are asynchronous/synchronous services that push information such as changes to the values of fields to other systems as XML messages via Integration Broker.

Asynchronous

Message

Asynchronous messages are not real-time – the message is sent to be picked up at some later time by the receiving application’s message broker.

Message Basic unit of data sent from one web services agent to another in the context of web services.

SOA Service Oriented Architecture - An architectural style that supports integration of business processes as linked services that may be accessed when needed over a network.

4


COMMON TERMS

TERM DEFINITION

Web Service A web service is a set of related application functions that can be programmatically invoked over the internet, designed to support interoperable machine-to-machine interaction over a network, making it easy for applications to communicate.

Integration Process Flow

Two sets of Enterprise Integration Points (EIPs) are released for integrating CS and CRM: Full Sync EIPs and Incremental Sync EIPs.

When the setup is done initially, the Full Sync EIPs are published. Through these EIPs, setup information including academic structure, academic type and load, and school information is sent from Campus Solutions to CRM for Higher Education so that prospective students can be created in CRM. Additionally, security constructs including institution, career, program and plan security by user ID, and test ID security are sent to CRM for Higher Education so that PeopleSoft CRM for Higher Education respects the same security as the Campus Solutions system.

To publish Full Sync EIPs, two patterns of publishing are used:

• Enterprise Component Full Sync.

• SOA Full Sync.

This document details each Full Sync EIP with the needed setup for the required publishing pattern. All of the Full Sync EIPs are intended to be published only once to seed the required data from Campus Solutions to CRM. After they are successfully published, the Full Sync messages should be inactivated.

To provide a real time update from Campus Solutions to CRM for Higher Education, incremental syncs are included. As changes are made in Campus Solutions to the prospect, applicant, or student (including applicant status, change of program, plan, and so on), real time messages are sent to CRM so that CRM always has the most up-to-date information about that constituent, ensuring accurately targeted communications. The Incremental Sync EIPs populate the same tables in CRM as their respective Full Sync EIPs.

The figure below depicts the basic integration points:

5


Figure 1. Basic integration points

In CRM for Higher Education, the synchronized data is used mainly in:

• Marketing/Online Marketing and Sales.

• Constituent 360-Degree View.

• Support Center.

Marketing/Online Marketing and Sales

In CRM 9.1, a number of new features are implemented to help higher education recruiters to market to constituents effectively. Institutions can now keep the suspects and prospects in the CRM database, which helps them to keep the huge volume of suspects/prospects out of the CS database and use CRM to market to these potential students more effectively.

In CRM, suspects and prospects can manually be created or Prospective Student Import can be used to import them in bulk. Initially, the constituent information and setup data for Institution, Campus, Career, and so on is copied over from CS to CRM using various full sync EIPs. For each suspect and prospect, a Person record is created with the Individual Consumer role. The Academic component tracks constituent information along with Institute, Campus, Career, Program, Plan, Last School Attended, and so on.

6


Recruiters use PeopleSoft Marketing and Online Marketing to create audiences and run campaigns to market the institution and specific programs and plans to the prospects. The Person Data Extend EIPs are used to copy constituent information such as Admission Interests, Extracurricular Activities, and so on from CS into their respective profiles in CRM. These profiles can then be used to create target audiences.

Using CRM Sales, a lead or opportunity can be created and assigned to a recruiter to work with a prospective student. Lead and opportunity components are enhanced to store higher education specific information for the prospect. The recruiter can follow up on the lead and track the progress of the prospect through the multiple lead statuses available.

Once the prospect is ready to apply for a specific Program and Plan, an applicant is created in Campus Solutions and a message is sent to CRM that determines whether that person already exists as a prospect and, if so, updates him or her to the status of applicant. From this point forward, the constituent is maintained in Campus Solutions and all the lifecycle status changes are sent across to CRM through EIP messages so that the Constituent Lifecycle Status remains in sync between the two systems. Additionally, if CRM has captured any official or self-reported test scores or information related to the applicant, that information is published to Campus Solutions through the Test Score EIP because it might be required as part of the application evaluation process.

Constituent 360-Degree View

The 360-degree view in CRM has been expanded to provide Higher Education specific information to aid institutions in building and maintaining relationships with constituents.

From the Constituent 360-Degree View component, a user can search and open the 360-degree view for a constituent. At this point, a synchronous request is sent to the CS system, which uses the 360-aggregation service to collect and send the data to be displayed for the following sections in the Constituent 360-Degree View:

• Constituent Summary

• Checklists/Communications/Comments

• Admissions

• Transfer Credits

• Academics

• Finances

• Financial Aid

• Transcript Request

• Contributor Relations

• Affiliations

7


It is quite valuable to see the relevant student data alongside the CRM data for a complete view of the constituent.

Support Center

In CRM 9.1, the Case component is enhanced to track Constituents information on the case itself.

A constituent can create a case by using different channels such as Self Service, Email, Chat, or a telephone call to support center. When an agent is engaged, the agent can use Constituent 360-Degree View to identify the constituent, which provides a complete view including student and employee information and case history information in a single screen.

The agent can create a case from the Constituent 360-Degree View itself. The case displays constituent information such as Institute, Career, Lifecycle Status, Program, Plan, and so on that helps the agent to manage the case more effectively. All the basic person information and the high-level academic information is synched up from Campus Solutions to CRM through a number of EIPs detailed in this document.

Action Links are also provided to enable users to seamlessly navigate between the Service Center for Higher Education and PeopleSoft Campus Solutions transactions.

EIP Summaries

Following are the basic descriptions of EIPs, their publishing trigger points in CS, and the CRM components that use the synchronized data:

SSR_ACAD_PROG_SYNC EIP

SSR_ACAD_PROG_SYNC is designed to publish any transactional changes that are made to the Student Records Academic Program entity (create, update, and delete transactions from batch or online, self-service or administrative). It has a Full Sync equivalent, SSR_ACAD_PROG_FULLSYNC.

Published from:

1. Student Academic Program/Plan Component: This is the main SR online component in which a student's academic program, plan, and subplan information can be maintained. Path: Records and Enrollment, Career and Program Information, Student program plan

2. Quick Admit component: Rapid-entry component that creates a new person and activates him into an academic career, program, and term. Path: Records and Enrollment, Enroll Student, Block Enrollment, Quick Admit a Student

3. Self-Service Graduation Apply component: This component updates a student’s Program/Plan stack with a new effective-dated row and a program action of Data Change. It also updates the student’s degree checkout status to Applied. Path: Self-Service, Degree Progress/Graduation, Apply for Graduation

8


4. Add Application: Main Admissions component to create bio/demographic and academic information for an applicant. Path: Student Admissions, Application Entry, Add Application

5. Maintain Application: Main Admissions component to maintain an applicant's academic program information. Matriculation can also be initiated from this point. Path: Student Admissions, Application Maintenance, Maintain Applications

6. Program Addition: This component allows a new program to be added to an existing application. Path: Student Admissions, Application Maintenance, Program Addition

7. Action/Reason Entry: Rapid-entry component to update multiple applications to an identical program action. Path: Student Admissions, Application Maintenance, Action/Reason Entry

8. Post Degree: A program action of Completion of Program on the Student Program initiates the Degree Posting process. Path: Records and Enrollment, Career and Program Information, Student

9. Program/Plan Revoke Degree: A degree can be revoked by entering a Program Action of Revoke Degree. Path: Records and Enrollment, Career and Program Information, Student Program/Plan

10. Student Academic Info component: This is a view only page. However, on clicking the Update Edit Program Data button, student is redirected to Student Academic Program/Plan Component. Path: Campus Community, Student Services Ctr

11. Student Activation and Term History components Path: Records and Enrollment, Student Term Information, Term Activate a Student Records and Enrollment, Student Term Information, Term History

12. Student Financials components Path: GRP_QUICK_POST Student Financials, Charges and Payments, Post Student Transaction STUDENT_PAYMENTS Student Financials, Cashiering, Post Student Payments CSH_POST_RCPT Student Financials, Cashiering, Post Receipts SSF_SS_PAYMENT Self Service, Campus Finances, Make a Payment

This EIP is also published from the following batch processes:

1. Studielink Inbound Process: Netherlands centralized admissions and enrollment system localized load process. Path: Student Admissions, Processing Studielink NLD, Process Studielink, Post Studielink Messages

9


2. Activate Applicants: Batch driver for matriculation process. Path: Student Admissions, Processing Applications, Activate Applicants

3. Graduation Reporting: This process can award degrees in batch, create transcript request for processed students, and make associated program stack changes. Path: Records and Enrollment, Graduation, Graduation Reporting

4. SFPQDPST.cbl: Student Financials Subsystem - Group Posting Program. Path: Student Financials, Charges and Payments, Group Processing, Post Transactions

5. SF-Credit Card Payments: Student Financials – Credit Card Payments. Path: Student Financials, Charges and Payments, Electronic Transactions, Electronic Payments, Process Credit Cards Student Financials, Charges and Payments, Electronic Transactions, Electronic Payments, Process Electronic Check

6. The synchronized data is used in CRM in: Component: Academics (Program and Plan tab). Path: Customers CRM, Academics Information, Academics

SSR_ACADINST_SETUP_SYNC

SSR_ACADINST_SETUP_SYNC is designed to publish any transactional changes that are made to the Institution Setup Data (create, update, and delete transactions from batch or online, self-service or administrative). Its Full Sync equivalent is SSR_ACADINST_SETUP_FULLSYNC.

Published from:

Set Up SACR, Foundation Tables, Academic Structure, Academic Institution Table

The synchronized data is used in CRM in:

Component: Academics (Career tab). Path: Customers CRM, Academics Information, Academics

Component: Constituent 360-Degree view Path: Constituent 360-Degree View

Component: Lead Path: Sales, Search Leads

Component: Opportunity Path: Sales, Search Opportunities

SSR_ACADCAMP_SETUP_SYNC

SSR_ACADCAMP_SETUP_SYNC is designed to publish any transactional changes that are made to the Institution Campus Setup Data (create, update, and delete transactions from batch or online, self-service or administrative). Its Full Sync equivalent is SSR_ACADCAMP_SETUP_FULLSYNC.

10


Published from:

Set Up SACR, Foundation Tables, Academic Structure, Campus Table




SSR_ACADCAR_SETUP_SYNC

SSR_ACADCAR_SETUP_SYNC is designed to publish any transactional changes that are made to the Academic Career Setup Data (create, update, and delete transactions from batch or online, self-service or administrative). Its Full Sync equivalent is SSR_ACADCAR_SETUP_FULLSYNC.

Published from:

Set Up SACR, Foundation Tables, Academic Structure, Academic Career Table






SSR_ACADPROG_SETUP_SYNC

SSR_ACADPROG_SETUP_SYNC is designed to publish any transactional changes that are made to Academic Program and Home Campus Setup Data (create, update, and delete transaction from batch or online, self-service or administrative). Its Full Sync equivalent is SSR_ACADPROG_SETUP_FULLSYNC.

Published from:

Set Up SACR, Foundation Tables, Academic Structure, Academic Program Table


Component: Academics (Program and Plan tab). Path: Customers CRM, Academics Information, Academics

11





SSR_ACADPLAN_SETUP_SYNC

SSR_ACADPLAN_SETUP_SYNC is designed to publish any transactional changes that are made to the Academic Plan Set up Data (create, update, and delete transaction from batch or online, self-service or administrative). Its Full Sync equivalent is SSR_ACADPLAN_SETUP_FULLSYNC.

Published from:

Set Up SACR, Foundation Tables, Academic Structure, Academic Plan Table






SSR_ACADSUBPLAN_SETUP_SYNC

SSR_ACADSUBPLAN_SETUP_SYNC is designed to publish any transactional changes that are made to the Academic Sub Plan Set up Data (create, update, and delete transactions from batch or online, self-service or administrative). Its Full Sync equivalent is SSR_ACADSUBPLAN_SETUP_FULLSYNC.

Published from:

Set Up SACR, Foundation Tables, Academic Structure, Academic SubPlan Table




12


SSR_ACADTRM_SETUP_SYNC

SSR_ACADTRM_SETUP_SYNC is designed to publish any transactional changes that are made to the Academic Term Set up Data (create, update, and delete transactions from batch or online, self-service or administrative). Its Full Sync equivalent is SSR_ACADTRM_SETUP_FULLSYNC.

Published from:

Set Up SACR, Foundation Tables, Term Setup, Term/Session Table






SCC_EXT_ORG_SYNC

SCC_EXT_ORG_SYNC is designed to publish External Organization data, which includes Organization details, Location and Location Phones, Contact and Contact Phones, Department and Department Phones, and Organization School data. CRM requires only School information, though CS sends all External Org data. Its Full Sync equivalent is SCC_EXT_ORG_FULLSYNC.

Published from:

1. ORGANIZATIONS: Campus Community, Organization, Create/Maintain Organizations, Organization Table Set Up SACR, Install, CS Integration Points, CC Interface, External Organizations Contributor Relations, Constituent Information, Organizations, Organization Information, Organization Table Student Admissions, Internship Contracts NLD, Organizations

2. LOCATIONS Contributor Relations, Constituent Information, Organizations, Organization Information, Locations. Campus Community, Organization, Create/Maintain Organizations, Organization Locations.

3. DEPARTMENTS Contributor Relations, Constituent Information, Organizations, Organization Information, Departments. Campus Community, Organization, Create/Maintain Organizations, Organization Departments.

13


4. CONTACTS Contributor Relations, Constituent Information, Organizations, Organization Information, Contacts. Campus Community, Organization, Create/Maintain Organizations, Organization Contacts.

5. ORGANIZATION SCHOOL DATA Campus Community, Organization, Create/Maintain Organizations, Organization School Data


ATP Load (SQR Process ccatppst.sqr) Campus Community, Organization, Organizations Data Load, ATP Search/Match/Post

The synchronized data is used in CRM in: Component: Academics (Last School tab). Path: Customers CRM, Academics Information, Academics

SCC_SCHL_TYPE_SETUP_SYNC

SCC_SCHL_TYPE_SETUP_SYNC is designed to publish setup data pertaining to School Types. Its Full Sync equivalent is SCC_SCHL_TYPE_SETUP_FULLSYNC.

Published from:

Set Up SACR, Common Definitions, External Education, School Type Table


Component: Academics (Last School tab). Path: Customers CRM, Academics Information, Academics

SAD_TEST_SETUP_SYNC

SAD_TEST_SETUP_SYNC is designed to publish any transactional changes that are made to the Test ID Setup Data (create, update, and delete transactions from batch or online, self-service or administrative). Its Full Sync equivalent is SAD_TEST_SETUP_FULLSYNC.

Published from:

Set Up SACR, Product Related, Recruiting and Admissions, External Test Scores, Test Tables


Component: Test Scores Path: Customers CRM, Academics Information, Test Scores

SAD_TEST_COMP_SYNC

SAD_TEST_COMP_SYNC is designed to publish any transactional changes that are made to the Test Component Setup Data (create, update, and delete transactions from batch or online, self-service or administrative). Its Full Sync equivalent is SAD_TEST_COMP_FULLSYNC.

14


Published from:

Set Up SACR, Product Related, Recruiting and Admissions, External Test Scores, Test Component Table



SAD_TEST_SCRTY_SYNC

SAD_TEST_SCRTY_SYNC is designed to publish any transactional changes that are made to the User ID Security for Test ID (create, update, and delete transactions from batch or online, self-service or administrative). Its Full Sync equivalent is SAD_TEST_SCRTY_FULLSYNC.

Published from:

Set Up SACR, Security, Secure Student Administration, User ID, Test ID Security



SAD_ADMITTYPE_SETUP_SYNC

SAD_ADMITTYPE_SETUP_SYNC is designed to publish setup data related to Admit Types. Its Full Sync equivalent is SAD_ADMITTYPE_SETUP_FULLSYNC.

Published from:

Set Up SACR, Product Related, Recruiting and Admissions, Prospect/Applicant Recruiting, Admit Type Table



SSR_SCRTY_INST_UID_SYNC

SSR_SCRTY_INST_UID_SYNC is designed to publish any transactional changes that are made to the Academic Institution User Security (create, update, and delete transactions from batch or online, self-service or administrative). Its Full Sync equivalent is SSR_SCRTY_INST_UID_FULLSYNC.

Published from:

1. Academic Institution Security Component Set Up SACR, Security, Secure Student Administration, User ID, Academic Institution Security

15


2. User Security Replacement Component Set Up SACR, Security, Secure Student Administration, Setup, User Security Replacement

3. Mass Replace Security: Pop Sel Process Set Up SACR, Security, Secure Student Administration, Process, Mass User Security Replacement

Note: The setups for Institution User Security, Academic Career User Security, Academic Program User Security, and so on are performed in Campus Solutions and are brought over to CRM through their respective EIPs. SSR_SCRTY_INST_UID_SYNC and other such security related EIPs discussed below are designed to set the respective security settings in CRM to match the security setup done in Campus Solutions.

SSR_SCRTY_CAR_UID_SYNC

SSR_SCRTY_CAR_UID_SYNC is designed to publish any transactional changes that are made to the Academic Career User Security (create, update, and delete transactions from batch or online, self-service or administrative). Its Full Sync equivalent is SSR_SCRTY_CAR_UID_FULLSYNC.

Published from:

1. Institution/Career Security Component Set Up SACR, Security, Secure Student Administration, User ID, Institution/Career Security



SSR_SCRTY_PROG_UID_SYNC

SSR_SCRTY_PROG_UID_SYNC is designed to publish any transactional changes that are made to the Academic Program User Security (create, update, and delete transactions from batch or online, self-service or administrative). Its Full Sync equivalent is SSR_SCRTY_PROG_UID_FULLSYNC.

Published from: 1. Academic Program Security Component

Set Up SACR, Security, Secure Student Administration, User ID, Academic Program Security



16


SSR_SCRTY_PLAN_UID_SYNC

SSR_SCRTY_PLAN_UID_SYNC is designed to publish any transactional changes that are made to the Academic Plan User Security (create, update, and delete transactions from batch or online, self-service or administrative). Its Full Sync equivalent is SSR_SCRTY_PLAN_UID_FULLSYNC.

Published from:

1. Academic Plan Security Component Set Up SACR, Security, Secure Student Administration, User ID, Academic Plan Security



SAD_SCRTY_APPL_CTR_SYNC

SAD_SCRTY_APPL_CTR_SYNC is designed to publish security details pertaining to Application Center. Its Full Sync equivalent is CS_SCRTY_APPL_CTR_FULLSYNC.

Published from:

1. Application Center Security Component Set Up SACR, Security, Secure Student Administration, User ID, Application Center Security



SAD_SCRTY_RECR_CTR_SYNC

SAD_SCRTY_RECR_CTR_SYNC is designed to publish security details pertaining to Recruitment Center. Its Full Sync equivalent is CS_SCRTY_RECR_CTR_FULLSYNC.

Published from:

1. Recruiting Center Security Component Set Up SACR, Security, Secure Student Administration, User ID, Recruiting Center Security



17


SAD_TEST_SCORES_SYNC

SAD_TEST_SCORES_SYNC is a bi-directional EIP that is designed to publish and subscribe Student Test Scores details. It synchronizes data from CS to CRM and from CRM to CS.

It has a Full Sync equivalent, CS_TEST_SCORES_FULLSYNC, that is used to publish data from CS to CRM only.

Published from:

1. Test Results Component Student Admissions, External Test Score Processing, Test Results Student Recruiting, External Test Score Processing, Test Results Records and Enrollment, Transfer Credit Evaluation, Test Results

2. Search/Match/Post Test Score Process Student Admissions, External Test Score Processing, Search/Match/Post Test Scores Student Recruiting, External Test Score Processing, Search/Match/Post Test Scores

3. Web Prospect Create Process Self-Service, Student Admission, Request Information



SAD_ADM_PRSPCT_DATA_SYNC

SAD_ADM_PRSPCT_DATA_SYNC is designed to publish any transactional changes that are made to the Admissions Prospect Data entity (create, update, and delete transactions from batch or online, self-service or administrative). Its Full Sync equivalent is CS_ADM_PRSPCT_DATA_FULLSYNC.

Published from:

1. Create/Update Prospects Component Student Recruiting, Maintain Prospects, Create/Update Prospects

2. Prospect Delete Component Student Recruiting, Delete Prospects, Prospect Delete Process


1. Search/Match/Post Test Score Process: Search/Match/Post process loads the Test Scores and Prospect data into CS Core records. Student Admissions, External Test Score Processing, Search/Match/Post Test Scores Student Recruiting, External Test Score Processing, Search/Match/Post Test Scores

2. Create Prospects from Tests Process Student Recruiting, External Test Score Processing, Create Prospects from Tests Student Admission, External Test Score Processing, Create Prospects from Tests

18


3. Create Prospects from Query Process Student Recruiting, Maintain Prospects, Create Prospects from Query

4. Web Prospect Create Process Self-Service, Student Admission, Request Information




SAD_ADM_APPL_DATA_SYNC

SAD_ADM_APPL_DATA_SYNC is designed to publish any transactional changes that are made to the Admissions Application Data entity (create, update, and delete transactions from batch or online, self-service or administrative). Its Full Sync equivalent is CS_ ADM_APPL_DATA_FULLSYNC.

1. Published from:

2. Add Application component: This is the main Admission online component in which the applicant’s biographic, program, plan, and subplan information are added. Student Admissions, Application Entry, Add Application

3. Program Addition component: This is the Admission online component in which the applicant’s program, plan, and subplan information can be added, modified, and deleted. Student Admissions, Application Maintenance, Program Addition

4. Maintain Applications component: This is the Admission online component in which applications are maintained. Student Admissions, Application Maintenance, Maintain Applications

5. Action/Reason Entry component Student Admissions, Application Maintenance, Action Reason Entry

6. Student Academic Program/Plan component: This is the main SR online component in which a student's academic program, plan, and subplan information can be maintained. Records and Enrollment, Career and Program Information, Student program plan

7. Student Financials components GRP_QUICK_POST Student Financials, Charges and Payments, Post Student Transaction STUDENT_PAYMENTS Student Financials, Cashiering, Post Student Payments CSH_POST_RCPT Student Financials, Cashiering , Post Receipts

19


SSF_SS_PAYMENT Self Service, Campus Finances, Make a Payment


1. Activate Applicant Process: This is a batch driver for the matriculation process and activates applicants as students. Student Admissions, Processing Applications, Activate Applicants

2. Application Delete Process: Process applications selected for deletion. Student Admissions, Application Delete, Application Delete Process

3. Application Status Update process: This process performs a background process to update the program evaluation status and program actions of applications that have been evaluated. Student Admissions, Processing Applications, Update Applications, Application Status Update

4. Application Program Update process: This process updates the program action for applications selected through mass change. Student Admissions, Processing Applications, Update Applications, Application Program Update

5. TS 189 Search/Match/Post Process: This process searches for an existing person and posts TS189 application data. Student Admissions, Application/Transcript Loads, TS 189, Search/Match/Post Process

6. Alternate Program Addition Process: This process updates application data for alternate programs. Student Admissions, Processing Applications, Alternate Program Addition

7. Studielink Inbound Process: Studielink - Netherlands centralized admissions and enrollment system localized load process. Student Admissions, Processing Studielink NLD, Process Studielink, Post Studielink Messages

8. Quick Admit Batch Apps Process: This process creates prospect records and/or applications for those entered through quick admit. Records and Enrollment, Enroll Students, Quick Admit Batch Apps

9. Create Applicants From Tests Process: This process creates applications from ADA, AMCAS, or LSDAS/LSAT tests. Student Admissions, External Test Score Processing, Create Applicants From Tests

10. Population Update Process Set Up SACR>System Administration>Utilities, Population Update

11. CBAP Post Process: This process updates the data from the CBAP suspense table into PeopleSoft tables Student Admissions, Processing Admissions NLD, CBAP Post

12. SFPQDPST.cbl: Student Financials Subsystem - Group Posting Program Student Financials, Charges and Payments, Group Processing, Post Transactions

20


13. SF-Credit Card Payments: Student Financials – Credit Card Payments Student Financials, Charges and Payments, Electronic Transactions, Electronic Payments>Process Credit Cards Student Financials, Charges and Payments, Electronic Transactions, Electronic Payments>Process Electronic Check

14. UCAS Post Process Student Admissions, UCAS Processing, Import Applicant Data




The full sync EIP CS_PERS_DATA_EXTEND_FULLSYNC synchronizes data for a number of different attributes. To manage the respective incremental sync, it is broken down into a number of real time EIPs as listed below:

• SCC_SRVC_IND_SYNC

• SAD_ADM_INTEREST_SYNC

• SSR_EXTRACUR_ACTVTY_SYNCS

• SAD_EXT_ACAD_DATA_SYNC

• SCC_PERSON_SYNC

CS_PERS_DATA_EXTEND_FULLSYNC should be used to seed the data initially, but thereafter you can use the real time EIPs to keep it synchronized. Details for each of these incremental sync EIPs are as follows:

SCC_SRVC_IND_SYNC

SCC_SRVC_IND_SYNC is designed to publish any transactional changes that are made to the Person Service Indicator entity (create, update, and delete transactions from batch or online, self-service or administrative).

Published from:

1. Service Indicator Data Component Campus Community, Service Indicators (Student), Manage Service Indicators

2. Service Indicator Data Component Campus Community, Student Services Ctr (Student)


21


1. Create Service Indicators Process Contributor Relations, Constituent Information, People, Service Indicators, Mass Assign Campus Community, Service Indicators (Student), Mass Assign Campus Community, Service Indicators, Person, Mass Assign

2. Release Service Indicators Process Contributor Relations, Constituent Information, People, Service Indicators, Mass Release Campus Community, Service Indicators (Student), Mass Release Campus Community, Service Indicators --> Person, Mass Release

In CRM, this EIP updates the profile “CS-ADM Service Indicators”. It can be used in the Manage Audiences component.

Path: Marketing, Manage Audiences

SAD_ADM_INTEREST_SYNC

SAD_ADM_INTEREST_SYNC is designed to publish any transactional changes that are made to the Person Admissions Interest entity (create, update, delete transactions from batch or online, self-service or administrative).

Published from:

1. Academic Interests Component Student Admissions, Application Entry, Academic Information, Academic Interests Student Recruiting, Maintain Prospects, Academic Information, Academic Interests



2. Create Prospects from Tests Process. Student Recruiting, External Test Score Processing, Create Prospects from Tests Student Admission, External Test Score Processing, Create Prospects from Tests

3. Create Prospects from Query Process Student Recruiting, Maintain Prospects, Create Prospects from Query

In CRM, this EIP updates the profile “CS-ADM Academic Interests”. It can be used in the Manage Audiences component.


22


SSR_EXTRACUR_ACTVTY_SYNC

SSR_EXTRACUR_ACTVTY_SYNC is designed to publish any transactional changes that are done to the Person Extracurricular Activities entity (create, update, and delete transactions from batch or online, self-service or administrative).

Published from:

1. Extracurricular Activities Component Student Recruiting, Student Recruiters, Participation and Achievements, Extracurricular Activities Self-service, Campus Personal Information, Extracurricular Activities Campus Community, Personal Information, Participation Data, Extracurricular Activities Campus Community, Personal Information (Student), Participation Data (Student), Extracurricular Activities Student Recruiting, Maintain Prospects, Participation, Extracurricular Activities Student Admissions, Application Entry, Participation, Extracurricular Activities Records and Enrollment, Student Background Information, Extracurricular Activities



2. Create Prospects from Tests Process Student Recruiting, External Test Score Processing, Create Prospects from Tests Student Admission, External Test Score Processing, Create Prospects from Tests

3. Create Prospects from Query Process Path: Student Recruiting, Maintain Prospects, Create Prospects from Query

In CRM, this EIP updates the profile “CS-ADM Extracur Activity”. It can be used in the Manage Audiences component.


SAD_EXT_ACAD_DATA_SYNC

SAD_EXT_ACAD_DATA_SYNC is designed to publish any transactional changes that are made to the Person External Academic Data entity (create, update, and delete transactions from batch or online, self-service or administrative).

Published from:

1. External Academic Summary Component Student Admissions, Application Entry, Academic Information, Education Student Recruiting, Maintain Prospects, Academic Information, Education Student Admissions, Application/Transcript Loads, Education

23


2. Student Admissions Info Component Campus Community, Student Services Center, Academics Campus Community, Student Services Ctr (Student), Academics

In CRM, this EIP updates the profile “CS-ADM Academic History”. It can be used in the Manage Audiences component.


SCC_PERSON_ SYNC

SCC_PERSON_SYNC is designed to publish any transactional changes that are made to the CS Person Extensions Data entity (create, update, or delete transaction from batch or online, self-service or administrative).

Published from:

1. FERPA Component Campus Community, Personal Information, Biographical, Person FERPA, FERPA

2. FERPA Quick Entry Component Campus Community, Personal Information, Biographical, Person FERPA, FERPA Quick Entry

3. Decedent Data Processing Component Contributor Relations, Constituent Information, People, Personal Attributes, Decedent Data

4. FERPA Restrictions Component Self Service, Campus Personal Information, FERPA Restrictions


1. Search/Match/Post Test Score Process: Search/Match/Post process loads the Person Data into CS Core record. Student Admissions, External Test Score Processing, Search/Match/Post Test Scores Student Recruiting, External Test Score Processing, Search/Match/Post Test Scores

2. Search/Match/Post TAC Process: Search/Match/Post TAC process loads the Person Data into CS Core record. Student Admissions, TAC Processing, Search/Match/Post TAC

In CRM, this EIP updates the profile “CS-Person”. It can be used in the Manage Audiences component.


SAD_RFRL_SRC_SETUP_SYNC

SAD_RFRL_SRC_SETUP_SYNC is designed to carry the setup details pertaining to all referral sources that may be used in admissions recruiting. Its Full Sync equivalent is SAD_RFRL_SRC_SETUP_FULLSYNC.

24


Published from: Set Up SACR, Product Related, Recruiting and Admissions, Prospects, Referral Source Table



Constituent Lifecycle Status Change The EIPs SAD_ADM_APPL_DATA_SYNC and SSR_ACAD_PROG_SYNC are used for syncing up the Constituent Lifecycle status changes from CS to CRM.

For example:

On adding an application (Student Admissions, Application Entry, Add Application), SAD_ADM_APPL_DATA_SYNC is published that changes the Lifecycle Status in CRM from Suspect/Prospect to Applicant and Application status to Application.

From Maintain Applications (Student Admissions, Application Maintenance, Maintain Applications), for Program Action MATR, on saving, SAD_ADM_APPL_DATA_SYNC is published that changes Lifecycle Status in CRM to Student and Application status to Matriculation.

From the Student Program tab (Career and Program Information, Student Program Plan), for Program Action SPND, on saving, SSR_ACAD_PROG_SYNC is published that changes the Student Status in CRM to Suspension.

From the Student Program tab (Records and Enrollment, Career and Program Information, Student Program Plan), for Program Action COMP, on saving, SSR_ACAD_PROG_SYNC is published that changes the Student Status in CRM to Completed Program.

Profile Choices Updates The EIP CS_PRFL_ATTR_CHOICES_FULLSYNC is designed to define profile field choices from CS to CRM. A number of profile field choices in profiles such as CS-ADM Applicant Recruiter, CS-ADM Applicant Program, CS-ADM Applicant Plan, CS-ADM Applicant Sub-Plan, CS-ADM Academic History, and CS-ADM Academic Interests are updated. For example, when changes for the field CS_EXTRA_ACTIVITY are included in this EIP, the profile field Extracurricular Activity in profile CS-ADM Extracur Activity will be populated with the list of valid extracurricular activities. After these profile field choices are available, the audience builder will be able to present a marketer with a valid list of extracurricular activities to choose from when defining an audience.

The section “Defining Full Data Publish Rules” and table “Full Table Publish Rules For CS_PRFL_ATTR_CHOICES_FULLSYNC” gives details of various attributes synchronized through this message.

EIP Setup

To set up EIPs for integration between PeopleSoft Campus Solutions and PeopleSoft CRM, a number of steps must be performed on the CS and CRM databases.

25


The basic information for this red paper is extracted from the PeopleSoft Enterprise Customer Relationship Management 9.1 Installation Guide, Chapter 14 (Integrating PeopleSoft Online Marketing 9.1 and PeopleSoft Student Administration 8.9 and 9.0) and the PeopleSoft Enterprise Campus Solutions CRM for Higher Education Developer’s Guide.

Several screenshots have been provided throughout this red paper as a visual aid to help clarify the various integration steps.

Prerequisites

Before you begin PeopleSoft CS and CRM integration, ensure that these requirements are met:

• Install and configure a PeopleSoft CRM 9.1 database.

• Install and configure a PeopleSoft Campus Solutions database (PeopleSoft CS 9.0 Feature Pack 2 is now part of Human Capital Management 9.0).

Setting up and Testing EIP Configuration on CS Database

Note: Complete the following steps on the PeopleSoft Campus Solutions database.

Verify Local Gateway Properties

The Local Gateway properties are set up during the PeopleSoft Campus Solutions 9 installation.

Verify this by navigating to PeopleTools, Integration Broker, Configuration, Gateways. The URL format is:

http://<CSmachine_name>/PSIGW/PeopleSoftListeningConnector

An example screenshot is provided below:

26


Figure 2. Gateway Properties

Note: If Gateways, HR Node, and CRM External node are already set, you can validate the connections by clicking the Ping Gateway and Ping Node buttons.

Verify HR Local Node and Connector

The Local Node is set up during the PeopleSoft Campus Solutions 9 installation. Verify this by navigating to People Tools, Integration Broker, Integration Setup, Nodes. Example screenshots are provided below:

Figure 3. Local Node

Navigate to Connector tab and make sure Connector ID is set to PSFTTARGET.

27


Figure 4. Local Node, Connectors

Click Gateway Setup Properties, then sign on using User ID/Password to get to the Node Configuration page and check that the PeopleSoft Nodes grid has an entry for the Local Node.

Figure 5. Local Node Configuration

Setting Up PeopleSoft CRM External Node and Connector

To set up the PeopleSoft CRM external node connector:

1. Navigate to People Tools, Integration Broker, Integration Setup, Nodes.

2. Search for the node PSFT_CR.

3. Ensure that the Active Node check box is selected. An example screenshot is provided below:

28


Figure 6. CRM External Node

4. Configure the node connection as follows:

• Select the Connectors tab, and ensure that the Connector ID is set to PSFTTARGET. The following is an example of the Connectors tab:

Figure 7. CRM External Node, Connector

• Click the Gateway Setup Properties link, enter the User ID and password, and click OK.

• Set the URL value to that of the PeopleSoft CRM local gateway for the PSFT_CR node. The URL format is http://<CRM_machinename>:<jolt port>.

29


Figure 8. CRM Node Configuration

5. Click OK.

6. Click Save.

7. Click the Routings tab to ensure that all of the following routings are defined, and set the PeopleSoft CRM node to the Active status:

• CS_ADM_APPL_DATA_FULLSYNC

• CS_ADM_PRSPCT_DATA_FULLSYNC

• CS_EMAIL_NOTICE

• CS_PERS_DATA_EXTEND_FULLSYNC

• CS_PRFL_ATTR_CHOICES_FULLSYNC

• CS_SCRTY_APPL_CTR_FULLSYNC

• CS_SCRTY_RECR_CTR_FULLSYNC

• CS_TEST_SCORES_FULLSYNC

• PERSON_BASIC_FULLSYNC

The following is an example of the Routings page for this PSFT_CR node:

30


Figure 9. CRM Node Routings

Activating the Service Operations

The Service Operations listed previously must be in Active state. To set this, do the following:

1. Navigate to PeopleTools, Integration Broker, Integration Setup, Service Operation. Search and open each Service Operation.

2. Select the Active check box.

The following is an example of the Service Operation page:

31


Figure 10. Service Operations

Setting Queues to Run state

For each of the Queue definitions listed below, navigate to PeopleTools, Integration Broker, Integration Setup, Queue, and set the Queue Status to Run:

• SAD_CRM_SETUP

• SAD_CRM_DATA

• PERSON_DATA

32


Figure 11. Queue

Activating the Domain

To activate the domain:

1. Navigate to PeopleTools, Integration Broker, Service Operations Monitor, Administration, Domain Status.

2. In the Domains grid, ensure that the Domain Status of the gateway machine is set to Active.

If it is not, select Active, click the Update button, and then click Refresh.

The following is an example of the Domain Status page:

33


Figure 12. Domain Status

Setting Up Single Signon

To set up single signon:

1. Navigate to PeopleTools, Security, Security Objects, Single Signon.

2. Add both the nodes for Single Signon.

The following is an example of the Single Signon page:

Figure 13. Single Signon

Testing the PeopleSoft CRM Node

To test (ping) the PeopleSoft CRM node:

1. Navigate to PeopleTools, Integration Broker, Service Operations Monitor, Administration, Node Status.

2. In the Message Node Name field, enter the PeopleSoft CRM default local node (for example, PSFT_CR).

3. Click the Ping Node button and verify that Success appears in the Message Text column.

34


Figure 14. Ping Node

Setting up and Testing EIP Configuration on CRM Database

Note: Complete the following steps on the PeopleSoft CRM database.

Verify Local Gateway Properties

The Local Gateway properties are set up during the PeopleSoft CRM 9.1 installation.

Verify this by navigating to PeopleTools, Integration Broker, Configuration, Gateways. An example screenshot is provided below:

35


Figure 15. CRM Local Gateway

Verify CRM Local Node and Connector

The Local Node is set up during the PeopleSoft CRM 9.1 installation. Verify this by navigating to People Tools, Integration Broker, Integration Setup, Nodes. Example screenshots are provided below:

Figure 16. CRM Local Node

36


Navigate to Connector tab and verify that Connector ID is set to PSFTTARGET.

Figure 17. CRM Local Node, Connector

Click Gateway Setup Properties, sign on using User ID/Password to get to the Node Configuration page and check that the PeopleSoft Nodes grid has an entry for the Local Node.

Figure 18. CRM Local Node Configuration

Navigate back to the Nodes component, click the Routings tab, and ensure that the routings shown in the following Default Local Node page are defined and active:

Figure 19. CRM Local Node , Routings

37


Setting Up Campus Solutions External Node and Connector

To set up the PeopleSoft CS external node and connector:

1. Navigate to PeopleTools, Integration Broker, Integration Setup, Nodes.

2. Search for the node PSFT_HR.

3. Ensure that the Active Node check box is selected.

Figure 20. CS External Node

4. Configure the node connection as follows:

• Select the Connectors tab, and ensure that the Connection ID is set to PSFTTARGET for PeopleSoft CS 8.9/9.0.

38


Figure 21. CS External Node, Connectors

• Click the Gateway Setup Properties link, enter the user ID and password, and click OK.

• Set the CS server and port for node PSFT_HR.

Figure 22. CS Node Configuration

5. Click OK.

6. Click Save.

7. Click the Routings tab to ensure that all of the routings are active and verify that the required routings are defined for this PeopleSoft CS node.

39




• CS_EMAIL_NOTICE







Figure 23. CS External Node, Routings

Activating the Service Operations and Handlers

The Service Operations listed previously must be in the Active state. To verify this, do the following:

1. Navigate to PeopleTools, Integration Broker, Integration Setup, Service Operation. Search and Open each Service Operation


The following is an example of the Service Operation page:

40



3. Click the Handlers tab and make sure that the Handler is set to Active.

The following is an example of the Handler page:

Figure 25. Handlers

41


In general, there is only one Handler defined for Service Operations. For the following three Service Operations, if you see multiple Handlers, activate only the following:

HANDLER ACTIVATION

CS_ADM_APPL_DATA_FULLSYNC ApplicantFullSync

CS_ADM_PRSPCT_DATA_FULLSYNC ProspectFullSync

CS_TEST_SCORES_FULLSYNC TEST_SCORES_FULLSYNC

Setting Queues to Run state

For each of the Queues listed below, navigate to PeopleTools, Integration Broker, Integration Setup, Queue, and set the Queue Status to Run:

• SAD_CRM_SETUP

• SAD_CRM_DATA

• PERSON_DATA

Activating the Domain

To activate the domain:

1. Navigate to PeopleTools, Integration Broker, Service Operations Monitor, Administration, Domain Status.

2. In the Domains grid, ensure that the Domain Status of the machine of gateway is set to Active. If it is not, select Active, click the Update button, and then click Refresh.

The following is an example of the Domain Status page:

42


Figure 26. Domain Status

Set up single signon

To set up single signon:

1. Navigate to PeopleTools, Security, Security Objects, Single Signon

2. Add both the nodes for Single Signon.

The following is an example of the Single Signon page:

Figure 27. Single Signon

Testing the PeopleSoft CS External Node

To test (ping) the PeopleSoft CS node:

1. Navigate to PeopleTools, Integration Broker, Service Operations Monitor, Administration, Node Status.

43


2. In the Message Node Name field, enter the PeopleSoft CS node (for example, PSFT_HR).

3. Click the Ping Node button and verify that Success appears in the Message Text column.

Figure 28. Node Status

Defining SetID for Inbound EIP Data

To define inbound data SetID:

1. Navigate to Set Up CRM, Common Definitions, Customer, Customer Installation Options.

2. Enter PSUSI in the Default SetID for Inbound EIPs field, and then click Save.

44


Figure 29, Default SetID

Publishing the Full Sync Messages


Defining Full Data Publish Rules

You must define a rule for each full sync message that is defined in your system.

In this task you configure full table publish rules for PERSON_BASIC_FULLSYNC. The first full publish sync that you perform using PERSON_BASIC_FULLSYNC will publish all EMPLIDs in your PeopleSoft HCM database to PeopleSoft CRM. This is necessary to populate the appropriate PeopleSoft CRM tables that may later be updated by subsequent incremental personal data updates using PERSON_BASIC_SYNC.

To define full data publish rules, navigate to Enterprise Components, Integration Definitions, Full Data Publish Rules. Create full data publish rules for the message PERSON_BASIC_FULLSYNC as follows:

45


1. Enter Publish Rule ID and a Description (for example, Person_Basic_FullSync).

2. Select Active from the Status drop-down list.

3. In the Message Options section, select the Create Message Header check box.

4. Click “+” to add another row to the Publish Rule Definition grid.

5. Enter a Publish Rule ID and a Description (for example, Person_Basic_Inc).

6. Select Inactive from the Status drop-down list.

7. In the Message Options section, select the Create Message Header check box.

Note: The first row is active for the first full publish sync that you perform and does not use a filtering view. All EMPLIDS in your PeopleSoft HCM database will be published by this full sync.

After the first run, you can switch the first row to inactive and then activate the second row. The second row uses a view based on PS_SAD_CRM_FLT_BAS to filter the integration, based on EMPLIDs that exist in the PS_SAD_CRM_ EMPLIDS table, and has a PERS_DATA_EFFDT that is greater than or equal to the last run date of the process.

46


Figure 30. Full Table Publish Rules

1. Select the Record Mapping tab and enter the following:

2. For Publish Rule ID Person_Basic_Inc, in the Message Record Name field, enter PERSON

3. In the Source/order by Record name field, enter SAD_CRM_FLT_BAS.

47


Figure 31. Full Table Publish Rules, Record Mapping

Note: For PERSON_BASIC_FULLSYNC, make sure that the message published from CS is transformed from version “INTERNAL” to “VERSION_3” using transformation program “HMTF_TR_OA”. This can be configured by following these steps:

Navigate to PeopleTools, Integration Broker, Integration Setup, Service Operations.

Search and open Service Operation PERSON_BASIC_FULLSYNC.

48


Figure 32. Service Operation, PERSON_BASIC_FULLSYNC

Click on the Routings tab, select or create the routing to publish from CS to CRM and select the Parameters tab to verify/add the transformation. An example screen shot is provided below:

49


Figure 33. Service Operation PERSON_BASIC_FULLSYNC, Routings, Parameters

Note: PeopleSoft might release a newer version of PERSON_BASIC_FULLSYNC; you should check the latest installation/release notes for HCM/CS to determine whether a newer version should be used.

Create full data publish rules for all the messages listed in the table below along with the Record Mapping information.

Make sure to select the Create Message Header check box for all of the following messages:

FULL DATA PUBLISH RULES

MESSAGE NAME MESSAGE RECORD NAME SOURCE/ORDER BY RECORD NAME

ADM_APPL_DATA SAD_CRM_FLT_DAT

ADM_APPL_PROG SAD_CRM_FLT_PRG

ADM_APPL_PLAN SAD_CRM_FLT_PLN

CS_ADM_APPL_DATA_FULLSYNC

ADM_APPL_SBPLAN SAD_CRM_FLT_SPL

CS_ADM_PRSPCT_DATA_FULLSYNC ADM_PRSPCT_CAR SAD_CRM_FLT_PRS

50


FULL DATA PUBLISH RULES

MESSAGE NAME MESSAGE RECORD NAME SOURCE/ORDER BY RECORD NAME

CS_PERS_DATA_EXTEND_FULLSYNC ADM_INTERESTS SAD_CRM_FLT_ADM

DISABILITY SAD_CRM_FLT_DIS

SCC_DIVERS_VW SAD_CRM_FLT_DIV

EXTRACUR_ACTVTY SAD_CRM_FLT_EXT

EXT_ACAD_DATA SAD_CRM_FLT_ACD

EXT_ACAD_SUM SAD_CRM_FLT_ACS

PERSONAL_DATA SAD_CRM_FLT_PER

SRVC_IND_DATA SAD_CRM_FLT_SRV

CS_SCRTY_APPL_CTR_FULLSYNC No mapping required (However, the Full Table Publish Rule must be marked Active)

CS_SCRTY_RECR_CTR_FULLSYNC No mapping required (However, the Full Table Publish Rule must be marked Active)

CS_TEST_SCORES_FULLSYNC STDNT_TEST SAD_CRM_FLT_TST

Create Full Data Publish Rule for message CS_PRFL_ATTR_CHOICES_FULLSYNC:

Navigate to Enterprise Components, Integration Definitions, Full Data Publish Rules. Create full data publish rules for message CS_PRFL_ATTR_CHOICES_FULLSYNC:

1. On the Full Table Publish Rules tab, create a new row for each Publish Rule Id listed in the table below.

2. Set the status to Active.

3. Clear the Create Message Header and Create Message Trailer options.

4. Select the Record Mapping tab. For the Message Record Name of SAD_CRM_ACH_WRK, configure the following:

FULL TABLE PUBLISH RULES FOR CS_PRFL_ATTR_CHOICES_FULLSYNC

PUBLISH RULE ID DESCRIPTION SOURCE/ORDER BY RECORD NAME

ACTIONS Program Actions SAD_CRM_ACTN_VW

APP_CENTERS Application Centers SAD_CRM_ACTR_VW

ACTIVITIES Extracurricular Activities SAD_CRM_ACTV_VW

ADMIT_TERMS Admit Terms SAD_CRM_ATRM_VW

51


FULL TABLE PUBLISH RULES FOR CS_PRFL_ATTR_CHOICES_FULLSYNC

PUBLISH RULE ID DESCRIPTION SOURCE/ORDER BY RECORD NAME

ADMIT_TYPES Admit Types SAD_CRM_ATYP_VW

CAMPUS Campus SAD_CRM_CAMP_VW

EXT_SUBJECTS External Subjects SAD_CRM_ESUB_VW

EXT_TERMS External Terms SAD_CRM_ETRM_VW

EXP_GRAD_TERMS Expected Graduation Terms SAD_CRM_GTRM_VW

GPA_TYPES GPA Types SAD_CRM_GTYP_VW

INSTITUTIONS Institutions SAD_CRM_INST_VW

PLANS Academic Plans SAD_CRM_PLAN_VW

PROGRAMS Academic Programs SAD_CRM_PROG_VW

RECRUIT_CAT Recruiting Categories SAD_CRM_RCAT_VW

REC_CENTERS Recruiting Centers SAD_CRM_RCTR_VW

ACTN_REASONS Academic Program Action Reasons SAD_CRM_RSN_VW

REFERRAL_SOURCE Referral Source SAD_CRM_RSRC_VW

REQ_TERMS Requirement Terms SAD_CRM_RTRM_VW

SUMM_TYPES Summary Types SAD_CRM_SMTP_VW

SUB_PLANS Academic Sub-Plans SAD_CRM_SPLN_VW

SRVC_IND Service Indicators SAD_CRM_SRVC_VW

TERMS Terms SAD_CRM_STRM_VW

TEST_COMP Test Components SAD_CRM_TCMP_VW

TEST_ID Test IDs SAD_CRM_TEST_VW

The following are the example screen shots for Full Table Publish Rules for message CS_PRFL_ATTR_CHOICES_FULLSYNC:

52


Figure 34. Full Table Publish Rules for CS_PRFL_ATTR_CHOICES_FULLSYNC

53


Figure 35. Full Table Publish Rules, Record Mappings for CS_PRFL_ATTR_CHOICES_FULLSYNC

Setting Service Operation Security

To set Service Operations Security:

1. Navigate to People Tools, Security, Permissions and Roles, Permissions Lists.

2. Select the appropriate permission list (for example, HCCPSSA1000 or HCSPSERVICE).

3. Select the Web Services tab.

4. Verify and grant FULL access for the following messages:



• CS_EMAIL_NOTICE

54








• PERSON_BASIC_SYNC

The following are the example screen shots:

Figure 36. Permission List

55


Figure 37. Permission List, Web Service Permissions

Granting Security for App Engine Processes and Pages

To grant security for Application Engine (AE) processes and new pages:

1. Navigate to People Tools, Security, Permissions and Roles, Permissions Lists.

2. Select the appropriate Permission List (for example, HCCPSSA1000 or HCSPSERVICE).

3. Select the Pages tab.

4. Add the menus SAD_CRM_INTEGRATION, EVALUATE_APPLICANTS, and LOAD_EXTERNAL_DATA.

Figure 38. Permission List, Pages

1. Click the Edit Component link for the SAD_CRM_INTEGRATION, EVALUATE_APPLICANTS, and LOAD_EXTERNAL_DATA menus that you just added.

56


2. Click the Edit Pages link

3. Click the Select All button for each menu.

4. Click OK.

5. Click OK again.

6. Click Save.

Note. You may need to sign out and sign back in to access the menu items.

Figure 39. Permission List, Pages, Component Permissions

Figure 40. Permission List, Pages, Page Permissions

SOA Based FullSync Messages

As part of PeopleSoft Enterprise Campus Solutions 9.0 feature pack 2, a number of new Full Sync EIPs were released along with their Event Registry configuration. Following is a list of the new Full Sync EIPs delivered to use the SOA Full Sync publishing pattern.

57


SOA FULL SYNC EIPS

FUNCTIONALITY EIP

External Org SCC_EXT_ORG_FULLSYNC

Academic Institution Setup SSR_ACADINST_SETUP_FULLSYNC

Academic Campus Setup SSR_ACADCAMP_SETUP_FULLSYNC

Academic Career Setup SSR_ACADCAR_SETUP_FULLSYNC

Academic Program Setup SSR_ACADPROG_SETUP_FULLSYNC

Academic Plan Setup SSR_ACADPLAN_SETUP_FULLSYNC

Academic Subplan Setup SSR_ACADSUBPLAN_SETUP_FULLSYNC

Academic Term Setup SSR_ACADTRM_SETUP_FULLSYNC

Academic Institution Security SSR_SCRTY_INST_UID_FULLSYNC

Academic Career Security SSR_SCRTY_CAR_UID_FULLSYNC

Academic Program Security SSR_SCRTY_PROG_UID_FULLSYNC

Academic Plan Security SSR_SCRTY_PLAN_UID_FULLSYNC

School Type Set up Table SCC_SCHL_TYPE_SETUP_FULLSYNC

Test Setup SAD_TEST_SETUP_FULLSYNC

Test Component Setup SAD_TEST_COMP_FULLSYNC

Test Security Setup SAD_TEST_SCRTY_FULLSYNC

Admit Type Setup SAD_ADMITTYPE_SETUP_FULLSYNC

Referral Source Table SAD_RFRL_SRC_SETUP_FULLSYNC

Student Status Change SSR_ACAD_PROG_FULLSYNC

Follow these steps to publish these full sync messages:


1. Navigate to PeopleTools, Integration Broker, Integration Setup, Service Operation.

2. Search for and open each Service Operation one by one. For example, SSR_ACADINST_SETUP_FULLSYNC.


58


Figure 41. Service Operation

4. Click the Routings tab

5. Make sure that the Routing is Active for the required sender and receiver nodes.

Figure 42. Service Operation, Routings

Follow the above steps to activate Service Operations and Routings for all the FullSync messages listed in the SOA Full Sync EIPs table.

59


SOA –NOTIFICATION HANDLER (FOR CRM to CS)

Verify that the following Notification Handler is Active:

1. Navigate to Home, Set Up SACR, System Administration, Integrations, Notification Handlers

2. Verify that the Notification Handler is configured as shown below:

SOA – NOTIFICATION HANDLER

EIP SERVICE OPERATION PACKAGE NAME PATH CLASS ID

Test Score Sync SAD_TEST_SCORES_SYNC CS_TEST_SCORE_SYNC : CSTestScoreSync

Note: The EIP SAD_TEST_SCORE_SYNC is a bi-directional EIP that is designed to sync data from CS to CRM and from CRM to CS. All the other EIPs detailed throughout this document are used only to sync data from CS to CRM.

Note: Complete the following steps on the PeopleSoft CRM database. 1. Navigate to PeopleTools, Integration Broker, Integration Setup, Service Operations.

2. Search for and open each Service Operation one by one. For example, SSR_ACADINST_SETUP_FULLSYNC.


60



4. Click the Handlers tab.

5. Make sure that the handler is Active.

61


Figure 44. Service Operations, Handlers

6. Click the Routings tab

7. Make sure that the routing is Active for the required sender and receiver nodes.

Figure 45. Service Operations, Routings

Follow the previous steps to activate Service Operations, Handlers, and Routings for all the FullSync messages listed in the SOA Full Sync EIPs table.


Running PERSON_BASIC_FULLSYNC from CS to CRM

PERSON_BASIC_FULLSYNC should be published before any other message that is publishing the student data from Campus Solutions. To publish the message PERSON_BASIC_FULLSYNC, follow these steps:

1. Navigate to Enterprise Components, Integration Definitions, Initiate Process, Full Data Publish.

2. Enter a run control ID (for example, Person_Basic_Full).

3. Enter a Request ID, Description, and Process Frequency as Once.

4. Select message name PERSON_BASIC_FULLSYNC

5. Save and click Run.

62


Figure 46. Full Data Publish

6. Check Full Table Data Publish and click OK.

Figure 47. Process Scheduler Request

7. Check that the process has run to Success. This should publish the PERSON_BASIC_FULLSYNC. You can monitor the service operation details from the Service Operations Monitor by navigating to People Tools, Integration Broker, Service Operations Monitor, Monitoring, Asynchronous Services.

Populating Profile Attribute Choices from CS to CRM

1. Navigate to Enterprise Components, Integration Definitions, Initiate Processes, Full Data Publish.

2. Enter a run control ID.

3. Enter a request ID.

4. (Optional) Enter a Description.

5. Select Once for Process Frequency.

63


6. Select CS_PRFL_ATTR_CHOICES_FULLSYNC as the Message Name.


7. Click Save and then click Run.

8. Check Full Table Data Publish and click OK

9. Check that the process has run to Success. This should publish CS_PRFL_ATTR_CHOICES_FULLSYNC. You can monitor these service operation details from the Service Operations Monitor.

Cleaning Up Profile-Related Data Integrity in the CRM Database

After populating the profile attribute choices from PeopleSoft CS to PeopleSoft CRM, you must confirm data integrity. Run the PeopleSoft Data Mover scripts to clean up the attribute choice IDs.

To run the PeopleSoft Data Mover scripts to clean up the attribute choice IDs:

1. Open the PeopleSoft Configuration Manager.

2. Select the Profile tab and click the Edit button for the Default profile.

3. Select the Common tab.

4. Set the Input Directory in PeopleSoft Data Mover Directories to <PS_HOME>\data (for example: c:\Tools\data, or \\networkmachine\Tools\data, or //unixMountDir/Tools/data).

5. Click OK.

6. Click OK again.

7. Save the configuration setting.

8. Open the script file olmsaresetids.dms from <PS_HOME>\scripts in PeopleSoft Data Mover.

64


9. Select File, Run Script.

10. Recycle the application server and clear the application server cache.

11. Recycle the Dialog Execution Server (DES).

Populating Student Data from CS to CRM

1. Navigate to Enterprise Components, Integration Definitions, Initiate Processes, Full Data Publish.

2. Enter a run control ID (for example, SAD_CRM_INTEGRATION).

3. For each row of the table below, add a row in the Process Request Scroll.

FULL DATA PUBLISH - SAD_CRM_INTEGRATION

REQUEST ID DESCRIPTION PROCESS FREQUENCY MESSAGE NAME

002 Extend Pers Data Once CS_PERS_DATA_EXTEND_FULLSYNC

003 Applicant Data Once CS_ADM_APPL_DATA_FULLSYNC

004 Prospect Data Once CS_ADM_PRSPCT_DATA_FULLSYNC

005 Test Score Data Once CS_TEST_SCORES_FULLSYNC

006 Application Center Security Once CS_SCRTY_APPL_CTR_FULLSYNC

007 Recruiting Center Security Once CS_SCRTY_RECR_CTR_FULLSYNC

4. Click Save.

Following is an example screen shot:

65



5. Click Save again.

6. Navigate to Set Up SACR, Product Related, Recruiting and Admissions, Manage CRM Integration, Populate ID Control Table.

7. Enter run control ID SAD_CRM_INTEGRATION.

8. Enter the lower limit date for applicant data.

9. Enter the lower limit date for prospect data.

10. Enter the lower limit date for test scores.

The dates that you enter on this page are used to create a control list of EMPL IDs that are integrated with PeopleSoft CRM. Only applicants and prospects that you create on or after the dates specified are considered for integration with PeopleSoft CRM. In addition, only test scores loaded on or after the test score as-of date are loaded into PeopleSoft CRM.

Following is an example screen shot:

66


Figure 50. Populate ID Control Tables

11. Click Run

12. Check SAD_CRM_SYNC and click OK

13. Check that the process has run to Success. This will publish the messages listed in the Full Data Publish - SAD_CRM_INTEGRATION table. You can monitor these service operation details from the Service Operations Monitor.

Publishing SOA based FullSync Messages

Note: Complete the following steps on the PeopleSoft Campus Solutions database. The SOA based FullSync messages are listed in table “SOA Full sync EIPs” in the “SOA based FullSync Messages” section. Follow these steps for each message to publish them from CS to CRM:

1. Navigate to Set Up SACR, System Administration, Integrations, Event Register

2. Search for and open each Service Operation listed in the SOA Full Sync Publishing table one by one. For example, SSR_ACADINST_SETUP_FULLSYNC.

3. Click the Run Now button on the row with the Integration Mode set to Full Refresh. This will publish all the data from the underlying message records of the Service Operation in context

67


Figure 51. Event Registry

4. You can check the publish status for the message by navigating to PeopleTools, Integration Broker, Service Operations Monitor, Asynchronous Services.

Figure 52. Asynchronous Services

5. In the CRM database, you can check whether the message was successfully subscribed by navigating to PeopleTools, Integration Broker, Service Operations Monitor, Asynchronous Services.

68


Incremental Sync EIPs

As part of PeopleSoft Enterprise Campus Solutions 9.0 feature pack 2, a number of new Incremental Sync EIPs were also released along with their Event Registry configuration. Following is a list of these Incremental Sync EIPs:

SOA INCREMENTAL SYNC EIPS

FUNCTIONALITY EIP

Academic Institution SSR_ACADINST_SETUP_SYNC

Academic Campus SSR_ACADCAMP_SETUP_SYNC

Academic Career SSR_ACADCAR_SETUP_SYNC

Academic Program SSR_ACADPROG_SETUP_SYNC

Academic Plan SSR_ACADPLAN_SETUP_SYNC

Academic Subplan SSR_ACADSUBPLAN_SETUP_SYNC

Academic Term SSR_ACADTRM_SETUP_SYNC

External Org SCC_EXT_ORG_SYNC

School Type Setup SCC_SCHL_TYPE_SETUP_SYNC

Test ID Setup SAD_TEST_SETUP_SYNC

Test Component Setup SAD_TEST_COMP_SYNC

Test Security Setup SAD_TEST_SCRTY_SYNC

Admit Type Setup SAD_ADMITTYPE_SETUP_SYNC

Academic Institution Security SSR_SCRTY_INST_UID_SYNC

Academic Career Security SSR_SCRTY_CAR_UID_SYNC

Academic Program Security SSR_SCRTY_PROG_UID_SYNC

Academic Plan Security SSR_SCRTY_PLAN_UID_SYNC

Student Status Change SSR_ACAD_PROG_SYNC

Application Center Security SAD_SCRTY_APPL_CTR_SYNC

Recruitment Center Security SAD_SCRTY_RECR_CTR_SYNC

Test Score Sync SAD_TEST_SCORES_SYNC (CS <-> CRM)

69


SOA INCREMENTAL SYNC EIPS

FUNCTIONALITY EIP

Prospect SAD_ADM_PRSPCT_DATA_SYNC

Applicant SAD_ADM_APPL_DATA_SYNC

Service Indicator Sync SCC_SRVC_IND_SYNC

Admission Interest Sync SAD_ADM_INTEREST_SYNC

Extra Curricular Activity SSR_EXTRACUR_ACTVTY_SYNC

External Academic Data SAD_EXT_ACAD_DATA_SYNC

Person Sync SCC_PERSON_SYNC

Referral Source Table SAD_RFRL_SRC_SETUP_SYNC

For all of the Incremental Sync EIPs listed in the SOA Incremental Sync EIPs table:

On the Campus Solutions Database:

1. Make sure that Service Operation for the EIP is Active.

2. Make sure that the respective Routings are Active with the required sender and receiver nodes

3. Make sure that the Event Registry for the Service Operation is Active.

On the CRM Database:

1. Make sure that Service Operation for the EIP is Active.

2. Make sure that the Handler is Active.

3. Make sure that the respective Routings are Active with the required sender and receiver nodes

Inactivate Full Sync Messages

The Full Sync messages are only meant to be run once. After all the FullSync messages are published successfully, you change their status to Inactive. .

70


APPENDIX I – Constituent 360-Degree View and Remote Query Setup

The 360-degree view in CRM has been expanded to provide Higher Education specific information to aid institutions in building and maintaining relationships with constituents. For example, the Recruitment section of the 360 degree view uses Last School Attended and School Type information, which is published from Campus Solutions as part of the

External Organization Data interface. This information is sought by CRM from CS via the synchronous 360 Aggregation Service.

The PeopleSoft Enterprise CRM for Higher Education Developer’s Guide provides details about each of the sections fetching data from CS over to CRM to display in the Constituent 360-Degree view.

A Solution (Document 1113823.1) posted on the support website details the Constituent 360-Degree view setup. Following is the link to that document:

Constituent 360 Degree View Integration Setup between CRM 9.1 and CS 9 FP2 (Doc ID 1113823.1):

https://support.us.oracle.com/oip/faces/secure/km/DocumentDisplay.jspx?id=1113823.1&h=Y There is also a Solution (Document 1267058.1) posted on the support website that details the audience creation through remote query. Following is the link to the document:

Set Up Required for Audience Generation Using Remote Query (QAS) (Doc ID 1267058.1):

https://support.us.oracle.com/oip/faces/secure/km/DocumentDisplay.jspx?id=1267058.1&h=Y

71






APPENDIX II – Troubleshooting

This section covers common errors, exceptions, and their resolutions.

Published Message is failing on CS Database with the following error:

Figure 53. Error Messages

This generally occurs when the Routing parameters for the Sender and Receiver nodes do not match.

To fix the problem, open the Service Operation and drill down to Routing Definition. Click the Parameter tab and make sure that the External Alias field value on the CS database matches the one defined on the CRM database.

Figure 54. Error Messages

72


It might help to delete and re-create the routings in CS, as well as CRM. When you are finished, resubmit the failed message in CS.

73


APPENDIX III – FullSync Publish Sequence

The FullSync messages should be published in the sequence shown in the following table:

FULLSYNC PUBLISH SEQUENCE

FUNCTIONALITY EIP

Person Basic FullSync PERSON_BASIC_FULLSYNC

Profile Attribute Choices CS_PRFL_ATTR_CHOICES_FULLSYNC

Applicant Data CS_ADM_APPL_DATA_FULLSYNC

Prospect Data CS_ADM_PRSPCT_DATA_FULLSYNC

Extend Pers Data CS_PERS_DATA_EXTEND_FULLSYNC

Application Center Security CS_SCRTY_APPL_CTR_FULLSYNC

Recruiting Center Security CS_SCRTY_RECR_CTR_FULLSYNC

Test Score Data CS_TEST_SCORES_FULLSYNC

External Org SCC_EXT_ORG_FULLSYNC

Academic Institution Setup SSR_ACADINST_SETUP_FULLSYNC

Academic Campus Setup SSR_ACADCAMP_SETUP_FULLSYNC

Academic Career Setup SSR_ACADCAR_SETUP_FULLSYNC

Academic Program Setup SSR_ACADPROG_SETUP_FULLSYNC

Academic Plan Setup SSR_ACADPLAN_SETUP_FULLSYNC

Academic Subplan Setup SSR_ACADSUBPLAN_SETUP_FULLSYNC

Academic Term Setup SSR_ACADTRM_SETUP_FULLSYNC

Academic Institution Security SSR_SCRTY_INST_UID_FULLSYNC

Academic Career Security SSR_SCRTY_CAR_UID_FULLSYNC

Academic Program Security SSR_SCRTY_PROG_UID_FULLSYNC

Academic Plan Security SSR_SCRTY_PLAN_UID_FULLSYNC

School Type Set up Table SCC_SCHL_TYPE_SETUP_FULLSYNC

74


FULLSYNC PUBLISH SEQUENCE

FUNCTIONALITY EIP

Test Setup SAD_TEST_SETUP_FULLSYNC

Test Component Setup SAD_TEST_COMP_FULLSYNC

Test Security Setup SAD_TEST_SCRTY_FULLSYNC

Admit Type Setup SAD_ADMITTYPE_SETUP_FULLSYNC

Referral Source Table SAD_RFRL_SRC_SETUP_FULLSYNC

Student Status Change SSR_ACAD_PROG_FULLSYNC

75


APPENDIX IV – Tables Impacted by EIPs

Following is a list of tables affected by the EIPs documented in this red paper. After you run the EIPs, check these tables to validate the data transfer.

TABLES IMPACTED BY EIPS

FUNCTIONALITY EIP IMPACTED TABLES

Person Basic FullSync PERSON_BASIC_FULLSYNC Customer Data Model Tables Updated

Profile Attribute Choices CS_PRFL_ATTR_CHOICES_FULLSYNC RA_ATTR_CHOICES

Applicant Data CS_ADM_APPL_DATA_FULLSYNC RD_CONSTITUENT RD_CAREER RD_PROGRAM RD_PLAN RD_SUBPLAN Marketing Profile Tables CS_ADM_APP_DATA CS_APPL_RECRUIT CS_ADM_APP_PROG CS_ADM_APP_PLAN CS_ADM_APP_SBPL

Prospect Data CS_ADM_PRSPCT_DATA_FULLSYNC RD_CONSTITUENT

RD_CAREER

RD_PROGRAM

RD_PLAN

RD_SUBPLAN

Extend Pers Data CS_PERS_DATA_EXTEND_FULLSYNC CS_SRVC_IND_DAT

CS_INTERESTS

CS_EXCR_ACTVTY

CS_ACAD_HISTORY

CS_PERS_DATA_SA

Application Center Security CS_SCRTY_APPL_CTR_FULLSYNC SCRTY_APPL_CTR

Recruiting Center Security CS_SCRTY_RECR_CTR_FULLSYNC SCRTY_RECR_CTR

76




Test Score Data CS_TEST_SCORES_FULLSYNC RD_TEST RD_TEST_SCORE

External Org SCC_EXT_ORG_FULLSYNC EXT_ORG_TBL ORG_LOCATION EXT_ORG_TBL_ADM

Academic Institution Setup SSR_ACADINST_SETUP_FULLSYNC INSTITUTION_TBL

Academic Campus Setup SSR_ACADCAMP_SETUP_FULLSYNC CAMPUS_TBL

Academic Career Setup SSR_ACADCAR_SETUP_FULLSYNC ACAD_CAR_TBL

Academic Program Setup SSR_ACADPROG_SETUP_FULLSYNC ACAD_PROG_TBL

Academic Plan Setup SSR_ACADPLAN_SETUP_FULLSYNC ACAD_PLAN_TBL

Academic Subplan Setup SSR_ACADSUBPLAN_SETUP_FULLSYNC ACAD_SUBPLN_TBL

Academic Term Setup SSR_ACADTRM_SETUP_FULLSYNC TERM_TBL

Academic Institution Security SSR_SCRTY_INST_UID_FULLSYNC SCRTY_TBL_INST

Academic Career Security SSR_SCRTY_CAR_UID_FULLSYNC SCRTY_TBL_CAR

Academic Program Security SSR_SCRTY_PROG_UID_FULLSYNC SCRTY_TBL_PROG

Academic Plan Security SSR_SCRTY_PLAN_UID_FULLSYNC SCRTY_TBL_PLAN

School Type Set up Table SCC_SCHL_TYPE_SETUP_FULLSYNC LS_SCHL_TYP_TBL

Test Setup SAD_TEST_SETUP_FULLSYNC SA_TEST_TBL SA_TCMP_REL_TBL

Test Component Setup SAD_TEST_COMP_FULLSYNC SA_TEST_CMP_TBL

Test Security Setup SAD_TEST_SCRTY_FULLSYNC SAD_TEST_SCTY

Admit Type Setup SAD_ADMITTYPE_SETUP_FULLSYNC ADMIT_TYPE_TBL

Referral Source Table SAD_RFRL_SRC_SETUP_FULLSYNC REFERL_SRCE_TBL

Student Status Change SSR_ACAD_PROG_FULLSYNC RD_CONSTITUENT RD_CAREER RD_PROGRAM RD_PLAN RD_SUBPLAN

77




Academic Institution SSR_ACADINST_SETUP_SYNC INSTITUTION_TBL

Academic Campus SSR_ACADCAMP_SETUP_SYNC CAMPUS_TBL

Academic Career SSR_ACADCAR_SETUP_SYNC ACAD_CAR_TBL

Academic Program SSR_ACADPROG_SETUP_SYNC ACAD_PROG_TBL

Academic Plan SSR_ACADPLAN_SETUP_SYNC ACAD_PLAN_TBL

Academic Subplan SSR_ACADSUBPLAN_SETUP_SYNC ACAD_SUBPLN_TBL

Academic Term SSR_ACADTRM_SETUP_SYNC TERM_TBL

External Org SCC_EXT_ORG_SYNC EXT_ORG_TBL ORG_LOCATION EXT_ORG_TBL_ADM

School Type Setup SCC_SCHL_TYPE_SETUP_SYNC LS_SCHL_TYP_TBL

Test ID Setup SAD_TEST_SETUP_SYNC SA_TEST_TBL SA_TCMP_REL_TBL

Test Component Setup SAD_TEST_COMP_SYNC SA_TEST_CMP_TBL

Test Security Setup SAD_TEST_SCRTY_SYNC SAD_TEST_SCTY

Admit Type Setup SAD_ADMITTYPE_SETUP_SYNC ADMIT_TYPE_TBL

Academic Institution Security SSR_SCRTY_INST_UID_SYNC SCRTY_TBL_INST

Academic Career Security SSR_SCRTY_CAR_UID_SYNC SCRTY_TBL_CAR

Academic Program Security SSR_SCRTY_PROG_UID_SYNC SCRTY_TBL_PROG

Academic Plan Security SSR_SCRTY_PLAN_UID_SYNC SCRTY_TBL_PLAN

Student Status Change SSR_ACAD_PROG_SYNC RD_CONSTITUENT RD_CAREER RD_PROGRAM RD_PLAN RD_SUBPLAN

Application Center Security SAD_SCRTY_APPL_CTR_SYNC SCRTY_APPL_CTR

Recruitment Center Security SAD_SCRTY_RECR_CTR_SYNC SCRTY_RECR_CTR

78




Test Score Sync SAD_TEST_SCORES_SYNC RD_TEST RD_TEST_SCORE

Prospect SAD_ADM_PRSPCT_DATA_SYNC RD_CONSTITUENT RD_CAREER RD_PROGRAM RD_PLAN RD_SUBPLAN

Applicant SAD_ADM_APPL_DATA_SYNC RD_CONSTITUENT RD_CAREER RD_PROGRAM RD_PLAN RD_SUBPLAN Marketing Profile Tables CS_ADM_APP_DATA CS_APPL_RECRUIT CS_ADM_APP_PROG CS_ADM_APP_PLAN CS_ADM_APP_SBPL

Service Indicator Sync SCC_SRVC_IND_SYNC CS_SRVC_IND_DAT

Admission Interest Sync SAD_ADM_INTEREST_SYNC CS_INTERESTS

Extra Curricular Activity SSR_EXTRACUR_ACTVTY_SYNC CS_EXCR_ACTVTY

External Academic Data SAD_EXT_ACAD_DATA_SYNC CS_ACAD_HISTORY

Person Sync SCC_PERSON_SYNC CS_PERS_DATA_SA

Referral Source Table SAD_RFRL_SRC_SETUP_SYNC REFERL_SRCE_TBL

79


APPENDIX V – Prospective Student Import, External Sources

Refer to the “Using Prospective Student Import” section of the “Recruiting Students” chapter in the PeopleSoft Enterprise CRM for Higher Education 9.1 PeopleBook for the complete explanation on using Prospective Student Import (PSI).

The following paragraph is contained in the documentation:

Messages from External Systems

For loading prospects from sources other than Campus Solutions directly into CRM, CRM includes a standard XML message specification that it recognizes as a Higher Education prospect load message. External sources must convert their prospect data into this format before sending it to CRM. This message is parsed, placed in the Import Staging Area, and processed by the Import Process just as the Campus Solutions messages are processed. The mechanism to load prospect data from Campus Solutions and from other external sources into CRM is the same.

A Test ID named EXT is included as system data in CRM to support external prospect loads. Messages from sources other than Campus Solutions must have Test ID set to EXT in the messages that they send to CRM.

This document will explain further how to create the XML message and send it to CRM via the PeopleTools SendMaster program.

Sample XML

The following is a sample XML for PSI:

<?xml version="1.0"?> <SAD_TEST_POST_ACT_CONTAINER_DS xmlns="http://xmlns.oracle.com/Enterprise/Tools/schemas/SAD_TEST_POST_ACT_CONTAINER_DS.v1"> <SAD_TEST_POST_PART_DS> <SAD_HEADER_CRM class="R" xmlns="http://xmlns.oracle.com/Enterprise/Tools/schemas/SAD_TEST_POST_PART_DS.v1"> <TEST_ID>EXT</TEST_ID> <PROCESS_INSTANCE>1077</PROCESS_INSTANCE> <OPRID>PS</OPRID> <RUN_CNTL_ID>DLB15</RUN_CNTL_ID> <INSTITUTION>PSUNV</INSTITUTION> <ACAD_CAREER>UGRD</ACAD_CAREER> <DATE_LOADED>2009-01-27</DATE_LOADED> <ADM_RECR_CTR>UGRD</ADM_RECR_CTR> <SAD_BIO_PRS_SUS class="R"> <TEST_ID>EXT</TEST_ID>

80


<PROCESS_INSTANCE>1077</PROCESS_INSTANCE> <TEST_REC_NBR>101928</TEST_REC_NBR> <EMPLID/> <NAME_PREFIX/> <NAME_SUFFIX/> <LAST_NAME>Linden</LAST_NAME> <FIRST_NAME>Garley1</FIRST_NAME> <MIDDLE_NAME>C</MIDDLE_NAME> <BIRTHDATE>1966-01-06</BIRTHDATE> <SEX>M</SEX> <MAR_STATUS>S</MAR_STATUS> <NATIONAL_ID_TYPE>PR</NATIONAL_ID_TYPE> <NATIONAL_ID>608123456</NATIONAL_ID> <CAMPUS>MAIN</CAMPUS> <INSTITUTION>PSUNV</INSTITUTION> <ACAD_CAREER>UGRD</ACAD_CAREER> <RECRUITING_STATUS>INQR</RECRUITING_STATUS> <ADDRESS_TYPE>BILL</ADDRESS_TYPE> <ADDRESS1>16 Captain Way</ADDRESS1> <ADDRESS2/> <ADDRESS3/> <CITY>Uniondale</CITY> <STATE>NY</STATE> <COUNTRY>USA</COUNTRY> <POSTAL>73829</POSTAL> <CITIZENSHIP_STATUS>1</CITIZENSHIP_STATUS> <PHONE_TYPE>CAMP</PHONE_TYPE> <PHONE>604/222-2222</PHONE> <E_ADDR_TYPE/> <EMAIL_ADDR/> <SETID>USA</SETID> <REG_REGION>USA</REG_REGION> <ETHNIC_GRP_CD>HISPA</ETHNIC_GRP_CD> <ADMIT_TYPE>FYR</ADMIT_TYPE> <ADMIT_TERM>3000</ADMIT_TERM> <ACADEMIC_LEVEL>01</ACADEMIC_LEVEL> <ADM_REFRL_SRCE>APPL</ADM_REFRL_SRCE> <LAST_SCH_ATTEND/> <GRADUATION_DT>1998-05-15</GRADUATION_DT> <FIN_AID_INTEREST>Y</FIN_AID_INTEREST> <HOUSING_INTEREST>H</HOUSING_INTEREST> <RELIGIOUS_PREF/> <SAD_PRS_PRG_SUS class="R"> <TEST_ID>EXT</TEST_ID>

81


<PROCESS_INSTANCE>1077</PROCESS_INSTANCE> <TEST_REC_NBR>101928</TEST_REC_NBR> <SEQNUM>1</SEQNUM> <ACAD_PROG>AA</ACAD_PROG> <ACAD_PLAN>ART-MINOR</ACAD_PLAN> <ACAD_SUB_PLAN/> </SAD_PRS_PRG_SUS> <SAD_PRS_EXT_SUS class="R"> <TEST_ID>EXT</TEST_ID> <PROCESS_INSTANCE>1077</PROCESS_INSTANCE> <TEST_REC_NBR>101928</TEST_REC_NBR> <SEQNUM>1</SEQNUM> <INTERNAL_EXTERNAL>E</INTERNAL_EXTERNAL> <EXTRA_ACTIVITY>EZZ</EXTRA_ACTIVITY> <DESCR>Other Club or Organization</DESCR> <INSTITUTION>PSUNV</INSTITUTION> <ACAD_CAREER>UGRD</ACAD_CAREER> </SAD_PRS_EXT_SUS> <SAD_PRS_INT_SUS class="R"> <TEST_ID>EXT</TEST_ID> <PROCESS_INSTANCE>1077</PROCESS_INSTANCE> <TEST_REC_NBR>101928</TEST_REC_NBR> <SEQNUM>1</SEQNUM> <EXT_SUBJECT_AREA>FREN</EXT_SUBJECT_AREA> <DESCR>French</DESCR> <LS_DATA_SOURCE>SLF</LS_DATA_SOURCE> <PRIORITY>1</PRIORITY> </SAD_PRS_INT_SUS> </SAD_BIO_PRS_SUS> </SAD_HEADER_CRM> </SAD_TEST_POST_PART_DS> </SAD_TEST_POST_ACT_CONTAINER_DS>

Tables and Fields

The following tables describe the XML data structure, the expected data types, and valid values.

SAD_HEADER_CRM Table

FIELD TYPE DESCRIPTION/SOURCE OF VALID VALUES

*TEST ID Char, 11 “EXT” (SA_TEST_TBL.TEST_ID)

PROCESS_INSTANCE Nbr, 10 Process instance identifier

OPRID Char, 30 PSOPRDEFN.OPRID

82


RUN_CNTL_ID Char, 30 Run control identifier

*INSTITUTION Char, 5 INSTITUTION_TBL.INSTITUTION

*ACAD_CAREER Char, 4 ACAD_CAR_TBL.ACAD_CAREER

*DATE_LOADED Date, 10 Required to determine effective date on effective dated rows. See PeopleBooks > Enterprise PeopleTools 8.50 PeopleBook: Using PeopleSoft Applications > Working With Pages > Understanding Effective Dates

ADM_RECR_CTR Char, 4 ADM_RECRCTR_TBL.ADM_RECR_CTR

SAD_ETHNIC_PRCS_SW Char, 1 XLAT [I, U], Ethnicity Update Rules

SAD_ACT_ETH_VER Char, 1 XLAT [D, N], Update IPEDS Ethnicity

SAD_BIO_PRS_SUS Table

FIELD VALUE DESCRIPTION / SOURCE OF VALID VALUES



*TEST_REC_NBR Nbr, 9 Must uniquely identify each prospect

EMPLID Char, 11 Employee identification number

NAME_PREFIX Char, 4 Name prefix

NAME_SUFFIX Char, 15 Name suffix

LAST_NAME Char, 30 Last name

FIRST_NAME Char, 30 First name

MIDDLE_NAME Char, 30 Middle name

BIRTHDATE Date, 10 Birth date

SEX Char, 1 XLAT [M, F, U]

MAR_STATUS Char, 1 XLAT […]

NATIONAL_ID_TYPE Char, 6 NID_TYPE_TBL.NATIONAL_ID_TYPE

NATIONAL_ID Char, 20 NID_SBR.NATIONAL_ID

CAMPUS Char, 5 CAMPUS_TBL.CAMPUS



83


RECRUITING_STATUS Char, 4 XLAT [APPL, INAC, INQR, PROS, SUSP]

ADDRESS_TYPE Char, 4 XLAT [BUSN, CAMP, DORM, HOME, LEGL, MAIL, OTHR]

ADDRESS1 Char, 55 Street Address

ADDRESS2 Char, 55 Street Address continuation

ADDRESS3 Char, 55 Street Address continuation

CITY Char, 30 City

STATE Char, 6 STATE_TBL.STATE

COUNTRY Char, 3 COUNTRY_TBL.COUNTRY

POSTAL Char, 12 Postal code

CITIZENSHIP_STATUS Char, 4 XLAT [NRA, PRA, RA, USC]

PHONE_TYPE Char, 4 XLAT […]

PHONE Char, 24 Phone number associated with above type

E_ADDR_TYPE Char, 4 XLAT [BUSN, CAMP, DORM, HOME, OTHR]

EMAIL_ADDR Char, 70 Email address associated with above type

SETID Char, 5 SETID_TBL.SETID

REG_REGION Char, 5 **REG_REGION_TBL.REG_REGION

ETHNIC_GRP_CD Char, 8 Not Used. Moved to SAD_PRS_ETH_SUS table

ADMIT_TYPE Char, 3 ADMIT_TYPE_TBL.ADMIT_TYPE

ADMIT_TERM Char, 4 TERM_TBL.STRM

ACADEMIC_LEVEL Char, 3 XLAT […]

ADM_REFRL_SRCE Char, 4 REFERL_SRCE_TBL.ADM_REFRL_SRCE

LAST_SCH_ATTEND Char, 11 EXT_ORG_TBL_ADM.EXT_ORG_ID

GRADUATION_DT Date, 10 Graduation Date

FIN_AID_INTEREST Char, 1 Y/N

HOUSING_INTEREST Char, 1 XLAT [C, F, H]

RELIGIOUS_PREF Char, 4 REL_PREF_TBL. RELIGIOUS_PREF

84


SAD_PRS_PRG_SUS Table (Optional Child Table)





SEQNUM Nbr, 3 Sequentially numbered rows [1, 2, 3...]

ACAD_PROG Char, 5 ACAD_PROG_TBL.ACAD_PROG

ACAD_PLAN Char, 10 ACAD_PLAN_TBL.ACAD_PLAN

ACAD_SUB_PLAN Char, 10 ACAD_SUBPLN_TBL.ACAD_SUB_PLAN

SAD_PRS_EXT_SUS Table (Optional Child Table)






INTERNAL_EXTERNAL Char, 1 XLAT [E, I]

EXTRA_ACTIVITY Char, 6 EXTR_ACTVTY_TBL.EXTRA_ACTIVITY

DESCR Char, 30 EXTR_ACTVTY_TBL.DESCR



SAD_PRS_INT_SUS Table (Optional Child Table)






85


EXT_SUBJECT_AREA Char, 4 EXT_SUBJECT_TBL.EXT_SUBJECT_AREA

DESCR Char, 30 EXT_SUBJECT_TBL.DESCR

LS_DATA_SOURCE Char, 3 XLAT […]

PRIORITY Nbr, 1 Priority

SAD_PRS_ETH_SUS Table






ETHNIC_GRP_CD Char, 8 **ETHNIC_GRP_TBL.ETHNIC_GRP_CD

HISP_LATINO Char, 1 Y/N

PRIMARY_INDICATOR Char, 1 Y/N

* Required field. The message will fail without this field.

** Campus Solutions table. All other tables exist in CRM.

Note: For XLAT fields, open the field definition in Application Designer, open the Field Properties, and change to the Translate Values tab in order to view the possible values and names for the field. The values have been provided where the current set contains only a few.

Sending the Message to CRM

To send the XML message to CRM, use the PeopleTools SendMaster program, found in one of the following locations:

Standalone: [PS_HOME]\sendmaster\StartSendMaster.bat

IB SDK: [PS_HOME]\webserv\peoplesoft\bin\StartSendMaster.bat

Use the following settings:

Project: PSI [XML]

Server URL: [IB Gateway URL] (Example: http://<HOST>:<PORT>/PSIGW/PeopleSoftListeningConnector)

Timeout: 0.0 sec

86


Headers: Content-type: text/xml; charset=UTF8

Requesting Node: [CRM Default Local Node]

Ext. Operation Name: EXT_CONST_LOAD_SERVICE.v1

Operation type: async

Input File: [your XML file name]

Click the Post button to send the message. Verify the message was sent successfully through the Output Information. This is an example of what that might look like:

<?xml version="1.0"?> <IBResponse type="success"> <DefaultTitle>Integration Broker Response</DefaultTitle> <StatusCode>0</StatusCode> <TransactionID>741f1b9e-7b1f-11df-9fc5-cbbc368a5a99</TransactionID> </IBResponse>

Additional Information

Following these guidelines, prospects can be successfully loaded into the staging tables. When performing an import, there are other conditions that can cause the import to fail which will be reported during the import process. These can include, but are not necessarily limited to:

• Missing TEST_REC_NBR

• Partial address

• The EMPLID must be valid if it is provided

• Academic sub plan must be valid for academic plan (and institution)

• Academic plan must be valid for academic program (and institution)

Validation and Feedback

This section documents the real-world validation that this red paper has received.

Customer Validation

Oracle is working with PeopleSoft customers to get feedback and validation on this document. Lessons that are learned from these customer experiences will be posted here.

Field Validation

Oracle Consulting Services has provided feedback and validation on this document. Additional lessons that are learned from field experience will be posted here.

87


88

Revision History

REVISION HISTORY

DATE CHANGE

04/15/2011 Initial Version.

Enterprise Integration Point Setup Between PeopleSoft Enterprise Campus Solutions and PeopleSoft Enterprise CRM April 2011 Oracle Corporation World Headquarters 500 Oracle Parkway Redwood Shores, CA 94065 U.S.A. Worldwide Inquiries: Phone: +1.650.506.7000 Fax: +1.650.506.7200 oracle.com

Copyright © 2011, 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 warranties or conditions, whether expressed orally or implied in law, including implied warranties and conditions of merchantability or fitness for a particular purpose. We specifically disclaim any liability with respect to this document and no contractual obligations are formed either directly or indirectly by this document. This document may not be reproduced or transmitted in any form or by any means, electronic or mechanical, for any purpose, without our prior written permission. Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners. AMD, Opteron, the AMD logo, and the AMD Opteron logo are trademarks or registered trademarks of Advanced Micro Devices. Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. UNIX is a registered trademark licensed through X/Open Company, Ltd. 0410

Documents

Enterprise Integration Point Setup Between People Soft Enterprise Campus Solutions and People Soft Enterprise CRM