oracle’s peoplesoft 9.0 recruiting and admissions ... · pdf fileoracle’s...

Oracle’s PeopleSoft 9.0 Recruiting andAdmissions: Managing PeopleSoftAdmission Transactions

April 2011

9.0Oracle’s PeopleSoft 9.0 Recruiting and Admissions: Managing PeopleSoft Admission TransactionsSKU lsad and lssr doclet

Copyright © 2011, Oracle and/or its affiliates. All rights reserved.

Trademark NoticeOracle is a registered trademark of Oracle Corporation and/or its affiliates. Other namesmay be trademarks of theirrespective owners.

License Restrictions Warranty/Consequential Damages DisclaimerThis software and related documentation are provided under a license agreement containing restrictions on use anddisclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreementor allowed by law, youmay not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute,exhibit, perform, publish or display any part, in any form, or by anymeans. Reverse engineering, disassembly, ordecompilation of this software, unless required by law for interoperability, is prohibited.

Warranty DisclaimerThe information contained herein is subject to change without notice and is not warranted to be error-free. If you findany errors, please report them to us in writing.

Restricted Rights NoticeIf this software or related documentation is delivered to the U.S. Government or anyone licensing it on behalf of theU.S. Government, the following notice is applicable:

U.S. GOVERNMENT RIGHTS

Programs, software, databases, and related documentation and technical data delivered to U.S. Government customersare “commercial computer software” or “commercial technical data” pursuant to the applicable Federal AcquisitionRegulation and agency-specific supplemental regulations. As such, the use, duplication, disclosure, modification, andadaptation shall be subject to the restrictions and license terms set forth in the applicable Government contract, and,to the extent applicable by the terms of the Government contract, the additional rights set forth in FAR 52.227-19,Commercial Computer Software License (December 2007). Oracle USA, Inc., 500 Oracle Parkway, Redwood City,CA 94065.

Hazardous Applications NoticeThis software is developed for general use in a variety of informationmanagement applications. It is not developedor intended for use in any inherently dangerous applications, including applications whichmay create a riskof personal injury. If you use this software in dangerous applications, then you shall be responsible to take allappropriate fail-safe, backup, redundancy and other measures to ensure the safe use of this software. OracleCorporation and its affiliates disclaim any liability for any damages caused by use of this software in dangerousapplications.

Third Party Content, Products, and Services DisclaimerThis software and documentationmay provide access to or information on content, products and services from thirdparties. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kindwith respect to third party content, products and services. Oracle Corporation and its affiliates will not be responsiblefor any loss, costs, or damages incurred due to your access to or use of third party content, products or services.

Contents

Chapter 1Managing PeopleSoft Admission Transactions.... .. ... .. ... .. ... .. ... .. ... .. ... .. ... .. ... .. .. . . . . . . . . . .1Admission Applications Web Services (AAWS).. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1

Prerequisites.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . .2External Search/Match and AAWS.... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . .2Using Applicant and Administrator Modes for AAWS... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . .2

Bulk Loading of Applications Using File Parser.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3CRM for Higher Ed EIPs and Admission Transactions.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4Setting Up Admission Transactions.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4

Pages Used to Set Up Admission Transactions.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . .6Setting Up Counters .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . .9Defining a Transaction.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . .9Defining the Search/Match Criteria.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . .19Defining Data Update Rules for Batch and Online Application Transactions.. . . . . . . . . . . . . . . . . . . . . .. . . . . . . .21Setting Up Affiliation Overrides for a Data Update Rule.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . .27Mapping Online Application Transactions to Academic Careers.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . .28Setting Up Application Defaults for Batch and Online Application Transactions.. . . . . . . . . . . . . . . . . .. . . . . . . .29Setting Up Prospect Creation Rules and Defaults for Batch and Online ApplicationTransactions... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . .32Setting Up Home or Unlisted Schools for Online Application Transactions.. . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . .34Setting Up List of Values for Online Applications.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . .36Maintaining and Extending Data for Online and Batch Transactions.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . .41Creating a Unit Test. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . .46Running Entity Unit Test Cases.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . .50

Reviewing and Processing Staged Admission Transactions.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .54Pages Used to Review and Process Staged Admission Transactions.. . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . .56Reviewing Applicant Error Messages and Transactions.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . .59Reviewing Applicant Details. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . .64Reviewing Applicant Participation Details. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . .66Reviewing Applicant’s Additional Personal Information.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . .68Reviewing Applicant’s Regional Information.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . .71Reviewing Application Error Messages and Application Data.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . .72Reviewing Applicant’s Education History.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . .79Reviewing Additional Academic Information.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . .81Reviewing General Materials and Attachments. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . .81

Copyright © 1992, 2011, Oracle and/or its affiliates. All rights reserved. iii

Contents

Reviewing Application Regional Information.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . .82Updating and Posting Transactions in Batch.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . .83Specifying Search/Match Parameters for Batch Processing.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . 86

iv Copyright © 1992, 2011, Oracle and/or its affiliates. All rights reserved.

CHAPTER 1

Managing PeopleSoft Admission Transactions

This PeopleBook chapter includes bundle documentation up to Bundle 21. This chapter was first released for Bundle18 when the AAWS feature was introduced. The last release of the chapter was for Additional Features January2011 - AAWS Application Fee (Bundle 20). You can find the Bundle 21 documentation updates in this chapter bysearching for the words Bundle 21.

This chapter discusses:

• Admission Applications Web Services (AAWS).• Bulk loading of applications using File Parser.• CRM for Higher Ed EIPs and admission transactions.• Setting up admission transactions.• Reviewing and processing staged admission transactions.

Admission Applications Web Services (AAWS)The PeopleSoft system delivers web service operations that enable your online application to interface with theCampus Solutions system. The AAWS User’s Guide contains details about the following service operations:

• Create Application• Save Application• Submit Application• Get Application• Get Applications• Get Attachment• User Registration• User Authentication• Get List of Values

Note. The "Setting Up Self-Service Request Information and Using Self-Service Student Recruiting" chapterin the PeopleSoft Enterprise Recruiting and Admissions 9.0 PeopleBook is no longer supported. Oracleexpects that academic institutions will use AAWS to develop and deploy their self service online applications.

Copyright © 1992, 2011, Oracle and/or its affiliates. All rights reserved. 1

dnair

Highlight

Managing PeopleSoft Admission Transactions Chapter 1

See AlsoAAWS User’s Guide

AAWS Developer’s Guide

Enterprise PeopleTools PeopleBook: Integration Broker

PrerequisitesComplete the following post installation setups described in the AAWS Developer’s Guide:

• Verify web service security settings.

• Set up user accounts.

• Perform a security analysis.

• Publish web service.

• Refresh the HCM registry cache.

• Set up Integration Broker.

• Verify Campus Solutions SOA framework setup entries.

• Verify Constituent Transaction Manager setup entries.

• Set up attachments URL.

External Search/Match and AAWSIf you want the system to search for duplicate records in an external system when a user submits an onlineapplication through AAWS, ensure that the CWS External Search/Match is set up.

See AlsoPeopleSoft Enterprise Campus Community Fundamentals 9.0 PeopleBook - Update 1, "Setting UpSearch/Match"

PeopleSoft Enterprise Campus Community Fundamentals 9.0 PeopleBook - Update 1, "Setting Up ExternalSearch/Match"

Using Applicant and Administrator Modes for AAWSThe Applicant mode is also known as the Self Service mode. In this mode, an applicant creates and submits anadmission application through AAWS.

In the Administrator mode, the administrative user creates and submits an application on behalf of anapplicant. The administrator may create the application for an existing EMPLID (if the administrator knowsthe applicant’s ID when creating the application), or for an unknown or new applicant.

In the Administrator mode, the system associates the application with the administrator’s user ID. You canview this association on the Application Transactions component when reviewing the submitted applications.In other words, you can use the Application Transactions component to see which administrator has created anapplication for an applicant.

In the Applicant mode, the system associates the application with the applicant’s user ID.

2 Copyright © 1992, 2011, Oracle and/or its affiliates. All rights reserved.

Chapter 1 Managing PeopleSoft Admission Transactions

In both modes, the system uses the Search/Match setup to determine which application records it should loadinto your database as new records, which records it should append to existing records in your database, whichrecords it should suspend for your further review, and which records should be ignored.

In the Administrator mode, the user must provide an institution and application center to create an application.The system enforces application center and academic structure security for the administrative user.

If an administrator saves an application, another administrator cannot submit it through AAWS. However, theother administrator can use the Application Transactions staging component to update the application statusto submitted and post the application.

In the Administrator mode, the Get Applications service call returns only in-progress applications, thatis, applications which have not been posted or cancelled. It is optional for an administrator to provide anEMPLID for a Get Applications call. If the administrator does not provide an applicant’s EMPLID, the systemreturns all the in-progress applications.

The Administrator mode is activated by the presence of this optional parameter in an incoming message:<SCC_ADMIN_MODE>. For example, an online application might send this message to Campus Solutionsfor administrator mode:

<SCC_ADMIN_MODE>

<ADM_APPL_CTR>UGRD</ADM_APPL_CTR>

<SCC_USERNAME>Userid</ SCC_USERNAME>

<EMPLID>AD1234</EMPLID>

</SCC_ADMIN_MODE>

The AAWS User’s Guide lists the parameters that an online application and the Campus Solutions systemexchange through AAWS.

See AlsoPeopleSoft Enterprise Campus Solutions 9.0 Application Fundamentals PeopleBook, “Securing Recruitingand Admissions”

PeopleSoft Enterprise Campus Solutions 9.0 Application Fundamentals PeopleBook, “Securing YourAcademic Institution”

Bulk Loading of Applications Using File ParserYou can use the PeopleSoft File Parser utility to load applications from an external file into Campus Solutions.The external file can be a delimited file or a flat file.

See AlsoAAWS Developer’s Guide

Updated "Using the File Parser Process" Campus Community PeopleBook chapter.



CRM for Higher Ed EIPs and Admission TransactionsEnterprise Integration Points (EIPs) enable your institution to exchange data between CS and CRM. EIPspublish data either whenever data updating happens for the given entities of the EIPs or when the user requestsdata. This data can be created, updated, or deleted through various channels like components, componentinterfaces, and batch processes.

The system publishes the following EIPs when an application that is submitted through AAWS or File Parserprocess is posted:

• SAD_ADM_PRSPCT_DATA_SYNC• SAD_ADM_APPL_DATA_SYNC• SAD_TEST_SCORES_SYNC• SAD_ADM_INTEREST_SYNC• SSR_EXTRACUR_ACTVTY_SYNC• SAD_EXT_ACAD_DATA_SYNC• SCC_PERSON_SYNC

The system can publish SAD_ADM_PRSPCT_DATA_SYNC when the system creates a prospect record fora saved or posted application. You use the Prospect Setup page to indicate when (upon save or post) thesystem should create a prospect record. The Prospect Setup page is discussed in the “Setting Up ProspectCreation Rules and Defaults” section of this chapter.

See AlsoPeopleSoft Enterprise Campus Solutions 9.0 Application Fundamentals PeopleBook - Update 1, “IntroducingCustomer Relationship Management for Higher Education”

CRM for Higher Education Developer’s Guide

Setting Up Admission TransactionsCampus Solutions generates a transaction when:

• An applicant or administrator uses an online application to register for a user name and password throughthe User Registration web service operation (online transaction).

• An applicant or administrator uses an online application to create, save or submit an application throughAAWS (online transaction).

• You use the File Parser utility to load applications from an external file (batch transaction).

An admissions-related online or batch transaction includes both the constituent and application data.Constituent data may include person data or data that is considered as not associated with the application.Examples of constituent data include Name, Gender, Address, and Email. Examples of application data includeAcademic Program, Admit Term, and Academic History.



When a transaction is generated, the system uses Search/Match to look for constituent data in your productionenvironment (based on the Search/Match parameters) that matches the constituent data in the transaction. Eachdefined transaction can have its own Search/Match setup. You can therefore determine the rules for creatinga new ID, updating an existing ID, suspending or ignoring a record.

The system stores the constituent and application data in staging tables. If there are errors or if Search/Matchdetermines that the incoming constituent record should be suspended or ignored, use the Constituent Stagingand Application Transactions components to correct the admissions transaction data. You can post transactionsindividually or by batch to the Campus Solutions database. The Constituent Staging and ApplicationTransactions components are discussed in the “Reviewing and Processing Staged Admission Transactions”section of this chapter.

Before you deploy your online application or start loading the applications, you must set up the transactions.

For AAWS, a minimum of two transactions must be set up: one for the data that a user submits through thenew user registration service operation and another for the online application that a user saves or submitsthrough the Save Application or Submit Application service operations. The following default transactions foruser registration and online application are delivered with the system:

• ADMISSIONS_REGISTRATION

• ADMISSIONS_APPLICATION

If you want to load admission applications using the PeopleSoft File Parser utility, set up a transaction for thebatch load.

Warning! For new user registration, do not define a new transaction. The system uses thedelivered ADMISSIONS_REGISTRATION for AAWS user registration. Do not modify theADMISSIONS_REGISTRATION transaction name because the system uses the name to register a user account.

Academic institutions require different rules for updating constituent and application data based on atransaction and the affiliation the institution has with the constituent. For example, you may have a graduateonline application rule where you want to update the constituent’s home email address in your database withthe value from a submitted graduate application. On the other hand, you may have a graduate application loadrule where you do not want to update an existing home email address value when you use File Parser to loadgraduate applications into Campus Solutions. Additionally, you may want to override this graduate applicationload rule if the constituent is a prospect. The Data Update Rule Entry component allows this flexibility. Thesystem uses these rules when it posts a transaction.

Different admission transactions may have different Search/Match settings and data update rules. For instance,an academic institution might allow undergraduate applicants to update their passport details when submittingan online application. Conversely, the institution might not want to allow graduate applicants to update theirpassport details if that data is already on the system. You can associate the two different data update rules tothese two separate transactions. Both these transactions may or may not have different Search/Match settings.

When establishing transactions, a single transaction for each institution and career combination couldbe defined. In this way, you can accommodate online applications for different careers (Examples:Undergraduate, Graduate, Graduation Business) which may have different Search/Match requirements, dataupdate rules, or intended methods of processing.

It is typical for administrators to enter the admissions application data for an applicant. It is possible for anadministrator to use the same online application to do so, as long as the application user interface is constructedto distinguish between an administrator log in and a self service applicant log in.

Administrators can use a different institution-developed user interface designed for quick data entry. The sametransaction value applied to the self service application is utilized for the institution/career combination forwhich the application is being created.



Use the Transaction Setup component to define a transaction, associate a data update rule with the transaction,and define the Search/Match setting for the transaction. Note that you cannot define a Search/Match settingfor the user registration transaction. The new user registration feature does not ask the user enough personalinformation for creating a new ID. Also, a new user may create a user ID and password without ever comingback to fill out an online application. The information entered as part of the new user registration process istherefore kept in the constituent data staging table until the user actually performs a transaction.

Applications typically vary among institutions and academic careers. Use the Appl Config page in theApplication Configuration component to map an institution and career to a transaction. The system uses thismapping to identify which transaction to use when it receives an application through AAWS. For example,suppose you have defined two transactions: UG Transaction for undergraduate applications and GradTransaction for graduate applications. When an applicant submits an undergraduate application, the systemlooks at the Appl Config page settings to determine that it needs to use the UG Transaction.

This section discusses how to:

• Set up counters.• Define a transaction.• Define the search/match criteria for a transaction.• Define data update rules for batch and online application transactions.• Set up affiliation overrides for a data update rule.• Map online application transactions to academic careers.• Set up application defaults for batch and online application transactions.• Set up prospect creation rules and defaults for batch and online application transactions.• Set up home or unlisted schools for online application transactions.• Set up list of values for your online application.• Maintain and extend data for online and batch transactions.• Create a unit test.• Run entity unit test cases.

Pages Used to Set Up Admission TransactionsPage Name Definition Name Navigation Usage

Counter Setup SCC_AWS_FIX_CTRS Set Up SACR, SystemAdministration, Utilities,Constituent TransactionMgmnt, Counter Setup

Set up the max ID numberfor the TemporaryConstituent ID.

Transaction Setup SCC_TRANSAC_DTLS • Set Up SACR, SystemAdministration, Utilities,Constituent TransactionMgmt, Transaction Setup

• Student Admissions,UCAS Processing,Search/Match Processing,Transaction Setup

Define the transaction foran online transaction or abatch transaction.



Page Name Definition Name Navigation UsageSearch/Match Setup SCC_SEARCH_PARMS • Set Up SACR, System

Administration, Utilities,Constituent TransactionMgmt, Transaction Setup,Search/Match Setup

• Student Admissions,UCAS Processing,Search/Match Processing,Transaction Setup,Search/Match Setup

Define the Search/Matchcriteria for an onlinetransaction or for runningSearch/Match manuallyfrom the Constituent Stagingcomponent.

Not applicable for the userregistration transaction.

Data Update Rule Entry SCC_DUR_ENTRY Set Up SACR, SystemAdministration, Utilities,Constituent TransactionMgmt, Data Update RuleEntry

Define how the constituentdata is processed for anonline transaction or batchtransaction.


Affiliation Overrides page SCC_DUR_AFL_OVRD Set Up SACR, SystemAdministration, Utilities,Constituent TransactionMgmt, Data Update RuleEntry, Affiliation Overrides

Override a data update rulebased on the affiliation theconstituent has with theacademic institution.


Appl Config SAD_TRANSAC_MAP Set Up SACR, ProductRelated, Recruiting andAdmissions, ApplicationConfiguration, ApplicationConfiguration, Appl Config

Map online applicationtransactions to academiccareers.

Not applicable for userregistration.

Application Setup SAD_APL_CNT Set Up SACR, ProductRelated, Recruiting andAdmissions, ApplicationConfiguration, ApplicationConfiguration, ApplicationSetup

Define how the systemshould assign an applicationcenter and optionally assign3Cs to an application bydefining which EventID should be used in theprocessing. The systemuses this setup when youload applications in batchor when the user saves orsubmits an applicationthrough AAWS.




Page Name Definition Name Navigation UsageProspect Setup SAD_PRS_SETUP Set Up SACR, Product

Related, Recruiting andAdmissions, ApplicationConfiguration, ApplicationConfiguration, ProspectSetup

Define how the systemshould create a prospectrecord, and if a prospectrecord is created, how toassign default values to theprospect record. The systemuses this setup when youprocess applications in batchor when the user saves orsubmits an applicationthrough AAWS.


School Setup SAD_AWS_SCH_DFL Set Up SACR, ProductRelated, Recruiting andAdmissions, ApplicationConfiguration, ApplicationConfiguration, School Setup

Define how the systemshould process unlisted orhome schools. The systemuses this setup when youload applications in batchor when the user saves orsubmits an applicationthrough AAWS.


List of Values Setup SCC_SL_LOV Set Up SACR, ProductRelated, Recruiting andAdmissions, ApplicationConfiguration, List of Values

Define how the systemshould return the list ofvalues for a field. Thesystem uses this setup whenthe online application callsthe Get List of Values serviceoperation.

Entity Registry SCC_ENTITY_REG Set Up SACR, SystemAdministration, Entity,Entity Registry

Maintain and extend the datastructure that representsthe information collectedfrom an online application orbatch load.

Entity Unit Tests (Setup) SCC_ENTITY_UT Click the View Unit Testsbutton on the Entity Registrypage.

Attach the unit testapplication classes to anentity.

Entity Unit Tester SCC_ENT_MASS_UT Set Up SACR, SystemAdministration, Entity,Entity Unit Tester

Run all the unit testsassociated with a specifiedentity. Unit tests are definedon the Entity Unit Tests(Setup) page.

Entity Unit Tests SCC_ENTITY_UT Click the View Unit Testslink from the Entity UnitTester page

View the unit tests tied to anentity name, the applicationclass used and the latest runstatus for a specific unit test.



Setting Up CountersAccess the Counter Setup page (Set Up SACR, System Administration, Utilities, Constituent TransactionMgmnt, Counter Setup).

Counter Setup page

The field on this page is automatically incremented by one by default when using the Constituent TransactionManager functionality. Set the last used number so that automatic numbering does not create numbers thatalready exist in the data.

Temp Constituent ID Displays the last Temporary Constituent ID assigned. A Temp Constituent IDis given when a transaction is performed from the Constituent TransactionManager framework.

See “Defining a Transaction” and “Reviewing Applicant Error Messages andTransactions” sections, for more information.

Fix Counter Clicking this button resets the Temp Constituent ID based on the highestvalue of that field in the database. The field is dynamically found based onthe Peopletools metadata for the record field relationships, and the maxpossible value for that field across all possible records is set as the counter.This avoids the possibility of the system trying to reuse an ID and beingpolluted by pre-existing data.

Note. After you have begun using the Constituent Transaction Manager functionality, you can access this pageto determine the last number that was incremented for the Temporary ID. Manually changing this number ispractical for the initial setup, but not recommended for further changes. If the ID entered is changed to anexisting number, the system will attempt to re-use the ID. Instead use the Fix Counter button.

Defining a TransactionAccess the Transaction Setup page (Set Up SACR, System Administration, Utilities, Constituent TransactionMgmt, Transaction Setup).

This is an example of the delivered sample online application transaction:



Transaction Setup page: Online application transaction (1 of 2)



Transaction Setup page: Online application transaction (2 of 2)

This is an example of the delivered new user registration transaction:



Transaction Setup page: New user registration transaction (1 of 2)

Transaction Setup page: New user registration transaction (2 of 2)

This is an example of a transaction for the File Parser batch load of applications:



Transaction Setup page: File Parser batch load transaction (1 of 2)



Transaction Setup page: File Parser batch load transaction (2 of 2)

For a File Parser batch load you must clear the Online Transaction check box and select the Batch option.Also, set up the transaction code for the batch load of applications on the Mapping page of the File MappingDefinition component. You can set this code as a default value (by default, the SCC_TRANSAC_CD field inthe SCC_STG_CONSTIT record stores the transaction code). The File Parser process can also retrieve thetransaction code directly from the load file (in such a case, set the mapping action to Direct from file). Formore information about the File Mapping Definition component, refer to the updated Campus CommunityFile Parser PeopleBook chapter.

Transaction Indicates the transaction code.You specify the transaction code when you add a transaction.

Transaction Status Activate or inactivate the transaction.

Data Update Rule Select the data update rule that you want the system to apply to the constituent(person) data managed by this transaction. You define a data update rule inthe Data Update Rule Entry page.

Transaction Options

Online Transaction Select to indicate that the transaction is performed online by a user. Forexample, an online transaction occurs when an applicant saves or submits anadmission application through AAWS.Clear this check box to indicate that the transaction is performed offline by auser. For example, an offline transaction occurs when you use File Parser toload applications from a text file.

New User Registration Select to indicate that the transaction is used to perform registration andauthentication of a new user.If you select this check box, the system hides the Search/Match Setup tab andthe Transaction Data Launch View group box, because they are not applicablefor a new user registration transaction.



Note. Your system allows for only one transaction to be set as new userregistration at a time. The ADMISSIONS_REGISTRATION transaction isdelivered with your system. Because of this restriction, the system hides theNew User Registration check box for all other transactions. Do not modify theADMISSIONS_REGISTRATION transaction name because the system usesthe name to register a user account.

Batch Select if you do not want the system to immediately run Search/Match whenthe data is individually submitted. If you select this option, the system storesthe submitted data in staging tables and you will need to run the TransactionManagement process to run Search/Match and post the submitted data toCampus Solutions.

Realtime Select to have the system immediately run Search/Match when the data issaved or submitted from an online or offline process.

Run on Save This check box appears if the Realtime check box is selected.Select this check box if you want the system to immediately run Search/Matchwhen a user saves a transaction.Clear this check box if you want the system to immediately run Search/Matchwhen a user submits a transaction.

Warning! Selecting Run on Save will trigger Search/Match immediately after user saves the transaction.Make sure your user interface requires sufficient personal information to be entered so that there is enoughdata to populate the search criteria used by Search/Match. Otherwise, Search/Match could create a new IDor update an existing record with erroneous or missing information.

Transaction HandlerA transaction can contain generic information about a constituent (such as names, addresses, and dateof birth), as well as data specific to the transaction. For example, an admission transaction will includepersonal information (constituent data) and application data (transaction data). You can use the TransactionHandler group box to define how the system should handle all the transaction data. You can create yourown PeopleCode application class handler for the transaction data and then associate that application classwith the transaction in this group box.

The following table lists the delivered transaction handler values for ADMISSIONS_APPLICATION. Donot change these values. Also use these values when defining a transaction handler for any new applicationtransaction you may create.

Root Package ID Path Application Class IDSCC_OLA TRANSACTION AdmissionTransaction

The following table lists the delivered transaction handler values for ADMISSIONS_REGISTRATION.Do not change these values.

Root Package ID Path Application Class IDSCC_OLA TRANSACTION DefaultTransaction



Transaction Status: The system needs a field in transaction staging tables where it can store the status ofthe transactions. Use the Transaction Status region to indicate the record and field where the transactionstatus is stored.

The following table lists the delivered transaction status setup values for ADMISSIONS_APPLICATION.Do not change these values. You should always use these values when defining a transaction status setup forany new application transaction you may create.

Record Name Field Name Date Field NameSAD_APL_DAT_STG SAD_APPL_STS SAD_APPL_STS_DT

The following table lists the delivered transaction status setup values for ADMISSIONS_REGISTRATION:

Record Name Field Name Date Field NameSCC_STG_CONSTIT SCC_STG_STATUS SCC_STG_STS_DT

Constituent HandlerYou can use the Constituent Handler group box to define how the system should handle the constituent data ina transaction. You can create your own PeopleCode application class handler for the constituent data and thenassociate that application class with the transaction in this group box.

The default application class that handles the constituent data is delivered with the system. You can modifythis application class or create a new application class.

The following table lists the default constituent handler values. You should always use these values whendefining the constituent handler values for an online application transaction or batch load transaction.

Root Package ID Path Application Class IDSCC_SL_TRANSACTION INTFC DefaultConstituent

Partition DataUse the following options to indicate how the system should maintain the data in the staging tables.

By Constituent Select this option to have the system maintain only one instance of theconstituent data for all transactions of the constituent (that is, One Constituent: Multiple Transactions ratio). This means that constituent data updatesperformed within a single transaction are visible across all other transactions.An example of the By Constituent impact: An applicant (user ID: Gina) hasused an online application to register for a user account and then, later on,saved or submitted four admission applications. The system creates a totalof five transactions for Gina, one transaction for user registration and fourtransactions for the four applications. For all the five transaction records, thesystem maintains a single constituent record. Gina updates her email addresswhen saving or submitting the fourth application. The system updates Gina’sconstituent record with the new email address.

By Transaction Select this option to have the system maintain a separate instance of constituentdata for every transaction of the constituent (that is, One Constituent : OneTransaction ratio). This means that constituent data updates performed withina single transaction are not visible across all other transactions. An example ofthe By Transaction impact: An applicant (user ID: Jason) has used an online



application to register for a user account and then, later on, saved or submittedfour admission applications. The system creates a total of five transactionsfor Jason. For all the five transaction records, the system maintains fiveconstituent records of Jason. Jason updates his email address when saving orsubmitting the fourth application. The system updates Jason’s constituentrecord related to the fifth transaction with the new email address but does notupdate his other four constituent records.

If you have selected By Constituent, the Summary Information page of the Constituent Staging componentdisplays multiple transaction rows in the Related Transaction region (if multiple transactions exist for theconstituent). When you search for transactions of a user who has multiple By Constituent transactions,the Constituent Staging component automatically displays the Summary Information page of the user with therelated transactions. In the following example, the partition data by constituent option has been selected for theADM_CONSTITUENT1 transaction and, therefore, the Summary Information page displays the constituentElizabeth’s multiple ADM_CONSTITUENT1 application transactions on a single page.

Partition Data By Constituent (Summary Information page)

If you have selected By Transaction, the Summary Information page of the Constituent Staging componentalways displays only one transaction row in the Related Transaction region (even if multiple transactions existfor the constituent). When you search for transactions of a user who has multiple By Transaction transactions,the Constituent Staging component displays multiple search results. In the following example, the partitiondata by transaction option has been selected for the ADMISSION_APPLICATION transaction and, therefore,the system displays multiple search results for the constituent Jonathon.



Partition Data By Transaction (search results)

In the following example, you can see that the Summary Information page displays only one applicationtransaction for the constituent because the partition data by transaction option has been selected for theADMISSION_APPLICATION transaction:

Partition Data By Transaction (Summary Information page)

If you have selected the partition by transaction option, the system assigns a unique temporary ID to eachtransaction that the system generates for the constituent. If you have selected the partition by constituent option,the system assigns a unique temporary ID to all the transactions that the system generates for the constituent.



See “Reviewing and Processing Staged Admission Transactions” section in this chapter for informationon the Constituent Staging component.

For the User Registration transaction, we recommend that you select the By Constituent option.

Note. The preceding two graphics of the Summary Information page do not show the Created By field.This new field has been added to all the pages of the Constituent Staging and Application Transactionscomponents for Bundle 21. Refer to the “Reviewing and Processing Staged Admission Transactions” sectionfor more information.

Note. In the AAWS administrator mode, the system always generates a temporary ID for each application thatan administrator creates, regardless of whether you have selected the By Transaction or By Constituent option.In other words, the system does not support partition by constituent for the administrator mode.

Transaction Data Launch ViewThis group box indicates how you can access the transaction details by clicking a link on the SummaryInformation page of the Constituent Staging component. By default, the text you enter in the TransactionName field becomes the label for the link on the Related Transactions grid of the Summary Information page.

The following table lists the delivered Transaction Data Launch View settings for ADMISSIONS_APPLICATION transaction. You should always use these values when defining the transaction data launchview settings for any new application transaction you may create.

Menu Name Menu Bar Name Menu Item Name Menu Page NameProcess Applications Use SAD_APPL_STG SAD_APPL_STG

The Transaction Data Launch View group box is not available for user registration. Therefore, by default, theSummary Information page does not display a link for the user registration transaction.

Defining the Search/Match CriteriaAccess the Search/Match Setup page (Set Up SACR, System Administration, Utilities, Constituent TransactionMgmt, Transaction Setup, Search/Match Setup).



Search/Match Setup page

Note. The words “Parameters Refreshed” appear if this is the first time you have entered this page, or if any ofthe parameters on this page changed since the last time you accessed this page.

Batch, Realtime and Runon Save

Indicates the Search/Match options you have selected on the Transaction Setuppage. These options are discussed in the "Defining a Transaction" section.

Select a Search Type, Search Parameter, Search Result Code, and other search fields as appropriate. Thevalues selected on this page are used behind the scenes when Search/Match is processed Realtime at the timethe user saves or submits and from the Summary Information page when an administrator manually triggersSearch/Match by clicking the Search/Match Results link for a specific transaction.

To set up Search/Match when set to process by Batch, see the “Specifying Search/Match Parameters forBatch Processing” section.

Note. Transaction Manager supports only person searches at this time. Therefore, the Search Type fielddefaults to Person and only Search Parameter and Search Result Code values set up for Person are valid.

See PeopleSoft Enterprise Campus Community Fundamentals 9.0 PeopleBook - Update 1, "Setting UpSearch/Match" for information about setting up Search/Match rules, order, parameters, and results.

See PeopleSoft Enterprise Campus Community Fundamentals 9.0 PeopleBook - Update 1, "Setting UpExternal Search/Match"



Match(es) FoundThis group box contains one row for each search rule defined in the Search Parameter selected. DefineSearch/Match orders and Search/Match rules on the Search/Match Rule page.

Search Order Nbr (searchorder number)

For each order number, select what you want to do with the incoming record ifthe search/match/post process discovers one or more matching records.

One Match andMultipleMatches

Select whether you want to add, update, suspend, or ignore matching records:

Add: Add a new record to your database using the staging table record.

Update: Update the existing record with the data in the staging table record.

Note. Updates are dependent on what has been defined as update rules on theData Update Rule Entry component.

Suspend: Suspend any processing of the staging table record. Use theConstituent Staging component to determine manually whether or not thisstaged record matches a record in your database. The Constituent Stagingcomponent is discussed in the “Reviewing and Processing Staged AdmissionTransactions” section of this chapter.Ignore: Ignore the staging table record that matched a record in your database.

No Match FoundSelect one of the following options to specify what Search/Match should do when it does not find a matchingrecord in your database or the external system if you use External Search/Match:

Add: Add the unmatched record, including personal data, to your database.

Suspend: Keep the unmatched record in the staging tables to be looked at manually. Use the ConstituentStaging component to review the record.

Ignore: Ignore the unmatched record completely.

See AlsoAAWS User’s Guide, “Configuration Hints and Tips”, Constituent Transaction Manager

Defining Data Update Rules for Batch and OnlineApplication TransactionsAccess the Data Update Rule Entry page (Set Up SACR, System Administration, Utilities, ConstituentTransaction Mgmt, Data Update Rule Entry).



Data Update Rule Entry page (1 of 4)




A data update rule defines whether or how transactions can update data in the constituent production tables.

When you add a new data update rule, the Data Update Rule Entry page displays only those entities for whichthe Apply Data Update Rule check box is selected. This check box is available on the Entity Registry page(Set Up SACR, System Administration, Entity, Entity Registry).

Refer to the AAWS Developer’s Guide and the “Maintaining and Extending Data for Online and BatchTransactions” section in this chapter for information about the Entity Registry page.

The default value for Update Action is Do Not Update.

Copy Click to access the Copy Data Update Rule page and copy an existing rule’ssettings to the new rule.

Refresh Click to refresh the entities populated on the Data Update Rule Entry page.When you click the button, a message appears indicating which entities havebeen added or removed from the page.For example, suppose you added a new entity and selected the Apply DataUpdate Rule check box on the Entity Registry page. In such a case, you mustclick the Refresh button to populate the Data Update Rule Entry page with thisnew entity. Conversely, you cleared the Apply Data Update Rule check boxon the Entity Registry page for an entity. In such a case, you must click theRefresh button to remove the entity from the Data Update Rule Entry page.

Set All Actions To Select an update action that you want to apply for all the entities. Theupdate actions you can select are Add If Blank, Do Not Update, Safe Update(applicable for only non-type entities) and Update/Insert.

Entity Name Displays the name of the entity as defined on the Entity Registry page.

Staging Record Displays the staging record where the system stores the incoming entity datafrom a transaction. You define a staging record for an entity on the EntityRegistry page.

Entity Type This field is only available for entities with multiple types, such as Addressand Name entities. The default value is All.Select Show All Types to display all the types for an entity. Select this valueif you want to specify a different update action for one or more types of anentity. For example, suppose you want to enter Update/Insert update action forcampus address and Add If Blank update action for all the other address types



(such as home or billing). In such a case, select Show All Types for the Addressentity and specify the update action for each address type.Select All if you do not want to display all the types for an entity. Select thisvalue if you want to specify the same update action for all the types of anentity. For example, select All if you want to enter Update/Insert update actionfor all the address types (such as campus, home and billing).

Entity Field This field is only available for entities that do not have any types, such asConstituent and Diversity entities.Select Show All Fields to display all the fields of an entity. Select this valueif you want to specify a different update action rule for one or more fieldsof an entity. For example, suppose you want to enter Do Not Update updateaction for Date of Birth field and enter Add If Blank update action for rest ofthe Constituent fields (such as Birth Location or Birth Country). In such acase, select Show All Fields for the Constituent entity and specify the updateaction for each Constituent field.

Update Action Identify what the system should do when it posts the entity data to theproduction records of an existing constituent:

Select Add If Blank to add the entity data only if the constituent does not havethe entity data. For example, suppose you have assigned Add If Blank to theHome Email Address entity type for the graduate application transaction. Thesystem receives a graduate application with a home email address throughfile load or AAWS. The constituent does not have a home email address inthe database. In such a case, the system adds the constituent’s home emailaddress to the database.

Select Do Not Update to prevent the constituent’s entity data from beingupdated. For example, suppose you have assigned Do Not Update to theNational ID entity for the graduate application transaction. The system receivesa graduate application with a National ID through file load or AAWS. Theapplicant already has a National ID on the production record of the database.In such a case, the system does not update the applicant’s existing National ID.

Warning! Note that if the Do Not Update action is selected for an entity, thedata will not be posted even if data does not exist on the production record.

Select Safe Update to update or insert the constituent’s entity data only if theincoming data is populated. This action is available only for entities withouta type. If the entity data has an effective date, then the system inserts neweffective dated rows but does not overwrite existing fields with blank or zero.If the entity data does not have an effective date, then the system updates theexisting record only for the fields where incoming data is populated. Forexample, suppose you have assigned Safe Update to the Constituent entityfor the graduate application transaction. The system receives a graduateapplication with only Date of Birth and Birth Country populated for theConstituent entity through file load or AAWS. Birth State and Birth Locationare not populated as part of the incoming data. The applicant already has Dateof Birth, Birth Country, Birth State and Birth Location on the productionrecord of the database. In such a case, the system updates Date of Birth andBirth Country with the incoming data but will not update Birth State and BirthLocation as these fields are not populated as part of the incoming data.



Select Update/Insert to update or insert the constituent’s entity data, even if theincoming and existing values are the same. If the entity data has an effectivedate, then the system inserts a new effective dated row if the incoming datadiffers from the current effective dated row. If the entity data does not have aneffective date, then the system updates the existing record.

Warning! Note that the Update/Insert action will update character-based fieldsto blank or null and numeric fields to zero if the field is not populated on theincoming entity. For example, suppose you have assigned Update/Insert tothe Constituent entity for the graduate application transaction. The systemreceives a graduate application with only Date of Birth and Birth Countrypopulated for the Constituent entity through file load or AAWS. Birth Stateand Birth Location are not populated as part of the incoming data. Theapplicant already has Date of Birth, Birth Country, Birth State and BirthLocation on the production record of the database. In such a case, the systemupdates the applicant’s existing Date of Birth and Birth Country with theincoming data but will also update Birth State and Birth Location to blank. Forthis reason, use caution when selecting the Update/Insert action to preventexisting data from being updated to blank or zero.

Refer to the next section “Setting Up Affiliation Overrides for a Data Update Rule” for information on howyou can have the system update constituent data based on the affiliation the institution has with the constituent.

See AlsoAAWS User’s Guide, “Configuration Hints and Tips”, Data Update Rules

Setting Up Affiliation Overrides for a Data Update RuleAccess the Affiliation Overrides page (Set Up SACR, System Administration, Utilities, ConstituentTransaction Mgmt, Data Update Rule Entry, Affiliation Overrides).

Affiliation Overrides page

Note. To use Affiliation Overrides, Transaction Setup must be set to Partition by Transaction, Institutionmust be a field for the Record Name entered in the Transaction Status section of Transaction Setup, and theAffiliation Overrides page must be set up.

Rule Name Displays the name of the base update rule.

Institution and AffiliationCode

Enter the academic institution and affiliation for which you want to overridethe rule defined on the Data Update Rule Entry page.



For example, suppose for a rule name UGRD_APPLICATION you havedefined an Update/Insert update action for the Home Address entity type.For the same rule, UGRD_APPLICATION, you can specify that if the systemreceives an application and the constituent has an affiliation of Employee forthe PSUNV institution, apply a different rule that has an update action of DoNot Update for the Home Address entity type.

Affiliation OverrideRule ID

Enter the overriding rule for the academic institution and affiliationcombination.

Order Indicate the order in which you want the system to check the override rule.The system applies the Affiliation Override Rule ID for the affiliation assignedto the constituent using the following criteria:

• The highest order where the affiliation status is Active.• The affiliation start date is less than or equal to the date when the

transaction is submitted.• The affiliation end date is either blank or greater than or equal to the date

when the transaction is submitted.For example, if you have defined an override rule for PSUNV and Employeewith order number 10 and another rule for PSUNV and Student with ordernumber 20, the system evaluates the the Employee rule before the Studentrule. If the constituent has active affiliations for both Employee and Student,the system applies the override rule for Employee. If the constituent has anactive affiliation for only Student, the system applies the override rule forStudent. If the constituent does not have an affiliation for either Employee orStudent, the system applies the base update rule.

Mapping Online Application Transactions to Academic CareersAccess the Appl Config page (Set Up SACR, Product Related, Recruiting and Admissions, ApplicationConfiguration, Application Configuration, Appl Config).

Appl Config page



You can enter only online transactions (except user registration transaction) in the Transaction field. To checkwhether a transaction has been marked as Online or Batch, use the Transaction Setup page (Set Up SACR,System Administration, Utilities, Constituent Transaction Mgmt, Transaction Setup).

See AlsoAAWS User’s Guide, “Configuration Hints and Tips”, Application Configuration

Setting Up Application Defaults for Batch and OnlineApplication TransactionsAccess the Application Setup page (Set Up SACR, Product Related, Recruiting and Admissions, ApplicationConfiguration, Application Configuration, Application Setup).

Application Setup page: Criteria tab (1 of 2)

Application Setup page: Criteria tab (2 of 2)



Application Setup page: Assigned Values tab (1 of 2)

Application Setup page: Assigned Values tab (2 of 2)

Use the Criteria tab to define the selecting criteria — such as academic career, academic program, andacademic plan — that will constitute a particular group of applications. Use the Assigned Values tab todefine the application center and event ID that the system assigns to the particular application group. Whenthe system receives an application, it uses this mapping to determine which application center and eventID should be assigned to an application.

In the exhibit example — Application Setup page: Criteria tab (2 of 2) — you can see that for row 12, career isUGRD, program is AA and plan is Music. For the same row, in the exhibit example — Application Setuppage: Assigned Values tab (2 of 2) — the application center is APP3. Assume that the system receives anapplication for a career of UGRD, program of AA, and plan of Music through AAWS or batch load. In such acase, the system assigns APP3 to this application.



The system requires an application center to create an admission application. Therefore, you must map eachcareer with an application center on the Application Setup page. The system generates an error message if itreceives an application through AAWS or batch load and it does not find the corresponding application centerfrom this mapping. You can view this error message on the Application Transactions staging component. Notethat the system assigns an application center from this mapping when an application is saved or submitted. Thesystem assigns the 3C Event ID when an application is posted.

Note. You should complete this mapping for only applicant mode. In the administrator mode, the userprovides the application center when creating an admission application. Therefore, this setup is not relevantfor administrator mode.

Criteria

Career Enter the career for which you want to assign an application center (andoptionally, an event ID).

Program Optionally, enter the program for which you want to assign an applicationcenter (and optionally, an event ID).If you leave this field blank, the system assigns the application center toall the programs within the career. For example, suppose you have twoapplication centers: APP01 and APP02. Map the career GRAD and programMBA combination to the APP01application center and map the GRAD careerto the APP02 application center. In such a case, the system will assign APP01application center to an MBA application and it will assign APP02 to othernon MBA applications such as a MS or MA application.

Plan Optionally, if you have entered a program, enter the plan for which you wantto assign an application center (and optionally, an event ID).If you leave this field blank, the system assigns the application center to all theplans within the program. For example, suppose you have two applicationcenters: APP03 and APP04. Map the career GRAD, program MS, and planFinance combination to the APP03 application center and map the GRADcareer and MS program to APP04 application center. In such a case, thesystem will assign APP03 application center to an MS Finance applicationand it will assign APP04 to other Master of Science applications such as MSin Biochemistry or MS in Physics.

Country and CitizenshipStatus

Enter the country and citizenship if you want to assign an application center(and optionally, an event ID) based on the applicant’s citizenship. Forexample, you could have the career UGRD, country USA, and citizenship AlienTemporary mapped to an Undergrad International Office application centerand GRAD, USA, and Alien Temporary mapped to a Graduate InternationalOffice application center.

Note. If you enter a value in one of the two fields, you cannot leave theother field blank. For example, if you enter a country, you must specifythe citizenship.

Note. When determining the application center assignment, the system uses the following order: citizenshipstatus, academic plan, academic program, and academic career.



Assigned ValuesEnter the application center, and optionally the event ID, for the row entered on the Criteria tab.

Only the event IDs that have the administrative functions ADMA (admissions application) and ADMP(admissions program) are available. ADMP is available only if you select an academic program on the Criteriatab. Define event IDs on the Event Definition page.

See PeopleSoft Enterprise Campus Community 9.0 Fundamentals PeopleBook - Update 1, "Using the 3CEngine," Defining 3C Engine Events.


Setting Up Prospect Creation Rules and Defaults for Batchand Online Application TransactionsAccess the Prospect Setup page (Set Up SACR, Product Related, Recruiting and Admissions, ApplicationConfiguration, Application Configuration, Prospect Setup).

Prospect Setup page: Criteria tab



Prospect Setup page: Assigned Values tab

Use the Criteria tab to specify whether you want the system to create a prospect when the user saves anapplication through AAWS or when you post an application to the Campus Solutions database. Also,on this tab define the criteria for creating the prospect. Use the Assigned Values tab to specify the defaultvalues that the system assigns to the prospect. You must specify the recruiting center, recruiting status, andreferral source values.

In the exhibit example — Prospect Setup page: Criteria tab — you can see that for row 3, career is MED,program is MED, plan is Pharmacology and Create Prospect value is SAVE. For the same row, in the exhibitexample — Prospect Setup page: Assigned Values tab — values such as the recruiting center MPHA isassigned. Assume that a user saves an pharmacology application through AAWS. In such a case, the systemcreates a prospect record for the applicant and also assigns the default values such as the recruiting centerMPHA to this newly created prospect record.

Note. To create prospect on save, the online application must ensure that the required constituent data iscollected before the user saves the application.

Also, ensure that the related transaction is set to run real time on save. If the related transaction is set torun on submit, then the Prospect Setup page displays a warning message if you choose the Save option forCreate Prospect. For example, suppose you have a transaction UGRD_online_app and you have mapped thistransaction to the UGRD career and GLAKE institution on Appl Config page. You have not selected the Runon Save check box on the Transaction Setup page for this transaction. In such a case, the Prospect Setup pagedisplays a warning message if you select the Save option for the UGRD and GLAKE criteria. If the prospectsetup is set to create a prospect on Save, but the transaction is not set to run real time on Save, you can stillcreate the prospect record by running the Transaction Management process for Saved transactions.

Criteria

Career Enter the career for which you want to create prospect records and assigndefault values.



Program Optionally, enter the program for which you want to create prospect recordsand assign default values.If you leave this field blank, the prospect records are created for all theprograms within the career.

Plan Optionally, if you have entered a program, enter the plan for which you wantto create prospect records and assign default values.

If you leave this field blank, the prospect records are created for all theplans within the program or career.

Create Prospect Identify how you want to create prospect records for the career (and programand/or plan, if applicable):Save: Select if you want the system to create a prospect record when itreceives a Save Application service operation request or when the applicationsare loaded into the staging tables using File Parser and have a transactionstatus of Saved.Post: Select if you want the system to create a prospect record when the onlineor batch transactions are posted to the Campus Solutions database.

If the prospect record already exists for the institution and career of the transaction, the system updates theprospect record to insert program and plan data that does not exist, and also inserts Housing Interest, FinancialAid Interest, Last School Attended and Graduation Date if not previously populated.

Note. If you want to create prospects for all applications received for the criteria entered, enter a row for Saveand a row for Post. This will ensure that the system will create a prospect record when an application isnot saved prior to submission.

Assigned ValuesEnter the recruiting center, recruiting status, referral source and optionally the event ID, for the row entered onthe Criteria tab.

Only the event IDs that have the administrative functions PROS (prospect) and PROP (prospect program) areavailable. PROP is available only if you select an academic program on the Criteria tab. Define event IDson the Event Definition page.


Setting Up Home or Unlisted Schools for OnlineApplication TransactionsAccess the School Setup page (Set Up SACR, Product Related, Recruiting and Admissions, ApplicationConfiguration, Application Configuration, School Setup).



School Setup page

An online application may need to capture the applicant’s academic history. The online application maypresent a field with a list of schools, colleges, and universities that exist in the system’s External Organizationtable and the user may select a value from this list. However, two applicant categories exist, those who haveattended an academic institution that is not listed in the list of values (unlisted schools) and those who arehome schooled. The online application may present a text field or some other method to capture the homeor unlisted school details. Use the School Setup page if you want to define how the system should processthese unlisted or home schools.

Unlisted Schools

Post Application UsingDefault

Select if you want to specify a default organization ID for unlisted schools or ifthe applicant has not provided the school name.

Default Organization This field appears if you select the Post Application Using Default option.

Specify the default organization ID to post with the application record.

Note. If the application contains multiple rows of Unlisted School data, thedefault will apply to the first processed row. Because External OrganizationID is a key field, it is not possible to use the default more than once. In theevent of multiple Unlisted Schools, the web service will create a reconciliationerror in the staging component and will require manual reconciliation of theadditional Unlisted School rows.

Require ManualReconciliation

Select if you want to manually correct an application that has an unlistedschool or no school.



If you select this option and if the application transaction has an unlistedschool or no school, the system retains the transaction in the staging table witha constituent status of Error. You will have to resolve the error message andthen post the application. You can use the Application Transactions componentto select an appropriate External Org ID and run the post process. Refer to the“Reviewing and Processing Staged Admission Transactions” section of thischapter for more information on this component.

Home School

Post Application UsingDefault

Select if you want to specify a default organization ID for home schools.

Default Organization This field appears if you select the Post Application Using Default option.Specify the default organization ID to post with the application record.

Note. If the application contains multiple rows of Home School data, thedefault will apply to the first processed row. Because External OrganizationID is a key field, it is not possible to use the default more than once. In theevent of multiple Home Schools, the web service will create a reconciliationerror in the staging component and will require manual reconciliation ofthe additional Home School rows.

Require ManualReconciliation

Select if you want to manually correct an application that has a home school.If you select this option and if the applicant has mentioned home school,the system retains the transaction in the staging table with a constituentstatus of Error. You will have to resolve the error message and then post theapplication. You can use the Application Transactions component to select anappropriate External Org ID and run the post process. Refer to the “Reviewingand Processing Staged Admission Transactions” section of this chapter formore information on this component.


Setting Up List of Values for Online ApplicationsAn online application may present list fields for the users. These fields only accept input from a list ofvalues. The list of values could be translate values or the values that you set up in Campus Solutions. Thefollowing is an example of a field with a list of values.

A List field



Your online application must use the Get List of Values service operation to retrieve the list of values for afield. This service operation looks at the default table record or column to retrieve the values for a field.However, if you want to control which values are sent back to the online application, use the List of ValuesSetup page. To access the List of Values Setup page, select Set Up SACR, Product Related, Recruiting andAdmissions, Application Configuration, List of Values.

List of Values Setup page

For instance, in the exhibit example — List of Values Setup page — you can see that the applicant andadministrator modes point to different tables for retrieving the admit type values. Therefore, to retrieve the listof values for an applicant, the service operation will use the ADMIT_TYPE_VW table. To retrieve the list ofvalues for an administrator, the service operation will use ADMIT_TYPE_TBL.

You set up admit types in the Admit Type Table page (Set Up SACR, Product Related, Recruiting andAdmissions, Prospect/Applicant Recruiting, Admit Type Table). The page accepts a description and shortdescription for an admit type. In the exhibit example — List of Values Setup page — the setup indicatesthat for self service users (applicants) the service operation will display the description, whereas for theadministrator the short description will be displayed in the list of values. The exhibit example also shows thatthe setup does not display the RAD admit type (Readmit) to the applicant.



This is an optional setup. Only the Get List of Values service operation can use this setup. Therefore, if youronline application is not using the Get List of Values service operation to populate its lists of values, then youshould not use this setup. Also, if you do not want to alter the default way in which the operation picks up thelist of values for a field, then you should not use this setup. For example, suppose you have presented the userwith an Admit Type drop down list. To display the admit type list of values, the Get List of Values serviceoperation, by default, picks the values you have defined in the Admit Type Table. If you do not want to hideany of these values from the user or point to a different record to pick up the values, you need not use theList of Values Setup page for the Admit Type field.

Record Name Indicates the table that contains the field values.You specify the record name when you add a list of values setup rule.

Field Name Enter the field whose list of values you want to modify.

A record may have multiple fields and therefore multiple rows may exist inthis page because:

• The online application could be inserting data into multiple fields ofthis record.

• One field is dependent on another field for its list of values.For example, the ADM_APPL_PROG record contains ACAD_PROGand ADMIT_TERM fields because the list of valid academic programs isdependent on an admit term. On an online application, the user must firstspecify an admit term and then the academic program.

Self Service ModeUse this group box to control the list of values for applicants who will use your online application.

This group box is available for only user defined list of values. Examples of fields that have user definedlist of values include ACAD_CAREER and ADMIT_TYPE. This group box is not available for fields thathave translate values. Examples of fields that have translate values include ACADEMIC_LEVEL andHOUSING_INTEREST.

Edit Table Select the table from which you want the service operation to retrieve thevalues.Note that the applicants may not have a user ID that is authorized to access asecure table. Therefore, you may need to select a table for which the systemdoes not apply user ID security.You cannot use a dynamic view or a derived record as an edit table becausethey are not a reliable list of values source for the service operation.

Prompt Select the column from which you want the service operation to retrievethe values.

Descr Field Select the description you want to display to the applicant.

Administrator ModeUse this group box to control the list of values for administrators who will use your online application. Thisgroup box is available for only user defined list of values and is not available for fields that have translatevalues.



Note that administrators will have a user ID that is authorized to access a secure table if you have set up theuser ID security (Set Up SACR, Security, Secure Student Administration, User ID).

Prompt Table KeysIn some cases, the Field Name on the List of Values Setup page does not provide a list of valid valuesto choose from. This is because the field name you selected, by itself, does not give the system enoughinformation to retrieve the appropriate set of values. That is, the values for the selected field are dependent onthe values of one or more other fields.

Use this group box to indicate the fields on which your list of values depend. Also, specify the order in whichthe service operation should collect data from these fields or specify a constant (default) for these fields.

In the following example, you can see that the Prompt Table Keys group box specifies that the onlineapplication must first specify the academic career (such as undergraduate or graduate), then the admit term(such as 2011 Spring or 2011 Fall), and then the institution before displaying the academic program listof values.

Prompt Table Keys: Request XML



Select the Allow Blanks check box to indicate that the value from the dependent field can be blank. Inthe Request XML example, none of the Allow Blanks check boxes are selected because a value must bespecified by the online application for each field. This allows the service operation to return a valid list ofacademic programs. However, in the List of Values Setup page example, the Admit Type field depends on theAcademic Career field for its list of values and the Allow Blank check box has been selected for AcademicCareer. This is because the Admit Type table can store admit types for a specific career, but it can alsostore admit types for all careers.

In the following example, you can see that the Prompt Table Keys group box specifies that the serviceoperation should return to the online application a list of external organization values with a type of schoolfor a School Attended field.

Prompt Table Keys: Constant

The Prompt Table Keys group box is available for only user defined list of values. This group box is notavailable for fields that have translate values.

Excluded ValuesUse this group box if you want to exclude one or more values in a list. This group box is applicable for onlyself service users (applicants).



Refresh LOV Click to populate the Excluded Values group box with the field’s values. If youuse this choice, you can view all the valid values that the service operation willreturn for a field.

Delete All Click to remove values from the Excluded Values region.

Value Specify a value that you want to hide from the applicant user.

This group box is available for both type of fields: fields that have user defined list of values and fields thathave translate list of values.

See AlsoAAWS User’s Guide, “Configuration Hints and Tips”, List of Values

AAWS User’s Guide, List of Values Web Service Operation

Maintaining and Extending Data for Online andBatch TransactionsAccess the Entity Registry page (Set Up SACR, System Administration, Entity, Entity Registry).



Entity Registry page

Note. Refer to the “Extending AAWS” section in the AAWS Developer’s Guide for more information aboutthe Entity Registry page and how to create new entities.

You can use the Entity Registry page to not only create new entities but also to maintain existing entities.For example, you can use the page to:

• Specify that you do not want to apply a data update rule to an entity.• Change the application class that handles the entity data.• Change the staging or production table record.



The PeopleSoft system delivers entities for the admission application and constituent data records. You canuse the delivered entities as they are, modify them, or create your own.

The following main constituent entities are delivered:

• Constituent• Names• Address• Email Address• National ID

The following miscellaneous constituent entities are delivered:

• Person Data Effdt

• Person Relation Affiliation

• Person Relation Communication

• Person Relationship

• Person Relationship Salutation

• Person SA• Emergency Contact

• Emergency Phone

• Diversity• Ethnicity Detail

• Ethnic Diversity

• Disability• Citizenship• Citizenship Passport

• Visa Permit Data

• Port of Entry Data

• Publications• Languages• Licenses and Certificates

• Drivers License Type

• Drivers License

• Memberships• Work Experience

• Extracurricular Activities

• Honors & Awards• Residency• Residency Appeal



• Residency Official• Residency Self• Religious Preference• Academic Interests• Academic Interests Header• External System• External System Key• External System IDs• Student Career (Constituent)• File Attachment

The following entities related to academic information are delivered:

• Academic History• Test Score Component• Test Score• External Academic Data• External Degree• External Course Grade• External Course Communication• External Course• External Education Comment• External Academic Subject• External Academic Summary

The following entities related to application and prospect information are delivered:

• Application• Application Attachment

• Application Fee Tender

• Academic Program

• Academic Plan• Academic Sub-Plan

• Career Sequence

• Q&A Application Extension

• General Materials

• Recruiter• Prospect Career

• Prospect Plan• Prospect Program



• Prospect Recruiter• Prospect Recruiting Category• Prospect Sub-Plan• Recruitment Category• Student Career (Prospect)• Student Response

The following country-specific entities are delivered (constituent, application and student records):

• Tribal Affiliation (NZL)• Person Data (NZL)• Academic Program (NZL)• HESA Person Data (UK)• HESA Person (UK)• Academic Program (AUS)• Citizenship History (AUS)• CHESSN (AUS)• CHESSN Prior HEP (AUS)• CHESSN Year 12 (AUS)• Student Data (AUS)• Student Report (CAN)• Person Data (CAN)• External Academic Data (CAN)• Application (NLD)• Academic Program (NLD)• Student Nationalities (NLD)• Student Names (NLD)• Scholarship Data (NLD)• Student Brincode (NLD)• Higher Ed Student Data (NLD)• Student Information (NLD)• Student Education (NLD)• Student Bank Account (NLD)• Student Correspondence (NLD)• Education Subject (NLD)• Student Prior Education (NLD)• Person Data (USA)



See AlsoAAWS User’s Guide, “Configuration Hints and Tips”, Entity Registry

AAWS Developer’s Guide, “Extending AAWS”

AAWS Developer’s Guide, “Developer’s Reference”

Creating a Unit TestUnit tests are small focused tests that academic institutions can use to ensure that each unit of code in an entityworks properly. This is done to find errors in the smallest segments of code during development and allowthem to be fixed early, resulting in higher quality code.

Because the Entity Registry component is highly extensible, the system integrates unit testing with the EntityRegistry, by delivering a unit test framework.

Coding a Unit TestEach unit test must extend the class TestBase.

There are three methods that the unit test can override in TestBase.

• Setup(): Is the first method that your unit test must call. This method should be used to set up theenvironment for the test. If environment setup is not required, the unit test does not have to implementthis method.

• Run(): Is the main testing method. A unit test must run all the code relevant to executing the test in thismethod. If the test fails, the property status should equal the property FAILED. If the test runs successfully,the property status should be set to PASSED. This method must be overridden.

• Teardown(): Is the method that does the cleanup. In theory, this method should reset all the data, as ifthe test had never been run, therefore, if required the test can be run again successfully. This method isoptional, depending on your testing requirements.

The full class reference for TestBase is presented in the SCC_COMMON:Testing:TestBase application class.This application class is described later in this section.

The following code shows an example where a unit test retrieves a constituent that is based on TestBase:

import SCC_COMMON:Testing:*;

import SCC_COMMON:ENTITY:IEntity;

import SCC_SL_TRANSACTION:INTFC:Constituent;

class GetConstituent extends SCC_COMMON:Testing:TestBase

method GetConstituent();

method setup();

method teardown();

method run();

end-class;

method GetConstituent

%Super = create SCC_COMMON:Testing:TestBase("GetConstituent");

end-method;



method run

/+ Extends/implements SCC_COMMON:Testing:TestBase.Run +/

Local SCC_SL_TRANSACTION:INTFC:Constituent &constituent = create

SCC_SL_TRANSACTION:INTFC:Constituent( Null);

/*Retrieves the constituent*/

&constituent.setStageMode( True);

&constituent.EMPLID = "KU0004";

&constituent.fromProduction();

/*Prints in the message area the complete consitutent xml

for the constituent received*/

Local XmlDoc &responseDoc = CreateXmlDoc("");

Local XmlNode &rootNode =

&responseDoc.CreateDocumentElement("CONSTITUENT");

&constituent.toXmlNode(&rootNode);

%This.Msg(&responseDoc.GenFormattedXmlString());

end-method;

method setup

/+ Extends/implements SCC_COMMON:Testing:TestBase.Setup +/

end-method;

method teardown

/+ Extends/implements SCC_COMMON:Testing:TestBase.Teardown +/

end-method;

Attaching a Unit TestYou attach a unit test to a specific entity. To attach a unit test to an entity:

1. Navigate to the Entity Registry page for the entity to which you want to attach a unit test (Set UpSACR, System Administration, Entity, Entity Registry). Continuing with the previous code example, thefollowing shows that the Constituent entity is selected.



Example of the Entity Registry page for the Constituent entity

2. Click the View Unit Tests button to access the Entity Unit Tests (setup) page.

Example: Entity Unit Tests (setup) page for the Constituent entity

Active Select to allow the system to run the unit test.If you clear this check box, the system ignores the unit test.



Type Select a categorical classification of the unit test, this is mostly for description.

Application Class Select the class that you have created for the unit test. In the previous exhibitexample — Entity Unit Tests (setup) page for the Constituent entity — theMessageGenerator class is selected for the Constituent entity.

Run Unit Tests Click to run the unit test.You can add any number of unit tests on this page and click this button onceto run all the tests simultaneously.

OK Click to save this unit test setup.

The other fields on this page are similar to the Entity Unit Tests (view-only) page that is described in the nextsection “Running Entity Unit Test Cases”.

class SCC_COMMON:Testing:TestBaseThis is the base class which developers must extend in order to code their tests. The methods to be overriddenare Setup(), Run(), and Teardown(). The system always calls these methods in that order for each test class. Inthe final phase of code execution, the system attempts to call Teardown(), even when there are errors.

In addition, the system delivers helper methods for asserting various invariant conditions. The syntax is: Assert(&condition_which_must_be_true, "The expected condition was not met!"); In other words, the first argumentto Assert() is a condition which you expect to be true. The second argument is an error message to display ifthe condition is not met. The other Assert*() methods are more of syntactic sugar.

Summary:

Property Summary:

• public string FAILED• public string NOT_RUN• public string PASSED• public string status• public string UnitTestName

Constructor Summary:

Method Modifier and ReturnType Method Name and Parameters Method Description

public void TestBase(string UnitTestName_in) This is the constructor. Developersshould pass in a test name as the soleargument. For now, the system doesnot use this value.

Method Summary:



Method Modifier and ReturnType Method Name and Parameters Method Description

public void Assert(boolean isTrue, string onFail) The first argument must be a booleanexpression, which should evaluateto true. If false, the system throwsan exception to indicate that thetest failed. The system catches theexception, marks the test as havingfailed, and continues on to the nexttest.

public void AssertNumbersDiffer(number num1,number num2, string onFail)

NA

public void AssertNumbersEqual(number num1,number num2, string onFail)

NA

public void AssertStringsDiffer(string str1, stringstr2, string onFail)

NA

public void AssertStringsEqual(string str1, stringstr2, string onFail)

NA

public void Msg(string msg) NApublic void Run() This method must be overridden

to implement the actual test thatdevelopers want to write.

Warning! If you do not override thismethod, the system throws an error.

public void Setup() The first method of the test class to becalled during a run.

public void Teardown() The last method of the test class to becalled during a run. The frameworktries to call this method even after anerror. Due to inconsistent exceptionhandling by the PeopleCode runtime,a PeopleCode "catch" statement doesnot catch all exceptions, and so thesystem cannot guarantee this methodwill be run after an error. Examplesof untrappable errors include calls tothe Error() builtin, SQL errors, andPeopleCode compile errors.

Running Entity Unit Test CasesAccess the Entity Unit Tester page (Set Up SACR, System Administration, Entity, Entity Unit Tester).



Entity Unit Tester page

This component is purely for running unit tests that you associate with entities on the Entity Unit Tests (setup)page. The unit tests themselves are based on the Campus Solutions delivered unit test framework.

Note. Refer to the “Extending AAWS” section in the AAWS Developer’s Guide for more information aboutthe Entity Registry page and how to create new entities. Also, refer to previous section “Creating a Unit Test”.



First, an entity is selected. This will load the unit tests specified in the Entity Registry for that entity and allchild entities in the grid below it. Except for the entity called ‘All’, the prompt dynamically marks with an *the entities that have no parent entity. Those can be considered top level entities. ALL is a special case asit will run unit tests for all entities in the registry.

Example of an Entity Unit Tester page for a selected entity

Once an entity is selected, any unit test for that entity or any children show up. If an entity has no unittests, it will not be in the grid.

Clicking Run Unit Tests will start running unit tests entity by entity. Each time all the unit tests for an entityare completed the status is returned and the next entity is set for running. This is all done automatically.

The statuses will be set to either Passed or Failed. Passed telling you all the unit tests passed and Failedmeaning at least one unit test failed.

Warning! Once the unit tests start, wait until statuses are set for all unit tests. Changing pages and other suchactions will interrupt the unit test process.

Note. When unit tests are run from the entity registry page directly it will perform a similar process, howeverinstead of doing it on a per entity basis it will be on a per unit test basis.

To view the individual unit tests for an entity click the View Unit Tests link.

Entity Unit Tests page



Note. The fields are display only. Their setup is defined under Set Up SACR, System Administration, Entity,Entity Registry by clicking the View Unit Tests button for the desired entity.

Active Specifies if the unit test is set to active and should be run. Any unit test set tonot active will not be run.

Type A categorical classification of the unit test, this is mostly for description.

Application Class The application class of the unit test you created for this entity.

Last Run Status The status the last time this unit test was run (Passed or Failed).

Last Run Datetime The last time this unit test was run.

Details Shows the details of the unit test, including all messages output. If a unittest fails, the information provided could help you identify the reasonsof the failure.

Entity Unit Test Details page



Reviewing and Processing Staged Admission TransactionsUse the Constituent Staging and Application Transactions components to review or edit the admissionstransaction data stored in the staging tables. The staging tables are holding tables and are separate from thecore production records. Any changes you make in the components posts to the core production recordswhen the posting process is executed (real time or batch) depending on data update rules. You can use thesecomponents to review the information stored in the staging tables at any time during the Processing AdmissionTransactions business process. For example, you might prefer to look at the transaction data immediately afterthe system loads it into the staging tables or after posting. This data is no longer editable once all transactionsrelated to the constituent record have a transaction status of Posted or Cancelled.

[ Bundle 21: A new field — Created By — has been added to all the pages of the Constituent Staging andApplication Transactions components. The following note has been added to this chapter. ]

Note. The Created By field has been added to all the pages of the Constituent Staging and ApplicationTransactions components for Bundle 21. In this chapter, except for the following graphic titled Example of aCreated By field, all the other graphics for these pages have not been updated for this change.

Example of a Created By field

Correcting Admission Transaction ErrorsWhen a user saves or submits an application through AAWS or when you use File Parser to batch load anapplication, the system creates a transaction. A transaction might have an error status for the constituent(person) or the application record. For error indicators, look through both the components to find thecorresponding field and enter a valid value.

For example, suppose you selected the Manual Reconciliation option for Home Schools on the School Setuppage. If the applicant has indicated that a school of attendance is a home school and submitted the application,the Application Transactions component displays an error message.


dnair

Highlight


Example of an error message in the Application Transactions component

To resolve such an error, you can click the Education History tab, then select the valid external organizationID for the home-schooled applicant and finally click the Save button.

Posting Admission TransactionsAfter you have reviewed a transaction and corrected the errors, you can run the search/match/post process fromthe components itself by clicking the Run Search/Match/Post button. On clicking this button, you can run bothprocesses at once: to search for matching people in your database and to post the transaction according to theSearch/Match parameters you set up on the Transaction Setup component. The latter happens if Search/Matchidentifies an ID that needs to be created or updated or if the user has used a User ID already tied to an ID.In either way, the system uses the identified ID (EMPLID) to post the data. Alternatively, you can use theConstituent Staging and Application Transactions components to correct multiple transactions and then run theTransaction Management process to post the multiple transactions to the Campus Solutions database.

If you have selected the Batch option on the Transaction Setup page, the system stores the transactions instaging tables and you will need to run the Transaction Management process to run Search/Match and postthe transactions to Campus Solutions. However, if the system knows the EMPLID for the applicant, thenthe transaction is effectively treated as real time.



Before running the Transaction Management process, set up the Search/Match parameters on the TransactionManagement Process component. The Search/Match parameters that you define for the TransactionManagement process overrides the Search/Match parameters set up on the Transaction Setup component.Regardless of how the post process is run, if it encounters any problems during processing, it will assign therecord an application status of Saved Error or Submitted Error. Use the Constituent Staging and ApplicationTransactions components to review these errors.

Pages Used to Review and Process Staged AdmissionTransactions

Page Name Definition Name Navigation UsageSummary Information SCC_STG_CONST_STG • Student Admissions,

Application TransactionMgmt, ConstituentStaging, SummaryInformation

• Campus Community,Constituent TransactionMgmt, ConstituentStaging, SummaryInformation

Review the constituentstatus, and the errormessages and transactionsfor the applicant.

Run the search/match/postprocess or post thetransaction data. Manuallytrigger Search/Match toreview the list of matchingcandidates.

Constituent Details SCC_STG_CONST_DTLS • Student Admissions,Application TransactionMgmt, ConstituentStaging, ConstituentDetails

• Campus Community,Constituent TransactionMgmt, ConstituentStaging, ConstituentDetails

Review and edit theapplicant’s personalinformation in the stagingrecord. An applicant’spersonal informationincludes data such as dateof birth, national ID, andaddress.

Participation Details SCC_STG_PARTICIP • Student Admissions,Application TransactionMgmt, ConstituentStaging, ParticipationDetails

• Campus Community,Constituent TransactionMgmt, ConstituentStaging, ParticipationDetails

Review and edit theapplicant’s participationdetails in the stagingrecord. An applicant’sparticipation details mayinclude information such aswork experience and honorsand awards.

Additional Personal Info SCC_STG_ADDITION • Student Admissions,Application TransactionMgmt, ConstituentStaging, AdditionalPersonal Info

• Campus Community,Constituent TransactionMgmt, ConstituentStaging, AdditionalPersonal Info

Review and edit theapplicant’s additionalpersonal information inthe staging record. Anapplicant’s additionalpersonal information mayinclude citizenship detailsand emergency contacts.



Page Name Definition Name Navigation UsageRegional SCC_STG_REGIONAL • Student Admissions,

Application TransactionMgmt, ConstituentStaging, Regional

• Campus Community,Constituent TransactionMgmt, ConstituentStaging, Regional

Review and edit theapplicant’s regionalinformation in the stagingrecord.

Application Data SAD_APPL_STG • Student Admissions,Application TransactionMgmt, ApplicationTransactions, ApplicationData

• Click the <TransactionName> link on theSummary Informationpage.

Review the error messagespertaining to the applicationin the staging record.

In addition, review and editthe application program dataand academic plan data. Youcan also review and editthe additional informationregarding the application,such as application center,application fees, andrecruiter assigned to theapplication.

Education History SCC_EXT_ACAD_DATA • Student Admissions,Application TransactionMgmt, ApplicationTransactions, EducationHistory

• Click the <TransactionName> link on theSummary Informationpage and then click theEducation History tab.

Review and edit theeducation history pertainingto the application in thestaging record. Educationhistory includes informationsuch as schools attended anddegrees that are in progressor completed.

Additional Academic Info SAD_STG_TEST • Student Admissions,Application TransactionMgmt, ApplicationTransactions, AdditionalAcademic Info

• Click the <TransactionName> link on theSummary Informationpage and then click theAdditional AcademicInfo tab.

Review and edit theadditional academicinformation pertaining to theapplication in the stagingrecord. Additional academicinformation includes testresults and academicinterests.



Page Name Definition Name Navigation UsageSupplemental Information SAD_GENM_ATTACH • Student Admissions,

Application TransactionMgmt, ApplicationTransactions,Supplemental Information

• Click the <TransactionName> link on theSummary Informationpage and then click theSupplemental Informationtab.

Review and edit thesupplemental informationpertaining to the applicationin the staging record.Supplemental informationincludes general materialsand file attachments.

Application Regional SAD_APL_REG_STG • Student Admissions,Application TransactionMgmt, ApplicationTransactions, ApplicationRegional

• Click the <TransactionName> link on theSummary Informationpage and then click theApplication Regional tab.

Review and edit thecountry-specific datapertaining to the applicationin the staging record.

Selection Parameters SCC_SL_SMP Student Admissions,Application TransactionMgmt, TransactionManagement Process,Selection Parameters

Campus Community,Constituent TransactionMgmt, TransactionManagement Process,Selection Parameters

Enter selection parametersfor running the TransactionManagement process. Youcan run search match andpost for saved and submittedtransactions in the stagingrecords. Also, you canprocess a transaction for asingle person, all persons, oruse Population Selectionto select the persons in thestaging records.

Before you post the data,set up the Search/Matchparameters on theSearch/Match Parameterspage.

Search/Match Parameters SCC_SL_SMP_PARM Student Admissions,Application TransactionMgmt, TransactionManagement Process,Search/Match Parameters

Campus Community,Constituent TransactionMgmt, TransactionManagement Process,Search/Match Parameters

Set up your Search/Matchparameters for theTransaction Managementprocess. These are the rulesthat determine what the postprocess should do with thestaging record after theSearch/Match process iscomplete.



Reviewing Applicant Error Messages and TransactionsAccess the Summary Information page (Student Admissions, Application Transaction Mgmt, ConstituentStaging, Summary Information).

Summary Information page

Constituent Status Indicates the status of the constituent data in the staging table. This statuscontrols when a transaction can be posted. Refer to the below table in thesub section titled Constituent Statuses for details.

Note. Do not modify the delivered values in any way. Any modifications tothese values require a substantial programming effort.

ID Indicates the ID that will be used to post a transaction. ID value is determinedeither by the User ID that performs the transaction (in the case of returningusers), the Search/Match process, or manually by an administrator if the searchfor duplicates was performed individually.Note that a returning user is a user ID that already has an EMPLID.

Run Search/Match/Post Click to run Search/Match and if an ID is identified, post the constituent withthe transactions that are listed in the Related Transactions section.If Search/Match has already been run, an ID is identified and the transactionstatus is Submitted, the system displays the Post Transaction Data buttoninstead of the Run Search/Match/Post button.If all the transactions in the Related Transactions have a status of Posted thesystem disables the Post Transaction Data button.

<Transaction Name> Click to access the Application Transactions component and view theadmission application staged data. You can access the ApplicationTransactions component only if you have access to the application centerassociated with the application transaction.

Note. The link name, by default, matches the name given to the transactionon the Transaction Setup component. In the preceding exhibit example —Summary Information page — you can see that the link is Application Databecause for the ADMISSIONS_APPLICATION transaction the TransactionName is set to Application Data on the Transaction Setup component.



Batch Trans (BatchTransaction)

Indicates whether this transaction is set as an online transaction or not on theTransaction Setup page. For example, if the transaction is generated becausean applicant has saved an application through AAWS, the system does notselect this check box. If the transaction is generated because you have loadedan application using the File Parser utility, the system selects this check box.

Search/Match Results Click to run Search/Match and manually review the matching candidates. Ifmatches are found, the system displays the Integrated Search Results pageafter Search/Match has run. The Search/Match function uses the SearchParameter and the Search Result Code values related to the transaction,for which you clicked the Search/Match Results link. You specify theSearch Parameter and the Search Result Code values for a transaction onthe Transaction Setup component.

Note. The system does not display the Search/Match Results link for anew user registration transaction.

Set To Update ID Click this button if inadvertently you or the system has created or updatedthe constituent data to a wrong ID and you want to repost the data withthe correct ID.The button appears only when Constituent Status = New ID Created or IDUpdated and none of the transactions listed in the Related Transactions gridhave a status = Posted (other than the new user registration transaction calledADMISSIONS_REGISTRATION).

Note. If a transaction was posted with the wrong ID, you need to first unpostthe transaction, delete the created transaction and then you will be able tosee the Set to Update ID button and change the ID. You unpost a transactionfrom the Application Transactions component.

The page displays the Constituent Errors section if the constituent status is Error.

Application Center SecurityThere are two ways to access the admission application transactions:

• Campus Community menu path navigation (Campus Community, Constituent Transaction Mgmt,Constituent Staging)

• Student Admissions menu path navigation (Student Admissions, Application Transaction Mgmt,Constituent Staging)

If you use the Campus Community menu path navigation and if your user ID is not associated with aparticular application center, you cannot access the application data associated with that application center.However, you can see how many applications exist for an applicant. In the following example, a user cansee there is one application for the constituent. However, the user cannot view the application data becausethe <Transaction Name> link is disabled. The system has disabled the link because the user does not haveaccess to the application center.



Application Data link disabled for a user who does not have application center access

If you use the Student Admissions menu path navigation and if your user ID is not associated with a particularapplication center, you cannot see how many applications associated with the application center exist. Also,you cannot view the application data associated with the application center. Therefore, the system strictlyenforces the application center security for Student Admissions menu as compared to Campus Communitymenu where the security is not enforced. In the following example, a user cannot see whether there is anapplication transaction for the constituent because the user does not have access to the application center.



Hidden search results for a user who does not have the application center access

See PeopleSoft Enterprise Campus Solutions 9.0 Application Fundamentals PeopleBook - Update 1, “SecuringRecruiting and Admissions”, Setting Security for Application Centers

Constituent StatusesThe following table describes the various constituent statuses:

ConstituentStatus Description How Status is Set

Loaded This status indicates that the system has loaded the data into thestaging records and has not run Search/Match.

Set by the system ifSearch/Match has not runor after an administratorcorrects an error.




New ID Created This status indicates that the system has run Search/Match and hascreated a new Employee ID for the staging record.

The system assigns this status to a record when it adds a newEmployee ID. It adds a new Employee ID when the Search/Matchsettings for the transaction determine that the record is new. Thesystem also assigns this status to a record when you manually setthe constituent status to Add New ID and then click the Run SearchMatch Post button or run the TransactionManagement process.

The system can assign this status at any time during the processdepending on how the transactions are set up. If you have selectedthe real time option on the Transaction Setup page, the status assignsthis status when the user saves or submits the admission application.

Set by the system.

ID Updated This status indicates that the system has run Search/Match andhas found an existing Employee ID for the staging record or thetransaction has been processed for a returning user where theEmployee ID is known for the user.

The system assigns this status to a record when it updates constituentdata for an existing Employee ID. It updates an existing EmployeeID when the Search/Match settings for the transaction determinethat a matching record exists or if a returning user saves or submitsa subsequent transaction. This can be done at any time during theprocess depending on how the transactions are set up. If the processis real time, it will be done at the point the user either saves orsubmits their application.

Set by the system.

Suspended This status indicates that the system has run Search/Match and hassuspended the staging record for your review.

The system suspends a record from further processing becausepossible matches have been found based on the Search/Matchsettings for the transaction.

If previously you had changed the status from suspended to anyother status, you can manually change the status back to suspended(depending on whether the constituent data has been posted to theproduction record).

Set by the system.

Set manually.

Ignore This status indicates that the system has run Search/Match and theSearch/Match parameters setup suggests you to ignore the stagingrecord.

Processing of the record will not continue while this status is set. Youcan also manually assign this status if you want the system to ignorethe staging record for further processing.

Set by the system.

Set manually.




Error This status indicates that the system has encountered a problem whenprocessing the record.

The system can assign this status to a staging record when itencounters a problem during data validation, when runningSearch/Match, or when the data is being posted.

The system displays the error message on the Summary Informationpage. You must resolve the error and save the record. The systemdoes not allow you to manually change from Error status to anotherstatus. When you resolve an error and save the record, the statusautomatically changes to Loaded, which indicates that you need tostart the processing again by running the post process again (whetherit is done by clicking the Run Search/Match/Post button or the PostTransaction Data button or by running the TransactionManagementprocess). Notice that if an ID was already identified, the post processwill use it to revalidate and to post the data.

Set by the system.

Add New ID This status indicates that you have determined that the constituentshould be added as a new person.

You can assign this status when you have determined that the stagingrecord should be added with a new Employee ID.

Set manually.

Update ID This status indicates that you have determined that an existingconstituent record should be updated with the staging record.

You can use the Search/Match results or the ID field to choose theEmployee ID whose record you want to update. After assigning thisstatus and choosing an Employee ID, you can click the Run SearchMatch Post button or run the Transaction Management process toupdate the existing record.

Set manually.

Cancelled This status indicates that you have determined the transaction isincomplete, duplicate or should not be processed further. You cannotdelete a transaction but you can cancel a constituent transaction. Nofurther data updates by the user or the administrative user can beperformed on a cancelled row. The Transaction Management processignores the cancelled rows.

Note. Cancelling a constituent implies that none of the transactionstied to it can be updated or processed further.

Also if your user interface for the online transaction is configuredappropriately, this status can be used when an end user has manuallycancelled the transaction (for instance closed the browser window)before saving or submitting an admission application.

Set by the system.

Set manually.

Reviewing Applicant DetailsAccess the Constituent Details page (Student Admissions, Application Transaction Mgmt, ConstituentStaging, Constituent Details).



Constituent Details page (1 of 2)

Constituent Details page (2 of 2)



Reviewing Applicant Participation DetailsAccess the Participation Details page (Student Admissions, Application Transaction Mgmt, ConstituentStaging, Participation Details).

Participation Details page (1 of 3)




Reviewing Applicant’s Additional Personal InformationAccess the Additional Personal Info page (Student Admissions, Application Transaction Mgmt, ConstituentStaging, Additional Personal Info).



Additional Personal Info page (1 of 3)



Reviewing Applicant’s Regional InformationAccess the Regional page (Student Admissions, Application Transaction Mgmt, Constituent Staging,Regional).

Regional page (1 of 2)



Regional page (2 of 2)

Reviewing Application Error Messages and Application DataAccess the Application Data page (Student Admissions, Application Transaction Mgmt, ApplicationTransactions, Application Data).



Application Data page (1 of 2)



Application Data page (2 of 2)

Set Status to Submitted This button only appears if the application status is Posted.If you have inadvertently posted the transaction data to a wrong ID, click theSet Status to Submitted button. On clicking the button, the system sets theapplication status back to submitted. For example, you may notice that anapplication was posted to a new ID but you should have created the applicationfor an existing ID. To repost the application to the existing ID, performthe following steps:

1. Run the Application Delete process to delete the application that you haveposted to the wrong ID so that you do not maintain duplicate applicationsin the system.

2. Click the Set Status to Submitted button and save the record.3. Click the Set to Update ID button on the Constituent Staging component

and select the existing ID.4. Click the Run Search/Match/Post button to post the application.

The following table describes the application statuses:



Application Status DescriptionSaved This status indicates that system has saved the admission application to the staging

records and the application is not ready to be processed.

The system automatically assigns this status when the online application callsthe Save Application service operation.

You can also manually set this status if you want to indicate that the application isnot ready for processing.

When setting up the File Mapping Definition, you can define the default value thatFile Parser should assign as the Application Status.

Submitted This status indicates that system has submitted the admission application to thestaging records and the application is ready to be processed.

The system automatically assigns this status to an application when the onlineapplication calls the Submit Application service operation.

You can manually set this status if you want to indicate that the application isready for processing. You cannot post Saved transactions; only transactions withSubmitted status can be posted.

When setting up the File Mapping Definition, you can define the default value thatFile Parser should assign as the Application Status.

Saved Error This status indicates that the system encountered problems when saving anadmission application. You must resolve these errors before the admissionapplication can be posted.

You cannot manually change this status. When you resolve the error and save thestaging record, the system automatically sets the status back to Saved.

Submit Error This status indicates that the system encountered problems when submittingan admission application. You must resolve these errors before the admissionapplication can be posted.

You cannot manually change this status. When you resolve the error and save thestaging record, the system automatically sets the status back to Submitted.

Pending This status indicates that manual reconciliation is required for some data elementwhich is not necessarily an error. For example, when manual reconciliation isrequired for application fee waiver requests, the status is set to Pending and theapplication fee status is set toWaiver. You can manually change this status.

Posted This status indicates that the system has posted the data. The system runs theposting process when you click the Post Transaction Data button or the RunSearch/Match/Post button, or when you run the Transaction Management process.

The setup of the AAWS Application Fee and Waiver Processing group box on the Application Center Tablepage controls how an online application fee payment or waiver is processed.

See: PeopleSoft Enterprise Recruiting and Admissions 9.0 PeopleBook, Building Your Recruiting Structure,Setting Up Your Recruiting Structure, Setting Up Application Processing Centers

For information about how the payment is collected through third party hosted payment processing usingStudent Financials web services, refer to the following:

See: PeopleSoft Enterprise Student Financials 9.0 PeopleBook, Using Student Financials Web Services forHosted ePayment Transactions

See: PeopleSoft Enterprise Campus Solutions 9.0 Admission Applications Web Services Developer’s Guideon My Oracle Support



See: PeopleSoft Enterprise Campus Solutions 9.0 Admission Applications Web Services User’s Guide onMy Oracle Support

When payment is authorized, the Amount Sent to GL field is updated in the Application Transactions stagingcomponent (the field is not visible on the page) and is carried through to the core production ApplicationMaintenance component (Application Items page). The Generate Direct to GL process uses the AmountSent to GL value.

See: PeopleSoft Enterprise Student Financials 9.0 PeopleBook, Using GL Interface Processing, GeneratingDirect to GL Entries

The following documentation discusses how the Application Data staging page fields are updated when anonline application fee or waiver is processed—based on the setup of the AAWS Application Fee and WaiverProcessing group box on the Application Center Table page.

The staging field SAD_APL_DAT_STG.APP_FEE_STATUS is not visible on the Application Data stagingpage.

Processing Application Fees When Waiver Request is Not AllowedSCENARIO 1

The Application Center Table setup is:

• An application fee is required.• Payment is required when the application is submitted.• Waiver request is not allowed.

When an applicant has completed all the required data for the online application and is ready to submitthe application, the applicant clicks a payment button which triggers the AAWS Submit web service(SAD_SUBMITAPPL). The web service calls the Application Fee Calculation API which calculates the feeand returns the amount and currency to the external user interface which displays the fee to the applicant.

The staging field SAD_APL_DAT_STG.APP_FEE_STATUS is set to Calculated.

When the applicant successfully makes a payment, the application is submitted. TheSAD_APL_DAT_STG.APPL_FEE_STATUS field is set to Received.

The field values are carried through to the core production Application Maintenance component:ADM_APPL_DATA.APP_FEE_STATUS is set to Calculated and ADM_APPL_DATA.APPL_FEE_STATUSis set to Received.

If the applicant does not successfully complete the payment process, the application remains in a saved status.

SCENARIO 2


• An application fee is required.

• Pay later is allowed.

• Waiver request is not allowed.

If the applicant selects to pay now, the process is the same as scenario 1.

If the applicant selects to pay later, SAD_APL_DAT_STG.APP_FEE_STATUS is set to Calculated andSAD_APL_DAT_STG.APPL_FEE_STATUS is set to Defer.



These values are carried through to core production: ADM_APPL_DATA.APP_FEE_STATUS is set toCalculated and ADM_APPL_DATA.APPL_FEE_STATUS is set to Deferred.

The Admissions office must follow up on fee payment. No other processing occurs in AAWS.

Processing Application Fee Waivers in StagingSCENARIO 3


• An application fee is required.• Payment is required when the application is submitted OR pay later is allowed.• Waiver request is allowed.• Manual reconciliation is required.

If the applicant completes the payment, the process is the same as scenario 1.

If the applicant requests a waiver, the applicant indicates the waiver basis (if required based on setup onApplication Center Table page) and provides supporting documentation (optional - may be submitted byuploading an attachment or at a later time) and submits the application.

Because Require Manual Reconciliation is selected as the Application Fee Waiver Process option on theApplication Center Table page, then when the applicant submits the application, the staging fields are setas follows:

• SAD_APL_DAT_STG. SAD_APPL_STS is set to Pending.• SAD_APL_DAT_STG.APPL_FEE_STATUS is set to Waiver.• SAD_APL_DAT_STG.WAIVED_AMT is set to blank.• SAD_APL_DAT_STG.APP_FEE_STATUS is set to Pending.

The administrator reviews supporting documentation (Supplemental Information page) and grants or deniesthe waiver.

If the waiver is granted, the staging fields are updated as follows:

• The administrator changes the staging Application Fee Status value to Waived.• Programmatically, SAD_APL_DAT_STG. SAD_APPL_STS is set to Submitted.• SAD_APL_DAT_STG.WAIVED_AMT shows the waiver amount.• SAD_APL_DAT_STG.APP_FEE_STATUS is set to Calculated.

These values are carried through to core production Admissions tables:

• On the Application Data - Application Fees page, the Fee Status value is Waived, the Waive Amount valueappears, and the Waiver Basis Code value appears based on the value in the related staging field.

• On the Application Data page, the value in the Status field in the Application Fee Information groupbox is Calculated.

If the waiver is denied, the administrator sets the Application Fee Status to Pending and the ApplicationStatus is automatically set to Saved. The administrator must manually notify the applicant that the waiverrequest is denied.



Processing Application Fee Waivers in Core AdmissionsSCENARIO 4


• An application fee is required.• Payment is required when the application is submitted OR pay later is allowed.• Waiver request is allowed.• Application can be posted to core production before waiver request is determined.

If the applicant completes the payment, the process is the same as scenario 1.

If the applicant selects to pay later, the process is the same as scenario 2. The Admissions office must followup on fee payment or waiver. No other processing occurs in AAWS.

If the applicant requests a waiver, the applicant indicates the waiver basis (if required based on setup onApplication Center Table page) and provides supporting documentation (optional - may be submitted byuploading an attachment or at a later time) and submits the application.

If Allow to Post is selected as the Application Fee Waiver Process option and the App Fee Status Waivedoption is selected on the Application Center Table page, then when the applicant submits the application, thestaging fields are set as follows:

• SAD_APL_DAT_STG.APPL_FEE_STATUS is set to Waived.• SAD_APL_DAT_STG.WAIVED_AMT is set to blank.• SAD_APL_DAT_STG.APP_FEE_STATUS is set to Calculated.


• On the Application Data - Application Fees page, the Fee Status value isWaived, the Waive Amount valueis blank and the Waiver Basis Code value appears based on the value in the related staging field.

• On the Application Data page, the value in the Status field in the Application Fee Information groupbox is Calculated.

The App Fee Status Waived option could be used by schools who allow waivers but automatically grant thewaiver without review or assessment.

If Allow to Post is selected as the Application Fee Waiver Process option and the App Fee Status WaiverRequest option is selected on the Application Center Table page, then when the applicant submits theapplication, the staging fields are set as follows:

• SAD_APL_DAT_STG.APPL_FEE_STATUS is set to Waiver.

• SAD_APL_DAT_STG.WAIVED_AMT is set to blank.

• SAD_APL_DAT_STG.APP_FEE_STATUS is set to Pending.


• On the Application Data - Application Fees page, the Fee Status value isWaiver, the Waive Amount valueis blank and the Waiver Basis Code value appears based on the value in the related staging field.

• On the Application Data page, the value in the Status field in the Application Fee Information groupbox is Pending.

Waiver requests must be assessed using the core production Application Maintenance component.



Query adm_appl_data.appl_fee_status to find the applicants with waiver requests.

Reviewing Applicant’s Education HistoryAccess the Education History page (Student Admissions, Application Transaction Mgmt, ApplicationTransactions, Education History).

Education History page (1 of 3)



Reviewing Additional Academic InformationAccess the Additional Academic Info page (Student Admissions, Application Transaction Mgmt, ApplicationTransactions, Additional Academic Info).

Additional Academic Info page

Reviewing General Materials and AttachmentsAccess the Supplemental Information page (Student Admissions, Application Transaction Mgmt, ApplicationTransactions, Supplemental Information).



Supplemental Information page

Reviewing Application Regional InformationAccess the Application Regional page (Student Admissions, Application Transaction Mgmt, ApplicationTransactions, Application Regional).



Application Regional page: Australia

The system displays this page only if the country-specific options are selected on the SA Features andAcademic Institution 6 pages.

See AlsoPeopleSoft Enterprise Campus Solutions 9.0 Application Fundamentals PeopleBook - Update 1, “ReviewingInstallation Setup and System Defaults”, Selecting Student Administration Installation Options

PeopleSoft Enterprise Campus Solutions 9.0 Application Fundamentals PeopleBook - Update 1, "DesigningYour Academic Structure," (AUS, CAN, GBR, NZL, NLD) Activating Other Student Administration Features

Updating and Posting Transactions in BatchAccess the Selection Parameters page (Student Admissions, Application Transaction Mgmt, TransactionManagement Process, Selection Parameters).



Selection Parameters page

Use this functionality to process temporary constituent IDs stored inside the constituent and the transactionstaging tables. You can process all IDs, just one at a time or use Population Selection to select staged IDsmeeting custom criteria. You can decide to only process the saved transactions, the submitted transactions or acombination of both. The process allows you to change the transaction (application) status from Saved toSubmitted, run Search/Match and once an EMPLID is identified, post the constituent and transaction data toproduction tables. The Transaction Management process does not process IDs with a Constituent Status set toCancelled or for which their transaction is already Posted. It also does not run the Search/Match process whenan EMPLID is already identified or the Constituent Status is set to Ignored, Suspended, or Error. When anID is set to be suspended, only manual intervention performed from the Constituent Summary page can bedone to reset the status to something else after evaluation. For instance, a self-service user submits an onlineapplication. Search/Match found one exact match and the transaction was set up to suspend the constituentif this condition is encountered. The suspended record requires manual intervention by the administrativeuser to validate the matching candidate found should be updated or not.

Transaction Name Select the transaction for which you want to process the constituent and theirtransactions (applications).

ID Selection

ID Selection Select one of these values:

• One Person Temporary ID: Select to run the process for a single person(constituent) in the staging record who is associated with the selectedtransaction name.

• All Person Temporary IDs: Select to run the process for all the persons inthe staging record who are associated with the selected transaction name.



• Population Selection: Select if you want to use the population selectionprocess for selecting the temporary IDs who are associated with theselected transaction name.

Temporary ID Available only when the ID Selection is One Person Temporary ID. You mustenter the specific temporary constituent ID to process here.

Process SubmittedTransactions

Select if you want the system to process transactions that have an applicationstatus of Submitted. When you select this option, the Submitted Transactionsbox appears.

Process Saved Transactions Select if you want the system to process transactions that have an applicationstatus of Saved. When you select this option, the Saved Transactions boxappears.The system posts only submitted transactions to the database.

Submitted TransactionsThis group box appears only when the Process Submitted Transactions option is selected.

Run Search Match Select to run Search/Match for the Submitted transactions.

Post Transaction Data Select to post the Submitted transactions.

Note. When processing submitted transactions, the component forces you to select both check boxes. This isto ensure that you are not introducing duplicates into your database. If an ID is already identified, the processskips Search/Match and proceeds to validate and post the transaction data.

Saved TransactionsThis group box appears only when the Process Saved Transactions option is selected.

Update Status to Submitted Select to change the application status from Saved to Submitted.

Run Search Match Select to run Search/Match for the saved transactions. If the process identifiesthat a new ID needs to be created or an existing ID needs to be updated, theconstituent data is posted.When an EMPLID is already known to the system, Search/Match is notinvoked by the process.

Post Transaction Data Select to post the transactions (applications). Only submitted transactions forwhich you have run Search/Match can be posted. Therefore, to be able toselect this check box, you must select the Update Status to Submitted and theRun Search Match check boxes. If you select all the three check boxes, theTransaction Management process will first change the status to Submitted, thenit runs Search/Match and finally depending on the Search/Match parametersit posts the transactions.

Population SelectionThis group box appears only when the ID Selection of Population Selection is selected.



Population selection is a method for selecting the IDs to process for a specific transaction. Selection tools areavailable based on the selection tools that your institution selected in the setup of the Population Selectionprocess for the Transaction Management process and on your user security. Fields in the group box appearbased on the selection tool that you select. If your institution uses a specific delivered selection tool (PS Query,Equation Engine equation, or external file) to identify IDs for a specific transaction, you must use it.

See PeopleSoft Enterprise Campus Community Fundamentals 9.0 PeopleBook, Using the Population SelectionProcess

Specifying Search/Match Parameters for Batch ProcessingAccess the Search/Match Parameters page (Student Admissions, Application Transaction Mgmt, TransactionManagement Process, Search/Match Parameters).

Search/Match Parameters page

Use this page to set up your Search/Match parameters. These are the rules that determine what the postprocess should do with the staging record after the Search/Match process is complete. The fields on this pageare similar to the Search/Match Setup page (Set Up SACR, System Administration, Utilities, ConstituentTransaction Mgmt, Transaction Setup, Search/Match Setup).


oracle’s peoplesoft 9.0 recruiting and admissions ... · pdf fileoracle’s...

Documents