Chapter 6 Population Selection - survey.vinu.edu

Chapter 6

Population Selection

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

6 Population Selection

Definitions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-3
Validation Forms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-4
Related Processes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-4
Menu Navigation Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-4
Forms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-6

Population Selection Extract Inquiry Form . . . . . . . . . . . (GLIEXTR) . . . . . . 6-6
Population Selection Extract Data Form . . . . . . . . . . . . . (GLAEXTR) . . . . . . 6-6
Population Selection Definition Rules Form . . . . . . . . . . . (GLRSLCT) . . . . . . 6-7
Population Selection Inquiry Form . . . . . . . . . . . . . . . (GLISLCT) . . . . . . 6-8
Application Definition Rules Form . . . . . . . . . . . . . . . (GLRAPPL) . . . . . . 6-8
Application Inquiry Form . . . . . . . . . . . . . . . . . . . . (GLIAPPL) . . . . . . 6-10
Variable Rules Definition Form . . . . . . . . . . . . . . . . . (GLRVRBL) . . . . . . 6-10
Variable Inquiry Form . . . . . . . . . . . . . . . . . . . . . . (GLIVRBL) . . . . . . 6-10
Object Definition Rules Form . . . . . . . . . . . . . . . . . . (GLROBJT) . . . . . . 6-11
Object Inquiry Form . . . . . . . . . . . . . . . . . . . . . . (GLIOBJT) . . . . . . 6-11
System Indicator Validation Form . . . . . . . . . . . . . . . . (GTVSYSI) . . . . . . 6-11
Population Selection Result Inquiry Form . . . . . . . . . . . . (GLIRSLT) . . . . . . 6-11

6-1

6 Population Selection
Table of Contents

This page intentionally left blank

General Release 6.2 April 2004

6-2 User Guide Confidential

6 Population Selection
Overview

Overview

6 Population The Population Selection module lets you identify and group entities in the
Selection database (for example, people, vendors, and organizations). You can define
Population Selection selection criteria to identify and extract a subset of these entities to use in SCT
Banner reports, processes, and letters. Some of the functions you can perform in the
Definitions Population Selection module are:

• 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.

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.

April 2004 General Release 6.2 6-3
Confidential User Guide

6 Population Selection
Validation Forms

Validation Forms

Population Selection forms use the following validation form. Refer to Chapter 3,
Validation Forms, for additional information.

Validation Form Used By
GTVSYSI System Indicator Validation Form GLRAPPL Application Definition Rules Form

Related Processes

The following processes are related to the Population Selection module. For
additional information, refer to Chapter 15, 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.

Menu Navigation Table

Forms in the Population Selection module can be accessed from the following
menu.

General Release 6.2 April 2004

6-4 User Guide Confidential

6 Population Selection
Menu Navigation Table

Population Selection Menu (*GENPOPSEL)

.....................................................................

GLIEXTR Population Selection Extract Inquiry Form
Displays a population, which is a set of Banner IDs used for
reports, processes, and letters.

GLAEXTR Population Selection Extract Data Form
Allows 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 Form
Defines 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 Form
Displays a list of population selections within an application.

GLRAPPL Application Definition Rules Form
Defines an application, which is a functional area that controls
population selections, populations, and variables.

GLIAPPL Application Inquiry Form
Displays a list of all applications defined on the GLRAPPL Form.

GLRVRBL Variable Rules Definition Form
Defines 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 Form
Displays a list of the variables defined on the GLRVRBL Form for
an application.

GLROBJT Object Definition Rules Form
Defines an object, which is a set of common rules used in many
different population selections and variables.

GLIOBJT Object Inquiry Form
Displays a list of objects defined on the GLROBJT Form.

GTVSYSI System Indicator Validation Form
Defines codes that identify the Banner applications used at your
institution.

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.

April 2004 General Release 6.2 6-5
Confidential User Guide

6 Population Selection
Forms

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).

General Release 6.2 April 2004

6-6 User Guide Confidential

6 Population Selection
Forms

• 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.

April 2004 General Release 6.2 6-7
Confidential User Guide

6 Population Selection
Forms

For complete information about using this form, refer to “Building a Population
Selection” in Chapter 4, 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:

To perform this function: Perform these steps:

Display a count of the number Select the population selection. Then select
of IDs in each population Selection ID Counts from the Options menu (or
associated with a population use the Duplicate Field function).
selection

Display rules for a population Select the population selection. Then select
selection (GLRSLCT) Selection ID Rules from the Options menu (or
use the Count Query Hits function).

Display a list of all populations Select List of Results from the Options menu (or

in the application use the Duplicate Record function).

Display a population Select List of Results from the Options menu (or
(GLIEXTR) use the Duplicate Record function). Then select
View Population from the Options menu (or use
the List function).

Maintain a population Select List of Results from the Options menu.
(GLAEXTR) 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

General Release 6.2 April 2004

6-8 User Guide Confidential

6 Population Selection
Forms

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:

SPRADDR_ACTIVITY_DATE >= ‘01-MAR-03’ AND
SPRADDR_ACTIVITY_DATE < ‘02-MAR-03’

• 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

April 2004 General Release 6.2 6-9
Confidential User Guide

6 Population Selection
Forms

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:

• Insert variable data into letters.
• 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 4, 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:

• Insert variable data into letters.
• Reference subqueries in application rules, population selection rules, and

variable rules.

6-10 General Release 6.2 April 2004
User Guide Confidential

6 Population Selection
Forms

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.

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
SCT-delivered values to identify the applications.

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.

Population Selection Result Inquiry Form (GLIRSLT)

Use this form to display a list of populations within a specific application.

April 2004 General Release 6.2 6-11
Confidential User Guide

6 Population Selection
Forms

This page intentionally left blank

6-12 General Release 6.2 April 2004
User Guide Confidential