Oracle s PeopleSoft 9.0 Recruiting and Admissions: Managing PeopleSoft Admission Transactions

Transcription

1 Oracle s PeopleSoft 9.0 Recruiting and Admissions: Managing PeopleSoft Admission Transactions April 2011

2 9.0 Oracle s PeopleSoft 9.0 Recruiting and Admissions: Managing PeopleSoft Admission Transactions SKU lsad and lssr doclet Copyright 2011, Oracle and/or its affiliates. All rights reserved. Trademark Notice Oracle is a registered trademark of Oracle Corporation and/or its affiliates. Other names may be trademarks of their respective owners. License Restrictions Warranty/Consequential Damages Disclaimer This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited. Warranty Disclaimer The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing. Restricted Rights Notice If this software or related documentation is delivered to the U.S. Government or anyone licensing it on behalf of the U.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 customers are commercial computer software or commercial technical data pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, the use, duplication, disclosure, modification, and adaptation 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 , Commercial Computer Software License (December 2007). Oracle USA, Inc., 500 Oracle Parkway, Redwood City, CA Hazardous Applications Notice This software is developed for general use in a variety of information management applications. It is not developed or intended for use in any inherently dangerous applications, including applications which may create a risk of personal injury. If you use this software in dangerous applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy and other measures to ensure the safe use of this software. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software in dangerous applications. Third Party Content, Products, and Services Disclaimer This software and documentation may provide access to or information on content, products and services from third parties. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third party content, products and services. Oracle Corporation and its affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use of third party content, products or services.

3 Contents Chapter 1 Managing PeopleSoft Admission Transactions Admission Applications Web Services (AAWS)...1 Prerequisites...2 External Search/Match and AAWS...2 Using Applicant and Administrator Modes for AAWS...2 Bulk Loading of Applications Using File Parser CRM for Higher Ed EIPs and Admission Transactions...4 Setting Up Admission Transactions...4 Pages Used to Set Up Admission Transactions...6 Setting Up Counters...9 Defining a Transaction...9 Defining the Search/Match Criteria...19 Defining Data Update Rules for Batch and Online Application Transactions...21 Setting Up Affiliation Overrides for a Data Update Rule...27 Mapping Online Application Transactions to Academic Careers...28 Setting Up Application Defaults for Batch and Online Application Transactions...29 Setting Up Prospect Creation Rules and Defaults for Batch and Online Application Transactions...32 Setting Up Home or Unlisted Schools for Online Application Transactions...34 Setting Up List of Values for Online Applications...36 Maintaining and Extending Data for Online and Batch Transactions...41 Creating a Unit Test...46 Running Entity Unit Test Cases...50 Reviewing and Processing Staged Admission Transactions Pages Used to Review and Process Staged Admission Transactions...56 Reviewing Applicant Error Messages and Transactions...59 Reviewing Applicant Details...64 Reviewing Applicant Participation Details...66 Reviewing Applicant s Additional Personal Information...68 Reviewing Applicant s Regional Information...71 Reviewing Application Error Messages and Application Data...72 Reviewing Applicant s Education History...79 Reviewing Additional Academic Information...81 Reviewing General Materials and Attachments...81 Copyright 1992, 2011, Oracle and/or its affiliates. All rights reserved. iii

4 Contents Reviewing Application Regional Information...82 Updating and Posting Transactions in Batch...83 Specifying Search/Match Parameters for Batch Processing iv Copyright 1992, 2011, Oracle and/or its affiliates. All rights reserved.

5 CHAPTER 1 Managing PeopleSoft Admission Transactions This PeopleBook chapter includes bundle documentation up to Bundle 21. This chapter was first released for Bundle 18 when the AAWS feature was introduced. The last release of the chapter was for Additional Features January AAWS Application Fee (Bundle 20). You can find the Bundle 21 documentation updates in this chapter by searching 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 the Campus 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" chapter in the PeopleSoft Enterprise Recruiting and Admissions 9.0 PeopleBook is no longer supported. Oracle expects 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

6 Managing PeopleSoft Admission Transactions Chapter 1 See Also AAWS User s Guide AAWS Developer s Guide Enterprise PeopleTools PeopleBook: Integration Broker Prerequisites Complete 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 AAWS If you want the system to search for duplicate records in an external system when a user submits an online application through AAWS, ensure that the CWS External Search/Match is set up. See Also PeopleSoft Enterprise Campus Community Fundamentals 9.0 PeopleBook - Update 1, "Setting Up Search/Match" PeopleSoft Enterprise Campus Community Fundamentals 9.0 PeopleBook - Update 1, "SettingUpExternal Search/Match" Using Applicant and Administrator Modes for AAWS The Applicant mode is also known as the Self Service mode. In this mode, an applicant creates and submits an admission application through AAWS. In the Administrator mode, the administrative user creates and submits an application on behalf of an applicant. The administrator may create the application for an existing EMPLID (if the administrator knows the 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 can view 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 an application 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.

7 Chapter 1 Managing PeopleSoft Admission Transactions In both modes, the system uses the Search/Match setup to determine which application records it should load into your database as new records, which records it should append to existing records in your database, which records 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, the other administrator can use the Application Transactions staging component to update the application status to submitted and post the application. In the Administrator mode, the Get Applications service call returns only in-progress applications, that is, applications which have not been posted or cancelled. It is optional for an administrator to provide an EMPLID for a Get Applications call. If the administrator does not provide an applicant s EMPLID, the system returns 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 Solutions for 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 system exchange through AAWS. See Also PeopleSoft Enterprise Campus Solutions 9.0 Application Fundamentals PeopleBook, Securing Recruiting and Admissions PeopleSoft Enterprise Campus Solutions 9.0 Application Fundamentals PeopleBook, Securing Your Academic Institution Bulk Loading of Applications Using File Parser You 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 Also AAWS Developer s Guide Updated "Using the File Parser Process" Campus Community PeopleBook chapter. Copyright 1992, 2011, Oracle and/or its affiliates. All rights reserved. 3

8 Managing PeopleSoft Admission Transactions Chapter 1 CRM for Higher Ed EIPs and Admission Transactions Enterprise Integration Points (EIPs) enable your institution to exchange data between CS and CRM. EIPs publish data either whenever data updating happens for the given entities of the EIPs or when the user requests data. This data can be created, updated, or deleted through various channels like components, component interfaces, and batch processes. The system publishes the following EIPs when an application that is submitted through AAWS or File Parser process 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 for a saved or posted application. You use the Prospect Setup page to indicate when (upon save or post) the system should create a prospect record. The Prospect Setup page is discussed in the Setting Up Prospect Creation Rules and Defaults section of this chapter. See Also PeopleSoft Enterprise Campus Solutions 9.0 Application Fundamentals PeopleBook - Update 1, Introducing Customer Relationship Management for Higher Education CRM for Higher Education Developer s Guide Setting Up Admission Transactions Campus Solutions generates a transaction when: An applicant or administrator uses an online application to register for a user name and password through the User Registration web service operation (online transaction). An applicant or administrator uses an online application to create, save or submit an application through AAWS (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 . Examples of application data include Academic Program, Admit Term, and Academic History. 4 Copyright 1992, 2011, Oracle and/or its affiliates. All rights reserved.

9 Chapter 1 Managing PeopleSoft Admission Transactions When a transaction is generated, the system uses Search/Match to look for constituent data in your production environment (based on the Search/Match parameters) that matches the constituent data in the transaction. Each defined transaction can have its own Search/Match setup. You can therefore determine the rules for creating a 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/Match determines that the incoming constituent record should be suspended or ignored, use the Constituent Staging and Application Transactions components to correct the admissions transaction data. You can post transactions individually or by batch to the Campus Solutions database. The Constituent Staging and Application Transactions 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 the new user registration service operation and another for the online application that a user saves or submits through the Save Application or Submit Application service operations. The following default transactions for user 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 the batch load. Warning! For new user registration, do not define a new transaction. The system uses the delivered ADMISSIONS_REGISTRATION for AAWS user registration. Do not modify the ADMISSIONS_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 a transaction and the affiliation the institution has with the constituent. For example, you may have a graduate online application rule where you want to update the constituent s home address in your database with the value from a submitted graduate application. On the other hand, you may have a graduate application load rule where you do not want to update an existing home address value when you use File Parser to load graduate applications into Campus Solutions. Additionally, you may want to override this graduate application load rule if the constituent is a prospect. The Data Update Rule Entry component allows this flexibility. The system 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 submitting an online application. Conversely, the institution might not want to allow graduate applicants to update their passport details if that data is already on the system. You can associate the two different data update rules to these 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 could be defined. In this way, you can accommodate online applications for different careers (Examples: Undergraduate, Graduate, Graduation Business) which may have different Search/Match requirements, data update rules, or intended methods of processing. It is typical for administrators to enter the admissions application data for an applicant. It is possible for an administrator to use the same online application to do so, as long as the application user interface is constructed to 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 same transaction value applied to the self service application is utilized for the institution/career combination for which the application is being created. Copyright 1992, 2011, Oracle and/or its affiliates. All rights reserved. 5

10 Managing PeopleSoft Admission Transactions Chapter 1 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 setting for the user registration transaction. The new user registration feature does not ask the user enough personal information for creating a new ID. Also, a new user may createauseridandpasswordwithoutevercoming back to fill out an online application. The information entered as part of the new user registration process is therefore 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 the Application Configuration component to map an institution and career to a transaction. The system uses this mapping 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 Grad Transaction for graduate applications. When an applicant submits an undergraduate application, the system looks 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 Transactions Page Name Definition Name Navigation Usage Counter Setup SCC_AWS_FIX_CTRS Set Up SACR, System Administration, Utilities, Constituent Transaction Mgmnt, Counter Setup Set up the max ID number for the Temporary Constituent ID. Transaction Setup SCC_TRANSAC_DTLS Set Up SACR, System Administration, Utilities, Constituent Transaction Mgmt, Transaction Setup Student Admissions, UCAS Processing, Search/Match Processing, Transaction Setup Define the transaction for an online transaction or a batch transaction. 6 Copyright 1992, 2011, Oracle and/or its affiliates. All rights reserved.

11 Chapter 1 Managing PeopleSoft Admission Transactions Page Name Definition Name Navigation Usage Search/Match Setup SCC_SEARCH_PARMS SetUpSACR,System Administration, Utilities, Constituent Transaction Mgmt, Transaction Setup, Search/MatchSetup Student Admissions, UCAS Processing, Search/Match Processing, Transaction Setup, Search/Match Setup Define the Search/Match criteria for an online transaction or for running Search/Match manually from the Constituent Staging component. Not applicable for the user registration transaction. Data Update Rule Entry SCC_DUR_ENTRY Set Up SACR, System Administration, Utilities, Constituent Transaction Mgmt, Data Update Rule Entry Affiliation Overrides page SCC_DUR_AFL_OVRD Set Up SACR, System Administration, Utilities, Constituent Transaction Mgmt, Data Update Rule Entry, Affiliation Overrides Appl Config SAD_TRANSAC_MAP Set Up SACR, Product Related, Recruiting and Admissions, Application Configuration, Application Configuration, Appl Config Application Setup SAD_APL_CNT Set Up SACR, Product Related, Recruiting and Admissions, Application Configuration, Application Configuration, Application Setup Define how the constituent data is processed for an online transaction or batch transaction. Not applicable for the user registration transaction. Overrideadataupdaterule based on the affiliation the constituent has with the academic institution. Not applicable for the user registration transaction. Map online application transactions to academic careers. Not applicable for user registration. Define how the system should assign an application center and optionally assign 3Cs to anapplicationby defining which Event ID should be used in the processing. The system uses this setup when you load applications in batch or when the user saves or submits an application through AAWS. Not applicable for the user registration transaction. Copyright 1992, 2011, Oracle and/or its affiliates. All rights reserved. 7

12 Managing PeopleSoft Admission Transactions Chapter 1 Page Name Definition Name Navigation Usage Prospect Setup SAD_PRS_SETUP Set Up SACR, Product Related, Recruiting and Admissions, Application Configuration, Application Configuration, Prospect Setup Define how the system should create a prospect record, and if a prospect record is created, how to assign default values to the prospect record. The system uses this setup when you process applications in batch or when the user saves or submits an application through AAWS. Not applicable for the user registration transaction. School Setup SAD_AWS_SCH_DFL Set Up SACR,Product Related, Recruiting and Admissions, Application Configuration, Application Configuration, School Setup Define how the system should process unlisted or home schools. The system uses this setup when you load applications in batch or when the user saves or submits an application through AAWS. Not applicable for the user registration transaction. List of Values Setup SCC_SL_LOV Set Up SACR, Product Related, Recruiting and Admissions, Application Configuration, List of Values Entity Registry SCC_ENTITY_REG Set Up SACR, System Administration, Entity, Entity Registry Entity Unit Tests (Setup) SCC_ENTITY_UT Click the View Unit Tests button on the Entity Registry page. Entity Unit Tester SCC_ENT_MASS_UT Set Up SACR, System Administration, Entity, Entity Unit Tester Entity Unit Tests SCC_ENTITY_UT Click the View Unit Tests link from the Entity Unit Tester page Define how the system should return the list of values for a field. The system uses this setup when the online application calls the Get List of Values service operation. Maintain and extend the data structure that represents the information collected from an online application or batch load. Attach the unit test application classes to an entity. Run all the unit tests associated with a specified entity. Unit tests are defined on the Entity Unit Tests (Setup) page. View the unit tests tied to an entity name, the application class used and the latest run status for a specific unit test. 8 Copyright 1992, 2011, Oracle and/or its affiliates. All rights reserved.

13 Chapter 1 Managing PeopleSoft Admission Transactions Setting Up Counters Access the Counter Setup page (Set Up SACR, System Administration, Utilities, Constituent Transaction Mgmnt, Counter Setup). Counter Setup page The field on this page is automatically incremented by one by default when using the Constituent Transaction Manager functionality. Set the last used number so that automatic numbering does not create numbers that already exist in the data. Temp Constituent ID Fix Counter Displays the last Temporary Constituent ID assigned. A Temp Constituent ID is given when a transaction is performed from the Constituent Transaction Manager framework. See Defining a Transaction and Reviewing Applicant Error Messages and Transactions sections, for more information. Clicking this button resets the Temp Constituent ID based on the highest value of that field in the database. The field is dynamically found based on the Peopletools metadata for the record field relationships, and the max possible 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 being polluted by pre-existing data. Note. After you have begun using the Constituent Transaction Manager functionality, you can access this page to determine the last number that was incremented for the Temporary ID. Manually changing this number is practical for the initial setup, but not recommended for further changes. If the ID entered is changed to an existing number, the system will attempt to re-use the ID. Instead use the Fix Counter button. Defining a Transaction Access the Transaction Setup page (Set Up SACR, System Administration, Utilities, Constituent Transaction Mgmt, Transaction Setup). This is an example of the delivered sample online application transaction: Copyright 1992, 2011, Oracle and/or its affiliates. All rights reserved. 9

14 Managing PeopleSoft Admission Transactions Chapter 1 Transaction Setup page: Online application transaction (1 of 2) 10 Copyright 1992, 2011, Oracle and/or its affiliates. All rights reserved.

15 Chapter 1 Managing PeopleSoft Admission Transactions Transaction Setup page: Online application transaction (2 of 2) This is an example of the delivered new user registration transaction: Copyright 1992, 2011, Oracle and/or its affiliates. All rights reserved. 11

16 Managing PeopleSoft Admission Transactions Chapter 1 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: 12 Copyright 1992, 2011, Oracle and/or its affiliates. All rights reserved.

17 Chapter 1 Managing PeopleSoft Admission Transactions Transaction Setup page: File Parser batch load transaction (1 of 2) Copyright 1992, 2011, Oracle and/or its affiliates. All rights reserved. 13

18 Managing PeopleSoft Admission Transactions Chapter 1 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 Mapping Definition component. You can set this code as a default value (by default, the SCC_TRANSAC_CD field in the SCC_STG_CONSTIT record stores the transaction code). The File Parser process can also retrieve the transaction code directly from the load file (in such a case, set the mapping action to Direct from file). For more information about the File Mapping Definition component, refer to the updated Campus Community File Parser PeopleBook chapter. Transaction Transaction Status Data Update Rule Indicates the transaction code. You specify the transaction code when you add a transaction. Activate or inactivate the transaction. 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 in the Data Update Rule Entry page. Transaction Options Online Transaction New User Registration Select to indicate that the transaction is performed online by a user. For example, an online transaction occurs when an applicant saves or submits an admission application through AAWS. Clear this check box to indicate that the transaction is performed offline by a user. For example, an offline transaction occurs when you use File Parser to load applications from a text file. Select to indicate that the transaction is used to perform registration and authentication of a new user. If you select this check box, the system hides the Search/Match Setup tab and the Transaction Data Launch View group box, because they are not applicable for a new user registration transaction. 14 Copyright 1992, 2011, Oracle and/or its affiliates. All rights reserved.

19 Chapter 1 Managing PeopleSoft Admission Transactions Note. Your system allows for only one transaction to be set as new user registration at a time. The ADMISSIONS_REGISTRATION transaction is delivered with your system. Because of this restriction, the system hides the New User Registration check box for all other transactions. Do not modify the ADMISSIONS_REGISTRATION transaction name because the system uses the name to register a user account. Batch Realtime RunonSave Select if you do not want the system to immediately run Search/Match when the data is individually submitted. If you select this option, the system stores the submitted data in staging tables and you will need to run the Transaction Management process to run Search/Match and post the submitted data to Campus Solutions. Select to have the system immediately run Search/Match when the data is saved or submitted from an online or offline process. This check box appears if the Realtime check box is selected. Select this check box if you want the system to immediately run Search/Match when a user saves a transaction. Clear this check box if you want the system to immediately run Search/Match when 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 enough data to populate the search criteria used by Search/Match. Otherwise, Search/Match could create a new ID or update an existing record with erroneous or missing information. Transaction Handler A transaction can contain generic information about a constituent (such as names, addresses, and date of birth), as well as data specific to the transaction. For example, an admission transaction will include personal information (constituent data) and application data (transaction data). You can use the Transaction Handler group box to define how the system should handle all the transaction data. You can create your own PeopleCode application class handler for the transaction data and then associate that application class with the transaction in this group box. The following table lists the delivered transaction handler values for ADMISSIONS_APPLICATION. Do not change these values. Also use these values when defining a transaction handler for any new application transactionyoumaycreate. Root Package ID Path Application Class ID SCC_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 ID SCC_OLA TRANSACTION DefaultTransaction Copyright 1992, 2011, Oracle and/or its affiliates. All rights reserved. 15

20 Managing PeopleSoft Admission Transactions Chapter 1 Transaction Status: The system needs a field in transaction staging tables where it can store the status of the transactions. Use the Transaction Status region to indicate the record and field where the transaction status 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 for any new application transaction you may create. Record Name Field Name Date Field Name SAD_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 Name SCC_STG_CONSTIT SCC_STG_STATUS SCC_STG_STS_DT Constituent Handler You can use the Constituent Handler group box to define how the system should handle the constituent data in a transaction. You can create your own PeopleCode application class handler for the constituent data and then associate 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 modify this application class or create a new application class. The following table lists the default constituent handler values. You should always use these values when defining the constituent handler values for an online application transaction or batch load transaction. Root Package ID Path Application Class ID SCC_SL_TRANSACTION INTFC DefaultConstituent Partition Data Use the following options to indicate how the system should maintain the data in the staging tables. By Constituent By Transaction Select this option to have the system maintain only one instance of the constituent data for all transactions of the constituent (that is, One Constituent : Multiple Transactions ratio). This means that constituent data updates performed within a single transaction are visible across all other transactions. An example of the By Constituent impact: An applicant (user ID: Gina) has used an online application to register for a user account and then, later on, saved or submitted four admission applications. The system creates a total of five transactions for Gina, one transaction for user registration and four transactions for the four applications. For all the five transaction records, the system maintains a single constituent record. Gina updates her address when saving or submitting the fourth application. The system updates Gina s constituent record with the new address. Select this option to have the system maintain a separate instance of constituent data for every transaction of the constituent (that is, One Constituent : One Transaction ratio). This means that constituent data updates performed within a single transaction are not visible across all other transactions. An example of the By Transaction impact: An applicant (user ID: Jason) has used an online 16 Copyright 1992, 2011, Oracle and/or its affiliates. All rights reserved.