Implementation Minutes
Student Team
Student Mapping
Date: October 28, 2008
Meeting Information
Facilitator
Duane Thowe
Note Taker
Renee Roach, Assistant Registrar, Cameron University
Attendees
Linda Phillips, Renee Roach, Kelly Simon, Dawne Massey, Julie Duncan, Rick
Clyburn, Debbie Goode, Tom Sutherlin, Ninette Carter, Brenda Russell
Registration Objectives
Relevant
Training/Discussion
Highlights:
GAPs Identified:


Dawne Massey mentioned that we will need a plac3e on SFARGRE
screen to identify those students who have elected to participate in the
tuition lock program. Duane stated that we could use a rate code on
the account or use Student attribute on the SFARGRE screen.
SOACURR only allows for 2 curriculums to be attempted at one time.
In legacy, we can indicate more than 2 areas of study. This might be an
issue with our student who receive more than 2 degrees within a single
semester.
Decisions Made:
Decisions Required:
Other Issues and
Concerns:
Action Items / Assignments
Description






Owner
Deadline
SOATERM is identified in STVTERM as far back as we are
converting in academic history. It has to be built
backwards.
Fields within SOATERM are: CRN – course reference
number. Each section will have its own CRN. The system
will automatically create the CRN.
When we roll the semester schedule, we roll fall to fall and
roll the semester information forward.
End users must have a password to access registration or
process data on these particular forms. We do not want to
give general access to this – only 1-2 persons should have
access to password override for the data.
Registration fee assessment and tracking by CRN – if we
are charging by CRN (course), we will need charges at the
catalog level or at the section level.
In BANNER, there is a registration error checking process
that will provide a fatal error message if certain criteria are
not met. For example, pre-requisites, co-requisites, max
hours and time could be included within these error flags.
SunGard Higher Education – Confidential & Proprietary
291221017
Page 1 of 4
5/29/2016
Implementation Minutes


















SOATERM Options – There can be parts of term for every
whole term. Full term, half term can have parts of a term
within a term.
Enrollment status is at the term header level and will be the
overall status of all coursework within that term.
SFARSTS – course registration status - each course will
have its own status.
STVRSTS – can be status for each course such as:
extension 1, extension 2, registered, dropped, withdrawn,
etc.
REGCONTROL screen name – SFAESTS – Enrollment
status control form. STVESTS has to be identified first
before we can build the database. We have enrollment
status dates (start and end) and enrollment status refund
rules for refunding. This is at the term level.
SOADEST – Student System Distribution Initialization will
allow us to print documents before we actually begin
registration. This option only appears at the first time
entering the system.
In order to override a hold, the user must have a password.
SFRSTCR – registration table behind the courses that will
show all the types of overrides that are available.
SFAREGS – option for 1098 T processing. We currently do
not outsource for this processing. It is completed in house.
SFAROVR – how to identify permits for overrides on
registration form. We have to assign a particular permit
and it will take you to a student override form.
REGFEES is a form for fee assessment and fee
processing. We will set up the fees and how to charge
students.
SFAFAUD – an audit trail of student fee assessment. This
is a form within REGFEES.
SFAAFEE – additional fees that might apply to everyone
(such as and ID fee, parking permit fee).
SFAFMAX – Registration fees minimum/maximum charge
control. These fees are applicable to everyone. This
option is not used very often.
SFARFND – fee assessment refund. We will enter the
period which will be part of the term period. Refund period
will be a start and end data – a range in which we want this
period to take place.
SFARGRE – method of assigning fees at the section level.
Includes a term and a rule type that are built by attribute,
campus, student and level. Entry type could be pre=bill or
regular. Typically most types are regular. Fees can be
built for a specific curriculum if needed such as for military
students or based upon a residency code.
If we need to assign fees at the section level, we will do so
in SSADETL underneath the Schedule form. This table
must be included within the mapping document
(SCRFEES).
Curriculum rules in processing – CURRIC – when we build
curriculum rules, we check where we want the flag to be
SunGard Higher Education – Confidential & Proprietary
291221017
Page 2 of 4
5/29/2016
Implementation Minutes



turned on. Gateway records are for where the curriculum
rules are applicable. Relay to Sandra to build the
SOACURR.
SOACTRL – overall curriculum rules as to what type of
checking we want done. Only two curriculums are allowed
for a particular module. This might be a GAP because we
currently allow students to have more than 2 majors
attempted at the same time.
SOACURR – include base curriculum rules, majors and
departments, rule based concentrations, minors, module
control, program level, college and degree. No data
mapping on these tables. Sandra will build prototype with
curriculum information. We will transfer whatever is in
legacy into BANNER. Sandra will configure gateway
records that were determined in discovery.
Fee assessment can be done online or in batch process
(SFRFASM). It was mentioned that it is preferred to run
this in sleep/wake mode. The sleep/wake option is
maintained at the operating system level and end users
should not have access to this form.
Accounts Receivable
Relevant
Training/Discussion
Highlights:

We do not make changes manually on the student account. You must
refer to the original source and correct the problem from that point
forward.
GAPs Identified:
Decisions Made:
Decisions Required:
Other Issues and
Concerns:
Action Items / Assignments
Description





Owner
Deadline
There are two forms in BANNER for Accounts Receivable,
the student side will be TS and the finance side will be TF.
Every user who completes a transaction is a potential
cashier. Anyone who runs an online transaction or process
is a cashier. A user will need to close their session at the
end of the day and tally up their transactions. Users can be
different from cashiers.
TSACTRL – a rule form that must be set up at the
beginning providing process parameters.
TGUAPRF – student system user could be a supervisor
over a certain number of users. We can restrict the user in
that they will only be allowed to enter certain detail code.
This is typically a one-time setup.
Term based detail code allows us to sue the same detail
code repeatedly and still hit finance (TSATBDS). Term
SunGard Higher Education – Confidential & Proprietary
291221017
Page 3 of 4
5/29/2016
Implementation Minutes




based designators eliminates the need for many sets of
code and simplifies the process.
TSADETS – detail code is one of the first things that must
be set up. An example would be the general ledger
interface to BANNER finance. The finance accounting
structure needs to be built before we can fill out this form.
Cameron University’s academic year in the Business office
is August to July. We are a trailing school.
TTVSRCE is a validation table for source. The source is
system required and cannot be manually changed. We do
not make an adjustment manually on the student’s
account. It is imperative that the user refer back to the
source (registration, etc). Adjustments have to be made
within the correct module to make changes. As an end
user and cashier, T-transaction is the only type of
transaction that should be manipulated on the student’s
account.
Student account can be viewed on several forms.
Examples are TBRAACD and SCADETL.
SunGard Higher Education – Confidential & Proprietary
291221017
Page 4 of 4
5/29/2016