december 2007 release 7 response includes registration, grade reporting, billing, financial aid, and...

What can we help you achieve?

Banner General User GuideDecember 2007

Release 7.5

This documentation is proprietary information of SunGard Higher Education and is not to be copied, reproduced, lent or disposed of, nor used for any purpose other than that for which it is specifically provided without the written permission of SunGard Higher Education.

SunGard Higher Education

4 Country View RoadMalvern, Pennsylvania 19355United States of America(800) 522 - 4827

Customer Support Center website

http://connect.sungardhe.com

Distribution Services e-mail address

[email protected]

Other services

In preparing and providing this publication, SunGard Higher Education is not rendering legal, accounting, or other similar professional services. SunGard Higher Education makes no claims that an institution's use of this publication or the software for which it is provided will insure compliance with applicable federal or state laws, rules, or regulations. Each organization should seek legal, accounting and other similar professional services from competent providers of the organization's own choosing.

Trademark

Without limitation, SunGard, the SunGard logo, Banner, Campus Pipeline, Luminis, PowerCAMPUS, Matrix, and Plus are trademarks or registered trademarks of SunGard Data Systems Inc. or its subsidiaries in the U.S. and other countries. Third-party names and marks referenced herein are trademarks or registered trademarks of their respective owners.

Notice of rights

Copyright © SunGard Higher Education 1992, 2007. This document is proprietary and confidential information of SunGard Higher Education Inc. and is not to be copied, reproduced, lent, displayed or distributed, nor used for any purpose other than that for which it is specifically provided without the express written permission of SunGard Higher Education Inc.

User Guide

General

1 System Overview

Introduction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3

Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3Job Submission . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-4Population Selection . . . . . . . . . . . . . . . . . . . . . . . . . . 1-4Letter Generation. . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-4General International Management. . . . . . . . . . . . . . . . . . . 1-4System Functions/Administration . . . . . . . . . . . . . . . . . . . . 1-4Event Management . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-4General Web Management . . . . . . . . . . . . . . . . . . . . . . . 1-5General VR Management. . . . . . . . . . . . . . . . . . . . . . . . 1-5Business Rule Builder . . . . . . . . . . . . . . . . . . . . . . . . . 1-5

Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-5

2 Validation Forms

Introduction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-5

Accessing Validation Forms . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-5

Validation Forms Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-5

Forms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-13

3 Processing

Introduction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-3

Job Submission Procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-3Defining New Reports and Processes to Job Submission . . . . . . . . 3-4Setting up Parameter Defaults for Banner Reports and Processes . . . . 3-4Using Oracle*Reports . . . . . . . . . . . . . . . . . . . . . . . . . 3-10Running Banner Reports and Processes. . . . . . . . . . . . . . . . . 3-13

Population Selection Procedures . . . . . . . . . . . . . . . . . . . . . . . . 3-19Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-19

iii

Table of Contents

Building a Population Selection. . . . . . . . . . . . . . . . . . . . . 3-20Copying a Population Selection. . . . . . . . . . . . . . . . . . . . . 3-24Creating a Population with GLBDATA . . . . . . . . . . . . . . . . . 3-24Creating a Manual Population . . . . . . . . . . . . . . . . . . . . . 3-29

Letter Generation Procedures . . . . . . . . . . . . . . . . . . . . . . . . . . 3-30Defining Variables . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-30Building Letters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-43Extracting Variables with GLBLSEL . . . . . . . . . . . . . . . . . . . 3-48Generating Letters from Banner with GLRLETR . . . . . . . . . . . . . 3-52Creating a Download File with GLRLETR . . . . . . . . . . . . . . . . 3-58

System Functions/Administration Procedures . . . . . . . . . . . . . . . . . . 3-62Establishing Currency Conversions . . . . . . . . . . . . . . . . . . . 3-62Creating Bank Information . . . . . . . . . . . . . . . . . . . . . . . 3-63Updating Bank Code Records . . . . . . . . . . . . . . . . . . . . . 3-66Setting Up and Using Electronic Documents . . . . . . . . . . . . . . 3-67Setting Up Events in the Event Queue Maintenance Module . . . . . . 3-75Customizing Menus . . . . . . . . . . . . . . . . . . . . . . . . . . 3-76Managing the Data Extract Feature . . . . . . . . . . . . . . . . . . . 3-80Creating and Using QuickFlows . . . . . . . . . . . . . . . . . . . . 3-81

Event Management Procedures . . . . . . . . . . . . . . . . . . . . . . . . . 3-83Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-84Managing Buildings and Rooms . . . . . . . . . . . . . . . . . . . . 3-84Managing Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-85Managing Functions . . . . . . . . . . . . . . . . . . . . . . . . . . 3-85Managing Tasks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-86Managing Participants . . . . . . . . . . . . . . . . . . . . . . . . . 3-87

General International Management Procedures . . . . . . . . . . . . . . . . . 3-87Visa Tracking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-87Student and Exchange Visitors Information System (SEVIS) . . . . . . . 3-89

Business Rule Builder Procedures . . . . . . . . . . . . . . . . . . . . . . . . 3-103Establish the Rule Builder. . . . . . . . . . . . . . . . . . . . . . . . 3-103Building Business Actions . . . . . . . . . . . . . . . . . . . . . . . 3-104Building Auto-population Rules. . . . . . . . . . . . . . . . . . . . . 3-105

Multi-Institution Functionality (MIF) Procedures . . . . . . . . . . . . . . . . . 3-106Home and Process Contexts . . . . . . . . . . . . . . . . . . . . . . 3-107How to View the Institution Code . . . . . . . . . . . . . . . . . . . 3-107How to Switch Between Institution Codes . . . . . . . . . . . . . . . 3-108How Changing Institution Codes Impacts your Banner Session . . . . . 3-108

Basic Person Procedures. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-109Common Matching and Basic Person . . . . . . . . . . . . . . . . . . 3-110Using ID and Name Extended Search. . . . . . . . . . . . . . . . . . 3-110Entering Basic Person Information . . . . . . . . . . . . . . . . . . . 3-113Maintaining Address and Telephone Information . . . . . . . . . . . . 3-116

General Release 7.5 December 2007iv User Guide Confidential

Table of Contents

4 Job Submission

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-3

Validation Forms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-3

Related Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-3

Menu Navigation Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-4

Forms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-5

5 Population Selection

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-3

Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-3


Related Processes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-4


Forms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-6

6 Letter Generation

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-3


Related Processes and Report . . . . . . . . . . . . . . . . . . . . . . . . . . 6-4


Forms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-6

7 General International Management

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-3



Forms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-7

December 2007 General Release 7.5Confidential User Guide v

Table of Contents

8 System Functions/Administration

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-3


Related Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-5


Forms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-13

9 Event Management

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-3



Forms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-10

Forms Used by the Banner Advancement System . . . . . . . . . . . . . . . . 9-155

10 General Web Management

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-3



Forms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-5

11 Voice Response Management

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-3


Forms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-4

12 Business Rule Builder

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-3


General Release 7.5 December 2007vi User Guide Confidential

Table of Contents


Forms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-4

13 Basic Person

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-3

Forms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-4

14 Reports & Processes

Reports and Processes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-3

COBOL Processes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-52

Troubleshooting

Letter Generation Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . T-1

Population Selection Messages . . . . . . . . . . . . . . . . . . . . . . . . . T-3

Variable/Population Selection Messages. . . . . . . . . . . . . . . . . . . . . T-4

Job Submission Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . T-7

Index

December 2007 General Release 7.5Confidential User Guide vii

Table of Contents

This page intentionally left blank

General Release 7.5 December 2007viii User Guide Confidential

Chapter 1

Overview

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3

Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3

1 System OverviewJob Submission . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-4Population Selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-4Letter Generation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-4General International Management . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-4System Functions/Administration . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-4Event Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-4General Web Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-5General VR Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-5Business Rule Builder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-5

Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-5

1-1

Table of Contents


General Release 7.4 November 20061-2 User Guide Confidential

1 System Overview

Introduction

1 System Overview

Banner supports the integrated processing of the information your organization uses to manage its resources and functions. The General System is the core component of Banner, providing centralized system management tools and utility programs to the other Banner systems. This manual provides instructions for using the General System.

Modules

System Overview The General System contains the modules that are common to all the Banner application systems:

Student Accounts Receivable Financial Aid

Human Resources Advancement Finance

Banner Application Systems

General System Modules

Job Submission Population Selection Letter Generation

System Functions/Administration Event Management

Business Rule Builder

General Web Management General International Management

General VR Management

Oracle

November 2006 General Release 7.4Confidential User Guide 1-3

1 System Overview

Job Submission

This module facilitates the submission of reports and processes throughout Banner. You can define new reports and processes to Job Submission, define default parameters, and run Banner reports and processes. You can also set up Job Submission for reports and processes developed on site.

Population Selection

This module lets you identify and group entities in the database, such as people, vendors, or organizations. You can define selection criteria to identify and extract a subset of these entities to use in Banner reports, processes, and letters.

Letter Generation

This module lets you define extract variables, build paragraphs, build a letter, extract variable data form the database, and merge the extracted variable data into the letter. You can also create a download file that can be used to produce letters with Microsoft Word or WordPerfect.

General International Management

This module has been designed to help institutions meet the requirements of the United States Bureau of Citizenship and Immigration Services (BCIS). If your institution is not located in the USA, you may not need these features. This module includes Visa tracking and SEVIS support.

System Functions/Administration

This module lets you set up, operate, and monitor Banner. You can set up currency codes, maintain EDI information, set up the Desktop Tools application, create electronic documents, set up Event Queue Maintenance, customize menus, create Banner objects, and set up QuickFlows, Fine-Grained Access Control (FGAC), and Common Matching.

Event Management

This module helps you manage an event and the functions, tasks, and participants associated with the event. You can schedule functions, organize administrative tasks, track attendance, and send messages. Keeping track of this information not only helps you manage the current event, but provides information that can be used to plan future events.


1 System Overview

General Web Management

This module supports the integrated processing between Banner and your self-service applications (Student Self-Service, Faculty and Advisor Self-Service, Employee Self-Service, Advancement Self-Service, and Executive Self-Service).

General VR Management

This module is a Banner software option available for Banner Student and Banner Financial Aid Systems that supports touch-tone telephone data entry and inquiry for student information. Voice Response includes Registration, Grade Reporting, Billing, Financial Aid, and Admissions modules.

Additional information about this module is in the Banner Voice Response Implementation Guide.


This module includes forms you can use to build business rules. It was designed to help you manage your Banner data for SEVIS processing, Multi-Institution Functionality (MIF), and Banner Integration Components, but rules you create can be used for other purposes.

You can create rules to create student and exchange visitor records automatically, and to populate columns in Banner tables with values from other columns.

Features

The General System includes the following major features:

• Comprehensive reporting. Both hard-copy reports and online inquiry forms are available.

• Main menu. The main menu provide easy access and navigation to infrequent users. Menus can be customized for your institution and individual users. Frequent users can use Direct Access or Object Search to bypass the main menu. It also includes a high-level Site Map to help users move through Banner more efficiently.

• Validation forms. Validation forms standardize the contents of certain fields and control data input. You can specify custom values without programmer intervention.

• Flexible, user-defined security. The limited access security system helps ensure that data is viewed and updated by authorized users only. The security feature can accommodate both centralized and decentralized operations. Additional information is provided in the Banner Security Technical Reference Manual.


1 System Overview

Note: In some fields, data can be partially or completed obscured for selected users through techniques called masking and concealing. Fields can also be made completely invisible to users through field hiding. For more information, see Chapter 10 of the Banner Data Security Handbook.

Value-based security (VBS) and personally identifiable information security (PII) -- both implemented through Oracle's Fine-Grained Access Control (FGAC), can selectively limit the data users can see through Banner forms. The details of the limitations depend entirely on the institution's VBS and PII rules. For more information, see the Banner Data Security Handbook.

• Online Help and Dynamic Help. The Online Help system contains information about forms and fields, as well as tasks you can perform with Banner. This help system runs in a web browser, and is available by choosing the Online Help button on the toolbar or the Online Help option from the Help pull-down menu. Additionally, you can access online help by selecting the Help Center link on the main menu.

SunGard Higher Education-delivered Dynamic Help is Banner’s original source for descriptions of forms and fields. Eventually, SunGard Higher Education plans to phase it out. Local Dynamic Help and Item Properties (choices available from the Help pull-down menu in Banner) both display column information when it is available. There are no plans to phase out Local Dynamic Help, which is a good place for you to maintain any custom information about forms or fields.

• Online manuals. You can access Banner documents directly from your computer. These electronic documents look the same as the hard copy versions, regardless of the computer you are using.


Chapter 2

Validation Forms

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-5

2 Validation FormsAccessing Validation Forms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-5

Validation Forms Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-5

Forms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-13

Cross-Product Credit Card Type Validation Form . . . . . . . . (GTVCCRD) . . . . . 2-13Certificate of Eligibility Validation Form . . . . . . . . . . . . . (GTVCELG) . . . . . 2-14Currency Codes Validation Form . . . . . . . . . . . . . . . . (GTVCURR) . . . . . 2-14Desktop Tools - Add-In Validation Form . . . . . . . . . . . . (GTVDADD) . . . . . 2-15District Division Code Validation Form . . . . . . . . . . . . . (GTVDICD) . . . . . 2-17Directory Item Validation Form . . . . . . . . . . . . . . . . . (GTVDIRO) . . . . . 2-17Visa Document Code Validation Form . . . . . . . . . . . . . (GTVDOCM). . . . . 2-18Desktop Tools - Step Property Validation Form . . . . . . . . . (GTVDPRP) . . . . . 2-18Desktop Tools - Step Type Validation Form . . . . . . . . . . . (GTVDSTP) . . . . . 2-20Duration Unit Validation Form . . . . . . . . . . . . . . . . . (GTVDUNT) . . . . . 2-22E-mail Address Type Validation Form . . . . . . . . . . . . . . (GTVEMAL) . . . . . 2-23Emphasis Code Validation Form . . . . . . . . . . . . . . . . (GTVEMPH) . . . . . 2-24Event Queue Code Validation Form . . . . . . . . . . . . . . (GTVEQNM) . . . . . 2-24Parameter Group Code Validation Form . . . . . . . . . . . . (GTVEQPG) . . . . . 2-25Parameter Code Validation Form . . . . . . . . . . . . . . . . (GTVEQPM) . . . . . 2-26Parameter Code Validation Form . . . . . . . . . . . . . . . . (GTVEQPM) . . . . . 2-27Target System Code Validation Form . . . . . . . . . . . . . . (GTVEQTS) . . . . . 2-28Expense Code Validation Form . . . . . . . . . . . . . . . . . (GTVEXPN) . . . . . 2-29FGAC Domain Validation Form . . . . . . . . . . . . . . . . . (GTVFDMN) . . . . . 2-30FGAC Domain Type Validation Form . . . . . . . . . . . . . . (GTVFDTP) . . . . . 2-30Fee Status Code Validation Form . . . . . . . . . . . . . . . . (GTVFEES) . . . . . . 2-31FGAC Group Validation Form . . . . . . . . . . . . . . . . . (GTVFGAC) . . . . . 2-31FGAC Business Profile Validation Form . . . . . . . . . . . . . (GTVFBPR). . . . . . 2-32Function Status Code Validation Form . . . . . . . . . . . . . (GTVFSTA) . . . . . . 2-33Fee Type Code Validation Form . . . . . . . . . . . . . . . . . (GTVFTYP) . . . . . . 2-33Function Code Validation Form . . . . . . . . . . . . . . . . . (GTVFUNC) . . . . . 2-33Immunization Code Validation Form . . . . . . . . . . . . . . (GTVIMMU) . . . . . 2-34Immunization Status Code Validation Form . . . . . . . . . . . (GTVIMST) . . . . . . 2-34Instructional Method Validation Form . . . . . . . . . . . . . (GTVINSM) . . . . . 2-35Integration Partner System Code Validation Form . . . . . . . . (GTVINTP) . . . . . . 2-35Learner Field of Study Type Validation Form . . . . . . . . . . (GTVLFST) . . . . . . 2-36Letter Code Validation Form . . . . . . . . . . . . . . . . . . (GTVLETR) . . . . . . 2-37Mail Code Validation Form . . . . . . . . . . . . . . . . . . . (GTVMAIL) . . . . . 2-38Menu Code Validation Form . . . . . . . . . . . . . . . . . . (GTVMENU) . . . . . 2-38Meeting Type Validation Form . . . . . . . . . . . . . . . . . (GTVMTYP) . . . . . 2-39

2-1

Table of Contents

Name Type Validation Form . . . . . . . . . . . . . . . . . . . (GTVNTYP) . . . . . . 2-40Object Code Validation Form . . . . . . . . . . . . . . . . . . (GTVOBJT) . . . . . . 2-40Paragraph Code Validation Form . . . . . . . . . . . . . . . . (GTVPARA) . . . . . . 2-40Partition Code Validation Form . . . . . . . . . . . . . . . . . (GTVPARS) . . . . . . 2-40Printer Validation Form . . . . . . . . . . . . . . . . . . . . . (GTVPRNT) . . . . . . 2-41Process Name Validation Form . . . . . . . . . . . . . . . . . (GTVPROC) . . . . . 2-41Participant Type Code Validation Form . . . . . . . . . . . . . (GTVPTYP) . . . . . . 2-42Purpose Code Validation Form . . . . . . . . . . . . . . . . . (GTVPURP) . . . . . . 2-42QuickFlow Code Validation Form . . . . . . . . . . . . . . . . (GTVQUIK) . . . . . . 2-42Fee Rate Code Validation Form . . . . . . . . . . . . . . . . . (GTVRATE) . . . . . . 2-43Revenue Code Validation Form . . . . . . . . . . . . . . . . . (GTVREVN). . . . . . 2-43Regulatory Race Validation Form . . . . . . . . . . . . . . . . (GTVRRAC). . . . . . 2-43RSVP Code Validation Form . . . . . . . . . . . . . . . . . . . (GTVRSVP) . . . . . . 2-44Rating Code Validation Form . . . . . . . . . . . . . . . . . . (GTVRTNG) . . . . . 2-44Scheduling Status Code Validation Form . . . . . . . . . . . . (GTVSCHS) . . . . . . 2-44EDI/ISO Standard Code Validation Form . . . . . . . . . . . . (GTVSCOD) . . . . . 2-46Crosswalk Validation Form . . . . . . . . . . . . . . . . . . . (GTVSDAX) . . . . . . 2-46Business Rule Parameter Code Validation Form . . . . . . . . . (GTVSQPA) . . . . . . 2-46Business Rule Process Code Validation Form . . . . . . . . . . (GTVSQPR) . . . . . . 2-47Business Rule Code Validation Form . . . . . . . . . . . . . . (GTVSQRU) . . . . . 2-48Visa Source Code Validation Form . . . . . . . . . . . . . . . (GTVSRCE) . . . . . . 2-49Subject Index Validation Form . . . . . . . . . . . . . . . . . . (GTVSUBJ) . . . . . . 2-49SEVIS Auto-populate Code Validation Form . . . . . . . . . . . (GTVSVAP) . . . . . . 2-50SEVIS Business Action Code Validation Form . . . . . . . . . . (GTVSVBA) . . . . . . 2-50SEVIS Student Cancellation Reason Code Validation Form . . . (GTVSVCA) . . . . . . 2-51SEVIS Category Code Validation Form . . . . . . . . . . . . . . (GTVSVCC) . . . . . . 2-52SEVIS Consular Post Code Validation Form . . . . . . . . . . . (GTVSVCP) . . . . . . 2-52SEVIS Creation Reason Code Validation Form . . . . . . . . . . (GTVSVCR) . . . . . . 2-53SEVIS Dependent Termination Code Validation Form . . . . . . (GTVSVDT) . . . . . . 2-53SEVIS Education Level Code Validation Form . . . . . . . . . . (GTVSVEL) . . . . . . 2-54SEVIS EV End Program Reason Code Validation Form . . . . . . (GTVSVEP) . . . . . . 2-54SEVIS Drop Below Full Time Reason Code Validation Form . . . (GTVSVFT) . . . . . . 2-55SEVIS Governmental Organization Code Validation Form . . . . (GTVSVGO) . . . . . 2-55SEVIS International Organization Code Validation Form . . . . . (GTVSVIO) . . . . . . 2-56SEVIS Infraction Type Code Validation Form . . . . . . . . . . (GTVSVIT) . . . . . . 2-56SEVIS Exchange Visitor Position Code Validation Form . . . . . (GTVSVPC) . . . . . . 2-57SEVIS Request for Form Reprint Validation Form . . . . . . . . (GTVSVRP) . . . . . . 2-57SEVIS Termination Reason Code Validation Form . . . . . . . . (GTVSVTR) . . . . . . 2-58SEVIS Transmittal Status Code Validation Form . . . . . . . . . (GTVSVTS) . . . . . . 2-58System Indicator Validation Form . . . . . . . . . . . . . . . . (GTVSYSI) . . . . . . 2-59Target Audience Code Validation Form . . . . . . . . . . . . . (GTVTARG). . . . . . 2-60Task Code Validation Form . . . . . . . . . . . . . . . . . . . (GTVTASK) . . . . . . 2-60EDI Transaction Type Validation Form . . . . . . . . . . . . . . (GTVTRTP) . . . . . . 2-60Task Status Code Validation Form . . . . . . . . . . . . . . . . (GTVTSTA) . . . . . . 2-61Task Type Code Validation Form . . . . . . . . . . . . . . . . (GTVTTYP) . . . . . . 2-61Value-Based Security Application Codes Form . . . . . . . . . (GTVVAPP) . . . . . . 2-61Value-Based Security Type Validation Form . . . . . . . . . . . (GTVVBTY) . . . . . . 2-62Visa Issuing Authority Validation Form . . . . . . . . . . . . . . (GTVVISS) . . . . . . 2-63Value-Based Security Object Code Validation Form . . . . . . . (GTVVOBJ) . . . . . . 2-63Electronic Documents Validation Form . . . . . . . . . . . . . (GTVWFED) . . . . . 2-64

General Release 7.5 December 20072-2 User Guide Confidential

Table of Contents

ZIP/Postal Code Validation Form . . . . . . . . . . . . . . . . (GTVZIPC) . . . . . . 2-64Bank Routing Number Validation Form . . . . . . . . . . . . . (GXVDIRD) . . . . . 2-65Address Source Validation Form . . . . . . . . . . . . . . . . (STVASRC) . . . . . . 2-65Address Type Code Validation Form . . . . . . . . . . . . . . (STVATYP) . . . . . . 2-65Building Code Validation Form . . . . . . . . . . . . . . . . . (STVBLDG). . . . . . 2-66Campus Code Validation Form . . . . . . . . . . . . . . . . . (STVCAMP). . . . . . 2-66Citizen Type Code Validation Form . . . . . . . . . . . . . . . (STVCITZ) . . . . . . 2-67County Code Validation Form . . . . . . . . . . . . . . . . . . (STVCNTY) . . . . . . 2-67College Code Validation Form . . . . . . . . . . . . . . . . . (STVCOLL) . . . . . . 2-67Day of Week Validation Form . . . . . . . . . . . . . . . . . . (STVDAYS) . . . . . . 2-68Degree Code Validation Form . . . . . . . . . . . . . . . . . . (STVDEGC). . . . . . 2-69Department Code Validation Form . . . . . . . . . . . . . . . (STVDEPT) . . . . . . 2-69Employment Type Validation Form . . . . . . . . . . . . . . . (STVEMPT) . . . . . . 2-70Ethnic Code Validation Form . . . . . . . . . . . . . . . . . . (STVETHN) . . . . . . 2-70Event/Function Type Code Validation Form . . . . . . . . . . . (STVETYP) . . . . . . 2-72Departmental Honors Code Validation Form . . . . . . . . . . (STVHOND) . . . . . 2-72Legacy Code Validation Form . . . . . . . . . . . . . . . . . . (STVLGCY) . . . . . . 2-72Major, Minor, Concentration Code Validation Form . . . . . . . (STVMAJR) . . . . . . 2-72Marital Status Code Validation Form . . . . . . . . . . . . . . (STVMRTL) . . . . . . 2-73Nation Code Validation Form . . . . . . . . . . . . . . . . . . (STVNATN). . . . . . 2-74Phone Rate Code Validation Form . . . . . . . . . . . . . . . (STVPRCD) . . . . . . 2-75Building/Room Attribute Code Validation Form . . . . . . . . . (STVRDEF) . . . . . . 2-76Religion Code Validation Form . . . . . . . . . . . . . . . . . (STVRELG) . . . . . . 2-76Relation Code Validation Form . . . . . . . . . . . . . . . . . (STVRELT) . . . . . . 2-76Room Status Code Validation Form . . . . . . . . . . . . . . . (STVRMST) . . . . . . 2-77Room Rate Code Validation Form . . . . . . . . . . . . . . . . (STVRRCD). . . . . . 2-77Site Code Validation Form . . . . . . . . . . . . . . . . . . . (STVSITE). . . . . . . 2-77State/Province Code Validation Form . . . . . . . . . . . . . . (STVSTAT) . . . . . . 2-78Telephone Type Validation Form . . . . . . . . . . . . . . . . (STVTELE) . . . . . . 2-78Term Code Validation Form . . . . . . . . . . . . . . . . . . . (STVTERM) . . . . . . 2-78

December 2007 General Release 7.5Confidential User Guide 2-3

Table of Contents



2 Validation Forms

Introduction

2 Validation Forms

This chapter describes the forms used to set up validation tables for the General System. Validation tables let you tailor the system to your needs by providing lists of coded values that can be entered in specific fields. You can use validation forms to build, maintain, and view validation tables.

Validation Forms The Expense Code Validation Form (GTVEXPN), for example, lets you identify and assign a code to each expense associated with event functions. When a user enters a value in the Expense field on a data entry form, the system checks the validation table, verifies the code, and issues an error message if the value is not valid. The system may also display the complete name of the expense code entered. If you need a new event expense or want to delete an obsolete expense, you can easily update the list of valid values by editing the validation form.

If more than one Banner product is installed at your institution, a number of the validation form names beginning with STV are shared validation forms. Shared validation forms are also listed in this chapter.

Accessing Validation Forms

Validation forms can be accessed in the following ways:

• Use Direct Access to enter the form name.

• Use Object Search to search for and select the form.

• Choose the List function while in the field. Sometimes the complete validation form appears, while other times a List of Values (LOV) appears. In either case, the values are display-only.

• Select from a menu.

Validation Forms Reference

This list identifies the validation forms used by the General System. Forms listed in shaded rows are used by other Banner systems in addition to the General System.

Validation Form Used By

GTVCCRD Cross-Product Credit Card Type Validation Form

None


2 Validation Forms

GTVCELG Certificate of Eligibility Validation Form GOAINTL Visa International Information Form

GTVCMSC Common Matching Source Code Validation Form

GOAMTCH Common Matching Entry FormGORCMRL Common Matching Rules FormGORCMSC Common Matching Source Rules FormGORCMUS Common Matching User Setup Form

GTVCURR Currency Codes Validation Form GUACURR Currency Conversion FormGUAINST Installation Control FormGXRBANK Bank Code Rule Form

GTVDADD Desktop Tools - Add-In Validation Form GOADADD Desktop Tools - Add-In Application Form

GTVDICD District Division Code Validation Form SLAEVNT Event FormSTVCAMP Campus Code Validation Form

GTVDIRO Directory Item Validation Form GOADPRF Web User Directory Profile Form

GTVDOCM Visa Document Code Validation Form GOAINTL Visa International Information Form

GTVDPRP Desktop Tools - Step Property Validation Form

GORDPRP Desktop Tools - Step Property Values Rule Form

GORDSTP Desktop Tools - Step Type Properties Rule Form

GTVDSTP Desktop Tools - Step Type Validation Form

GOADSTE Desktop Tools - Wizard Steps Setup Application Form


GTVDUNT Duration Unit Validation Table SCACRSE Basic Course Information FormSFARGFE Student Course Registration FormSFARHST Student Registration History and

Extension FormSSARULE Schedule Processing Rules FormSSASECQ Schedule Section Query FormSSASECT Schedule Form

GTVEMAL E-mail Address Type Validation Form GOAEMAL E-mail Address Form

GTVEMPH Emphasis Code Validation Form GEAFUNC Event Function Form

GTVEQNM Event Queue Code Validation Form GOAEQRM Event Queue Record Maintenance FormGOREQNM Event Queue Name Definition Form



2 Validation Forms

GTVEQPG Parameter Group Code Validation Form GOREQNM Event Queue Name Definition FormGOREQPG Parameter Group Rule Form

GTVEQPM Parameter Code Validation Form GOREQPG Parameter Group Rule Form

GTVEQTS Target System Code Validation Form GOAEQRM Event Queue Record Maintenance FormGOREQNM Event Queue Name Definition Form

GTVEXPN Expense Code Validation Form GEAFUNC Event Function Form

GTVFDMN FGAC Domain Validation Form GOAFGAC FGAC Group Rules FormGORFDMN FGAC Domain Driver Rules FormGOAFBPI FGAC PII Domain Business Profile

Assignments

GTVFDTP FGAC Domain Type Validation Form GORFDMN FGAC Domain Driver Rules FormGORFDTP FGAC Domain Type Predicate Rules

Form

GTVFEES Fee Status Code Validation Form GEAATID Event Registration FormGEAATTD Attendance Form

GTVFGAC FGAC Group Validation Form GOAFGAC FGAC Group Rules Form

GTVFBPR FGAC Business Profile Validation Form GOAFGAC FGAC Group Rules FormGOAFPUD FGAC Person User Defaults FormGORDMSK Data Display Mask Rules Form

GTVFSTA Function Status Code Validation Form GEAFUNC Event Function Form

GTVFTYP Fee Type Code Validation Form GEAFUNC Event Function Form

GTVFUNC Function Code Validation Form GEAFUNC Event Function FormSLAEVNT Event Form

GTVINSM Instructional Method Validation Form ROASECT Section Unavailable for Aid FormSCACRSE Basic Course Information FormSFARGFE Registration Fee Assessment Rules FormSOAORUL Open Learning Section Default Rules

FormSSADFEE Section Fee Assessment Control FormSSASECQ Schedule Section Query FormSSASECT Schedule FormSTVSCHD Schedule Type Code Validation Form



2 Validation Forms

GTVLETR Letter Code Validation Form GEAFUNC Event Function FormGUALETR Letter Process Form

GTVLFST Learner Field of Study Type Validation Form

SRARECR Recruit Prospect Information FormSAAADMS Admissions Application FormSGASTDN General Student FormSFAREGS Student Course Registration FormSHADEGR Degrees and Other Formal Awards Form

GTVMAIL Mail Code Validation Form GEAFUNC Event Function Form

GTVMENU Menu Code Validation Form GEAATID Event Registration FormGEAATTD Attendance FormGEAFUNC Event Function Form

GTVMTYP Meeting Type Validation Form SSASECT Schedule FormSSAXMTI Cross List Meeting Time / Instructor

Query Form

GTVNTYP Name Type Validation Form xPAIDEN Identification Form

GTVOBJT Object Code Validation Form GUAOBJS Object Definition FormGUTGMNU Menu Maintenance Form

GTVPARA Paragraph Code Validation Form GUALETR Letter Process FormGUAPARA Paragraph Form

GTVPARS Scheduling Partition Validation Form None

GTVPRNT Printer Validation Form GJAJOBS Process Maintenance FormGJAPCTL Process Parameter Entry Form

GTVPROC Process Name Validation Form None

GTVPTYP Participant Type Code Validation Form GEAPART Function Participant Form

GTVPURP Purpose Code Validation Form GEAFUNC Event Function Form

GTVQUIK QuickFlow Code Validation Form GUAQUIK QuickFlow Definition Form

GTVRATE Fee Rate Code Validation Form GEAFUNC Event Function Form

GTVREVN Revenue Code Validation Form GEAFUNC Event Function Form



2 Validation Forms

GTVRSVP RSVP Code Validation Form GEAATID Event Registration FormGEAATTD Attendance Form

GTVRTNG Rating Code Validation Form GEAPART Function Participant Form

GTVSCHS Scheduling Status Code Validation Form None

GTVSCOD EDI/ISO Standard Code Validation Form

GUACURR Currency Code Maintenance Form

GTVSDAX Crosswalk Validation Form None

GTVSQPA Business Rule Parameter Code Validation Form

GORRSQL Business Rules Form

GTVSQPR Business Rule Process Code Validation Form


GTVSQRU Business Rule Code Validation Form GORRSQL Business Rules Form

GTVSRCE Visa Source Code Validation Form GOAINTL Visa International Information Form

GTVSUBJ Subject Index Code Validation Form GEAFCOM Function Comment Form

GTVSVCA SEVIS Student Cancellation Reason Code Validation Form

GOASEVS SEVIS Information Form

GTVSVCC SEVIS Category Code Validation Form GOASEVS SEVIS Information Form

GTVSVCP SEVIS Consular Post Validation Form GOASEVS SEVIS Information Form

GTVSVCR SEVIS Creation Reason Code Validation Form


GTVSVDT SEVIS Dependent Termination Code Validation Form


GTVSVEL SEVIS Education Level Code Validation Form


GTVSVEP SEVIS EV End Program Reason Code Validation Form




2 Validation Forms

GTVSVFT SEVIS Drop Below Full Time Reason Code Validation Form


GTVSVGO SEVIS Governmental Organization Code Validation Form


GTVSVIO SEVIS International Organization Code Validation Form


GTVSVIT SEVIS Infraction Type Code Validation Form


GTVSVPC SEVIS Exchange Visitor Position Code Validation Form


GTVSVRP SEVIS Request for Form Reprint Code Validation Form


GTVSVTR SEVIS Termination Reason Code Validation Form


GTVSVTS SEVIS Transmittal Status Code Validation Form

SEVIS Transmittal History Form (GOASEVR)

GTVSYSI System Indicator Validation Form GJAJOBS Process Maintenance FormGLRAPPL Application Definition Rules FormGORTCTL Third-Party Electronic Control Rules

FormGUAOBJS Object Maintenance FormGUTGMNU Menu Maintenance FormGUTMENU General Menu Maintenance FormSLAEVNT Event Form

GTVTARG Target Audience Code Validation Form GEAFUNC Event Function Form

GTVTASK Task Code Validation Form GEATASK Function Task Form

GTVTRTP EDI Transaction Type Validation Form GXATPID EDI Trading Partner Identification Form

GXRETID EDI Transaction ID Rules Form

GTVTSTA Task Status Code Validation Form GEATASK Function Task Form

GTVTTYP Task Type Code Validation Form GEATASK Function Task FormGTVTASK Task Code Validation Form



2 Validation Forms

GTVVAPP Value-Based Security Application Codes Form

GOABACR Value-Based Security Access Rules FormGOAPCRL Value-Based Security Pattern Control

Rules FormGOAVUSR Value-Based Restricted Users Form

GTVVBTY Value-Based Security Type Validation Form


GTVVISS Visa Issuing Authority Validation Form GOAINTL Visa International Information Form

GTVVOBJ Value-Based Security Object Code Validation Form

GOABACR Value Based Security Access Rules FormGOAPCRL Value-Based Security Pattern Control

Rules Form

GTVWFED Electronic Documents Validation Form GOAWFED Electronic Documents FormGORWFDB Electronic Documents Builder Form

GTVZIPC ZIP/Postal Code Validation Form SLABLDG Building Definition FormSTVSITE Site Code Validation Form

GXVDIRD Bank Routing Number Validation Form GXADIRD Direct Deposit Recipient Form

STVASRC Address Source Validation Form GOAADDR Address Review and Verification Form

STVATYP Address Type Code Validation Form GOAADDR Address Review and Verification FormGOAADRL Address Role Privileges FormGOADIRO Directory Options Rule Form

STVBLDG Building Code Validation Form SLABLDG Building Definition Form

STVCAMP Campus Code Validation Form GTVPARS Scheduling Partition Validation FormSLABLDG Building Definition FormSLAEVNT Event Form

STVCITZ Citizen Type Code Validation Form Refer to the system-specific documentation for a complete listing

STVCNTY County Code Validation Form GOAADDR Address Review and Verification FormGTVZIPC ZIP/Postal Code Validation FormSLABLDG Building Definition Form

STVCOLL College Code Validation Form GTVEMPH Emphasis Code Validation FormSLABLDG Building Definition FormSLAEVNT Event FormSLARDEF Room Definition Form



2 Validation Forms

STVDAYS Day of Week Validation Form GEAFUNC Event Function FormSLAEVNT Event Form

STVDEGC Degree Code Validation Form Refer to the system-specific documentation for a complete listing

STVDEPT Department Code Validation Form GTVEMPH Emphasis Code Validation FormSLABLDG Building Definition FormSLAEVNT Event FormSLARDEF Room Definition Form

STVEMPT Employment Type Validation Form Refer to the system-specific documentation for a complete listing

STVETHN Ethnic Code Validation Form Refer to the system-specific documentation for a complete listing

STVETYP Event/Function Type Code Validation Form

GEAFUNC Event Function FormGTVFUNC Function Code Validation FormSLAEVNT Event Form

STVHOND Departmental Honors Code Validation Form

Refer to the system-specific documentation for a complete listing

STVLGCY Legacy Code Validation Form Refer to the system-specific documentation for a complete listing

STVMAJR Major, Minor, Concentration Code Validation Form

Refer to the system-specific documentation for a complete listing

STVMRTL Marital Status Code Validation Form Refer to the system-specific documentation for a complete listing

STVNATN Nation Code Validation Form GOAADDR Address Review and Verification FormGOASEVS SEVIS Information FormGTVZIPC ZIP/Postal Code Validation FormGUACURR Currency Code Maintenance FormGUAINST Installation Control FormSTVSITE Site Code Validation Form

STVPRCD Phone Rate Code Validation Form SLABLDG Building Definition FormSLARDEF Room Definition Form

STVRDEF Building/Room Attribute Code Validation Form

SLABLDG Building Definition FormSLARDEF Room Definition Form



2 Validation Forms

Forms

This section describes the validation forms used by the General System. The forms appear in alphabetical order by their seven-character form name.

Cross-Product Credit Card Type Validation Form (GTVCCRD)

Use this form to define the various credit card types that can be used with Banner Web Credit Card Payment processing.

STVRELG Religion Code Validation Form Refer to the system-specific documentation for a complete listing

STVRELT Relation Code Validation Form Refer to the system-specific documentation for a complete listing

STVRMST Room Status Code Validation Form SLARDEF Room Definition Form

STVRRCD Room Rate Code Validation Form SLABLDG Building Definition FormSLARDEF Room Definition Form

STVSITE Site Code Validation Form SLABLDG Building Definition FormSLAEVNT Event Form

STVSTAT State/Province Code Validation Form GOAADDR Address Review and Verification FormGTVZIPC ZIP/Postal Code Validation FormSLABLDG Building Definition FormSTVSITE Site Code Validation Form

STVTELE Telephone Type Validation Form GOAADDR Address Review and Verification FormSTVATYP Address Type Code Validation Form

STVTERM Term Code Validation Form SLARDEF Room Definition Form

GTVIMMU Immunization Code Validation Form GOAIMMU Immunization Information Form

GTVIMST Immunization Status Code Validation Form

GOAIMMU Immunization Information Form



2 Validation Forms

For more information on GTVCCRD, refer to the Web Credit Card Payments Handbook.

Certificate of Eligibility Validation Form(GTVCELG)

This form provides a list of certifications of eligibility for employment. Some examples, in the United States, are the I-20 and IAP-66. It has the following fields:

Currency Codes Validation Form (GTVCURR)

Use this form to display all currency codes used in Banner. Examples of currencies include Canadian dollars, German deutsche marks, and British pounds. The display includes active codes and inactive codes.

Currency codes must be defined on the Currency Code Maintenance Form (GUACURR). They are display-only on GTVCURR.

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions

Credit Card Code

Code that identifies a credit card type that can be used with Banner Web Credit Card Payment processing. Examples of credit card types include American Express and Visa.

Column: GTVCCRD_CODE

Description Description of the credit card code.

Column: GTVCCRD_CODE

User ID User who created or last updated the credit card code.

Activity Date Date the credit card code was created or last updated.

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions

Code The 6-character code representing the certification of eligibility for employment. You can query on this field.

Description The description of the code, up to 30 characters. You can query on this field.

Activity Date The date when the record was created or last updated.


2 Validation Forms

Desktop Tools - Add-In Validation Form (GTVDADD)

Use this form to create and maintain add-in codes. An add-in is a program, such as Banner Finance Spreadsheet Budgeting, that adds extra features to an application such as Microsoft Excel. You can use the add-in codes delivered with Banner, as well as create your own.

Once you create an add-in code on this form, you must use the following forms to define how it will be used:

• Desktop Tools—Add-In Application Form (GOADADD)

• Desktop Tools—Wizard Step Setup Application Form (GOADSTE)

Additionally, you must establish security for those who use the add-in on the Desktop Tools—User Security Rule Form (GORDSEC).

Note: Changes made on this form become effective the next time you log into the application.

Tip: For user-defined (local) add-in codes, the code can be changed, as long as additional information has not been defined for the code on either the Desktop Tools—Add-In Application Form (GOADADD) or the Desktop Tools—Wizard Step Setup Application Form (GOADSTE). You can change the descriptions of both local and Banner-delivered (baseline) add-in codes at any time.

Main window (GTVDADD)

Use this window to create and maintain add-in codes. You can use the add-in codes delivered with Banner, as well as create your own.


2 Validation Forms

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions / Buttons

Add-In Code Code of the add-in. An add-in is a program, such as Banner Finance Spreadsheet Budgeting, that adds extra features to an application such as Microsoft Excel. This field is required.

Add-in codes are either delivered with Banner (baseline) or created at your institution (local).

Column: GTVDADD_CODE

Source: For a baseline add-in, this value is delivered as seed data. It cannot be changed, but you can change the associated description.

For a local add-in, enter a unique code. It can be changed, as long as additional information has not been defined for the code on either the Desktop Tools—Add-In Application Form (GOADADD) or the Desktop Tools—Wizard Step Setup Application Form (GOADSTE).

Description Description of the add-in. For example, “Spreadsheet Budgeting.” This field is required. Changes to this value will appear on the Excel toolbar.

Column: GTVDADD_DESC

Source: For a baseline add-in, the default value is the description delivered with the code. It can be changed.

For a local add-in, enter a description. It can be changed.

Note: Changes made on this form become effective the next time you log into the application.

Activity Date Date on which the add-in code was created or changed.

Column: GTVDADD_ACTIVITY_DATE

Source: Banner updates this value automatically when you create or change the record. It cannot be changed.

User ID Banner-assigned value that indicates whether the add-in code was delivered with Banner (baseline) or created by a user (local).

Column: GTVDADD_USER_ID

Source: Banner assigns this value. It cannot be changed.

Values:

Baseline - The add-in code was delivered with Banner.

Local - The add-in code was created by a user.


2 Validation Forms

To create a new add-in code:

1. Access the Desktop Tools—Add-In Validation Form (GTVDADD).

2. Enter an Add-In Code.

3. Enter a description.

4. Save.

To modify an add-in description:

1. Access the Desktop Tools—Add-In Validation Form (GTVDADD).

2. Change the description.

3. Save.

Note: For local codes, you can also change or delete the code, as long as additional information has not been defined for the code on either the Desktop Tools—Add-In Application Form (GOADADD) or the Desktop Tools—Wizard Step Setup Application Form (GOADSTE). You cannot change the code of a baseline add-in.

District Division Code Validation Form (GTVDICD)

Use this form to define codes that identify districts or divisions. These codes can be assigned to:

• Employees on the Employee Form (PEAEMPL).

• Job activity on the Employee Job Activity Form (PEAJACT).

• Events on the Event Form (SLAEVNT).

• Campus codes on the Campus Code Validation Form (STVCAMP).

Directory Item Validation Form (GTVDIRO)

Use this form to define codes for the types of information included in directory profiles. The profile is used to select and print information in the Web directory.

A set of directory item codes is delivered with Banner. To ensure proper directory processing, you must not change these codes. You can change directory item descriptions without affecting directory processing. You can also add directory item codes for your site’s Web campus directory profile and the Web directory.


2 Validation Forms

Visa Document Code Validation Form (GTVDOCM)

This form provides a list of documents that could be used to validate a visa request. It has the following fields:

Desktop Tools - Step Property Validation Form (GTVDPRP)

Use this form to create and maintain property codes. A property is a type of object, such as a radio button or a picture, that appears on a step (wizard window). When combined with steps, properties control the way a user interacts with an add-in such as Banner Finance Spreadsheet Budgeting.

Once you create a property code on this form, you must use the following forms to define how it will be used:

• Desktop Tools—Step Type Properties Rule Form (GORDSTP)

• Desktop Tools—Wizard Steps Setup Application Form (GOADSTE)

You can use the property codes delivered with Banner, as well as create your own. For user-created property codes, you must use the Desktop Tools—Step Property Values Rule Form (GORDPRP) if the .DLL requires values that fall within a certain range.

Caution: Changes made on this form must reflect changes made to the GODDTOP.DLL.

Tip: For user-defined (local) property codes, the code can be changed, as long as additional information has not been defined for the code on either GORDPRP, GORDSTP, or GOADSTE. You can change the descriptions of both local and Banner-delivered (baseline) property codes at any time.

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions

Code The 6-character code representing the requested document. You can query on this field.




2 Validation Forms

Main window (GTVDPRP)

Use this window to create and maintain property codes. You can use the property codes delivered with Banner, as well as create your own.

. . . . . . . . . . . . . . Fields


Property Code Code of the property. A property is a type of object, such as a radio button or a picture, that appears on a step (wizard window).

For a local property, enter a unique code. It can be changed, as long as additional information has not been defined for the code on the Desktop Tools—Step Property Values Rule Form (GORDPRP), the Desktop Tools—Step Type Properties Rule Form (GORDSTP), or the Desktop Tools—Wizard Steps Setup Application Form (GOADSTE).

Column: GTVDPRP_CODE

Source: For a baseline property, this value is delivered with Banner. It cannot be changed, but you can change the associated description.

Description Description of the property (for example, Picture).

Column: GTVDPRP_DESC

Source: For a baseline property code, this value is delivered with the code. It can be changed.

Activity Date Date on which the property code was created or changed.

Column: GTVDPRP_ACTIVITY_DATE


User ID Banner-assigned value that indicates whether the property code was delivered with Banner or created by a user.

Column: GTVDPRP_USER_ID


Values:

BASELINE - The property code was delivered with Banner.

LOCAL - The property code was created by a user.


2 Validation Forms

To create a new property code:

1. Access the Desktop Tools—Step Property Validation Form (GTVDPRP).

2. Enter a Property Code.


4. Save.

To change a property description:

Access the Desktop Tools—Step Property Validation Form (GTVDPRP).

Change the description.

Save.

Note: For local codes, you can also change or delete the code, as long as additional information has not been defined for the code on either the Desktop Tools—Step Property Values Rule Form (GORDPRP), the Desktop Tools—Step Type Properties Rule Form (GORDSTP), or the Desktop Tools—Wizard Steps Setup Application Form (GOADSTE). You cannot change the code of a baseline add-in.

Desktop Tools - Step Type Validation Form (GTVDSTP)

Use this form to create and maintain step type codes. A step is a collection of properties that appears on a wizard window and controls the way a user interacts with an add-in such as Banner Finance Spreadsheet Budgeting.

Once you create a step type code on this form, you must use the following forms to define how it will be used:

• Desktop Tools—Step Type Properties Rule Form (GORDSTP)

• Desktop Tools—Wizard Steps Setup Application Form (GOADSTE)

You can use the step type codes delivered with Banner, as well as create your own.


Tip: For baseline step type codes, only the description can be changed. For local step type codes, both the code and description can be changed.


2 Validation Forms

Main window (GTVDSTP)

Use this window to create and maintain step type codes. You can use the step type codes delivered with Banner, as well as create your own.


. . . . . . . . . . . . . . Fields


Step Type Code Code of the step. A step is a collection of properties that appears on a wizard window.

For a local step, enter a unique code. It can be changed, as long as additional information has not been defined for the code on the Desktop Tools—Step Type Properties Rule Form (GORDSTP) or the Desktop Tools—Wizard Steps Setup Application Form (GOADSTE).

Column: GTVDSTP_CODE

Source: For a baseline step, this value is delivered with Banner. It cannot be changed, but you can change the associated description.

Description Description of the step (for example, Single Selection Step).

Column: GTVDSTP_DESC

Source: For a baseline step, this value is delivered with the code. It can be changed.

Activity Date Date on which the step was created or changed.

Column: GTVDSTP_ACTIVITY_DATE


User ID Banner-assigned value that indicates whether the step was delivered with Banner or created by a user.

Column: GTVDSTP_USER_ID


Values:

BASELINE - The step was delivered with Banner.

LOCAL - The step was created by a user.


2 Validation Forms

To create a new step code:

1. Access the Desktop Tools—Step Type Validation Form (GTVDSTP).

2. Enter a Step Type Code.


4. Save.

To change a step description:

1. Access the Desktop Tools—Step Type Validation Form (GTVDSTP).

2. Change the description.

3. Save.

For local codes, you can also change or delete the code, as long as additional information has not been defined for the code on either the Desktop Tools—Step Type Properties Rule Form (GORDSTP) or the Desktop Tools—Wizard Steps Setup Application Form (GOADSTE).

Duration Unit Validation Form (GTVDUNT)

This form is used to create and maintain duration unit codes which are associated with the calculation of an expected completion date. A calendar equivalent can be created to make sure that regardless of when the learner started the course, they would have the same time frame in which to complete it. This is done without defining attendance hours.

For example, if the learner starts the course on January 1, and the course has a duration of six weeks (where a week equates to seven days), the learner’s expected completion date of the course would be the second week of February. Or, the course has a duration of ten units (where a unit equates to 30 days). Or, the course has a duration of one semester (which equates to x days).

The duration unit code is also used as an alternate method of assessing fees. For example, an institution may require that tuition at a rate of $50 per week be assessed and charged to the learner instead of an amount that is calculated by credit hours. This type of section level fee assessment could be used for self-paced sections of a course and allow the learner to buy time in the course. Other courses such as continuing education could also use this method of assessing fees where individual learner progress in a course is required for refunding purposes without the need to define a proliferation of parts-of-term. Section level refunding rules would control any fee refunds in these instances.

Duration unit codes will only be used when associated with open learning courses in SSASECT. The duration unit code can be defined at the course level in SCACRSE


2 Validation Forms

and will default to the section record when it is created. (An open learning course is characterized by the lack of a part-of-term code in SSASECT.)

• The days information is used to derive the student’s expected completion date, if it is based on the date the student has elected to start the course. Conversely, the student may choose their expected completion date. In this case, the start date will be derived based on the duration days information.

• The units will be associated with the course duration information entered in the Basic Course Information Form (SCACRSE) for those courses that will be available for open learning registration. This information will be used in tandem with a numeric value representing the number of units (i.e., 16 weeks).

Duration unit codes cannot be deleted if they have been associated with a course or section.

E-mail Address Type Validation Form (GTVEMAL)

Use this form to define valid e-mail address type codes. Examples of e-mail address types include business, personal, and school.

These codes are used on the E-mail Address Form (GOAEMAL) to enter e-mail address information for individuals.

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions

Code Duration Unit Code. Enter the code for the duration unit, such as SEM (Semester), WEEK (Week), DAYS (Days), or MTHS (31 Days).

Description Enter the description of the duration unit code.

Days Per Unit This field displays the number of calendar days the duration unit equals. For example, for the duration code of WEEK, one unit equals seven days.

This information is used in the registration process to calculate the learner's expected course completion date.

User ID This is the ID of the person who created or last updated the record.

Activity Date This is the date the record was created or updated and is system-generated.


2 Validation Forms

The Description field is required. This text appears on Web pages where users can view or update e-mail information. Once created, an e-mail address type code cannot be changed. The description can be updated any time.

If the Web check box is selected, the e-mail type will be included in LOVs in the Banner Self-Service products as a valid address type.

Note: This indicator has no influence on the E-mail Address Form (GOAEMAL). You can use GOAEMAL to determine which e-mail addresses for a particular person should appear on the web. For example, you may want a person’s university address to appear, but not their home address.

If the URL check box is selected, the e-mail address type is a URL.

Emphasis Code Validation Form (GTVEMPH)

Use this form to define codes that identify the emphasis of functions. Examples of an emphasis include recruiting and building fund. Each emphasis can be optionally associated with a college code and/or a department. Emphasis codes can be assigned to functions on the Event Function Form (GEAFUNC).

Event Queue Code Validation Form (GTVEQNM)

Use this form to define the events that will be captured and sent to external systems. Adding an e-mail address, changing a grade, adding a course, hiring an employee, and changing a password are all examples of events that can be defined on this form.

When you first access GTVEQNM, the form displays all defined event codes. You can query any displayed field, including Activity Date.

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions

Event Code Code that uniquely identifies an event. This code is matched to the event name in the external system during the communication process. Required.

You can change or delete the Event Code only if both of these conditions exist:

• The event was never run. This means the event was never inserted into the Event Queue table to be selected by the Event Dispatcher.

• The event is not associated with any target system on the Event Queue Name Definition Form (GOREQNM).


2 Validation Forms

Parameter Group Code Validation Form (GTVEQPG)

Use this form to define the parameter groups that can be associated with events. For example, a parameter group can be defined for all the parameters passed to Workflow when an employee is hired.

The parameter group code is defined on GTVEQPG. Once the code is defined, you can use the Parameter Group Rule Form (GOREQPG) to assign specific parameters to the group.

When you first access GTVEQPG, the form displays all defined group codes. You can query any displayed field, including Activity Date.

Description Freeform description of the event. Maximum length is 30 characters. This field is accessible only if an Event Code is defined for the record. Required.

All user IDs can update this field.

User ID Code that indicates who inserted the record:

BASELINE SunGard Higher Education delivered the record as seed data or the client inserted the record while logged into Banner as BASELINE. Only BASELINE users can change or delete the Event Code field.

LOCAL The client inserted the record with a login ID other than BASELINE. Any user ID can change or delete the Event Code field.

Display-only.

Activity Date Date the record was last updated. Display-only.

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions

Group Code Code that uniquely defines a parameter group.

You can change or delete the Group Code only if the group code has no detail records on the Parameter Group Rule Form (GOREQPG).


2 Validation Forms

Parameter Code Validation Form (GTVEQPM)

Use this form to define the parameters that are associated with events. Employee class, e-mail address, student major, and term code are all examples of parameters than can be defined on this form.

When you first access GTVEQPM, the form displays all defined parameter codes. You can query any displayed field, including Activity Date.

Description Freeform description of the group code. Maximum length is 30 characters. This field is accessible only if a Group Code is defined for the record. Required.



BASELINE SunGard Higher Education delivered the record as seed data or the client inserted the record while logged into Banner as BASELINE. Only BASELINE users can change or delete the Group Code field.

LOCAL The client inserted the record with a login ID other than BASELINE. Any user ID can change or delete the Group Code field.

Display-only.


. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions

Parameter Code Code that uniquely identifies a parameter. This code is matched to the context parameters in the external system during the communication process. Required.

You can change or delete the Parameter Code only if the parameter code is not associated with any parameter group code on the Parameter Group Rule Form (GOREQPG).

Warning: Parameter codes are case sensitive. They must be defined exactly the same in Banner and in the external systems. ClearText/Credential and ClearText/SCT.Credential must be entered in mixed case.


2 Validation Forms

Target System Code Validation Form (GTVEQTS)

Use this form to define the external systems that require notification when an event occurs. Campus Pipeline/Luminis and Workflow are external systems.

When you first access GTVEQTS, the form displays all defined target system codes. You can query any displayed field, including Activity Date.

Description Free-form description of the parameter code. Maximum length is 30 characters. This field is accessible only if a Parameter Code is defined for the record. Required.



BASELINE SunGard Higher Education delivered the record as seed data or the client inserted the record while logged into Banner as BASELINE. Only BASELINE users can change or delete the Parameter Code field.

LOCAL The client inserted the record with a login ID other than BASELINE. Any user ID can change or delete the Parameter Code field.

Display-only.


To display the Activity Date, use the scroll bar at the bottom of the pane that contains the User ID field.

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions

Target Code Code that uniquely identifies an external system that requires notification when an event occurs. Required.

Caution: Target codes WORKFLOW and PIPELINE are delivered with the system and should not be changed or deleted. (Changes may impact the processing of events.)

You can change or delete the Target Code only if the target system has no associated records in the detail block on the Event Queue Name Definition Form (GOREQNM).


2 Validation Forms

Expense Code Validation Form (GTVEXPN)

Use this form to define expense codes for functions, campaigns, and prospect contacts. Examples of expenses include consulting, equipment, facilities, and publicity.

Expense codes can be assigned to:

• Functions on the Event Function Form (GEAFUNC).

• Campaigns on the Campaign Expenses Form (AFAEXPN).

• Prospect contacts on the Prospect Contact Form (AMACONT).

FGAC Domain Validation Form (GTVFDMN)

This validation form defines the various domains that are secured by Fined-Grain Access. VBS and PII FGAC security will not control access to the data contained in the domain if a domain is not defined on this form.

Note: Inserting user-defined domains is only one step of implementing FGA security. There are other essential implementation steps to enforce the FGA rules and processes.

Description Free-form description of the target system. Maximum length is 30 characters. This field is accessible only if a Target Code is defined for the record. Required.



BASELINE SunGard Higher Education delivered the record as seed data or the client inserted the record while logged into Banner as BASELINE. Only BASELINE users can change or delete the Target Code field.

LOCAL The client inserted the record with a login ID other than BASELINE. Any user ID can change or delete the Target Code field.

Display-only.


. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions


2 Validation Forms

FGAC Domain Type Validation Form (GTVFDTP)

Use this form to define the domain predicate types. The VBS type depends upon the predicate clause for the driver table. The PII types have their predicate logic defined in a database function delivered with this project.

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions

Code User-defined code associated with the Banner domain. The naming convention for domain codes is <product initial>+B_<product module name>_<fdtp code>.

For example, the domain for admissions is SB_ADMISSIONS_PII.

Column GTVFDMN_CODE

Description Code Description.

Column GTVFDMN_DESC

Activity Date Date the code was created or updated. Display only.

Column GTVFDMN_ACTIVITY_DATE

User ID Oracle ID of the individual that created or updated the record. Display only.

Column GTVFDMN_USER_ID

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions

Code FGAC domain type code.

Column GTVFDTP_CODE

Description Description of the FGAC domain type code.

Column GTVFDTP_DESC

Activity Date Date when the record was created or last updated. Display only.

Column GTVFDTP_ACTIVITY_DATE


2 Validation Forms

Fee Status Code Validation Form (GTVFEES)

Use this form to define codes that identify the payment status of fees associated with a function. Examples of a payment status include paid, partially paid, and pending.

Fee status codes can be assigned to invitees and guests on the following forms:

• Attendance Form (GEAATTD)

• Event Registration Form (GEAATID)

The Paid check box is not currently used by any Banner processing. If it is selected for a code, that code indicates the fee is completely paid. Otherwise, the status code indicates that the fee is not completely paid.

The description for a fee status code can be overwritten when a fee status code is entered for a function attendee on GEAATTD or GEAATID.

FGAC Group Validation Form (GTVFGAC)

This validation form establishes FGAC groups. The FGAC Group Rules Form (GOAFGAC) uses these group codes when you define domain predicate and business profile/user assignments.

User ID ID of the person who created or last updated the record. Display only.

Column GTVFDTP_USER_ID

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions

Code Code that uniquely identifies the security group.

Column GTVFGAC_CODE

Description Description of the security group code.

Column GTVFGAC_DESC

Activity Date Date the code was added or updated. Display only.

Column GTVFGAC_ACTIVITY_DATE


2 Validation Forms

FGAC Business Profile Validation Form (GTVFBPR)

This validation form defines the various business profiles that you can assign to various users in a group. For example, if specific users in the Admissions office process College of Arts and Science admissions, you can define a specific business profile for that purpose. You assign individual users to these Business Profiles on the FGAC Business Profile Assignment Form (GOAFBPR).

Function Status Code Validation Form (GTVFSTA)

Use this form to define codes that describe the status of functions. Examples of a function status include active, postponed, and cancelled.

Function status codes must be assigned to functions on the Event Function Form (GEAFUNC).

If you create a function on the Event Form (SLAEVNT), the system automatically assigns the status code A(active) to the function. You can override this status on GEAFUNC.

User ID Oracle ID of the individual that added or updated the record. Display only.

Column GTVFGAC_USER_ID

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions

Code User-defined business profile code.

Column GTVFBPR_CODE

Description Description of the business profile code.

Column GTVFBPR_DESC

Activity Date Date the code was added or updated.

Column GTVFBPR_ACTIVITY_DATE

User ID Oracle ID of the individual that added or updated the record.

Column GTVFBPR_USER_ID


2 Validation Forms

The Active check box is not currently used by any Banner processing. Select the check box for status codes that indicate the function is active. Clear the check box for status codes that indicate the function is no longer active.

Fee Type Code Validation Form (GTVFTYP)

Use this form to define codes that identify the different types of fees associated with functions. Examples of fee types include registration, dinner, and charitable donation.

Fees can be assigned to functions on the Event Function Form (GEAFUNC). The fee type code is one of the three components of a function fee:

• Fee type code. This code identifies the type of fee. These codes are defined on GTVFTYP.

• Fee rate code. This code identifies the type of rate. These codes are defined on the Fee Rate Code Validation Form (GTVRATE).

• Amount. An amount is associated with each fee type and fee rate.

Function Code Validation Form (GTVFUNC)

Use this form to define codes for the functions offered or sponsored by your institution. Examples of functions include receptions, dinners, conferences, and lectures.

Function codes must be assigned to functions on the following forms:

• Event Form (SLAEVNT)

• Event Function Form (GEAFUNC)

Each function code must be associated with an event/function type code by entering the code in the Type field. Event/function types are defined on the Event/Function Type Code Validation Form (STVETYP).

Immunization Code Validation Form (GTVIMMU)

Use this form to store immunization codes and their descriptions.


2 Validation Forms

Immunization Status Code Validation Form (GTVIMST)

Use this form to store immunization status codes and their descriptions.

Instructional Method Validation Form (GTVINSM)

This form is used to create and maintain instructional method codes. An instructional method code can be associated with a schedule type code from STVSCHD or can be used as a standalone description of the content delivery method for the course at the section level. Once an instructional method code has been assigned to a schedule type or section record, it cannot be deleted until all its course and section associations have been removed.

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions

Immunization Code

Code for the immunization.

Description Description of the immunization code (for example, Measles Immunization).

User ID User ID that created or last modified the record.

Activity Date Date on which the record was created or last modified.

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions

Immunization Status

Code of the immunization status (for example, 1).

Description Description of the immunization status (for example, First Inoculation).




2 Validation Forms

The Instructional Method field has been added to SSASECT where you can enter the code as a standalone value. If the code has been associated with a course, the code will default and automatically populate the field.

Integration Partner System Code Validation Form (GTVINTP)

Use this form to create and maintain your institution’s integration partner system codes. The codes you build on this form are then mapped to integration partner values on the Integration Partner System Rules Form (GORINTG).

Main Window

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions

Code Instructional Method Code. Enter the code for the instructional method, such as CLASS (Classroom-based), TUTOR (Tutorial), or WEB (Web-based).

Description Enter the description for the instructional method code.

Voice Response Message Number

This field is used to assign a number to the recorded message that describes the instructional method code for telephone applications.


User ID This is the ID of the person who created or last updated the record.

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions

Integration Partner System

Code for the partner system.

Note: Only BB (BlackBoard) and WEBCT are supported with Release 7.2.

Description Description of the partner system code

User ID User ID of the user who created or last modified the record.


2 Validation Forms

Learner Field of Study Type Validation Form (GTVLFST)

This form is used to maintain field of study type codes.

Letter Code Validation Form (GTVLETR)

Use this form to define codes that identify the letters you can generate in Banner. Examples of letters include acknowledgement, applicant, and financial aid offer letters.

Letter codes are used throughout Banner. For example, you can assign letter codes to:

• IDs on the Mail Form (xUAMAIL) of various Banner systems.

• Dues information on the Dues Installment Form (AAADINS).

• Materials on the Material Form (SOAMATL).



. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions

Code This is the code for the learner’s field of study type, such as MAJOR, MINOR, CONCENTRATION.

Description This is the description of the field of study code.

System Required The System Required checkbox is used to determine which values are required by the system. If the System Required checkbox is checked, the validation table record cannot be deleted.

This indicator is set to Y for delivered values.

User ID This field displays the user ID of the person who created the record.

Activity Date This field displays the date the record was created or modified.


2 Validation Forms

Note: Use the Letter Process Form (GUALETR) to create the actual contents of a letter.

The Allow Duplicates check box indicates whether a letter can be sent more than once to the same ID within a time frame. Leave it blank if a letter should be sent only once to the same ID within a time frame. The time frame depends on the Banner system sending the letter:

For this system: The time frame is:

Advancement For the Dues Acknowledgment Process (AAPACKN) and the Pledge/Gift Acknowledgment Report (AGPACKN), the time frame is the fiscal year. If duplicates are not permitted, an alternate letter can be sent if the Alternate Letter Code field contains a letter code.

For all other processing, no time frame is used.

Financial Aid The time frame is the aid year.

Student For Communication Plan Processing, no time frame is used if a valid materials code is entered on the Student Mail Form (SUAMAIL). An ID can receive only one mailing for a materials code, regardless of whether the Allow Duplicates check box is selected or cleared.

For all other processing, the time frame is the term.

Finance No time frame is used.

Human Resource No time frame is used.

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions

Letter Code Letter Code.

Description Letter Code description.

Allow Duplicates

Check box that indicates whether more than one letter for this Letter Code may be produced per person. If the box is checked, then multiple letters may be produced for this Letter Code per person.

Alternate Letter Code

Alternate Letter Code for letters that do not allow duplicates.

Note: This value indicates which letter should be processed, if duplicates are not allowed. Banner does not automatically send the alternate letter.


2 Validation Forms

Mail Code Validation Form (GTVMAIL)

Use this form to define codes that describe mailings for functions, campaigns, and constituent IDs. Examples of mailings include newsletters, annual reports, and invitations.

Mail codes can be assigned to:


• Campaigns on the Campaign Header Form (AFACAMP).

• Constituent IDs on the Alumni/Development Mail Form (APAMAIL).

Menu Code Validation Form (GTVMENU)

Use this form to define codes for the various food and beverage items associated with a function. Examples of menu items include baked ham, breakfast buffet, and kosher dinner.

Menu codes can be assigned to:


• Invitees and guests on the Attendance Form (GEAATTD) or the Event Registration Form (GEAATIID).

Meeting Type Validation Form (GTVMTYP)

Use this form to create and maintain meeting type codes. This information provides institutions with the ability to specify the purpose of the meeting time defined in the Meeting Time block of the Schedule Form (SSASECT).

For example, if there are regular chat sessions established for a Web-based course, these can be defined as such and then communicated to the student via their student schedule or via the Web.

Print Command Override print command. You can enter operating system print commands for special forms.


. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions


2 Validation Forms

You cannot delete meeting type records if a code has been associated with an SSRMEET record or has been defined as system required.

Name Type Validation Form (GTVNTYP)

Use this form to define codes for name types that can be associated with ID names. Examples of name types include maiden, nickname, and legal. These codes can be used for correspondence and reporting.

Object Code Validation Form (GTVOBJT)

Use this form to define codes that identify the object types used on the Object Maintenance Form (GUAOBJS). Examples of an object type include form, job, menu, and QuickFlow.

The Object Type can be a form, job, menu, QuickFlow, or message. Process menus use the message object type to display a message that tells you to use a desktop or Web application to complete the activity.

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions

Code This is the meeting type code, e.g., CHAT or CLAS.

Description This is the description of the code, e.g., Chat or Class.

System Required The System Required check box is used to indicate which values are system-required. If it is selected, the validation table record must not be deleted.

Voice Response Message Number

This field is used to assign a number to the recorded message that describes the meeting type code for telephone applications.


User ID This is the ID of the user who created or updated the record.


2 Validation Forms

Paragraph Code Validation Form (GTVPARA)

Use this form to define codes that identify the paragraphs used in Banner letters. Paragraph codes can be assigned to letters on the Letter Process Form (GUALETR).

Note: Use the Paragraph Form (GUAPARA) to create the actual contents of a paragraph. To access GUAPARA, select Build Paragraph from the Options menu on GTVPARA.

If you use Duplicate Record to copy a paragraph code and create a new one, the associated paragraph text defined on GUAPARA is also copied.

Partition Code Validation Form (GTVPARS)

Use this form to define partition codes (a category or grouping of rooms). This form is currently used as part of the interface between Banner schedule processing and the third party scheduling products Schedule 25/Model25.

Partition codes are optional, but can be used in the scheduling process to provide preferred placement of classes in a geographic area of the school. The partition code serves as a convenience for the user and is not extracted to the Scheduler software.

The partition can be placed at various levels:

• Subject

• Course

• Section

• Meeting time for the section

• Building

• Individual room

When a new partition code and description are entered and saved in this form, a sequence number is generated if the Scheduler Seq No. field is null. This unique identifier is used in the Schedule25 algorithm. Use the Maintenance button to resequence the value in the Scheduler Seq No. field. This process will overwrite the existing code and replace it in sequence starting with a value of 01.

Use the Campus field to add a campus code to a partition.

Note: The Schedule25 Rooms file requires that each room have a partition. Banner is delivered with code 00 for the default partition.


2 Validation Forms

Printer Validation Form (GTVPRNT)

Use this form to define codes that identify the printers at your institution.

Main window (GTVPRNT)

Use this window to create codes that identify the printers at your institution. Printer codes are assigned to jobs and reports on two forms:

• Process Submission Control Form (GJAPCTL)

• Sleep Wake Maintenance Form (GJASWPT)

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions

Code Code that uniquely identifies a printer. Enter the code exactly as the operating system recognizes it. Once the code is saved, it cannot be changed.

Description Description of the printer.

Command Operating system command that directs output to the printer for a sleep/wake job. This command is ignored if the job or report sending output to the printer is not a sleep/wake job.

Note: Only the Student System and Accounts Receivable System use sleep/wake mode.

Enter the command as it would normally be entered from the command line prompt. Use an at sign (@) as a placeholder for the file name to be printed. For example, in a UNIX environment the command lp –o land –d talaris1 @ prints a file in landscape mode on a printer named talaris1. In this example, lp is the print command, -o land indicates landscape mode, -d talaris1 is the destination printer, and @ is a placeholder for the file to be printed.

Printer Port Network printer port used to print output from the Saved Output Review Form (GJIREVO). The name of a local LPT device can also be used. Printing is accomplished by copying a file to this location. This port must be a valid target for a copy operation. An example is \\network\talaris1.


2 Validation Forms

To create a printer code:

1. Access the Printer Validation Form (GTVPRNT).

2. Enter the new printer Code on a blank line.

3. Enter a Description of the printer.

4. (Optional) Enter any other printer information.

5. Save.

Landscape Codes

Escape sequence of concatenated chr values that tells the printer in the Printer Port field how to print in landscape mode. The Saved Output Review Form (GJIREVO) uses this information when output is saved and printed with the maximum line length greater than 80 characters.

For example, this string tells a Talaris 1794 PS1960 printer how to print landscape:

chr(27)||chr(91)||chr(39)||chr(112)||chr(27)||chr(91)||



chr(53)||chr(48)||chr(48)||chr(59)||chr(118)

Warning: Do not enter carriage returns.

Tip: The Edit function makes it easier to enter this field.

Portrait Codes Escape sequence of concatenated chr values that tells the printer in the Printer Port field how to print in portrait mode. The Saved Output Review Form (GJIREVO) uses this information when output is saved and printed with the maximum line length less than 80 characters.

Warning: Do not enter carriage returns.

Tip: The Edit function makes it easier to enter this field.

Activity Date Date when the printer code was created or last updated.

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions


2 Validation Forms

Process Name Validation Form (GTVPROC)

Use this form to define the various Banner processes that use Web Credit Card Payment processing..

For more information on GTVPROC, refer to the Web Credit Card Payments Handbook.

Participant Type Code Validation Form (GTVPTYP)

Use this form to define codes that identify the types of participants a function can have. Examples of a participant type include caterer, speaker, and panelist.

Participant type codes must be assigned to participants on the Function Participant Form (GEAPART).

Purpose Code Validation Form (GTVPURP)

Use this form to define codes that describe the purpose of functions. Examples of a purpose include build morale, community service, and fund raiser.

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions

Process Name Code

Code that identifies a Banner process that uses Web Credit Card Payment processing. An example is WEBCCREGFEES, the Student Self-Service Registration Fees process that handles credit card payments within Registration.

Description Description of the Banner process.

Sys Ind Check box that indicates whether the code was delivered by SunGard Higher Education and is required by the system.

selected The code was delivered by SunGard Higher Education and is system-required.

cleared The code was created locally. This is the default value for new records.

User ID User who created or last updated the process name code.

Activity Date Date the process name code was created or last updated.


2 Validation Forms

Purpose codes can be assigned to functions on the Event Function Form (GEAFUNC).

QuickFlow Code Validation Form (GTVQUIK)

Use this form to define the QuickFlow codes used in the QuickFlow process. For information about the use of this form, see Creating and Using QuickFlows in Chapter 3, Processing.

Fee Rate Code Validation Form (GTVRATE)

Use this form to define codes that identify the different types of rates associated with functions. Examples of fee rates include student, discount, and regular.

Fees can be assigned to functions on the Event Function Form (GEAFUNC). The fee rate code is one of the three components of a function fee:

• Fee type code. This code identifies the type of fee. These codes are defined on the Fee Type Code Validation Form (GTVFTYP).

• Fee rate code. This code identifies the type of rate. These codes are defined on GTVRATE.

• Amount. An amount is associated with each fee type and fee rate.

Revenue Code Validation Form (GTVREVN)

Use this form to define revenue codes for functions. Examples of revenues include sponsor subsidies, donations, and fund raisers.

Revenue codes can be assigned to functions on the Event Function Form (GEAFUNC).

Regulatory Race Validation Form (GTVRRAC)

Use this form to create the new race codes that are used in the data collection of race information required by United States government regulations. Institutions in other countries that want to collect and report on race and/or ethnicity can also use this form to identify race/ethnicity codes.


2 Validation Forms

RSVP Code Validation Form (GTVRSVP)

Use this form to define codes that describe the responses invitees can give to function invitations. Examples of responses include attending, not attending, and send regrets.

RSVP codes can be assigned to invitees on the following forms:



Select the Plan to Attend check box if the code indicates the ID plans to attend. Clear the Plan to Attend check box if the code indicates the ID does not plan to attend. The value of this check box is automatically displayed on GEAATTD and GEAATID when the RSVP code is entered.

Rating Code Validation Form (GTVRTNG)

Use this form to define codes that identify the ratings you can give to participants of a function. Examples of ratings include excellent, unacceptable, and not rated.

Rating codes can be assigned to participants on the Function Participant Form (GEAPART).

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions

Race Regulatory race code.

Note: System-required race codes are delivered as SEED data.

Description Race code description.

System Required Indicates whether the race code is system required. System-required values are necessary for system processing and cannot be deleted.

User ID Oracle user ID that created or last updated the record.

Activity Date Date on which the record was last modified.


2 Validation Forms

Scheduling Status Code Validation Form (GTVSCHS)

Use this form to store Schedule25 status codes. This form is currently used as part of the interface between Banner schedule processing and the third party scheduling products Schedule 25/Model25.These status codes control whether the section is to be scheduled and listed.

The System Required check box indicates which codes are system required. If the box is selected, the code must not be deleted.

The following codes are required by Schedule25 for assignment and are delivered with Banner:

The following codes are required by Schedule25 for pre-assignment and are delivered with Banner:

Code Description

NSM Class needs a room assignment.

1SM Class needs a room assignment and has a preferred first choice room indicated in the Room Name field. This code limits the initial pool of candidate rooms in the assignment algorithm.

WSM Class needs a room assignment and must be assigned with the preceding NSM or 1SM record to the same room at the same time (cross-listed).

RSM Class is related to the preceding NSM or 1SM record and must be assigned to the same room but not at the same days/time.

NXM Class needs a room assignment and can share a room with another class whose times overlap with it (can be doubled-booked).

1XM Class needs a room assignment, has a preferred first choice room indicated in the Room Name field, and can share a room with another class whose times overlap with it (can be double-booked).

RXM Class is related to the previous NXM or 1XM record and must be assigned to the same room at the same or overlapping times.

Code Description

ASM Class has a room assignment that was made manually or in another system, such as the student information system.

AXM Class has a room assignment that was made manually or in another system, and the class time span overlaps part of all of the time span of another class assigned to the same room (double-booking or intentional conflict).


2 Validation Forms

EDI/ISO Standard Code Validation Form (GTVSCOD)

Use this form to maintain the EDI/ISO standard code lists that are used in EDI documents.

Crosswalk Validation Form (GTVSDAX)

Use this form to define records in the Crosswalk Table. Object:Access uses this information to identify the data to be reported in repeating groups and the external codes that should be selected in the Object:Access views. For more information, please refer to the GTVSDAX Handbook.

HSM This is a set of home cross-listed classes pre-assigned to the same room at identical days and times.

VSM This is a set of visitor cross-listed classes pre-assigned to the same room at identical days and times.

5SM Schedule25 assigned the class a room during a previous run.

5XM Schedule25 assigned the class a room, and it is double-booked with another class.

Code Description

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions

Element Number that identifies the EDI or ISO standard code list.

Code EDI or ISO standard code.

Description Description of the EDI or ISO standard code.

Standard Code that identifies the standards agency that defined the code list:

X X12

E EDIFACT

I ISO

(lookup) List Standard Indicator LOV

Activity Date Date the record was last updated.


2 Validation Forms

Business Rule Parameter Code Validation Form (GTVSQPA)

This form lets you define the parameters or variables you will use to build your process rules on the Business Rules Form (GORRSQL). You will use the codes you define on this form in the dynamic SQL statements on GORRSQL.

Business Rule Process Code Validation Form (GTVSQPR)

On this form, you can set up the process codes that are valid for dynamic query processing. The delivered value is SEVIS.

Process codes contain rule codes. Each individual rule is made unique by a specific process code/rule code combination.

All the SunGard Higher Education-delivered values will be required by the system; you can make codes inactive by entering the end date, but you cannot delete them. You can add codes and you can modify the descriptions of existing codes. You can

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions

Code The code that represents the parameter. There are two SunGard Higher Education-delivered values, PIDM and TERM.

Description The description of the code.

Data Type The data type for the parameter, e.g., number. Valid values are Character, Number, and Date.

Start Date The date the code becomes active, in DD-MON-YYYY format.

End Date The last day the code is effective, in DD-MON-YYYY format.

Activity Date The date this data was created or modified. Display-only.

User ID The user ID of the person who created the data or modified it last. Display-only.


2 Validation Forms

delete any of the additional codes you create. However if it is used in an existing table, you cannot delete it at all.

Business Rule Code Validation Form (GTVSQRU)

This form allows you to define the rule codes that will be used in your dynamic SQL statements. For SEVIS reporting, you might want to set up rule codes such as Create Student, Update Major, etc.

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions

Code The process code. SEVIS has been delivered.


System Required Indicates if the code is required by the system. Valid values are:

Selected - the code is required for Banner to process your data correctly. You cannot delete this code. Cleared - the code is not required by the system.

Start Date The date the code becomes effective, in DD-MON-YYYY format.

End Date The last day the code is effective, in DD-MON-YYYY format.



. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions

Code The code that identifies the rule used on GORRSQL.

Description The description of the SQL Rule code.




2 Validation Forms

Visa Source Code Validation Form (GTVSRCE)

This form provides a list of sources for documentation used to validate Visa requests. It has the following fields:

Subject Index Validation Form (GTVSUBJ)

Use this form to define indexes (keywords) that describe the subject matter of comments for functions, prospects, constituents, and designations.

Subject index codes can be assigned to comments on the following forms:

• Function Comment Form (GEAFCOM)

• Prospect Comment Form (AMACOMT)

• Comment Form (APACOMT)

• Designation Comment Form (ADACOMT)


End Date The last day the code is active, in DD-MON-YYYY format.



. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions

Code The 6-character abbreviation representing the source of a requested document. You can query on this field.

Description The description of the abbreviation, up to 30 characters. You can query on this field.



2 Validation Forms

SEVIS Auto-populate Code Validation Form (GTVSVAP)

This form allows you to define the fields in the GOBSEVS table that will be populated automatically (auto-populated) from other Banner tables. Column names from the GOBSEVS table have been delivered.

SEVIS Business Action Code Validation Form (GTVSVBA)

This form allows you to define business action codes and the procedures they will execute.

Two business actions are delivered as seed data; CREATE_STUDENT and CREATE_EV.

You can add codes using this form, and delete any codes where the System Required indicator is not selected. If the code is used in an existing table, you cannot delete it.

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions

Code The database column that will be populated in the GOBSEVS table.









2 Validation Forms

SEVIS Student Cancellation Reason Code Validation Form (GTVSVCA)

This form contains the student cancellation reason codes for SEVIS.

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions

Code The code that represents the business action. Required.


Database Package/Procedure

The package.procedure that will perform certain actions when called by your rule.







. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions

Code Cancellation reason code.

Description Description of the cancellation reason code.

User ID User ID who created or last modified the record.

Activity Date Date on which the record was created or modified.


2 Validation Forms

SEVIS Category Code Validation Form (GTVSVCC)

This form stores delivered data for the valid SEVIS exchange visitor category codes. The data is delivered, but you can change it.

SEVIS Consular Post Code Validation Form (GTVSVCP)

This form stores delivered data for the valid SEVIS consular post codes. The data is delivered, but you can change it.

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions

Code The code representing the exchange visitor’s program category. It can be up to four characters in length.

Description Description that corresponds to the code. It can be up to 60 characters in length.

User ID The user ID of the person who entered the data or changed it last. Display-only.

Activity Date The date the information was entered, or was last changed. Display-only.

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions

Code The code representing the consular post where the visa was issued. It can be up to three characters in length.





2 Validation Forms

SEVIS Creation Reason Code Validation Form (GTVSVCR)

This form contains the codes that represent why the student or exchange visitor records were created, such as initial attendance or transfer.

SEVIS Dependent Termination Code Validation Form (GTVSVDT)

This form stores codes representing the reasons a person’s dependent is no longer included on the record. For example, the dependent may have left the United States.

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions

Code The reason code specifying why the record was created.

Description The description of the creation reason code. It can be up to 30 characters in length.

Usage Indicates whether the code is for a student or an exchange visitor. Valid values are:

1 - Student2 - Exchange Visitor

User ID The user ID for the person who created the data or modified it last.

Activity Date Date on which the code was created or modified.

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions

Code The two-character code specifying why the dependent is no longer included on the record.

Description The description of the dependent termination code. It can be up to 30 characters in length.



2 Validation Forms

SEVIS Education Level Code Validation Form (GTVSVEL)

This form stores codes representing education levels, for example, associate, bachelor, and other university-obtained degrees.

SEVIS EV End Program Reason Code Validation Form (GTVSVEP)

This form stores codes representing the reasons an exchange visitor’s program could be ended.


. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions

Code The two-character education level code.

Description The description of the SEVIS education level code. It can be up to 30 characters in length.



. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions

Code The two-character code specifying why the person’s employment or fellowship ended.

Description The description of the end program reason code. It can be up to 30 characters in length.




2 Validation Forms

SEVIS Drop Below Full Time Reason Code Validation Form (GTVSVFT)

This form stores SEVIS drop below full time reason codes. They describe why the student did not carry enough credits to be considered a full-time student. Examples include illness and difficulty learning English.

SEVIS Governmental Organization Code Validation Form (GTVSVGO)

This form contains the SEVIS Governmental Organization codes. You can query on all fields.

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions

Code The two-character code specifying why the person dropped below the minimum number of credits required to be considered a full-time student.

Description The description of the SEVIS drop below full time reason code. It can be up to 30 characters in length.



. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions

Code Code representing the government organization that allowed the EV to enter the United States, up to six characters long. Display-only.

Description The description that corresponds to the code, up to 30 characters long.




2 Validation Forms

SEVIS International Organization Code Validation Form (GTVSVIO)

This form stores the data for SEVIS International Organization Codes. You can query on all fields.

SEVIS Infraction Type Code Validation Form (GTVSVIT)

This form stores the data for SEVIS exchange visitor infraction codes. You can query on all fields.

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions

Code Code representing the international organization that is sponsoring the EV while in the United States. It can be up to six characters long.

Description The description that corresponds to the code. It can be up to 30 characters long.



. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions

Code The exchange visitor infraction code. It can be up to three characters long.

Description The description of the infraction code, up to 60 characters long.




2 Validation Forms

SEVIS Exchange Visitor Position Code Validation Form (GTVSVPC)

This form stores delivered data for the valid SEVIS exchange visitor position codes. You can query on all fields.

SEVIS Request for Form Reprint Validation Form (GTVSVRP)

This form stores codes representing reasons for reprinting Visa request forms. The student may have lost the original, or it may have been damaged.

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions

Code Code representing the position the exchange visitor holds. It can be up to three characters in length.




. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions

Code The two-character code specifying why the person requested a new Visa request form.

Description The description of the reprint reason code. It can be up to 30 characters in length.




2 Validation Forms

SEVIS Termination Reason Code Validation Form (GTVSVTR)

This form stores SEVIS termination reason codes. They indicate why the student or exchange visitor was terminated from the school (expulsion, delinquency, etc.).

SEVIS Transmittal Status Code Validation Form (GTVSVTS)

This form contains the valid transmittal statuses for SEVIS records. You can query on all fields.

Note: These are internal Banner codes that are used to process records. They are not sent to SEVIS.

Warning: Do not delete any codes that have System Required selected.

Valid values are:

• P - Pending response from the U.S. government after the records were transmitted, either manually or via GORSEVE

• E - Pending response from the U.S. government after the records were transmitted manually via the SEVIS RTI

• W - Ready for batch transmittal via GORSEVE; this code is populated on records when GOASEVE is run in audit mode, and briefly when it is run in update mode (it is changed to P almost immediately)

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions

Code The termination reason code.

Description The description of the termination reason code. It can be up to 30 characters in length.

Usage The one-character code that specifies whether the termination code applies to students or exchange visitors. Valid values are:

1 - Student2 - Exchange Visitor




2 Validation Forms

• C - Response was received from the U.S. government and processing is complete

• M - The record must be sent to the U.S. government manually instead of via GORSEVE; the record contains adjudicated information

• N - No action taken

• R - Returned with error. A transaction can be returned with error by SEVISTA (usually due to a problem with the XML) or by SEVIS (the Bureau):

• If the transaction is returned by SEVISTA, the SEVIS Transmittal History Form (GOASEVR) will be populated with an R in the Trans. Status field and the SEVIS Result Code Message field will contain SEVISTA.

• If the transaction is returned by SEVIS, GOASEVR will be populated with an R in the Trans. Status field, the Status Code field will contain the error code from the Bureau, and the SEVIS Result Code Message field will contain the message that corresponds to the error code.

• X - Disregard, the record was not sent

System Indicator Validation Form (GTVSYSI)

Use this form to display codes that identify the various Banner systems used at your institution. Examples of systems include Human Resources, Student, and Finance.

Warning: Values on this form should not be changed, because Banner requires the SunGard Higher Education-delivered values to identify the applications.

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions

Code Code representing the one-character transmittal status code. Display-only.

Description The description that corresponds to the code. It can be up to 30 characters long.

System Required Indicates if this code is required by Banner. Valid values are:

Selected - the code is requiredCleared - the code can be deleted; it is not required by Banner




2 Validation Forms

You can add W, Y, and Z as codes to be used with your custom forms to differentiate them from the delivered Banner forms. However, if you set up and use other codes, your custom forms may not appear on menus.

Target Audience Code Validation Form (GTVTARG)

Use this form to define codes that identify the groups of people who can be invited to a function. Examples of target audiences include current undergraduates, high school seniors, and loan recipients.

Target audience codes can be assigned to functions on the Event Function Form (GEAFUNC).

Task Code Validation Form (GTVTASK)

Use this form to define codes that identify the tasks required to plan or carry out a function. Examples of tasks include reserve equipment, book room, and contact participants.

Task codes can be assigned to functions on the Function Task Form (GEATASK).

EDI Transaction Type Validation Form (GTVTRTP)

Use this form to display the EDI transaction types that are available within Banner. The table associated with this form is delivered with Banner and contains valid transaction types.

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions

Transaction Type ID

EDI transaction type code defined by the EDI standards committees.

Description Description of the EDI transaction type.



2 Validation Forms

Task Status Code Validation Form (GTVTSTA)

Use this form to define codes that describe the status of a task. Examples of a task status include active, completed, and pending.

Task status codes can be assigned to tasks on the Function Task Form (GEATASK).

The Complete check box is not currently used by any Banner processing. Select the check box for status codes that indicate the task is completed. Clear the check box for status codes that indicate the task is not completed.

Task Type Code Validation Form (GTVTTYP)

Use this form to define codes that describe the types of tasks a function can have. Examples of task types include clerical, maintenance, and security.

Task type codes can be assigned to:

• Specific tasks on the Function Task Form (GEATASK).

• Task codes on the Task Code Validation Form (GTVTASK).

If a type code is assigned to a task code on GTVTASK, that type code is used as the default type when a task is created on the Function Task Form (GEATASK). You can override the default type on GEATASK.

If a type code is not assigned to a task code on GTVTASK, you can manually enter a type code on GEATASK.

Value-Based Security Application Codes Form (GTVVAPP)

Use this form to define codes that identify the application items used by Value-Based Security (VBS). You must specify the VBS type associated with each application code. Some applications are predefined and are delivered as system-required values.

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions

Code Code for a VBS application. Once defined and saved, a VBS application code cannot be changed.

Description Description of the VBS application. The description can be changed at any time.


2 Validation Forms

Value-Based Security Type Validation Form (GTVVBTY)

Use this form to define codes that identify Value-Based Security (VBS) types. Some VBS types are predefined and are delivered as system-required values.

Type VBS type associated with the application.

Examples:

• Secured modules such as Admissions and Recruiting are associated with object type A (Application).

• Data values by which application records can be secured include Program, Campus, College, Level, and Department. These applications are associated with object type R (Access Rule).

• Various tables are secured based upon different conditions and kinds of information. Person-related records (recruiting and admissions records, for example) are secured by PIDM. Applications that describe the keys to secured records are associated with object type S (System Rules).

(lookup) List VBS Type Codes (GTVVBTY) list

System Required Check box that indicates whether the VBS application is required by system processing and cannot be deleted:

Selected The application is required (Y is stored in the database). Once the check box is selected, it cannot be cleared, and the record cannot be deleted.

Cleared The application is not required (N is stored in the database). This is the default when a new record is added, but it can be changed.

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions

Code Code for a VBS type. Once defined and saved, a VBS type code cannot be changed.


2 Validation Forms

Visa Issuing Authority Validation Form(GTVVISS)

This form lists the codes representing the country/embassy that may issue visas. It has the following fields:

Value-Based Security Object Code Validation Form (GTVVOBJ)

Use this form to define codes that identify the specific groups of data values to which access is controlled using Value-Based Security (VBS). Some objects are predefined and are delivered as system-required values.

Description Description of the VBS type. The description can be changed at any time.

System Required Check box that indicates whether the VBS type code is required by system processing and cannot be deleted:

Selected The type code is required (Y is stored in the database). Once the check box is selected, it cannot be cleared, and the record cannot be deleted.

Cleared The type code is not required (N is stored in the database). This is the default when a new record is added, but it can be changed.

Activity Date Date the record was added or last updated.

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions

Code The 6-character code representing the issuer of the visa. You can query on this field.




2 Validation Forms

Electronic Documents Validation Form (GTVWFED)

Use this form to create and maintain the codes and descriptions of the electronic documents.

ZIP/Postal Code Validation Form (GTVZIPC)

Use this form to identify ZIP codes and postal codes used throughout Banner. You can assign ZIP/postal codes to:

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions

Code Code for a VBS object. VBS objects identify the various groups of data values to which access is controlled using VBS. Once defined and saved, a VBS object code cannot be changed.

Description Description of the VBS object. The description can be changed at any time.

System Required Check box that indicates whether the VBS object is required by system processing and cannot be deleted:

Selected The object code is required (Y is stored in the database). Once the check box is selected, it cannot be cleared, and the record cannot be deleted.

Cleared The object code is not required (N is stored in the database). This is the default when a new record is added, but it can be changed.

Activity Date Date the record was added or last updated.

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions

Electronic Document Type

Electronic document code. Required.

Description Free-form text describing the code. Required.

Activity Date Date the record was created or was last updated. Display-only.


2 Validation Forms

• Sites on the Site Code Validation Form (STVSITE).

• Buildings on the Building Definition Form (SLABLDG).

• Recruits on the Quick Recruit Form (SRAQUIK).

• Donors on the Gift Form (AGAGIFT).

Defining ZIP/postal codes on this form can help you enter addresses in Banner more accurately. If you are on an application form and select a ZIP/postal code from a List of Values, address data from GTVZIPC automatically appears in the associated fields on the form.

Bank Routing Number Validation Form (GXVDIRD)

Use this form to define bank routing information. This information is required if you make payments by direct deposit. The Direct Deposit Recipient Form (GXADIRD) requires this bank routing information to identify the recipient’s bank that receives the payments via direct deposit.

Address Source Validation Form (STVASRC)

Use this form to define address source codes that describe why an address was added or changed. Examples of address sources include self-reported, post office change, and electronic data interchange.

Address Type Code Validation Form (STVATYP)

Use this form to define codes that identify the address types used throughout Banner. Examples of address types include billing, mailing, and permanent. An address type is required whenever you maintain an address associated with an ID. You can link a telephone type with an address type.

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions

Bank Routing Number

Routing number for the recipient’s bank. This number is required to send funds to the recipient’s bank via direct deposit.

Bank Name Name of the bank associated with the routing number.

Activity Date Date the bank routing record was created or last updated.


2 Validation Forms

The System Req field determines which codes are system required. If the check box is selected, the code cannot be deleted. Various Banner jobs require the following address types:

• MA (mailing). If the Student System or Financial Aid System tape loading process adds a person, the MA address type is used.The Preferred Address type in Constituent records created by the Student to Advancement Interface (APPSTDI) defaults to MA if a person has no address types entered as parameters for the interface.

• PA (parents). The tape loading process requires this address type. Any address for a person’s parents added during the test tape load process is added with the PA address type.

• BI (billing) and BU (business). If the Finance System is installed, these address types are required for sample data.

• XX. This address type is used when Accounting Feed (TGRFEED) creates an Accounts Payable record for a refund and the person does not have an effective address as specified in the address hierarchy parameters for the job.

Building Code Validation Form (STVBLDG)

Use this form to define codes that identify the buildings and facilities used at your institution for housing, classes, events, and functions. Examples of buildings include Biology Building, Jones Hall, and Athletic Field.

Building codes are used throughout Banner. For example, you can assign building codes to:

• Dormitory rooms on the Room Assignment Form (SLARASG).

• Classes on the Schedule Form (SSASECT).


• Functions on the Event Function Form (GEAFUNC)

The VR Msg field is used to assign a number to a recorded Voice Response message that describes the building for telephone applications.

Campus Code Validation Form (STVCAMP)

Use this form to define codes that identify the campuses within your institution. Examples of campuses include main campus and downtown campus.

Campus code are used throughout Banner. For example, you can assign campus codes to:


2 Validation Forms

• Applicant IDs on the Admissions Application Form (SAAADMS).

• Courses on the Schedule Form (SSASECT).

• Degree data on the Degrees and Other Formal Awards Form (SHADEGR).



Note: You must create a foreign campus code and an off-campus code for IPEDS reporting.

Campus codes can be associated with a district code, as defined on the District/Division Code Validation Form (GTVDICD).

Citizen Type Code Validation Form (STVCITZ)

Use this form to define citizenship codes. Examples of citizenships include citizen, noncitizen, and resident alien.

The EDI Equivalent field assigns the EDI SPEEDE/ExPRESS citizen type code values to an institution's citizen type codes. The EDI equivalent value is used in the electronic transmission of transcript information via EDI. These values are defined in the EDI SPEEDE/ExPRESS Implementation Guide for data element #1066.

County Code Validation Form (STVCNTY)

Use this form to define codes that identify counties. County codes are used throughout Banner. For example, you can assign county codes to:

• IDs on the Quick Entry Form (SAAQUIK).

• IDs on the Identification Form (SPAIDEN).


• ZIP/postal codes on the ZIP/Postal Code Validation Form (GTVZIPC).


College Code Validation Form (STVCOLL)

Use this form to define codes that identify the schools and colleges within your institution. Examples of colleges include College of Agriculture and College of Business.


2 Validation Forms

College codes are used throughout Banner. For example, you can assign college codes to:

• Applicant IDs on the Admission Application Form (SAAADMS).

• Courses on the Basic Course Information Form (SCACRSE).



• Designations on the Designation Form (ADADESG).

• Emphasis codes on the Emphasis Code Validation Form (GTVEMPH).

Note: Codes 00 (No College Designated) and 99 (College Used in Statistical Calculation) are required by Banner processing.

The Voice Response Message Number field is used to assign a number to a recorded Voice Response message that describes the college for telephone applications.

The System Required field determines which codes are system required. If the check box is selected, the code cannot be deleted.

The Canadian Statistics Code is used on the Annual University Full-Time Teaching Staff Survey.

Day of Week Validation Form (STVDAYS)

Use this form to define codes that identify days of week. Day-of-week codes are used throughout Banner. For example, you can use day-of-week codes to schedule meeting times for:

• Classes on the Schedule Form (SSASECT).



The System Req field determines which codes are system required. If the check box is selected, the code cannot be deleted.

Note: Codes U (Sunday), M (Monday), T (Tuesday), W (Wednesday), H (Thursday), F (Friday), and S (Saturday) are required by Banner processing.


2 Validation Forms

Degree Code Validation Form (STVDEGC)

Use this form to define codes that identify the degrees awarded by your institution and degrees earned at other institutions that may be recorded for alumni, employment applicants, and faculty members.

The Count in Financial Aid check box is not used for Banner Financial Aid, but may be used to interface data to third party financial aid software.

Note: The Financial Aid Eligibility check box on the Major, Minor, Concentration Code Validation Form (STVMAJR) is used to indicate aid--eligible programs for Banner Financial Aid.

The Level code indicates whether the degree is an undergraduate, graduate, or another level.

The Award Category code indicates how the degree is treated in the IPEDS reporting process.

The Voice Response Message Number field is used to assign a number to a recorded Voice Response message that describes the degree for telephone applications.

The Web Indicator check box is used to indicate whether the degree can be displayed in Banner self-service applications. You can limit the degree types that can be displayed to a subset of all degrees. This indicator defaults to unchecked (N) when a new record is added, but it can be changed to checked (Y) at any time.


Note: Code 000000 (Degree Not Declared) is required by Banner processing.

Department Code Validation Form (STVDEPT)

Use this form to define codes that identify the departments and other organizational subdivisions within your institution. Examples of departments include History, Accounting, and Drama.

Department codes are used throughout Banner. For example you can assign department codes to:

• Courses on the Basic Course Information Form (SCACRSE).

• Prospects on the Quick Recruit Form (SRAQUIK).

• Applicants on the Admissions Application Form (SAAADMS).

• Degrees on the Degrees and Other Formal Awards Form (SHADEGR).


2 Validation Forms


• Rooms on the Room Definition Form (SLARDEF).


The System Req field determines which codes are system required. If the box is checked, the code cannot be deleted.

Note: Code 0000 (Undeclared Department) is required by Banner processing.

The VR Msg No field is used to assign a number to a recorded Voice Response message that describes the department for telephone applications.

Employment Type Validation Form (STVEMPT)

Use this form to define codes that identify employment types. Examples of employment types include self-employed, employer sponsored, and no employment.

Ethnic Code Validation Form (STVETHN)

Use this form to define ethnic codes. Examples of ethnic groups include Caucasian, Chinese, and Cuban.

This form can also be used to establish crosswalk values so that when a user enters the ethnicity code, the ethnicity and race fields on Banner personal information forms will be populated, if the ethnicity and race codes do not already exist.

Warning: Addition, deletions, and revisions to codes on the Ethnic Code Rule Form (PTRETHN) in the Banner Human Resources System appear on STVETHN.

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions

IPEDS Code Used to associate your institution’s codes with IPEDS codes.

EDI Equivalent Assigns the EDI SPEEDE/ExPRESS ethnic code values to an institution's ethnic codes. The EDI equivalent value is used in the electronic transmission of transcript information via EDI. These values are defined in the EDI SPEEDE/ExPRESS Implementation Guide for data element #1109.


2 Validation Forms

LMS Equivalent Displays the IA-PLUS Loan Management System (LMS) ethnicity codes that are equivalent to the Banner ethnic codes. These codes are not validated. The translation to these LMS codes occurs during the LMS transaction feed interface from Banner Financial Aid. For more information, refer to the Banner Financial Aid User Guide or the IA-PLUS Loan Management System User Manual.

Institution Race Code

Institution race code. Choices come from the Race Rules Validation (GORRACE) list.

Description (untitled)

Description of your institution’s race code.

New Ethnicity New ethnicity codes as required by the U.S. government. Choices are:

None

Not Hispanic or Latino

Hispanic or Latino

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions


2 Validation Forms

Event/Function Type Code Validation Form (STVETYP)

Use this form to define codes that identify the types of events and functions offered at your institution. Examples of event/function types include conference, presentation, and reception.

Event/function type codes can be assigned to:


• Specific functions on the Event Function Form (GEAFUNC).

• Function codes on the Function Code Validation Form (GTVFUNC).

Departmental Honors Code Validation Form (STVHOND)

Use this form to define departmental honors codes. Examples of departmental honors include Drama Award and Math Honors.

The Degrees and Other Formal Awards Form (SHADEGR) validates departmental honors codes against the codes defined on this form.

If the Transcript Print Ind or Commencement Print Ind check box is selected, the associated honors is printed on the student's transcript or commencement program.

Legacy Code Validation Form (STVLGCY)

Use this form to define codes that identify legacy relationships. Legacy relationships indicate that a relative of the person was once associated with the institution. Examples of legacies include aunt, parents, and sister.

Major, Minor, Concentration Code Validation Form (STVMAJR)

Use this form to define codes that describe a student’s academic program enrollment. You must set up codes for all majors, minors, and concentrations at your institution plus those offered by other institutions that may be recorded for alumni, employment applicants, and faculty members.

The CIPC field identifies the Classification of Instructional Programs (CIP) code associated with the major area of study. These codes are used for IPEDS reporting.


2 Validation Forms

The Occupation check box is used to indicate those majors that have been designated as occupationally specific majors for IPEDS reporting. Only those majors with a check in this check box are reported on the Occupational Specific Programs Report (SHRCIPC).

The Financial Aid Eligibility check box is used by Banner Financial Aid. When this check box is selected, the student is eligible for financial aid. The financial aid record is tied to the major code in the Student System.

The Voice Response Message Number field is used to assign a number to a recorded Voice Response message that describes the major code for telephone applications.

The SEVIS Equivalent field contains the SEVIS major code that corresponds to each Banner major code. The U.S. government requires that you use SEVIS nation codes in your SEVIS reports.

Note: SEVIS is using the CIPC 2000 codes. These will eventually be stored in the Banner CIPC Code Validation Table (STVCIPC). The IPEDS Completion Report will require you to use the CIPC 2000 codes in April of 2004. For now, you can add the CIPC 2000 code to the SEVIS equivalent.

In a future release, Banner will provide a script that you can run when you are ready to move from using CIPC codes to CIPC 2000 codes. The script will move the SEVIS equivalent to STVMAJR_CIPC_CODE.

The System Required field determines which codes are system required. If the box is checked, the code cannot be deleted.

Note: Code 0000 (Major Not Declared) is required by Banner processing.

Marital Status Code Validation Form (STVMRTL)

Use this form to define codes that describe marital statuses.

The FA Equiv field indicates the marital status code equivalent for Financial Aid purposes.

The EDI Equiv field assigns the EDI SPEEDE/ExPRESS marital status code values to an institution's marital status codes. The EDI equivalent value is used in the electronic transmission of transcript information via EDI. These values are defined in the EDI SPEEDE/ExPRESS Implementation Guide for data element #1067.


2 Validation Forms

Nation Code Validation Form (STVNATN)

Use this form to define nation codes. Examples of nations include Albania, France, and Mongolia.

Nation codes are used throughout Banner. For example, you can assign nation codes to:

• IDs on the Identification Form (PPAIDEN).

• Addresses on the Receipt Form (TGARCPT).


• Nationality information on the International Information Form (SPAINTL).


• ZIP/postal codes on the ZIP/Postal Code Validation Form (GTVZIPC).

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions

Nation Code Code that uniquely identifies the nation. You can use any method to set up your codes. Your local codes will be translated to the appropriate EDI, LMS, ISO, and Statistics Canada values based on the translation values defined on this form.

Description Name of the nation.

SEVIS Equivalent The SEVIS code that corresponds to the existing Banner codes. The U.S. government requires that you use SEVIS nation codes in your SEVIS reports.

EDI Equivalent EDI SPEEDE/ExPRESS country code associated with the Banner nation code. This code is used in the electronic transmission of transcript information via EDI.

Values are defined in the EDI SPEEDE/ExPRESS Implementation Guide for data element #26.

Note: If no code is entered, the nation code is not sent via EDI.

LMS Equivalent IA-PLUS Loan Management System (LMS) country or nation code associated with the Banner nation code.

Banner nation codes are translated to IA PLUS LMS nation codes during the LMS transaction feed interface from the Banner Financial Aid System. For more information, refer to the Banner Financial Aid User Guide and the IA PLUS Loan Management System User Manual.


2 Validation Forms

The following publications provide standards for nation codes:

• “Codes for Educational and Cultural Exchange.” The United States Information Agency prints this list of codes and supplies updates when countries change and are renamed. This publication is available from:

Office of the General CounselUnited States Information AgencyWashington, DC 20547

• “Federal Information Processing Standards Publication 10-3.” The United States Department of Commerce uses the two-character nation codes in this publication. This free publication, current change notices, and future revisions are available from:

Standards Processing Coordinator (ADP)Computer Systems LaboratoryBuilding 225, Room B-64National Institute of Standards and TechnologyGaithersburg, MD 20899-0001Phone: (301) 975-2000

Phone Rate Code Validation Form (STVPRCD)

Use this form to define codes that identify different kinds of phone service and the billing frequency for each service. Examples of phone service include private line (daily rate), shared phone (term rate), and party line (monthly rate).

ISO Code International Standards Organization (ISO) nation code associated with the Banner nation code.This code is used internationally by countries like Canada for specific reporting requirements.

(lookup) List EDI/ISO Standard Code Validation Form (GTVSCOD)

Canadian Statistics Code

Code that identifies the nation to Statistics Canada. This number is used on the Annual University Full-Time Teaching Staff Survey.

MMREF Code MMREF-1 code that is listed in the MMREF-1 format document published by the SSA each year. The Banner Human Resources System uses this code to produce W-2 disc files in MMREF-1 format.

Activity Date Date the nation record was created or last updated.

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions


2 Validation Forms

Phone rate codes can be assigned to:



• IDs on the Phone Assignment Form (SLAPASG).

• Rate rules on the Room/Meal/Phone Rate Code Rules Form (SLSALMFE).

If the Banner Student System is not installed, phone service codes are informational only. They are not used in any processing.

Building/Room Attribute Code Validation Form (STVRDEF)

Use this form to define codes that identify the features of a building or room. Examples of attributes include handicapped accessible, air conditioned, and non-smoking.

Attribute codes can be assigned to:



• Ceremonies on the Ceremony Form (SHACRMY).

• Dormitory room assignments on the Dorm Room and Meal Application Form (SLARMAP).

• Roommate room applications on the Roommate Application Form (SLARMAT).

Religion Code Validation Form (STVRELG)

Use this form to define religion codes. Examples of religions include Baptist, Hindu, and Lutheran.

Relation Code Validation Form (STVRELT)

Use this form to define relation codes for use in beneficiary and emergency contact information. Examples of relations include brother, mother, and spouse.

The SEVIS Equiv field contains the SEVIS dependent relationship codes that correspond to the existing Banner codes.


2 Validation Forms

Room Status Code Validation Form (STVRMST)

Use this form to define codes that identify the status of rooms. Examples of a status include active and being renovated.

Status codes can be assigned to rooms on the Room Definition Form (SLARDEF).

Room Rate Code Validation Form (STVRRCD)

Use this form to define codes that identify different kinds of building and room rates and the billing frequency for each rate. Examples of room rates include conference, double room, and single room.

Room rate codes can be assigned to:



• Room assignments on the Room Assignment Form (SLARASG).

• Rate rules on the Room/Meal/Phone Rate Code Rules Form (SLALMFE).

If the Banner Student System is not installed, room rate codes are informational only. They are not used in any processing.

Site Code Validation Form (STVSITE)

Use this form to define codes that identify sites and their addresses. Addresses entered on STVSITE are not displayed on any other forms and are not included in any processing. Examples of sites include downtown site and suburb.

Site codes are used throughout Banner. For example, you can assign site codes to:



• Prospects on the Prospect Information Form (SRARECR).

• Applicants on the Admissions Application Form (SAAADMS).

• Students on the General Student Form (SGASTDN).

• Ceremonies on the Ceremony Form (SHACRMY).


2 Validation Forms

State/Province Code Validation Form (STVSTAT)

Use this form to define codes that identify states and provinces. Examples of states and provinces include Pennsylvania, Alberta, and American Samoa. You can use any method to set up your codes. Your local codes will be translated to the appropriate EDI and Stats Canada values based on the translation values defined on this form.

State/province codes are used throughout Banner. For example, you can assign state/province codes to:

• IDs on the Identification Form (PPAIDEN)

• Donors on the Gift Form (AGAGIFT)

• Receipt addresses on the Receipt Form (TGARCPT)

• Buildings on the Building Definition Form (SLABLDG)

The EDI Equivalent field assigns the EDI SPEEDE/ExPRESS state and province code values to an institution's state and province codes. The EDI equivalent value is used in the electronic transmission of transcript information via EDI. These values are defined in the EDI SPEEDE/ExPRESS Implementation Guide.

The IPEDS State Code field is used to produce the IPEDS First Time Residency Report (SHRIRES) web upload file, which is produced in conjunction with the report output.

The Canadian Statistics Code is the code for the state or province. It is used on the Annual University Full-Time Teaching Staff Survey.

Telephone Type Validation Form (STVTELE)

Use this form to define telephone type codes. Examples of telephone types include car, residence hall, and business.

Term Code Validation Form (STVTERM)

Use this form to define codes that identify terms. Examples include 999999 for end of time and 200201 for fall 2002. Term codes must be numeric and in the YYYYTT format. Codes must be constructed so they maintain the appropriate sequence of terms.

The Term/Housing Dates Start and End fields are used in the Location Management and Housing module to indicate the dates when the housing, meal plan, and phone assignments are to run.


2 Validation Forms

The Term Type field is used to assign the EDI SPEEDE/ExPRESS session code (type of session) values to the institution's term codes. The type defaults from the Academic History Control Form (SHACTRL) and can be overridden. Type codes are used in the electronic transmission of transcript information via EDI.

The Academic Year field indicates the academic year associated with the term.


Note: Codes 000000 (Beginning of Time) and 999999 (End of Time) codes are required by Banner processing.

The Financial Aid Process Year field is used to indicate the aid year with which the term is associated. Because Financial Aid is processed by aid year, institutional terms must be associated with a value in this field.

The Term and Period fields may be used to interface with third party financial aid. They are not required for Banner Financial Aid.


2 Validation Forms



Chapter 3

Processing

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-3

3 ProcessingJob Submission Procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-3

Defining New Reports and Processes to Job Submission. . . . . . . . . . . . . . . . . 3-4Setting up Parameter Defaults for Banner Reports and Processes . . . . . . . . . . . . 3-4Using Oracle*Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-10Running Banner Reports and Processes . . . . . . . . . . . . . . . . . . . . . . . . . 3-13

Population Selection Procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-19

Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-19Building a Population Selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-20Copying a Population Selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-24Creating a Population with GLBDATA . . . . . . . . . . . . . . . . . . . . . . . . . . 3-24Creating a Manual Population . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-29

Letter Generation Procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-30

Defining Variables. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-30Building Letters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-43Extracting Variables with GLBLSEL . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-48Generating Letters from Banner with GLRLETR . . . . . . . . . . . . . . . . . . . . . 3-52Creating a Download File with GLRLETR . . . . . . . . . . . . . . . . . . . . . . . . 3-58

System Functions/Administration Procedures . . . . . . . . . . . . . . . . . . . . . . 3-62

Establishing Currency Conversions . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-62Creating Bank Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-63Updating Bank Code Records . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-66Setting Up and Using Electronic Documents . . . . . . . . . . . . . . . . . . . . . . 3-67Setting Up Events in the Event Queue Maintenance Module . . . . . . . . . . . . . . 3-75Customizing Menus . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-76Managing the Data Extract Feature . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-80Creating and Using QuickFlows. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-81

Event Management Procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-83

Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-84Managing Buildings and Rooms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-84Managing Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-85Managing Functions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-85Managing Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-86Managing Participants . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-87

3-1

Table of Contents

General International Management Procedures . . . . . . . . . . . . . . . . . . . . . 3-87

Visa Tracking. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-87Student and Exchange Visitors Information System (SEVIS) . . . . . . . . . . . . . . . . 3-89

Business Rule Builder Procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-103

Establish the Rule Builder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-103Building Business Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-104Building Auto-population Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-105

Multi-Institution Functionality (MIF) Procedures . . . . . . . . . . . . . . . . . . . . 3-106

Home and Process Contexts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-107How to View the Institution Code . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-107How to Switch Between Institution Codes . . . . . . . . . . . . . . . . . . . . . . . . 3-108How Changing Institution Codes Impacts your Banner Session . . . . . . . . . . . . . 3-108

Basic Person Procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-109

Procedures for Extended ID and Name Searching . . . . . . . . . . . . . . . . . . . . 3-110


3 Processing

Introduction

3 Processing This chapter describes tasks you can perform with Banner General:

Processing • Job Submission

• Population Selection

• Letter Generation

• General International Management

• System Functions/Administration

• Event Management

• Business Rule Builder

• Basic Person Maintenance

The following documentation contains additional information about using Banner General features:

• The Banner Getting Started Guide contains basic information about using the Banner system.

• The WebTailor User Guide includes detailed information on using the General Web Management module.

• The Voice Response Implementation Guide contains more detailed information on using the Voice Response module.

• The Banner Data Security Handbook has more detailed information on using the FGAC module.

• The Banner Common Matching Handbook includes information about setting up and using Common Matching.

Job Submission Procedures

Submitting reports and other data processing jobs is a common activity for all Banner systems. With the Job Submission module you can:

• Define new reports and processes to Job Submission

• Define default parameter settings

• Run Banner reports and processes


3 Processing

Defining New Reports and Processes to Job Submission

1. Use the Process Maintenance Form (GJAJOBS) to define the characteristics of the report or process.

Note: If the code for the process is not written in RPT or Pro C, you may need to modify the gjajobs procedure (gjajobs.shl or gjajobs.com) to submit jobs from the Process Submission Control Form (GJAPCTL).

2. Use the Parameter Definitions Form (GJAPDEF) to define the characteristics and validation requirements of the parameters for the report or process. Optionally, you can establish system-level defaults.

3. For parameters that cannot be validated by an existing validation or list form on Banner, but have a defined set of values, use the Parameter Value Validation Form (GJAPVAL) to set up valid values. An example of this type of parameter is a Y/N option or a R (report)/U (update) option.

4. Use the Default Parameter Value Validation Form (GJAPDFT) to define any user-level defaults. Each user must individually identify defaults on this form. Defaults are saved under the user ID that logged on to Banner.

Setting up Parameter Defaults for Banner Reports and Processes

Using default parameters reduces the number of parameter values you must enter each time you run a report or process. You can define both system-level and user-level defaults.

System-level defaults apply to all users at your institution. They have lower priority and are used only when a parameter does not have a user-level default. System-level defaults are defined on the Parameter Definition Form (GJAPDEF). A report or process can have only one set of system-level defaults.

Individual users can have one or more sets of user-level defaults for a report or process. This is useful if a user wants to run a report or process with distinct, but frequently used parameter combinations. For example, a user can have three sets of defaults for running the Person Directory (SPRPDIR): one set for recruits, another for students, and another for faculty. Each set of defaults is called a job parameter set and has its own name. If a user has more than one set of defaults for a report or process, the name of the job parameter set must be entered when the report or process is submitted on the Process Submission Control Form (GJAPCTL).

Parameter defaults must pass several validation checks when you create them:

• If specific parameter values are defined on the Parameter Value Validation Form (GJAPVAL), the default must equal one of these values.

• If a validation form is linked to the parameter on the Parameter Definition Form (GJAPDEF), the default must equal a value on the validation form.


3 Processing

• If a validation routine is linked to the parameter on GJAPDEF, the default must pass the special validation checking.

• The default must meet all validation criteria defined on GJAPDEF. These criteria include the data type, length, and range of values.

• If a validation routine is linked to the report or process on the Process Maintenance Form (GJAJOBS), the default must pass consistency checks applied to a group of parameters.

Setting Up System-Level Defaults

1. Access the Parameter Definition Form (GJAPDEF).

2. Enter the name of the report or process in the Process Name field. You can select the down arrow icon to access the Process Maintenance Form (GJAJOBS) to search for a report or process.

3. Go to the next block.

4. Select the parameter for which you are entering a system-level default.

5. Enter the default value in the Default field. If validation requirements have been established for the parameter, select the down arrow icon to display a list of valid parameter values.

6. Save your changes.

Setting Up User-Level Defaults

There are two ways to set up user-level parameter defaults:

• You can create a single set of user-level defaults for a report or process on the Default Parameter Value Validation Form (GJAPDFT). The defaults are associated with the user ID.

• You can create one or multiple sets of defaults by using the Process Submission Control Form (GJAPCTL). If you have multiple sets, each job parameter set must have its own name. The defaults in each set are associated with the user ID and the job parameter set.

Using GJAPDFT

This form lets you create a single set of user-level parameter defaults for a report or process.

1. Log on to Banner with the user ID that will be linked to the defaults.

2. Access the Default Parameter Value Validation Form (GJAPDFT).


3 Processing

3. Enter the report or process name in the Process field. Select the down arrow icon to access the Process Maintenance Form (GJAJOBS) to search for a report or process.

4. Make sure the Parameter Set field is blank.


6. Select the parameter for which you are entering a user-level default.

Note: A message at the bottom of the form describes the selected parameter.


8. Enter the valid parameter value in the User Default field. If validation requirements have been established for the parameter, select the down arrow icon to display a list of valid parameter values.


Using GJAPCTL

This form lets you run a report or process and save the parameters as user-level defaults. If you want to save more than one set of parameters for the report or process, you can save the current set with a unique name. The defaults in each set are associated with the user ID and the job parameter set.

1. Log on to Banner with the user ID that will be linked to the defaults.

2. Access the Process Submission Control Form (GJAPCTL).

3. Enter the name of the report or process in the Process field. You can select the down arrow icon to access the Process Maintenance Form (GJAJOBS) to search for a report or process.


5. Go to the Printer Control block.

6. (Optional) Enter any print parameters. (Print parameters are not saved as user-level defaults.)

7. Go to the Parameter Values block.

8. Enter the default value for each parameter in the Values fields.

Select the down arrow icon on the Parameters field to display the Parameter Definition Form (GJAPDEF) with details for the selected parameter.

If validation requirements have been established for the parameter, you can select the down arrow icon on the Values field to display a list of valid parameter values.


3 Processing

Note: A message at the bottom of the block describes the selected parameter.

9. Go to the Submission block.

10. Select the Save Parameters check box.

11. If you want only one set of parameter defaults for the report or process, make sure the As field is blank.

OR

If you want multiple sets of parameter defaults for the report or process, enter the name and description of a new job parameter set in the As field.

12. Select the Hold radio button or the Submit radio button.


Note: If you enter a job parameter set name and description in step 11, the job parameter set is automatically added to the Job Parameter Set Rule Form (GJRJPRM).

Changing User-Level Defaults

You can change user-level parameter defaults on two different forms:

• Default Parameter Value Validation Form (GJAPDFT)


Using GJAPDFT

1. Log on to Banner with the user ID that is linked to the defaults that need to be changed.


3. Enter the report or process name in the Process field. You can select the down arrow icon to access the Process Maintenance Form (GJAJOBS) to search for a report or process.

4. If you are changing defaults for a job parameter set, enter the name of the set in the Parameter Set field. You can select the down arrow icon to access the Job Parameter Set Rule Form (GJRJPRM) to search for a job parameter set.


6. Select the parameter for which you are changing a user-level default.

Note: A message at the bottom of the form describes the selected parameter.



3 Processing

8. To change the default, enter the new default in the User Default field. If validation requirements have been established for the parameter, you can select the down arrow icon to display a list of valid parameter values.

OR

To delete the default, select the Remove Record function.

OR

To clear all user-level defaults associated with the job parameter set for the report or process, select the Clear Block function.

9. Save your changes. The new defaults appear on the Process Submission Control Form (GJAPCTL) the next time the report or process is run.

Using GJAPCTL

1. Log on to Banner with the user ID that is linked to the defaults that need to be changed.



4. If you are changing defaults for a job parameter set, enter the name of the set in the Parameter Set field. You can select the down arrow icon to access the Job Parameter Set Rule Form (GJRJPRM) to search for a job parameter set.


6. (Optional) Enter any print parameters. (Print parameters are not saved as user-level defaults.)


8. Enter any changes to the parameter values in the Values fields.

Select the down arrow icon on the Parameters field to display the Parameter Definition Form (GJAPDEF) with details for the selected parameter.

If validation requirements have been established for the parameter, you can select the down arrow icon on the Values field to display a list of valid parameter values.

Note: A message at the bottom of the block describes the selected parameter.




3 Processing

Note: If you entered a job parameter set name in step 4, the name and description automatically appear in the As fields.

Caution: If you delete the job parameter set in this block, defaults associated with the user ID will be updated, not the defaults associated with the job parameter set.



Copying User-Level Defaults to Another User

1. Log on to Banner with the user ID that is linked to the defaults that are being copied.


3. Enter the name of the report or process in the Process field. Select the down arrow icon to access the Process Maintenance Form (GJAJOBS) to search for a report or process.

4. If you are copying defaults for a job parameter set, enter the name of the set in the Parameter Set field. You can select the down arrow icon to access the Job Parameter Set Rule Form (GJRJPRM) to search for a job parameter set.


6. Select Copy Defaults to New User from the Options menu. The Copy Defaults to New User window appears.

7. Enter the user ID to whom the defaults are to be copied in the New User field. You can select the down arrow icon to list user IDs.


Creating a Job Parameter Set

A single user can have multiple sets of user-level parameter defaults for a report or process. Each set of defaults is called a job parameter set and has its own name. There are two ways to create a job parameter set:

• You can use the Job Parameter Set Rule Form (GJRJPRM) to define the name of the job parameter set. The actual defaults for a specific user are defined at a later time on the Process Submission Control Form (GJAPCTL). Different users can use the same job parameter set name but have different defaults in the set.

• You can define the name of the job parameter set and save the associated parameter values as user-level defaults all at once on the Process Submission


3 Processing

Control Form (GJAPCTL). The job parameter set is automatically added to GJRJPRM.

In either case, once defaults are saved on GJAPCTL, the job parameter set cannot be deleted from GJRJPRM.

Using GJRJPRM

1. Access the Job Parameter Set Rule Form (GJRJPRM).

2. Enter the report or process name in a blank Process field. Select the down arrow icon to access the Process Maintenance Form (GJAJOBS) to search for a report or process.

3. Enter the name of the job parameter set in the Parameter Set field.

4. Enter a description of the job parameter set in the Description field.


These steps establish the name of the job parameter set. The actual defaults in the set are defined on the Process Submission Control Form (GJAPCTL). See the steps on page 3-6 for details.

Different users can define different defaults with the same job parameter set name. For example, users JKELLY and KMEYER might both use job parameter set YEAREND. JKELLY’s default for parameter 1 might be Y (yes), while KMEYER’s default for the same parameter might be N (no).

Using GJAPCTL

You can define the name of the job parameter set and save the associated parameter values as user-level defaults all at once on the Process Submission Control Form (GJAPCTL). The job parameter set is automatically added to the Job Parameter Set Rule Form (GJRJPRM). See the steps on page 3-6 for details.

Using Oracle*Reports

Oracle Reports are special product-specific reports that are delivered with Banner Student, Accounts Receivable, and Finance. Additionally, your site may have its own custom Oracle Reports.

For information about running a specific Oracle Report, refer to the appropriate Banner Student, Accounts Receivable, or Finance user guide. For technical information about Oracle Reports, refer to the Banner General Technical Reference Manual.

You can specify the following for your Oracle Reports:


3 Processing

• Format of the report (PDF, HTML, RTF, XML, etc.)

• Destination type of the report (CACHE, FILE, MAIL, or PRINTER)

• Where you want the report to be sent (either a file location or, if the destination type is MAIL, an e-mail address)

• Execution mode (BATCH or RUNTIME)

• Whether the report should be run synchronously or asynchronously

• Whether you will run the report from GJAPCTL alone or from a form

• Whether the Oracle Reports parameter form should appear, displaying the existing parameters and allowing you to change them

These options are specified in the following parameters:

• 71 - Destination Format

• 72 - Destination Type

• 73 - Destination Name

• 74 - Execution Mode

• 75 - Communication Mode

• 76 - Parameter Form

• 77 - Display Report Value Window

Setting Up Default Values for Parameters 71-77

Job Submission parameters 71 -77 define how the report will be run (e.g., its format, destination, whether it will be run in synchronous or asynchronous mode, etc.). You can set up the default values for each report on the Parameter Definitions Form (GJAPDEF) and the Parameter Value Validations Form (GJAPVAL).

Note: You have the option of using GJAPCTL to run custom Oracle Reports without any rows defined on the Parameter Definitions Form (GJAPDEF). The system automatically adds parameters 71 through 76.

1. Access the Parameter Definitions Form (GJAPDEF).

2. Enter a value for 71 - Destination Format.

This parameter defines the report’s default format. Valid values include DELIMITED, HTML, PDF, and RTF. The default value is PDF.

Note: POSTSCRIPT and PRINTER DEFINITION are not available at this time. If you choose either of these values, you will receive the error Destination format of printer definition is not currently supported.

3. Enter a value for 72 - Destination Type.

This parameter specifies the report’s default destination type. Valid values are:

• CACHE - display the report on the screen (the default)


3 Processing

• FILE - save the report to a file

• MAIL - send the report to an e-mail address

• PRINTER - send the report to a printer

Note: If you choose a Destination Type of FILE, MAIL, or PRINTER, then the Execution Mode parameter must be ASYNC.

Warning: Because your institution’s reports could contain sensitive information, make sure that you send report data to a place where only the appropriate users have access to it.

4. Enter a value for 73 - Destination Name.

This parameter defines the default location where you want the report to be sent. You can enter up to 30 characters.

• If the Destination Type is FILE, this must be the name and location of a file to which the data should be written.

• If the Destination Type is MAIL, this must be a valid e-mail address. If you are sending the data to more than one address, each address must be separated by a comma (no spaces are permitted).

• If the Destination Type is PRINTER, this must be a valid printer name. If you leave this blank, the output will go to the report server’s default printer (if you have defined one).

5. Enter a value for 74 - Execution Mode.

This parameter specifies either BATCH or RUNTIME as the execution mode. RUNTIME is the default value.

6. Enter a value for 75 - Communication Mode.

• If the Communication Mode is ASYNC (asynchronous), the person who submitted the report can continue working in Banner while the report runs.

• If the Communication Mode is SYNC (synchronous), control only returns to the calling form after the report has finished processing.

The default value is SYNC.

When you submit a report asynchronously, you will receive a message in a pop-up window with the report job ID.

Note: If you have the Communication Mode parameter set to ASYNC (Asynchronous), you cannot set the Parameter Form Designation to Yes.

7. (Optional) Enter a value for 76 - Parameter Form Designation.

This parameter controls the display of the Oracle Reports parameter form.

• If YES, the form is displayed.

• If NO, the form is not displayed.


3 Processing

If you want to run a report with the Parameter Form Designation parameter set to YES, then the Destination Type parameter must be CACHE.

Note: You will receive an error if you run any Oracle Report with the parameters form set to display (parameter 76 = YES) in conjunction with a wildcard value for any of the other parameters.

8. Enter a value for 77 - Show Report Value Window.

This parameter specifies whether the Oracle Report Value Window appears when a user runs a report from a form other than GJAPCTL. It enables you to review and, if necessary, change various processing parameters for your job.

• If YES, the window appears and the user can change the values before submitting the report.

• If NO, the window does not appear and the report is run with the default values.

Note: The Report Value Window is not displayed for reports run from GJAPCTL because the information it contains is displayed in the Parameter Values block on GJAPCTL. It is available for forms like the Standard Billing 270 Form (FRR270B), where you can enter data into the form, then run the report via the Options menu.


Note: You will receive an error if you try to resubmit a report after returning to the parameter form to correct an error.

For example, if you entered a detail category code value of BLL instead of BIL, you would receive no data. You would then return to the parameter form, correct your mistake, and re-execute the report, at which point you would receive the error.

Accessing the Oracle Reports URL (Report Server Showjobs)

Only users with the Reports Administrator role can access Oracle Report output via a URL or any of the Report Server commands.

Running Banner Reports and Processes

There are two ways to run Banner reports and processes:

• Using Job Submission

• Using the operating system prompt

Whatever method you use, your Job Submission procedures may vary from the ones described in this section, usually because of differences in operating systems, different versions, or site-specific system modifications. Modify the following


3 Processing

procedures to your site-specific standards as necessary. See the Banner General Technical Reference Manual for more information.

Note: Interactively entering job parameters from the host is no longer supported. Parameters for all jobs must be entered on the Process Submission Controls Form (GJAPCTL).

Using Job Submission

Job Submission uses the Process Submission Control Form (GJAPCTL) to run reports and processes. You can optionally use the Saved Output Review Form (GJIREVO) to view, save, and print these reports and processes without exiting to the operating system.

Running Reports and Processes

You must have proper authorization before you can run a report or process. User authorization is established on the Oracle/Banner Security Maintenance Form (GSASECR) by authorized staff according to the policies and procedures defined at your institution.



3. If the report or process has more than one job parameter set, enter the name of the set in the Parameter Set field. You can select the down arrow icon to access the Job Parameter Set Rule Form (GJRJPRM) to search for a job parameter set.


5. (Optional) Enter any print parameters. Defaults come from the Process Maintenance Form (GJAJOBS), but they can be changed.

Note: If you want to view, save, or print online, enter DATABASE in the Printer field.

6. Go to the Parameter Values block. Parameters defined for the report or process appear. These parameters are defined on the Parameter Definition Form (GJAPDEF). Default parameter values appear, if they have been defined. These defaults can be system-level or user-level.

7. Enter any changes to the parameter values in the Values fields. Here are some tips:

• A message at the bottom of the block describes the currently selected parameter.


3 Processing

• You can select the down arrow icon on the Parameters field to display the Parameter Definition Form (GJAPDEF) with details for the selected parameter.

• If validation requirements have been established for the parameter, you can select the down arrow icon on the Values field to display a list of parameter values.

• Some parameters can have more than one value. This is indicated in the message at the bottom of the block as M/S: Multiple. To enter multiple values, place the cursor on the parameter. Select Insert Record. Select Duplicate Record to copy the previous value. Place the cursor on the copied value and change it to the appropriate value. Do not enter multiple values on the same line.


9. (Optional) To save the set of parameter values as user-level defaults, select the Save Parameters check box. If you have only one set of user-level defaults for the report or process, leave the As field blank. If you have more than one set of user-level defaults, enter the job parameter set name and description in the As field.

Note: If you entered a job parameter set name in step 3, the name and description automatically appear in the As fields.

10. To hold the report or process and run it from the operating system, select the Hold radio button. Take note of the sequence number that appears in the auto hint. Refer to the procedure on page 3-18 to run the report or process from the operating system.

OR

To run the report or process immediately, select the Submit radio button.


Caution: When a report or process is saved on GJAPCTL, the associated parameters are stored in the GJBPRUN Table with an assigned parameter sequence number. If a process on hold is never run or if a process runs and fails, the parameter entries remain in the GJBPRUN Table. Over time the table can grow in size tremendously. This is a potential problem depending on the procedures at your installation. The space allocation for GJBPRUN should be monitored closely. Parameters left in the table can be removed through SQL*Plus.

Viewing, Saving, and Printing Online Output

Job Submission provides online access to output for viewing, saving, and printing via the Saved Output Review Form (GJIREVO).

Note: In a Macintosh environment you cannot print directly from GJIREVO. You must first save the output to a desktop file and print from there.


3 Processing

The Printer Validation Form (GTVPRNT) must contain the following information for the default printer that is used with GJIREVO:

• The Printer Port field identifies the network printer port used to print output from GJIREVO. The name of a local LPT device can also be used. Printing is accomplished by copying a file from the local directory where it is saved to this location. This port must be a valid target for a copy operation.

• The Landscape Codes field contains the escape sequence of concatenated chr values that tells the printer how to print in landscape mode. GJIREVO uses this information when output is saved and printed with a maximum line length greater than 80 characters.

• The Portrait Codes field contains the escape sequence of concatenated chr values that tells the printer how to print in portrait mode. GJIREVO uses this information when output is saved and printed with a maximum line length less than 80 characters.

The Job Submission Profile Maintenance Form (GJAJPRF) contains user-level parameters that are used with GJIREVO. The GURJOBS_DIRECTORY parameter identifies the directory used to save your output from Pro*C jobs that are run with the Process Submission Control Form (GJAPCTL).

To set up Banner to support this feature, you must perform the following steps:

1. Create an Oracle Application Server Listener and PL/SQL cartridge, or use an existing one. An example URL might be:

http://yourserver.com:portnumber/plsql/

2. In Banner, go to the General User Preferences Maintenance Form (GUAUPRF). Select the Directory Options tab.

3. Scroll down until you find the Description that contains Enter the name of your Web Output URL.

The Default Value field contains http://yourserver.com/directory.

4. Enter your directory name in User Value.

5. Enter the URL you created in User Value and save your changes, for example:

http://machine123.college.edu:8888/plsql/

Note: If you want to change this value for all users, you must log onto Banner as the BASELINE user, and then make the changes on GUAUPRF.

6. Login to Banner and go to GJIREVO. The output of the job appears in a separate browser window. You can save the output to a file or send it to a printer by selecting the appropriate item from the Options menu.

Use these steps to view, save, and print online output:


3 Processing

1. Make sure that the default printer used to print online output is set up on the Printer Validation Form (GTVPRNT).

2. Use the Process Submission Control Form (GJAPCTL) to run the report or process as usual. Enter DATABASE in the Printer field.

Note: If you are running multiple jobs with the same name, the system should not overwrite existing output because Job Submission uses the job’s “one up number” as part of the file name. If you are running jobs that don’t use the “one up number” as part of the file name, you may overwrite an existing file.

3. Access the Saved Output Review Form (GJIREVO).

4. Enter the report or process name that created the output in the Process Name field.

5. Enter the sequence number that identifies the specific report or process in the Number field.

6. Enter the name of the output file in the File Name field.

7. Review the job’s output.

8. To save your output to your local directory and print a copy:

Windows PC: Select Save and Print File from the Options menu. A series of dialog boxes asks you to choose a printer and optionally set up a default printer.

Macintosh computer: Select Save to File from the Options menu. Then print from your desktop.

Web browser: The output of the job appears in a separate browser window. You can save the output to a file or send it to a printer by selecting the appropriate item from the Options menu

OR

To save your output to your local directory without printing, select Save to File from the Options menu.

OR

To remove the selected file from the database, select Delete Output from the Options menu.

Note: A file is not automatically deleted from the local directory when you save or print the file. You must maintain this directory.


3 Processing

Using the Operating System Prompt

You can submit a report or process from the operating system. You need directions from your technical support staff regarding directory names, specific commands, and syntax for your operating system. There may be timing restrictions at your installation to prevent long processes from being executed during peak operating hours.

Use the following command format to submit a Banner baseline report or process from the host command:

For example, the command to run GJRRPTS is

If you don't specify the username and password on the command line, the system prompts you for them.

Depending on where the executable C program is located at your institution, you may need to enter the directory name before entering the job name. Check with your data center personnel for details. All output is directed to the current directory.

To create an automatic page break for each page (rather than a series of line feeds), enter -f following the job name. For example,


The system requests two additional parameters:

• Run Sequence Number. This is a system-generated number that uniquely identifies the parameter values for executing the job. It is generated when you select the Hold field on the Process Submission Control Form (GJAPCTL). If you can leave the parameter blank, the report or process prompts you for all other parameters required for processing. If you enter the run sequence number, the report or process does not prompt for any other parameters. It obtains the parameter values from the parameter table, using the run sequence number as the key to the table. All reports and processes request this parameter, even those normally set up on sleep/wake routines. Entries in the

UNIX: jobname username/passwordOpenVMS: runproc jobname username/password

UNIX: gjrrpts genlusr/u_pick_itOpenVMS: runproc gjrrpts genlusr/u_pick_it

UNIX: gjrrpts -f genlusr/u_pick_itOpenVMS: runproc gjrrpts -f genlusr/u_pick_it


3 Processing

GJBPRUN Table for the run sequence number are deleted once the process is successfully completed.

• Number of Lines Per Printed Page. This parameter controls page breaking. The default, which is set on the Process Maintenance Form (GJAJOBS), is 55 lines per page. You can override the default on GJAPCTL before the job is run.

Caution: The default 55 lines per page cannot be overridden with a value greater than 66 because of an existing rpf restriction that is being enforced to emulate rpf functionality in Pro*C programs converted via SCTCCONV.

You may wish to view the contents of your report online before you print it to verify that you will get the desired output. Check with your technical staff for instructions.

Banner also allows specific reports to be written to a collector file for user-specified time interval processing and print capabilities. These processes use the “sleep/wake” routines which are unique to each process.

Population Selection Procedures

Many Banner reports, processes, and letters use sets of Banner IDs called populations. For example, a particular letter may be mailed to a specific population, and a Banner report may be generated for another population.

With the Population Selection module you can:

• Build a population selection, which is a set of rules used to select IDs from the Banner database. You can build the rules from scratch or copy an existing population selection and make changes.

• Create a population of Banner IDs. You can either use the rules in a population selection to extract IDs from the database, or you can manually create a population.

Once a population is created, you can view its contents on the Population Selection Extract Inquiry Form (GLIEXTR).

Definitions

The following definitions are useful for understanding the functions of the Population Selection module:

Population A set of Banner IDs used for reports, processes, and letters. A population is uniquely identified by an application, selection ID, creator ID, and user ID.


3 Processing

Building a Population Selection

A population selection is a set of rules used to select IDs from the Banner database for reports, processes, and letters. A population selection is uniquely identified by an application, selection ID, and creator ID.

Note: You can use objects to simplify the building process. An object is a set of common rules used in many different population selections and variables. Objects are defined on the Object Definition Rules Form (GLROBJT). Once they are defined, you can reference the object rather than enter the entire set of rules each time it is needed. Objects are not required, but they simplify data entry and provide some consistency.

1. Make sure the application associated with the population selection is defined on the Application Definition Rule Form (GLRAPPL). An application is a functional area that controls a population selection. Optionally, an application will include general, high-level rules used to select IDs, if they exist for that application.

Note: Once defined, the application can be used repeatedly for every population selection associated with that application.

2. Access the Population Selection Definition Rules Form (GLRSLCT).

3. Enter the application in the Application field.

4. Enter a population selection name in the Selection ID field. You can click the down arrow icon to access the Population Selection Inquiry Form (GLISLCT) to see the population selections that already exist.

5. Verify the Creator ID. Your user ID is the default, but it can be changed.

6. Go to the Description block.

Population selection

A set of rules used to select IDs from the Banner database for reports, processes, and letters. A population selection is uniquely identified by an application, selection ID, and creator ID.

Application A functional area with similar characteristics that can be applied to population selections, populations, and variables.

Variable A specific piece of data in the database and the set of rules used to select that data.

Object A set of common rules used in many different population selections and variables. Objects are not required, but they simplify data entry and provide some consistency.


3 Processing

(a) Enter a free-form description of the population selection in the Description field.

(b) (Optional) Select the Manual check box if all joins must be entered manually in the Rules block. No automatic PIDM joins occur when rules are compiled. This check box is used for population selections that use secondary PIDMs rather than key PIDMs to join two or more tables.

Any GLRAPPL high-level rules for the application will be included in manual population selections.

(c) (Optional) Select the Lock check box to lock the population selection. If the population selection is locked, only the creator ID can use this population selection in the Population Selection Extract Process (GLBDATA), view a selected population on the Population Selection Extract Inquiry Form (GLIEXTR), or change a selected population on the Population Selection Extract Data Form (GLAEXTR).

Note: A user cannot change or delete population selection rules that were created by another user ID, regardless of the lock indicator.

(d) (Optional) Select the Delete check box to delete all rules associated with the population selection. This also deletes all IDs that have the same user ID as the creator ID associated with their population selection. If a population was extracted by a user ID different from the creator ID, the IDs are not deleted.

7. Go to the Definition block. This is where you identify the data to be selected from the database.

(a) In the Select field, enter the database column from which data will be extracted. This database column must reference a PIDM (for example, SPRIDEN_PIDM or RORSTAT_PIDM). (A PIDM is a unique internal ID maintained by the system for each entity entered on Banner.) This column name is validated against the data dictionary.

(b) In the From field, enter the names of all tables from which you want to extract data. Use the format <table><alias>, separating multiple table names with commas. You can use aliases to reference tables in subqueries within the selection rules, or multiple times within the selection rules. Aliases have a maximum length of four characters. Table names are validated against the data dictionary.

If the application associated with a population selection has selection rules, include all tables referenced in the application rules. To improve performance of the Population Selection Extract Process (GLBDATA), list multiple tables in the From field from most general to most specific, or largest to smallest. For example, if two tables are being used, one with one record per ID and another with multiple records, list the multiple record table first.

8. Go to the Rules block. This is where you enter the selection rules.


3 Processing

Note: Use open and closed parentheses to group nested statements for logical evaluation. You can use up to three levels of nested statements. The number of open parentheses on a line must equal the number of closed parentheses.

(a) In the Data Element field, enter the name of the database column used in the selection rule. The name must be a valid database column in the Oracle data dictionary. You cannot enter the name of an SQL function, such as MAX or MIN, in this field.

To reference an object, enter *INCL followed by the object name. For example, enter *INCL AID_PERIOD. Then select Next Item. The rules from the AID_PERIOD object are automatically added to the population selection. You can click the down arrow icon to access the Object Inquiry Form (GLIOBJT) to search for an object.

(b) In the Operator field, enter an SQL operator (=, <>, >, <, and so forth). The operator is used to compare the Data Element and Value fields.

For date comparisons, avoid using an equal sign (=) because dates are often stored with hours, minutes, and seconds. A better approach is to use less than (<), greater than (>), less than or equal (<=), or greater than or equal (>=). You might need an extra condition. For example, ACTIVITY_DATE is stored with hours, minutes, and seconds. Use these statements to find addresses changed on March 1, 2003:

SPRADDR_ACTIVITY_DATE >= ‘01-MAR-03’ ANDSPRADDR_ACTIVITY_DATE < ‘02-MAR-03’

(c) In the Value field, enter the value that is compared with the Data Element based on the Operator. This can be a constant literal, another database column name or alias, combination of a constant literal and database column name, dynamic parameter, or subquery. Use upper case.

Note: Do not enter a value if the Operator contains NULL or IS NOT NULL.

Constant literal: The data type of the Data Element determines the format of the literal. Values that are compared to character data elements must be enclosed in single quotes. Values that are compared to numeric data elements must be numeric. Values that are compared to date data elements must be in the format 'DD-MON-YY' or 'DD-MON-YYYY'. Single quotes are not used with SYSDATE. Use the operator AND between ranges. For example, enter ‘01-JAN-03’ AND ‘31-JAN-03’. Use the same format for both years (YY or YYYY).

Note: The operator BETWEEN cannot execute dynamic parameters in a Selection ID or Variable. Dynamic parameters contained within single quotes are treated as literals.

Another database column name: The Value is validated against the Oracle data dictionary. If the data types (character, numeric, or date) of the Value


3 Processing

and Data Element are not the same, a warning appears. You can override the warning and keep the comparison.

Dynamic parameter: Enter an ampersand (&) followed by text (for example, &Letter_Code). When you extract a population with the Population Selection Extract Process (GLBDATA), the system prompts for each dynamic parameter in the selection rules.

Subquery: Enter (*SUB<variable>). Use a subquery to select one record when an ID might have multiple records. The parentheses are required. The literal *SUB indicates this is a subquery, or reference to another variable. The variable is a valid variable name already defined on the Variable Rules Definition Form (GLRVRBL) and compiled in this application. You can select the down arrow icon to access the Variable Inquiry Form (GLIVRBL) to search for a variable. If you select a variable from the list, the system gives it the proper syntax. A population selection can have only one subquery. If defined, it must be the last rule.

9. In the AND/OR field, enter the connector that links rules with AND or OR logic. All lines in the Rules block, except the last line, must contain a connector.

10. Once all the rules are entered, save your changes.

Task Notes

• When using a dynamic parameter with an IN or NOT IN operator be sure to include left and right parentheses. Do not include spaces when entering the value for the dynamic parameter. The following is correct:

88 EMAL_CODE (‘WWW’,’URL’)

• To improve processing time, certain criteria (such as whether a person is alive or has a current ID) should be specified through population selection rules rather than with a subquery.

• Outer joins cannot be performed. A join in Oracle occurs when fields from two or more tables are compared. If a matching row in one table does not exist, no result is returned. An outer join would cause a result to be returned even if a matching row does not exist.

For example, suppose you want to select everyone on Banner with a birth date after 1985, or an unknown birth date. The birth date is stored on the General Person Table (an optional table). If the person record exists for an ID, the ID and birth date are selected even if the birth date does not exist. If the person record does not exist for the ID, the ID is not selected. To extract this information you must create two population selections: one to select everyone with a person record whose birth date is greater than 1985 or whose birthdate is null, and another to select everyone who does not have a person record. The two population selections would then be combined in the Population Selection Extract Process (GLBDATA) with a union function, to give the desired population.


3 Processing

Copying a Population Selection

You can copy the rules in an existing population selection to create a new population selection. You can change the application and selection ID. Your ID becomes the creator ID. A copied population selection can be changed as needed.

1. Access the Population Selection Definition Rules Form (GLRSLCT).

2. Enter the application associated with the population selection you want to copy in the Application field.

3. Enter the population selection you want to copy in the Selection ID field. You can select the down arrow icon to access the Population Selection Inquiry Form (GLISLCT) to search for a population selection.

4. To access the Selection ID Copy window, select Copy from the Options menu. Information in the Copy From block defaults from the main window.

5. Enter the application associated with the new population selection in the Copy To Application field.

6. Enter the new population selection ID in the Copy To Selection field. You can select the down arrow icon to access the Population Selection Inquiry Form (GLISLCT) to see the existing population selection IDs that cannot be used.

Note: The Creator ID defaults to your user ID. It cannot be changed.

7. Select the Insert Record function. The main window reappears with the cursor in the Description field.

8. Use the normal steps to change and save rules for the new population selection. You can use the steps in “Building a Population Selection” on page 3-20, beginning with step 6.

Creating a Population with GLBDATA

A population is a set of Banner IDs used for reports, processes, and letters. One way to create a population is with the Population Selection Extract Process (GLBDATA). The Banner user ID that runs GLBDATA becomes the user ID associated with the population.

There are two ways to use GLBDATA:

• Extract IDs using the population selection rules defined on the Population Selection Definition Rules Form (GLRSLCT).

• Create a population from the union, intersection, or difference (minus) of the rules in two existing population selections.

You can run GLBDATA from the Process Submission Control Form (GJAPCTL) or from the operating system. If you run the process from the operating system


3 Processing

prompt, check with your technical personnel for the appropriate command to use at your institution. For example:

Extracting IDs Using Population Selection Rules

You can create a population by extracting IDs using the population selection rules defined on the Population Selection Definition Rules Form (GLRSLCT).


2. Enter GLBDATA in the Process field.

3. If the process has more than one job parameter set, enter the name of the set in the Parameter Set field. You can select the down arrow icon to access the Job Parameter Set Rule Form (GJRJPRM) to search for a job parameter set.

4. (Optional) If you want to view, save, or print online, enter DATABASE in the Printer field.

5. Go to the Parameter Values block. Parameters defined for the process appear. Default parameter values appear, if they have been defined.

6. Enter the following parameter values:




10. (Optional) If the population selection in parameter 1 has dynamic parameters, the cursor returns to the Parameter Values block. Enter values for the dynamic

UNIX: glbdata.shl username passwordOpenVMS: @glbdata username password

Parameter Number

Parameter Value

1 Selection Identifier 1

ID of the population selection that will be used to extract the population

6 Application Code

Application associated with the population selection

7 Creator ID of Selection ID

Oracle ID of the user who created the population selection

8 Detail Execution Report

S - Display SQL statements.I - Display SQL statements and inserts.Y - Display paragraphs.


3 Processing

parameters in parameter 88. Return to the Submission block. Save your changes again.

Note: You must enter a non-blank value for each 88 level prompt.

Creating a Population from the Union, Intersection,or Minus of Existing Population Selection Rules

You can create a population from the union, intersection, or minus (difference) of the rules in two existing population selections. The rules in both of the existing population selections are defined on the Population Selection Definition Rules Form (GLRSLCT).

Note: The two existing population selections must have the same application and creator ID.


2. Enter GLBDATA in the Process field.

3. If the process has more than one job parameter set, enter the name of the set in the Parameter Set field. You can select the down arrow icon to access the Job Parameter Set Rule Form (GJRJPRM) to search for a job parameter set.

4. (Optional) To view, save, or print online, enter DATABASE in the Printer field.



Parameter Number

Parameter Value


ID of the first existing population selection that will be used to create a new population selection


ID of the second existing population that will be used to create a new population selection

3 New Selection Identifier

ID of the new population selection that will be created from the two existing population selections

4 Description for New Selection

Freeform description of the new population selection


3 Processing




10. (Optional) If either of the population selections in parameter 1 or 2 has dynamic parameters, the cursor returns to the Parameter Values block. Enter values for the dynamic parameters in parameter 88. Return to the Submission block. Save your changes again.


Task Notes

• Creating a new population from the union, intersection, or minus of two existing population selections uses the rules defined for the two existing

5 Union/Intersection/Minus

Code that determines the contents of the resulting population:

U The population includes all IDs extracted by the first population selection and all IDs extracted by the second population selection. If an ID is selected by both, it is included only once in the population.

I The population includes only those IDs that are extracted by both population selections.

M The population includes all IDs extracted by the first population selection except those IDs extracted by the second population selection.

6 Application Code

Application associated with the two existing population selections. This becomes the application associated with the new population selection.

7 Creator ID of Selection ID

Oracle ID of the user who created the two existing population selections

8 Detail Execution Report

S - Display SQL statements.I - Display SQL statements and inserts.Y - Display paragraphs.

Parameter Number

Parameter Value


3 Processing

population selections. Manual entries for a population are not considered as part of any population selection.

• For the union or intersection option, the order of the selection IDs in parameters 1 and 2 does not matter. For the minus option, the results are different depending on the order of the selection IDs.

• A population selection created from the union, intersection, or minus cannot be used as parameter 1 or parameter 2 because there are no rules associated with it. However, a population selection can be created with rules that extract the IDs from the generated population selection with no rules.

• If you are using the union, intersection, or minus option, you only have to run GLBDATA once to get IDs for the new population (union, intersection, or minus). You don’t have to run GLBDATA for the two existing population selections before you run it for the new population selection.

• When you create a new population selection from two existing population selections, “header” information for the new population selection is based on parameters 3 (ID) and 4 (description) that are entered for GLBDATA.

• If this is a new ID, the ID and description are added to the Population Selection Definition Rules Form (GLRSLCT). The new population selection has no selection rules.

• If the ID already exists on GLRSLCT without rules associated with it, the description is updated with the description you entered in parameter 4.

• If the ID already exists on GLRSLCT with rules, you'll receive an error message. The GLBDATA process terminates.

• To avoid a potential problem with GLBDATA adding duplicate IDs to POP SEL on GLAEXTR, use the following steps:

(a) Before running any popsel where you think you may have duplicate IDs, remove all records from GLBEXTR.

(b) Got to GLAEXTR, pull up POP SEL, and check the Delete All check box.

OR

Delete via SQLPLUS:

delete from glbextrwhere GLBEXTR_APPLICATION = 'MARK_TEST'AND GLBEXTR_SELECTION = 'SMITH'AND GLBEXTR_CREATOR_ID = 'SAISUSR'AND GLBEXTR_USER_ID = 'SAISUSR';commit;

(c) Run GLBDATA to get all the correct SYSTEM entry IDs.

(d) Run GLAEXTR and manually add those IDs you need to add, making sure to not to add any MANUAL duplicates as described above.


3 Processing

Creating a Manual Population

A population is a set of Banner IDs used for reports, processes, and letters. You can create a manual population with the Population Selection Extract Data Form (GLAEXTR).

1. Make sure the application associated with the population is defined on the Application Definition Rule Form (GLRAPPL). An application is a functional area that controls a population.

Note: Once defined, the application can be used repeatedly for every manual population associated with that application.

2. Make sure the population selection associated with the population is defined on the Population Selection Definition Rules Form (GLRSLCT). Because this is a manual population, you don’t need selection rules, just a name and description.

3. Access the Population Selection Extract Data Form (GLAEXTR).


5. Enter the population selection name in the Selection ID field. You can select the down arrow icon to access the Population Selection Inquiry Form (GLISLCT) to search for a population selection.

Note: If the population selection is locked, only the creator ID can create a population with the population selection.

6. Verify the Creator ID. The ID associated with the population selection is the default.


8. Enter each ID in the population. You can select the down arrow icon to access the Person Search Form (SOAIDEN) or the Non-Person Search Form (SOACOMP) to search for an ID. The Manual radio button is automatically selected to indicate the ID was added manually.

Note: Duplicate IDs cannot be added on GLAEXTR.


Task Note

No rules are associated with a manual population. Therefore, a manual population cannot be used in the Population Selection Extract Process (GLBDATA) to create a new population from the union, intersection, or minus of two population selections.


3 Processing

Letter Generation Procedures

With the Letter Generation module you can:

• Define the variables used to select a specific piece of data in the database.

• Build letters.

• Extract variable data from the database for a specific letter.

• Generate letters by merging the extracted variable data with a letter.

• Create a download file to merge with a Microsoft Word or WordPerfect text file.

Note: SunGard Higher Education does not support WordPerfect 8.0 or higher.

Before using these procedures, you should be familiar with the procedures described for the Population Selection module beginning on page 3-19.

SunGard Higher Education delivers and supports certain letters, variables, and population selections. Refer to the product-specific Banner user guides for additional information.

Note: The overall Letter Generation process is a powerful tool. The coding or modification of variables and population selections requires SQL-like code, which is considered site-specific customization that is not eligible for support.

Defining Variables

A variable is a specific piece of data in the database and the set of rules used to select that data. Variables are used to:

• Insert variable data into letters.

• Reference subqueries in application rules, population selection rules, and variable selection rules.

Each variable is associated with an application.

Creating a Variable

1. Make sure the application associated with the variable is defined on the Application Definition Rule Form (GLRAPPL). An application is a functional area that controls a variable.

2. Access the Variable Rules Definition Form (GLRVRBL).



3 Processing

4. Enter the variable name in the Variable field. The name must begin with an asterisk (*) and must contain at least one alpha character. The maximum number of characters is 30.

You can select the down arrow icon to access the Variable Inquiry Form (GLIVRBL) to see the variable names that already exist for the application.

Note: The same variable name can be used with different applications and defined with different rules.

5. Go to the Description block.

(a) Enter a free-form description of the variable in the Description field.

(b) (Optional) Select the Type of variable if special processing and updating of the database occur when the variable is used in a letter:

Checklist The value of the variable contains information regarding checklist items associated with an admissions application. For example, the Admissions Office uses this type of variable for applicants who need to send information to the institution to continue the admissions process. When you run the Letter Generation Print Report (GLRLETR) for a letter containing a checklist variable, the First Request, Last Request, and Count fields on the Student Checklist Table (SARCHKL) on the Admissions Application Form (SAAADMS) are updated for all checklist items for an applicant and term (parameter to GLRLETR) that have not been received yet and are indicated to print.

First The Letter Extract Process (GLBLSEL) processes this variable first. See “Defining a Variable with a First Variable Type” on page 3-41 for more information.

Manual You must enter all joins in the Rules block. See “Creating a Variable with ID Information Other Than the ID Receiving the Letter” on page 3-39 for more information.

RORVIEW The variable looks at one of the following Financial Aid views to determine its value:

ROVCSUM Third Party Contract Payment Detail ROVESUM Billing Exemption Payment Summary ROVSCRD Current Enrollment ROVSTOD Basic Student Selection ROVTHST Summary Academic History Level and Term

SelectionROVTRMG GPA By Term and Level Selection RPVARCO Contract Resource RPVAREX Exemption Resource RPVATRM Award by Term


3 Processing

Leave this field blank if none of these type applies.

6. Go to the Definition block. This is where you identify the data to be selected from the database.

Note: The system-generated Sequence fields identify the number of pieces of information being selected from the database. The first number defines the sequence number of the record currently displayed. The second number defines the total number of records defined for the variable (for example, 1 of 3).

(a) In the Select field, enter the database column from which data will be extracted, literal text, or a combination of both such as 'Dear' || SPRIDEN_FIRST_NAME || ',' . SQL functions (such as MAX or MIN) are allowed in the Select field. Database columns entered here are not validated against the data dictionary, so be careful to enter the names correctly. Use upper case.

You can refer to another variable in the Select statement as long as the variable is already defined and the rules are compiled under the same application as the variable that references them. You must also define a referenced variable in the letter so that the Letter Extract Process (GLBLSEL) can determine the value.

Note: You can model a more complex query on the following example:

Example where the same table is used in both the query and the subquery: SELECT DISTINCT(SPRIDEN_PIDM),SYSDATE FROM SATURN.SPBPERS A,SATURN.SPRIDEN WHERE SPBPERS_PIDM = SPRIDEN_PIDM AND SPRIDEN_LAST_NAME = 'Smith' AND SPRIDEN_CHANGE_IND IS NULL AND SPRIDEN_PIDM NOT IN (SELECT SPBPERS_PIDM FROM SATURN.SPBPERS WHERE SPBPERS_DEAD_IND = 'Y' AND SPBPERS_PIDM = A.SPBPERS_PIDM )

RPVTERM Applicant Award Term

Identifying a RORVIEW variable improves performance. The Letter Extract Process (GLBLSEL) populates RORVIEW with a record for each type RORVIEW variable in the letter.

Signature The value of the variable comes from the Initials Code Validation Form (STVINIT). This form maintains initials, descriptions, and titles for people. The initials associated with the value of the variable are placed in the Initials field on the Mail Table (GURMAIL) when the Letter Generation Print Report (GLRLETR) is run in update mode.


3 Processing

(b) In the From field, enter the names of all tables referenced in the Select field. Use the format <owner>.<table><alias>, separating multiple table names with commas. The owner is required only if your database contains multiple tables with the same name. You can use aliases to reference tables in subqueries within the variable selection rules. Aliases have a maximum length of four characters. Owner and table names are validated against the data dictionary.

To improve performance of the Letter Extract Process (GLBLSEL), list multiple tables in the From field from most general to most specific, or largest to smallest. For example, if two tables are being used, one with one record per ID and another with multiple records, list the multiple record table first.

(c) In the Order By field, enter the names of the database columns used to sort multiple records returned from the database. Use commas to separate multiple column names. These database column names are validated against the data dictionary. SQL functions (such as MAX or MIN) are not allowed with these field names.

(d) In the Group By field, enter the names of the database columns used to group multiple records returned from the database. Use commas to separate multiple column names.These database columns are validated against the data dictionary. SQL functions (such as MAX or MIN) are not allowed with these field names.

(e) In the Description field, enter an optional description of this selection within the variable. This is an 80-character field.

7. Go to the Rules block. This is where you enter the selection rules that determine how data is selected. PIDM join rules are not required except for a Manual type variable. The Automatic Letter Compilation Process (GLOLETT) adds the necessary PIDM joins for other variable types.

Note: Use open and closed parentheses to group nested statements for logical evaluation. You can use up to three levels of nested statements. The number of open parentheses on a line must equal the number of closed parentheses.

(a) In the Data Element field, enter the name of the database column used in the selection rule. The name must be a valid database column in the data dictionary. SQL functions (such as MAX or MIN) are not allowed with these column names.

To reference an object, enter *INCL followed by the object name (for example, *INCL AID_PERIOD). Then select Next Item. The rules from the AID_PERIOD object are automatically added to the variable rule. You can click the down arrow icon to access the Object Inquiry Form (GLIOBJT) to search for a valid object.

(b) In the Operator field, enter an SQL operator (=, <>, >, <, and so forth). The operator is used to compare the Data Element and Value fields.


3 Processing

For date comparisons, avoid using an equal sign (=) because dates are often stored with hours, minutes, and seconds. A better approach is to use less than (<), greater than (>), less than or equal (<=), or greater than or equal (>=). You might need an extra condition. For example, ACTIVITY_DATE is stored with hours, minutes, and seconds. Use these statements to find addresses changed on March 1, 2003:


(c) In the Value field, enter the value that is compared with the Data Element based on the Operator. This can be a constant literal, another database column name or alias, combination of a constant literal and database column name, dynamic parameter, or subquery. Use upper case.

Note: Do not enter a value if the Operator contains NULL or IS NOT NULL.

Constant literal: The data type of the Data Element determines the format of the literal. Values that are compared to character data elements must be enclosed in single quotes. Values that are compared to numeric data elements must be numeric. Values that are compared to date data elements must be in the format 'DD-MON-YY' or 'DD-MON-YYYY'. Single quotes are not used with SYSDATE. Use the operator AND between the ranges. For example, enter ‘01-JAN-03’ AND ‘31-JAN-03’. Use the same format for both years (YY or YYYY).

Note: The operator BETWEEN cannot execute dynamic parameters in a Selection ID or Variable. Dynamic parameters contained within single quotes are treated as literals.

Another database column name: The Value is validated against the data dictionary. If the data types (character, numeric, or date) of the Value and Data Element are not the same, a warning appears. You can override the warning and keep the comparison.

Dynamic parameter: Enter an ampersand (&) followed by text (for example, &Letter_Code). When you extract a variable with the Letter Extract Process (GLBLSEL), the system prompts for each dynamic parameter in the application rules and variable rules.

Subquery: Enter (*SUB<variable>). The parentheses are required. The literal *SUB indicates this is a subquery or a reference to another variable. The variable is a valid variable name already defined on the Variable Rules Definition Form (GLRVRBL) and compiled in this application. You can click the down arrow icon to access the Variable Inquiry Form (GLIVRBL) to search for a variable. If you select a variable from the list, the system gives it the proper syntax. A variable used as a subquery cannot have another subquery defined within it. A variable can have only one subquery. If defined, it must be the last rule.


3 Processing

8. In the AND/OR field, enter the connector that links rules with AND or OR logic. All lines in the Rules block, except the last line, must contain a connector.

9. Once all the rules are entered, save your changes.

Task Notes

• When using a dynamic parameter in a variable, the field that is being compared to the dynamic parameter should, if possible, be from the table that is used in the Select statement.

• When using a dynamic parameter with an IN or NOT IN operator be sure to include left and right parentheses. Do not include spaces when entering the value for the dynamic parameter. The following is correct:

88 EMAL_CODE (‘WWW’,’URL’)

• To improve processing time, certain criteria (such as whether a person is alive or has a current ID) should be specified through population selection rules rather than in variables.

• Columns from the Address View (SPVADDS) or any view using collector table records, cannot be concatenated with columns from other tables in the same Select statement on GLRVRBL. For example, Mr. John Smith cannot be extracted from a single variable because Mr. is the prefix being extracted from the Person Table (SPBPERS) and John Smith is the name being extracted from the Address View (SPVADDS). Creating two separate variables, one for the prefix and one for the name, and printing them together is a solution. A second solution would be to extract the name from the Identification Table (SPRIDEN) rather than the Address View. If the second solution is used, the prefix can be extracted in the same variable and concatenated to the name.

• A variable cannot have multiple sequences if the SPVADDS view is being used. The address variables must be broken into their component pieces such as street line 1, city, and state.

• Rules entered in the Rules block on the GLRVRBL Form are ignored for variables that select columns from the SPVADDS view.

Copying Variable Rules

You can copy the rules for an existing variable to create a new variable. A copied variable can be changed as needed.

1. Access the Variable Rules Definition Rules Form (GLRVRBL).

2. Enter the application associated with the variable you want to copy in the Application field.

3. Enter the variable you want to copy in the Variable field. You can select the down arrow icon to access the Variable Inquiry Form (GLIVRBL) to search for a variable.


3 Processing

4. To access the Variable Copy window, select Copy from the Options menu. Information in the Copy From block defaults from the main window.

5. Enter the application associated with the new variable in the Copy To Application field. You can select the down arrow icon to access the Application Inquiry Form (GLIAPPL) to search for an application.

6. Enter the new variable in the Copy To Variable field. The name must begin with an asterisk (*).

7. Save your changes. The main window reappears with the cursor in the Description field.

8. Use the normal steps to change and save rules for the new variable. You can use the steps in “Creating a Variable” on page 3-30, beginning with step 5.

Creating a Multiple-Sequence Variable

You can create a variable with multiple sequences. Each sequence can have its own definition elements such as Select, From, Order By, Group By, and selection rules. Situations when multiple sequence variables are valuable include:

• Bringing back a value for each sequence without creating multiple variables

• Bringing back a single value that depends on the characteristics of the ID

Bringing Back a Value for Each Sequence Without Creating Multiple Variables

It is sometimes easier and gives better results to create a single variable with multiple sequences than to create multiple variables. For example, you want to print an individual's first, last, and middle names on a letter in this format:

Last: SmithFirst: RonMiddle: James

You could create three variables, one for each part of the name. Another method is to create one variable with three sequences, one for each part of the name:

1. Enter Full Name as the variable description in the Description field.

2. Define the first variable sequence:

Sequence 1 of 3

Select 'Last: '||SPRIDEN_LAST_NAME


3 Processing

This sequence concatenates the text of ‘Last:’ with the value of the last name. Notice the rule to check that the current name record is accessed (SPRIDEN_CHANGE_IND IS NULL).

3. Define the second variable sequence:

This sequence concatenates the text of ‘First:’ with the first name. Again note the rule to check that the current name record is accessed.

4. Define the third variable sequence:

This sequence concatenates the text of ‘Middle:’ with the middle initial. You must enter the same rule on all sequences to ensure the current name record is returned. You have created only one variable. If an ID doesn’t have a middle name, the printed letter will not have a blank.

Bringing Back a Single Value That Depends on the Characteristics of the ID

A variable can sometimes return only one value for an ID, but, depending on the characteristics of the ID, the value could differ. For example, you’re sending the

From SPRIDEN

Data ElementOperatorValue

SPRIDEN_CHANGE_INDIS NULL

Sequence 2 of 3

Select 'First: '||SPRIDEN_FIRST_NAME

From SPRIDEN



Sequence 3 of 3

Select 'Middle: '||SPRIDEN_MIDDLE_NAM

From SPRIDEN



Sequence 1 of 3


3 Processing

same letter to both people and organizations. You could define, as a single variable, a variable that has either first and last name (if a person) or name (if an organization). But because an ID is a person or an organization (not both), you can use a multiple sequence variable.

1. Define the first variable sequence:

This sequence concatenates the first name and last name, with a space between, based on the rules established for the person. Notice the rule to check that the current name record is accessed (SPRIDEN_CHANGE_IND IS NULL).

2. Define the second variable sequence:

This sequence retrieves only the last name field because that is where the organization name is stored. Notice the rule that this sequence will be met only by IDs that are organizations (SPRIDEN_ENTITY_IND = ‘C’). Again note the rule to check that the current name record is accessed (SPRIDEN_CHANGE_IND IS NULL).

Sequence 1 of 2

Select SPRIDEN_FIRST_NAME||' '||SPRIDEN_LAST_NAME

From SPRIDEN




SPRIDEN_ENTITY_IND=‘P’

Sequence 2 of 2

Select SPRIDEN_LAST_NAME||'

From SPRIDEN




SPRIDEN_ENTITY_IND=‘C’


3 Processing

The rules on each sequence are mutually exclusive, so any ID meets the criteria of only one sequence. You have created fewer variables, which results in simpler letter definitions for determining whether a person or an organization is being processed.

Creating a Variable with ID Information Other Than the ID Receiving the Letter

Some variables have ID information other than the ID receiving the letter. Examples of this type of variable include:

• Spouse ID information

• Roommate ID information

• Employer ID information

• Advisor ID information

Rules for these variables are defined differently because they involve multiple IDs (PIDMS). Two conditions must exist:

• The variable Type must be defined on the Variable Rules Definition Form (GLRVRBL) as Manual. This means that all joins must be entered in the Rules block, including PIDM joins that automatically take place in other variable types.

• The first table in the From field must be the table that contains the column from the Rules block that references the PIDM receiving the letter. This is necessary for the Letter Extract Process (GLBLSEL) to correctly extract the data for the variable.

Sorting Variables

When you use the Letter Generation Print Report (GLRLETR) to produce letters directly in Banner, not through the download option, you may want to sort the letters by a variable such as name, ZIP code, or postal code. The GLRLETR process uses a sort parameter.

Sometimes you may want to sort on a variable that is not being printed in the letter by itself. For example, the variable for name might concatenate first and last name. You want to sort the letter by last name, which is not a variable being printed in the letter. Because the name variable is a concatenation of fields, it cannot be used as the sort variable. Here's how you can accomplish the task:

1. Use the Variable Rules Definition Form (GLRVRBL) to create a variable that is always NULL. This is a simple variable to create, and it controls logic flow in the letter:

• Enter *NULL_VAR in the Variable field.

• Enter Null Variable in the Description field.

• Enter two single quotes (’’) in the Select field.


3 Processing

• Enter DUAL in the From field.

• Don’t enter any rules for the variable.

2. Use the Paragraph Form (GUAPARA) to create a paragraph that includes:

• An ÎFNULL check on the *NULL_VAR variable.

• A branch around the sort variable. This branch prevents the variable from being printed but allows its value to be extracted by the Letter Extract Process (GLBLSEL) and used as a sort value by the Letter Generation Print Report (GLRLETR).

• The sort variable on a line by itself, between the check on the *NULL_VAR and the location to which the logic branches.

3. Use the Letter Process Form (GUALETR) to build a letter that includes the paragraph.

Example:

This sample paragraph checks to see if a null variable is null (which it will always be) and branches to another location, preventing the lines following the check from being printed:

This paragraph checks the value of *NULL_VAR, and if it is null, branches to the line that starts with &END_PARA. The variables between the ÎFNULL check and the &END_ PARA line are not printed in the letter. These variables must be listed because their values are used for other purposes (other variables have these variables in their Select statements).

Note: The *NULL_VAR must be listed even though it is in the ̂ IFNULL line. This is because the GLBLSEL process extracts data only for variables that start in position 1. To correctly process the ̂ IFNULL check on the *NULL_VAR, GLBLSEL must know the value of *NULL_VAR. The only way it can know the value is if it is on a line by itself like all other variables.

Creating a Hidden Variable

The Letter Extract Process (GLBLSEL) only extracts variables starting in column 1 and appearing on a separate line in the letter. To extract variables found within

ÎFNULL*NULL_VAR &END_PARA*NULL_VAR*BAMT*CAMT*ORES_AMT*ERES_AMT*CRES_AMT*RESOURCES*TERM01_TOTAL*TERM02_TOTAL*TERM03_TOTAL&END_PARA


3 Processing

another variable’s Select clause, or variables only referenced in ̂ IFNULL statements, the variables must be hidden on the letter:

• Define a variable that will always be null.

• Enter this variable on the letter just before all other variables to be hidden.

• Place an ^IFNULL condition above the dummy null variable. This causes the logic to skip around the null variable and hidden variables.

Defining a Variable with a First Variable Type

When the Letter Extract Process (GLBLSEL) is run, it must identify the variable it will process first to determine whether the ID should receive the letter. The first processed variable must return only one value for an ID, because it becomes the key of extracting the values of the other variables in this letter. If the first variable returns more than one value for an ID, then all other variables in the letter have that many values multiplied by the number of values it should have returned. Also, if the first variable returns no value for an ID, no other variable in the letter returns a value for that ID, and the ID does not receive a letter.

There are two ways to identify the first variable:

• Using the default first variable

• Defining the first variable on GLRVRBL

Caution: If there is no default first variable and no first variable defined on GLRVRBL, the first variable that GLBSLEL processes is unpredictable. The output of the variables in the letter can cause unexpected results.

Using the Default First Variable

The default first variable that GLBLSEL uses is a variable that defines an address using the SPVADDS view. This view contains one address per ID based on the address hierarchy entered for the address type parameters on GLBLSEL. This means that every ID receiving the letter being processed needs to have an effective address with an address type that matches one of the address parameter values entered during processing. If it does, then the SPVADDS variable returns one value per ID and the other variables in the letter return the correct number of values. If the ID does not have an effective address with an address type that matches one of the address parameter values entered during processing, no value will be in the SPVADDS view for the ID. The SPVADDS variable returns no value, and the ID does not receive a letter.

On the Variable Definition Rules Form (GLRVRBL), an SPVADDS_NAME variable is defined like this:


3 Processing

This variable retrieves the last name of the ID if the ID has an address of one of the address types entered for the address type (parameter 10) when you run GLBLSEL.

Defining the First Variable on GLRVRBL

Another way to identify the first variable that GLBLSEL processes is to define the variable type as First on the Variable Definition Rules Form (GLRVRBL). This variable, when used in a letter not containing SPVADDS - related variables, indicates that it is the first variable GLBLSEL should process.

Using a first type variable allows you to specify an address not necessarily found in the SPVADDS view. Some of the Banner products have specific address types that are to be used for a letter, and the first-type variable allows those addresses to be used. (Those address variables are probably defined using SPRADDR field names.)

In defining a first-type variable, two important items must be considered:

• The variable must be ID-related. That is, it must be a table where the ID has a record and it cannot be a variable that uses a non-PIDM table like DUAL or GUBINST.

• The variable must return only one value per ID. If more than one value is returned, all other variables in the letter will have multiple values. If no value is returned, the ID will not receive a letter.

If more than one variable in a letter is defined as first-type, there is no way to determine which one GLBLSEL will process first. However, if all first-type variables follow these two guidelines, it is not a problem to have multiple first-type variables in a letter.

Caution: Even if a first-type variable is used and no SPVADDS variable is used, the address type parameter on GLBLSEL must be entered with at least one value.

Example:

Sequence 1 of 1

Select SPVADDS_LAST_NAME

From SPVADDS

Sequence 1 of 1

Select SPRIDEN_LAST_NAME


3 Processing

SPRIDEN_CHANGE_IND IS NULL ensures that the current name record is accessed, not any previous last names. This guarantees that only one value per ID is selected.

Building Letters

1. Use the Letter Code Validation Form (GTVLETR) to create a letter code and description for the letter. You can identify whether duplicate letters are allowed.

2. Use the Paragraph Code Validation Form (GTVPARA) to create a paragraph code and description for each paragraph in the letter.

3. Use the Variable Definition Rules Form (GLRVRBL) to define the variables used in the paragraphs and build their associated selection rules. Examples include name, address, and salutations.

Note: The GLBLSEL process can handle up to about 121 variables per letter. The exact number depends on the length of the variable name; if you use shorter names you may be able to use more variables. This is controlled by the WS-PARM-LIST value in GLBLSEL.pco.

If you exceed the limit, you will receive the error message *ERROR* PREPARING PARM1 CURSOR . . . ABORTING SQLCODE = 0907, and GLBLSEL will abend.

4. Use the Paragraph Form (GUAPARA) to build individual paragraphs that can be used in letters. Paragraphs contain user-defined text, variables, and formatting commands (for example, underline and center). Whenever possible, build paragraphs that can be used in multiple letters.

5. Use the Letter Process Form (GUALETR) to build the letter. Identify the paragraphs in the letter and the sequence in which the paragraphs should appear.

From SPRIDEN



Sequence 1 of 1


3 Processing

Task Notes

• Letter Generation does not support the GOTO command. You can simulate this command by using the ̂ IFNULL condition on a variable that is always null.

• Variables whose data can contain a pound sign (#), such as the street line of an address, should be preceded by a #CL formatting command and followed by a pound sign. This prevents Letter Generation from treating the pound sign in the variable as a formatting command.

• A page break should exist at the top of each letter (after any table definitions) so that each copy of the letter starts on a new page. The page break should be in a paragraph by itself.

• If the letter will be created from a download file, the letter only needs to contain one paragraph. This paragraph must contain a list of the variables used in the letter. Text and formatting commands are ignored.

• If additional table definitions need to be used in a letter, all table definitions must be defined in a paragraph by themselves. This must be the first paragraph in the letter.

• Use caution if you use the SunGard Higher Education-delivered variable names in your own letters. The delivered variables have been created specifically for the SunGard Higher Education-supported letters and may need modifications in other letter extract selections.

Facility Oracle Report Formatting Emulation Commands

The following formatting commands can be used when building paragraphs on the Paragraph Form (GUAPARA). Formatting commands must appear on a line by themselves.

These conventions are used in following table:

• The word closed indicates that the command must be terminated by a pound sign (#) after the information about the command. For example, you must identify the last character of the text to be underlined by inserting a pound sign (#) after the last character to be underlined. The pound sign does not have to appear on a line by itself.

• The character x indicates text or variable information.

• The character n indicates a numeric value.

Code Description

#B Blank — Insert one blank line in the output text.

#CENxxx#

Center Text — Center the text or variable “xxx” in the current column. Closed.

#CL xxx#

Column Literal — Suspend formatting for all text or variables in the current column for #CL through #. Closed.


3 Processing

Note: Variables containing multiple sequence numbers will not format properly using the column literal. If you want this type of formatting, each sequence number must be a separate variable.

#CONCAT x Concatenate — Place x next to the preceding word without inserting a space between them. Frequently used to place punctuation after a variable.

Note: A backslash (\) is required to concatenate a period (.), for example:

*VARIABLE#CONCAT ,

*VARIABLE#CONCAT !

*VARIABLE#CONCAT \.

Note: A trailing space is required after the #CONCAT command and before the x string.

#CS n Column Skip — Skip n lines in the current column.

#CULxxx#

Center with Underline — Center and underline the text or variable xxx following the #CUL command within the current column. Closed.

Code Description


3 Processing

#DT n s1 e1 s2 e2 ...sn en # Define Table — Define the column boundaries for the specified table where n is the unique table number, s1 is the starting position of column 1, e1 is the ending position of column 1, and s2 through en are the starting and ending positions of other columns. The #DT command is similar to setting formatting lines and tab stops in word processing. Multiple tables can be defined within the same letter, but must be placed as the first paragraphs in the letter. They must be in a paragraph by themselves. #DT commands are the only commands that should precede the #NP command at the top of the letter.

Note: Make sure the first paragraph has only #DT commands. You will not receive an error message if the first paragraph is not a #DT paragraph, but the letter will not process.

A #DT, seq#1 paragraph is necessary when the letter contains a #T command. You do not need the #DT if the #T is not present.

Note: #DT is not required if the GLRLETR parameter 02, Word Processor Extract Option is 1 (Word) or 2 (WordPerfect). #DT is required if the GLRLETR parameter 02 is 0 (Banner).

Closed.

Note: IFNULL only works when you run GLRLETR for a Banner extracted letter (Word Processor Extract Option = 0). In addition, the download file will not contain paragragh text or literals.

#FR Flush Right — Justify both left and right margins. This is the default setting.

Note: When using #FR, large gaps may appear between words so that both margins align properly.

#I Indent — Indent all following text or variables in the current column. This is different from #P which only indents the first line.

#N New Line — Advance to the next line in the current column.

#NC New Column — Advance to the next column.

#NP New Page — End the current page and start a new page. To prevent page creep, the #NP command should be placed as the first command in a letter and should be the only command in a paragraph. It is preceded only by a paragraph with #DT commands.

#PAGE t b Page Boundary — Define the top and bottom page boundaries where t is the top line and b is the bottom line.

Code Description


3 Processing

#P Paragraph — Start a new line within the current column. Indent five spaces at the beginning of the line.

#R Right Justify — Set or reset the switch to right justify all text or variables in the current column.

#RR Ragged Right — Left justify all text or variables, but leave the right margin unjustified.

#S n Line Skip — Skip n lines.

#SPN t p sl bn sn # Start Page Numbering — Define page numbering where t is the type of numbering:

1 = Section Page Numbering [m-n] 2 = Letter Page Numbering [n - from page 2 onward]3 = Period Page Numbering [n]4 = Plain Page Numbering [n]

p is the character position where the number is printed; sl is the number of lines to skip after printing the number; bn is the number of the first output page; and sn is the section number if type 1 was selected. Closed.

#T n Table — Use the column rules for table n previously defined in the #DT command.

Note: Tables do not close when a new table is invoked. Remember to use the #TE command before invoking a new table.

#TE Table End — End one table before invoking another.

#TTL yxxx #

Title —Underline a specific title at the top of each page. y is the length of line to center. Closed.

If a new page formatting command (for example, #NP) is in the same letter as a title command, place the new page marker directly after the title command in the letter.

#UL CLOSED #UL Underline. Closed.

^IFNULL *VARIABLE &BRANCH If *VARIABLE returns a null value, skip all actions (text, variables, and formatting commands) up to &BRANCH. &BRANCH must be a label that begins with an ampersand(&), starts in the first position of a line in a paragraph, and is the only item on that line.

*VARIABLE is the variable to be checked for null values. *VARIABLE must also be identified elsewhere in the letter on a line by itself.

Code Description


3 Processing

Extracting Variables with GLBLSEL

The Letter Extract Process (GLBLSEL) extracts values from the database for the variables that appear in a specified letter. The extracted data is inserted into the Letter Collector Table (GLRCOLR).

You can run GLBLSEL from the Process Submission Control Form (GJAPCTL) or from the operating system.


You can process all pending letters (those waiting to be printed) for a specific letter code, or you can process the letter code for a specific population.

Note: If you process the letter code for a specific population, the population must be extracted with the Population Selection Extract Process (GLBDATA) before you run GLBLSEL.

1. If you are extracting variables for a specific population, make sure the population has been extracted with the Population Selection Extract Process (GLBDATA).


3. Enter GLBLSEL in the Process field.

4. If the process has more than one job parameter set, enter the name of the set in the Parameter Set field. You can click the down arrow icon to access the Job Parameter Set Rule Form (GJRJPRM) to search for a job parameter set.





3 Processing

Parameter Number

Parameter Value

1 Application Application associated with the letter being processed. This must be a valid application defined on the Application Definition Rules Form (GLRAPPL). This must be the same application associated with the population selection (if being used) and all variables in the letter. One application can be processed per run.

2 Process Pending Letters

Code that determines how the letter code is processed:

Y Process all pending letters for the letter code. See “Pending Letters” on page 3-52 for more information.

N Process the letter code for a specific population. The population must have been previously extracted with the Population Selection Extract Process (GLBDATA).

Note: If you are running GLBLSEL from the operating system, system prompts give you the ability to process all pending letters for the application or all pending letters for a specific letter code. If you are running online from GJAPCTL, you can only process pending letters for a specific letter code.

3 Letter Code Code of the letter being processed. This must be a valid letter defined on the Letter Code Validation Form (GTVLETR). One letter can be processed per run.

4 Selection ID ID of the population selection for which the letter is being processed. This must be a valid population selection defined on the Population Selection Definition Rules Form (GLRSLCT) and must be associated with the application entered in parameter 1. A population selection is required if parameter 2 is set to N.

5 Creator ID Oracle ID of the user who created the population selection. A creator ID is required if you entered a population selection in parameter 4.


3 Processing

6 User ID Oracle ID of the user who extracted the population with the Population Selection Extract Process (GLBDATA). A user ID is required if you entered a population selection in parameter 4.

Note: A population must exist for the combination of application, selection ID, creator ID, and user ID.

7 Term Code Code of the term for which you wish to process pending letters. This must be a valid code on the Term Code Validation Form (STVTERM). This parameter is used only if you are processing pending letters in the Student System. One term can be processed per run.

8 Aid Year Aid year for which you wish to process pending letters. This parameter is used only if you are processing pending letters in the Financial Aid System. One aid year can be processed per run.

9 Address Selection Date

Address date for which the address of choice must be effective. If blank, the current date is used.

10 Address Type Type codes of the addresses you wish to process, prefixed by the priority of each type code. The first character is the priority, and the second and third characters are the address type code from the Address Type Validation Form (STVATYP). For example, 1MA means the mailing address (MA) is the first choice; 2PR means the permanent address (PR) is the second choice. Enter each choice on a separate line.

Note: You can have up to 9 entries, and the valid priority numbers are 1 - 9. More than one entry can have the same priority.

11 Detailed Error Report

Y Write error messages to the glblsel.log file for IDs for which variable data could not be extracted.

N Do not write error messages to the log file.

12 Detailed Execution Report

S Display SQL statements.I Display SQL statements and inserts.Y Display paragraphs.

Parameter Number

Parameter Value


3 Processing



10. Select the Save function.

11. (Optional) If the letter contains variables with dynamic parameters, the cursor returns to the Parameter Values block. Enter values for the dynamic parameters in parameter 88. Select the Save function again.


Using the Operating System

Check with your technical personnel for the appropriate command to use at your institution. For example:

The parameters used if you are running from the operating system are similar to those used if you are running online from the Process Submission Control Form (GJAPCTL). The only difference is that you can process pending letters for all letter codes within an application. With GJAPCTL you are limited to processing pending letters for a specific letter code.


Task Notes

• GLBLSEL does not write a record to the Letter Collector Table (GLRCOLR) if the value of the variable selected is blank. For example, if the variable is a birthdate (*BDATE) and the person's birthdate is not on the system, no record is written for this person for birthdate. Only variables requested in the paragraphs contained in the letter are written to GLRCOLR.

• If you are processing pending letters and multiple applications are associated with the system indicator, GLBLSEL extracts the variables for the application entered as parameter 1 and not necessarily the application associated with the variables in the letters.

• If different pending letters use the same format table definitions (for example, DT #1), the formatting of the letters causes errors and indicates that the table is defined multiple times.

• Letters are not extracted unless an effective address is found for the person which meets one of the address types entered in GLBLSEL and a first type variable is not used. This applies to both pending and nonpending letters. If a letter could not be created because no address existed in SPRADDR for that ID

UNIX: glblsel.shl username passwordOpenVMS: @glblsel username password


3 Processing

or because an address was found, but it was inactive, Banner lists that person’s name and ID in the log file for GLBLSEL.

• When DATABASE is specified in the Printer field, GLBLSEL creates a .log for reviewing output, but not a .lis.

Pending Letters

Pending letters are letters that were created on the system-specific Mail Form (xUAMAIL) or created through a process but not yet printed. You can query pending letters or all letters for an ID, regardless of the Banner system, on the Mail Query Form (GUIMAIL). Check the appropriate Banner system documentation to determine which processes may create a pending letter.

GLBLSEL identifies pending letters as those letters on GUIMAIL that meet all of the following conditions:

• The Letter code on GUIMAIL matches the letter code entered as parameter 3 for GLBLSEL.

• The Term on GUIMAIL matches the term in parameter 7 for GLBLSEL (Student System only).

• The Initiated plus the Wait days on GUIMAIL is less than or equal to the current date.

• The Printed date on GUIMAIL is blank.

If you are running GLBLSEL from the operating system, you can also process pending letters for all letter codes within an application. Rather than checking for a match of the Letter code, GLBLSEL checks to make sure the System indicator on GUIMAIL matches the system indicator of the application in parameter 1.

Generating Letters from Banner with GLRLETR

The Letter Generation Print Report (GLRLETR) can generate letters directly from Banner. The system reads the paragraphs within a letter in the sequence specified. Text is formatted and printed. When a variable is encountered (identified by an asterisk and a variable name), the value of the variable name is extracted from the Letter Collector Table (GLRCOLR) and merged into the letter. When an RPF command is read, the letter is formatted as specified. The General Mail Table (GURMAIL) is updated.


3 Processing

Note: GLRLETR can also create a download file that can be merged with a word processing text file. See “Creating a Download File with GLRLETR” on page 3-58 for more details.

GLRLETR can be run through Job Submission or through the operating system.



1. Make sure the letter was built on the Letter Process Form (GUALETR).

2. If a population is being used, make sure the population was selected with the Population Selection Extract Process (GLBDATA).

3. Make sure variable data was extracted from the database with the Letter Extract Process (GLBLSEL).


5. Enter GLRLETR in the Process field.






3 Processing

Parameter Number

Parameter Value

1 Application Code

Application associated with the letter being processed. This must be a valid application defined on the Application Definition Rules Form (GLRAPPL). One application can be processed per run.

2 Word Processor Extract Option

Code that indicates whether letters are generated directly from Banner or created from a download file. Enter the value 0 to generate letters directly from Banner.

Note: If this option is 1 (Word) or 2 (WordPerfect), you do not need a #DT paragraph.

3 Process ALL Pending Letters

Code that determines what letters are printed:

Y Print all pending letters extracted for the application code. See “Pending Letters” on page 3-52 for more information.

N Print a specific letter code. This is the default value.

Note: Process ALL Pending Letters only works when the Word Processor Extract Option is 0 (extracted directly from Banner)

4 Letter Code Code of the letter being printed. This must be a valid letter code defined on the Letter Code Validation Form (GTVLETR). One letter can be processed per run.

5 Sort Variable Name of the variable used to sort letters in a specific order. The variable name must start with an asterisk (*). Use uppercase. Examples of sort variables are ZIP/postal code and name.

If the variable is not in the letter, no letters are printed and the Control Report indicates the sort variable is not valid.


3 Processing

6 Term Code Code of the term for which you wish to print letters. This must be a valid code on the Term Code Validation Form (STVTERM). One term code can be processed per run. This code is required if you are processing letters in the Student System.

Caution: If you are processing GLRLETR through Job Submission, this parameter is required regardless of the system. However, it is used only to process letters in the Student System.

7 Module Code One-character code that identifies the module associated with the letter being printed. Examples include A (Admissions), G (Gift/Pledge), C (Constituent), R (Recruiting), B (Billing), H (History), and F (Registration). This parameter is not validated.

GLRLETR updates the print date in the GURMAIL Table for published materials that match this module code. A list of the recipients and their materials is included in the report control information. Published materials are items that are sent to individuals, but are not printed by Letter Generation. Examples include college catalogs, sports brochures, and pre-printed forms.

Caution: This parameter is not required if you are processing from the operating system. A value is required, however, if you are processing from Job Submission. If updates should not be made for published materials, enter a module code that is not currently used.

8 Audit Indicator

Y Print one sample letter for each letter code extracted. No updates occur.

N Generate letters, generate a summary report, update the print dates for generated letters on the Mail Query Form (GUIMAIL), and delete all data in the Letter Collector Table (GLRCOLR) for the letters selected to print.

Parameter Number

Parameter Value


3 Processing




13. Print the letter using the operating system’s print command.

Using the Operating System

Use these steps to generate letters directly in Banner from the operating system:

1. Use the appropriate command for your institution. For example:

9 Free Format Date 1

Free-form date that is printed on the requested letter for variable *DATE1. *DATE1 can be a variable on a letter that is not built on the Variable Definition Rules Form (GLRVRBL); the value of this parameter becomes the variable value. The maximum length of this date is 30 characters.





12 Aid Year Code Aid year for which you wish to print letters. This must be a valid code on the Institution Financial Aid Options Form (ROAINST). This parameter is required if the application code in parameter 1 is associated with the Financial Aid System.

UNIX: glrletr -r userid/passwordOpenVMS: runproc glrletr -r userid/password

Parameter Number

Parameter Value


3 Processing

The resulting output file (glrletr.rpf) contains formatting commands and instructions, boilerplate text, and variable text that will be substituted in each letter.

2. Enter this command to format the results:

The resulting output file is named glrletr.lis. If you want to specify a different name for the output file, format the command like this:

3. Print the letter using the operating system’s print command.


Task Notes

• A letter is not generated for an ID if the letter code has a duplicate indicator of N on the Letter Code Validation Form (GTVLETR) and the ID already has an entry on the Mail Query Form (GUIMAIL) for the letter.

• A letter is not generated for an ID if Date Printed is not blank.

• If a checklist variable is used in a letter, the request dates and request count on the Admissions Checklist block of the Admissions Application Form (SAAADMS) are updated.

• If a variable name is found in a letter but does not exist on the extract file, nothing is printed. For example, if the letter is requesting some action by the person as of a certain date and the date parameters are not entered in the extract program, the text appears but the date does not. In this example, the date should appear after the word “by,” but the date does not exist:

Please send your transcript to my office by or you will be unable to register.

• Only one letter is created in a run for a letter code and person.

• If multiple items for a variable are extracted, the first value is printed and a line is skipped before the next value is printed. If there is a single value variable, no line is skipped.

In the following example, there is a single date and a single term. Multiple *CHKL variables have been extracted. The paragraph reads as follows:

Line 1: The following items are requested by

Line 2: *DATE1

Line 3: in order for you to register by

Line 4: *TERM

UNIX: guaprpf -f glrletrOpenVMS: runproc guaprpf -f glrletr

UNIX: guaprpf -f -o outputfilename glrletrOpenVMS: runproc guaprpf -f -o outputfilename glrletr


3 Processing

Line 5: #CONCAT \.

Line 6: #S 2

Line 7: *CHKL

Line 8: #S 2

Line 9: Thank you.

The result is:

The following items are requested by August 1, 2002 in order for you to register by Fall 2003.

0001 High School Transcript

0004 Tuition Deposit

Thank you.

Creating a Download File with GLRLETR

The Letter Generation Print Report (GLRLETR) can create a download file that can be merged with a text file created by certain word processors. Supported tools are Microsoft Word for Windows (version 2.0 or higher) and WordPerfect (version 4.2 or higher). This download option allows you to print letters using all available formatting, styles, and fonts of your word processor.

Note: SunGard Higher Education does not support WordPerfect 8.0 and higher.

GLRLETR can also generate a letter directly in Banner. See “Generating Letters from Banner with GLRLETR” on page 3-52 for more details.

The download option of GLRLETR creates two files:

• The download file contains a “header record” with all of the variables used in the letter and records for each ID in the population. The name of the download file depends on the run sequence number produced by job submission and ends with a .DOC extension. For example, GLRLETR_1234.DOC is a valid name, where 1234 is the run sequence number.

• A control report contains information about the letters that were processed. This information includes the number of “letters” produced, referring to the number of IDs that had data extracted.


Use these steps to create a download file:

1. Make sure the letter was built on the Letter Process Form (GUALETR).


3 Processing

Note: The letter only needs to contain one paragraph. This paragraph must contain a list of the variables used in the letter. (Text and formatting commands are ignored.) Variables must be defined on the Variable Definition Rules Form (GLRVRBL). Each variable must be entered on a separate line. The order of the variables does not matter.

2. If a population is being used, make sure the population was selected with the Population Selection Extract Process (GLBDATA).

3. Make sure variable data was extracted from the database with the Letter Extract Process (GLBLSEL).


5. Enter GLRLETR in the Process field.





Parameter Number

Parameter Value

1 Application Code

Application associated with the letter being processed. This must be a valid application defined on the Application Definition Rules Form (GLRAPPL). One application can be processed per run.

2 Word Processor Extract Option

Code that indicates whether letters are generated directly from Banner or created from a download file. Enter one of these values:

0 Letters are generated directly from Banner.

1 Produce an output file for Word.

2 Produce an output file for WordPerfect.


3 Processing

3 Process ALL Pending Letters

Code that determines what letters are printed:

Y Print all pending letters for the application code. See “Pending Letters” on page 3-52 for more information.

N Print a specific letter code. This is the default value.

Note: Process ALL Pending Letters is only valid when the Word Processor Extract Option is 0 (letters produced directly from Banner).

4 Letter Code Code of the letter being printed. This must be a valid letter code defined on the Letter Code Validation Form (GTVLETR). One letter can be processed per run.

6 Term Code Code of the term for which you wish to print letters. This must be a valid code on the Term Code Validation Form (STVTERM). This parameter is required if the application code in parameter 1 is associated with the Student System.

7 Module Code One-character code that identifies the module associated with the letter being printed. This code updates pending published letter codes in the GURMAIL Table with a print date and lists the information in the report control information. Examples include A (Admissions), G (Gift/Pledge), C (Constituent), R (Recruiting), B (Billing), H (History), and F (Registration). This parameter is not validated.

Parameter Number

Parameter Value


3 Processing



12. Save your changes. This creates a download file.

13. Use your institution’s procedures to merge the letter into your word processing environment. Check your word processor’s documentation for instructions on using the “mail merge” feature.

Note: The WordPerfect download file is a binary file. Make sure you indicate in your communication software that a binary file is being downloaded.

Task Notes

• When you produce a download file, you can produce only one letter (that is, one letter code) for a single run of GLRLETR. Each letter needs its own unique header record and, therefore, its own data file.

• The three date parameters (*DATE1, *DATE2, and *DATE3) are ignored if they are defined in the letter. The feature of entering dates dynamically can be accomplished in MS Word for Windows and WordPerfect (DOS version).

• The Mail Table (forms *UAMAIL) is updated when you use the extract option.

• Other GLRLETR processing performed when creating a letter in Banner (option 0) still occurs (such as signature variables and duplicate letter checking).

• IFNULL only works when you run GLRLETR for a Banner extracted letter (Word Processor Extract Option = 0). In addition, the download file will not contain paragragh text or literals.

8 Audit Indicator

Y Print one sample letter for each letter code extracted. No updates occur.

N Generate letters, generate a summary report, update the print dates for generated letters on the Mail Query Form (GUIMAIL), and delete all the data in the Letter Collector Table (GLRCOLR) for the letters selected to print.

12 Aid Year Code Aid year for which you wish to print letters. This must be a valid code on the Institution Financial Aid Options Form (ROAINST). This parameter is required if the application code in parameter 1 is associated with the Financial Aid System.

Parameter Number

Parameter Value


3 Processing

System Functions/Administration Procedures

The System Functions/Administration module lets you set up, operate, and monitor Banner. With this module you can:

• Establish currency conversions

• Set up and use electronic documents

• Set up events in the Event Queue Maintenance module

• Customize menus

• Customize toolbars

• Manage the Data Extract feature

• Create and use QuickFlows

• Set up Value-Based Security with Fined-Grained Access Controls

• Set up and use Common Matching

• Enable Messaging/Events processing for your institution

Establishing Currency Conversions

Banner can process foreign currencies. The base currency for your institution, referenced on the Institutional Description Table (GUBINST), is used in all foreign currency calculations. The currency codes, with daily or periodic rates, are maintained on the Currency Code Maintenance Form (GUACURR).

Currency conversions are used in the Purchasing and Procurement, Accounts Payable, and General Ledger modules of the Finance System. Unless otherwise specified, amounts are entered in the installation's base currency that is referenced on the Installation Control Form (GUAINST). When dealing with a foreign currency, you can enter a currency code in the Currency Code field. The system automatically calculates the converted amount (entered amount divided by the exchange rate). Refer to the Banner Finance User Guide for additional information.

To process transactions in a foreign currency, the associated currency code (for example, DM for Deutsch Marks) must be defined on the Currency Conversion Validation Table (GTVCURR). You can produce statements or invoices in foreign currencies.

1. Determine which foreign currencies are used at your institution.

2. Use the Currency Code Maintenance Form (GUACURR) to create your currency records. This updates the Currency Conversion Validation Table (GTVCURR).


3 Processing

Creating Bank Information

The Bank Code Rule Form (GXRBANK) is used to:

• Define bank codes for you institution’s bank accounts

• Link bank funds and bank accounts with your cash accounts

• Define Automatic Clearing House (ACH) information for your institution’s bank accounts

The first two actions are performed on the main window of GXRBANK. ACH information is entered on the ACH Rules window of the form.

You can create several records for a particular bank code. Only one record per bank code is valid for a defined effective date range. Each record, however, can be distinguished by a different bank name.

As illustrated in the procedures below, new bank codes are defined in data entry mode; and additional records for a previously defined bank code are accessible in query mode. Any modifications to existing bank records must be done after executing a query.

Defining a New Bank Code

1. Access the Bank Code Rule Form (GXRBANK). The system displays a message indicating that the form is in query mode. Select OK.

2. Enter the bank code in the Bank field.

You can use the down arrow icon to access a list of previously defined bank codes. If more than one bank name exists for the same bank code, use the down arrow to view other bank names with that code.

3. Enter the name to be associated with the bank code in the Name field.

4. Select the Active Status check box if the bank is available for use within Banner. Clear this check box if the bank is not active.

5. Enter the effective date of the bank record in the Effective Date field. The default value of this field is today’s date. This value can be changed.

6. (Optional) Enter the date that the bank code record is no longer valid in the Termination Date field. You can enter a past or future date.

Note: If you want a bank code to be valid for only a certain length of time, you can enter an effective date (when you can start using the bank code) and a termination date (when the bank code can no longer be used).


3 Processing

7. (Used only by Banner Finance) Enter the currency code for this bank in the Base Currency field, e.g., USD may represent U.S. dollars. You can double-click in the field to access the Currency Code Validation Form (GTVCURR) and search for a currency code.

8. Enter the identification number for the bank in the Bank ID field. You can select the down arrow icon to access the Non-Person Search Form (SOACOMP) and search for a bank ID.

Note: When you save a bank code, Banner creates an identification record in the Identification Table (spriden) for the bank ID and bank name. Use the Identification Form (FOAIDEN for Finance or PPAIDEN for Human Resources) to update existing bank names.

9. Enter the bank account number in the Bank Account Number field.

If the bank code you’re defining is to be used with the Banner Finance System, identify the Banner bank funds and bank accounts associated with your cash account. (See the Linking Bank Funds and Bank Accounts with Cash Accounts sub-procedure below for instructions on providing this information.)

10. Select the ACH Status check box if the ACH functionality is active for the bank. Clear this check box if it isn’t.

If you selected the check box, you must specify the information required for sending direct deposit tapes from your bank to the Automatic Clearing House (ACH). (See the Creating ACH Information for a Bank Account sub-procedure below for instructions on providing this information.)

If you did not select it, continue to step 11.

11. Save the record.

Linking Bank Funds and Bank Accounts with Cash Accounts (For Finance Only)

This sub-procedure of the Defining a New Bank Code procedure is used to identify the Banner Finance bank funds and bank accounts to be associated with the bank code. You must perform all the steps in this sub-procedures if the bank code you are defining will be used with the Banner Finance System. Perform these steps after performing step 9 of the main procedure.

Note: The fields referenced in the sub-procedure are active and navigable only if the Banner Finance System is installed at your site.


3 Processing

Sub-Procedure

1. Enter the code identifying the Chart of Accounts (COA) for the Banner accounts in the Chart of Accounts field. You can double click in the field to access the Chart of Accounts List (FTVCOAS) and search for a COA code.

2. Enter the code identifying the bank fund (that is, the account that represents the accumulation, or total, of all your institution’s cash accounts) in the Bank Fund field. You can double click in the field to access the Fund Code Validation Form (FTVFUND) and search for a bank fund.

3. Enter the code identifying the account used for cash transactions in the Cash Account field. You can double-click in the field to access the Account Code Validation Form (FTVACCT) and search for an account code.

4. Enter the code identifying the interfund account in the Interfund Account field. The interfund account acts as an intermediate account that can hold money temporarily before the money is sent to the final destination accounts.

5. Go to step 10 of the Defining a New Bank Code procedure.

Creating ACH Information for a Bank Account

This sub-procedure of the Defining a New Bank Code procedure is used to specify the information required for sending direct deposit tapes from your bank to the Automatic Clearing House (ACH). This information must be defined for a bank account if funds are to be transferred from that account to another account. It is sent with the direct deposit tapes submitted to your bank. The information is available from your bank or clearing house.

Performs the steps in this sub-procedure after performing step 9 in the main procedure.

Sub-procedure

1. Access the ACH Rules window of GXRBANK by selecting ACH Rules from the Options menu.

2. Enter the routing number of the ACH operator or receiving point to which the direct deposit files are sent in the Destination ID field.

3. Enter the name associated with the destination ID in the Destination Name field.

4. Enter the routing number of the ACH operator or sending point that is sending the direct deposit files in the Origin ID field.

5. Enter the name associated with the origin ID in the Origin Name field.


3 Processing

6. Enter the short name to be associated with the origin ID in Short Name field. The default short name comes from the Origin Name field; it matches the first 16 characters in this field. This value can be overridden.

Note: The name entered in this field will be used as the origin name for a Canadian magnetic tape deposit.

7. Enter the routing number of the Deposit Finance Institution originating entries in the Originating Bank Routing Number field.

8. Complete the Organization Number Type field by selecting the radio group entry identifying the type of identification number that your institution uses for direct deposit processing.

9. Enter your institution’s identification number for direct deposit processing in the Organization ID Number field. Enter a number of the type specified in the Organization Number Type field.

10. Save the record.

Updating Bank Code Records

Any updates to bank code records (i.e., the creation of new records or modifications to existing records) must be done upon executing a query. Procedures for updating bank code records follow:

1. Access the Bank Code Rule Form (GXRBANK). The system displays a message indicating that the form is in data entry mode. Select OK and go to step 2.

Note: To determine whether records currently exist for a particular bank code, use the down arrow icon for the Bank field to access a list of previously defined bank codes. If more than one bank name exists for the same bank code, use the down arrow to view other bank names with that code. Do this before performing step 2.

2. Enter query mode.

3. Enter the bank code for the record you want to modify or duplicate.

4. Execute the query.

5. If additional records have previously been created for the bank code, scroll through the records until the version that you want to modify or duplicate is displayed.

Note: If a more recent record exists, its date is displayed in the Next Change Date field.

If you want to modify the displayed record, go to step 7. If you want to create a new record, go to step 6.


3 Processing

6. Duplicate the displayed record.

7. Make your changes on the original or duplicated record.

8. Save the record.

Setting Up and Using Electronic Documents

Setting Up Electronic Documents

Business analysts create your institution’s electronic documents. Each institution’s policies are different, so electronic documents vary among institutions.

Before creating the document, plan how you want it to look and which Banner fields it should contain. Determine which fields are required, and what, if any, default values you want to use. These properties are assigned on the Electronic Documents Builder Form (GORWFDB) in step 4 below, but it is best to plan them in advance.

To create an electronic document, you must complete the following steps. A detailed description of each step follows this list.

1. Establish a document type code for your electronic document.

2. Import the Banner forms that contain the fields you want to use on it.

3. Review and manipulate the field data on a metadata level.

4. Build the electronic document and assign properties to all its labels and fields.

5. Grant super user authority to the appropriate users.

6. Test the electronic document.

Establishing a Document Type Code

1. Access the Electronic Documents Validation Form (GTVWFED).

2. Enter an Electronic Document Type code and Description.

3. Select the Save function.

Importing Banner Forms

Electronic documents contain fields from Banner forms (in addition to user-defined fields). The forms must be imported before the fields can be used.

1. Access the Electronic Documents Wizard Form (GOAWFIZ).

2. Click Next> on the splash screen.


3 Processing

3. Click the Banner forms that contain fields you want to include on your document. You can scroll through the form names or use query functionality to search for them. If a form has already been imported, a checkmark appears in the Previously Setup check box. If the check box is selected, you do not need to import the form again.

4. Click Next>. The selected forms are imported.

5. On the last screen of the wizard, click the Finish button.

Note: You can click Cancel at any time to leave the wizard.

The importing process has concluded. You can use any of the fields from any of those forms in your electronic documents, or from any forms that were previously imported.

Reviewing and Manipulating Metadata Information

Now you can begin to look at the fields rather than just at the forms. You need to inspect the metadata information and make any necessary changes.

Note: Metadata is “data about data.” In this step you are reviewing data about fields. For example, you can review the length, value range, and format mask of individual fields on an imported form.

1. Access the Electronic Documents Dictionary Form (GORWFDD).

2. Enter the Application Name.

3. Perform a Next Block function. Each field from the form is listed on the left, and data about the currently highlighted field is displayed on the right. Scroll through the fields and make any necessary changes, such as altering default values, setting up code/description functionality, and setting up lists of values (LOVs).


Your changes are stored with the field data in the Data Dictionary, and are used whenever the field is used. No changes made here affect the original Banner tables.

Building the Electronic Document

Now you can build the electronic document. You will lay out the fields, establish properties for each field, and specify the order in which Banner forms will appear during the apply process.

1. Access the Electronic Documents Builder Form (GORWFDB).

2. Enter the Document Code you created on the Electronic Documents Validation Form (GTVWFED), or double-click the field to see a list of the codes and select one.


3 Processing

3. Perform a Next Block function.

4. Enter a label in the grid where you want it to appear on the electronic document.

5. Click the Properties button to see the Properties window.

6. Verify that the Cell Type is Label and click the OK button.

7. Put your cursor in the cell next to the label and click the Properties button.

8. Verify that the identifier for the correct cell (for example, A2) appears in the box at the top of the window.

9. Enter the properties for the cell, including its length, default value, whether it is validated or calculated, and Help text.

Note: If you enter the Database Target Name, some fields display default values.

10. Click the OK button.

11. Fill in the rest of the grid with labels and fields, defining properties for them on the Properties window. Your document can have more than one sheet, if necessary. Save often.

Note: If a field asks a yes or no question with no direct link to a database, you must include the Banner form on the Application Apply Order window in the proper order. Otherwise, the form will not appear automatically during the apply process.

12. Click the Apply Order button to access the Application Apply Order window,

13. Define the order in which the Banner forms will appear when the applier begins updating the databases.


15. When your document is complete, save your changes.

This is the longest and most complex part of the process. If you invest time in the planning process, though, it will be easier.

Setting Up the Code/Description Lookup Feature

When you build your electronic document, you can set up some fields to use the code/description lookup feature included in Banner.

To include this feature in your electronic document, you must set it up on both the Electronic Documents Dictionary Form (GORWFDD) and on the Electronic Documents Builder Form (GORWFDB). Both forms must be set up for the code and for the corresponding description.


3 Processing

Use these steps to set up the electronic document on the Electronic Documents Dictionary Form (GORWFDD):

1. Scroll down until the Element Name that represents the code is highlighted.

2. Enter the appropriate information for the List Name, Table Name, Column Code Name, and Column Desc Name fields. Although the wizard automatically populates most of the information on GORWFDD, you may have to enter this information.

3. Scroll down until the Element Name that represents the description is highlighted.

4. Enter the appropriate information for the List Name, Table Name, Column Code Name and Column Desc Name fields.

Use these steps to set up the electronic document on the Electronic Documents Builder Form (GORWFDB). If all the information has been entered on GORWFDD, this is easy.

1. Place your cursor in the field for the code.

2. Click the Properties button.

3. Enter the following on the Properties window:

• Cell Type must be Text.

• Application Name must be the Banner form that holds the code.

• Application Target Name must be the field in the form that holds the code and description.

The rest of the necessary information is displayed automatically. It is not necessary to add anything in the Event API block.

4. Click the OK button to leave the Properties window.

5. Place your cursor in the field for the description.

6. Click the Properties button.

7. Enter the following on the Properties window:

• Cell Type must be Display

8. Click the OK button to leave the Properties window.

Granting Super User Authority

All users have access to electronic documents in which they play a part, by initiating the document, approving it, or applying its data to the Banner databases. Any users that need super user access must be set up separately.


3 Processing

1. Access the Electronic Documents Security Form (GORWFDS).

2. Enter the User ID, or click the down arrow icon to see a list of valid users and select one.


4. Enter the code for your document in the Document Type field, or double-click the field to see a list of the codes and select one.

5. Select the Update check box to give the user update access to the document.


Testing the Electronic Document

1. Access the Electronic Documents Form (GOAWFED).

2. Click the Create a New Document button.

3. Enter your code in the Document Type field, or double-click the field to see a list of the codes and select one.

4. Enter a description in the Transaction Description field.

5. Perform a Next Block function. Your new document appears.

6. Test the document to make sure all the validations and calculations work correctly.

Using Electronic Documents

You can use electronic documents in Banner alone or with Workflow. The main difference is that you never click the Workflow Submit button if you are using electronic documents outside Workflow; you just save the transaction. For details on using electronic documents with Workflow, refer to the Workflow documentation.

The standard role-level security used throughout Banner is used here as well. Users must be granted update access to the forms and underlying system tables.

When a user initiates a transaction, the user ID is stored with the transaction number. Banner gives users access to transactions they initiated, updated, reviewed, and approved.

Creating an Electronic Document Transaction

1. Access the Workflow Electronic Documents Form (GOAWFED).

2. Click the Create a New Document button.


3 Processing

3. Enter the Document Type, or double-click the field to see a list of the codes and select one.

4. Enter the Transaction Description. It is helpful if the description is unique for your transaction (for example, John Smith; New Hire).

5. Perform a Next Block function. The Transaction # is generated automatically by the system, and the Status is Hold.

6. Fill in all the necessary fields. You can click the down arrow icon to see valid values, depending on how the fields were set up. Any help text for the fields appears on the status bar. Some fields may be validated; you may receive an error message if you enter an invalid value, depending on how the fields were set up.

7. (Optional) Use the arrow buttons on the navigation bar to see how many sheets the document has. You can move between sheets by clicking the appropriate arrow buttons.

8. (Optional) To add comments, click the Comments button. Enter your comments in the Current Comments field and click the OK button. Any comments are stored with the transaction.

9. (Optional) If you are not finished but want to leave the document for a while, save the data. Be sure to note the transaction number — you will need to enter it to open the transaction again. Exit the form.

10. When you are finished, click the Complete button. If you have filled in all the necessary fields, the Status changes from Hold to Pending. Otherwise, the status changes to Waiting.

Reviewing and Changing an Existing Transaction

1. Access the Electronic Documents Form (GOAWFED).

2. Click the View/Update Existing Document button. The form is displayed with the cursor in the Transaction # field.

3. Enter the transaction number or click the down arrow icon to see a list of transactions and select one. (The only transactions you can see with the down arrow icon are ones you initiated, updated, approved, or applied, unless you are a super user.)


5. Enter your changes as with a new transaction. Enter comments as necessary.

6. When all the fields have been entered, click the Complete button. If you have filled in all the necessary fields, the Status changes from Hold to Pending. Otherwise, the status changes to Waiting.


3 Processing

Returning a Transaction for Correction

If you are an approver, you can return a transaction for correction if it is not completed correctly. For example, a transaction may contain incorrect data, even though the originator filled out all the required fields with valid values.

1. Open the transaction on the Electronic Documents Form (GOAWFED).

2. Click the Comment button to open the Comments window. Explain why you are returning the transaction in the Current Comments field.


4. Click the Return for Correction button. The transaction status is now Returned.

Approving/Disapproving a Transaction

If your role makes you an approver, you can review a transaction and approve or disapprove it. If you and all the other approvers approve a transaction, its status becomes Approved. If you or one of the other approvers denies the request, its status becomes Disapproved.


2. If you are approving the transaction, click the Approved button.

OR

If you are denying the request, click the Disapproved button. You may want to add a comment on the Comments window:

• Click the Comment button to access the Comment window. Explain why you are disapproving the transaction in the Current Comments field.

• Click the OK button.

Applying Data to the Databases

When a transaction is approved, the data must be applied to the Banner databases. You must copy or enter the appropriate information into the different Banner forms as they appear.

Note: When an electronic document is created, the business analyst specifies which Banner forms will appear during the apply process, and in what order. Some fields in the document may not have been used. You do not need to access the forms that contain those fields.

Use the following steps to apply data by accessing all forms in order:


2. Click the Start Apply Process button. The first Banner form appears.


3 Processing

3. Click the Open Electronic Document button on the toolbar to display the Electronic Documents Form (GOQWFED). This form is identical to GOAWFED, which has the same name. You can toggle between the transaction containing the approved data and the form where the data should be entered by choosing them from the Window pull-down menu.

4. Enter the appropriate data from the electronic document, and any additional information that may be needed. You can copy and paste information from the transaction.

5. Save your changes and exit the form.

6. The next form appears. Enter the data as before, save your changes, and exit the form.

7. Continue until you have entered data into all the forms. After you have viewed all the forms, the Apply Order window appears. Each form listed is checked, even if you did not enter any data on that form.

8. Click the OK button. The status of the transaction becomes Applied.

Use the following steps to apply data by accessing selected forms:


2. Click the Selected Apply button. A window appears with all the Banner forms listed in order. You can choose which forms you want to see, one at a time. You must access the forms in the order listed — if you skip a form you cannot return to it.

3. Find the first form you want to access, and click the Select to Apply button to the left of it. If you realize you need to access all of them, click the Apply All button to access the forms in order. The selected form appears.

4. Click the Open Electronic Document button on the toolbar to display the Electronic Documents Form (GOQWFED). This form is identical to GOAWFED, which has the same name. You can toggle between the transaction containing the approved data and the form where the data should be entered by choosing them from the Window pull-down menu.

5. Enter the appropriate data from the electronic document, and any additional information that may be needed. You can copy and paste information from the transaction.

6. Save your changes and exit the form. The window with Banner forms listed in order reappears. The form you just updated has a checkmark in the Applied column.

7. Choose another form, if necessary. Enter the data as before, save your changes, and exit the form.

8. Continue until you have entered all the data.


3 Processing

9. Click the OK button. The status of the transaction becomes Applied.

Once the status of a transaction changes to Applied, the transaction cannot be changed. It can be viewed by the users that created, updated, approved, or applied it, and by super users.

Setting Up Events in the Event Queue Maintenance Module

An event is a Banner database change that potentially triggers another action in an external system. For example, a clerk in the Registrar’s Office cancels a class using a Banner form. This triggers an event for each student registered for that class. The same cancellation event could also be sent to Workflow, which might initiate a workflow that cancels the faculty member’s teaching contract and removes any job records associated with that contract.

The Event Queue Maintenance module within Banner General supports the event queue processing required by Campus Pipeline/Luminis, Workflow, and potentially other external systems.

Use these steps to set up an event:

1. Use the Target System Code Validation Form (GTVEQTS) to define the external systems that require notification when an event occurs.

2. Use the Event Queue Code Validation Form (GTVEQNM) to define the events that will be captured and sent to external systems.

3. Use the Parameter Code Validation Form (GTVEQPM) to define the parameters that are associated with events.

4. Use the Parameter Group Code Validation Form (GTVEQPG) to define the parameter groups that can be associated with events.

5. Use the Parameter Group Rule Form (GOREQPG) to assign defined parameters to a groups.

6. Use the Event Queue Name Definition Form (GOREQNM) to define specific events for the target systems. This definition includes associating a parameter group with each event.

Refer to Integrating Banner or Plus With Partner Systems for more details on event processing for Campus Pipeline.

Refer to Using Workflow With Banner: Getting Started Guide for more details on event processing for Workflow.


3 Processing

Customizing Menus

Your institution can create new menus and customize the contents of the menus delivered with Banner. In addition, each user can create a customized, personal menu tied to the Oracle user ID and make minor changes to the appearance of the main menu.

Note: All menus must be placed on an existing menu structure that branches out from *MAIN.

Creating and Maintaining Menus for Your Institution

Banner is delivered with the following menus:

You can use the Menu Maintenance Form (GUTGMNU) to create new menus and customize the contents of menus for your institution. A menu can contain any combination of forms, jobs, other menus, and QuickFlows.

Creating a New Menu Using the List of Objects

Use these steps to create a menu by choosing objects from a displayed list of objects.

1. Access the Menu Maintenance Form (GUTGMNU).

2. Enter the new menu name, menu description, and system identifier in the three fields above the right pane. Remember that a menu name must start with an asterisk (*).

Menu Description Menu Name

Manage the Enterprise *PROCESS1

Matriculate to Educate *PROCESS2

Forecast to Enroll *PROCESS3

Plan to Fund *PROCESS4

Student System *STUDENT

Alumni/Development System *ALUMNI

Finance System *FINANCE

Human Resources System *HRS

Financial Aid System *RESOURCE

General System *GENERAL


3 Processing

3. Use the pull-down list above the left pane to select the object type you want to display. The left pane lists the objects of the selected type that can be added to the menu.

4. (Optional) To query for specific objects:

(a) Click in the left pane.

(b) Select the Enter Query function. The object list disappears.

(c) Enter the search criteria for the object description.

You can use the Oracle wildcards % and _. Capitalization matters. Data is matched against the search criteria exactly as you enter them.

(d) Select the Execute Query function. The left pane lists the matching objects.

5. To add all objects displayed in the left pane to the menu (if there are 20 objects

or less), select the Insert All button in the middle of the form .

6. To add selected objects to the menu:

(a) In the left pane, select each object you want to add to the menu. When you select an object, the name is highlighted.

Note: As you move the cursor over an object description, its seven-character name is displayed.

Note: You can highlight and right-click a menu name or QuickFlow name to list the items associated with that object.

In Internet-native Banner, you cannot use the right-click function; it is not supported by Oracle at this time. Use Key-Next-Block instead.

(b) (Optional) Use the pull-down list above the left pane to select another object type. Select additional objects for the menu. (You can select objects from multiple object types and insert them together.)

(c) Click in the right pane where you want to place the new menu items.

(d) Select the Insert Selection button in the middle of the form . The selected objects are added to the right pane below the place you clicked.

7. (Optional) Customize object descriptions.




3 Processing

Creating a Menu Using Object Names

Use these steps to create a menu if you know the object names you want to appear on the menu.


2. Enter the new menu name, menu description, and system identifier in the three fields above the right pane. Remember that a menu name must start with an asterisk (*).

3. Place the cursor in a blank Name field in the right pane.

4. Enter the object’s seven-character name.

5. Press Enter. The object’s type, description, and name appear in the right pane.

6. Repeat steps 3 through 5 for each object you want to add to the menu.

7. (Optional) Customize the object descriptions.



Maintaining an Existing Menu (Additions, Deletions, and Changed Sequence)


2. Enter the menu name in the left-most field above the right pane (field to the left of the down arrow icon). You can click the down arrow icon to access the Object Search Form (GUIOBJS) to search for a menu name.

3. Click in the right pane. All existing menu items appear.

4. Click the selected menu item so it is no longer selected.

5. To add objects to the menu:

(a) Use the pull-down list above the left pane to select the object type you want to display. The left pane lists the objects of the selected type.

(b) (Optional) To query for specific objects, click in the left pane. Select the Enter Query function. The object list disappears. Enter the search criteria for the object description. (You can use the Oracle wildcards % and _. Capitalization matters. Data is matched against the search criteria exactly as you enter them.) Select the Execute Query function. The left pane lists the matching objects.

(c) In the left pane, select each object you want to add to the menu. When you select an object, the name is highlighted.


3 Processing

Note: As you move the cursor over an object description, its seven-character name is displayed.

Note: You can highlight and right-click a menu name or QuickFlow name to list the items associated with that object. In Internet-native Banner, use Key-Next-Block instead of the right-mouse-click.

(d) Repeat steps a through c for each object type you want to add to the menu. (You can select objects from multiple object types and insert them together.)

(e) Click in the right pane where you want to place the new menu items.

(f) Select the Insert Selection button in the middle of the form . The selected objects are added to the right pane below the place you clicked.

(g) (Optional) Customize the object descriptions.

6. To delete selected objects from the menu:

(a) In the right pane, select each object you want to delete from the menu. When you select an object, the name is highlighted.

(b) Select the Remove Selection button in the middle of the form . The selected objects are deleted.

7. To delete all objects from the menu, click the Remove All button in the middle

of the form .

8. To change the order of objects on the menu:

(a) Use the tasks in step 5 to add the object to its new location.

(b) Use the tasks in step 6 to delete the object from the old location.


Note: If you add an object to a menu, all objects on the menu are processed, not just the new ones. The transaction count on the status line includes all menu items.

Deleting a Menu


2. Enter the menu name in the left-most field above the right pane (field to the left of the down arrow icon). You can select the down arrow icon to access the Object Search Form (GUIOBJS) to search for a menu name.

3. Select the Delete Record function. A dialog box asks if you really want to delete the menu.


3 Processing

OR

Click in the right pane. All existing menu items appear. Select the Remove All

button in the middle of the form . Save your changes. A dialog box asks if

you want to delete the menu.

4. Select the Yes button.


Creating and Maintaining Personal Menus

Individual users can create personal menus that include the forms, jobs, menus, and QuickFlows that are most important in their daily work. A personal menu is tied to the user’s Oracle user ID and can be accessed from the main menu (under My Banner).

Note: Objects must be added to GUAOBJS properly before they can be used on on any of the menus.

You can use these forms to create and copy personal menus:

• Personal Menu Maintenance Form (GUAPMNU). Lets a user create and change a personal menu.

• Personal Menu Maintenance and Copy Form (GUTPMNU). Lets a user copy a personal menu to or from another user.


Changing the Appearance of the Main Menu

Individual users can make the following changes to the main menu:

• Sizes of the left and right panes

• Show or hide the 7- or 8-character form mnemonics

• Order of items in the right pane

Managing the Data Extract Feature

Banner is delivered with the Data Extract feature enabled on most validation forms. With this feature, you can extract data from a Banner form to a spreadsheet. You can extract detail data from the current block with or without data from the key block.

SunGard Higher Education also supports the extract feature on a limited number of rule, application, and inquiry forms where the feature has been tested. The system administrator at your institution can enable the extract feature on any form


3 Processing

that has been tested. For a list of tested forms, refer to chapter 3 of the Banner Getting Started Guide.

Note: Extract results are unpredictable on forms that have not been tested with this feature. If you want to extract data on an untested form, you can consider enabling the extract feature on GUAOBJS. SunGard Higher Education does not support this feature on untested forms. SunGard Higher Education will, however, continue to test more forms and expand support with future releases.

Note: WebUtil offers another way to save extracted data in Banner. Information about configuring WebUtil is contained in the Middle Tier Implementation Guide.

Enabling the Data Extract Feature for a Form

Caution: If you wish to enable the extract feature on local forms, you must test the extract feature on them before you enable the feature on GUAOBJS.

1. Access the Object Maintenance Form (GUAOBJS).

2. Select a value from the pull-down list in the Data Extract Option field:

Key and Data Block Enable the extract feature for both key and data blocks.Data Block Only Enable the extract feature for data blocks only.

Changing the Default Directory Location for Extract Files

SunGard Higher Education delivers Banner with C:\temp as the default directory for extract files. The system administrator at your institution can use the General User Preferences Maintenance Form (GUAUPRF) to change this default value to meet your institutional needs. Only those staff members with appropriate security can perform this task.

In addition, individual users can set their own default directory for extract files. Chapter 3 of the Banner Getting Started Guide contains instructions for how to change the default directory.

Creating and Using QuickFlows

A QuickFlow is a technique that lets you access a set of forms in a specific sequence. QuickFlow processing uses the following forms:

• QuickFlow Validation Form (GTVQUIK). Defines a QuickFlow code and description.

• QuickFlow Definition Form (GUAQUIK). Specifies the sequence of forms and assigns a four-character identifier for executing the flow of forms.


3 Processing

• QuickFlow Form (GUAQFLW). Lets you enter the identifier and access the first form in the QuickFlow. When you exit the first form, the next form in the sequence is automatically accessed. This process continues until all forms in the QuickFlow have been accessed and exited. At this point, you can execute the QuickFlow again or exit to the location where you called the QuickFlow.

Creating a QuickFlow

Any form, except the following, can be added to a QuickFlow:

• Main menu (GUAGMNU)

• Welcome to Banner Form (GUAINIT)

• QuickFlow Form (GUAQFLW)

• Security Maintenance Form (GSASECR)

• Any query form (Q is the third character of the form name)

Use these steps to create a QuickFlow:

1. Determine the purpose of your QuickFlow, and identify all forms that must be accessed for the tasks you wish to perform. For example:

2. Use the QuickFlow Validation Form (GTVQUIK) to create a code and description for the QuickFlow. For example:

3. Access the QuickFlow Definition Form (GUAQUIK).

4. Enter the QuickFlow code (defined in step 2) in the QuickFlow field. If you want to search for a QuickFlow code, click the Search button to select the QuickFlow Codes option, which accesses the QuickFlow Validation (GTVCALL) list.

5. Go to the next block. All existing object names appear in the left pane.

6. Select the objects you want to add, and then use the arrow buttons to move the objects from the left pane to the right pane. Be sure to list them in the order they are to be accessed in the QuickFlow.

OR

Enter the seven-character name of each object you want in the QuickFlow. Be sure to list them in the order they are to be accessed in the QuickFlow. You can

Purpose: Add jobs to Job SubmissionForms needed: GJAJOBS

GJAPDEFGJAPVALGJAPDEF

Code: JOBDescription: Job Submission


3 Processing

use the List function to access the Object Search Form (GUIOBJS) to search for an object.

7. When all the desired objects are entered in the right pane, save your changes.

Using a QuickFlow

1. Access the QuickFlow Form (GUAQFLW).

2. Enter the QuickFlow code in the QuickFlow field. You can select the down arrow icon to access the QuickFlow Query Form (GUQQUIK) to search for a QuickFlow code.

3. Select the Start button or select the Next Block function. The first form in the QuickFlow appears.

4. Enter data on the form.

5. Exit the form. The next form in the QuickFlow appears.

6. Repeat steps 4 and 5 for all the forms in the QuickFlow. After you pass through all the forms in the QuickFlow, the QuickFlow Form (GUAQFLW) reappears.

Note: A form in a QuickFlow cannot be bypassed. If you do not have any data to enter on a form, exit the form. If the message DO YOU WANT TO QUIT? appears, answer Y. (The message is form-dependent.)

Note: If you want to exit the QuickFlow before all the forms are accessed, select the Exit QuickFlow option on the File pull-down menu.

7. If you are finished, select the Cancel button.

OR

To execute the QuickFlow again, select the Start button.

Event Management Procedures

The Event Management module helps you manage an event and the functions, tasks, and participants associated with the event. You can schedule functions, organize administrative tasks, determine financial requirements, and track attendance. Keeping track of this information not only lets you manage the current event, but provides information that can be used to plan future events.

With the Event Management module you can manage:


3 Processing

• Buildings and rooms

• Events

• Functions

• Tasks

• Participants

Definitions

The following definitions are useful for understanding the functions of the Event Management module:

Managing Buildings and Rooms

Data must be set up for every building and room that is a potential site for an event. Event Management uses the same forms used by the Banner Student System to schedule classes and housing. If your institution uses Banner Student, buildings and rooms may already be set up. If not, you need to set up buildings and rooms.

1. Use the Building Code Validation Form (STVBLDG) to set up building codes for each building at your institution.

2. Use the Building Definition Form (SLABLDG) to enter data for each building where functions can be scheduled.

3. Use the Room Definition Form (SLARDEF) to enter data for each room in a building. Values default from SLABLDG but can be overwritten.

Note: A room can be inactivated for a period of time by defining a Start Date and End Date in the Room Inactivation Block of SLARDEF. For example, a room can be inactivated for scheduled maintenance.

Event Any occasion that your institution offers or sponsors. Examples include a meeting, conference, and graduation ceremony.

Function An activity associated with an event and scheduled for a specific date, time, and place. An event can have several functions. Examples include reception, dinner, and lecture.

Task A specific activity required to plan or carry out a function.

Participant An ID who assists with a function and may or may not attend.


3 Processing

Managing Events

1. Use the Event/Function Type Code Validation Form (STVETYP) to set up codes for each type of event sponsored or offered by your institution (such as alumni gathering, social gathering, and conference).

2. Use the Event Form (SLAEVNT) to enter data for the event. The system assigns a five-character ID beginning with the letter A.

3. (Optional) To create and schedule functions, select Schedule from the Options menu. The Meeting Times window appears. Schedule the functions.

4. (Optional) To add comments about the event, select Comments from the Options menu. The Event Comments window appears. Enter free-form comments.

Note: You can use SLAEVNT or the Event Function Form (GEAFUNC) to schedule functions. Other function details, however, must be entered on the GEAFUNC Form.

Managing Functions

1. Use the Event/Function Type Code Validation Form (STVETYP) to set up codes for each type of function sponsored or offered by your institution (such as meal, break, and sporting function).

2. Use the Function Code Validation Form (GTVFUNC) to set up codes for each function sponsored or offered by your institution (such as breakfast, football game, and basketball game).

3. Make sure that the event has been created with the Event Form (SLAEVNT).

4. (Optional) To create and schedule functions using SLAEVNT, select Schedule from the Options menu. The Meeting Times window appears. Enter the schedule.

5. Use the Event Function Form (GEAFUNC) to enter details for each function.

Note: You can use the GEAFUNC Form to track function details such as revenue, expenses, fee structure, target audience codes, mailings, and meal selections.

6. (Optional) To schedule functions using the GEAFUNC Form, select Meeting Time from the Options menu. The Meeting Time window appears. Enter the schedule.

Note: You can use the SLAEVNT or GEAFUNC Form to schedule a function. Function details, however, must be entered on the GEAFUNC Form.


3 Processing

You can also enter information on the following optional forms to manage additional function details:

• Attendance Form (GEAATTD). Lets you record attendance information for a specific function. You can track information for each ID invited to the function and the ID’s guests.

• Event Registration Form (GEAATID). Lets you record attendance information for an ID who is invited to multiple functions within an event. You can also track information for the ID’s guests.

• Function Comment Form (GEAFCOM). Lets you enter, display, and edit freeform comments about a function. You can assign subject indexes (key words) to a comment to help you search for the comment at a later time.

• Function Affiliation Form (AEAAFIL). If Banner Alumni/Development is installed, this form lets you affiliate a function with campaigns, designations, and prospect management projects.

Managing Tasks

1. (Optional) Use the Task Type Code Validation Form (GTVTTYP) to define each type of task (such as administrative, maintenance, and security) that can be associated with a function.

2. Use the Task Code Validation Form (GTVTASK) to set up codes for the tasks (such as check room availability, reserve space, and clean up) that can be associated with functions.

3. Use the Function Task Form (GEATASK) to identify the specific tasks associated with a function. Tasks are automatically displayed in chronological order, based on the From date.

4. (Optional) To create a message, select Detail from the Options menu. Task details appear. Enter the Recipient ID and the Message. You can select the down arrow icon to access the User Identification Control Form (GUAIDEN) to search for an ID.

Note: The message is sent to the recipient on the message date. The recipient can use the General Message Form (GUAMESG) to read the message. This form identifies the source of the message as GEATASK and shows the task’s function code, but does not link the message to a specific task. To make the message more useful, you should refer to the task in the text of the message.

5. (Optional) To assign a task to a person, select Detail from the Options menu. Task details appear. Enter the ID of the assigned person in the ID field in the ID Assigned to Task block. To assign more persons to the task, select the Next Record function and enter another ID. You can use the ID/name search feature to search for a name or ID.


3 Processing

Note: Each person assigned to a task must have a Banner ID. These IDs are set up with the ID maintenance form of the appropriate Banner system.

Managing Participants

1. Use the Participant Type Code Validation Form (GTVPTYP) to define each type of participant (such as speaker or caterer) that can be associated with a function.

2. Use the Function Participant Form (GEAPART) to identify the participants associated with a function.

Note: Each participant must have a Banner ID. These IDs are set up with the ID maintenance form of the appropriate Banner system.

General International Management Procedures

Visa Tracking

The International Information Form (GOAINTL) is used to track Visa information. Details about this form are located in the General International Management chapter of this guide.

Setting Up Supporting Forms

Begin by entering information in the following validation forms:

• Nation Code Validation Form (STVNATN)

• Visa Type Code Validation Form (STVVTYP)

• Port of Entry Code Validation Form (STVPENT)

• Language Code Validation Form (STVLANG)

• International Student Sponsor Code Validation Form (STVSPON)

• Employment Type Validation Form (STVEMPT)

• Admission Request Checklist Code Validation Form (STVADMR)

• Visa Issuing Authority Validation Form (GTVVISS)

• Visa Source Code Validation Form (GTVSRCE)

• Visa Document Code Validation Form (GTVDOCM)

• Certification of Eligibility Validation Form (GTVCELG)


3 Processing

Entering Visa Information

Visa tracking information is stored on the Visa International Information Form (GOAINTL). To enter visa information about an international student:

Note: A student, prospect, or employee must exist in Banner (have a Banner ID) before you can enter information about them into GOAINTL.

1. Enter the person’s ID in the key block, or search for it by selecting the pull-down arrow.

2. Use <Ctrl><PgDn> to move into the Visa Information block on the Visa tab.

3. Enter the data into the Visa Information block.


5. Navigate to the Document block.

6. Enter information about the person’s supporting documents.


8. Navigate to the Passport Information tab.

9. Enter information about the person’s passport, and their admission and departure.


11. Navigate to the Certification of Eligibility tab.

12. Enter information about the documents that prove the person’s eligibility.


14. Navigate to the Nationality tab.

15. Enter information about the person’s Nationality and about family members who have accompanied them to the United States.


Deleting Records

Previously, you could not delete GOAINTL records; they were all stored as history. Now you can delete visa information from the Visa Information block. You cannot change the visa type, you can only delete the record.

Note: You cannot delete a record if there are supporting documents for it. You will receive an error message, and you will not be able to save your


3 Processing

change. You must first go to the Document block and delete all the items listed there.

Overlapping Visa Dates

GOAINTL has always supported multiple visas for one person, but none of the dates could overlap. If they did, you would receive an error message and you could not save the record.

Now people can have visas with overlapping dates. Banner will display an informational message, but you do not need to take any special actions as a result of it.

Displaying Multiple Visas

GOAINTL had displayed multiple visas sorted by the date, now it displays them by sequence number. The lowest number (the visa added earliest) appears on the form first, and you can scroll down to see the rest, sorted lowest to highest.

Student and Exchange Visitors Information System (SEVIS)

Overview

The Bureau of Citizenship and Immigration Services (BCIS), part of the U.S. Department of Homeland Security, is asking institutions in the United States to provide information about non-immigrant students and exchange visitors using the Internet.

The Student and Exchange Visitors Information System (SEVIS) provides tracking, monitoring, and access to accurate and current information on non-immigrant students (those with an F or M visa) and exchange visitors (those with a J visa), and on their dependents. Using SEVIS ensures that information is collected in a usable, shareable electronic format from the beginning, before the State Department issues the visa, and provides current, accurate data throughout the person’s course of study or program.

All institutions must be certified by the Bureau of Citizenship and Immigration Services to participate in SEVIS. The certification process will provide each institution with the appropriate login IDs and passwords.

For more information about SEVIS, please refer to the Bureau of Citizenship and Immigration Service’s web site.

Note: The Bureau of Citizenship and Immigration Services was formerly known as the Immigration and Naturalization Service (INS).

Banner currently supports:


3 Processing

• Fields in which you can enter the SEVIS-required data

• Conversion of Banner data into the codes required by the Bureau

• Storage of responses from the Bureau

• Storage and maintenance of historic SEVIS data

• An inquiry form to view and query records

• A batch process to prepare your data for transmittal to the Bureau and help you load the results of the transactions into Banner databases

• Interfaces with an external tool, the SEVIS Transfer Adaptor (SEVISTA), to send your files to the Bureau’s web site and import the response data into Banner tables.

You enter information into the SEVIS Information Form (GOASEVS), and create a student or exchange visitor history record. You can do this by:

• Selecting Create Student or Create Exchange Visitor from the Options menu

• Executing the SEVIS Batch Extract Process (GORSEVE)

Either method will create a Student or Exchange Visitor history record, respectively, and will convert certain Banner codes into SEVIS codes. The Bureau will only accept SEVIS codes. You can view the final record on the SEVIS Transmittal History Form (GOASEVR).

Any time there is a change for the student or exchange visitor that must be reported to the Bureau, you will update the information on the GOASEVS form, select the appropriate option or run GORSEVE, view the information on the GOASEVR form, and send it to the Bureau. You cannot change data on GOASEVR.

What is SEVISTA?

The SEVIS Transfer Adaptor (SEVISTA) is a Java tool that will reside on the platform that has the VeriSign Certificate. It takes data from Banner temporary table entries created by GORSEVE, converts it to XML, validates the XML and transmits it to the Bureau's web site.

Note: If SEVISTA finds errors in certain records when it validates the XML, it rejects those records. They are not included in the batch that SEVISTA transmits to the Bureau. The Status Code field on GOASEVR will be set to R (Returned with error).

SEVISTA will relay the Bureau's responses, sending an e-mail to the designated person. That information can be used to check the status of the batch and resubmit any records that were rejected.

Note: To receive e-mails from SEVISTA, you must have subscribed to it. For more information, please refer to the SEVIS Transfer Adaptor Installation & Implementation Guide.


3 Processing

When the batch has been processed by the Bureau, SEVISTA returns the information to your institution, loading it directly into the Banner tables by updating the Status Code and SEVIS Result Code Message fields on GOASEVR.

SEVISTA relies on the school code to transmit student records and the program code to transmit exchange visitor records. The school code and the program code must be unique for each instance of SEVISTA.

Note: GORSEVE does not validate the school or program code. If you enter a code that does not exist in a SEVISTA instance, either as a parameter to GORSEVE or on an individual record, GORSEVE will still select the records to send to the Bureau. It will create a batch ID and header information, but the header data will remain in GORSVBH and the transaction data will remain in GOTSVBT with no SEVISTA activity.

When you check on your batches you will see that the transmittal status code never changed. To get the batch to process, you must correct the school or program code on GOASEVS and re-create the records.

Structures

The Bureau has grouped related pieces of information together in a structure. A structure can contain other structures.

A record is created whenever any data element within that structure is changed. Each changed structure is included in a separate record. Because the INS requires this, you will probably find that your institution sends a larger number of records than you might have expected.

In Banner, the name of the structure is included in the GOASEVR record, and is displayed on the SEVIS Transmittal Status Query Form (GOISEVS) and on the SEVIS Transmittal History Form (GOASEVR).

Setting Up SEVIS Features

1. Determine the address codes to be used to populate the US and Foreign Address fields.

2. Use GTVSDAX to identify the address types to the SEVIS process. The codes are SVSUADDR and SVSFADDR

Note: A hierarchy of address types can be used to identify multiple address types.

3. The Bureau requires you to provide certain pieces of information about each student and exchange visitor. In some cases, the information (e.g., Nation) is already captured in Banner with a Banner code. You must map the SEVIS codes to the existing Banner ones because the Bureau will only accept SEVIS codes. You can find the SEVIS codes on the Bureau’s web site.


3 Processing

Add SEVIS equivalent codes to the corresponding Banner codes on the following validation forms:

(a) Major, Minor, Concentration Code Validation Form (STVMAJR)

(b) Nation Code Validation Form (STVNATN)

(c) Relation Code Validation Form (STVRELT)

(d) Visa Type Code Validation Form (STVVTYP)

(e) Port of Entry Code Validation Form (STVPENT)

Note: If you try to create a SEVIS record without first mapping these codes, you will receive an error message.

4. Enter both the US and foreign addresses for each student or exchange visitor on the Address Information window on the Identification Form (SPAIDEN).

5. Enter all information into the SEVIS Information Form (GOASEVS). Information will default in from SPAIDEN and SPAPERS.

Note: If the people and their dependents are set up on SPAIDEN and SPAPERS, their names, birthdates, and genders will be automatically populated on GOASEVS. You cannot enter this information into GOASEVS; it must be populated from SPAIDEN or SPAPERS.

6. Create population selection rules, if necessary.

7. Run the SEVIS Batch Export Process (GORSEVE).

Creating Student and Exchange Visitor Records

Creating Records Manually

Note: The student or exchange visitor must already exist in Banner before information can be added for them. They must have been created on the Identification Form (SPAIDEN).

1. Access the SEVIS Information Form (GOASEVS) through Direct Access or through the Banner Menus.

2. Enter the person’s Banner ID in the key block, or search for it by selecting the pull-down arrow then selecting Person Search (SOAIDEN) or Alternate ID Search (GUIALTI) from the Options.

3. Use <Ctrl><PgDn> to navigate to the SEVIS Common Data tab, or select it from the Options pull-down menu.

4. Enter information into the block and save your changes.


3 Processing

Note: Some Creation Reason codes are valid for students and some for exchange visitors. When you select Create Student or Create Exchange Visitor from the Options pull-down menu, Banner verifies that you have an appropriate Creation Reason code. If you don’t, Banner displays an error message.

5. Navigate to the SEVIS Student Data tab (if the person is a student) or to the Exchange Visitor Data tab (if the person is an exchange visitor).

6. Enter information into the block and save your changes.

7. Enter information in the Activity Site Data block (if the person is an exchange visitor).

8. Access the SEVIS Dependent Data block if the person has dependents in the United States.

If the dependent exists in Banner, enter the Banner ID to automatically populate some of data from SPAIDEN. Otherwise, enter the dependent’s name and biographical information manually.

9. If you want to verify or change the person’s personal information, select Name, Address, and Telephone Information from the Options pull-down menu. The link will take you directly to the Identification Form (SPAIDEN). Exit the form to return to GOASEVS.

10. When you are sure the data is complete and accurate, select Create Student or Create Exchange Visitor from the Options pull-down menu, depending on whether the person is a student or an exchange visitor. This invokes the scripts that convert various Banner codes to SEVIS codes and populate the SEVIS Transmittal History Form (GOASEVR). The scripts will verify that there is a SEVIS equivalent code for the Banner codes you entered for Visa Type, Primary Major, Birth Nation, Legal Nation, and Port of Entry for the person and their dependents.

The process that creates these records will verify that there is information in all of the required fields.

Note: GOASEVS will always contain the current information. You can view the history of your transactions on GOASEVR.

You can enter data into all the fields on GOASEVS. You can only enter status information on GOASEVR - all the other fields are display only.

GOASEVS contains Banner codes. GOASEVR contains the corresponding SEVIS codes.

11. Select View SEVIS Record from the Options pull-down menu. GOASEVR is displayed, and you can see that the SEVIS codes have been substituted for the Banner codes.


3 Processing

Creating Records Automatically

The SEVIS Batch Extract Process (GORSEVE) creates records, too.

When you run GORSEVE in audit or update mode, it compares GORSEVS records (present) to the most current GORSEVS record (history) to see if there is a change. If there is, it automatically creates the student and exchange visitor records as if you had selected Create Student or Create Exchange Visitor for them individually.

As part of its processing, GORSEVS will verify that there is information in all of the required fields.

After it creates the records, GORSEVS transmits them to the SEVIS Transfer Adaptor (SEVISTA), which converts them to an XML file and send them to the Bureau.

For more information about GORSEVE, refer to the Reports and Processes chapter in this document.

Viewing Records

Querying Records

1. Go to the SEVIS Transmittal Status Query Form (GOISEVS)

2. Enter the criteria by which you want to search and submit the query. The records that match your criteria will be listed in the Record block. You can also issue queries from the Record block itself.

Running GORSEVE in Audit Mode

If you want to see the records that will go to the Bureau before they are sent, you can run GORSEVE in audit mode.

• If the records can be transmitted through normal processing, GORSEVE creates the record for GOASEVR with a transmittal status code of W

• If the records contain adjudicated information and, therefore, must be transmitted manually, GORSEVE changes the transmittal status code to M

It will create the records as if it were going to send them, but it will print them on a report. You can use the report and the GOISEVS form to review the records. If you find a record that should not be sent to the Bureau, change the transmittal status code to X, and it will not be sent the next time GORSEVE is run (update mode).

Handling Adjudicated Information

The Bureau has determined that some information is so critical that it must be transmitted manually via the SEVIS RTI. Therefore, it is possible that a change to one person’s information could result in more than one record; you could have


3 Processing

some records with adjudicated information that you must send manually and some with information that can be sent as XML files.

The SEVIS Batch Extract Process (GORSEVE) is designed to know which events for students are adjudicated and which are not. It will take the information you enter on the SEVIS Information Form (GOASEVS) and will divide it into multiple records, as necessary. It will list the adjudicated records on the GORSEVE report, and give them the transmittal status code M. You must enter the information manually on the Bureau’s web site.

Adjudicated events for exchange visitors must be handled manually at this time. GORSEVE will not identify them.

The response records from the Bureau will be uploaded into Banner using SEVISTA.

Sending Records to the Bureau

There are two ways to send records to the Bureau:

1. You can provide the information to the Bureau manually via the SEVIS RTI.

2. You can use the batch process GORSEVE and the external tool SEVISTA

It is the responsibility of your institution to make sure the proper information is sent to the Bureau. For example, when you terminate a dependent, you cannot request an I-20 for that dependent. Banner will not prevent you from making this request, but the record will be rejected by the Bureau.

Transmitting Data via the RTI

1. Access the SEVIS Transmittal History Form (GOASEVR).

2. Access the Bureau web site.

3. Transfer the information in the Banner fields to fields on the web site.


5. Check to see the record’s status:

(a) If the record was accepted, access GOASEVR, display the person’s record, and enter the Status Code and any SEVIS Result Code Message. The Creation Date is populated automatically. Save your changes.

Access GOASEVS. Enter the SEVIS IDs for the person and for any dependents. Save your changes.

Note: After the SEVIS ID has been entered for this person, it will not have to be entered again, even if the information about that person changes.


3 Processing

(b) If the record was rejected, see If the Record is Rejected in this document.

Sending Data to the Bureau via the Batch Process

Note: SunGard Higher Education recommends that you set up the GORSEVE process and SEVISTA to run automatically each night.

1. Create a directory on the server/pc with the VeriSign certificate, and name it SEVIS. After GORSEVE has run, SEVISTA will send the XML file to the SEVIS directory.

2. SEVISTA will verify that the data is formatted correctly. It will also make sure that all the codes are accepted values. SEVISTA will send back a message indicating if the file has passed this check.

For details about GORSEVE, please refer to the Reports and Processes chapter in this document.

All the records that come from GORSEVE that have a transmittal status of P will be sent to the Bureau by SEVISTA. SEVISTA formats the data into an XML file and validates it against the SEVIS XML schemas to make sure it is in the proper format for transmission.

All the valid records are then uploaded to the Bureau’s web site.

When the records are sent to the Bureau, the transmittal status code remains P, because no response has yet come from the Bureau. When the Bureau responds, the code is changed to C if the Bureau approved the batch or R if the Bureau rejected it.

Multiple School/Program Codes

If your institution has multiple campuses, you must install multiple instances of SEVISTA. Each instance uniquely identifies the campus with a school and program code, and will process records for that school and program code only.

For more information about installing multiple instances of SEVISTA on the same server, please refer to the SEVIS Transfer Adaptor Installation & Implementation Guide.

Record submission is triggered by the SEVIS Batch Export Process (GORSEVE). You should run GORSEVE for a single school code or program code at a time, each with its own SEVIS Officer IDs for the Batch Approver and Transaction Approver.

Caution: Do not try to submit GORSEVE with both a school code and a program code as parameters; the program checks for one or the other, and will issue an error message if it finds both.

SunGard Higher Education recommends that you use population selections or Banner IDs as parameter values for GORSEVE if you have more than one school or program code.


3 Processing

If you set up new Student or EV records without assigning them a school or program code and create the actual records using GORSEVE, they will be given the school or program code for which GORSEVE was run.

Note: The SEVIS Approver ID needs to be correct for the school or program code or the Bureau will reject the transmission.

If you want to make sure student or exchange visitor records are associated with a specific school or program code, you can assign the code directly on GOASEVS.

All records with a transmittal status code of W (waiting) will be selected by GORSEVE for transmission to the Bureau, no matter what the school or program code is:

• If the school or program code stored on the record is the same as the one you entered as a parameter for GORSEVE, that school or program code will be included in the batch

• If a different school or program code is stored in the record, the stored code will be included in a new batch

• If there is no school or program code stored in the record, GORSEVE will use the one you entered as a parameter for GORSEVE, including it in the batch

Note: The school or program code must be unique for each batch. If one execution of GORSEVE finds records with more than one school or program code, GORSEVE will separate them into different batches.

If Records are Rejected by SEVISTA

SEVISTA validates your data against the SEVIS XML schemas. If any records are rejected, SEVISTA sends an e-mail to the SEVISTA subscriber. It also populates the Error Code field with SEVISTA. This is the field that usually contains any error codes from the Bureau.

The e-mail includes the batch number and lists the rejected records. You can review batch header information on the SEVIS Batch Header Inquiry Form (GOISVBH).

After the records are corrected, GORSEVE will select the records and pass them to SEVISTA, as usual. SEVISTA will convert them to XML, validate the XML and send them to the Bureau. The new batch header will have different information than the original. The Bureau considers the original batch to have been processed completely and the updated records are part of a new batch. The rejection is stored as part of the records’ history and cannot be changed.

Responses from the Bureau

The Bureau will respond to a batch in one of three ways:


3 Processing

1. It will reject the entire batch

2. It will accept some records and reject the others

3. It will accept all the records

In all of these cases, the designated person (a subscriber) will receive an e-mail from SEVISTA. It will provide the batch number and the number of records that have been accepted and rejected.

SEVISTA will automatically take the file from the Bureau and update the Trans. Status field with:

• C if the record was accepted

• R if it was rejected

If the record was accepted and the person did not already have a SEVIS ID, SEVISTA enters the SEVIS ID into the GOBSEVS and GORSEVD tables, too.

If the record was rejected, SEVISTA enters the Status Code and SEVIS Result Code Message provided by the Bureau into the Banner tables.

Note: If you have requested student or exchange visitor forms, SEVISTA places them in one of its directories. For more information, please refer to the SEVIS Transfer Adaptor Installation & Implementation Guide.

Receiving Data from the Bureau

Note: Before SEVISTA was available, the now-obsolete SEVIS Batch Import Process (GORSEVI) required you to set up the directory where you would place the XML files, XMLSEVIS. If you had created this directory previously, you should drop it now.

SEVISTA files, including the uploaded XML files and the downloaded files from the Bureau (including the .pdf files), are stored in directories on the SEVISTA server.

If a Record is Rejected

If a record is rejected, the result code (an error code), the result code message, and the transmittal status code (R) are automatically entered into the SEVIS Transmittal History Form (GOASEVR).

Note: You cannot correct a record and resend it. You must store the information about the rejection and create a new record. Only the new record can be sent. The rejected record is locked. The transmittal status code R indicates that it was returned with error.


3 Processing

1. You must go into the SEVIS Information Form (GOASEVS), the Identification Form (SPAIDEN), or General Person Form (SPAPERS) to make the changes.


3. (Optional) From GOASEVS, select Create a Student or Create an Exchange Visitor from the Options pull-down menu. GOASEVR appears. W appears in the Transmittal Status Code field automatically. This will ensure that the next run of GORSEVE includes the record in the batch file.

Interface with fsaATLAS

Note: You will not need this feature if your institute does not perform SEVIS processing, or if you use SEVISTA to process SEVIS records.

The SEVIS Batch Export Process (GORSEVE) can create a comma-separated value (CSV) file that can be imported by the fsaATLAS Campus DataLink. You can use the CSV file as you wish, but it was designed for fsaATLAS. fsaATLAS is an application specifically designed for Visa, Case Management, and SEVIS tracking.

Note: If you use fsaATLAS, you will not use the SEVIS Transfer Adaptor (SEVISTA) to transmit your records to the United States Bureau of Citizenship and Immigration Services (BCIS).

This differs from existing SEVIS processing in the following ways:

• No history records are created, so you cannot see the record on the SEVIS Transmittal History Form (GOASEVR).

• You will not use SEVISTA to validate and transmit your data.

• The CSV file will reside in your Job Submission directory and will have the same one-up name as the GORSEVE.lis file. You cannot view this file on the Saved Output Review Form (GJIREVO). You can download the file to fsaATLAS using the process in place at your institution.

If you do not specify individual Banner IDs or a population selection, the CSV file will contain an extract of all the records in SEVIS Data Table (GOBSEVS) and the associated views.

Note: If you do not have fsaATLAS, you can continue to use SEVISTA. There has been no change to SEVIS reporting when GORSEVE is run it Audit or Update mode for SEVISTA.

To create a CSV file of SEVIS data:

1. Specify individual Banner IDs or create a population selection for entry on GORSEVE. If no population selection or individual IDs have been entered on


3 Processing

GORSEVE, all the records on the SEVIS Data Table (GOBSEVS) will be selected to be part of the extract/CSV file.

2. Enter the following parameters:

(a) For parameter 02, enter the SEVIS User ID (Batch Approver). GORSEVE requires the Batch Approver to execute in Extract mode, but it is not required by fsaATLAS. You can enter any value for Batch Approver; it cannot be left blank (be null).

(b) For parameter 05, enter Y if you use Business Actions to create records. Otherwise enter N.

(c) For parameter 06, enter Y if you use Auto-population to create records. Otherwise enter N.

(d) For parameter 07, enter the Term Code if you use Auto-population. Otherwise, do not enter anything for parameter 07.

(e) For parameter 08, enter the Banner IDs you want to process. Optional.

(f) For parameters 09 - 12, enter population selection values. Optional.

(g) For parameter 13, enter Y if you want to print records that have had no activity in the GORSEVE.lis file. Otherwise enter N.

(h) For parameter 14, enter E.

Note: Parameter 14 is required if you are creating the CSV file.

(i) For parameter 15, enter the Department Owner ID for fsaATLAS.

Note: Parameter 15 is required if you are creating the CSV file. It is also required by fsaATLAS.

3. fsaATLAS Campus DataLink will insert the Banner ID into the Admissions ID field in fsaATLAS. This will help you cross-reference the data in the two systems. Admissions ID is not SEVIS-specific information.

4. The CSV file resides in your Job Submission directory, just like the results of any other job. You can view the CSV file in any editor you choose. It will not be available on GJIREVO; it is only written to the Job Submission directory.

Note: If you do not specify individual Banner IDs or create a population selection, all the records in the SEVIS Data Table (GOBSEVS) will be selected and written to the CSV file. You can run GORSEVE with the extract parameters as many times as you want; all it does is create another CSV file. It will not adversely affect Banner.

You can set up and use Business Rules (Business Actions and Auto-population) with the extract option.


3 Processing

Caution: The minimum data required by GORSEVE for each record Extracted is a creation reason or termination reason code. Records that do not have one or the other will not be processed by GORSEVE and included in the CSV file, but the records will appear on the .lis file.

Records that have both a creation reason code and a termination reason code will not be processed by GORSEVE, too.

EducationLevel/Change and EducationLevel/Cancel Processing

The new SEVIS 5.0 data structures are straightforward, but two of them (EducationLevel/Change Program and EducationLevel/Cancel) deserve mention regarding the handling of the data by SEVIS versus by Banner.

EducationLevel/Change

The EducationLevel/Change program structure submits a new program request with the same SEVIS ID. For example, a student in a BS program wants to continue at the institution in a master’s program, so an Education Level/Change program would be submitted for this student while he/she was still considered ACTIVE and currently attending the institution at the B.S. level.

As of SEVIS 5.0, once the new EducationLevel/Change program structure is processed by SEVIS, it is very important to note that SEVIS will begin to maintain two separate records for the individual: one record in ACTIVE (for example, BS) status and one record in INITIAL (for example, MS) status.

Banner/GOASEVS maintains only the most recent SEVIS record, which once the EducationLevel/Change program structure is submitted and processed by SEVIS, would be considered the INITIAL (MS, for example) record at SEVIS and not the ACTIVE (BS, for example) record. Certain structures can be submitted at this point that may update the ACTIVE and/or INITIAL record. Please refer to the EXHIBIT 5: SEVIS Batch - RTI Event Matrix for Students and Dependents section of the ICD/API. It is important for you to know which record you intend to update versus the record that is actually updated at SEVIS when you submit structures where two different records exist at SEVIS.

It is suggested that you do not send the Education Level/Change program structure to SEVIS until you have no more structures to submit against the ACTIVE record, and move forward at that point with the understanding that you are maintaining the INITIAL record only.

In order to ACTIVATE the student in the new program, a REGISTRATION structure would be applied to the student in the new program. Once SEVIS processes that transaction, the student would become ACTIVE in his/her new program.

EducationLevel/Cancel

If the student has no intention of registering in the new program, or if there is reason to cancel the request, the EducationLevel/Cancel can be submitted to SEVIS. When SEVIS processes this request, the INITIAL record at SEVIS will be


3 Processing

deactivated and SEVIS will revert to allow maintenance of the original ACTIVE record only.

When Banner submits the EducationLevel/Cancel structure, it looks for a Completed EducationLevel/Change structure in GORSEVS/GOASEVR. If it finds the structure 'C'omplete, it will find the structure submitted just prior to the EducationLevel/Change and backfill previous program information to GOBSEVS/GOASEVS.

A new history record in GOASEVR will be created representing this backfill called RevertHistory.

Note: Structures submitted to SEVIS between the EducationLevel/Change and EducationLevel/Cancel will need careful review. You may not have been aware of the record that got updated at SEVIS. You may want to log into the SEVIS RTI and review the SEVIS data and GOASEVS data for the student to be sure it is not out of sync.

The program fields that will be re-populated/backfilled upon EducationLevel/Cancel are listed in the following table:

GORSEVS Field Description Backfilled to GOBSEVS

GORSEVS_SVEL_CODE LEVEL GOBSEVS_SVEL_CODE

GORSEVS_SVEL_COMMENT OTHER REMARKS GOBSEVS_SVEL_COMMENT

GORSEVS_MAJR_CODE PRIMARY MAJOR GOBSEVS_MAJR_CODE*

GORSEVS_MAJR_CDE_2 SECOND MAJOR GOBSEVS_MAJR_CDE_2*

GORSEVS_MAJR_CDE_MINR MINOR GOBSEVS_MAJR_CDE_MINR*

GORSEVS_STUDY_LENGTH LENGTH OF STUDY GOBSEVS_STUDY_LENGTH

GORSEVS_PROGRAM_BEGIN_DATE PROGRAM START DATE GOBSEVS_PROGRAM_BEGIN_DATE

GORSEVS_PROGRAM_END_DATE PROGRAM END DATE GOBSEVS_PROGRAM_END_DATE

GORSEVS_ENG_PROF_REQ_IND ENGLISH REQUIRED GOBSEVS_ENG_PROF_REQ_IND

GORSEVS_ENG_PROF_MET_IND ENGLISH REQUIREMENTS MET

GOBSEVS_ENG_PROF_MET_IND

GORSEVS_ENG_PROF_REASON NOT REQUIRED REASON

GOBSEVS_ENG_PROF_REASON

GORSEVS_ACADEMIC_TERM_MONTHS ACADEMIC TERM GOBSEVS_ACADEMIC_TERM_MONTHS

GORSEVS_TUITION_EXPENSE TUITION GOBSEVS_TUITION_EXPENSE

GORSEVS_LIVING_EXPENSES LIVING EXPENSES GOBSEVS_LIVING_EXPENSES


3 Processing

Business Rule Builder Procedures

Establish the Rule Builder

The general process is as follows:

1. Set up Process Codes using the Business Rule Process Code Validation Form (GTVSQPR). The code SEVIS has been delivered.


3. Establish substitution parameters on the Business Rule Parameter Code Validation Form (GTVSQPA). The codes TERM and PIDM have been delivered.

(a) TERM allows you to ask the user for a value for the term, which will be used as a parameter in your rule.

(b) PIDM allows you to ask the user to enter a specific PIDM, which will be processed in your rule.


5. On the Business Rule Process Parameters Form (GORSQPA), associate process codes defined on GTVSQPR with substitution parameters defined on GTVSQPA. The number of substitution parameters a process code can have is restricted by the coding associated with the process. As delivered, the SEVIS Information Form (GOASEVS) will only prompt users to enter TERM or PIDM.

GORSEVS_DEPENDENT_EXPENSES DEPENDENT EXPENSES GOBSEVS_DEPENDENT_EXPENSES

GORSEVS_OTHER_EXPENSES AMOUNT GOBSEVS_OTHER_EXPENSES

GORSEVS_OTHER_EXP_COMMENT REMARKS GOBSEVS_OTHER_EXP_COMMENT

GORSEVS_PERSONAL_FUNDS PERSONAL GOBSEVS_PERSONAL_FUNDS

GORSEVS_SCHOOL_FUNDS AMOUNT GOBSEVS_SCHOOL_FUNDS

GORSEVS_SCHOOL_FUNDS_COMMENT REMARKS GOBSEVS_SCHOOL_FUNDS_COMMENT

GORSEVS_OTHER_FUNDS AMOUNT GOBSEVS_OTHER_FUNDS

GORSEVS_OTHER_FUNDS_COMMENT REMARKS GOBSEVS_OTHER_FUNDS_COMMENT

GORSEVS_EMPLOYMENT_FUNDS EMPLOYMENT (FUNDS)

GOBSEVS_EMPLOYMENT_FUNDS

GORSEVS Field Description Backfilled to GOBSEVS


3 Processing

Note: The package that processes parameters, GOKSVSQ, is only set up to handle TERM and PIDM at present. If you want to add other parameters, you must modify GOKSVSQ.


7. Set up codes and descriptions for all the Business Rules you plan to use on the Business Rule Code Validation Form (GTVSQRU).


9. On the SEVIS Business Rules Form (GORSVSQ), associate your process code/rule code combinations with an auto-population field or business action. If you select Business Action from the Process Type pull-down menu, you can only enter information in the SEVIS Business Action field (from GTVSVBA). If you select Auto-populate from the pull-down menu, you can only enter information in the SEVIS Auto-populate Code field (from GTVSVAP).


11. You will define the Business Rules themselves on the Business Rules Form (GORRSQL) by linking a Process Code (defined in Step 1) with a Rule Code (defined in Steps 4 and 7). Then you must create the dynamic SQL statements that will be executed when the SEVIS Batch Extract Process (GORSEVE) is executed, or when Business Action or Auto-populate is selected from the Options pull-down menu on GOASEVS. Be sure to save your changes.

Note: Be careful to enter your statements on GORRSQL in the correct order. GORSEVE and GOASEVS (when you select Create Student SEVIS Transaction or Create Exchange Visitor SEVIS Transaction from the Options menu) will execute each rule until they receive the Boolean value True for Business Actions or a single valid value for auto-population. It does not process any rules after that.

You can build two types of Business Rules without changing Banner programming logic: rules that initiate business actions and rules that auto-populate Banner columns from other Banner columns. If you want to make other kinds of rules, you must change the code.

Building Business Actions

A rule that initiates Business Actions will return a true/false condition. To build a Business Action:

1. On the SEVIS Business Action Code Validation Form (GTVSVBA), create a code and description for the package/procedure that will perform the tasks for your business action. SunGard Higher Education has delivered CREATE_STUDENT and CREATE_EV to be used with your SEVIS reporting.



3 Processing

3. On the SEVIS Business Rules Form (GORSVSQ), associate an existing Rule Code (from GTVSQRU) with a Process Code (from GTVSQPR).

4. Select Business Rule from the Process Type pull-down menu on GORSVSQ.

5. Enter the name of the Business Action you created on GTVSVBA in the SEVIS Business Action field.

6. Provide additional information about how it will be used, as necessary. For example, you can specify an effective date and end date for your rule with the Start Date and End Date fields.


Your Business Action can be triggered in two ways:

• When you execute GORSEVE with Y as Parameter 05 - Process Business Action. You must enter a term code as Parameter 07.

• When you select Business Action from the Options pull-down menu from GOASEVS. You will be prompted to enter a term code.

The package GOKSVSQ executes the specific process associated with the Business Rule, sending the person’s PIDM and Term as parameters.

Note: The package that processes parameters, GOKSVSQ, is only set up to handle Term and PIDM at present. If you want to add other parameters, you must modify GOKSVSQ.

In either case, all Business Actions with a process code of SEVIS are executed. If this results in the creation of any student or exchange visitor SEVIS records, any auto-population rules where the process code is SEVIS will be executed, too.

Caution: If you create a Business Action and it does not apply to anyone in the population selection, Banner will not provide you with an error message. This is also the case if there are no active Business Actions at all. As far as the Banner logic is concerned, it has processed all valid, active Business Actions for all the applicable people.

Building Auto-population Rules

A rule that initiates the auto-population of columns with other Banner data will return a single value. For auto-population, you have to perform the following as described in the Establish the Rule Builder section of this document:

1. Create a process code on the Business Rule Process Code Validation Form (GTVSQPR). SEVIS has been delivered.

Then you must perform a few additional steps:


3 Processing

2. On the SEVIS Auto-populate Code Validation Form (GTVSVAP), create a code and description for your auto-population. The code is the column name that you want to populate from another source. The column names from the GOBSEVS table have been delivered.


4. On the SEVIS Business Rules Form (GORSVSQ), associate an existing Rule Code (from GTVSQRU) with a Process Code (from GTVSQPR).

5. Select Auto-populate from the Process Type pull-down menu on GORSVSQ.

6. Enter the name of the auto-population code you created on GTVSVAP in the SEVIS Auto-populate Code field.

7. Provide additional information about how it will be used, as necessary. For example, you can specify an effective date and end date for your rule with the Start Date and End Date fields.


Your Auto-population can be triggered in two ways:

• When you execute GORSEVE with Y as Parameter 06 - Auto-population. You must enter a term code as Parameter 07.

• When you select Auto-populate from the Options pull-down menu from GOASEVS. You will be prompted to enter a term code.

Note: You cannot access Auto-populate from the Options pull-down menu if you are in the Key block.

The value returned in the auto-populate rule will update the field associated with the rule on GORSVSQ.

The package GOKSVSQ executes the specific process associated with the Auto-population, sending the person’s PIDM and Term as parameters.

Note: The package that processes parameters, GOKSVSQ, is only set up to handle Term and PIDM at present. If you want to add other parameters, you must modify GOKSVSQ.

When you use the Auto-population feature, the value returned in the Auto-populate rule will update the field associated with it on GORSVSQ.

Multi-Institution Functionality (MIF) Procedures

Multi-Institution Functionality (MIF) enables a user to switch between Institution Codes while logged into Banner.


3 Processing

Note: MIF is only available at schools that have implemented Virtual Private Database (VPD) functionality. If your institution is interested in using MIF, it is strongly recommended that SunGard Higher Education Application Practices perform the implementation. Do not attempt to make VPD changes to the database on your own.

Home and Process Contexts

At institutions that use MIF, all forms that are MIF-enabled display two contexts in the title bar: the home context and the process context. In the following example, the home context appears first, and is enclosed in parentheses. The process context appears second, and has no parentheses.

Home Context

The home context is the Institution Code that you choose on the Set Institution Form (GUQSETI) when you log in to your Banner session. Your options for choosing the home context vary according to how Institution Codes are set up for you on the Oracle/Banner VPD Security Maintenance Form (GSAVPDI):

• If there are multiple Institution Codes set up for your User ID on the User Assignment tab of GSAVPDI, then you will have multiple codes from which to choose the home context for your Banner session. If you exit GUQSETI without manually selecting a code, then the code designated as your default Institution Code on GSAVPDI will be used as the home context. Your default code always appears first in the GUQSETI list, and is highlighted.

• If there is only one Institution Code set up on the User Assignment tab, then that code will be used as your home context, and GUQSETI will not appear when you log in.

• If no codes are set up for you on the User Assignment tab, then the Banner system default Institution Code will be used as your home context.

Process Context

The process context is the Institution Code to which you switch during your Banner session. If you do not change codes during the session, then your process context will be the same as your home context.

How to View the Institution Code

If your institution already uses Virtual Private Databases (VPD), you will see a change in the location of the Institution Code on your forms. Previously, it was located in a field on the form, but now it is located in the title bar of Banner.


3 Processing

How to Switch Between Institution Codes

If MIF has been implemented at your institution, you can switch between the databases at different campuses that comprise your institution. The databases to which you have access depend upon your user role and the particular security that has been set up for you.

To Switch to Another Institution Code:

1. Click the MIF icon on the toolbar, or press the Ctrl-Shift-F10 keys simultaneously.

2. Enter an Institution Code. You can use the Search button to select a code from the Institution Code Validation (GTVVPDI) list, or, if you want to view further information about the available codes, click the View Existing Institutions Values link. If you select a row from the Existing Institution Values list, the values are brought back to the key block of the form. You can then view the data related to those particular values elsewhere on the form.

3. Click OK.

This Institution Code (the “process context”) now appears in the title bar after the code under which you logged in (the “home context”). Depending on the security policies established by the institution, you may have the ability to insert, update, or delete information using this selected institution code, or you may be limited to only viewing data with this selected institution.

How Changing Institution Codes Impacts your Banner Session

Banner processes always use the user’s default Institution Code that is set on GSAVPDI. If you choose a different institution on the Set Institution Code Form (GUQSETI) when you log in to Banner, then this value becomes your default and is used by Banner processes, regardless of whether you switch to another code during the session. It is important to note, however, that the Banner forms you use during your session use the Institution Code to which you have switched, as long as those forms are MIF-enabled.

When you change Institution Codes during a session, the code that the forms use is the code that appears second in your title bar. The code you chose on GUQSETI upon login appears first in the title bar.

Example of title bar after you have switched Institution Codes:(CAMP1) : CAMP2

(CAMP1) is the code you chose upon login. It is always used by Banner processes, regardless of whether you change Institution Codes.

CAMP2 is the code to which you changed. It is used by Banner forms.


3 Processing

Oracle Reports

Running Oracle Reports From the Form

Oracle Reports are run using the process context setting (Camp 2 in the preceding example), as long as the form from which the report is being called is listed on GORVPDI.

Note: If the form that calls the Oracle Report is not listed on GORVPDI, then the report can only be run under the user's home context.

Running Oracle Reports From Job Submission

If you have Oracle Reports that can only be run via GJAPCTL, or if the Oracle Report is initiated through GJAPCTL, then the home context is used.

If users need to use the process context for Oracle Reports that are initiated through GJAPCTL, then you may consider adding GJAPCTL to GORVPDI. However, this causes the process context to appear in the title bar of GJAPCTL, which then allows the user to change Institution Codes. A user who is executing a C process or other Banner report might assume that the process or report is being executed under the process context institution, which is not the case. The change in the Institution Code is only effective for Oracle Reports.

Basic Person Procedures

Basic person is a generic term that refers to people (persons) and companies (non-persons). Basic person information includes:

• Name/ID

• Address

• Telephone

• E-mail

• Biographical information

The basic person identification forms (forms whose seven-character names end with IDEN, such as SPAIDEN or GUAIDEN) are used throughout the Banner applications to capture information for all persons (and non-persons) associated with the institution. All persons/non-persons are first entered into the database using one of these forms. Information maintained on these forms is specific to the person/non-person, and does not relate to their involvement at the institution. All other modules and applications depend on the information captured and maintained on these forms. Any changes to a person's/non-person's biographic or demographic information must be made on one of them.


3 Processing

Common Matching and Basic Person

Common Matching is a feature in Banner that helps your institution avoid duplicate PIDMs, or storing the same information for a person under several different IDs. The Common Matching process checks for existing identification records before a new one is added to the database. You can access the Common Matching Entry Form (GOAMTCH) from an identification form to enter information for a new ID, and then execute the matching process before a new PIDM is created in Banner. Common Matching also provides a mechanism to add new records to the Banner database and update existing ones.

For information about setting up and using Common Matching, refer to the Common Matching Handbook.

To access GOAMTCH from an identifcation form:

1. Go to an identification form such as SPAIDEN or APAIDEN.

2. Enter GENERATED in the ID field.

OR

Select the Generate ID button.

OR

Enter an ID in the ID field that does not exist in Banner.

3. The GOAMTCH form appears.

Note: If a person record is created using the GOAMTCH form, then the Origin field (on SPAIDEN and SPRIDEN) is set to GOAMTCH. If the person record is created using SRRSRIN or SRIPREL, then the Origin field is set to SRKPREL.

You can search on last names, first names, and non-person names by text to see if similar names exist. Use the Search feature from the Last Name and First Name fields to view similar names on the Person Search Form (SOAIDEN). Use the Search feature from the Non-Person Name Information Name field to view similar names on the Non-Person Search Form (SOACOMP).

Tip: The current identification information on the main window is accessed by the Current Identification tab, if you want to return to the main window from a secondary window.

Using ID and Name Extended Search

The Extended Search feature provides advanced querying capabilities to help you maintain identification information for persons and non-persons.


3 Processing

To use the Extended Search window:

1. In a key block ID field, enter a partial ID and a wildcard ( % and _), or enter a partial name in the Name field. Wildcards can also be used in the Name field, but are not required for searching. For example, if an entire last name is entered, with no first name or wildcards, the Extended Search window will open and the search results will include all persons/non-persons that have that last name.

Note: The underscore ( _ ) wildcard cannot be used to search in the Name fields.

2. The ID and Name Extended Search window appears. The person/non-person count displays the number of persons/non-persons returned by the search.

3. Click the Search Results pull-down list to see the ID and name of the person/non-persons returned from the query.

Note: A person/non-person may be listed multiple times in the results list if the person has alternate names or IDs. However, each person/non-person is only included in the count once.

To review additional information about the persons in the search result set:

1. Click the Person Search Detail icon.

2. The Person Search form opens. The form that appears will vary by Banner product. For example, if the searching is being performed on a Student form such as SPAIDEN, the SOIDEN form will open. An ID can be selected on this form. If the ID is selected, you will be returned to the original form and this ID will display in the key block. If no ID is selected, when you exit this form, you will return to the key block of the original form. The Extended Search window will not redisplay automatically.

To review additional information about the non-persons in the search result set:

1. Click the Non-Person Search Detail icon.

2. The Non-Person Search form opens. The form that is called will vary by Banner product. For example, if the searching is being performed on a Student form such as SPAIDEN, the SOACOMP form will open. An ID can be selected on this form. If the ID is selected, you will be returned to the original form and this ID will display in the key block. If no ID is selected, when you exit this form, you will return to the key block of the original form. The Extended Search window will not redisplay automatically.


3 Processing

To reduce the search to person or non-person:

1. Click the radio button for the person or non-person.

2. The results will be updated to included only persons or non-persons, depending on your selection.

3. To reset the results to include persons and non-persons, select the Both radio button.

To reduce the search based on additional criteria:

1. Add additional search criteria in any combination of the fields: City, State or Province, ZIP or Postal Code, Name Type, SSN/SIN/TIN, Birth Date, Gender.

2. Click the Reduce Search button.

To clear the data from a previous search, or to enter a new query:

1. Click the Clear Search button.

To close the Extended Search window:

1. Click the X in the upper right hand corner of the window, or use keystrokes to perform a Clear Form function.

To determine who entered the current name/ID of a non-person and the form on which the data was entered:


2. Enter the ID of the non-person you are identifying.

3. Verify that the non-person's name has been entered on the main window on the Current Identification window.

4. Review the data in the ID and Name Source block.

To determine who entered the alternate name/ID of a non-person and the form on which the data was entered:




3 Processing

3. Verify that the non-person's name has been entered on the main window on the Current Identification window.

4. Go to the Alternate Identification window.

5. Review the data in the Origin, User, Activity Date, Create User, and Create Date fields.

Entering Basic Person Information

To enter current identification data for a person:


2. Enter the ID.

Note: If Common Matching is enabled for you, you will be directed to the Common Matching Entry Form (GOAMTCH), where you can enter information for the new ID and check for matches. Save the record. The ID and associated name are displayed in the key block.

3. Go to the Current Identification window.

Note: If the person currently has a record in Banner, the system copies the identification information and automatically places it into the fields in the current identification block. Complete the remaining fields, following the directions below.

4. Enter the person's Name Type.

5. Enter the person's SSN/TIN/SIN.( This field is available on FOAIDEN and PPAIDEN).

6. Enter the person's Last Name.

7. Enter the person's First Name.

8. Enter the person's Middle Name.

9. Enter the person's name Prefix.

10. Enter the person's name Suffix.

11. Enter the person's Marital Status. (This field is available on APAIDEN and FOAIDEN).

12. Save.


3 Processing

To enter alternate identification data for a person:


2. Verify the ID and the First Name, Last Name, and Middle Initial information on the Current Identification window.

Note: If the ID is generated, you must save the record before accessing the Alternate Identification block.

Note: If Common Matching is enabled for you, you will be directed to the Common Matching Entry Form (GOAMTCH) where you can enter information for the new ID and check for matches. Save the record. The ID and associated name are displayed in the key block.

3. Go to the next block, which takes you to the Alternate Identification window.

4. Enter the Change of Name or ID.

Note: The Duplicate Record function will copy the ID or name information into the appropriate fields on the Alternate Identification window depending on what type of change you enter.

5. Enter the person's alternate ID.

OR

Enter the person's alternate Last Name.

6. Enter the person's alternate First Name.

7. Enter the person's alternate Middle Name.


To view alternate identification data for a person:


2. Verify the ID and the First Name, Last Name, and Middle Name information on the Current Identification window.

3. Go to the next block, which takes you to the Alternate Identification window.

To enter current identification data for a non-person:


2. Enter an ID.


3 Processing

Note: If Common Matching is enabled for you, you will be directed to the Common Matching Entry Form (GOAMTCH) where you can enter information for the new ID and check for matches. Save the record. The ID and associated name are displayed in the key block.


4. Enter the name of the non-person in the Non-Person Information field.

5. Save.

To update an organization's and a person's name or ID:


2. Go to the Current Identification window.

3. Enter the new data over the existing data.

4. Save.

5. Go to the next block (which takes you to the Alternate Identification window) to see the changes.

Note: For updated IDs, the ID appears in the Change field. For updated names, the name appears in the Change field.

6. Select Next Record to view alternate names or IDs.

To delete an organization's and person's alternate name or ID:


2. Select Next Record until the desired name or ID appears.

3. Select Remove Record.

4. Save. The record is no longer displayed, and it no longer exists on either the Person Search Form (SOAIDEN) or the Non-Person Search Form (SOACOMP).


3 Processing

Maintaining Address and Telephone Information

To enter address information for a person:


2. Enter the ID.

3. Verify that the person's First Name and Last Name have been entered on the main window in the Current Identification tab.

4. Go to the Address window.

Note: If the person currently has a record in Banner, the system displays the address information on the Address window. You can insert new information by selecting Insert Record. Complete the remaining fields, following the directions below.

5. Enter the Type code for a new address.

OR

Select an address to be modified from the group of addresses previously entered for the person.

6. Enter the street address portion of the address in the Address fields. The first field is required. The remaining fields of the address are optional.

7. Enter the City (required), State or Province, and ZIP or Postal Code portion of the address.

OR

Search to select a City, ZIP or Postal Code, and State or Province from the ZIP or Postal Code Validation Form (GTVZIPC).

Note: If the city and state are both blank and a ZIP or postal code is entered, the city and state will default into those fields from GTVZIPC.

8. Enter the Nation code portion of the address.

Note: You must enter either the State /Province code or the Nation code.

9. If you do not want to create bar codes for the address, go to the last step.

OR

If you want to create bar codes for the addresses, go to the next step.

10. Select the ZIP/PC field, and open the Delivery Information window.

11. Enter all available delivery information.


3 Processing

12. Return to the Address window.

13. (Optional) Enter the Phone number associated with the Address.

14. Save.

Note: A person must have at least one complete address.

To enter address information for a non-person:

1. Access an Identification Form (%IDEN).


3. Verify the non-person's Name field entry have been entered on the Current Identification window.


5. Enter the Type code for a new address.

OR

Select an address to be modified from the group of addresses previously entered for the person.



OR



8. Enter the Nation code portion of the address.

Note: You must enter either the State/Province code or the Nation code.

9. If you do not want to create bar codes for the address, go to step 13.

OR

If you want to create bar codes for the addresses, go to step 10.

10. Select the ZIP/Postal Code field, and go to the Delivery Information window.


3 Processing

11. Enter all available delivery information.

12. Return to the Address window.

13. (Optional) Enter the Telephone number associated with the address.

14. Save.

To enter a primary telephone number with a new address:


2. Enter the ID.



5. Enter the Type code for the new address.



OR



8. Enter the Nation Code portion of the address.

Note: You must enter either the State/Province code or the Nation code.

9. Enter the area code, basic number, and the extension in the Telephone fields.

10. Enter the Telephone Type.

Note: Telephone types are associated with address types on the Address Type Code Validation Form (STVATYP). The telephone type associated with the address type defaults, but can be overwritten.

11. Save.

Note: Telephone numbers entered on the Address window are automatically associated with an address.


3 Processing

To add a primary telephone number to an existing address:

You can associate a primary telephone number with an address by using either the Address window or the Telephone window. Keep in mind that when you associate a telephone number with an address, the telephone number will become inactive if you designate the address inactive at some point.

To use the Address window:


2. Enter an ID in the ID field. Go to the next block.


4. Enter an address and address type, or query for an existing one that you want to use.

5. Choose the Telephone Type.


6. Enter the telephone number in the Telephone field.

7. Save.

To use the Telephone window:



3. Go to the Telephone window.

4. Choose a Telephone Type.


5. Enter the telephone number in either the Telephone field or the International Access field. For international numbers, enter the entire telephone number, including the international code.

6. Choose an Address Type and Sequence Number. You can query to find the address type and sequence number that identifies the address you want to use.

7. Save.


3 Processing

To enter a telephone number without an address:



3. Go to the Telephone window.

4. Choose a Telephone Type.

5. Enter the telephone number in either the Telephone field or the International Access field. For international numbers, enter the entire telephone number, including the international code.

6. Save.

To make an address inactive:




4. Choose the address you want to inactivate.

5. Check the Inactivate check box.

6. Save.

Note: When you inactivate an address, then the telephone number for that address will also be designated as inactive. If you want to keep the telephone number active, do one of the following:

• On the Telephone window, uncheck the Inactivate check box for the telephone number.

• On the Address window, choose To and From Dates to specify the active dates for the address, instead of checking the Inactivate check box for the address.

• On the Telephone window, do not associate an address type with the telephone number. If an address type is already specified, then delete it.

Note: For telephone numbers entered on the Address window of Banner Self-Service, the address type and sequence number specified on the window are always automatically associated with the telephone number in Banner.


Chapter 4

Job Submission

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-3

4 Job SubmissionValidation Forms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-3

Related Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-3

Menu Navigation Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-4

Forms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-5

Process Submission Control Form . . . . . . . . . . . . . . . . (GJAPCTL) . . . . . . 4-5Process Maintenance Form . . . . . . . . . . . . . . . . . . . (GJAJOBS) . . . . . . 4-15Parameter Definition Form . . . . . . . . . . . . . . . . . . . (GJAPDEF) . . . . . . 4-18Parameter Value Validation Form . . . . . . . . . . . . . . . . (GJAPVAL) . . . . . . 4-24Default Parameter Value Validation Form . . . . . . . . . . . . (GJAPDFT) . . . . . . 4-27Job Parameter Set Rule Form . . . . . . . . . . . . . . . . . . (GJRJPRM) . . . . . . 4-33Process Results Form . . . . . . . . . . . . . . . . . . . . . . (GJARSLT) . . . . . . 4-35Printer Validation Form . . . . . . . . . . . . . . . . . . . . . (GTVPRNT) . . . . . 4-36Saved Output Review Form . . . . . . . . . . . . . . . . . . . (GJIREVO) . . . . . . 4-39Job Submission Profile Maintenance Form . . . . . . . . . . . (GJAJPRF) . . . . . . 4-42Sleep Wake Maintenance Form . . . . . . . . . . . . . . . . . (GJASWPT). . . . . . 4-44Alternate Logon Verification Form . . . . . . . . . . . . . . . (GUAUIPW) . . . . . 4-45

4-1

Table of Contents



4 Job Submission

Overview

4 Job Submission

The Job Submission module facilitates the submission of reports and processes throughout Banner. Some of the functions you can perform in the Job Submission module are:

Job Submission • Submit a Banner report or process for processing.

• Define the characteristics of each Banner report or process that can be run at your institution.

• Define the parameters that control the processing of a report or process.

• Define user-level defaults for the parameters that control the processing of a report or process.

• Display output from a report or process that was run through Job Submission and saved to the database.

Validation Forms

Job Submission forms use the following validation forms. Refer to Chapter 2, Validation Forms, for additional information.

Related Report

The List of Reports and Parameters (GJRRPTS) shows reports and processes with their associated parameters. You can print the report for a single process, or you can use wildcards to print the report for all processes that begin with a specified string of characters. For additional information and a report sample, refer to Chapter 13, Reports and Processes.


GTVPRNT Printer Validation Form GJAJOBS Process Maintenance FormGJAPCTL Process Submission Control Form

GTVSYSI System Indicator Validation Form GJAJOBS Process Maintenance Form


4 Job Submission

Menu Navigation Table

Forms in the Job Submission module can be accessed from the following menu.

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Job Submission Menu (*GENJOB)

GJAPCTL Process Submission Control FormLets you submit a Banner report or process for processing. You can run the process or report immediately or hold it for later processing. You can save the parameter values as user-level defaults.

GJAJOBS Process Maintenance FormDefines the characteristics of each Banner report and process that can be run at your institution.

GJAPDEF Parameter Definition FormIdentifies the parameters that control the processing of a report or process. Establishes validation characteristics for the parameters. Defines system-level defaults for the parameters.

GJAPVAL Parameter Value Validation FormDefines valid values for the parameters that control the processing of a report or process.

GJAPDFT Default Parameter Value Validation FormDefines user-level defaults for the parameters that control the processing of a report or process.

GJRJPRM Job Parameter Set Rule FormDefines the names of the job parameter sets used at your institution.

Note: The actual defaults in a set are defined on the Process Submission Control Form (GJAPCTL) or the Default Parameter Value Validation Form (GJAPDFT).

GJARSLT Process Results FormDisplays a list of reports and processes that were run through Job Submission. Failure messages identify problems in batch processing and COBOL processes that were run online.

GTVPRNT Printer Validation FormDefines the codes that identify the printers at your institution.

GJIREVO Saved Output Review FormDisplays output from a report or process that was run on the Process Submission Control Form (GJAPCTL) and saved to the database.


4 Job Submission

Job Submission also uses the Alternate Logon Verification Form (GUAUIPW), which is not called from the menu. This form lets you enter an alternate user ID and password, changing the user ID that runs the job.

Note: You cannot enter an OPS$ account in the Alternate User ID field on GUAUIPW.

Forms

This section describes each form in the Job Submission module. Forms are described in the order they appear on the Job Submission Menu (*GENJOB).

Process Submission Control Form (GJAPCTL)

Use this form to submit a Banner job or report for processing. You can specify the print settings and parameter values that control processing. You can run the job or report immediately or hold it for later processing from the operating system.

Default parameter values appear if they have been defined. They can be user-level defaults, system-level defaults, or a combination of both. Using defaults reduces the number of entries you must make each time you run the job or report.

Warning: The Process Run Parameter Table (GJBPRUN) stores parameter values until a job or report runs successfully. Closely monitor the space allocation and contents of this table. Use SQL*Plus to remove parameter values for jobs and reports that fail or never run.

User-level defaults

The signed-on user ID can have one or more sets of user-level defaults for a job or report. For example, a user can have three sets of defaults for running the Person Directory (SPRPDIR): one set for recruits, another for students, and another for faculty. Each set of defaults is called a job parameter set and has its own name. If a

GJAJPRF Job Submission Profile Maintenance FormDefines the directory used to save output from Pro*C jobs run with the Process Submission Control Form (GJAPCTL).

GJASWPT Sleep Wake Maintenance FormAllows you to monitor and control sleep/wake processing that has been set up for specific Banner processes in the Student System and the Accounts Receivable System.

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Job Submission Menu (*GENJOB)


4 Job Submission

user has more than one set of defaults for a job or report, the name of the job parameter set must be entered when the job or report is submitted on GJAPCTL.

User-level defaults are defined on one of the following forms:

• Process Submission Control Form (GJAPCTL). A user can submit a job or report on this form and save the parameter values as user-level defaults. If the user has more than one set of parameters for the job or report, each set must be named uniquely.

• Default Parameter Value Validation Form (GJAPDFT). A user can create a single set of user-level defaults or copy user-level defaults from one user ID to another. A user can also use this form to change default values in an existing job parameter set.

System-level defaults

A system-level default applies to all users at your institution. It has lower priority and is used only when the parameter has no user-level default. System-level defaults are defined on the Parameter Definition Form (GJAPDEF).

Prerequisites

The job or report must be defined. You can define the job or report on the Process Maintenance Form (GJAJOBS).

The current user must be authorized to run the job or report. You can establish authorizations on the Oracle/Banner Security Maintenance Form (GSASECR) according to your institution’s policies and procedures.

Run-time parameters must be defined for the job or report. You can define the parameters on the Parameter Definition Form (GJAPDEF).

Main Window

Use this window to submit a Banner job or report for processing. You can specify the printer settings and parameter values that control processing. You can run the job or report immediately or hold it for later processing from the operating system.

Key Block

Use this block to identify the Banner job or report you want to submit for processing. If the job or report has multiple sets of user-level defaults, you must also identify the job parameter set you want to use.


4 Job Submission

Printer Control Block

Use this block to specify the print settings for the job or report.

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions

Process Banner job or report you want to submit for processing. The job or report must be defined on the Process Maintenance Form (GJAJOBS).

Column: Not base table items (code and description)

Choices: Choices come from GJAJOBS.

Parameter Set Job parameter set that contains the user-level defaults for running the job or report. All sets linked to the signed-on user ID and job or report are available.

The signed-on user ID can have more than one set of defaults for the job or report, each with its own name. Using job parameter sets lets you run a job or report with different combinations of user-level parameter values. For example, a user can have three sets of defaults for running the Person Directory (SPRPDIR): one set for recruits, another for students, and another for faculty.

If the signed-on user ID has more than one set of defaults for the job or report, enter the job parameter set name in this field.

If the signed-on user ID has only one set of defaults for the job or report, leave this field blank.

If you a creating a new job parameter set, leave this field blank. Enter the name in the Submission block instead.

Column: Not a base table item

Choices: Choices come from the Job Parameter Set Rule Form (GJRJPRM).


4 Job Submission

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions

Printer Destination printer for output from the job or report.

Warning: Leave this field blank for jobs and reports that run with sleep/wake processing. For these kinds of jobs and reports, enter the printer code as a parameter.


Source: This value comes from the Printer field on the Process Maintenance Form (GJAJOBS). It can be changed.

Choices: Choices come from the Printer Validation (GTVPRNT) list. You can also use these values:

blank - Use the system printer.

NOPRINT - Skip printing.

DATABASE - Save output for viewing on the Saved Output Review Form (GJIREVO).

Special Print Print stock or form command for output from the job or report.


Source: This value comes from the Special Print Stock field on the Process Maintenance Form (GJAJOBS). It can be changed.

Choices: For special forms, use the specific operating system forms command. Other choices are:

LANDSCAPE (default) - Print across the wide side of the paper.

PORTRAIT - Print across the narrow side of the paper.

Note: This option is not available for Windows NT Server.

Lines Number of print lines per page for output from the job or report. The default value is 55.


Source: This value comes from the Lines Per Page field on the Process Maintenance Form (GJAJOBS). It can be changed.

Submit Time Time when the job or report will be submitted for processing. To use this date, you must customize your installation processes.



4 Job Submission

Parameter Values Block

Use this block to specify the parameter values that control processing of the job or report.

Default parameter values appear if they have been defined. They can be user-level defaults, system-level defaults, or a combination of both. Using defaults reduces the number of entries you must make each time you run the job or report.

Note: When you select a displayed parameter, hints for entering the parameter value appear at the bottom of the block.

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions

Number (untitled)

Number that uniquely identifies each parameter for the job or report. Parameters must be defined on the Parameter Definition Form (GJAPDEF).

Column: GJBPRUN_NUMBER

Source: This value comes from the Parameter field on GJAPDEF. It can be changed.

Parameters Description of the parameter.


Source: This value comes from the Parameter field on the Parameter Definition Form (GJAPDEF). It cannot be changed.

Choices: Choices come from the Parameter Definition Form (GJAPDEF).


4 Job Submission

Values Value of the parameter used to run the job or report. Use these guidelines to enter a value:

• If specific parameter values are defined for the job or report on the Parameter Value Validation Form (GJAPVAL), enter one of the defined values.

• Make sure the value meets all criteria defined on the Parameter Definition Form (GJAPDEF). These criteria include the data type, length, and range of values.

• If a validation form is linked to the parameter on GJAPDEF, enter a value from the specified validation form.

• If a validation routine is linked to the parameter on GJAPDEF, make sure the value passes the special validation checks.

• If a validation routine is linked to the job or report on the Process Maintenance Form (GJAJOBS), make sure the value passes consistency checks applied to a group of parameters.

Note: Hints for entering a selected value appear at the bottom of the block.

If a parameter can have multiple values (indicated in the hint at the bottom of the block), each value must be entered on a separate line. Select Insert Record and Duplicate Record to create entries on separate lines.

Column: GJBPRUN_VALUE

Source: This value comes from one of the following sources, from highest to lowest priority:

• If the user ID has more than one set of user-level defaults for the job or report, the default in the job parameter set is used.

• If the user ID has only one set of user-level defaults for the job or report, the user-level default is used.

• If the user ID does not have any user-level defaults for the job or report, the system-level default is used.

• If there are no system-level defaults for the job or report, the field is blank.

Any default can be changed. A job or report can have a mixture of user-level and system-level defaults.

• Choices: If specific parameter values are defined for the job or report on GJAPVAL, choices come from a Parameter Values list. If a validation form is linked to the parameter on GJAPDEF, choices come from the validation form.

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions


4 Job Submission

Submission Block

Use this block to save user-level defaults and to submit the job or report for processing.

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions

Save Parameters Check box that indicates whether the parameter values should be saved as user-level defaults for the job or report.

If the user has one set of defaults for the job or report, select this check box and leave the As fields blank.

If the user has more than one set of defaults for the job or report, select this check box and enter the name and description of the job parameter set in the As fields.


Choices are:

Selected - Save the parameter values as user-level defaults.

Cleared - Do not save the parameter values as user-level defaults.

Hold/Submit Radio group that indicates whether the job or report is held for later processing or run immediately.


Choices are:

Hold - Hold for later processing from the operating system. A sequence number appears in the Auto Hint. Use this number when you submit the job from the operating system.

Submit (default) - Process the job or report immediately.


4 Job Submission

As Name and description of a set of user-level defaults for the job or report. Use these fields to save defaults when a user ID has more than one set of defaults for the job or report. To use these fields, the Save check box must be selected.

The signed-on user ID can have more than one set of defaults for the job or report, each with its own name. Using job parameter sets lets you run a job or report with different combinations of user-level parameter values. For example, a user can have three sets of defaults for running the Person Directory (SPRPDIR): one set for recruits, another for students, and another for faculty.

If the signed-on user has one set of defaults for the job or report, leave these fields blank. The defaults are linked directly to the signed-on user ID.

If the signed-on user has more than one set of defaults for the job or report, enter the name and description of the job parameter set as follows:

• To save a new set, enter the name and description of the set in these fields. Blank spaces are allowed. The new set is automatically added to the Job Parameter Set Rule Form (GJRJPRM). The defaults are linked to the signed-on user ID under this name.

• To save changes to an existing set, enter the name of the set in Parameter Set field in the key block. The name and description automatically appear in these fields in the Submission block. The defaults remain linked to the signed-on user ID under this name.

• To change the name of an existing set, enter the name of the original set in the Parameter Set field in the key block. Change the name and description in these fields in the Submission block. The defaults are linked to the signed-on user ID under the new name.

Caution: If you delete the job parameter set name, defaults tied directly to the user are updated, not the defaults in the job parameter set.


Source: These values comes from the Parameter Set field in the key block. They can be changed.

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions


4 Job Submission

Procedures

To submit a job or report with Job Submission

1. Access the Process Submission Control Form (GJAPACTL).

2. Enter the name of the job or report in the Process field.

3. If you have job parameter sets for the job or report, enter the name of the Parameter Set.


5. Verify the print parameters. Change if necessary.


7. Verify all parameter Values. Change if necessary.


9. To hold the job or report for later processing, select the Hold radio button.

OR

To process the job or report immediately, select the Submit radio button.

10. Save.

To create one set of user-level defaults

Note: Use these steps if the user ID has only one set of user-level defaults for the job or report.





Note: Print parameters are not saved as user-level defaults.


6. Enter the parameter values in the Values fields.



9. Make sure the As field is blank.


4 Job Submission


OR


11. Save.

Note: You can also create a single set of user-level defaults on the Default Parameter Value Validation Form (GJAPDFT).

To create a job parameter set

Note: Use these steps if the user ID has more than one set of user-level defaults for the job or report.







6. Enter the parameter values in the Values fields.



9. Enter the name of the job parameter set in the As field.

10. Enter the description of the job parameter set in the adjacent field.


OR


12. Save.

To change user-level defaults




4 Job Submission

3. If the user ID has more than set of user-level defaults, enter the name of the Parameter Set.

OR

If the user ID has only one set of user-level defaults, make sure the Parameter Set field is blank.




6. Enter any changes to the parameter values in the Values fields.



Note: If you entered a job parameter set name in step 3, the name and description appear in the As fields.


OR


10. Save.

Note: You can also change user-level defaults on the Default Parameter Value Validation Form (GJAPDFT).

Process Maintenance Form (GJAJOBS)

Use this form to create and store the characteristics of each Banner job and report that can be run at your institution.

Caution: Only the person who originally defined a job or report on this form should change any of the job or report’s characteristics on this form.

Main Window

Use this window to create and store the characteristics of each Banner job and report that can be run at your institution.


4 Job Submission

Process Maintenance Block

Use this block to create and store the characteristics of each Banner job and report that can be run at your institution. The characteristics stored in this block are used to build the command for running a job or report when you submit it for processing from the Process Submission Control Form (GJAPCTL) or a specific application form.

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions

Name Name of a Banner job or report that can be run at your institution.

Column: GJBJOBS_NAME

Title Short title of the job or report. This title appears with the job name on various Job Submission forms.

Column: GJBJOBS_TITLE

System Code of the Banner system associated with the job or report. This code is used to determine which validation routines are used for the job or report.

Column: GJBJOBS_SYSI_CODE

Choices: Choices come from the System Indicator Validation (GTVSYSI) list.

Desc (Description)

Long description of the job or report.

Column: GJBJOBS_DESC

Type Pull-down list that indicates the type of job or report.

Column: GJBJOBS_JOB_TYPE_IND

Choices are:

PRO*C (default) - The job or report is written in Pro*C. This value is stored in the database as C.

Executable - The job or report is written in COBOL. This value is stored in the database as E.

Procedure - The job or report is run with an operating system command procedure such as a UNIX shell (.shl), a VMS command procedure (.com), or an NT perl script (.pl). This value is stored in the database as P.

Oracle Report - The job or report is written in Oracle Report language. This value is stored in the database as R.


4 Job Submission

Printer Default destination printer for output from the job or report.

Column: GJBJOBS_PRINT_CODE

Choices: Choices come from the Printer Validation (GTVPRNT) list. You can also use these values:

NOPRINT - Skip printing.

DATABASE - Save output for viewing on the Saved Output Review Form (GJIREVO) before printing.

Lines Per Page Default number of print lines per page for output from the job or report.

Column: GJBJOBS_LINE_COUNT

Special Print Stock

Default print stock or form command for output from the job or report.

Column: GJBJOBS_PRINT_FORM

Choices: For special forms, use the specific operating system forms command. Other choices are:

LANDSCAPE (default) - Print across the wide side of the paper.

PORTRAIT - Print across the narrow side of the paper.

Note: If you want to print in landscape mode on WinNT, you need to define another print alias in WinNT where the default properties are to print in landscape mode.

Example:

\\server\laser_p - default print is portrait\\server\laser_l - default print is landscape

Define these printers on GTVPRNT, and then select the \\server\laser_l when you want to print a landscape report.

Validation Routine used to validate a group of parameters when the job or report is submitted through Job Submission. The validation routines are contained in the xOKPVAL database package (xOKPVAL.sql), where x is the system code.

Column: GJBJOBS_VALIDATION

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions


4 Job Submission

Procedures

To create a job or report

1. Access the Process Maintenance Form (GJAJOBS). The form opens in query mode.

2. Cancel the query.

3. Enter the Name of the job or report.

4. Enter the Title of the job or report.

5. Enter the System code associated with the job or report.

6. Enter the long description of the job or report in the Desc field.

7. Verify the Type of the job or report. Change if necessary.

8. (Optional) Enter any other job or report characteristics.

9. Save.

Parameter Definition Form (GJAPDEF)

Use this form to:

• Identify the parameters that control the processing of a job or report.

• Establish validation characteristics for the parameters. The Process Submission Control Form (GJAPCTL) and Default Parameter Value Validation Form (GJAPDFT) use these characteristics to validate parameters.

Command Name

Name of the command used to build the command for executing the job or report. If this field is left blank, the job name is used.

Warning: Do not use an extension. An extension, if needed, is automatically added, based on your operating system and the type of job or report.

Column: GJBJOBS_COMMAND_NAME

Activity Date Date when the job or report was created or last updated.

Column: GJBJOBS_ACTIVITY_DATE

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions


4 Job Submission

• Define system-level defaults for the parameters. These defaults apply to all users at your institution and are used when parameters have no user-level defaults.

Note: The job or report must be defined. You can define the job or report on the Process Maintenance Form (GJAJOBS).

Warning: Only the person who originally defined a job or report on GJAPCTL should set up and maintain parameters on this form.

Main Window

Use this window to:




Key Block

Use this block to identify the job or report for which you are defining parameters.

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions

Process Name Name and short title of the Banner job or report for which you are defining parameters. The job or report must be defined on the Process Maintenance Form (GJAJOBS).

Column: Not base table items (name and title)

Source: The short title comes from the Title field on GJAJOBS. It cannot be changed.



4 Job Submission

Parameter Definition Block

Use this block to:




. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions

Parameter Number that identifies a specific parameter used to process a job or report. This number determines the order in which the job or report uses the parameters and the order in which the parameters appear on the Process Submission Control Form (GJAPCTL).

Column: GJBPDEF_NUMBER

Parameter Description (untitled)

Freeform description of the parameter.

Column: GJBPDEF_DESC

List Validation form used to validate values for this parameter. If you want to restrict the parameter to specific values on the validation form, you must identify the specific values on the Parameter Value Validation Form (GJAPVAL). Otherwise, all values on the validation form are available to the parameter.

The following forms validate parameter values against this validation form:


• Parameter Value Validation Form (GJAJPVAL)


Column: GJBPDEF_LIST_VALUES


4 Job Submission

Type Pull-down list that indicates the type of data that can be accepted for this parameter.

Column: GJBPDEF_TYPE_IND

Choices are:

None - The parameter value has no requirements regarding data type.

Character (default) - Parameter value must be alphanumeric. This value is stored in the database as C.

Date - Parameter value must be a date. This value is stored in the database as D.

Integer - Parameter value must be a whole number. This value is stored in the database as I.

Number - Parameter value must be numeric. This value is stored in the database as N.

Length Maximum number of characters the parameter can contain.

Column: GJBPDEF_LENGTH

Choices: The value can be 01 through 30.

Optional/Required

Radio group that indicates whether the parameter value is optional or required on the Process Submission Control Form (GJAPCTL).

Column: GJBPDEF_OPTIONAL_IND

Choices are:

Optional (default) - A parameter value can be entered on GJAPCTL but is not required. This value is stored in the database as O.

Required - A parameter value must be entered on GJAPCTL for the job or report to run. This value is stored in the database as R.

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions


4 Job Submission

Single/Multiple Radio group that indicates whether only one or more than one parameter value can be entered on the Process Submission Control Form (GJAPCTL).

Column: GJBPDEF_SINGLE_IND

Choices are:

Single (default) - Only one value can be entered for the parameter on GJAPCTL. This value is stored in the database as S.

Multiple - Multiple values can be entered for the parameter on separate lines of GJAPCTL. This value is stored in the database as M.

Low Lowest value that can be entered for the parameter.

Column: GJBPDEF_LOW_RANGE

High Highest value that can be entered for the parameter.

Column: GJBPDEF_HIGH_RANGE

Validation Routine that validates this parameter when the job or report is submitted on the Process Submission Control Form (GJAPCTL).

Column: GJBPDEF_VALIDATION

Default System-level default for the parameter. This default applies to all users at your institution and is used only when a user ID has no user-level default for the parameter.


Choices: Choices come from the Parameter Values list.

Help Freeform text that gives additional information about the parameter. This text appears on the following forms:


• Parameter Value Validation Form (GJAPVAL)


Column: GJBPFEF_HELP_TEXT

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions


4 Job Submission

Procedures

To define a parameter


2. Enter the Process Name.


4. Enter the number that identifies the new Parameter on a blank line.

5. Enter the description of the parameter in the adjacent field.

6. Verify the parameter Type. Change if necessary.

7. Enter the parameter Length.

8. Verify the Optional/Required radio button. Change if necessary.

9. Verify the Single/Multiple radio button. Change if necessary.

10. (Optional) Enter any other validation characteristics.

11. (Optional) Enter the system-level Default for the parameter.

12. Save.

To create system-level defaults




4. Select the Parameter for which you are entering a system-level default.

5. Enter the system-level Default.

6. Save.


4 Job Submission

Parameter Value Validation Form (GJAPVAL)

Use this form to define valid values for the parameters that control the processing of a job or report. These values are used to validate entries on the Process Submission Control Form (GJAPCTL). This ensures that parameter values are valid and in the correct format before you submit a job or report.

Caution: Only the person who originally defined a job or report on GJAPCTL should set up and maintain parameter values on this form.

Prerequisites


The parameters must be defined. You can define the parameters on the Parameter Definition Form (GJAPDEF).

Main Window

Use this window to define valid values for the parameters that control the processing of a job or report. These values are used to validate entries on the Process Submission Control Form (GJAPCTL). This ensures that parameter values are valid and in the correct format before you submit a job or report.

Key Block

Use this block to identify the job or report for which you are defining parameter values.

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions

Process Name Name and short title of the Banner job or report for which you are defining parameter values. The job or report must be defined on the Process Maintenance Form (GJAJOBS).





4 Job Submission

Parameter Values Block

Use this block to define valid values for the parameters that control the processing of a job or report. These values are used to validate entries on the Process Submission Control Form (GJAPCTL). This ensures that parameter values are valid and in the correct format before you submit a job or report.

You can define two kinds of values in this block:

• You can define values for parameters that cannot be validated by a validation table. For example, if a report has a sort parameter that must be 1, 2, or 3, you can define the values 1, 2, and 3 on GJAPVAL.

• You can define values for parameters that use some, but not all, values in a validation table. For example, if a job uses specific ZIP codes from the ZIP/Postal Code Validation Form (GTVZIPC), you can define the specific ZIP codes on GJAPVAL. Do not use this block, however, if the parameter is validated against all values in a validation form. Instead, use the List field on the Parameter Definition Form (GJAPDEF) to identify the validation form.

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions

Number (untitled)

Number that identifies a specific parameter used to process the job or report. This number determines the order in which the job or report uses the parameters and the order in which the parameters appear on the Process Submission Control Form (GJAPCTL).

Note: To display the validation characteristics for a parameter, select the parameter number and click the Search button. The Parameter Definition Form (GJAPDEF) appears.

Column: GJBPVAL_NUMBER

Parameters Free-form description of the parameter.

Column: GJBPVAL_DESC

Source: This value comes from the Parameter field on the Parameter Definition Form (GJAPDEF). It can be changed.


4 Job Submission

Procedures

To define valid parameter values

1. Access the Parameter Value Validation Form (GJAPVAL).



4. To enter a new parameter value, enter the number that identifies the parameter in the first field of a blank record.

OR

To change an existing parameter value, select the parameter number on the line that contains the value you want to change.

5. Enter a parameter value in the Values field.

6. Repeat steps 4 and 5 for each parameter value you are adding or changing.

7. Save.

Values Valid parameter value that can be used to run the job or report. If the parameter can have multiple values, enter each value on a separate line. Each value must meet the validation criteria defined for the parameter on the Parameter Definition Form (GJAPDEF).

Note: Data-entry hints for the selected parameter appear at the bottom of the form. This information comes from the Help field on GJAPDEF.

Column: GJBPVAL_VALUE

Choices: If the parameter is validated against a validation form, choices come from the validation or list form identified in the List field on GJAPDEF.

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions


4 Job Submission

Default Parameter Value Validation Form (GJAPDFT)

Use this form to define user-level defaults for the parameters that control the processing of a job or report. You can create new defaults, change existing defaults, and copy defaults from one user ID to another.

Caution: Only the person who originally defined a job or report on the Process Submission Control Form (GJAPCTL) should set up and maintain parameter defaults on GJAPDFT.

User-level defaults

The signed-on user ID can have one or more sets of user-level defaults for a job or report. For example, a user can have three sets of defaults for running the Person Directory (SPRPDIR): one set for recruits, another for students, and another for faculty. Each set of defaults is called a job parameter set and has its own name.

You can create one set of user-level defaults on GJAPDFT. If the user ID has multiple job parameter sets for a job or report, each set must be defined on the Process Submission Control Form (GJAPCTL). You can use GJAPDFT, however, to change defaults in an existing job parameter set.

System-level defaults

In addition to user-level defaults, you can have system-level defaults. These defaults apply to all users at your institution. They have lower priority and are used only when parameters have no user-level defaults. System-level defaults are defined on the Parameter Definition Form (GJAPDEF).

Prerequisites


Parameters for the job or report must be defined. You can define the parameters on the Parameter Definition Form (GJAPDEF).

You must be logged on with the user ID that will be linked to the defaults that are being created, changed, or copied.

Main Window

Use this window to define user-level defaults for the parameters that control the processing of a job or report. You can create new defaults, change existing defaults, and copy defaults from one user ID to another.


4 Job Submission

Key Block

Use this block to identify the job or report for which you are defining user-level defaults. You must also identify the job parameter set if you are changing existing defaults or copying defaults and the user ID has more than one set of parameters for the job or report.

System Level Defaults Block

Use this block to display system-level defaults that apply to all users at your institution. These defaults have lower priority and are used only when parameters have no user-level defaults.

Information comes from the Parameter Definition Form (GJAPDEF). Information is display-only and cannot be changed.

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions

Process Name and short title of the Banner job or report for which you are defining user-level defaults. The job or report must be defined on the Process Maintenance Form (GJAJOBS).




Parameter Set Job parameter set used to run the job or report. Use this field only if the signed-on user ID has more than one set of defaults for the job or report. The set must be defined on the Job Parameter Set Rule Form (GJRJPRM).

A job parameter set is a set of user-level defaults used to run the job or report. The signed-on user ID can have more than one set of defaults for the job or report, each with its own name. Using job parameter sets lets you run a job or report with different combinations of user-level parameter values. For example, a user can have three sets of defaults for running the Person Directory (SPRPDIR): one set for recruits, another for students, and another for faculty.

Note: To create a new job parameter set, you must use GJRJPRM or the Job Submission Control Form (GJAPCTL). You cannot create a new set on GJAPDFT.


Choices: Choices come from GJRJPRM.


4 Job Submission

User Level Defaults Block

Use this block to define the user-level default value for the selected parameter.

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions

No (Number) Number that identifies a specific parameter used to process a job or report. This number determines the order in which the job or report uses the parameters and the order in which the parameters appear on the Process Submission Control Form (GJAPCTL).

Column: GJBPDFT_NUMBER


Description Free-form description of the parameter.



System Default System-level default value for the parameter. This default applies to all users at your institution and is used only when a user ID has no user-level default for the parameter.

Column: GJBPDDFT_VALUE

Source: This value comes from the Default field on the Parameter Definition Form (GJAPDEF). It cannot be changed.


4 Job Submission

Copy Defaults to New User Window

Use this window to copy user-level defaults from the signed-on user ID to another user ID.

New User Block

Use this block to copy user-level defaults from the signed-on user ID to another user ID.

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions

User Default User-level default value for the selected parameter. This default appears on the Process Submission Control Form (GJAPCTL) when the signed-on user ID runs the job or report. The user can override the default on GJAPCTL.

Follow these guidelines to define a default value:

If specific parameter values are defined on the Parameter Value Validation Form (GJAPVAL), the default must equal one of these values.

• If a validation form is linked to the parameter on the Parameter Definition Form (GJAPDEF), the default must equal a value on the validation form.

• If a validation routine is linked to the parameter on GJAPDEF, the default must pass the special validation checking.

• The default must meet all validation criteria defined on GJAPDEF. These criteria include the data type, length, and range of values.

• If a validation routine is linked to the job or report on the Process Maintenance Form (GJAJOBS), the default must pass consistency checks applied to a group of parameters.

Note: Data-entry hints for the selected parameter appear at the bottom of the form. This information comes from the Help field on GJAPDEF.

Column: GJBPDFT_VALUE

Choices: If the parameter is linked to a validation form on GJAPDEF, choices come from the associated validation form. If valid values are defined for the parameter on GJAPVAL, choices come from the Parameter Values list.


4 Job Submission

Procedures

To create user-level defaults

You must be logged on with the user ID that will be linked to the defaults.

Note: Use these steps if the user ID has only one set of user-level defaults for the job or report.


2. Enter the Process.

3. Go to the next block. Parameters for the job or report appear with system defaults shown.

4. Select the parameter for which you want to create a user-level default.


6. Enter the User Default.

7. Save.

Note: You can also create a single set of user-level defaults on the Process Submission Control Form (GJAPCTL).

To change user-level defaults




3. If you are changing defaults for a job parameter set, enter the name of the Parameter Set.


5. Select the parameter for which you want to change a user-level default.

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions

New User User ID to whom the user-level defaults are to be copied.


Choices: Choices come from the User IDs list.


4 Job Submission


7. To change the default, enter the new User Default.

OR

To delete the default, select Remove Record.

8. Save.

Note: You can also change user-level defaults on the Process Submission Control Form (GJAPCTL).

To copy user-level defaults




3. If you are copying defaults in a job parameter set, enter the name of the Parameter Set.


5. Go to the Copy Defaults to New User window.

6. Enter the New User ID to whom the defaults are to be copied.

7. Save.

To clear all user-level defaults




3. If you are clearing defaults for a job parameter set, enter the name of the Parameter Set.



6. Select Clear Block.


4 Job Submission

Job Parameter Set Rule Form (GJRJPRM)

Use this form to define the names of the job parameter sets used at your institution. A job parameter set contains user-level defaults used to run a job or report. This feature lets you save frequently used combinations of user-level parameter values for running a job or report.

Note: GJRJPRM lets you establish the name of a job parameter set. The actual defaults in a set are defined for the signed-on user on the Process Submission Control Form (GJAPCTL) or Default Parameter Value Validation Form (GJAPDFT).

Job parameter sets provide a lot of flexibility in defining defaults. Different users can define different defaults with the same job parameter set name. For example, users JSMITH and KMYER might both use job parameter set YEAREND. JSMITH’s default for parameter 1 might be Y (yes), while KMYER’s default might be N (no).

In addition, a user can use different job parameter sets to run the same job. For example, a user can run the Person Directory (SPRPDIR) with one set of defaults for recruits, another set for students, and another set for faculty. Each set of defaults must have its own name.

Note: You can also create a new job parameter set when you submit a job or report for processing on GJAPCTL. The name of the new set is automatically added to GJRJPRM. The parameter values on GJAPCTL are stored as user-level defaults under the new job parameter set name.

Caution: A job parameter set cannot be deleted from GJRJPRM once any user-level defaults are defined for the set.

Main Window

Use this window to define the names of the job parameter sets used at your institution.

Job Parameter Set Block

Use this block to define the names of the job parameter sets used at your institution. A job parameter set is a set of user-level defaults used to run a job or report. This feature lets you save frequently used combinations of user-level parameter values for running a job or report.

Note: GJRJPRM lets you establish the name of a job parameter set. The actual defaults in a set are defined for the signed-on user on the Process Submission Control Form (GJAPCTL) or Default Parameter Value Validation Form (GJAPDFT).

Caution: A job parameter set cannot be deleted from this window once any user-level defaults are defined for the set.


4 Job Submission

Procedures

To create a job parameter set

1. Access the Job Parameter Set Rule Form (GJRJPRM).

2. Enter the Process name on a blank line.

3. Enter the Parameter Set name.

4. Enter the Description.

5. Save.

Note: You can also create a job parameter set on the Process Submission Control Form (GJAPCTL).

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions

Process Banner job or report for which you are defining a job parameter set. The job or report must be defined on the Process Maintenance Form (GJAJOBS).

Column: GJRJPRM_JOB


Parameter Set Name of the job parameter set. A job parameter set is a set of user-level defaults used to run the job or report. Each set must have its own name.

Note: To display the current user’s defaults for the selected job parameter set, select View Defaults from the Options menu.

Column: GJRJPRM_CODE

Description Free-form description of the job parameter set.

Column: GJRJPRM_DESC

Activity Date Date when the job parameter set was created or last updated.

Column: GJRJPRM_ACTIVITY_DATE


4 Job Submission

Process Results Form (GJARSLT)

Use this form to display a list of jobs and reports that were run through Job Submission.

Main Window

Use this window to display a list of jobs and reports that were run through Job Submission. Failure messages identify problems in batch processing and COBOL processes that were run online. You can query all jobs and reports that were run, or you can limit the query by entering selection criteria.

Information is display-only and cannot be changed. However, you can manually delete jobs and reports from the list.

Success messages older than two days and failure messages older than 30 days are automatically deleted. For jobs and reports that use the Alternate Logon Verification Form (GUAUIPW) to enforce an extra security check, these messages are deleted if the alternate user ID and password are validated. For OPS$ users, the SQL script delrslt deletes these messages.

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions

Process Banner job or report that was run.

Column: GJBRSLT_JOB

Source: This value comes from the name of the job or report that was run through Job Submission. It cannot be changed.

Process Number Process number.

Failure Message Failure message from batch processing or an online COBOL process.

Column: GJBRSLT_MESSAGE

Source: This value comes from the job or report that was run through Job Submission. It cannot be changed.

User ID User ID that created or last updated the record.

Activity Date Date when the job or report was run.

Column: GJBRSLT_ACTIVITY_DATE


4 Job Submission

Procedures

To query jobs and reports that were run with Job Submission

1. Access the Process Results Form (GJARSLT).

2. View the list of jobs and reports.

To delete a job or report from the Process Results Form (GJARSLT)

1. Access the Process Results Form (GJARSLT).

2. Select the job or report you want to delete from the form.

3. Select Remove Record.

4. Save.

Saved Output Review Form (GJIREVO)

Use this form to display output from a job or report that you ran on the Process Submission Control Form (GJAPCTL) and saved to the database.

Note: The job or report that created the output must have been run under your user ID with DATABASE in the Printer field on the Process Submission Control Form (GJAPCTL).

Main Window

Use this window to display output from a job or report that you ran on the Process Submission Control Form (GJAPCTL) and saved to the database. Once you display the output on GJIREVO, you can:

• Save the output to your local directory and print on a specified printer (Windows environment only)

• Save the output to your local directory without printing

• Delete the output from the database

Key Block

Use this block to identify the saved output you want to display. You can display only output from jobs and reports that you ran under your user ID and saved to the database.


4 Job Submission

Saved Output Block

Use this block to display the requested output file. This information is display-only and cannot be changed.

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions

Job Name Job or report that created the output you want to display. The job or report that created the output must:

• Be a Pro*C program.

• Have been run under your user ID with DATABASE in the Printer field on the Process Submission Control Form (GJAPCTL).


Choices: Choices come from a list of jobs saved in the database under your user ID.

Number Sequence number that uniquely identifies the specific job or report that was run. The system assigns this number when the job or report is run and displays it in the Auto Hint on the Process Submission Control Form (GJAPCTL).


Choices: Choices come from a list of jobs saved in the database under your user ID.

File Name Output file you want to display. Format is job name_job number.extension.


Choices: Choices come from a list of output files saved in the database under your user ID for the job or report and number.

Lines Number of lines in the output file.


Source: This value is calculated by the system. It cannot be changed.


4 Job Submission

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions

Output (untitled) Contents of the requested output file. This information is display-only and cannot be changed.


Source: This output comes from a job or report that you ran on the Process Submission Control Form (GJAPCTL) and saved to the database.


4 Job Submission

Procedures

To display saved output:

The job or report that created the output must:




2. Enter the Process that created the output.

3. Enter the Number that identifies the specific job or report that was run.

4. Enter the File Name of the output file.

5. Review the displayed output.

To save output and print:








5. Select Save and Print from the Options menu.

To delete saved output








4 Job Submission


5. Select Delete Output from the Options menu.

6. To delete the file, click OK in the dialog box.

OR

To cancel the deletion, click Cancel in the dialog box.

Job Submission Profile Maintenance Form (GJAJPRF)

Use this form to specify values for the GURJOBS_DIRECTORY parameter on Unix and OpenVMS platforms. Job Submission uses these values to process batch jobs.

When using Record>Insert on GJAJPRF to specify a different Job Submission directory, the Operating System value automatically populates with:

• UNIX, if forms are running on Unix based app server

• WIN32COMMON, if forms are running on a Windows application server

Note: Your GJAJPRF preferences may disappear after an upgrade if your upgraded forms are running on a different platform (i.e., if your site upgraded from client/server to a Unix-based application server for INB).

Note: Although this form is still available in Banner, enhancements to Oracle*Reports functionality make it unnecessary.

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions

Operating System

Operating system for which the defaults apply.

Column: GURUPRF_KEY

Source: This value is supplied by the system. It cannot be changed.

Component Name of the output parameter.

Column: GURUPRF_STRING

GURJOBS_DIRECTORY - This parameter identifies the directory used to save your output from Pro*C jobs run with the Process Submission Control Form (GJAPCTL). This value may not appear if you are using the system-generated value.


4 Job Submission

To define the GURJOBS directory:

1. Access the Job Submission Profile Maintenance Form (GJAJPRF).

2. If the GURJOBS_DIRECTORY does not exist, select Insert Record. The record appears with the system-generated value.

3. Enter the new Value.

4. Save.

Value Value of the associated output parameter.

Column: GURUPRF_VALUE

GURJOBS_DIRECTORY parameter - The value is the directory used to save your output from Pro*C jobs run with the Process Submission Control Form (GJAPCTL). This value is created automatically when you run a job:

• For UNIX, Banner looks up the user ID in the /ETC/PASSWD file. If the user ID is found and the user has write privileges, the literal JOBSUB is added to the user’s home directory ($HOME). Otherwise, the value is left blank.

• For VMS, Banner looks up the user ID in the SYSUAF.LIS file. If the user ID is found and the user has write privileges, the name of the user’s default directory is used. Otherwise, the value is left blank.

You can enter any valid directory name for the GURJOBS_DIRECTORY parameter. For example, you may want to use a directory on a file system that can be exported and mounted to a PC. When you change the directory, GURJOBS creates a test file in the new location before accepting your entry.

Note: If the GURJOBS_DIRECTORY record does not appear on the Job Submission Profile Maintenance Form (GJAJPRF), use Insert Record to display it.

Note: To change the GURJOBS_DIRECTORY to your current home directory, enter LOOKUP in the Value field.

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions


4 Job Submission

Sleep Wake Maintenance Form (GJASWPT)

Use this form to monitor and control sleep/wake processing that has been set up for specific Banner processes in the Student System and the Accounts Receivable System. Sleep/wake processing is a method of running a process in a cyclical manner.

Note: Sleep/wake processing requires specific setups on the Printer Validation Form (GTVPRNT), System Distribution Initialization Information Form (SOADEST or TOADEST), and the Process Submission Control Form (GJAPCTL). See the Banner General Technical Reference Manual for more details.

Once sleep/wake processing is set up, you can use GJASWPT to:

• Change the number of seconds in the processing cycle by entering a new value in the Next cycle time field. The job “sleeps” until this time interval passes. Then it “wakes up” and performs any necessary processing.

• Stop sleep/wake processing for the process by entering N in the Continue to Run field. The process continues processing until the next time it “wakes up” and completes the processing cycle.

• Monitor whether any jobs ended abnormally, when the process last executed, when the process will execute next, the number of rows processed in the last wake interval, and the total number of rows processed since the process started.

Alternate Logon Verification Form (GUAUIPW)

Use this form to enter a user ID and password when a job or report requires an extra security check.

Use the Current Values block to enter a user ID and password when a job or report requires an extra security check. Two kinds of jobs and reports automatically call GUAUIPW:

• Selected Banner jobs and reports that run with Job Submission

• External host processes executed by selected Banner forms

An external COBOL program validates the ID and password and tries to connect you to Oracle. If the connection succeeds, control passes to the original form. If the connection fails, an error message appears and control returns to GUAUIPW.


4 Job Submission

Note: GUAUIPW appears automatically when a Banner job or external host process requires it. It does not appear on any Banner menus.

To enter an alternate logon:

1. Enter your Alternate User ID.

2. Enter your Alternate Password.

3. Select Verify.

4. Respond to the dialog boxes.

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions

Alternate User ID

Alternate user ID for accessing the job or report. The ID must be in the ALL_USERS table. The ID cannot begin with OPS$.

Alternate Password

Alternate password for accessing the job or report.


4 Job Submission



Chapter 5

Population Selection

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-3

5 Population SelectionDefinitions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-3

Validation Forms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-4

Related Processes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-4


Forms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-6

Population Selection Extract Inquiry Form . . . . . . . . . . . (GLIEXTR) . . . . . . 5-6Population Selection Extract Data Form . . . . . . . . . . . . . (GLAEXTR) . . . . . . 5-6Population Selection Definition Rules Form . . . . . . . . . . . (GLRSLCT) . . . . . . 5-7Population Selection Inquiry Form . . . . . . . . . . . . . . . (GLISLCT) . . . . . . 5-8Application Definition Rules Form . . . . . . . . . . . . . . . (GLRAPPL) . . . . . . 5-9Application Inquiry Form . . . . . . . . . . . . . . . . . . . . (GLIAPPL) . . . . . . 5-10Variable Rules Definition Form . . . . . . . . . . . . . . . . . (GLRVRBL). . . . . . 5-10Variable Inquiry Form . . . . . . . . . . . . . . . . . . . . . . (GLIVRBL) . . . . . . 5-11Object Definition Rules Form . . . . . . . . . . . . . . . . . . (GLROBJT) . . . . . . 5-11Object Inquiry Form . . . . . . . . . . . . . . . . . . . . . . (GLIOBJT) . . . . . . 5-11System Indicator Validation Form . . . . . . . . . . . . . . . . (GTVSYSI) . . . . . . 5-11Population Selection Result Inquiry Form . . . . . . . . . . . . (GLIRSLT) . . . . . . 5-12

5-1

Table of Contents




Overview


The Population Selection module lets you identify and group entities in the database (for example, people, vendors, and organizations). You can define selection criteria to identify and extract a subset of these entities to use in Banner reports, processes, and letters. Some of the functions you can perform in the Population Selection module are:

Population Selection • Manually create, change, and display a population of IDs for reports, processes, and letters.

• Define the rules used to select IDs from the Banner database for reports, processes, and letters.

• Define the functional areas (applications) used in the Population Selection and Letter Generation modules.

• Define the variables used in the Population Selection and Letter Generation modules to select a specific piece of data in the database.

• Define common rules, or objects, that are used in many different population selections and variables.

Definitions

The following definitions are useful for understanding the functions of the Population Selection module:

• Population. A set of Banner IDs used for reports, processes, and letters. A population is uniquely identified by an application, selection ID, creator ID, and user ID.

• Population selection. A set of rules used to select IDs from the Banner database for reports, processes, and letters. A population selection is uniquely identified by an application, selection ID, and creator ID.

• Application. A functional area with similar characteristics that can be applied to population selections, populations, and variables.

• Variable. A specific piece of data in the database and the set of rules used to select that data.

• Object. A set of common rules used in many different population selections and variables. Objects are not required, but they simplify data entry and provide some consistency.



Validation Forms

Population Selection forms use the following validation form. Refer to Chapter 2, Validation Forms, for additional information.

Related Processes

The following processes are related to the Population Selection module. For additional information, refer to Chapter 13, Reports and Processes.

• The Population Selection Extract Process (GLBDATA) extracts IDs (people and non-persons) from the Banner database based on the rules entered on the Population Selection Definition Rules Form (GLRSLCT). This is a COBOL program. If the results of this extract will be used to identify the population receiving a letter, it should be executed before running the Variable Data Extract Process (GLBLSEL). If the results of this extract will be used to identify the population to be used in a report, it must be executed before running that report.

• Parameter Selection Compile Process (GLBPARM) creates Job Submission parameters for all variables and selection IDs for a given application. This COBOL program that should be executed before the Automatic Letter Compilation Process (GLOLETT). Only execute this process when application rule changes require recompiling the associated population selections.

• Automatic Letter Compilation Process (GLOLETT) generates SQL statements from the rules entered on the Population Selection Definition Rules Form (GLRSLCT) and the Variable Rules Definition Form (GLRVRBL). This COBOL program that is executed automatically from the GLRSLCT Form when a population selection is created or changed and from the GLRVRBL Form when a variable is created or changed.


Forms in the Population Selection module can be accessed from the following menu.


GTVSYSI System Indicator Validation Form GLRAPPL Application Definition Rules Form



Population Selection also uses the Population Selection Result Inquiry Form (GLIRSLT), which is not called from the menu. This form displays a list of populations within a specific application.

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Population Selection Menu (*GENPOPSEL)

GLIEXTR Population Selection Extract Inquiry FormDisplays a population, which is a set of Banner IDs used for reports, processes, and letters.

GLAEXTR Population Selection Extract Data FormAllows you to manually create, change, and display a population, which is a set of Banner IDs used for reports, processes, and letters.

GLRSLCT Population Selection Definition Rules FormDefines a population selection, which is a set of rules used to select IDs from the Banner database for reports, processes, and letters.

GLISLCT Population Selection Inquiry FormDisplays a list of population selections within an application.

GLRAPPL Application Definition Rules FormDefines an application, which is a functional area that controls population selections, populations, and variables.

GLIAPPL Application Inquiry FormDisplays a list of all applications defined on the GLRAPPL Form.

GLRVRBL Variable Rules Definition FormDefines a variable, which is a specific piece of data in the database and the set of rules used to select that data.

GLIVRBL Variable Inquiry FormDisplays a list of the variables defined on the GLRVRBL Form for an application.

GLROBJT Object Definition Rules FormDefines an object, which is a set of common rules used in many different population selections and variables.

GLIOBJT Object Inquiry FormDisplays a list of objects defined on the GLROBJT Form.

GTVSYSI System Indicator Validation FormDefines codes that identify the Banner applications used at your institution.



Forms

This section describes each form in the Population Selection module. Forms are described in the order they appear on the Population Selection Menu (*GENPOPSEL).

Population Selection Extract Inquiry Form (GLIEXTR)

Use this form to display a population. A population is a set of Banner IDs used for reports, processes, and letters. A population is uniquely identified by an application, selection ID, creator ID, and user ID:

• The Application is the functional area that controls the population.

• The Selection ID identifies the population selection, or set of rules, that selected the IDs. Select the Search button to display population selection IDs on the Population Selection Inquiry Form (GLISLCT).

• The Creator ID is the Oracle ID of the user who created the population selection.

• The User ID is the Oracle ID of the user who selected the population. This ID defaults to the ID of the person logged on to Banner, but you can enter another ID to view a population selected by another user. The User ID must be an ID that previously ran the extract to obtain a population.

If a population selection is locked, only the creator ID can display any populations created with the population selection.

The Sys/Man radio group indicates how the ID was added to the population:

• Sys (System) indicates the Population Selection Extract Process (GLBDATA) selected the ID.

• Man (Manual) indicates the ID was manually added on the Population Selection Extract Data Form (GLAEXTR).

Population Selection Extract Data Form (GLAEXTR)

Use this form to manually create, change, and display a population. A population is a set of Banner IDs used for reports, processes, and letters. A population is uniquely identified by an application, selection ID, creator ID, and user ID:

• The Application is the functional area that controls the population.

• The Selection ID identifies the population selection, or set of rules, that selected the IDs. Select the Search button to display population selection IDs on the Population Selection Inquiry Form (GLISLCT).



• The Creator ID is the Oracle ID of the user who created the population selection.

• The User ID is the Oracle ID of the user who selected the population. This ID defaults to the ID of the person logged on to Banner, but you can enter another ID. The User ID must be an ID that previously ran the extract to obtain a population.

You can change or display only those populations created with your user ID. If a population selection is locked, only the creator ID can create, change, or display any populations created with the population selection.

Note: You can use the Population Selection Extract Inquiry Form (GLIEXTR) to display a population created by another user ID.

Once you display a population, you can manually change the contents of the population:

• To add an ID, select the Insert Record function. Select the Search button to search for an ID on the Person Search Form (SOAIDEN) or on the Non-Person Search Form (SOACOMP).

• To delete a specific ID, place your cursor in the ID field and select the Remove Record function.

• To delete all IDs in the population, select the Delete All? check box and select the Save function.

Population Selection Definition Rules Form (GLRSLCT)

Use this form to define, maintain, and copy a population selection. A population selection is a set of rules used to select IDs from the Banner database for reports, processes, and letters. For example, you can use a population selection to select a group of applicants for an orientation letter. A population selection is uniquely identified by an application, selection ID, and creator ID:

• The Application is the functional area that controls the population selection. Any application-level rules are automatically compiled into the population selection rules.

• The Selection ID identifies the population selection. Select the Search button to display population selection IDs on the Population Selection Inquiry Form (GLISLCT).

• The Creator ID is the Oracle ID of the user who created the population selection. This is the only person who can change any rules in the population selection.

You can copy the rules in an existing population selection and create a new population selection. You can change the application and selection ID. Your ID becomes the creator ID. A copied population selection can be changed as needed.



For complete information about using this form, refer to “Building a Population Selection” in Chapter 3, Processing.

Population Selection Inquiry Form (GLISLCT)

Use this form to display a list of the population selections within an application. A population selection is a set of rules used to select IDs from the Banner database for reports, processes, and letters.

Once you display the list of population selections, you can perform other functions:

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions

Application Level Rules Exist

Check box that indicates whether application-level rules exist and will be added to the displayed rules upon compilation. This field assists users in building rules and population extracts.

To perform this function: Perform these steps:

Display a count of the number of IDs in each population associated with a population selection

Select the population selection. Then select Selection ID Counts from the Options menu (or use the Duplicate Field function).

Display rules for a population selection (GLRSLCT)

Select the population selection. Then select Selection ID Rules from the Options menu (or use the Count Query Hits function).

Display a list of all populations in the application

Select List of Results from the Options menu (or use the Duplicate Record function).

Display a population (GLIEXTR)

Select List of Results from the Options menu (or use the Duplicate Record function). Then select View Population from the Options menu (or use the List function).

Maintain a population (GLAEXTR)

Select List of Results from the Options menu. Then select Maintain Population from the Options menu (or use the Duplicate Field function).



Application Definition Rules Form (GLRAPPL)

Use this form to define and maintain an application. An application is a functional area with similar characteristics that can be applied to population selections, populations, and variables.

You must provide a freeform Description and a System indicator. The System indicator identifies the Banner system associated with the application. This indicator updates information displayed on the Mail Query Form (GUIMAIL) when letters are printed.

An application can optionally include general, high-level rules used to select IDs. Any rules in an application are automatically included in all population selections controlled by the application. Population selections within an application have additional, more detailed rules that select specific populations. For example, an application can select undergraduate students. Within the application, various population selections might select seniors, resident students, and international students.

Note: If you change application rules, you must run the Parameter Selection Compile Process (GLBPARM) and the Automatic Letter Compilation Process (GLOLETT) to compile the changed application rules into each population selection controlled by the application.

The application selection rules reference fields within the Banner database. The rules are defined by entering values into the following fields:

• Data Element. Enter the name of the database column used in the selection rule. The name must be a valid database column in the Oracle data dictionary. Select the Search button to access the Object Inquiry Form (GLIOBJT) to search for an object. The column name, operator, and value automatically appear when you select an object.

• Operator. Enter an SQL operator (such as =, <>, >, or <). The operator is used to compare the Data Element and Value fields.

Note: For date comparisons, avoid using an equal sign (=) because dates are often stored with hours, minutes, and seconds. A better approach is to use less than (<), greater than (>), less than or equal (<=), or greater than or equal (>=). You might need an extra condition. For example, ACTIVITY_DATE is stored with hours, minutes, and seconds. Use these statements to find addresses changed on March 1, 2003:


• Value. Enter the value that is compared with the Data Element based on the Operator. This can be a constant literal, another database column name, or a dynamic parameter.



• The format of a constant literal depends on the data type of the Data Element field. For character data types, enclose the literal in single quotes. For numeric data types, enter numbers. For date data types, use the format ‘DD-MON-YY’ or ‘DD-MON-YYYY’. Do not use single quotes with SYSDATE.

• A database column name is validated against the Oracle data dictionary. If the data type (character, numeric, or date) of the column is not the same as that of the Data Element, a warning appears. You can override the warning and keep the value.

• The format of a dynamic parameter is an ampersand (&) followed by text (for example, &Letter_Code). When you extract a population with the Population Selection Extract Process (GLBDATA), the system prompts for each dynamic parameter in the application rules.


• AND/OR. Enter the connector that links statements with AND or OR logic. All lines in the Rules block, except the last line, must contain a connector.

Use open and closed parentheses to group nested statements for logical evaluation. You can use up to three levels of nested statements. The number of open parentheses on a line must equal the number of closed parentheses.

Application Inquiry Form (GLIAPPL)

Use this form to display a list of all applications defined on the Application Definition Rules Form (GLRAPPL). An application is a functional area with similar characteristics that can be applied to population selections, populations, and variables.

The Application code, Description, Sys, and Activity Date fields can be queried.

Variable Rules Definition Form (GLRVRBL)

Use this form to define, maintain, and copy a variable. A variable is a specific piece of data in the database and the set of rules used to select that data. Variables are used to:


• Reference subqueries in application rules, population selection rules, and variable rules.

Before a variable can be created, the application under which the variable is defined must be created on the Application Definition Rules Form (GLRAPPL).



For additional information, refer to “Defining Variables” in Chapter 3, Processing.

Variable Inquiry Form (GLIVRBL)

Use this form to display a list of all variables defined on the Variable Rules Definition Form (GLRVRBL) for an application. A variable is a specific piece of data in the database and the set of rules used to select that data. Variables are used to:



Object Definition Rules Form (GLROBJT)

Use this form to define and maintain an object. An object is a set of common rules used in many different population selections and variables. Objects are not required, but they simplify data entry and provide some consistency.

Once you define a set of rules as an object, you can reference the object rather than manually enter all the rules each time they are needed. For example, many variables and population selections use the current record for names and IDs. You can create an object with the rule spriden_change_ind is null and insert this object whenever it is needed.

Objects are not directly associated with an application; they can be referenced in any variable or population selection in any application. The selection rules that are contained within an object contain the same components as the selection rules used to define an application.

Object Inquiry Form (GLIOBJT)

Use this form to display a list of objects defined on the Object Definition Rules Form (GLROBJT). An object is a set of common rules used in many different population selections and variables.





Warning: Values on this form should not be changed because Banner requires the SunGard Higher Education-delivered values to identify the applications.


Population Selection Result Inquiry Form (GLIRSLT)

Use this form to display a list of populations within a specific application.


Chapter 6

Letter Generation

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-3

6 Letter GenerationValidation Forms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-3

Related Processes and Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-4


Forms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-6

Mail Query Form . . . . . . . . . . . . . . . . . . . . . . . . (GUIMAIL) . . . . . . 6-6Letter Process Form . . . . . . . . . . . . . . . . . . . . . . . (GUALETR) . . . . . 6-6Paragraph Form . . . . . . . . . . . . . . . . . . . . . . . . . (GUAPARA) . . . . . 6-7Variable Rules Definition Form . . . . . . . . . . . . . . . . . (GLRVRBL). . . . . . 6-8Variable Inquiry Form . . . . . . . . . . . . . . . . . . . . . . (GLIVRBL) . . . . . . 6-8Object Definition Rules Form . . . . . . . . . . . . . . . . . . (GLROBJT) . . . . . . 6-8Object Inquiry Form . . . . . . . . . . . . . . . . . . . . . . (GLIOBJT) . . . . . . 6-9Application Definition Rules Form . . . . . . . . . . . . . . . (GLRAPPL) . . . . . . 6-9Application Inquiry Form . . . . . . . . . . . . . . . . . . . . (GLIAPPL) . . . . . . 6-10Letter Code Validation Form . . . . . . . . . . . . . . . . . . (GTVLETR) . . . . . . 6-10Paragraph Code Validation Form . . . . . . . . . . . . . . . . (GTVPARA) . . . . . 6-12System Indicator Validation Form . . . . . . . . . . . . . . . . (GTVSYSI) . . . . . . 6-12Letter Display Form . . . . . . . . . . . . . . . . . . . . . . . (GUQLETR) . . . . . 6-12

6-1

Table of Contents



6 Letter Generation

Overview

6 Letter Generation

The Letter Generation module lets you generate letters or produce a download file that can be used to produce letters with Microsoft Word or WordPerfect. Some of the functions you can perform in the Letter Generation module are:

Letter Generation • Define the functional areas (applications) used in the Population Selection and Letter Generation modules.

• Define common rules (objects) that are used in many different population selections and variables.

• Define the variables used in the Population Selection and Letter Generation modules to select a specific piece of data in the database.

• Build paragraphs that include user-created text, variables, and formatting commands.

• Build a letter from these paragraphs.

• Extract variable data from the database for pending letters, or for a specific letter and selected population. (You can use the Population Selection module or a specific Banner process to select the population.)

• Merge the extracted variable data into the letter and generate letters, or produce a download file for Microsoft Word or WordPerfect.

Note: SunGard Higher Education does not support WordPerfect 8.0 and higher.

Validation Forms

Letter Generation forms use the following validation forms. Refer to Chapter 2, Validation Forms, for additional information.


GTVLETR Letter Code Validation Form GUALETR Letter Process Form

GTVPARA Paragraph Code Validation Form GUALETR Letter Process FormGUAPARA Paragraph Form

GTVSYSI System Indicator Validation Form GLRAPPL Application Definition Rules Form


6 Letter Generation

Related Processes and Report

The following processes and report are related to the Letter Generation module. For additional information, refer to Chapter 13, Reports and Processes.

• The Automatic Letter Compilation Process (GLOLETT) generates SQL statements from the rules entered on the Variable Rules Definition Form (GLRVRBL). This COBOL program is executed automatically when you create or change a variable on GLRVRBL. It adds the necessary pidm joins as part of the SQL statements.

• The Letter Extract Process (GLBLSEL) extracts variable data from the Banner database to be included when letters are printed. This COBOL program is run before executing the Letter Generation Print Process (GLRLETR). GLBLSEL can be run for all pending letters (letters waiting to be printed) for a letter code, or for a letter code for a specific population. If the letter cannot be created because no address existed in SPRADDR for that ID, or because the address was found but it is inactive, a log file will list the names and IDs for those who did not receive the letter. This listing is printed whether or not you elect to print the error report.

The messages are:

• ### Following persons did NOT meet Selection criteria and will not get a letter

• ### Following person did NOT meet Address criteria and will not get a letter

• The Letter Generation Print Report (GLRLETR) generates letters directly from Banner, prints a summary report, and updates the General Mail Table (GURMAIL). Alternatively, GLRLETR can produce a download file for Microsoft Word or WordPerfect.


Note: For Financial Aid, Advancement, Student, and other products that use a time frame parameter (such as fiscal or aid year, or term code), one method to allow for the letter to be run multiple times is to check the Allow Duplicates check box on the Letter Code Validation Form (GTVLETR).

Below is a select clause that can be run in sqlplus that you can use to keep track of people to whom you might have sent duplicate letters. It contains an example to identify those PIDMs that have already received the specific letter in the current fiscal year.

Note that you would need to enter the specific letter code as well as the last day the previous fiscal year ended indicated on the Fiscal Year Validation Form (ATVFISC).

select * from gurmail


6 Letter Generation

where gurmail_system_ind not in ('R','S')and gurmail_letr_code = '&LETRCODE' and gurmail_date init > to_date('&&fiscyr_end_date','DD-MON-YY') and gurmail_date_printed > to_date('&&fiscyr_end_date','DD-MON-YY');

Inspect both the gurmail_date_init and gurmail_date_printed columns rather than just the date_printed, since there might be some previous years’ letters actually printed in the current fiscal year.


Forms in the Letter Generation module can be accessed from the following menu.

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Letter Generation Menu (*GENLETTER)

GUIMAIL Mail Query FormLists printed letters and pending letters (those waiting to be sent) for an ID.

GUALETR Letter Process FormBuilds a letter from paragraphs created on the Paragraph Form (GUAPARA).

GUAPARA Paragraph FormBuilds a paragraph that can be inserted in letters on the Letter Process Form (GUALETR). A paragraph can include text, variables, and formatting commands.

GLRVRBL Variable Rules Definition FormDefines a variable, which is a specific piece of data in the database and the set of rules used to select that data.

GLIVRBL Variable Inquiry FormDisplays a list of the variables defined on the GLRVRBL Form for an application.

GLROBJT Object Definition Rules FormDefines an object, which is a set of common rules used in many different population selections and variables.

GLIOBJT Object Inquiry FormDisplays a list of objects defined on the GLROBJT Form.

GLRAPPL Application Definition Rules FormDefines an application, which is a functional area that controls population selections, populations, and variables.

GLIAPPL Application Inquiry FormDisplays a list of all applications defined on the GLRAPPL Form.


6 Letter Generation

Letter Generation also uses the Letter Display Form (GUQLETR), which is not called from the menu. This form displays the details of a letter, including the text, variables, and formatting commands.

Forms

This section describes each form in the Letter Generation module. Forms are described in the order they appear on the Letter Generation Menu (*GENLETTER).

Mail Query Form (GUIMAIL)

Use this form to list printed letters and pending letters (those waiting to be sent) for an ID.

The form displays different types of information depending on which Banner system created the letter. Some common information is displayed regardless of the originating system:

• Banner System associated with the letter

• Letter code and description

• Date Initiated (when the letter was created)

• Date Printed (blank if the letter is pending)

• User ID that created the letter

Each Banner system has its own Mail Form (xUAMAIL) where information is added and maintained. Refer to the documentation for the appropriate Banner system for additional information.

GTVLETR Letter Code Validation FormDefines codes that identify the letters you can generate in Banner.

GTVPARA Paragraph Code Validation FormDefines codes that identify the paragraphs used in Banner letters.

GTVSYSI System Indicator Validation FormDefines codes that identify the Banner applications used at your institution.

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Letter Generation Menu (*GENLETTER)


6 Letter Generation

Letter Process Form (GUALETR)

Use this form to build a letter from paragraphs created on the Paragraph Form (GUAPARA). You must specify the sequence in which the paragraphs appear.

The Letter code uniquely identifies the letter. These codes must be defined on the Letter Code Validation Form (GTVLETR).

The Paragraph codes identify the paragraphs in the letter. These codes must be defined on the Paragraph Code Validation Form (GTVLETR).

The Sequence number identifies the order in which the paragraphs appear in the letter.

Additional navigational options are available from the Options menu:

• To access the Letter Display Form (GUQLETR) and review the entire letter, select Letter Detail.

• To access the Paragraph Form (GUAPARA) and review paragraph details, select Paragraph Detail.

Paragraph Form (GUAPARA)

Use this form to build a paragraph that can be inserted in letters on the Letter Process Form (GUALETR). A paragraph can include text, variables, and formatting commands:

• Enter text as it should appear in the letter.

• You must build variables on the Variable Rules Definition Form (GLRVRBL) before you can insert them into a paragraph. Select the Search button on the Text/Variable/Formatting Command field to access the Variable Inquiry Form (GLIVRBL) to search for a variable associated with an application.

The value of variables included in a paragraph can be checked for NULL values. If the value of the variable being checked is NULL (in other words, no data has been extracted from the database for that variable), the logic in the paragraph can branch to a label defined elsewhere in the paragraph.

Example:

^IFNULL *REQUIREMENTS &NO_REQ

The literal ^IFNULL indicates that the value of the specified variable *REQUIRMENTS is being checked for NULL values. If the variable is NULL, the logic goes to the label called &NO_REQ; if the variable contains data, the next line in the paragraph is executed.


6 Letter Generation


• Formatting commands are an emulation of standard Oracle RPF commands. For more information, refer to Facility Oracle Report Formatting Emulation Commands in Chapter 3, Processing.

Variable Rules Definition Form (GLRVRBL)

Use this form to define, maintain, and copy a variable. A variable is a specific piece of data in the database and the set of rules used to select that data. Variables are used to:



Before a variable can be created, the application under which the variable is defined must be created on the Application Definition Rules Form (GLRAPPL).

For additional information, refer to Defining Variables in Chapter 3, Processing.

Variable Inquiry Form (GLIVRBL)

Use this form to display a list of all variables defined on the Variable Rules Definition Form (GLRVRBL) for an application. A variable is a specific piece of data in the database and the set of rules used to select that data. Variables are used to:



Object Definition Rules Form (GLROBJT)

Use this form to define and maintain an object. An object is a set of common rules used in many different population selections and variables. Objects are not required, but they simplify data entry and provide some consistency.

Once you define a set of rules as an object, you can reference the object rather than manually enter all the rules each time they are needed. For example, many variables and population selections use the current record for names and IDs. You can create


6 Letter Generation

an object with the rule spriden_change_ind is null and insert this object whenever it is needed.

Objects are not referenced directly within the text of a letter; they can be referenced in any variable or population selection in any application. The selection rules that are contained within an object contain the same components as the selection rules used to define an application.

Object Inquiry Form (GLIOBJT)

Use this form to display a list of objects defined on the Object Definition Rules Form (GLROBJT). An object is a set of common rules used in many different population selections and variables.

Application Definition Rules Form (GLRAPPL)

Use this form to define and maintain an application. An application is a functional area with similar characteristics that can be applied to population selections, populations, and variables.

You must provide a free-form Description and a System indicator. The System indicator identifies the Banner system associated with the application. This indicator updates information displayed on the Mail Query Form (GUIMAIL) when letters are printed.

An application can optionally include general, high-level rules used to select IDs. Any rules in an application are automatically included in all population selections controlled by the application. Population selections within an application have additional, more detailed rules that select specific populations. For example, an application can select undergraduate students. Within the application, various population selections might select seniors, resident students, and international students.

Note: If you change application rules, you must run the Parameter Selection Compile Process (GLBPARM) and the Automatic Letter Compilation Process (GLOLETT) to compile the changed application rules into each population selection controlled by the application.

The application selection rules reference fields within the Banner database. The rules are defined by entering values into the following fields:

• Data Element. Enter the name of the database column used in the selection rule. The name must be a valid database column in the Oracle data dictionary. Select the Search button to access the Object Inquiry Form (GLIOBJT) to


6 Letter Generation

search for an object. The column name, operator, and value automatically appear when you select an object.

• Operator. Enter an SQL operator (such as =, <>, >, or <). The operator is used to compare the Data Element and Value fields.

Note: For date comparisons, avoid using an equal sign (=) because dates are often stored with hours, minutes, and seconds. A better approach is to use less than (<), greater than (>), less than or equal (<=), or greater than or equal (>=). You might need an extra condition. For example, ACTIVITY_DATE is stored with hours, minutes, and seconds. Use these statements to find addresses changed on March 1, 2003:


• Value. Enter the value that is compared with the Data Element based on the Operator. This can be a constant literal, another database column name, or a dynamic parameter.

• The format of a constant literal depends on the data type of the Data Element field. For character data types, enclose the literal in single quotes. For numeric data types, enter numbers. For date data types, use the format ‘DD-MON-YY’ or ‘DD-MON-YYYY’. Do not use single quotes with SYSDATE.

• A database column name is validated against the Oracle data dictionary. If the data type (character, numeric, or date) of the column is not the same as that of the Data Element, a warning appears. You can override the warning and keep the value.

• The format of a dynamic parameter is an ampersand (&) followed by text (for example, &Letter_Code). When you extract a population with the Population Selection Extract Process (GLBDATA), the system prompts for each dynamic parameter in the application rules.


• AND/OR. Enter the connector that links statements with AND or OR logic. All lines in the Rules block, except the last line, must contain a connector.

Use open and closed parentheses to group nested statements for logical evaluation. You can use up to three levels of nested statements. The number of open parentheses on a line must equal the number of closed parentheses.


Use this form to display a list of all applications defined on the Application Definition Rules Form (GLRAPPL). An application is a functional area that controls population selections, populations, and variables.

The Application code, Description, System, and Activity Date fields can be queried.


6 Letter Generation


Use this form to define codes that identify the letters you can generate in Banner. Examples of letters include acknowledgement, applicant, and financial aid offer letters.

Letter codes are used throughout Banner. For example, you can assign letter codes to:

• IDs on the Mail Form (xUAMAIL) of various Banner systems.

• Dues information on the Dues Installment Form (AAADINS).

• Materials on the Material Form (SOAMATL).


Note: Use the Letter Process Form (GUALETR) to create the actual contents of a letter.

Select the Allow Duplicates check box to indicate a letter can be sent more than once to the same ID within a time frame. Clear the Allow Duplicates check box if a letter should be sent only once to the same ID within a time frame. The time frame depends on the Banner system sending the letter:

For this system: The time frame is:

Advancement For the Dues Acknowledgment Process (AAPACKN) and the Pledge/Gift Acknowledgment Report (AGPACKN), the time frame is the fiscal year. If duplicates are not permitted, an alternate letter can be sent if the Alternate Letter field contains a letter code.

For all other processing, no time frame is used.

Financial Aid The time frame is the aid year.

Student For Communication Plan Processing, no time frame is used if a valid materials code is entered on the Student Mail Form (SUAMAIL). An ID can receive only one mailing for a materials code, regardless of whether the Dupl check box is selected or cleared.

For all other processing, the time frame is the term.

Finance No time frame is used.

Human Resource No time frame is used.


6 Letter Generation

Paragraph Code Validation Form (GTVPARA)

Use this form to define codes that identify the paragraphs used in Banner letters. Paragraph codes can be assigned to letters on the Letter Process Form (GUALETR).

Note: Use the Paragraph Form (GUAPARA) to create the actual contents of a paragraph. To access GUAPARA, select Build Paragraph from the Options menu of GTVPARA.

If you use Duplicate Record to copy a paragraph code and create a new one, the associated paragraph text defined on GUAPARA is also copied.



Warning: Values on this form should not be changed, because Banner requires the SunGard Higher Education-delivered values to identify the applications.


Letter Display Form (GUQLETR)

Use this form to display the details of a letter, including the text, variables, and formatting commands. This is a query form only and cannot be accessed directly. To access this form, select Letter Detail from the Options menu on the Letter Process Form (GUALETR).

The Current Paragraph field displays the paragraph code associated with the line where the cursor is located. Use the scroll bar to scroll through all the paragraphs in the letter.


Chapter 7

General International Management

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-3

7 General International ManagementValidation Forms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-3


Forms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-7

Visa International Information Form . . . . . . . . . . . . . . (GOAINTL) . . . . . 7-7SEVIS Transmittal History Form . . . . . . . . . . . . . . . . . (GOASEVR) . . . . . 7-14SEVIS Information Form . . . . . . . . . . . . . . . . . . . . . (GOASEVS) . . . . . 7-34SEVIS Transmittal Status Query Form . . . . . . . . . . . . . . (GOISEVS) . . . . . . 7-53SEVIS Batch Header Inquiry Form . . . . . . . . . . . . . . . (GOISVBH) . . . . . 7-55Race Rules Form . . . . . . . . . . . . . . . . . . . . . . . . (GORRACE) . . . . . 7-57SEVIS Business Rules Form . . . . . . . . . . . . . . . . . . . (GORSVSQ) . . . . . 7-58

7-1

Table of Contents




Overview


The General International Management module lets you store information about foreign students attending your institution and create reports with that information. It has been designed to help institutions meet the requirements of the United States Bureau of Citizenship and Immigration Services (BCIS). If your institution is not located in the USA, you may not need this module.

Some of the functions you can perform in the General International Management module are:

General International

Management

• Store and maintain visa information for students, applicants, and employees

• Track visas for students, applicants and employees

• Create reports to track expiring visa documents

• Create SEVIS records to be sent to the Bureau

• Collect and report on race/ethnicity codes

Validation Forms

International Management forms use the following validation forms. Refer to Chapter 2, Validation Forms, for additional information.


GTVCELG Certification of Eligibility Validation Form

GOAINTL Visa International Information Form

GTVDOCM Documentation Code Validation Form GOAINTL Visa International Information Form

GTVSRCE Source Code Validation Form GOAINTL Visa International Information Form

GTVSVCC SEVIS Category Code Validation Form GOASEVS SEVIS Information Form

GTVSVCP SEVIS Consular Post Validation Form GOASEVS SEVIS Information Form

GTVSVCR SEVIS Creation Reason Code Validation Form


GTVSVDT SEVIS Dependent Termination Code Validation Form


GTVSVEL SEVIS Education Level Code Validation Form


GTVSVEP SEVIS EV End Program Reason Code Validation Form





Forms in the General International Management module can be accessed from the following menus.

GTVSVFT SEVIS Drop Below Full Time Reason Code Validation Form


GTVSVGO SEVIS Governmental Organization Code Validation Form


GTVSVIO SEVIS International Organization Code Validation Form


GTVSVIT SEVIS Infraction Type Code Validation Form


GTVSVPC SEVIS Exchange Visitor Position Code Validation Form


GTVSVRP SEVIS Request for Form Reprint Code Validation Form


GTVSVTR SEVIS Termination Reason Code Validation Form


GTVSVTS SEVIS Transmittal Status Code Validation Form

GOASEVR SEVIS Transmittal History Form

GTVSVAP SEVIS Auto-populate Code Validation Form

GORSVSQ SEVIS Business Rules Form

GTVSVBA SEVIS Business Action Code Validation Form

GORSVSQ SEVIS Business Rules Form

GTVVISS Visa Issuing Authority Validation Form GOAINTL Visa International Information Form

GTVRRAC Regulatory Race Validation Form GORRACE Race Rules Form


. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . General International Management Menu (*GENINTL)

*GENMVISA General Multi Visa MenuContains the menus that help you track visa information for students, applicants, and employees



*GENSEVIS General SEVIS MenuContains the menus that help you manage your institution’s relationship with the Bureau.

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . General Multi Visa Menu (*GENINTL)

GOAINTL Visa International Information FormAllows you to store and display information about the visas held by students, applicants, and employees.

GTVCELG Certification of Eligibility Validation FormProvides a list of certifications of eligibility for employment. Some examples, in the United States, are the I-20 and IAP-66.

GTVDOCM Documentation Code Validation FormProvides a list of documents that could be used to validate a visa request.

GTVSRCE Visa Source Code Validation FormProvides a list of documents that could be used to validate a visa request.

GTVVISS Visa Issuing Authority Validation FormLists the codes representing the agencies that may issue visas.

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . General SEVIS Menu (*GENSEVIS)

GOASEVR SEVIS Transmittal History FormDisplays the student’s or exchange visitor’s completed record, ready for transmittal to the Bureau. It will also display historical records.

GOASEVS SEVIS Information FormAllows you to store information about students and exchange visitors so it can be sent to the Bureau using the Internet. It contains SEVIS-specific data elements and dependent relationship information.

GOISEVS SEVIS Transmittal Status Query Form Allows you to view records that have been created from the SEVIS Batch Export Process (GORSEVE).

GTVSVCC SEVIS Category Code Validation FormAllows you to store data for the valid SEVIS exchange visitor category codes.

GTVSVCP SEVIS Consular Post Code Validation FormAllows you to store data for the valid SEVIS consular post codes.

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . General International Management Menu (*GENINTL)



GTVSVCR SEVIS Creation Reason Code Validation FormContains the codes that represent why the student or exchange visitor records were created, such as initial attendance or transfer.

GTVSVDT SEVIS Dependent Termination Code Validation Form Stores codes representing the reasons a person’s dependent is no longer included on the record. For example, the dependent may have left the United States.

GTVSVEL SEVIS Education Level Code Validation FormProvides codes representing education levels, for example, associate, bachelor, and other university-obtained degrees.

GTVSVEP SEVIS EV End Program Reason Code Validation FormStores codes representing the reasons an exchange visitor’s program could be ended.

GTVSVFT SEVIS Drop Below Full Time Reason Code Validation FormStores SEVIS drop below full time reason codes. They describe why the student did not carry enough credits to be considered a full-time student. Examples include illness and difficulty learning English.

GTVSVGO SEVIS Governmental Organization Code Validation FormStores SEVIS governmental organization codes. They describe the government organization that allowed the EV to enter the United States. An example would be the Department of State.

GTVSVIO SEVIS International Organization Code Validation FormStores SEVIS EV infraction codes. They describe the international organization that is sponsoring the EV while in the United States. An example would be the World Health Organization.

GTVSVIT SEVIS Infraction Type Code Validation FormStores SEVIS EV infraction type codes. An example would be the failure to extend a DS-2019 in a timely manner.

GTVSVRP SEVIS Request for Form Reprint Code Validation FormStores codes representing reasons for reprinting Visa request forms. The student may have lost the original, or it may have been damaged.

GTVSVTR SEVIS Termination Reason Code Validation FormStores SEVIS termination reason codes. They indicate why the student or exchange visitor was terminated from the school (expulsion, delinquency, etc.).




Forms

This section describes each form in the General International Management module. Forms are described in the order they appear on the General International Management Menu (*GENINTL).

The Race Rules Form (GORRACE) appears on the Miscellaneous General Forms Menu (*GENMISC).

Visa International Information Form (GOAINTL)

Warning: This form could display information that is considered confidential by certain individuals or institutions. When granting access to this form, please consult your site-specific policies for protecting confidential information.

This form allows you to store and display information about the visas held by students, applicants, and employees.

GTVSVTS SEVIS Transmittal Status Code Validation Form These codes are not defined by the Bureau. These codes are used by Banner to process your institution’s SEVIS transactions. They represent the status of a transaction, e.g., Processing Complete.

GTVSVAP SEVIS Auto-populate Code Validation FormStores the fields in the GOBSEVS table that will be populated automatically (auto-populated) from other Banner tables. Column names from the GOBSEVS table have been delivered.

GTVSVBA SEVIS Business Action Code Validation FormAllows you to define business action codes and the procedures they will execute. Two business actions are delivered as seed data; CREATE_STUDENT and CREATE_EV.

GORSVSQ SEVIS Business Rules FormAllows you to associate business actions or auto-populations with process code/rule code combinations.

GOISVBH SEVIS Batch Header Query Form Allows you to review the header information for batches that have been sent to the Bureau.




Note: The International Information Form (PPAINTL) and the Student International Information Form (SPAINTL) have been replaced by a General form, the Visa International Information Form (GOAINTL). When you access SPAINTL and PPAINTL now, you receive a message saying that the forms are query-only.

If you have data in those tables, you will need to convert it before using this module. Refer to the Banner General Release 5.5 Release Guide for instructions on how to perform this conversion.

Key Block

Visa Window

The Visa window consists of the Visa Information block and the Document Information block.

Visa Information Block

The Visa Information block allows you to see or enter visa information for the person or organization displayed in the key block. You can insert multiple records for the ID.

The current visa information, based on the system date and Start Date, is automatically displayed.

You can scroll through additional records, if they exist. The sequence number will advance automatically to indicate which record you are viewing. The most recent record has the highest number.

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions

ID The Banner ID for which you would like to see or enter visa information. It is the 9-digit Banner ID on SPRIDEN. You can enter the ID, or select the flashlight button to search for it on the Person Search Form (SOAIDEN) or the Alternate ID Search Form (GUIALTI). Required.

(Untitled) Name. The name of the person or organization. This is automatically populated from information stored in SPRIDEN, and is a combination of the last name, first name, and middle initial. Display-only.



. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions

Visa Type Type code for the visa. This can be added to the record, but not modified. Required.

(lookup) List Visa Type Code list (STVVTYP)

Visa Number The visa number, with a maximum length of 18 characters. Optional.

Nation of Issue The nation that issued this visa. Optional.

(lookup) List Nation Validation list (STVNATN)

Issuing Authority

The agency that authorized the issuance of the visa. Optional.

(lookup) List Visa Issuing Authority Code list (GTVVISS)

Port of Entry The port where the person entered the country. Optional.

(lookup) List Port of Entry Validation list (STVPENT)

Sequence Number

Indicates which visa’s information is being displayed. It is automatically incremented as new visa records are added for the person. Display-only.

Entry The entry visa indicator. Valid values are:

Selected - the visa is an entry visaCleared - the visa is some other type of visa (default)

Optional.

Number of Entries

The number of times this ID has used this visa to enter the country. If used, this must be a 2-digit number from 01 - 99. If Entry has been selected, this is required.

Date Requested The date the visa was requested. The default value is the system date, but you can change it. Optional.

Date Issued The date the visa was issued. The default value is the Date Requested, but you can change it. Optional.



You must save your changes before proceeding to the next block.

Document Block

This block lets you add multiple supporting documents for the visa in the Visa Information block.

Document codes, as defined on the Visa Type Code Form (STVVTYP), must be unique to allow multiple documents for each visa type and visa number combination. You can modify an existing document record with the same document code, but you cannot insert another document record with the same document code.

Records are displayed in ascending order by document code.

Start Date The date the visa started. The default value is the Date Issued, but you can change it. If you do change it, you cannot make it predate the Date Issued. Optional.

End Date The date the visa expired. It cannot predate the Start Date. Optional.

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions

Document The type of document that supports this visa.

(lookup) List Visa Document Code list (GTVDOCM)

Optional.

Description The description of the document code. It is populated automatically from GTVDOCM. Display-only.

Source The code identifying the source of the document code.

(lookup) List Visa Source Code list (GTVSRCE)

Optional.

Description The description of the source code. It is populated automatically from GTVSRCE. Display-only.

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions



Passport Window

This window contains information about the person’s passport, and about their admission and departure. It does not depend on the information in the Visa Information or Documentation Information blocks.

Date Requested The date the supporting documentation was requested. The default value is the system date, but you can change it. Required.

Disposition The status of the supporting documentation. Valid values are stored in a pull-down list. They are:

Pending - the documentation is being processed (default)Accepted - the documentation has been acceptedRejected - the documentation was rejected

Required.

Date Received The date the supporting documentation was received by your institution. The default value is the Date Requested, but you can change it. Optional.

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions

Number The passport number, with a maximum length of 15 characters. Optional.

Nation of Issue The nation that issued the passport.


Optional.

Expiration Date The date the passport expires as DD-MON-YYYY. Optional.

Status The passport’s status. Enter an I-94 status in this 3-character free-form field. Optional.

Expiration Date The date the admission/departure expires as DD-MON-YYYY. Optional.

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions



Certification of Eligibility Information Window

The Certification Information window allows you to see or enter information for the visa. It contains the following fields:

You must save your changes before proceeding to the next block.

Alien Registration Number

The alien registration number, with a maximum length of 15 characters. Optional.

Duration of Stay The duration of stay indicator. Valid values are:

Selected - the visa is for the length of stayCleared - the visa is not for the length of stay (default)

Optional.

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions

Certification The certification code for the visa.

(lookup) List Certification of Eligibility Code list (GTVCLEG)

Optional.

Number The certification number, with a maximum length of 11 characters. Optional.

Issue Date The date the certification was issued as DD-MON-YYYY. Optional.

Receipt Date The date the certification was received as DD-MON-YYYY. Optional.

Admission Request

The admission request code.

(lookup) List Admission Request Code Validation list (STVADMR)

Optional.

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions



Nationality Window

This window contains information about the nationality of the person or organization in the key block. It does not depend on information entered in any of the other blocks.

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions

Nation of Birth The nation where the person was born.


Optional.

Nation of Citizen

The nation where the person is currently a citizen.


Optional.

Native Language

The person’s native language.

(lookup) List Native Language Validation (STVLANG)

Optional.

Sponsor The sponsor code.

(lookup) List International Sponsor Validation list (STVSPON)

Optional.

Employment Type

The code for the type of employment the person has.

(lookup) List Employment Type Validation list (STVEMPT)

Optional.

Foreign Tax ID The tax identification number. This is a 9-character free-form field. Optional.



SEVIS Transmittal History Form (GOASEVR)

This form displays the student’s or exchange visitor’s completed record. It will also display historical records.

Note: A number of the fields are automatically populated with the corresponding data in the SEVIS Information Form (GOASEVS), Identification Form (SPAIDEN), and General Person Form (SPAPERS) when you select Create Student or Create Exchange Visitor from GOASEVS, or when the SEVIS Batch Export Process (GORSEVE) is run in update mode.

Most of the fields on this form are display-only.

The codes populated on this form are the SEVIS equivalents of Banner codes, which appear on GOASEVS. In addition, dates are displayed on this form in the Bureau-required format (YYYY-MM-DD) if they will be sent to the Bureau. GOASEVS displays all dates in the standard Banner format (DD-MON-YYYY).

Warning: You will maintain the status of your records on this form. When you save your changes, there is no mechanism in Banner to undo those changes.

Spouse Accompanying Person to Country

Indicates if the person’s spouse came to this country with them. Valid values are stored in a pull-down list. They are:

Not Reported - the information was not reported (default)Yes - the spouse did comeNo - the spouse did not come

Required.

Number of Children Accompanying Person

A 2-digit field where you can enter the number of children the person brought with them to the country. Optional.

Signature Available for Funds

Field for recording if a signature is required to release scholarship funds. Valid values are stored in a pull-down list. They are:

Not Reported - the information was not reported (default)Yes - Signature is requiredNo - Signature is not required

Required.

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions



The Creation Comment, Transfer Remarks and Issue Remarks fields have been consolidated into the Creation, Issue, Transfer Comments field on the Common Data window. The columns were not removed from the table so your history data is intact. A script, gselsevs.sql, has been provided to help you identify your historical data.

If you are using the fsaATLAS application, you will not use the SEVIS Transfer Adaptor (SEVISTA) to transmit your data to the Bureau. Instead, you will be creating a .csv file to be imported into fsaATLAS. When you run the SEVIS Extract Process (GORSEVE) in Extract mode with the parameters that create the .csv file, no records are populated in this form.

Key Block

This will contain an ID field and corresponding name field.

Common Data Window

This window contains data elements that are common to both foreign students and exchange visitors. Data for this block comes from the Common Data block of GOASEVS when Create Student or Create Exchange Visitor is selected, or when the GORSEVE process is run in update mode.

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions

ID The Banner ID for which you would like to see or enter SEVIS information. It is the 9-digit Banner ID on SPRIDEN. You can enter the ID, or select the search button to search for it on the Person Search Form (SOAIDEN) or the Alternate ID Search Form (GUIALTI). Required.

(Untitled) Name. The name of the person. This is automatically populated from information stored in SPRIDEN, and is a combination of the last name, first name, and middle initial. Display-only.

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions

Sequence The sequence number that identifies which SEVIS record you are viewing for the person. Records are listed in chronological order - the most recent has the highest number.

To view SEVIS history for this person, scroll through the records.



Status Code The code indicating if the record was accepted or rejected by the Bureau. You will receive this code from the Bureau after the record has been processed.

Warning: After you enter this information and save it, there is no mechanism in Banner to change it. The record is locked.

Submit Date The date the batch was submitted to the Bureau.

Creation Date The date the Status Code was entered. It is created automatically when the record is saved.

Transaction Status

A code indicating the transmittal status of the record (e.g., processing complete, pending response from SEVIS, etc.). Required.

(lookup) List SEVIS Transmittal Status Code list (GTVSVTS)

Creation Reason A code indicating why the record was created.

(lookup) List SEVIS Creation Reason Code list (GTVSVCR)

Creation, Issue, Transfer Comments

The Issue Remarks and Transfer Remarks, and Creation Comments fields have been combined into one, the Creation, Issue, Transfer Comments field. It is automatically populated from information on the SEVIS Information Form (GOASEVS).

Visa Type The Visa type code. It is automatically populated by running the SEVIS process, but you can change it.


Birth Nation The person’s country of birth. It is automatically populated by running the SEVIS process.

Note: This is the SEVIS equivalent of a Banner code.

Birth Nation Reason

Birth nation reason for exchange visitor when birth nation = U.S. or U.S Territory.

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions



Legal Nation The person’s nation of citizenship. It is automatically populated by running the SEVIS process.


Birth Date The date the person was born as YYYY-MM-DD. It is populated from SPAPERS automatically by running the SEVIS process.

Gender The person’s gender. This is automatically populated by running the SEVIS process. Valid values are:

M - MaleF - FemaleU - Unknown

Program Begin Date

The date the program began as YYYY-MM-DD. It is automatically populated by running the SEVIS process.

Program End Date

The date program should normally end as YYYY-MM-DD. It is automatically populated by running the SEVIS process.

Program New End Date

The date the program actually ended as YYYY-MM-DD. It is automatically populated by running the SEVIS process.

Cancel Program Extension

Cancel student program extension.

SEVIS Result Code Message

Enter the message that you received from the Bureau after transmitting the data.

Warning: After you enter this information and save it, there is no mechanism in Banner to change it.

Structure Update

The SEVIS data structure that has been updated with this transmission.

Termination Reason

The reason the student was terminated. It is automatically populated by running the SEVIS process.

(lookup) List SEVIS Termination Reason Code list (GTVSVTR)

Termination Date

The date the program was terminated as YYYY-MM-DD. It is automatically populated by running the SEVIS process.

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions



Termination Reason Comments

Comments about the person’s termination. It is automatically populated by running the SEVIS process.

Officer ID The SEVIS-created Officer ID for each student or exchange visitor. This field is primarily used for multi-campus institutions.

If this field was not used, the Officer ID entered for the SEVIS Batch Extract Process (GORSEVE) will be used.

Display-only.

SEVIS ID This is the identifier assigned to a student or exchange visitor by SEVIS after the first record has been submitted.

Print Required Indicator

If selected, the person has requested that a form be reprinted. This is automatically populated by running the SEVIS process.

Request ID This number is assigned to the transaction when it is sent to the Bureau. Display-only.

No Show (Exchange Visitor)

Exchange visitor no show status.

Reprint Reason Reprint reason for the student. Choices come from the GTVSVRP list of values.

Reprint Reason Comments

Reprint reason comments for the student.

Cancellation Reason (Student)

Student cancel reason.

Cancel Student or Invalidate EV comments

Optional cancel student comments or required invalidate exchange visitor comments.

Extend Program Comments

Comments about why the person’s program was extended. This is automatically populated by running the SEVIS process.

Activity Date Date on which this data was created or modified.

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions



Address/Common Financial Data Window

This window contains address and financial information for the student or exchange visitor. All the fields are display-only.

The system uses the Crosswalk Validation Table (GTVSDAX) to determine which address type codes to use. The GTVSDAX code SVSUADDR represents the US address, and SVSFADDR represents the foreign address.

SEVIS Address Data


. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions

Last Name The person’s last name, populated from the Key block.

Suffix The person’s suffix, populated from the Key block.

First Name The person’s first name, populated from the Key block.

Middle Name The person’s middle name, populated from the Key block.

USA Address The address where the person is staying in the United States. It is populated from SPRADDR.

USA City The city where the person is staying in the United States. It is populated from SPRADDR.

USA State The state where the person is staying in the United States. It is populated from SPRADDR.

USA ZIP The zip code where the person is staying in the United States. It is populated from SPRADDR.

USA Routing Code

The 4-digit extension code used in U.S. addresses. It is populated from SPRADDR.

Foreign Address The person’s address outside the United States. It is populated from SPRADDR.

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions



SEVIS Common Financial Data Block

Student Data Window

This window contains student-specific data. All of the information in these fields is automatically populated from GOASEVS when you create the student’s record. They are display-only.

Foreign City The person’s city outside the United States. It is populated from SPRADDR.

Foreign Province

The person’s province outside the United States. It is populated from SPRADDR.

Foreign Postal Code

The person’s postal code outside the United States. It is populated from SPRADDR.

Nation The nation associated with the Foreign Address. It is populated with the SEVIS equivalent code for the Nation code on SPRADDR.

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions

Personal Funds The amount of the person’s funding provided by themselves, not an outside source. This is automatically populated by running the SEVIS process. This field will accept the value 0.

Funding Comment

Comments about the funding. This is automatically populated by running the SEVIS process.

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions

Program Enroll Date

The date the student was enrolled in the program as YYYY-MM-DD.

Current Session End Date

The date when the session ends as YYYY-MM-DD.

Next Session Start Date

The date when the session starts as YYYY-MM-DD.

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions



Commuter Indicator

Specifies if the student is a commuter from outside the USA.

Drop Below Full Time Reason

A code specifying why the student is no longer carrying enough credits to be considered a full-time student.

(lookup) List SEVIS Drop Below FT Reason Code list (GTVSVFT)

Drop Below Full Time Start Date

The date the student was authorized to drop below full-time as YYYY-MM-DD.

Drop Below Full Time End Date

The date the student resumed full-time study as YYYY-MM-DD.

Drop Below Full Time Comments

Comments about why the student is no longer taking enough credits to be considered a full-time student.

Cancel Drop Below Fulltime

Cancel drop below full-time request. Cannot cancel after start date.

Prior Drop Below FT Reason

Prior drop below full-time reason.

Resume Full Course Comments

Comments about the student’s return to full-time study.

Program Completion Comments

Comments regarding the student’s completion of the program in a free-form field.

Defer Attendance Start Date

The new start date due to the student’s deferred attendance as YYYY-MM-DD.

Defer Attendance End Date

The new end date due to the student’s deferred attendance as YYYY-MM-DD.

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions



Defer Attendance Comments

Comments about why the student’s attendance was deferred.

Verify Status Confirmation of status for the student- 6 month check.

Educational Level

A code specifying the student’s education level.

Primary Major A code specifying the student’s primary major.


Second Major A code representing the student’s secondary major.


Minor A code representing the student’s minor.


Education Level Comments

Any comments about the person’s education level.

Disciplinary Action Comments

Comments regarding the disciplinary action taken against the student in a free-form field.

Criminal Conviction

Indicates if the student has had a criminal conviction. Valid values include:

Selected - the student was convicted of a crimeCleared - the student was not convicted of a crime

Academic Term The number of months used to calculate expenses.

Length of Study The length of study in months.

School Code Code representing the school the student attends. This field is used primarily for multi-campus institutions.

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions



Student Financial and Common Travel Data Window

This window contains additional information about the student.

English Proficiency Required

Indicates if proficiency in English is required for the program in which the student is enrolled.

English Proficiency Met

Indicates if the student has the necessary proficiency in English for the program.

English Proficiency Remarks

SEVIS requires that a reason be provided if proficiency in English is not necessary for a program. The only time this field will be used is when the neither English Proficiency Required nor the English Proficiency Met check boxes have been selected.

Edit Program Comments

Comments about why the program information was edited.

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions

Tuition Expenses The dollar amount of the student’s tuition expenses.

Living Expenses The total living expenses for the student.

Dependent Expenses

The amount of money needed by the student’s dependents.

Other Expenses The amount of money needed by the student to cover any additional expenses that have not already been recorded.

Other Expenses Comments

Comments about the additional expenses.

School Funds The amount of money your institution is paying towards the cost of the student’s education.

School Funds Comments

Any comments about the school funding.

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions



Employment Funds

The amount of money the student receives through on-campus employment.

Other Funds The amount of money the student receives from other sources.

Other Funds Comments

Any comments about the other funds.

Passport Number

The identification number on the student’s passport.

Passport Nation A code representing the nation that issued the passport.


Passport Expiration Date

The date on which the student’s passport will expire.

Visa Number The identification number of the student’s visa.

Consular Post A code representing the consular post that issued the visa.

Visa Issue Date (Student and EV)

Visa issue date.

Visa Expiration Date

The date on which the student’s visa will expire.

Port of Entry A code representing the student’s port of entry.

Entry Date The date on which the student entered the United States.

Port of Entry Comments

Comments about the port of entry.

Admission Number

The student’s I-94 admission number.

Driver’s License The student’s driver’s license number.

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions



Student Employment Information Window

The following fields allow you to track student employment. You can store information for an unlimited number of employers per student, although the Bureau stores only 25.

License State Code

The state that issued the license.

SSN The student’s social security number.

TIN The student’s tax identification number.

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions

Sequence A sequence number that identifies the employer for the student. Each time a new employer is added, the form increments this number, so employer with the highest sequence number is the most recent. Display-only.

Authorized Indicates that the institution has given permission for the student to be employed. Valid values are:

Selected - the student is authorized to be employed Cleared - the student does not have proper authorization for employment

Display-only.

Employment Type

The Employment Type. Valid values are:

OPT - Optional practical trainingCPT - Curricular practical trainingOff_Campus - off-campus

Display-only.

Employment Code

The Employment Code. Valid values are:

Economic HardshipInternational OrganizationSpecial Student Relief

Display-only.

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions



Employment Time

Specifies whether the student is employed full- or part-time.

Full timePart time

Display-only.

Start Date The date the student began working for this employer.

End Date The date the student stopped working for this employer.

Course Relevance

Comments about how the employment is relevant to the student’s courses from the SEVIS Information Form (GOASEVS). Display-only.

Activity Date The date the record was created or last changed. Display-only.

Employer Name The Employer Name information from the SEVIS Information Form (GOASEVS).

Address The first line of the employer’s street address from the SEVIS Information Form (GOASEVS). Display-only.

(untitled) The second line of the employer’s street address from the SEVIS Information Form (GOASEVS). Display-only.

City The employer’s city from the SEVIS Information Form (GOASEVS). Display-only.

State The employer’s state code from the SEVIS Information Form (GOASEVS). Display-only.

ZIP The employer’s zip code from the SEVIS Information Form (GOASEVS). Display-only.

Routing Code The routing code for the employer’s zip code from the SEVIS Information Form (GOASEVS). Display-only.

Prior Start Date (Student)

Prior drop below full time start date.

Prior End Date (Student)

Prior drop below full time end date.

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions



Exchange Visitor Data Window

Use this window to view data pertaining to an exchange visitor. These fields are automatically populated from GOASEVS when you create the exchange visitor’s record.

Employment Comments

Additional comments about the employment from the SEVIS Information Form (GOASEVS). Display-only.

Cancel Employment (Student)

Cancel student employment.

Off Campus Recommendation

Off Campus Employment recommendation comments.

Prior Employment Code

Prior type of employment.

Prior Start Date Employment prior start date.

Prior End Date Employment prior end date.

OPT Academic Year Met (Student)

Indicate if student has met one full academic year requirement for OPT employment.

User ID The Banner ID of the person who created the record or changed it. Display-only.

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions

Form Number The number of the exchange visitor’s IAP66/DS2019 form.

Birth City The city where the exchange visitor was born.

Permanent Resident Nation

The country in which the exchange visitor resides permanently.


. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions



Position Code A code representing the exchange visitor’s position in your institution.

Category Code A code representing the exchange visitor’s category, e.g., Research Scholar.

Matriculation Type

The type of matriculation.

Subject Code A code representing the subject in which the exchange visitor is involved.


Subject Description

Provide remarks explaining the subject or field of study.

Subject Comments

Comments about the exchange visitor’s subject.

Program Sponsor Funds

The amount of money the exchange visitor receives from the program’s sponsor.

U.S. Government Agency Funds

Indicates if the exchange visitor receives funds from an agency of the U.S. government. This flag is automatically set if an agency code is entered on GOASEVS.

Agency #1 Code A code representing the government agency that is providing funding to the exchange visitor.

Agency #1 Name

U.S. Government agency name if code =OTHER.

Amount The amount of money the agency specified in the Agency #1 Code field is providing.

Agency #2 Code A code representing a second government agency that is providing funding to the exchange visitor.

Agency #2 Name


. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions




Organization #1 Code

A code representing the international organization that provided that funding.

Organization #1 Name

Organization name if code= OTHER.

Amount The amount of money the agency specified in the Org #1 Code field is providing.

Organization #2 Code

A code representing a second international organization that is providing funding to the exchange visitor.

Organization #2 Name



Other Organization Name

Other Organization name.

Exchange Visitor Government Funds

The amount of money the exchange visitor has received from his or her government.

Bi-national Comm. Funds

The amount of money received by the exchange visitor from a bi-national commission.

Other Organization Funds

The amount of money the exchange visitor has received from another organization.

Program Code Code representing the program with which the exchange visitor is associated. Display-only.

Initial Program Begin Date

The date that the program originally began for a continuing exchange visitor (the Creation Reason is CO). Display-only.

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions



Exchange Visitor Activity Site Information Window

This window allows you to track information on an unlimited number of activity sites per exchange visitor.

Note: To access this window, you may need to click on the icon to the right of the tabs to see a pull-down list of available tabs.

Amend Program Comments

Comments about why exchange visitor’s program was amended.

End Program Reason

A code representing the reason the exchange visitor’s program ended.

Program End Effective Date

The effective date of the program’s end as YYYY-MM-DD.

End Program Comments

Comments about why exchange visitor’s program ended.

Edit Biographical Data Comments

Comments on changes to the exchange visitor’s biographical data.

Infraction Code A code representing a minor or technical infraction for an exchange visitor.

Infraction Comments

Comments about the minor or technical infraction.

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions

Sequence A sequence number generated by the form to indicate the order in which the activity sites were entered. The site you entered most recently is the site that the form displays first. Display-only.

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions



Dependent Data Window

Use this window to view information about the student’s or exchange visitor’s dependents in the United States. It is display-only.

Terminated This indicator specifies if the site was terminated for this person. Valid values are:

Selected - the person is no longer participating in activities at this siteCleared - the person is still assigned to this site

Display-only.

Primary Site Primary site of activity.

Activity Site Name

The name of the exchange visitor’s activity site. Display-only.

Activity Site Address

The address of the activity site. Display-only.

City The city of the activity site. Display-only.

State The state of the activity site. Display-only.

ZIP The postal code for the activity site. Display-only.

Routing Code The routing code for the activity site. Display-only.

Activity Site Comments

Any comments about the activity site. Display-only.

Prior Activity Site Name

Name of prior activity site.



. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions



It is populated when you create the student’s or exchange visitor’s record. A separate view for dependent information is run in conjunction with both of those options and populates these fields.

Scroll to view the information for multiple dependents.

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions

Sequence The number created when a new record is stored to the database. Display-only.

Last Name The last name of the dependent.

Suffix The dependent’s suffix.

First Name The first name of the dependent.

Middle Name The middle name of the dependent.

SEVIS ID The SEVIS ID assigned to the dependent. This field will initially be blank because the ID is only returned by SEVIS after the first record is sent.

Relationship Code

The SEVIS code representing the relationship.

Birth Nation The SEVIS code representing the dependent’s birth nation.


Birth Nation Reason Code

Birth nation reason for dependent of exchange visitor when birth nation = U.S. or U.S Territory.

Legal Nation The SEVIS code representing the dependent’s country of citizenship.


Permanent Residency Nation (Exchange Visitor)

The nation in which the exchange visitor’s dependent permanently resides.




Visa Type A code representing the type of the dependent’s visa.


Form Purpose Dependent of exchange visitor form purpose to indicate text to print on DS 2019.

Delete Dependent (Exchange Visitor)

Delete dependent of exchange visitor.

Cancel Dependent (Student)

Cancel dependent of student.

Termination Code

A code indicating why the dependent is being removed from the record.

Termination Comments

Comments about the dependent’s termination.

Gender Radio buttons indicating the dependent’s gender. Valid values are:

MaleFemaleUnknown

Birth Date The dependent’s birth date as YYYY-MM-DD.

Birth City (Exchange Visitor)

The city where the exchange visitor’s dependent was born.


Activity Date Date on which the data was created or modified.

Terminate Effective Date

Date on which the dependent was terminated.

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions



SEVIS Information Form (GOASEVS)

Use this form to store information about students and exchange visitors so it can be sent to SEVIS using the Internet. It contains SEVIS-specific data elements and dependent relationship information.

This form displays the Banner codes and is where you enter the majority of the SEVIS information. To view the corresponding SEVIS codes, use the SEVIS Transmittal History Form (GOASEVR), which is where historical information is stored.

If you enter a Banner code that does not have a corresponding SEVIS code, you will receive an error message when you select Create Student or Create Exchange Visitor from the Options pull-down menu.

Warning: You can create SEVIS records on this form by selecting Create Student or Create Exchange Visitor from the Options pull-down menu. You can also create them by running the GORSEVE process.

There is no mechanism in Banner to change SEVIS records after they have been created. All the fields on GOASEVR are display-only, except for Status Code, SEVIS Result Code Message, and Transaction Status.

Key Block

This will contain an ID field and corresponding name field.

Reprint Request Request reprint for dependent of student.

Reprint Reason Reprint reason code for dependents of exchange visitors. Choices come from the GTVSVRP list of values.

Reprint Reason Comments

Reprint comments for dependents of exchange visitors when reprint reason code = OTHER.

Dependent Comments

Any additional comments about the dependent.

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions



Common Data Window

This window contains data elements that are common to both foreign students and exchange visitors.

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions

ID The Banner ID for which you would like to enter SEVIS information. It is the 9-digit Banner ID on SPRIDEN. You can enter the ID, or select the search button to search for it on the Person Search Form (SOAIDEN) or the Alternate ID Search Form (GUIALTI). Required.

Name (untitled) Name of the person. This field is automatically populated from information stored in SPRIDEN, and is a combination of the last name, first name, and middle initial. Display-only.

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions

Creation Reason The reason the student or exchange visitor record was created.

(lookup) List SEVIS Creation Reason Code list (GTVSVCR)

Creation, Issue, Transfer Comments

Remarks about why the record was created, why a new visa was issued, or why the student transferred, up to 500 characters in length. Select the Comments icon to access the Banner Editor. If Creation Reason is O or T, this field is required.

Visa Type The Banner code representing the Visa type.


Legal Nation The Banner code representing the person’s nation of citizenship, up to 30 characters in length. The code you enter here must have a SEVIS equivalent code.


Birth Nation The Banner code representing the person’s country of birth.




Birth Nation Reason

Birth nation reason for exchange visitor when birth nation = U.S. or U.S Territory.

Program Begin Date

The date the program began as DD-MON-YYYY.

Program End Date

The date program should normally end as DD-MON-YYYY.

Program New End Date

The date the program actually ended as DD-MON-YYYY.

Extend or Shorten Program Comments

Comments about why the student’s program was extended, up to 500 characters. Select the Comments icon to access the Banner Editor.

Cancel Program Extension

Cancel student program extension.

Termination Reason

The Banner code representing the reason the student was terminated.

(lookup) List SEVIS Termination Reason Code list (GTVSVTR)

Termination Date

The date the program was terminated as DD-MON-YYYY.


Comments about the person’s termination, up to 500 characters. Select the Comments icon to access the Banner Editor.

Cancellation Reason

Student cancellation reason. Choices come from the GTVSVCA list of values.

Cancel Student or Invalidate EV

Optional Cancel Student Comments or Required Invalidate Exchange Visitor Comments.

No Show (Exchange Visitor)

Exchange visitor no show status.

SEVIS ID This is the identifier assigned to a student or exchange visitor by SEVIS after the first record has been submitted.

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions



Student Data Window

Use this window to enter student-specific data.

Officer ID Enter a SEVIS-created Officer ID for each student or exchange visitor. This field is primarily used for multi-campus institutions.

Officer ID information is required by SEVIS, but this field is optional. If you do not enter the information here, the Officer ID entered for the SEVIS Batch Extract Process (GORSEVE) will be used.

Print Request Indicator

Allows you to request that a form be printed for the student or exchange visitor. Valid values are:

Selected - A form should be printedCleared - A new form is not needed

Reprint Reason Reprint reason for the student. Choices come from the GTVSVRP list of values.

Reprint Comments

Reprint comments for the student.

Edit Student Person Info or Exchange Visitor Bio

Comments about changed Student personal or Exchange Visitor biographical data (maximum of 500 characters).

Personal Funds The amount of the person’s funding provided by themselves, not an outside source.

Funding Comment

Comments about the funding, up to 500 characters. Select the Comments icon to access the Banner Editor.



. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions



. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions

Program Enroll Date

The date the student was enrolled in the program as DD-MON--YYYY.

Current Session End Date

The date when the session ends as DD-MON-YYYY.

Next Session Start Date

The date when the session starts as DD-MON-YYYY.

Drop Below Full Time Reason

A code specifying why the student is no longer carrying enough credits to be considered a full-time student.

(lookup) List SEVIS Drop Below FT Reason Code list (GTVSVFT)

Drop Below Full Time Start Date

The date the student was authorized to drop below full-time status as DD-MON-YYYY.

Drop Below Full Time End Date

The date the student assumed a full-time course load again, in DD-MON-YYYY format.

Cancel Drop Below Fulltime

Check box that indicates whether you want to cancel the drop below full time request. You cannot cancel after the start date.

Cancel Education Level Change Request

Cancel education level change request.

Drop Below Full Time Comments

Comments about why the student is no longer taking enough credits to be considered a full-time student. The field can hold up to 500 characters. Select the Comments icon to access the Banner Editor.

Program Completion Comments

Comments regarding the student’s completion of the program in a free-form field. The maximum length is 500 characters. Select the Comments icon to access the Banner Editor.

Disciplinary Action Comments

Comments regarding the disciplinary action taken against the student in a free-form field. The maximum length is 500 characters. Select the Comments icon to access the Banner Editor.



Criminal Conviction

Indicates if the student has had a criminal conviction. Valid values are:

Selected - the student was convicted of a crimeCleared - the student was not convicted of a crime

Education Level A code specifying the student’s education level.

(lookup) List SEVIS Education Level Code list (GTVSVEL)

Education Level Comments

Any comments about the student’s education level, up to 500 characters. This is required if the Education Level is Other.

Primary Major A Banner code specifying the student’s primary major.

(lookup) List All Major Codes list (STVMAJR)

Secondary Major

Code representing the student’s secondary major.


Minor Code representing the student’s minor.


Academic Term The number of months used to calculate expenses.

Length of Study The length of study in months.

School Code Code representing the school the student attends. This field is used primarily for multi-campus institutions. You can use it to make sure a person is assigned to a particular school.

Verify Status Confirmation of status - 6 month check.

Defer Attendance Start Date

The new start date because of the student’s deferred attendance as DD-MON-YYYY.

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions



Defer Attendance End Date

The new end date because of the student’s deferred attendance as DD-MON-YYYY.

Defer Attendance Comments

Comments about why the student’s attendance was deferred, up to 500 characters. Select the Comments icon to access the Banner Editor.

Commuter Indicator

Specifies if the student is a commuter. Valid values are:

Selected - the student is a commuter from outside the USA, they do not have a local US addressCleared - the student does not commute from outside the USA, they have a US address

If cleared, the student must have a US address on SPAIDEN.

Note: This only applies to students living in Canada and Mexico.

English Proficiency Required

Indicates if proficiency in English is required for the program in which the student is enrolled. Valid values are:

Selected - proficiency in English is requiredCleared - proficiency in English is not required

English Proficiency Met

Indicates if the student has the necessary proficiency in English for the program. Valid values are:

Selected - the student has the necessary proficiency Cleared - the student does not have the necessary proficiency

English Proficiency Remarks

SEVIS requires that a reason be provided if proficiency in English is not necessary for a program. You must enter comments in this free-form field if the English Proficiency Req check box is cleared. The only time you can enter data into this field is when the neither English Proficiency Req nor the English Proficiency Met check boxes have been selected.

You can enter up to 500 characters. Select the Comments icon to access the Banner Editor.

Edit Program Comments

Comments about why the program information was edited, up to 500 characters. Select the Comments icon to access the Banner Editor.

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions



Student Financial and Common Travel Data Window

This window contains financial and port of entry information for the student.

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions

Tuition Expenses The dollar amount for the student’s tuition expenses.

Living Expenses The total living expenses for the student.

Dependent Expenses

The amount of money needed by the student’s dependents.

Note: If you add a dependent and you see the message asking you to update the dependent expenses, you should do it. If you do not heed the message, and you run GORSEVE, the file will be rejected by SEVIS.

Other Expenses The amount of money needed by the student to cover any additional expenses that have not already been recorded.

Other Expenses Comments

Comments about the additional expenses in a free-form field, up to 500 characters. Select the Comments icon to access the Banner Editor.

School Funds The amount of money the student receives from the institution for an academic term.

School Funds Comments

Any comments about the school funding, up to 500 characters. Select the Comments icon to access the Banner Editor.

Employment Funds

The amount of money the student receives through on-campus employment.

Other Funds The amount of money the student receives from other sources.

Other Funds Comments

Any comments about the other funds, up to 500 characters. Select the Comments icon to access the Banner Editor.

Passport Number

The identification number on the student’s passport.

Passport Nation A code representing the nation that issued the passport.

(lookup) List Nation Validation List (STVNATN)



Student Employment Window

This window allows you to track student employment. You can store information for an unlimited number of employers per student, although the Bureau stores only 25.

Passport Expiration Date

The date on which the student’s passport will expire in DD-MON-YYYY format.

Visa Number The identification number of the student’s visa.

Visa Issue Date (Student and EV)

Visa issue date.

Visa Expiration Date

The date on which the student’s visa will expire in DD-MON-YYYY format.

Consular Post A code representing the consular post that issued the visa.

(lookup) List SEVIS Consular Post Code list (GTVSVCP)

Port of Entry A code representing the student’s port of entry.

Entry Date The date on which the student entered the United States.

Admission Number

The student’s I-94 admission number.

Travel Remarks Comments about the port of entry, up to 500 characters. Select the Comments icon to access the Banner Editor.

Driver’s License The student’s driver’s license number

License State Code

The state that issued the license.

(lookup) List State/Province Code Validation list (STVSTAT)

TIN The student’s tax identification number, up to 9 characters.

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions



. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions

Sequence A sequence number that identifies the employer for the student. Each time a new employer is added, the form increments this number, so employer with the highest sequence number is the most recent. Display-only.

Employer ID The Banner ID for the employer in SPRIDEN.

(lookup) List Person Search list (SOAIDEN)

(lookup) Count Hits Non-Person Search list (SOACOMP)

(lookup) Duplicate Item SSN/SIN/TFN Alternate ID Search list (GUIALTI)

Employer Name If there is no Banner ID for the employer, you must enter the employer’s name here. If there is a Banner ID for the employer, the corresponding name information is automatically populated from SPRIDEN. The Employer Name can be up to 500 characters in length. This field is actually an Edit box like the comments fields.

Employment Type

Select the type from the pull-down menu. Valid values are:

OPT - Optional practical trainingCPT - Curricular practical trainingOff_Campus - off-campus

Employment Code

Select the code from the pull-down menu. Valid values are:

Economic HardshipInternational OrganizationSpecial Student Relief

Employment Time

Select the time from the pull-down menu. Valid values are:

Full timePart time

Employment Start Date

The date the student began working for this employer, in DD-MON-YYYY format.

Employment End Date

The date the student stopped working for this employer, in DD-MON-YYYY format.



Address Type Code

If you enter a Banner ID, this field is required. The valid address type codes depend on the Banner ID. If you did not enter a Banner ID, this field is null, and you must enter the address information manually.

(lookup) List Address Type Validation list (STVATYP)

Employer Address

The employer’s street address. It is automatically populated from SPAIDEN, based on the Address Type Code you chose for the Employer ID. If no Employer ID has been entered, you must enter this information.

City The employer’s city. It is automatically populated from SPAIDEN, based on the Address Type Code you chose for the Employer ID. You can only add addresses or change them on SPAIDEN. Display-only.

State The employer’s state code. It is automatically populated from SPAIDEN, based on the Address Type Code you chose for the Employer ID. You can only add addresses or change them on SPAIDEN. However, if no Employer ID was entered, you can update this information manually.


ZIP The employer’s zip code. It is automatically populated from SPAIDEN, based on the Address Type Code you chose for the Employer ID. You can only add addresses or change them on SPAIDEN. However, if no Employer ID was entered, you can updated this information manually.

(lookup) List Zip/Postal Code Validation list (GTVZIPC)

Cancel Check box that indicates whether you want to cancel OPT, OCE, or CPT employment.

OPT Academic Year Met

Indicate if student has met one full academic year requirement for OPT employment.

Course Relevance

Comments about how the employment is relevant to the student’s courses. The field can hold up to 500 characters. Select the Comments icon to access the Banner Editor.

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions



Exchange Visitor Data Window

Use this window to maintain data pertaining to an exchange visitor.

Off Campus Recommendation

Off Campus Employment recommendation comments.

Employment Comments

Additional comments about the employment. The field can hold up to 500 characters. Select the Comments icon to access the Banner Editor.



. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions

Birth City The city where the exchange visitor was born, up to 200 characters.

Permanent Residency Nation

The country in which the exchange visitor resides permanently.


Position Code A code representing the exchange visitor’s position in your institution.

(lookup) List SEVIS Position Code list (GTVSVPC)

Category Code A code representing the exchange visitor’s category, e.g., Government Visitor.

(lookup) List SEVIS Category Code list (GTVSVPC)

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions



Matriculation Type

The type of matriculation. Valid values found on a pull-down menu are:

None (default)Associates to BachelorsBachelors to MastersMasters to Doctorate

Subject Code A code representing the subject in which the exchange visitor is involved.


Subject Description (EV)

Provide remarks explaining the subject or field of study.

Subject Comments

Comments about the exchange visitor’s subject, up to 500 characters in length. Select the Comments icon to access the Banner Editor.

Validate Participant

Indicates if the person has permission to be an exchange visitor. Valid values are:

Selected - the person is a valid exchange visitorCleared - the person is not yet a valid exchange visitor (default)

Program Sponsor Funds

The amount of money the exchange visitor receives from the program’s sponsor.

Agency #1 Code A code representing the government agency that is providing funding to the exchange visitor.

(lookup) List SEVIS Government Organization Code list (GTVSVGO)

Agency #1 Name (EV)



. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions



Agency #2 Code A code representing a second government agency that is providing funding to the exchange visitor.

(lookup) List SEVIS Government Organization Code list (GTVSVGO)

Agency #2 Name (EV)



Org #1 Code A code representing the international organization that provided that funding.

(lookup) List SEVIS International Organization Code list (GTVSVIO)


Organization #1 Name (EV)


Org #2 Code A code representing a second international organization that is providing funding to the exchange visitor.

(lookup) List SEVIS International Organization Code list (GTVSVIO)

Organization #2 Name (EV)



Other Organization Name (EV)

Other Organization name.

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions



Exchange Visitor Government Funds

The amount of money the exchange visitor has received from his or her government.

Bi-national Commission Funds

The amount of money received by the exchange visitor from a bi-national commission.

Other Organization Funds

The amount of money the exchange visitor has received from another organization.

Program Code Code representing the program with which the exchange visitor is associated. You can use it to make sure that a person is assigned to a particular program.

Amend Program Comments

Comments about why exchange visitor’s program was amended, up to 500 characters in length. Select the Comments icon to access the Banner Editor.

End Program Reason

A code representing the reason the exchange visitor’s program ended.

(lookup) List SEVIS End EV Program Reason Code list (GTVSVEP)

Program End Effective Date

The effective date of the program’s end as DD-MON-YYYY.

End Program Comments

Comments about why exchange visitor’s program ended, up to 500 characters in length. Select the Comments icon to access the Banner Editor.

Edit Biographical Data Comments

Enter any comments about the exchange visitor’s biographical data, up to 500 characters. Select the Comments icon to access the Banner Editor.

Infraction Code A code representing a minor or technical infraction for an exchange visitor.

(lookup) List SEVIS Infraction Code list (GTVSVIT)

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions



Exchange Visitor Activity Site Data Window

This window allows you to track information on activity sites for each exchange visitor.

Infraction Comments

Comments about the minor or technical infraction, up to 500 characters. Select the Comments icon to access the Banner Editor.

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions

Sequence A sequence number generated by the form to indicate the order in which the activity sites were entered. The site you entered most recently is the site that the form displays first.

Termination Indicator

This indicator specifies if the site was terminated for this person. You cannot delete the site - it is retained as part of the person's history. Valid values are:

Selected - the person is no longer participating in activities at this siteCleared - the person is still assigned to this site

Site of Activity ID

The Banner ID for this activity site. When you enter the ID, the corresponding name information is populated from SPRIDEN.

(lookup) List Non-Person Search list (SOACOMP)

Primary Site Indicator

Primary site of activity for the exchange visitor.

Site of Activity Name

The name that corresponds to the Activity Site ID field. If the Activity Site ID was entered, this information is populated automatically from SPRIDEN. If it was not, you can enter the name information manually.

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions



Dependent Data Window

Enter information about the student’s or exchange visitor’s dependents in the United States on this window.

Address Type Code

Code representing the type of address the activity site has. If the Activity Site ID was entered, you can only enter a code that is valid for that ID. If no ID was entered, the code is null, and you can enter the address manually.

(lookup) List Address Type Code Validation list (STVATYP)

This field is required if an Activity Site ID has been entered.

Site of Activity Address

The address of the activity site.

City The city of the activity site.

State The state of the activity site.


ZIP The ZIP code for the activity site.

(lookup) List ZIP/Postal Code Validation Form (GTVZIPC)

Site of Activity Comment

Comments about the site of activity, up to 500 characters in length. Select the Comments icon to access the Banner Editor.



. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions



Use Insert Record to create multiple dependents. Use the scroll bar to view data for each one.

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions

Sequence The number created when a new record is stored to the database. Display-only.

ID The Banner ID for the dependent. It is the 9-digit Banner ID on SPRIDEN. You can enter the ID, or search for it on the Person Search Form (SOAIDEN) or the Alternate ID Search Form (GUIALTI). Optional.

Last Name The last name of the dependent.

Suffix The suffix for the dependent’s name. Valid values are listed on the Bureau’s website.

First Name The first name of the dependent.

Middle Name The middle name of the dependent.

SEVIS ID The SEVIS ID assigned to the dependent. This field will initially be blank since the ID is only returned by SEVIS after the first record is sent.

Relationship Code

The Banner relationship code.

(lookup) List Relationship Validation list (STVRELT)

Birth Nation The Banner code representing the dependent’s birth nation.


Birth Nation Reason

Birth nation reason for dependent of exchange visitor when birth nation = U.S. or U.S Territory.

Legal Nation The Banner code representing the dependent’s country of citizenship.




Gender Radio buttons indicating the dependent’s gender. Valid values are:

MaleFemaleUnknown (default)

Permanent Residency Nation (Exchange Visitor)

The nation in which the dependent permanently resides. This is required for the dependents of exchange visitors.


Visa Type A code representing the type of the dependent’s visa.


Form Purpose Dependent of exchange visitor form purpose to indicate text to print on DS 2019.

Delete Dependent (Exchange Visitor)

Delete the dependent of the exchange visitor.

Cancel Dependent (Student)

Check box that indicates whether you want to cancel the dependent.

Termination Code

A code indicating why the dependent is being removed from the record.

(lookup) List SEVIS Dependent Termination Code list (GTVSVDT)

Terminate Effective Date

The date the person was terminated as a dependent, in DD-MON-YYYY format.


Comments about the dependent’s termination, up to 500 characters. Select the Comments icon to access the Banner Editor.

Birth Date The dependent’s birth date as DD-MON-YYYY.

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions



SEVIS Transmittal Status Query Form (GOISEVS)

This form allows you to review records that have been created from the SEVIS Batch Export Process (GORSEVE).

For example, you can use this form to find out which records have been sent to the Bureau, and are awaiting the reply. Enter P in the Transmittal Status Code field, and submit the query. You can scroll through all the records.

You can review the records that were transmitted on a specific date by entering that date in the Submit Date field, and submitting the query.

You can also see pending records for a particular ID by entering that ID in the ID field and entering P in Transmittal Status Code.

Note: If you are running the SEVIS Extract Process (GORSEVE) in Extract mode with the parameters that create a .csv file, no records are populated in this form. For more information on GORSEVE’s parameters, refer to the Reports and Processes chapter

Birth City (Exchange Visitor)

The city where the dependent was born. This is required for the dependents of exchange visitors.



Reprint Request Check box that indicates whether you want to request a reprint for the dependent of student.

Reprint Reason Reprint reason code for dependents of exchange visitors. Choices come from the GTVSVRP list of values.

Reprint Comments

Reprint comments for dependents of exchange visitors when reprint reason code = OTHER.

Dependent Comments

Any additional comments about the dependent, up to 500 characters. Select the Comments icon to access the Banner Editor.

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions



Key Block

This block contains the fields you can use to query for data. You can query with each field, or a combination of them.

Record Block

The records that meet the criteria you specified appear in this block. All the fields in this block are queryable and display-only.

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions

Transmittal Status

The code representing the current status of the record. Valid values are:

(lookup) List SEVIS Transmittal Status list (GTVSVTS)

Submit Date The date the record was created as a SEVIS record (the date it could be viewed on GOASEVR) in DD-MON-YYYY format.

ID The Banner ID of the student or exchange visitor from SPRIDEN.

(Untitled) The name of the person who has the specified ID.

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions

ID The Banner ID of the student or exchange visitor from SPRIDEN.

SEVIS ID The ID given to the person by the Bureau. This will only be populated after the person’s record has been sent to the Bureau once.

Sequence A number indicating which record is displayed. Every time a record is created for the person, the sequence number is incremented.

Last Name The person’s last name.

First Name The first name of the student or exchange visitor.

Mi The person’s middle initial.



SEVIS Batch Header Inquiry Form (GOISVBH)

This form allows you to review the header information for batches that have been sent to the Bureau. You cannot modify the information, only see it. You can query on all fields.

This information is stored in the new SEVIS Batch Header Table (GORSVBH).

Note: If you are running the SEVIS Extract Process (GORSEVE) in Extract mode with the parameters that create a .csv file, no records are populated in this form. For more information on GORSEVE’s parameters, please refer to Chapter 13, Reports and Processes.

Key Block

The following fields appear in the key block:

Usage Pulldown list that indicates whether the record pertains to a student or to an exchange visitor.

Transmittal Status

The transmittal status code of the record.

Submit Date The date on which the record was created, in DD-MON-YYYY format.

Status The result code returned by the Bureau. Valid values are listed on the Bureau’s website.

Result A message from the Bureau pertaining to the transaction’s status.

Structure The structure to which the field belongs. The contents of the structures are defined by the Bureau.

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions

Create Date The date the batch was created.

Submit Date The date the batch was submitted to the Bureau.



Main Block

This block contains information about your batches. You cannot change the information in any of these fields. Each batch that matches your search criteria is displayed, and you can scroll down to see all of them.

You can query on all fields.

Return Date The date the response file came from the Bureau.

Batch Type The type of records that were sent in the batch. Select Student or Visitor from the pull-down list. The default value is All for all the records in the batch, both student and exchange visitor.

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions

Batch ID The ID number generated by GORSEVE. It is a combination of the date/time stamp and a 2-digit sequence number.

Type The type of records in the batch, or that you want to use in your search criteria. Valid values are:

S - StudentV - Exchange visitor

Date Created The date and time that the batch was created by GORSEVE, in DD-MON-YYYY HH:MI:SS format.

Date Submitted The date and time that the batch was sent to the Bureau, in DD-MON-YYYY HH:MI:SS format.

Returned Date The date and time that the response from the Bureau was returned and update in Banner, in DD-MON-YYYY HH:MI:SS format.

Processed The status of the batch. A batch is considered processed when it has been created by GORSEVE, sent to the Bureau, a response has been returned, and the Banner databases have been updated. Valid values are:

Selected - the batch has been processedCleared - the batch has not yet been completely processed

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions



Race Rules Form (GORRACE)

Use this form to create and maintain the institution-defined race codes that are used on the personal information forms throughout Banner.

Institutions in other countries that want to collect and report on race and/or ethnicity can also use this form to identify race/ethnicity codes.

School Code The code submitted in the batch header for student records. It is the code that was assigned to your school by the Bureau.

Program Code The code submitted in the batch header for exchange visitor records. It is code that was assigned to your exchange visitor program by the Bureau.

Officer The Officer ID of the person who submitted the batch to the Bureau. It is the code that was assigned to your SEVIS Officer by the Bureau.

Error Code The code returned by the Bureau to describe why an entire batch was rejected.

Error Message The description that corresponds to the Error Code, up to 500 characters.

Records In Batch The number of records that were submitted in the batch.

SEVISTA Rejected

The number of records in the batch that the SEVISTA process rejected. These records were never sent to the Bureau. You must correct the information in Banner and re-submit the records. The rejection is stored as part of each record’s history.

SEVIS Approved The number of records in the batch that the Bureau approved.

SEVIS Rejected The number of records in the batch that the Bureau rejected. You must update the records on GOASEVR to enter the rejection into history, and change the information on GOASEVS so GORSEVE can send the records to the Bureau again.

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions



SEVIS Business Rules Form (GORSVSQ)

This form allows you to associate business actions or auto-populations with process code/rule code combinations. You will use the Business Rules Form (GORRSQL) to associate the process code/rule code combinations with that you define on this form with programming logic.

Note: If the process code/rule code combinations are not identical on GORSVSQ and on GORRSQL, the rule will not work.

There are two categories of business rules:

1. Business Action - creates student or exchange visitor records under the circumstances you specify. The records are created automatically when you run GORSEVE from Job Submission with the correct parameter values, or from the SEVIS Information Form (GOASEVS) when you select Business Action from the Options pull-down menu.

2. Auto-populate - updates specific fields in the SEVIS tables from other fields in Banner. The fields are updated automatically when you run GORSEVE from Job Submission with the correct parameter values, or from the SEVIS Information Form (GOASEVS) when you select Auto-populate from the Options pull-down menu.

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions

Institution Race Institution-defined race code.

Description Description of the institution-defined race code.

Regulatory Race Regulatory race code associated with your institution-defined race code.

Choices come from the Regulatory Race Code (GTVRRAC) list.

EDI EDI Equivalent code.

LMS LMS Equivalent code.

User ID Oracle user ID that created or last updated the record.

Activity Date Date on which the record was last modified.



You can only delete business rules from this form if you have not used Process Code and Rule Code on the Business Rules Form (GORRSQL).

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions

Process Code The process code associated with the rule. SEVIS has been delivered.

(lookup) List Business Rule Process Code Validation list (GTVSQPR)

(Untitled) The description of the process code. Display-only.

Rule Code The rule code that represents the rule. Process code/rule code combinations must be unique.

(lookup) List Business Rule Code Validation list (GTVSQRU)

(Untitled) The description of the rule code. Display-only.

Sequence Number

The sequence number of the rule, sorted by process type and rule code. You can have multiple rows (sequences) per rule. Display-only.

Active Indicates if the rule is active. Valid values are:

Selected - the rule is activeCleared - the rule is no longer active


Start Date The date the rule becomes active, in DD-MON-YYYY format.

End Date The last day the rule is active, in DD-MON-YYYY format.




Process Type Specifies the process type for the rule. Valid values are:

Auto-populateBusiness Action

If you select Auto-populate, you will be creating a rule that will select columns of Banner data to enter into the corresponding GOBSEVS column. For example, you could decide which of the major codes used in Banner should be automatically entered as the Primary Major.

If you select Business Action, you will be creating a rule that will specify the conditions that will trigger the creation of a student or exchange visitor record. For example, you could decide that when a student's major is updated on the forms in Banner Student, a Create Student record will be generated to send the information to the Bureau.

SEVIS Auto-populate Code

Indicate the column and table you want to populate by your rule.

(lookup) List SEVIS Auto-populate Code Validation list (GTVSVAP)

You can only enter information in this field if the Process Type is Auto-populate.

SEVIS Business Action

Indicate the Business Action (package/procedure combination) your rule should trigger.

(lookup) List SEVIS Business Action Codes list (GTVSVBA)

You can only enter information in this field if the Process Type is Business Action.

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions


Chapter 8

System Functions & Administration

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-3

1 System Functions/AdministrationValidation Forms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-3

Related Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-5


Forms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-13

Currency Code Maintenance Form . . . . . . . . . . . . . . . (GUACURR) . . . . . 8-13Currency Codes Validation Form . . . . . . . . . . . . . . . . (GTVCURR) . . . . . 8-13Bank Code Rule Form . . . . . . . . . . . . . . . . . . . . . (GXRBANK) . . . . . 8-14Bank Code Query Form . . . . . . . . . . . . . . . . . . . . . (GXIBANK). . . . . . 8-18Bank Routing Number Validation Form . . . . . . . . . . . . . (GXVDIRD) . . . . . 8-19Direct Deposit Recipient Form . . . . . . . . . . . . . . . . . (GXADIRD) . . . . . 8-20EDI/ISO Standard Code Validation Form . . . . . . . . . . . . (GTVSCOD) . . . . . 8-23EDI Transaction Type Validation Form . . . . . . . . . . . . . (GTVTRTP). . . . . . 8-24EDI Trading Partner Identification Form . . . . . . . . . . . . . (GXATPID) . . . . . . 8-24EDI Trading Partner Query Form . . . . . . . . . . . . . . . . (GXQTPID) . . . . . 8-25EDI Transaction ID Rules Form . . . . . . . . . . . . . . . . . (GXRETID) . . . . . . 8-26Desktop Tools - Step Property Values Rule Form . . . . . . . . (GORDPRP) . . . . . 8-27Desktop Tools - User Security Rule Form . . . . . . . . . . . . (GORDSEC) . . . . . 8-29Desktop Tools - Step Type Properties Rule Form . . . . . . . . (GORDSTP) . . . . . 8-32Desktop Tools - Add-In Application Form . . . . . . . . . . . . (GOADADD) . . . . 8-35Desktop Tools - Wizard Steps Setup Application Form . . . . . (GOADSTE) . . . . . 8-44Electronic Documents Wizard Form. . . . . . . . . . . . . . . (GOAWFIZ) . . . . . 8-49Electronic Documents Dictionary Form . . . . . . . . . . . . . (GORWFDD) . . . . 8-50Electronic Documents Builder Form . . . . . . . . . . . . . . (GORWFDB). . . . . 8-51Electronic Documents Form . . . . . . . . . . . . . . . . . . (GOAWFED) . . . . . 8-55Electronic Documents Security Form . . . . . . . . . . . . . . (GORWFDS) . . . . . 8-60Electronic Documents Validation Form . . . . . . . . . . . . . (GTVWFED) . . . . . 8-60Electronic Documents Form . . . . . . . . . . . . . . . . . . (GOQWFED) . . . . 8-61Target System Code Validation Form . . . . . . . . . . . . . . (GTVEQTS) . . . . . 8-61Parameter Code Validation Form . . . . . . . . . . . . . . . . (GTVEQPM) . . . . . 8-62Parameter Group Code Validation Form . . . . . . . . . . . . (GTVEQPG) . . . . . 8-63Event Queue Code Validation Form . . . . . . . . . . . . . . (GTVEQNM) . . . . . 8-64Integration Partner System Rules Form . . . . . . . . . . . . . (GORINTG) . . . . . 8-65Parameter Group Rule Form . . . . . . . . . . . . . . . . . . (GOREQPG) . . . . . 8-66Event Queue Name Definition Form . . . . . . . . . . . . . . (GOREQNM) . . . . 8-67Event Queue Record Maintenance Form . . . . . . . . . . . . (GOAEQRM). . . . . 8-69Integration Configuration Settings Form . . . . . . . . . . . . . (GORICCR) . . . . . 8-72Menu Maintenance Form . . . . . . . . . . . . . . . . . . . . (GUTGMNU) . . . . 8-73

1-1

Table of Contents

Oracle Password Change Form . . . . . . . . . . . . . . . . . (GUAPSWD) . . . . . 8-74General User Preferences Maintenance Form . . . . . . . . . . (GUAUPRF) . . . . . 8-75My Banner Maintenance Form . . . . . . . . . . . . . . . . . (GUAPMNU) . . . . . 8-80My Banner Maintenance and Copy Form . . . . . . . . . . . . (GUTPMNU) . . . . . 8-81Object Maintenance Form . . . . . . . . . . . . . . . . . . . . (GUAOBJS) . . . . . . 8-81Object Search Form . . . . . . . . . . . . . . . . . . . . . . . (GUIOBJS) . . . . . . 8-82Object Code Validation Form . . . . . . . . . . . . . . . . . . (GTVOBJT) . . . . . . 8-82QuickFlow Code Validation Form . . . . . . . . . . . . . . . . (GTVQUIK) . . . . . . 8-82QuickFlow Definition Form . . . . . . . . . . . . . . . . . . . (GUAQUIK) . . . . . 8-83QuickFlow Form . . . . . . . . . . . . . . . . . . . . . . . . (GUAQFLW) . . . . . 8-83User Identification Control Form . . . . . . . . . . . . . . . . (GUAIDEN). . . . . . 8-84Enterprise Access Control Form . . . . . . . . . . . . . . . . . (GOAEACC) . . . . . 8-84General Medical Information Form . . . . . . . . . . . . . . . (GOAMEDI) . . . . . 8-85Credit Card Transaction ID Form . . . . . . . . . . . . . . . . (GOAMERC) . . . . . 8-88Geographic Regions/Divisions by ID Form . . . . . . . . . . . (GOAPGEO) . . . . . 8-88Source/Background Institution Geographic Form . . . . . . . . (GOASGEO) . . . . . 8-88Credit Card Rules Form . . . . . . . . . . . . . . . . . . . . . (GORCCRD) . . . . . 8-88Medical Disability Rule Form . . . . . . . . . . . . . . . . . . (GORMEDR) . . . . . 8-89Crosswalk Validation Form . . . . . . . . . . . . . . . . . . . (GTVSDAX) . . . . . . 8-90ZIP/Postal Code Validation Form . . . . . . . . . . . . . . . . (GTVZIPC) . . . . . . 8-90Help Form . . . . . . . . . . . . . . . . . . . . . . . . . . . . (GUAHELP). . . . . . 8-91Installation Controls Form . . . . . . . . . . . . . . . . . . . . (GUAINST) . . . . . . 8-91General Message Form . . . . . . . . . . . . . . . . . . . . . (GUAMESG) . . . . . 8-94Options Maintenance Form . . . . . . . . . . . . . . . . . . . (GUAOPTM) . . . . . 8-95Enterprise PIN Preferences Form . . . . . . . . . . . . . . . . . (GUAPPRF) . . . . . . 8-101System Identification Form . . . . . . . . . . . . . . . . . . . (GUASYST) . . . . . . 8-104SSN/SIN/TFN Alternate ID Search Form . . . . . . . . . . . . . (GUIALTI). . . . . . . 8-105SSN/SIN/TFN History Form. . . . . . . . . . . . . . . . . . . . (GUITINH) . . . . . . 8-107Immunization Information Form . . . . . . . . . . . . . . . . . (GOAIMMU) . . . . . 8-111Banner Message Aware Entity Rules Form . . . . . . . . . . . . (GURMESG) . . . . . 8-111Direct Access Form . . . . . . . . . . . . . . . . . . . . . . . (GUAPARM) . . . . . 8-116Calendar Form . . . . . . . . . . . . . . . . . . . . . . . . . (GUACALN) . . . . . 8-116Calculator Form . . . . . . . . . . . . . . . . . . . . . . . . . (GUACALC) . . . . . 8-117About Banner Form . . . . . . . . . . . . . . . . . . . . . . . (GUAABOT) . . . . . 8-117General Menu Form . . . . . . . . . . . . . . . . . . . . . . . (GUAGMNU). . . . . 8-118Banner Error and Warning Messages Form . . . . . . . . . . . (GUAERRM) . . . . . 8-118Personal Image Form . . . . . . . . . . . . . . . . . . . . . . (GUAIMGE) . . . . . 8-119VPDI Included Objects Form . . . . . . . . . . . . . . . . . . (GORVPDI) . . . . . . 8-119Set Institution Form . . . . . . . . . . . . . . . . . . . . . . . (GUQSETI) . . . . . . 8-120General WebUtil File Extract Form . . . . . . . . . . . . . . . (GUQWUTL) . . . . . 8-121



Overview


The System Functions/Administration module lets you set up, operate, and monitor Banner. Many forms in this module are used primarily by members of your data center to define and monitor the ongoing use of the system. Other forms are useful to end users. Some of the functions you can perform in the System Functions/Administration module are:

System Functions/

Administration

• Define the currency codes used in the system

• Define bank codes, bank routing information, and direct deposit information

• Display and maintain information used with EDI (Electronic Data Interchange)

• Define the codes and rules used by the Desktop Tools application to access data from a PC application

• Create and modify electronic documents

• Create new transactions based on electronic documents

• Define the codes and rules used by the Event Queue Maintenance module to define and track events as they occur in the Banner database

• Create and maintain custom menus for your institution

• Create or copy personal menus

• Establish personal preferences for the logged in user ID

• Create new objects

• Define and submit QuickFlows

• Set up VBS (Value Based Security)

• Track changes to a Social Security Number (SSN), Social Insurance Number (SIN), or Tax Filing Number (TFN)

• Cross-reference institution-defined codes with valid integration partner system codes

Validation Forms

Systems Functions/Administration forms use the following validation forms. Refer to Chapter 2, Validation Forms, for additional information.


FTVACCT Account Code Validation Form GXRBANK Bank Code Rule Form

FTVCOAS Chart of Accounts Validation Form GXRBANK Bank Code Rule Form

FTVFUND Fund Code Validation Form GXRBANK Bank Code Rule Form



GTVCURR Currency Codes Validation Form GUACURR Currency Code Maintenance FormGUAINST Installation Control FormGXRBANK Bank Code Rule Form

GTVDADD Desktop Tools - Add-In Validation Form GOADADD Desktop Tools - Add-In Application Form

GTVDPRP Desktop Tools - Step Property Validation Form

GORDPRP Desktop Tools - Step Property Values Rule Form


GTVDSTP Desktop Tools - Step Type Validation Form

GOADSTE Desktop Tools - Wizard Steps Setup Application Form


GTVEQNM Event Queue Code Validation Form GOAEQRM Event Queue Record Maintenance FormGOREQNM Event Queue Name Definition Form

GTVEQPG Parameter Group Code Validation Form GOREQNM Event Queue Name Definition FormGOREQPG Parameter Group Rule Form

GTVEQPM Parameter Code Validation Form GOREQPG Parameter Group Rule Form

GTVEQTS Target System Code Validation Form GOAEQRM Event Queue Record Maintenance FormGOREQNM Event Queue Name Definition Form

GTVINTP Integration Partner System Code Validation Form

GORINTG Integration Partner System Rules Form

GTVOBJT Object Code Validation Form GUAOBJS Object Maintenance FormGUTGMNU Menu Maintenance Form

GTVQUIK QuickFlow Code Validation Form GUAQUIK QuickFlow Definition Form

GTVSCOD EDI/ISO Standard Code Validation Form

GUACURR Currency Codes Validation Form

GTVSYSI System Indicator Validation Form GUAOBJS Object Maintenance FormGUTGMNU Menu Maintenance FormGUTMENU General Menu Maintenance Form


GOABACR Value-Based Security Access Rules FormGOAVUSR Value-Based Security Restricted Users

Form

GTVVBTY Value-Based Security Object Types Form GTVVAPP Value-Based Security Application Codes Form




Related Process

The Print Dynamic Help for a Form Process (GURHELP) prints Dynamic Help for selected forms. You can print form-level, block-level, and field-level help.


Forms in the System Functions/Administration module can be accessed from the following menus.

GTVVOBJ Value-Based Security Objects Form GOABACR Value-Based Security Access Rules FormGOAPCRL Value-Based Security Pattern Control

Rules Form

GTVWFED Electronic Documents Validation Form GOAWFED Electronic Documents FormGORWFDB Electronic Documents Builder Form

GXVDIRD Bank Routing Number Validation Form GXADIRD Direct Deposit Recipient Form

STVCAMP Campus Code Validation Form GOABACR Value-Based Security Access Rules Form

STVCOLL College Code Validation Form GOABACR Value-Based Security Access Rules Form

STVDEPT Department Code Validation Form GOABACR Value-Based Security Access Rules Form

STVLEVL Level Code Validation Form GOABACR Value-Based Security Access Rules Form

STVNATN Nation Code Validation Form GTVZIPC ZIP/Postal Code Validation FormGUACURR Currency Code Maintenance FormGUAINST Installation Control Form


. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . System Functions/Administration Menu (*GENSYS)

*GENCURR Banking and Currency MenuProvides access to the forms used to define currency codes, bank codes, bank routing information, and direct deposit information.

*GENEDI Electronic Data Interchange MenuProvides access to the forms used to maintain EDI information.



*GENDTOOLS Desktop Tools MenuProvides access to the forms used to define the codes and rules used by the Desktop Tools application.

*GENWFED Electronic Documents MenuProvides access to the forms used to create and modify electronic documents.

*GENEQS Event Queue Maintenance MenuProvides access to the forms used to define the codes and rules used by the Event Queue Maintenance module.

*GENMENU Menu/Preference Maintenance MenuProvides access to the forms used to customize menus for your institution, change an Oracle password, establish personal preferences for the logged in user ID, create personal menus, and copy personal menus.

*GENOBJS Object Maintenance MenuProvides access to the forms used to create Banner objects.

*GENQUIK QuickFlow Process MenuProvides access to the forms used to define and submit QuickFlows.

*GENMISC Miscellaneous General FormsProvides access to miscellaneous General forms.

*GENINTCOMP

Integration Component Management MenuProvides access to Integration Components forms.

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Banking and Currency Menu (*GENCURR)

GUACURR Currency Code Maintenance FormDefines the currency codes used in the system.

GTVCURR Currency Codes Validation FormDisplays the currency codes used in the system.

GXRBANK Bank Code Rule FormDefines the bank codes for your institution’s bank accounts. Links bank funds and bank accounts with your cash accounts. Defines ACH information for each bank account used to make payments by direct deposit.

GXIBANK Bank Code Query FormDisplays historical information for the bank codes defined on the Bank Code Rule Form (GXRBANK).

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . System Functions/Administration Menu (*GENSYS)



GXVDIRD Bank Routing Number Validation FormDefines bank routing information used to make payments by direct deposit.

GXADIRD Direct Deposit Recipient FormIdentifies the recipients (such as employees, students, and vendors) that receive payments by direct deposit.

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Electronic Data Interchange Menu (*GENEDI)

GTVSCOD EDI/ISO Standard Code Validation FormDisplays the EDI/ISO standard code lists that are used in EDI documents.

GTVTRTP EDI Transaction Type Validation FormDisplays the EDI transaction types that are available within Banner.

GXATPID EDI Trading Partner Identification FormEstablishes trading partner data that is used to trade business documents with a specified vendor.

GXRETID EDI Transaction ID Rules FormDefines the names of the files where the extracted EDI transactions are written.

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Desktop Tools Menu (*GENDTOOLS)

GTVDADD Add-In Validation FormDefines codes that identify add-in programs that add extra features to an application such as Microsoft Excel.

GTVDPRP Step Property Validation FormDefines the property codes used with step type codes to control the way a user interacts with an add-in program.

GTVDSTP Step Type Validation FormDefines the step type codes used with property codes to control the way a user interacts with an add-in program.

GORDPRP Step Property Values Rule FormAssociates values (objects) with property codes.

GORDSEC User Security Rule FormEstablishes user access for the specific wizards associated with an add-in.

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Banking and Currency Menu (*GENCURR)



. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Event Queue Maintenance Menu (*GENEQS)

GORDSTP Step Type Properties Rule FormAssociates properties with a step type code.

GOADADD Add-In Application FormAssociates wizards and data lookups with an add-in, and specifies the order in which the wizards and data lookups appear.

GOADSTE Wizard Step Setup Application FormAssigns steps (wizard windows) to a wizard, and assigns specific property values to each step.

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Electronic Documents Menu (*GENWFED)

GOAWFIZ Electronic Documents Wizard FormImports Banner forms into the Electronic Documents Dictionary Form (GORWFDD).

GORWFDD Electronic Documents Dictionary FormDisplays information, at the metadata level, that was imported from Banner forms with GOAWFIZ.

GORWFDB Electronic Documents Builder FormLets you create and modify electronic documents.

GOAWFED Electronic Documents FormCreates a new transaction, based on an electronic document, or displays an existing transaction.

GORWFDS Electronic Documents Security FormLets you specify super user access to electronic documents, based on Oracle ID.

GTVWFED Electronic Documents Validation FormDefines the codes that identify electronic documents.

GTVEQTS Target System Code Validation FormDefines the external systems that require notification when an event occurs.

GTVEQPM Parameter Code Validation FormDefines the parameters that are associated with events.

GTVEQPG Parameter Group Code Validation FormDefines the parameter groups that can be associated with events.

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Desktop Tools Menu (*GENDTOOLS)



GTVEQNM Event Queue Code Validation FormDefines the events that will be captured and sent to external systems.

GOREQPG Parameter Group Definition FormAssigns defined parameters to groups.

GOREQNM Event Queue Name Definition FormDefines specific events for the target system.

GOAEQRM Event Queue Record Maintenance FormDisplays event records created in Banner, by target system.

GORICCR Integration Configuration Settings FormMaintains settings and configurations that are required for the Integration for e-Learning product.

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Menu/Preference Maintenance Menu (*GENMENU)

GUTGMNU Menu Maintenance FormAllows you to create and maintain custom menus for your institution.

GUAPSWD Oracle Password Change FormAllows you to change your Oracle password.

GUAUPRF General User Preferences Maintenance FormAllows you to establish personal preferences for the logged in user ID.

GUAPMNU My Banner Maintenance FormAllows you to create a personal menu tied to your Oracle user ID.

GUTPMNU My Banner Maintenance and Copy FormAllows you to copy a personal menu from one user to another user or group of users.

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Object Maintenance Menu (*GENOBJS)

GUAOBJS Object Maintenance FormDefines new Banner objects (forms, jobs, menus, and QuickFlows).

GUIOBJS Object Search FormAllows you to search for an object (form, job, menu, or QuickFlow) using as much of the name, description, or type as you know.



GTVOBJT Object Code Validation FormDefines codes that identify the object types used on the Object Maintenance Form (GUAOBJS).

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . QuickFlow Process Menu (*GENQUIK)

GTVQUIK QuickFlow Code Validation FormDefines the QuickFlow codes used in the QuickFlow process.

GUAQUIK QuickFlow Definition FormDefines a QuickFlow.

GUAQFLW QuickFlow FormAllows you to submit a QuickFlow that has been defined on the QuickFlow Definition Form (GUAQUIK).

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Integration Component Management Menu (*GENINTCOMP)

GTVEQTS Target System Code Validation FormDefines the external systems that require notification when an event occurs.

GTVEQPM Parameter Code Validation FormDefines the parameters that are associated with events.

GTVEQPG Parameter Group Code Validation FormDefines the parameter groups that can be associated with events.

GTVEQNM Event Queue Code Validation FormDefines the events that will be captured and sent to external systems.

GTVINTG Integration Partner System Code Validation FormCreate and maintain your institution’s integration partner system codes.

GORINTG Integration Partner System Rules FormCreate and maintain the rules and cross-referenced codes that are used by institutions with one or more schedule type codes or instructional method codes that are used to flag courses and course sections for integration.

GOREQPG Parameter Group Definition FormAssigns defined parameters to groups.

GOREQNM Event Queue Name Definition FormDefines specific events for the target system.

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Object Maintenance Menu (*GENOBJS)



GOAEQRM Event Queue Record Maintenance FormDisplays event records created in Banner, by target system.

GORICCR Integration Configuration Settings FormMaintains settings and configurations that are required for the Integration for e-Learning product.

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Miscellaneous General Forms (*GENMISC)

GOAEACC Enterprise Access Control FormAssociates an Oracle username with a PIDM.

GOAMERC Credit Card Merchant ID FormDefines the merchant IDs associated with Credit Card Payment processing within Banner.

GOAPGEO Geographic Regions/Divisions by ID FormDisplays the geographic regions assigned to an ID based on its addresses.

GOASGEO Source/Background Institution Geographic FormDisplays the geographic regions assigned to a source/background institution based on its address.

GORCCRD Credit Card Rules FormDefines the rules that are used to process Credit Card Payments within Banner.

GTVSDAX Crosswalk Validation FormDefines records in the Crosswalk Table.

GTVZIPC ZIP/Postal Code Validation FormDefines the ZIP codes and postal codes used throughout Banner.

GUAHELP Help FormAllows you to create, edit, and display Dynamic Help.

GUAIDEN User Identification Control FormAssociates system IDs with the proper names of users.

GUAINST Installation Control FormDefines overall system information for your institution.

GUAMESG General Message FormAllows you to send messages to and receive messages from other Banner users.

GUAOPTM Options Maintenance FormDefines the options that appear in the Options menu for a specific form.

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Integration Component Management Menu (*GENINTCOMP)



System Functions/Administration also uses the following forms that are not called from a menu:

• The Electronic Documents Form (GOQWFED) is used to copy transaction information, created with the Electronic Documents Form (GOAWFED), into another Banner form. After the appropriate information is copied, you can apply the copied data to the Banner database.

• The About Banner Form (GUAABOT) displays information about Banner, including the name and version number of the form from which GUAABOT was called and your session ID.

GUAPPRF Enterprise PIN Preferences FormAllows a site to establish rules for controlling PIN information, when a PIN is initially created, reset, or changed.

GUASYST System Identification FormIdentifies the Banner systems that contain information about an ID.

GUIALTI SSN/SIN Alternate ID Search FormAllows users to search for a Banner ID when they know a portion of the SSN/SIN, name, or the date of birth. Users can also list Banner IDs where the Change indicator is selected.

GUITINH SSN/SIN/TFN History FormAllows users to search for the identification number for a person or non-person, and view changes made to these numbers. These identification numbers are those that cause an update to the SPBPERS_SSN field. The form is display-only.

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Medical and Immunization Information Menu (*GENMEDICAL)

GORMEDR Medical Disability Rules FormAllows you to associate user-defined disability types with medical code conditions

GOAMEDI General Medical Information FormAllows you to view and update the medical conditions of people at your institution, including students, faculty, and staff.

GTVIMMU Immunization Code Validation FormStores immunization codes and their descriptions.

GTVIMST Immunization Status Code Validation FormStores immunization status codes and their descriptions.

GOAIMMU Immunization Information FormMaintains immunization status information for an ID.

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Miscellaneous General Forms (*GENMISC)



• The Calculator Form (GUACALC) displays a calendar. You can access this form by double-clicking any numeric field on a form, using a button on the Banner tool bar, or using Direct Access.

• The Calendar Form (GUACALN) displays a calendar. You can access this form by double-clicking any date field on a form, using a button on the Banner tool bar, or using Direct Access.

• The Direct Access Form (GUAPARM) is used to directly access forms, jobs, menus, and QuickFlows by name. You can access this form from the File pull-down menu.

Forms

This section describes each form in the System Functions/Administration module. Forms are described in the order they appear on the System Functions/Administration Menu (*GENSYS).

Currency Code Maintenance Form (GUACURR)

Use this form to establish and maintain the currency codes used in the system. Each code can be associated with various attributes that can be used in system processing. Many of the attributes are optional and are not appropriate for all currency codes.

Note: If the Finance System is not installed, the Accounts Payable Account and Exchange Account fields are not displayed. If the Finance or Human Resources Systems are installed, the Bank Code field is required. Otherwise it is optional.

Currency Codes Validation Form (GTVCURR)

Use this form to display all currency codes used in Banner. Examples of currencies include Canadian dollars, German deutsche marks, and British pounds. The display includes active codes and inactive codes.

Currency codes must be defined on the Currency Code Maintenance Form (GUACURR). They are display-only on GTVCURR.



Bank Code Rule Form (GXRBANK)

Use this form to:

• Define bank codes for your institution’s bank accounts

• Link bank funds and bank accounts with your cash accounts

• Define Automatic Clearing House (ACH) information for your institution’s bank accounts

Before you can use direct deposit to transfer funds from your bank to another bank, you must establish ACH information in the ACH Rules window for each bank account from which your institution withdraws funds. This information is sent to the clearing house in the direct deposit file.

Note: This form replaces the Finance System Bank Code Maintenance Form (FTMBANK) and parts of the Human Resources System Installation Rule Form (PTRINST).

This form opens in data-entry mode. To display an existing record for update, you must enter query mode, enter a Bank code, and execute the query.

Note: Anyone who will be using GXRBANK should have a non-person source code listed as their default on the Common Matching User Setup Form (GORCMUS).

Main Window

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions

Bank User-defined code that identifies a bank in Banner.

(button) List Bank Code List (GXVBANK)

Required.

Name Name associated with the bank code. A bank code can have more than one name. You can scroll to view information for each bank name. Required.

Active Status Check box that indicates the status of the bank:

Selected Bank is active, available for use in Banner.

Cleared Bank is not active.

Optional.



Effective Date Date the bank code record is effective or valid for use in DD-MON-YYYY format. The current date is the default value. Required.

Next Change Date

Date the record was most recently modified. The next change date indicates that a record has been updated. This allows you to create a series of records for one bank code, based on dates. Display-only.

Termination Date

Date the bank code record is no longer valid. It can be a past date or a future date. If you want the bank code to be valid only for a certain length of time, enter an Effective Date (when you can start using the bank code) and a Termination Date (when the bank code can no longer be used). Optional.

Last Activity Date the bank code record was last updated. Display-only.

Base Currency Code that identifies the type of currency normally associated with this account. An example is USD for United States dollars. This field is used only by Banner Finance.

(lookup) List Currency Code Validation (GTVCURR) list

Optional.

Bank ID Identification number for the bank, as defined in the Identification Table (SPRIDEN).

(button) List Non-Person Search Form (SOACOMP)

Note: When you save a bank code, Banner creates an identification record in SPRIDEN for the bank ID and bank name. You cannot modify the bank ID if it already exists in SPRIDEN. Use the Identification Form (FOAIDEN) or the Identification Form (PPAIDEN) to update existing bank names.

Required.

Bank Account Number

Bank account number for this record. If you have multiple accounts at one bank, create a separate bank for each account. Required.

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions



Chart of Accounts

Aggregation of FOAPAL elements (fund, organization, account, program, activity, and program) in Banner that uniquely reflects the organization's structure and enables financial reporting. All FOAPAL elements in Banner must be linked to a specific Chart of Accounts.

(lookup) List Chart of Accounts List (FTVCOAS)

Note: If Banner Finance is installed, this field is active and navigable. You must enter this field if the bank code will be used with the Banner Finance System. If Banner Finance is not installed, this field is not active and navigable.

Bank Fund Account that represents the accumulation (or total) of all your cash accounts within your Chart of Accounts.

(lookup) List Fund Code Validation Form (FTVFUND)


Cash Account Account defined for your cash transactions within your Chart of Accounts.

(lookup) List Account Code Validation Form (FTVACCT)


. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions



ACH Rules Window

Use this window to enter information that is used to transfer funds from your bank to another bank via direct deposit. This information is available from your bank or clearing house.

Interfund Account

Account number identified as your interfund account. The interfund account acts as a intermediate account, which can hold money temporarily before that money is sent to the final destination accounts.

(lookup) List Account Code Validation Form (FTVACCT)


ACH Status Check box that indicates whether the bank account can have funds withdrawn and sent to the payee via direct deposit:

Selected ACH functionality is active. The bank can make direct deposits.

Cleared ACH functionality is not active. The bank cannot make direct deposits.

Optional.

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions

Destination ID Identification number of the Automated Clearing House (ACH) that receives the funds sent via direct deposit.

Destination Name

Name of the ACH that receives the funds sent via direct deposit.

Origin ID Identification number of the bank where you send the direct deposit file.

Origin Name Name of the bank where you send the direct deposit file.

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions



Bank Code Query Form (GXIBANK)

Use this form to display historical information for the bank codes established on the Bank Code Rule Form (GXRBANK). Bank code records are sorted by Chart of Account (if Banner Finance is installed) and bank code.

Note: This form replaces the Finance Bank Code Validation Form (FTVBANK).

Short Name Short name of the bank where you send the direct deposit file. The direct deposit file limits the bank name to 16 characters. Use this field to create a 16-character name for the bank. The field defaults to the first 16 characters of the Origin Name.

Originating Bank Routing Number

Routing number for the account from which direct deposit disbursements are deducted.

Organization Number Type

Radio group that indicates whether your institution’s identification number for direct deposit processing is your IRS employer ID, your Data Universal Systems (DUS) number, or a user-defined number.

Organization ID Number

Your institution’s identification number for direct deposit processing. This number can be your IRS employer ID, your Data Universal Systems (DUS) number, or a user-defined number.

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions

COA Chart of Accounts code used in Banner for the bank code.

Note: This field appears only if Banner Finance is installed at your institution.

Bank Code Code that identifies a bank in Banner. Display-only.



Bank Routing Number Validation Form (GXVDIRD)

Use this form to define bank routing information. This information is required if you make payments by direct deposit. The Direct Deposit Recipient Form (GXADIRD) requires this bank routing information to identify the recipient’s bank that receives the payments via direct deposit.

Account Name Name associated with the bank code.

Note: This field appears only if Banner Finance is installed at your institution.

Display-only.

Status Status of the bank code:

A Active

I Inactive

Display-only.

Effective Date Date the bank code record is effective or valid for use. Optional.

Termination Date

Date the bank code record is no longer valid. It can be a past date or a future date. Optional.

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions

Bank Routing Number

Routing number for the recipient’s bank. This number is required to send funds to the recipient’s bank via direct deposit.

Bank Name Name of the bank associated with the routing number.

Activity Date Date the bank routing record was created or last updated.



Direct Deposit Recipient Form (GXADIRD)

Use this form to identify the recipients (such as employees, students, or vendors) that receive payments via direct deposit. This form specifies the bank and bank account where the recipient has requested that money be deposited. This information is sent to the clearing house in the direct deposit file.

Access privileges to various fields on this form depend on the Banner products you are permitted to access. Certain fields can be accessed or seen by a Human Resources user only (defined on the PTRUSER Form). Other fields can be accessed by an Accounts Payable user only (defined on the TBBUPRF or FOBPROF Table). This means the same bank record can be used differently by Human Resources and Accounts Payable users. If you can access both products, you can access all fields.

An Accounts Payable vendor can have multiple bank accounts for payment of different invoices. You can create multiple addresses for these different payments.

Note: Before using this form, you must establish bank routing information on the Bank Routing Number Validation Form (GXVDIRD).

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions

ID Identification number of the recipient (employee, student, or vendor) that receives payments via direct deposit.

(button) List Person Search Form (SOAIDEN)

(button) Count Hits Non-Person Search Form (SOACOMP)

Bank Routing Routing number for the recipient’s bank. This number must be defined on the Bank Routing Number Validation Form (GXVDIRD). It is used to send funds to the recipient’s bank via direct deposit.

(lookup) List Bank Routing Number Validation Form (GXVDIRD)



Address Type Address type associated with the bank account. If you leave this field blank, the account information is valid for all unspecified address types.

(lookup) List Address Summary Form (SOADDRQ)

Note: You can access this field only if Banner Finance is installed at your institution and you have appropriate security access.

Note: On this form, only one account can be tied to an address type and sequence number.

Address Sequence

Sequence number associated with the address type. If you leave the Address Type field blank, then no sequence number is allowed. This field is required only if a value is entered in the Address Type field.

Note: You can access this field only if Banner Finance is installed at your institution and you have appropriate security access.

Note: On this form, only one account can be tied to an address type and sequence number.

Accounts Payable

Check box that indicates whether the recipient is eligible for accounts payable disbursements. Whenever this is the only check box selected, the default priority is 0 (you can change it).

Note: You can access this check box only if Banner Finance is installed at your institution and you have appropriate security access.

Payroll Check box that indicates whether the recipient is eligible for payroll disbursements.

Note: You can access this check box only if Banner Human Resources is installed at your institution and you have appropriate security access.

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions



Account Number

Recipient’s bank account that receives disbursements via direct deposit.

Note: It is possible to have more than one account (e.g., a checking account and a savings account) with the same number. Make sure they have different priorities.

CheckingSavings

Type of bank account that receives disbursements via direct deposit (Checking or Savings).

Status Recipient’s direct deposit status:

Active Payments are received through direct deposit.

Prenote A prenotification or test record is created. Actual payments are made through regular check processing. (Default)

Inactive No direct deposit payments are made. Payments are made through regular check processing.

Priority User-defined priority code for the sequence in which processing and disbursements occur. Valid priorities are 1 through 99. Items with a priority of 1 process before those with a priority of 2.

Note: This field appears only if Banner Human Resources is installed at your institution and you have appropriate security access.

If Accounts Payable is the only check box selected, the default priority is 0. It can be changed.

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions



EDI/ISO Standard Code Validation Form (GTVSCOD)

Use this form to display the EDI/ISO standard code lists that are used in EDI documents.

You do not need to enter the codes on GTVSCOD; they are supplied by EDI.Smart and Banner.

Amount or Percent

Amount or percentage to be deposited in the bank. Enter either a fixed dollar amount or a percentage (not both). If you enter a percentage, the system determines the exact dollar amount that is deposited. If no amount or percent is entered, the system assumes 100 percent.

If funds are deposited in more than one bank, you must set up each bank routing number on this form with the appropriate amount or percentage.

Note: This field appears only if Banner Human Resources is installed at your institution and you have appropriate security access. (Finance accounts payable payments assume 100 percent distribution; payments cannot be split among several banks.)

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions

Element Number that identifies the EDI or ISO standard code list.

Code EDI or ISO standard code.

Description Description of the EDI or ISO standard code.

Standard Code that identifies the standards agency that defined the code list:

X X12E EDIFACTI ISO





EDI Transaction Type Validation Form (GTVTRTP)

Use this form to display the EDI transaction types that are available within Banner. The table associated with this form is delivered with Banner and contains valid transaction types.

EDI Trading Partner Identification Form (GXATPID)

Use this form to set up trading partner data. This information is needed when you trade business documents with a specified vendor. You must create an entry for each EDI transaction or message that you plan to trade with the specified vendor.

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions

Transaction Type ID

EDI transaction type code defined by the EDI standards committees.

Description Description of the EDI transaction type.


. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions

ID Vendor’s ID number.



Address Type Address type associated with the vendor.

(lookup) List Address Summary Form (SOADDRQ)

Address Sequence

Sequence number associated with the vendor ID and address type.

Trading Partner ID

Unique ID for the trading partner. This trading partner ID must be set up in EDI.Smart.



EDI Trading Partner Query Form (GXQTPID)

Use this form to display trading partner data. This information is used to trade business documents with a specified vendor. This form is query-only.

Transaction Type

Transaction type associated with the EDI transaction or message that you plan to trade.

(lookup) List EDI Transaction Type Validation (GTVTRTP) list

Transaction ID X12 or EDIFACT document that you are trading. Choices are limited to the X12 or EDIFACT documents associated with the code entered in the Transaction Type field.

(button) List EDI Transaction ID Rules (GXRETID) list

EDI Standard EDI standard code associated with the document in the Transaction ID field:

X X12E EDIFACT

Active Status of the trading partnership:

A ActiveI InactiveT Test

Send Immediate Check box that determines when this transaction is sent to your trading partner:

Selected Send whenever the extract process runs.Cleared Send only when the extract process runs in

batch.

Next Control Number

Control number to be assigned to the transaction when it is sent. This number is updated each time an additional transaction of this type is sent to this trading partner. It is recommended that you begin at 1, unless your trading partner has requested otherwise.


. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions



Note: To access this form, select View EDI Trading Partners from the Options menu on the EDI Trading Partner Identification Form (GXATPID).

EDI Transaction ID Rules Form (GXRETID)

Use this form to define the names of the files where the extracted EDI transactions are written. You must define a record for each EDI X12 and EDIFACT document you will be sending.

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions

ID Vendor’s ID number.

Address Type Address type associated with the vendor.

Sequence Number

Sequence number associated with the vendor ID and address type.

Trading Partner ID

Unique ID for the trading partner.

Transaction ID X12 or EDIFACT document that you are trading.

Status Status of the trading partnership:

A ActiveI InactiveT Test


. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions

EDI Transaction Type ID

EDI transaction type associated with the transaction or message you are defining.

(lookup) List EDI Transaction Type Validation Form (GTVTRTP)

EDI Transaction ID

EDI transaction ID of the transaction you are defining. Examples include 850 and ORDERS.



Desktop Tools - Step Property Values Rule Form (GORDPRP)

Use this form to associate values with the property codes that are defined on the Desktop Tools - Step Property Validation Form (GTVDPRP). A value is a specific object, such as a picture of a bag of money, that belongs to a property category such as Picture. A step is a collection of properties that appears on a wizard window and controls the way a user interacts with an add-in. You can use the values delivered with Banner, or you can create your own. You can associate multiple values with a single property code.

Note: A property must exist on the Desktop Tools—Step Property Validation Form (GTVDPRP) before it is used on this form.

You can use the values delivered with Banner, as well as create your own. You can associate multiple values with a single property code.


Main Window

Use this window to associate values with property codes defined on the Desktop Tools—Step Property Validation Form (GTVDPRP).

You can use the values delivered with Banner, as well as create your own. You can associate multiple values with a single property code.

EDI Standard EDI standard code associated with the transaction you are defining.


EDI Extract File Name

Name of the file where the extracted EDI data is written. This name must also be defined in EDI.Smart.


. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions



Key Block

Value Description Block

Use this block to enter the value(s) to associate with the property code in the key block.

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions

Property Code Code of the property.


Choices: Choices come from the Desktop Tools—Step Property Validation Form (GTVDPRP).

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions

Value Name Code of the value. A value is a specific object, such as a picture of a bag of money, that belongs to a property.

Column: GORDPRP_VALUE_NAME

Source: For baseline property codes, value names are delivered with Banner. They cannot be changed.

Description Description of the value (for example, Wizard with Question Mark might be associated with the value QUESTION_MARK).

Column: GORDPRP_VALUE_DESCRIPTION

Source: For baseline property codes, descriptions are delivered with Banner. They can be changed.

Activity Date Date on which the value was created or changed.

Column: GORDPRP_ACTIVITY_DATE

Source: Banner updates the activity date automatically when you create or change the record. It cannot be changed.

User ID Banner-assigned value that indicates whether the value was delivered with Banner or created by a user.

Column: GORDPRP_USER_ID


Values:

BASELINE - The value was delivered with Banner.

LOCAL - The value was created by a user.



To associate values with a property code:

1. Access the Desktop Tools—Step Property Values Rule Form (GORDPRP).



4. Enter a Value Name.


6. Save.

To change a value associated with a property:

1. Access the Desktop Tools—Step Property Values Rule Form (GORDPRP).



4. Change the appropriate Value Name and/or Description.

5. Save.

Desktop Tools - User Security Rule Form (GORDSEC)

Use this form to establish user access for the specific wizards associated with an add-in. You can grant a user access to the wizards from multiple add-ins, if necessary. For example, in Banner Spreadsheet Budgeting, you can grant a user authorization to download, validate, and/or upload data from and to Banner tables. You can copy user privileges from one ID to another.

Note: Updates to a user’s access privileges are reflected the next time he/she logs in to the application.

Main Window

Use this window to grant a user access to specific wizards associated with an add-in. You can grant a user access to as many wizards as necessary.

Key Block

User this block to select a user ID.



Wizard Access Block

Use this block to select the wizard(s) to which you want to grant a user access.

Copy User Information Window

Use this window to copy the wizards authorized for one user to another user ID.

Copy Block

Use this block to copy the wizards authorized for one user to another user ID.

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions

User ID ID of the person for which you want to grant wizard access.


Choices: Choices come from the User ID list.

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions

Add-In Code Code of the add-in.

Column: GORDSEC_DADD_CODE (code). Not a base table item (description).

Choices: Choices come from the Available Add-Ins list.

Wizard Name Name of the wizard.

Column: GORDSEC_WIZARD_NAME (code). Not a base table item (description).

Choices: Choices come from the Enabled Wizards for Add-In list.

Activity Date Date on which the user was granted access to the wizard.

Column: GORDSEC_ACTIVITY_DATE

Source: Banner updates this value automatically when you grant access to a wizard. It cannot be changed.



To establish wizard security for a user:

1. Access the Desktop Tools—User Security Rule Form (GORDSEC).

2. Enter a User ID.


4. Enter the wizards to which the user will have access.

5. Save.

To copy wizards from one user ID to another:


2. Enter the User ID to which you want to copy wizard access.

3. Select Copy User IDs from the Options menu.

4. Enter the ID of the user from which you want to copy access privileges in the Copy from User ID field.

5. Select the Copy button.

6. Save.

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions

User ID User ID to which you want to copy wizards.


Source: This value comes from the User ID field in the key block. It can be changed.

Choices: Choices come from the All Oracle Users list.

Copy from User ID

User ID from which you want to copy wizards.


Choices: Choices come from the All Oracle Users list.



To delete a user’s access privileges:


2. Enter the User ID from which you want to remove access privileges.

3. Select Delete All User Information from the Options menu.

4. Select the Yes button.

5. Save.

Tip: You can also delete access privileges when your cursor is in the Wizard Access block.

Desktop Tools - Step Type Properties Rule Form (GORDSTP)

Use this form to associate properties with a step type code. A step is a collection of properties that appears on a wizard window and controls the way a user interacts with an add-in such as Banner Spreadsheet Budgeting. This form lets you customize the appearance of each wizard window.

Prior to using this form, you must establish step and property information on the following forms:

• Desktop Tools—Step Property Validation Form (GTVDPRP)

• Desktop Tools—Step Type Validation Form (GTVDSTP)


Main Window

Use this window to associate properties with a step type code. A step is a collection of properties that appears on a wizard window and controls the way a user interacts with an add-in such as Banner Finance Spreadsheet Budgeting.

Key Block

Use this block to enter a step type code.



Property Association Block

Use this block to select the properties that you want to associate with the step code in the key block.

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions

Step Type Code Code of the step. A step consists of the functions that appear on a wizard window.


Choices: Choices come from the Desktop Tools—Step Type Validation Form (GTVDSTP).

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions

Property Code Code of the property. A property is a type of object, such as a radio button or a picture, that appears on a wizard window.

Column: GORDSTP_DPRP_CODE (code). Not a base table item (description).

Choices: Choices come from the Desktop Tools—Step Property Validation Form (GTVDPRP).

Locked Check box that indicates whether you can change the layout of a wizard window by changing a property. Baseline properties that are locked on this form cannot be modified at all on the Desktop Tools—Wizard Steps Setup Application Form (GOADSTE).

Column: GORDSTP_LOCK_IND

Source: For baseline properties that must be present in order for a wizard to function properly, this check box is selected. It cannot be changed.

Choices are:

selected - The baseline property cannot be modified on GOADSTE.

cleared - The baseline property can be modified on GOADSTE.

Note: This check box applies only to baseline properties.



To associate properties with a step (wizard):

1. Access the Desktop Tools—Step Type Properties Rule Form (GORDSTP).

2. Enter a Step Type Code.


4. Enter the Property Code.

Required Check box that indicates whether the property is required on the Desktop Tools—Wizard Steps Setup Application Form (GOADSTE). Required properties must be present for the wizard to perform correctly.

Column: GORDSTP_REQUIRED_IND

Choices are:

selected - The property is required in order for the wizard to perform correctly.

cleared - The property is optional and does not need to be present in order for the wizard to perform correctly.

Caution: If you create a new required property within the DLL, then you must select this check box. This ensures that the property always appears on GOADSTE, and that the wizard perform correctly.

Activity Date Date on which the property was associated with the Step Type Code.

Column: GORDSTP_ACTIVITY_DATE


User ID Banner-assigned value that indicates whether the property was associated with the Step Type Code by Banner or by a user.

Column: GORDSTP_USER_ID


Values are:

BASELINE - The property association was delivered with Banner.

LOCAL - The property association was created by a user.

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions



5. If the property must be present in order for the wizard to perform correctly, select the Required check box.

6. Save.

7. Repeat steps four through six for each property that you want to associate with the step.

Desktop Tools - Add-In Application Form (GOADADD)

Use this form to associate wizards and data lookups with an add-in, and specify the order in which the wizards and data lookups appear. You can associate multiple wizards and data lookups with a single add-in code.

Use this form to associate wizards and data lookups with an add-in, and to specify the order in which the wizards and data lookups will appear.

You can associate multiple wizards and data lookups with a single add-in code.

Prior to using this form, you must establish add-in information on the Desktop Tools—Add-In Validation Form (GTVDADD).

Tip: Establish security for add-in users on the Desktop Tools—User Security Rule Form (GORDSEC).

Tip: For baseline add-in codes, only the wizard description and the data lookup description can be changed. For local add-in codes, you can change any value except the activity date and user ID.

Main Window

Use this window to associate wizards with an add-in code.

Key Block

Use this block to enter the add-in code.

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions

Add-In Code Code of the add-in. An add-in is a program, such as Banner Finance Spreadsheet Budgeting, that adds extra features to an application such as Microsoft Excel.


Choices: Choices come from the Desktop Tools—Add-In Validation Form (GTVDADD).



Wizard Association Block

Use this block to enter the wizards that you want to associate with the add-in in the key block. This window is also used to select the products/modules with which the particular wizard is active.

Note: If a product/module check box is disabled, then the product/module is not installed. Users cannot change the status of disabled check boxes.

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions

Wizard Name Code of the wizard that you want to associate with the add-in.

Column: GORDWIZ_WIZARD_NAME

Source: For baseline add-in codes, the Wizard Name is delivered with Banner. It cannot be changed.

Description Description of the wizard that you want to associate with the add-in. This description appears on the Excel toolbar.

Column: GORDWIZ_WIZARD_DESCRIPTION

Next Function PL/SQL procedure that indicates what happens when you click the Next button at the bottom of each wizard window.

Column: GORDWIZ_NEXT_FUNCTION

Source: For baseline add-in codes, the Next Function is delivered with Banner. It cannot be changed.

Finish Function PL/SQL procedure that indicates what happens when you click the Finish button at the end of a series of wizard windows.

Column: GORDWIZ_FINISH_FUNCTION

Source: For baseline add-in codes, the Finish Function is delivered with Banner. It cannot be changed.

Unload Function

PL/SQL procedure that purges temporary data from Banner tables when you click the Finish or Cancel button.

Column: GORDWIZ_UNLOAD_FUNCTION

Source: For baseline add-in codes, the Unload Function is delivered with Banner. It cannot be changed.



Menu Sequence Number that indicates the position in which the wizard item appears on the menu bar.

Column: GORDWIZ_MENU_SEQNO

Source: For baseline add-in codes, the Menu Sequence is delivered with Banner. It cannot be changed.

Activity Date Date on which the wizard was associated with the add-in code.

Column: GORDWIZ_ACTIVITY_DATE


User ID Banner-assigned value that indicates whether the wizard was delivered with Banner or created by a user.

Column: GORDWIZ_USER_ID


Values are:

BASELINE - The wizard code was delivered with Banner.

LOCAL - The wizard code was created by a user.

Financial Aid Check box that indicates whether the wizard is enabled for Banner Financial Aid. You can select this check box only if Banner Financial Aid is installed.

Column: GORDWIZ_FINAID_IND

Source: For baseline add-in codes, this value is delivered with Banner. It cannot be changed.

Choices are:

selected - The wizard is enabled for Banner Financial Aid.

cleared - The wizard is not enabled for Banner Financial Aid.

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions



Position Control Check box that indicates whether the wizard is enabled for Banner Position Control. You can select this check box only if Banner Position Control is installed.

Column: GORDWIZ_POSBUD_IND


Choices are:

selected - The wizard is enabled for Banner Position Control.

cleared - The wizard is not enabled for Banner Position Control.

Human Resources

Check box that indicates whether the wizard is enabled for Banner Human Resources. You can select this check box only if Banner Human Resources is installed.

Column: GORDWIZ_HUMANRE_IND


Choices are:

selected - The wizard is enabled for Banner Human Resources.

cleared - The wizard is not enabled for Banner Human Resources.

Finance Check box that indicates whether the wizard is enabled for Banner Finance. You can select this check box only if Banner Finance is installed.

Column: GORDWIZ_FINANCE_IND


Choices are:

selected - The wizard is enabled for Banner Finance.

cleared - The wizard is not enabled for Banner Finance.

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions



Data Lookup Window

Use this window to associate data lookups with an add-in code. A data lookup is a function, such as a list of values, that a user can call by clicking a button.

This window is also used to select the products/modules with which the particular data lookup is active.

Advancement Check box that indicates whether the wizard is enabled for Banner Advancement. You can select this check box only if Banner Advancement is installed.

Column: GORDWIZ_ALUMNI_IND


Choices are:

selected - The wizard is enabled for Banner Advancement.

cleared - The wizard is not enabled for Banner Advancement.

Accounts Receivable

Check box that indicates whether the wizard is enabled for Banner Accounts Receivable. You can select this check box only if Banner Accounts Receivable is installed.

Column: GORDWIZ_BILCSH_IND


Choices are:

selected - The wizard is enabled for Banner Accounts Receivable.

cleared - The wizard is not enabled for Banner Accounts Receivable.

Student Check box that indicates whether the wizard is enabled for Banner Student. You can select this check box only if Banner Student is installed.

Column: GORDWIZ_STUDENT_IND


Choices are:

selected - The wizard is enabled for Banner Student.

cleared - The wizard is not enabled for Banner Student.

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions



Note: If a product/module check box is disabled, then the product/module is not installed. Users cannot change the status of disabled check boxes.

Data Lookup Block

Use this block to enter the data lookups that you want to associate with the add-in in the key block.

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions

Data Lookup Name

Code of the data lookup that you want to associate with the add-in.

Column: GORDLUP_LOOKUP_NAME

Source: For baseline add-in codes, the Data Lookup Name is delivered with Banner.

Description Description of the data lookup that you want to associate with the add-in. Changes to this value appears on the Excel toolbar.

Column: GORDLUP_LOOKUP_DESCRIPTION

Load Function PL/SQL procedure that indicates what happens when you click the menu entry for a data lookup.

Column: GORDLUP_LOAD_FUNCTION

Source: For baseline add-in codes, the Load Function is delivered with Banner. It cannot be changed.

Menu Sequence Number that indicates the position in which the data lookup appears on the menu bar.

Column: GORDLUP_MENU_SEQNO

Source: For baseline add-in codes, the Menu Sequence is delivered with Banner. It cannot be changed.

Activity Date Date on which the data lookup was associated with the add-in code.

Column: GORDLUP_ACTIVITY_DATE




User ID Banner-assigned value that indicates whether the data lookup was delivered with Banner or created by a user.

Column: GORDLUP_USER_ID


Values are:

BASELINE - The data lookup was delivered with Banner.

LOCAL - The data lookup was created by a user.

Financial Aid Check box that indicates whether the data lookup is enabled for Banner Financial Aid. You can select this check box only if Banner Financial Aid is installed.

Column: GORDLUP_FINAID_IND


Choices are:

selected - The data lookup is enabled for Banner Financial Aid.

cleared - The data lookup is not enabled for Banner Financial Aid.

Position Control Check box that indicates whether the data lookup is enabled for Banner Position Control. You can select this check box only if Banner Position Control is installed.

Column: GORDLUP_POSBUD_IND


Choices are:

selected - The data lookup is enabled for Banner Position Control.

cleared - The data lookup is not enabled for Banner Position Control.

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions



Human Resources

Check box that indicates whether the data lookup is enabled for Banner Human Resources. You can select this check box only if Banner Human Resources is installed.

Column: GORDLUP_HUMANRE_IND


Choices are:

selected - The data lookup is enabled for Banner Human Resources.

cleared - The data lookup is not enabled for Banner Human Resources.

Finance Check box that indicates whether the data lookup is enabled for Banner Finance. You can select this check box only if Banner Finance is installed.

Column: GORDLUP_FINANCE_IND


Choices are:

selected - The data lookup is enabled for Banner Finance.

cleared - The data lookup is not enabled for Banner Finance.

Advancement Check box that indicates whether the data lookup is enabled for Banner Advancement. You can select this check box only if Advancement is installed.

Column: GORDLUP_ALUMNI_IND


Choices are:

selected - The data lookup is enabled for Banner Advancement.

cleared - The data lookup is not enabled for Banner Advancement.

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions



To associate a wizard with an add-in code:

1. Access the Desktop Tools—Add-In Application Form (GOADADD).

2. Enter an Add-in Code.


4. Enter a Wizard Name.


6. Enter the Next Function.

7. Enter the Finish Function.

8. Enter the Unload Function.

9. Enter the Menu Sequence number.

Accounts Receivable

Check box that indicates whether the data lookup is enabled for Banner Accounts Receivable. You can select this check box only if Banner Accounts Receivable is installed.

Column: GORDLUP_BILCSH_IND


Choices are:

selected - The data lookup is enabled for Banner Accounts Receivable.

cleared - The data lookup is not enabled for Banner Accounts Receivable.

Student Check box that indicates whether the data lookup is enabled for Banner Student. You can select this check box only if Banner Student is installed.

Column: GORDLUP_STUDENT_IND


Choices are:

selected - The data lookup is enabled for Banner Student.

cleared - The data lookup is not enabled for Banner Student.

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions



10. Save.

To associate a data lookup with an add-in code:

1. Access the Desktop Tools—Add-In Application Form (GOADADD).

2. Enter an Add-in Code.


4. Go to the Data Lookup window.

5. Enter the Data Lookup Name.

6. Enter the Load Function.

7. Enter the Menu Sequence number.

8. Save.

Desktop Tools - Wizard Steps Setup Application Form (GOADSTE)

Use this form to assign steps (wizard windows) to a wizard, and assign specific property values to each step.

Tip: If you have created your own steps, the properties that you designated as “required” on the Desktop Tools—Step Type Properties Rule Form (GORDSTP) automatically appear.

Main Window

Use this window to assign steps (wizard windows) to a wizard, and to assign specific property values to each step.

Key Block

Use this block to enter the add-in code and wizard name for which you want to assign steps.



Step Information Block

Use this block to enter the steps that you want to assign to the wizard. You must subsequently assign properties to each step by using the Property Assignment block.

Tip: Make a step active by scrolling up or down to highlight it. When the appropriate step is highlighted, you can then go to the next block to assign properties to that step.

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions

Add-In Code Code of the add-in.


Choices: Choices come from the Available Add-Ins list.

Note: The add-in code must be defined on the Desktop Tools—Add-In Validation Form (GTVDADD) before it is used on this form. In addition, the wizard must be enabled for the products/modules installed at your institution.

Wizard Name Code of the wizard associated with the add-in.


Choices: Choices come from the Enabled Wizards for Add-In list.

Note: The wizard name must be defined on the Desktop Tools—Add-In Application Form (GOADADD) before it is used on this form.

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions

Step Name User-defined name for the step (wizard window).

Column: GORDSTE_STEP_NAME

Step Type Code Code of the step (wizard window).

Column: GORDSTE_DSTP_CODE (code). Not a base table item (description).

Choices: Choices come from the Step Type Code list.



Property Assignment Block

Use this block to select the properties and their specific values that you want to appear on the wizard window.

Activity Date Date on which the step was associated with the add-in code.

Column: GORDSTE_ACTIVITY_DATE


User ID Banner-assigned value that indicates whether the step was associated with the add-in code by Banner or by a user.

Column: GORDSTE_USER_ID


Values are:



. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions

Property Code Code of the property.

Column: GORDSPR_DPRP_CODE

Choices: Choices come from the Property Code list.

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions



Required Indicator

Code that indicates whether the property is necessary to the correct functioning of the wizard. If a property is required, then it cannot be deleted from the step (wizard window).

Properties are designated as required on the Desktop Tools—Step Type Properties Rule Form (GORDSTP).


Source: This value comes from the Required field on the Desktop Tools—Step Type Properties Rule Form (GORDSTP). It cannot be changed.

Choices are:

Y (yes) - The property is required and cannot be deleted from the step. It is necessary to the correct performance of the wizard.

N (no) - The property is optional and may be deleted from the step. It is not necessary to the correct performance of the wizard.

Note: Required properties may be changed as long as they are not locked on the Desktop Tools—Step Type Properties Rule Form (GORDSTP).

Value Code of the value for the property. A value is a specific object, such as a picture of a bag of money, that belongs to a certain property.

Column: GORDSPR_VALUE

Choices: If values exist for this field, then the Search button is enabled, and choices come from the Property Type Codes list. If no values exist for this field, then you can enter a free-format value.

Note: Baseline values that are locked on the Desktop Tools--Step Type Properties Rule Form (GORDSTP) cannot be changed.

Activity Date Date on which the property was associated with the wizard.

Column: GORDSPR_ACTIVITY_DATE


. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions



To change the text of a wizard question:

Note: You can change the text of questions only for properties that are not locked on the Desktop Tools—Step Type Properties Rule Form (GORDSTP).

1. Access the Desktop Tools—Wizard Steps Setup Application Form (GOADSTE).

2. Enter the Add-In Code of the wizard.

3. Enter the Wizard Name.


5. Select the Step Name (wizard window) for which you want to change text. You can use the scroll bar to view the steps associated with the wizard in the key block.

Tip: You can query on any of the fields in this block using standard query functions.


7. Change the desired text in the Value field.

8. Save.

Warning: This form automatically saves your changes when you navigate out of a changed field.

To change the Value field:

Note: You can change the text of questions only for properties that are not locked on the Desktop Tools—Step Type Properties Rule Form (GORDSTP).

User ID Banner-assigned value that indicates whether the property was associated with the wizard by Banner or by a user.

Column: GORDSPR_USER_ID


Values:



. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions



1. Access the Desktop Tools—Wizard Steps Setup Application Form (GOADSTE).

2. Enter the Add-In Code of the wizard.

3. Enter the Wizard Name.


5. Select the Step Name (wizard window) for which you want to change text. You can use the scroll bar to view the steps associated with the wizard in the key block.

Tip: You can query on any of the fields in this block using standard query functions.


7. Make any changes to the Value field.

8. Save.

Warning: This form automatically saves your changes when you navigate out of a changed field.

Electronic Documents Wizard Form(GOAWFIZ)

Use this form to import Banner forms into the Electronic Documents Dictionary Form (GORWFDD). A form must be imported into GORWFDD before you can use any fields on the form in electronic documents. You can use any field on any imported form in an electronic document.

When you access the wizard, the Welcome screen appears. Click Next to continue. The Electronic Documents Metadata Setup window appears.

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions

Form Names List of Banner forms. Select the forms that contain fields you want to include on electronic documents. You can scroll through the form names or use standard query functionality to search for them. Display-only.

Description English name of each form. Display-only.

Previously Set Up

Check box that indicates whether the form was already imported. If it was already imported, you don’t need to import it again.



Electronic Documents Dictionary Form (GORWFDD)

Use this form to review and manipulate information from the Banner forms that were imported with the Electronic Documents Wizard Form (GOAWFIZ). GORWFDD shows you information about each field on each form at the metadata level.

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions

Product Type Defaults to Oracle Forms.

Application Name

Name of an imported Banner form.

(button) List Application Name Metadata List (list of all the forms that have been imported)

Element Name Fields from the Banner form. Information about the highlighted field appears in the right half of the window. As you scroll down the list of fields on the left, you can see the information change on the right.

Hint Text Help text as it looks on the status bar in Banner.

Type Field type (text, check box, or list).

Length Maximum field length.

Datatype Type of data (character, number, date, or long data).

Database Name Target database for the field.

Low Range Minimum value the field can contain.

Required Ind If selected, the field is required by the source table.

High Range Maximum value the field can contain.

Single Ind If selected, the field is a single row item, rather than a multiple row item.

Case Restriction Specifies whether data entered in the field must be uppercase, lowercase, or mixed case.



Electronic Documents Builder Form (GORWFDB)

Use this form to create and modify electronic documents.

Note: Before you can create an electronic document, you must create its code on the Electronic Documents Validation Form (GTVWFED). Also, make sure all the fields that will be built into it are from forms that have been imported via the Electronic Documents Wizard Form (GOAWFIZ).

If you try to change an electronic document that was delivered by SunGard Higher Education, you must be logged on as the BASELINE user.

Main Window

The heading section contains the following fields:

Format Mask Format for the data (for example, a date might be DD-MON-YYYY).

List Name Name of the source Banner form used for code/description searches.

(lookup) List List of Objects (forms imported using GOAWFIZ)

Table Name Name of the source table used for code/description searches.

Column Code Name

Name of the source code column used for code/description searches.

Column Desc Name

Name of the source description column used for code/description searches.

Where Clause Where clause statement used for code/description searches.

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions

Document Code Name of the electronic document.

(lookup) List Electronic Documents Validation Form (GTVWFED)



The toolbar between the heading section and the body contains the following fields and buttons:

The body of the form is a spreadsheet where you can create fields and assign labels to them. You must enter attributes for each field on the Properties window. Scroll to place the labels and fields where you want them. You can add sheets to your electronic document.


Description of the electronic document. Display-only.

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions

Cursor Location (untitled)

As you move through the spreadsheet, this field changes to indicate the location of your cursor. Display-only.

First Page Select this button to go to the first sheet of the electronic document.

Previous Page Select this button to go to the previous sheet of the electronic document.

Current Page (untitled)

Indicates which sheet you are viewing. Display-only.

Next Page Select this button to go to the next sheet of the electronic document.

Last Page Select this button to go to the last page of the electronic document.

Apply Order Select this button to display the Application Apply Order window so you can specify the order in which the Banner forms will appear to the user applying the data.

Properties Select this button to display the Properties window so you can specify properties for each cell in the spreadsheet.

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions



Application Apply Order Window

Use this window to specify the order in which the Banner forms will appear to the user applying data for an electronic document. Use the Apply Order button to display this window.

Properties Window

Use this window to assign properties to labels and fields. A label has only one property: the Cell Type is Label. Use the Properties button to display this window.

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions

Seq # Sequence number that indicates the order in which the form will appear when data is being applied.

Name Name of the Banner form. The form must have been imported using the Electronic Documents Wizard Form (GOAWFIZ).

(lookup) List Application Name Metadata List

Description Description of the Banner form. Display-only.

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions

Cursor Location (untitled)

Row and column where your cursor is located. Display-only.

Cell Type Cell type:

Label User cannot enter information into the field.

Text User can enter information into the field.

Display Information is displayed but cannot be updated.

Application Name

Name of the Banner form where data will be applied after the request is approved. Entering a form here puts it on the Application Apply Order window.

(button) List Application Name Metadata List (list of all the forms that have been imported)



Application Target Name

Field in the form where the data is entered when it is applied.

(button) List Application Elements Metadata List

Database Target Name

Database field that will hold the data when it is applied. This information is entered automatically when you select the Application Target Name.

Required Indicator

Check box that indicates whether an entry is required when someone fills out the electronic document.

Datatype Type of data to be entered in the field.

Length Maximum number of characters that can be entered.

Default Value Default value that is automatically entered when the electronic document is first entered.

Prevent Override Default Values

Check box that indicates whether the default value can be overridden.

Event Type Type of event:

Validate Validate the entry.

Calculate Calculate a value.

Security Restrict access.

The function that performs this action is described in the Event API block. If you enter a function in the Event API block, but do not specify its type in this field, the function is not performed.

Low Range Smallest valid value a user can enter in the field.

Entry Help Help text that appears when data is entered into the field. This text appears in the status bar when the cursor is in the field.

High Range Largest valid value a user can enter in the field.

Apply Help Help text that appears when data is applied. This text appears in the status bar when the cursor is in the field.

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions



Event API Block

Use this block to identify functions that perform an event for the field.

Note: If you want to delete information from the Properties window after it has been saved, you must perform a Delete Record function with your cursor in the top portion of the window and another with your cursor in the Event API block. They are separate blocks.

Electronic Documents Form (GOAWFED)

Use this form to create a new transaction based on an electronic document. You can also use this form to view an existing transaction.

List Banner validation form containing the valid values for the field.

(lookup) List Application Name Metadata List (list of all the forms that have been imported)

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions

Seq # Sequence in which the functions should be evaluated. If the function passes more than one parameter, the function is listed once for each parameter, and this sequence number is repeated.

Function Name Function used to perform the event specified in the Event Type field in the main block. If you enter a function but don’t have an Event Type, the function is not performed.

Seq # Sequence in which the parameters are passed to the function.

X Column containing the field being passed to the function as a parameter.

Y Row containing the field being passed to the function as a parameter.

Datatype Datatype of the parameter being passed to the function.

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions



Main Window

Use this window to create a new transaction or review an existing one:

• To create a new transaction, you must enter the Document Type and Transaction Description.

• To review an existing transaction, you must enter the Transaction Description or Transaction # of the transaction you want to see.

The same three fields are visible regardless of the choice you make:

Below these fields is a toolbar with the following fields and buttons:

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions

Document Type Electronic document type code. Required.

(lookup) List Electronic Document Type List (GTVWFED)

Transaction Description

Freeform text describing your transaction. Required.

Transaction # If you are creating a new transaction, this field is display-only. Banner automatically generates this number to identify your transaction. Each transaction number is unique.

If you are reviewing an existing transaction, select the Search button to see all the transactions you have had a part in, by initiating them, approving them, or applying the data. When you select a transaction number, Banner displays the Document Type and Transaction Description fields automatically.

(button) List Transaction History Data List

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions

First Page Select this button to display the first sheet of the electronic document.

Previous Page Select this button to display the previous sheet of the electronic document.

Current Page (untitled)

Indicates which sheet you are viewing. Display-only.

Next Page Select this button to display the next sheet of the electronic document.



Last Page Select this button to display the last page of the electronic document.

Comments Select this button to display the Comments window so you can enter a comment. Your comments are stored with the electronic document, and other users can add to and review them throughout the transaction’s life.

Search Place your cursor in a field and select this button to see valid values for the field. The LOV must have been specified on GORWFDB.

In Process Select this button to put a transaction into Hold status. (Select the Completed button to take the transaction out of Hold status).

Completed Select this button when you are finished entering data in the document. If you have not entered all the necessary fields, the transaction’s status is Waiting; otherwise, its status is Pending.

Approve Select this button to approve a transaction. The status of the transaction becomes Approved. This button is only visible when the form is accessed by an authorized approver or a super user.

Disapprove Select this button to disapprove a transaction. The status of the transaction becomes Disapproved. This button is only visible when the form is accessed by an authorized approver or a super user.

Return for Correction

Select this button to send the transaction back to the originator. The transaction’s status becomes Returned for Correction. This button is only visible when the form is accessed by an authorized approver or a super user.

Selected Apply Select this button to see a list of all the forms used in the apply process for this document.

Choose the first one you want to see and select the Exit button to return to the list of forms. Choose the next one, skipping over any that don’t pertain to the current document. You must view them in the order in which they are listed, however. If you skip one, you cannot go back to it.

This button is only visible when the form is accessed by an applier or a super user.

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions



The body of the electronic document has labels and fields as designed by the business analyst.

If fields on an electronic document were set up on the Electronic Documents Builder Form (GORWFDB) to allow code/description searches, you can use this functionality on those fields. Enter the code for an item, and press the Tab key. A function built into the field returns the description of the code in the next field.

Start Apply Process

Select this button to see the first form in the apply process. Select the Exit button to move to the next one. You will move through all forms specified for the electronic document in order. This button is only visible when the form is accessed by an applier or a super user.

Status Current status of the transaction:

HoldThe originator selected the In Process button so the document could be finished later.

WaitingThe originators selected the Completed button, but some of the required fields are empty.

PendingThe originator entered all the required fields and selected the Completed button. The approval process has begun. If the transaction must be approved by more than one person, the status remains Pending until one person returns it for correction or disapproves it, or until all have approved it.

ReturnedOne of the approvers sent the transaction back to the originator by selecting the Return for Correction button.

DisapprovedOne of the approvers disapproved the document by selecting the Disapproved button.

ApprovedAll the approvers selected the Approved button.

AppliedAll the appliers entered the data into the Banner forms, then selected the OK button; or an automated activity electronically updated the Banner tables.

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions



Comments Window

Use this window to enter comments about the transaction. Select the Comments button on the main window to display the Comments window.

During the life of the transaction, different users can add their comments, which are displayed in the Comments field at the top of the window. You can scroll back to see all the users and their comments, from the newest comments to the oldest.

Selected Apply Window

Use this window to apply data to the Banner databases. When you are ready to apply data, select the Selected Apply button to access this window. It lists all the forms on which data can be applied for this transaction, allowing you to skip any that are not necessary for your particular situation.

You must access the forms in order; if you skip a form, you cannot go back to it.

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions

User Name Last user who entered a comment for this transaction. Display-only.

Activity Date Date the last comment was entered. Display-only.

Comments Last comments entered for this transaction. Display-only.

Current Comments

Enter your comments here, then select the OK button.

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions

Select to Apply Select this button to access the corresponding form.

Seq # Sequence in which the form is accessed if the user uses the Apply All process.

Application Name

Banner form into which data will be entered.

Description Description of the form.

Applied If selected, the form has been accessed and the data has been applied on it.



Electronic Documents Security Form (GORWFDS)

Use this form to specify super user access to electronic documents, based on Oracle ID.

Electronic Documents Validation Form (GTVWFED)

Use this form to create and maintain the codes and descriptions of the electronic documents.

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions

User ID Oracle user ID. Required.

(button) List Oracle Users List Form

Document Type Electronic document to which you are granting access to the super user. Required.

(lookup) List Document Types List Form

Query Check box that indicates the super user can query the electronic document. The check box is selected automatically. Display-only.

Update Check box that indicates the super user can update the electronic document.

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions

Electronic Document Type

Electronic document code. Required.

Description Freeform text describing the code. Required.

Activity Date Date the record was created or was last updated. Display-only.



Electronic Documents Form (GOQWFED)

Use this form to apply data to the Banner databases. This form does not appear on any Banner menus. It is a mirror image of the Electronic Document Form (GOAWFED), which has the same name.

GOQWFED lets you toggle back and forth between the electronic document containing the data to be applied and the Banner form on which the data should be entered. You can copy and paste the data from one to the other. See Chapter 3, Processing, for instructions on using this form.

Target System Code Validation Form (GTVEQTS)

Use this form to define the external systems that require notification when an event occurs. Campus Pipeline and Workflow are external systems.

When you first access GTVEQTS, the form displays all defined target system codes. You can query any displayed field, including Activity Date.

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions

Target Code Code that uniquely identifies an external system that requires notification when an event occurs. Required.

Caution: Target codes WORKFLOW and PIPELINE are delivered with the system and should not be changed or deleted. (Changes may impact the processing of events.)

You can change or delete the Target Code only if the target system has no associated records in the detail block on the Event Queue Name Definition Form (GOREQNM).

Description Free-form description of the target system. Maximum length is 30 characters. This field is accessible only if a Target Code is defined for the record. Required.




Parameter Code Validation Form (GTVEQPM)

Use this form to define the parameters that are associated with events. Employee class, e-mail address, student major, and term code are all examples of parameters that can be defined on this form.

When you first access GTVEQPM, the form displays all defined parameter codes. You can query any displayed field, including Activity Date.


BASELINE SunGard Higher Education delivered the record as seed data or the client inserted the record while logged into Banner as BASELINE. Only BASELINE users can change or delete the Target Code field.

LOCAL The client inserted the record with a login ID other than BASELINE. Any user ID can change or delete the Target Code field.

Display-only.


. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions

Parameter Code Code that uniquely identifies a parameter. This code is matched to the context parameters in the external system during the communication process. Required.

You can change or delete the Parameter Code only if the parameter code is not associated with any parameter group code on the Parameter Group Rule Form (GOREQPG).

Warning: Parameter codes are case sensitive. They must be defined exactly the same in Banner and in the external systems. ClearText/Credential and ClearText/SCT.Credential must be entered in mixed case.



Parameter Group Code Validation Form (GTVEQPG)

Use this form to define the parameter groups that can be associated with events. For example, a parameter group can be defined for all the parameters passed to Workflow when an employee is hired.

The parameter group code is defined on GTVEQPG. Once the code is defined, you can use the Parameter Group Rule Form (GOREQPG) to assign specific parameters to the group.

When you first access GTVEQPG, the form displays all defined group codes. You can query any displayed field, including Activity Date.

Description Free-form description of the parameter code. Maximum length is 30 characters. This field is accessible only if a Parameter Code is defined for the record. Required.



BASELINE SunGard Higher Education delivered the record as seed data or the client inserted the record while logged into Banner as BASELINE. Only BASELINE users can change or delete the Parameter Code field.

LOCAL The client inserted the record with a login ID other than BASELINE. Any user ID can change or delete the Parameter Code field.

Display-only.


To display the Activity Date, use the scroll bar at the bottom of the pane that contains the User ID field.

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions



Event Queue Code Validation Form (GTVEQNM)

Use this form to define the events that will be captured and sent to external systems. Adding an e-mail address, changing a grade, adding a course, hiring an employee, and changing a password are all examples of events that can be defined on this form.

When you first access GTVEQNM, the form displays all defined event codes. You can query any displayed field, including Activity Date.

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions

Group Code Code that uniquely defines a parameter group.

You can change or delete the Group Code only if the group code has no detail records on the Parameter Group Rule Form (GOREQPG). Required.

Description Free form description of the group code. Maximum length is 30 characters. This field is accessible only if a Group Code is defined for the record. Required.



BASELINE SunGard Higher Education delivered the record as seed data or the client inserted the record while logged into Banner as BASELINE. Only BASELINE users can change or delete the Group Code field.

LOCAL The client inserted the record with a login ID other than BASELINE. Any user ID can change or delete the Group Code field.

Display-only.




Integration Partner System Rules Form (GORINTG)

Use this form to create and maintain the rules and cross-referenced codes that are used by institutions with one or more schedule type codes or instructional method codes that are used to flag courses and course sections for integration.

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions

Event Code Code that uniquely identifies an event. This code is matched to the event name in the external system during the communication process. Required.

You can change or delete the Event Code only if both of these conditions exist:

• The event was never run. This means the event was never inserted into the Event Queue table to be selected by the Event Dispatcher.

• The event is not associated with any target system on the Event Queue Name Definition Form (GOREQNM).

Description Freeform description of the event. Maximum length is 30 characters. This field is accessible only if an Event Code is defined for the record. Required.



BASELINE SunGard Higher Education delivered the record as seed data or the client inserted the record while logged into Banner as BASELINE. Only BASELINE users can change or delete the Event Code field.

LOCAL The client inserted the record with a login ID other than BASELINE. Any user ID can change or delete the Event Code field.

Display-only.




Main Window

Parameter Group Rule Form (GOREQPG)

Use this form to assign defined parameters to groups. For example, you can assign the ID, position code, effective date, and employee class parameters to a group.

Once parameters are assigned to a parameter group, you can use the Event Queue Name Definition Form (GOREQNM) to assign the parameter group to events.

You can insert or delete parameters into a parameter group only if the parameter group is not associated with any target systems on the Event Queue Name Definition Form (GOREQNM).

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions

Integration Partner Value

Code used by your institution to identify a partner system. For example, W might be used to identify WebCT courses. You would then use the W code to flag the appropriate course records on SCACRSE and course section records on SSASECT.

Description Description of your institution’s partner value.

Cross Referenced Partner System

Partner system code. Choices come from the Integration Partner System Code Validation Form (GTVINTP).

Description Partner system code description. This value is defined on the Integration Partner System Code Validation Form (GTVINTP).



. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions

Group Code Code that uniquely defines a parameter group. Maximum length is 100 characters. Optional.

(lookup) List Parameter Group Validation List (GTVEQPG)



Event Queue Name Definition Form (GOREQNM)

Use this form to define specific events for the target system. This definition includes associating a parameter group with each event.

For example, you can use this form to set up an event for hiring an employee and identify the specific group of parameters associated with that event.

Sequence Sequence number that defines the order in which the parameter is sent to the target system. Required.

Parameter Code that uniquely identifies a parameter. Required.

(lookup) List Parameter Validation List (GTVEQPM)

Warning: Parameter codes are case sensitive. They must be defined exactly the same in Banner and in the external system.

Default Value Default value for the parameter. Maximum length is 2000 characters. This default value, if defined, is sent to the target system. Enter this value if the parameter value is the same each time the event occurs. Optional.

You cannot update this field if the Parameter field is EVENTTYPE or SUBEVENTTYPE.

Warning: Default values are case sensitive.

Target Parameter Name

Name used in the target system to identify the parameter. This field links the Banner parameter with the associated parameter in the target system. Maximum length is 100 characters.

This is an optional field. You can leave this field blank if the target system uses the name that is in the Parameter field. If the target system uses another parameter name, you must enter that name in this field. By using this field, you can set up a more user friendly name in the target system.

Warning: Target parameter names are case sensitive. They must be defined exactly the same in Banner and in the external system.

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions



. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions

Target System Code that uniquely identifies the target system. Optional.

(lookup) List Target System Validation List (GTVEQTS)

Event Code Code that uniquely identifies an event. Required.

You can update or delete this code only if the event was never run. This means the event was never inserted into the Event Queue table to be selected by the Event Dispatcher.

(lookup) List Event Validation List (GTVEQNM)

Description Description associated with the event code. Display-only.

Group Code Code that uniquely identifies a parameter group. Required.

You can update or delete this code only if the associated event was never run. This means the event was never inserted into the Event Queue table to be selected by the Event Dispatcher.

(lookup) List Parameter Group Validation List (GTVEQPG)

Description Description associated with the parameter group. Display-only.

Active Check box that determines whether the event is active or inactive.

selected The event is active. Records are inserted into the Event Queue table when the event occurs. The Event Dispatcher sends parameters and values to the appropriate target system for processing.

cleared The event is inactive. Records are not inserted into the Event Queue table when the event occurs.

Events are delivered with an inactive status. This status can be changed.



Event Queue Record Maintenance Form (GOAEQRM)

Use this form to review event records created in Banner. You can change the status of event records on this form. This form lists all events by target system. You can further refine the listing by event code and/or event status.

This form shows three kinds of information:

• Events Data. This is the basic information about all events that match the criteria in the key block.

• Parameter Data. This is parameter information for a specific event selected in the Events Data block.

• Event Errors. These are all error messages for the target system specified in the key block.

Key Block

Use this block to identify the events you want to review. You must identify the target system you want to review. Within the selected target system, you can optionally refine the list by event code and/or event status.


BASELINE SunGard Higher Education delivered the record as seed data or the client inserted the record while logged into Banner as BASELINE. Only BASELINE users can delete these records, change the Event Code field, or change the Group Code field.

LOCAL The client inserted the record with a login ID other than BASELINE. Any user ID can delete these records, change the Event Code field, or change the Group Code field.

To display the User ID, use the scroll bar at the bottom of the pane that contains the Description and Active fields.

Display-only.

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions



Events Data Block

Use this block to review and/or change the status of events. This block shows basic information about all events that match the criteria in the key block.

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions

Target System Code that uniquely identifies the target system. Optional.

(lookup) List Target System Validation List (GTVEQTS)

Event Code Code that uniquely identifies an event.

(lookup) List Event Validation List (GTVEQNM)

If you enter a value in this field, only records with that event code are displayed in the Events Data block. If you leave the field blank, all events for the target system are displayed. Optional.

Status Drop-down list that identifies the status of events. If you select a status, only records with that status are displayed in the Events Data block. If you wish to view all records, select None from the list. Required.

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions

Sequence Unique one-up number generated by the system to identify an event. Display-only.

Event Code that uniquely identifies the event associated with the sequence number. Display-only.



Parameter Data Block

Use this block to display parameter information for a specific event selected in the Events Data block. All fields in this block are display-only.

Status Drop-down list that identifies the current status of the event. Valid values are:

Ready for ProcessingThis is a new event that the Event Dispatcher has not selected for processing. You can change the status of this event. The system can also change this status to Processing.

ProcessingThe Event Dispatcher has selected the event, but has not yet completed processing it. You can change the status of this event. The system can also change this status to Processed or Rejected.

ProcessedThe Event Dispatcher has selected the event, and has completed processing it. You can change the status of this event. The system does not change this status.

RejectedThe Event Dispatcher has rejected the event and will not process it. You should correct the event or event rules so that the event can be processed. Once corrections are made, the system administrator can change the status to the appropriate value. This value is reserved for system use only. The system administrator cannot set an event to Rejected.

HoldThe event should not be selected by the Event Dispatcher for processing. Only the system administrator can change this status.

Required.

User ID Oracle ID of the person who last updated the record. Display-only.


. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions

Sequence Number that defines the order in which the parameter is sent to the target system.

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions



Event Errors Window

Use this window to display all error messages for the target system specified in the key block. All fields in this block are display-only.

Integration Configuration Settings Form (GORICCR)

Use this form to maintain settings and configurations that are required for the Integration for e-Learning product. These configurations allow clients to control aspects of their institution's integration between Banner and third party systems.

Main Window

Key Block

Parameter Code that uniquely identifies a parameter.

Value Value the system generated for the associated parameter when the event occurred.

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions

Error The Oracle error number.

Error Message The Oracle error message.

Call Stack Location in the program code where the error occurred.


. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions

Process Code used to select process which contains all settings related to the integration solution. As of Intcomp’s Release 7.3, the only valid process value is ELEARNING.

Setting Code that is used to determine (or cross reference) specific values that are used to configure Integration for e-Learning.



Configuration Settings Block

Menu Maintenance Form (GUTGMNU)

Use this form to create and maintain custom menus for your institution. You can customize the menus delivered by SunGard Higher Education to make them more applicable to your operations. Menus can contain any combination of forms, jobs, other menus, and QuickFlows.

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions

Setting Specific code for the integration (for example, ACTIVE_ENROLLMENT_STATUS).

Sequence Sequence number for settings that may have multiple values where the order is significant (for example, ICADDRESS).

Value Institution-defined value. This value comes from Banner validation forms. An example is a term code from STVTERM. These values may also come from a finite set of allowed values (for example, LDIMODE has a setting of A or L).

Description Description of the value.



Translation Translation value, if required. For example, ICMEETYPE has a translation value of CLASSROOM.



This form contains three parts:

• The left pane lists the available forms, jobs, menus, or QuickFlows that can be added to a menu. When you select an object type from the pull-down list above this pane, a list of associated objects appears in the left pane.

• The middle of the form contains iconic buttons used to insert your selections, remove selections, insert all items listed from the left pane, and remove all items from the right pane.

• The right pane lists the contents of a menu. The fields above the right pane identify the menu name, menu description, and system associated with the menu.

To add objects to a menu, you can select names in the left pane and use the Insert Selection button.

To remove objects from a menu, you can select names in the right pane and use the Remove Selection button.

Refer to the “Processing” chapter in this guide for more information.

Oracle Password Change Form (GUAPSWD)

Use this form to change your Oracle password. The password becomes effective when you exit and re-enter Banner.

The Oracle User ID field contains your current Oracle ID and cannot be changed. Enter your current password in the Oracle Password field. You must correctly enter your current password before you can proceed to the next field. Enter your new password in the New Oracle Password field. Re-enter the new password in the Verify Password field exactly as you entered it in the New Oracle Password field.

Passwords cannot include a dollar sign ($). Passwords cannot begin with a number, but you can use a number anywhere else in the password. Make sure you do not select an Oracle reserved word as your password.

Select the OK button to save your changes, or select Cancel to exit the form.

Note: If Workflow is enabled, a password change fires a business event for Workflow.



General User Preferences Maintenance Form (GUAUPRF)

Use this form to establish personal preferences for your user ID. You can choose:

• Whether different elements, such as warning messages and the release number, display on your screen

• The color of selected elements

• A directory path for various Banner features

• Links for your My Links section on the main menu

• Which Banner menus are open when you log in

This form is also used by system administrators to set up default preferences for the entire institution. Institution-wide settings are specified in the Default Value fields, and can only be changed by a system administrator. Additionally, portions of this form are only accessible by a system administrator. Information about using these portions of the form is contained in the Banner Middle Tier Implementation Guide.

The User Value fields are where you specify your personal preferences. The values you enter in these fields override the default values set up by the system administrator. Use caution when overriding default values, because some features of Banner depend upon these settings.

You can access this form from the main menu, by using Direct Access, or by selecting Preferences from the File pull-down menu.

Note: Most of the changes you make on this form appear immediately on all Banner forms; however, the General Menu Form (GUAGMNU) will not display changed title bar preferences for form name, release number, or database instance until you log out and log back in. Also, the Personal Links description changes do not display on the General menu form (GUAGMNU) until you log out and log back in.

Refer to the Banner Getting Started Guide for more information about using this form to customize Banner for your preferences.

Display Options Window

Use this window to specify how different options in Banner are displayed.

Display Options

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions

Display Form Name on Title Bar

Check box that indicates whether you want the seven-character name of the form to appear on the title bar (for example, SPAIDEN).



Alert Options

Display Form Name on Menu

Check box that indicates whether you want the seven-character name of the form to appear on menus.

Display Release Number on Title Bar

Check box that indicates whether you want the release number to appear on the title bar.

Display Database Instance on Title Bar

Check box that indicates whether you want the database instance to appear on the title bar.

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions

Prompt Before Exiting Banner

Check box that indicates whether you want to be prompted with a message Are you sure you want to quit? prior to exiting your Banner session. By using the prompt, you can avoid unintentionally closing your Banner session.

Display Additional Confidential Warning

Check box that indicates whether you want Banner to display an extra Confidential pop-up message for records that contain confidential information.

Display Additional Deceased Warning

Check box that indicates whether you want Banner to display an extra Deceased message for records associated with a deceased person.

Display Duplicate SSN/SIN/TIN Warning

Check box that indicates whether you want Banner to display a warning message if you try to create a new ID with a SSN/SIN/TIN that is already being used.

If you check this box, a pop-up error message window will be displayed for any duplicate SSNs when you add the SSN/SIN/TIN to the identification record.

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions



Data Extract

User Interface Color Settings

In this section of the form, you can change the colors of elements on your Banner screen, including:

• Non-iconic buttons

• The canvas

• Code/Description prompts

• The broadcast message canvas on the main menu

• The main menu canvas

• The menu links canvas

• Highlighted records

• Scroll bars

• Separator lines

Directory Options Window

Use this window to specify the directory that you want to use for various features of Banner. Each option on this window has three fields:

• Description--The type of directory, such as Local directory for saving output.

• Default Value--The default directory for the entire institution. The value is set by the system administrator. You cannot change it.

• User Value--Your preferred value for the option, if you want to use a value other than the institution default. If you do not enter a value in this field, then the value in the Default Value field is used.

Note: If you enter a User Value and later want to use the Default Value, you must delete the record. You cannot simply erase the User Value.

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions

Include Header Row in Data Extract

Check box that indicates whether you want to have a column heading on your data extract file. If you check this box, column headings will always be added to your extract files.



Local directory for saving output

This directory is where files are saved if your institution uses the WebUtil method of saving output. Output from Banner’s data extract feature, the GASB Parameter Form (FGAGASB), and the Saved Output Review Form (GJIREVO) is all saved to this directory.

Note: System administrators should choose the default location carefully, taking into consideration the security implications. It is recommended that a central, shared directory is not used.

The value c:\temp is delivered as the default value for both the User Value and Default Value fields. It refers to the c:\temp directory on the client workstation.

Data extract format: FILE, TEXT, or WEBUTIL

This record enables you to specify the method you want to use for data extracts.

• FILE--Saves your output in comma separated value (CSV) format, so you can save the information to your desktop, and open it with an application such as Microsoft Excel.

Note: This option does not work if your institution uses a Real Application Cluster (RAC) environment.

• TEXT--Displays your extracted data as text that appears in a new browser window. Do not use this option if you want to save the output after viewing it.

• WEBUTIL--Uses the General WebUtil File Extract Form (GUQWUTL) to save your output to a file. This is the preferred method to extract data in a RAC environment.

Note: This option only works if your system administrator has configured Oracle WebUtil at your institution. If it is not configured, and you choose WEBUTIL as the value for this record, you will receive an error when you try to extract the data. System administrators can refer to the Banner Middle Tier Implementation Guide for information about configuring WebUtil.

Enter the location for your online help for web access

This record contains the URL that points to the directory where the online help files are stored. The directory must be accessible from the Web server.

Enter the location of your Banner ID images

This directory is the location of the images that are displayed for user IDs on the Personal Image Form (GUAIMGE). The directory you choose must be available from the Web server.

ID images must be .bmp files, and named in the following manner: the capital letter I followed by the last seven characters of the ID (for example, I0807091.bmp).



Enter the name of your Oracle Reports Server

This record contains the name of the Oracle Reports server.

Enter the name of your Oracle Reports Service Name

This record contains the Oracle Reports Service Name.

Enter the name of your Oracle Reports Root Subfolder

This record contains the name of the subfolder within the Oracle Reports root directory. Depending upon how Oracle Reports are set up at your institution, you may be able to specify a subfolder for your username directory on the Oracle Reports server.

Enter the name of your Web Output URL

Web Output URL to be used for viewing the output of a data extract or job submission.

My Links Window

You can create a link from the main menu to a web site or Banner object using personal links. The first link is your institution’s web site.

Note: Make sure you do not have pop-ups blocked with any third-party software. Pop-up blockers can interfere with the performance of your personal links.

To create a link:

1. Choose the My Links tab.

2. Enter a description of your link in the User Value field associated with the first personal link description.

3. Enter the URL or Banner object name in the User Value field associated with the first personal link URL or Banner object.

4. Save. You must exit Banner and log back in to see your new descriptions on the Main Menu form (GUAGMNU).

You can create up to six personal links. Each personal link is comprised of two records—the description and the URL/object. Make sure the description record matches the corresponding URL or Banner object record.



Menu Settings Window

Use this window to choose the menu that will be open when you first log in to Banner.

LDAP Options Window

This window is used to store the options for LDAP and Single Socket Layer (SSL) for your institution.

Note: Only system administrators can access this window. For information about configuring LDAP and SSL, refer to the Banner Middle Tier Implementation Guide.

My Banner Maintenance Form (GUAPMNU)

Use this form to create a personal menu tied to your Oracle user ID. A personal menu contains the forms, jobs, menus, and QuickFlows that are most important in your daily work. Once the personal menu is created, you can access it from the main menu.

This form contains three parts:

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions

Default Value A preference is initially set for the institution by a script run during installation. It can only be changed by a user logged in as the BASELINE user, which changes the preference for the whole institution.

User Default If you want to use an open menu other than the institution default, you can specify it in this field. The value you choose will not be overwritten by subsequent releases of Banner, and only applies to your user ID.

If you do not specify a preference, the institution’s default preference will be displayed.

For either default you can enter the name of the menu, or click the Search button to search for a menu on the Object Search Form (GUIOBJS). The menu must already exist on GUIOBJS, or you will receive an error message. The description of the menu is automatically populated.

Note: Any menu chosen to be the default must already exist as part of the *MAIN Banner menu tree structure. It must exist in GUIOBJS with a Type of Menu.



• The left pane lists the available forms, jobs, menus, or QuickFlows that can be added to a personal menu. When you select an object type from the pull-down list above this pane, a list of associated objects appears in the left pane.

• The middle of the form contains buttons used to insert your selections, remove selections, insert all items listed from the left pane, and remove all items from the right pane.

• The right pane lists the contents of the personal menu. The field above the right pane shows the Oracle user ID associated with the person logged on to the system.

To add objects to a personal menu, select names in the left pane by double-clicking them, and then use the Insert or Insert All button.

To remove objects from a personal menu, select names in the right pane by double-clicking them, and then use the Delete or Delete All button.

My Banner Maintenance and Copy Form (GUTPMNU)

Use this form to copy a personal menu from one user to another user or group of users. This feature is very helpful when a new employee needs to perform certain tasks. If another employee performs similar tasks, you can copy the existing personal menu to the new employee.

You can add, delete, and move menu items before you perform the copy function. This works the same way as maintenance on the My Banner Maintenance Form (GUAPMNU).

When you are ready to copy, select the Copy button in the middle of the form. A list of IDs appears in the left pane. Scroll through the list or search for an ID. Select each ID to receive the copied menu. Select the Copy to users button in the middle of the form.

Object Maintenance Form (GUAOBJS)

Use this form to create new Banner objects (forms, jobs, menus, and QuickFlows). New objects are created as follows:

• New forms must be created on this form.

• New jobs can be created on this form or on the Process Maintenance Form (GJAJOBS).

• New menus can be created on this form or on the Menu Maintenance Form (GUTGMNU).

• New QuickFlows can be created on this form or on the QuickFlow Definition Form (GUAQUIK).



The System field contains a system indicator code from the System Indicator Validation Form (GTVSYSI). You must use one of the delivered codes or you can set up W, Y, or Z on GTVSYSI to use with your custom forms.

The Data Extract Option field determines which extract options are enabled on the Help menu. The option can be enabled for both key and data blocks, data blocks only, or not enabled. SunGard Higher Education delivers Banner with the extract option enabled for all validation forms. Your system administrator can use this form to enable the extract feature on any form where the extract has been tested.

Note: If you want to extract data on an untested form, your system administrator can consider enabling the extract feature on GUAOBJS. SunGard Higher Education does not support this feature on untested forms. SunGard Higher Education will, however, continue to test more forms and expand support with future releases.

The User ID is BASELINE if the object was delivered with Banner; these objects cannot be deleted. The User ID is LOCAL if the object was developed at your institution.

Object Search Form (GUIOBJS)

Use this form to search for an object (form, job, menu, or QuickFlow) using as much of the name, description, or type as you know. Once you locate the object, you can access it directly from this form.

Object Code Validation Form (GTVOBJT)

Use this form to define codes that identify the object types used on the Object Maintenance Form (GUAOBJS). Examples of an object type include form, job, menu, and QuickFlow.

The Object Type can be a form, job, menu, QuickFlow, or message. Process menus use the message object type to display a message that tells you to use a desktop or Web application to complete the activity.

QuickFlow Code Validation Form (GTVQUIK)

Use this form to define the QuickFlow codes used in the QuickFlow process. For information about the use of this form, see “Creating a QuickFlow” in Chapter 3, Processing.



QuickFlow Definition Form (GUAQUIK)

Use this form to define a QuickFlow. A QuickFlow is a technique that lets you link a set of forms in a specific sequence. Any form, except for the following forms, can be added to a QuickFlow:

• Main menu (GUAGMNU)

• Welcome to Banner Form (GUAINIT)

• QuickFlow Form (GUAQFLW)

• Security Maintenance Form (GSASECR)

• Any query form (Q is the third character of the form name)

The QuickFlow Form (GUAQFLW) lets you access the first form in the QuickFlow. When you exit the first form, the next form in the sequence is automatically accessed. This process continues until all the forms in the QuickFlow have been accessed and exited.

The QuickFlow code must be defined using the QuickFlow Code Validation Form (GTVQUIK). Forms in the QuickFlow must be valid Banner form names.

Note: When you search for a QuickFlow code, you may notice that the values in the list of values (LOV) come from GTVCALL, rather than GTVQUIK. The values in the GTVCALL table populate the GTVQUIK form. Form names do not necessarily match table names.

See “Creating a QuickFlow” in Chapter 3, Processing, for specific instructions on using this form.

QuickFlow Form (GUAQFLW)

Use this form to submit a QuickFlow that has been defined on the QuickFlow Definition Form (GUAQUIK). When you enter the QuickFlow name and click the Start button, the system accesses the first form in the QuickFlow. When you exit the first form, the next form in the sequence is accessed. This process continues until all the forms in the QuickFlow have been accessed and exited. At this point, you can execute the QuickFlow again or exit to the location where you called the QuickFlow.

Banner form-level security is checked before each form is called to ensure that only authorized users execute the proper forms. Users must have the proper authorization for every form in the QuickFlow when form level security is activated via the Installation Control Form (GUAINST).

Only QuickFlows that have been defined on the QuickFlow Definition Form (GUAQUIK) can be submitted. You can select the Search button to access the QuickFlow Query Form (GUQQUIK) to search for a QuickFlow.



See “Using a QuickFlow” in Chapter 3, Processing, for specific instructions on using this form.

User Identification Control Form (GUAIDEN)

Use this form to associate Oracle log-in IDs with the proper names of users. This form is used throughout Banner:

• The General Message Form (GUAMESG) uses it to select and identify senders and recipients of messages.

• The Function Task Form (GEATASK) uses it to send messages to users regarding performance of tasks for a function.

• Various forms in the Prospect Management module of the Advancement System use it.

• Value-Based Security requires users to be defined on it before they can be defined to VBS.

Enterprise Access Control Form (GOAEACC)

Use this form to associate an Oracle username with a PIDM. This is the only form that establishes a relationship between the Oracle username and the SPRIDEN record.

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions

Abbrev Abbreviation that uniquely identifies the user. The abbreviation can be up to five characters long. Required.

The Prospect Management module of Banner Advancement uses this abbreviation to identify prospect researchers, assignees, contact originators, and comment authors.

The Event Management module in Banner General uses this abbreviation to send messages to users regarding performance of function tasks.

User ID User’s Oracle log-in ID that exists in the ALL_USERS Table. Required.

Name Description that further identifies the user. Enter the proper full name. Required.



General Medical Information Form (GOAMEDI)

This form allows you to view and update the medical conditions of people at your institution, including students, faculty, and staff.

You can use select the Medical Disability Rule Form (GORMEDR) from the Options pull-down menu to access and view the medical condition and disability group associations.

Note: This form is designed to determine if the person entered in the key block is a student, an employee, or both. If the person is an employee, the HR security routines are invoked, based on the rules established on the Installation Rules Form (PTRINST).

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions

Username User’s Oracle name. Required.

If you enter a name that isn’t currently defined as an Oracle username, an error message appears.

If Value-Based Security (VBS) is turned on, a warning appears if the username does not have a VBS profile defined on the Value-Based Restricted Users Form (GOAVUSR).

(button) List VBS Users list

(button) Count Hits All Oracle Users list

ID User’s Banner ID. This ID must be set up on SPRIDEN.


Name Name associated with the ID on SPRIDEN. Display-only.



Key Block

Medical Information Block

This block contains the medical information for the person identified in the key block.

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions

ID The Banner ID for which you would like to see or enter SEVIS information. It is the 9-digit Banner ID on SPRIDEN. You can enter the ID, or select the search button to search for it on the Person Search Form (SOAIDEN), the Employee Search Form (POIIDEN) or the Alternate ID Search Form (GUIALTI). Required.

(Untitled) Name. The name of the person. This is automatically populated from information stored in SPRIDEN, and is a combination of the last name, first name, and middle initial. Display-only.

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions

Medical Code Code that represents the person’s medical condition or physical impairment.

(lookup) List Medical Code Validation (STVMEDI)

(unlabeled) The description of the medical code, up to 30 characters in length. Display-only.

Medical Date This field enables you to record the date associated with the Medical Code so you can track immunization schedules or any date-related medical information.

Disability Type Code representing the nature of the person’s disability. If the code was selected as the default on GORMEDR, it is populated in this field automatically, but you can change it.

(lookup) List Disability Service Validation (STVDISA)

(unlabeled) The description of the disability type code, up to 30 characters in length. Display-only.



Disability Onset Age

A free-form field where you can enter the age at which the person developed the medical condition or physical impairment. Optional.

Primary Disability?

Check box that identifies if the medical condition or physical impairment is the person’s primary disability. Valid values are:

Selected - the specified disability is the person’s primary disabilityCleared - there is another disability that is the person’s primary disability (the default)

Equipment Code Two-digit code indicating what equipment is necessary to respond to the person’s medical conditions that are identified on this form. It may also indicate that a physical change to property is necessary (e.g., a ramp must be installed). Required.

(lookup) List Medical Equipment Code Validation (STVMDEQ)

(unlabeled) The description that corresponds with the Equipment Code. Display-only.

Disability Service

Code representing services available for the person with the disability, e.g., a sign language interpreter. Required.

(lookup) List Disability Service Validation (STVSPSR)

Comment Free-form field, up to 4000 characters in length. Select the Comments icon to access the Banner Editor. Optional.

User ID The Banner ID of the person who created or last updated the record. Display-only.

Activity Date The date the record was created or last updated. Display-only.

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions



Credit Card Transaction ID Form (GOAMERC)

Use this form to identify the:

• Credit card type associated with a Banner process, Banner system, and merchant ID. This set of information determines which credit card types can be used when credit card transactions are performed.

• Cashier associated with a credit card type, Banner process, Banner system, and merchant ID. This set of information is used to assign a cashier ID when a credit card payment request is entered into Banner.

For more information on setting up and using this form, refer to the Web Credit Card Payments Handbook.

Geographic Regions/Divisions by ID Form (GOAPGEO)

Use this form to display the geographic regions assigned to an ID based on its addresses. Regions can be active or inactive.

A record with the System check box selected can be made inactive, but no other fields can be changed. If a record is entered by the user, the System check box remains cleared.

Source/Background Institution Geographic Form (GOASGEO)

Use this form to display the geographic regions assigned to a source/background institution based on its address. You can access this form from the Source/Background Institution Base Form (SOASBGI), the High School Information Form (SOAHSCH), and the Prior College Form (SOAPCOL).

A record with the System check box checked can be made inactive, but no other fields can be changed. If a record is entered by the user, the System check box remains unchecked.

Credit Card Rules Form (GORCCRD)

Use this form to define the rules for validating credit card numbers that are entered by users. For more information, refer to the Web Credit Card Payments Handbook.



Medical Disability Rule Form (GORMEDR)

This form allows you to maintain information needed on the Medical Information Form (GOAMEDI). It allows you to establish the disability types that are associated with medical conditions.

Medical Code Information Block

This block contains all the medical codes that have been defined on the STVMEDI form. It is display-only.

Disability Type Information Block

This block contains all the disability types that are currently associated with the highlighted medical code in the Medical Code Information block. As you highlight other medical codes, the information in this block will change.

Choices are based on values from the Disability Type Validation Form (STVDISA) list of values.

Note: Disability Codes can only be created using the Disability Type Validation Form (STVDISA) form.

Select the Default? indicator if this disability type should be the default for the Disability Type field on GOAMEDI. Only one disability type can be selected as default.

The Disability codes are displayed in alphabetical order, by code.

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions

Medical Code Code, up to 10 characters, that represents a person’s medical condition or physical impairment. Display-only.

Description The description that corresponds to the Medical Code, up to 30 characters in length. Display-only.



Crosswalk Validation Form (GTVSDAX)

Use this form to define records in the Crosswalk Table. Object:Access uses this information to identify the data to be reported in repeating groups and the external codes that should be selected in the Object:Access views. For more information, please refer to the GTVXDAX Handbook.

ZIP/Postal Code Validation Form (GTVZIPC)

Use this form to identify the ZIP codes and postal codes used throughout Banner. You can assign ZIP/postal codes to:



• Recruits on the Quick Recruit Form (SRAQUIK).


. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions

Disability Type Two-character disability types that can be associated with the medical code highlighted in the Medical Code Information block. Required.

(lookup) List Disability Type Code Validation (STVMEDI)

Description The description that corresponds to the Disability Type. Display-only.

Default? This check box indicates if the disability type should be the default value for the Disability Type field on the Medical Information Form (GOAMEDI). Valid values are:

Selected - this should be the default value on GOAMEDICleared - a different value, or none, should be the default

Note: Only one disability type can be the default.

User ID The Banner ID of the person who created or last updated this information. Display-only.

Activity Date The date the record was created or last updated. Display-only.



Defining ZIP/postal codes on this form can help you enter addresses in Banner more accurately. If you are on application form and select a ZIP/postal code from a List of Values, address data from GTVZIPC automatically appears in the associated fields on the form.

Help Form (GUAHELP)

Use this form to create, edit, and display Dynamic Help. Dynamic Help is the traditional help for Banner forms, blocks, and fields. Banner provides two kinds of Dynamic Help:

• Banner Dynamic Help. This help is delivered and updated each time the system is upgraded. You can change this help text, but each system upgrade overwrites your changes.

• Local Dynamic Help. This help is completely written and maintained by your institution. System upgrades do not affect this help text. This is the default when you access Dynamic Help.

Installation Controls Form (GUAINST)

Use this form to enter and maintain overall system information for your institution. This includes your institution’s name and address as you want them to appear in standard report headings and in the About Banner option in the Help pull-down menu.

On this form, you can maintain various process flags that indicate the presence or absence of major components, licensed applications, and/or optional features.

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions

Name Name of your institution.

Address Address of your institution.

Nation Code and description of your institution’s nation.

Phone Area code, telephone number, and extension of your institution.

Operating System

Operating System.

Installation Type Installation Type.



Instance Name Name of the database instance.


ZIP/Postal Code Length

ZIP/Postal Code length, if your institution enforces a length.

Base Currency Base currency.

Maximum Number of Open Forms

Maximum number of Banner forms that can be open in a session concurrently, due to memory considerations on the client workstation. SunGard Higher Education generally recommends that you set this field to NULL, since the introduction of Internet-Native Banner greatly reduced the potential for client-side memory issues.

Century Pivot The Century Pivot is always set to 49. This means that Banner converts two-digit year numbers 00 through 49 to 2000 through 2049, and year numbers 50 and above to 1950 through 1999.

Default Date Format

Radio group that indicates the order in which the month, day, and year components of the date are displayed.

Online Matching Process Enabled

The Online Matching Process Enabled check box is used to turn on the Common Matching process so that it runs automatically. Without doing this, users can access the Common Matching Entry Form (GOAMTCH) and use the Common Matching process, but it will not run automatically whenever a user tries to create a new identification record.

Enable SSN ID Lookup

Click this check box to enable searching for Social Security Numbers in ID fields.

Workflow Enabled

The Workflow Enabled check box is used to turn on Workflow so it can run with Banner. All users should be logged off the system when you change this indicator (either select or clear the check box).

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions



SQL Trace Enabled

The SQL Trace Enabled check box allows you to enable or disable the SQL trace feature. If the check box is selected, users can select Help from the menu bar, then Technical Support, then Turn SQL Trace On to create a trace file that may help you resolve problems. However, it was possible that users could unintentionally create very large trace files. If this check box is cleared, users cannot use this feature.

Messaging Enabled

The Messaging Enabled check box allows you to specify if your institution is messaging-aware. It does not refer to individual business entities, but to the institution as a whole.

Advancement Check box that indicates if your institution is using the Banner Advancement product.

Accounts Receivable

Check box that indicates if your institution is using the Banner Accounts Receivable product.

Financial Aid Check box that indicates if your institution is using the Banner Financial Aid product.

Other Financial Aid

Check box that indicates if your institution is using a non-Banner Financial Aid product.

General (untitled)

This field always displays GENERAL, since General is a required component of Banner.

Finance Check box that indicates if your institution is using the Banner Finance product.

Human Resources

Check box that indicates if your institution is using the Banner Human Resources product.

Position Control Check box that indicates if your institution is using the Banner Position Control product.

Student Check box that indicates if your institution is using the Banner Student product.

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions



General Message Form (GUAMESG)

Use this form to send messages to and receive messages from other Banner users. You can also use this form to query messages. You must have appropriate security to use this form.

The Message can be up to 180 characters long. If the Message is about a person or organization in Banner, you can specify the ID in the Reference ID field. You can print the messages to your system account.

Note: The New Message dialog box will only appear once per Banner session, even if additional new messages are received during the session.

You can flag the status of the message:

If the Confidential check box is checked, only the sender and recipient can query on the message. If the check box is not checked, anyone can query on the message.

Broadcast Messages

You can send broadcast messages to all users. To send a broadcast message, create it on GUAMESG as usual, and use BASELINE as the recipient.

Whenever you receive a broadcast message:

• The Broadcast Message button on the toolbar will be enabled.

• The message will appear on the General Menu form (GUAGMNU) in the Broadcast Messages section.

Note: Only users assigned to the BROADCAST security object can send broadcast messages.

Complete You have read the message. A green check mark does not appear when you access a new form or return to the main menu.

Pending or Hold A green check mark appears next to the Check Banner Messages link when you initially log in and have pending messages, or whenever a new message arrives.

Pending is the default status when a message is created. The system processes both statuses the same way. You can determine your own criteria for defining each status. If you use each status for specific purposes, you can query on the status.



Personal Messages

A checked box icon appears in the My Links window next to the Check Banner Message link whenever you have a personal message.

Options Maintenance Form (GUAOPTM)

Use this form to define the options that appear in the Options menu for a specific form, and also on the menu bar. These options are used to navigate within Banner. When a user accesses the Options menu, he can use the mouse or arrow keys to choose the option, or enter the option’s shortcut character.

You can define internal options that call accessible windows and blocks within the current form.

You can also define external options that call forms and processes other than the current form. When a user selects an external option, the external form or process is called. When the user exits the called form or completes the process, the user is returned to the calling form.

Note: There is a 24-form limit for the Options menu.

A message on GUAOPTM tells you whether the option is baseline or local:

• BASELINE Option. SunGard Higher Education delivered the option. Before you change a baseline option, carefully consider the implications. If you change the option, you are committed to making the same change for all subsequent releases. The BASELINE user is the only user who can change a baseline option.

• LOCAL Option. Your institution added the option. Any user with the appropriate security can change a local option.

Main Window

Use this window to define the options that appear in the Options menu and in the Options menu on the menu bar. These options are used to navigate within Banner.

You can define both internal options and external options. Internal options call accessible windows and blocks within the current form. External options call forms and processes other than the current form.

Key Block

Use this block to identify the form for which you are defining navigation options.



Options Block

Use this block to:

• Define the text that appears in the Options menu.

• Identify the object (such as block, window, or form) that the option calls.

• (Optional) Identify a trigger that the option executes.

• (Optional) Change the default character that is used as the shortcut key for the option.

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions

Form Name Name and description of the form for which you are defining navigation options. Defined options will appear in the Options menu on this form.

Column: Not base table items (name and description)

Choices: Choices come from the Object Maintenance Form (GUAOBJS) list of values. This list of values includes all objects that have FORM as the object type.

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions

Description Text that appears in the Options menu for the option. This text describes the block, window, form, or process that the option calls.

By default, the shortcut character used for your option is the first character in the Description field. To make the shortcut another character from this field, enter an ampersand (&) directly before the character you want to use as the shortcut.

For example, with a description of Short Form, the default shortcut would be s. If you entered Short &Form instead, then the shortcut character would be f.

Note: Customized shortcut characters do not work for objects in the the Last 10 list in the File pull-down menu.

Tip: After you enter the description, you should view the results and verify that the text wraps correctly. You may need to manually add spaces to improve readability. Although the maximum data length is 100 characters, a short description is easier to read than a long one.

Column: GUROPTM_NAME1_DESC



Type Indicator Pull-down list that indicates the type of object that the option calls.

Column: GUROPTM_TYPE_IND

Choices are:

F = Form (default) - The option calls another form. The Select option in the File menu of the called form is enabled.

W = Window - The option calls a window within the current form.

B = Block - The option calls a block within the current form.

P = Trigger - The option executes a trigger and calls an object other than a form. The Select option in the File menu of the called object is disabled. The trigger name must be entered in the Trigger Name field.

L = Trigger Calling A Form - The option executes a trigger and calls a form. The Select option in the File menu of the called form is disabled. The trigger name must be entered in the Trigger Name field.

Note: If an option executes a trigger, this indicator must be set to P or L, depending on the type of object it calls.

Form Called Name of the form that the option calls. This is the seven- or eight-character form name (for example, GJAJOBS).

A user-level preference on the General User Preferences Maintenance Form (GUAUPRF) determines whether this form name is displayed with the option description in the Options menu. There are two choices for determining how form names are displayed:

• Form names can be completely omitted from the Options menu. (This is the way Banner is delivered.)

• Form names can appear after option descriptions in the Options menu.

Column: GUROPTM_FORM_TO_BE_CALLED

Called Object Name of the object (such as a block, window, or form) that the option calls. The option can call any accessible window or block within the current form or an external form or process.

Column: GUROPTM_NAME1

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions



Form Call Mode Pull-down list that indicates whether the form is called in maintenance mode or query mode. This field is used only if the option calls a form.

Note: This field cannot be updated for baseline options.

Column: GUROPTM_CAPACITY

Choices are:

Maintenance (default) - The called form can be updated. This value is stored in the database as M.

Query - The called form can be queried only (no updates). This value is stored in the database as Q.

Trigger Name Name of the trigger to be executed if the option executes a trigger. This field is used only if the Type Indicator is set to P (Trigger) or L (Trigger Calling A Form). The trigger can be built-in or user-defined.

Note: If an option executes a trigger, the Type Indicator must be set to P or L, depending on the type of object it calls. The trigger name must be entered in this field.

Column: GUROPTM_TRG_NAME

Block Block in which the option is available.

Enter a block name in this field if the option is supposed to appear in the Options menu only when the cursor is in a specific block. Leave this field blank if the option is available in all blocks on the form.

Column: GUROPTM_BLOCK_VALID

Choices: Choices come from a list of the block names in the form.

Trigger Call Mode

Pull-down list that indicates whether the trigger in the Trigger Name is built-in or user-defined.

Column: GUROPTM_TRG_TYPE

Choices are:

Built-in (default) - The trigger is built-in. A DO_KEY will execute the trigger. This value is stored in the database as B.

User Defined - The trigger is user-defined. An EXECUTE_TRIGGER will execute the trigger. This value is stored in the database as U.

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions



Procedures

To create an option that calls a form:

Use these steps to create an option that calls a form without executing a trigger.

1. Access the Options Maintenance Form (GUAOPTM).

2. Enter the Form Name. This is the form for which you are creating a new option.


Navigate to Item Specific item to which the option navigates. This field is used only if the option calls a window or block, and only if the option navigates to a specific item in the block or window. The recommended format is block.item (for example, PRNT_CTRL.DISPLAY_PRNT_CODE).

Column: GUROPTM_NAME2

Sequence Number

Sequence number that determines the order in which options are displayed in the Options menu. Decimals are allowed, in case you need to insert an option between existing options (for example, 1, 1.2, 1.4, and 2).

Column: GUROPTM_SORT_SEQ

Tab Security Form

Name of a tabbed form that will be the destination of the option menu item.

Note: A value in this field is necessary only when the tab form’s name is different from the form on which the option exists. That is to say, the option is used for external navigation (navigation to a tab in a different form than that which is indicated in the key_block of this form). If the field is null, the option is used for internal navigation (navigation to a tab within the form that is indicated in the key_block of this form).

Internal Tab Name

The tab name, as referenced internally by the Banner system (as defined by Oracle Forms Developer), of the tab to navigate to.

External Tab Name

The tab name that displays on the Banner form. (This field is display only.)

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions



4. Select Insert Record.


6. Select F = Form from the Type Indicator pull-down list.

7. Enter the Form Called. This is the form name that optionally appears with the description in the Options menu.

8. Enter the Called Object. This is the form that the option will call.

9. Verify the Form Call Mode. Change if necessary.

10. (Optional) If the option is valid only when the cursor is in a specific block, enter the Block name.

11. Enter the Sequence Number.

12. Save.

To create an option that calls a window or block:

Use these steps to create an option that calls a window or block without executing a trigger.






6. To create an option for a window, select W = Window from the Type Indicator pull-down list.

OR

To create an option for a block, select B = Block from the Type Indicator pull-down list.

7. Enter the Called Object. This is the window or block that the new option will call.


9. (Optional) If the cursor should navigate to a specific field in the window or block, enter the item name in the Navigate to Item field.




11. Save.

To create an option that executes a trigger






6. To create an option that executes a trigger and calls a form, select L = Trigger Calling A Form from the Type Indicator pull-down list.

OR

To create an option that executes a trigger and calls an object other than a form, select P = Trigger from the Type Indicator pull-down list.

7. Enter the Called Object. This is the object that the new option will call.

8. If the option calls a form, verify the Form Call Mode. Change if necessary.

9. Enter the Trigger Name.

10. Verify the Trigger Call Mode. Change if necessary.


12. (Optional) If the cursor should navigate to a specific field in the window or block, enter the item name in the Navigate to Item field.


14. Save.

Enterprise PIN Preferences Form (GUAPPRF)

Use this form to specify your institutional preferences for handling PINs.

PIN Preferences Block

Use this block to specify the following preferences for your institution:



• Format of reset PINs (alphanumeric or numeric)

• Value of reset PINs (birthdates or random values)

• Whether PINs are pre-expired

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions

PIN Reset Format

Pull-down list that indicates whether reset PINs can be alphanumeric or must be numeric. This setting applies to PINs that are reset by users on the Change PIN page accessed from Banner Self-Service, by users who answer a security question during login to a self-service application, and by administrative users on the Third Party Access Form (GOATPAD). Numeric is the default.

If your institution generates alphanumeric PINs and at a later date changes this setting to numeric PINs, the system checks all existing PINs. If any alphanumeric PINs are found, an error message is displayed. You must manually change all alphanumeric PINs before you can change this setting from Alphanumeric to Numeric. Alphanumeric PINs provide greater security.

Note: If you select Alphanumeric in this field, and also choose Random Value for the PIN Reset Value field, then PINs will be in all UPPERCASE.

Note: Voice Response requires numeric PINs. If your institution uses the VR product, you must select Numeric.

Required.

PIN Reset Value Pull-down list that indicates whether PINs are reset to users’ birthdates or random values.

Birthdate PINs are reset to birthdates. If there is no birthdate, a PIN is reset to the last six digits of the user’s Banner ID. This is the default value.

Random Value PINs are reset to random values. A value is numeric or alphanumeric, depending on the value of the PIN Reset Format field.

Note: If you choose Random Value for this field, and select Alphanumeric for the PIN Reset Format field, then PINs will be in all UPPERCASE.

Required.



Pre-Expire New PIN

Pull-down list that indicates whether PINs are pre-expired when they are created the first time via the PIN Mass Create process or the Table PIN Create Controls.

Yes The PIN record is created with an expiration date one day before the system date.

No The PIN record is created without an expiration date.

Letter Generation Application Name

Letter Generation application associated with the letter and/or e-mail that is sent to users when their PINs are reset. Optional.

This field must have a value if Hard-copy Letter Generation Code or E-mail Letter Generation Code has a value.

If this field has a value, Hard-copy Letter Generation Code or E-mail Letter Generation Code must have a value.

(lookup) Application Inquiry (GLBAPPL) list of values

Hard-copy Letter Generation Code

Letter code that identifies the hardcopy letter sent to users when PINs are reset. This code is used to create a GURMAIL record when a person’s PIN is reset. Optional.

This field can have a value only if the Letter Generation Application Name field has a value.

(lookup) Letter Code Validation (GTVLETR) list of values

E-mail Letter Generation Code

Letter code that identifies the e-mail sent to users when PINs are reset. When a person’s PIN is reset, this code is used to insert a record into a table that interfaces with your institution’s e-mail system. Optional.



When user changes PIN

Pull-down list that determines what notifications (e-mail, hardcopy letter, both e-mail and letter, or neither) are sent when users reset their own PINs via the Web. Required.

When Admin/Process changes PIN

Pull-down list that determines what kind of notifications (e-mail, hardcopy letter, both e-mail and letter, or neither) are sent when an administrator or system process changes user PINs. Required.

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions



Table PIN Creation Controls BlockUse this block to establish a PIN, for the first time, when specific Banner forms create specific Banner tables.

System Identification Form (GUASYST)

Use this form to identify the Banner systems that contain information about an ID. Each system is also broken down into key modules, such as Recruiting or Admissions in the Student System. This helps to further define the information being stored and maintained about the ID in Banner.

GUASYST provides a quick overview of information about an ID as it exists in the Banner database, enabling you to see, for example, certain correlations of an individual's activity. However, the information displayed here is not distinguishable by date, term, or other time frame. The form is simply a quick-reference to systems where further information about an ID may be stored.

Each module is associated with one or more database tables:

User ID User who created or last updated the preferences. Display-only.

Activity Date Date the preferences were created or last updated. Display-only.

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions

Table Name Table that directs whether a PIN is generated, if one does not yet exist. Table names are provided by SunGard Higher Education and cannot be changed.

Create PIN? Code that indicates whether a new PIN is inserted when the associated table is created. Required.

Y When the table is created, the process verifies whether a PIN exists. If a PIN does not exist, the process creates a PIN.

N When the table is created, the process does not verify whether a PIN exists.

Activity Date Date the table preferences were created or last updated. Display-only.

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions



SSN/SIN/TFN Alternate ID Search Form (GUIALTI)

The SSN/SIN Alternate ID Search Form (GUIALTI) provides a way for you to find the Banner ID of a person or organization when you know one of the following items, or a portion of it:

System Module Database Table

Student Recruiting SRBRECRAdmissions SARADAPTransfer Work SHRTRAMGeneral Student SGBSTDNRegistration SFBETRMHousing SLBRMAPFaculty SIBINST

Human Resources Applicant PABAPPLEmployee PEBEMPLBeneficiary PDRBENECobra Person PCBPERS

Advancement Constituent APBCONSOrganization AOBORGN

Financial Aid Applicant RORSTAT

Finance Agency FTVAGCYBank FTVBANKCustomer FTVCUSTEmployee FCBEMPLFinancial Manager FTVFMGRVendor FTVVEND

Accounts Receivable A/R TBRACCDTBRDEPOTBRMEMTBBCPRF

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions

Category (ID) Displays the Category code associated with the ID. Display-only.

Class (ID) Displays the Class code associated with the ID. Display-only.

Category (Organization)

Displays the Category code associated with the organization. Display-only.



• SSN (United States)

• SIN (Canada)

• TFN (organizations)

• Name

• Date of Birth

You can query on all fields. By choosing the appropriate button at the bottom of the form, you can make your queries case-sensitive or not. When you have found the right person or organization, you can return the Banner ID information to the calling form.

Warning: This form will display information for those who have the Confidential indicator selected on their records. Please make sure you give access to this form only to those who have the authority to view confidential information.

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions

SSN/SIN/TIN The Social Security Number (United States), Social Insurance Number (Canada) or Tax Information Number (organizations). Optional.

ID The 9-digit Banner ID. Optional.

Entity Indicates if the record pertains to a person or an organization. Valid values are:

P The record belongs to a person

C The record belongs to an organization

Display-only.

Last Name The last name of the person with the displayed Banner ID, or the organization’s name. Optional.

First Name The first name of the person with the displayed Banner ID. Optional.

Middle Name The middle name of the person with the displayed Banner ID. Optional.

Birthdate The date of birth of the person with the displayed Banner ID. Optional.



Note: This form does not allow you to create a new Banner ID. Information about the person must exist in Banner before it can appear on this form.

This form has Banner application-level security.

Users can call GUIALTI directly from the following General forms:



• Function Participant Form (GEAPART)


• Population Selection Extract Data Form (GLAEXTR)

• Web User Directory Profile Form (GOADPRF)

• Enterprise Access Control Form (GOAEACC)

• E-mail Address Form (GOAEMAL)

• Geographic Regions/Divisions by ID Form (GOAPGEO)

• Third Party Access Form (GOATPAC)

• Third Party Audit Form (GOATPAD)

• Survey Response Query Form (GOISRVY)

• System Identification Form (GUASYST)

• Mail Query Form (GUIMAIL)

• Direct Deposit Recipient Form (GXADIRD)

• EDI Trading Partner Identification Form (GXATPID)

Note: To see the forms in other Banner products that call GUIALTI, refer to the product-specific documentation.

SSN/SIN/TFN History Form(GUITINH)

Your institution may receive information about a person or non-person that lists a different Social Security Number (SSN), Social Insurance Number (SIN), or Tax Filing Number (TFN) than the one on record in Banner. You need a way to find out

Change The indicator that specifies how the information was last changed. Valid values are:

blank No changes.

N The name for the Banner ID has been changed.

I The Banner ID for the name has been changed.

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions



which identification number is the correct one and determine if the other number exists in Banner.

The SSN/SIN/TFN History Form (GUITINH) allows you to search for these numbers and view changes made to them. It displays information for persons and for non-persons. You cannot update identification number information using this form.

Note: The form stores changes to all identification numbers that cause an update to the SPBPERS_SSN field.

You can search on this form to find the current identification number if you know either:

• The Banner ID

• The identification number

Note: The person or non-person must already exist in Banner to appear on this form.

Note: This form will display information for those who have the Confidential indicator selected on their records. Be sure you give access to this form only to those who have the authority to view confidential information.

Key Block

The key block contains the two fields you can use to query for a person’s or non-person’s identification history. You must enter information into one or the other.

Banner checks SPBPERS_SSN and GURHLOG_PREVIOUS_VALUE to see if the identification number exists anywhere in the system.

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions

ID The Banner ID for which you would like to see identification number history. It is the 9-digit Banner ID on SPRIDEN. Select the flashlight button to search for an ID:



(button) Duplicate Item SSN/SIN/TIN Alternate ID Search Form (GUIALTI)

Optional.



Entity Selection Block

The Entity Selection block contains the current identification number. The fields it contains are all display-only.

Note: If the identification number was never changed, the value in SPBPERS_SSN will be displayed in the Entity Selection Block. GURHLOG_PREVIOUS_VALUE will be empty and no identification numbers will be displayed in the Historical Data Block.

(Untitled) The name of the person or non-person. This is automatically populated from information stored in SPRIDEN, and is a combination of the last name, first name, and middle initial. You can navigate to the ID and perform an extended name search by entering a full or partial name into this field. Display-only.

SSN/SIN/TIN The identification number for which you would like to see identification number history. It is the 9-digit number from SPBPERS_SSN (if no changes have been made to the identification number) or GURHLOG_PREVIOUS_VALUE (if the identification number was changed). Optional.

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions

ID The Banner ID. Optional.

Entity Identifies whether the ID is a person or a non-person. Valid values are:

P - PersonC - Non-person

Optional.

Name The name of the person or non-person. It is the concatenation of the last name, first name and middle initial from SPRIDEN. Optional.

Current SSN/SIN/TIN

The current SSN, SIN, or TIN for that ID. Optional.

Birth Date The date of birth for the ID. Optional.

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions



If the identification number has been changed, the value in GURHLOG_PREVIOUS_VALUE will be displayed in the Historical Data Block and the current value in SPBPERS_SSN will be displayed in the Entity Selection Block.

Historical Data Block

This block contains details about the identification number history for the Banner ID highlighted in the Entity Selection Block. It is sorted by the date listed in Date Changed, and all its fields are display-only. It contains the following fields:

Security

This form has the standard Banner object-level security. Banner General application-level security has been used.

Note: This form could display information that is considered confidential by certain individuals or institutions. When granting access to this form, please consult your site-specific policies for protecting confidential information.

This form will show the identification numbers of persons or non-persons that the Confidential indicator selected for their records.

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions

SSN/SIN/TIN Changed From

The previous SSN, SIN, or TIN. Optional.

SSN/SIN/TIN Changed To

The new SSN, SIN, or TIN. Optional.

Changed By The Banner user ID for the person that changed the SSN, SIN, or TIN. Optional.

Date Changed The date the identification number was changed. Optional.

Time Changed The time of day that the information number was changed. Optional.



Immunization Information Form (GOAIMMU)

Use this form to maintain immunization status information for an ID.

Note: Immunization codes must be set up on the Immunization Code Validation Form (GTVIMMU), and immunization status codes must be set up on the Immunization Status Code Validation Form (GTVIMST) prior to using them on this form.

Banner Message Aware Entity Rules Form (GURMESG)

Messaging allows clients to develop real-time data messaging functionality to synchronize data across the corresponding applications on their network. Clients can either plan and manage API-to-API development projects, or they can invest in one or more of the products comprising the Luminis Data Integration Suite, a data-messaging solution for higher education which employs an enterprise application integration (EAI) system.

Banner Messaging Support provides APIs that are used by the Banner Common Business API to make a Banner Business Entity message-enabled. If a Business Entity is

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions

ID ID and name for which you want to view or record immunization status information.

Immunization Immunization code and description. Choices come from the Immunization Code Validation Table.

Status Immunization status code and description. Choices come from the Immunization Status Validation Table.

Immunization Date

Date of immunization.



Comment Comment about the immunization. Comments can be up to 4,000 characters in length (including spaces). Click the Edit button to edit an existing comment, or simply to view the comment in a new window.



message-enabled, the data associated with it can be associated with one or more Enterprise Messages.

Banner Messaging Support provides a loosely - coupled architecture that insulates Banner from knowing what Business Entities are associated with which Enterprise Messages.

This form lists the business entities that are currently defined, and indicates if they are messaging-aware.

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions

Entity Name Specifies the name of the Business Entity.

Column: GURMESG_ENTITY_NAME

Source Specifies if the Business Entity is delivered or if it is custom. Valid values are:

(B)aseline, indicates that the entity was delivered by SunGard Higher Education

(L)ocal, indicates that the entity is a custom entity

Column: GURMESG_SOURCE_IND

Enabled Indicator

Indicates that the entity is messaging-aware. Valid values are:

Selected - Y, the entity is messaging-aware

Cleared - any other value, including null, the entity is not messaging-aware

Column: GURMESG_ENABLED_IND

VPD Indicator Specifies if the business entity is using the Oracle Virtual Private Database (VPD) feature. Valid values are:

Selected - the entity is using VPD and the Banner Business Entities data will be associated with the institution code set up on the Oracle/Banner VPD Security Maintenance Form (GSAVPDI)Cleared - the entity is not using VPD, so the Banner Business Entities data will be shared with all institution codes.

This indicator allows you to segregate messages by campus code. The campus that will receive the message is determined by the messaging code.

Base Table Displays the name of the base table.

Package Name Displays the package name.



Procedures

To implement Banner Messaging for e-Procurement

Note: To successfully implement Banner Messaging for e-Procurement, the following software must be installed, configured, and running on the messaging host platforms:

• Luminis Data Integration (LDI)

• LDI for e-Procurement

1. Log in to Banner with the BASELINE user ID.

2. Access the General User Preferences Maintenance Form (GUAUPRF). Select Directory Options.

Scroll down until you see the description Enter the name of the Messaging URL #001.

3. Change the URL to reference the primary Banner Gateway Producer application, e.g:

rmi://messaginghost1.university.edu:1099/BannerMessagingService

4. Find the description Enter the name of the Messaging URL #002. Change the URL to reference the secondary Banner Gateway Producer application, such as:

rmi://messaginghost2.university.edu:1099/BannerMessagingService

The URLs support automatic failover: if Banner Messaging support cannot communicate with the primary Gateway Producer for some reason, it will automatically use the secondary one. If it cannot communicate with the secondary Gateway Producer, Banner Messaging will send an error message to the user.

5. When you are finished, save your changes.

User ID Banner ID of the person who created or last changed the record. Display-only.

Column: GURMESG_USER_ID

Activity Date Date the record was created or last changed. Display-only.

Column: GURMESG_ACTIVITY_DATE

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions



Technical Note:

The Banner Gateway Producer application is responsible for generating and publishing Enterprise synchronization messages depending on the changes made to Banner Business Entities.

6. Access the Banner Messaging Aware Entity Rules Form (GURMESG). It controls whether a Business Entity is messaging-aware or not.

Make sure the Enabled Indicator check box is selected for the following:

• ACCOUNTING_ELEMENT

• ADDRESS

• CHART_OF_ACCOUNTS

• COMMODITY

• IDENTIFICATION

• PURCHASE_ORDER_ACCOUNTING

• PURCHASE_ORDER_HEADER

• PURCHASE_ORDER_ITEM

• PURCHASE_REQUISITION_ACCOUNTING

• PURCHASE_REQUISITION_HEADER

• PURCHASE_REQUISITION_ITEM

• SHIP_TO_LOCATION

• TELEPHONE

• VENDOR

• VENDOR_TYPE

These are the Banner Business Entities that are required to support e-Procurement.

Note: In the future, you may have custom Business Entities. If so, they will have the Source (L)ocal instead of (B)aseline.

7. When you are finished, save your changes.

Now Banner Messaging support will track any changes to these entities as programs call the entities' APIs. During a database commit, any changes will be sent to the Banner Gateway Producer application where Enterprise synchronization messages will be generated and published for each Enterprise message which is associated with the entity.

Because of this synchronization, your institution can manage its information more efficiently and your data administration will be easier.

Technical Note:

These records are stored in the GENERAL.GURMESG table. Each row defines the Business Entity name, the Source indicator, and the Enabled indicator.



8. Next you must enable messaging for your entire Banner system. Access the Installation Controls Form (GUAINST).

9. Select the Messaging Enabled check box and save your changes.

This allows Banner Messaging Support to send business entity changes to the Banner Gateway Producer application. Banner will begin producing Enterprise synchronization messages for the Banner Business Entities that you have defined as messaging-aware.

Technical Note

These records are stored in the GENERAL.GUBISNT table. If the column GUBINST_MESSAGE_ENABLED_IND contains Y, messaging is enabled for the entire Banner system. If it contains any other value, including null, messaging is disabled for your system.

Note: The values stored in the GUBINST table override the settings on GURMESG. Clearing the Messaging Enabled check box on GUAINST is a quick way to completely turn off messaging in Banner.

Banner Messaging Support will only contact the Banner Gateway Producer if you select the Messaging Enabled check box on the GUAINST form and the Enabled Indicator check box for the individual entities on the GURMESG form (see Step 3). Both conditions must be met for messaging to work.

10. Test the connectivity between your Banner system and the Banner Gateway Producer.

The following will produce a HelloWorld-Create-Sync message:

(a) Execute the Oracle SQLPlus application and log in with the BANINST1 user ID.

Column Name Description

GURMESG_ENTITY_NAME Specifies the name of the Business Entity.GURMESG_SOURCE_IND Specifies if the Business Entity is delivered or custom.

Valid values are:B - Baseline, indicating that it was delivered by SunGard Higher EducationL - Local, indicates a custom entity

GURMESG_ENABLED_IND Indicates that the entity is messaging-aware. Valid values are:Selected - Y, the entity is messaging-awareCleared - any other value, including null, the entity is

not messaging-awareGURMESG_USER_ID The user ID of the person who created or last

updated the record.GURMESG_ACTIVITY_DATE The date the record was created or last updated.



(b) Execute the following statements:

set serverout on;call dbms_java.set_output(20000);begingb_messaging.p_register_entity('$CREATE_HELLO_WORLD',gb_messaging.CREATE_OPERATION);gb_messaging.p_add_parameter('$MESSAGE', 'Hello Banner World');gb_messaging.p_publish;end;/

The SQLPlus application should display PL/SQL procedure successfully completed if no errors were encountered. If any errors are encountered they will appear in the SQLPlus application window.

Direct Access Form (GUAPARM)

Use this form to directly access forms, jobs, menus, and QuickFlows by name. You can access this form from the File pull-down menu.

Calendar Form (GUACALN)

Use this form to display a calendar. You can access this form by double-clicking any date field on a form. If the date field has a value, the calendar highlights that date. If the date field is empty, the calendar highlights the current date. You can double-click a date on the calendar to return it to the calling form.

You an also access this form with a button on the Banner tool bar or with Direct Access. When accessed this way, the calendar works independently of any form or field. You cannot select a date and return it to a form.



Calculator Form (GUACALC)

Use this form to display a calculator. You can access this form by double-clicking any numeric field on a form. If the numeric field has a value, the calculator shows that value.

You can use the mouse, number keys on the keyboard, or the numeric keypad (if the NumLock is enabled) to make calculations. When you’re done, click the OK button to return the calculated value to the calling form.

You can also access this form with a button on the Banner tool bar or with Direct Access. When accessed this way, the calculator works independently of any form or field. You cannot return a calculation to a form.

About Banner Form (GUAABOT)

This form can be accessed from the Help pull-down menu or with Direct Access. It displays the following information:

• The name and release number of the form from which GUAABOT was called

• The modification ID, if one exists

• The date and time

• Your user ID

• Your session ID

• The different applications (Student, Advancement, Human Resources, etc.) that are installed and their version numbers

• Legal statements and copyright information

Procedures

How to set up a modification ID

A number of institutions prefer to customize Banner forms. However, this may make it difficult to know if the form being displayed is the SunGard Higher Education-delivered version or the custom version.

Banner can display a modification ID number in brackets on the title bar of the form and on GUAABOT. This enhancement does not perform version control of any kind; it merely identifies the form as being custom.

To enable this feature for your custom forms:



1. Access the General User Preferences Maintenance Form (GUAUPRF).

2. Select the Display Release Number on Title Bar check box, if it has not been selected already.


Note: The modification number will not appear on the title bars if you clear the check box on GUAUPRF. However, it will still appear on GUAABOT.

4. In the form in which you want to enable this feature:

(a) Add a text_item to the FORM_HEADER block.

(b) Name this text_item MOD_ID.

(c) Set the Enabled Property of MOD_ID to No.

(d) Set the Max Length to 16.

(e) Provide a value from 1 to 16 alphanumeric characters for the FORM_HEADER.MOD_ID in the form-level trigger LOAD_CURRENT_RELEASE.


The value you entered will appear in the title bar of that form and on GUAABOT.

General Menu Form (GUAGMNU)

The General Menu Form is your initial contact with Banner. From this form, you can navigate to forms by browsing through menus or by entering the seven-character name in the Go To field.

The Broadcast Messages section displays links to system-wide messages at your institution.

The Site Map link displays a high-level view of all Banner products installed at your site as well as the modules that comprise those products.

Banner Error and Warning Messages Form (GUAERRM)

This form is a modal window, and it displays any error messages that are passed from an API to a form. Error messages are generated if, for example, a record fails to include required information or contains an invalid code upon committing a transaction.



This form is launched by new triggers that have been added to goqrpls.pll to support the use of APIs. The triggers are ON-INSERT, ON-DELETE, and ON-UPDATE.

An exception handler within the triggers:

1. Calls GUAERRM.

2. Calls gb_common.p_rollback to roll back the transaction and discard the pending messages.

3. Displays the error messages.

This form appears as a window in a form, and is display-only. It can display messages up to 4,000 characters in length. Longer messages are truncated.

Note: This form is not accessible through any Banner menus. It only appears when an API error occurs.

Personal Image Form (GUAIMGE)

This form displays the stored ID image of a person. When your cursor is in the User ID field of selected forms, you can select Help>Display ID Image, and this form will display the image, if one is available.

Site administrators can refer to the Middle Tier Implementation Guide for information about setting up personal images in Banner.

VPDI Included Objects Form (GORVPDI)

Use this form to list the forms that are enabled for MIF at your institution. When a form is added to this list, then both the home and process contexts appear in the title bar of the form.

If you add a form that has had VPD changes applied to it, then the MIF toolbar button becomes active and users can access the Institution Code Validation list of values (LOV) from that form. For forms that have not had VPD applied to them, the button is not active.

Note: Do not add forms that do not re-query data and use the Rollback function. If the data cannot be re-queried, then the user should not be changing Institution Codes while on that form.

This form appears on the Miscellaneous General Forms Menu (*GENMISC).



Set Institution Form (GUQSETI)

This form enables you to switch between Institution Codes, if your institution uses Multi-Institution Functionality (MIF). Refer to the Processing chapter for information about switching between Institution Codes.

Note: MIF is only available at schools that have implemented Virtual Private Database (VPD) functionality. If your institution is interested in using MIF, it is strongly recommended that SunGard Higher Education Application Practices perform the implementation. Do not attempt to make VPD changes to the database on your own.

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions

Object Name Name of the Banner object. Choices come from the Object Maintenance Form (GUAOBJS) list.

Description Description of the Banner object. This value comes from the description associated with the object on GUAOBJS.


User ID User ID that created or modified the record.

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions

Code Institution Code.

Description Description of the Institution Code.



General WebUtil File Extract Form (GUQWUTL)

This form appears when you select the option to extract data in a WebUtil-enabled Banner session. It displays a message about whether the data were extracted successfully, and enables you to save the output to a file on your local machine by using the Save File button.

Note: If your system administrator has not configured WebUtil at your institution, and you change the GUAUPRF record for Data Extract Format to WEBUTIL, then you will receive an error if you try to extract data to a file using GUQWUTL.

Note: There is a known issue when saving the file on a Macintosh workstation. The file does not target the local directory (and subdirectory, if specified), when given proper syntax. The file does transfer properly and completely; however, the file transfers to the top-level directory of the Macintosh hard drive, and has a somewhat cryptic file name. The user may need to manually rename and move the file on the Macintosh workstation.


Chapter 9

Event Management

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-3

9 Event ManagementValidation Forms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-3


Forms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-10

Event Form . . . . . . . . . . . . . . . . . . . . . . . . . . . (SLAEVNT) . . . . . . 9-11Event Function Form . . . . . . . . . . . . . . . . . . . . . . (GEAFUNC) . . . . . 9-19Function Task Form . . . . . . . . . . . . . . . . . . . . . . . (GEATASK) . . . . . . 9-36Function Participant Form . . . . . . . . . . . . . . . . . . . (GEAPART). . . . . . 9-48Function Comment Form . . . . . . . . . . . . . . . . . . . . (GEAFCOM) . . . . . 9-57Event Registration Form . . . . . . . . . . . . . . . . . . . . . (GEAATID) . . . . . . 9-65Attendance Form . . . . . . . . . . . . . . . . . . . . . . . . (GEAATTD) . . . . . 9-83Building Definition Form . . . . . . . . . . . . . . . . . . . . (SLABLDG). . . . . . 9-97Room Definition Form . . . . . . . . . . . . . . . . . . . . . (SLARDEF) . . . . . . 9-105Function Attendance Inquiry Form . . . . . . . . . . . . . . . (GEIATTD) . . . . . . 9-118Event Function Inquiry Form . . . . . . . . . . . . . . . . . . (GEIFUNC). . . . . . 9-126Individual Function Inquiry Form . . . . . . . . . . . . . . . . (GEIIDFN) . . . . . . 9-130Function Subject Index Query Form . . . . . . . . . . . . . . (GEISUBJ) . . . . . . 9-142Building Query Form . . . . . . . . . . . . . . . . . . . . . . (SLABQRY). . . . . . 9-144Building/Room Schedule Form . . . . . . . . . . . . . . . . . (SSAMATX). . . . . . 9-146

Forms Used by the Banner Advancement System . . . . . . . . . . . . . . . . . . . 9-156

9-1

Table of Contents



9 Event Management

Overview

9 Event The Banner Event Management module helps you manage an event and the functions, tasks, and participants associated with the event. You can perform these kinds of activities:

• Schedule dates and date ranges, times, buildings, and rooms.

• Organize administrative tasks associated with functions.

• Determine financial requirements, including fee and rate structures, budgets, costs, anticipated income, and actual income.

• Arrange for speakers, entertainment, ticketing, invitations, and mailings.

• Track anticipated attendance and actual attendance.

Keeping track of this information not only helps you manage the current event, but provides information that can be used to plan future events.

Event Management

Validation Forms

Event Management forms use the following validation forms. Refer to Chapter 2, Validation Forms, for additional information.


GTVDICD District Division Code Validation Form

SLAEVNTSTVCAMP

Event FormCampus Code Validation Form

GTVEMPH Emphasis Code Validation Form GEAFUNC Event Function Form

GTVEXPN Expense Code Validation Form GEAFUNC Event Function Form

GTVFEES Fee Status Code Validation Form GEAATIDGEAATTD

Event Registration FormAttendance Form

GTVFSTA Function Status Code Validation Form

GEAFUNC Event Function Form

GTVFTYP Fee Type Code Validation Form GEAFUNC Event Function Form

GTVFUNC Function Code Validation Form GEAFUNCSLAEVNTSSAMATX

Event Function FormEvent FormBuilding/Room Schedule Form

GTVLETR Letter Code Validation Form GEAFUNC Event Function Form

GTVMAIL Mail Code Validation Form GEAFUNC Event Function Form


9 Event Management

GTVMENU Menu Code Validation Form GEAATIDGEAATTDGEAFUNC

Event Registration FormAttendance FormEvent Function Form

GTVPTYP Participant Type Code Validation Form

GEAPART Function Participant Form

GTVPURP Purpose Code Validation Form GEAFUNC Event Function Form

GTVRATE Fee Rate Code Validation Form GEAFUNC Event Function Form

GTVREVN Revenue Code Validation Form GEAFUNC Event Function Form

GTVRSVP RSVP Code Validation Form GEAATIDGEAATTD

Event Registration FormAttendance Form

GTVRTNG Rating Code Validation Form GEAPART Function Participant Form

GTVSUBJ Subject Index Validation Form GEAFCOM Function Comment Form

GTVSYSI System Indicator Validation Form SLAEVNT Event Form

GTVTARG Target Audience Code Validation Form

GEAFUNC Event Function Form

GTVTASK Task Code Validation Form GEATASK Function Task Form

GTVTSTA Task Status Code Validation Form GEATASK Function Task Form

GTVTTYP Task Type Code Validation Form GEATASKGTVTASK

Function Task FormTask Code Validation Form

GTVZIPC ZIP/Postal Code Validation Form SLABLDGSTVSITE

Building Definition FormSite Code Validation Form

STVBLDG Building Code Validation Form SLABLDG Building Definition Form

STVCAMP Campus Code Validation Form GTVPARS

SLABLDGSLAEVNT

Scheduling Partition Validation FormBuilding Definition FormEvent Form

STVCNTY County Code Validation Form SLABLDGGTVZIPC

Building Definition FormZIP/Postal Code Validation Form

STVCOLL College Code Validation Form GTVEMPHSLABLDGSLAEVNTSLARDEF

Emphasis Code Validation FormBuilding Definition FormEvent FormRoom Definition Form



9 Event Management


Forms in the Event Management module can be accessed from the following menus:

• Event/Function Processing Menu (*GENEVPROC)

• Event/Function Inquiry Menu (*GENEVQRY)

• Event/Function Control Menu (*GENEVCONT)

Descriptions of the forms in the third menu, *GENEVCONT, appear in Chapter 2, Validation Forms, in this manual.

STVDEPT Department Code Validation Form GTVEMPHSLABLDGSLAEVNTSLARDEF

Emphasis Code Validation FormBuilding Definition FormEvent FormRoom Definition Form

STVETYP Event/Function Type Code Validation Form

GEAFUNCGTVFUNCSLAEVNT

Event Function FormFunction Code Validation FormEvent Form

STVNATN Nation Code Validation Form STVSITEGTVZIPC

Site Code Validation FormZIP/Postal Code Validation Form

STVPRCD Phone Rate Code Validation Form SLABLDGSLARDEF

Building Definition FormRoom Definition Form

STVRDEF Building/Room Attribute Code Validation Form

SLABLDGSLARDEF


STVRMST Room Status Code Validation Form SLARDEF Room Definition Form

STVRRCD Room Rate Code Validation Form SLABLDGSLARDEF


STVSITE Site Code Validation Form SLABLDGSLAEVNT

Building Definition FormEvent Form

STVSTAT State/Province Code Validation Form

SLABLDGSTVSITEGTVZIPC

Building Definition FormSite Code Validation FormZIP/Postal Code Validation Form

STVTERM Term Code Validation Form SLARDEF Room Definition Form



9 Event Management

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Event /Function Processing Menu (*GENEVPROC)

SLAEVNT Event FormDefines the various events that your institution offers or sponsors.

GEAFUNC Event Function FormDefines the functions associated with an event.

GEATASK Function Task FormDefines the tasks associated with a function.

GEAPART Function Participant FormDefines the participants associated with a function.

GEAFCOM Function Comment FormAllows you to enter freeform comments for a function and associate keywords or subject indexes with the comments.

GEAATID Event Registration FormCreates and maintains attendance information by ID.

GEAATTD Attendance FormCreates and maintains attendance information by function.

SLABLDG Building Definition FormDescribes the buildings at your institution.

SLARDEF Room Definition FormDescribes the rooms within a building.

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Event /Function Inquiry Menu (*GENEVQRY)

GEIATTD Function Attendance Inquiry FormDisplays information about invitees and their guests.

GEIFUNC Event Function Inquiry FormDisplays information about all the functions associated with an event.

GEIIDFN Individual Function Inquiry FormDisplays information about all events and their functions that an ID has attended or in which the ID has participated.

GEISUBJ Function Subject Index Query FormDisplays all subject index codes associated with comments for a function.

SLABQRY Building Query FormSelects a subset of the buildings at your institution based on a set of criteria.


9 Event Management

SSAMATX Building Room Schedule FormDisplays information for all scheduled buildings and rooms at your institution.

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Event /Function Control Menu (*GENEVCONT)

*GENEVVAL1 Validation Forms (STV)Provides access to the forms that build, maintain, and display the Student System validation tables used by the Event Management module.

*GENEVVAL2 Validation Forms (GTVEMPH - GTVPURP)Provides access to the forms that build, maintain, and display the General System validation tables used by the Event Management module (GTVEMPH through GTVPURP).

*GENEVVAL3 Validation Forms (GTVRATE - GTVZIPC)Provides access to the forms that build, maintain, and display the General System validation tables used by the Event Management module (GTVRATE through GTVZIPC).

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Validation Forms (STV) Menu (*GENEVVAL1)

STVBLDG Building Code Validation FormDefines codes for the buildings and facilities associated with events and functions.

STVCAMP Campus Code Validation FormDefines codes for the campuses associated with buildings and events.

STVCNTY County Code Validation FormDefines codes for the counties associated with buildings.

STVCOLL College Code Validation FormDefines codes for the schools and colleges associated with buildings and events.

STVDEPT Department Code Validation FormDefines codes for the departments and other organizational subdivisions associated with buildings, rooms, and events.

STVETYP Event/Function Type Code Validation FormDefines type codes associated with events and functions.

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Event /Function Inquiry Menu (*GENEVQRY)


9 Event Management

STVPRCD Phone Rate Code Validation FormDefines codes for the different kinds of telephone service associated with rooms and buildings and the billing frequency for each service.

Note: The Banner Student System also uses codes defined here in Housing and Location Management processing. If the Banner Student System is not installed, these values are for information only.

STVRDEF Building/Room Attribute Code Validation FormDefines codes for the attributes or features associated with buildings and rooms.

STVRMST Room Status Code Validation FormDefines status codes associated with rooms.

STVRRCD Room Rate Code Validation FormDefines codes for the different kinds of rates associated with rooms and buildings and the billing frequency for each rate.

Note: The Banner Student System also uses codes defined here in Housing and Location Management processing. If the Banner Student System is not installed, these values are for information only.

STVSITE Site Code Validation FormDefines codes for sites and addresses associated with buildings and events.

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Validation Forms (GTVEMPH - GTVPURP) Menu (*GENEVVAL2)

GTVEMPH Emphasis Code Validation FormDefines codes that identify the emphasis of functions.

GTVEXPN Expense Code Validation FormDefines codes for expenses associated with functions.

GTVFEES Fee Status Code Validation FormDefines codes for the payment status of fees associated with functions.

GTVFSTA Function Status Code Validation FormDefines status codes associated with functions.

GTVFTYP Fee Type Code Validation FormDefines codes for the types of fees associated with functions.

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Validation Forms (STV) Menu (*GENEVVAL1)


9 Event Management

GTVFUNC Function Code Validation FormDefines codes for the types of functions.

GTVLETR Letter Code Validation FormDefines codes for the letters associated with functions.

GTVMAIL Mail Code Validation FormDefines codes for mailings associated with functions.

GTVMENU Menu Code Validation FormDefines codes for the food and beverage items associated with functions.

GTVNTYP Name Type Validation FormDefines codes for the name types associated with IDs.

GTVPARS Partition Code Validation FormDefines codes for categories or groupings of rooms.

GTVPTYP Participant Type Code Validation FormDefines codes for the types of participants associated with functions.

GTVPURP Purpose Code Validation FormDefines codes that describe the purposes of functions.

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Validation Forms (GTVRATE - GTVZIPC) Menu (*GENEVVAL3)

GTVRATE Fee Rate Code Validation FormDefines codes for the types of rates associated with functions.

GTVREVN Revenue Code Validation FormDefines codes for revenues associated with functions.

GTVRSVP RSVP Code Validation FormDefines codes for the responses invitees can give to function invitations.

GTVRTNG Rating Code Validation FormDefines codes for ratings that can be assigned to function participants.

GTVSCHS Scheduling Partition Validation FormDefines Schedule25 status codes, which are used in the interface between Banner schedule processing and the third party scheduling products Schedule 25/Model25 to control whether a section is to be scheduled and listed.

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Validation Forms (GTVEMPH - GTVPURP) Menu (*GENEVVAL2)


9 Event Management

Event Management also uses the following inquiry and query forms that are not called from a menu:

• The Event Available Room Query Form (SLIAEVN) displays a list of rooms available in a date and time range.

• The Building Category Query Form (SLQBCAT) displays a list of categories in a building. A category is a physical area of a building (for example, specific wings and floors). The only way to access SLQBCAT is from the Category field on specific forms.

• The Room Query Form (SLQROOM) displays summary information about the rooms in your institution’s buildings for an indicated term. The only way to access SLQROOM is from the Room field on specific forms.

• The Event Query Form (SLQEVNT) displays summary information about the events at your institution. The only way to access SLQEVNT is from the Event field on specific forms.

Forms

This section describes each form in the Event Management module. Forms are described in the order they appear on the Event Management Menu (*GENEVENT).

GTVSUBJ Subject Index Validation FormDefines codes for indexes (keywords) that describe the subject matter of function comments.

GTVTARG Target Audience Code Validation FormDefines codes for groups of people who can be invited to a function.

GTVTASK Task Code Validation FormDefines codes for the tasks required to plan or carry out functions.

GTVTSTA Task Status Code Validation FormDefines status codes for tasks associated with functions.

GTVTTYP Task Type Code Validation FormDefines type codes for tasks associated with functions.

GTVZIPC ZIP/Postal Code Validation FormDefines codes for ZIP codes and postal codes associated with buildings.

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Validation Forms (GTVRATE - GTVZIPC) Menu (*GENEVVAL3)


9 Event Management

Event Form (SLAEVNT)

Use this form to create, maintain, and schedule an event. An event is any occasion that your institution offers or sponsors. Examples include meetings, conferences, and graduation ceremonies.

An event can optionally have several functions scheduled for specific dates, times, and places. For example, an event such as an alumni weekend might have a reception, dinner, conference, and lecture scheduled at various times and locations. You can create and schedule functions on SLAEVNT or on the Event Function Form (GEAFUNC). All other function details (such as contacts and status) must be entered on GEAFUNC.

You can also associate an Agency ID with an event. The agency can be created using the Identification Form (SPAIDEN) accessed from the Options Menu from the Event Information block.

The buildings where the events are being scheduled must exist on the Building Definition Form (SLABLDG). The rooms being used in event scheduling must exist on the Room Definition Form (SLARDEF). Room conflicts are checked when a record is first created, and also if the record is later updated with a new date, time, or room assignment.

Main Window

Use this window to create and maintain an event.

Key Block

Use the key block to identify the event.

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions

Event Unique code that identifies an event. An event is any occasion that your institution offers or sponsors. Examples include meetings, conferences, and graduation ceremonies. If this is an existing event, the description appears next to the event code.

To create a new event, enter ADD or select Add Event from the Options Menu. The next available event code is automatically assigned with the character A in the first position. The new code appears in the Event field after event details are saved.

To access an existing event, choices come from the Event Query Form (SLQEVNT).



9 Event Management

Event Details Block

Use the Event Details block to enter information about an event.

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions

Description Free form description of the event.

Column: SLBEVNT_DESC

Committee or Service Indicator

Indicates whether the scheduled event is tied to a committee or service on the Committee/Service Form (SHACOMI). This value comes from SHACOMI. It cannot be changed. Valid values are:

selected -- The event is associated with a committee or service on SHACOMI. This value is stored in the database as Y.cleared -- The event is not associated with a committee or service on SHACOMI. This value is stored in the database as N.

Column: SLBEVNT_COMM_IND

System Banner system associated with the event. The system determines what forms and tables (for example, identification and address forms) are accessed from the other forms for the event. Choices come from the System Indicator Validation (GTVSYSI) list.

Note: System codes G and T cannot be used. The General System (code G) supports other Banner systems and cannot be directly associated with an event. Accounts Receivable (code T) is part of the Student System and the Finance System.

Column: SLBEVNT_SYSI_CODE (code). Not a base table item (description)

Event Type Type of event. Examples include conference, presentation, and reception. Choices come from the Event/Function Type Validation (STVETYP) list.

Column: SLBEVNT_ETYP_CODE (code). Not a base table item (description)

Agency or Commercial ID

ID and name of the agency sponsoring the event. Choices come from the Person Search Form (SOAIDEN) or Non-Person Search Form (SOACOMP).

Column: Not base table items


9 Event Management

Contact ID ID and name of the contact within the sponsoring agency. If the contact is set up in Banner, choices come from the Person Search Form (SOAIDEN) or Non-Person Search Form (SOACOMP). If the contact is not set up in Banner, skip the Contact ID field and enter the contact name in the adjacent field.


Address Type Address type code for the contact assigned to the event. This field is used only if the contact ID is set up in Banner. Examples include business, mailing, and billing. Choices come from the address form for the associated Banner system.

Column: SLBEVNT_ATYP_CODE

Phone Telephone number of the contact. You can enter the telephone number only if the contact ID is not set up in Banner. If the contact ID is set up in Banner, these values come from the Identification Form (xxAIDEN) for the associated Banner system. They cannot be changed.


Campus Campus that is sponsoring the event. If you identify the campus for an event, you can query by campus on the Available Event Room Query Form (SLQEVNT). Choices come from the Campus Validation (STVCAMP) list.

Column: SLBEVNT_CAMP_CODE (code). Not a base table item (description)

Site Site location, within a campus, that is sponsoring the event. If you identify the site for an event, you can query by site on the Available Event Room Query Form (SLQEVNT). Choices come from the Site Validation (STVSITE) list.

Column: SLBEVNT_SITE_CODE (code). Not a base table item (description)

District or Division

District or division that is sponsoring the event. Choices come from the District Division Code Validation (GTVDICD) list.

Column: SLBEVNT_DICD_CODE (code). Not a base table item (description)

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions


9 Event Management

Meeting Times Window

Use this window to:

• Schedule an event. An event is any occasion that your institution offers or sponsors. Examples include meetings, conferences, and graduation ceremonies.

• Create and schedule functions. A function is an activity associated with an event and scheduled for a specific date, time, and place. Examples of functions include a reception, dinner, and lecture.

If there is a scheduling conflict, you must reschedule or select Conflict Override.

Note: You can also create and schedule functions on the Event Function Form (GEAFUNC).

College College that is sponsoring the event. If you identify the college for an event, you can query by college on the Available Event Room Query Form (SLQEVNT). Choices come from the College Validation (STVCOLL) list.

Column: SLBEVNT_COLL_CODE (code). Not a base table item (description)

Department Department, within a college, that is sponsoring the event. If you identify the department for an event, you can query by department on the Available Event Room Query Form (SLQEVNT). Choices come from the Department Validation (STVDEPT) list.

Column: SLBEVNT_DEPT_CODE (code). Not a base table item (description)

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions

Start Date Start date of the event or function.

Column: SSRMEET_START_DATE

End Date End date of the event or function. The end date must be the same as or later than the start date.

Column: SSRMEET_END_DATE

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions


9 Event Management

Mon (Monday) Indicates whether the event or function is scheduled for Mondays. Valid values are:

selected -- The event or function is scheduled for Mondays. This value is stored in the database as M.cleared -- The event or function is not scheduled for Mondays.

Note: If the start and end dates are the same, the system automatically determines the day of week.

Column: SSRMEET_MON_DAY

Tue (Tuesday) Indicates whether the event or function is scheduled for Tuesdays. Valid values are:

selected -- The event or function is scheduled for Tuesdays. This value is stored in the database as T.cleared-- The event or function is not scheduled for Tuesdays.


Column: SSRMEET_TUE_DAY

Wed (Wednesday)

Indicates whether the event or function is scheduled for Wednesdays. Valid values are:

selected -- The event or function is scheduled for Wednesdays. This value is stored in the database as W.cleared -- The event or function is not scheduled for Wednesdays.


Column: SSRMEET_WED_DAY

Thu (Thursday) Indicates whether the event or function is scheduled for Thursdays. Valid values are:

selected -- The event or function is scheduled for Thursdays. This value is stored in the database as R.cleared -- The event or function is not scheduled for Thursdays.


Column: SSRMEET_THU_DAY

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions


9 Event Management

Fri (Friday) Indicates whether the event or function is scheduled for Fridays. Valid values are:

selected -- The event or function is scheduled for Fridays. This value is stored in the database as F.cleared -- The event or function is not scheduled for Fridays.


Column: SSRMEET_FRI_DAY

Sat (Saturday) Indicates whether the event or function is scheduled for Saturdays. Valid values are:

selected -- The event or function is scheduled for Saturdays. This value is stored in the database as S.cleared -- The event or function is not scheduled for Saturdays.


Column: SSRMEET_SAT_DAY

Sun (Sunday) Indicates whether the event or function is scheduled for Sundays. Valid values are:

selected -- The event or function is scheduled for Sundays. This value is stored in the database as U.cleared -- The event or function is not scheduled for Sundays.


Column: SSRMEET_SUN_DAY

Begin Time Time when the event or function begins. Format is HHMM in 24-hour military time.

Column: SSRMEET_BEGIN_TIME

End Time Time when the event or function ends. Format is HHMM in 24-hour military time.

Column: SSRMEET_END_TIME

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions


9 Event Management

Event Comments Window

Use this window to enter comments about the event.

Building Building where the event or function is being held. Choices come from the Building Query Form (SLABQRY) or Event Available Room Query Form (SLIAEVN).

Column: SSRMEET_BLDG_CODE

Room Room where the event or function is being held. Choices come from the Room Query Form (SLQROOM).

Column: SSRMEEET_ROOM_CODE

Function Function being scheduled. A function is an activity associated with an event and scheduled for a specific date, time, and place. Examples of functions include a reception, dinner, and lecture.

To create a new function, choices come from the Function Code Validation (GTVFUNC) list. The function is automatically added to the Event Function Form (GEAFUNC). The status of the new function is A (active). The function type comes from the Function Code Validation Form (GTVFUNC). You can change these defaults on GEAFUNC.

To access an existing function, choices come from the Event Function Inquiry Form (GEIFUNC) or Event Function Form (GEAFUNC).

Column: SSRMEEET_FUNC_CODE

Conflict Override

Indicates whether more than one event or function can be scheduled for the same time and location. Valid values are:

selected -- More than one event or function can be scheduled for the same time and location. This value lets you override scheduling conflicts. This value is stored in the database as O.cleared -- Only one event or function can be scheduled for the same time and location.

Column: SSRMEET_OVER_RIDE

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions

Comment Free-form comment about the event.

Column: SLRECMT_COMMENTS

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions


9 Event Management

Procedures

To create an event:

1. Access the Event Form (SLAEVNT).

2. Enter ADD in the Event field.

or

Select Add Event from the Options Menu.

3. Go to the Event Details block.

4. (Optional) Enter a description of the event.

5. Enter the system associated with the event.

6. Enter the event type.

7. (Optional) Enter any other available event information in the Event Information block.

8. (Optional) Schedule the event.

9. (Optional) Go to the Event Comments Window, and enter comments.

10. Save.

To schedule an event:

1. Access the Event Form (SLAVENT).

2. Enter the event code.

3. Go to the Meeting Times Window.

4. Enter the start and end dates of the event.

5. Enter the begin and end times of the event.

6. (Optional) Enter the building code in the Building field.

7. (Optional) Enter the Room code.

8. Save.

9. If there is a scheduling conflict, return to step 4 to reschedule the event or select the Conflict Override checkbox.


9 Event Management

To create a function:

Note: The event must exist. You can create the event on the Event Form (SLAEVNT).



3. Go to the Meeting Times Window.

4. Enter the start and end dates of the function.

5. Enter the begin and end times of the function.


7. (Optional) Enter the room code.

8. Enter the function code.

9. Save.

10. If there is a scheduling conflict, return to step 4 to reschedule the function or select the Conflict Override checkbox.

Note: You can also create a function on the Event Function Form (GEAFUNC).

To enter comments for an event:



3. Go to the Event Comments Window.

4. Enter the comments.

5. Save.

Event Function Form (GEAFUNC)

Use this form to create, maintain, and schedule a function. A function is an activity associated with an event and scheduled for a specific date, time, and place. An event can have several functions. Examples of functions include a reception, dinner, and lecture.

You can create and schedule functions on GEAFUNC or on the Event Form (SLAEVNT). All other function details must be entered on GEAFUNC.


9 Event Management

If you delete a function with Remove Record, all function information is deleted, including tasks, participants, comments, and attendees.

Main Window

Use this window to create or maintain information for a function. A function is an activity associated with an event and scheduled for a specific date, time, and place. An event can have several functions. Examples of functions include a reception, dinner, and lecture.

Use the key block to identify the function.

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions

Event Event associated with the function. An event is any occasion that your institution offers or sponsors. Examples include meetings, conferences, and graduation ceremonies. The event must be defined on the Event Form (SLAEVNT).


Choices: Choices come from the Event Query Form (SLQEVNT).

System Name of the Banner system associated with the event.

Column: SLBEVNT_SYSI_DESC

Source: This value comes from the System field in the main window on the Event Form (SLAEVNT). It cannot be changed.

Function Function or activity associated with an event and scheduled for a specific date, time, and place. An event can have several functions. Examples of functions include a reception, dinner, and lecture.

Tip: To display all functions for the event, leave this field blank. When you go to the next block, use the scroll bar to scroll through each function associated with the event.

Column: GEBFUNC_FUNC_CODE1 (code). Not a base table item (description).

Choices: For all function codes, choices come from the Function Code Validation (GTVFUNC) list.

For all function codes associated with this event, choices come from the Event Function Inquiry Form (GEIFUNC).


9 Event Management

Details Window

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions

Function Function or activity associated with an event and scheduled for a specific date, time, and place. An event can have several functions. Examples of functions include a reception, dinner, and lecture.

Tip: To display details for the event associated with the function, select Event Information (SLAEVNT) from the Option List.

Column: GEBFUNC_FUNC_CODE (code). Not a base table item (description).

Source: For an existing function, this value comes from the Function field in the key block. It cannot be changed.

Note: If the Function field in the key block is blank, all functions associated with the event appear. Use the scroll bar in this block to scroll through the functions.

Choices: For a new function, choices come from the Function Code Validation (GTVFUNC) list. For existing functions associated with this event, choices come from the Event Function Inquiry Form (GEIFUNC).

Type Type of function. Examples include conference, presentation, and reception.

Column: GEBFUNC_ETYP_CODE (code). Not a base table item (description).

Source: For a new function, this value comes from the Type field on the Function Code Validation Form (GTVFUNC). It can be changed.

Choices: Choices come from the Event/Function Type Code Validation (STVETYP) list.

Status Status of the function. Examples include active, postponed, and cancelled.

Column: GEBFUNC_FSTA_CODE (code). Not a base table item (description).

Source: For a new function this value is A. It can be changed.

Choices: Choices come from the Function Status Validation (GTVFSTA) list.


9 Event Management

Purpose Purpose of the function. Examples include morale-builder, community service, and fund-raiser.

Column: GEBFUNC_PURP_CODE (code). GEBRUNC_PURP_DESCRIPTION (description).

Source: The description comes from the Description field on the Purpose Code Validation Form (GTVPURP). It can be changed.

Choices: Choices come from the Function Purpose Validation (GTVPURP) list.

Emphasis Emphasis of the function. Examples include recruiting and building fund.

The emphasis code can optionally be associated with a college, department, or both on the Emphasis Code Validation Form (GTVEMPH).

Column: GEBFUNC_EMPH_CODE (code). Not a base table item (description).

Choices: Choices come from the Function Emphasis Validation (GTVEMPH) list.

Sponsor ID and name of the sponsor of the function.


Choices: For an existing ID, choices come from the Person Search Form (SOAIDEN) or the Non-Person Search Form (SOACOMP).

For a new ID, click the Search button and select Add New ID from the Option List.

Sponsor Name (untitled)

Name of the sponsor of the function.


Invitation Invitation letter to be sent to invitees using the Letter Generation module.

The Mail Query Form (GUIMAIL) for an invitee includes this letter code. The Event Registration Form (GEAATID) and Attendance Form (GEAATTD) show whether the letter has been sent to an invitee.

Column: GEBFUNC_LETR_CODE

Choices: Choices come from the Letter Code Validation (GTVLETR) list.

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions


9 Event Management

Invitation Date Date when invitation letters for the function will be sent.

Column: GEBFUNC_INVITATION_DATE

Response Date Deadline date when RSVPs must be received.

Column: GEBFUNC_RSVP_CONFIRM_DATE

Committee Freeform name of the committee associated with the function.

Column: GEBFUNC_COMMITTEE_NAME

Planned Attendance

Number of attendees for which the function is being planned.

Column: GEBFUNC_PLAN_ATTEND

Break Even Attendance needed to cover expenses for the function.

Column: GEBFUNC_BRK_EVEN_ATTEND

Activity Date Date when information for the function was created or last updated.

Column: GEBFUNC_ACTIVITY_DATE

Location Contact

ID and name of the contact at the location where the function is being held.


Source: These values come from the Contact field in the main window on the Function Participant Form (GEAPART). They cannot be changed.

Primary Contact ID and name of the primary contact for the function.


Source: These values from the Contact field in the main window on the Function Participant Form (GEAPART). They cannot be changed.

Location Freeform location of the function, if it is being held off-site at a location not set up in Banner (for example, a hotel).

Note: If the function is being held at a location set up in Banner, enter the building and room in the Meeting Time window.

Column: GEBFUNC_LOCATION

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions


9 Event Management

Meeting Time Window

Use this window to schedule a function. A function is an activity associated with an event and scheduled for a specific date, time, and place. Examples of functions include a reception, dinner, and lecture.

If there is a scheduling conflict, you must reschedule the function or select Conflict Override.

Note: You can also schedule functions on the Event Form (SLAEVNT).

Additional Tasks Indicates whether the function has tasks defined on the Function Task Form (GEATASK).


Source: This value depends on whether tasks are defined on GEATASK. It cannot be changed.

Additional Participants

Indicates whether the function has participants defined on the Function Participant Form (GEAPART).


Source: This value depends on whether participants are defined on GEAPART. It cannot be changed.

Additional Comments

Indicates whether the function has comments defined on the Function Comment Form (GEAFCOM).


Source: This value depends on whether comments are defined on GEAFCOM. It cannot be changed.

Additional Attendance Data

Indicates whether the function has attendance information entered on the Event Registration Form (GEAATID) or Attendance Form (GEAATTD).


Source: This value depends on whether attendance information is entered on GEAATID or GEAATTD. It cannot be changed.

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions

Start Date Start date of the function.


. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions


9 Event Management

End Date End date of the function. The end date must be the same as or later than the start date.


Mon (Monday) Indicates whether the function is scheduled for Mondays.


Choices are:

selected - The function is scheduled for Mondays. This value is stored in the database as M.cleared - The function is not scheduled for Mondays.


Tue (Tuesday) Indicates whether the function is scheduled for Tuesdays.

Column: SSRMEET_TUUE_DAY

Choices are:

selected - The function is scheduled for Tuesdays. This value is stored in the database as T.cleared - The function is not scheduled for Tuesdays.


Wed (Wednesday)

Indicates whether the function is scheduled for Wednesdays.


Choices are:

selected - The function is scheduled for Wednesdays. This value is stored in the database as W.cleared - The function is not scheduled for Wednesdays.


. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions


9 Event Management

Thu (Thursday) Indicates whether the function is scheduled for Thursdays.


Choices are:

selected - The function is scheduled for Thursdays. This value is stored in the database as R.cleared - The function is not scheduled for Thursdays.


Fri (Friday) Indicates whether the function is scheduled for Fridays.


Choices are:

selected - The function is scheduled for Fridays. This value is stored in the database as F.cleared -The function is not scheduled for Fridays.


Sat (Saturday) Indicates whether the function is scheduled for Saturdays.

Column: SRMEET_SAT_DAY

Choices are:

selected - The function is scheduled for Saturdays. This value is stored in the database as S.cleared - The function is not scheduled for Saturdays.


Sun (Sunday) Indicates whether the function is scheduled for Sundays.


Choices are:

selected - The function is scheduled for Sundays. This value is stored in the database as U.cleared - The function is not scheduled for Sundays.


. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions


9 Event Management

Revenue Window

Use this window to track budgeted and actual revenues for a function.

Begin Time Time when the function begins. Format is HHMM in 24-hour military time.


End Time Time when the function ends. Format is HHMM in 24-hour military time.


Building Building where the function is being held.


Choices: Choices come from the Building Query Form (SLABQRY).

Room Room where the function is being held.

Column: SRMEEET_ROOM_CODE

Choices: Choices come from the Room Query Form (SLQROOM).

Conflict Override

Indicates whether more than one function can be scheduled for the same time and location.

Column: SSRMEET_OVER_RIDE

Choices are:

selected - More than one function can be scheduled for the same time and location. This value lets you override scheduling conflicts. This value is stored in the database as O.cleared - Only one function can be scheduled for the same time and location.

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions


9 Event Management

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions

Code Type of revenue this function generates. Examples include sponsor subsidies, donations, and fund-raisers. You can enter information for a revenue type more than once.

Column: GERFREV_REVN_CODE (code). Not a base table item (description).

Choices: Choices come from the Function Revenue Validation (GTVREVN) list.

Budget Amount Amount budgeted for the revenue type.

Column: GERFREV_BUDGET_AMT

Actual Amount Amount actually received for the revenue type.

Column: GERFREV_ACTUAL_AMT

Difference Difference between the actual amount received for the revenue type and the amount budgeted for the revenue type:

Actual Amount – Budget Amount

This value appears only if you enter both the Actual Amount and Budget Amount. A positive value means you are doing better than expected. A negative value means you are doing worse than expected.


Revenue Date Date when the revenue was received.

Column: GERFREV_REVENUE_DATE

Source: This value comes from the date when the revenue was entered on the form. It can be changed.

Total Budget Amount (untitled)

Total revenues budgeted for the function.

Column: Not a base table item.

Total Actual Amount (untitled)

Total revenues actually received for the function.



9 Event Management

Expenses Window

Use this window to track budgeted and actual expenses for a function.

Total Difference (untitled)

Difference between the total revenues received and the total revenues budgeted for the function:

Total Actual Amount – Total Budget Amount

A positive value means you are doing better than expected. A negative value means you are doing worse than expected.


. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions

Code Type of expense the function incurs. Examples include consulting, equipment, facilities, and publicity. You can enter information for an expense type more than once.

Column: GERFEXP_EXPN_CODE (code). Not a base table item (description).

Choices: Choices come from the Expense Code Validation (GTVEXPN) list.

Budget Amount Amount budgeted for the expense type.

Column: GERFEXP_BUDGET_AMT

Actual Amount Amount actually incurred for the expense type.

Column: GERFEXP_ACTUAL_AMT

Difference Difference between the amount budgeted for the expense type and the actual amount incurred for the expense type:

Budget Amount – Actual Amount

This value appears only if you enter both the Actual Amount and Budget Amount. A positive value means you are doing better than expected. A negative value means you are doing worse than expected.


. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions


9 Event Management

Fee Structure Window

Use this window to define the fees associated with a function.

A fee has three components:

• Fee type code identifies the fee.

• Fee rate code identifies the different kinds of rates the fee can have. For example a registration fee might have a regular rate (REG) and a senior discount rate (SRDIS).

• Fee amount specifies the amount charged for the fee type and fee rate.

Information in this window is informational only and is not used in any processing.

Expense Date Date when the expense was incurred.

Column: GERFEXP_EXPENSE_DATE

Source: This value comes from the date when the expense was entered on the form. It can be changed.

Total Budget Amount (untitled)

Total expenses budgeted for the function.


Total Actual Amount (untitled)

Total expenses actually incurred for the function.


Total Difference (untitled)

Difference between the total expenses budgeted and the total expenses incurred for the function:

Total Budget Amount – Total Expense Amount

A positive value means you are doing better than expected. A negative value means you are doing worse than expected.


. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions


9 Event Management

Target Audience Window

Use this window to identify the target audiences for a function. A target audience is a group for which a function is targeted.

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions

Type Type of fee associated with the function. Examples include registration, dinner, and charitable donation.

Column: GERFFEE_FTYP_CODE (code). Not a base table item (description).

Choices: Choices come from the Fee Type Code Validation (GTVFTYP) list.

Rate Type of rate associated with the fee. A fee can have more than one rate. For example, a registration fee might have a regular rate (REG) and a senior discount rate (SRDIS).

Column: GERFFEE_RATE_CODE

Choices: Choices come from the Rate Code Validation (GTVRATE) list.

Amount Amount of the fee associated with the fee type and fee rate.

Column: GERFFEE_AMT

Activity Date Date when the fee information was created or last changed.

Column: GERFFEE_ACTIVITY_DATE

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions

Code Type of audience for which the function is targeted. Examples include current undergraduates, high school seniors, and loan recipients.

Column: GERFCON_TARG_CODE (code). Not a base table item (description).

Choices: Choices come from the Target Audience Validation (GTVTARG) list.

Date Date when the target audience for the function was created or last changed.

Column: GERFCON_ACTIVITY_DATE


9 Event Management

Mailings Window

Use this window to track the various mailings for a function. A function can have an unlimited number of mailings.

Meal Menu Window

Use this window to identify the various food and beverage choices for a function.

A function can have an unlimited number of meal menu choices.

When you enter a menu choice for an attendee or guest on the Event Registration Form (GEAATID) or Attendance Form (GEAATTD), a warning appears if the menu choice has not been set up for the function in this window. You can override the warning if the attendee or guest has special dietary needs.

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions

Code Mailing associated with the function. Examples include invitations and tickets.

Column: GERFCOR_MAIL_CODE (code). Not a base table item (description).

Choices: Choices come from the Mail Code Validation (GTVMAIL) list.

Mailing Date Date when the mailing is scheduled to be sent or date it was sent.

Column: GERFCOR_MAIL_DATE

Piece Count Number of items mailed.

Column: GERFCOR_NUM_MAILINGS

Audience Audience targeted to receive the mailing. This audience must have been previously associated with the function in the Target Audience window.

Column: GERFCOR_TARG_CODE

Choices: Choices come from the Target Audience list of audiences defined for the function.

Letter Code Letter to be sent using the Letter Generation module.

Column: GERFCOR_LETR_CODE

Choices: Choices come from the Letter Code Validation (GTVLETR) list.


9 Event Management

Procedures

To create a function

1. Access the Event Function Form (GEAFUNC).

2. Enter the Event code.


4. Select Create Record.

5. Enter the code of the new Function.

6. Verify the function Type. Change if necessary.

7. Verify the function Status. Change if necessary.

8. (Optional) Enter any other function details.

9. Go to the Meeting Time window.

10. Enter the Start Date and End Date of the function.

11. Enter the Begin Time and End Time of the function.


13. (Optional) Enter the Room code.

14. Save.

15. If there is a scheduling conflict, return to step 10 to reschedule the function or select the Conflict Override check box.

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions

Code Menu choice associated with the function. Examples include baked ham, breakfast buffet, and kosher dinner.

Column: GERMENU_MENU_CODE (code). Not a base table item (description).

Choices: Choices come from the Menu Code Validation (GTVMENU) list.

Activity Date Date when the menu choice for the function was created or last changed.

Column: GERMENU_ACTIVITY_DATE


9 Event Management

Note: You can also create a function on the Event Form (SLAEVNT).

To enter receipts for a function



3. Enter the Function code in the key block.


5. Go to the Revenues window.

6. Enter the revenue Code.

7. (Optional) Enter the revenue Budget Amount.

8. Enter the revenue Actual Amount.

9. Save.

To enter expenses for a function





5. Go to the Expenses window.

6. Enter the expense Code.

7. (Optional) Enter the expense Budget Amount.

8. Enter the expense Actual Amount.

9. Save.

To create the fee structure for a function





5. Go to the Fee Structure window.


9 Event Management

6. Enter the fee Type associated with the function.

7. Enter the Rate type associated with the fee type.

8. Enter the Amount of the rate associated with the fee type and fee rate.

9. Save.

To identify the target audiences for a function





5. Go to the Target Audience window.

6. Enter the Code that identifies the target audience associated with the function.

7. Save.

To track mailings for a function





5. Go to the Mailings window.

6. Enter the Code that identifies the mailing associated with the function.

7. (Optional) Enter any other details about the mailing.

8. Save.

To identify menu items for a function





5. Go to the Meal Menu window.


9 Event Management

6. Enter the Code that identifies the menu item associated with the function.

7. Save.

Function Task Form (GEATASK)

Use this form to:

• Record information about the tasks required to plan and carry out a function.

• Send task-related messages.

• Assign task-related responsibilities to IDs.


The function must exist. You can create the function on SLAEVNT or on the Event Function Form (GEAFUNC).

Key Block

Use the key block to identify the function associated with the tasks.

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions

Event Event associated with the tasks. An event is any occasion that your institution offers or sponsors. Examples include meetings, conferences, and graduation ceremonies. The event must be defined on the Event Form (SLAEVNT).







9 Event Management

Task Information Window

A function can have an unlimited number of tasks. However, a specific task can be entered only once. Tasks appear in chronological order based on their start dates.

Tip: Use the Detail/Summary option in the Options menu to switch back and forth between summary and detail modes. Summary mode displays basic information for three tasks. Detail mode displays additional details for one selected task.

Function Function associated with the tasks. A function is an activity associated with an event and scheduled for a specific date, time, and place. Examples of functions include a reception, dinner, and lecture. The function must be defined on the Event Form (SLAEVNT) or Event Function Form (GEAFUNC).


Choices: Choices come from the Event Function Inquiry Form (GEIFUNC).

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions

Task Code Specific task or activity required to plan or carry out the function.

Column: GERTASK_TASK_CODE (code). Not a base table item (description).

Choices: Choices come from the Function Task Code (GTVTASK) list.

Task Type Type of task. Examples include clerical, maintenance, and security.

Column: GERTASK_TTYP_CODE (code). Not a base table item (description).

Source: The code comes from the Type field on the Task Code Validation Form (GTVTASK). It can be changed. The description comes from the Description field on the Task Type Validation Form (GTVTTYP). It cannot be changed.

Choices: Choices come from Task Type Validation (GTVTTYP) list.

From Date when the task starts.

Column: GERTASK_BEGIN_DATE

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions


9 Event Management

From Time (untitled)

Time when the task starts. Format is HHMM in 24-hour military time.

Column: GERTASK_START_TIME

To Date when the task ends.

Column: GERTASK_END_DATE

To Time (untitled)

Time when the task ends. Format is HHMM in 24-hour military time.

Column: GERTASK_END_TIME

Status Status of the task. Examples include active, completed, and pending.

Column: GERTASK_TSTA_CODE

Choices: Choices come from the Task Status Validation (GTVTSTA) list.

Status Date Date when the task status code was assigned or last updated.

Column: GERTASK_TSTA_DATE

Message Indicates whether the task has a message.

Column: GERTASK_MESSAGE_IND

Source: This value comes from the Message field in the task details. It cannot be changed. Choices are:

selected - The task has a message. This value is stored in the database as Y.cleared - The task does not have a message.

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions


9 Event Management

Detail Window

This window provides detailed information about the function.

Detail Indicates whether additional information (target completion date, message, or assigned responsibilities) exists for the task. If you are already in detail mode, this check box does not appear.

Tip: To display additional information for the task, select the Detail option in the Options menu.


Source: This value comes from the task details. It cannot be changed.

Choices are:

selected - The task has additional details. This value is stored in the database as Y.cleared - The task has no additional details.

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions

Task Code Specific task or activity required to plan or carry out the function.

Column: GERTASK_TASK_CODE (code). Not a base table item (description).

Choices: Choices come from the Function Task Code (GTVTASK) list.

Task Type Type of task. Examples include clerical, maintenance, and security.

Column: GERTASK_TTYP_CODE (code). Not a base table item (description).

Source: The code comes from the Type field on the Task Code Validation Form (GTVTASK). It can be changed. The description comes from the Description field on the Task Type Validation Form (GTVTTYP). It cannot be changed.

Choices: Choices come from Task Type Validation (GTVTTYP) list.

From Date when the task starts.

Column: GERTASK_BEGIN_DATE

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions


9 Event Management

From Time (untitled)

Time when the task starts. Format is HHMM in 24-hour military time.

Column: GERTASK_START_TIME

To Date when the task ends.

Column: GERTASK_END_DATE

To Time (untitled)

Time when the task ends. Format is HHMM in 24-hour military time.

Column: GERTASK_END_TIME

Status Status of the task. Examples include active, completed, and pending.

Column: GERTASK_TSTA_CODE

Choices: Choices come from the Task Status Validation (GTVTSTA) list.

Status Date Date when the task status code was assigned or last updated.

Column: GERTASK_TSTA_DATE

Message Indicates whether the task has a message.

Column: GERTASK_MESSAGE_IND

Source: This value comes from the Message field in the task details. It cannot be changed. Choices are:

selected - The task has a message. This value is stored in the database as Y.cleared - The task does not have a message.

Target Complete Date

Target date for completing the task. This field appears only in detail mode (selected with the Detail option in the Options menu).

Column: GERTASK_TARGET_COMPL_DATE

Source: This value comes from the To date in the main window. It can be changed.

Activity Date Date when the task details were created or last updated. This field appears only in detail mode (selected with the Detail option in the Options menu).

Column: GERTASK_ACTIVITY_DATE

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions


9 Event Management

Recipient ID to whom the message will be sent. This field appears only in detail mode (selected with the Detail option in the Options menu).

Column: GERTASK_MESSAGE_RECIPIENT

Choices: Choices come from the identification form (xxAIDEN) for the associated Banner system.

Message Text of the message. This field appears only in detail mode (selected with the Detail option in the Options menu). Refer to the specific task in the message text. This helps the recipient associate the message with a task. (The standard message does not identify the task.)

The message is sent to the recipient on the message date. The recipient can use the General Message Form (GUAMESG) to read the message. The Source is GEATASK, the Ref ID is the function code, and the status is Pending.

You can query on this field.

Column: GERTASK_COMMENT

Date (untitled) Date when the message will be sent to the recipient. This field appears only in detail mode (selected with the Detail option in the Options menu).

Column: GERTASK_MESSAGE_DATE

Source: This value comes from the date when the message is created. It can be changed.

ID ID and name assigned to the task. These fields appear only in detail mode (selected with the Detail option in the Options menu).


Choices: Choices come from the Person Search Form (SOAIDEN) or the Non-Person Search Form (SOACOMP).

Name (untitled) Name of the ID assigned to the task. This field appears only in detail mode (selected with the Detail option in the Options menu).


. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions


9 Event Management

Function Information Window (GEATASK)

Use this window to display information about the function associated with the tasks. This block is display-only.

Comment Freeform comment associated with the ID assigned to the task. This field appears only in detail mode (selected with the Detail option in the Options menu).

Column: GERTKID_COMMENT

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions



Source: These values come from the Purpose field in the main window on the Event Function Form (GEAFUNC). They cannot be changed.



Source: This value comes from the Status field in the main window on the Event Function Form (GEAFUNC). It cannot be changed.



Source: These values come from the Type field in the main window on the Event Function Form (GEAFUNC). They cannot be changed.



Source: This value comes from the Emphasis field in the main window on the Event Function Form (GEAFUNC). It cannot be changed.

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions


9 Event Management



Source: These values come from the Sponsor field in the main window on the Event Function Form (GEAFUNC). They cannot be changed.

Location Contact









Source: This value comes from the Start Date field in the Meeting Time window on the Event Function Form (GEAFUNC). It cannot be changed.

End Date End date of the function.


Source: This value comes from the End Date field in the Meeting Time window on the Event Function Form (GEAFUNC). It cannot be changed.

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions


9 Event Management



Source: This value comes from the Mon field in the Meeting Time window on the Event Function Form (GEAFUNC). It cannot be changed.

Choices are:




Source: This value comes from the Tue field in the Meeting Time window on the Event Function Form (GEAFUNC). It cannot be changed.

Choices are:


Wed (Wednesday)



Source: This value comes from the Wed field in the Meeting Time window on the Event Function Form (GEAFUNC). It cannot be changed.

Choices are:


. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions


9 Event Management



Source: This value comes from the Thu field in the Meeting Time window on the Event Function Form (GEAFUNC). It cannot be changed.

Choices are:




Source: This value comes from the Fri field in the Meeting Time window on the Event Function Form (GEAFUNC). It cannot be changed.

Choices are:

selected - The function is scheduled for Fridays. This value is stored in the database as F.cleared - The function is not scheduled for Fridays.



Source: This value comes from the Sat field in the Meeting Time window on the Event Function Form (GEAFUNC). It cannot be changed.

Choices are:


. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions


9 Event Management



Source: This value comes from the Sun field in the Meeting Time window on the Event Function Form (GEAFUNC). It cannot be changed.

Choices are:


Begin Time Time when the function begins.


Source: This value comes from the Begin Time field in the Meeting Time window on the Event Function Form (GEAFUNC). It cannot be changed.

End Time Time when the function ends.


Source: This value comes from the End Time field in the Meeting Time window on the Event Function Form (GEAFUNC). It cannot be changed.



Source: This value comes from the Building field in the Meeting Time window on the Event Function Form (GEAFUNC). It cannot be changed.



Source: This value comes from the Room field in the Meeting Time window on the Event Function Form (GEAFUNC). It cannot be changed.

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions


9 Event Management

Procedures

To create a task

1. Access the Function Task Form (GEATASK).


3. Enter the Function code.


5. Enter the Task Code for the task.

6. Verify the Task Type. Change if necessary.

7. (Optional) Enter any additional information for the task.

Tip: To enter task details, select the Detail option in the Options menu.

8. Save.

To send a task-related message





5. Select the Task Code for which you want to send a message.

6. Select the Detail option in the Options menu.

7. Enter the ID of the Recipient to whom you are sending the message.

8. Enter the message in the field adjacent to the Recipient.

Tip: Refer to the specific task in the message text. This helps the recipient associate the message with a task. (The standard message does not identify the task.)

9. Verify the date when you want the message to be sent. Change if necessary.

10. Save.

To assign task-related responsibilities




9 Event Management



5. Select the Task Code for which you want to assign responsibilities.

6. Select the Detail option in the Options menu.

7. Go to the ID Assigned to Task block.

8. Enter the ID assigned to the task.

9. Save.

Function Participant Form (GEAPART)

Use this form to record information about the participants associated with a function. A participant assists with a function and may or may not attend. A function can have an unlimited number of participants. Examples include speakers, caterers, and presenters.

Main Window

Use this window to record information about the participants associated with a function.

Tip: Use the Detail/Summary option in the Options menu to switch back and forth between summary and detail modes. Summary mode displays basic information for three participants. Detail mode displays additional details for one selected participant.

Use the key block to identify the function associated with the participants.

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions

Event Event associated with the participants. An event is any occasion that your institution offers or sponsors. Examples include meetings, conferences, and graduation ceremonies. The event must be defined on the Event Form (SLAEVNT).




9 Event Management




Function Function associated with the participants. A function is an activity associated with an event and scheduled for a specific date, time, and place. Examples of functions include a reception, dinner, and lecture. The function must be defined on the Event Form (SLAEVNT) or Event Function Form (GEAFUNC).



ID ID and name of the participant.


Choices: For an existing ID, choices come from the Person Search Form (SOAIDEN) or the Non-Person Search Form (SOACOMP). For a new ID, you can create an ID on the identification form (xxAIDEN) for the associated Banner system.

Name (untitled) Name of the participant.


Type Type of participant. Examples include caterers, panelists, and speakers.

Column: GERPART_PTYP_CODE (code). Not a base table item (description).

Choices: Choices come from Participant Type Code Validation (GTVPTYP) list.

Date Date when the ID is participating in the function.

Column: GERPART_DATE

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions


9 Event Management

Attend Indicates whether the participant plans to attend the function.


Choices are:

selected - The participant plans to attend the function. This value creates attendance information for the ID on the Attendance Form (GEAATTD) and the Event Registration Form (GEAATID). This value is stored in the database as Y.cleared (default) - The participant does not plan to attend the function. This value removes attendance information, if it exists, from GEAATTD and GEAATID. This value is stored in the database as N.

Contact Indicates whether the participant is a contact person for the function.

Column: GERPART_CONTACT_IND

Choices are:

none (default) - This participant is not a contact.Primary - This participant is the primary contact for the function. This value is stored in the database as P.Location - This participant is the location contact for the function. This value is stored in the database as L.

Note: If Primary or Location is selected, the participant’s name and ID appear as the contact on the Event Function Form (GEAFUNC).

More Detail Indicates whether additional information (address type, phone, rating, or comments) exists for the participant. If you are already in detail mode, this check box does not appear.

Note: To display additional information for the ID, select the Detail option in the Options menu.


Source: This value comes from the participant details. It cannot be changed.

Choices are:

selected - The participant has additional details. This value is stored in the database as Y.cleared - The participant has no additional details. This value is stored in the database as N.

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions


9 Event Management

Function Information Window

Use this window to display information about the function associated with the participants.

Address Type Participant’s address type. Examples include business, mailing, and billing.

Column: GERPART_ATYP_CODE

Choices: Choices come from an address, telephone, or identification form, depending on the associated Banner system.

Phone Primary telephone number associated with the participant’s address type code.


Source: These values come from the identification form (xxAIDEN) for the associated Banner system. They cannot be changed.

Rating Rating that indicates how well the participant performed. Examples include excellent, unacceptable, and not rated.

Column: GERPART_RTNG_CODE

Choices: Choices come from the Rating Code Validation (GTVRTNG) list.

Comment Freeform comment about the participant. .

Column: GERPART_COMMENT

Date (untitled) Date when the participant details were created or last updated.

Column: GERPART_ACTIVITY_DATE

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions




. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions


9 Event Management













Location Contact







. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions


9 Event Management










Choices are:





Choices are:


. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions


9 Event Management

Wed (Wednesday)




Choices are:





Choices are:





Choices are:

selected - The function is scheduled for Fridays. This value is stored in the database as F.

cleared - The function is not scheduled for Fridays.

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions


9 Event Management




Choices are:





Choices are:











. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions


9 Event Management

Procedures

To add a participant

1. Access the Function Participant Form (GEAPART).




5. Enter the ID of the participant.

6. Enter the code that identifies the Type of participant.

7. Verify the type of Contact.

8. (Optional) Enter any additional information for the participant.

Tip: To enter participant details, select the Detail option in the Options menu.

9. Save.

Function Comment Form (GEAFCOM)

Use this form to enter, display, and edit freeform comments about a function. A function can have an unlimited number of comments. You can assign subject indexes (keywords) to a comment to help you search for the comment at a later time.

You can use comments to:

• Track the progress of a function.

• Leave detailed instructions.

• Record details for future planning.




. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions


9 Event Management



Main Window

Use this window to enter, display, and edit freeform comments about a function. A function can have an unlimited number of comments. You can assign subject indexes (keywords) to a comment to help you search for the comments at a later time.

The main window contains three interrelated blocks:

• The key block identifies the function associated with the comments.

• The Comment block shows each comment on a separate line.

• The Subject Indexes block shows the subject indexes associated with the comment selected in the Comment block. Each comment can have different subject indexes.

If you identify a subject index in the key block, only those comments associated with the subject index appear in the Comment block.

Use the key block to identify the function associated with the comments. If you are displaying existing comments, you can optionally enter a subject index (keyword). This limits the display to those comments associated with a specific subject index.

Use the Comment block to display or enter comments.

Use the Subject Indexes block to display the subject indexes (keywords) associated with the comment selected in the Comment block. Each comment can have different subject indexes.

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions

Event Event associated with the comments. An event is any occasion that your institution offers or sponsors. Examples include meetings, conferences, and graduation ceremonies. The event must be defined on the Event Form (SLAEVNT).




9 Event Management

Subject Subject matter of the comments.


Choices:

To enter new comments, leave this field blank.

To display all comments for the function, leave this field blank.

To display comments associated with a specific subject index, enter a subject index. Choices come from the Function Subject Index Query Form (GEISUBJ).

Function Function associated with the comments. A function is an activity associated with an event and scheduled for a specific date, time, and place. Examples of functions include a reception, dinner, and lecture. The function must be defined on the Event Form (SLAEVNT) or Event Function Form (GEAFUNC).






Comment Freeform comment associated with the function. Each line is a separate comment and can have approximately 65,000 characters. The radio buttons in front of these fields indicate which comment is selected. When a comment is selected, subject indexes for that comment appear in the Subject Indexes block. If a subject index is entered in the Subject field in the key block, only those comments associated with that subject index appear.

Column: GERFCOM_COMMENT

User User who created or last updated the comment.

Column: GERFCOM_USER_ID

Source: This value comes from the user ID of the user who created or last updated the comments.

Activity Date Date when the comment was last entered or updated.

Column: GERFCOM_ACTIVITY_DATE

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions


9 Event Management


Use this window to display information about the function associated with the comments.

Subject Keyword that identifies the subject matter of the comment. A function can have an unlimited number of subject indexes (keywords). These subject indexes can help you search for comments at a later time.

Note: A selected radio button in the Comment block indicates which comment is associated with the displayed subject indexes.

Column: GERSUBJ_SUBJ_CODE (code). Not a base table item (description).

Choices: Choices come from the Subject Index Validation (GTVSUBJ) list.

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions










. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions


9 Event Management







Location Contact













. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions


9 Event Management




Choices are:





Choices are:


Wed (Wednesday)




Choices are:


. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions


9 Event Management




Choices are:





Choices are:





Choices are:


. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions


9 Event Management




Choices are:














. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions


9 Event Management

Procedures

To enter comments for a function

1. Access the Function Comment Form (GEAFCOM).



4. Go to the Comment block.

5. Enter the Comment on a blank line.

6. Save.

To enter subject indexes for a comment





5. Select the Comment to which you want to assign subject indexes.

6. Go to the Subject Indexes block.

Note: The radio button in front of the comment shows which comment is selected.

7. Enter the Subject index code associated with the comment.

8. Repeat step 7 for each subject index associated with the comment.

9. Save.

To display comments for a function




4. To display all comments for the function, leave the Subject field in the key block blank.

OR


9 Event Management

To display comments with a specific subject index, enter the subject index in the Subject field in the key block.


6. View the comments.

To edit comments for a function





5. Select the Comment you want to edit.

6. Click the Comments button. The Comment Text window appears.

7. Edit the comment.

8. Click the OK button. The main window reappears.

9. Save.

Event Registration Form (GEAATID)

Use this form to record attendance information for an ID who is invited to multiple functions within an event. You can also track information for the ID’s guests. This information helps you plan successful events.

You can also record attendance information on the Attendance Form (GEAATTD). Use GEAATID to record information by ID; use GEAATTD to record information by function.

Attendance information entered on GEAATID can be queried on the Function Attendance Inquiry Form (GEIATTD).

Main Window

Use this window to record attendance information for an ID who is invited to multiple functions within an event.

Use the key block to identify the event and ID associated with the attendance information.


9 Event Management

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions

Event Event associated with the attendance information. An event is any occasion that your institution offers or sponsors. Examples include meetings, conferences, and graduation ceremonies. The event must be defined on the Event Form (SLAEVNT).






ID ID and name of the invitee. The ID can be a person or a non-person (for example, a company or organization).



For a new ID, click the drop-down arrow and select Create New ID from the Option List.

Name (untitled) Name of the invitee. The invitee can be a person or a non-person (for example, a company or organization).


Function Function associated with the attendance information. A function is an activity associated with an event and scheduled for a specific date, time, and place. Examples of functions include a reception, dinner, and lecture. The function must be defined on the Event Form (SLAEVNT) or Event Function Form (GEAFUNC).

Column: GERATTD_FUNC_CODE



9 Event Management

RSVP ID’s responses to the invitation. Examples include attending, not attending, and send regrets.

Column: GERATTD_RSVP_CODE

Choices: Choices come from the RSVP Code Validation (GTVRSVP) list.

Plan to Attend Check box that indicates whether the ID plans to attend the function.


Source: This value comes from the Plan to Attend field on the RSVP Code Validation Form (GTVRSVP) for the ID’s RSVP code. It cannot be changed.

Choices are:

selected - The ID plans to attend the function. This value is stored in the database as Y.cleared - The ID does not plan to attend the function. This value is stored in the database as N.

Attended Check box that indicates whether the ID attended the function.

Column: GERATTD_ATTENDANCE_IND

Choices are:

selected - The ID attended the function. This value is stored in the database as Y.cleared - The ID did not attend the function. This value is stored in the database as N.

Fee Status ID’s payment status of any fees associated with the function. Examples include paid, partially paid, and due.

Column: GERATTD_FEES_CODE

Choices: Choices come from the Fee Status Validation (GTVFEES) list.

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions


9 Event Management

Event Attendance Information Window

Use this window to record additional attendance information for an ID and specific function.

Detail Indicates whether additional attendance information exists for the ID in the Event Attendance Information window.


Source: This value comes from the attendance details in the Event Attendance Information window. It cannot be changed.

Choices are:

selected - The ID has additional details. This value is stored in the database as Y.cleared - The ID has no additional details. This value is stored in the database as N.

Guests Indicates whether the ID has guests with information in the Event Registration Guest Information window.


Source: This value comes from the guest information in the Event Registration Guest Information window. It cannot be changed.

Choices are:

selected - The ID has guests. This value is stored in the database as Y.cleared - The ID has no guests. This value is stored in the database as N.

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions

Function Function associated with the attendance information. A function is an activity associated with an event and scheduled for a specific date, time, and place. Examples of functions include a reception, dinner, and lecture.

Column: GERATTD_FUNC_CODE (code). Not a base table item (description).

Source: This code comes from the Function field in the main window. It cannot be changed.

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions


9 Event Management

Attended Indicates whether the ID attended the function.


Source: This value comes from the Attended field in the main window. It can be changed.

Choices are:


Plan to Attend Indicates whether the ID plans to attend the function.



Choices are:

selected - The ID plans to attend the function. This value is stored in the database as Y.

cleared - The ID does not plan to attend the function. This value is stored in the database as N.


Column: GERATTD_RSVP_CODE (code). Not a base table item (description).

Source: The code comes from the RSVP field in the main window. It can be changed. The description comes from the Description field of the corresponding RSVP code on the RSVP Code Validation Form (GTVRSVP). It cannot be changed.


RSVP Date Date when the ID’s RSVP was received.

Column: GERATTD_RSVP_DATE

Source: This value comes from the date when the ID’s RSVP code was last entered or updated. It can be changed.

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions


9 Event Management


Column: GERATTD_FEES_CODE (code). GERATTD_FEES_DESC (description).

Source: The code comes from the Fee Status field in the main window. It can be changed. The description comes from the Description field for the corresponding code on the Fee Status Code Validation Form (GTVFEES). It can be changed.


Fee Date Date when the ID’s fee status code was last entered or updated.

Column: GERATTD_FEE_DATE

Source: This value comes from the date when the ID’s fee status code was last entered or updated. It can be changed.

Menu ID’s menu choice for this function. Examples include baked ham, breakfast buffet, and kosher dinner.

Warning: If you enter a menu code that is not set up for the function on the Event Function Form (GEAFUNC), a warning appears. You can override the warning to allow for special meals.

Column: GERATTD_MENU_CODE (code). Not a base table item (description).

Choices are: Choices come from the Menu Code Validation (GTVMENU) list or a list of menu codes defined for the function.

Participant Type of participant, if the ID is participating in the function. Asterisks (****) indicate the ID has more than one role as a participant. Examples include caterers, panelists, and speakers.

Participant information is recorded on the Function Participant Form (GEAPART).


Source: This value comes from the Type field in the main window on GEAPART. It cannot be changed.

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions


9 Event Management

Address Type Type of address associated with the ID. This address type is defined on the identification form for the associated Banner system. Examples include business, mailing, and billing.

Column: GERATTD_ATYP_CODE

Choices: Choices come from the address form for the associated Banner system.

Number of Tickets

Number of tickets the ID requested.

Column: GERATTD_TICKET_CNT

Invitation sent Indicates whether an invitation letter was sent to the ID. The Event Function Form (GEAFUNC) includes the letter code of the invitation letter. Once the letter is sent, the letter code is recorded on the invitee’s mail form (xxxMAIL) and this check box is selected.


Source: This value comes from the ID’s mail form (xxxMAIL). It cannot be changed.

Choices are:

selected - An invitation letter was sent and appears on the mail form. This value is stored in the database as Y.cleared - An invitation letter was not sent.

Date Sent Date when the invitation letter was sent to the ID.



Name Tag Name for the ID’s name tag.

Column: GERATTD_NAME_TAG_NAME

Source: If the ID plans to attend the function, this value (including the prefix and suffix) comes from the identification form (xxAIDEN) for the associated Banner system. It can be changed.

If the function is associated with the Advancement System, this value comes from the preferred address name, if it exists. It can be changed.

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions


9 Event Management

Event Registration Guest Information Window

Use this window to record attendance information for a guest associated with a function and invitee.

Use the Button Control block to identify the function associated with the attendance information. Use the Guest ID block to identify the guests associated with the function and invitee.

Use the Guest Information block to record attendance information for a guest associated with a function and invitee.

Place Card Name for the ID’s place card.

Column: GERATTD_PLACE_CARD_NAME


If the function is associated with the Advancement System, this name comes from the preferred address name, if it exists. It can be changed.

Comment Freeform comment associated with the ID.

Column: GERATTD_COMMENT

Activity Date Date when the ID’s attendance information was last entered or updated.

Column: GERATTD_ACTIVITY_DATE

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions



Source: This value comes from the Function field in the main window. It cannot be changed.

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions


9 Event Management

Guest ID ID and name of each guest associated with the function and invitee. You can add a new guest or select an existing guest for which you want to enter attendance information.


Choices:

For an existing guest, select the guest ID.

For a new guest, make sure the cursor is on a blank Guest ID field. Click the drop-down arrow and select Person Search from the Option List. Choices come from the Person Search Form (SOAIDEN).

For a new ID, click the drop-down arrow and select Add New ID from the Option List.

(Advancement System only) For cross reference IDs for the associated invitee, click the drop-down arrow and select Cross Reference IDs from the Option List.

Guest Name (untitled)

Name of each guest associated with the function and invitee. You can add a new guest or select an existing guest for which you want to enter attendance information.


Guest ID and name of a guest associated with the function and invitee.


Source: These values come from the Guest ID field selected in the top part of the window. They cannot be changed.

Attended Indicates whether the guest attended the function.


Choices are:

selected - The guest attended the function. This value is stored in the database as Y.cleared - The guest did not attend the function.

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions


9 Event Management

Fee Status Guest’s payment status of any fees associated with the function. Examples include paid, partially paid, and due.

Columns:

GERATTD_FEES_CODE (code)GERATTD_FEES_DESC (description)

Source: These values come from the Fee Status field in the main window. They describe the fee status of the ID who invited the guest. They can be changed for the guest.


Fee Date Date when the guest’s fee status was entered or last updated.


Source: This value comes from the Fee Status Date field in the main window. It is the fee status date for the ID who invited the guest. It can be changed for the guest.

Menu Guest’s menu choice for this function. Examples include baked ham, breakfast buffet, and kosher dinner.



Choices: Choices come from the Menu Code Validation (GTVMENU) list or a list of menu codes defined for the function.

Address Type of address associated with the guest. This address type is defined on the identification form for the associated Banner system. Examples include business, mailing, and billing.


Choices: Choices come from the Address Type Validation (STVATYP) list.

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions


9 Event Management


Use this window to display information about the function associated with the attendance information.

Use the Function Base Information block to display information about the function associated with the attendance information. This block is display-only. No information can be changed.

Name Tag Name on the guest’s name tag.


Source: If the invitee plans to attend the function, this value (including the prefix and suffix) comes from the identification form (xxAIDEN) for the associated Banner system. It can be changed.


Place Card Name on the guest’s place card.




Comment Freeform comments associated with the guest.


Activity Date Date when the guest’s attendance information was entered or last updated.


. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions


9 Event Management

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions

















9 Event Management

Location Contact
















Choices are:


. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions


9 Event Management




Choices are:


Wed (Wednesday)




Choices are:





Choices are:


. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions


9 Event Management




Choices are:





Choices are:





Choices are:




Source: This value comes from the Begin Timefield in the Meeting Time window on the Event Function Form (GEAFUNC). It cannot be changed.

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions


9 Event Management

Procedures

To enter attendance information for an invitee

1. Access the Event Registration Form (GEAATID).


3. Enter the invitee’s ID.


5. Enter the Function code on a blank record.

6. Enter attendance information for the invitee.

7. (Optional) Enter additional attendance details on the Event Attendance Information window.

8. Repeat steps 5 through 7 for each function to which the ID is invited.

9. Save.










. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions


9 Event Management

To enter attendance information for a guest





5. Select the Function code for which you are adding a guest.

6. Go to the Event Registration Guest Information window.

7. Enter the Guest ID on a blank record.

8. Save.

9. Click any field in the bottom part of the form.

10. Enter attendance information for the guest.

11. Save.

To update attendance information for an invitee





5. Update attendance information.

6. (Optional) Update attendance details on the Event Attendance Information window.

7. Save.

To update attendance information for a guest





5. Select the Function code for which you are updating guest attendance information.


9 Event Management

6. Go to the Event Registration Guest Information window.

7. Select the Guest ID for which you are updating attendance information.

8. Update attendance information in the bottom part of the form.

9. Save.

Attendance Form (GEAATTD)

Use this form to record attendance information for a specific function. You can track information for each ID invited to the function and the ID’s guests. This information helps you plan successful events.

You can also record attendance information on the Event Registration Form (GEAATID). Use GEAATID to record information by ID; use GEAATTD to record information by function.

Attendance information entered on GEAATTD can be queried on the Function Attendance Inquiry Form (GEIATTD).

Main Window

Use this window to record attendance information for IDs invited to a function. You can also identify an ID’s guests for the function.

Use the key block to identify the function associated with the attendance information. Use the Guests block to identify the guests associated with the function and invitee.

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions

Event Event associated with the attendance information. An event is any occasion that your institution offers or sponsors. Examples include meetings, conferences, and graduation ceremonies. The event must be defined on the Event Form (SLAEVNT).







9 Event Management

Function Function associated with the attendance information. A function is an activity associated with an event and scheduled for a specific date, time, and place. Examples of functions include a reception, dinner, and lecture. The function must be defined on the Event Form (SLAEVNT) or Event Function Form (GEAFUNC).



ID ID and name of the invitee. The ID can be a person or a non-person (for example, a company or organization).

Column: Not base table items.


For a new ID, click the drop-down arrow and select Create New ID from the Option List.

Name (untitled) Name of the invitee. The invitee can be a person or a non-person (for example, a company or organization).


Attended Indicates whether the ID attended the function.


Choices are:


. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions


9 Event Management

Plan to Attend Indicates whether the ID plans to attend the function.



Choices are:

selected - The ID plans to attend the function. This value is stored in the database as Y.cleared - The ID does not plan to attend the function. This value is stored in the database as N.


Column: GERATTD_RSVP_CODE (code). Not a base table item (description).


Date Date when the ID’s RSVP was received.

Column: GERATTD_RSVP_DATE

Source: This value comes from the date when the ID’s RSVP code was last entered or updated. It can be changed.


Columns:


Source: The description comes from the Description field for the corresponding code on the Fee Status Code Validation Form (GTVFEES). It can be changed.


Date Date when the ID’s fee status code was last entered or updated.


Source: This value comes from the date when the ID’s fee status code was last entered or updated. It can be changed.

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions


9 Event Management

Menu ID’s menu choice for this function. Examples include baked ham, breakfast buffet, and kosher dinner.




Participant Type of participant, if the ID is participating in the function. Asterisks (****) indicate the ID has more than one role as a participant. Examples include caterers, panelists, and speakers.

Participant information is recorded on the Function Participant Form (GEAPART).


Source: This value comes from the Type field on GEAPART. It cannot be changed.

Address Type Type of address associated with the ID. This address type is defined on the identification form for the associated Banner system. Examples include business, mailing, and billing.



Number of Tickets

Number of tickets the ID requested.

Column: GERATTD_TICKET_CNT

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions


9 Event Management

Invitation sent Indicates whether an invitation letter was sent to the ID. The Event Function Form (GEAFUNC) includes the letter code of the invitation letter. Once the letter is sent, the letter code is recorded on the invitee’s mail form (xxxMAIL) and this check box is selected.



Choices are:

selected - An invitation letter was sent and appears on the mail form. This value is stored in the database as Y.cleared - An invitation letter was not sent.

Date Sent Date when the invitation letter was sent to the ID.



Name Tag Name for the ID’s name tag.




Activity Date Date when the ID’s attendance information was last entered or updated.


. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions


9 Event Management

Guest Information Window

Use this window to record attendance information for a guest associated with a function and invitee.

Use the Guest Information block to record attendance information for a guest associated with a function and invitee. The Guests block on the main window lists the invitee’s guests for the function. The Guest Information block contains additional details for a selected guest.

Place Card Name for the ID’s place card.




Comment Free-form comment associated with the ID.


Guest ID ID and name of each guest associated with the function and invitee. You can add a new guest or select an existing guest for which you want to update attendance information.

Column: Not base table items (ID and name)

Choices: For an existing guest, select the guest ID. Click the drop-down arrow and select Guest Information from the Option List.

For a new guest, make sure the cursor is on a blank Guest ID field. Select the Search button and select Person Search from the Option List. Choices come from the Person Search Form (SOAIDEN).

For a new ID, click the drop-down arrow and select Add New ID from the Option List.

(Advancement System only) For cross reference IDs for the associated invitee, click the drop-down arrow and select Cross Reference IDs from the Option List.

Guests Name of each guest associated with the function and invitee.


. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions


9 Event Management

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions

Guest ID and name of a guest associated with the function and invitee.


Source: These values come from the Guest ID field selected in the top part of the window. They cannot be changed.

Guest Name (untitled)

Name of a guest associated with the function and invitee.


Source: This value comes from the selected Guest ID field in the main window. It cannot be changed.



Choices are:

selected - The guest attended the function. This value is stored in the database as Y.cleared - The guest did not attend the function.

Fee Status Guest’s payment status of any fees associated with the function. Examples include paid, partially paid, and due.

Columns:


Source: These values come from the Fee Status field in the main window. They describe the fee status of the ID who invited the guest. They can be changed for the guest.




Source: This value comes from the Fee Status Date field in the main window. It is the fee status date for the ID who invited the guest. It can be changed for the guest.


9 Event Management

Menu Guest’s menu choice for this function. Examples include baked ham, breakfast buffet, and kosher dinner.




Address Type of address associated with the guest. This address type is defined on the identification form for the associated Banner system. Examples include business, mailing, and billing.







Activity Date Date when the guest’s attendance information was entered or last updated.


. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions


9 Event Management


Use this window to display information about the function associated with the attendance information. This window is display-only. No information can be changed.







. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions







. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions


9 Event Management










Location Contact










. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions


9 Event Management







Choices are:





Choices are:


Wed (Wednesday)




Choices are:


. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions


9 Event Management




Choices are:





Choices are:





Choices are:


. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions


9 Event Management

Procedures

1. Access the Attendance Form (GEAATTD).





Choices are:














. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions


9 Event Management



5. Enter the invitee’s ID on a blank record.

6. Enter attendance information for the invitee.

7. Save.

To enter attendance information for a guest





5. Select the ID who invited the guest.

6. Go to the Guests block.

7. Enter the Guest ID on a blank record.

8. Save.

9. Go to the Guest Information window.

10. Enter attendance information for the guest.

11. Save.

To update attendance information for an invitee





5. Select the ID for which you are updating attendance information.

6. Update attendance information for the invitee.

7. Save.


9 Event Management

To update attendance information for a guest





5. Select the ID who invited the guest.

6. Go to the Guests block.

7. Select the Guest ID for which you are updating attendance information.

8. Go to the Guest Information window.

9. Update attendance information for the guest.

10. Save.

Building Definition Form (SLABLDG)

Use this form to enter and update information about your institution’s buildings. Three Banner modules use this building information:

• Location Management (Student System) assigns student housing in buildings.

• Class Schedule (Student System) schedules classes in buildings.

• Event Management (General System) schedules events and functions in buildings.

After you set up a building on SLABLDG, you can use the Room Definition Form (SLARDEF) to enter information about specific rooms in the building.

Special Building Information

You can enter two kinds of special building information on SLABLDG:

Attributes. These are features and equipment that apply to all rooms in the building. Examples include handicapped-accessible, air-conditioned, and nonsmoking. (You can change the attributes for a specific room on SLARDEF.)

Categories. These are the physical areas of the building. Examples include specific floors and wings.


9 Event Management

Main Window

Use this window to enter and update information about your institution’s buildings.

Key Block

Use the key block to identify the building.

Building Definition Block

Use the Building Definition block to enter and update information about your institution’s buildings.

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions

Building Building used at your institution for student housing, classes, events, and functions. For a new building, choices come from the Building Code Validation (STVBLDG) list. For an existing building, choices come from the Building Query Form (SLABQRY).


. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions

Campus Campus where the building is located. Choices come from the Campus Validation (STVCAMP) list.

Column: SLBBLDG_CAMP_CODE (code). Not a base table item (description).

Site Site location, within a campus, where the building is located. If you identify the site for a building, you can query by site on the Building Query Form (SLABQRY). Choices come from the Site Validation (STVSITE) list.

Column: SLBBLDG_SITE_CODE (code). Not a base table item (description)

Capacity Normal capacity of the building.

Column: SLBBLDG_CAPACITY

Maximum Absolute maximum capacity of the building. Enter this value if extra people, over the normal capacity, can be assigned to the building. This value comes from the Capacity field in this window. It can be changed.

Column: SLBBLDG_MAXIMUM_CAPACITY


9 Event Management

Gender Radio group that indicates gender restrictions for the building.

Choices:

Male -- The building is available to males only. Females and persons of unknown gender cannot be assigned to any room in the building. This value is stored in the database as M.

Female -- The building is available to females only. Males and persons of unknown gender cannot be assigned to any room in the building. This value is stored in the database as F.

Not Applicable (default) -- The building is available to males and females. You can change the gender restriction on any room in the building on the Room Definition Form (SLARDEF).

Column: SLBBLDG_SEX

College College that has primary responsibility for operating and maintaining the building.

This college is automatically assigned to each room in the building. If necessary, you can change the college for individual rooms on the Room Definition Form (SLARDEF).

Choices come from the College Validation (STVCOLL) list.

Column: SLBBLDG_COLL_CODE (code). Not a base table item (description)

Department Department, within the college, that has primary responsibility for operating and maintaining the building.

This department is automatically assigned to each room in the building. If necessary, you can change the department for individual rooms on the Room Definition Form (SLARDEF).

Choices come from the Department Validation (STVDEPT) list.

Column: SLBBLDG_DEPT_CODE

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions


9 Event Management

Partition Defines an appropriate partition code for the building and provides a means to group rooms for scheduling purposes. Valid values come from the Scheduling Partition Validation Form (GTVPARS).

This partition code will default to the room when new entries are created on SLARDEF. If the partition code is changed, it will not affect existing room definitions but will be reflected in any new room records that are created.

• If all rooms in a building are considered one partition, then the partition code could be defined at the building level, rather than at the individual room level, to save data entry.

• If a building is divided into several partitions, the partition code should not be assigned to the building but should be entered for the individual rooms.

• If the majority of rooms within a building constitute one partition, you can record the partition on the building and override the applicable code for rooms not considered part of the “building” partition.

The auto scheduling extract process reads the partition from the room definition. If a partition code is not established on the room record, the partition code defined on this form will be retrieved.

Column: SLBBLDG_PARS_CODE

Room Rate Rate charged for each room in the building. If necessary, you can change the rate for individual rooms on the Room Definition Form (SLARDEF). Choices come from the Room Rate Code Validation (STVRRDC) list.

Column: SLBBLDG_RRCD_CODE

Phone Rate Telephone rate charged for each room in the building. If necessary, you can change the rate for individual rooms on the Room Definition Form (SLARDEF). Choices come from the Phone Rate Code Validation (STVPRCD) list.

Column: SLBBLDG_PRCD_CODE

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions


9 Event Management

Street Line 1/2/3 Street address of the building.

Tip: To automatically enter the rest of the address based on the ZIP or postal code, select Next Primary Key. The cursor skips to the ZIP/PC field. Select a ZIP or postal code from the ZIP/Postal Code Validation (GTVZIPC) list. Associated address data automatically appears in the appropriate fields.

Column: SLSBBLDG_STREET_LINE1

SLSBBLDG_STREET_LINE2

SLSBBLDG_STREET_LINE3

City City or town where the building is located.

Tip: To automatically enter the city based on the ZIP or postal code, select Next Primary Key. The cursor skips to the ZIP/PC field. Select a ZIP or postal code from the ZIP/Postal Code Validation (GTVZIPC) list. The city automatically appears if it is defined for the selected ZIP or postal code.

Column: SLBBLDG_CITY

State or Province

State or province where the building is located. Choices come from the State/Province Code Validation (STVSTAT) list.

Tip: To automatically enter the state or province based on the ZIP or postal code, select Next Primary Key. The cursor skips to the ZIP/PC field. Select a ZIP or postal code from the ZIP/Postal Code Validation (GTVZIPC) list. The state or province automatically appears if it is defined for the selected ZIP or postal code.

Column: SLBBLDG_STAT_CODE

ZIP or Postal Code

ZIP or postal code for the address where the building is located. Choices come from the ZIP/Postal Code Validation Form (GTVZIPC).

Column: SLBBLDG_ZIP

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions


9 Event Management

Building Attributes, Category, and Comments Window

Use this window to enter the following building information:

• Attributes. These are features and equipment that apply to all rooms in the building. Examples include handicapped-accessible, air-conditioned, and nonsmoking. You can change the attributes for a specific room on the Room Definition Form (SLARDEF).

• Categories. These are the physical areas of the building. Examples include specific floors and wings.

• Comments. This is miscellaneous information for the building.

County Code County where the building is located. Choices come from the Country Code Validation (STVCNTY) list.

Tip: To automatically enter the county based on the ZIP or postal code, select a ZIP or postal code from the ZIP/Postal Code Validation Form (GTVZIPC), using a List function from the ZIP/PC field. The county automatically appears if it is defined for the selected ZIP or postal code.

Column: SLBBLDG_CNTY_CODE (code). Not a base table item (description).

Phone Area code, main telephone number (without a hyphen), and extension for the building.

Column: SLBBLDG_PHONE_AREA

SLBBLDG_PHONE_NUMBER

SLBBLDG_PHONE_EXTENSION

Key Number Free form number of the key associated with the building.

Column: SLBBLDG_KEY_NUMBER

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions


9 Event Management

Building Attributes Block

The following fields are in this block:

Building Category Block

The following fields are in this block:

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions

Attributes Features and equipment that apply to all rooms in the building. A building can have an unlimited number of attributes. Examples include handicapped-accessible, air-conditioned, and nonsmoking.

You can change the attributes for a specific room on the Room Definition Form (SLARDEF).

Choices come from the Building/Room Attributes Validation (STVRDEF) list.

Column: SLRBDEF_RDEF_CODE (code). Not a base table item (description)

Description Free form description of the building attribute.

Not a base table item

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions

Category Code that identifies a physical area of the building. Examples include specific floors and wings. The Location Management module uses building categories to assign students to preferred areas of a building. The code is free form.

You can use the Room Definition Form (SLARDEF) to assign a category to a room.

Column: SLRBCAT_CODE

Description Free form description of the building category. Examples of categories include specific floors and wings. The Location Management module uses building categories to assign students to preferred areas of a building.

You can use the Room Definition Form (SLARDEF) to assign a category to a room.

Column: SLRBCAT_DESC


9 Event Management

Building Comments Block

The following field is in this block:

Procedures

To create a building:

1. Access the Building Definition Form (SLABLDG).

2. Enter a building code.

3. Go to the Building Definition block.

4. Enter the campus code.

5. Enter the building’s capacity.

6. Click the Maximum field, and verify the value. Change if necessary.

7. Verify the setting of the Gender radio group. Change if necessary.

8. (Optional) Enter any other building information in the Building Definition block.

9. (Optional) Go to the Building Attributes block, and enter each building attribute on a blank line.

10. (Optional) Go to the Building Category block, and enter each building category on a blank line.

11. (Optional) Go to the Building Comments block, and enter comments.

12. Save.

To identify special features of a building (attributes):


2. Enter the building code.


4. Go to the Building Attributes block.

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions

Building Comments

Free form comments about the building can be entered here, such as which campus the building is located on.

Column: SLRBCMT_COMMENTS


9 Event Management

5. Enter each building attribute on a blank line.

6. Save.

To identify physical areas of a building (categories):


2. Enter the building code.


4. Go to the Building Category block.

5. Enter a building category on a blank line.

6. (Optional) Enter a description of the category.

7. Save.

Room Definition Form (SLARDEF)

Use this form to enter and update information about the rooms in your institution’s buildings. Three Banner modules use this room information:

• Location Management (Student System) assigns student housing in rooms.

• Class Schedule (Student System) schedules classes in rooms.

• Event Management (General System) schedules events and functions in rooms.

Room information is defined by term. You can change room information for a term at any time. You do not have to wait until the end of the term. You can copy room information from one term to another using the Copy button or a Duplicate Record function.

You can identify the attributes of a room. Attributes are special features and equipment such as handicapped-accessible, air-conditioned, and nonsmoking.

Note: The building in which the room is located must exist prior to entering information for the room. You can create the building on the Building Definition Form (SLABLDG).

Main Window

Use this window to enter and update room information by term and building.


9 Event Management

Key Block

Use the key block to identify the room and the term when the room information is effective.

Room Definition Block

Use the Room Definition block to enter and update information about a room in one of your institution’s buildings.

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions

Building Building used at your institution for student housing, classes, events, and functions.

Choices come from the Building Query Form (SLABQRY) or Room Query Form (SLQROOM).


Room Room used at your institution for student housing, classes, events, and functions. You can enter any user-defined code.

Choices come from the Room Query Form (SLQROOM).


Term Term when the room information is effective. Use this field to display or change room information for a specific term.

Choices come from the Term Code Validation (STVTERM) list.


. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions

New Term Term for which new or copied room information applies. Use this field when you create a new room or copy existing room information to a new term. Choices come from the Term Code Validation (STVTERM) list.

Tip: Use a Duplicate Record function to copy existing room information to a new term. Enter the new term for which the copied room information applies.

Note: You do not have to have a term in the Term field in the key block to copy information to a new effective term in the Room Definition block.

Column: SLBRDEF_TERM_CODE_EFF


9 Event Management

From Term Term when the currently displayed room information becomes effective.

This value is automatically updated when room information is created for a new effective term. It cannot be changed.


To Term Term when the currently displayed room information is no longer effective. The range of effective terms is up to this term, not including the To Term.

This value is automatically updated when room information is created for a new effective term. It cannot be changed.


Description Free form description of the room.

Column: SSLBRDEF_DESC

Capacity Normal capacity of the room. Banner uses this value as follows:

• Location Management (Student System) uses this value to assign the correct number of students to a dormitory room.

• Class Schedule (Student System) uses this value to schedule a class in a properly sized room.

• Event Management (General System) uses this value to schedule an event or function in a properly sized room.

Column: SLBRDEF_CAPACITY

Maximum Absolute maximum capacity of the room. Enter this value if extra people, over the normal capacity, can be assigned to the room. The Room Assignment Form (SLARASG) uses this value if you want to assign extra people to a room.

This value comes from the Capacity field in this window. It can be changed.

Column: SLBRDEF_MAXIMUM_CAPACITY

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions


9 Event Management

Gender Radio group that indicates any gender restrictions for the room. The Room Assignment Form (SLARASG) and Batch Scheduler Report (SLRSHCD) use this information to assign student housing. The following forms identify a person’s gender:

• Dorm Room and Meal Application Form (SLARMAP)

• General Person Form (SPAPERS)

Source - This value comes from the Gender field in the main window on the Building Definition Form (SLABLDG). If the building is available to one gender only (male or female), you cannot change the restriction for an individual room. If the building is available to both genders, you can change the restriction for an individual room.

Choices:

Male -- The room is available to males only. Females and persons of unknown gender cannot be assigned to the room. This value is stored in the database as M.

Female -- The room is available to females only. Males and persons of unknown gender cannot be assigned to the room. This value is stored in the database as F.

N/A (default) -- The room is available to both males and females. Rooms are assigned as follows:

If you are using the Room Assignment Form (SLARASG), you can assign both males and females to the room. This method is useful for married couples and co-ed housing.

If you are using the Batch Scheduler Report (SLRSHCD), the gender of the first person assigned to the room determines the gender of the room. If the first person assigned has an unknown gender, no one else is assigned to the room. The gender restriction on the Room Definition Form (SLARDEF) does not change.

Column: SLBRDEF_SEX

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions


9 Event Management

Room Type Radio group that indicates the room type.

Choices:

Residence Hall (default) -- The Room Assignment form (SLARASG) and Batch Scheduler Report (SLRSHCD) can assign IDs to this room. This value is stored in the database as D.

Classroom -- The Schedule Form (SSASECT) can schedule classes in this room, the Event Form (SLAEVNT) can schedule events and functions in this room, and the Event Function Form (GEAFUNC) can schedule functions in this room. This value is stored in the database as C.

Other -- SLAEVNT can schedule events and functions in this room, and GEAFUNC can schedule functions in this room. This value is stored in the database as O.

Column: SLBRDEF_ROOM_TYPE

College College that has primary responsibility for operating and maintaining the room. If you identify the college for a room, you can query by college on the Room Query Form (SLQROOM).

This value comes from the College field in the main window on the Building Definition Form (SLABLDG). It can be changed.

Choices come from the College Validation (STVCOLL) list.

Column: SLBRDEF_COLL_CODE (code)

Not a base table item (description)

Department Department, within the college, that has primary responsibility for operating and maintaining the room. If you identify the department for a room, you can query by department on the Room Query Form (SLQROOM).

This value comes from the Department field in the main window on the Building Definition Form (SLABLDG). It can be changed.

Choices come from the Department Validation (STVDEPT) list.

Column: SLBRDEF_DEPT_CODE (code)


. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions


9 Event Management

Status Status of the room. Examples include active and being renovated. If you identify the status of a room, you can query by status on the Room Query Form (SLQROOM).

A room cannot be used for a class, dormitory assignment, event, or function if its status code is flagged inactive on the Room Status Code Validation Form (STVRMST).

Choices come from the Room Status Code Validation (STVRMST) list.

Column: SLBRDEF_RMST_CODE (code)


Category Physical area of the building where the room is located. Examples include specific floors and wings. The Location Management module uses categories to assign students to preferred areas of a building. If you identify the category of a room, you can query by category on the Room Query Form (SLQROOM).

Choices come from the Building Category Query Form (SLQBCAT).

Column: SLBRDEF_BCAT_CODE (code)


Partition Defines an appropriate partition code for the room and provides a means to group rooms for scheduling purposes. Valid values come from the Scheduling Partition Validation Form (GTVPARS).

If a partition code has been defined for the corresponding building record, the building partition code will default into this field. You may change the partition code that has been established for the building.

The extract process will first read the partition from the room definition. If a partition code is not established on the room record, the partition code defined for the building will be retrieved.

Column: SLBRDEF_PARTITION_CODE

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions


9 Event Management

Room Rate Rate charged for the room. The Room Assignment Form (SLARASG) uses this rate as the default room rate. It can be changed on SLARASG. This value comes from the Room Rate field in the main window on the Building Definition Form (SLABLDG). It can be changed.

Choices come from the Room Rate Code Validation (STVRRCD) list.

Column: SLBRDEF_RRCD_CODE (code)


Phone Rate Telephone rate charged for the room. The Phone Assignment Form (SLAPASG) uses this rate as the default phone rate. It can be changed on SLAPASG. This value comes from the Phone Rate field in the main window on the Building Definition Form (SLABLDG). It can be changed.

Choices come from the Phone Rate Code Validation (STVPRCD) list.

Column: SLBRDEF_PRCD_CODE (code)


Phone Area code, main telephone number (without a hyphen), and extension for the room. The area code is optional.

The Phone Assignment Form (SLAPASG) uses this as the default telephone number. It can be changed on SLAPASG.

Column: SLBRDEF_PHONE_AREA

SLBRDEF_PHONE_NUMBER

SLBRDEF_PHONE_EXTENSION

Utility Rate Utility rate associated with the room for the time period indicated in the Period field. This rate is informational only and is not used in any processing.

The value can be 0.00 through 99999.99.

Column: SLBRDEF_UTILITY_RATE

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions


9 Event Management

Period Pulldown list that indicates the time period associated with the utility rate. This value is informational only and is not used in any processing.

Choices:

None (default) -- No rate period is entered.

Month -- The rate period is monthly. This value is stored in the database as MO.

Term -- The rate period is term. This value is stored in the database as TR.

Year -- The rate period is yearly. This value is stored in the database as YR.

Day -- The rate period is daily. This value is stored in the database as DY.

Column: SLBRDEF_UTILITY_RATE_PERIOD

Priority Number that indicates the order in which the Batch Scheduler Report (SLRSHCD) schedules the room. Rooms are scheduled in descending order, starting with 99999999.

The default value is 9999999. It can be changed.

Column: SLBRDEF_PRIORITY

Key Number Free form number of the key associated with the room.

Column: SLBRDEF_KEY_NUMBER

Width Width (in feet) of the room. The value can be 0.00 through 9999.99.

Column: SLBRDEF_WIDTH

Length Length (in feet) of the room. The value can be 0.00 through 9999.99.

Column: SLBRDEF_LENGTH

Area Area (in square feet) of the room. This value is automatically calculated when the width and length are saved.

Column: SLBRDEF_AREA

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions


9 Event Management

Attributes, Inactive Dates, and Comments Window

Use this window to enter the following room information:

• Attributes. These are special features and equipment of the room such as handicapped-accessible, air-conditioned, and nonsmoking.

• Inactive dates. These are dates the room is unavailable.

• Comments. This is miscellaneous information for the room.

Room Attributes Block

Use the Room Attributes block to enter information about the special features and equipment that apply a room and to identify the range of terms when the room attributes are effective. Examples include handicapped-accessible, air-conditioned, and nonsmoking.

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions

From Term Term when the currently displayed room attributes become effective. This value comes from the From Term field in the main window. It cannot be changed.


To Term Term when the currently displayed room attributes are no longer effective. The range of effective terms is up to this term, not including the To Term.

This value comes from the To Term field in the main window. It cannot be changed.


Attribute Special features and equipment that apply to the room. A room can have an unlimited number of attributes. Examples include handicapped-accessible, air-conditioned, and nonsmoking.

These values come from the Attribute fields in the Building Attributes, Category, and Comments Window on the Building Definition Form (SLABLDG). They can be changed or deleted.

Choices come from the Building/Room Attributes Validation (STVRDEF) list.

Column: SLRRDEF_RDEF_CODE (code)



9 Event Management

Room Inactivation Block

Use the Room Inactivation block to identify dates when the room is unavailable.

Must Match Indicates whether the attribute is critical and must be matched when the Batch Scheduler Report (SLRSHCD) assigns dormitory rooms.

Choices:

selected -- The attribute must be matched when SLRSHCD assigns dormitory rooms. This value is stored in the database as Y.

cleared -- The attribute does not have to be matched when SLRSHCD assigns dormitory rooms.

Column: SLRRDEF_MUST_MATCH

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions

Start Date Start date of the time period when the room is unavailable for scheduling.

Column: SLRRUSE_START_DATE

Begin Time Time on the start date when the room starts being unavailable for scheduling. Format is HHMM in 24-hour military time. If you enter a start time, you must enter an end time.

Column: SLRRUSE_BEGIN_TIME

Mon (Monday) Indicates whether the room is available for scheduling on Mondays during the specified time period.

Choices:

selected -- Room is unavailable on Mondays.cleared -- Room is available on Mondays.

Column: SLRRUSE_MON_DAY

Tue (Tuesday) Indicates whether the room is available for scheduling on Tuesdays during the specified time period.

Choices:

selected -- Room is unavailable on Tuesdays.cleared -- Room is available on Tuesdays.

Column: SLRRUSE_TUE_DAY

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions


9 Event Management

Wed (Wednesday)

Indicates whether the room is available for scheduling on Wednesdays during the specified time period.

Choices:

selected -- Room is unavailable on Wednesdays.cleared -- Room is available on Wednesdays.

Column: SLRRUSE_WED_DAY

Thu (Thursday) Indicates whether the room is available for scheduling on Thursdays during the specified time period.

Choices:

selected -- Room is unavailable on Thursdays.cleared -- Room is available on Thursdays.

Column: SLRRUSE_THU_DAY

Fri (Friday) Indicates whether the room is available for scheduling on Fridays during the specified time period.

Choices:

selected -- Room is unavailable on Fridays.cleared -- Room is available on Fridays.

Column: SLRRUSE_FRI_DAY

Sat (Saturday) Indicates whether the room is available for scheduling on Saturdays during the specified time period.

Choices:

selected -- Room is unavailable on Saturdays.cleared -- Room is available on Saturdays.

Column: SLRRUSE_SAT_DAY

Sun (Sunday) Indicates whether the room is available for scheduling on Sundays during the specified time period.

Choices:

selected -- Room is unavailable on Sundays.cleared -- Room is available on Sundays.

Column: SLRRUSE_SUN_DAY

End Date End date of the time period when the room is unavailable for scheduling.

Column: SLRRUSE_END_DATE

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions


9 Event Management

Room Comments Block

Use the Room Comments block to enter miscellaneous information for the room.

Procedures

To create a room:

Note: The building in which the room is located must exist prior to entering information for the room. You can create the building on the Building Definition Form (SLABLDG).

1. Access the Room Definition Form (SLARDEF).

2. Enter the building code in the Building field.

3. Enter the room code.

4. Go to the Room Definition block.

End Time Time on the end date when the room stops being unavailable for scheduling. Format is HHMM in 24-hour military time. The end date and end time must be later than the start date and start time. If you entered a start time, you must enter an end time.

Column: SLRRUSE_END_TIME

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions

From Term Term when the currently displayed room comments become effective. This value comes from the From Term field in the main window. It cannot be changed.


To Term Term when the currently displayed room comments are no longer effective. The range of effective terms is up to this term, not including the To Term.

This value comes from the To Term field in the main window. It cannot be changed.


Comments (untitled)

Free form comments about the room.

Column: SLRCMNT_COMMENTS

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions


9 Event Management

5. Enter the effective term in the New Term field.

6. Enter the room capacity.

7. Click the Maximum field, and verify the value. Change if necessary.

8. Verify the setting of the Gender radio group. Change if necessary.

9. Verify the Room Type Indicator. Change if necessary.

10. Verify any displayed room information. Change if necessary.

11. (Optional) Enter any other room information in the Room Definition block.

12. (Optional) Go to the Room Attributes block, and enter each room attribute on a blank line.

13. (Optional) Go to the Room Inactivation block, and inactivate rooms by start and end date and time and day of the week if the room will not be in use at certain times or day.s.

14. (Optional) Go to the Room Comments block, and enter comments.

15. Save.

To copy room information to a new term:




4. (Optional) Enter the term of the room information to be copied.


6. Perform a Duplicate Record function in the New Term field.

7. Enter the new term to which room information is being copied.

8. (Optional) Enter any changes to the displayed room information.

9. Save.

To inactivate a room:






9 Event Management

5. Go to the Room Inactivation block.

6. Enter the start date of the inactive period.

7. Enter the start time of the inactive period.

8. Enter the end date of the inactive period.

9. Enter the end time of the inactive period.

10. Select the check boxes for the days of the week that the room should be inactive.

11. Save.

Function Attendance Inquiry Form (GEIATTD)

Use this form to display attendance information for an event or function. You can query all invitees and guests, or you can limit the query by entering selection criteria. This form shows the total number of IDs that match your criteria, plus a list of all the matching IDs.

Note: Events are initially created on the Event Form (SLAEVNT).

This form helps you answer the following kinds of questions:

• How many people are planning to attend the event or function?

• What meals need to be ordered? How many?

• How many people have paid their fees?

• How many invitees are bringing guests?

• How many people actually attended?

Information comes from the Event Registration Form (GEAATID) and the Attendance Form (GEAATTD). Information is display-only and cannot be changed.

Main Window

Use this window to query attendance information for an event or function. You can query all invitees and guests, or you can limit the query by entering selection criteria. This window shows the total number of IDs that match your criteria, plus a list of all the matching IDs.

Information comes from the Event Registration Form (GEAATID) and the Attendance Form (GEAATTD). Information is display-only and cannot be changed.


9 Event Management

Use the Inquiry Criteria block to enter the selection criteria for querying attendance information for an event or function. You can query all invitees and guests, or you can limit the query by entering selection criteria in this block.

Use the Attendee Display block to display attendance information for the IDs that match your selection criteria. Information is display-only and cannot be changed.

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions

Event Event you want to query. An event is any occasion that your institution offers or sponsors. Examples include meetings, conferences, and graduation ceremonies. The event must be defined on the Event Form (SLAEVNT).






Function Function you want to query. A function is an activity associated with an event and scheduled for a specific date, time, and place. Examples of functions include a reception, dinner, and lecture.

Note: An ID can attend more than one function for the event. If you query all functions for the event (the Function field is blank), the ID appears in the Attendee Display block for each function. However, the ID is counted only once in the Count field.


Choices: To query all functions for the event, leave this field blank. To query a specific function, choices come from the Event Function Inquiry Form (GEIFUNC).

Fee Status Fee status you want to query. This code identifies the payment status of fees. Examples include paid, partially paid, and due.




9 Event Management

RSVP RSVP code you want to query. This code identifies the invitee’s response to the invitation. Examples include attending, not attending, and send regrets.



Menu Menu code you want to query. This code indicates the invitee’s menu choice for this function. Examples include baked ham, breakfast buffet, and kosher dinner.


Choices: Choices come from the Menu Code Validation (GTVMENU) list.

Guest Indicator Radio group that indicates whether you are querying IDs with guests or IDs without guests.


Choices are:

Has Guest - Query IDs who have guests. This value is stored in the database as Y.

Has No Guest - Query IDs who do not have guests. This value is stored in the database as N.

No Guest Criteria - Query all IDs, regardless of whether they have guests.

Invitee/Guest Indicator

Radio group that indicates whether you are querying IDs who are invitees or IDs who are guests.


Choices are:

Invitee - Query IDs who are invitees. This value is stored in the database as I.

Guest - Query IDs who are guests. This value is stored in the database as G.

Both - Query all IDs, regardless of whether they are an invitee or guest.

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions


9 Event Management

Attended Indicator

Radio group that indicates whether you are querying IDs who attended or IDs who did not attend.


Choices are:

Attended - Query IDs who attended the event or function. This value is stored in the database as Y.

Did Not Attend - Query IDs who did not attend the event or function. This value is stored in the database as N.

No Attendance Criteria - Query all IDs, regardless of whether they attended.

Count Number of IDs that meet the selection criteria. This value appears after you enter your selection criteria and go to the next block.

An ID can attend more than one function for the event. If you query all functions for the event (the Function field in the key block is blank), the ID is counted only once in this total, regardless of the number of functions the ID attended.


Source: This value comes from the number of IDs that match your selection criteria. It cannot be changed.

ID ID of the invitee or guest.

Tip: To display attendance details for the ID, click the drop-down arrow. If the ID is an invitee, the Attendance Form (GEAATTD) appears. If the ID is a guest, the Guest Information window appears.

Column: GEVATTD_ID

Source: This value comes from the ID or Guest ID field on the Attendance Form (GEAATTD) or Event Registration Form (GEAATID). It cannot be changed.

Name Name of the invitee or guest.

Column: GEVATTD_FULL_NAME

Source: This value comes from the Name field on the identification form (xxAIDEN) for the associated Banner system. It cannot be changed.

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions


9 Event Management


Column: GEVATTD_FUNC_CODE

Source: This value comes from the Function field on the Attendance Form (GEAATTD) or Event Registration Form (GEAATID). It cannot be changed.

RSVP ID’s response to the invitation. Examples include attending, not attending, and send regrets.

Column: GEVATTD_RSVP_CODE

Source: This value comes from the RSVP field on the Attendance Form (GEAATTD) or Event Registration Form (GEAATID). It cannot be changed.

Fee Status Code ID’s payment status of any fees associated with the function. Examples include paid, partially paid, and due.

Column: GEVATTD_FEES_CODE

Source: This value comes from the Fee Status field on the Attendance Form (GEAATTD) or Event Registration Form (GEAATID). It cannot be changed.

Tickets Number of tickets the ID requested.

Column: GEVATTD_TICKET_CNT

Source: This value comes from the No of Tkts field on the Attendance Form (GEAATTD) or Event Registration Form (GEAATID). It cannot be changed.

Guest Indicates whether the ID has guests.


Source: This value depends on whether guest information is entered on the Attendance Form (GEAATTD) or Event Registration Form (GEAATID). It cannot be changed.

Choices are:

selected - The ID has guests. This value is stored in the database as Y.

cleared - The ID has no guests.

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions


9 Event Management


Use this window to display attendance details for a guest associated with an event or function. This information is display-only and cannot be changed.

Tip: You can tell that an ID is a guest if the Invitee/Guest field in the main window contains the character G. To display the Guest Information window, select the guest ID in the main window and click the down arrow next to the ID field.

Invitee/Guest Code that indicates whether the ID is an invitee or guest.

Column: GEVATTD_INVOLVE_IND

Source: This value depends on whether invitee or guest information is entered on the Attendance Form (GEAATTD) or Event Registration Form (GEAATID). It cannot be changed.

Choices are:

I - The ID is an invitee.

G - The ID is a guest.

Attendance Indicates whether the ID attended the event or function.

Column: GEVATTD_ATTENDANCE_IND

Source: This value comes from the Attended field on the Attendance Form (GEAATTD) or Event Registration Form (GEAATID). It cannot be changed.

Choices are:

selected - The ID attended the event or function. This value is stored in the database as Y.

cleared - The ID did not attend the event or function. This value is stored in the database as N.

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions

Guest ID and name of the guest.

Tip: To display attendance information for the ID who invited this guest, click down arrow. The Attendance Form (GEAATTD) appears.


Source: These values comes from the Guest ID field in the Guest Information window on the Attendance Form (GEAATTD) or Event Registration Form (GEAATID). They cannot be changed.

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions


9 Event Management

Fee Status Payment status of any guest fees associated with the function. Examples include paid, partially paid, and due.

Column: GERATTD_FEES_CODE (code). Not a base table item (description).

Source: These values come from the Fee Status field in the Guest Information window on the Attendance Form (GEAATTD) or Event Registration Form (GEAATID). They cannot be changed.



Source: This value comes from the Fee Date field in the Guest Information window on the Attendance Form (GEAATTD) or Event Registration Form (GEAATID). It cannot be changed.

Menu Code Guest’s menu choice for this function. Examples include baked ham, breakfast buffet, and kosher dinner.

Column: GERATTD_MENU_CODE (code). Not a base table item (description)

Source: These values come from the Menu field in the Guest Information window on the Attendance Form (GEAATTD) or Event Registration Form (GEAATID). They cannot be changed.



Source: This value comes from the Name Tag field in the Guest Information window on the Attendance Form (GEAATTD) or Event Registration Form (GEAATID). It cannot be changed.



Source: This value comes from the Place Card field in the Guest Information window on the Attendance Form (GEAATTD) or Event Registration Form (GEAATID). It cannot be changed.



Source: This value comes from the Comment field in the Guest Information window on the Attendance Form (GEAATTD) or Event Registration Form (GEAATID). It cannot be changed.

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions


9 Event Management

Procedures

To query attendance information

1. Access the Function Attendance Inquiry Form (GEIATTD).


3. To query a specific function, enter the Function code.

OR

To query all functions for the event, leave the Function field blank.

Attended Indicates whether the guest attended the event or function.


Source: This value comes from the Attended check box in the Guest Information window on the Attendance Form (GEAATTD) or Event Registration Form (GEAATID). It cannot be changed.

Choices are:

selected - The guest attended the event or function. This value is stored in the database as Y.

cleared - The guest did not attend the event or function.

Address Type Address type of the guest. Examples include business, mailing, and billing.


Source: This value comes from the Address field in the Guest Information window on the Attendance Form (GEAATTD) or Event Registration Form (GEAATID). It cannot be changed.

Activity Date Date when the guest information was created or last updated.


Invited By ID and name of the invitee who invited this guest.


Source: These values come from the ID field in the main window on the Attendance Form (GEAATTD) or Event Registration Form (GEAATID). They cannot be changed.

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions


9 Event Management

4. Verify your search criteria. Change if necessary.


6. View matching IDs.

To display attendance details for an ID

1. Access the Function Attendance Inquiry Form (GEIATTD).


3. To query a specific function, enter the Function code.

OR

To query all functions for the event, leave the Function field blank.

4. Verify your search criteria. Change if necessary.

5. Go to the next block. Matching IDs appear.

6. Select the ID for which you want to display attendance details.

7. Click down arrow next to the ID field.

8. If the ID is an invitee, the Attendance Form (GEAATTD) appears.

OR

If the ID is a guest, the Guest Information window appears.

Event Function Inquiry Form (GEIFUNC)

Use this form to display summary information for the functions associated with an event. You can query all functions for an event, or you can limit the query by entering selection criteria. Functions appear in chronological order by start date.


• What functions are planned for an event?

• When does each function start and end?

• How much has been spent and received for a function?

Note: Events are initially created on the Event Form (SLAEVNT).

Information comes from the Event Function Form (GEAFUNC). Information is display-only and cannot be changed.


9 Event Management

Main Window

Use this window to display summary information for the functions associated with an event. You can query all functions for an event, or you can limit the query by entering selection criteria. Functions appear in chronological order by start date.

Use the key block to enter the event code associated with the functions you want to query.

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions







Function Function associated with the event. A function is an activity scheduled for a specific date, time, and place. Examples of functions include a reception, dinner, and lecture. The function must be defined on the Event Form (SLAEVNT) or Event Function Form (GEAFUNC).

Column: SSRMEET_FUNC_CODE (code). SSRMEET_FUNC_DESC (description).

Source: These values come from the Function field in the main window on the Event Function Form (GEAFUNC). They cannot be changed.

Function Description (untitled)

Description of the function associated with the event. A function is an activity scheduled for a specific date, time, and place. Examples of functions include a reception, dinner, and lecture. The function must be defined on the Event Form (SLAEVNT) or Event Function Form (GEAFUNC).

Column: SSRMEET_FUNC_DESC

Source: In display mode, this value comes from the Function field in the main window on the Event Function Form (GEAFUNC). It cannot be changed.


9 Event Management


Column: GEBFUNC_ETYP_CODE

Source: This value comes from the Type field in the main window on the Event Function Form (GEAFUNC). It cannot be changed.








Column: GEBFUNC_PURP_CODE

Source: This value comes from the Purpose field in the main window on the Event Function Form (GEAFUNC). It cannot be changed.

Invitation Date Date when invitation letters for the function will be sent.

Column: GEBFUNC_INVITATION_DATE

Source: This value comes from the Date field in the main window on the Event Function Form (GEAFUNC). It cannot be changed.

Confirmation Date

Deadline date when RSVPs must be received.

Column: GEBFUNC_RSVP_CONFIRM_DATE

Source: This value comes from the Response Date field in the main window on the Event Function Form (GEAFUNC). It cannot be changed.

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions


9 Event Management

Procedures

To query functions

1. Access the Event Function Inquiry Form (GEIFUNC).



4. View the functions associated with the event.

5. (Optional) To view details for a function, select the Function. Then select the View Function Detail option on the Options menu.


Column: GEBFUNC_FSTA_CODE


Expense Total amount actually spent for this function to-date.


Source: This value comes from the total Actual Amount field in the Expenses window on the Event Function Form (GEAFUNC). It cannot be changed.

Revenue Total amount actually received for this function to-date.


Source: This value comes from the total Actual Amount field in the Revenue window on the Event Function Form (GEAFUNC). It cannot be changed.

Planned Attendees

Planned number of attendees.

Column: GEBFUNC_PLAN_ATTEND

Source: This value comes from the Planned Attendance field in the main window on the Event Function Form (GEAFUNC). It cannot be changed.

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions


9 Event Management

To display function details

1. Access the Event Function Inquiry Form (GEIFUNC).



4. Select the Function for which you want to display details.

5. Select the View Function Detail option on the Options menu.

6. View function details on the Event Function Form (GEAFUNC).

Individual Function Inquiry Form (GEIIDFN)

Use this form to display attendance and participation information for the events and functions associated with an ID. You can query all events and functions for an ID, or you can limit the query by entering selection criteria.

If the ID is an invitee or guest, attendance information appears in the Attendance block. If the ID is a participant, participation information appears in the Participation block.


• Was the ID an invitee or guest?

• Did the ID send an RSVP?

• Did the ID attend?

• Did the ID have any outstanding fees?

• Was the ID a participant?

• When did the ID participate?

• Was the ID a contact?

• How well did the ID perform as a participant?

Information comes from the Event Registration Form (GEAATID), Attendance Form (GEAATTD), and Function Participant Form (GEAPART). Information is display-only and cannot be changed.

Note: IDs are created ID on the identification form (xxAIDEN) for the associated Banner system.


9 Event Management

Main Window

Use this window to display attendance and participation information for the events and functions associated with an ID. You can query all events and functions for an ID, or you can limit the query by entering selection criteria.

If the ID is an invitee or guest, attendance information appears in the Attendance block. If the ID is a participant, participation information appears in the Participation block.

Information comes from the Event Registration Form (GEAATID), Attendance Form (GEAATTD), and Function Participant Form (GEAPART). Information is display-only and cannot be changed.

Use the key block to identify the ID for whom you are displaying attendance and participation information.

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions

ID ID and name of the invitee, guest, or participant you want to query.


Choices: Choices come from the Person Search Form (SOAIDEN) or Non-Person Search Form (SOACOMP).

Name (untitled) Name of the invitee, guest, or participant you want to query.

Column: Not a base table item.

Event Event for which the ID is an invitee or guest. An event is any occasion that your institution offers or sponsors. Examples include meetings, conferences, and graduation ceremonies. You can query on this field.

Column: GERATTD_EVNT_CRN (code). Not a base table item (description).

Source: These values come from the Event field on the Event Registration Form (GEAATID) or Attendance Form (GEAATD). They cannot be changed.

Choices: Query choices come from the Event Query Form (SLQEVNT).


9 Event Management

Function Function for which the ID is an invitee or guest. A function is an activity associated with an event and scheduled for a specific date, time, and place. Examples of functions include a reception, dinner, and lecture. You can query on this field.

Tip: To display summary information for a function, select the function and click the Search button.

Column: GERATTD_FUNC_CODE

Source: This value comes from the Function field on the Event Registration Form (GEAATIDD) or Attendance Form (GEAATD). It cannot be changed.

Choices: Query choices come from the Function Code Validation (GTVFUNC) list.

Invitee or Guest Code that indicates whether the ID is an invitee or guest. You can query on this field.

Column: GERATTD_INVOLVE_IND

Source: This value depends on whether invitee or guest information is entered on the Attendance Form (GEAATTD) or Event Registration Form (GEAATID). It cannot be changed.

Choices are:

I - The ID is an invitee.

G - The ID is a guest.

Confirmation ID’s response to the invitation. Examples include attending, not attending, and send regrets. You can query on this field.

Column: GERVATTD_RSVP_CODE

Source: This value comes from the Response field on the Attendance Form (GEAATTD) or Event Registration Form (GEAATID). It cannot be changed.

Choices: Query choices come from the RSVP Code Validation (GTVRSVP) list.

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions


9 Event Management

Attend Indicates whether the ID attended the event or function. You can query on this field.


Source: This value comes from the Attended field on the Attendance Form (GEAATTD) or Event Registration Form (GEAATID). It cannot be changed.

Choices are:

selected - The ID attended the event or function. This value is stored in the database as Y.

cleared - The ID did not attend the event or function.

Fee Status ID’s payment status of any fees associated with the function. Examples include paid, partially paid, and due. You can query on this field.

Column: GERATTD_FEES_CODE

Source: This value comes from the Fee Status field on the Attendance Form (GEAATTD) or Event Registration Form (GEAATID). It cannot be changed.

Choices: Query choices come from the Fee Status Validation (GTVFEES) list.

Event Event for which the ID is a participant. An event is any occasion that your institution offers or sponsors. Examples include meetings, conferences, and graduation ceremonies. You can query on this field.

Column: GERPART_EVNT_CRN (code). Not a base table item (description).

Source: These values come from the Event field on the Function Participant Form (GEAPART). They cannot be changed.

Choices: Query choices come from the Event Query Form (SLQEVNT).

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions


9 Event Management

Function Function for which the ID is a participant. A function is an activity associated with an event and scheduled for a specific date, time, and place. Examples of functions include a reception, dinner, and lecture. You can query on this field.

Column: GERPART_FUNC_CODE

Source: This value comes from the Function field on the Function Participant Form (GEAPART). It cannot be changed.

Choices: Query choices come from the Function Code Validation (GTVFUNC) list.

Type Type of participant. Examples include caterers, panelists, and speakers. You can query on this field.

Column: GERPART_PTYP_CODE

Source: This value comes from the Type field on the Function Participant Form (GEAPART). It cannot be changed.

Choices: Query choices come from the Participant Type Code Validation (GTVPTYP) list.

Date Date when the ID is participating in the function. You can query on this field.

Column: GERPART_DATE

Source: This value comes from the Date field on the Function Participant Form (GEAPART). It cannot be changed.

Contact Code that indicates whether the participant is a contact person for the function. You can query on this field.

Column: GERPART_CONTACT_IND

Source: This value comes from the Contact field on the Function Participant Form (GEAPART). It cannot be changed.

Choices are:

none - This participant is not a contact.

P - This participant is the primary contact for the function.

L - This participant is the location contact for the function.

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions


9 Event Management


Use this window to display attendance details for a guest associated with an ID and function. This information is display-only and cannot be changed.

Tip: You can tell that an ID is a guest for the function if the Invitee or Guest field in the Attendance block contains the character G. To display the Guest Information window, select the event in the main window and click the down arrow next to the Event field.

Rating Rating that indicates how well the participant performed. Examples include excellent, unacceptable, and not rated. You can query on this field.

Column: GERPART_RTNG_CODE

Source: This value comes from the Rating field on the Function Participant Form (GEAPART). It cannot be changed.

Choices: Query choices come from the Rating Code Validation (GTVRTNG) list.

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions

Guest ID and name of the guest.


Source: These values comes from the Guest ID field in the Guest Information window on the Attendance Form (GEAATTD) or Event Registration Form (GEAATID). They cannot be changed.

Fee Status Payment status of any guest fees associated with the function. Examples include paid, partially paid, and due.

Column: GERATTD_FEES_CODE (code). Not a base table item (description).

Source: These values come from the Fee Status field in the Guest Information window on the Attendance Form (GEAATTD) or Event Registration Form (GEAATID). They cannot be changed.



Source: This value comes from the Fee Date field in the Guest Information window on the Attendance Form (GEAATTD) or Event Registration Form (GEAATID). It cannot be changed.

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions


9 Event Management

Menu Code Guest’s menu choice for this function. Examples include baked ham, breakfast buffet, and kosher dinner.

Column: GERATTD_MENU_CODE (code).

Not a base table item (description).

Source: These values come from the Menu field in the Guest Information window on the Attendance Form (GEAATTD) or Event Registration Form (GEAATID). They cannot be changed.



Source: This value comes from the Name Tag field in the Guest Information window on the Attendance Form (GEAATTD) or Event Registration Form (GEAATID). It cannot be changed.



Source: This value comes from the Place Card field in the Guest Information window on the Attendance Form (GEAATTD) or Event Registration Form (GEAATID). It cannot be changed.



Source: This value comes from the Comment field in the Guest Information window on the Attendance Form (GEAATTD) or Event Registration Form (GEAATID). It cannot be changed.



Source: This value comes from the Attended check box in the Guest Information window on the Attendance Form (GEAATTD) or Event Registration Form (GEAATID). It cannot be changed.

Choices are:

selected - The guest attended the function. This value is stored in the database as Y.

cleared - The guest did not attend the function.

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions


9 Event Management


Use this window to display information about the function associated with the attendance information or participation information. This window is display-only. No information can be changed.

Address Type Address type of the guest. Examples include business, mailing, and billing.


Source: This value comes from the Address field in the Guest Information window on the Attendance Form (GEAATTD) or Event Registration Form (GEAATID). It cannot be changed.

Activity Date Date when the guest information was created or last updated.


Invited By ID and name of the invitee who invited this guest.


Source: These values come from the ID field in the main window on the Attendance Form (GEAATTD) or Event Registration Form (GEAATID). They cannot be changed.

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions


Column: Not base table items (code and description).

Source: These values come from the Purpose fields in the main window on the Event Function Form (GEAFUNC). They cannot be changed.




. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions


9 Event Management


Column: Not base table items (code and description).

Source: These values come from the Type fields in the main window on the Event Function Form (GEAFUNC). They cannot be changed.






Source: These values come from the Sponsor fields in the main window on the Event Function Form (GEAFUNC). They cannot be changed.

Location Contact



Source: These values come from the Contact fields in the main window on the Function Participant Form (GEAPART). They cannot be changed.



Source: These values come from the Contact fields in the main window on the Function Participant Form (GEAPART). They cannot be changed.




. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions


9 Event Management







Choices are:

selected - The function is scheduled for Mondays. This value is stored in the database as M.

cleared - The function is not scheduled for Mondays.



Choices are:

selected - The function is scheduled for Tuesdays. This value is stored in the database as T.

cleared - The function is not scheduled for Tuesdays.

Wed (Wednesday)




Choices are:

selected - The function is scheduled for Wednesdays. This value is stored in the database as W.

cleared - The function is not scheduled for Wednesdays.

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions


9 Event Management




Choices are:

selected - The function is scheduled for Thursdays. This value is stored in the database as R.

cleared - The function is not scheduled for Thursdays.




Choices:

selected - The function is scheduled for Fridays. This value is stored in the database as F.

cleared - The function is not scheduled for Fridays.




Choices are:

selected - The function is scheduled for Saturdays. This value is stored in the database as S.

cleared - The function is not scheduled for Saturdays.

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions


9 Event Management




Choices are:

selected - The function is scheduled for Sundays. This value is stored in the database as U.

cleared - The function is not scheduled for Sundays













. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions


9 Event Management

Procedures

To query attendance information

1. Access the Individual Function Inquiry Form (GEIIDFN).

2. Enter the ID.

3. Go the next block.

4. View attendance information.

To query participation information


2. Enter the ID.


4. View participation information.

To display attendance details for an ID


2. Enter the ID.


4. Select the Event for which you want to display attendance details.

5. Select the Attendance Detail option in the Options menu. If the ID is a guest, the Guest Information window appears.

OR

If the ID is an invitee, the Attendance Form (GEAATTD) appears.

Function Subject Index Query Form (GEISUBJ)

Use this form to display the subject indexes (keywords) associated with a function’s comments. You can query all subject indexes for a function, or you can limit the query by entering selection criteria. Subject indexes appear in alphabetical order. Information is display-only and cannot be changed.

Subject indexes are initially associated with a function on the Function Comment Form (GEAFCOM). Subject indexes help you search for comments on GEAFCOM at a later time.


9 Event Management



Main Window

Use this window to display the subject indexes (keywords) associated with a function’s comments. You can query all subject indexes for a function, or you can limit the query by entering selection criteria. Subject indexes appear in alphabetical order. Information is display-only and cannot be changed.

Subject indexes are initially associated with a function on the Function Comment Form (GEAFCOM). Subject indexes help you search for comments on GEAFCOM at a later time.

Use the key block to identify the function associated with the subject indexes (keywords).

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions







Function Function you want to query. A function is an activity associated with an event and scheduled for a specific date, time, and place. Examples of functions include a reception, dinner, and lecture. The function must be defined on the Event Form (SLAEVNT) or Event Function Form (GEAFUNC).


Choice: Choices come from the Event Function Inquiry Form (GEIFUNC).


9 Event Management

Procedures

To query subject indexes

1. Access the Function Subject Index Query Form (GEISUBJ).




5. View subject indexes for the function’s comments.

Building Query Form (SLABQRY)

Use this form to display summary information about your institution’s buildings. You can query all buildings, or you can limit the query by entering selection criteria.


• What buildings are located on a specific campus or site?

• What buildings have a specific capacity?

• What buildings have a specific maximum capacity?

Subject Subject index code (keyword) of a comment. Subject index codes are initially associated with a function on the Function Comment Form (GEAFCOM). They are used to help search for comments on GEAFCOM at a later time.

Column: GERSUBJ_SUBJ_CODE (code). Not a base table item (description).

Source: These values come from the Subject field on the Function Comment Form (GEAFCOM). They cannot be changed.

Choices: In query mode, choices come from the Subject Index Validation (GTVSUBJ) list.

Activity Date Date when the comment was created or last updated.

Column: GERSUBJ_ACTIVITY_DATE

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions


9 Event Management

Information comes from the Building Definition Form (SLABLDG). Information is display-only and cannot be changed.

Main Window

The following fields are in this form:

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions

Campus Campus where the building is located. This value comes from the Campus field in the main window on the Building Definition Form (SLABLDG). It cannot be changed. Query choices come from the Campus Validation (STVCAMP) list.

Column: SLBBLDG_CAMP_CODE

Site Site location, within a campus, where the building is located. This value comes from the Site field in the main window on the Building Definition Form (SLABLDG). It cannot be changed. In query mode, choices come from the Site Validation (STVSITE) list.

Column: SLBBLDG_SITE_CODE

Building Building used at your institution for student housing, classes, events, and functions. This value comes from the Building field in the main window on the Building Definition Form (SLABLDG). It cannot be changed. In query mode, choices come from the Building Code Validation (STVBLDG) list.

Column: SLBBLDG_BLDG_CODE (code). Not a base table item (description)

Capacity Normal capacity of the building. This value comes from the Capacity field in the main window on the Building Definition Form (SLABLDG). It cannot be changed.

Tip: In query mode, use the sign < to query capacities less than a specific value. Use the sign > to query capacities greater than a specific value. For example, enter <100 to query capacities less than 100 or >200 to query a capacities over 200.

Column: SLBBLDG_CAPACITY


9 Event Management

Procedures

To query buildings

1. Access the Building Query Form (SLABQRY).

2. (Optional) To refine your query, enter selection criteria.

3. Select Execute Query.

4. View information for the matching buildings.

Building/Room Schedule Form (SSAMATX)

Use this form to display information about buildings and rooms scheduled for events, functions, and courses. You can query all scheduled buildings and rooms, or you can limit the query by entering selection criteria.

This form helps you resolve building, room, and time conflicts by answering the following kinds of questions:

• When is a building or room scheduled for use?

• What is the meeting pattern for a building or room?

• What events, functions, and courses are scheduled for a building or room?

Information comes from the form where the event, function, or course was scheduled:



• Schedule Form (SSASECT)

Maximum Absolute maximum capacity of the building. If this value is greater than the normal capacity, extra people can be assigned to the building. This value comes from the Maximum field in the main window on the Building Definition Form (SLABLDG). It cannot be changed.

Tip: In query mode, use the sign < to query capacities less than a specific value. Use the sign > to query capacities greater than a specific value. For example, enter <100 to query capacities less than 100 or >200 to query a capacities over 200.

Column: SLBBLDG_MAXIMUM_CAPACITY

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions


9 Event Management

Information is display-only and cannot be changed.

Main Window

Use this window to display information about buildings and rooms scheduled for various functions.

This window contains three panes:

• The left pane identifies the building, room, and campus.

• The middle pane displays scheduling information such as the meeting pattern, begin date, and end date.

• The right pane identifies the course, event, or function scheduled for the building or room.

Use the items in the Options Menu (Days, Times, Term, Dates, Courses, X/L, and Function) to display specific sections on the panes.

Query Instructions

Before you execute a query, the form displays the Building and Room fields, the Days of the Week check boxes in the scroll box, and the Subject field. After you have entered and executed your query, you may view the information which is displayed in a series of scroll boxes or windowpanes. As you move through the fields or use the horizontal scroll bars, additional fields are displayed.

Your global term (the term last used in some other form) will automatically roll into this form as the Query Term. You can enter a different term in the Term field in the scroll box and then choose Search to query the database.

Note: Until you execute a query, the Query Term field will not reflect the term being queried.

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions

Building Building scheduled at your institution for courses, events, or functions. In query mode, choices come from the Building Code Validation (STVBLDG) list.

Source: This value comes from the Building field on the form where the building was scheduled:




The source cannot be changed.



9 Event Management

Room Room scheduled at your institution for courses, events, or functions.

Source: This value comes from the Room field on the form where the room was scheduled:





Column: SSRMEET_ROOM_CODE

Campus Campus where the scheduled building is located. In query mode, choices come from the Campus Validation (STVCAMP) list.

Source: This value comes from the Campus field in the main window on the Building Definition Form (SLABLDG). It cannot be changed.

Column: SLBBLDG_CAMP_CODE

Mon (Monday) Code or checkbox that indicates whether the building or room is scheduled for Mondays.

In query mode, this field appears as a checkbox. In display mode, a character string indicates the days in the meeting pattern (for example, MWF). Choices are:

selected -- Monday is in the meeting pattern. This value is stored in the database as M.

cleared -- Monday is not in the meeting pattern.

Source: This value comes from the Mon field on the form where the building or room was scheduled:






. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions


9 Event Management

Tue (Tuesday) Code or checkbox that indicates whether the building or room is scheduled for Tuesdays.


selected -- Tuesday is in the meeting pattern. This value is stored in the database as T.

cleared -- Tuesday is not in the meeting pattern.

Source: This value comes from the Tue field on the form where the building or room was scheduled:





Column: SSRMEET_TUE_DAY

Wed (Wednesday)

Code or checkbox that indicates whether the building or room is scheduled for Wednesdays.


selected -- Wednesday is in the meeting pattern. This value is stored in the database as W.

cleared -- Wednesday is not in the meeting pattern.

Source: This value comes from the Wed field on the form where the building or room was scheduled:






. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions


9 Event Management

Thu (Thursday) Code or checkbox that indicates whether the building or room is scheduled for Thursdays.


selected -- Thursday is in the meeting pattern. This value is stored in the database as R.

cleared -- Thursday is not in the meeting pattern.

Source: This value comes from the Thu field on the form where the building or room was scheduled:






Fri (Friday) Code or checkbox that indicates whether the building or room is scheduled for Fridays.


selected -- Friday is in the meeting pattern. This value is stored in the database as F.

cleared -- Friday is not in the meeting pattern.

Source: This value comes from the Fri field on the form where the building or room was scheduled:






. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions


9 Event Management

Sat (Saturday) Code or checkbox that indicates whether the building or room is scheduled for Saturdays.


selected -- Saturday is in the meeting pattern. This value is stored in the database as S.

cleared -- Saturday is not in the meeting pattern.

Source: This value comes from the Sat field on the form where the building or room was scheduled:





Column: SSRMEET_SAT_DAY

Sun (Sunday) Code or checkbox that indicates whether the building or room is scheduled for Sundays.


selected -- Sunday is in the meeting pattern. This value is stored in the database as U.

cleared -- Sunday is not in the meeting pattern.

Source: This value comes from the Sun field on the form where the building or room was scheduled:






. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions


9 Event Management

Begin Time Time when the scheduled course, event, or function starts. Format is HHMM in 24-hour military time.

Source: This value comes from the Begin Time field on the form where the building or room was scheduled:






End Time Time when the scheduled course, event, or function ends. Format is HHMM in 24-hour military time.

Source: This value comes from the End Time field on the form where the building or room was scheduled:






Term Term associated with the displayed scheduling information. For a course, the term code for the course appears. For an event or function, the word Event appears. In query mode, choices come from the Term Code Validation (STVTERM) list.

Source: For courses, this value comes from the Term field on the Schedule Form (SSASECT). It cannot be changed. For events and functions, the word Event always appears. It cannot be changed.

Column: SSRMEET_TERM_CODE

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions


9 Event Management

Start Date Date when the scheduled course, event, or function starts.

Source: This value comes from the Start Date field on the form where the building or room was scheduled:





Tips: To query all buildings and rooms scheduled on or after the start date, leave the end date blank. To query all buildings and rooms scheduled on or before the end date, leave the start date blank.


End Date Date when the scheduled course, event, or function ends.

Source: This value comes from the End Date field on the form where the building or room was scheduled:





Tips: To query all buildings and rooms scheduled on or after the start date, leave the end date blank. To query all buildings and rooms scheduled on or before the end date, leave the start date blank.


Subject Subject or event scheduled for the building or room. In query mode, choices come from the Subject Validation (STVSUBJ) list.

Note: In query mode, this field is labelled Subject. When you execute the query, the label changes to Course/CRN/Cross List. For courses, the subject code is the first value in this field. For events, the event code is in this field.

Source: For courses, this value comes from the Subject field on the Schedule Form (SSASECT). It cannot be changed. For events and functions, this value comes from the Event field on the Event Form (SLAEVNT) or Event Function Form (GEAFUNC). It cannot be changed.

Column: SSBSECT_SUBJ_CODE

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions


9 Event Management

Course Course number scheduled for the building or room.

Note: In query mode, this field is unlabelled. When you execute the query, the label Course/CRN/Cross List appears. The course number is the second value in this field.

Source: This value comes from the Course Number field on the Schedule Form (SSASECT). It cannot be changed.

Column: SSBSECT_CRSE_NUMB

CRN (Course Reference Number)

Reference number of the course scheduled for the building or room.

Note: In query mode, this field is labeled CRN. When you execute the query, the label changes to Course/CRN/Cross List. The course reference number is the third value in this field.

Source: This value comes from the Course Number field on the Schedule Form (SSASECT). It cannot be changed.

Column: SSRMEET_CRN

Cross List Cross list group code.

Note: In query mode, this field is labeled X/L. When you execute the query, the label changes to Course/CRN/Cross List. The cross list group code, if it exists, is the fourth value in this field.

Source: This value comes from the Cross List field on the Schedule Form (SSASECT). It cannot be changed.

Column: SSRXLST_XLST_GROUP

Function Function scheduled for the building or room. In query mode, choices come from the Function Code Validation (GTVFUNC) list.

Note: When you execute a query, the event code associated with the function appears in the Course/CRN/Cross List field.

Source: This value comes from the Function field on the Event Form (SLAEVNT) or Event Function Form (GEAFUNC). It cannot be changed.

Column: SSRMEET_FUNC_CODE

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions


9 Event Management

Procedures

To query scheduled buildings and rooms

1. Access the Building Room Schedule Form (SSAMATX).



4. View information for the scheduled buildings and rooms.

To query buildings and rooms scheduled for events and functions:


2. Enter EVENT in the Term field.

3. (Optional) Enter the function code.



6. View information for the scheduled buildings and rooms.

To query buildings and rooms scheduled for courses


2. Enter selection criteria in any of the Subject, Course, CRN, and Cross List fields.

3. (Optional) To refine your query, enter any other selection criteria.


View information for the scheduled buildings and rooms.

Query Term Term associated with the displayed scheduling information.

Source: This value comes from your query entry in the Term field in the middle pane of this form. If you do not enter a term, this field shows ALL. It cannot be changed.


. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions


9 Event Management

Forms Used by the Banner Advancement System

The Advancement System includes its own menu (*ALUEVENT) with the Event Management forms. In addition to all the Event Management forms that normally appear in the General System, the Advancement System includes the Function Affiliation Form (AEAAFIL). The Advancement System must be installed at your institution for this form to appear on a menu.

For more information, please refer to the Advancement documentation.


9 Event Management



Chapter 10

General Web Management

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-3

10 General Web ManagementValidation Forms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-3


Forms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-5

Third Party Access Form . . . . . . . . . . . . . . . . . . . . (GOATPAC) . . . . . 10-6Third Party Access Audit Form . . . . . . . . . . . . . . . . . (GOATPAD) . . . . . 10-9E-mail Address Form . . . . . . . . . . . . . . . . . . . . . . (GOAEMAL) . . . . . 10-14Address Role Privileges Form . . . . . . . . . . . . . . . . . . (GOAADRL) . . . . . 10-17Address Review and Verification Form . . . . . . . . . . . . . (GOAADDR). . . . . 10-18Directory Options Rule Form . . . . . . . . . . . . . . . . . . (GOADIRO) . . . . . 10-21Web User Directory Profile Form . . . . . . . . . . . . . . . . (GOADPRF) . . . . . 10-22Survey Response Query Form . . . . . . . . . . . . . . . . . . (GOISRVY). . . . . . 10-23Survey Definition Form . . . . . . . . . . . . . . . . . . . . . (GUASRVY) . . . . . 10-24Survey Summary Query Form . . . . . . . . . . . . . . . . . . (GUISRVS) . . . . . . 10-27Third Party Procedures and Parameters Form . . . . . . . . . . (GOAFNXR) . . . . . 10-29Third Party Electronic Control Rules Form . . . . . . . . . . . (GORTCTL) . . . . . 10-31Enterprise PIN Preferences Form . . . . . . . . . . . . . . . . (GUAPPRF) . . . . . 10-33Directory Item Validation Form . . . . . . . . . . . . . . . . . (GTVDIRO) . . . . . 10-36E-mail Address Type Validation Form . . . . . . . . . . . . . . (GTVEMAL) . . . . . 10-36

10-1

Table of Contents




Overview


The General Web Management module supports the integrated processing between Banner and your Web applications (Student Self-Service, Faculty/Advisor Self-Service, Employee Self-Service, Advancement Self-Service, Finance Self-Service, and Executive Self-Service). Some of the functions you can perform in the General Web Management module are:

• Associate address type codes with user roles and access privileges.

• Display addresses added or changed within Banner or via the Web.

• Define PINs and other user parameters for third-party access products.

• Define controls for Banner interfaces with third-party products.

• Identify the kinds of information that are included in your student, employee, and alumni directories.

• Define the profile information that appears on the Web directory for an ID.

• Record one or more e-mail addresses for any Banner ID.

• Set up and track surveys.

General Web

Management

Refer to the Banner Middle Tier Implementation Guide for more information.

Validation Forms

General Web Management forms use the following validation forms. Refer to Chapter 2, Validation Forms, for additional information.


GTVDIRO Directory Item Validation Form GOADPRF Web User Directory Profile Form

GTVEMAL E-mail Address Type Validation Form GOAEMAL E-mail Address Form

GTVSYSI System Indicator Validation Form GORTCTL Third Party Electronic Control Rules Form

STVASRC Address Source Validation Form GOAADDR Address Review and Verification Form

STVATYP Address Type Code Validation Form GOAADDR Address Review and Verification FormGOAADRL Address Role Privileges FormGOADIRO Directory Options Rule Form

STVCNTY County Code Validation Form GOAADDR Address Review and Verification Form




Forms in the General Web Management module can be accessed from the following menu.

STVNATN Nation Code Validation Form GOAADDR Address Review and Verification Form

STVSTAT State/Province Code Validation Form GOAADDR Address Review and Verification Form

STVTELE Telephone Type Validation Form GOADIRO Directory Options Rule Form


. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . General Web Management Menu (*GENWEB)

GOATPAC Third Party Access FormUpdates PIN information and provides mechanism for resetting a PIN.

GOATPAD Third Party Access Audit FormEstablishes PINs and PIN information for accessing third party products.

GOAEMAL E-mail Address FormRecords one or more e-mail addresses for any Banner ID.

GOAADRL Address Role Privileges FormAssociates address type codes from the Address Type Code Validation Form (STVATYP) with user roles and access privileges.

GOAADDR Address Review and Verification FormDisplays addresses added or changed within Banner or via the Web.

GOADIRO Directory Options Rule FormIdentifies the kinds of information that are included in your student, employee, and advancement Web directories.

GOADPRF Web User Directory Profile FormDefines the profile information that appears on the Web directory for an ID.

GOISRVY Survey Response Query FormDisplays responses to surveys, by person.

GUASRVY Survey Definition FormDefines a survey.



Forms

This section describes each form in the General Web Management module. Forms are described in the order they appear on the General Web Management Menu (*GENWEB).

GUISRVS Survey Summary Query FormDisplays responses to surveys, by survey.

GOAFNXR Third Party Procedures and Parameters Form (GOAFNXR)Allows you to view functions and transactions used by third-party products.

GORTCTL Third Party Electronic Control Rules FormDefines controls for Banner interfaces with third-party products.

GUAPPRF Enterprise PIN Preferences FormDefines institutional preferences for handling PINs.

GTVDIRO Directory Item Validation FormDefines codes for the types of information included in directory profiles.

GTVEMAL E-mail Address Type Validation FormDefines e-mail address type codes (for example, business, personal, and school).

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . General Web Management Menu (*GENWEB)



Third Party Access Form (GOATPAC)

Use this form to:

• Enter or update current PIN information for a user.

• Reset a user’s PIN and PIN expiration date. The next time the user logs in to a third party product, he/she sees or hears a message explaining that the PIN has expired and must be changed immediately.

PINs are used to access third party products such as Voice Response, Campus Pipeline, and the Web.

Warning: The major difference between GOATPAC and the Third Party Access Audit Form (GOATPAD) is the security assigned to the two forms. GOATPAC is available to various administrative users. GOATPAD should be restricted to key security administrators. PIN information should be protected and accessed only when security administrators need to research PIN questions and problems.

The PIN reset feature uses the institutional preferences specified on the Enterprise PIN Preferences Form (GUAPPRF).

Key Block

Third Party Information Block

Use this block to enter or update current PIN information for a user.

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions

ID Identification number of the user whose PIN information is being accessed on this form.

(lookup) List Person Search Form (SOAIDEN)



. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions

PIN Disabled Indicates whether the PIN is disabled:

selected The PIN is disabled. The user cannot access the product, even if the correct user ID and PIN are entered.

cleared The PIN is enabled. The user can access the product if the correct user ID and PIN are entered (default).

There are three ways a PIN can be disabled:

• An administrative user can manually select this check box.

• The security administrator can manually disable the PIN on the Third Party Access Audit Form (GOATPAD).

• The PIN is automatically disabled if the user exceeds the number of invalid login attempts specified on the Web Rules page in WebTailor.

PIN Expiration Date

Date when the end user must change his or her PIN. There are four ways this date can be assigned:

• An administrative user can manually assign this date on this form.

• The security administrator can manually assign this date on the Third Party Access Audit Form (GOATPAD).

• This date is automatically assigned if the end user changes his/her PIN and a rule for PIN expiration days is specified on the Customize Web Rules page in WebTailor.

• This date is automatically set to one day before the current date if the PIN is reset on this form or on GOATPAD.



Web Access Terms Accepted

Indicates whether the terms of usage for third-party products have been accepted:

selected Terms of usage have been accepted. They are not displayed when the user accesses the product.

cleared Terms of usage have not been accepted yet. They will be displayed the next time the user logs in. The user must agree to these terms before proceeding. After agreeing to the terms, the check box is automatically selected and the terms will not be displayed on subsequent logins.

You may want to clear this indicator if your terms of usage change and you want the user to see the new terms.

Last Web Access Date

Date when the user last accessed a Banner self-service product. Display-only.

Reset PIN Resets the PIN and PIN expiration date:

• If the PIN Reset Value on the Enterprise PIN Preferences Form (GUAPPRF) is set to Birthdate, the PIN is reset to the end user’s six-digit birth date. The date format is based on the default date format specified on the Installation Control Form (GUAINST). If the user does not have a birth date, the last six numeric digits of the Banner ID are used. (If there is neither a birth date nor six numeric digits at the end of the Banner ID, an error message is displayed.)

• If the PIN Reset Value on the Enterprise PIN Preferences Form (GUAPPRF) is set to Random Value, the PIN is reset to a random value. It will be either numeric or alphanumeric, depending on the value in the PIN Reset Format field on GUAPPRF.

• The PIN expiration date is set to one day before the current date.

Third Party ID Unique internal ID used by Campus Pipeline to route e-mail. Display-only.

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions



Third Party Access Audit Form (GOATPAD)

Security administrators can use this form to:

• Assign a new PIN

• Change PIN information

• Review current and historic PIN information

• Generate or update the third party ID

PINs are used to access third-party products such as Voice Response and Campus Pipeline/Luminis.

Warning: The major difference between GOATPAD and the Third Party Access Form (GOATPAC) is the security assigned to the two forms. GOATPAC is available to various administrative users. GOATPAD should be restricted to key security administrators. PIN information should be protected and accessed only when security administrators need to research PIN questions and problems.

For more information about setting up and maintaining PINs, refer to the “PINs” chapter of the WebTailor User Guide.

LDAP User ID The mapping between the Banner ID and the LDAP User ID. This allows LDAP to use the settings in Banner General to regulate how the user’s credentials are authenticated for non-Luminis institutions. You can store the mapping for your self-service users in this field, or on your LDAP server. Optional.

Note: If you are using an LDAP server to authenticate your users’ credentials for Banner Self-Service, none of the fields on GOATPAC will contain valid data for your users.

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions



Key Block

Current Third Party Information Block

Use this block to enter or update current PIN information for the user.

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions

ID Identification number of the user whose PIN information is being accessed on this form.


. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions

PIN Personal identification number (PIN) the user uses to access third-party products. The PIN must be six characters long due to Voice Response integration requirements. It can be numeric or alphanumeric, depending on the institution’s preference as defined on the Enterprise PIN Preferences Form (GUAPPRF).

Note: Voice Response requires numeric PINs.

(button) Resets the PIN and PIN expiration date. The PIN is reset to either the end user’s six-digit birthdate or a random value, depending on what was set up on GUAPPRF. The PIN expiration date is set to one day before the current date.

If the PIN Reset Value on GUAPPRF is Birthdate, the date format used is based on the default date format specified on the Installation Control Form (GUAINST). If the user does not have a birthdate, the last six numeric digits of the Banner ID are used. (If there is neither a birthdate nor six digits at the end of the Banner ID, an error message is displayed.)

If the PIN Reset Value on GUAPPRF is set to Random Value, the PIN is reset to a random value. It will be either numeric or alphanumeric, depending on the value in the PIN Reset Format field on GUAPPRF.



Disabled Indicates whether the PIN is disabled:

selected The PIN is disabled. The user cannot access the product, even if the correct user ID and PIN are entered.

cleared The PIN is enabled. The user can access the product if the correct user ID and PIN are entered (default).

There are three ways a PIN can be disabled:

• The security administrator can manually select this check box.

• An administrative user can manually disable the PIN on the Third Party Access Form (GOATPAC).

• The PIN is automatically disabled if the user exceeds the number of invalid login attempts specified on the Customize Web Rules page in the WebTailor module.

If a PIN in changed on this form, the Disabled value does not change.

Accepted Indicates whether the terms of usage for third-party products have been accepted:

selected Terms of usage have been accepted. They are not displayed when the user accesses the product.

cleared Terms of usage have not been accepted yet. They will be displayed the next time the user logs in. The user must agree to these terms before proceeding. After agreeing to the terms, the check box is automatically selected and the terms will not be displayed on subsequent logins. When a new PIN is created, this check box is cleared by default.

If a PIN in changed on this form, the Accepted value does not change.

You may want to clear this indicator if your terms of usage change and you want the user to see the new terms.

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions



Expiration Date Date when the end user must change his/her PIN. There are four ways this date can be assigned:

1. The security administrator can manually assign this date on this form.

2. An administrative user can manually assign this date on the Third Party Access Form (GOATPAC).

3. This date is automatically assigned if the end user changes his/her PIN and a rule for PIN expiration days is specified on the Customize Web Rules page in the WebTailor module.

4. This date is automatically set to one day before the current date if the PIN is reset on this form or on GOATPAC.

An expiration date is not assigned when a PIN is added or changed.

User ID User ID that added or changed the PIN. This can be the end user, an administrative user, or the security administrator, depending on who made the change. Display-only.

Web Last Access Date

Date when the user last accessed a Banner self-service product. Display-only.

Activity Date Date when PIN information was added or changed. Display-only.

Third Party ID Unique internal ID used by Campus Pipeline/Luminis to route e-mail. If you enter the ID manually, it cannot already exist in the system for another person. (It can, however, be a previous third party ID for the same person.) Available characters are lowercase letters, numbers, periods, hyphens, and underscores. You can also click the associated button to generate an ID.

(button) Generates an ID. The ID is constructed from the first character of the user’s first name and up to seven characters of the user’s last name. Nonalphabetic characters other than periods, hyphens, and underscores are removed. If the ID is not unique, the last digit(s) are replaced with one-up numbers until the ID is unique.

Sourced ID System-generated, one-up number used to synchronize the user’s data with various SunGard Higher Education partner systems. The ID is unique for the PIDM. Display-only.

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions



LDAP User ID The mapping between the Banner ID and the LDAP User ID. This allows LDAP to use the settings in Banner General to regulate how the user’s credentials are authenticated for non-Luminis institutions. You can store the mapping for your self-service users in this field, or on your LDAP server. Optional.

If you are using an LDAP server to authenticate your users’ credentials for Banner Self-Service, the following fields on GOATPAD are ignored:

• PIN

• PIN Hint Question

• PIN Hint Response

• Expiration Date

If the Disable indicator is selected, the user will receive an error message when attempting to login to Banner Self-Service:

Error mapping LDAP attribute to Self Service

PIN Hint Question

If the Web user forgets his or her PIN, they can view this question. It is set up by the user the first time they access Banner Self-Service.

PIN Hint Response

The answer to the PIN Hint Question. It should not be the actual PIN, but it should remind the user of what the PIN is.

Activity Source Identifies the method used to create or reset the PIN:

• Self - The Web user submitted the PIN change via a web application.

• Admin - An administrative user reset the PIN, either manually or with the reset feature on the Third-Party Access Form (GOATPAC) or the Third-Party Access Audit Form (GOATPAD).

• System - The system inserted or changed information on the PIN record because the user logged on to one of the Banner Self-Service applications for the first time and accepted the Terms of Agreement.

• Mass - The system inserted or changed information on the PIN record via the PIN Mass Create and Table PIN Create processes.

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions



Third Party History Information Block

Use this block to display information about previous PIN changes for the user. All fields are display-only.

E-mail Address Form (GOAEMAL)

Use this form to record one or more e-mail addresses for any Banner ID.

Note: This form will allow you to specify if an e-mail address, regardless of type, should appear on the web.

The Web check box on the E-Mail Address Type Validation Form (GTVEMAL) does not determine this; instead, it specifies if this type of e-mail address will be included in LOVs on the web.

Use this form to set up one or more e-mail addresses for any Banner ID. A user can have multiple e-mail addresses of the same e-mail address type (for example, personal and professional). Only one address, however, can be designated as the preferred address.

A duplicate is defined as one ID having two or more records with the same e-mail type and e-mail address.

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions

PIN Personal identification number (PIN) used to access third-party products.

Third Party ID Internal ID used by Campus Pipeline/Luminis to route e-mail.

Change Code that identifies the type of change:

I The third-party ID was changed.

P The PIN was changed.

User ID User ID that added or changed the PIN. This can be the end user, an administrative user, or the security administrator, depending on who made the change.

Activity Date Date when PIN information was added or changed.



Main Window

Use this window to establish one or more e-mail addresses for any Banner ID.

Key Block

Use this block to identify the person for whom you want to establish an e-mail address..

E-Mail Address Block

Use this block to enter e-mail address information for the person.

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions

ID ID and name of the person for whom you are establishing an e-mail address.


Choices: Choices come from the Person Search Form (SOAIDEN).

(untitled) Name of the person for whom you are establishing an e-mail address.


. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions

E-mail Type Type of e-mail address. Examples include personal and business. The ID cannot have more than one e-mail address of the same type.

Column: GOREMAL_EMAL_CODE (code)Not a base table item (description)

Choices come from the E-Mail Type Validation (GTVEMAL) list.

E-mail Address Full e-mail address. Include required syntax and punctuation.

Note: The accuracy of this field is determined only by user maintenance.

Column: GOREMAL_EMAIL_ADDRESS



Preferred Indicates whether the e-mail address is the preferred contact address. Only one e-mail address can be the preferred address.

Note: If a preferred address becomes Inactive, the preferred status is automatically removed.

Column: GOREMAL_PREFERRED_IND

Choices are:

selected - This e-mail address is preferred. This value is stored in the database as Y.

cleared (default) - This e-mail address is not preferred. This value is stored in the database as N.

Inactivate Indicates the status of this e-mail address.

Column: GOREMAL_STATUS_IND

Choices are:

selected - This e-mail address is inactive. If the preferred address is made inactive, the preferred status is automatically removed. This value is stored in the database as I.

cleared (default) - This e-mail address is active. This value is stored in the database as A.

Display on Web Indicates whether this e-mail address may appear on the web.

Column: GOREMAL_DISP_WEB_IND

Choices are:

selected (default) - This e-mail address may appear on the web. This value is stored in the database as Y.

cleared - This e-mail address may not appear on the web. This value is stored in the database as N.

URL Indicates whether this e-mail address is a Uniform Resource Locator (URL).


Choices are:

selected - This e-mail address is a URL.

cleared - This e-mail address is not a URL.

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions



Procedures

To add an e-mail address

1. Access the E-Mail Address Form (GOAEMAL).

2. Enter the user ID.

3. Enter the E-mail Type.

4. Enter the ID’s E-mail Address information. Use the required syntax and punctuation.

5. (Optional) If the ID has multiple e-mail addresses and this is the preferred one, select the Preferred check box.

6. (Optional) If the e-mail address should appear in Banner Self-Service on the web, select the Display on Web check box.

7. (Optional) If the e-mail type has been designated as a URL on GTVEMAL, then the URL check box will automatically be selected.

8. Save.

Address Role Privileges Form (GOAADRL)

Use this form to associate address type codes from the Address Type Code Validation Form (STVATYP) with user roles and access privileges. Information on this form determines which roles can access and update each address type on the Web.

The Role field must be set to ALUMNI, FACULTY, STUDENT, FRIEND, or EMPLOYEE. Valid values for the Privileges field are U (update), D (display), or N (none).

Comment Comments about the e-mail address.

Column: GOREMAL_COMMENT

Activity Date Date the record was created or last changed.

User ID of the person who created or last changed the record.

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions



Address Review and Verification Form (GOAADDR)

Use this form to display addresses added or changed within Banner or via the Web. You can display all new and changed addresses, or you can limit the view based on a user, date range, and/or source.

You cannot add or delete an address with this form, but you can update address information.

Special Note

Due to the introduction of APIs, it is possible that you have performance issues if you do not enter data into the key block before performing a query or changing data. This is because this form displays information from multiple tables.

SunGard Higher Education expects to correct this in a future release. It is recommended that, for now, you perform queries and updates in two steps:

1. Enter the queries without data in the key block.

2. Re-query those addresses using key block data and update them then.

However, you will not experience the performance issues if you enter data in the key block before performing the query or update.

Main Window

Key Block

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions

User ID User ID who entered or changed addresses. If this field is entered, only those addresses entered or changed by this ID appear on this form.

(button) Count Hits Enterprise Access Control Form (GOAEACC)

Activity Date Search From/Activity Date Search To

Period of time when addresses were entered or changed. If one or both dates are entered, only those addresses entered or changed in that time period appear on this form.

To display addresses entered or updated after a certain date, enter the From date and leave the To date blank.

To display addresses entered or updated before a certain date, leave the From date blank and enter the To date.



Address Block

Source Source of the address information. If this field is entered, only those addresses from that source appear on this form.

(lookup) List Address Source Code Validation (STVASRC) list

Not Reviewed/Reviewed

Check boxes that indicate whether you are searching for verified or unverified addresses.

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions

ID ID for whom address information is displayed. Display-only.

Reviewed Indicates whether the address has been reviewed:

selected The address was reviewed (Y is stored in the database).

cleared The address was not reviewed.

By User ID of the person who reviewed the address. Display-only.

Name Name for whom address information is displayed.

From DateTo Date

Dates when the address starts and stops being effective. Leave blank if the address is always effective.

Inactivate Address

Indicates whether the address is inactive:

selected Inactive (I is stored in the database)

cleared Active

Address Type Address type associated with the ID.

(lookup) List Address Type Validation (STVATYP) list

(lookup) Count Hits Address Summary Form (SOADDRQ)

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions



Source Source of the address information.

(lookup) List Address Source Validation (STVASRC) list

Sequence Number

Internal sequence number assigned to each address type associated with the ID. Display-only.

Street Line 1Street Line 2Street Line 3

Street address.

City City.

State or Province

State or province.

(lookup) List State/Province Code Validation (STVSTAT) list

ZIP or Postal Code

ZIP or postal code.

(button) List ZIP/Postal Code Validation Form (GTVZIPC)

Delivery Point Delivery point information used for bar coding.

Correction Digit Correction digit used for bar coding.

Carrier Route Carrier route associated with the ID’s address.

County County.

(lookup) List County Code Validation (STVCNTY) list

Nation Nation.

(lookup) List Nation Validation (STVNATN) list

Telephone Type Telephone type code.

(lookup) List Telephone Type Validation (STVTELE) list

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions



Directory Options Rule Form (GOADIRO)

Use this form to identify the kinds of information that are included in your student, employee, and alumni Web directories. An HTML page lists address and phone information for each student, employee, or alumnus, in alphabetical order by last name or department. Online Web readers can use these links to go to different letters of the alphabet to find other listings.

The value in the Directory Item Code field identifies the type of directory information. This includes name, permanent address, permanent telephone number, e-mail address, FAX number, business address, and business telephone number. For students you can also have school, expected graduation year, campus address, campus telephone number, and college affiliation. For employees you can also have position title, department, office address, and office telephone number. For alumni you can also have home address, home telephone number, class year, maiden name, and preferred college.

The Display in Directory indicator tells you which Web directories can include the item.

Fields on the right side of the form lets you set options for each kind of directory information:

• Include in Profile - indicates whether the information appears in the directory.

• Update in Profile - indicates whether the user can choose to have the information appear in the directory.

• Default to Directory - indicates which profile information defaults to the directory if a user does not have a directory profile set up.

The Address and Telephone Type Information window is used to enter address and telephone types. The priority determines which addresses and telephone numbers are displayed and/or updated.

Telephone Area code, phone number, and extension.

(button) Count Hits Telephone Form (SPATELE)

User User who entered or changed the address. Display-only.

Activity Date Date when the address was entered or last changed. Display-only.

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions



Web User Directory Profile Form (GOADPRF)

Use this form to define the profile information that appears on the Web directory for an ID. You can optionally build a profile based on default profile information for the ID’s self-service roles (faculty, student, employee, or alumni).

Note: Once a PIN is assigned to a user, the user can update his or her own profile via the Web.

Key Block

Directory Block

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions

ID ID of the Web user.



. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions

Directory Item Code

Code that identifies the type of information included in the directory profile.

(lookup) List Directory Item Validation (GTVDIRO) list

Description Description of the directory item code. Display-only.

Display in Directory

Check box that indicates whether the item appears in the Web directory.

selected Item is displayed (Y is stored in the database). This is the default.

cleared Item is not displayed (N is stored in the database).

User ID User who entered or changed the profile. Display-only.

Activity Date Date when the profile was created or last changed. Display-only.



Survey Response Query Form (GOISRVY)

Use this form to display responses to surveys, by person. Survey responses entered via the Web automatically update this form.

Main Window

Use this window to display general information about survey responses.

Key Block

Responses Block

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions

ID ID of the Web user who responded to the surveys.

(button) Count Hits Person Search Form (SOAIDEN)

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions

Survey Name of the survey or surveys to which the ID has responded. They can be in progress, completed, or declined. Display-only.

Title Description of the survey for which the ID is a desired respondent. Display-only.

Complete Indicates whether the ID completed the survey.

selected ID completed the survey.

cleared ID did not complete the survey.

Display-only.

Declined Indicates whether the ID declined responding to the survey.

selected ID declined the survey.

cleared ID did not decline the survey.

Display-only.

Activity Date Date when the ID responded to the survey. Display-only.



Questions Window

Use this window to display the user’s response to each question in the survey.

Survey Definition Form (GUASRVY)

Use this form to define the following information for a survey:

• Whether the survey appears on the Web

• Date range when the survey appears on the Web

• Description that appears on the Web

• Questions and valid responses in the survey

• Web products and populations that can access the survey

Main Window

Use this window to describe the survey and optionally to identify a population of Banner IDs that can respond to the survey.

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions

Question # Number and text of each question in the survey. Use the scroll bar to display each question in the survey. Display-only.

If the question is too long to display in this field, select Edit to display the complete question in the Editor window.

Response [n] Possible responses to the question. A question can have up to five possible responses. The check box indicates which response the respondent chose. The text of the response appears in the field next to the check box. Display-only.

Comments Free-form comments entered by the respondent. Display-only.

If the comments are too long to display in this field, select the Comments icon to display the complete comments in the Editor window.

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions

Survey Name of the survey. The maximum length is 15 characters.

Title Description of the survey that appears if the survey is displayed on the Web. You can query on this field.



Survey Questions Window

Use this window to define the questions and valid responses in the survey.

Display on Web Indicates whether the survey should appear on the Web.

selected Display on the Web (Y is stored in the database).

cleared Do not display on the Web (N is stored in the database).

If selected, the survey can be also viewed or removed from the Web when it is being constructed or modified.

Display from Beginning date when the survey is displayed on the Web. The format is DD-MON-YYYY.

Display to Ending date when the survey is displayed on the Web. The format is DD-MON-YYYY.

Information Text Free-form description that appears if the survey is displayed on the Web.

(button) Edit Editor window

Application Functional area associated with a population of Banner IDs.

(lookup) List Population Selection Applications

Selection Code that identifies a set of rules used to select a population of Banner IDs.

(lookup) List Population Selections

Creator Oracle ID of the user who created the rules used to select a population of Banner IDs.

User Oracle ID of the user who ran the Population Selection Extract Process (GLBDATA) to select the population of Banner IDs.

Note: The Application, Selection, Creator, and User fields identify a population of Banner IDs that can respond to the survey. If a population is defined with these fields, only those IDs in the population can access the survey.

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions



Survey Roles Window

Use this window to define the Web products where the survey can appear.

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions

Survey Name of the survey. Display-only.

Title Description of the survey. Display-only.

Question # Sequential number that identifies each question in the survey. Use the scroll bar to scroll through the questions in the survey. The maximum number of questions is 999.

Question Free-form text of each question in the survey.


Allow Multiple Responses

Indicates whether a user can give more than one response to the question.

selected Multiple responses are allowed (Y is stored in the database).

cleared Only one response is allowed (N is stored in the database).

Response [n] Free-form text that appears on the Web to describe each possible response to the question. A question can have up to 5 responses.

Allow Comments

Indicates whether comments can be entered as a response.

selected Comments are allowed (Y is stored in the database).

cleared Comments are not allowed (N is stored in the database).

Comment Text Free-form text that appears on the Web before the comment box, if comments can be entered as a response.

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions

Survey Name of the survey. Display-only.



Survey Summary Query Form (GUISRVS)

Use this form to display responses to surveys, by survey. This form is display-only.

Survey Summary Tab

Use this tab to display general statistics about responses to the survey.

Survey Questions Tab

Use this window to display information about the responses to each question in the survey.

Title Description of the survey. Display-only.

Roles Self-Service product where the survey can appear. Valid values are ALUMNI, EMPLOYEE, FACULTY, and STUDENT.

Activity Date Date when the role was entered or last changed. Display-only.

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions

Survey Name of the survey.

Title Description of the survey.

End Date Ending date when the survey is displayed on the Web.

Responses Total number of responses to the survey.

Complete Total number of persons who completed the survey.

Incomplete Total number of persons who responded but did not complete the survey.

Declined Total number of persons who declined to complete the survey.



Survey Respondents Tab

Use this window to display a list of respondents to the survey.

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions



Question Number

Sequential number that identifies each question in the survey. Use the scroll bar to scroll through the questions in the survey.

(untitled)Question

Free-form text of each question in the survey.


Allow Multiple Responses

Indicates whether users can give more than one response to the question.

selected Multiple responses are allowed.

cleared Only one response is allowed.

Response [n] Free-form text that appears on the Web to describe each possible response to the question. A question can have up to five responses.

Count Number of respondents who selected this response to the question.

Allow Comments

Indicates whether comments can be entered as a response.

selected Comments are allowed.

cleared Comments are not allowed.

Comment Count Number of respondents who entered comments to the question.

(button) List Survey Comments window

Note: Select the icon to access the Survey Comments window.



Survey Comments Window

Use this window to display user comments for a survey question. You can access this window by selecting the icon by the Comment Count field on the Survey Questions tab.

Third Party Procedures and Parameters Form (GOAFNXR)

This form enables you to view the functions and transactions used by third-party products.

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions



ID ID of each person who responded to the survey.

Name Name of each person who responded to the survey.

Declined Indicates whether the ID declined to respond to the survey.

selected ID declined.

cleared ID did not decline.

Complete Indicates whether the ID completed the survey.

selected ID completed the survey.

cleared ID did not complete the survey.

Activity Date Date when the ID responded to the survey.

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions

Question # Sequential number that identifies a question in the survey.

Comment Text Free-form text that appears on the Web before the comment box.

(untitled) Comments

User comments entered for the question.



• The first block contains function or transaction names along with the name of the package and procedure associated with the transaction.

• The second block contains the parameters required by the procedure highlighted in the first block.

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions

Function Function or transaction name. Use the scroll bar at the far right to navigate through the different functions and packages. Parameters for the database procedure highlighted in this block appear in the next block on this form.

Package Procedure name. Use the scroll bar at the far right to navigate through the different functions and packages. Parameters for the database procedure highlighted in this block appear in the next block on this form.

System Required Indicator

Indicates whether this function is required by Banner.

Package Procedure name. The name that appears in this field is the same as the package highlighted in the first block of this form.

Parameter Name Parameters associated with the procedure name indicated in the Package field.

Sequence Number

Sequence number for the parameter.

Parameter Position

Position of the parameter in the parameter string. Allowable values for this field are 0–99.

Data Type Parameter data type. Valid values for this field are T (table), C (character), or N (number).

Minimum Length

Minimum length of the parameter. Valid values for this field are 0–99.

Maximum Length

Maximum length of the parameter. Valid values for this field are 0–99.

Output Indicator Indicates whether this procedure generates output.



Third Party Electronic Control Rules Form (GORTCTL)

Use this form to define controls for Banner interfaces with third-party products. Voice Response currently uses this form. Other third party products will use this form in future Banner releases.

You can set up these kinds of controls on GORTCTL:

• Terms and/or aid years when a Banner function is available through third party products. For example, you can control when registration or grade information is available through Voice Response.

• Miscellaneous values associated with third party products. For example, Voice Response requires certain message numbers to be spoken for certain functions.

Each Admissions, Billing, Financial Aid, Grade Reporting, and Registration term or year has at least one control. Use the scroll bar to scroll through the controls.


Indicates whether this procedure is required by the system.

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions

Group Banner functional group associated with the control. Current groups are COMMON, ADMISSIONS, BILLING, FINANCIAL_AID, GRADE_REPORTING, and REGISTRATION.

Function Name of the function that is executed by the third-party product.

Description Description of the function that is executed by the third-party product.

System Indicator System code that determines how values entered in the Term/Year field are validated. Optional.

(lookup) List System Indicator Validation (GTVSYSI) list

Term/Year Term code (Student), aid year code (Financial Aid), or fiscal year code (Accounts Receivable) associated with the control. If the control does not need a term, aid year, or fiscal year code, the default value is 999999.



Control Number Control number used by the third party product for internal processing and sorting.

The way this number is used depends on the third party product. For Voice Response, this is the menu option used to perform a function. For example, if the option to review account detail is “press 2,” this value is 2.

Value Value of the control. Voice Response uses these values:

Y yes

N no

B use birth date instead of PIN (Admissions module)

G speak different messages for different grades (Grading module)

For example, this value equals Y if the function is available to Voice Response.

Sequence Number

Sequence number that uniquely identifies the control if the group/function has more than one record.

Active Indicates whether the control is active (selected) or inactive (cleared).

System Required Indicates whether the Banner system requires the control.

selected The control is required (Y is stored in the database).

cleared The control is not required by Banner baseline.

Once this box is selected, it cannot be changed or deleted.

Begin Date Date when the control becomes effective. For example, enter the date when Billing inquiry becomes available for third party products.

End Date Last date when the control is effective. For example, enter the date when Billing inquiry is no longer available for third party products.

Begin Time Time of day when the control becomes effective.

End Time Time of day after which the control is no longer effective.

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions



Enterprise PIN Preferences Form (GUAPPRF)

Use this form to specify your institutional preferences for handling PINs.

PIN Preferences Block

Use this block to specify the following preferences for your institution:

• Format of reset PINs (alphanumeric or numeric)

• Value of reset PINs (birthdates or random values)

Days Available Days when the control is effective. Values in the pull-down list are EVERYDAY, SUNDAY, MONDAY, TUESDAY, WEDNESDAY, THURSDAY, FRIDAY, SATURDAY, WEEKDAYS, and WEEKEND.

Year 1 4-digit year required by some third-party products. For example, Voice Response uses this year in the message “Financial Aid inquiry is available from fall <year 1> through spring <year 2>.”

Year 2 4-digit year required by some third-party products. For example, Voice Response uses this year in the message “Financial Aid inquiry is available from fall <year 1> through spring <year 2>.”

Value 2Value 3Value 4

Values required by some third-party products. For Voice Response, these may include message numbers and/or values used in processing.

System Indicator 2

System code that determines how values entered in the Term/Year 2 field are validated. Optional.

(lookup) List System Indicator Validation (GTVSYSI) list

Term/Year 2 Term code (Student), aid year code (Financial Aid), or fiscal year code (Accounts Receivable) associated with the control.

Date Miscellaneous date used by some third-party products.

Activity Date Date when the control was entered or updated. Display-only.

User User ID who entered or changed the control. Display-only.

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions



• Whether PINs are pre-expired

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions

PIN Reset Format

Indicates whether reset PINs can be alphanumeric or must be numeric. This setting applies to PINs that are reset by users on the Change PIN page accessed from self-service applications, by users who answer a security question during login to an self-service application, and by administrative users on the Third Party Access Form (GOATPAD). Numeric is the default.

If your institution generates alphanumeric PINs and at a later date changes this setting to numeric PINs, the system checks all existing PINs. If any alphanumeric PINs are found, an error message is displayed. You must manually change all alphanumeric PINs before you can change this setting from Alphanumeric to Numeric.

Alphanumeric PINs provide greater security.

Note: Voice Response requires numeric PINs. If your institution uses the VR product, you must select Numeric.

PIN Reset Value Pull-Indicates whether PINs are reset to users’ birthdates or random values.

Birthdate PINs are reset to birthdates. If there is no birthdate, a PIN is reset to the last six digits of the user’s Banner ID. This is the default value.

Random Value PINs are reset to random values. A value is numeric or alphanumeric, depending on the value of the PIN Reset Format field.

Pre-Expire New PIN

Indicates whether PINs are pre-expired when they are created the first time via the PIN Create Process (GURTPAC) or the Table PIN Create Controls.

Yes The PIN record is created with an expiration date one day before the system date.

No The PIN record is created without an expiration date.



PIN Notification Preferences Block

Use this block to specify how users are notified when their PINs are reset.

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions

Letter Generation Application Name

Letter Generation application associated with the letter and/or e-mail that is sent to users when their PINs are reset.

This field must have a value if Hard-copy Letter Generation Code or E-mail Letter Generation Code has a value.

If this field has a value, Hard-copy Letter Generation Code or E-mail Letter Generation Code must have a value.

(lookup) Application Inquiry (GLBAPPL) list of values

Hard-copy Letter Generation Code

Letter code that identifies the hardcopy letter sent to users when PINs are reset. This code is used to create a GURMAIL record when a person’s PIN is reset.



E-mail Letter Generation Code

Letter code that identifies the e-mail sent to users when PINs are reset. When a person’s PIN is reset, this code is used to insert a record into a table that interfaces with your institution’s e-mail system.



When user changes PIN

Indicates what notifications (e-mail, hardcopy letter, both e-mail and letter, or neither) are sent when users reset their own PINs via the Web.

When Admin/Process changes PIN

Indicates what kind of notifications (e-mail, hardcopy letter, both e-mail and letter, or neither) are sent when an administrator or system process changes user PINs.

User ID User who created or last updated the preferences.

Activity Date Date the preferences were created or last updated.



Table PIN Creation ControlsUse this block to establish a PIN, for the first time, when specific Banner forms create specific Banner tables.

Note: To create PINs based on a population selection, use the PIN Create Process (GURTPAC). For more information, refer to the Reports and Processes chapter of this manual.

Directory Item Validation Form (GTVDIRO)

Use this form to define codes for the types of information included in directory profiles. The profile is used to select and print information in the Web directory.

A set of directory item codes is delivered with Banner. To ensure proper directory processing, you must not change these codes. You can change directory item descriptions without affecting directory processing. You can also add directory item codes for your institution’s Web campus directory profile and the Web directory.

E-mail Address Type Validation Form (GTVEMAL)

Use this form to define e-mail address type codes. Examples of address types include business, personal, and school. These codes are used to enter e-mail address information for individuals on the E-mail Address Form (GOAEMAL).

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions

Table Name Table that directs whether a PIN is generated, if one does not yet exist. Table names are provided by SunGard Higher Education and cannot be changed.

Create PIN Code that indicates whether a new PIN is inserted when the associated table is created.

Y When the table is created, the process verifies whether a PIN exists. If a PIN does not exist, the process creates a PIN.

N When the table is created, the process does not verify whether a PIN exists.

Activity Date Date the table preferences were created or last updated.



The Description field is required. This description appears on Web pages where users can view or update e-mail information. Once created, an e-mail address type code cannot be changed. The description can be updated any time.

The Web check box specifies if this type of e-mail address will be included in LOVs on the web.

Note: This is different from the Display on Web check box on GOAEMAL, which specifies if an e-mail address, regardless of type, should appear on the web.

The URL check box indicates if the e-mail address type is a URL.


Chapter 11

Voice Response Management

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-3

11 Voice Response ManagementMenu Navigation Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-3

Forms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-4

Voice Response Menu Control Rules Form . . . . . . . . . . . (GORMENU). . . . . 11-4Voice Response Duty Flag Rules Form . . . . . . . . . . . . . (GORFLAG) . . . . . 11-6VR Operator Availability & System Parameter Rules Form . . . (GORPARM) . . . . . 11-8VR Admissions Term Based Rules Form . . . . . . . . . . . . . (GORADMS) . . . . . 11-10Voice Response Billing Term Based Rules Form . . . . . . . . . (GORBILL) . . . . . . 11-17Voice Response Financial Aid Award Year and Term Based

Rules Form . . . . . . . . . . . . . . . . . . . . . . . . . . (GORAWPD) . . . . 11-21Voice Response Registration & Grading Term Based Rules Form (GORRGTM). . . . . 11-30Voice Response Registration Status Rules Form . . . . . . . . . (GORRSTS) . . . . . 11-37Voice Response Control Rules Form . . . . . . . . . . . . . . (GORVCTL) . . . . . 11-38

11-1

Table of Contents




Overview

11 Voice Response Management Voice Response

Management

Voice Response is a Banner software option available for Banner Student and Banner Financial Aid Systems that supports touch-tone telephone data entry and inquiry for student information. Voice Response includes Registration, Grade Reporting, Billing, Financial Aid, and Admissions modules. All Banner Voice Response modules provide your institution with the following:

• Direct student access to online registration, billing, admissions, financial aid, and/or grade information from a touch-tone telephone through a series of simple entries — student ID, Personal Identification Number (PIN), menu selections, and course request numbers.

• Modifiable voice response system messages.

• Easy-to-use Oracle tables for modification of system responses.

Refer to the Banner Voice Response Implementation Guide for details.


Forms in the General Voice Response Management module can be accessed from the following menu.

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . General VR Management Menu (*GENVR)

GORMENU VR Menu Control Rules FormMaintains all menu records, regardless of the Voice Response modules to which they apply.

GORFLAG Voice Response Duty Flag Rules FormMaintains all duty flags, regardless of the Voice Response modules to which they pertain.

GORPARM VR Operator Availability /System Parameter Rules FormMaintains all system parameters and operator availability information, regardless of the Voice Response module to which they pertain.

GORADMS VR Admissions Term Based Rules FormMaintains basic information about the VR Admissions module.

GORBILL Voice Response Billing Term Based Rules FormMaintains information about billing terms and dates, and billing deadline dates.



Forms

This section describes each form in the General VR Management module. Forms are described in the order they appear on the General VR Management Menu (*GENVR).

Voice Response Menu Control Rules Form (GORMENU)

Use this form to display and update all menu records, regardless of the Voice Response modules to which they pertain.

Note: This form is restricted to the administrative security class.

GORAWPD Voice Response Financial Aid Award Year/Term Based Rules FormMaintains basic information about the VR Financial Aid module.

GORRGTM Voice Response Registration & Grading Term Based Rules FormMaintains basic registration and grading information.

GORRSTS Voice Response Registration Status Rules FormMaintains the status information for the VR Registration module.

GORVCTL Voice Response Control Rules FormCreates and maintains the group, function and control number combinations.

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . General VR Management Menu (*GENVR)

. . . . . . . . . . . . . . Fields


Group Banner functional group associated with the control. Required.

(lookup) List Voice Response Controls Group List

Function Name of the function or indicator. Required.

(lookup) List Voice Response Controls Function List



Control Number For GORMENU only, this is the value that indicates the number on the keypad that should be pressed and will be spoken after, “press,” for example, “... press 1.” Required.

(lookup) List Voice Response Controls Control Number List

Sequence Number

Sequential counter used for multiple group/function/control number records. Display only.

When only one record exists for this function, a default value of 1 is used for this field.

Active Record Indicates whether the menu option is active.

If cleared, the menu option will not be spoken.

System Required Indicates whether the record is system-required.

This indicator is selected and display-only for all delivered records on GORMENU. If you insert a new record or create a duplicate record, this value defaults to cleared.

Begin Date Date that the menu option becomes effective and is spoken to the caller.

If a value is entered in this field, a value must also be entered in the End Date field.

The use of begin/end dates is independent of begin/end times.

End Date Last day the menu option is effective and spoken to the caller (for example, the last day of registration).

If used in conjunction with the Begin Date field, the value in this field must be greater than or equal to the value in the Begin Date field.

Begin Time First time of day the menu is spoken to the caller.

If a value is entered in this field, a value must also be entered in the End Time field. For example, if you want the Orientation Menu to be offered from 8:00 a.m. to 5:00 p.m., you need to define the 8:00 a.m. begin time here and the 5:00 p.m. end time in the End Time field.)

. . . . . . . . . . . . . . Fields




Voice Response Duty Flag Rules Form (GORFLAG)

Use this form to display and update all duty flags, regardless of the Voice Response modules to which they pertain.


End Time Last time of day the message is spoken to the caller.

If used in conjunction with the Begin Time field, the value in this field must be greater than or equal to the value in the Begin Time field.

Days Available Days the control is in effect.

You can select the valid values from a pull-down list. The default value is Everyday.

Voice Response Menu Message Number

Numeric value of the message spoken when the caller is prompted to select this menu option (for example, “For Billing press 2”).

Function Call Code

Name of the Voice Response function that is called when a menu option is chosen.

For operator functions, this is the phone number of the operator to be dialed.

Activity Date Date the record was last updated. Display only.

User User ID of the last person who entered or changed the record. Display only.

. . . . . . . . . . . . . . Fields




. . . . . . . . . . . . . . Fields


Group Banner functional group associated with the control.

Enter one of the following:

• COMMON

• ADMISSIONS

• BILLING

• FINANCIAL_AID

• GRADE_REPORTING

• REGISTRATION

Function Name of the function or indicator.

Refer to the GORFLAG, GORMENU, or GORPARM sections in this chapter for valid function values.

Active Record Indicates if the record is active. Valid values are:

selected - the rule is activecleared - the rule is inactive


This indicator is selected and display-only for all delivered records on GORVCTL. If you insert a new record or create a duplicate record, the default value is cleared.

Sequence Number

For record type VCMENU, this is the value that indicates the menu option offered and that will be spoken after, “press,” for example, “... press 1.”

For all other record types, this value should be 1.

Duty Flag Value Value associated with the corresponding function. Values currently used by Voice Response are Y, N, B, G where Y equals yes and N equals no.

Begin Date The date the rule becomes effective.

End Date The date the rule is no longer effective.

Begin Time The time on the Begin Date that the rule becomes effective.

End Time The time on the End Date that the rule is no longer effective.



VR Operator Availability & System Parameter Rules Form (GORPARM)

Use this form to display and update all system parameters and operator availability information, regardless of the Voice Response module to which they pertain.


Days Available Allows you to specify the days on which the rule will be effective. Valid values are EVERYDAY, SUNDAY, MONDAY, TUESDAY, WEDNESDAY, THURSDAY, FRIDAY, SATURDAY, SUNDAY, WEEKDAYS, and WEEKEND.


User User ID of the last person who entered or changed the control. Display only.

. . . . . . . . . . . . . . Fields


. . . . . . . . . . . . . . Fields


The following fields are displayed in the Operator Availability block.

Group Banner functional group associated with the control. Required.

(lookup) List Voice Response Controls Group List

Function Name of the function or indicator. Required.

(lookup) List Voice Response Function List

Sequence Number

Sequential counter used for multiple group/function records. Display-only.

When only one record exists for this function, a default value of 1 is used for this field.

Operator Available

Indicates whether Operator menu option is available.




If you insert a new record or create a duplicate record, this value defaults to cleared.

Phone Number Phone number of the operator associated with this record.

Operator Message Number

Numeric value of the message to be spoken to describe this option.

Begin Date Date that the operator number becomes effective and is spoken to the caller.



End Date Last day the operator number is effective and spoken to the caller (for example, the last day of registration).


Begin Time First time of day the operator number is active.

If a value is entered in this field, a value must also be entered in the End Time field. For example, if you want to allow credit card payments through the Billing module only from 8:00 a.m. to 5:00 p.m., you need to define the 8:00 a.m. begin time here and the 5:00 p.m. end time in the End Time field.)

End Time Last time of day the operator number is active.


Days Available Days the control is in effect.



. . . . . . . . . . . . . . Fields




VR Admissions Term Based Rules Form (GORADMS)

Use this form to display and update the following information related to the VR Admissions module:

• Admissions terms and dates

• Admissions application deadline dates

• Admissions credentials deadline dates

• Admissions orientation information

GORADMS is composed of the following windows:

• Main window, Admissions Terms and Dates block, which is used to define and maintain the messages used for your Admissions Term menu, including message availability

• Voice Response Admissions Application Deadlines window, which is used to define and maintain the messages used for your application deadline information, including message availability

• Voice Response Admissions Credentials Deadlines window, which is used to define and maintain the availability of the credential deadlines for the respective application deadlines

• Voice Response Admissions Orientation Information window, which is used to define and maintain the messages used for your orientation schedules, including message availability


The following fields are displayed in the System Parameters block.

Parameter Alpha-numeric value that indicates the setting of the system parameter (for example, the parameter for "Maximum Number of Retries Allowed" is 3). Required.

Description Description associated with the parameter. Display only.


. . . . . . . . . . . . . . Fields




Main Window

. . . . . . . . . . . . . . Fields


Admissions Term Code

Code associated with the term for which you are defining Admissions messages.

Control Number Numeric value that uniquely identifies the record with the specified term. This value is system-generated, but can be changed during the creation of the record. Once a record is saved, the value in this field cannot be changed.

Sequence Number

Sequential counter used to identify additional records created for the specified term. This value is system-generated.

Active Admissions Term

Indicates whether the record is activated for use. This value defaults to selected for new records.

Year Spoken Year spoken by the Voice Response system. Required.

The value in this field corresponds to the term specified in the key block.

Term Menu Message Number

Message number that precedes the year spoken. Required.

For example, if you enter 1004 (“For Fall term ...”) in this field and 2004 in the Year Spoken field, the message spoken is “For Fall term 2004 ....”

Term Message Number

Number of the term message to be used in subsequent dialog once the term has been selected (for example, 1123 for “... Fall term ...”). Required.

Begin Date First date on which the menu option is available for the term specified in the key block.



End Date Last date on which the menu option is available for the term specified in the key block.




Voice Response Admissions Application Deadline Window

Use this window to create a deadline for admission applications for the term specified in the key block of the main window.

Begin Time First time of day that the menu option is available for the term specified in the key block.

If a value is entered in this field, a value must also be entered in the End Time field. For example, if you want the Admissions Menu to be available from 8:00 a.m. to 5:00 p.m., you need to define the 8:00 a.m. begin time here and the 5:00 p.m. end time in the End Time field.)

End Time Last time of day that the menu option is available for the term specified in the key block.


Days Available Days that this information is offered.




. . . . . . . . . . . . . . Fields



Sequence Number


Active Deadline Term


. . . . . . . . . . . . . . Fields








For example, if you enter 1004 (“For Fall term...”) in this field and 2004 in the Year Spoken field, the message spoken is “For Fall term 2004....”

Admissions Deadline Date

Date by which admissions applications must be received.

Begin Date First date on which the deadline menu option is available for the term specified in the key block.



End Date Last date on which the menu deadline option is available for the term specified in the key block.


Begin Time First time of day that the deadline menu option is available for the term specified in the key block.

If a value is entered in this field, a value must also be entered in the End Time field. For example, if you want the deadline information to be available from 8:00 a.m. to 5:00 p.m., you need to define the 8:00 a.m. begin time here and the 5:00 p.m. end time in the End Time field.)

End Time Last time of day that the deadline menu option is available for the term specified in the key block.


. . . . . . . . . . . . . . Fields




Voice Response Admissions Credentials Deadlines Window

Use this window to create a credential deadline for the term specified in the key block of the main window. This record is automatically associated with the record in the Voice Response Admissions Application Deadlines window. No credentials deadline record can be created until the application deadline record with which it is to be associated has been created. The credentials deadline record is automatically given the same control number as the associated application deadline record.





. . . . . . . . . . . . . . Fields


Sequence Number


Active Deadline Term


Credentials Deadline Date

Date by which admissions credentials must be received.




. . . . . . . . . . . . . . Fields




Voice Response Admissions Orientation Window

Use this window to specify orientation details for the term specified in the key block of the main window.











. . . . . . . . . . . . . . Fields



. . . . . . . . . . . . . . Fields




Sequence Number


Active Orientation Term




Term Message Number

Message number the precedes the year spoken. Required.

For example, if you enter 1004 (“For Fall term...”) in this field and 2004 in the Year Spoken field, the message spoken is “For Fall term 2004....”

Level-Orientation Message

Number of the term message to be used preceding the orientation schedule information spoken (for example, 2026 for “For undergraduate students”). Required.

Orientation Begin Date

Date on which orientation begins for the term specified in the key block.



Orientation End Date

Date on which orientation ends for the term specified in the key block.


Orientation Begin Time

Time of day at which orientation begins for the term specified in the key block.

If a value is entered in this field, a value must also be entered in the End Time field. For example, if orientation runs from 9:00 a.m. to 3:00 p.m., you need to define the 9:00 a.m. begin time here and the 3:00 p.m. end time in the End Time field.)

. . . . . . . . . . . . . . Fields




Voice Response Billing Term Based Rules Form (GORBILL)

Use this form to display and update the following information related to the VR Billing module:

• Billing terms and dates

• Billing deadline dates

GORBILL is composed of the following windows:

• Main window, Voice Response Billing Terms and Dates block, which is used to define and maintain the messages used for your Billing Terms menu, including message availability

• Voice Response Billing Deadline Dates window, which is used to define and maintain the messages used for your billing payment deadline dates for each level at your institution, including message availability

Orientation End Time

Time of day at which orientation ends for the term specified in the key block.






. . . . . . . . . . . . . . Fields


. . . . . . . . . . . . . . Fields


Billing Term Code

Code associated with the term for which you are defining Billing messages.




Sequence Number


Active Billing Term







Term Message Number


Begin Date First date on which the menu option is available for the term specified in the key block.



End Date Last date on which the menu option is available for the term specified in the key block.


. . . . . . . . . . . . . . Fields




Voice Response Billing Deadline Dates Window

Use this window to create a billing deadline for the term specified in the key block of the main window.

Begin Time First time of day that the menu option is available for the term specified in the key block.

If a value is entered in this field, a value must also be entered in the End Time field. For example, if you want the Billing Menu to be available from 8:00 a.m. to 5:00 p.m., you need to define the 8:00 a.m. begin time here and the 5:00 p.m. end time in the End Time field.)

End Time Last time of day that the menu option is available for the term specified in the key block.






. . . . . . . . . . . . . . Fields



Sequence Number


Active Deadline Record


. . . . . . . . . . . . . . Fields






Term Message Number

Message number the precedes the year spoken. Required.


Level-Deadline Message

Message number the precedes the deadline date (for example, 2026 for “For undergraduate students”). Required.

Billing Deadline Date

Date by which the billing item must be received.










. . . . . . . . . . . . . . Fields




Voice Response Financial Aid Award Year and Term Based Rules Form (GORAWPD)

Use this form to display and update the following information related to the VR Financial Aid module:

• Financial Aid award periods

• Financial Aid application deadline dates

• Financial Aid credentials deadline dates

• Financial Aid terms and dates

GORAWPD is composed of the following windows:

• Main window, Voice Response Financial Aid Award Periods block, which is used to define and maintain the messages used for your Financial Aid Award Year menu, including message availability

• Voice Response Financial Aid Application Deadline Dates window, which is used to define and maintain the messages used for your award year-specific application deadline information, including message availability

• Voice Response Financial Aid Credential Deadline Dates window, which is used to define and maintain the availability of your credential deadlines for the respective application deadlines.

• Voice Response Financial Aid Terms & Dates window, which is used to define and maintain the messages used for the term-specific detail within the award period, including message availability





. . . . . . . . . . . . . . Fields




Key Block

Voice Response Financial Aid Award Periods Block

. . . . . . . . . . . . . . Fields


Award Year Code

Code representing the year for which the Financial Aid is awarded. Valid values come from the Aid Year Validation list (ROBINST).

. . . . . . . . . . . . . . Fields


Control Number Numeric value that uniquely identifies the award period record with the specified award year. This value is system-generated, but can be changed during the creation of the record. Once a record is saved, the value in this field cannot be changed.

Active Award Period Record


Sequence Number

Sequential counter used to identify additional records created for the specified award year. This value is system-generated.

1st Year Spoken First year in the award period spoken by the Voice Response system. Required.

The value in this field corresponds to the beginning year of the award period code specified in the key block.

2nd Year Spoken Second year in the award period spoken by the Voice Response system. Required.

The value in this field corresponds to the ending year of the award period code specified in the key block.

1st Term Menu Message Number

Message number that precedes the first term spoken. Required.



1st Term Message Number

Message number to be used with the first year spoken in subsequent dialog once the award period has been selected (for example, 3010 for “... Fall ...”). Required.

For example, if you enter 3010 (“... Fall ...”) in this field and 2004 in the 1st Year Spoken field, the message spoken is “... Fall 2004 ....”

2nd Term Message Number

Message number to be used with the second year spoken in subsequent dialog once the award period has been selected (for example, 3012 for “... Spring ...”). Required.

For example, if you enter 3012 (“... Spring ...”) in this field and 2005 in the 2nd Year Spoken field, the message spoken is “... Spring 2005 ....”

Begin Date First date on which the menu option is available for the award year specified in the key block.



End Date Last date on which the menu option is available for the award year specified in the key block.


Begin Time First time of day that the menu option is available for the award year specified in the key block.


End Time Last time of day that the menu option is available for the award year specified in the key block.


. . . . . . . . . . . . . . Fields




Voice Response Financial Aid Application Deadline Dates Block

Use this window to create a deadline for financial aid applications for the award year specified in the key block of the main window.



User ID User ID of the last person who entered or changed the record. Display only.


. . . . . . . . . . . . . . Fields


Control Number Numeric value that uniquely identifies the application deadline record with the specified award year. This value is system-generated, but can be changed during the creation of the record. Once a record is saved, the value in this field cannot be changed.



Sequence Number


Deadline Date Date the application for Financial Aid is due for the specified Award Year.

1st Year Spoken First year in the award period spoken by the Voice Response system. Required.

The value in this field corresponds to the beginning year of the award period code specified in the key block.

2nd Year Spoken Second year in the award period spoken by the Voice Response system. Required.

The value in this field corresponds to the ending year of the award period code specified in the key block.

. . . . . . . . . . . . . . Fields




1st Term Message Number

Message number to be used with the first year spoken in subsequent dialog once the award period has been selected (for example, 3010 for “... Fall ...”). Required.

For example, if you enter 3010 (“... Fall ...”) in this field and 2004 in the 1st Year Spoken field, the message spoken is “... Fall 2004 ....”

2nd Term Message Number

Message number to be used with the second year spoken in subsequent dialog once the award period has been selected (for example, 3012 for “... Spring ...”). Required.

For example, if you enter 3012 (“... Spring ...”) in this field and 2005 in the 2nd Year Spoken field, the message spoken is “... Spring 2005 ....”










. . . . . . . . . . . . . . Fields




Credentials Deadline Dates Window

Use this window to create a credential deadline for the award year specified in the key block of the main window. This record is automatically associated with the record in the Voice Response Financial Aid Application Deadlines window. No credentials deadline record can be created until the application deadline record with which it is to be associated has been created. The credentials deadline record is automatically given the same control number as the associated application deadline record.





. . . . . . . . . . . . . . Fields


Sequence Number




Deadline Date Date by which the Financial Aid application must be received.






. . . . . . . . . . . . . . Fields




Voice Response Financial Aid Credentials Deadline and Term Dates Window

Use this window to define and maintain the messages used for the term-specific detail within the award period.

Voice Response Financial Aid Credentials Deadline Dates Block









. . . . . . . . . . . . . . Fields


Sequence Number



Indicates if the record is active. Valid values are:

selected - the record is activecleared - the record is inactive

. . . . . . . . . . . . . . Fields




Voice Response Financial Aid Terms and Dates

Note: Select the Load Defaults button to have Banner populate the fields with the default values.

Deadline Date Date by which the Financial Aid credentials must be received.

Begin Date First date on which the menu option is available for the term specified in the Term Code field.



End Date Last date on which the menu option is available for the award year specified in the Term Code field.


Begin Time First time of day that the menu option is available for the award year specified in the Term Code field.

If a value is entered in this field, a value must also be entered in the End Time field. For example, if you want financial aid information to be available from 8:00 a.m. to 5:00 p.m., you need to define the 8:00 a.m. begin time here and the 5:00 p.m. end time in the End Time field.)

End Time Last time of day that the menu option is available for the award year specified in the Term Code field.






. . . . . . . . . . . . . . Fields




. . . . . . . . . . . . . . Fields


Control Number Numeric value that uniquely identifies the record with the specified term within the award year. This value is system-generated, but can be changed during the creation of the record. Once a record is saved, the value in this field cannot be changed.

Active Aid Term Record


Sequence Number


Term Code Code of the term during the award year for which the system will offer callers Financial Aid information. Required.

(lookup) List Term Code Validation (STVTERM)


The value in this field corresponds to the term specified in the Term Code field.



For example, if you enter 3006 (“For Fall ...”) in this field and 2004 in the Year Spoken field, the message spoken is “For Fall 2004 ....”

Term Message Number

Message number to be used with the year spoken in subsequent dialog once the award period has been selected (for example, 3010 for “... Fall ...”). Required.

For example, if you enter 3010 (“... Fall ...”) in this field and 2004 in the Year Spoken field, the message spoken is “... Fall 2004 ....”

Begin Date First date on which the menu option is available for the term specified in the Term Code field.





Voice Response Registration & Grading Term Based Rules Form (GORRGTM)

Use this form to display and update the following term-specific information:

• VR Registration module terms and dates

• VR Registration module drop dates

• VR Registration module add dates

• VR Grading module terms and dates

End Date Last date on which the menu option is available for the award year specified in the Term Code field.


Begin Time First time of day that the menu option is available for the award year specified in the Term Code field.

If a value is entered in this field, a value must also be entered in the End Time field. For example, if you want financial aid information to be available from 8:00 a.m. to 5:00 p.m., you need to define the 8:00 a.m. begin time here and the 5:00 p.m. end time in the End Time field.)

End Time Last time of day that the menu option is available for the award year specified in the Term Code field.






. . . . . . . . . . . . . . Fields




Main Window

The main window of GORRGTM is used to define and maintain the messages used for the Registration Term menu and registration deadline dates, as well as their availability.

The begin dates and end dates must be defined if you want corresponding registration deadline dates for the specified term to be spoken to a caller under the general Registration Information menu. Delivery of deadline dates will also be subject to the valid status of the registration term record as designated by the following fields, as applicable:

• Active Registration Term

• Begin Date

• End Date

• Begin Time

• End Time

• Days Available

. . . . . . . . . . . . . . Fields


Term Code Code associated with the term for which you are defining Registration messages.


Sequence Number


Active Registration Term









Term Message Number


Begin Date First date on which students can add or drop courses for the term specified in the key block.



End Date Last date on which students can add or drop courses for the term specified in the key block.


Begin Time First time of day that students can add or drop courses for the term specified in the key block.

If a value is entered in this field, a value must also be entered in the End Time field. For example, if you want Registration to be open from 8:00 a.m. to 5:00 p.m., you need to define the 8:00 a.m. begin time here and the 5:00 p.m. end time in the End Time field.)

End Time Last time of day that students can add or drop courses for the term specified in the key block.






. . . . . . . . . . . . . . Fields




Voice Response Registration Add and Drop Dates Window

This window is composed of two blocks.

• Use the Voice Response Registration Add Dates block to define the beginning and end dates for the period of time students can add a course to their schedule. Students can add courses through the Add Classes menu or the Check Availability menu. The dates defined in the Voice Response Registration Add Dates block will activate both options.

• Use the Voice Response Registration Drop Dates block to define the beginning and end dates for the period of time students can drop courses from their schedules and withdraw from the institution. Since a student may opt to do both at the same time, the availability of these two menu options is tied together. The dates you define in the Voice Response Registration Drop Dates block apply to the availability of both of these options.

. . . . . . . . . . . . . . Fields


The following fields are displayed in the Voice Response Registration Add Dates block.


Sequence Number


Active Reg-Add Record


Begin Date First date on which students can add courses for the term specified in the key block.



End Date Last date on which students can add courses for the term specified in the key block.




Begin Time First time of day that students can add courses for the term specified in the key block.


End Time Last time of day that students can add courses for the term specified in the key block.






The following fields are displayed in the Voice Response Registration Drop Dates block.


Sequence Number


Active Reg-Drop Record


Begin Date First date on which students can drop courses for the term specified in the key block.



. . . . . . . . . . . . . . Fields




Voice Response Grading Terms and Dates Window

The Voice Response Grading Terms and Dates block is used to define and maintain the messages used for the Grade Reporting menu, as well as their availability.

End Date Last date on which students can drop courses for the term specified in the key block.


Begin Time First time of day that students can drop courses for the term specified in the key block.


End Time Last time of day that students can drop courses for the term specified in the key block.






. . . . . . . . . . . . . . Fields


Term Code Code associated with the term for which you are defining Grade Reporting messages.

. . . . . . . . . . . . . . Fields





Sequence Number


Active Grading Term






For example, if you enter 1004 (“For Fall term ...”) in this field and 2004 in the Year Spoken field, the message spoken is “For Fall term 2004 ...”

Term Message Number


Begin Date First date on which grading information is to be available for the term specified in the key block.



End Date Last date on which grading information is to be available for the term specified in the key block.


. . . . . . . . . . . . . . Fields




Voice Response Registration Status Rules Form (GORRSTS)

Use this form to display and update the following information related to the VR Registration module:

• Drop registration status codes and dates

• Registered registration status codes

• Waitlisted registration status codes

Begin Time First time of day that grading information is to be available for the term specified in the key block.

If a value is entered in this field, a value must also be entered in the End Time field. For example, if you want the Grade menu to be open from 8:00 a.m. to 5:00 p.m., you need to define the 8:00 a.m. begin time here and the 5:00 p.m. end time in the End Time field.)

End Time Last time of day that grading information is to be available for the term specified in the key block.






. . . . . . . . . . . . . . Fields




Voice Response Control Rules Form (GORVCTL)

Use this form to create, display, and update group, function, and control number combinations. These combination rules are used on the following forms:

• VR Menu Control Rules Form (GORMENU)

• VR Duty Flag Rules Form (GORFLAG)

• VR Operator Availability and System Parameter Rules Form (GORPARM)

Note: GORVCTL is restricted to the administrative security class.

. . . . . . . . . . . . . . Fields


Record Type Value that associates the applicable Voice Response rules to the appropriate Voice Response module.

Values include VCMENU, VCPARM, VCOPER, and VCFLAG.

Group Banner functional group associated with the control.

Enter one of the following:

• COMMON

• ADMISSIONS

• BILLING

• FINANCIAL_AID

• GRADE_REPORTING

• REGISTRATION

Function Name of the function or indicator.

Refer to the GORFLAG, GORMENU, or GORPARM sections in this chapter for valid function values.

Control Number For record type VCMENU, this is the value that indicates the menu option offered and that will be spoken after, “press,” for example, “... press 1.”

For all other record types, this value should be 1.

Description Text that describes the function of the group/function/control number. This is a free-form value.




This indicator is selected and display-only for all delivered records on GORVCTL. If you insert a new record or create a duplicate record, this value defaults to cleared.

User User ID of the last person who entered or changed the control. Display only.


. . . . . . . . . . . . . . Fields



Chapter 12


Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-3

12 Business Rule BuilderValidation Forms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-3


Forms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-4

Business Rule Process Parameters Form . . . . . . . . . . . . . (GORSQPA) . . . . . 12-4Business Rules Form . . . . . . . . . . . . . . . . . . . . . . (GORRSQL) . . . . . 12-5

12-1

Table of Contents




Overview

Business Rule Builder To help you manage your Banner data for SEVIS processing, Multi-Institution Functionality (MIF), and Banner Integration Components, General includes forms you can use to build business rules. The rules you create can be used to populate columns in Banner tables with values from other columns. Your rules can also create student and exchange visitor records automatically.

Validation Forms


Business Rule Builder forms use the following validation forms. Refer to Chapter 2, Validation Forms, for additional information.


Forms in the Business Rule Builder module can be accessed from the following menu.


GTVSQRU Business Rule Code Validation Form GORSVSQ SEVIS Business Rules FormGORRSQL Business Rules Form

GTVSQPR Business Rule Process Code Validation Form

GORSVSQ SEVIS Business Rules FormGORRSQL Business Rules Form

GTVSQPA Business Rule Parameter Code Validation Form


. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . General Business Rule Builder Menu (*GENBUSINESSRULE)

GTVSQRU Business Rule Code Validation FormMaintains the rule codes that will be used in your dynamic SQL statements. For SEVIS reporting, you might want to set up rule codes such as Create Student, Update Major, etc.

GTVSQPR Business Rule Process Code Validation FormMaintains the process codes that are valid for dynamic query processing. The delivered value is SEVIS.



Forms

This section describes the forms in the Business Rule Builder module. Forms are described in the order they appear on the Business Rule Builder Menu (*GENBUSINESSRULE).

The validation forms that support business rules are described in Chapter 2, Validation Forms.

Business Rule Process Parameters Form (GORSQPA)

Use this form to associate the process code with the parameter codes to be used on GORRSQL. The valid parameter codes are defined on the Business Rule Parameter Code Validation Form (GTVSQPA).

Process codes can have multiple parameters.

For SEVIS reporting, the process code must be SEVIS, and the parameters associated with it are PIDM and TERM.

GTVSQPA Business Rule Parameter Code Validation FormMaintains the parameters or variables you will use to build your process rules on the Business Rules Form (GORRSQL). You will use the codes you define on this form in the dynamic SQL statements on GORRSQL.

GORSQPA Business Rule Process Parameters FormAssociates a process code with the parameter codes it will use on GORRSQL. The valid parameter codes are defined on the Business Rule Parameter Code Validation Form (GTVSQPA).

GORRSQL Business Rules FormAllows you to build SQL statements that will perform certain functions when they are executed from the SEVIS Batch Extract Process (GORSEVE).

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . General Business Rule Builder Menu (*GENBUSINESSRULE)



Key Block

Rules Block

This block allows you to specify parameters for the process code.

Business Rules Form (GORRSQL)

This form allows you to build SQL statements that will perform certain functions when they are executed from the SEVIS Batch Extract Process (GORSEVE) or some other process.

. . . . . . . . . . . . . . Fields


Process Code Code representing the process for which you want to assign parameters.



The description that corresponds to the SQL Process Code.

. . . . . . . . . . . . . . Fields


Parameter Code Code representing the parameter you want to associate with the process code.

(lookup) List Business Rule Parameter Code Validation list (GTVSQPA)

Description The description that corresponds to the parameter code.


Indicates if the code is required by the system. Valid values are:


User ID The Banner ID of the person who created the record or changed it last.

Activity Date The date the record was created or the last date it was changed.



It allows you to specify the columns you want to use in your statements, and provides operators so you can build them. You must validate, activate, and save each SQL statement before you can use it.

Note: Be sure to enter the same process code/rule code combination this form that you set up on the SEVIS Business Rules Form (GORSVSQ). The SQL where clause you build on GORRSQL will populate data based on what you have set up on GORSVSQ. If the process code/rule code combination does not exist on both forms, nothing will happen.

Each SQL statement returns one value, which updates the field associated with the business rule. These fields are assigned on the SEVIS Business Rules Form (GORSVSQ).

You cannot change the Validated indicator; Banner updates it automatically when the SQL statement is validated. If the statement is not validated, Banner displays an error message. You can save GORRSQL records without validating them and return to them later, but you cannot use them until you validate them and activate them.

If you modify a rule that was previously validated, the rule becomes invalid until you re-validate it by selecting Validate to invoke the SQL parsing process again.

The following must be true for a rule to be used:

• The rule must be validated.

• The rule must be activated.

• The current date must be within the start and end dates for the rule.

• The rule assignments on the SEVIS Business Rules Form (GORSVSQ) must be valid, and within their start and end dates.

. . . . . . . . . . . . . . Fields


Process Code The process code for the rule.


Rule Code The code that describes what the rule will do.

(lookup) List Business Rule Code Validation list (GTVSQRU)

Sequence This displays the sequence number for the rule. It is used by Banner to maintain the uniqueness of each rule and determine rule priority.

This field is display-only. Be sure to enter your rules in the proper order.



User ID The Banner ID of the person who created the record or changed it last.

Start Date The date the rule becomes active. The default value is the system date.

End Date When the rule becomes inactive. Use null to indicate that the rule will never be inactive because of the passage of time.

Note: You can still make the rule inactive by clearing the Active check box.

Activity Date The date the record was created or the last date it was changed.

Validate Select this button when you have finished entering your SQL statement. You cannot use the rule with GORSEVE or GOASEVS until it has been validated.

Active Indicates if the rule is currently active. Valid values are:

Selected - the rule is activeCleared - the rule is inactive

System Required Indicates whether the process code/rule code combination in the key block is system required.

System-required combinations cannot be deleted. You can change the start date, end date, and the status of the active indicator. You can also add sequences to the system-required rule to further define the SQL statement, but you cannot remove the original delivered sequence.

SunGard Higher Education recommends that you use the system-required values as delivered.

Validated Indicates if the rule has been successfully validated. Valid values are:

Selected - the rule has been validatedCleared - the rule has not yet been validated

SQL Statement Enter the SQL statement for this Process Code/Rule/Sequence Number combination. You can use the Table, Column, Operator, and Parameter buttons and fields to help you build the statement. Each selection from the buttons and fields is appended to your SQL statement.

. . . . . . . . . . . . . . Fields




Parsed SQL Block

This block appears when you select View Parsed Rule from the Options pull-down menu, or select Next Block from the Rule Data block. It contains the current, parsed version of your SQL. This view may be helpful during updates, when you try to compare changes to existing parsed, error-free SQL.

Table This is a tool to help you build your SQL statement. Select the button to see a list of Banner tables, then double-click on the field to append the table name to your SQL statement.

Column This is a tool to help you build your SQL statement. Select the button to see a list of columns for the table you just selected, then select the column you want. It will be appended to your SQL statement.

Operator This is a tool to help you build your SQL statement. Select the operator you want to use in your SQL statement from the pull-down menu. It will be appended to your SQL statement.

Parameter This is a tool to help you build your SQL statement. Select the button to see a list of parameters you defined on GTVSQPA, then select the one you want. (Term and PIDM have been delivered.) It will be appended to your SQL statement.

Editor Select the icon to display the Banner editor so you can make additional changes to your SQL statement.

. . . . . . . . . . . . . . Fields



Chapter 13

Basic Person

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-3

13 Basic PersonForms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-4

Common Forms Object Library . . . . . . . . . . . . . . . . . (GOQCLIB) . . . . . 13-4

13-1

Table of Contents



13 Basic Person

Overview

13 Basic Person

Basic Person identification forms (forms that follow the naming convention %IDEN, such as APAIDEN, SPAIDEN, and PPAIDEN) are used throughout Banner to capture biographic/demographic information for all persons/non-persons associated with the institution.

Persons/non-persons may belong to any or all of the installed applications (Student, Finance, etc.). All persons/non-persons are first entered into the database using an identification form. The information maintained in this form is specific to the person/non-person and does not relate to the person's/non-person's involvement at the institution. All other modules/applications are dependent on the information captured and maintained in this form. Any changes or additions to a person's/non-person's biographic/demographic information must be made in this form.

Basic Person To maintain consistency in Banner, the identification forms all reference a Banner library called the Common Forms Object Library (GOQCLIB). This library is a form object, just like other forms, but it is used to store common form elements that are used by many other forms.

The common elements that support Basic Person are stored in GOCLIB, and are described in this chapter. Familiarizing yourself with these elements will help you understand Basic Person processing, as well as troubleshoot errors that may occur during your work with Basic Person functionality.


13 Basic Person

Forms

Common Forms Object Library (GOQCLIB)

This library contains the tabs that display in the %IDEN forms and other forms in Banner. The following table lists the forms which display the tabs that exist in the library. The purpose of the tabs that exist in the library is for creating basic information about a person or non-person. The data that is collected through the forms includes Identification number, Name information, Address, Telephone, Biographical information such as age and birth date, E-mail, and Emergency Contact information.

Key Block

Use the Key Block to enter the ID of the person or non-person. If the ID already exists, the person/non-person's name information will display in the name field in the key block. If the ID does not exist, the user can move to the current Identification window to create the new ID and related name information. The user has the option of generating an ID or entering a new ID when creating a new person/non-person.

ID Alternate ID

Address Telephone E-mail Bio Emergency contact

APAIDEN Yes Yes Yes Yes Yes YesAPANAME YesFOAIDEN Yes Yes Yes Yes Yes Yes YesFTMVEND YesFTMFMGR YesFTMCUST YesFTMAGCY YesGOAEMAL YesPPAIDEN Yes Yes Yes Yes Yes Yes YesPPATELE YesPEA1PAY YesPEAHIRE YesSAAQUIK Yes YesSPAEMRG YesSPAIDEN Yes Yes Yes Yes Yes Yes YesSPAPERS YesSPATELE YesSRAQUIK Yes Yes


13 Basic Person

Current Identification Window

The Current Identification window is used to insert or update name information. If the record being added is a person, the first and last names are required. All other fields in the Person block are not required but can be entered for a person. If the record being added is a company or other non-person entity, the non-person name should be added in the non-person block. The fields in the person block cannot be entered for a non-person. The name that displays on this window is a person/non-person's current name and the one that will display on forms through the Banner system. This record can be updated but cannot be deleted. When the name is changed, the old name will become an alternate record. The user ID of the Banner user who originally created the ID will always display in the in the Original creation user field on the current ID window, regardless of whether subsequent name or ID changes have been made.

. . . . . . . . . . . . . . Fields


Confidential (Confidential Message)

Displays when the Confidential check box is checked on the General Person Form (SPAPERS). Confidentiality may be requested by the student or determined by institution policy.


Note: The confidential warning message is displayed for a user when the GUAUPRF Alert Option Display Additional Confidential Warning check box is checked.

Deceased (Deceased Message)

Displays when the Deceased check box is checked on the General Person Form (SPAPERS). You may process data for a person who is deceased.


Note: The deceased warning message is displayed for a user when the GUAUPRF Alert Option Display Additional Deceased Warning check box is checked.

ID ID and name of the person or non-person. Choices differ by form. For example, choices on SPAIDEN are: the Person Search Form (SOAIDEN), the Non-Person Search Form (SOACOMP), or the Alternate ID Search Form (GUIALTI). Use the Options Menu to access the forms, use List for SOAIDEN or Count Query Hits for SOACOMP, or use Duplicate Record from for GUIALTI.

Column: Not base table items (ID and name)


13 Basic Person

. . . . . . . . . . . . . . Fields


ID This field defines the identification number used to access person online.

The ID field is used to create or update a current identification number for a person associated with a record. To change information, the user can type over the current information.

Column: SPRIDEN_ID

Length: 9

Name Type Use this field to enter a type for the name in the key block. For example, name types could be preferred name, legal name, maiden name, formal name, etc.

Column:SPRIDEN_NTYP_CODE

Length: 4

(lookup) List Name Type (GTVNTYP)

SSN/SIN/TIN This field maintains person social security number, social insurance number, or tax identification number.

Column: SPBPERS_SSN

Length: 9

Last Name This field defines the last name of person.

Column:SPRIDEN_LAST_NAME

Length: 60

First Name This field identifies the first name of person.

Column:SPRIDEN_FIRST_NAME

Length: 15

Middle Initial This field identifies the middle name of person.

Column:SPRIDEN_MI

Length: 15

Prefix This field maintains the prefix (Mr., Mrs., etc.) used before person name.

Column:SPBPERS_NAME_PREFIX

Length: 20


13 Basic Person

Suffix This field maintains the suffix (Jr., Sr., etc.) used after person name.

Column:SPBPERS_NAME_SUFFIX

Length: 20

Preferred First Name

This field maintains the preferred first name associated with person.

Column:SPBPERS_PREF_FIRST_NAME

Length: 15

Full Legal Name This field maintains legal name associated with person.

Column:SPBPERS_LEGAL_NAME

Length: 60

Marital Status This field maintains martial status associated with person.

Column:SPBPERS_MRTL_CODE

Length: 1

Non-Person Name

The Non-Person Name field is used to create or change the current name of a non-person associated with the identification number. To change information, the user can type over the current information. Full name of non-person must be entered.

Column: SPRIDEN_LAST_NAME

Length: 60

Last Update User

The ID for the user that most recently updated the record.

Column: SPRIDEN_USER

Length: 30

Last Update Activity Date

This field defines the most current date record is created or changed.

Column: SPRIDEN_ACTIVITY_DATE

Length: 7

. . . . . . . . . . . . . . Fields



13 Basic Person

Last Update Origin

The name of the Banner object that was used most recently to update the row in the SPRIDEN table.

Column: SPRIDEN_ORIGIN

Length: 30

Original Creation User

This field contains the ID of the Banner user who created the new identification record. When a new identification record is created, the user's ID is stored in this field. When the name or ID is changed for a particular Identification record, the ID of the original user, not the user who made the change will continue to display on the current ID window. The ID of the user who made the name or ID change will be reflected on the Alternate ID window on the record that gets inserted when the change is made on the Current ID window.

Column: SPRIDEN_CREATE_USER

Length: 30

Original Creation Create Date

This field contains the date on which Banner user created the new identification record. When a new identification record is created, the date is stored in this field. When the name or ID is changed for a particular Identification record, the date of the original record creation, not date of the change will continue to display in this field on the Current ID window. The date the change was made will be reflected on the Alternate ID window on the record that gets inserted when the change is made on the Current ID window.

Column: SPRIDEN_CREATE_DATE

Length: 7

. . . . . . . . . . . . . . Fields



13 Basic Person

Alternate ID Window

The purpose of the Alternate ID window is to record a persons/non-persons alternate names. Alternate names can be inserted on this window without changing the person's current name.

. . . . . . . . . . . . . . Fields


Name Type Use the Name Type field to enter a type for the name in the key. For example, name types could be preferred name, legal name, maiden name, formal name, etc.

Column:SPRIDEN_NTYP_CODE

Length: 4

(lookup) List Name Type (GTVNTYP)

Change Type This field is used to display the type of change which occurred. The letter I indicates an identification number change, while the letter N indicates a name change.

Column: SPRIDEN_CHANGE_IND

ID The person/non-person's alternate ID. This could represent a previous ID, if the person ID changed, or it could represent an alternate ID associate with the person/non-person.

Column: SPRIDEN_ID

Length: 8

Last Name This field defines the last name of person.

Column:SPRIDEN_LAST_NAME

Length: 60

First Name This field identifies the first name of person.

Column:SPRIDEN_FIRST_NAME

Length: 15

Middle Initial This field identifies the middle name of person.

Column:SPRIDEN_MI

Length: 15

Origin The name of the Banner object that was used most recently to update the row in the SPRIDEN table.

Column: SPRIDEN_ORIGIN


13 Basic Person

Address Window

A person/non-person's addresses are maintained on the address window. A person/non-person can have different types of addressed, for example a mailing address, parent's address, etc. A person/no-person can have one active address per address type as a general rule. An exception to this rule is that Vendors (entered on FTMVEND), Financial Managers (entered on FTMCUST) and Agencies (entered on FTMAGCY) may have multiple active addresses of the same address type. A telephone number can be associated with the address by adding a telephone type and telephone number on the window. The telephone number will become the primary telephone for the address type/sequence.

User The ID for the user that most recently updated the record.

Column: SPRIDEN_USER

Activity Date This field defines the most current date record is created or changed.

Column: SPRIDEN_ACTIVITY_DATE

Create User This field contains the ID of the Banner user who created the alternate identification record. When a new alternate record is created, the user's ID is stored in this field. When the name or ID is changed for a particular identification record on the Current ID window, the ID of the user who is making the change will be reflected in the create user on the Alternate ID window.

Create Date This field contains the date on which the alternate identification record was created. When a new alternate record is created, the date is stored in this field. When the name or ID is changed for a particular identification record on the Current ID window, the date on which the change took place will be reflected in the create date on the Alternate ID window.

. . . . . . . . . . . . . . Fields


From Date This field maintains the effective start date of address associated with person.

The field is used to specify the effective start date of the address associated with person/non-person.

Column:SPRADDR_FROM_DATE

Length: 7

. . . . . . . . . . . . . . Fields



13 Basic Person

To Date This field maintains the effective end date of address associated with person.

The field is used to specify the date until which the address is effective. If the field is left blank, then the address is always effective.

Column:SPRADDR_TO_DATE

Length: 7

Inactivate This check box is used to indicate if the address information is current/active or I - Inactive.

Column: SPRADDR_STATUS_IND

Length: 1

Address Type The Address Type field is used to enter code for address type (e.g. permanent residence, mailing). Click on the Type button to display an Options list from which you can select either a list of valid address codes (STVATYP) or an address summary form. The user can use LIST to display the Address Type Validation Form (STVATYP), from which address type search/selection may be conducted.

Column: SPRADDR_ATYP_CODE

Length: 2

Sequence Number

The Sequence Number field is used to assign an internal sequence number to each address. There is a separate sequencing by address type for each person/non-person.

Column: SPRADDR_SEQNO

Length:2

Street Line 1 This field maintains the first line of the address associated with person/non-person.

Do not put a "#"(pound sign) in the address. This will cause problems with commands in the form GUALETR.

Column: SPRADDR_STREET_LINE1

Length: 30

. . . . . . . . . . . . . . Fields



13 Basic Person

Street Line 2 This field maintains the second line of the address associated with person/non-person.


Length: 30

Street Line 3 This field maintains the third line of the address associated with person/non-person.


Length: 30

City The City field is used to identify the city associated with the person/non-person's address.


Length: 20

State or Province

The State or Province field is used to identify the state or province associated with the person/non-person's address. Click the button or use LIST to display the State/Province Validation Form (STVSTAT) from which search/selection may be conducted by entering state abbreviation in the field.

Column: SPRADDR_STAT_CODE

Length: 3

ZIP/Postal Code The ZIP or Postal Code field is used to enter the ZIP or postal code associated with person/non-person's address. Click the ZIP/PC button or use LIST to display a list of valid codes from the ZIP/Postal Code Validation Form (GTVZIPC). If an existing ZIP/postal code is entered before the city and state are entered on the address window, the city and state will default from GTVZIPC.

Column: SPRADDR_ZIP

Length: 10

. . . . . . . . . . . . . . Fields



13 Basic Person

County The County Code field is used to enter the code assigned to the county associated with person/non-person's address. Click the County button or use LIST to display valid codes from the County Code Validation Form (STVCNTY) from which search/selection may be conducted by entering county name.

Column: SPRADDR_CNTY_CODE

Length: 5

Nation The Nation Code field is used to identify the nation/country associated with person/non-person's address. Click the Nation/Country button or use LIST to display valid codes from the Nation Code Validation Form (STVNATN) which search/selection may be conducted by entering name of nation/country in the field.

Column: SPRADDR_NATN_CODE

Length: 5

Telephone Type The Telephone Type field is used to enter code for phone type (e.g. permanent residence, mailing). Click on the Type button or use LIST to display the Phone Type Validation Form (STVTELE) from which phone type codes can be selected.

Column: SPRTELE_TELE_CODE

Length: 4

Telephone The Telephone (Telephone Number) field is used to identify the telephone number of the person/non-person associated with identification form.

Click on the Telephone button to display the Telephone window where the user can create an unlimited number of telephone numbers associated with a person. The telephone number can be associated with an address type and sequence number. The primary indicator must be Y to display with the address information.

Column: SPRTELE_PHONE_AREA

Length: 3

Column: SPRTELE_PHONE_NUMBER

Length: 7

Column: SPRTELE_PHONE_EXT

Length: 4

. . . . . . . . . . . . . . Fields



13 Basic Person

Source The Source field is used to identify how the address information was created or updated. Click the Source button or use LIST to display valid codes from the Address Source Code Validation Form (STVASRC).

Column: SPRADDR_ASRC_CODE

Length: 4

Delivery Point This field is used to designate the delivery point for mail as established by the Postal Service.

Column: SPRADDR_DELIVERY_POINT

Length: 2

Correction Digit The Correction Digit field is defined by the Postal Service and is used to determine the digits used for delivery related to the ZIP code.

Column: SPRADDR_CORRECTION_DIGIT

Length: 1

Carrier Route The addresses to which a carrier delivers mail. In common usage, carrier route includes city routes, rural routes, highway contract routes, post office box sections, and general delivery units.

Column: SPRADDR_CARRIER_ROUTE

Length: 4

Last Update User

The ID for the user that most recently updated the record.

Column: SPRADDR_USER

Length: 30


This field defines the most current date record is created or changed.

Column: SPRADDR_ACTIVITY_DATE

Length: 7

Preferred Address

The preferred address displays on APAIDEN only. It is a calculated value which depends on the preferred address type that is set on APACONS for the person. The preferred address check box on the Address window will be 'checked' on the current active address having the same address type as the preferred address type designated on APACONS.

. . . . . . . . . . . . . . Fields



13 Basic Person

Telephone Window

A person/non-person's telephone numbers are maintained on the telephone window. The telephone number field consists of the area code and telephone number. When creating a telephone number the telephone type and telephone number are required. Alternatively, the telephone type and international number fields can be used. If the international number is used, the entire phone number should be entered in the international field, including the international code and telephone number. The telephone can be associated with an address by entering the address type and sequence number. The telephone umber will display on the address window if the primary indicator is checked.

Preferred Region The preferred region displays in APAIDEN only. The Preferred Region Address Type is the address type that identifies the address to which you want to send information that has a geographical orientation. For instance, if an advancement individual wants to receive, at a business address, notifications of alumni events that are being held near that business, you would enter the address type for that business address as the Preferred Region Address Type.

The Preferred Region Address Type is optional; it defaults based on the Preferred Address Type defined on APACONS. Although it isn't used by any processes or reports, it can be incorporated into correspondence by using Banner Letter Generation. For more information, see the "Letter Generation" chapter of the Banner General User Guide.

Combined Mailing

The Combined Mailing Address Type is used in conjunction with the Combined Mailing Name in creating labels. This address type determines which address is used when one piece of mail is to be sent jointly to two IDs. The combined mailing information Address type is set on APANAME.

Employment Details

This indicator is checked if the address displaying is associated with an employment record on APAEHIS. The button navigates to APAEHIS to display the related employment history record.

This field only displays on APAIDEN.

. . . . . . . . . . . . . . Fields



13 Basic Person

. . . . . . . . . . . . . . Fields


Telephone Type Telephone type code.

Column: SPRTELE_TELE_CODE

Length: 3

Telephone Number

The first three positions are for the area code. The next seven positions are for the telephone number. The last four positions are for the phone extension.

Column: SPRTELE_PHONE_AREA

Length: 3

Column: SPRTELE_PHONE_NUMBER

Length: 7

Column: SPRTELE_PHONE_EXT

Length: 4

Primary Primary indicator to denote primary telephone numbers based on telephone types.

Column: SPRTELE_PRIMARY_IND

Length: 1

Unlisted Unlisted telephone number indicator.

Column: SPRTELE_UNLIST_IND

Length: 1

Inactivate Status of telephone number, active or inactive. Check the box to inactivate the telephone number.

Column: SPRTELE_STATUS_IND

Length: 1

International Access

Free-format international access code for telephone number including country and city code and telephone number.

Column: SPRTELE_INTL_ACCESS

Length: 16


13 Basic Person

Biographical Window

A person's biographical information is maintained on the Biographical window.

Comment Comment relating to telephone number.

Column: SPRTELE_COMMENT

Length: 60

Address Type Optional address type code associated with telephone number.

Note: The telephone number will display on the address window on the address that has the same address type and sequence number as entered on the telephone window, if the primary checkbox is checked.

Column: SPRTELE_ATYP_CODE

Length: 2

Sequence Optional address sequence associated with telephone number.

Note: The telephone number will display on the address window on the address that has the same address type and sequence number as entered on the telephone window, if the primary checkbox is checked.

Column: SPRTELE_ADDR_SEQNO

Length: 2

Activity Date This field defines the most current date record is created or changed.

Column: SPRTELE_ACTIVITY_DATE

Length: 7

User The ID for the user that most recently updated the record.

Column: SPRTELE_USER_ID

Length: 30

. . . . . . . . . . . . . . Fields



13 Basic Person

. . . . . . . . . . . . . . Fields


Gender ID's gender. Select Male or Female, or Not Available if the gender is unknown.

Column: SPBPERS_SEX

Length: 1

Birth Date ID's birth date. You may not enter a future birth date, i.e., one which is greater than the system date.

Column: SPBPERS_BIRTH_DATE

Length: 7

Age ID's age. Calculated by the system based on the date of birth. The age is not stored in the database, but is calculated each time the form is called.

SSN/SIN/TIN ID's Social Security Number, Social Insurance Number (Canada), or Tax Identification Number (non-person) as applicable. Institutions in other countries can use this field to store any 9-digit identifier, such as a TFN (Tax Form Number) for Australia.

SSN/SIN/TIN is used by some reports and processes, instead of the ID, such as tax documents (W-20, T2202A, etc.). Tape loads can match against either ID or SSN/SIN/TIN.

Column: SPBPERS_SSN

Length: 9

Confidential Confidential indicator. To indicate that information about this person should remain confidential, select the checkbox. If the box is checked, then the message Confidential displays on any forms with the ID in the key information.

The Confidential indicator does not control any other system processing.

Column: SPBPERS_CONFID_IND

Length: 1


13 Basic Person

Deceased Select if the ID is deceased. Online processing is not prevented for deceased IDs; however, the message Deceased displays on any forms with the ID in the key information. You may request and run a transcript for a student who is deceased. However, the Grade Mailer Report (SHRGRDE) and associated processing are prohibited for a deceased person.

Column: SPBPERS_DEAD_IND

Length: 1

Deceased Date Date of death if deceased. If you enter the deceased date, then the system automatically checks the Deceased check box.

Column: SPBPERS_DEAD_DATE

Length: 7

Citizenship ID's citizenship.

Column: SPBPERS_CONFID_IND

Length: 1

(lookup) List Citizen Type Validation list

Marital Status ID's marital status.

Column: SPBPERS_MRTL_CODE

Length: 1

(lookup) List Marital Status Validation List

Religion ID's religion.

Column: SPBPERS_RELG_CODE

Length: 2

(lookup) List Religion Code Validation list

Legacy ID's relationship to alumni of the institution.

Column: SPBPERS_LGCY_CODE

Length: 1

(lookup) List Legacy Code Validation list

. . . . . . . . . . . . . . Fields



13 Basic Person

Ethnicity ID's ethnic background. This is critical for IPEDs and additional reports.

Column: SPBPERS_ETHN_CODE

Length: 1

(lookup) List Ethnic Code Validation list

New Ethnicity This field identifies the ethnic code defined by the U.S. government. The valid values are 1 - Not Hispanic or Latino, 2 - Hispanic or Latino, or null.

Column: SPBPERS_ETHN_CDE

Length: 1

Ethnicity and Race Confirmed

This field identifies the race and ethnicity has been confirmed. Valid values are (Y)es, (N)o and null.

Column: SPBPERS_CONFIRMED_RE_CDE

Length: 1

Confirmed Date This field identifies when the race and ethnicity has been confirmed.

Column: SPBPERS_CONFIRMED_RE_DATE

Length: 7

Veteran File Number

ID's Vietnam file number.

Column: SPBPERS_VETC_FILE_NUMBER

Length: 10

. . . . . . . . . . . . . . Fields



13 Basic Person

Race Block

The Race block is used record the race of the person. Multiple races can be added for a person.

The U.S. 2000 Census was collected using new race and ethnicity categories, and the EEOC has mandated that Affirmation Action reports for 2005 use this census data

Veteran Category

If the ID is associated with one of the categories in the pulldown list, they may be eligible for Veteran-related programs, if applicable. This field is also used in Banner Human Resources VETS-100 reporting. The values for the pulldown list are:

Category--Employees Included in

None--Non-veterans

Other Protected Veteran Only--Other protected veterans who did not serve in Vietnam

Vietnam Veteran Only--Vietnam veterans who do not meet the criterion for other protected veteran only

Both Vietnam and Other Eligible Veteran--Vietnam veterans who meet the criterion for other protected veteran only

Column: SPBPERS_VERA_IND

Length: 1

Active Duty Separation

This is the date the person was separated from active duty. Enter in DD-MON-YYYY format.

Column: SPBPERS_ACTIVE_DUTY_SEPR_DATE

Length: 7

Special Disabled Veteran

Indicator to identify an individual as a special disabled veteran.

Column: SPBPERS_SDVET_IND

Length: 1

Last Update User

This is the ID of the user who created or updated the record.

Column: SPBPERS_USER_ID

Length: 30


This is the date the record was created or updated.

Column: SPBPERS_ACTIVITY_DATE

Length: 7

. . . . . . . . . . . . . . Fields



13 Basic Person

for comparison purposes. Not all U.S. government departments have adopted this requirement. SunGard SCT anticipates that the National Center for Education Statistics (NCES) will eventually release new IPEDS reporting parameters that require institutions to provide information based on the new OMB categories. Thus, institutions should begin the process of collecting the information based on the new categories.

E-mail Window

The E-mail window allows you to set up one or more e-mail addresses or URLs for any Banner ID. A person/non-person can have multiple addresses of the same e-mail address type (for example, personal and professional). Only one however, can be designated as the preferred address. This window will also allow you to specify if an e-mail address should appear on the web.

. . . . . . . . . . . . . . Fields


Race This field identifies the person's institution race code as defined on GORRACE.

Column: GORPRAC_RACE_CDE

Length: 3

User User who inserted or last updated the data.

Column: GORPRAC_USER_ID

Length: 30

Activity Date This field defines the most current date a record is added or changed.

Column: GORPRAC_ACTIVITY_DATE

Length: 7

. . . . . . . . . . . . . . Fields


E-mail Type The type of e-mail address.

Column: GOREMAL_EMAL_CODE

Length: 4

E-mail Address The E-mail address.

Column: GOREMAL_EMAIL_ADDRESS

Length: 90


13 Basic Person

Emergency Contact Window

The Emergency Contact window is used to capture emergency contact information for persons. The information you can enter here includes: contact name, relationship to the person with the emergency, and address and phone information for the person to be contacted.

Preferred This column indicates if the e-mail address is the preferred contact address.

Column: GOREMAL_PREFERRED_IND

Length: 1

Inactivate The status of the e-mail address: (A)ctive, or (I)nactive.

Column: GOREMAL_STATUS_IND

Length: 1

Display on Web Indicates whether a e-mail address should appear on the Web.

Column: GOREMAL_DISP_WEB_IND

Length: 1

URL This field is display-only on the E-mail window. If the check box is checked, it indicates that the e-mail type entered is a URL.

Column: GTVEMAL_URL_IND

Length: 1

Comment This is a free-format comment regarding the e-mail information.

Column: GOREMAL_COMMENT

Length: 60

Activity Date The date on which the row was added or modified.

Column: GOREMAL_ACTIVITY_DATE

Length: 7

User The user ID when the row was added or modified.

Column: GOREMAL_USER_ID

Length: 30

. . . . . . . . . . . . . . Fields



13 Basic Person

. . . . . . . . . . . . . . Fields


Priority Priority indicator associated with emergency address of person record.

Column: SPREMRG_PRIORITY

Length: 1

Contact Last Name

Last name of person associated with emergency address information.

Column: SPREMRG_LAST_NAME

Length: 25

First Name First name of person associated with emergency address information.

Column: SPREMRG_FIRST_NAME

Length: 15

Middle Initial Middle initial of person associated with emergency address information.

Column: SPREMRG_MI

Length: 1

Relationship This field identifies the relationship between emergency contact person and the person record.

Column: SPREMRG_RELT_CODE

Address Type The address type associated with the emergency address. The purpose of this field on the emergency contact window is to allow the user to choose an address from the persons list of address to associate with the emergency contact. For example the emergency contact person maybe the parent of a student and when creating the emergency contact record, you can choose from the students list of existing address's. The address chosen will default into the emergency contact record. If a change is made to an address on the emergency contact window, the emergency contact's address will be updated but the person's (i.e., student's) address will not be updated.

Column: SPREMRG_ATYP_CODE

Length: 2


13 Basic Person

Street Line 1 Line one of emergency address.

Column: SPREMRG_STREET_LINE1

Length: 30

Street Line 2 Line two of emergency address.


Length: 30

Street Line 3 Line three of emergency address.


Length: 30

City City associated with emergency address.

Column: SPREMRG_CITY

Length: 20

State State associated with emergency address.

Column: SPREMRG_STAT_CODE

Length: 3

Zip or Postal Code

Zip code associated with emergency address.

Column: SPREMRG_ZIP

Length: 10

Nation Nation/country associated with emergency address.

Column: SPREMRG_NATN_CODE

Length: 5

Telephone Phone number associated with emergency address.

Column: SPREMRG_PHONE_AREA

Length: 3

Column: SPREMRG_PHONE_NUMBER

Length:7

Column: SPREMRG_PHONE_EXT

Length:4

. . . . . . . . . . . . . . Fields



13 Basic Person

Last Update User

User who inserted or last update the data.

Column: SPREMRG_USER_ID

Length: 30


Most current date that the record was created or changed.

Column: SPREMRG_ACTIVITY_DATE

Length: 7

. . . . . . . . . . . . . . Fields



Chapter 14

Reports & Processes

Reports and Processes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-3

14 Reports & ProcessesList of Reports and Parameters . . . . . . . . . . . . . . . . . (GJRRPTS) . . . . . . 14-4Letter Generation Print Report . . . . . . . . . . . . . . . . . (GLRLETR) . . . . . . 14-8Person Geo Region/Divisions Report . . . . . . . . . . . . . . (GORPGEO) . . . . . 14-12SEVIS Batch Export Process . . . . . . . . . . . . . . . . . . . (GORSEVE) . . . . . 14-19SBGI Geo Region/Divisions Report . . . . . . . . . . . . . . . (GORSGEO) . . . . . 14-26Address Purge . . . . . . . . . . . . . . . . . . . . . . . . . (GPPADDR) . . . . . 14-28Document Code Delete Process . . . . . . . . . . . . . . . . (GUPDELT) . . . . . 14-32Document Detail Report . . . . . . . . . . . . . . . . . . . . (GURDETL) . . . . . 14-34Insert Output Program . . . . . . . . . . . . . . . . . . . . . (GURINSO) . . . . . 14-36Institution Role Maintenance Process . . . . . . . . . . . . . . (GURIROL) . . . . . 14-37Print Dynamic Help for a Form . . . . . . . . . . . . . . . . . (GURHELP) . . . . . 14-39Data Element Dictionary . . . . . . . . . . . . . . . . . . . . (GURPDED) . . . . . 14-42Condensed Table Listing . . . . . . . . . . . . . . . . . . . . (GURTABL) . . . . . 14-45Document Code Report . . . . . . . . . . . . . . . . . . . . (GURTEXT) . . . . . 14-48PIN Create Process . . . . . . . . . . . . . . . . . . . . . . . (GURTPAC) . . . . . 14-50

COBOL Processes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-52

Automatic Letter Compilation Process . . . . . . . . . . . . . (GLOLETT) . . . . . . 14-52Population Selection Extract Process . . . . . . . . . . . . . . (GLBDATA) . . . . . 14-54Letter Extract Process . . . . . . . . . . . . . . . . . . . . . . (GLBLSEL) . . . . . . 14-57Parameter Selection Compile Process . . . . . . . . . . . . . . (GLBPARM) . . . . . 14-60User ID/Password Verification Process . . . . . . . . . . . . . (GUAVRFY) . . . . . 14-61

14-1

Table of Contents



14 Report

November 200614-3 Confidential

Report

, list of parameters, and sample

Reports &14 Repo

s & Processes

General Release 7.4 User Guide

s and Processes

This chapter describes each report and process in the Banner General System. A descriptionreport are given where appropriate.

Processes rts & Processes

14 R


List

Desc name may be specified, or a wildcard nformation that is printed includes le occurrence indicator, low range, rameters may optionally be printed.

Param Values

ed. rs. r their

lts for Y Print default values.

N Do not print default values.

eports & Processes


of Reports and Parameters (GJRRPTS)

ription This report lists all reports/batch processes and their associated parameters. A single job may be used to print all jobs that begin with a specified string of characters. Parameter iparameter number, description, length, type, required/optional indicator, single/multiphigh range, validation label, system default, and validation values. User defaults for all pa

eters Name Required? Description

Jobs to be Selected No Wildcard that determines what reports are listEnter % to list all reports and their parameteOther wildcard selections may also be used; foexample, G% lists only the General reports andparameters.

Print User Level Defaults No Code that determines whether user-level defauthe parameters are printed.

14 Report


Report Sa

08-JA PAGE 1

NAME-----GJRRP

P NO VALIDATION LABEL -- - ------------------------------ 01

02

GLBLS

P NO VALIDATION LABEL -- - ------------------------------ 01

02

s & Processes


mple

N-2001 16:04:41 Systems & Computer Technology List of reports and parameters

JOB TITLE/DESCRIPTION VALIDATION LABEL-- ------------------------------ ------------------------------TS list of reports and parameters

ARAMETER DESCRIPTION LENGTH TYPE R/O S/M LOW RANGE HIGH RANGE ----------------------------- ------ ---- --- --- ---------------------- ---------------------Jobs to be Selected 30 Char O S System Default:Validation Values: User Defaults: FAISMNT R%

Print User Level Defaults 1 Char O S System Default: YValidation Values: N Y User Defaults: FAISMNT N FIMSUSR Y SAISUSR Y

EL Letter Extract

ARAMETER DESCRIPTION LENGTH TYPE R/O S/M LOW RANGE HIGH RANGE ----------------------------- ------ ---- --- --- ---------------------- ---------------------Application 30 Char R S System Default:Validation Values: User Defaults:

Selection date 9 Date O S System Default:Validation Values: User Defaults:

14 R


08 PAGE 2

N--GL

VALIDATION LABEL ----- ------------------------------

GL

VALIDATION LABEL ----- ------------------------------

eports & Processes


-JAN-2001 16:04:41 Systems & Computer Technology List of reports and parameters

JOBAME TITLE/DESCRIPTION VALIDATION LABEL----- ------------------------------ ------------------------------BLSEL (continued)

PARAMETERNO DESCRIPTION LENGTH TYPE R/O S/M LOW RANGE HIGH RANGE -- ----------------------------- ------ ---- --- --- ---------------------- -----------------03 Address Type 3 Char R M System Default: Validation Values: User Defaults:

04 Process Pending 1 Char R S System Default: Validation Values: User Defaults:

05 Term Code 6 Char R S System Default: Validation Values: User Defaults:

06 Initials 4 Char O S System Default: Validation Values: User Defaults:

OLETT Automatic Letter Compilation Financial Aid Automatic Letter Compilation Program

PARAMETERNO DESCRIPTION LENGTH TYPE R/O S/M LOW RANGE HIGH RANGE -- ----------------------------- ------ ---- --- --- ---------------------- -----------------01 Type Indicator 2 Char R S System Default: Validation Values: User Defaults:

14 Report


08-JA PAGE 9

P

s & Processes


N-2001 16:04:41 Systems & Computer Technology List of reports and parameters

* * * REPORT CONTROL INFORMATION * * *

Report Name: GJRRPTS

Jobs Selected: g%rint User Defaults: Y Line Count: 45 Jobs Count: 11

14 R


Lett

Desc ed to produce a download file for

Param Values

. One Application Inquiry Form (GLIAPPL)

0 None

1 Word

2 WordPerfect

d for Y All pending letters extracted for the application code

N Specific letter code

s only d.


ecific ame). *) and

eports & Processes


er Generation Print Report (GLRLETR)

ription This report prints letters with data extracted by the GLBLSEL process. It can also be usMicrosoft Word for Windows or WordPerfect.


Application Code Yes Application code for the letters being printedcode may be entered per run.

Word Processor Extract Option

Yes Type of output file to be created.

Process ALL Pending Letters

No Code that determines which letters are printethe application code.

Letter Code No Code of the letter to be printed. Letter code irequested if all pending letters are not selecte

Sort Variable No Name of the variable used to sort letters in a sporder (for example, the ZIP/postal code or nThe variable name must start with an asterisk (must be entered in all capital letters.

14 Report


e Term Code Validation Form (STVTERM).

e A Admission

R Recruiting

B Billing

H History

F Registration

Y Print sample letter.

N Do not print sample letter.

d d.

d d.

d d.

Parameteued)

Values

s & Processes


Term Code Yes * Term code for which letters are being printed. Onterm code must be specified per run.

Module Code Yes Code that identifies the module associated with thletters being printed. This code updates the Mail Table.

Audit Indicator No Code that determines whether a sample letter is printed.

Free Format Date 1 No Freeform date (up to 30 characters) that is printeon letters where the *DATE1 variable is reference



rs (contin Name Required? Description

14 R


Aid Year Inquiry Form (ROIAIDY)

Paramued)

Values

eports & Processes


Aid Year Code Yes† Aid year code for Financial Aid letters.

* for Student applications only

† for Financial Aid letters only

eters (contin Name Required? Description

14 Report


Sample L

R 3 V

D

I r

I b p c a M i

W c I

S

B U S

s & Processes


etter

April 11, 2002

ichard Scott12 Bridle Rd.illanova PA 19101

ear Richard,

t's a pleasure to send the information you requested. Take your timeeading it to find out more about the Institute of Technology.

invite you to learn firsthand about us by visiting the campus. We'lle glad to welcome you for a personal visit between 8:00 a.m. and 5:00.m. Monday through Friday. Just stop by or, better yet, write orall for an appointment. Our Preview provides another good way to seend learn about the Institute of Technology. It takes placeAY 30, 2002, so mark your calendar now. We will send you morenformation after APRIL 30,2002.

e appreciate each opportunity to serve you as you make your collegehoice. Of course, we hope that you'll agree with us that the nstitute of Technology can be for you.

incerely,

. Andrew Stevens IIIniversity President.C.T. Institute of Technology

14 R


Repo

0819

EX

eports & Processes


rt Sample

-JAN- 2001 16:30:32 Systems & Computer Technology PAGE 19301 Letter Generation Print Report GLRLETR

AUDIT MODE, SAMPLE LETTERS, NO UPDATES


RUN SEQUENCE NUMBER: APPLICATION CODE:RECRUITINGTRACT FOR 1=WORD, 2=WORD PERFECT, 0=NONE:0 PRINT ALL PENDING:y LETTER CODE: SORT BY VARIABLE: TERM CODE:199301 MODULE CODE:R AUDIT MODE:Y DATE 1:APRIL 11, 2002Parameter entered but not used by letter DATE 2:APRIL 30,2001Parameter entered but not used by letter DATE 3: LINE COUNT:45

LETTER COUNT:35

14 Report


Person

Descripti combination with the rules with the GORPGEO table.

Paramete Values

e C Use all IDs in collector table GORCGEO

I Use individual ID in collector table

P Use population selection

h of

ry e


s & Processes


Geo Region/Divisions Report (GORPGEO)

on This process assigns regions to individuals using the data in the GORCGEO collector table indefined on the Geographic Region Rules Form (SOAGEOR). These regions are then stored

rs Name Required? Description

Use Collector File Yes Code that determines what IDs are used to run thprocess.

ID No ID of the person for whom you want to create geographic region/division records.

Application Code No Code that identifies the application group for whicthe population selection was defined. All or none the population selection parameters must be entered.

You can use the Population Selection Extract InquiForm (GLIEXTR) to review the people who will bprocessed in the load based on the selection identifier and application code entered.

14 R


ish to on

LCT). eters


tion ified

one of

n. Address Type Code Validation Form (STVATYP)

un in Y Run in sleep/wake mode.

N Do not run in sleep/wake mode.

The default is 60 seconds.

sleep/ Printer Validation Form (GTVPRNT)

Param Values

eports & Processes


Selection Identifier No ID of the population selection with which you wwork. The selection identifier must be definedthe Population Selection Inquiry Form (GLISAll or none of the population selection parammust be entered.

Creator ID No User ID of the person who created the populaselection. The creator ID must have been specwhen defining the selection identifier. All or nthe population selection parameters must be entered.

Address Type No Address type for the ID or population selectio

Run in Sleep/Wake Mode

No Code that determines whether the process is rsleep/wake mode.

Sleep/Wake Time No Number of seconds to sleep, if the sleep/wakeparameter is Y.

Sleep/Wake Printer No Printer used in the Sleep/Wake process, if the wake parameter is Y.


14 Report


A Run in audit mode.

U Run in update mode.

Y Print all details.

N Suppress details and print summary totals only.

Paramete Values

s & Processes


Audit Indicator Yes

Report Indicator Yes


14 R


Repo

10-N PAGE 1 GORPGEO

ID - GEOD ACT5894 ALUM ALURECRUIT DEVEL ALUM

4627 ADMISSIONS RECR RECR

A000 ADMISSIONS RECR RECR



7010 ALUM ALURECRUIT DEVEL ALUM

7010 ALUM ALURECRUIT DEVEL ALUM



A000 ALUM ALURECRUIT ALUM


8755 ALUM ALURECRUIT RECR ALUM

eports & Processes


rt Sample

OV-2000 10:11:56 SunGard Higher Ed University Person Geo Region/Divisions

NAME ATY SEQ CITY ST ZIP NATN CNTY GEOR 46377 Skinner, Daniel C PR 1 N Charleston SC 294182122 BALT/WASH BALT/WASH SOUTHEAST TRISTATE

96830 Rangel, Cecilia A PR 1 Pomfret Center CT 06259 MINIEAST NEWENGLAND RECRDZK

06488 Emilio, Emily PR 1 Pomfret CT 06259 MINIEAST NEWENGLAND RECRDZK

06490 Emilio, Anthony PR 1 Pomfret CT 06259 MINIEAST NEWENGLAND RECRDZK

06492 Carpenter, Rose PR 1 Pomfret CT 06259 MINIEAST NEWENGLAND RECRDZK

00050 Adams, Aretha L MA 1 Petterson AL 359012626 BALT/WASH BALT/WASH SOUTH TRISTATE

00050 Adams, Aretha L MA 2 Gadsden AL 359012626 BALT/WASH BALT/WASH SOUTH TRISTATE

97210 Zaurtskie, Tom PR 1 Boston MA 02134 MINIEAST NEWENGLAND RECRDZK

97211 Zarutskie, Kevin PR 1 Boston MA 02134 MINIEAST NEWENGLAND RECRDZK

06496 Endicott, Joe MA 1 Bayonne NJ 25841 BALT/WASH BALT/WASH TRISTATE

06497 Lusa, Jill PR 1 Pomfret CT 06259 MINIEAST NEWENGLAND RECRDZK

55511 Ramon, Else PR 1 LLLL MD 222222 BALT/WASH BALT/WASH MIDATLANTC TRISTATE

14 Report


10-NOV-2 PAGE 2 GORPGEO

ID - NAM EOD ACT87555551 LURECRUIT

A0000649 DMISSIONS ECR ECR


A0000650 LUM LURECRUIT LUM LURECRUIT

A0000650 LUM LURECRUIT ECR LUM LURECRUIT


A0000650 ECRUITER LURECRUIT EVEL



A0000650 ECRUITER EVEL



A0000650 ECRUITER

s & Processes


000 10:11:56 SunGard Higher Ed University Person Geo Region/Divisions

E ATY SEQ CITY ST ZIP NATN CNTY GEOR G1 Ramon, Else PR 1 LLLL MD 222222 TRISTATE A

8 Lusa, Jack PR 1 Pomfret CT 06259 MINIEAST A NEWENGLAND R RECRDZK R

9 Lemon, Jane PR 1 Pomfret CT 06259 MINIEAST A NEWENGLAND R RECRDZK R

0 Langley, William PR 1 Fairfax VA 20891 BALT/WASH A BALT/WASH A TRISTATE A TRISTATE A

1 Foster, Janice Annette PR 1 lllll MD 20901 BALT/WASH A BALT/WASH A MIDATLANTC R TRISTATE A TRISTATE A

2 Hall, Mary Ann PR 1 Boston MA 02134 MINIEAST A NEWENGLAND R RECRDZK R

3 Hall, John PR 1 San Francisco CA 97123 RECRDMF R WESTCOAST A WESTCOAST D

4 Foster, William PR 1 xxxxxx MD 2222222 BALT/WASH A BALT/WASH A MIDATLANTC R TRISTATE A TRISTATE A

5 Foster, Heather PR 1 uuuuu MD 20904 BALT/WASH A BALT/WASH A MIDATLANTC R TRISTATE A TRISTATE A

6 Evan, Lee PR 1 Lonestar TX 7079 RECRDMF R SOUTH D

7 Evan, Lisa PR 1 Lonestar TX 78099 RECRDMF R SOUTH D

8 Evan, Matilda Ruth PR 1 Lonestar TX 77809 RECRDMF R SOUTH D

9 Evans, Ruth Ann PR 1 LL TX 78099 RECRDMF R

14 R


10-N PAGE 3 GORPGEO

ID - GEOD ACTA000 DEVEL

A000 ADMISSIONS RECR


8765 ALUM ALURECRUIT ALUM ALURECRUIT


4596 DEVEL

1122 ALUM ALUM RECR


5006 RECRUITER DEVEL

5006 DEVEL

0789 RECRUITER DEVEL

A000 ALUM ALURECRUIT DEVEL ALUM

0586 RECRUITER ALURECRUIT DEVEL

eports & Processes


OV-2000 10:11:56 SunGard Higher Ed University Person Geo Region/Divisions

NAME ATY SEQ CITY ST ZIP NATN CNTY GEOR 06509 Evans, Ruth Ann PR 1 LL TX 78099 SOUTH

06510 Wilson, Dennis PR 1 Brooklyn MA 06810 MINIEAST NEWENGLAND

79689 Gray, Katrina M PR 1 Boston MA 02134 MINIEAST NEWENGLAND RECRDZK

59000 Long, Harriet MA 1 Washington DC 20052 BALT/WASH BALT/WASH TRISTATE TRISTATE

19991 Isaacs, Alexandra M PR 1 Boston MA 02134 MINIEAST NEWENGLAND RECRDZK

16156 Mckenzie, Jacqueline PR 1 Provo UT 58744 SOUTHWEST

33445 Jones, Meghan M MA 1 Malvern PA 12345 BALT/WASH NYMETRO PHILAMETRO

06515 Howard, Fran PR 1 Pomfert CT 06259 MINIEAST NEWENGLAND RECRDZK

74111 Kloss, Wilma MA 1 Lonestar TX 78099 RECRDMF SOUTH

74111 Kloss, Wilma MA 2 Sandy UT 84093 SOUTHWEST

94444 Flowers, Sophie PR 1 Houston TX 78099 RECRDMF SOUTH

00685 Chaves, Tom MA 3 Charlotte NC 28211 BALT/WASH BALT/WASH SOUTHEAST TRISTATE

43010 Geiling, Grant PR 1 San Bernardino CA 92407 RECRDMF WESTCOAST WESTCOAST

14 Report


10-NOV- PAGE 4 GORPGEO

RPTNAMEVERSIONSOURCE SLEEP WAUDIT OREPORT LINE CO

RECORD

s & Processes


2000 10:11:56 SunGard Higher Ed University Person Geo Region/Divisions * * * REPORT CONTROL INFORMATION * * *

: GORPGEO: 4.1IS COLLECTOR TABLEAKE MODE: NOR UPDATE INDICATOR: UINDICATOR : YUNT : 55

COUNT: 111

14 R


SEVI

This .S. Government for SEVIS reporting in a b

If you o-populate = Y, GORSEVE will create the st GOBSEVS table for that person with data

N selection.

For m

N Business Action from the Options menu. You

GOR pdate. It appears on GOASEVR, and can contain one o

• P

• E

• W

• C

• N

• M

• R

• X

eports & Processes


S Batch Export Process (GORSEVE)

process allows you to extract information about students and exchange visitors so it can be sent to the Uatch transaction via the Internet. All dependent data is extracted as well.

have created the appropriate rules, and if you have selected the parameters Business Action = Y and Autudent and exchange visitor records (Business Actions), and it will automatically populate columns in thethat exists in other Banner tables (Auto-population).

ote: When either of these parameters is set to Y, you must run GORSEVE with IDs or with a population

ore information, refer to Chapter 4, Processing.

ote: When you are on the SEVIS Information Form (GOASEVS), you can also select Auto-populate andcannot select them when your cursor is in the key block, however.

SEVE uses the Transmittal Status Code field to determine if the record should be sent in the next batch uf the following valid values:

- Pending a response after the transmittal was created

- Transmittal was created manually via the SEVIS RTI, pending response

- Needs batch transmittal

- Received the acceptance response from the U.S. Government, processing is completed

- No action was taken

- Must be entered manually on the U.S. Government’s website

- Returned with error, either by the SEVIS Transfer Adaptor (SEVISTA) or by the Bureau

- Disregard, invalid record

14 Report


Note: run the install script to make sure the

GORSEV tion of like data elements), and changes the submit da au.

GORSEV nnot be transmitted without this conversion.

GORSEV ASEVS to the last transaction for the person on GOAS not create a SEVIS transmittal history record but will, i r own purposes or it can be imported into fsaATLAS

• If GO tudent adjudicated events). You can review the r U.S. Government. When you run GORSEVE in up at allows transmittal to SEVISTA.

• If GO udent adjudicated events). You are not given the o ls to SEVISTA and changes the transmittal statu ctivity, anyone who has changes pending but no SE an Update record cannot.)

Note: ta directly into the SEVIS RTI on the U.S.

The proc o an exchange visitor. Different information is sent to indicator associated with the creation code on the SE cess will extract student data. If it contains 2, GORSEV

s & Processes


As you move from processing your SEVIS records manually to using the new batch interface, you mustTransmittal Status Code contains N.

E creates a record with the transmittal status code P for each structure updated (a structure is a combinate. Then it hands the records off to SEVISTA, which converts them to XML and sends them to the Bure

E converts special characters (ampersand, quotation mark, etc.) into their ASCII equivalents. The files ca

E has three modes, audit, update and extract. In audit and update mode, the process compares data on GOEVR. If there are differences, GORSEVE will create a GOASEVR record. In extract mode, GORSEVE willnstead, create a file of SEVIS data in comma-separated value (CSV) format. This file can be used for you.

RSEVE is running in audit mode, the records are created with a transmittal status code of W (or M for secords and change the transmittal status code from W to X for any records you do not wish to send to thedate mode, it will change the transmittal status code from W to P and will populate a temporary table th

RSEVE is running in update mode, the records are created with a transmittal status code of W (or M for stpportunity to review the records. Instead, GORSEVE populates a temporary table that allows transmittas code to P. Also, if you run GORSEVE in update mode and use parameter #8 to print accounts with no aVIS ID will be included on the report. (A Create record can be sent for a person with no SEVIS ID, but

GORSEVE will not transmit records to SEVISTA if they have adjudicated fields. You must enter that daGovernment’s website.

ess will look at GOBSEVS_SVCR_CODE for each record so determine if the record applies to a student or t the U.S. Government, depending on whether the person is a student or an exchange visitor. If the usageVIS Creation Reason Code Validation Table (GTVSVCR) contains 1, the person is a student, and the proE will extract exchange visitor data.

14 R


GOR

1. e of W (or M for an adjudicated event for a .

2. hem off to SEVISTA to be converted to XML for SEVIS is pending. If Banner IDs or a population

GOR aximum of 250 records, you may have a number of fil

Batch

y

The b ding order, otherwise they will be rejected by the U.S.

At th

1.

2. ment History Table (GORSVEH) and SEVIS etected in the SEVIS Data Table (GOBSEVS), VIS Activity Site Table (GORSVAS).

3. TSVBT). The creation of the Batch Header row

4.

5.

6.

eports & Processes


SEVE is a two-step process:

GORSEVE creates GORSEVS records (either student or exchange visitor) with the transmittal status codstudent). It is affected by the parameters for the Banner ID or what was set up in a population selection

GORSEVE looks for records with a transmittal status code of W in the GORSEVE table, and then hands tthe U.S. Government. Then it changes the transmittal status code to P to indicate that the response fromselection was entered for processing, only those students or exchange visitors will be processed.

SEVE creates separate batches for student and exchange visitor records. Since each batch can contain a mes to transmit to the U.S. Government in a batch.

IDs are in the following format:

ymmddhhmissxx.XML

atch ID is the date and timestamp, followed by a 2-digit sequence number. You must send them in ascenGovernment.

e time specified for transmission to the U.S. Government, GORSEVE:

Assigns a batch ID to the set of records being transmitted

Creates SEVIS History Table (GORSEVS), SEVIS Dependent History Table (GORSEVH), SEVIS EmployActivity Site History Table (GORSVAH) records where changes to the person’s information have been dSEVIS Dependent Data Table (GORSEVD), SEVIS Employment Information Table (GORSVEI), and SE

Creates rows in temporary tables for each batch (GOTSVBH) and each transaction within each batch (GOsignals SEVISTA to transmit the records to SEVIS.

Uses the processing parameters, where necessary, to create the SEVIS data.

Changes the transmittal status code to P (pending response from SEVIS) for all the records

Prints the SEVIS Record Extract Report, including all records transmitted in that batch.

14 Report


Note:

Paramete Value

er

s & Processes


It is recommended that you schedule GORSEVE to run every night.


School Code Yes Your institution’s code as defined by the U.S. Government

User ID Yes The U.S. Government’s ID for the person runningGORSEVE

Program Number Yes The 9-character number the U.S. Government assigned to your institution’s exchange visitor program

Banner IDs No If you are running in update mode or audit modeand you want to include a few people, list the BannIDs and the process will process only those IDs

Application Code No The application code for population selection, anoptional field used when creating a batch via population selection

Selection Identifier No The selection identifier for population selection

Creator ID Yes The Banner ID for the person who created the population selection

14 R


in the s been

N the message will not be displayed

Y the message will be displayed for all IDs that do not have a SEVIS ID

The U.S. Government differentiates between create records (information about a person they do not have in their database yet) and update records (a change for a person they have in their database). Create records will never have a SEVIS ID; all update records must have one.

If this parameter is Y, you will not receive the warning message for create records, but you will receive it for update records.

Param Value

eports & Processes


Print No Activity No Determines if a warning message is displayed LIS file, Updates cannot be sent until SEVIS ID haassigned


14 Report


A Audit mode

U Update mode

E Extract mode

a

e E

n ll

t

Determined by fsaATLAS.

Paramete Value

s & Processes


Mode Yes The mode the process will run under

Department Owner ID for Extract

Yes, if using fsaATLAS

Used by fsaATLAS. If you are creating the CSV filefor another purpose, this parameter is optional.

Caution: The minimum data required by GORSEVE for each record Extracted iscreation reason or termination reason code. Records that do not have one or thother will not be processed by GORSEVand included in the CSV file, but the records will appear on the .lis file.

Records that have both a creation reasocode and a termination reason code winot be processed by GORSEVE.

GORSEVE requires the 02 - Batch Approver parameter to execute in Extract mode, but it is norequired by fsaATLAS. You can enter any value forBatch Approver; it cannot be left blank (be null).


14 R


Repo

The ve. The records are listed in Banner ID order.

30 1 GORSEVESt-- -----424242121818181821A0A0ZYA0A0A0A0A0A0A0

Contd...2 30 GORSEVESt-- -----

eports & Processes


rt Sample—SEVIS Batch Export Process (GORSEVE)

GORSEVE process generates a report, the SEVIS Record Extract Report, using the parameters listed abo

-MAR-2003 08:16:54 AM SunGard Higher Ed SEVIS Extract Process u/EV ID Name | Tran | Result/Comment -----------------------------------------------------------------------------------------------------------9887341 No Last Name, Othello | | Cannot update - Required EditPersonal field(s) missing.9887341 No Last Name, Othello | | Cannot update - EditProgramInfo Major Code missing.9887341 No Last Name, Othello | | Cannot update-EditStudentFinancial Term mos or exp. missing.3456987 Nevermind MH, Bernard | | Cannot create transmittal-US addr field(s) missing.1489814 Blake, Ian Russell | | Cannot update - Required EditPersonal field(s) missing.1489814 Blake, Ian Russell | | Cannot update - EditProgramInfo Study Length missing.1489814 Blake, Ian Russell | | Cannot update-EditStudentFinancial Term mos or exp. missing.1489815 Blake, Nichole Ellen | | Cannot create transmittal-Create comment required.0009307 Dennis Johnson, Doris Jan | | Cannot create transmittal-Session dates required.0006417 Guillaume, Ernesto Rudolp | W | UAddr info not updated - Required field(s) missing.0006417 Guillaume, Ernesto Rudolp | | Cannot update - EditProgramInfo Study Length missing.B000000 Peters, Mathew Ryan | | Cannot update - Required US Address field(s) missing.0006831 SEVIS, Carlos Jose | | Cannot create transmittal-Study length missing.0006786 Sevis, One Test | | Cannot update-StudentReg Session date or Addr Info missing.0006335 Patterson, Anna Grace | P | Student create 0006786 Sevis, One Test | P | Student create 0007306 Sevis, Stu Test | P | Student create 0006790 Sevis, Test3 Test | P | Student create 0006339 Thompson, Alisa Marie | P | Student create

-MAR-2003 08:16:54 AM SunGard Higher Ed 2 SEVIS Extract Process u/EV ID Name | Tran | Result/Comment -----------------------------------------------------------------------------------------------------------

CONTROL SUMMARY ---------------

Program Name : GORSEVE(6.0) One up Number : 1067719 Print Report : Number of lines per page :

Total pages Printed : 2

****** END OF REPORT ******

14 Report


SBGI G

Descripti th the region rules set up on the he GORSGEO table.

Paramete Values

A Run in audit mode.

U Run in update mode.

Y Print all details.

N Suppress details and print summary totals only.

u t

Source/Background Institution Validation Form (STVSBGI)

n

6, g

-

s & Processes


eo Region/Divisions Report (GORSGEO)

on This process assigns regions to high schools using the high school address in combination wiGeographic Region Rule Form (SOAGEOR). These high school regions are then stored in t


Audit Indicator Yes

Report Indicator Yes

Source/Background Inst Code

No Source/background institution code for which yowant to assign region records. Leave blank to selecall codes.

Activity Date No Beginning date for selecting all changed records oSOBSBGI.

For example, if the activity date equals 10-MAY-200the process runs against all SOBSBGI records havinan activity date greater than (or equal to) 10-MAY2006.

14 R


Repo

11- PAGE 1 GORSGEO

SB CODE GEOD CODE I DATE

002 LANTC ALUM N 11-NOV-00 LANTC ALURECRUIT N 11-NOV-00 LANTC DEVEL N 11-NOV-00 EAST ALURECRUIT N 11-NOV-00 METRO ALURECRUIT N 11-NOV-00 LANTC RECR 22-OCT-00 METRO RECR 11-NOV-00

11- PAGE 2 GORSGEO

RPTVERAUDREPSBGACTLIN

NUMNUMNUMNUM

eports & Processes


rt Sample

NOV-2000 17:11:41 SunGard Higher Ed University Source/Background Summary

GI Name of Institution CITY ST ZIP NATION COUNTY GEOR

000 SunGard Higher Ed High School Philadelphia PA 19101 MIDAT MIDAT MIDAT NORTH PHILA MIDAT PHILA

NOV- 2000 17:11:41 SunGard Higher Ed University Source/Background Summary * * * REPORT CONTROL INFORMATION * * *

NAME: GORSGEOSION: 4.1IT - UPDATE INDICATOR: UORT INDICATOR : YI CODE : 002000IVITY DATE :E COUNT : 55

BER SBGI PROCESSED : 1BER SBGI INSERTED : 2BER SBGI UPDATED : 5BER PRINTED : 7

14 Report


Address

Descripti (date must exist to be purged),

ecords. It only deletes phone is more than one telephone

R simply reports the error, skips

is rolled back. This allows the ple phone records exist.

Paramete Values

1 Purge by address expiration date. (Date must exist to be purged.)

2 Purge inactive addresses. (Purge occurs regardless of expiration date.)

is Date format of DD-MMM-YYYY

s & Processes


Purge (GPPADDR)

on This process purges address information for people. You can purge by address expiration dateor you can purge all inactive addresses (regardless of date).

Note: The Address API (gb_address) maintains the deletion of associated telephone rrecords if there is exactly one phone number associated with the address. If therenumber, then the API raises an exception. When an exception is raised, GPPADDthat address, and continues processing.

In audit mode, the API is called to delete the address, and then that transactionuser to view any addresses in the .lis file that the API cannot delete because multi


Purge Option Yes Criteria by which address information should be purged.

Address Selection Date Yes† Date used with option 1 to purge addresses. Addresses with an expiration date on or before thdate are purged.

† if option 1 chosen

14 R


Address Type Code Validation Form (STVATYP)

A Audit mode (no addresses purged)

U Update mode (addresses purged)

Param Values

eports & Processes


Address Types to be Bypassed

No Address types to be excluded from the purge process. Multiple types are permitted.

Run Mode Yes Code that indicates the mode for running theprocess.


14 Report


Report Sa

24-MA PAGE 1 GPPADDR

2821s

AChec

AT&T

Adams

Adams

Adams

Adams

Adams

Adams

s & Processes


mple

Y-2006 09:12:42 BANNER University Address Purge Audit Report Only

mithx Rachel, A2051385 A00020705MA I Greenwood Po Box 169 Montego B Y, R710750 76

k Vendor With A Nice Long Name for T VCHECKAP I PO BOX 247 Fall River, MA 02720

new name 10/26/04, V9MA I 888 Pacific Ave San Francisco, CA 98773

, Adam A00023291MA 29-NOV-2004 I 56 Crandall Cranford, RI 43222 133 29-NOV-2004 I 8685 Moody St Cypress, CA 90630

, April CD0000002BU I 315 Maple Glen Malvern, PA 19355

, Cindy A00027108MA I 1st address Malvern, PA 11111 Address cannot be deleted, more than one phone number is associated.

, Jennifer A00027116MA I 3 Broomall, PA 19008 Address cannot be deleted, more than one phone number is associated.

, John A00027110MA I 1 Malvern, PA 19355 Address cannot be deleted, more than one phone number is associated.

, Julie A00027115MA I 2 Broomall, PA 19008 Address cannot be deleted, more than one phone number is associated.

14 R


24 PAGE 19 GPPADDR

ReCuPuAdEx Au

EnNuNu

eports & Processes


-MAY-2006 09:12:42 BANNER University Address Purge Audit Report Only


port Name........................: GPPADDRrrent Release....................: 7.3rge Option.......................: 2dress Selection Date.............: 24-MAY-2006cluded Address Type(s)...........: PRdit Mode.........................: A

tities Selected..................: 197mber of Potential Address Deletes: 421mber of errors encountered.........: 94

14 Report


Docum

Descripti XT tables. Job parameters allow

) be restricted to staff members tion should be exercised when GURFEED (not just those from ithout chance of recovery.

ecord Function. Enter the deleted in the parameter value ers are similar and only requires

and GURTEXT.

Paramete Values

s & Processes


ent Code Delete Process (GUPDELT)

on This new process is used to delete inappropriate documents from the GURFEED and GURTEspecification of multiple document numbers.

Note: It is recommended that access to the Document Code Delete Process (GUPDELTresponsible for maintenance of data in the GURFEED and GURTEXT tables. Causelecting a document for removal. This process can be used for any document in FUPLOAD). As such, AR, Advancement, and HR information could be deleted w

To enter multiple Document Codes, enter the first document to be deleted. Use the Insert Rparameter value “01” in the parameter number column and enter the next document to be column. The Insert Record/Duplicate Record Function can also be used if document numbchanging a few values for each.

Some sub-systems may not be able to recreate transactions that have been fed to GURFEED

Delete operations are not performed in Audit Mode.


Enter Document Number

Yes Alpha, 8 characters, allow multiple numbers.

14 R


A Audit

U Update

e

Param Values

eports & Processes


Enter Run Mode Yes Code that indicates the mode for running theprocess.

Enter System ID Yes Specify SYSTEM_ID for the document(s) to bdeleted.


14 Report


Docum

Descripti terface to Finance Table

Paramete Values

s & Processes


ent Detail Report (GURDETL)

on This report is used to list transaction data for any document stored in the Banner General In(GURFEED).


Document Number Yes Alpha, 8 characters, allow multiple numbers.

14 R


Repo

GU 26-APR-2002 01:46:05

DO --CM==

R NUMBER ITEM SEQ# TYPE ACTION BANK DOCUMENT REF NO - ---- ---- ---- ---- ------ ---- --------- J1 DOCREF J1 DOCREF

DO --CM==

NUMBER ITEM SEQ# TYPE ACTION BANK DOCUMENT REF NO - ----- --- ---- ---- ------ ---- --------- J1 DOCREF J1 DOCREF

GU 26-APR-2002 01:46:05

eports & Processes


rt Sample

RDETL SunGard Higher Ed Development Document Detail report Page : 1

CUMENT# SUB# TRANSACTION DOCUMENT TOTAL USER ID System ID DATE------- ---- ----------- -------------- -------- ---------000014 26-MAR-02 20.00 JWILDER COMPUP==============================================================================

SEQ# RULE CHART INDEX FUND ORG ACCOUNT PROGRAM ACTIVITY LOCATION PROJECT TRANSACTION DB/C CLASS CODE AMOUNT --- ------ ------ ------ ------ ----- ------ ------ ------- ------- ------- ----------- ---- ---1 JE16 1 JFUNDA JORGA JACTA JPROGA JLOCNA 10.00 D 2 JE16 1 JFUNDA JORGA JACTA JPROGA JACTVA 10.00 C

CUMENT# SUB# TRANSACTION DOCUMENT TOTAL USER ID System ID DATE------- ---- ----------- -------------- -------- ---------000013 26-MAR-02 20.01 JWILDER COMPUP==============================================================================

SEQ# RULE CHART INDEX FUND ORG ACCOUNT PROGRAM ACTIVITY LOCATION PROJECT TRANSACTION DB/CR CLASS CODE AMOUNT --- ------ ------ ------ ------ ----- ------ ------ ------- ------- ------- ------------ ---- --1 JE16 1 JFUNDA JORGA JACTA JPROGA JACTVA 10.01 D 2 JE16 1 JFUNDA JORGA JACTA JPROGA JLOCNA 10.00 C

* * * REPORT CONTROL INFORMATION - GURDETL Release: 5.4.1 * * *

RDETL SunGard Higher Ed Development Document Detail report Page : 2

14 Report


Insert O

Descripti the Saved Output Review Form

ogram was executed.

the database.

otifies entry to each

s & Processes


utput Program (GURINSO)

on This program reads a file from the file system and loads it into the database. You can then use(GJIREVO) to access the file on the database.

This program is run from the operating system with the following command line switches:

Switch Required? Description

-j <job/process name> Yes Job or process that generated the file.

-i <input file> Yes File to be loaded into the database.

-n <number> Yes One-up number created when the batch pr

-w <username> Yes User who ran the job.

-o <output file name> No New name of the file after it is loaded into

-t No Switch that turns on sql_trace.

-x No Switch that turns on extended debugging; nfunction.

14 R


Insti

Desc le information in the GORIROL to determine users’ roles, and then PI to insert, update, or delete those

an be run at any time to update the role information stored in the tner data synchronization.

Running it from the host is not eshooting purposes.

Param Value

Choices come from the Application Inquiry Form (GLIAPPL).

Choices come from the Population Selection Inquiry Form (GLISLCT).

.

eports & Processes


tution Role Maintenance Process (GURIROL)

ription The Institution Role Maintenance Process (GURIROL) is used to maintain institution rotable. This process uses the rules that are set up on the Business Rules Form (GORRSQL)calls the gb_institution_role.p_maintain_roles procedure in the Institution Role Aroles from GORIROL.

You can use Population Selection to limit the number of users processed. This process cGORIROL table. This process is used to support Integration for e-Learning. The personGORIROL table is used by Integration for e-Learning's extract and event process for par

Note: This process is designed to be run via the Job Submission Form (GJAPCTL). supported by SunGard Higher Education, and should only be used for troubl


Application Code No Application code of the Population Selection.

Selection ID No ID of the Population Selection.

Creator ID No ID that created the Population Selection rules

User ID No ID of user who selected the population.

14 Report


ss For Integration for e-Learning clients, INTCOMP is the valid value.

.

n

For Integration for e-Learning clients, all valid institution and custom roles are supported.

Paramete Value

s & Processes


Role Group Yes The Institution Role group is the same as the ProceCode used on the Business Rules Form (GORRSQL).

Role No Person Institution role(s) that you want to processYou can use multiple roles and/or population selection.

If you leave this parameter blank, then all institutioand custom roles will be processed.


14 R


Prin

Desc t should be run only by your data

ms with a wildcard indicator (for

ard indicator (for example, G%).

Param Values

ards

1 Form help

2 Form and block help

3 Form, block, and field help

eports & Processes


t Dynamic Help for a Form (GURHELP)

ription This report lists all the Dynamic Help for a selected system, module, or form. This reporcenter.

To print Help for a single form, specify the form name (for example, GJAPDEF).

To print Help for the forms in a single module, specify the first two characters of the forexample, GJ% for all forms in the Job Submission module).

To print Help for all forms in a system, use the system designation followed by the wildc


Form Name Yes Form(s) for which help is to be printed. Wildcare acceptable.

Level Yes Level of help to be printed.

14 Report


Report Sa

The for val (GJ thi A p Pro als

The and cha par ins The sys acc * *NO

s & Processes


mple

PROCESS SUBMISSION CONTROL FORM ( GJAPCTL )

purpose of the Job Submission Form is to define parameter values, specific processes, and to submit the report using these parameterues. The characteristics defined in the Parameter Definition FormAPDEF) are used to validate the values for each parameter entered ins form. FORM DEPENDENCIESrocess must first be created and then defined to the system using thecess Maintenance Form (GJAJOBS). The parameters for the report musto be defined using the Parameter Definition Form (GJAPDEF).

PARAMETER DEFINITION FORM ( GJAPDEF )

purpose of the Parameter Definition Form is to define the parameters, their validation characteristics, for specific processes. Theracteristics defined in this form will be used to validate theameter values entered on the Job Submission form (GJAPCTL). Thisures parameter values are validated before a report is submitted. FORM DEPENDENCIES process must first be created and then defined/assigned to thetem using the Process Maintenance Form (GJAJOBS) before it can beessed by the Parameter Definition Form.

TE* This form is a control form. Only the person who designed and/or created the specific report/process should enter or edit the parameter definitions.

14 R


eports & Processes


DEFAULT PARAMETER VALUE VALIDATION FORM ( GJAPDFT )

The purpose of the Default Parameter Value Validation Form is to definethe user level default values for any/all parameters for specificprocesses. The values entered on this form will be used as the defaultson the Job Submission form (GJAPCTL). This form allows the restrictionof parameters to only user-defined values. FORM DEPENDENCIESThe process must first be created and then defined to the system usingthe Process Maintenance Form (GJAJOBS) before it can be accessed by theParameter Definition Form.**NOTE* This form is a control form. Only the person who designed and/or created the specific process should enter or edit the parameter definitions.

PARAMETER VALUE VALIDATION FORM ( GJAPVAL )

The purpose of the Parameter Value Validation Form is to define thevalid values for any/all parameters for specific SQL*Reports. Thevalues entered on this form will be used to validate the parametervalues entered on the Job Submission form (GJAPCTL). This insuresparameter values are validated before a report is submitted. This formallows the restriction of parameters to only user-defined values. FORM DEPENDENCIESThe process must first be created and then defined/assigned to thesystem using the Process Maintenance Form (GJAJOBS) before it canbe accessed by the Parameter Definition Form.**NOTE* This form is a control form. Only the person who designed and/or created the specific report/process should enter or edit the parameter definitions.


RPTNAME .............................GURHELPReport Run Date ....................... 01/08/2000SQL*Forms Application Name ............ g%

RECORD COUNT - Forms .................. 48

14 Report


Data Ele

Descripti n comments.

Paramete Values

is

re

re

N Do not increase the top margin.

Y Increase the top margin (default).

Y Underline.

N Do not underline (default).

s & Processes


ment Dictionary (GURPDED)

on This report shows information for all the database columns, including type, scale, and colum


USERID of Table Creator

Yes Oracle account under which the table was created(owner of the table). For example, a General tableowned by GENERAL.

Table(s) to be Reported Yes Name of a specific table to be printed. Wildcards aallowed.

USERID of View Creator No Oracle account under which the view was created (owner of the view).

View(s) to be Reported No Name of a specific view to be printed. Wildcards aallowed.

Binding Margin Option Yes Code that indicates whether an extra binding margin is required.

Heading Underline Option

Yes Code that indicates whether report and page headings are underlined.

14 R


Repo

============================ ============================ ith One Up Number and Number ds. used along with Job and y records. sed along with Job and One Up y records. stored for this parameter. this record was created. llaneous field for optional

eports & Processes


rt Sample

Date: 01/08/2000 Page: 1

TABLE: GJBCOLR

CREATOR: GENERAL

Jobs Parameter Collector Table

======================================================================================= Column Name Type Width Scale Nulls Column Comments =============================== ====== ===== ===== ========= ========================== GJBCOLR_JOB CHAR 30 NOT NULL JOB: Job name used along w to uniquely identify recor GJBCOLR_ONE_UP_NO NUMBER NOT NULL ONE UP NO: Sequence number Number to uniquely identif GJBCOLR_NUMBER CHAR 2 NOT NULL NUMBER: Parameter number u Number to uniquely identif GJBCOLR_VALUE CHAR 30 NOT NULL VALUE: Actual value being GJBCOLR_ACTIVITY_DATE DATE 7 NOT NULL ACTIVITY DATE: Actual date GJBCOLR_MISC_VALUE CHAR 30 NULL MISCELLANEOUS VALUE: Misce use.

14 Report


======================== ======================== dure or report. his job. rameter. parameter. dentify parameter type of or (N)umber. to identify whether or al or (R)equired. identify whether or not or (M)ultiple times. eter was created or last ange boundary for this range boundary for this parameter. lidation label to be d through the Job all for List of Values

s & Processes


CREATOR: GENERAL

Jobs Parameter Definition Table

=========================================================================================== Column Name Type Width Scale Nulls Column Comments =============================== ====== ===== ===== ========= ============================== GJBPDEF_JOB CHAR 30 NOT NULL JOB: Name of executable, proce GJBPDEF_NUMBER CHAR 2 NOT NULL NUMBER: Parameter number for t GJBPDEF_DESC CHAR 30 NOT NULL DESCRIPTION: Description of pa GJBPDEF_LENGTH NUMBER 2 NOT NULL LENGTH: Length of the defined GJBPDEF_TYPE_IND CHAR 1 NOT NULL TYPE INDICATOR: Indicator to i (C)haracter, (D)ate, (I)nteger GJBPDEF_OPTIONAL_IND CHAR 1 NOT NULL OPTIONAL INDICATOR: Indicator not this parameter is (O)ption GJBPDEF_SINGLE_IND CHAR 1 NOT NULL SINGLE INDICATOR: Indicator to this parameter occurs (S)ingle GJBPDEF_ACTIVITY_DATE DATE 7 NOT NULL ACTIVITY DATE: Date this param modified. GJBPDEF_LOW_RANGE CHAR 30 NULL LOW RANGE: Specifies the low r parameter. GJBPDEF_HIGH_RANGE CHAR 30 NULL LOW RANGE: Specifies the high parameter. GJBPDEF_HELP_TEXT CHAR 78 NULL HELP TEXT: Long description of GJBPDEF_VALIDATION CHAR 30 NULL VALIDATION: Parameter level va performed when job is submitte Submission system. GJBPDEF_LIST_VALUES CHAR 30 NULL LIST VALUES: Name of form to c for this parameter.

14 R


Con

Desc

Param

are tion

eports & Processes


densed Table Listing (GURTABL)

ription This report lists selected system tables.


Table Owner Yes Owner of the tables you wish to list, such as GENERAL.

Table Name Yes Name of the tables you wish to list. Wildcards allowed. For example, to list all General validatables enter gtv%.

14 Report


Report Sa

SYST THIS CORPOFOR AWRITT All Bconve NOTE: a al Al by tr

s & Processes


mple

EMS AND COMPUTER TECHNOLOGY, CORP. DATA DICTIONARY REPORT ON TABLES FOR THE FOLLOWING OWNER GENERAL 10/19/00 * * * * * * * * * * * * * * * * * * * * * * * CONFIDENTIAL BUSINESS INFORMATIONDOCUMENT IS PROPRIETARY INFORMATION OF SYSTEMS & COMPUTER TECHNOLOGYRATION AND IS NOT TO BE COPIED, REPRODUCED, LENT OR DISPOSED OF, NOR USEDNY PURPOSE OTHER THAN THAT WHICH IT IS SPECIFICALLY PROVIDED WITHOUT THEEN PERMISSION OF SAID COMPANY. * * * * * * * * * * * * * * * * * * * * * * * TABLE NAMING CONVENTIONSanner table names are seven characters in length using the followingntions: abcdddd where a = A (for ALUMNI SYSTEM) C (for COURTS SYSTEM) F (for FINANCE SYSTEM) G (for GENERAL SYSTEM) N (for POSITION CONTROL) P (for PAYROLL SYSTEM) R (for FINAID SYSTEM) S (for STUDENT SYSTEM) T (for A/R SYSTEM) U (for UTILITIES SYSTEM) where b = a one position code identifying the primary module owning the table. Values vary with each where c = a one position code identifying the type of table. Valid values are: B = BASE DATA TABLE R = REPEATING DATA TABLE V = VALIDATION TABLE (if b = T) V = VIEW (if b not = T) where dddd = a unique four position table name. Maximum Record Lengths are the sum of all column widths defined intable. Please remember that columns described as "NULL" arelowed to be empty, in which case, would occupy no space on disk.so remember that columns described as type "CHAR" will be condensed Oracle, and the actual disk space used would not include anyailing blanks.

14 R


TA SP

eports & Processes


1BLE FIELD SIZE D TYPE NULL MAXIMUM RECORD LENGTHRIDEN Person Identification/Name Repeating Table SPRIDEN_PIDM 8 NUMBER N SPRIDEN_ID 9 VARCHA N SPRIDEN_LAST_NAME 60 VARCHA N SPRIDEN_FIRST_NAME 15 VARCHA Y SPRIDEN_MI 15 VARCHA Y SPRIDEN_CHANGE_IND 1 VARCHA Y SPRIDEN_ENTITY_IND 1 VARCHA Y SPRIDEN_ACTIVITY_DATE 7 DATE N SPRIDEN_USER 30 VARCHA Y SPRIDEN_ORIGIN 30 VARCHA Y SPRIDEN_SEARCH_LAST_NAME 60 VARCHA Y SPRIDEN_SEARCH_FIRST_NAME 15 VARCHA Y SPRIDEN_SEARCH_MI 15 VARCHA Y SPRIDEN_SOUNDEX_LAST_NAME 4 CHAR Y SPRIDEN_SOUNDEX_FIRST_NAME 4 CHAR Y SPRIDEN_NTYP_CODE 4 VARCHA Y MAXIMUM RECORD LENGTH 278

14 Report


Docum

Descripti nt Text Table (GURTEXT).

s & Processes


ent Code Report (GURTEXT)

on This report is used to list document numbers currently stored in the External Feed Docume

There are no parameters for this report.

14 R


Repo

GU 24-JUN-2002 03:59:05

Do--BKBKBKBK

GU 24-JUN-2002 03:59:05

eports & Processes


rt Sample

RTEXT SunGard Higher Ed Development GURTEXT Document List Page : 1

cument Code-------000104000107000109000114

* * * REPORT CONTROL INFORMATION - GURTEXT Release: 5.4.1 * * *

RTEXT SunGard Higher Ed Development GURTEXT Document List Page : 2

14 Report


PIN Cre

Descripti s PIN records and external user

Paramete Values

Application Inquiry Form (GUIAPPL)


Y Print a detailed listing of results.

N Print the control report.

s & Processes


ate Process (GURTPAC)

on This process will take a population selection (list of PIDMs) and will assign Third Party AccesIDs based on settings in the Enterprise PIN Preferences Form (GUAPPRF).


Application Yes Application for the population selection.

Selection ID Yes Selection identifier for the population selection.

Creator ID Yes Creator of the Selection ID rules.

User ID Yes ID of the person who performed the population selection.

Print Detail Report? Yes Specifies if the detail report should be printed.

14 R


Repo

24

ID2161612161212161216121212171

24

eports & Processes


rt Sample

-OCT-2002 14:18:00 SunGard Higher Ed DEVELOPMENT PAGE 1 PIN Creation Process GURTPAC

NAME Result 1119506 Abbe, Anthony PIN Already Exists0009604 Abernathy, Holister Sheraz PIN Already Exists0009109 Adason, Marlene T PIN Generated0009306 Charles, Corey PIN Already Exists0009508 Charles, Henry PIN Generated5630492 Charter, Clifford PIN Already Exists0009604 Childress, Nancy PIN Already Exists0009613 Clark, Donald James PIN Generated0392871 Clark, Lindsay PIN Already Exists0009517 Clark, Susan PIN Generated0493827 Compin, Shantay PIN Already Exists0009622 Cooper, Carla PIN Generated0009110 Jackson, James Jarvis PIN Generated0000014 Zevan, David J. PIN Already Exists

-OCT-2002 14:18:00 SunGard Higher Ed DEVELOPMENT PAGE 2 PIN Creation Process GURTPAC

* * * REPORT CONTROL INFORMATION - GURTPAC - RELEASE 5.5 * * * RPTNAME:GURTPAC

APPLICATION ID:....................BANSTU_SAMPLE SELECTION ID:......................MEN CREATOR ID:........................SAISUSR USER ID:...........................SAISUSR PRINT DETAIL:......................Y

Number in Population:..............16

Number of PINs Generated:..........6

14 Report


COBO

Automa

Descripti ile called glolett_NUMBER.log

(determined by records existing ulation selection rules to be

s & Processes


L Processes

tic Letter Compilation Process (GLOLETT)

on This process compiles variables and population selection rules in the Banner database. A log fis created, where NUMBER is the one-up sequence number created at runtime.

When you run GLOLETT, the variables and population selection rules waiting to be compiledin GJBPRUN) are compiled. Running the GLBPARM process can identify variables and popcompiled.

Note: You can model a more complex query on the following example:

Example where the same table is used in both the query and the subquery: SELECT DISTINCT(SPRIDEN_PIDM),SYSDATE FROM SATURN.SPBPERS A,SATURN.SPRIDEN WHERE SPBPERS_PIDM = SPRIDEN_PIDM AND SPRIDEN_LAST_NAME = 'Smith' AND SPRIDEN_CHANGE_IND IS NULL AND SPRIDEN_PIDM NOT IN (SELECT SPBPERS_PIDM FROM SATURN.SPBPERS WHERE SPBPERS_DEAD_IND = 'Y' AND SPBPERS_PIDM = A.SPBPERS_PIDM )

14 R


Param Values

%V Variable

%S Population selection

or

eports & Processes



Type Indicator Yes Record type to be compiled.

Application Name Yes Application code of the variable or populationselection to be compiled.

Selection ID or Variable Name

No Code that identifies the population selection variable.

Creator ID of Selection ID

Yes User ID of the Oracle user who created the population selection or variable.

14 Report


Populat

Descripti inition Rules Form (GLRSLCT). ules in two existing population

ence number created at runtime.

Paramete Values

ill

s. l

s.

s & Processes


ion Selection Extract Process (GLBDATA)

on This process selects a population based on the rules entered on the Population Selection DefIt can also create a population based on either the union, intersection, or difference of the rselections. A log file called glbdata_NUMBER.log is created, where NUMBER is the one-up sequ


Selection Identifier 1 Yes ID of the first existing population selection that wbe used to create a new population selection.

Note: Any dynamic parameters for this populationselection are entered after the standard parameterYou must enter a non-blank value for each 88 leveprompt.

Selection Identifier 2 No ID of the second existing population that will be used to create a new population selection.

New Selection Identifier No ID of the new population selection that will be created from the two existing population selection

Description for New Selection

No Free-form description of the new population selection.

14 R


lting I Include only those IDs that are extracted by both populations selections.

M Include all IDs extracted by the first population selection except those IDs extracted by the second population selection.

U Include all IDs extracted by the first population selection and all IDs extracted by the second population selection. If an ID is selected by both, include only once.

cation Application Inquiry Form (GLIAPPL)

Param Values

eports & Processes


Union/Intersection/Minus

No Code that determines the contents of the resupopulation.

Application Code Yes Application associated with the two existing population selections. This becomes the appliassociated with the new population selection.


14 Report


S Displays no debug information for selected parameters.

I Displays no debug information for selected parameters.

Y Shows debug information for SQL, inserts, and paragraphs.

Paramete Values

s & Processes


Creator ID of Selection ID

Yes Oracle ID of the user who created the two existingpopulation selections.

Detail Execution Report No Code that determines the contents of the detail execution report.


14 R


Lett

Desc letter. These variable values are created on request. A log file called at runtime.

bles). This limit is controlled by the

Param Values

Y Process all pending letters for the letter code.

N Process the letter code for a specific population.

this

for


tter is Population Selection Inquiry Form (GLISLCT)

eports & Processes


er Extract Process (GLBLSEL)

ription This process extracts values from the database for the variables that appear in a specifiedmerged into letters with the Letter Generation Print Report (GLRLETR). An error list isglblsel_NUMBER.log is created, where NUMBER is the one-up sequence number created

There is a limit on the number of variables that can be added to a letter (about 121 variaWS-PARM-LIST value in GLBLSEL.pco.


Application Yes Application associated with the letter being processed.

Process Pending Letters Yes Code that determines how the letter code is processed.

Letter Code Yes Code of the letter being processed.

Note: Any dynamic parameters for variables inletter code are entered after the standard parameters. You must enter a non-blank valueeach 88 level prompt.

Selection ID Yes ID of the population selection for which the lebeing processed.

14 Report


n

Term Code Validation Form (STVTERM)

Aid Year Inquiry Form (ROIAIDY)

e

el

d.

Paramete Values

s & Processes


Creator ID Yes Oracle ID of the user who created the populationselection.

User ID Yes Oracle ID of the user who extracted the populatiowith the Population Selection Extract Process (GLBDATA).

Term Code No* Code of the term for which you wish to process pending letters.

Aid Year No† Aid year for which you wish to process pending letters.

Address Selection Date No Address date for which the address of choice must beffective.

You can define a system-level parameter default onthe Parameter Definition Form (GJAPDEF) to usethe system date as this date. However, any user-levdefaults would override it.

If the job is executed with a null value for this parameter, the current system date is used. If the users save their parameters, the null would be save

If users want some other value than the current system date, they must enter a not-null value on GJAPCTL.


14 R


ss, Address Type Code Validation Form (STVATYP)

el file. Y Write error messages for IDs for which variable data could not be extracted.

N Do not write error messages.

il S Show SQL statements.

I Show SQL statements and inserts.

Y Show paragraphs.

Param Values

eports & Processes


Address Type Yes Type codes of the addresses you wish to proceprefixed by the priority of each type code.

Detailed Error Report No Code that determines the contents of the glbls

Detailed Execution Report

No Code that determines the contents of the detaexecution report.

* for Student applications only

† for Financial Aid letters only


14 Report


Parame

Descripti Automatic Letter Compilation h variable/population selection, ons and variables appears on the ce number created at runtime.

Paramete Values


Y Extract variable.

N Do not extract variables.

s & Processes


ter Selection Compile Process (GLBPARM)

on This process identifies population selections and variables that need to be recompiled by theProcess (GLOLETT) in certain situations, such as when you change application rules. For eaca record is inserted into the list of records awaiting compilation. The list of population selectireport. A log file called glbparm_NUMBER.log is created, where NUMBER is the one-up sequen


Application Code Yes Application you wish to compile.

Extract Variables Indicator

Yes Code that determines whether variables are extracted for the application.

14 R


User

Desc .log is created, where NUMBER is the

eports & Processes


ID/Password Verification Process (GUAVRFY)

ription This process verifies the correct user ID and password. A log file called guavrfy_NUMBERone-up sequence number created at runtime.

This process contains no parameters.

Troubleshooting

Troubleshooting

Letter Generation Messages

As you work with the Letter Generation programs, Banner provides diagnostic messages to alert you to problem that might occur along the way and gives you directions to remedy the situation. Messages may indicate a data entry mistake, such as an invalid or missing value, or other problem.

Troubleshooting If an Oracle error occurs during the running of the GLBLSEL process, the message usually ends with the word “Aborting.” To help you diagnose and correct these situations, the system displays an error number in the glblsel.log file as "SQLCODE=####." Refer to your Oracle Error Messages Manual for help.

14 Troubleshooting

Listed below are some of the common Banner diagnostic messages you may see, with their corrective actions.

Message: <address type> is not valid

Cause: The address type entered as a parameter is not defined on the Address Type Code Validation Form (STVATYP).

Action: Define the address type on STVATYP, or enter the correct address type for the parameter.

Message: Application <application> does not exist

Cause: The application entered as a parameter is not defined on the Application Definition Rules Form (GLRAPPL).

Action: Define the application on GLRAPPL, or enter the correct application for the parameter.

Message: CANNOT PROCESS ALL VARIABLES

Cause: No compiled variables (GLRCMPL records) were found for any variables in the letter.

Action: Recompile all variables, and re-run GLBLSEL. (Recompiling requires running GLBPARM and GLOLETT. See the Banner General Technical Reference Manual for details.)

December 2007 General Release 7.5Confidential User Guide T-1

Troubleshooting

Message: Letter <letter> does not exist

Cause: The letter code entered as a parameter is not defined on the Letter Code Validation Form (GTVLETR).

Action: Define the letter code on GTVLETR, or enter the correct letter code for the parameter.

Message: Program must be run using Pending Letters or Selection

Cause: Running GLBLSEL requires either choosing pending letters or entering a population. Pending letters were not chosen, and a population was not entered.

Action: Run GLBLSEL again, either choosing pending letters or entering a population.

Message: Term <term> does not exist

Cause: The term code entered as a parameter is not defined on the Term Code Validation Form (STVTERM).

Action: Define the term code on STVTERM, or enter the correct term code for the parameter.

Message: Variable <variable> on letter <letter> is not owned by application <application>

Cause: A variable defined in the letter does not belong to the application entered as the parameter.

Action: Use the Variable Definition Form (GLRVRBL) to copy the variable from the application that does own the variable to the one entered for the parameter.

General Release 7.5 December 2007T-2 User Guide Confidential

Troubleshooting

Error: In a letter generated directly by the Letter Generation module (rather than by downloading), a variable's name, rather than the translation value for the variable, appears in the text of the letter. For example, the variable “*freestone” rather than the value “John” appears.

Cause: Either the generated letter has multiple tables defined (that is, #DT commands) and the #DT commands are not the first paragraph of the letter, or the #DT command paragraphs have commands other than #DT (for example, #NP).

Action: Use the Letter Process Form (GUALETR) to review the first paragraph of the letter. Make sure the first paragraph has only #DT commands. Use the Paragraph Form (GUAPARA) to make any modifications. Rerun the Letter Extract Process (GLBLSEL) and the Letter Generation Print Report (GLRLETR).

Note: If you ran GLRLETR in audit mode when you determined the error, you only need to run GLRLETR. There's no need to run GLBLSEL again.

Population Selection Messages

If a problem arises as you work with the Population Selection Extract Process (GLBDATA), Banner provides diagnostic messages to guide you toward solution.

In addition, you may encounter Oracle messages if GLBDATA does not run successfully. Look up the message number displayed on the screen as “SQLCODE=####” in your Oracle Error Messages Manual.

Listed below are some of the Banner diagnostic messages you may see, with their corrective actions.

Message: Application <application> does not exist

Cause: The application entered as a parameter has not been defined on the Application Definition Rules Form (GLRAPPL).

Action: Define the application on GLRAPPL, or enter the correct application for the parameter.


Troubleshooting

Message: Maximum number of dynamic parms exceeded

Cause: More than 100 unique dynamic parameters were found among all population selection and application rules used in the population.

Action: Reduce the number of dynamic parameter to less than 100 by either “hardcoding” values or setting values equal to other field values.

Message: No GLRCMPL record for <selection ID>

Cause: No rules were found for the combination of application code, selection ID, and creator ID that were entered as parameters.

Action: Reenter rules on the Population Selection Definition Rules Form (GLRSLCT) to force the rules to be generated again.

Message: Private Selection ID. Cannot Access.

Cause: The population selection is locked on the Population Selection Definition Rules Form (GLRSLCT).

Action: Either unlock the population selection on GLRSLCT (if you are the creator), or enter a population selection that is not locked.

Message: Query does not exist <application/selection/creator>

Cause: The combination of the application code, selection ID, and creator ID that were entered as parameters does not exist on the Population Selection Definition Rules Form (GLRSLCT).

Action: Either create the selection ID under the application and creator ID on GLRSLCT, or enter a combination that is already defined.

Variable/Population Selection Messages

When you build population selection rules on the Population Selection Definition Rules Form (GLRSLCT) and variable rules on the Variable Rules Definition Form (GLRVRBL), the system generates SQL code to extract the IDs and variable data. Both forms call the COBOL process Automatic Letter Compilation Process (GLOLETT). The following diagnostic messages may be generated during the process.


Troubleshooting

Message: MAXIMUM NUMBER OF TABLES ALLOWED HAS BEEN REACHED . . . ABORTING

Cause: More than 15 tables are used in the variable/population selection.

Action: Reduce the number of tables being used to less than 15.

Message: No GLRVFRM record found for: <application, variable >

Cause: The variable being “compiled” by the Automatic Letter Compilation Process (GLOLETT) could not be found.

Action: Verify that the variable has the 'Select' information entered on the Variable Rules Definition Form (GLRVRBL).

Message: Only 1 sub-query per variable allowed . . . ABORTING

Cause: A variable being compiled has a subquery on another variable that has a subquery defined. Subqueries can be nested only 1 deep.

Action: Redefine the variables to only use one subquery.

Message: Select Valid Column . . . Aborting

Cause: A column name found in the variable or population selection could not be found or is found multiple times in the ALL_TAB_COLUMNS view. Finding it multiple times implies that the field name might exist on two different tables or views.

Action: Create unique field names within Banner tables and views that are used by variables and population selections.

Message: Unknown function . . . Aborting

Cause: The text immediately preceding a left parenthesis in the Select statement of the variable is not one of the fifty (50) functions known to the program.

Action: Change the variable.


Troubleshooting

Message: Undefined column located . . . Aborting

Cause: A column specified in the variable or population selection is not found in the ALL_TAB_COLUMNS view for that table and user.

Action: Change the variable or population selection to include the correct column name. Usually it is a misspelling of a column name in the Select statement or the Value field.

Message: Unknown variable/object . . . Aborting

Cause: A table specified in the variable or population selection is not found in the ALL_TAB_COLUMNS view for that user, and is considered invalid. This is probably because the user ID running the program has not been granted Select access to a table referenced in the variable or population selection. It does not matter to the program that the user might have DBA access; explicit grants to the table(s) are needed.

Action: Verify that the user ID of the person who is attempting to run the variable/selection process has access to all tables referenced in the rules. To do this, perform a Describe on each table in SQL* Plus.

Message: Variable <variable> cannot be used here . . . Aborting

Cause: A variable referenced in the Select clause of another variable cannot reference THAT variable in its own Select clause.

Action: Change the variables.

Message: Variable <variable> does not return a numeric value

Cause: The variable specified in the error message is referenced in the Select clause of the variable being compiled. This 'referenced' variable was not compiled first.

Action: Find the variables 'referenced' in the Select statements and compile them first. They can be found with the following SQL statement:

SELECT GLRVFRM_APPLICATION, GLRVFRM_SELECT_CLAUSE

FROM GENERAL.GLRVFRM

WHERE (GLRVFRM_SELECT_CLAUSE LIKE '%*%'

AND GLRVFRM_SELECT_CLAUSE NOT LIKE '%* %')


Troubleshooting

ORDER BY GLRVFRM_APPLICATION, GLRVFRM_SELECT_CLAUSE

Message: <element> is undefined. Cannot compile.

Cause: An undefined element was found in the Select clause of the variable. The program cannot determine what it is, so compilation terminates.

Action: Find the variable causing the problem, and correct the syntax in the Select clause, or redefine the element.

Job Submission Messages

If you make a mistake when you submit a job using the Process Submission Control Form (GJAPCTL), Banner provides a diagnostic message to alert you to the problem and gives you directions to remedy the situation. Here are some of the common diagnostic messages you may see, with their corrective actions.

Message: Can't read form by that name

Cause: The system cannot validate a parameter you entered on the Process Submission Control Form (GJAPCTL) because it can't find the appropriate validation form for this application. GJAPCTL validates parameters on the system-specific validation form (*OQPVAL), where * is the first character of the application's job name:

Action: If this is the first time you are trying to run this job, the required validation form may not be in the process's path. Make sure that the correctly defined *OQPVAL form exists in the base system. If you are not sure how to do this, talk with your data center personnel.

If you have created this job with a first letter different from the ones delivered with your base system, you must also create an appropriately named validation form to provide the appropriate parameter validation checks for your process. Remember that

AOQPVAL AlumniFOQPVAL FinanceGOQPVAL GeneralNOQPVAL Position ControlPOQPVAL PayrollROQPVAL Financial AidSOQPVAL StudentTOQPVAL Accounts Receivable


Troubleshooting

SunGard Higher Education recommends you use letters X, Y, or Z for your own customized jobs. Talk with your data center personnel about your requirements.

Message: Can't read form by that name

Cause: This message usually occurs when trying to submit a locally created job that begins with W, Y, or Z. For baseline Banner jobs, parameter and process level validation are performed by a product specific database package xOKPVAL, where x is the product’s System Indicator code. For example, General’s package is named GOKPVAL. In the event that the database package is not accessible, an attempt is made to call the product specific validation form xOQPVAL, where, once again, x is the product’s System Indicator code.

The reason for the error message is that neither the package nor the form could be found and validation was specified for the parameter or job.

Action: If you are submitting a baseline job, speak with your data center personnel and tell them you suspect a problem with the XOKPVAL package. If you are submitting a local job, one beginning with the letter W, Y, or Z, verify that a corresponding xOKPVAL database package has been created, or that a xOQPVAL form has been created. One or the other must exist before the validation can occur. Talk with your data center personnel about your requirements.

Message: Run sequence number is invalid. Aborting job.

Cause: If you submitted this job using the Process Parameter Control Form (GJAPCTL), the system cannot find the parameter values and associated run sequence numbers that are stored for each job in the GENERAL.GJBPRUN Table. If the job is a newly-created one, it's possible that the variable that defines the name of the process is not correct. Often a new process is cloned from an existing one, and some instances of the old process name are not changed.

If you submitted this job interactively from the host command, the run sequence number you entered can't be found with the parameter values that are stored for each job in the GJAPCTL. You probably did not enter the correct run sequence number.

Action: If this is a first-time use of a new job, look for all occurrences of the name of the process that was copied and change them to the new name. You may need help from your data processing personnel. Resubmit the job.


Troubleshooting

If you're running this job from the host command, you probably did not enter the correct run sequence number. Enter the parameter values on GJAPCTL again and “hold” the values. When you have finished, note the sequence number that appears in the auto hint -- this is the number that should be used as the run sequence number when you rerun the job from the host.

Message: Run sequence number is invalid. Aborting job.

Cause: No entries were found in the Process Run Parameter Table (GJBPRUN) for the run sequence number specified. If you submitted this job interactively, the run sequence number you entered can't be found in the GENERAL.GJBPRUN Table. You probably did not enter the correct run sequence number.

Action: Check the source of the program to verify that all selects against the GJBPRUN table refer to the correct job name. If the job is new and was cloned from an existing one, check that the selects against the GJBPRUN table were changed to refer to the new program name, not the cloned one. You may need help from your data processing personnel. Resubmit the job. If you're running this job from the operating system prompt, you probably did not enter the correct run sequence number. Enter the parameter values on GJAPCTL again and select “hold”, then select Commit. When you have finished, note the sequence number that appears in the autohelp -- this is the number which should be used as the Run Sequence Number when you rerun the job from the operating system prompt.

Message: *ERROR* Problem communicating with job submission program. Seek Help.

Cause: Either the background process that processes Job Submission requests is not running, or the volume of job requests is excessive.

Action: Contact your technical staff to determine whether you should start the background process (gurjobs) if it not running. If it is running, technical staff may need to start more than one occurrence of gurjobs to handle the volume.

Message: *ERROR* Unable to submit job. Verify that the gurjobs program is running.

Cause: Either the background process that processes job submission requests is not running, or the volume of job requests is excessive.

Action: Contact your technical staff to determine whether it is necessary to start the background process (gurjobs) if it not running. If it is


Troubleshooting

running, technical staff may need to start more than one occurrence of gurjobs to handle the volume.

Message: *Warning* Timed out waiting for response from job submission program.

Cause: The background process that processes job submission requests is not running, the volume of job requests is excessive, the job you submitted is still running or the job you submitted aborted.

Action: Contact your technical staff to determine whether it is necessary to start the background process (gurjobs) if it not running. If it is running, try to locate any output files generated by your job to see if an error message is present.

Message: The variables’ values do not print when I run GLRLETR. When I print my letters directly from Banner (the “0 = none” option), only the variables within the letter print (e.g., *FNAME, *LNAME), and not the values for the variables. The GLRCOLR table has been updated correctly through the GLBLSEL process.

Cause: This situation occurs when the letter’s table definitions [i.e., “margin settings”] are not contained within a separate paragraph code (GTVPARA/GUAPARA).

Action: All table definitions [not text or variables] must be held in a separate paragraph, and that paragraph must be Sequence 1 on the Letter Process Form (GUALETR). A good technique, also, is to have the new page format command [#NP] in a separate paragraph and to have that be Sequence 2 on the Letter Process Form.

Message: External Program Could Not Execute Or Had An Error. This occurs sometimes when I enter variable rules on GLRVRBL or population selection rules on GLRSLCT, and I exit the forms so the GLOLETT process can compile the rules, How can I prevent this from occurring?

Cause: The Process Results table, GJBRSLT, may be growing too large. This table should be monitored and periodically cleaned out through SQL*Plus.

Action: There may be some extraneous values lodged in the GJBPRUN table. Have your Computer Services Department issue the following statement using SQL*Plus:

SQL> delete gjbprun where gjbprun_job =’GLOLETT’;


Troubleshooting

Message: Dynamic parameters found. Please fill in the appropriate values.

Cause: The job which you have submitted has dynamic parameters which must be entered. You will be prompted with a second window to allow you to enter the necessary values.


Troubleshooting



Index

Index

Symbols

(SLABLDG) Building Definition Form 9-96(SLABQRY) Building Query Form 9-143(SLAEVNT) Event Form 9-11(SLARDEF) Room Definition Form 9-104(SSAMATX) Building/Room Schedule Form 9-145

A

About Banner Form (GUAABOT) 8-118Address Purge (GPPADDR) 14-28Address Review and Verification Form (GOAADDR) 10-18Address Role Privileges Form (GOAADRL) 10-17Address Source Validation Form (STVASRC) 2-65Address Type Code Validation Form (STVATYP) 2-65Alternate Logon Verification Form (GUAUIPW) 4-5, 4-42Application Definition Rules Form (GLRAPPL) 5-9, 6-9Application Inquiry Form (GLIAPPL) 5-10, 6-10application, definition of 3-20, 5-3Attendance Form (GEAATTD) 9-6, 9-82Automatic Letter Compilation Process (GLOLETT) 5-4, 6-4,

14-52auto-population rules 3-105

B

Bank Code Query Form (GXIBANK) 8-18Bank Code Rule Form (GXRBANK) 8-14Bank Routing Number Validation Form (GXVDIRD) 2-65, 8-

19Banner

extracting data to a spreadsheet 3-80module overview 1-3running reports and processes 3-13

Banner Error Messages Form (GUAERRM) 8-119Banner Message Aware Entity Rules Form (GURMESG) 8-

112basic person

Common Forms Object Library (GOQCLIB) 13-4basic person information 3-109building a letter 3-43building a population selection 3-20Building Category Query Form (SLQBCAT) 9-10Building Code Validation Form (STVBLDG) 2-66Building Definition Form (SLABLDG) 9-6, 9-96Building Query Form (SLABQRY) 9-6, 9-143Building Room Schedule Form (SSAMATX) 9-7Building/Room Attribute Code Validation Form

(STVRDEF) 2-76

Building/Room Schedule Form (SSAXMTX) 9-145business actions 3-104Business Rule Builder

validation forms reference 12-3Business Rule Builder forms

Business Rule Process Parameters Form (GORSQPA) 12-4

Business Rules Form (GORRSQL) 12-5Business Rule Builder procedures 3-103Business Rule Code Validation Form (GTVSQRU) 2-48Business Rule Parameter Code Validation Form (GTVSQPA)

2-47Business Rule Process Code Validation Form (GTVSQPR) 2-

47Business Rule Process Parameters Form (GORSQPA) 12-4Business Rules

building auto-population rules 3-105building business rules 3-104creating 3-103

Business Rules Form (GORRSQL) 12-5

C

Calculator Form (GUACALC) 8-118Calendar Form (GUACALN) 8-117Campus Code Validation Form (STVCAMP) 2-66Certificate of Eligibility Validation Form (GTVCELG) 2-14changing the appearance of the main menu 3-80changing user-level defaults 3-7Citizen Type Code Validation Form (STVCITZ) 2-67Class Schedule Forms

Building/Room Schedule Form (SSAMATX) 9-145COBOL processes 14-52College Code Validation Form (STVCOLL) 2-67Common Forms Object Library (GOQCLIB) 13-4Common Matching Entry Form (GOAMTCH) 8-117Concealing 1-6Condensed Table Listing (GURTABL) 14-45copying a population selection 3-24copying user-level defaults 3-9copying variable rules 3-35County Code Validation Form (STVCNTY) 2-67creating

download file 3-58hidden variable 3-40job parameter set 3-9manual population 3-29menu 3-76multiple-sequence variable 3-36personal menu 3-80population 3-24population from the union, intersection, or minus of

existing population selection rules 3-26QuickFlow 3-82

December 2007 General Release 7.5Confidential User Guide I-1

Index

variable 3-30variable with ID information other than the ID receiving

the letter 3-39creating ACH information for a bank account 3-65creating additional records or modifying records for an

existing bank code 3-66Credit Card Rules Form (GORCCRD) 8-88Credit Card Transaction ID Form (GOAMERC) 8-88Cross-Product Credit Card Type Validation Form

(GTVCCRD) 2-13Crosswalk Validation Form (GTVSDAX) 2-46, 8-90Currency Code Maintenance Form (GUACURR) 8-13Currency Codes Validation Form (GTVCURR) 2-14, 8-13currency conversions 3-62customizing Banner

main menu 3-76

D

Data Element Dictionary (GURPDED) 14-42Data Extract 3-80

See also Banner Getting Started Guide 3-80Day of Week Validation Form (STVDAYS) 2-68Default Parameter Value Validation Form (GJAPDFT) 3-4, 3-

5, 3-7, 3-9, 4-4, 4-27defining

new processes 3-4new reports 3-4variable with a first variable type 3-41variables 3-30

defining a new bank code 3-63Degree Code Validation Form (STVDEGC) 2-69deleting Visa records 3-88Department Code Validation Form (STVDEPT) 2-69Departmental Honors Code Validation Form (STVHOND)

2-72Desktop Tools - Add-In Application Form (GOADADD) 8-35Desktop Tools - Add-In Validation Form (GTVDADD) 2-15Desktop Tools - Step Property Validation Form (GTVDPRP)

2-18Desktop Tools - Step Property Values Rule Form

(GORDPRP) 8-27Desktop Tools - Step Type Properties Rule Form

(GORDSTP) 8-32Desktop Tools - Step Type Validation Form (GTVDSTP) 2-20Desktop Tools - User Security Rule Form (GORDSEC) 8-29Desktop Tools - Wizard Steps Setup Application Form

(GOADSTE) 8-44Direct Access Form (GUAPARM) 8-117direct deposit 3-63, 3-64, 3-65, 3-66Direct Deposit Recipient Form (GXADIRD) 8-20Directory Item Validation Form (GTVDIRO) 2-17, 10-36Directory Options Rule Form (GOADIRO) 10-21displaying images 8-78

displaying multiple Visas 3-89District Division Code Validation Form (GTVDICD) 2-17download file for letters 3-58Duration Unit Validation Form (GTVDUNT) 2-22

E

EDI Trading Partner Identification Form (GXATPID) 8-24EDI Trading Partner Query Form (GXQTPID) 8-25EDI Transaction ID Rules Form (GXRETID) 8-26EDI Transaction Type Validation Form (GTVTRTP) 2-60, 8-

24EDI/ISO Standard Code Validation Form (GTVSCOD) 2-46,

8-23electronic documents 3-67, 3-71Electronic Documents Builder Form (GORWFDB) 3-68Electronic Documents Dictionary Form (GORWFDD) 3-68,

8-50Electronic Documents Form (GOAWFED) 3-71, 8-55Electronic Documents Form (GOQWFED) 3-74, 8-61Electronic Documents Security Form (GORWFDS) 3-71, 8-

60Electronic Documents Validation Form (GTVWFED) 2-64, 8-

60Electronic Documents Wizard Form (GOAWFIZ) 3-67Electronic Documents Wizard Form (GOAWIZZ) 8-49E-mail Address Form (GOAEMAL) 10-14E-mail Address Type Validation Form (GTVEMAL) 2-23, 10-

36Emphasis Code Validation Form (GTVEMPH) 2-24Employment Type Validation Form (STVEMPT) 2-70entering Visa information 3-88Enterprise Access Control Form (GOAEACC) 8-84Enterprise PIN Preferences Form (GUAPPRF) 8-102establishing bank information 3-63establishing currency conversions 3-62Ethnic Code Validation Form (STVETHN) 2-70Event Available Room Query Form (SLIAEVN) 9-10Event Form (SLAEVNT) 9-6, 9-11Event Function Form (GEAFUNC) 9-6, 9-19Event Function Inquiry Form (GEIFUNC) 9-6, 9-125Event Management

definitions 3-84forms 9-5managing buildings and rooms 3-84managing events 3-85managing functions 3-85managing participants 3-87managing tasks 3-86menus and forms 9-5overview 9-3procedures 3-83validation forms reference 9-3with the Advancement System 9-155

General Release 7.5 December 2007I-2 User Guide Confidential

Index

Event Management FormsBuilding Definition Form (SLABLDG) 9-96

Event Management formsAttendance Form (GEAATTD) 9-6, 9-82Building Definition Form (SLABLDG) 9-6Building Query Form (SLABQRY) 9-6Building Room Schedule Form (SSAMATX) 9-7Bulding Category Query Form (SLQBCAT) 9-10Event Available Room Query Form (SLIAEVN) 9-10Event Form (SLAEVNT) 9-6Event Function Form (GEAFUNC) 9-6, 9-19Event Function Inquiry Form (GEIFUNC) 9-6, 9-125Event Query Form (SLQEVNT) 9-10Event Registration Form (GEAATID) 9-6, 9-65Function Attendance Inquiry Form (GEIATTD) 9-6, 9-

117Function Code Validation Form (GTVFUNC) 2-32Function Comment Form (GEAFCOM) 9-6, 9-56Function Participant Form (GEAPART) 9-6, 9-48Function Status Code Validation Form (GTVFSTA) 2-31Function Subject Index Query Form (GEISUBJ) 9-6, 9-

141Function Task Form (GEATASK) 9-6, 9-36Individual Function Inquiry Form (GEIIDFN) 9-6, 9-129Room Definition Form (SLARDEF) 9-6Room Query Form (SLQROOM) 9-10

Event Query Form (SLQEVNT) 9-10Event Queue Code Validation Form (GTVEQNM) 2-24, 8-64Event Queue Name Definition Form (GOREQNM) 8-67Event Queue Record Maintenance Form (GOAEQRM) 8-69Event Registration Form (GEAATID) 9-6, 9-65event, definition of 3-84Event/Function Type Code Validation Form (STVETYP) 2-

72Expense Code Validation Form (GTVEXPN) 2-28extracting Banner data 3-80extracting IDs using population selection rules 3-25extracting variables 3-48

F

facility Oracle report formatting emulation commands 3-44Fee Rate Code Validation Form (GTVRATE) 2-43Fee Status Code Validation Form (GTVFEES) 2-30Fee Type Code Validation Form (GTVFTYP) 2-32FGAC Business Profile Validation Form (GTVFBPR) 2-31FGAC Domain Type Validation Form (GTVFDTP) 2-29FGAC Domain Validation Form (GTVFDMN) 2-28FGAC Group Validation Form (GTVFGAC) 2-30Fine-Grained Access Control 1-6Forms

(SLABLDG) Building Definition Form 9-96(SLABQRY) Building Query Form 9-143(SLAEVNT) Event Form 9-11(SLARDEF) Room Definition Form 9-104

(SSAMATX) Building/Room Schedule Form 9-145forms

Common Matching Entry Form (GORCMSC) 8-117FGAC Business Profile Validation Form (GTVFBPR) 2-

31FGAC Domain Type Validation Form (GTVFDTP) 2-29FGAC Domain Validation Form (GTVFDMN) 2-28FGAC Group Validation Form (GTVFGAC) 2-30GEAATID Event Registration Form 9-6, 9-65GEAATTD Attendance Form 9-6, 9-82GEAFCOM Function Comment Form 9-6, 9-56GEAFUNC Event Function Form 9-6, 9-19GEAPART Function Participant Form 9-6, 9-48GEATASK Function Task Form 9-6, 9-36GEIATTD Function Attendance Inquiry Form 9-6, 9-117GEIFUNC Event Function Inquiry Form 9-6, 9-125GEIIDFN Individual Function Inquiry Form 9-6, 9-129GEISUBJ Function Subject Index Query Form 9-6, 9-141GJAJOBS Process Maintenance Form 3-4, 4-4, 4-15GJAJPRF Job Submission Profile Maintenance Form 3-

16, 4-5, 4-40GJAPCTL Process Submission Control Form 3-6, 3-8, 3-

10, 3-14, 3-25, 3-26, 4-4, 4-5GJAPDEF Parameter Definition Form 3-4, 3-5, 4-4, 4-18GJAPDFT Default Parameter Value Validation Form 3-4,

3-5, 3-7, 3-9, 4-4, 4-27GJAPVAL Parameter Value Validation Form 3-4, 4-4, 4-

24GJARSLT Process Results Form 4-4, 4-35GJASWPT Sleep Wake Maintenance Form 4-5, 4-42GJIREVO Saved Output Review Form 3-17, 4-4, 4-36GJRJPRM Job Parameter Set Rule Form 3-10, 4-4, 4-33GLAEXTR Population Selection Extract Data Form 3-

29, 5-6GLIAPPL Application Inquiry Form 5-10, 6-10GLIEXTR Population Selection Extract Inquiry Form 5-

6GLIOBJT Object Inquiry Form 5-11, 6-9GLIRSLT Population Selection Result Inquiry Form 5-

12GLISLCT Population Selection Inquiry Form 5-8GLIVRBL Variable Inquiry Form 5-11, 6-8GLRAPPL Application Definition Rules Form 5-9, 6-9GLROBJT Object Definition Rules Form 5-11, 6-8GLRSLCT Population Selection Definition Rules Form

3-20, 3-24, 5-7GLRVRBL Variable Rules Definition Form 3-30, 3-35, 3-

39, 5-10, 6-8GOAADDR Address Review and Verification Form 10-18GOAADRL Address Role Privileges Form 10-17GOADADD Desktop Tools - Add-In Application Form 8-

35GOADIRO Directory Options Rule Form 10-21GOADPRF Web User Directory Profile Form 10-22GOADSTE Desktop Tools - Wizard Steps Setup

Application Form 8-44GOAEACC Enterprise Access Control Form 8-84GOAEMAL E-mail Address Form 10-14


Index

GOAEQRM Event Queue Record Maintenance Form 8-69

GOAFNXR Third Party Procedures and Parameters Form 10-29

GOAIMMU Immunization Information Form 8-112GOAINTL Visa International Information Form 3-88, 7-

7GOAMEDI General Medical Information Form 8-85GOAMERC Credit Card Transaction ID Form 8-88GOAPGEO Geographic Regions/Divisions by ID Form

8-88GOASEVR SEVIS Transmittal History Form 3-90, 7-14GOASEVS SEVIS Information Form 3-90, 7-33GOASGEO Source/Background Institution

Geographic Form 8-88GOATPAC Third Party Access Form 10-6GOATPAD Third Party Access Audit Form 10-9GOAWFED Electronic Documents Form 3-71, 8-55GOAWFED Workflow Electronic Documents Form 3-71GOAWFIZ Electronic Documents Wizard Form 8-49GOAWFIZ Workflow Electronic Documents Wizard

Form 3-67GOISEVS SEVIS Transmittal Status Query Form 7-52GOISRVY Survey Response Query Form 10-23GOISVBH SEVIS Batch Header Inquiry Form 7-54GOQWFED Electronic Documents Form 3-74, 8-61GORADMS VR Admissions Term Based Rules Form 11-

10GORAWPD VR Fin Aid Award Year/Term Based Rules

Form 11-21GORBILL Voice Response Billing Term Based Rules

Form 11-17GORCCRD Credit Card Rules Form 8-88GORDPRP Desktop Tools - Step Property Values Rule

Form 8-27GORDSEC Desktop Tools - User Security Rule Form 8-

29GORDSTP Desktop Tools - Step Type Properties Rule

Form 8-32GOREQNM Event Queue Name Definition Form 8-67GOREQPG Parameter Group Rule Form 8-66GORFLAG Voice Response Duty Flag Rules Form 11-6GORICCR Integration Configuration Settings Form 8-

72GORINTG Integration Partner System Rules Form 8-65GORMEDR Medical Disability Rule Form 8-89GORMENU Voice Response Menu Control Rules Form

11-4GORPARM VR Operator Availability & System

Parameter Rules Form 11-8GORRACE Race Rules Form 7-56GORRGTM Voice Response Registration & Grading

Term Based Rules Form 11-30GORRSQL Business Rules Form 12-5GORRSTS Voice Response Registration Status Rules

Form 11-37GORSQPA Business Rule Process Parameters Form 12-4GORSVSQ SEVIS Business Rules Form 7-57GORTCTL Third Party Electronic Control Rules Form

10-31

GORVCTL Voice Response Control Rules Form 11-38GORVPDI VPDI Included Objects Form 8-120GORWFDB Electronic Documents Builder Form 3-68GORWFDB Workflow Electronic Documents Builder

Form 8-51GORWFDD Electronic Documents Dictionary Form 8-

50GORWFDD Workflow Electronic Documents

Dictionary Form 3-68GORWFDS Electronic Documents Security Form 8-60GORWFDS Workflow Electronic Documents Security

Form 3-71GTVCCRD Cross-Product Credit Card Type Validation

Form 2-13GTVCELG Certificate of Eligibility Validation Form 2-14GTVCURR Currency Code List Form 2-14, 8-13GTVDADD Desktop Tools - Add-In Validation Form 2-

15GTVDICD District Division Code Validation Form 2-17GTVDIRO Directory Item Validation Form 2-17, 10-36GTVDOCM Visa Document Code Validation Form 2-18GTVDPRP Desktop Tools - Step Property Validation

Form 2-18GTVDSTP Desktop Tools - Step Type Validation Form 2-

20GTVDUNT Duration Unit Validation Form 2-22GTVEMAL E-mail Address Type Validation Form 2-23,

10-36GTVEMPH Emphasis Code Validation Form 2-24GTVEQNM Event Queue Code Validation Form 2-24, 8-

64GTVEQPG Parameter Group Code Validation Form 2-

25, 8-63GTVEQPM Parameter Code Validation Form 2-26, 8-62GTVEQTS Target System Code Validation Form 2-27, 8-

61GTVEXPN Expense Code Validation Form 2-28GTVFEES Fee Status Code Validation Form 2-30GTVFSTA Function Status Code Validation Form 2-31GTVFTYP Fee Type Code Validation Form 2-32GTVFUNC Function Code Validation Form 2-32GTVINSM Instructional Method Validation Form 2-33GTVLETR Letter Code Validation Form 2-35, 6-11GTVLFST Learner Field of Study Type Validation Form

2-35GTVMAIL Mail Code Validation Form 2-37GTVMENU Menu Code Validation Form 2-37GTVMTYP Meeting Type Validation Form 2-37GTVNTYP Name Type Validation Form 2-38GTVOBJT Object Code Validation Form 2-38, 8-82GTVPARA Paragraph Code Validation Form 2-39, 6-12GTVPARS Partition Code Validation Form 2-39GTVPRNT Printer Validation Form 2-40, 2-42, 3-16, 4-4GTVPTYP Participant Type Code Validation Form 2-42GTVPURP Purpose Code Validation Form 2-42GTVQUIK QuickFlow Code Validation Form 2-43, 8-82GTVRATE Fee Rate Code Validation Form 2-43GTVREVN Revenue Code Validation Form 2-43GTVRSVP RSVP Code Validation Form 2-44GTVRTNG Rating Code Validation Form 2-44


Index

GTVSCHS Scheduling Status Code Validation Form 2-45

GTVSCOD EDI/ISO Standard Code Validation Form 2-46, 8-23

GTVSDAX Crosswalk Validation Form 2-46, 8-90GTVSQPA Business Rule Parameter Code Validation

Form 2-47GTVSQPR Business Rule Process Code Validation Form

2-47GTVSQRU Business Rule Code Validation Form 2-48GTVSRCE Visa Source Code Validation Form 2-49GTVSUBJ Subject Index Code Validation Form 2-49GTVSVAP SEVIS Auto-populate Code Validation Form

2-50GTVSVBA SEVIS Business Action Code Validation Form

2-50GTVSVCC SEVIS Category Code Validation Form 2-52GTVSVCP SEVIS Consular Post Code Validation Form

2-52GTVSVCR SEVIS Creation Reason Code Validation

Form 2-53GTVSVDT SEVIS Dependent Termination Code

Validation Form 2-53GTVSVEL SEVIS Education Level Code Validation

Form 2-54GTVSVEP SEVIS EV End Program Reason Code

Validation Form 2-54GTVSVFT SEVIS Drop Below Full Time Reason Code

Validation Form 2-55GTVSVGO SEVIS Governmental Organization Code

Validation Form 2-55GTVSVIO SEVIS International Organization Code

Validation Form 2-56GTVSVIPC SEVIS Exchange Visitor Position Code

Validation Form 2-57GTVSVIT SEVIS Infraction Type Code Validation Form

2-56GTVSVRP SEVIS Request for Form Reprint Validation

Form 2-57GTVSVTR SEVIS Termination Reason Code Validation

Form 2-58GTVSVTS SEVIS Transmittal Status Code Validation

Form 2-58GTVSYSI System Indicator Validation Form 2-59, 5-11, 6-

12GTVTARG Target Audience Code Validation Form 2-60GTVTASK Task Code Validation Form 2-60GTVTRTP EDI Transaction Type Validation Form 2-60,

8-24GTVTSTA Task Status Code Validation Form 2-61GTVTTYP Task Type Code Validation Form 2-61GTVVAPP Value-Based Security Application Codes

Form 2-61GTVVBTY Value-Based Security Type Validation Form 2-

62GTVVISS Visa Issuing Authority Validation Form 2-63GTVVOBJ Value-Based Security Object Code Validation

Form 2-63GTVWFED Electronic Documents Validation Form 8-60GTVZIPC ZIP/Postal Code Validation Form 2-64, 8-90

GUAABOT About Banner Form 8-118GUACALC Calculator Form 8-118GUACALN Calendar Form 8-117GUACURR Currency Code Maintenance Form 8-13GUAERRM Banner Error Messages Form 8-119GUAGMNU General Menu Form 8-119GUAHELP Help Form 8-91GUAIDEN User Identification Control Form 8-84GUAIMGE Personal Image Form 8-120GUAINST Installation Control Form 8-91GUALETR Letter Process Form 3-40, 6-7GUAMESG General Message Form 8-94GUAOBJS Object Maintenance Form 8-81GUAOPTM Options Maintenance Form 8-96, 8-102GUAPARA Paragraph Form 3-40, 6-7GUAPARM Direct Access Form 8-117GUAPMNU My Banner Maintenance Form 8-80GUAPPRF Enterprise PIN Preferences Form 8-102GUAPSWD Oracle Password Change Form 8-74GUAQFLW QuickFlow Form 3-83, 8-83GUAQUIK QuickFlow Definition Form 3-82, 8-83GUASRVY Survey Definition Form 10-24GUASYST System Identification Form 8-105GUAUIPW Alternate Logon Verification Form 4-5, 4-42GUAUPRF General User Preferences Maintenance

Form 8-75GUIALTI SSN/SIN/TFN Alternate ID Search Form 8-

106GUIMAIL Mail Query Form 6-6GUIOBJS Object Search Form 8-82GUISRVS Survey Summary Query Form 10-27GUITINH SSN/SIN/TFN History Form 8-108GUQLETR Letter Display Form 6-12GUQSETI Set Institution Form 8-121GUQWUTL General WebUtil File Extract Form 8-122GURMESG Banner Message Aware Entity Rules Form 8-

112GUTGMNU Menu Maintenance Form 3-76, 8-73GUTPMNU Personal Menu Maintenance and Copy

Form 8-81GXADIRD Direct Deposit Recipient Form 8-20GXATPID EDI Trading Partner Identification Form 8-

24GXIBANK Bank Code Query Form 8-18GXQTPID EDI Trading Partner Query Form 8-25GXRBANK Bank Code Rule Form 8-14GXRETID EDI Transaction ID Rules Form 8-26GXVDIRD Bank Routing Number Validation Form 2-

65, 8-19SLABLDG Building Definition Form 9-6SLABQRY Building Query Form 9-6SLAEVNT Event Form 9-6SLARDEF Room Definition Form 9-6SLIAEVN Event Available Room Query Form 9-10SLQBCAT Building Category Query Form 9-10SLQEVNT Event Query Form 9-10SLQROOM Room Query Form 9-10SSAMATX Building Room Schedule Form 9-7STVASRC Address Source Validation Form 2-65STVATYP Address Type Code Validation Form 2-65


Index

STVBLDG Building Code Validation Form 2-66STVCAMP Campus Code Validation Form 2-66STVCITZ Citizen Type Code Validation Form 2-67STVCNTY County Code Validation Form 2-67STVCOLL College Code Validation Form 2-67STVDAYS Day of Week Validation Form 2-68STVDEGC Degree Code Validation Form 2-69STVDEPT Department Code Validation Form 2-69STVEMPT Employment Type Validation Form 2-70STVETHN Ethnic Code Validation Form 2-70STVETYP Event/Function Code Validation Form 2-72STVHOND Departmental Honors Code Validation

Form 2-72STVLGCY Legacy Code Validation Form 2-72STVMAJR Major, Minor, Concentration Code

Validation Form 2-72STVMRTL Marital Status Code Validation Form 2-73STVNATN Nation Code Validation Form 2-74STVPRCD Phone Rate Code Validation Form 2-75STVRDEF Building/Room Attribute Code Validation

Form 2-76STVRELG Religion Code Validation Form 2-76STVRELT Relation Code Validation Form 2-76STVRMST Room Status Code Validation Form 2-77STVRRCD Room Rate Code Validation Form 2-77STVSITE Site Code Validation Form 2-77STVSTAT State/Province Code Validation Form 2-78STVTELE Telephone Type Validation Form 2-78STVTERM Term Code Validation Form 2-78

Function Attendance Inquiry Form (GEIATTD) 9-6, 9-117Function Code Validation Form (GTVFUNC) 2-32Function Comment Form (GEAFCOM) 9-6, 9-56Function Participant Form (GEAPART) 9-6, 9-48Function Status Code Validation Form (GTVFSTA) 2-31Function Subject Index Query Form (GEISUBJ) 9-6, 9-141Function Task Form (GEATASK) 9-6, 9-36function, definition of 3-84

G

GEAATID Event Registration Form 9-6, 9-65GEAATTD Attendance Form 9-6, 9-82GEAFCOM Function Comment Form 9-6, 9-56GEAFUNC Event Function Form 9-6, 9-19GEAPART Function Participant Form 9-6, 9-48GEATASK Function Task Form 9-6, 9-36GEIATTD Function Attendance Inquiry Form 9-6, 9-117GEIFUNC Event Function Inquiry Form 9-6, 9-125GEIIDFN Individual Function Inquiry Form 9-6, 9-129GEISUBJ Function Subject Index Query Form 9-6, 9-141General Business Rule Builder

forms 12-3overview 12-3, 13-3

General International Managementdeleting Visa records 3-88

displaying multiple Visas 3-89entering Visa information 3-88overlapping Visa dates 3-89procedures 3-87setting up SEVIS codes 3-91SEVIS 3-89Visa tracking 3-87

General International Management formsCertificate of Eligibility Validation Form (GTVCELG) 2-

14Race Rules Form (GORRACE) 7-56SEVIS Batch Header Inquiry Form (GOISVBH) 7-54SEVIS Business Rules Form (GORSVSQ) 7-57SEVIS Consular Post Code Validation Form

(GTVSVCP) 2-52SEVIS Creation Reason Code Validation Form

(GTVSVCR) 2-53SEVIS Dependent Termination Code Validation Form

(GTVSVDT) 2-53SEVIS Drop Below Full Time Reason Code Validation

Form (GTVSVFT) 2-55SEVIS Education Level Code Validation Form

(GTVSVEL) 2-54SEVIS EV End Program Reason Code Validation Form

(GTVSVEP) 2-54SEVIS Exchange Visitor Position Code Validation Form

(GTVSVPC) 2-57SEVIS Governmental Organization Code Validation

Form (GTVSVGO) 2-55SEVIS Information Form (GOASEVS) 3-90, 7-33SEVIS Infraction Type Code Validation Form

(GTVSVIT) 2-56SEVIS International Organization Code Validation

Form (GTVSVIO) 2-56SEVIS Request for Form Reprint Validation Form

(GTVSVRP) 2-57SEVIS Student Cancellation Reason Code Validation

Form (GTVSVCA) 2-51SEVIS Termination Reason Code Validation Form

(GTVSVTR) 2-58SEVIS Transmittal History Form (GOASEVR) 3-90, 7-14SEVIS Transmittal Status Code Validation Form

(GTVSVTS) 2-58SEVIS Transmittal Status Query Form (GOISEVS) 7-52Visa Document Code Validation Form (GTVOCM) 2-18Visa International Information Form (GOAINTL) 3-88,

7-7Visa Issuing Authority Validation Form (GTVVISS) 2-63

General Medical Information Form (GOAMEDI) 8-85General Menu Form (GUAGMNU) 8-119General Message Form (GUAMESG) 8-94general person

Common Forms Object Library (GOQCLIB) 13-4General User Preferences Maintenance Form (GUAUPRF)

8-75General Voice Response Management

forms 11-3overview 11-3

General VR Management forms


Index

Voice Response Billing Term Based Rules Form (GORBILL) 11-17

Voice Response Control Rules Form (GORVCTL) 11-38Voice Response Duty Flag Rules Form (GORFLAG) 11-6Voice Response Financial Aid Award Year & Term Based

Rules Form (GORAWPD) 11-21Voice Response Menu Control Rules Form

(GORMENU) 11-4Voice Response Registration & Grading Term Based

Rules Form (GORRGTM) 11-30Voice Response Registration Status Rules Form

(GORRSTS) 11-37VR Admissions Term Based Rules Form (GORADMS)

11-10VR Fin Aid Award Year/Term Based Rules Form

(GORAWPD) 11-21VR Operator Availability & System Parameter Rules

Form (GORPARM) 11-8General Web Management

forms 10-4overview 10-3valiation forms reference 10-3

General Web Management formsAddress Review and Verification Form (GOAADDR) 10-

18Address Role Privileges Form (GOAADRL) 10-17Directory Item Validation Form (GTVDIRO) 2-17, 10-36Directory Options Rule Form (GOADIRO) 10-21E-mail Address Form (GOAEMAL) 10-14E-mail Address Type Validation Form (GTVEMAL) 2-23,

10-36Survey Definition Form (GUASRVY) 10-24Survey Response Query Form (GOISRVY) 10-23Survey Summary Query Form (GUISRVS) 10-27Third Party Access Audit Form (GOATPAD) 10-9Third Party Access Form (GOATPAC) 10-6Third Party Electronic Control Rules Form

(GORTCTL) 10-31Third Party Procedures and Parameters Form

(GOAFNXR) 10-29Web User Directory Profile Form (GOADPRF) 10-22

General WebUtil File Extract Form (GUQWUTL) 8-122generating letters

from Banner 3-52from the operating system 3-56

Geographic Regions/Divisions by ID Form (GOAPGEO) 8-88

GJAJOBS Process Maintenance Form 3-4, 4-4, 4-15GJAJPRF Job Submission Profile Maintenance Form 3-16, 4-

5, 4-40GJAPCTL Process Submission Control Form 3-6, 3-8, 3-10, 3-

14, 3-25, 3-26, 4-4, 4-5GJAPDEF Parameter Definition Form 3-4, 3-5, 4-4, 4-18GJAPDFT Default Parameter Value Validation Form 3-4, 3-5,

3-7, 3-9, 4-4, 4-27GJAPVAL Parameter Value Validation Form 3-4, 4-4, 4-24GJARSLT Process Results Form 4-4, 4-35GJASWPT Sleep Wake Maintenance Form 4-5, 4-42

GJIREVO Saved Output Review Form 3-17, 4-4, 4-36GJRJPRM Job Parameter Set Rule Form 3-10, 4-4, 4-33GJRRPTS List of Reports and Parameters 14-4GLAEXTR Population Selection Extract Data Form 3-29, 5-6GLBDATA Population Selection Extract Process 3-24, 5-4,

14-54GLBLSEL Letter Extract Process 3-48, 6-4, 14-57GLBPARM Parameter Selection Compile Process 5-4, 14-60GLIAPPL Application Inquiry Form 5-10, 6-10GLIEXTR Population Selection Extract Inquiry Form 5-6GLIOBJT Object Inquiry Form 5-11, 6-9GLIRSLT Population Selection Result Inquiry Form 5-12GLISLCT Population Selection Inquiry Form 5-8GLIVRBL Variable Inquiry Form 5-11, 6-8GLOLETT Automatic Letter Compilation Process 5-4, 6-4,

14-52GLRAPPL Application Definition Rules Form 5-9, 6-9GLRLETR Letter Generation Print Report 3-52, 3-58, 6-4, 14-

8GLROBJT Object Definition Rules Form 5-11, 6-8GLRSLCT Population Selection Definition Rules Form 3-20,

3-24, 5-7GLRVRBL Variable Rules Definition Form 3-30, 3-35, 3-39, 5-

10, 6-8GOAADDR Address Review and Verification Form 10-18GOAADRL Address Role Privileges Form 10-17GOADADD Desktop Tools - Add-In Application Form 8-35GOADIRO Directory Options Rule Form 10-21GOADPRF Web User Directory Profile Form 10-22GOADSTE Desktop Tools - Wizard Steps Setup Application

Form 8-44GOAEACC Enterprise Access Control Form 8-84GOAEMAL E-mail Address Form 10-14GOAEQRM Event Queue Record Maintenance Form 8-69GOAFNXR Third Party Procedures and Parameters Form

10-29GOAIMMU Immunization Information Form 8-112GOAINTL Visa International Information Form 3-88, 7-7GOAMEDI General Medical Information Form 8-85GOAMERC Credit Card Transaction ID Form 8-88GOAPGEO Geographic Regions/Divisions by ID Form 8-88GOASEVR SEVIS Transmittal History Form 3-90, 7-14GOASEVS SEVIS Information Form 3-90, 7-33GOASGEO Source/Background Institution Geographic

Form 8-88GOATPAC Third Party Access Form 10-6GOATPAD Third Party Access Audit Form 10-9GOAWFED Electronic Documents Form 3-71, 8-55GOAWFED Workflow Electronic Documents Form 3-71GOAWFIZ Electronic Documents Wizard Form 8-49GOAWFIZ Workflow Electronic Documents Wizard Form 3-

67GOISEVS SEVIS Transmittal Status Query Form 3-94, 7-52GOISRVY Survey Response Query Form 10-23GOISVBH SEVIS Batch Header Inquiry Form 7-54


Index

GOQCLIBCommon Forms Object Library 13-4

GOQWFED Electronic Documents Form 3-74, 8-61GORADMS VR Admissions Term Based Rules Form 11-10GORAWPD VR Fin Aid Award Year/Term Based Rules Form

11-21GORBILL Voice Response Billing Term Based Rules Form

11-17GORCCRD Credit Card Rules Form 8-88GORDPRP Desktop Tools - Step Property Values Rule Form

8-27GORDSEC Desktop Tools - User Security Rule Form 8-29GORDSTP Desktop Tools - Step Type Properties Rule Form

8-32GOREQNM Event Queue Name Definition Form 8-67GOREQPG Parameter Group Rule Form 8-66GORFLAG Voice Response Duty Flag Rules Form 11-6GORICCR Integration Configuration Settings Form 8-72GORINTG Integration Partner System Rules Form 8-65GORMEDR Medical Disability Rule Form 8-89GORMENU Voice Response Menu Control Rules Form 11-4GORPARM VR Operator Availability & System Parameter

Rules Form 11-8GORPGEO Person Geo Region/Divisions Report 14-12GORRACE Race Rules Form 7-56GORRGTM Voice Response Registration & Grading Term

Based Rules Form 11-30GORRSQL Business Rules Form 12-5GORRSTS Voice Response Registration Status Rules Form

11-37GORSEVE

SEVIS Batch Extract Process 3-94GORSEVE SEVIS Batch Export Process 14-19GORSGEO SBGI Geo Region/Divisions Report 14-26GORSQPA Business Rule Process Parameters Form 12-4GORSVSQ SEVIS Business Rules Form 7-57GORTCTL Third Party Electronic Control Rules Form 10-31GORVCTL Voice Response Control Rules Form 11-38GORVPDI VPDI Included Objects Form 8-120GORWFDB Electronic Documents Builder Form 3-68GORWFDB Workflow Electronic Documents Builder Form

8-51GORWFDD Electronic Documents Dictionary Form 8-50GORWFDD Workflow Electronic Documents Dictionary

Form 3-68GORWFDS Electronic Documents Security Form 8-60GORWFDS Workflow Electronic Documents Security Form

3-71GPPADDR Address Purge 14-28GTVCCRD Cross-Product Credit Card Type Validation Form

2-13GTVCELG Certificate of Eligibility Validation Form 2-14GTVCURR Currency Code List Form 2-14, 8-13GTVDADD Desktop Tools - Add-In Validation Form 2-15GTVDICD District Division Code Validation Form 2-17GTVDIRO Directory Item Validation Form 2-17, 10-36

GTVDOCM Visa Document Code Validation Form 2-18GTVDPRP Desktop Tools - Step Property Validation Form 2-

18GTVDSTP Desktop Tools - Step Type Validation Form 2-20GTVEMAL E-mail Address Type Validation Form 2-23, 10-36GTVEMPH Emphasis Code Validation Form 2-24GTVEQNM Event Queue Code Validation Form 2-24, 8-64GTVEQPG Parameter Group Code Validation Form 2-25, 8-

63GTVEQPM Parameter Code Validation Form 2-26, 8-62GTVEQTS Target System Code Validation Form 2-27, 8-61GTVEXPN Expense Code Validation Form 2-28GTVFEES Fee Status Code Validation Form 2-30GTVFSTA Function Status Code Validation Form 2-31GTVFTYP Fee Type Code Validation Form 2-32GTVFUNC Function Code Validation Form 2-32GTVLETR Letter Code Validation Form 2-35, 6-11GTVMAIL Mail Code Validation Form 2-37GTVMENU Menu Code Validation Form 2-37GTVNTYP Name Type Validation Form 2-38GTVOBJT Object Code Validation Form 2-38, 8-82GTVPARA Paragraph Code Validation Form 2-39, 6-12GTVPARS Partition Code Validation Form 2-39GTVPRNT Printer Validation Form 2-40, 2-42, 3-16, 4-4GTVPTYP Participant Type Code Validation Form 2-42GTVPURP Purpose Code Validation Form 2-42GTVQUIK QuickFlow Code Validation Form 2-43, 8-82GTVRATE Fee Rate Code Validation Form 2-43GTVREVN Revenue Code Validation Form 2-43GTVRSVP RSVP Code Validation Form 2-44GTVRTNG Rating Code Validation Form 2-44GTVSCHS Scheduling Status Code Validation Form 2-45GTVSCOD EDI/ISO Standard Code Validation Form 2-46,

8-23GTVSDAX Crosswalk Validation Form 2-46, 8-90GTVSQPA Business Rule Parameter Code Validation Form 2-

47GTVSQPR Business Rule Process Code Validation Form 2-47GTVSQRU Business Rule Code Validation Form 2-48GTVSRCE Visa Source Code Validation Form 2-49GTVSUBJ Subject Index Code Validation Form 2-49GTVSVAP SEVIS Auto-populate Code Validation Form 2-50GTVSVBA SEVIS Business Action Code Validation Form 2-50GTVSVCC SEVIS Category Code Validation Form 2-52GTVSVCP SEVIS Consular Post Code Validation Form 2-52GTVSVCR SEVIS Creation Reason Code Validation Form 2-

53GTVSVDT SEVIS Dependent Termination Code Validation

Form 2-53GTVSVEL SEVIS Education Level Code Validation Form 2-

54GTVSVEP SEVIS EV End Program Reason Code Validation

Form 2-54GTVSVFT SEVIS Drop Below Full Time Reason Code

Validation Form 2-55


Index

GTVSVGO SEVIS Governmental Organization Code Validation Form 2-55

GTVSVIO SEVIS International Organization Code Validation Form 2-56

GTVSVIT SEVIS Infraction Type Code Validation Form 2-56GTVSVPC SEVIS Exchange Visitor Position Code Validation

Form 2-57GTVSVRP SEVIS Request for Form Reprint Validation Form

2-57GTVSVTR SEVIS Termination Reason Code Validation

Form 2-58GTVSVTS SEVIS Transmittal Status Code Validation Form 2-

58GTVSYSI System Indicator Validation Form 2-59, 5-11, 6-12GTVTARG Target Audience Code Validation Form 2-60GTVTASK Task Code Validation Form 2-60GTVTRTP EDI Transaction Type Validation Form 2-60, 8-24GTVTSTA Task Status Code Validation Form 2-61GTVTTYP Task Type Code Validation Form 2-61GTVVAPP Value-Based Security Application Codes Form 2-

61GTVVBTY Value-Based Security Type Validation Form 2-62GTVVISS Visa Issuing Authority Validation Form 2-63GTVVOBJ Value-Based Security Object Code Validation

Form 2-63GTVWFED Electronic Documents Validation Form 8-60GTVZIPC ZIP/Postal Code Validation Form 2-64, 8-90GUAABOT About Banner Form 8-118GUACALC Calculator Form 8-118GUACALN Calendar Form 8-117GUACURR Currency Code Maintenance Form 8-13GUAERRM Banner Error Messages Form 8-119GUAGMNU General Menu Form 8-119GUAHELP Help Form 8-91GUAIDEN User Identification Control Form 8-84GUAIMGE 8-78GUAIMGE Personal Image Form 8-120GUAINST Installation Control Form 8-91GUALETR Letter Process Form 3-40, 6-7GUAMESG General Message Form 8-94GUAOBJS Object Maintenance Form 8-81GUAOPTM Options Maintenance Form 8-96, 8-102GUAPARA Paragraph Form 3-40, 6-7GUAPARM Direct Access Form 8-117GUAPMNU Personal Menu Maintenance Form 8-80GUAPPRF Enterprise PIN Preferences Form 8-102, 10-33GUAPSWD Oracle Password Change Form 8-74GUAQFLW QuickFlow Form 3-83, 8-83GUAQUIK QuickFlow Definition Form 3-82, 8-83GUASRVY Survey Definition Form 10-24GUASYST System Identification Form 8-105GUAUIPW Alternate Logon Verification Form 4-5, 4-42GUAUPRF General User Preferences Maintenance Form 8-

75GUAVRFY User ID/Password Verification Process 14-61

GUIALTI SSN/SIN/TFN Alternate ID Search Form 8-106GUIMAIL Mail Query Form 6-6GUIOBJS Object Search Form 8-82GUISRVS Survey Summary Query Form 10-27GUITINH SSN/SIN/TFN History Form 8-108GUPDELT Document Code Delete Process 14-32GUQLETR Letter Display Form 6-12GUQSETI Set Institution Form 8-121GUQWUTL General WebUtil File Extract Form 8-122GURDETL Document Detail Report 14-34GURHELP Print Dynamic Help for a Form 14-39GURINSO Insert Output Program 14-36GURIROL Institution Role Maintenance Process 14-37GURMESG Banner Message Aware Entity Rules Form 8-112GURPDED Data Element Dictionary 14-42GURTABL Condensed Table Listing 14-45GURTEXT Document Code Report 14-48GURTPAC PIN Create Process 10-34, 10-36, 14-50GUTGMNU Menu Maintenance Form 3-76, 8-73GUTPMNU My Banner Maintenance and Copy Form 8-81GXADIRD Direct Deposit Recipient Form 8-20GXATPID EDI Trading Partner Identification Form 8-24GXIBANK Bank Code Query Form 8-18GXQTPID EDI Trading Partner Query Form 8-25GXRBANK Bank Code Rule Form 8-14GXRETID EDI Transaction ID Rules Form 8-26GXVDIRD Bank Routing Number Validation Form 2-65, 8-

19

H

Help Form (GUAHELP) 8-91Hiding 1-6

I

Immunization Code Validation Form (GTVIMMU) 2-32Immunization Information Form (GOAIMMU) 8-112Immunization Status Code Validation Form (GTVIMST) 2-

33Individual Function Inquiry Form (GEIIDFN) 9-6, 9-129Insert Output Program (GURINSO) 14-32, 14-36Installation Control Form (GUAINST) 8-91Institution Role Maintenance Process (GURIROL) 14-37Instructional Method Validation Form (GTVINSM) 2-33Integration Configuration Settings Form (GORICCR) 8-72Integration Partner System Code Validation Form

(GTVINTP) 2-34Integration Partner System Rules Form (GORINTG) 8-65International Management

overview 7-3


Index

validation forms reference 7-3

J

job parameter set 3-9Job Parameter Set Rule Form (GJRJPRM) 3-10, 4-4, 4-33Job Submission

changing user-level defaults 3-7copying user-level defaults 3-9creating a job parameter set 3-9defining new processes 3-4defining new reports 3-4forms 4-4generating letters from Banner 3-53overview 4-3printing online output 3-15procedures 3-3reports 4-3running Banner reports and processes 3-14saving online output 3-15setting up parameter defaults 3-4setting up system-level defaults 3-5setting up user-level defaults 3-5troubleshooting T-7validation forms reference 4-3viewing online output 3-15

Job Submission formsAlternate Logon Verification Form (GUAUIPW) 4-5, 4-

42Default Parameter Value Validation Form (GJAPDFT) 3-

4, 3-5, 3-7, 3-9, 4-4, 4-27Job Parameter Set Rule Form (GJRJPRM) 3-10, 4-4Job Parameter Set Rule Form Form (GJRJPRM) 4-33Job Submission Profile Maintenance Form (GJAJPRF)

3-16, 4-5, 4-40Parameter Definition Form (GJAPDEF) 3-4, 3-5, 4-4, 4-

18Parameter Value Validation Form (GJAPVAL) 3-4, 4-4, 4-

24Printer Validation Form (GTVPRNT) 2-40, 2-42, 3-16, 4-

4Process Maintenance Form (GJAJOBS) 3-4, 4-4, 4-15Process Results Form (GJARSLT) 4-4, 4-35Process Submission Control Form (GJAPCTL) 3-6, 3-8,

3-10, 3-14, 3-25, 3-26, 4-4, 4-5Saved Output Review Form (GJIREVO) 3-17, 4-4, 4-36Sleep Wake Maintenance Form (GJASWPT) 4-5

Job Submission Profile Maintenance Form (GJAJPRF) 3-16, 4-5, 4-40

L

LDAP Options 8-80

Learner Field of Study Type Validation Form (GTVLFST) 2-35

Legacy Code Validation Form (STVLGCY) 2-72letter

building 3-43generating 3-52pending 3-52variable extract 3-48

Letter Code Validation Form (GTVLETR) 2-35, 6-11Letter Display Form (GUQLETR) 6-12Letter Extract Process (GLBLSEL) 3-48, 6-4, 14-57Letter Generation

building a letter 3-43copying variable rules 3-35creating a download file 3-58creating a hidden variable 3-40creating a multiple-sequence variable 3-36creating a variable 3-30creating a variable with ID information other than the

ID receiving the letter 3-39defining a variable with a first variable type 3-41defining variables 3-30extracting variables 3-48facility Oracle report formatting emulation commands

3-44forms 6-5generating letters from Banner 3-52overview 6-3pending letters 3-52procedures 3-30processes 6-4report 6-4sorting variables 3-39troubleshooting T-1validation forms reference 6-3

Letter Generation formsApplication Definition Rules Form (GLRAPPL) 5-9, 6-9Application Inquiry Form (GLIAPPL) 5-10, 6-10Letter Code Validation Form (GTVLETR) 2-35, 6-11Letter Display Form (GUQLETR) 6-12Letter Process Form (GUALETR) 3-40, 6-7Mail Query Form (GUIMAIL) 6-6Object Definition Rules Form (GLROBJT) 5-11, 6-8Object Inquiry Form (GLIOBJT) 5-11, 6-9Paragraph Code Validation Form (GTVPARA) 2-39, 6-

12Paragraph Form (GUAPARA) 3-40, 6-7System Indicator Validation Form (GTVSYSI) 2-59, 5-11,

6-12Variable Rules Definition Form (GLRVRBL) 3-30, 3-35,

3-39, 5-10, 6-8Letter Generation Print Report (GLRLETR) 3-52, 3-58, 6-4,

14-8Letter Process Form (GUALETR) 3-40, 6-7libraries

GOQCLIB 13-4linking bank funds and bank accounts with cash accounts 3-

64


Index

List of Reports and Parameters (GJRRPTS) 14-4Location Management Forms

Building Query Form (SLABQRY) 9-143Event Form (SLAEVNT) 9-11Room Definition Form (SLARDEF) 9-104

M

Mail Code Validation Form (GTVMAIL) 2-37Mail Query Form (GUIMAIL) 6-6main menu

customizing 3-76maintaining menu 3-76maintaining personal menu 3-80Major, Minor, Concentration Code Validation Form

(STVMAJR) 2-72managing buildings and rooms 3-84managing events 3-85managing functions 3-85managing participants 3-87managing tasks 3-86Marital Status Code Validation Form (STVMRTL) 2-73Masking 1-6Medical Disability Rule Form (GORMEDR) 8-89Meeting Type Validation Form (GTVMTYP) 2-37Menu Code Validation Form (GTVMENU) 2-37Menu Maintenance Form (GUTGMNU) 3-76, 8-73MIF

home and process contexts 3-107How to switch institution codes 3-108how to view institution code 3-107Oracle Reports 3-109

Multi-Institution Functionality (MIF) procedures 3-106

N

Name Type Validation Form (GTVNTYP) 2-38Nation Code Validation Form (STVNATN) 2-74

O

Object Code Validation Form (GTVOBJT) 2-38, 8-82Object Definition Rules Form (GLROBJT) 5-11, 6-8Object Inquiry Form (GLIOBJT) 5-11, 6-9Object Maintenance Form (GUAOBJS) 8-81Object Search Form (GUIOBJS) 8-82object, definition of 3-20, 5-3Open Learning forms

Duration Unit Validation Form (GTVDUNT) 2-22

Instructional Method Validation Form (GTVINSM) 2-33

operating system prompt, running from 3-18Options 8-96Options Maintenance Form (GUAOPTM) 8-96, 8-102Oracle Password Change Form (GUAPSWD) 8-74Oracle report formatting emulation commands 3-44Oracle Reports

parameters 71 - 77 3-10, 3-11overlapping Visa dates 3-89

P

Paragraph Code Validation Form (GTVPARA) 2-39, 6-12Paragraph Form (GUAPARA) 3-40, 6-7Parameter Code Validation Form (GTVEQPM) 2-26, 8-62parameter defaults

changing 3-7copying 3-9job parameter set 3-9setting up 3-4, 3-5system-level 3-4use of 3-4user-level 3-4validation checks 3-4

Parameter Definition Form (GJAPDEF) 3-4, 3-5, 4-4, 4-18Parameter Group Code Validation Form (GTVEQPG) 2-25,

8-63Parameter Group Rule Form (GOREQPG) 8-66Parameter Selection Compile Process (GLBPARM) 5-4, 14-

60Parameter Value Validation Form (GJAPVAL) 3-4, 4-4, 4-24parameters 71 - 77 3-10, 3-11Participant Type Code Validation Form (GTVPTYP) 2-42participant, definition of 3-84Partition Code Validation Form (GTVPARS) 2-39pending letters 3-52Person Geo Region/Divisions Report (GORPGEO) 14-12Personal Image Form (GUAIMGE) 8-78, 8-120personal menu

creating 3-80maintaining 3-80

Personal Menu Maintenance and Copy Form (GUTPMNU) 8-81

Personal Menu Maintenance Form (GUAPMNU) 8-80Phone Rate Code Validation Form (STVPRCD) 2-75PII

Personally Identifiable Information 1-6PIN Create Process (GURTPAC) 10-34, 10-36, 14-50population

creating with GLBDATA 3-24manual 3-29

Population Selectionbuilding a population selection 3-20


Index

copying a population selection 3-24creating a manual population 3-29creating a population 3-24creating a population from the union, intersection, or

minus of existing population selection rules 3-26definitions 5-3extracting IDs using population selection rules 3-25forms 5-4, 7-4overview 5-3procedures 3-19related processes 5-4troubleshooting T-3validation forms reference 5-4

population selectionbuilding 3-20copying 3-24definition of 3-20, 5-3

Population Selection Definition Rules Form (GLRSLCT) 3-20, 3-24, 5-7

Population Selection Extract Data Form (GLAEXTR) 3-29, 5-6

Population Selection Extract Inquiry Form (GLIEXTR) 5-6Population Selection Extract Process (GLBDATA) 3-24, 5-4,

14-54Population Selection forms

Application Definition Rules Form (GLRAPPL) 5-9, 6-9Application Inquiry Form (GLIAPPL) 5-10, 6-10Object Definition Rules Form (GLROBJT) 5-11, 6-8Object Inquiry Form (GLIOBJT) 5-11, 6-9Population Selection Definition Rules Form

(GLRSLCT) 3-20, 3-24, 5-7Population Selection Extract Data Form (GLAEXTR) 3-

29, 5-6Population Selection Extract Inquiry Form (GLIEXTR)

5-6Population Selection Inquiry Form (GLISLCT) 5-8Population Selection Result Inquiry Form (GLIRSLT) 5-

12System Indicator Validation Form (GTVSYSI) 2-59, 5-11,

6-12Variable Inquiry Form (GLIVRBL) 5-11, 6-8Variable Rules Definition Form (GLRVRBL) 3-30, 3-35,

3-39, 5-10, 6-8Population Selection Inquiry Form (GLISLCT) 5-8Population Selection Result Inquiry Form (GLIRSLT) 5-12population, definition of 3-19, 5-3Print Dynamic Help for a Form (GURHELP) 14-39Printer Validation Form (GTVPRNT) 2-40, 2-42, 3-16, 4-4printing online output 3-15Procedures

basic person 3-109procedures

extended ID and name searching 3-110Process Maintenance Form (GJAJOBS) 3-4, 4-4, 4-15Process Results Form (GJARSLT) 4-4, 4-35Process Submission Control Form (GJAPCTL) 3-6, 3-8, 3-10,

3-14, 3-25, 3-26, 4-4, 4-5processes

see reports and processesPurpose Code Validation Form (GTVPURP) 2-42

Q

QuickFlowcreating 3-82definition of 3-81using 3-83

QuickFlow Code Validation Form (GTVQUIK) 2-43, 8-82QuickFlow Definition Form (GUAQUIK) 3-82, 8-83QuickFlow Form (GUAQFLW) 3-83, 8-83

R

Race Rules Form (GORRACE) 7-56Rating Code Validation Form (GTVRTNG) 2-44Regulatory Race Validation Form (GTVRRAC) 2-43Relation Code Validation Form (STVRELT) 2-76Religion Code Validation Form (STVRELG) 2-76report formatting emulation commands 3-44report parameters 71 - 77 3-10, 3-11reports and processes

COBOL processes 14-52defining to Job Submission 3-4GJRRPTS List of Reports and Parameters 14-4GLBDATA Population Selection Extract Process 3-24, 5-

4, 14-54GLBLSEL Letter Extract Process 3-48, 6-4, 14-57GLBPARM Parameter Selection Compile Process 5-4,

14-60GLOLETT Automatic Letter Compilation Process 5-4,

6-4, 14-52GLRLETR Letter Generation Print Report 3-52, 3-58, 6-

4, 14-8GORPGEO Person Geo Region/Divisions Report 14-12GORSEVE Batch Export Process 14-19GORSGEO SBGI Geo Region/Divisions Report 14-26GPPADDR Address Purge 14-28GUAVRFY User ID/Password Verification Process 14-61GURHELP Print Dynamic Help for a Form 14-39GURINSO Insert Output Program 14-32, 14-36GURIROL Institution Role Maintenance Process 14-37GURPDED Data Element Dictionary 14-42GURTABL Condensed Table Listing 14-45GURTPAC PIN Create Process 10-34, 10-36, 14-50parameter defaults 3-4printing online output 3-15running from the operating system 3-18running with Job Submission 3-14saving online output 3-15viewing online output 3-15

Revenue Code Validation Form (GTVREVN) 2-43


Index

Room Definition Form (SLARDEF) 9-6, 9-104Room Query Form (SLQROOM) 9-10Room Rate Code Validation Form (STVRRCD) 2-77Room Status Code Validation Form (STVRMST) 2-77RSVP Code Validation Form (GTVRSVP) 2-44running Banner reports and processes 3-13

S

Saved Output Review Form (GJIREVO) 3-17, 4-4, 4-36saving online output 3-15SBGI Geo Region/Divisions Report (GORSGEO) 14-26Scheduling Status Code Validation Form (GTVSCHS) 2-45Searching

extended ID and name 3-110Set Institution Form (GUQSETI) 8-121setting up direct deposit 3-63setting up electronic documents 3-67setting up events 3-75setting up parameter defaults 3-4setting up SEVIS codes 3-91setting up system-level defaults 3-5setting up user-level defaults 3-5SEVIS 3-89

handling adjudicated information 3-94If a Record is Rejected 3-98If Records are Rejected by SEVISTA 3-97Receiving data from the Bureau 3-98Responses from the Bureau 3-97Sending Data to the Bureau via the Batch Process 3-96Sending Records to the Bureau 3-95structures 3-91Transmitting Data via the RTI 3-95

SEVIS Auto-populate Code Validation Form (GTVSVAP) 2-50

SEVIS Batch Export Process (GORSEVE) 14-19SEVIS Batch Extract Process (GORSEVE) 3-94, 14-19SEVIS Batch Header Inquiry Form (GOISVBH) 7-54SEVIS Business Action Code Validation Form (GTVSVBA) 2-

50SEVIS Business Rules Form (GORSVSQ) 7-57SEVIS Category Code Validation Form (GTVSVCC) 2-52SEVIS codes

setting up 3-91SEVIS Consular Post Code Validation Form (GTVSVCP) 2-

52SEVIS Creation Reason Code Validation Form (GTVSVCR)

2-53SEVIS Dependent Termination Code Validation Form

(GTVSVDT) 2-53SEVIS Drop Below Full Time Reason Code Validation Form

(GTVSVFT) 2-55SEVIS Education Level Code Validation Form (GTVSVEL) 2-

54

SEVIS EV End Program Reason Code Validation Form (GTVSVEP) 2-54

SEVIS Exchange Visitor Position Code Validation Form (GTVSVPC) 2-57

SEVIS Governmental Organization Code Validation Form (GTVSVGO) 2-55

SEVIS Information Form (GOASEVS) 3-90, 7-33SEVIS Infraction Type Code Validation Form (GTVSVIT) 2-

56SEVIS International Organization Code Validation Form

(GTVSVIO) 2-56SEVIS Request for Form Reprint Validation Form

(GTVSVRP) 2-57SEVIS Student Cancellation Reason Code Validation Form

(GTVSVCA) 2-51SEVIS Termination Reason Code Validation Form

(GTVSVTR) 2-58SEVIS Transfer Adaptor (SEVISTA) 3-90SEVIS Transmittal History Form (GOASEVR) 3-90, 7-14SEVIS Transmittal Status Code Validation Form (GTVSVTS)

2-58SEVIS Transmittal Status Query Form (GOISEVS) 3-94, 7-52Single Socket Layer (SSL) 8-80Site Code Validation Form (STVSITE) 2-77SLABLDG Building Definition Form 9-6SLABQRY Building Query Form 9-6SLAEVNT Event Form 9-6SLARDEF Room Defintion Form 9-6Sleep Wake Maintenance Form (GJASWPT) 4-5, 4-42SLIAEVN Event Available Room Query Form 9-10SLQBCAT Building Category Query Form 9-10SLQEVNT Event Query Form 9-10SLQROOM Room Query Form 9-10sorting variables 3-39Source/Background Institution Geographic Form

(GOASGEO) 8-88spreadsheet, data extracted to 3-80SSAMATX Building Room Schedule Form 9-7SSL 8-80SSN/SIN/TFN Alternate ID Search Form (GUIALTI) 8-106SSN/SIN/TFN History Form (GUITINH) 8-108State/Province Code Validation Form (STVSTAT) 2-78Student and Exchange Visitors Information System (SEVIS)

3-89STVASRC Address Source Validation Form 2-65STVATYP Address Type Code Validation Form 2-65STVBLDG Building Code Validation Form 2-66STVCAMP Campus Code Validation Form 2-66STVCITZ Citizen Type Code Validation Form 2-67STVCNTY County Code Validation Form 2-67STVCOLL College Code Validation Form 2-67STVDAYS Day of Week Validation Form 2-68STVDEGC Degree Code Validation Form 2-69STVDEPT Department Code Validation Form 2-69STVEMPT Employment Type Validation Form 2-70STVETHN Ethnic Code Validation Form 2-70


Index

STVETYP Event/Function Code Validation Form 2-72STVHOND Departmental Honors Code Validation Form 2-

72STVLGCY Legacy Code Validation Form 2-72STVMAJR Major, Minor, Concentration Code Validation

Form 2-72STVMRTL Marital Status Code Validation Form 2-73STVNATN Nation Code Validation Form 2-74STVPRCD Phone Rate Code Validation Form 2-75STVRDEF Building/Room Attribute Code Validation Form

2-76STVRELG Religion Code Validation Form 2-76STVRELT Relation Code Validation Form 2-76STVRMST Room Status Code Validation Form 2-77STVRRCD Room Rate Code Validation Form 2-77STVSITE Site Code Validation Form 2-77STVSTAT State/Province Code Validation Form 2-78STVTELE Telephone Type Validation Form 2-78STVTERM Term Code Validation Form 2-78Subject Index Validation Form (GTVSUBJ) 2-49subquery 3-23Survey Definition Form (GUASRVY) 10-24Survey Response Query Form (GOISRVY) 10-23Survey Summary Query Form (GUISRVS) 10-27System Functions forms

Immunization Code Validation Form (GTVIMMU) 2-32Immunization Status Code Validation Form

(GTVIMST) 2-33Integration Partner System Code Validation Form

(GTVINTP) 2-34System Functions/Administration

changing the appearance of the main menu 3-80creating a QuickFlow 3-82creating and using QuickFlows 3-81creating menu 3-76creating personal menu 3-80customizing menus 3-76establishing bank information 3-63, 3-64, 3-65, 3-66establishing currency conversions 3-62forms 8-5maintaining menu 3-76maintaining personal menu 3-80overview 8-3procedures 3-62process 8-5setting up electronic documents 3-67setting up events 3-75using a QuickFlow 3-83using electronic documents 3-71validation forms reference 8-3

System Functions/Administration formsAbout Banner Form (GUAABOT) 8-118Bank Code Query Form (GXIBANK) 8-18Bank Code Rule Form (GXRBANK) 8-14Bank Routing Number Validation Form (GXVDIRD) 2-

65, 8-19Banner Error Messages Form (GUAERRM) 8-119

Banner Message Aware Entity Rules Form (GURMESG) 8-112

Calculator Form (GUACALC) 8-118Calendar Form (GUACALN) 8-117Credit Card Rules Form (GORCCRD) 8-88Credit Card Transaction ID Form (GOAMERC) 8-88Cross-Product Credit Card Type Validation Form

(GTVCURR) 2-13Crosswalk Validation Form (GTVSDAX) 2-46, 8-90Currency Code Maintenance Form (GUACURR) 8-13Currency Codes Validation Form (GTVCURR) 2-14, 8-

13Desktop Tools - Add-In Application Form (GOADADD)

8-35Desktop Tools - Add-In Validation Form (GTVDADD) 2-

15Desktop Tools - Step Property Validation Form

(GTVDPRP) 2-18Desktop Tools - Step Property Values Rule Form

(GORDPRP) 8-27Desktop Tools - Step Type Properties Rule Form

(GORDSTP) 8-32Desktop Tools - Step Type Validation Form (GTVDSTP)

2-20Desktop Tools - User Security Rule Form (GORDSEC) 8-

29Desktop Tools - Wizard Steps Setup Application Form

(GOADSTE) 8-44Direct Access Form (GUAPARM) 8-117Direct Deposit Recipient Form (GXADIRD) 8-20EDI Trading Partner Identification Form (GXATPID) 8-

24EDI Trading Partner Query Form (GXQTPID) 8-25EDI Transaction ID Rules Form (GXRETID) 8-26EDI Transaction Type Validation Form (GTVTRTP) 2-

60, 8-24EDI/ISO Standard Code Validation Form (GTVSCOD)

2-46, 8-23Electronic Documents Builder Form (GORWFDB) 3-68Electronic Documents Dictionary Form (GORWFDD)

3-68Electronic Documents Form (GOAWFED) 3-71, 8-55Electronic Documents Form (GOQWFED) 3-74, 8-61Electronic Documents Security Form (GORWFDS) 3-

71, 8-60Electronic Documents Validation Form (GTVWFED) 2-

64, 8-60Electronic Documents Wizard Form (GOAWFIZ) 3-67,

8-49Enterprise Access Control Form (GOAEACC) 8-84Enterprise PIN Preferences Form (GUAPPRF) 8-102Event Queue Code Validation Form (GTVEQNM) 2-24,

8-64Event Queue Name Definition Form (GOREQNM) 8-67Event Queue Record Maintenance Form (GOAEQRM)

8-69General Medical Information Form (GOAMEDI) 8-85General Menu Form (GUAGMNU) 8-119General Message Form (GUAMESG) 8-94


Index

General User Preferences Maintenance Form (GUAUPRF) 8-75

Geographic Regions/Divisions by ID Form (GOAPGEO) 8-88

GOAMTCH Common Matching Entry Form 8-117Help Form (GUAHELP) 8-91Immunization Information Form (GOAIMMU) 8-112Installation Control Form (GUAINST) 8-91Integration Configuration Settings Form (GORICCR)

8-72Integration Partner System Rules Form (GORINTG) 8-

65Medical Disability Rule Form (GORMEDR) 8-89Menu Maintenance Form (GUTGMNU) 3-76, 8-73Object Code Validation Form (GTVOBJT) 2-38, 8-82Object Maintenenace Form (GUAOBJS) 8-81Object Search Form (GUIOBJS) 8-82Options Maintenance Form (GUAOPTM) 8-96, 8-102Oracle Password Change Form (GUAPSWD) 8-74Parameter Code Validation Form (GTVEQPM) 2-26, 8-

62Parameter Group Code Validation Form (GTVEQPG)

2-25, 8-63Parameter Group Rule Form (GOREQPG) 8-66Personal Image Form (GUAIMGE) 8-120Personal Menu Maintenance and Copy Form

(GUTPMNU) 8-81Personal Menu Maintenance Form (GUAPMNU) 8-80QuickFlow Code Validation Form (GTVQUIK) 2-43, 8-

82QuickFlow Definition Form (GUAQUIK) 3-82, 8-83QuickFlow Form (GUAQFLW) 3-83, 8-83Sleep Wake Maintenance Form (GJASWPT) 4-42Source/Background Institution Geographic Form

(GOASGEO) 8-88SSN/SIN/TFN Alternate ID Search Form (GUIALTI) 8-

106SSN/SIN/TFN History Form (GUITINH) 8-108System Identification Form (GUASYST) 8-105Target System Code Validation Form (GTVEQTS) 2-27,

8-61User Identification Control Form (GUAIDEN) 8-84Value-Based Security Application Codes Form

(GTVVAPP) 2-61Value-Based Security Object Code Validation Form

(GTVVOBJ) 2-63Value-Based Security Type Validation Form (GTVVBTY)

2-62VPDI Included Objects Form (GORVPDI) 8-120Workflow Electronic Documents Builder Form

(GORWFDB) 8-51Workflow Electronic Documents Dictionary Form

(GORWFDD) 8-50ZIP/Postal Code Validation Form (GTVZIPC) 2-64, 8-90

System Identification Form (GUASYST) 8-105System Indicator Validation Form (GTVSYSI) 2-59, 5-11, 6-12

T

Target Audience Code Validation Form (GTVTARG) 2-60Target System Code Validation Form (GTVEQTS) 2-27, 8-61Task Code Validation Form (GTVTASK) 2-60Task Status Code Validation Form (GTVTSTA) 2-61Task Type Code Validation Form (GTVTTYP) 2-61task, definition of 3-84Telephone Type Validation Form (STVTELE) 2-78Term Code Validation Form (STVTERM) 2-78Third Party Access Audit Form (GOATPAD) 10-9Third Party Access Form (GOATPAC) 10-6Third Party Electronic Control Rules Form (GORTCTL) 10-

31Third Party Procedures and Parameters Form (GOAFNXR)

10-29troubleshooting

Job Submission T-7Letter Generation T-1Population Selection T-3variable/population selection T-4

U

User ID/Password Verification Process (GUAVRFY) 14-61User Identification Control Form (GUAIDEN) 8-84, 8-91using a QuickFlow 3-83using electronic documents 3-71

V

Validation formsRegulatory Race Validation Form (GTVRRAC) 2-43

validation formsaccessing 2-5Address Source Validation Form (STVASRC) 2-65Address Type Code Validation Form (STVATYP) 2-65Bank Routing Number Validation Form (GXVDIRD) 2-

65, 8-19Building Code Validation Form (STVBLDG) 2-66Building/Room Attribute Code Validation Form

(STVRDEF) 2-76Business Rule Code Validation Form (GTVSQRU) 2-48Business Rule Parameter Code Validation Form

(GTVSQPA) 2-47Business Rule Process Code Validation Form

(GTVSQPR) 2-47Campus Code Validation Form (STVCAMP) 2-66Certificate of Eligibility Validation Form (GTVCELG) 2-

14Citizen Type Code Validation Form (STVCITZ) 2-67College Code Validation Form (STVCOLL) 2-67


Index

County Code Validation Form (STVCNTY) 2-67Cross-Product Credit Card Type Validation Form

(GTVCCRD) 2-13Crosswalk Validation Form (GTVSDAX) 2-46, 8-90Currency Codes Validation Form (GTVCURR) 2-14, 8-

13Day of Week Validation Form (STVDAYS) 2-68Degree Code Validation Form (STVDEGC) 2-69Department Code Validation Form (STVDEPT) 2-69Departmental Honors Code Validation Form

(STVHOND) 2-72Directory Item Validation Form (GTVDIRO) 2-17, 10-36District Division Code Validation Form (GTVDICD) 2-

17EDI Transaction Type Validation Form (GTVTRTP) 2-

60, 8-24EDI/ISO Standard Code Validation Form (GTVSCOD)

2-46, 8-23E-mail Address Type Validation Form (GTVEMAL) 2-23,

10-36Emphasis Code Validation Form (GTVEMPH) 2-24Employment Type Validation Form (STVEMPT) 2-70Ethnic Code Validation Form (STVETHN) 2-70Event/Function Type Code Validation Form

(STVETYP) 2-72Expense Code Validation Form (GTVEXPN) 2-28Fee Rate Code Validation Form (GTVRATE) 2-43Fee Status Code Validation Form (GTVFEES) 2-30Fee Type Code Validation Form (GTVFTYP) 2-32FGAC Business Profile Validation Form (GTVFBPR) 2-

31FGAC Domain Type Validation Form (GTVFDTP) 2-29FGAC Domain Validation Form (GTVFDMN) 2-28FGAC Group Validation Form (GTVFGAC) 2-30Function Code Validation Form (GTVFUNC) 2-32Function Status Code Validation Form (GTVFSTA) 2-31GTVLFST Learner Field of Study Type Validation Form

2-35Legacy Code Validation Form (STVLGCY) 2-72Letter Code Validation Form (GTVLETR) 2-35, 6-11list of 2-5Mail Code Validation Form (GTVMAIL) 2-37Major, Minor, Concentration Code Validation Form

(STVMAJR) 2-72Marital Status Code Validation Form (STVMRTL) 2-73Menu Code Validation Form (GTVMENU) 2-37Name Type Validation Form (GTVNTYP) 2-38Nation Code Validation Form (STVNATN) 2-74Object Code Validation Form (GTVOBJT) 2-38, 8-82Paragraph Code Validation Form (GTVPARA) 2-39, 6-

12Participant Type Code Validation Form (GTVPTYP) 2-

42Partition Code Validation Form (GTVPARS) 2-39Phone Rate Code Validation Form (STVPRCD) 2-75Printer Validation Form (GTVPRNT) 2-40, 2-42, 3-16, 4-

4Purpose Code Validation Form (GTVPURP) 2-42QuickFlow Code Validation Form (GTVQUIK) 2-43, 8-

82

Rating Code Validation Form (GTVRTNG) 2-44Relation Code Validation Form (STVRELT) 2-76Religion Code Validation Form (STVRELG) 2-76Revenue Code Validation Form (GTVREVN) 2-43Room Rate Code Validation Form (STVRRCD) 2-77Room Status Code Validation Form (STVRMST) 2-77RSVP Code Validation Form (GTVRSVP) 2-44Scheduling Status Code Validation Form (GTVSCHS) 2-

45SEVIS Auto-populate Code Validation Form

(GTVSVAP) 2-50SEVIS Business Action Code Validation Form

(GTVSVBA) 2-50SEVIS Category Code Validation Form (GTVSVCC) 2-

52SEVIS Consular Post Code Validation Form

(GTVSVCP) 2-52SEVIS Creation Reason Code Validation Form

(GTVSVCR) 2-53SEVIS Dependent Termination Code Validation Form

(GTVSVDT) 2-53SEVIS Drop Below Full Time Reason Code Validation

Form (GTVSVFT) 2-55SEVIS Education Level Code Validation Form

(GTVSVEL) 2-54SEVIS EV End Program Reason Code Validation Form

(GTVSVEP) 2-54SEVIS Exchange Visitor Position Code Validation Form

(GTVSVPC) 2-57SEVIS Governmental Organization Code Validation

Form (GTVSVGO) 2-55SEVIS Infraction Type Code Validation Form

(GTVSVIT) 2-56SEVIS International Organization Code Validation

Form (GTVSVIO) 2-56SEVIS Request for Form Reprint Validation Form

(GTVSVRP) 2-57SEVIS Termination Reason Code Validation Form

(GTVSVTR) 2-58SEVIS Transmittal Status Code Validation Form

(GTVSVTS) 2-58Site Code Validation Form (STVSITE) 2-77State/Province Code Validation Form (STVSTAT) 2-78Subject Index Validation Form (GTVSUBJ) 2-49System Indicator Validation Form (GTVSYSI) 2-59, 5-11,

6-12Target Audience Code Validation Form (GTVTARG) 2-

60Task Code Validation Form (GTVTASK) 2-60Task Status Code Validation Form (GTVTSTA) 2-61Task Type Code Validation Form (GTVTTYP) 2-61Telephone Type Validation Form (STVTELE) 2-78Term Code Validation Form (STVTERM) 2-78Value-Based Security Application Codes Form

(GTVVAPP) 2-61Value-Based Security Object Code Validation Form

(GTVVOBJ) 2-63Value-Based Security Type Validation Form (GTVVBTY)

2-62


Index

Visa Document Code Validation Form (GTVDOCM) 2-18

Visa Issuing Authority Validation Form (GTVVISS) 2-63Visa Source Code Validation Form (GTVSRCE) 2-49ZIP/Postal Code Validation Form (GTVZIPC) 2-64, 8-90

Value-based securityVBS 1-6

Value-Based Security Application Codes Form (GTVVAPP) 2-61

Value-Based Security Object Code Validation Form (GTVVOBJ) 2-63

Value-Based Security Type Validation Form (GTVVBTY) 2-62variable

copying rules 3-35creating 3-30definition of 3-20, 3-30, 5-3extracting 3-48first variable type 3-41hidden 3-40multiple-sequence 3-36sorting 3-39type 3-31

Variable Inquiry Form (GLIVRBL) 5-11, 6-8Variable Rules Definition Form (GLRVRBL) 3-30, 3-35, 3-39,

5-10, 6-8viewing online output 3-15Visa Document Code Validation Form (GTVDOCM) 2-18Visa International Information Form (GOAINTL) 3-88, 7-7Visa Issuing Authority Validation Form (GTVVISS) 2-63Visa Source Code Validation Form (GTVSRCE) 2-49Visa tracking 3-87Voice Response Billing Term Based Rules Form (GORBILL)

11-17Voice Response Control Rules Form (GORVCTL) 11-38Voice Response Duty Flag Rules Form (GORFLAG) 11-6Voice Response Menu Control Rules Form (GORMENU) 11-

4Voice Response Registration & Grading Term Based Rules

Form (GORRGTM) 11-30Voice Response Registration Status Rules Form (GORRSTS)

11-37VPDI Included Objects Form (GORVPDI) 8-120VR Admissions Term Based Rules Form (GORADMS) 11-10VR Fin Aid Award Year/Term Based Rules Form

(GORAWPD) 11-21VR Operator Availability & System Parameter Rules Form

(GORPARM) 11-8

W

Web User Directory Profile Form (GOADPRF) 10-22Workflow Electronic Documents Builder Form

(GORWFDB) 8-51

Z

ZIP/Postal Code Validation Form (GTVZIPC) 2-64, 8-90


Index

SunGard Higher Education4 Country View RoadMalvern, PA 19355

1-800-223-7036www.sungardhe.com
