PowerCAMPUS Code Tables

User Guide
Release 8.1
June 2012
Banner®, Colleague®, PowerCAMPUS®, Luminis® and Datatel® are trademarks of Ellucian or its affiliates and are registered in the U.S. and
other countries. Ellucian, Advance, DegreeWorks, fsaATLAS, Course Signals, SmartCall, Recruiter, MOX, ILP, and WCMS are trademarks of
Ellucian or its affiliates. Other names may be trademarks of their respective owners.

©2007-2012 Ellucian. All rights reserved. The unauthorized possession, use, reproduction, distribution, display or disclosure of this material or
the information contained herein is prohibited.

Contains confidential and proprietary information of Ellucian and its subsidiaries. Use of these materials is limited to Ellucian licensees, and is
subject to the terms and conditions of one or more written license agreements between Ellucian and the licensee in question.

In preparing and providing this publication, Ellucian is not rendering legal, accounting, or other similar professional services. Ellucian 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.

Prepared by: Ellucian

4375 Fair Lakes Court
Fairfax, Virginia 22033
United States of America

Revision History

Publication Date Summary

June 2012 New version that supports PowerCAMPUS Code Tables 8.1 software.
PowerCAMPUS Code Tables 8.1
User Guide

Contents

Chapter 1 Introduction to Code Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1

Chapter 2 Code Table Values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1

Code tables pop-up window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1

Entering or editing code table values . . . . . . . . . . . . . . . . . . . . . . . . 2-3

Changing the Code (Key) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-3

Chapter 3 Code Table Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1

Code tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1

Academic interest . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-3
Academic rating . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-3
Academic standing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-3
Accreditation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4
Acknowledgement print . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4
Acknowledgement type. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-5
Action status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-5
Action type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-5
Activity achievement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-6
Activity behavior . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-7
Activity code . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-7
Activity type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-7
Address type. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-8
Affiliation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-8
Applicant rating type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-9
Association . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-9
Attendance status - course . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-9
Attendance status - daily . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-10

June 2012 PowerCAMPUS Code Tables 8.1 iii

User Guide
Contents
 Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-11
Award type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-11
Award value . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-12
Balance type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-13
Building function. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-15
CASE type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-15
CIP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-15
Cancel section reason . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-16
Cancel action reason . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-16
Change reason (name) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-16
Charge/Credit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-17
Class level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-23
Cohort . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-23
Cohort exclusion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-24
Collection rating . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-24
College . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-25
College attend status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-25
Column comparison . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-26
Communications type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-26
Condition (facilities) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-27
Contact . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-27
Control type (institution) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-27
Country . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-28
County . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-29
Credit type (academic) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-30
Curriculum . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-30
Day of week . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-31
Decision (application) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-32
Dedication notify . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-33
Dedication type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-33
Dedication value . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-34
Deferred giving status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-34
Deferred giving type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-34
Degree . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-35
Department . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-36
Disability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-36
Disability special requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-36

iv PowerCAMPUS Code Tables 8.1 June 2012

User Guide
Contents
 Discipline . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-37
Discount type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-37
Donor index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-38
Donor status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-38
Dorm plan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-38
Drop reason . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-39
Economic rating . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-39
Enrollment status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-39
Ethnicity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-40
Event classification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-41
Event sub type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-41
Event type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-42
FASB type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-42
Finance type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-43
Fiscal period . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-43
Food plan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-44
Full/Part time flag . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-44
Fund type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-45
Funding interest . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-45
General education . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-46
Gift allocation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-46
Gift appeal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-47
Gift benefit type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-47
Gift campaign . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-48
Gift club . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-48
Gift club report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-49
Gift form . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-50
Gift program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-52
Gift size . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-53
Gift source . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-54
Gift tender . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-54
Gift test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-54
Gift type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-55
Give probable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-55
Government note type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-56
Grade/Grade comments change reasons . . . . . . . . . . . . . . . . . . . . . . . 3-56
Grading activity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-57

June 2012 PowerCAMPUS Code Tables 8.1 v

User Guide
Contents
 Honors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-57
Immunization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-58
Immunization status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-58
IMS institution role type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-58
Institution Type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-59
Interest level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-59
Interest type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-59
IPEDS Ethnicity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-60
ISO 3166 country codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-60
ISO 639 language codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-61
Journal source . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-61
Language . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-62
Leadership . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-62
Mailing type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-63
Marital status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-64
Matching gift status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-64
Matching gift type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-65
Media type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-65
Meeting type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-65
Method how . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-66
Method when . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-66
Method who . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-66
Money level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-67
NSC status codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-67
Non Cash/In kind status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-68
Note type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-68
Office . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-69
Office held . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-69
Organization Phone Type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-69
Payment plan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-70
Permanent home . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-71
Person Phone Type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-72
Picture locations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-72
Pledge status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-72
Pledge term . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-73
Pledge type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-74
Population . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-74

vi PowerCAMPUS Code Tables 8.1 June 2012

User Guide
Contents
 Position . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-75
Position (activities) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-75
Prefix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-75
Program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-76
Rating . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-77
Rating result . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-77
Rating type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-77
Reason for no contact . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-78
Receipt print . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-78
Record type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-78
Registration method . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-79
Registration permission status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-80
Registration type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-80
Relationship . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-81
Release information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-81
Religion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-82
Residency months . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-82
Resource . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-82
Response to contacts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-83
Room type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-83
SIC code level 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-83
SIC code level 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-84
Salutation type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-84
Scholarship requirement received . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-85
Scholarship level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-85
Scholarship requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-85
Scholarship status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-86
Scholarship type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-86
Screening method . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-86
Section fee group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-87
Session . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-89
SEVIS events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-89
Solicitor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-90
Solicitor method . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-91
Source . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-91
Source type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-91
Sponsor status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-92

June 2012 PowerCAMPUS Code Tables 8.1 vii

User Guide
Contents
 Sponsor type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-92
State . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-93
Statement message. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-93
Statement type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-94
Status (application) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-94
Status (inquiry) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-95
Stop list reasons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-95
Sub cohort . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-96
Suffix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-97
Summary type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-97
Tenure status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-98
Term . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-98
Test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-99
Test type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-100
Transfer sub type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-101
Tuition exemption . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-101
Tuition plan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-101
Tuition range . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-102
Veteran . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-102
Violation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-102
Violation category . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-103
Visa . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-103
Volunteer interest . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-105
Waived reason . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-105

Chapter 4 Code Tables Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1

Code table. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1

Appendix A Code Tables Template. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-1

Summary representation of code tables template . . . . . . . . . . . . . . . . A-1

Charge/Credit code table template . . . . . . . . . . . . . . . . . . . . . . . . . . A-2

System-Defined code table values . . . . . . . . . . . . . . . . . . . . . . . . . . A-3

viii PowerCAMPUS Code Tables 8.1 June 2012

User Guide
Contents
 Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . I-1

June 2012 PowerCAMPUS Code Tables 8.1 ix

User Guide
Contents
x PowerCAMPUS Code Tables 8.1 June 2012
User Guide
Contents
 1 Introduction to Code
Tables

PowerCAMPUS is a vehicle for maintaining data on a wide range of areas, including

applicants, students, faculty, alumni, donors, courses and facilities. Each institution has its
own definitions for data fields within these areas. Code tables allow your institution to
define a specific set of values for these data fields. They allow you to tailor the system to
the needs of your institution while still maintaining data integrity. For example,
Curriculum is a data field tracked within PowerCAMPUS. An engineering school’s
Curriculum code table might include values for Mechanical, Civil and Electrical
Engineering. A liberal arts college, on the other hand, might wish the same Curriculum
code table to include values for Art Appreciation, English Literature and World History.
Therefore, the Curriculum code table should include all of these values and any other
applicable college’s necessary values as well.

Setting up code tables

Setting up code tables is very different from creating user-defined fields in the system. An
Ellucian-defined set of code tables is included with your PowerCAMPUS system and each
corresponds to one or more fields in the baseline system. These code tables will allow you
to maintain consistency across the data entered by users at your institution, since only the
values that are system-defined or defined by your institution in the associated code table
may be selected. On the other hand, user-defined fields will allow your institution to create
new fields in order to track information that is not available in the PowerCAMPUS
baseline system. User-defined fields can be created by the system administrator using the
User Defined setup, located under Tools: Setup in the System Administrator Setflow.
These fields will then be available for entry on the User Defined window of the
appropriate workflow.

A user-defined field must be created when neither a code table nor a data entry field
currently exist for data that your institution is required to track.

In order to efficiently run PowerCAMPUS, these code table values should be established
before data entry or conversion of data begins. A limited number of personnel should be
given a security profile that allows them to enter code table values. An important part of
the establishment of code table values is analyzing where each value will be used for both
data entry and retrieval. The coding should enable you to select, sort and statistically
analyze data in a logical manner. For more information about establishing this coding, see
“Code Table Values”.

June 2012 PowerCAMPUS Code Tables 8.1 1-1

User Guide
Introduction to Code Tables
 Note
Some code tables are completely defined by the system, which means
every code value within the code table is defined by the system. Some
code tables contain system-defined code values, but other user-defined
code values can be created. For more information regarding which code
tables have system-defined values, see “System-Defined code table
values”. 

Office

You may view descriptions for each individual code table in the Code Tables Descriptions
section. All code tables can be accessed from the System Administrator Setflow; however,
many of the code tables are only accessible from specific ‘offices’. In this usage, the term
‘office’ includes each individual PowerCAMPUS setflow.

Offices describe the area(s) in which each code table is used and will be listed in the
individual code table descriptions. For example, the Honors code table is only available
from the Admissions Setflow and the Academic Records Setflow because of its use in the
Transcripts Workflow. For lists of the code tables separated out by office see Code Tables
by Office in the appropriate PowerCAMPUS setflow manual.

Note
The specific code tables necessary to a data window or process will be
listed as a part of the documentation for that data window or process. 

The “Code Tables Reports” contains all of the code tables-related reports on the system.

An Appendix A, “Code Tables Template” is available to provide you additional

information in the form of charts, templates, etc.

1-2 PowerCAMPUS Code Tables 8.1 June 2012

User Guide
Introduction to Code Tables
 2 Code Table Values

The Code Tables tool can be accessed from the Tools pull-down menu of the Main Menu
Bar. The Code Tables sheet has the same command buttons and Start with capability of the
sheets available from PowerCAMPUS workflows, except that the Start with function here
takes you to the code value beginning with the letter entered in the highlighted table rather
than to the code table beginning with that letter. The code tables associated with the
current setflow are listed on the left of the window. Once you have selected a specific code
table with which to work, the values currently existing for that code table will display on
the right.

Code tables pop-up window

Code (Key) lengths are predetermined. For example, academic sessions may be coded
with a value of up to ten characters, while address types may only be four characters.

Note
You can change the Code (Key) after saving the record as long as you
have not used that code yet in the system. This will allow you to change
your mind on how you want to code your values during the initial setup of
the system. Once the code has been used in the system, however, you
must change its Status to Inactive in order for it to not be accessible for
use. 

Note the following recommendations:

• Use all upper case lettering in the Code (Key) field and that consistent rules be
applied when creating code values.
• Do not use any spaces in the Code (Key) field. PowerCAMPUS will not allow you
to create a Code (Key) value longer than the maximum number of characters
allowed. However, you may create code values with less than the maximum
number.
• Do not use any punctuation when creating code values, not only in the Code (Key)
field, but also in the Short Description, Medium Description and Long Description
fields. Using punctuation may result in syntax errors when running certain
processes in PowerCAMPUS.
• Do not use: apostrophes, periods, hyphens, back or forward slashes, quotes,
asterisks, underscores, commas, etc. Reports will be sorted based on the Code
(Key) value, not on the Short Description, Medium Description or Long

June 2012 PowerCAMPUS Code Tables 8.1 2-1

User Guide
Code Table Values
 Description. In order to avoid confusion, the Code (Key) value should be set up so
that it matches its respective description as closely as possible.
In the Prefix and Suffix code tables only, the Code (Key), rather than any of the
descriptions, will display throughout the system on various data windows and
reports and on mailings handled in the Mail Merge Processing Workflow.
Therefore, you may use upper and lower case lettering and you may use periods.

The Code will automatically default with what was entered for the Code (Key) and is
grayed out to prevent entry.

The Status of code values may be flagged as Active or Inactive. At times, institutions will
find it necessary to change the way records are coded. Inactivating a code will prevent you
from entering the code in a record. Inactive values will not display during data entry.
Records entered previously will still maintain the coding as it was entered when the value
was active.

Note
If codes have been inactivated, the code description will no longer display
on the data window. Instead, the Code itself will be displayed or printed.
However, the code description will still display on reports. 

A Short Description (length of 10), a Medium Description (length of 20) and a Long
Description (length of 40) of each code value should be entered in these fields. The
Medium Description will display in the code table drop down list boxes during data entry
and retrieval. Which description will display on reports depends upon how much space is
available.

Note
The Gift Club Report code table varies in length for short, medium and
long description fields from the other code tables. The short and medium
descriptions for this code table have a length of 30 and the long
description has a length of 64. 

Tip
The concept of short, medium and long descriptions was developed as a
way to avoid truncating descriptions on reports. It is recommended that
you use upper and lower case lettering when creating the Short
Description, Medium Description and Long Description, because these
descriptions will display throughout the system on various data windows
and reports and on mailings handled in the Mail Merge Processing
Workflow. 

If your institution is also running the 4.X version of Campus for Windows, the
corresponding code value should be entered in the Version 4.X Code and Version 4.X
Description fields. This will allow for proper mapping to take place between the two
systems. For example, the PowerCAMPUS value for the fall session may be Fall;
whereas, in the 4.X version of Campus for Windows, the fall session may have been coded
as ‘1’.

2-2 PowerCAMPUS Code Tables 8.1 June 2012

User Guide
Code Table Values
 Entering or editing code table values
Use the following instructions to enter new code table values or edit existing code table
values for a specific code table. The Version 4.X Code and the Version 4.X Description
fields can be used to record the code value from your previous system, but are for
reference only.

1. Select any setflow. From the Main Menu Bar, select Tools, and then select Code
Tables.

2. Select the appropriate code table from the list of code tables on the left-hand side of
the window.

The existing code table values, if any, will display in the Code Value list on the right-
hand side of the window.

3. Click File, and then click New to create a new code table value. To edit an existing
code table value, select the appropriate code table value. The Code Value window
will display.

4. Enter or edit the Code (Key), Short Description, Medium Description, and Long
Description for the code value. The Code will automatically default with what was
entered for the Code (Key). The Status will default to Active but can be changed.

5. Click File, and then click Save to save the information.

Note
Some code tables may have additional fields that are required. For more
information, see “Code Table Descriptions”. 

6. Repeat steps 2 through 5 until all of the code table values have been entered/edited
for the selected code table.

Tip
It is not necessary to complete the Version 4.X Code and Version 4.X
Description fields unless you are also running the 4.X version of Campus
for Windows or wish to track the code and description from your previous
system. These two fields are for reference only. 

Changing the Code (Key)

Once the Code (Key) has been used in the database, it must not be edited or deleted. You
must inactivate the code value and enter the new code table value. The inactive code table
values will no longer display in the drop-down list boxes within PowerCAMPUS for
selection; however, leaving them in the database will ensure the integrity of the existing
data.

June 2012 PowerCAMPUS Code Tables 8.1 2-3

User Guide
Code Table Values
2-4 PowerCAMPUS Code Tables 8.1 June 2012
User Guide
Code Table Values
 3 Code Table
Descriptions

All of the code tables included in the PowerCAMPUS are listed below.

Note
All of these code tables can be accessed by selecting Tools: Code Tables
in the System Administrator Setflow. 

KEY: * = code table is used by Self-Service only

Code tables
The code tables are described in the following sections.

Academic Interest Event Sub Type Pledge Term

Academic Rating Event Type Pledge Type
Academic Standing FASB Type Population
Accreditation Finance Type Position
Acknowledgement Print Fiscal Period Position (Activities)
Acknowledgement Type Food Plan Prefix
Action Status Full/Part Time Flag Program
Action Type Fund Type Rating
Activity Achievement Funding Interest Rating Result
Activity Code General Education Rating Type
Activity Type Gift Allocation Reason for No Contact
Address Type Gift Appeal Receipt Print
Affiliation Gift Benefit Type Record Type
Applicant Rating Type Gift Campaign Registration Method
Association Gift Club Registration Permission Status
Attend Status - Course Gift Club Report Registration Type
Attend Status - Daily Gift Form Relationship
Attributes Gift Program Release Information
Award Type Gift Size Religion
Award Value Gift Source Residency Months
Balance Type Gift Tender Resource
Building Function Gift Test Response to Contacts
Cancel Action Reason Gift Type Room Type
Cancel Section Reason Give Probable Salutation Type

June 2012 PowerCAMPUS Code Tables 8.1 3-1

User Guide
Code Table Descriptions
 CASE Type Government Note Type Scholarship Level
Change Reason (Name) Grade/Grade Scholarship Requirement Received
Comments Change
Reasons
Charge/Credit Grading Activity* Scholarship Requirements
CIP Honors Scholarship Status
Class Level Immunization Scholarship Type
Cohort Immunization Status Screening Method
Cohort Exclusion IMS Institution Role Section Fee Group
Type
Collection Rating Institution Type Session
College Interest Level SEVIS Events
College Attend Status Interest Type SIC Code Level 1
Column Comparison IPEDS Ethnicity SIC Code Level 2
Communications Type ISO3166 Country Solicitor
Codes
Condition (Facilities) ISO639 Language Solicitor Method
Codes
Contact Journal Source Source
Control Type (Institution) Language Source Type
Country Leadership Sponsor Status
County Mailing Type Sponsor Type
Credit Type (Academic) Marital Status State
Curriculum Matching Gift Status Statement Message
Day of Week Matching Gift Type Statement Type
Decision (Application) Media Attribute* Status (Application)
Dedication Notify Media Category* Status (Inquiry)
Dedication Type Media Entity* Stop List Reasons
Dedication Value Media Type* Sub Cohort
Deferred Giving Status Meeting Type Suffix
Deferred Giving Type Method How Summary Type
Degree Method When Tenure Status
Department Method Who Term
Disability Money Level Test
Disability Special Non Cash/In Kind Test Type
Requirements Status
Discipline Note Type Transfer Sub Type
Discount Type NSC Status Codes Tuition Exemption
Donor Index Office Tuition Plan
Donor Status Office Held Tuition Range
Dorm Plan Organization Phone Veteran
Type

3-2 PowerCAMPUS Code Tables 8.1 June 2012

User Guide
Code Table Descriptions
 Drop Reason Payment Plan Violation
Economic Rating Permanent Home Violation Category
Enrollment Status Person Phone Type Visa
Ethnicity Picture Locations Volunteer Interest
Event Classification Pledge Status Waived Reason

Academic interest
The general areas that an inquiry or applicant is interested in pursuing can be tracked using
this code table. Examples of academic interests might include: Arts, Science, and Pre-
Med. The length of the Code (Key) is restricted to 6 characters, and this code table is
applicable to Admissions.

Tip
If the Short Description or Medium Description fields are modified for the
Academic Interest code table, the system administrator will need to run
the stored procedure sp_correct_acainterestsum. 

The Academic Interest field is populated by this code table.

Example of the field location in the system: Academic Interest window of the
Inquiries Workflow and the Applicants Workflow.

Code values entered here are stored in the Code_AcaInterest table.

Academic rating

This code table holds values that can be used to describe a student’s academic rating.
Examples of academic ratings might include: academically disadvantaged, competitive,
and gifted. The length of the Code (Key) is restricted to 6 characters, and this code table is
applicable to Academic Records, and Admissions.

The Academic Rating field is populated by this code table.

Example of the field location in the system: Academic window of the Registration
Workflow; Academic drill down, available from the Academic window of the
Applicants Workflow, the Students Workflow and the People Billing Workflow.

Code values entered here are stored in the Code_AcademicRate table.

Academic standing

Academic achievements or sanctions are tracked using this code table. Examples of
academic standings might include: probation, suspension and dean’s list, as well as

June 2012 PowerCAMPUS Code Tables 8.1 3-3

User Guide
Code Table Descriptions
 academic awards such as PTK and departmental awards. The length of the Code (Key) is
restricted to 6 characters, and this code table is applicable to Academic Records.

Tip
This code table will be removed in a later version of PowerCAMPUS and
replaced with the Award Value code table. Currently, in order for the
Standing field to work properly, this code table's values should be inputted
to match those of the Award Value code table exactly. 

The Academic Standing field is populated by this code table.

Example of the field location in the system: Academic Standing setup.

Code values entered here are stored in the Code_AcaStanding table.

Accreditation
Many institutions are tracked throughout the PowerCAMPUS system for recruiting
purposes and as sources of transfer students and credits. The accreditation(s) earned by
these institutions can be tracked using this code table. In addition, your institution may
code its own accreditation status. Examples of accreditations might include: Middle
States, medical associations, accredited, and not accredited. The length of the Code (Key)
is restricted to 6 characters, and this code table is applicable to Academic Records, and
Admissions.

The Accreditation field is populated by this code table.

Example of the field location in the system: Accreditation window of the Institutions
Workflow.

Code values entered here are stored in the Code_Accreditation table.

Acknowledgement print

This code table holds values that specify how an acknowledgement is generated.
Examples might include: manual, operator, and system. The length of the Code (Key) is
restricted to 10 characters, and this code table is applicable to Advancement.

The Acknowledge Print and Print fields are populated by this code table.

Example of the fields location in the system:

• Acknowledge Print : Batch Gift and Pledge Defaults window of the Donor
Processing Workflow.
• Print: Acknowledgements and Solicitors windows, available by selecting the Show
Detail button on either the Gifts window or the Pledges window of the Donor
Processing Workflow

3-4 PowerCAMPUS Code Tables 8.1 June 2012

User Guide
Code Table Descriptions
 Code values entered here are stored in the Code_AcknowledgePrint table.

Acknowledgement type

This code table holds values that specify which acknowledgement is generated. Examples
of acknowledgement types might include: Card, Reunion, and VPLetter. The length of the
Code (Key) is restricted to 10 characters, and this code table is applicable to
Advancement.

The Acknowledgement Type field is populated by this code table.

Example of the field location in the system: Batch Gift and Pledge Defaults window
of the Donor Processing Workflow; Acknowledgements and Solicitors windows,
available by selecting the Show Detail button on either the Gifts window or the
Pledges window of the Donor Processing Workflow.

Code values entered here are stored in the Code_AcknowledgeType table.

Action status

This code table allows you to group action rules together and indicate where they are in
the process of being created and regenerated. Examples of action statuses might include:
ready to activate, ready to deactivate, approved for regeneration, and needs review. For
more information, see Action Rules in Action Scheduling. The length of the Code (Key) is
restricted to 10 characters, and this code table is applicable to Academic Records,
Admissions, Advancement, Billing, Cash Receipts, and System Administrator.

The Status field is populated by this code table.

Example of the field location in the system: Action Rule Setup tool; Action Rule
Regen tool.

Code values entered here are stored in the Code_ActionStatus table.

Action type
This code table is used to record the different types of actions that you wish to track for
people or organizations. Examples of action types might include: letters, emails, phone
calls, interviews, and meetings.

Prompts also exist to differentiate types of letters, if a letter is the selected action type.
Selecting the PowerCAMPUS Letter checkbox means that letters of this type will be
generated using the PowerCAMPUS Mail Merge. This insures that the form letter and data
file locations are saved properly for the action. An action flagged as an Access Mail Merge
Letter is a letter that is created and maintained using the MS Access form. Although letters
of this type are generated outside of the PowerCAMPUS system, the form allows you to

June 2012 PowerCAMPUS Code Tables 8.1 3-5

User Guide
Code Table Descriptions
 generate action records in PowerCAMPUS to record whether or not the recipient has
received a particular letter and the date on which that letter was sent.

The length of the Code (Key) is restricted to 6 characters, and this code table is applicable
to Academic Records, Admissions, Advancement, Billing, Cash Receipts, and System
Administrator.

Tip
If you think you may wish to send certain letters by email after running the
mail merge, be sure to flag the action type for emails as PowerCAMPUS
Letter. 

For more information, see Action Definition in Action Scheduling.

The Type (view only) and Select Action Types fields are populated by this code table.

Example of the fields location in the system:

• Type (view only) : Actions Available list box on the main window of the Mail
Merge Processing Workflow (this list can also be filtered by Type using the left-
hand drop down list box above the list)
• Select Action Types: Scheduled Action Filter window, available from the icon in
the upper left corner of the main Scheduled Actions window of any people-related
or organization-related workflow

Code values entered here are stored in the Code_ActionType table.

Activity achievement

Any awards, honors or achievements that an inquiry or applicant has received for an
activity can be coded here. Examples of activity achievements might include: lettered,
honors, and dean’s list. The length of the Code (Key) is restricted to 6 characters, and this
code table is applicable to Admissions.

The Achievement field is populated by this code table.

Example of the field location in the system: Activity Achievements drill down,
available from the Activity window of the Inquiries Workflow and the Applicants
Workflow.

Code values entered here are stored in the Code_ActAchieve table.

3-6 PowerCAMPUS Code Tables 8.1 June 2012

User Guide
Code Table Descriptions
 Activity behavior

This code table is not supported beyond PowerCAMPUS 6.32. The length of the Code
(Key) is restricted to 10 characters.

Code values entered here are stored in the Code_ActivityBehavior table.

Activity code

This code table should be used to hold any extracurricular activities for an inquiry/
applicant. Activity codes are a subset of activity types. Examples of activity codes might
include: Baseball, Key Club, and Honor Society.

An activity type must be associated with each activity code, so the Activity Type code
table should be set up prior to this table. Then, when entering activities on the Activity
window, only associated activity codes will display for each activity type. The length of
the Code (Key) is restricted to 10 characters, and this code table is applicable to
Admissions.

The Code field is populated by this code table.

Example of the field location in the system: Activity window of the Inquiries
Workflow and the Applicants Workflow.

Code values entered here are stored in the Code_Activity table.

Activity type

An activity type is used to group activity codes set up in the Activity Code code table.
Examples of activity types might include: athletics, community service, and student
government. The length of the Code (Key) is restricted to 10 characters, and this code
table is applicable to Admissions.

Note
Build this table prior to your Activity Code code table because an activity
type will be required in that table. 

The Type and Activity Type fields are populated by this code table.

Example of the fields location in the system:

• Type: Activity window of the Inquiries Workflow and the Applicants Workflow.
• Activity Type: Activity Code code table.

Code values entered here are stored in the Code_ActivityType table.

June 2012 PowerCAMPUS Code Tables 8.1 3-7

User Guide
Code Table Descriptions
 Address type

Every address entered on the system must be coded with an address type. Address Type is
used to define the address. Examples of address types might include: home, local,
business, summer, and campus.

The person or organization’s Preferred Address will also be selected from these types and
will determine the default address to which all mailings are sent. However, a specific
address type can be selected as the Preferred Address for each mailing record. For more
information, see Mailings in People or Organizations. If an address type becomes inactive
or expires, the address type will automatically be reassigned based upon the hierarchy for
address records. For more information, see Understanding Date Driven Addresses in
People or Organizations.

The length of the Code (Key) is restricted to 4 characters, and this code table is applicable
to Academic Records, Admissions, Advancement, Billing, and Cash Receipts.

Note
If new address type code values are created, or are inactivated, the
AddressHierarchy and the AddressHierarchyUnique tables will be
automatically updated. 

The Address Type, Address, and Preferred Address fields are populated by this code
table.

Example of the fields location in the system:

• Address Type: Address window of any people-related or organization-related
workflow (including Facility Management, Registration, Transfer Policy,
Transcripts, People Billing, and Organization Billing); Telecommunications
window of any people-related or organization-related workflow; Mailings window
of any people-related or organization-related workflow (including Facility
Management and Registration); Payment Plan Contract setup; Coupon window of
the report setup for the Statements report.
• Address: Affiliations window of any people-related or organization-related
workflow.
• Preferred Address: Name window of any people-related or organization-related
workflow (including Facility Management, Registration, Transfer Policy,
Transcripts, People Billing, and Organization Billing); Campaigns window of the
Donor Processing Workflow.

Code values entered here are stored in the Code_AddressType table.

Affiliation

This code table holds values that specify an individual’s affiliation with an organization.
Examples of affiliations might include: attorney, board member, volunteer, and trustee.

3-8 PowerCAMPUS Code Tables 8.1 June 2012

User Guide
Code Table Descriptions
 The length of the Code (Key) is restricted to 10 characters, and this code table is
applicable to Academic Records, Admissions, Advancement, Billing, and Cash Receipts.
The Affiliation field is populated by this code table.

Example of the field location in the system: Affiliations window of any people-related
or organization-related workflow.

Code values entered here are stored in the Code_Affiliation table.

Applicant rating type

This code table holds the code values for all rating types that can be tracked for an
applicant. Examples of application ratings might include: live audition, videotape and
phone interview. The length of the Code (Key) is restricted to10 characters, and this code
table is applicable to Admissions.

The Rating field is populated by this code table.

Example of the field location in the system: Rating window of the Applicants
Workflow.

Code values entered here are stored in the Code_ApplicantRating table.

Association

Associations to an organization or a group internal to your institution can be tracked in this

code table. Associations can later be assigned to all people with or without a year, year or
term or year, or term, or session. Examples of associations might include: French Club,
choir, Kiwannis Club, Junior League, and environmental club. The length of the Code
(Key) is restricted to 6 characters, and this code table is applicable to Academic Records,
Admissions, and Advancement.

The Association field is populated by this code table.

Example of the field location in the system: Associations window of any people-
related or organization-related workflow.

Code values entered here are stored in the Code_Association table.

Attendance status - course

This code table tracks the overall attendance status of the students of each course offered.
A last attendance date can also be assigned to the status of the student for a particular
course. Examples of overall attendance statuses might include: poor attendance, status
unknown, and attended. The length of the Code (Key) is restricted to 4 characters, and this
code table is applicable to Academic Records.

June 2012 PowerCAMPUS Code Tables 8.1 3-9

User Guide
Code Table Descriptions
 Entry of overall attendance statuses can be done by using the Attendance Status Workflow
in the Academic Records Setflow in PowerCAMPUS OR in PowerCAMPUS Self-
Service. For more information, refer to the Self-Service for Faculty User Guide.

The Attend Status and Attend Status (view only) fields are populated by this code table.

Example of the fields location in the system:

• Attend Status: Attendance Status window of the Attendance Status Workflow; Add
window of the Transcripts Workflow.
• Attend Status (view only): Detail window of the Grades Workflow.

Code values entered here are stored in the Code_AttendStatus table.

Attendance status - daily

This code table tracks the daily attendance status of the students of each course offered.
An attendance date can also be assigned to the status of the student for a particular course.
Examples of daily attendance statuses might include: absent, present, and excused tardy.

Entry of daily attendance statuses can be done by using the Attendance window of the
Students Workflow in the Academic Records Setflow in PowerCAMPUS, or by using the
Attendance window of the Gradebook page in Self-Service. For more information see
Students in Academic Records and the Self-Service for Faculty manual of the
documentation for Self-Service.

The length of the Code (Key) is restricted to 10 characters, and this code table is
applicable to Academic Records.

Tip
The code values Present and Absent are system-defined. These should
not be modified. A Category of excused absence, unexcused absence,
excused tardy, unexcused tardy or present must be assigned to each
daily attendance status. 

Note
Each category may only be assigned to one daily attendance status. 

The Attendance Status field is populated by this code table.

Example of the field location in the system: Attendance Status window of the Students
Workflow.

Code values entered here are stored in the Code_AttendStatusDetail table.

3-10 PowerCAMPUS Code Tables 8.1 June 2012

User Guide
Code Table Descriptions
 Attributes

This code table holds values that can be used to describe attributes or characteristics for a
catalog entry, section, person, campus, building, or room. Examples of attributes might
include: air conditioning, lab desks, flexible configuration, chalkboards, and handicap
accessible. Other examples of attributes include: smoker, non-smoker, interest in alumni
trips, etc. Each entry must have at least one attribute type selected: Day, Campus,
Building, Room, Resource, Event, Section, Time, or People. The length of the Code (Key)
is restricted to 10 characters, and this code table is applicable to Academic Records,
Admissions, Advancement, Billing, and Cash Receipts.

Note
When Event Attribute is selected or deselected, Section Attribute will
automatically be selected or deselected but can be changed. The
Attributes drop down list box on the Attributes window, available from any
people-related workflow, as well as the Catalog, Sections and Facility
Management Workflows, will include both days set up in the Day of Week
code table and the values set up in this code table. 

Attributes are used by the Master Scheduler process to schedule courses. If the only
attribute type selected for an attribute is the People Attribute, then the Master Scheduler
process will ignore it when scheduling courses.

Each entry must also have either the Sum the quantity of attributes or the Take the
maximum quantity of attributes radio button selected. This selection is used by the Master
Scheduler process when combining attributes for course sections and by faculty members
who are teaching the course sections.

For more information about the Master Scheduler process, see Master Scheduler in
Master Scheduler.

The Attribute and Attribute (view only) fields are populated by this code table.

Example of the fields location in the system:

• Attribute: Attributes window of any people-related workflow, the Catalog
Workflow and the Sections Workflow; Attributes window, available from the
Campus, Building and Room windows of the Facility Management Workflow.
• Attribute (view only): Time Block Attributes drill down of the Day of Week code
table (only attributes with an attribute type of Day or Time will display here).

Code values entered here are stored in the Code_Attributes table.

Award type

This code table is used to group award values. Examples of award types might include:
departmental and academic. Print Order determines the order in which the awards will
appear on data entry windows and any associated reports. The length of the Code (Key) is

June 2012 PowerCAMPUS Code Tables 8.1 3-11

User Guide
Code Table Descriptions
 restricted to 10 characters, and this code table is applicable to Academic Records, and
Admissions.

Note
In order to link award types with one or more awards from the Award
Value code table, double-click on the magnifying glass. A drill down
window will display to allow entry of the award values. 

Tip
The code values OVERSTND and TERMSTND are system-defined. Any
academic standing award values specifically associated with the
Academic Standing setup, located under Tools: Setup in the Academic
Records Setflow, should be linked to either OVERSTND or TERMSTAND.
The system-defined award values, OVERSTND and TERMSTND, will not
display in the Award Wizard process available from the Term Processing
Workflow. These award values are only applicable to the Academic
Standing setup. For more information about this setup, see Tools. 

The Type and Award Typefields are populated by this code table.

Example of the fields location in the system:

• Type: Awards window of the Transcripts Workflow.
• Award Type: Award Wizard process of the Term Processing Workflow.

Code values entered here are stored in the Code_AwardType table.

Award value

Academic achievements or sanctions are tracked using this code table. Examples of award
values might include: academic standings such as probation, suspension and dean’s list, as
well as academic awards such as PTK and departmental awards. The length of the Code
(Key) is restricted to 6 characters, and this code table is applicable to Academic Records,
and Admissions.

The Award, Award Value, and Standing fields are populated by this code table.

Example of the fields location in the system:

• Award: Awards window of the Transcripts Workflow.
• Award Value: Award Wizard process of the Term Processing Workflow.
• Standing: Academic Standing setup; Award Type code table.

Code values entered here are stored in the Code_AwardValue table.

3-12 PowerCAMPUS Code Tables 8.1 June 2012

User Guide
Code Table Descriptions
 Balance type

This code table is used to indicate the balance types used in PowerCAMPUS. This code
table is defined by the system and cannot be modified. The system-defined Balance Type
values are: Academic Year, Calendar Year, Current, Fiscal Year, Year/Term (All Sessions
Only), Year/Term (Term/All Sessions), Year/Term (Term/All Sessions + Cumulative),
Year/Term (Term Only), Year/Term (Term Only + Cumulative) and Year/Term/Session.

The Sort Order field determines the order in which the Balance Type values will display in
drop down list boxes on windows such as the Balance window in PowerCAMPUS. The
length of the Code (Key) is restricted to 6 characters, and this code table is applicable to
Billing.

The following table provides the definition for each of the system-defined Balance Type
values:

Sort
Code Key Long Description Order Definition
CURR Current 10 All charge or credit records,
regardless of entry date, year/
term or fiscal year.

ALLTERMCUM Year/Term (Term/All 20 All term and session level

Sessions + Cumulative) charge or credit records within
the year/term specified + the
cumulative balance for all
previous year/terms.

ALLTERM Year/Term (Term/All 30 All term and session level

Sessions) charge or credit records within
the year/term specified.

TERMCUM Year/Term (Term Only + 40 All term level charge or credit

Cumulative) records only within the year/
term specified + the
cumulative balance for all
previous year/terms.

TERM Year/Term (Term Only) 50 All term level charge or credit

records only within the year/
term specified.

ALLSESS Year/Term (All Sessions 60 All session level charge or

Only) credit records only within the
year/term specified(excludes
term level charge or credit
records).

June 2012 PowerCAMPUS Code Tables 8.1 3-13

User Guide
Code Table Descriptions
 Sort
Code Key Long Description Order Definition
YTS Year/Term/Session 70 All charge or credit records
within the year/term/session
specified.

ACAYR Academic Year 80 All charge or credit records

within the academic year
specified.

FISCYR Fiscal Year 90 All charge or credit records

within the fiscal year specified.

CALYR Calendar Year 100 All charge or credit records

within the calendar year
specified.

The View drop down list box, Balance, and Balance Type drop down list box fields are
populated by this code table.

Example of the fields location in the system:

• View:
• Balance window of the Registration, People Billing, Organization Billing,
and Cash Receipts Workflows (all balance types are available).
• Charge or Credit window of the Registration, People Billing, Organization
Billing (only the Year/Term (Term Only), Year/Term/Session, Year/Term
(Term/All Sessions) and Year/Term (All Sessions Only) balance types are
available).
• History window of the Registration, People Billing, Organization Billing,
and Cash Receipts (By People only) Workflows (all balance types are
available)
• Balance: Setup window of the Balance report of the Reports Workflow (all balance
types are available)
• Balance Type: Detail window of the Setup window for the Statements report of the
Reports, Registration, People Billing, Organization Billing, and Cash Receipts
Workflows and from the Charge/Credit drill down window of the Sponsor
Agreement window in the People and Organizations Workflows (all balance types
are available, except Current).

Code values entered here are stored in the Code_BalanceType table.

3-14 PowerCAMPUS Code Tables 8.1 June 2012

User Guide
Code Table Descriptions
 Building function

This code table is used to track the various functions of buildings. Examples of building
functions might include: administrative, classroom, and dormitory. A building may have
multiple functions on campus. For example, one building may hold administrative offices
as well as classroom space. The length of the Code (Key) is restricted to 6 characters, and
this code table is applicable to Academic Records.

The Function field is populated by this code table.

Example of the field location in the system: Function window of the Facility
Management Workflow (available by selecting Building from the drop down list box).

Code values entered here are stored in the Code_BuildFunction table.

CASE type

This code table tracks a constituent’s classifications for use in the Council for
Advancement in Support of Education (CASE) report. Each type must be assigned a sort
order for reporting and a category of people, organizations, or both. Examples of CASE
types might include: alumni, corporation, foundation, friend, government, parent, and
religious institution. The length of the Code (Key) is restricted to 10 characters, and this
code table is applicable to Advancement.

The CASE Type and CASE Types fields are populated by this code table.

Example of the fields location in the system:

• CASE Type: CASE Type window of the Alumni Workflow, the People Workflow
and the Organizations Workflow in the Advancement Setflow only.
• CASE Types: Record Type code table.

Code values entered here are stored in the Code_CASEType table.

CIP

This code table holds code values for Classification of Instruction Programs (CIP). Course
and curriculum offerings may be coded with CIP codes. These codes should be obtained
from the Board of Education. The length of the Code (Key) is restricted to 20 characters,
and this code table is applicable to Academic Records.

The CIP field is populated by this code table.

Example of the field location in the system: Catalog window of the Catalog
Workflow; Detail window of the Registration Workflow.

Code values entered here are stored in the Code_CIP table.

June 2012 PowerCAMPUS Code Tables 8.1 3-15

User Guide
Code Table Descriptions
 Cancel section reason

This code table tracks the reasons for canceling a course section. Examples of cancel
section reasons might include: low enrollment, faculty availability, and attribute
availability. The length of the Code (Key) is restricted to 10 characters, and this code table
is applicable to Academic Records.

The Reason field is populated by this code table.

Example of the field location in the system: Section window of the Sections
Workflow.

Code values entered here are stored in the Code_CancelSectionReason table.

Cancel action reason

This code table tracks reasons for cancellation of an action, such as a letter or telephone
call. Examples of cancel action reasons might include: donor’s request, student’s request,
course cancellation, and withdrawal. The length of the Code (Key) is restricted to 6
characters, and this code table is applicable to Academic Records, Admissions,
Advancement, Billing, and Cash Receipts.

The field to the right of the Canceled check box is populated by this code table.

Example of the field location in the system: Scheduled Actions drill down, available
from the Scheduled Actions window of any people-related or organization-related
workflow.

Code values entered here are stored in the Code_CancelReason table.

Change reason (name)

This code table tracks the reasons for changing a name. Examples of name change reasons
might include: marriage, divorce, and preference. The length of the Code (Key) is
restricted to 4 characters, and this code table is applicable to Academic Records,
Admissions, and Advancement.

The Change Reason field is populated by this code table.

Example of the field location in the system: Former Names window of any people-
related workflow.

Code values entered here are stored in the Code_NameChgReason table.

3-16 PowerCAMPUS Code Tables 8.1 June 2012

User Guide
Code Table Descriptions
 Charge/Credit

The Charge/Credit code table is the main code table used in both the Billing and Cash
Receipts systems. It enables the setup of charges, credits, cash receipts, and financial aid
coding structure. All entries that will affect a person/organization’s statement or balance
must be set up here. Examples of charge or credits might include: tuition, graduation fees,
insurance fees, and dorm fees or deposits, as well as financial aid such as PELL grants and
SEOG. If your institution uses multiple accounts receivable (A/R) accounts that depend on
the student’s program, college, degree, or curriculum, each variation must be established
as a separate charge or credit. The length of the Code (Key) is restricted to 10 characters,
and this code table is applicable to Billing, and Cash Receipts.

This code table populates dozens of fields throughout the PowerCAMPUS system and is
absolutely essential if you are running either the Billing module or the Cash Receipts
module of PowerCAMPUS.

In order to build this code table quickly and efficiently and be prepared to begin using
your billing system, follow the workflow below:

1. Upload your current chart of accounts into the PowerCAMPUS ChartofAccounts

table or manually enter your chart of accounts.

2. Set up all other billing-related code tables first, leaving the Charge or Credit (Code)
code table for last.

3. Use the Charge or “Code Tables Template”, found in the appendix of Code Tables, to
help define your code values on paper first.

4. Set up the Charge/Credit (Code) code table, being sure to save cash receipt code
values for last. Other codes, such as those for financial aid, will be prompted for when
setting up your cash receipt code values.

5. If you are going to use either the Academic Records Setflow or the Cash Receipts
Setflow to enter miscellaneous cash receipts, set up as many codes as you have cash
accounts. You may edit the credit account on the Cash Receipts Distribution pop-up
either on the Receipts window of the Registration Workflow in the Academic Records
Setflow or the Receipts window of the Cash Receipts Workflow in the Cash Receipts
Setflow.

Note
The Charge/Credit code table cannot be accessed using the Academic
Records Setflow. 

6. Complete all options under Tools: Setup in the Billing Setflow prior to entering
student information into the billing system.

June 2012 PowerCAMPUS Code Tables 8.1 3-17

User Guide
Code Table Descriptions
 This code table has numerous fields necessary for entry, which are described below.

The Code (Key) is the system identifier that you wish to use for this charge or credit code.
The Code will default based upon the Code (Key) and the Status will default to Active.

Note
Once a charge or credit code has been used anywhere in the
PowerCAMPUS system, do not change the Code (Key) for the charge or
credit code. Instead, inactivate the incorrect code, by changing its Status
to Inactive, and create a new code. 

Tip
A Type of charge, credit, financial aid, or cash receipt must be assigned to
each charge or credit that is entered. When entering the Type, you can
select 'C' to bring up the Charge type. Selecting 'C' again will change the
type to Credit. Selecting it a third time will change the type to Cash
Receipt. Descriptions for each of the charge or credit entries must be set
up here. Keep in mind that the Long Description is used on statements.

The Handle/Late Fee checkbox, which will only be available if a Type of

Charge is selected, is used with the Payment Plan and Late Fee
Assessment processes. Selecting this checkbox will allow the amount of
the charge to be a percentage amount, as well as a flat or per credit
amount. 

Going ahead the Taxable checkbox will determine if the amount of this charge, credit,
cash receipt or financial aid code can have taxes applied to it.

The Include in Payment Option check box is used to determine if this charge or credit
code is to be included in determining the amount due per statement for students that have
elected a payment option. All charge or credit codes will be included in the payment
option by default, but this can be changed if necessary.

Note
The Include in Payment Option checkbox is not related to payment plans
in any way. Students may opt for either a payment plan or a payment
option, or they may elect not to follow either payment assistance program.
For more information, see Understanding Student Payment Assistance
Programs. 

• Select the Fin (financial) Aid Eligible check box to indicate if a charge can be
paid off by financial aid. Charges such as library fines and dorm damage may not
be able to be paid by any financial aid that a student receives.
• Select the Eligible for Refund checkbox for those charge or credits that can be
adjusted if a student decreases his credit load or has had some sort of circumstantial
change that affects his bill, such as a dorm or meal plan change.
• Select the Beginning Balance checkbox if the charge record that gets created at the
end of a fiscal year, which records a student’s outstanding balance, becomes the
beginning balance record for the new fiscal year. Do not select Beginning Balance

3-18 PowerCAMPUS Code Tables 8.1 June 2012

User Guide
Code Table Descriptions
 if there will be no supporting detail to this record, as is the case when you are
converting just a lump sum balance record for each student. Beginning balance
records do not get posted.

Note
Only select the Beginning Balance checkbox for the actual code value
that represents the beginning balance code. There should be one charge
or credit code flagged as Beginning Balance for each accounts receivable
account in your institution’s chart of accounts. For more information, see
Beginning Balance in Billing. 

• Select the Detail Present checkbox on a charge or credit record if those charge or
credits that are uploaded into the PowerCAMPUS system have a summary record
in the ChargeCredit table and the supporting detail information in the
ChargeCreditLine table.
For example, each line item of detail on a phone bill may be uploaded into the
ChargeCreditLine table. However, only the overall telephone bill amount is
uploaded into the ChargeCredit table and printed on statements. Most, if not all, of
your entries will leave the Detail Present check box deselected.

A 1098-T Type of tuition and related expenses, scholarships or grants, or not applicable
must be assigned to each charge or credit that is entered. This information is used when
generating the 1098-T form. For more information, see Taxpayers Relief Act.

Note
The 1098-T Type field defaults Not Applicable for all new code table
entries and is disabled for charge or credit codes with a Type of Cash
Receipt, since cash receipts are not included in the 1098-T calculations. 

Indicate the Amount of the charge or credit and whether the amount is calculated as a per
credit or flat fee amount. If the Handle/Late Fee check box is selected, you may also
choose to enter a percentage amount.

Note
The Amount may be entered as $0.00 for charges that can vary in
amount, such as library or parking fines. Charge/credit codes that are
intended to be section fees, such as course or lab fees that can vary in
amount based upon the type of course or number of credits for the
course, may also be set to $0.00 or any other amount and then changed
when the fee is linked to the course.

For example, you may have a flat $100.00 course fee and then wish to
add that same course fee to twenty different sections, all with different flat
or per credit amounts. However, charge or credit codes that have a
specific rate amount for the academic year/term, such as a flat tuition rate
or flat meal plan rate, should be created with the actual amount and
should not be changed mid-term, after the charge or credit code has been
used in an assessment rule.

In other words, you must not initially set the amount of a charge or credit

June 2012 PowerCAMPUS Code Tables 8.1 3-19

User Guide
Code Table Descriptions
 code, create an assessment rule using the code, and then change the
amount in the code table and reapply it to the same assessment rule or
add the same charge or credit code to another assessment rule for the
same year or term. Regardless of whether the amount is different, you
should not use the same charge or credit code in multiple assessment
rules, unless the charge or credit code is being set up as a section fee on
the Fees window of the Sections Workflow. 

Tip
Negative amounts for charges, credits, cash receipts, and financial aid will
display in red throughout the system on windows such as those of the
People Billing, Organization Billing and Cash Receipts Workflows. The
GL Account 1 (Debit) and GL Account 2 (Credit) fields must be completed
for each charge or credit code value.

There are two ways to enter the GL accounts for each charge or credit
code. One is to manually enter the GL account ID. Upon entering the GL
account ID, the system will confirm that the account ID is valid. The other
is to use the Chart of Accounts search, available from the Search pull-
down menu of the Main Menu Bar, to select the appropriate accounts. 

Note
All charge or credits to be used for a person or organization must either
debit or credit an accounts receivable account. Only cash receipts used
for miscellaneous cash received from an organization can debit or credit
any account, as long as the cash receipt is not associated with any
specific charge. However, if organizations, such as those that are
sponsors, are receiving charges, then you will want to set up cash receipt
codes for organizations that will credit an accounts receivable account. 

Tip
Codes flagged as Beginning Balance must have an A/R account entered
as the debit account. The credit account cannot also be an accounts
receivable account. An account is flagged as an A/R Account using the
Chart of Accounts Workflow in either the Billing or Cash Receipts Setflow.

Remember the following statements:

• Charge or credit codes that have a Type of Charge should debit an accounts
receivable account and credit a revenue/income account.
• Charge or credit codes that have a Type of Credit should debit a revenue or
income account and credit an accounts receivable account.
• Charge/credit codes that have a Type of Financial Aid should debit a federal
income account (if federal aid) or a revenue or income account (if non-
federal aid) and credit an accounts receivable account.
• Charge/credit codes that have a Type of Cash Receipt should debit a cash
account and credit an accounts receivable account.
• Once a charge or credit code has been used anywhere in the PowerCAMPUS
system, do not change the debit or credit GL account ID. Instead, inactivate
the incorrect code and create a new code.

3-20 PowerCAMPUS Code Tables 8.1 June 2012

User Guide
Code Table Descriptions
 • If the GL accounts are set up incorrectly, then the Beginning Balance process
will return errors and fail to create the beginning balance charge or credit
records.

Tip
You will receive a warning message if a debit account ID and credit
account ID are the same. You may continue if this is a valid setup. For
example, the payment plan offset charge or credit code is set up in this
manner. For more information, see Payment Plan in Billing.

Statement Type displays a drop down list box of the values in the
Statement Type code table. Statement types group charge or credit rows
together on statements.

Summary Type displays a drop down list box of the values in the
Summary Type code table. Summary types group charge or credit codes
together to provide summary financial information and summary views of
data. For more information about these code tables, see Summary Type
and Statement Type.

Print Order applies to all charge or credits entered in this code table.
Statements and other reports will print all charge or credits first by entry
date order then by print order. Print order can be numbered from 001
through 999. The Print Order does not have to be unique for each charge
or credit code. You may want to group different types of code values in a
specific range of numbers. Leave spaces in your numbering scheme for
Print Order and Distribution Order. You may need to add code values after
your initial setup of the code table. 

Going ahead the Distribution Order of a charge must be entered in order to indicate in
what priority order charges are to be paid off by a cash receipt, financial aid, or a credit.
For example, you may want tuition to be paid off first (distribution order 001), followed
by student fees (distribution order 002) and health (distribution order 003). The
outstanding charges are sorted first by the distribution order and then by the oldest date.
For now, Distribution Order is not a required field.
• Select the Overload check box to indicate that the charge being set up is an
overload charge. An overload charge will be charged to students who exceed the
course credit base amount.

You must enter a Course Credit Base amount when setting up an overload charge. If you
assess an overload charge for credits taken above a certain amount, enter that amount as
the course credit base. Any credits taken above that base amount will be assessed the
overload charge amount (flat fee or per credit).

Note
Project ID is currently not available. 

June 2012 PowerCAMPUS Code Tables 8.1 3-21

User Guide
Code Table Descriptions
 Associated Fin Aid Code

The Associated Fin Aid Code is used only with cash receipt charge or credit codes. This
field will be used by the PowerCAMPUS Charge or Credit Import process, by the Cash
Receipts Workflow in the Cash Receipts Setflow, and by the Registration Workflow in the
Academic Records Setflow when anticipated financial aid is reduced by the amount of a
cash receipt. For example, a bank loan is showing as anticipated aid on a student’s
account. When the check is received, the anticipated aid will be either reduced (if not fully
received) or voided (if fully received). The charge or credit code value for this cash receipt
must be set up with the associated financial aid code it can reduce. The drop down list box
on the field Associated Fin Aid Code will be available for entry only for charge or credit
codes set up with a Type of Financial Aid.

Fin Aid Upload Code

The Fin Aid Upload Code is used to indicate the corresponding Fund ID in PowerFAIDS,
if this financial aid system is used. When the PowerFAIDS Interface to PowerCAMPUS
process is run, the upload code is used to convert the data into PowerCAMPUS with the
correct PowerCAMPUS code.

Note
Each new academic year, new fund IDs are assigned in PowerFAIDS.
When the new Fund IDs are available in PowerFAIDS, you MUST update
the Fin Aid Upload Code field with the new Fund ID in PowerFAIDS for
each of the corresponding financial aid codes in PowerCAMPUS. For
more information about setting up fund IDs, see the Funds and Manual
Packaging chapter of the documentation for PowerFAIDS. 

Fin Aid Fee

The Fin Aid Fee is used if the code value being entered has a type of financial aid and
needs to subtract a fee from the awarded amount. This is usually the case for loans. Select
either None, Flat Fee, Percentage, Flat & Percentage, or Percentage & Flat.

Flat & Percentage Vs Percentage & Flat

The difference between Flat & Percentage and Percentage & Flat is the order in which the
financial aid amount is reduced. For example, if you select Flat & Percentage, the amount
will be reduced first by the flat amount specified and then by the percentage amount
specified. If you select Percentage & Flat, the amount will be reduced first by the
percentage amount. Depending on what was entered in Financial Aid Fee, you can enter
either the Fin Aid Flat Fee, the Fin Aid % Fee, none, or both. For example, Stafford Loans
are reduced by 4 % of the awarded amount. In the case, the Financial Aid Fee would be
Percentage and the Fin Aid % Fee would be '4.00'.

Note
E-mail Message is currently not available. 

3-22 PowerCAMPUS Code Tables 8.1 June 2012

User Guide
Code Table Descriptions
 Statement Message

Statement Message is a message printed on every statement underneath the associated

charge or credit description. If a charge or credit is to print on a statement, the message
found here will also print. This statement message will print in addition to the messages
set up in the Statement Message code table.

Note
Help description is currently not available. 

For more information about the Version 4.X Code and Version 4.X Description fields, see
“Code Table Values”.

For more information about charge or credits, cash receipts and financial aid in general,
see Introduction to Billing in Billing.

Code values entered here are stored in the Code_ChargeCredit table.

Class level

This code table holds the code values that define the various levels of the different classes
of students. Examples of class levels might include: freshman, sophomore, junior, and
senior. Nontraditional schools will be able to use the coding to meet their own unique
requirements. Class level is usually determined by number of credits and these should be
established in the Student Coding setup, located under Tools: Setup in the Academic
Records Setflow. Different values can be given for different program/degree/curriculums.
The length of the Code (Key) is restricted to 4 characters, and this code table is applicable
to Academic Records, and Admissions.

The Class Level and Class Level (view only) fields are populated by this code table.

Example of the fields location in the system:

• Class Level: Application window of the Applicants Workflow; Target window of
the Sources Workflow; Academic window of the Registration Workflow; Catalog
window of the Catalog Workflow; Others Allowed window of the Catalog
Workflow and the Sections Workflow.
• Class Level (view only): View State/High School Vista view.

Code values entered here are stored in the Code_ClassLevel table.

Cohort

Cohorts, or groupings of students, are tracked using this code table. An example of a
cohort value is Fall06Und. This cohort may include all the full-time, first-time degree
seeking undergraduate students to your institution in Fall 2006. The length of the Code

June 2012 PowerCAMPUS Code Tables 8.1 3-23

User Guide
Code Table Descriptions
 (Key) is restricted to 10 characters, and this code table is applicable to Academic Records,
and Admissions.

The Effective Date represents the beginning of the time frame used to define the cohort.
The value entered here is the default effective date defined for the student’s association to
the selected cohort when entered on the Cohorts window of the Students Workflow.

The End Date represents the end of the time frame used to define the cohort. This field is
included for information only.

The Cohort field is populated by this code table.

Example of the field location in the system: Cohorts window of the Students
Workflow.

Code values entered here are stored in the Code_Cohorts table.

Cohort exclusion

Cohort Exclusions are tracked using this system defined code table. Tracking sub cohorts
enables the institution to develop statistical reports based upon the sub groupings within a
cohort. Sub cohorts permit the institution to associate students with a sports team.
Examples of a sub cohort values are Baseball, Basketball, Football, Other, and Track/
Cross Country. The length of the Code (Key) is restricted to 10 characters, and this code
table is applicable to Academic Records, and Admissions.

The Sub Cohort field is populated by this code table.

Example of the field location in the system: Cohorts window of the Students
Workflow.

Code values entered here are stored in the Code_CohortExclusions table.

Collection rating
This code table holds the values that track the potential for collection of a pledge.
Examples of collection ratings might include: 100%, 50%, high, low, and medium. The
length of the Code (Key) is restricted to 10 characters, and this code table is applicable to
Advancement.

The Collection Rating field is populated by this code table.

Example of the field location in the system: Pledges window of the Donor Processing
Workflow.

Code values entered here are stored in the Code_CollectionRating table.

3-24 PowerCAMPUS Code Tables 8.1 June 2012

User Guide
Code Table Descriptions
 College

Separate colleges at an institution may be defined through this code table. Examples of
colleges might include: Arts & Sciences, Business, Nursing, and Engineering. The length
of the Code (Key) is restricted to 6 characters, and this code table is applicable to
Academic Records, Admissions, and Advancement.

The College field is populated by this code table.

Example of the field location in the system: Inquiry window of the Inquiries
Workflow; Application window of the Applicants Workflow; Target window of the
Sources Workflow; Academic window of the Registration Workflow; Catalog window
of the Catalog Workflow; Others Allowed window of the Catalog Workflow and the
Sections Workflow; Degrees window of the Transcripts Workflow (the College can be
changed for the printing of a transcript here, but this change will not be updated in the
student’s academic record).

Code values entered here are stored in the Code_College table.

College attend status

This code table holds the code values for a student’s college attendance. College attend
status will be automatically updated as students register. Certain codes can be set up as
defaults to indicate if this is the student’s first time attending the institution (new student),
if the student attended last term, or if the student attended previously but did not attend last
term. Selecting the different default code checkboxes determines the values that will
update the college attend status for students. The system will verify that you have only one
code flagged as New Student, only one code flagged as Last Term and only one code
flagged as Previously Attended. Examples of college attend statuses might include: first
semester, last semester, and previous semester. The length of the Code (Key) is restricted
to 4 characters, and this code table is applicable to Academic Records, Admissions, and
Self-Service.

Note
If you do not want the system to update the college attend status
automatically, you may still set up your codes; however, do not flag any of
your codes with any of the three default code checkboxes. In order for
College Attend values to be updating properly, you must set all the flags
for the defaults codes. For example, there must be one value with the
New Student default selected, one with Last Term default selected and
one with Previously Attended default selected. 

June 2012 PowerCAMPUS Code Tables 8.1 3-25

User Guide
Code Table Descriptions
 The College Attendance, College Attend, College Attend Status and College Attend
Status (view only) fields are populated by this code table.

Example of the fields location in the system:

• College Attendance: Application window of the Applicants Workflow.
• College Attend: Academic window of the Registration Workflow; Inquiry window
of the Inquiries Workflow.
• College Attend Status: Online Application and Online Inquiry forms in Self-
Service.
• College Attend Status (view only): View State/High School Vista view

Code values entered here are stored in the Code_CollegeAttend table.

Column comparison

All possible column comparisons and their descriptions for duplicate checking are stored
in this code table. For each column that can be compared it is indicated whether it is a
column for the name or address by the People/Address field. This code table is defined by
the system and cannot be modified. The system-defined column comparisons are: Address
Lines, Bits of First Name, Bits of Last Name, City, Date of Birth, Email Address, First
Name, Former First Name, Former Last Name, Gender Code, Government ID, Last Name,
Middle Initial, Phone Number, Soundex of First Name, Soundex of Last Name, State,
Suffix and Zip Code. The length of the Code (Key) is restricted to 10 characters, and this
code table is applicable to System Administrator.

The Comparison Column field is populated by this code table.

Example of the field location in the system: Groups window of the Duplicate
Checking setup. System Administrator

Code values entered here are stored in the Code_ColumnComparison table.

Communications type

This code table is used to record the different methods of communication with a person or
organization. Examples of communications types might include: beeper, fax, voice mail,
and web site. The HISTE (historical email) communication type will default as one of
your values. The code value HISTE is system-defined and cannot be modified. The length
of the Code (Key) is restricted to 10 characters, and this code table is applicable to
Academic Records, Admissions, Advancement, Billing, and Cash Receipts. The Type
field is populated by this code table.

Example of the field location in the system: Telecommunications window of any

people-related or organization-related workflow. Code values entered here are stored
in the Code_ComType table.

3-26 PowerCAMPUS Code Tables 8.1 June 2012

User Guide
Code Table Descriptions
 Condition (facilities)

The Condition field is used in the Facility Management Workflow to define the state of a
particular room. Examples of facilities conditions might include: good, satisfactory, and
poor. The length of the Code (Key) is restricted to 6 characters, and this code table is
applicable to Academic Records.

The Condition field is populated by this code table.

Example of the field location in the system: Room window of the Facility
Management Workflow.

Code values entered here are stored in the Code_Condition table.

Contact

The Contact field is used when recording information about a scheduled action and
regards the type of contact you had with a person or organization. Examples of contacts
might include: left message, spoke with inquiry, no answer, and spoke with parents. The
length of the Code (Key) is restricted to 6 characters, and this code table is applicable to
Academic Records, Admissions, Advancement, Billing, Cash Receipts, and System
Administrator.

The Contact field is populated by this code table.

Example of the field location in the system: Scheduled Actions drill down, available
from the Scheduled Actions window of any people-related or organization-related
workflow.

Code values entered here are stored in the Code_Contact table.

Control type (institution)

The Control Type field is used to describe the controlling body at an institution. Examples
of control types might include: public, private, and state. The length of the Code (Key) is
restricted to 6 characters, and this code table is applicable to Admissions.

The Control Type field is populated by this code table.

Example of the field location in the system: Institution window of the Institutions
Workflow and the Transfer Policy Workflow.

Code values entered here are stored in the Code_ControlType table.

June 2012 PowerCAMPUS Code Tables 8.1 3-27

User Guide
Code Table Descriptions
 Country

Various countries may be entered in this code table. Examples of countries might include:
India, Japan, Poland and United States. The country code can also be used to determine
the format for phone numbers stored on the Phone Numbers window, for phone numbers
associated with rooms on your campus in Facility Management and for phone numbers for
emergency contacts entered on the emergency window. In the Phone Format field, enter
the format that you wish the phone numbers to have using the wildcard symbol (as the
numbers), parentheses, dashes or appropriate symbols, country codes, city codes, etc. (i.e.,
(@@@) @@@-@@@@ or @@-@@@@@@@@). For this to be the case, enter the
format that you wish the phone numbers to have using the wildcard symbol (as the
numbers), parentheses, and dashes. The length of the Code (Key) is restricted to 6
characters, and this code table is applicable to Academic Records, Admissions,
Advancement, Billing, and Cash Receipts.

Note
The symbol used for a wildcard is set up by the system administrator in
the Wildcard setup, located under Tools: Setup in the System
Administrator Setflow. 

The SEVIS Country Code field allows you to map the PowerCAMPUS country code
values with the corresponding codes for SEVIS reporting purposes. The Citizenship
checkbox allows you to determine which countries should display in the drop down list
box for the Citizenship field. The Birth Country field.

The ISO 3166 Country Code field allows you to map the PowerCAMPUS country code
values with the corresponding ISO 3166 country codes for IMS Enterprise standards.

The Print Country with address checkbox allows you to determine which countries should
display and/or print on sheets and reports.

Note
The Print Country with address checkbox is not used to determine which
countries should display and/or print on mailings handled in the Mail
Merge Processing Workflow. When setting up your form documents, you
will need to add logic using the If…Then…Else option, available from the
Insert Word Field button in MS Word, in order to suppress the country for
domestic addresses. For more information, see the documentation for
Microsoft Word. It is good practice to make the Code Key for this table
follow international standards. The Code Key listed for the country will
print on 1098-T forms (Taxpayers Relief Act) for all foreign students in the
City, state, and ZIP code line. 

The Country, Citizenship, Dual Citizenship, Country of Birth, Select Code for United
States, Country, Other Country and Issuing Country fields are populated by this code
table.

3-28 PowerCAMPUS Code Tables 8.1 June 2012

User Guide
Code Table Descriptions
 Example of the fields location in the system:

Field Description
Country • Address window of any people-related or organization-
related workflow (including Facility Management,
Registration, Transfer Policy, Transcripts, People Billing,
Organization Billing).
• Phone Numbers window of any people-related workflow
(including Inquiries, Applicants, Students, Faculty, People,
Registration, Alumni)

Citizenship, Dual Name window of any people-related workflow (excluding

Citizenship, Country of Inquiries but including Registration, Transcripts, People
Birth Billing); Demographics window of the Inquiries Workflow;
Demographics window of the Applicants Workflow and the
Students Workflow.

Select Code for United NSC Processing process of the Registration Processing
States Workflow

Country, Other Country Online Application and Online Inquiry pages in Self-Service

Issuing Country Government window of the People Workflow, Inquiries

Workflow, Applicants Workflow, Faculty Workflow, Students
Workflow and Registration Workflow

Code values entered here are stored in the Code_Country table.

County

Each address can be coded with a county. In addition, county information, such as length
of residency, is stored in the student’s financial records. The length of the Code (Key) is
restricted to 6 characters, and this code table is applicable to Academic Records,
Admissions, Advancement, Billing, and Cash Receipts.

The County field is populated by this code table.

Example of the field location in the system: Address window of any people-related or
organization-related workflow (including Facility Management, Registration, Transfer
Policy, Transcripts, People Billing, Organization Billing); Financials window of the
Applicants Workflow, the Students Workflow and the Registration Workflow.

Code values entered here are stored in the Code_County table.

June 2012 PowerCAMPUS Code Tables 8.1 3-29

User Guide
Code Table Descriptions
 Credit type (academic)

Courses may have multiple credit types. Examples of credit types might include: cross
enroll, continuing education, and senior discount. The length of the Code (Key) is
restricted to 4 characters, and this code table is applicable to Academic Records, Billing
and Cash Receipts.

Credit Type is also used to define the type of grade a student will receive. Examples of this
use might include: pass/fail and audit. Credit types are differentiated by the amount of
course credit given for each of a variety of categories. Different amounts of credit can be
given for the categories Grade, Registration, Billing, FTE, Workload, Federal Financial
Aid, State Financial Aid, County Financial Aid, Federal Reporting, State Reporting, and
County Reporting. The Credit Type (Academic) code table stores High/Low values for
these categories. A particular population of students can be associated with a specific
credit type on the Population code table. For more information about credit types, see
Understanding Credit Types in Academic Records.

The Credit Type, Credit Type (view only), Type field (view only), Default Credit
Type, Default Credit Types, and Default Credit Types for Sub Type fields are
populated by this code table.

Example of the fields location in the system:

• Credit Type: Grade Values setup; Add and Transfer windows of the Transcripts
Workflow; Catalog, Subtype and Credits windows of the Catalog Workflow;
Section and Credits windows of the Sections Workflow.
• Credit Type (view only): Student Withdrawal Process of the Registration
Processing Workflow; Grades window of the Grades Workflow; Attendance Status
window of the Attendance Status Workflow.
• Type field (view only): Detail window of the Grades Workflow.
• Default Credit Type: Population code table.
• Default Credit Types, Default Credit Types for Sub Type: Catalog Preferences
setup.

Code values entered here are stored in the Code_AcaCreditType table.

Curriculum

All available curriculum majors, minors, and concentrations should be entered in this code
table. Examples of curriculums might include: Art, English, Accounting, and Biology. The
Formal Title field defaults from the Long Description and will be the description that

3-30 PowerCAMPUS Code Tables 8.1 June 2012

User Guide
Code Table Descriptions
 prints on transcripts. The length of the Code (Key) is restricted to 6 characters, and this
code table is applicable to Academic Records, Advancement, and Admissions.

Tip
Some institutions require a way to track home and sending schools and
related academic information in the event that a student is studying
abroad. This feature is available on the Home/Sending School window.
On this window, curriculums will display in a drop down list box labeled
Duration. Therefore, if you will be using this feature, you may want to add
some code values for international study program durations to the
Curriculum code table. You can then select these on the Application
window when a student applies for an international study program. 

The Curriculum, Curriculum (view only), and Duration fields are populated by this
code table.

Example of the fields location in the system:

• Curriculum: Inquiry window of the Inquiries Workflow; Application window of the
Applicants Workflow; Source window of the Inquiries Workflow and the
Applicants Workflow; Target window of the Sources Workflow; Academic window
of the Students Workflow, the Academic Plan Workflow, and the Registration
Workflow; Catalog window of the Catalog Workflow; Others Allowed window of
the Catalog Workflow and the Sections Workflow; Education window of any
people-related workflow (including Registration and Transcripts); Honors window
of the Transcripts Workflow; Degree Requirement setup and Copy to New Matric
Year/Term processes of the Degree Requirement Setup Workflow; Change Plan
window of the Academic Plan Workflow.
• Curriculum (view only): Academic window of the People Billing Workflow.
• Duration: Home/Sending School window of the Applicants Workflow and the
Students Workflow.

Code values entered here are stored in the Code_Curriculum table.

Day of week

This code table maintains the days of the week when events, including courses, meetings,
office hours, etc., can be held. All days of the week should be listed individually, as well as
common combinations, such as Tuesday, or Thursday or Monday, or Wednesday or
Friday. Selecting the appropriate check boxes allows PowerCAMPUS to map the selected
days to its own academic calendar. The length of the Code (Key) is restricted to 4
characters, and this code table is applicable to Academic Records.

If your institution plans to implement online registration using Self-Service, you should
also create codes for courses that will never have a set schedule, such as independent study
courses. Additionally, you should create a ‘to be determined’ code for courses that do not

June 2012 PowerCAMPUS Code Tables 8.1 3-31

User Guide
Code Table Descriptions
 have a set schedule when registration begins. In these examples, you should not select any
of the day checkboxes.

Tip
A drill down, accessible from the Clock icon, takes you to the Time Blocks
window and allows you to enter the valid Start Time and End Time for a
particular day code. For example, MWF may have time blocks for 8:00
AM - 8:50 AM, 9:00 AM - 9:50 AM, etc. Time blocks must be entered in
order for the Master Scheduler process to automatically assign courses to
rooms. 

Once you have entered time blocks, you can use the Time Block Attributes drill down,
accessible from the magnifying glass icon, to enter time block attributes for each day and
time. All attributes that have been specified as Day/Time on the Attributes code table will
display here. Select the attributes that apply to each day/time combination. For example,
you might want to set up the 8:00 to 8:50 AM time block for MWF to be Weekday and
Morning. For more information about the Master Scheduler process, see Master Scheduler
in Master Scheduler.

The Day, Day(s) (view only), and Attribute fields are populated by this code table.

Example of the fields location in the system:

• Day: Properties window of the Master Calendar Workflow.
• Day(s) (view only): Schedule window of the Catalog Workflow and the Sections
Workflow.
• Attribute: Attributes window of any people-related workflow, the Catalog
Workflow and the Sections Workflow; Attributes window, available from the
Campus, Building and Room windows of the Facility Management Workflow.

Code values entered here are stored in the Code_Day, TimeBlockAttributes, and
TimeBlocks table.

Decision (application)

This code table holds the code values for all decisions made regarding your institution’s
acceptance or denial of an applicant. Examples of application decisions might include:
conditional, denied, accepted, and waitlisted. The decisions that are considered “accepted”
must be indicated. Applicants with accepted decisions and a confirmed status will
automatically be converted to students. The length of the Code (Key) is restricted to 4
characters, and this code table is applicable to Admissions.

The Decision, and Application Decision (view only) fields are populated by this code
table.

Example of the fields location in the system:

• Decision: Application window of the Applicants Workflow; Applicants setup.

3-32 PowerCAMPUS Code Tables 8.1 June 2012

User Guide
Code Table Descriptions
 • Application Decision (view only): Admissions Educ Vista report; Admissions
Status Vista report; Source - Applicants Vista report; View Applicant Sources Vista
view; View Applicant Demographics Vista view; View Applicant State/Education
Vista view.

Code values entered here are stored in the Code_AppDecision table.

Dedication notify
This code table holds the values that specify who should receive notification of a
dedication gift. Examples might include: attorney, bank, and family. The length of the
Code (Key) is restricted to 10 characters, and this code table is applicable to
Advancement.

The Notify, and Dedication Notify fields are populated by this code table.

Example of the fields location in the system:

• Notify: Dedications window, available by selecting the Show Detail button on
either the Gifts window or the Pledges window of the Donor Processing Workflow.
• Dedication Notify: Batch Gift and Pledge Defaults window of the Donor
Processing Workflow.

Code values entered here are stored in the Code_DedicationNotify table.

Dedication type

This code table holds the values that differentiate dedication gifts for use in mail merge
processing. Examples of dedication types might include: Dedication to, In honor of, and In
memory of. The length of the Code (Key) is restricted to 10 characters, and this code table
is applicable to Advancement.

The Type, and Dedication Type fields are populated by this code table.

Example of the fields location in the system:

• Type: Dedications window of the Alumni Workflow and the People Workflow in
the Advancement Setflow only; Dedications window, available by selecting the
Show Detail button on either the Gifts window or the Pledges window of the Donor
Processing Workflow.
• Dedication Type: Batch Gift and Pledge Defaults window of the Donor Processing
Workflow.

Code values entered here are stored in the Code_DedicationType table.

June 2012 PowerCAMPUS Code Tables 8.1 3-33

User Guide
Code Table Descriptions
 Dedication value

This code table holds the values that specify the category of the dedication gift. Examples
of dedication values might include: memorial and tribute. The length of the Code (Key) is
restricted to 10 characters, and this code table is applicable to Advancement.

The Value, and Dedication Value fields are populated by this code table.

Example of the fields location in the system:

• Value: Dedications window of the Alumni Workflow and the People Workflow in
the Advancement Setflow only; Dedications window, available by selecting the
Show Detail button on either the Gifts window or the Pledges window of the Donor
Processing Workflow.
• Dedication Value: Batch Gift and Pledge Defaults window of the Donor Processing
Workflow.

Code values entered here are stored in the Code_DedicationValue table.

Deferred giving status

This code table tracks the condition of a deferred gift. This code table is defined by the
system and cannot be modified. The system-defined deferred giving status values are:
Canceled, Closed, Pending, Pledged, and Received. The length of the Code (Key) is
restricted to 10 characters, and this code table is applicable to Advancement.

The Status field is populated by this code table.

Example of the field location in the system: Deferred window of the Donor Processing
Workflow.

Code values entered here are stored in the Code_DeferredStatus table.

Deferred giving type

This code table holds the values that are used to categorize deferred gifts. Examples of
deferred giving types might include: annuity, bequest, pooled income fund, and trust. The
length of the Code (Key) is restricted to 10 characters, and this code table is applicable to
Advancement.

The Type field is populated by this code table.

Example of the field location in the system: Deferred window of the Donor Processing
Workflow.

Code values entered here are stored in the Code_DeferredType table.

3-34 PowerCAMPUS Code Tables 8.1 June 2012

User Guide
Code Table Descriptions
 Degree

The Degree column is used in the People table to define degrees already obtained, as well
as degrees being pursued by students. All degrees offered by the institution should be
listed. Examples of degrees might include: Associates (AA), Bachelor of Arts (BA), and
Masters of Science (MS).

Some institutions require a way to track home and sending schools and related academic
information in the event that a student is studying abroad. This feature is available on the
Home/Sending School window. On this window, degrees will display in a drop down list
box labeled Region. Therefore, if you will be using this feature, you may want to add
some code values for international study program regions to the Degree code table. You
can then select these on the Application window when a student applies for an
international study program.

The Degree Type field allows you to determine if this degree is a Major, Minor,
Concentration or Other.

The Sort Order field allows you to determine the order in which majors, minors and/or
concentrations should display for SEVIS reporting purposes. The length of the Code
(Key) is restricted to 6 characters, and this code table is applicable to Academic Records,
Admissions, and Advancement.

Note
The Sort Order field allows the system to identify which major should be
reported to SEVIS, in addition to the primary academic record, and which
minors should be reported to SEVIS. 

Tip
(Future) Additionally, the Sort Order will be used to sort majors, minors
and/or concentrations for viewing and reporting purposes within
PowerCAMPUS. 

The Degree, Degree (view only), and Region fields are populated by this code table.

Example of the fields location in the system:

• Degree: Inquiry window of the Inquiries Workflow; Application window of the
Applicants Workflow; Source window of the Inquiries Workflow and the
Applicants Workflow; Target window of the Sources Workflow; Academic window
of the Students Workflow, the Academic Plan Workflow, and the Registration
Workflow; Catalog window of the Catalog Workflow; Others Allowed window of
the Catalog Workflow and the Sections Workflow; Education window of any
people-related workflow (including Registration and Transcripts); Honors window
of the Transcripts Workflow; Degree Requirement setup and Copy to New Matric
Year/Term processes of the Degree Requirement Setup Workflow; Change Plan
window of the Academic Plan Workflow.
• Degree (view only): Academic window of the People Billing Workflow.

June 2012 PowerCAMPUS Code Tables 8.1 3-35

User Guide
Code Table Descriptions
 • Region: Home/Sending School window of the Applicants Workflow and the
Students Workflow.

Code values entered here are stored in the Code_Degree table.

Department

Under each college, individual departments may be defined. Department codes can be
associated with courses and faculty. Examples of departments might include: English,
Mathematics, French, and History. The length of the Code (Key) is restricted to 10
characters, and this code table is applicable to Academic Records, Admissions, and
Advancement.

The Department field is populated by this code table.

Example of the field location in the system: Inquiry window of the Inquiries
Workflow; Application window of the Applicants Workflow; Target window of the
Sources Workflow; Academic window of the Registration Workflow; Catalog window
of the Catalog Workflow; Others Allowed window of the Catalog Workflow and the
Sections Workflow.

Code values entered here are stored in the Code_Department table.

Disability

Information regarding specific disabilities or challenges faced by inquiries, alumni,

applicants, donors, students, or faculty is maintained in this code table. Examples of
disabilities might include: vision impaired, hearing impaired, and wheelchair bound. The
length of the Code (Key) is restricted to 6 characters, and this code table is applicable to
Academic Records, Admissions, and Advancement.

The Disability field is populated by this code table.

Example of the field location in the system: Disability window of any people-related
workflow.

Code values entered here are stored in the Code_Disability table.

Disability special requirements

Special requirements for those with a disability may be listed in this code table. Examples
of special requirements might include: wheelchair, ramp required, and special parking
required. The length of the Code (Key) is restricted to 6 characters, and this code table is
applicable to Academic Records, Admissions, and Advancement.

3-36 PowerCAMPUS Code Tables 8.1 June 2012

User Guide
Code Table Descriptions
 If a person is listed with a disability, a special requirement must be entered. You may want
to set up a requirement of none in case no special requirement is necessary for a particular
disability.

The Special Requirements field is populated by this code table.

Example of the field location in the system: Disability window of any people-related
workflow.

Code values entered here are stored in the Code_DisableReq table.

Discipline

Disciplines are used in the Academic Plan Workflow. They facilitate the process of
building degree requirements, by grouping classifications of courses together, and can be
used as a tool for quick assignment of classifications. An example of a discipline is
Humanities. Its associated classifications could be Fine Arts, English, and History. A Print
Order should be assigned to each code value for use in the academic plan reports. For
more information, see Degree Requirement Setup in Academic Plan. The length of the
Code (Key) is restricted to 10 characters, and this code table is applicable to Academic
Records.

The Discipline field is populated by this code table.

Example of the field location in the system: Discipline setup process of the Degree
Requirement Setup Workflow; Degree Requirement Disciplines drill down, available
from the Degree Requirement setup process of the Degree Requirement Setup
Workflow; Disciplines drill down, available from the Customize window of the
Academic Plan Workflow.

Code values entered here are stored in the Code_Discipline table.

Discount type

This code table tracks the types of discounts offered by your institution. Examples of
discount types might include: employee, marketing event, and college fair. The length of
the Code (Key) is restricted to 10 characters, and this code table is applicable to Academic
Records, Admissions, and Billing.

Tip
The code value AFFIL is system-defined. If AFFIL is selected as the
Discount Type on the Main window of the Discounts Workflow, you must
enter an Affiliation for your discount. 

The Discount Type field is populated by this code table.

Example of the field location in the system: Main window of the Discounts Workflow.

June 2012 PowerCAMPUS Code Tables 8.1 3-37

User Guide
Code Table Descriptions
 Code values entered here are stored in the Code_DiscountType table.

Donor index

This code table allows you to track the possible level of giving for a donor. Examples of
donor indexes might include: top prospect, second tier, and unrated. The length of the
Code (Key) is restricted to 10 characters, and this code table is applicable to
Advancement.

The Donor Index field is populated by this code table.

Example of the field location in the system: Solicitor Information window of the
Alumni Workflow, the People Workflow and the Organizations Workflow in the
Advancement Setflow only.

Code values entered here are stored in the Code_DonorIndex table.

Donor status

This code table holds the values that indicate a donor’s classification. This code table is
defined by the system and cannot be modified. The system-defined donor status values
are: Active, Inactive, Lybunt (gave Last Year But Not This year), and Sybunt (gave Some
Year But Not This year). The length of the Code (Key) is restricted to 10 characters, and
this code table is applicable to Advancement.

The Classification (view only) field is populated by this code table.

Example of the field location in the system: Donor Classification Vista view; Donor
Classification Vista report.

Code values entered here are stored in the Code_DonorStatus table.

Dorm plan

This code table defines the housing or dormitory plans offered by your institution. This
information will link to the Billing assessment processes, so that the appropriate housing
charges may be applied to the student's account. Examples of dorm plans might include:
single, double, and suite. The length of the Code (Key) is restricted to 4 characters, and
this code table is applicable to Academic Records, Admissions, Billing, and Cash
Receipts.

The Dorm Plan field is populated by this code table.

Example of the field location in the system: Residency window of the Applicants
Workflow and the Students Workflow.

3-38 PowerCAMPUS Code Tables 8.1 June 2012

User Guide
Code Table Descriptions
 Code values entered here are stored in the Code_DormPlan table.

Drop reason

This code table tracks the reasons a student may have dropped a course. Examples of drop
reasons might include: personal reasons, course overload, and schedule conflict. The
length of the Code (Key) is restricted to 10 characters, and this code table is applicable to
Academic Records.

Tip
The code value Cancel is system-defined. This value is defaulted into the
TranscriptMarketing table as the drop reason when the status of a course
section is changed from Active to Cancel. 

The Drop Reason, and Reason fields are populated by this code table.

Example of the fields location in the system:

• Drop Reason: Drop Course Process of the Registration Processing Workflow;
Student Withdrawal Process of the Registration Processing Workflow.
• Reason: Registration window of the Registration Workflow.

Code values entered here are stored in the Code_DropReason table.

Economic rating

This code table allows you to track different economic ratings of students for state or
federal reporting. These ratings could describe the combined family income of the student
or the student's own income, if independent. Examples of economic ratings might include:
<$30,000, $30,001-$50,000, and $50,001-$70,000. The length of the Code (Key) is
restricted to 6 characters, and this code table is applicable to Academic Records,
Admissions, Billing, and Cash Receipts.

The Economic Rating field is populated by this code table.

Example of the field location in the system: Financials window of the Applicants
Workflow, the Students Workflow and the Registration Workflow.

Code values entered here are stored in the Code_EconomicRate table.

Enrollment status

This code table is used to track changes in status that a student may have during his time at
your institution. Examples of enrollment statuses might include: enrolled, withdrawn,
leave of absence, and graduated. Any of these may be set up to require a separation date by

June 2012 PowerCAMPUS Code Tables 8.1 3-39

User Guide
Code Table Descriptions
 selecting the Require a Separation Date check box. The length of the Code (Key) is
restricted to 4 characters, and this code table is applicable to Academic Records.

The SEVIS Termination Reason field allows you to link an enrollment status with the
corresponding termination reason recognized by SEVIS. The following termination
reasons are recognized by SEVIS for reporting: Absent from Country for Five Months,
Change of Nonimmigrant Classification, Cost Exceeds Resources, Death, Denied
Transfer, Expulsion, Extension Denied, Failure to Enroll, Otherwise Failing to Maintain
Status, Suspension, Transfer Student No Show, Unauthorized Drop Below Full Course of
Study, Unauthorized Drop Below Full Course Time Exchange, and Unauthorized
Employment.

The Enrolled Status, Enrollment Status (view only), Withdrawal Reason, and
PowerCAMPUS Value (view only) fields are populated by this code table.

Example of the fields location in the system:

• Enrolled Status: Grade Values setup: Academic window of the Students Workflow,
the Academic Plan Workflow, and the Registration Workflow; Application window
of the Applicants Workflow.
• Enrollment Status (view only): Academic window of the People Billing Workflow;
View Headcount and View State/High School Vista views; Enrollment Vista
reports.
• Withdrawal Reason: Student Withdrawal Process of the Registration Processing
Workflow.
• PowerCAMPUS Value (view only): NSC Processing process of the Registration
Processing Workflow (these values can be mapped to NSC values here).

Code values entered here are stored in the Code_Enrollment table.

Ethnicity

This code table holds the values for any ethnicity information that will be tracked on the
system. Examples of ethnicity might include: American Indian, Caucasian, Asian and
Pacific Islander. The length of the Code (Key) is restricted to 6 characters, and this code
table is applicable to Academic Records, Admissions, and Advancement.

The Ethnicity, and Ethnic fields are populated by this code table.

Example of the fields location in the system:

• Ethnicity: Name window of any people-related workflow (excluding Inquiries but
including Registration, Transcripts, People Billing); Demographics window of the
Inquiries Workflow.
• Ethnic: Demographics window of the Applicants Workflow and the Students
Workflow.

3-40 PowerCAMPUS Code Tables 8.1 June 2012

User Guide
Code Table Descriptions
 Code values entered here are stored in the Code_Ethnicity table.

Event classification

Classifications are used in the Academic Plan Workflow. They facilitate the process of
building degree requirements, by grouping like courses together, and can be used as a tool
for quick assignment of courses. An example of an event classification is Fine Arts. Its
associated courses could be courses from the Art, Music, and Theater departments. A Print
Order should be assigned to each code value for use in the academic plan reports. For
more information, see Degree Requirement Setup in Academic Plan. The length of the
Code (Key) is restricted to 10 characters, and this code table is applicable to Academic
Records.

The Classification field is populated by this code table.

Example of the field location in the system: Catalog Classification setup process of
the Degree Requirement Setup Workflow; Discipline Classifications drill down,
available from the Discipline setup process of the Degree Requirement Setup
Workflow; Degree Requirement Classifications drill down, available from the Degree
Requirement setup process of the Degree Requirement Setup Workflow;
Classifications drill down, available from the Disciplines drill down on the Customize
window of the Academic Plan Workflow.

Code values entered here are stored in the Code_EventClass table.

Event sub type

The information for each course offered at your institution is stored in the Event tables.
These courses may be broken down into subtypes. Examples of event subtypes might
include: lectures, labs, workshops, and recitations. A Serial ID may be assigned to each
subtype. A Sort Order may also be assigned to each subtype to indicate how multiple
subtypes within the event will sort on views and reports. The length of the Code (Key) is
restricted to 4 characters, and this code table is applicable to Academic Records.

The Sub Type, Sub Type (view only), and Course Sub Type fields are populated by this
code table.

Example of the fields location in the system:

• Sub Type: Subtype, Subtype Description, Credits, Corequisites, Cross Tally, Fees,
Others Allowed, Personnel, Schedule, and Session windows of the Catalog
Workflow; Section window of the Sections Workflow; Registration window of the
Registration Workflow; Block Registration process of the Registration Processing
Workflow; Add and Transfer windows of the Transcripts Workflow; Transfer
Policy window of the Transfer Policy Workflow; Customize window of the
Academic Plan Workflow (this field is at the Courses level and drilling down is
required to locate it); Catalog Classification, Discipline, and Degree Requirement

June 2012 PowerCAMPUS Code Tables 8.1 3-41

User Guide
Code Table Descriptions
 setup processes of the Degree Requirement Setup Workflow (this field is at the
Courses level and drilling down is required to locate it).
• Sub Type (view only): Drop Course Process, Student Withdrawal Process and
Prerequisite Check process of the Registration Processing Workflow; Transcripts
window of the Transcripts Workflow; Detail window of the Transfer Policy
Workflow; all windows of the Sections Workflow.
• Course Sub Type: Attributes and Prerequisites windows of the Catalog Workflow.

Code values entered here are stored in the Code_EventSubType table.

Event type

The information for each course offered at your institution is stored in the Event tables.
Each course can be classified as a particular type, although this categorization may
currently be done more efficiently using other PowerCAMPUS fields. By coding Test as
an event type, however, some institutions use this code table to track and print tests as
courses on their transcripts. Examples of event types might include: course, test, and
seminar. The length of the Code (Key) is restricted to 4 characters, and this code table is
applicable to Academic Records.

The Type, and Type (view only) fields are populated by this code table.

Example of the fields location in the system:

• Type: Catalog window of the Catalog Workflow; Section window of the Sections
Workflow; Detail window of the Registration Workflow; Add window of the
Transcripts Workflow.
• Sub Type (view only): Prerequisite Check process of the Registration Processing
Workflow.

Code values entered here are stored in the Code_EventType table.

FASB type

This code table is used to indicate the two pledge classifications as required by the
Financial Accounting Standards Board (FASB) Statement No. 116. This code table is
defined by the system and cannot be modified. The system-defined FASB type values are:
Conditional and Unconditional. The length of the Code (Key) is restricted to 10
characters, and this code table is applicable to Advancement.

The FASB Type field is populated by this code table.

Example of the field location in the system: Pledges window of the Donor Processing
Workflow; Batch Gift and Pledge Defaults window of the Donor Processing
Workflow (this field is available for entry only when working with pledges).

3-42 PowerCAMPUS Code Tables 8.1 June 2012

User Guide
Code Table Descriptions
 Code values entered here are stored in the Code_FASBType table.

Finance type

This code table is used to track different types of financial information. This code table is
defined by the system and cannot be modified, with the exception of one field. The
system-defined finance type values are: Dependent Expense, Employment Funds, Living
Expense, Other Expense, Other Funds, Personal Funds, School Funds, and Tuition
Expense.

The Finance Category field determines the category to which the finance type belongs.
The values available from this drop down list box are defined by SEVIS and cannot be
modified. The finance category values are: Fund and Expense.

The Default Amount field allows you to enter the default amount for each finance type.
The amount can be changed on each international student’s or exchange visitor's record.
This is the only field that can be modified in this code table.

The Description required for SEVIS check box indicates that further descriptions of
specific finance types will be required. The Description field defaults as required for
finance types of Other Expense, School Funds and Other Funds.

The System Defined check box indicates whether the selected code value is defined by the
system.

The length of the Code (Key) is restricted to 10 characters, and this code table is
applicable to Academic Records, and Admissions.

The Finance Type field is populated by this code table.

Example of the field location in the system: Financial Information drill down on the
Government window of the People Workflow, Inquiries Workflow, Applicants
Workflow, Faculty Workflow, Students Workflow and Registration Workflow.

Code values entered here are stored in the Code_FinancialType table.

Fiscal period
At different points throughout the system you will be prompted for the fiscal year or
period to be used for charge or credits. Examples of fiscal periods might include: 01, 02,
January, and February. In this code table, you can set up your fiscal periods, assign them a
unique order within the Fiscal Year, and select a Month from the drop down list box. This
allows PowerCAMPUS to map the period to the academic calendar. The length of the
Code (Key) is restricted to 4 characters, and this code table is applicable to Billing, and
Cash Receipts.

The Fiscal Period, and Fiscal Period (view only) fields are populated by this code table.

June 2012 PowerCAMPUS Code Tables 8.1 3-43

User Guide
Code Table Descriptions
 Example of the fields location in the system:
• Fiscal Period: Post Batch window of the Donor Processing Workflow; Posting to
the General Ledger Journal process of the Billing Processing Workflow.
• Fiscal Period (view only): History window of the People Billing Workflow,
Organization Billing Workflow and Registration Workflow; Posted Information
drill down, available from the Gifts and Pledges windows of the Donor Processing
Workflow; Posting drill down, available from several windows of the People
Billing Workflow, Organization Billing Workflow, Cash Receipts Workflow, and
Registration Workflow.

Code values entered here are stored in the Code_FiscalPeriod table.

Food plan
This code table defines the different meal plans offered by your institution. This
information will link to the Billing assessment processes, so that the appropriate food plan
charges may be applied to the student’s account. Examples of food plans might include: all
meals, dinners only, and lunches or dinners. The length of the Code (Key) is restricted to 4
characters, and this code table is applicable to Academic Records, Admissions, Billing,
and Cash Receipts.

The Food Plan field is populated by this code table.

Example of the field location in the system: Residency window of the Applicants
Workflow and the Students Workflow.

Code values entered here are stored in the Code_FoodPlan table.

Full/Part time flag

In this code table, all code values used to define full or part-time status should be entered.
Examples of full/part time flags might include: full-time, part-time, and half-time. Each
department can establish their own requirements for full-time status versus part-time
status in the Student Coding setup, located under Tools: Setup in the Academic Records
Setflow. The Full/Part Time field is automatically updated at registration based upon these
requirements. The length of the Code (Key) is restricted to 4 characters, and this code
table is applicable to Academic Records, and Admissions.

The Full/Part, Full/Part Time, Full/Part Time Status (view only), and
PowerCAMPUS Value (view only) fields are populated by this code table.

Example of the fields location in the system:

• Full/Part: Inquiry window of the Inquiries Workflow; Application window of the
Applicants Workflow; Academic window of the Registration Workflow.

3-44 PowerCAMPUS Code Tables 8.1 June 2012

User Guide
Code Table Descriptions
 • Full/Part Time: Target window of the Sources Workflow.
• Full/Part Time Status (view only): View Headcount and View State/High School
Vista views.
• PowerCAMPUS Value (view only): NSC Processing process of the Registration
Processing Workflow (these values can be mapped to NSC values here).

Code values entered here are stored in the Code_FullPartFlag table.

Fund type

This code table is used to track different types of exchange visitor fund types. This code
table is defined by the system and cannot be modified. The system-defined fund type
values are: Binational Comm Funds, EV Government Funds, Government Org 1 Funds,
Government Org 2 Funds, International Org 1 Funds, International Org 2 Funds, Other
Organization Funds, Personal Funds, and Program Sponsor Funds.

Associated organization codes will be required for specific fund types. The Organization
field on the Funding Information drill down on the Exchange Visitor window defaults as
required for the fund types of Government Org 1 Funds, Government Org 2 Funds,
International Org 1 Funds, and International Org 2 Funds.

The System Defined check box indicates whether the selected code value is defined by
the system. The length of the Code (Key) is restricted to 10 characters, and this code table
is applicable to Academic Records, and Admissions.

The Fund Type field is populated by this code table.

Example of the field location in the system: Funding Information drill down on the
Exchange Visitor window of the People Workflow, Inquiries Workflow, Applicants
Workflow, Faculty Workflow, Students Workflow and Registration Workflow.

Code values entered here are stored in the Code_FundType table.

Funding interest

This code table tracks a constituent’s areas of giving interest. Examples of funding
interests might include: athletics, museum, and theater. The length of the Code (Key) is
restricted to 10 characters, and this code table is applicable to Advancement.

The Funding Interest, and Funding Interest (view only) fields are populated by this
code table.

June 2012 PowerCAMPUS Code Tables 8.1 3-45

User Guide
Code Table Descriptions
 Example of the fields location in the system:
• Funding Interest: Prospect Rating and Solicitor Information windows of the
Alumni Workflow, the People Workflow and the Organizations Workflow in the
Advancement Setflow only.
• Funding Interest (view only): Deferred window of the Donor Processing Workflow.

Code values entered here are stored in the Code_FundingInterest table.

General education

This code table defines the general education requirements that a course can satisfy. It can
be used for sorting purposes on reports. Examples of general education requirements
might include: Liberal Arts, Business, and Sciences. The length of the Code (Key) is
restricted to 10 characters, and this code table is applicable to Academic Records.

Tip
General education is not currently being used by the academic plan. 

The General Ed field is populated by this code table.

Example of the field location in the system: Catalog window of the Catalog
Workflow; Section window of the Sections Workflow.

Code values entered here are stored in the Code_GeneralEd table.

Gift allocation

This code table tracks general gift and pledge designations. Examples of gift allocations
might include: capital, endowment, and operating. The length of the Code (Key) is
restricted to 10 characters, and this code table is applicable to Advancement.

Note
Because Allocation is available for selection as the Gift Club Report in the
Gift Club Report setup, located under Tools: Setup in the Advancement
Setflow, you must not create a code value of Overall in this code table.
Overall is specifically used as the code value for the overall gift club in the
Gift Club Report code table. If new code values are created in this code
table, the Gift Club Report setup has already been completed and
Allocation has been selected as the Gift Club Report in the Gift Club
Report setup, the new code value will automatically be created in the
GiftClubReport table. However, you will need to set the Track Detail Gift
Club and Include in Overall Gift Club fields appropriately. 

The Allocation field is populated by this code table.

Example of the field location in the system: Campaigns window of the Donor
Processing Workflow (this field is available on the Campaign Entry window at the

3-46 PowerCAMPUS Code Tables 8.1 June 2012

User Guide
Code Table Descriptions
 Projects level); Batch Gift and Pledge Defaults window of the Donor Processing
Workflow; Details window and its drill down, available by selecting the Show Detail
button on either the Gifts window or the Pledges window of the Donor Processing
Workflow.

Code values entered here are stored in the Code_GiftAllocation table.

Gift appeal
This code table holds the values that describe fundraising appeals. Examples of gift
appeals might include: library, reunion, and spring mailing. The length of the Code (Key)
is restricted to 10 characters, and this code table is applicable to Advancement.

Note
Because Appeal is available for selection as the Gift Club Report in the
Gift Club Report setup, located under Tools: Setup in the Advancement
Setflow, you must not create a code value of Overall in this code table.
Overall is specifically used as the code value for the overall gift club in the
Gift Club Report code table. If new code values are created in this code
table, the Gift Club Report setup has already been completed and Appeal
has been selected as the Gift Club Report in the Gift Club Report setup,
the new code value will automatically be created in the GiftClubReport
table. However, you will need to set the Track Detail Gift Club and Include
in Overall Gift Club fields appropriately. 

The Appeal field is populated by this code table.

Example of the field location in the system: Campaigns window of the Donor
Processing Workflow (this field is available on the Campaign Entry window at the
Appeals and Projects levels); Batch Gift and Pledge Defaults window of the Donor
Processing Workflow; Details window and its drill down, available by selecting the
Show Detail button on either the Gifts window or the Pledges window of the Donor
Processing Workflow.

Code values entered here are stored in the Code_GiftAppeal table.

Gift benefit type

This code table holds the values that specify benefits received in exchange for a gift.
Examples of gift benefit types might include: mug, sticker, and sweatshirt. The length of
the Code (Key) is restricted to 10 characters, and this code table is applicable to
Advancement.

The Benefit Type field is populated by this code table.

Example of the field location in the system: Batch Gift and Pledge Defaults window
of the Donor Processing Workflow; Details window and its drill down, available by

June 2012 PowerCAMPUS Code Tables 8.1 3-47

User Guide
Code Table Descriptions
 selecting the Show Detail button on either the Gifts window or the Pledges window of
the Donor Processing Workflow.

Code values entered here are stored in the Code_GiftBenefitType table.

Gift campaign

This code table tracks fundraising campaigns. Examples of gift campaigns might include:
capital, membership, and reunion. The All campaign will default as one of your values.
The code value is system-defined and cannot be modified. The length of the Code (Key) is
restricted to 10 characters, and this code table is applicable to Advancement.

Note
The All code value is strictly used by the Solicitor Information window in
the event that you are not currently linking solicitors to campaigns on the
Campaigns tab in Donor Processing. The All campaign allows solicitors to
still be assigned to donors or prospects on the Solicitor Information
window since the Campaign field is a required field on the window. For
more information, see Solicitor Information in People/Organizations. 

The Campaign field is populated by this code table.

Example of the field location in the system: Campaigns window of the Donor
Processing Workflow (this field is available on the Campaign Entry window at the
Campaigns level); Batch Gift and Pledge Defaults window of the Donor Processing
Workflow; Details window and its drill down, available by selecting the Show Detail
button on either the Gifts window or the Pledges window of the Donor Processing
Workflow.

Code values entered here are stored in the Code_GiftCampaign table.

Gift club

This code table holds the values for all of the gift clubs offered at your institution.

Gifts clubs can be set up specifically for people, specifically for organizations or for both
people and organizations. Whenever a new gift club is entered, select People,
Organizations or Both from the drop down list box. Examples of gift clubs might include:
Century, Dean’s, and Gold. The length of the Code (Key) is restricted to 10 characters, and
this code table is applicable to Advancement.

Tip
A code value may not be changed from both to People or to
Organizations, if one or more people and organizations have already
been assigned that code table value. For example, if Club A is flagged as
Both and one person and one organization have been assigned to Club
A, you will not be able to change Club A to be only for people.
Additionally, if you attempt to delete a gift club code value directly in the

3-48 PowerCAMPUS Code Tables 8.1 June 2012

User Guide
Code Table Descriptions
 database using MS SQL Server's Query Analyzer, you will be prevented
from doing so if one or more donors have already been assigned that
code value in the GiftClub table. 

Note
The code table may be set up with gift clubs for Both people and
organizations AND with gift clubs for People and for Organizations
separately. If gift clubs have been added or changed here, you will need
to run the Recalculate Gift Clubs process of the Record Maintenance
Workflow. For more information, see Record Maintenance in Record
Maintenance. 

The Club Level field is populated by this code table.

Example of the field location in the system: Gift Club window of the Alumni
Workflow, the People Workflow and the Organizations Workflow in the Advancement
Setflow only.

Code values entered here are stored in the Code_GiftClub table.

Gift club report

This code table tracks the various gift club reports and gift club report levels for gift clubs.
The overall (overall) gift club report will default as one of your values. The code value
overall is system-defined and cannot be modified. If you institution chooses to track detail
gift clubs, the code values for the detail gift clubs in this code table are built dynamically
by the system based upon the Gift Club Report setup, located under Tools: Setup in the
Advancement Setflow, and cannot be modified. For more information, see Setups in
Advancement. The length of the Code (Key) is restricted to 10 characters, and this code
table is applicable to Advancement.

Note
Although Overall is a system-defined code value, you do not have to track
an overall gift club. You may select ‘No’ in the Include in Overall Gift Club
field for every value in the Gift Club Report setup. This will allow you to
track only detail gift clubs. For more information, see Setups in
Advancement. 

Tip
In order to link the gift club reports with the Gift Club code table, double
click on the magnifying glass. A drill down window will display to allow
entry of the gift club report levels. The Gift Club Report Levels window
allows you to enter the values that specify donor recognition levels. Each
gift club must be assigned a Low Gift Amount and a High Gift Amount,
indicating the range of the gift amounts that will grant your donors
acceptance to each particular gift club. 

Note
Within the same gift club report, gift clubs for people or organizations only
may not have equal or overlapping low and high gift amounts with gift

June 2012 PowerCAMPUS Code Tables 8.1 3-49

User Guide
Code Table Descriptions
 clubs set up for both people and organizations. You will be given an error
message if this situation should occur. However, the low and high
amounts can overlap for gift clubs in different gift club reports. For
example, the same set of gift clubs for people can have one set of low
and high amount ranges for one gift club report and have a different set of
low and high amount ranges for another gift club report, even if the
amounts overlap. 

You may also specify whether this particular gift club is a lifetime gift club by selecting
the Lifetime check box. The type of gift club (people, organization or both) will display as
reference only.

You may add or delete gift clubs as necessary for each gift club report.

Code values entered here are stored in the Code_GiftClubRptLevels table.

The Report Level field is populated by this code table.

Example of the field location in the system: Gift Club window of the Alumni
Workflow, the People Workflow and the Organizations Workflow in the Advancement
Setflow only; Gift Club Report Level setup in the Advancement Setflow.

Code values entered here are stored in the Code_GiftClubReport table.

Gift form

This code table is used to establish the values that specify the donation’s classification and
the credit designation associated with each classification. The code values Outright and
Pledge are system-defined and cannot be modified. Other examples of gift forms might
include: deferred, in kind and pledge payment. If a record is found in the
GiftCreditDesignation table for a particular gift form, the credit designation set here will
be overridden. The length of the Code (Key) is restricted to 10 characters, and this code
table is applicable to Advancement.

A GL Account Debit and GL Account Credit must be assigned to each gift form. These
accounts will default at gift entry but may be overridden by entering a project ID on the
Details window, available by selecting the Show Detail button on the Gifts window of the
Donor Processing Workflow. For more information, see Donor Processing in
Advancement.

Tip
Depending upon whether your institution posts pledges or not, the GL
accounts entered for various gift forms will be different. 

3-50 PowerCAMPUS Code Tables 8.1 June 2012

User Guide
Code Table Descriptions
 If your institution does post pledges:
• The GL Account Debit would be a pledge receivables account (balance sheet
account) and the GL Account Credit would be a gift income account when
recording pledges.
• The GL Account Debit would be a cash account (balance sheet account) and the
GL Account Credit would be the accounts receivable account used for pledges
when recording pledge payments.
• The GL Account Debit would be a cash account (balance sheet account) and the
GL Account Credit would be a gift income account when recording outright gifts.

If your institution does not post pledges and instead makes one journal entry in the general
ledger for the amount of the outstanding pledges they are likely to receive:
• The GL Account Debit AND the GL Account Credit would be a gift income
account when recording pledges.
• The GL Account Debit would be a cash account (balance sheet account) and the
GL Account Credit would be a gift income account when recording pledge
payments.
• The GL Account Debit would be a cash account (balance sheet account) and the
GL Account Credit would be a gift income account when recording outright gifts.

A Category of deferred, in kind, match, membership, outright, payment, or pledge must be

assigned to each gift form.

Note
Each Category may only be assigned to one gift form. For example, a gift
form of Pledge would be linked to the Category of Pledge. There cannot
be any other gift form with the Category of Pledge. Consider using the
Pledge Type, Tender or Gift Type field, available on either the Pledges or
the Gifts window of the Donor Processing Workflow, to track different
types of gifts and pledges. 

A Credit Percentage must be assigned to each gift form. This is the percentage of the gift
for which the donor receives credit. For example, an individual may receive credit for
100% of an outright gift, while an organization receives credit for 0% of a matching gift.
Memberships and pledges do not receive any credit.

A Matching Donor Percentage must be assigned for any gift forms with a category of
Match. This is the percentage of the organization’s matching gift for which the individual
receives credit.

Note
Gift credit percentages can be assigned to spouses by drilling down on
the People icon. This option is not available for memberships and
pledges. 

June 2012 PowerCAMPUS Code Tables 8.1 3-51

User Guide
Code Table Descriptions
 Include Spouse indicates whether a spouse receives credit for gifts.

Note
The spouse must be entered on the Spouse drill down of the Relationship
Links window in order to receive gift credit. 

Include Deceased Spouse indicates whether a deceased spouse receives credit for gifts.
This option is not available if the Include Spouse option is set to No.

Include Separated Spouse indicates whether a separated spouse receives credit for gifts.
This option is not available if the Include Spouse option is set to No.

Donor Percentage indicates the percentage of the gift for which the donor receives credit if
the Include Spouse option is set to Yes.

Spouse Percentage indicates the percentage of the gift for which the spouse receives credit
if the Include Spouse option is set to Yes. For example, if the Donor Percentage is set to
50% and the Spouse Percentage is set to 50%, each will receive credit for one half of the
gift.

Note
System-assigned soft credit to multiple spouses is currently under
development. 

For more information about the using credit designations to assign soft credit, see
Understanding Soft Credit in Advancement.

The Gift Form, and Funding Interest (view only) fields are populated by this code table.

Example of the fields location in the system:

• Gift Form: Gift Designate window of the Alumni Workflow, the People Workflow
and the Organizations Workflow in the Advancement Setflow only; Gifts and
Credits windows of the Donor Processing Workflow.
• Gift Form (view only): Batch Maintenance, Batch Gift and Pledge Defaults and
Batch Entry List windows of the Donor Processing Workflow; Details window,
available by selecting the Show Detail button on either the Gifts window or the
Pledges window of the Donor Processing Workflow; Payments window, available
by selecting the Show Detail button on the Pledges window of the Donor
Processing Workflow.

Code values entered here are stored in the Code_GiftForm table.

Gift program

This code table tracks the Advancement Office’s program that is responsible for a gift or
pledge. Examples of gift programs might include: annual giving, corporate, foundation,

3-52 PowerCAMPUS Code Tables 8.1 June 2012

User Guide
Code Table Descriptions
 and young alumni. The length of the Code (Key) is restricted to 10 characters, and this
code table is applicable to Advancement.

Note
Because Program is available for selection as the Gift Club Report in the
Gift Club Report setup, located under Tools: Setup in the Advancement
Setflow, you must not create a code value of Overall in this code table.
Overall is specifically used as the code value for the overall gift club in the
Gift Club Report code table. If new code values are created in this code
table, the Gift Club Report setup has already been completed and
Program has been selected as the Gift Club Report in the Gift Club
Report setup, the new code value will automatically be created in the
GiftClubReport table. However, you will need to set the Track Detail Gift
Club and Include in Overall Gift Club fields appropriately. 

The Program, and Gift Program fields are populated by this code table.

Example of the fields location in the system:

• Program: Batch Gift and Pledge Defaults window of the Donor Processing
Workflow; Details window and its drill down, available by selecting the Show
Detail button on either the Gifts window or the Pledges window of the Donor
Processing Workflow.
• Gift Program: Online Donations page in Self-Service.

Code values entered here are stored in the Code_GiftProgram table.

Gift size

This code table tracks gift amount ranges for use in reporting. Each gift size must be
assigned a low gift value and a high gift value. Examples of gift sizes might include: less
than $100, $1,000 to $2,499, and more than $25,000. The length of the Code (Key) is
restricted to 10 characters, and this code table is applicable to Advancement.

Note
If the ranges overlap, the Giving Summary by Gift Size/Constituency
report will not return data. 

The Gift Size (view only) field is populated by this code table.

Example of the field location in the system: Giving Summary by Gift Size/
Constituency report

Code values entered here are stored in the Code_GiftSize table.

June 2012 PowerCAMPUS Code Tables 8.1 3-53

User Guide
Code Table Descriptions
 Gift source

This code table tracks what prompted a gift or pledge. Examples of gift sources might
include: appeal, event, unknown and visit. The length of the Code (Key) is restricted to 10
characters, and this code table is applicable to Advancement.

The Source, Gift Source, and Gift Source (view only) fields are populated by this code
table.

Example of the fields location in the system:

• Source: Credits window of the Donor Processing Workflow; Batch Gift and Pledge
Defaults window of the Donor Processing Workflow.
• Gift Source: Gifts window of the Donor Processing Workflow.
• Gift Source (view only): Payments window, available by selecting the Show Detail
button on the Pledges window of the Donor Processing Workflow.

Code values entered here are stored in the Code_GiftSource table.

Gift tender

This code table holds the values that specify the form of payment. The code values Cash,
Check, and Creditcard are system-defined and cannot be modified. Other examples of gift
tenders might include: payroll deduction, and in kind. The length of the Code (Key) is
restricted to 10 characters, and this code table is applicable to Advancement.

The Tender, Tender (view only), and Gift Tender (view only) fields are populated by
this code table.

Example of the fields location in the system:

• Tender: Batch Gift and Pledge Defaults window of the Donor Processing
Workflow; Gifts and Credits windows of the Donor Processing Workflow.
• Tender (view only): Batch Entry List window of the Donor Processing Workflow.
• Gift Tender (view only): Payments window, available by selecting the Show Detail
button on the Pledges window of the Donor Processing Workflow.

Code values entered here are stored in the Code_GiftTender table.

Gift test

This code table holds the values that track which mailing source generated a response.
Examples of gift tests might include: catalog, chamber of commerce, and purchase. The
length of the Code (Key) is restricted to 10 characters, and this code table is applicable to
Advancement.

3-54 PowerCAMPUS Code Tables 8.1 June 2012

User Guide
Code Table Descriptions
 The Market Test field is populated by this code table.

Example of the field location in the system: Batch Gift and Pledge Defaults window
of the Donor Processing Workflow.

Code values entered here are stored in the Code_GiftTest table.

Gift type
This code table tracks the general use of a gift. Examples of gift types might include:
restricted and unrestricted. The length of the Code (Key) is restricted to 10 characters, and
this code table is applicable to Advancement.

Note
Because Gift Type is available for selection as the Gift Club Report in the
Gift Club Report setup, located under Tools: Setup in the Advancement
Setflow, you must not create a code value of Overall in this code table.
Overall is specifically used as the code value for the overall gift club in the
Gift Club Report code table. If new code values are created in this code
table, the Gift Club Report setup has already been completed and
Program has been selected as the Gift Club Report in the Gift Club
Report setup, the new code value will automatically be created in the
GiftClubReport table. However, you will need to set the Track Detail Gift
Club and Include in Overall Gift Club fields appropriately. 

The Type, and Gift Type fields are populated by this code table.

Example of the fields location in the system:

• Type: In Kind window of the Donor Processing Workflow.
• Gift Type: Batch Gift and Pledge Defaults window of the Donor Processing
Workflow; Details window and its drill down, available by selecting the Show
Detail button on either the Gifts window or the Pledges window of the Donor
Processing Workflow.

Code values entered here are stored in the Code_GiftType table.

Give probable
This code table allows you to track the probability that a prospect will donate. Examples
of giving probabilities might include: high, medium, and low. The length of the Code
(Key) is restricted to 10 characters, and this code table is applicable to Advancement.

The Giving Probability field is populated by this code table.

Example of the field location in the system: Prospect Rating window of the Alumni
Workflow, the People Workflow and the Organizations Workflow in the Advancement
Setflow only.

June 2012 PowerCAMPUS Code Tables 8.1 3-55

User Guide
Code Table Descriptions
 Code values entered here are stored in the Code_GiveProbable table.

Government note type

This code table is used to track different types of governmental notes relating to SEVIS.
This code table is defined by the system and cannot be modified. The system-defined
government notes type values are: Amend Program Remarks, Approval Failure
Comments, Complete Program Remarks, Conclude Program Comments, Defer Program
Remarks, Dependent End Status Reason, Disciplinary Action Explanation, Drop Below
Fulltime Remarks, End Program Remarks, EV Termination Remarks, Exchange Visitor
Remarks, Extend Program Comments, Extend Program Remarks, Funding Remarks,
Infraction Comments, Port of Entry Remarks, Reprint Reason, Subject Remarks,
Terminate Dependent Comments, and Terminate Student Remarks. The length of the Code
(Key) is restricted to 10 characters, and this code table is applicable to Academic Records,
and Admissions.

The System Defined checkbox indicates whether the selected code value is defined by the
system.

The Note Type field is populated by this code table.

Example of the field location in the system: Government Notes drill down on the
Exchange Visitor and Government windows of the People Workflow, Inquiries
Workflow, Applicants Workflow, Faculty Workflow, Students Workflow and
Registration Workflow.

Code values entered here are stored in the Code_GovtNoteType table.

Grade/Grade comments change reasons

If the Grades setup, located under Tools: Setup in the Academic Records Setflow, requires
that a reason be recorded for every grade or every grade comments change (mid session or
final), use this code table to define all possible reasons for a grade or grade comment
change. Examples of grade/grade comments change reasons might include: input error,
extra work, and retest. The length of the Code (Key) is restricted to 4 characters, and this
code table is applicable to Academic Records.

The Reason (view only) field is populated by this code table.

Example of the field location in the system: Detail window of the Grades Workflow
(this field is available by selecting Grade Change History from the drop down list box
at the lower left of the window).

Code values entered here are stored in the Code_GradeChange table.

3-56 PowerCAMPUS Code Tables 8.1 June 2012

User Guide
Code Table Descriptions
 Grading activity

This code table holds the code values for the types of course activities that can be set up in
Self-Service. For more information, see the Self-Service for Faculty User Guide. The
length of the Code (Key) is restricted to 10 characters, and this code table is applicable to
Self-Service.

Selecting the Exam Activity check box allows quicker viewing/entry of grades for
activities such as quizzes, tests, midterms and finals. For more information, see the Self-
Service for Faculty User Guide.

A grading activity can have one of two system-defined values for Activity Behavior.
Default Value will default for new entries, changing this to Has Subtasks will mean that
Tasks and Criteria can be tracked for the Activity. These values are not supported beyond
PowerCAMPUS 6.32.

Code values entered here are stored in the Code_GradeActivity table.

Honors

This code table is used, when tracking education information, to designate that a degree
has been received with a certain level of honors. Examples of honors might include:
magna cum laude and cum laude. The length of the Code (Key) is restricted to 6
characters, and this code table is applicable to Academic Records, and Admissions.

Honors can also be used to enter grades ‘with honors’. Set up the different honors that can
be given with a grade. For example, students may be authorized to perform extra work for
a course to receive a grade with honors.

The Honors, Honors (view only), and Honor Code fields are populated by this code
table.

Example of the fields location in the system:

• Honors: Education window of any people-related workflow (including Transcripts
and Registration); Grades window of the Grades Workflow; Add window of the
Transcripts Workflow; Honors window of the Transcripts Workflow.
• Honors (view only): Detail window of the Grades Workflow.
• Honor Code: Graduation Honors process of the Graduation Processing Workflow.

Code values entered here are stored in the Code_Honors table.

June 2012 PowerCAMPUS Code Tables 8.1 3-57

User Guide
Code Table Descriptions
 Immunization

Various immunizations that a person is required to have prior to attending or being

employed by your institution can be tracked in this code table. Examples of
immunizations might include: MMR (Measles, Mumps, Rubella) and TB (Tuberculosis).
The length of the Code (Key) is restricted to 6 characters, and this code table is applicable
to Academic Records, and Admissions.

The Immunization field is populated by this code table.

Example of the field location in the system: Immunization window of any people-
related workflow.

Code values entered here are stored in the Code_Immune table.

Immunization status

Immunizations may be tracked with a status and a status date. Examples of immunization
statuses might include: verified and not verified. The length of the Code (Key) is restricted
to 4 characters, and this code table is applicable to Academic Records, and Admissions.

The Status field is populated by this code table.

Example of the field location in the system: Immunization window of any people-
related workflow.

Code values entered here are stored in the Code_ImmuneStatus table.

IMS institution role type

The IMS Institution Role Types as specified by the IMS Enterprise standards are stored in
this code table. This code table is defined by the system and cannot be modified. The
length of the Code (Key) is restricted to 32 characters, and this code table is applicable to
System Administrator.

The Destination Values field is populated by this code table.

Example of the field location in the system: IMS Mapping window of the Institutional
Management Systems (IMS) setup.

Code values entered here are stored in the Code_IMSInstitutionRoleType table.

3-58 PowerCAMPUS Code Tables 8.1 June 2012

User Guide
Code Table Descriptions
 Institution Type

Different types of institutions can be entered in this code table, tracked on the system, and
reported. Examples of institution types might include: colleges, community colleges, and
high schools. The length of the Code (Key) is restricted to 6 characters, and this code table
is applicable to Academic Records, and Admissions.

The Institution Type field is populated by this code table.

Example of the field location in the system: Institution window of the Institutions
Workflow.

Code values entered here are stored in the Code_InstituteType table.

Interest level

Inquiries and applicants can be associated with a specific interest level in your institution,
as well as the institution's interest in the inquiry and applicant.. Examples of interest levels
might include: low, medium, and high. Interest levels could also be coded by a numerical
scale (1,2,3,...). The length of the Code (Key) is restricted to 4 characters, and this code
table is applicable to Admissions.

The Institution Level field is populated by this code table.

Example of the field location in the system: Inquiry window of the Inquiries
Workflow and on the Interest Type and Level Link window of the Interest Type code
table.

Code values entered here are stored in the Code_InterestLevel table.

Interest type

Interest types indicate the type of interest level information being tracked. The INQUIRY
(inquiry), APPLICANT (applicant) and INST_INQ (institution’s interest in inquiry) and
INST_APP (institution's interest in applicant) interest types will default as four of your
values. The code values INQUIRY, APPLICANT, INST_INQ and INST_APP are system-
defined and cannot be modified. Additional interest types may be added if necessary. The
length of the Code (Key) is restricted to 10 characters, and this code table is applicable to
Admissions.

Note
In order to link interest levels with one or more interest types from the
Interest Level code table, single click on the Interest Level Link
drilldown. The Interest Type and Level Link window will display to allow
entry of the interest levels and their corresponding ranks. The Rank field
allows you to place an order on the Interest Levels available. 

June 2012 PowerCAMPUS Code Tables 8.1 3-59

User Guide
Code Table Descriptions
 Data entered here is stored in the InterestTypeLevels table.

The Institution Type field is populated by this code table.

Example of the field location in the system: Interest Level window of the Inquiries
Workflow and the Applicants Workflow.

Code values entered here are stored in the Code_InterestType table.

IPEDS Ethnicity

This code table holds the values for IPEDS ethnicity information tied to the IPEDS
Federal Race Categories that will be tracked in the system.

Examples of Race/Ethnicity might include: American Indian or Alaska Native/Apache,

Asian/Chinese, Black or African American/Zulu, Native Hawaiian or Other Pacific
Islander/Polynesian, and White/Scandinavian.

The Integrated Postsecondary Education Data System (IPEDS), established as the core
postsecondary education data collection program for National Center for Education
Statistics (NCES), is a single, comprehensive system designed to encompass all
institutions and educational organizations whose primary purpose is to provide
postsecondary education. IPEDS is built around a series of interrelated surveys that collect
institution-level data in areas including enrollments, program completions, faculty, staff,
and finances.

The Sub-Race Category field is populated by this code table.

Example of the field location in the system: IPEDS Ethnicity window of people-
related workflows such as Admissions/People, Admissions/Applicants, Academic
Records/People and Academic Records/Students.

Code values entered here are stored in the Code_IPEDSEthnicity table.

ISO 3166 country codes

The ISO 3166 standard country codes are stored in this code table. This code table is
defined by the system and cannot be modified. The length of the Code (Key) is restricted
to 10 characters, and this code table is applicable to System Administrator.

Note
This code table is used to populate the ISO 3166 Code field in the
Country code table. 

The ISO 3166 Country Code field is populated by this code table.

Example of the field location in the system: Country code table window.

3-60 PowerCAMPUS Code Tables 8.1 June 2012

User Guide
Code Table Descriptions
 Code values entered here are stored in the Code_ISO3166 table.

ISO 639 language codes

The language codes recognized by the ISO 639 standard are stored in this code table. This
code table is defined by the system and cannot be modified. The length of the Code (Key)
is restricted to 10 characters, and this code table is applicable to System Administrator.

The Default language of database for the export process field is populated by this code
table.

Example of the field location in the system: IMS Defaults window of the Institutional
Management Systems (IMS) setup.

Code values entered here are stored in the Code_ISO639 table.

Journal source

Use this code table to enter the different subsidiary sources that you wish to track on the
system when cash receipts, charge/credits and gifts/pledges are posted to the General
Ledger Journal using either the Posting to the General Ledger Journal process in the
Billing or Cash Receipts Setflow or the Post Batch process in the Advancement Setflow.
Examples of journal sources might include: ‘CR’ to indicate cash receipts, ‘AR’ to
indicate charge/credits, and ‘Gift’ and ‘Pledge’ to indicate gifts/pledges. The length of the
Code (Key) is restricted to 10 characters, and this code table is applicable to Billing, and
Cash Receipts.

Tip
Remember not to use any punctuation, including slashes, when creating
your code values. You may use slashes, if desired, in the Short
Desciption field. Because the Journal Source field is used in multiple
setflows, you may wish to set up the descriptions so that the journal
sources used in the Billing and Cash Receipts Setflows do not overlap
with the journal sources used in the Advancement Setflow.

For Example:

Code Value Short Description Medium Description

AR A/R Accounts Receivable

CR C/R Cash Receipt

GIFT GIFT GIFT

PLEDGE Pledge Pledge

June 2012 PowerCAMPUS Code Tables 8.1 3-61

User Guide
Code Table Descriptions
 The Journal Source, Gift Journal Source, Pledge Journal Source,
and Source (view only) fields are populated by this code table. 

Example of the fields location in the system:

• Journal Source: Posting to the General Ledger Journal process of the Billing
Processing Workflow.
• Gift Journal Source, Pledge Journal Source: Post Batch window of the Donor
Processing Workflow.
• Source (view only): Posted Information drill down, available from the Gifts and
Pledges windows of the Donor Processing Workflow; Posting drill down, available
from several windows of the People Billing Workflow, Organization Billing
Workflow, Cash Receipts Workflow, and Registration Workflow.

Code values entered here are stored in the Code_JournalSource table.

Language

The various languages spoken by inquiries, applicants, students, and faculty can be coded
here for later entry of demographics information. Examples of languages might include:
English, Spanish, and Mandarin. The length of the Code (Key) is restricted to 6 characters,
and this code table is applicable to Academic Records, Admissions, and Advancement.

The Primary Language, and Home Language fields are populated by this code table.

Example of the fields location in the system: Name window of any people-related
workflow (excluding Inquiries but including Registration, Transcripts, and People
Billing); Demographics window of the Applicants Workflow and the Students
Workflow; Demographics window of the Inquiries Workflow.

Code values entered here are stored in the Code_Language table.

Leadership

Gift club leadership positions are tracked using this code table. Examples of leadership
roles might include: agent, chair, committee and president. The length of the Code (Key)
is restricted to 10 characters, and this code table is applicable to Advancement.

The Leadership field is populated by this code table.

Example of the fields location in the system: Gift Club window of the Alumni
Workflow, the People Workflow and the Organizations Workflow in the Advancement
Setflow only.

Code values entered here are stored in the Code_Leadership table.

3-62 PowerCAMPUS Code Tables 8.1 June 2012

User Guide
Code Table Descriptions
 Mailing type

This code table is used to define the different types of mail sent out by your institution.
Examples of mailing types might include: grade and billing. Report cards and transcripts
would then be grade mailings and statements would be billing mailings. The GNRL
(general), SEVISD (SEVIS Domestic) and SEVISF (SEVIS Foreign) mailing types will
default as three of your values. The code values GNRL, SEVISD and SEVISF are system-
defined and cannot be modified. Whenever a new mailing type is entered, select People,
Organizations, or Both from the drop down list box. Upon saving, this will automatically
update every person and/or organization in the system with this new mailing type. The
length of the Code (Key) is restricted to 6 characters, and this code table is applicable to
Academic Records, Admissions, Advancement, Billing, and Cash Receipts.

Note
The SEVISD and SEVISF mailings types are used to track the domestic
and foreign addresses for international students, exchange visitors, and
their employers on the Government Information report. If you track
international student and exchange visitor information, you will need to
assign these two mailing types to the appropriate record types for people
(such as students and faculty) and for organizations (such as employers).
You may also manually assign these mailing types on an as needed
basis. For more information, see People Reports in People/
Organizations. If you do not track information on international students
and/or exchange visitors, do not assign record types to the SEVISD and/
or SEVISF mailing types. 

Tip
A drill down, accessed by double clicking on the Mailbox icon, allows you
to associate each mailing type with one or more record types. Thus, the
Record Type code table should be set up prior to this table. The GNRL
mailing type will automatically be assigned to every record type created.
For more information about the Record Type code table, see Record
Type. 

Note
Adding, updating or deleting a record type will require the system to add,
update or delete a mailing record for every person and/or organization in
the system with the specified record type. The changes to the Mailing
table will occur immediately upon the saving. 

Data entered here is stored in the RecordMailingLink table.

Every mailing type defaults with the Preferred Address. You can then change the address
type per person or organization if the mailing type should be associated with a different
address type. You can also change the recipient of each mailing type per person or
organization. For more information about the Mailings window, see People or
Organizations in People/Organizations.

The Mailing Type field is populated by this code table.

June 2012 PowerCAMPUS Code Tables 8.1 3-63

User Guide
Code Table Descriptions
 Example of the fields location in the system: Mailings window of any people-related
or organization-related workflow (including Facility Management and Registration);
Payment Plan Contract setup; NSC Processing process of the Registration Processing
Workflow; Mailing window of the report setup for the Statements report.

Code values entered here are stored in the Code_MailingType table.

Marital status
For each person entered on the system, the marital status can be maintained. This code
table allows various marital statuses to be coded for later entry of demographics
information. Examples of marital statuses might include: single, married, and divorced.
The length of the Code (Key) is restricted to 4 characters, and this code table is applicable
to Academic Records, Admissions, and Advancement.

The Marital Status, and Marital fields are populated by this code table.

Example of the fields location in the system:

• Marital Status: Name window of any people-related workflow (excluding Inquiries
but including Registration, Transcripts, and People Billing); Demographics
window of the Inquiries Workflow.
• Marital: Demographics window of the Applicants Workflow and the Students
Workflow.

Code values entered here are stored in the Code_MaritalStatus table.

Matching gift status

This code table tracks the condition of a matching gift. This code table is defined by the
system and cannot be modified. The system-defined matching gift status values are:
Canceled, Closed, Pending, Pledged, and Received. The length of the Code (Key) is
restricted to 10 characters, and this code table is applicable to Advancement.

The Match Status fiels is populated by this code table.

Example of the fields location in the system: Matches windows of the Donor
Processing Workflow.

Code values entered here are stored in the Code_MatchStatus table.

3-64 PowerCAMPUS Code Tables 8.1 June 2012

User Guide
Code Table Descriptions
 Matching gift type

This code table holds the values that specify an individual’s matching gift classification.
Examples of matching gift types might include: board member, employee, retiree, and
spouse. The length of the Code (Key) is restricted to 10 characters, and this code table is
applicable to Advancement.

The Match Type, and Type fields are populated by this code table.

Example of the fields location in the system:

• Match Type: Matching Rules window of the Alumni Workflow and the People
Workflow in the Advancement Setflow only; Matches windows of the Donor
Processing Workflow.
• Type: Matching Rules window of the Organizations Workflow in the Advancement
Setflow only.

Code values entered here are stored in the Code_MatchType table.

Media type

This code table is used to track the various types of media objects that can be uploaded in
PowerCAMPUS Self-Service. All the default values in this code table are defined by the
system and cannot be modified. However, an Institution may add new code values to suit
the needs of their constituents. The system-defined media type values are: MS Access
File, Adobe PDF, eBook, GIF Image, HTML File, JPEG Image, MPEG Audio, MPEG
Video, MS Excel Document, MS Power Point, MS Word Document, Text File, and ZIP
File. The length of the Code (Key) is restricted to 15 characters, and this code table is
applicable to PowerCAMPUS Self-Service.

Code values viewed here are stored in the Code_MediaType and MediaTypeReqAttr table.

Meeting type
The types of meetings for course sections can be tracked using this code table. Examples
of meeting types might include: classroom, off-site, and field trip. The length of the Code
(Key) is restricted to 10 characters, and this code table is applicable to Academic Records.

Select the Meeting Default checkbox for the code value that should be used when the
system automatically creates section meeting records based upon start and end dates for
the course and schedule information. Select the Meeting Value check box for any code
value(s) that should be counted towards the total number of scheduled meetings for the
course section. For more information, see Sections in Academic Records.

June 2012 PowerCAMPUS Code Tables 8.1 3-65

User Guide
Code Table Descriptions
 Tip
If you do not want to create section meeting records, do not flag any of
the meeting types as Meeting Default. The Meeting Default checkbox
can only be selected for one meeting type. 

The Meeting Type field is populated by this code table.

Example of the fields location in the system: Section Meetings window of the
Sections Workflow.

Code values entered here are stored in the Code_MeetingType table.

Method how
This code table tracks how a gift or pledge was solicited. Examples might include: mail,
personal, and phonathon. The length of the Code (Key) is restricted to 10 characters, and
this code table is applicable to Advancement.

The Method How field is populated by this code table.

Example of the fields location in the system: Details window, available by selecting
the Show Detail button on either the Gifts window or the Pledges window of the
Donor Processing Workflow.

Code values entered here are stored in the Code_MethodHow table.

Method when

This code table tracks when a gift or pledge was solicited. Examples might include: fall,
leadership, reunion, and spring. The length of the Code (Key) is restricted to 10 characters,
and this code table is applicable to Advancement.

The Method When field is populated by this code table.

Example of the fields location in the system: Details window, available by selecting
the Show Detail button on either the Gifts window or the Pledges window of the
Donor Processing Workflow.

Code values entered here are stored in the Code_MethodWhen table.

Method who

This code table tracks which constituent group was solicited. Examples might include:
alumni, corporations, and parents. The length of the Code (Key) is restricted to 10
characters, and this code table is applicable to Advancement.

3-66 PowerCAMPUS Code Tables 8.1 June 2012

User Guide
Code Table Descriptions
 The Method Who field is populated by this code table.

Example of the fields location in the system: Details window, available by selecting
the Show Detail button on either the Gifts window or the Pledges window of the
Donor Processing Workflow.

Code values entered here are stored in the Code_MethodWho table.

Money level

This code table holds values to indicate a level of assets, income and liquidity. Examples
of money levels might include: less than $25,000, $50,000 - $100,000, greater than $1
million, moderate, significant wealth, and unknown. The length of the Code (Key) is
restricted to 10 characters, and this code table is applicable to Advancement.

The Person Income Level, Person Asset Level, Person Liquidity Level, Family
Income Level, Family Asset Level, and Family Liquidity Level fields are populated by
this code table.

Example of the fields location in the system: Solicitor Information window of the
Alumni Workflow, the People Workflow and the Organizations Workflow in the
Advancement Setflow only.

Code values entered here are stored in the Code_MoneyLevel table.

NSC status codes

The NSC status codes are those codes used by the National Student Loan Clearinghouse to
indicate full/part-time status, enrollment status and release information. These codes are
used by the NSC Processing process. This code table is defined by the system and cannot
be modified, with the exception of one field. The length of the Code (Key) is restricted to
10 characters, and this code table is applicable to Academic Records.

The system-defined NSC status code values are:

F = Full Time A = Approved Leave of Absence

H = Half Time or More, But Less Than D = Deceased
Full Time
L = Less Than Half Time (But Still Y = Yes (student has requested a block on the
Enrolled) release of his data)
W = Withdrawn N = No (student has not requested a block on
the release of his data)
G = Graduated

These codes are currently in use by the NSC and are automatically added to the code table.
The NSC Mapping Type indicates whether these codes are Enrollment Status, Full/Part

June 2012 PowerCAMPUS Code Tables 8.1 3-67

User Guide
Code Table Descriptions
 Time Flag or Release Information codes. For example, the code your institution uses for
full-time would typically be set up with an NSC Mapping Type of Full/Part Time Flag
while the yes and no codes are Release Information codes. For more information about the
NSC Processing process, see Registration Processing in Academic Records.

Note
NSC Mapping Type is the only field on the window that may be modified.

The NSC Value field is populated by this code table.

Example of the fields location in the system: NSC Processing process of the
Registration Processing Workflow.

Code values entered here are stored in the Code_NSLC table.

Non Cash/In kind status

This code table tracks the condition of a non cash or in kind gift. This code table is defined
by the system and cannot be modified. The system-defined non cash/in kind status values
are: Canceled, Closed, Pending, Pledged, and Received. The length of the Code (Key) is
restricted to 10 characters, and this code table is applicable to Advancement.

The Status field is populated by this code table.

Example of the field location in the system: In Kind window of the Donor Processing
Workflow.

Code values entered here are stored in the Code_NonCashStatus table.

Note type

Note types are used to indicate different types of notes that can be entered into a person's
file. Examples of note types might include: academic advising, financial, and general. The
code value TRANDT (transcript note type) is system-defined. The length of the Code
(Key) is restricted to 6 characters, and this code table is applicable to Academic Records,
Admissions, Advancement, Billing and Cash Receipts.

Note
You do not need to create a code value for transcript-related notes. When
notes are entered on the Notes window of the Transcripts Workflow, a
note type of ‘TRANDT’ will automatically be created in the Notes table. 

The Note Type field is populated by this code table.

Example of the field location in the system: Notes window of any people-related or
organization-related workflow.

Code values entered here are stored in the Code_NoteType table.

3-68 PowerCAMPUS Code Tables 8.1 June 2012

User Guide
Code Table Descriptions
 Office

This code table is used to specify the office responsible for the entry being made. The
Office field is requested when entering information such as notes, cash receipts, or actions.
Examples of offices might include: Advising, Counseling, and Registrar. The length of the
Code (Key) is restricted to 10 characters, and this code table is applicable to Academic
Records, Admissions, Advancement, Billing and Cash Receipts.

The Office field is populated by this code table.

Example of the field location in the system: Withdrawal setup; Action window of the
Action Definition tool; Action Rule Setup tool; Checklist Setup window of the
Checklist Workflow; Notes window of any people-related or organization-related
workflow (including Academic Plan and Transcripts); Defaults window of the Cash
Receipts Workflow; main window of the ActionSchedule and Notes Office Access
Workflow.

Code values entered here are stored in the Code_Office table.

Office held

Used in conjunction with associations, the Office Held field can be used to track any office
or position held by a person within an association. Examples of offices held might include:
treasurer, vice president, and secretary. The length of the Code (Key) is restricted to 6
characters, and this code table is applicable to Academic Records, Admissions, and
Advancement.

The Office Held field is populated by this code table.

Example of the field location in the system: Associations window of any people-
related or organization-related workflow.

Code values entered here are stored in the Code_OfficeHeld table.

Organization Phone Type

Every organization phone number entered in the system must be coded with an
organization phone type. Organization Phone Type is used to define each organization’s
phone number. Examples of organization phone types might include: main office, fax, and
satellite office.

This code table populates the Phone Number window of any organization-related
workflow.

Code values entered here are stored in the Code_OrgPhoneType table.

June 2012 PowerCAMPUS Code Tables 8.1 3-69

User Guide
Code Table Descriptions
 Payment plan

This code table is used to establish the different payment plans available either internally
at your institution or through an external source. For internal plans, information such as
number of payments, payment frequency, payment start date, and any late fees to be
charged will be tracked by student. Examples of payment plans might include: quarterly
and monthly. The length of the Code (Key) is restricted to 4 characters, and this code table
is applicable to Academic Records, Admissions, Billing and Cash Receipts.

All data entered in this code table will default when a Payment Plan is selected in the
Payment Plan wizard.

The Number of Installments is the number of payments that will be created when this
payment plan is selected.

The Day of Month Payments are Due is a required field that is used to calculate the due
dates for each payment.

Select the First Installment Due day of Payment Plan Creation check box if you want
the first installment to be paid when the student is put on a payment plan.

The Installment Charge/Credit Code and Offset Charge/Credit Code must exist first in the
Charge/Credit (Code) code table in order to be selected from the drop down list box here.
The installment charge code will be used to create the installment charges and the offset
credit code will be used to create an offset to those charges.

1. Tuition and fees are assessed to the student and can be used to determine the payment
plan amount.

2. The payment plan amount is used to create installment charges that are associated
with due dates.

3. Since the installment charges are added to the student’s account, an equal offsetting
credit amount must be created so that the student’s balance is not affected.

4. You will now be able to track the payment plan receivable account as well as the
lump sum offset to the receivables.

When setting up the Installment Charge/Credit Code, the general ledger accounts should
be receivable accounts. The GL Account 1 (Debit) should be a Payment Plan Receivable
account and the GL Account 2 (Credit) should be the student receivable account. You can
set up an installment charge code for each of your student receivable accounts.

The Offset Charge/Credit Code should be a debit and credit to the same ‘fund balance’
account. The balance to this account will always be zero.

3-70 PowerCAMPUS Code Tables 8.1 June 2012

User Guide
Code Table Descriptions
 The Handling Fee Charge/Credit Code must exist first in the Charge/Credit (Code) code
table in order to be selected from the drop down list box. This handling fee, an optional
charge to the student, can be a flat amount or a percentage of the total amount.

The Late Fee Charge/Credit Code must exist first in the Charge/Credit (Code) code table
in order to be selected from the drop down list box. This late fee, assessed on charges that
are overdue, can be a flat amount or a percentage of the total amount.

Note
Although payment plan charge/credit code values of the type Cash
Receipt do not need to be set up at the time during which the payment
plan code values are being established, they must be set up prior to
entering cash receipts against the payment plan installment codes. For
these charge/credit code values, the GL Account 1 (Debit) should be a
cash account and the GL Account 2 (Credit) should be the payment plan
receivable account. 

For more information about handling and late fees, see “Charge/Credit”.

The Minimum First Installment Amount or the Minimum First Installment Percent fields
can be used to indicate whether the first installment should be an amount different from
the other installment charges. You may select one or the other. When the payment plan is
created, this will be the amount for the first installment. The total payment plan balance
amount minus this installment will be distributed to the remaining installments.

The Payment Plan, and Payment Plan (view only) fields are populated by this code
table.

Example of the fields location in the system:

• Payment Plan: Financials window of the Applicants Workflow, the Students
Workflow, the Registration Workflow and the People Billing Workflow; Payment
Plan Setup window of the Payment Plan Workflow.
• Payment Plan (view only): Balance window of the People Billing Workflow, the
Cash Receipts Workflow (By People) and the Registration Workflow (if
applicable); Pay Plan window of the People Billing Workflow and the Cash
Receipts Workflow (By People).

Code values entered here are stored in the Code_PaymentPlan table.

Permanent home

This code table is used to define the different places where an applicant may currently
reside. Examples of permanent homes might include: with parents, with father, with
mother, and with guardian. The length of the Code (Key) is restricted to 4 characters, and
this code table is applicable to Admissions.

The Permanent Home field is populated by this code table.

June 2012 PowerCAMPUS Code Tables 8.1 3-71

User Guide
Code Table Descriptions
 Example of the field location in the system: Name window of any people-related
workflow (excluding Inquiries but including Registration, Transcripts, and People
Billing); Demographics window of the Inquiries Workflow, the Applicants Workflow
and the Students Workflow.

Code values entered here are stored in the Code_PerHome table.

Person Phone Type

Every person phone number entered in the system must be coded with a person phone
type. Person Phone Type is used to define people’s phone numbers. Examples of person
phone types might include: home, local, business, summer, and campus.

This code table populates the Phone Number window of any people-related workflow.

Code values entered here are stored in the Code_PersonPhoneType table.

Picture locations

If you wish to view a person’s picture online, set up the code values that group these
picture files and enter a Picture Path and/or Picture URL for each. Various locations and/or
URL’s can be set up depending, for example, on the type of person (i.e., alumni, faculty
member, student). The length of the Code (Key) is restricted to 4 characters, and this code
table is applicable to Academic Records, Admissions, and Advancement.

Note
When specifying the path name, a back slash (\) is required at the end of
the path. The picture will not display without the ending back slash,
because the name of the folder and that of the .bmp or .jpg image file will
be combined. PowerCAMPUS will then read this combination as the File
Name and will not be able to locate it. The Picture URL field would be
used for storing pictures used in Self-Service. 

The Location field is populated by this code table.

Example of the field location in the system: Picture window of any people-related
workflow (including Registration).

Code values entered here are stored in the Code_PictureDir table.

Pledge status
This code table tracks the condition of a pledge. This code table is defined by the system
and cannot be modified. The system-defined pledge status values are: Canceled, Open,
Paid, Pending, Pledged, Reversed, and WriteOff. The length of the Code (Key) is
restricted to 10 characters, and this code table is applicable to Advancement.

3-72 PowerCAMPUS Code Tables 8.1 June 2012

User Guide
Code Table Descriptions
 When the pledge is initially saved, the system will automatically change the Pledge Status
to Pledged. When the first payment has been made against the pledge, the system will
automatically change the Pledge Status to Open and the Amount and FASB Type fields
will become unavailable. When the pledge is fully paid, the system will automatically
change the Pledge Status to Paid and the Amount, FASB Type, Pledge Term, Pledge
Status, month check boxes, Months, Payments and Send Reminders fields will become
unavailable. Prior to payments being received the Pledge Status can be manually changed
to Canceled or Pending. If the pledge has been reversed, the system will automatically
change the Pledge Status to Reversed. At any time, the Pledge Status can be manually
changed to Write Off.

The Pledge Status, and Status fields are populated by this code table.

Example of the fields location in the system:

• Pledge Status: Batch Gift and Pledge Defaults window of the Donor Processing
Workflow (this field is available for entry only when working with pledges);
Pledges window of the Donor Processing Workflow.
• Status: In Kind window of the Donor Processing Workflow.

Code values entered here are stored in the Code_PledgeStatus table.

Pledge term

The payment term for a pledge is tracked using this code table. Examples of pledge terms
might include: annual, monthly, and quarterly. The SCTAPRDTRM (Automatic Monthly
Deductions) pledge term will default as one of your values. The code value
SCTAPRDTRM is system-defined and cannot be modified. The length of the Code (Key)
is restricted to 10 characters, and this code table is applicable to Advancement.

A Number of Payments and a Number of Months can be assigned to each pledge term.
The number of payments and months will default at pledge entry but may be overridden.
Send Reminders can also be selected to default for each pledge term but may be
overridden.

If you wish to specify the exact months for each pledge term, you may select the
appropriate check box for each month in Months for Payments. The selected months will
default at pledge entry but may be overridden. For example, if you have a specific pledge
campaign in which you always take payments in April and September, you could default
these months as selected for the pledge term.

Note
Please keep in mind, if you choose to default specific months as selected
months, you will need to adjust the Start Date to match the first month
selected. In the example above, this would mean that, if you enter a
pledge for April and September in February, you may leave the Pledge
Date as a February date but will need to adjust the Start Date to a date in
April. 

June 2012 PowerCAMPUS Code Tables 8.1 3-73

User Guide
Code Table Descriptions
 The Pledge Term field is populated by this code table.

Example of the field location in the system: Batch Gift and Pledge Defaults window
of the Donor Processing Workflow (this field is available for entry only when working
with pledges); Pledges window of the Donor Processing Workflow.

Code values entered here are stored in the Code_PledgeTerm table.

Pledge type

This code table holds the values that specify the kind of pledge made. Examples of pledge
types might include: written and verbal. The SCTAPRD (Automatic Deduction) and
SCTMPRD (Manual Deduction) pledge types will default as two of your values. The code
values SCTAPRD and SCTMPRD are system-defined and cannot be modified. The length
of the Code (Key) is restricted to 10 characters, and this code table is applicable to
Advancement.

The Pledge Type field is populated by this code table.

Example of the field location in the system: Batch Gift and Pledge Defaults window
of the Donor Processing Workflow (this field is available for entry only when working
with pledges); Pledges window of the Donor Processing Workflow.

Code values entered here are stored in the Code_PledgeType table.

Population

Population is a further breakdown of people. Examples of populations might include:

regular students, high school early starts, and senior citizens. Specific populations can be
linked with specific default credit types in order to be given different credit amounts for
coursework. Credit types are set up in the Credit Type (Academic) code table and the
available options will appear in the drop down list box for Default Credit Type (for
Registration). The length of the Code (Key) is restricted to 6 characters, and this code
table is applicable to Academic Records, Admissions, and Billing.

Note
The credit type associated with each population will be used when a
student registers for classes. This credit type will override the credit type
assigned to the section. The Credit Type associated with the Population
will only default if it is an allowed credit type. Otherwise, the Credit Type
will come from the default set up for the section for which the student is
currently registering. 

The Population field is populated by this code table.

Example of the field location in the system: Inquiry window of the Inquiries
Workflow; Application window of the Applicants Workflow; Target window of the
Sources Workflow; Academic window of the Registration Workflow; Catalog window

3-74 PowerCAMPUS Code Tables 8.1 June 2012

User Guide
Code Table Descriptions
 of the Catalog Workflow; Others Allowed window of the Catalog Workflow and the
Sections Workflow.

Code values entered here are stored in the Code_Population table.

Position

This code table tracks various types of positions held by the people at your institution. The
Position field can be used to track employment information for people, contract
information for faculty, or qualification information for courses. Examples of positions
might include: salaried, adjunct math faculty, and hourly. The length of the Code (Key) is
restricted to 10 characters, and this code table is applicable to Academic Records,
Admissions, and Advancement.

The Position field is populated by this code table.

Example of the field location in the system: Employment window of any people-
related workflow; Contracts window of the Faculty Workflow.

Code values entered here are stored in the Code_Position table.

Position (activities)

This code table is used to track positions that may have been held in association with
activities. Examples of positions for the activity of National Honor Society might include:
president and treasurer. Examples of positions for the activity of baseball might include:
team captain and short stop. The length of the Code (Key) is restricted to 5 characters, and
this code table is applicable to Admissions.

The Position field is populated by this code table.

Example of the field location in the system: Activity window of the Inquiries
Workflow and the Applicants Workflow.

Code values entered here are stored in the Code_ActivityPos table.

Prefix

All prefixes that you would use for a person’s name can be set up here to avoid redundant
data entry. Examples of prefixes might include: Dr., Miss, and Mr. Prefixes can be
associated with a gender, by selecting it from the drop down list box for Default Gender
Code. The gender will then default when the prefix is entered. The length of the Code
(Key) is restricted to 15 characters, and this code table is applicable to Academic Records,
Admissions, Advancement, Billing, and Cash Receipts.

June 2012 PowerCAMPUS Code Tables 8.1 3-75

User Guide
Code Table Descriptions
 Tip
Since prefix is used throughout the system, the Code(Key) that you set up
for the prefix will default in the short, medium, and long descriptions and
cannot be changed. 

The Prefix field is populated by this code table.

Example of the field location in the system: Name window of any people-related
workflow (including Registration, Transcripts, and People Billing).

Code values entered here are stored in the Code_Prefix table.

Program
A program is used to define distinct areas of study or course offerings. Examples of
programs might include: undergraduate, post-baccalaureate, and graduate. The length of
the Code (Key) is restricted to 6 characters, and this code table is applicable to Academic
Records, Admissions, and Advancement.

FTE (Full-Time Equivalency) Credits must be entered for each program to indicate the
amount of credits necessary for full-time status within it. FTE credits are used for
reporting purposes.

The Program Type must be entered for each program to indicate whether it is an
Undergraduate, Graduate or Other type of program. This program type is used by the NSC
Processing process. For more information about this process, see Registration Processing
in Academic Records.

The Program, and Program (view only) fields are populated by this code table.

Example of the fields location in the system:

• Program: Inquiry window of the Inquiries Workflow; Application window of the
Applicants Workflow; Source window of the Inquiries Workflow and the
Applicants Workflow; Target window of the Sources Workflow; Academic window
of the Students Workflow, the Academic Plan Workflow, and the Registration
Workflow; Catalog window of the Catalog Workflow; Others Allowed window of
the Catalog Workflow and the Sections Workflow; Education window of any
people-related workflow (including Registration and Transcripts); Honors window
of the Transcripts Workflow; Degree Requirement setup and Copy to New Matric
Year/Term processes of the Degree Requirement Setup Workflow; Change Plan
window of the Academic Plan Workflow; Home/Sending School window of the
Applicants Workflow and the Students Workflow.
• Program (view only): Academic window of the People Billing Workflow.

Code values entered here are stored in the Code_Program table.

3-76 PowerCAMPUS Code Tables 8.1 June 2012

User Guide
Code Table Descriptions
 Rating

Rating is used when recording information about a scheduled action. You can rate your
contact with a person or organization for any type of action, such as an interview or phone
conversation, on your overall impression or success. Examples of ratings might include:
low, medium, and high. Ratings could also be coded by a numerical scale (1,2,3,...). The
length of the Code (Key) is restricted to 3 characters, and this code table is applicable to
Academic Records, Admissions, Advancement, Billing, and Cash Receipts.

The Rating field is populated by this code table.

Example of the field location in the system: Scheduled Actions drill down, available
from the Scheduled Actions window of any people-related or organization-related
workflow.

Code values entered here are stored in the Code_Rating table.

Rating result

This code table holds the values that indicate ratings for donors. Examples of rating results
might include: < $1000, $1 million or more, high, low, and medium. The length of the
Code (Key) is restricted to 10 characters, and this code table is applicable to
Advancement.

The Rating Result field is populated by this code table.

Example of the field location in the system: Prospect Rating window of the Alumni
Workflow, the People Workflow and the Organizations Workflow in the Advancement
Setflow only.

Code values entered here are stored in the Code_RatingResult table.

Rating type
This code table allows you to track the types of ratings for donors. Examples of rating
types might include: annual, capital, special project, and reunion. The length of the Code
(Key) is restricted to 10 characters, and this code table is applicable to Advancement.

The Rating Type field is populated by this code table.

Example of the field location in the system: Prospect Rating window of the Alumni
Workflow, the People Workflow and the Organizations Workflow in the Advancement
Setflow only.

Code values entered here are stored in the Code_RatingType table.

June 2012 PowerCAMPUS Code Tables 8.1 3-77

User Guide
Code Table Descriptions
 Reason for no contact

If a person is not to be contacted at the current address or telephone numbers, you can
indicate a reason for no contact. Examples of reasons for no contact might include:
personal request, returned address, and lost address. The length of the Code (Key) is
restricted to 4 characters, and this code table is applicable to Academic Records,
Admissions, Advancement, Billing, and Cash Receipts.

The Mail No Contact, and Do Not Call Reason fields are populated by this code table.

Example of the fields location in the system:

• Mail No Contact: Address window of any people-related or organization-related
workflow (including Facility Management, Registration, Transfer Policy,
Transcripts, People Billing, and Organization Billing).
• Do Not Call Reason: Phone Numbers window of any people-related workflow
(including Inquiries, Applicants, Students, Faculty, People, Registration, Alumni).

Code values entered here are stored in the Code_NoContact table.

Receipt print

This code table holds the values that specify how a receipt is generated. Examples might
include: manual, operator, and system. The length of the Code (Key) is restricted to 10
characters, and this code table is applicable to Advancement.

The Receipt Print field is populated by this code table.

Example of the field location in the system: Batch Gift and Pledge Defaults window
of the Donor Processing Workflow; Details window and its drill down, available by
selecting the Show Detail button on either the Gifts window or the Pledges window of
the Donor Processing Workflow.

Code values entered here are stored in the Code_ReceiptPrint table.

Record type
Record types are used to indicate different types of people and organizations. Examples of
record types might include: Corporation, Student Worker, or Foundation. The length of the
Code (Key) is restricted to 4 characters, and this code table is applicable to System
Administrator.

3-78 PowerCAMPUS Code Tables 8.1 June 2012

User Guide
Code Table Descriptions
 Defined record types are as follows:

Advisor (P) Employee (Former) (P) Prospect (B)

Advisor (Former) (P) Employer (O) Provides Students (O)
Advocate (P) Faculty (P) Publication (O)
Advocate (Former) (P) Faculty (Former) (P) Religious Institution (O)
Alumni (P) Guest (P) School (O)
Applicant (P) Inquiry (P) Signoff (P)
Continuing Education (P) Insurance Company (O) Sponsor (B)
Contact (P) Legacy (P) Student (P)
Counselor (P) Member (B) Trustee (P)
Counselor (Former) (P) Parent (P) Vendor (O)
Donor (B) Parent (Future) (P)
Employee (P) Parent (Past) (P)

Note
P means that the record type applies to people, O means that it applies to
organizations, and B means that it applies to both. 

Specific record types can be linked with specific CASE types in order to classify donors
for the Council for Advancement in Support of Education (CASE) report. CASE types are
set up in the CASE Type code table and the available options will appear in the drop down
list box for CASE Types.

The Record Type, and Select Record Types that will link to Mailing Type fields are
populated by this code table.

Example of the fields location in the system:

• Record Type: Record Type window of any people-related or organization-related
workflow.
• Select Record Types that will link to Mailing Type: Drill down on the Mailing Type
code table.

Code values entered here are stored in the Code_RecordType table.

Registration method

This code table tracks the means by which a student was registered for a particular course
section. Examples of registration methods might include: walks in, phone and mail. The
length of the Code (Key) is restricted to 15 characters, and this code table is applicable to
Academic Records, Admissions, and Billing.

Tip
The code values WEB and POWERCAMPUS are system-defined and
cannot be modified. The purpose of these values is to differentiate

June 2012 PowerCAMPUS Code Tables 8.1 3-79

User Guide
Code Table Descriptions
 between using the Online Registration page of Self-Service and using the
Registration Workflow in the Academic Records Setflow in
PowerCAMPUS to register for courses. For more information about
Online Registration, see the Self-Service for Students User Guide. 

The Registration Method field is populated by this code table.

Example of the field location in the system: Transcript Marketing/Discounts drill

down on the Registration window of the Registration Workflow.

Code values entered here are stored in the Code_RegistrationMethod table.

Registration permission status

This code table is defined by the system and cannot be modified. The registration
permission status code values are: Approved, Denied, and Waiting. The length of the Code
(Key) is restricted to 10 characters, and this code table is applicable to Academic Records.

This code table contains the registration permission statuses that Faculty use for Instructor
Permissions in Self-Service. For more information, see the Self-Service for Faculty User
Guide.

Code values entered here are stored in the Code_RegistrationPermStatus table.

Registration type

This code table tracks the type of Registration for a particular course, either ‘Traditional’
or ‘Continuing Education’. The length of the Code (Key) is restricted to 10 characters, and
this code table is applicable to Academic Records.

Tip
All of the code values in this table are system-defined and cannot be
modified. The purpose of these values is to distinguish courses as either
‘Traditional’ or ‘Continuing Education’ in order to facilitate reporting and
filtering throughout the system. 

Note
If a student registers in a particular Year/Term for courses where
Registration Type = Continuing Education then they will automatically be
assigned a Record Type of Continuing Education. 

The Registration Type field is populated by this code table.

Example of the field location in the system: Section window of the Sections
Workflow.

Code values entered here are stored in the Code_RegistrationType table.

3-80 PowerCAMPUS Code Tables 8.1 June 2012

User Guide
Code Table Descriptions
 Relationship

This code table tracks types of relationships between people in the system. Examples of
relationships might include: parent to child, spouse to spouse, and sibling to sibling. You
can link these code values by entering each as the Offset Code of the other. For example,
for the code value of Parent, the Other Relationship Code to be updated may be CHD, for
child. The length of the Code (Key) is restricted to 4 characters, and this code table is
applicable to Academic Records, Admissions, and Advancement.

To enter a relationship, the person does not have to be in the system. If the person does
have a record, the ID of the relation can be entered. When the relationship is entered for
one ID, the system will automatically create a relationship record for the other ID.

The SEVIS Relationship Type field allows you to link the relationship types with the
values recognized by SEVIS. The SEVIS Relationship Type field is defined by SEVIS and
cannot be modified. The relationship type values are: Child, Other and Spouse.

The Relationship Type field is populated by this code table.

Example of the field location in the system: Relationship Links window of any
people-related workflow.

Code values entered here are stored in the Code_Relationship table.

Release information

Release information displays at the top of every people-related window. Code values can
signify any restrictions there may be on release of information for each person. Examples
of release information types might include: limited access, no release, and authorized
personnel only. The length of the Code (Key) is restricted to 6 characters, and this code
table is applicable to Academic Records, Admissions, and Advancement.

Tip
It is recommended to create a Directory Only code value, so that you may
filter on every code value except this one when selecting the people who
should be globally excluded from online directories based upon their
release information in Self-Service. For more information, see the Self-
Service for Administrators User Guide. 

The Release Information, and Do Not Call Reason fields are populated by this code
table. Example of the fields location in the system:
• Release Information: Name window of any people-related workflow (including
Registration, Transcripts, and People Billing).
• PowerCAMPUS Value (view only): NSC Processing process of the Registration
Processing Workflow (these values can be mapped to NSC values here).

Code values entered here are stored in the Code_ReleaseInfo table.

June 2012 PowerCAMPUS Code Tables 8.1 3-81

User Guide
Code Table Descriptions
 Religion

If you wish to track the religions of any people on the system, enter the various code
values in this code table. Examples of religions might include: Hindu, Muslim, and
Protestant. The length of the Code (Key) is restricted to 4 characters, and this code table is
applicable to Academic Records, Admissions, and Advancement.

The Religion field is populated by this code table.

Example of the field location in the system: Name window of any people-related
workflow (excluding Inquiries but including Registration, Transcripts, People
Billing); Demographics window of the Inquiries Workflow, the Applicants Workflow
and the Students Workflow.

Code values entered here are stored in the Code_Religion table.

Residency months

This code table maintains all possible numbers of months of state and/or county residency
that may be recorded as part of a student’s financial record. Examples of residency months
might include: 1,2,...99. The length of the Code (Key) is restricted to 2 characters, and this
code table is applicable to Academic Records, Admissions, Billing and Cash Receipts.

The Months field is populated by this code table.

Example of the field location in the system: Financials window of the Applicants
Workflow, the Students Workflow and the Registration Workflow.

Code values entered here are stored in the Code_ResidentMonth table.

Resource

This code table holds the values that indicate the allocation of the institution or
department’s resources. Examples of resources might include: minimal, maximum, none,
50%, and 100%. The length of the Code (Key) is restricted to 10 characters, and this code
table is applicable to Advancement.

The Resource Allocation field is populated by this code table.

Example of the field location in the system: Prospect Rating window of the Alumni
Workflow, the People Workflow and the Organizations Workflow in the Advancement
Setflow only.

Code values entered here are stored in the Code_Resource table.

3-82 PowerCAMPUS Code Tables 8.1 June 2012

User Guide
Code Table Descriptions
 Response to contacts

This code table is used to track a person’s reaction to a contact from your institution.
Examples of responses to contacts might include: favorable, negative, and requested more
information. The length of the Code (Key) is restricted to 6 characters, and this code table
is applicable to Academic Records, Admissions, Advancement, Billing and Cash
Receipts.

The Response field is populated by this code table.

Example of the field location in the system: Scheduled Actions drill down, available
from the Scheduled Actions window of any people-related or organization-related
workflow.

Code values entered here are stored in the Code_Response table.

Room type

Room types are used to facilitate the scheduling of events, including courses, meetings,
office hours, etc. Examples of room types might include: classrooms, faculty offices,
lecture halls, laboratories, and conference rooms. The length of the Code (Key) is
restricted to 6 characters, and this code table is applicable to Academic Records.

The Type field is populated by this code table.

Example of the field location in the system: Room window of the Facility
Management Workflow (available by selecting Room from the drop down list box).

Code values entered here are stored in the Code_RoomType table.

SIC code level 1

This code table holds the values that indicate the Standard Industrial Classification (SIC)
division codes for organizations. Examples of Level 1 codes might include finance,
manufacturing, retail trade, and transportation. The length of the Code (Key) is restricted
to 10 characters, and this code table is applicable to Advancement.

The SIC Code Level 1 field is populated by this code table.

Example of the field location in the system: SIC Codes window of the Organizations
Workflow in the Advancement Setflow only.

Code values entered here are stored in the Code_SICCodeLevel1 table.

June 2012 PowerCAMPUS Code Tables 8.1 3-83

User Guide
Code Table Descriptions
 SIC code level 2

This code table holds the values that indicate the Standard Industrial Classification (SIC)
group codes for organizations. Examples of Level 2 codes might include banking,
brokerage services, airline, automobile, and railroad. The length of the Code (Key) is
restricted to 10 characters, and this code table is applicable to Advancement.

The SIC Code Level 2 field is populated by this code table.

Example of the field location in the system: SIC Codes window of the Organizations
Workflow in the Advancement Setflow only.

Code values entered here are stored in the Code_SICCodeLevel2 table.

Salutation type

It is necessary to set up various salutations if you wish to address a person in a letter in a

format other than that of his official name. Each office may wish to use a different
salutation in its letters. For example, the Advising Office’s salutation might be by
nickname. New salutation types default to include Prefix and Last Name but may be
changed. Examples of salutation types might include: Advising, President’s, and Dean’s.
The length of the Code (Key) is restricted to 4 characters, and this code table is applicable
to Academic Records, Admissions, and Advancement.

Note
If a salutation should only include the Nickname, you will need to
additionally select Include First Name or Include Last Name in the event
that a nickname does not exist for the person. However, the salutation will
include only the nickname if one does exist. If you select Include Last
Name, the Last Name Prefix (if any) will automatically be included. For
example, for a full name 'John Van der Horst', 'Van der' is the Last Name
Prefix for the Last Name 'Horst'.

Currently, only the advancement mailing lists provide salutation

functionality. These mailing lists join to the View Salutation and View
Salutation 2 Vista views. For more information, see Understanding
Naming Conventions in Advancement. Although the Salutation column is
available in all other mailing lists, it is currently system-defined as Prefix +
Last Name. Additionally, you cannot filter on a specific salutation type in
any mailing lists other than advancement mailing lists. 

The Type field is populated by this code table.

Example of the field location in the system: Salutations window of any people-related
workflow.

Code values entered here are stored in the Code_Salutation table.

3-84 PowerCAMPUS Code Tables 8.1 June 2012

User Guide
Code Table Descriptions
 Scholarship requirement received

This code table tracks the values for Scholarship Requirements Received. Examples of
scholarship requirement received values might include: Cancel or Hold. The code values
Not Received, Received and Waived are system-defined and cannot be modified. The
length of the Code (Key) is restricted to 10 characters, and this code table is applicable to
Academic Records, and Admissions.

The Scholarship Require field is populated by this code table.

Example of the field location in the system: Requirements drilldown of the

Scholarships Workflow for Applicants or Students.

Code values entered here are stored in the Code_ScholarReqReceived table.

Scholarship level

This code table tracks the levels for Scholarships. Examples of scholarship levels might
include: Basic, Silver and Platinum. The length of the Code (Key) is restricted to 10
characters, and this code table is applicable to Academic Records, and Admissions.

The Scholarship Level field is populated by this code table.

Example of the field location in the system: Levels window of the Scholarships
Workflow.

Code values entered here are stored in the Code_ScholarshipLevel table.

Scholarship requirements

This code table tracks the requirements for Scholarships. Examples of scholarship
requirements might include: release, signature, and authorization. The length of the Code
(Key) is restricted to 10 characters, and this code table is applicable to Academic Records,
and Admissions.

The Scholarship Requirements field is populated by this code table.

Example of the field location in the system: Requirements window of the Scholarships
Workflow.

Code values entered here are stored in the Code_ScholarshipReqs table.

June 2012 PowerCAMPUS Code Tables 8.1 3-85

User Guide
Code Table Descriptions
 Scholarship status

This code table tracks the status of Scholarships. Examples of scholarship statuses might
include: open, pending, and awarded. The statuses that are considered ‘Awarded’ must be
indicated by selecting the Awarded check box. If a scholarship record has an awarded
status, the scholarship Awarded Amount will be populated with the number from the
Applied Amount field. The length of the Code (Key) is restricted to 10 characters, and
this code table is applicable to Academic Records, and Admissions.

The Scholarship Status field is populated by this code table.

Example of the field location in the system: Scholarship window of the Scholarships
Workflow.

Code values entered here are stored in the Code_ScholarshipStatus table.

Scholarship type

This code table tracks the types of Scholarships that applicants and students can obtain.
Examples of scholarship types might include: academic, athletic and in-kind. The length
of the Code (Key) is restricted to 10 characters, and this code table is applicable to
Academic Records, and Admissions.

The Scholarship Type field is populated by this code table.

Example of the field location in the system: Scholarship window of the Scholarships
Workflow.

Code values entered here are stored in the Code_ScholarshipType table.

Screening method

This code table allows you to track methods of screening donors. Examples of screening
methods might include: Econometrics, Marts & Lundy, Peer review, and staff. The length
of the Code (Key) is restricted to 10 characters, and this code table is applicable to
Advancement.

The Screening Method field is populated by this code table.

Example of the field location in the system: Prospect Rating window of the Alumni
Workflow, the People Workflow and the Organizations Workflow in the Advancement
Setflow only.

Code values entered here are stored in the Code_ScreeningMethod table.

3-86 PowerCAMPUS Code Tables 8.1 June 2012

User Guide
Code Table Descriptions
 Section fee group

This code table holds code values for section fee groups. The code value All is system-
defined and cannot be modified. This code value is the default section fee group. These
groups can be assigned to section fees on the Fees window of the Sections Workflow. For
more information, see Sections in Academic Records.

The Rank field allows you to establish the hierarchy of the section fee groups. The All
section fee group is by default 000, indicating that every student will receive the section
fees associated with this group, if it exists on the Fees window of the Sections Workflow.

Students can fall into more than one section fee group but, in terms of assessments,
students can only meet One other section fee group in addition to the All section fee
group, if it exists on the Fees window. This is accomplished by setting up the rank in
ascending order from the most specific group to the most general group. Each Rank must
be unique and, the lower the rank is, the higher precedence it takes when determining
which section fees group should be selected during assessments.

Each student will be assessed the section fees associated with the All group, if it exists on
the Fees window, and those associated with the First additional group for which the
student meets the corresponding view, based upon the lowest rank number.

The length of the Code (Key) is restricted to 10 characters, and this code table is
applicable to Academic Records.

Tip
Because students can only meet one other section fee group in addition
to the All section fee group, you will need to carefully evaluate the section
fee groups you create and their sort orders.

Assume you have the following section fee groups and sort orders: All
000, Undergraduates 001, Graduates 002, In State 003, and Out of State
004.

Assume a course has the following section fees: Laptop Fee $5000.00
(flat) ALL, Course Fee $500.00 (per credit) In State and $600.00 (per
credit) Out of State.

If an undergraduate student registers for this course and he is also an out

of state student, then this student would not receive the out of state
course fee at all because this student meets the Undergraduate group
first.

Students may only meet one other section fee group (based upon lowest
rank) in addition to the All section fee group. So for this course, the In
State and Out of State section fee groups are more important than the
Undergraduate and Graduate section fee groups. This means you may
want to reevaluate the sort orders on your section fee groups. However,
for another course, the Undergraduate and Graduate section fee groups
may be more important than the In State and Out of State section fee

June 2012 PowerCAMPUS Code Tables 8.1 3-87

User Guide
Code Table Descriptions
 groups, so you need to evaluate your section fee groups and their sort
orders carefully. 

The Group View field allows you to select the view that corresponds with each section fee
group. The drop down list box will display all views that are stored on the database to
which PowerCAMPUS is connected. Views created using the Vista Views tool will
display a magnifying glass icon to the left of each view name. Views created using another
tool, such as Enterprise Manager or MS Access, will display with a glasses icon to the left
of each view name.

Each view contains the students who will receive the section fee(s) associated with each
section fee group on the Fees window of the Sections Workflow. The All section fee group
will not be linked to a view because all students fall into this group.

Note
Each view must contain the following columns in order to be selected for a
section fee group: People_Code_ID, Academic_Year, Academic_Term
and Academic_Session. If the selected view does not contain all of these
columns, a warning message will display. These columns can be from any
table that contains the four required columns, such as the Academic table
or the TranscriptDetail table.

Views not created using the Vista Views tool must not contain spaces or
any punctuation, because syntax errors will result either when saving the
section fee group or during the assessment process itself. 

When the section fee group is saved, a stored procedure (spAssessGroup) is automatically
created for the section fee group and view selected. There is a stored procedure called
spGenerateAssessGroup that creates spAssessGroup and will be run with each version
upgrade in order to maintain your section fee groups. This stored procedure will be called
when students are assessed.

Tip
It is recommended that you verify that the section fee group logic was
added to the spAssessGroup stored procedure. If the spAssessGroup
stored procedure does not contain a section for each section fee group,
assessment results will not be correct. If for some reason you do not see
a section for each section fee group, you may manually run
spGenerateAssessGroup in MS SQL Server’s Query Analyzer to rebuild
the spAssessGroup stored procedure. 

Note
The section fee assessment process will determine and return the groups
for which a student matches and assess only the section fees associated
with those groups. The Rank and Group View fields may not be blank;
therefore, you should identify the rank order and create the views prior to
creating the section fee groups. 

The Fee Group field is populated by this code table.

3-88 PowerCAMPUS Code Tables 8.1 June 2012

User Guide
Code Table Descriptions
 Example of the field location in the system:
• Fee Group:
• Fees window of the Sections Workflow
• Find Course Sections page in Self-Service

Code values entered here are stored in the Code_SectionFeeGroup table.

Session

Sessions should be coded if terms (semesters) are broken down into a number of different
starting and ending dates. You can use sessions to group courses that are scheduled for the
same period of time. There can be multiple sessions within a term. Examples of sessions
might include: full, first, and second. Numerical sessions could also be used. A Session
order within Term can be assigned to each session for displaying on views and reports.
The length of the Code (Key) is restricted to 10 characters, and this code table is
applicable to Academic Records, Admissions, Advancement, Billing, and Cash Receipts.

This code table populates dozens of fields throughout the PowerCAMPUS system and is
absolutely essential for storing historical data.

Tip
Session is a required field. If your institution only uses Year and Term to
define the academic year, create a generic value for session, such as ‘01’
or ‘1’. 

Code values entered here are stored in the Code_AcaSession table.

SEVIS events

This code table tracks all events that the SEVIS reporting process uses. These events
describe the different possible scenarios that may cause a person’s information or status in
the system to change and, therefore, have to be reported to the Bureau of Citizenship and
Immigration Services (BCIS). This code table is defined by the system and cannot be
modified. The system-defined values are: Authorize Drop Below Full Course - Add,
Authorize Drop Below Full Course - Cancel, Authorize Drop Below Full Course - Edit,
CPT Employment - Add, CPT Employment - Cancel, Create Student, Dependent - Add,
Dependent - Cancel, Dependent - Edit, Dependent - Reactivate, Dependent - Reprint,
Dependent - Terminate, Disciplinary Action, Edit Student Financial, Education - Level
Cancel, Education - Level Change, OffCampus Employment - Add, OffCampus
Employment - Cancel, OffCampus Employment - Edit, OPT Employment - Add, OPT
Employment - Cancel, Personal Info, Program - Cancel Extension, Program - Defer
Attendance, Program - Edit, Program - Extend, Program - Shorten, Reprint, Status -
Cancel, Status - Complete, Status - Terminate, Status - Verify and Student Registration.
The length of the Code (Key) is restricted to 10 characters, and this code table is
applicable to Academic Records, and Admissions.

June 2012 PowerCAMPUS Code Tables 8.1 3-89

User Guide
Code Table Descriptions
 The Record Status field indicates the record status for which the event is available.

The Adjudicated field indicates whether the event requires adjudication.

For detailed descriptions of each event see SEVIS Batch Processing in Admissions or
Academic Records.

The Event Type field is populated by this code table.

Example of the field location in the system: SEVIS Request Editor window of the
SEVIS Batch Processing Workflow.

Code values entered here are stored in the Code_SEVISEvents table.

Solicitor

This code table holds the values that identify Advancement Office staff members
responsible for solicitations and acknowledgements. Examples of solicitors might include:
Acknowledgement Secretary, Annual Giving Director, Director of Development, Gift
Entry Operator, Major Gifts Officer, and President. The length of the Code (Key) is
restricted to 10 characters, and this code table is applicable to Advancement.

Note
As new solicitor codes are added to the code table, they will need to be
linked to at least the All campaign on the Solicitors level of the Campaigns
tab in Donor Processing in order for solicitors to be assigned to donors/
prospects on the Solicitor Information window. For more information, see
Donor Processing in Advancement and Solicitor Information in People/
Organizations. 

Example of the fields location in the system:

• Solicitor: Solicitor Information window of the Alumni Workflow, the People
Workflow and the Organizations Workflow in the Advancement Setflow only;
Campaigns window of the Donor Processing Workflow (this field is available on
the Campaign Entry window at the Solicitors level); Batch Gift and Pledge
Defaults window of the Donor Processing Workflow; Solicitors window, available
by selecting the Show Detail button on either the Gifts window or the Pledges
window of the Donor Processing Workflow.
• Solicitor (view only): Deferred window of the Donor Processing Workflow.

Code values entered here are stored in the Code_Solicitor table.

3-90 PowerCAMPUS Code Tables 8.1 June 2012

User Guide
Code Table Descriptions
 Solicitor method

This code table tracks the method of solicitation. Examples of solicitor methods might
include: direct mail, in person, and phone. The length of the Code (Key) is restricted to 10
characters, and this code table is applicable to Advancement.

The Solicitor Method field is populated by this code table.

Example of the field location in the system: Batch Gift and Pledge Defaults window
of the Donor Processing Workflow; Solicitors window, available by selecting the
Show Detail button on either the Gifts window or the Pledges window of the Donor
Processing Workflow.

Code values entered here are stored in the Code_SolicitorMethod table.

Source

This code table is used to code the ways in which inquiries and applicants heard about
your institution. Examples of sources might include: regional college fairs, current
students, and newspaper ads in the New York Times. The length of the Code (Key) is
restricted to 10 characters, and this code table is applicable to Admissions, and Self-
Service. Each code is associated with a source type, set up in the Source Type code table.

The How did you hear about this institution?, and Source fields are populated by this
code table.

Example of the fields location in the system:

• How did you hear about this institution?: Online Application and Online Inquiry
forms in Self-Service.
• Source: Source window of the Sources Workflow.

Code values entered here are stored in the Code_Source table.

Source type

The code values entered in this code table are used to group together sources of inquiries
and applicants. Examples of source types might include: newspaper ads, radio ads, and
college fairs. The length of the Code (Key) is restricted to 4 characters, and this code table
is applicable to Admissions.

Note
Build this table prior to your Source code table because a source type can
be entered in that table. 

The Type, and Source Type fields are populated by this code table.

June 2012 PowerCAMPUS Code Tables 8.1 3-91

User Guide
Code Table Descriptions
 Example of the fields location in the system:
• Type: Source window of the Sources Workflow.
• Source Type: Source code table.

Code values entered here are stored in the Code_SourceType table.

Sponsor status
This code table is used to define the status of sponsor agreements. Examples of sponsor
statuses might include: pending, active, canceled, and closed. The statuses that are
considered to allow registration and the statuses that are considered closed must be
indicated. The length of the Code (Key) is restricted to 4 characters, and this code table is
applicable to Academic Records, Admissions, Advancement, Billing, and Cash Receipts.

Note
Only the Allow Registration OR the Closed Status checkbox can be
selected for each sponsor status. Both cannot be selected for the same
sponsor status code value; however, both may be left deselected if you
are tracking a sponsor status equating to pending.

When linking agreements to courses during registration, only those

agreements with a status that will Allow Registration can be saved. If the
status of a selected agreement is a Closed Status, you will receive a
warning upon selecting it from the Agreement search, available from the
Search pull-down menu of the Main Menu Bar. If the status of a selected
agreement has neither Allow Registration nor Closed Status selected for
it, the agreement will not be saved when linked to a course in
registration. 

The Status field is populated by this code table.

Example of the field location in the system: Sponsor Agreement window of the People
Workflow and the Organizations Workflow.

Code values entered here are stored in the Code_SponsorStatus table.

Sponsor type
This code table holds the values that are used to categorize the different types of sponsors.
Examples of sponsor types might include: agent, corporation, and foundation. The length
of the Code (Key) is restricted to 6 characters, and this code table is applicable to
Academic Records, Admissions, Advancement, Billing, and Cash Receipts.

The Type field is populated by this code table.

3-92 PowerCAMPUS Code Tables 8.1 June 2012

User Guide
Code Table Descriptions
 Example of the field location in the system: Sponsor Agreement window of the People
Workflow and the Organizations Workflow. Code values entered here are stored in the
Code_SponsorType table.

State
Enter all of the states as they are abbreviated for mailings in this code table. For example,
enter FL for Florida. The Short Description will automatically default to what is entered as
the code value and cannot be changed. This is to accommodate the merge fields State
(which prints the Long Description of the state in your letter) and City_St_Zip (a
concatenated field which prints the Short Description of the state). The length of the Code
(Key) is restricted to 4 characters, and this code table is applicable to Academic Records,
Admissions, Advancement, Billing, and Cash Receipts.

The SEVIS State Code field allows you to map the PowerCAMPUS state code value with
the corresponding codes recognized by SEVIS for reporting purposes.

The State, and Issuing State fields are populated by this code table.

Example of the fields location in the system:

• State: Address window of any people-related or organization-related workflow
(including Facility Management, Registration, Transfer Policy, Transcripts, People
Billing, and Organization Billing); Financials window of the Applicants Workflow,
the Students Workflow and the Registration Workflow.
• Issuing State: Government window of the People Workflow, Inquiries Workflow,
Applicants Workflow, Faculty Workflow, Students Workflow and Registration
Workflow.

Code values entered here are stored in the Code_State table.

Statement message

This code table allows you to establish the various messages to be printed on a statement.
Each code value refers to the message inputted in the text box for Message. The messages
may be categorized into four types, each of which can be selected from the Message Type
drop down list box. These are Positive balance messages, Negative balance messages,
General messages, and Anticipated credit messages. The length of the Code (Key) is
restricted to 5 characters, and this code table is applicable to Billing, and Cash Receipts.

The positive balance message type indicates messages that should print when the balance
of the statement is positive. The negative balance message type indicates messages that
should print when the balance of the statement is negative. The general message type
indicates messages that will be printed on all statements generated. When printing
statements, you can select which general messages are to print. The anticipated credit
message type indicates messages that should print if a student has anticipated aid.

June 2012 PowerCAMPUS Code Tables 8.1 3-93

User Guide
Code Table Descriptions
 Examples of statement messages might include: holiday messages and remittance
messages.

The Statement Message field is populated by this code table.

Example of the field location in the system: Message window of the report setup for
the Statements report.

Code values entered here are stored in the Code_StatementMsg table.

Statement type
This code table is used when printing multiple statements per person/organization.
Charge/credit rows of the same statement type are grouped on one statement. This allows
several separate statements to be printed for each person/organization. Examples of
statement types might include: a general student statement type for all tuition related
charge/credits, a payment option statement, a sponsor statement, a faculty statement, a rent
statement for organizations to whom you are leasing office space, and a general
organization statement for those organizations that are not sponsors. The length of the
Code (Key) is restricted to 3 characters, and this code table is applicable to Billing, and
Cash Receipts.

The Statement Type, and Statement Type (view only) fields are populated by this code
table.

Example of the fields location in the system:

• Statement Type: Charge/Credit (Code) code table; Mailing window of the report
setup for the Statements report.
• Statement Type (view only): Statement window of the Registration Workflow,
People Billing Workflow and Organization Billing Workflow.

Code values entered here are stored in the Code_StatementType table.

Status (application)

These code values are used to define the status of applications. Examples of application
statuses might include: received, incomplete, complete, and committee review. The
statuses that are considered confirmed and the statuses that are considered canceled must
be indicated. If an application has an accepted decision and a confirmed status, the
applicant will automatically be converted to a student. An application with a canceled
status means that either the applicant or your institution has terminated the application
process. The length of the Code (Key) is restricted to 4 characters, and this code table is
applicable to Admissions.

The Status, and Application Status (view only) fields are populated by this code table.

3-94 PowerCAMPUS Code Tables 8.1 June 2012

User Guide
Code Table Descriptions
 Example of the fields location in the system:
• Status: Application window of the Applicants Workflow; Applicants setup.
• Application Status (view only): Admissions Educ Vista report; Admissions Status
Vista report; Source - Applicants Vista report; View Applicant Sources Vista view;
View Applicant Demographics Vista view; View Applicant State/Education Vista
view.

Code values entered here are stored in the Code_AppStatus table.

Status (inquiry)
These code values are used to define the status of inquiry records. Examples of inquiry
statuses might include: received inquiry, has applied, and no longer interested. The
statuses that are considered converted and the statuses that are considered canceled must
be indicated. If an inquiry record has a converted status, the inquiry will automatically be
converted to an applicant. An inquiry record with a canceled status means that either the
inquiry or your institution has terminated the inquiry process. The length of the Code
(Key) is restricted to 4 characters, and this code table is applicable to Admissions.

The Status, and Inquiry Status (view only) fields are populated by this code table.

Example of the fields location in the system:

• Status: Inquiry window of the Inquiries Workflow; Inquiries setup.
• Inquiry Status (view only): Source - Inquiries Vista report; View Inquiry Sources
Vista view; View Inquiry Demographics Vista view; View Inquiry State/Education
Vista view.

Code values entered here are stored in the Code_InqStatus table.

Stop list reasons

This code table should list any reasons that would prevent a student from registering for
courses or receiving grades. These reasons can be academic or financial in nature or for
purposes of maintaining address information. Examples of stop list reasons might include:
academic suspension, overdue fines, outstanding balance and expired address information.
The length of the Code (Key) is restricted to 4 characters, and this code table is applicable
to Academic Records, Admissions, Advancement, Billing, and Cash Receipts.

Selecting the Stop Registration check box means that the system will block registration
with an error message. Selecting the Stop Grades check box means that the system will
give a warning message when printing report cards or transcripts. The warning message
for Stop Grades may or may not be over-ridden by the operator depending on an indication
made in Grades setup, located under Tools: Setup in the Academic Records Setflow.
Selecting Show Stop Picture means that the system will display a stop sign icon and the

June 2012 PowerCAMPUS Code Tables 8.1 3-95

User Guide
Code Table Descriptions
 appropriate stop list reason on the Name window in any people-related workflow, with the
exception of the Inquiries Workflow.

Assigning and clearing stop list reasons

Stop List Reasons can be manually assigned and cleared on the Stop List window.
However, some features in PowerCAMPUS provide an automated process for assigning
stop list reasons. Many wizards within PowerCAMPUS prompt for the assignment of a
stop list reason, such as the Late Fee Assessment wizard. However, at this time, the system
will not automatically clear the stop list reason once the balance has been paid. For more
information, see Billing Processing in Billing. Date Driven Address currently assigns and
clears Stop List Reasons. Date Driven Address setup provides the ability to select a stop
list reason when all addresses are about to expire and a stop list reason when all addresses
have expired. Once the stop list reason has been created here and then has been selected in
the Date Driven Address setup, the system will automatically assign the appropriate stop
list reason.

Stop List Reasons can also be globally assigned and cleared for overdue balances using
the Stop List Process, located in Billing Processing in Billing. For more information, see
Billing Processing in Billing.

Creating stop list reasons

Your institution can create each stop list reasons, specifying the code, short/medium/long
descriptions and what if anything the stop list reason will prevent. However, when date
driven address stop list reasons are automatically created by the system, the system will
additionally default the Description for each stop list reason on the Stop List window. The
description for the stop list reason selected when all addresses are about to expire is: "All
of your addresses are about to expire. Please submit your updated address information."
The description for the stop list reason selected when all addresses have expired is: "You
have no valid address information. Please submit your updated address information." At
this time, you are not able to define the default description for the date driven address stop
list reasons. For more information, see Date Driven Address setup in System
Administrator.

The Stop Reason field is populated by this code table.

Example of the field location in the system: Stop List window of any people-related
workflow (including Registration and People Billing).

Code values entered here are stored in the Code_StopList table.

Sub cohort

Sub cohorts, or sub groupings of students, are tracked using this code table. Tracking sub
cohorts enables the institution to develop statistical reports based upon the sub groupings
within a cohort. Sub cohorts permit the institution to associate students with a sports team.
Examples of a sub cohort values are Baseball, Basketball, Football, Other, and Track/

3-96 PowerCAMPUS Code Tables 8.1 June 2012

User Guide
Code Table Descriptions
 Cross Country. The length of the Code (Key) is restricted to 10 characters, and this code
table is applicable to Academic Records, and Admissions.

The Sub Cohort field is populated by this code table.

Example of the field location in the system: Cohorts window of the Students
Workflow.

Code values entered here are stored in the Code_SubCohorts table.

Suffix
All suffixes that you would use for a person’s name can be set up here to avoid redundant
data entry. Examples of suffixes might include: Jr., Sr., and M.D. The length of the Code
(Key) is restricted to 15 characters, and this code table is applicable to Academic Records,
Admissions, Advancement, Billing, and Cash Receipts.

Tip
Since suffix is used throughout the system, the Code(Key) that you set up
for the suffix will default in the short, medium, and long descriptions and
cannot be changed. 

The Suffix field is populated by this code table.

Example of the field location in the system: Name window of any people-related
workflow (including Registration, Transcripts, and People Billing).

Code values entered here are stored in the Code_Suffix table.

Summary type

This code table is used to group like charge/credits together to get summary financial
information and summary views of data. Examples of summary types might include:
beginning balance summary, tuition summary, student fee summary, miscellaneous fee
summary, cash receipts, and financial aid. A Sort Order may be assigned to each summary
type to indicate how it should sort on views and reports. The length of the Code (Key) is
restricted to 6 characters, and this code table is applicable to Billing, and Cash Receipts.

Tip
A summary type of CUM (Cumulative) will automatically be created with
the first entry to this code table. This summary type is used in reporting to
track the cumulative balance for an academic year and academic year/
term. A sort order of 000 and a long description of Previous Cum will be
given to this type. 

The Summary Type, and Summary Type (view only and not labeled) fields are
populated by this code table.

June 2012 PowerCAMPUS Code Tables 8.1 3-97

User Guide
Code Table Descriptions
 Example of the fields location in the system:
• Summary Type: Charge/Credit (Code) code table.
• Summary Type (view only and not labeled): Balance window of the Registration
Workflow, People Billing Workflow, Organization Billing Workflow and Cash
Receipts Workflow.

Code values entered here are stored in the Code_SummaryType table.

Tenure status

This code table allows various tenure statuses to be created so that each faculty member
can be associated with one. Examples of tenure statuses might include: full tenure, under
review, and no tenure. The length of the Code (Key) is restricted to 10 characters, and this
code table is applicable to Academic Records.

Tip
Since suffix is used throughout the system, the Code(Key) that you set up
for the suffix will default in the short, medium, and long descriptions and
cannot be changed. 

The Tenure Status field is populated by this code table.

Example of the field location in the system: Faculty Data window of the Faculty
Workflow.

Code values entered here are stored in the Code_Tenure table.

Term

A term (semester) indicates a period of time within an academic year. There can be
multiple terms within an academic year. Examples of terms might include: Fall, Spring,
and Summer. The length of the Code (Key) is restricted to 10 characters, and this code
table is applicable to Academic Records, Admissions, Advancement, Billing, and Cash
Receipts.

A Term order within Chronological Year can be assigned to each term for displaying on
views and reports. The order is determined by the chronological order of terms within the
same academic year. For example, the 2000 academic year may consist of Fall, Winter,
Spring, and Summer. The chronological order of the terms for 2000 would most likely be
Winter, Spring, Summer, Fall where Winter would be ‘001’, Spring would be ‘002’,
Summer would be ‘003 and Fall would be ‘004’.

3-98 PowerCAMPUS Code Tables 8.1 June 2012

User Guide
Code Table Descriptions
 This code table populates dozens of fields throughout the PowerCAMPUS system and is
absolutely essential for storing historical data.

Tip
Sort orders need to be unique because both page breaks and ordering on
reports are dependent on this order. If a report shows two terms on the
same page but all other terms on a separate page, your sort order is
duplicated on these two terms. The Session code table is available if
multiple time periods exist within a term. For more information, see
Session. 

Code values entered here are stored in the Code_AcaTerm table.

Test

This code table is where tests that are tracked by your institution are held. Examples of
tests might include: Scholastic Aptitude Test (SAT), Test of English as a Foreign
Language (TOEFL), and Graduate Records Exam (GRE). Each test can be identified as a
numeric or alpha test by selecting either the Numeric Scores or the Alpha Scores radio
button. You may also flag each test to keep a total score, a high total score, or an average
score. Test names and scores can also be printed on transcripts by selecting the Print on
Transcript check box.

The length of the Code (Key) is restricted to 6 characters, and this code table is applicable
to Academic Records, and Admissions.

Note
If you select the Alpha Scores radio button, the Keep Total Score, Keep
High Total Score and Keep Average Score checkboxes will not be
available. These three options are only available for numeric tests. 

The total score is the addition of the scores for each test type (subject) of a test taken on a
particular date. For example, selecting the Keep Total Score check box for an SAT test
would combine the scores for both the Math and the Verbal test types into a total SAT
score.

The average score is the average of the scores, regardless of test type (subject) for a test
taken on a particular test date. For example, selecting the Keep Average Score check box
for an SAT test would combine the scores for both the Math and the Verbal test types and
then divide the sum by two.

The high total score is the addition of the highest score for each test type (subject) for a
test regardless of test date. For example, selecting the Keep High Total Score check box
for the SAT test would, if a student took the SAT multiple times, combine the highest score
achieved for the Verbal test type with the highest score achieved for the Math test type into
a high total SAT score.

June 2012 PowerCAMPUS Code Tables 8.1 3-99

User Guide
Code Table Descriptions
 If the Print on Transcript check box is selected, then new test scores entered on the Test
Scores window will default to Yes for Print on Transcript but can be changed.

Tip
If any of the tests are flagged to keep total, high total, or average scores,
a maximum length of four (4) characters will be allowed for the Code
(Key). 

Note
Build this table prior to your Test Type code table because a test will be
required in that table. 

The Test, and Select Tests that will link to Test Type fields are populated by this code
table.

Example of the fields location in the system:

• Test: Test Scores window of the Inquiries Workflow and the Applicants Workflow;
Test Type code table.
• Select Tests that will link to Test Type: Drill down on Test Type code table.

Code values entered here are stored in the Code_Test table.

Test type

Test types indicate the type of test, the test subject, or the different scoring sections of a
test being tracked. Examples of test types might include: Reading Comprehension, Math,
Verbal, and Science. The length of the Code (Key) is restricted to 4 characters, and this
code table is applicable to Academic Records, and Admissions.

High score within a test type can be tracked by selecting the Keep High Score check box.
A test type with High appended to the code value will automatically be created.

Tip
The system will also create test types for each of the totals that you
indicated you wanted to track in the Test code table. These include ZTOT
for Total, ZSHG for High Total, and ZTVG for Average. 

Note
In order to link test types with one or more tests from the Test code table,
double click on the magnifying glass. A drill down window will display to
allow entry of the tests. Then, once a test is selected in the Test Scores
window for an inquiry, applicant or student, only associated test types will
display for that test. 

Data entered here is stored in the Code_TestTypeLink table.

The Test Type field is populated by this code table.

3-100 PowerCAMPUS Code Tables 8.1 June 2012

User Guide
Code Table Descriptions
 Example of the field location in the system: Test Scores window of the Inquiries
Workflow and the Applicants Workflow.

Code values entered here are stored in the Code_TestType table.

Transfer sub type

Each transfer course may be broken down into subtypes. Since transfer subtypes can be
different than your institution's event subtypes, a different code table is provided.
Examples of transfer subtypes might include: lecture, lab, and self-study. A Sort Order
may be assigned to each subtype to indicate how it should sort within the transfer course
on views and reports. The length of the Code (Key) is restricted to 4 characters, and this
code table is applicable to Academic Records.

The Sub Type, Transfer Sub Type, and Transfer Sub Type (view only) fields are
populated by this code table.

Example of the fields location in the system:

• Sub Type: Transfer window of the Transcripts Workflow.
• Transfer Sub Type: Transfer Policy window of the Transfer Policy Workflow.
• Transfer Sub Type (view only): Detail window of the Transfer Policy Workflow.

Code values entered here are stored in the Code_TranSubType table.

Tuition exemption

This code table allows you to track tuition exemptions, which are used to determine if a
student should receive certain tuition credit against his bill. Examples of tuition
exemptions might include: employee, child of employee, and state resident.

The Tuition/Fee Exemption field is populated by this code table.

Example of the field location in the system: Financials window of the Applicants
workflow, the Students workflow, and the Registration workflow; and the Cash
Receipts workflow.

Code values entered here are stored in the Code_TuitionExempt table.

Tuition plan

Tracking tuition plans is another way to determine the fees charged to a student. Enter
code values for tuition plans in this code table. Examples of tuition plans might include:
out of state, discounted, and county resident.

June 2012 PowerCAMPUS Code Tables 8.1 3-101

User Guide
Code Table Descriptions
 The Tuition Plan field is populated by this code table.

Example of the field location in the system: Financials window of the Applicants
workflow, the Students workflow, and the Registration workflow; and the Cash
Receipts workflow. Code values entered here are stored in the Code_TuitionPlan
table.

Tuition range
The cost of tuition for various institutions can be broken down into a number of price
ranges in this code table. These code values can then be assigned to institutions that are
sources of inquiries, applicants, or students. Examples of tuition ranges might include:
dollar figures such as $0.00 to $1,000.00 or high, mid-range, and low.

The Tuition Range field is populated by this code table.

Example of the field location in the system: Institution window of the Institutions
Workflow and the Transfer Policy Workflow; and the Cash Receipts workflow.

Code values entered here are stored in the Code_TuitionRange table.

Veteran

This code table allows you to track veteran status for applicants, students, and faculty. The
institution may have to track this in order to determine eligibility for certain types of
financial aid. Examples of statuses might include: ROTC, status verified, and honorable
discharge. The length of the Code (Key) is restricted to 4 characters, and this code table is
applicable to Academic Records, Admissions, and Advancement.

The Veteran field is populated by this code table.

Example of the field location in the system: Name window of any people-related
workflow (excluding Inquiries but including Registration, Transcripts, People
Billing); Demographics window of the Inquiries Workflow, the Applicants Workflow
and the Students Workflow.

Code values entered here are stored in the Code_Veteran table.

Violation

This code table tracks the violations of students. Entry of violations can be done from the
Violations window of the Students Workflow in the Academic Records Setflow or from
the Violations window of the Gradebook page in Self-Service. For more information, see
Students in Academic Records and the Self-Service for Faculty User Guide. Examples of
violations might include: started fight, no tie, and no homework. The length of the Code
(Key) is restricted to 10 characters, and this code table is applicable to Academic Records.

3-102 PowerCAMPUS Code Tables 8.1 June 2012

User Guide
Code Table Descriptions
 A Category must be assigned to each violation. For example, you could have violation
categories of conduct, dress code and academic.

The Violation field is populated by this code table.

Example of the field location in the system: Violations window of the Students
Workflow. Code values entered here are stored in the Code_Violations table.

Violation category

The code values entered in this code table are used to group together the violations of
students. Examples of violation categories might include: dress code, conduct, and
academic. The length of the Code (Key) is restricted to 10 characters, and this code table is
applicable to Academic Records.

Note
Build this table prior to your Violation code table because a violation
category will be required in that table. 

The Category, and Violation fields are populated by this code table.

Example of the fields location in the system:

• Category: Violation code table.
• Violation: Violations window of the Students Workflow (displays under Category).

Code values entered here are stored in the Code_ViolationCategory table.

Visa

The different types of visas of people at your institution who are not citizens of the country
can be maintained here for later entry into their demographic information. Examples of
visas might include: permanent resident, green card, and student visa. The length of the
Code (Key) is restricted to 4 characters, and this code table is applicable to Academic
Records, Admissions , and Advancement.

The SEVIS Visa Code field allows you to map the PowerCAMPUS visa code values with
the corresponding codes recognized by SEVIS for reporting purposes. The visa codes are
defined by SEVIS and cannot be modified.

Visa code values

The visa code values defined by SEVIS are as follows:

June 2012 PowerCAMPUS Code Tables 8.1 3-103

User Guide
Code Table Descriptions
 F-1 (Foreign Student Visa)

This is the type of visa given by U.S. Consulates and the type of immigration status given
by the INS to foreign nationals who intend to be or are enrolled for a full course of study at
approved educational institutions in the United States. The F-1 visa is for non-immigrants
to enter the United States solely for the purpose of study and means that, upon completing
his studies, the individual will return to the foreign country of permanent residence. This
visa code will display as 01 on the Government Information report.

F-2 (Dependent Spouse or Child of F-1 Visa Holder)

This is the type of visa given by U.S. Consulates and the type of immigration status given
by the INS to the spouse and/or unmarried minor dependents (under the age of 21) of a F-
1 visa holder. This visa is issued if the spouse and/or dependent wishes to accompany or
visit alone, at a later time, the F-1 visa holder. This visa code will display as 04 on the
Government Information report.

J-1 (Exchange Visitor Visa)

• This is the type of visa given by U.S. Consulates and the type of immigration status
given by the INS to foreign nationals who intend to be or are: teaching, studying,
researching, consulting, demonstrating special skills or receiving training in the
United States. This visa code will display as 03 on the Government Information
report.

J-2 (Dependent Spouse or Child of J-1 Visa Holder)

This is the type of visa given by U.S. Consulates and the type of immigration status given
by the INS to the spouse and/or unmarried minor dependents (under the age of 21) of a J-1
visa holder. This visa is issued if the spouse and/or dependent wishes to accompany or
visit alone, at a later time, the J-1 visa holder. This visa code will display as 06 on the
Government Information report.

M-1 (Foreign Student Visa)

This is the type of visa given by U.S. Consulates and the type of immigration status given
by the INS to foreign nationals who intend to be or are students in vocational or other
nonacademic programs (other than language training) in the United States. Students with
this visa cannot change immigration status. This visa code will display as 02 on the
Government Information report.

M-2 (Dependent Spouse or Child of M-1 Visa Holder)

This is the type of visa given by U.S. Consulates and the type of immigration status given
by the INS to the spouse and/or unmarried dependents (under the age of 21) of a M-1 visa
holder. This visa is issued if the spouse and/or dependent wishes to accompany or visit
alone, at a later time, the M-1 visa holder. This visa code will display as 05 on the
Government Information report.

3-104 PowerCAMPUS Code Tables 8.1 June 2012

User Guide
Code Table Descriptions
 The Visa field is populated by this code table.

Example of the field location in the system: Name window of any people-related
workflow (excluding Inquiries but including Registration, Transcripts, People
Billing); Demographics window of the Inquiries Workflow, the Applicants Workflow
and the Students Workflow.

Code values entered here are stored in the Code_Visa table.

Volunteer interest

This code table tracks the interests of prospects and donors for which they may have
volunteered. Examples of volunteer interests might include phonathons, reunions, and
homecomings. The length of the Code (Key) is restricted to 6 characters, and this code
table is applicable to Advancement.

The Volunteer/Interest field is populated by this code table.

Example of the field location in the system: Volunteer/Interest window of the Alumni
Workflow, the People Workflow and the Organizations Workflow in the Advancement
Setflow only. Code values entered here are stored in the Code_VolunteerInterest table.

Waived reason

This code table tracks reasons for which an action might be waived. Examples of waived
reasons might include: counselor discretion and substitution of another document. The
length of the Code (Key) is restricted to 6 characters, and this code table is applicable to
Academic Records, Admissions, Advancement, Billing, and Cash Receipts.

The field to the right of the Waived check box is populated by this code table.

Example of the field location in the system: Scheduled Actions drill down, available
from the Scheduled Actions window of any people-related or organization-related
workflow.

Code values entered here are stored in the Code_WaivedReason table.

June 2012 PowerCAMPUS Code Tables 8.1 3-105

User Guide
Code Table Descriptions
3-106 PowerCAMPUS Code Tables 8.1 June 2012
User Guide
Code Table Descriptions
 4 Code Tables Reports

Each report has a default that includes the standard system sort and filter. New reports
with customized sorting and filtering can be created and saved. A customized setup can be
done on many reports as well. For more information see Customizing a Report in User
Introduction.

Code table
The Code Table report prints a listing of all of the values entered for each code table.
Information such as the code value, status, short, medium and long description, and
revision information will display on the Code Table report. Use this report for verifying
that all of the necessary values have been entered or properly converted

Tip
The page buttons for the Code Table report act differently than with other
reports in PowerCAMPUS. The First Page button moves to the Previous
Code Table. The Previous Page button moves to the Previous Page of
the code table displaying. The Next Page button moves to the Next Page
of the code table displaying. The Last Page button moves to the Next
Code Table. 

Note
Click Setup to enter additional printing parameters. 

The Code Table report setup will take the place of building filter criteria. Three options are
available for printing the Code Table report in PowerCAMPUS. You may print the report
with one of the following options selected: Print All Tables, Print By Office or Print By
Specific Table. When selecting Print By Office or Print By Specific Table, a drop down
list box will display allowing you to select which office or table to use for the report.

Tip
Please be aware that a blank page will print between each code table if
Form Feed is selected on your printer. 

June 2012 PowerCAMPUS Code Tables 8.1 4-1

User Guide
Code Tables Reports
4-2 PowerCAMPUS Code Tables 8.1 June 2012
User Guide
Code Tables Reports
 A Code Tables Template

This appendix is included to provide you with a template for creating your charge/credit
codes and a list of system defined code table values.

Summary representation of code tables

template
The table below describes the summary representation of code tables template.

Charge/Credit Code Table This template, to be used in conjunction with the Charge/
Template* Credit (Code) code table, located under Tools: Code Tables in
the Billing, Cash Receipts and System Administrator Setflows,
will enable you to set up your charge/credit code values on
paper before entering them into the PowerCAMPUS system.
Due to the volume of information that is needed, it is
recommended to use this template prior to entering your
charge/credit codes in PowerCAMPUS.
System-Defined Code This chart will display all of the system defined code table
Table Values values in code tables that are either completely system-defined
or contain some system-defined code table values.

This template has been formatted for printing with all margins set at 0.8” (inches).

June 2012 PowerCAMPUS Code Tables 8.1 A-1

User Guide
Code Tables Template
 Charge/Credit code table template

A-2 PowerCAMPUS Code Tables 8.1 June 2012

User Guide
Code Tables Template
 System-Defined code table values
All of the code tables included in the PowerCAMPUS and PowerCAMPUS Self-Service
systems that are either completely system-defined or contain some system-defined code
values are listed below. When you first open the code table, these code values will default
for you automatically and may not be changed.

Note
All of these code tables can be accessed by selecting Tools: Code Tables
in the System Administrator Setflow. 

KEY: * = code table is system-defined

** = code table contains system-defined code values

***= code table is not used beyond PowerCAMPUS 6.32

Code Table Name Code Values

Activity Behavior*** DEFAULT, SUBTASKS

Address Type** GP

Attendance Status - Daily** ABSENT, PRESENT

Attributes** System-defined code table values will be created as Day

Attributes for each day code table value created in the Day of
Week code table.

Award Type** OVERSTND, TERMSTND

*Balance Type ACAYR, ALLSESS, ALLTERM, ALLTERMCUM, CALYR,

CURR, FISCYR, TERM, TERMCUM, YTS

Batch Type* IQFEES, IQREG, PCAMPUS

Cohort Exclusion DEATH, MILSERVICE, SRVARMFORC, SRVCHRCHMS,

SRVFORAID, TOTPRMDIS

Column Comparison* BIT_FNAME, BIT_LNAME, CITY, DOB, EMAIL, FNAME,

FRM_FNAME, FRM_LNAME, GENDER, GOVTID, LINE,
LNAME, MI, PHONE, SDX_FNAME, SDX_LNAME,
STATE, SUFFIX, ZIPCODE

Communications Type** HISTE

Community Member LEADER, MEMBER

Level***

June 2012 PowerCAMPUS Code Tables 8.1 A-3

User Guide
Code Tables Template
 Code Table Name Code Values
Community Member ACTIVE
Status***

Deferred Giving Status* CANCELED, CLOSED, PENDING, PLEDGED, RECEIVED

Discount Type** AFFIL

Donor Status* ACTIVE, INACTIVE, LYBUNT, SYBUNT

Drop Reason** CANCEL

FASB Type* COND, UNCOND

Finance Type* DEPENDEXP, EMPLOYFUND, LIVINGEXP, OTHEREXP,

OTHERFUND, PERSONFUND, SCHOOLFUND,
TUITIONEXP

Forum Access Type*** PRIVATE, PRIVCOURSE, PUBLIC

Forum Status*** CLOSED, HIDDEN, OPEN

Forum User Level*** MODERATOR, RESTRICTED, USER

Fund Type* BINCOMFUN, EVGOVTFUN, GOVTORG1, GOVTORG2,

INTERORG1, INTERORG2, OTHORGFUN, PERSONFUN,
PROGSPOFUN

Gift Campaign** ALL

Gift Club Report* OVERALL (Additional system-defined values could display

based upon the Gift Club Report setup. For more information,
see Setups in Advancement.)

Gift Form*** OUTRIGHT, PLEDGE

Gift Tender** CASH, CHECK, CREDITCARD

Government Note Type* AMENDPRREM, APPFAILCOM, COMPROGREM,

CONPROGCOM, DBFREM, DEFPROGREM,
DEPENDREAS, DISACTEXP, ENDPROGREM,
EVTERMREM, EXTPROGCOM, EXTPROGREM,
EXVISREM, FUNDREM, INFRACTCOM, POEREM,
REPRINTREA, RFCREM, SUBJECTREM,
TERMDEPCOM, TERMSTDREM

Grading Activity** PERCEPTION

Grading Method*** AVE, HIGH, LAST, MED, TOT

A-4 PowerCAMPUS Code Tables 8.1 June 2012

User Guide
Code Tables Template
 Code Table Name Code Values
IMS Institution Role Type* ADMINISTRATOR, ALUMNI, FACULTY, GUEST,
INSTRUCTOR, LEARNER, MEMBER, MENTOR,
OBSERVER, PROSPECTIVESTUDENT, STAFF, STUDENT

Interest Type** APPLICANT, INQUIRY, INST_APP, INST_INQ

ISO 3166 Country Codes* AD, AE, AF, AG, AI, AL, AM, AN, AO, AQ, AR, ASAT, AU,
AW, AZ, BA, BB, BD, BE, BF, BG, BH, BI, BJ, BM, BN, BO,
BR, BS, BT, BV, BW, BY, BZ, CA, CC, CD, CF, CG, CH, CI,
CK, CL, CM, CN, CO, CR, CS, CU, CV, CX, CY, CZ, DE, DJ,
DK, DM, DO, DZ, EC, EE, EG, EH, ER, ES, ET, FI, FJ, FK,
FM, FO, FR, GA, GB, GD, GE, GF, GH, GI, GL, GM, GN, GP,
GQ, GR, GS, GT, GU, GW, GY, HK, HM, HN, HR, HT, HU,
ID, IE, IL, IN, IO, IQ, IR, IS, IT, JM, JO, JP, KE, KG, KH, KI,
KM, KN, KP, KR, KW, KY, KZ, LA, LB, LC, LI, LK, LR, LS,
LT, LU, LV, LY, MA, MC, MD, MG, MH, MK, ML, MM, MN,
MO, MP, MQ, MR, MS, MT, MU, MV, MW, MX, MY, MZ,
NA, NC, NE, NF, NG, NI, NL, NO, NP, NR, NU, NZ, OM, PA,
PE, PF, PG, PH, PK, PL, PM, PN, PR, PS, PT, PW, PY, QA, RE,
RO, RU, RW, SA, SB, SC, SD, SE, SG, SH, SI, SJ, SK, SL, SM,
SN, SO, SR, ST, SV, SY, SZ, TC, TD, TF, TG, TH, TJ, TK, TL,
TM, TN, TO, TR, TT, TV, TW, TZ, UA, UG, UM, US, UY, UZ,
VA, VC, VE, VG, VI, VN, VU, WF, WS, YE, YT, ZA, ZM, ZW

ISO 639 Language Codes* AA, AB, AF, AM, AR, AS, AY, AZ, BA, BE, BG, BH, BI, BN,
BO, BR, CA, CO, CS, CY, DA, DE, DZ, EL, EN, EO, ES,
ET,EU, FA, FI, FJ, FO, FR, FY, GA, GD, GL, GN, GU, HA, HI,
HR, HU, HY, IA, IE, IK, IN, IS, IT, IW, JA, JI, JW, KA, KK,
KL, KM, KN, KO, KS, KU, KY, LA, LN, LO, LT, LV, MG, MI,
MK, ML, MN, MO, MR, MS, MT, MY, NA, NE, NL, NO, OC,
OM, OR, PA, PL, PS, PT, QU, RM, RN, RO, RU, RW, SA, SD,
SG, SH, SI, SK, SL, SM, SN, SO, SQ, SR, SS, ST, SU, SV, SW,
TA, TE, TG, TH, TI, TK, TL, TN, TO, TR, TS, TT, TW, UK,
UR, UZ, VI, VO, WO, XH, YO, ZH, ZU

Mailing Type** GNRL, SEVISD, SEVISF

Matching Gift Status* CANCELED, CLOSED, PENDING, PLEDGED, RECEIVED

Media Attribute* ASSIGNED, AUTHOR, COPYRIGHT, DESCRIPTION,

DUE_DATE, KEYWORD, ORIGFILE, POSTED_BY,
POSTED_DATE, PRICE, RATING, SIZE, TITLE,
VIEW_END_DATE, VIEW_END_TIME,
VIEW_START_DATE, VIEW_START_TIME

Media Category* ASSIGN, DELIVERABLE, ETEXTBOOK, NOTES, QUIZ,

SYLLABUS, TEST

June 2012 PowerCAMPUS Code Tables 8.1 A-5

User Guide
Code Tables Template
 Code Table Name Code Values
Media Entity* BUILDING, CALENDAR, FACULTY, ORGANIZATION,
PEOPLE, ROOM, SECTIONGRADINGDETAIL,
SECTIONS, STUDENT, WEBMESSAGES

Media Type* EBOOK, EXCEL, GIF, HTML, JPG, MP3, MPEG-VIDEO,

PDF, PPT, TXT, WORDDOC, ZIP

Non Cash/In Kind Status* CANCELED, CLOSED, PENDING, PLEDGED, RECEIVED

NSC Status Codes* A, D, F, G, H, L, N, W, Y

Pledge Status* CANCELED, OPEN, PAID, PENDING, PLEDGED,

REVERSED, WRITEOFF

Pledge Term** APRDTRM

Pledge Type** APRD, MPRD

Record Type** ADT, ADTP, ADV, ADVP, ALUM, APP, CNSL, CNSP,
CONE, CONT, DONR, EMP, EMPP, EMPR, FAC, FACP,
GUST, INQ, INS, LEG, MEM, PAR, PARF, PARP, PRST, PUB,
REL, SCH, SIGN, SPS, STUD, TRUS, VEN

Registration Method* POWERCAMPUS, WEB

Registration Permission APPROVED, DENIED, WAITING

Status*

Registration Type* CONED, TRAD

Scholarship Requirements NOT_RECEIVED, RECEIVED, WAIVED

Received*

Section Fee Group** ALL

SEVIS Events* ADDDEP, AUTHDBFC, COMPROG, CPTEMP,

CREATESTUD, DEFATTEND, DISCACT, EDITDEP,
EDITFIN, EDITPERS, EDITPROG, EXTPROG, OCEMP,
OPTREQ, REACTDEP, RESFC, STUDREG, TERMDEP,
TERMSTUD

Sub Cohort BASEBALL, BASKETBALL, FOOTBALL, OTHER,

TRKCRSCNTR

Statement Type** IQ

A-6 PowerCAMPUS Code Tables 8.1 June 2012

User Guide
Code Tables Template
 Index

A Change Reasons
Divorce 3-16
A/R account 3-19 Marriage 3-16
Academic Interests Preference 3-16
Arts 3-3 Code (Key) 2-1
Pre-Med 3-3 Code Table Report 4-1
Science 3-3 Code Tables 2-1
Academic Records 3-11 Code Value 2-3
Acknowledgement Print Cohort 3-23
Manual 3-4 Effective Date 3-23
Operator 3-4 End Date 3-23
System 3-4 Cumulative 3-13
Action Rule Regen 3-5 Curriculum 1-1
Address Type

D
Business 3-7
Home 3-7
Local 3-7
Data Integrity 1-1
Summer 3-7
Dedication 3-32
Adjunct Math Faculty 3-74
Demographics 3-63
Affiliation 3-36
Dependent Spouse 3-103
Alumni Workflow 3-48
Distribution Order 3-20
Art Appreciation 1-1
Donor Processing 3-24
Asterisks 2-1
Drop Reason 3-38
Attributes 3-11
Award Wizard 3-12
E
B Electrical Engineering 1-1
Endowment 3-45
Bachelor of Arts 3-33
Enterprise Manager 3-87
Balance Report 3-14
Balance Type 3-14
Baseball 3-7 F
Batch Gift 3-4
Facility Management 3-27
Behavior 3-6
FASB type 3-41
Billing 3-5
Fin Aid Upload Code 3-21
Binational Comm Funds 3-44
Financial Aid 3-20
Building Function 3-1
Flexible Configuration 3-10
Foreign Student Visa 3-102
C Full-Time Equivalency 3-75

Cash Receipts Setflow 3-17

June 2012 PowerCAMPUS Code Tables 8.1 I-1

User Guide
Index
G N
General Ledger Journal 3-43 Nonimmigrant 3-39
Gift Club Report 2-2 NSC Processing 3-28
Government 3-15 Nursing 3-24
Graduated 3-66
O
H
Office 1-2
High School Vista 3-25 Outright 3-49
Historical Data 3-97
Honor Code 3-56 P
Honors 1-2
Payment Plan Creation 3-69
I People Billing Workflow 3-3
Percentage 3-21
Immunization Picture Path 3-71
Measles 3-57 Pledge Defaults 3-4
Mumps 3-57 Population 3-73
Rubella 3-57 Port of Entry Remarks 3-55
Tuberculosis 3-57 Prefix 2-1
Inquiries Workflow 3-3 Print By Office 4-1
ISO 3166 Code 3-59 Print Order 3-11

J R
Journal Entry 3-50 Record Maintenance 3-48
Record Type
L Advisor 3-78
Contact 3-78
Language Employee 3-78
Home Language 3-61 Faculty 3-78
Primary Language 3-61 Insurance Company 3-78
Late Fee 3-19 Parent 3-78
Logical 1-1 School 3-78
Vendor 3-78

M
S
Magnifying Glass 3-31
Mail Merge 2-1 Scheduled Actions 3-76
Market Test 3-53 Scholarship 3-85
Master Scheduler 3-11 Screening Method
Masters of Science 3-33 Econometrics 3-85
MS Access File 3-64 Self 3-1
Self-Service 3-1
Serial 3-40

I-2 PowerCAMPUS Code Tables 8.1 June 2012

User Guide
Index
 Sophomore 3-22 W
Sort Order 3-96
Source Windows 2-3
Online Application 3-90 WriteOff 3-71
Online Inquiry 3-90
Stop List 3-95
Z
Subsidiary Sources 3-60
Suffix 2-1 ZIP File 3-64
Summary A-1
System Administrator Setflow 1-1

T
Taxpayers Relief Act 3-27
Telecommunications 3-8
Term
Fall 3-97
Spring 3-97
Summer 3-97
Winter 3-97
Termination Remarks 3-55
Traditional 3-79
Transcripts 3-56
Transfer Policy 3-8
Trustee 3-8

U
Unauthorized Employment 3-39
Undergraduate 3-75

V
Vehicle 1-1
Violations 3-101
Volunteer Interest
Homecomings 3-103
Phonathons 3-103
Reunions 3-103

June 2012 PowerCAMPUS Code Tables 8.1 I-3

User Guide
Index