Database Extension Utility FAQ
This FAQ is also available on the Commons at
http://www.edu1world.org/CommonsBanner/wiki/document/4230
What is Database Extension Utility?
Database Extension Utility delivers database changes that are required for two other initiatives: user
interface modernization of administrative Banner (Project Horizon/Banner 9) and Multi-Entity Processing.
This is in response to having smaller, incremental releases that do not require such a large upgrade
window.
The Database Extension Utility is a controlled release. There would be two reasons you would want
to install this release:
1. Those who plan to implement Multi-Entity Processing
2. Those who would like to be an early adopter of Banner 9/Student Horizon
If your institution fits one of these cases and would like to obtain the release, please submit a Service
Request via the Customer Support Center with your request. When submitting your request use Product
Line = Banner; Product = General; Module = Database Extension Utility; Product Version = 8.0.
The Database Extension Utility will be released in two phases:
Phase One will
be delivered in the First Quarter of 2011. This phase of the Database Extension
Utility will add up to six new columns to all tables in the database. Tables which already have
_VPDI_CODE, _ACTIVITY_DATE, _DATA_ORIGIN and/or _USER_ID will not have these
columns added.
Phase Two will be delivered later in 2011 and will be executed as part of the installation of the Horizon
modules (Catalog, Schedule, etc.). This phase of the Database Extension Utility will “enable”• the
recently added columns that pertain to Horizon (SURROGATE_ID and VERSION) and will only convert
the tables that are associated with the UI objects within the modules. Enabling the columns will consist of
populating each column with a default value and updating each column to be NOT NULL. Triggers to
populate these columns will also be added at this phase.
What columns are being added as a part of Database
Extension Utility?
Up to six new columns are being added as part of Database Extension Utility. All columns will be
delivered as nullable and unpopulated.
Name
Type
Nullable?
Could
Exist?
Value
*_SURROGATE_ID
NUMBER(19)
Yes
No
Populated from sequence
*_VERSION
NUMBER(19)
Yes
No
One up, start at 0 increment with each update
*_USER_ID
VARCHAR2(30)
Yes
Yes
User who last updated record
*_ACTIVITY_DATE
DATE
Yes
Yes
Date that record was last updated
*_DATA_ORIGIN
VARCHAR2(30)
Yes
Yes
System where data came from, if not Banner
*_VPDI_CODE
VARCHAR2(6)
Yes
Yes
Code of institution to which the data belongs;
default value is BANNER
The _SURROGATE_ID and _VERSION columns are required to support the new user interface
architecture (Project Horizon).The _VPDI_CODE column is being added to support Multi-Entity
Processing. The remaining three columns, USER_ID, ACTIVITY_DATE and DATA_ORIGIN have been
added to complete work started as part of the API effort. All tables will now have these columns.
Which Banner products will Database Extension Utility
affect?













Banner Accounts Receivable
Banner Advancement
Banner Document Management Suite
Banner Finance
Banner Financial Aid
Banner Flexible Registration
Banner General
Banner Human Resources
Banner Integration
Banner Student
Banner Student Aid for Canada
Banner Travel & Expense Management
Banner Solution Centers localizations
o Australasian Solution Center
o California Solution Center
o Canadian Solution Center
o Latin American Solution Center
o European Solution Center
o Middle East Solution Center
o Brazilian Solution Center
Will all tables in my Banner database get these new
columns?
Yes. All tables, including validation tables and SPRIDEN, will get these new columns.
What happens if a column already exists in a table?
If a table already has a column with the name <table>_SURROGATE_ID, the Database Extension Utility
will assume that the table has already been modified and thus, not process that table. If the table does
not have this column, the tool will inspect it for the remaining 5 columns and will only add the missing
columns.
If I already have Multi-Entity Processing (MEP)
implemented on my campus, what impact will Database
Extension Utility have on my environment?
If your campus already has Multi-Entity Processing implemented, applying Database Extension Utility will
not negatively impact your environment. The Database Extension Utility will detect that the _VPDI_CODE
column already exists in some tables and will not add it again. One of the goals of Database Extension
Utility is to have the _VPDI_CODE permanently in the database to ease the upgrade burden for our Multi
Entity Processing customers.
What is the minimum version of the database that I need to
be on in order to apply Database Extension Utility?
Oracle Database 11GR1 (11.1.0.7)
Will there be one sequence for all tables or one sequence per
table to assign the SURROGATE_ID?
There will be one sequence per table. This avoids the latch contention that may occur if multiple high
volume tables share a single sequence.
Where will the new columns be added in the table?
New columns will be added at the end of the existing column list for the table.
Will the required columns be pre-populated?
Initially, in Phase One of the Database Extension Utility release, all columns will be required to be added,
if they do not currently exist, but they will be unpopulated. Phase Two of the Database Extension Utility
release will populate the _SURROGATE_ID, _VERSION and _VPDI_CODE columns.
Will Ellucian address inconsistencies in column names
(USERID vs. USER_ID) as part of Database Extension
Utility?
The Database Extension Utility project will not address inconsistencies in column names. The migration
tool will inspect the tables and add the new columns when exact column name matches are not found.
Inconsistencies found as part of the Database Extension Utility development process will be documented
and will be addressed on a case-by-case basis by the individual product groups as part of future
development.
What impact will the new columns have on my
modifications?
The different types of issues found in the baseline product that require changes to the code will be
documented. These issues will be broken down into root cause, grouped into similar types and patterns,
and included in the Database Extension Utility documentation. Sample resolutions will be provided.
Clients will then be able to use these materials to help identify and address issues in their custom
modifications.
Do I need to run Database Extension Utility against my
custom tables?
Clients will need to apply the Database Extension Utility changes to their custom tables in the following
situations:



If these custom tables are used within a modified baseline form
If these custom tables are a part of a custom form to which the new user interface will be
applied
If your institution plans on implementing Multi-Entity Processing
If you choose to apply the changes to all of your custom tables, there should be little to no impact.
Can we migrate one product or schema at a time as part of
Database Extension Utility, or must all tables be updated at
once?
Clients who opt to install this controlled release will be required to migrate all tables at the same time.
This will ensure that your database is at the minimum standards in order to accommodate future
releases.
How will I know if my database has been extended?
Once your database has been upgraded, you should refer to it as Extended Database. This will let the
people on your campus and Ellucian staffers, such as the ActionLine, know that you have added the new
columns to your database. When the database administrators have completed the upgrade, they will run
a script to add the latest version of the Banner applications that have been upgraded, along with the date,
to a new tab (Extended Database) on the GUIVERS (Display Banner Versions and Patches) form.
For example, currently, your campus is running the following versions: Student 8.4 and General 8.3.1.
Database Administrators on your campus apply the Database Extension Utility scripts, ending with the
script that applies the version number to the Extended Database tab. When you access the Display
Banner Version and Patches form (GUIVERS), there will be a new tab labeled ‘Extended Database’
where you will see General 8.3.1 and Student 8.4 as shown in this sample screen shot.
What are the minimum required versions to go to Database
Extension Utility?
Product
Version
Banner Accounts Receivable
8.2.1
Banner Advancement
8.4
Banner Advancement Self Service
8.5
Banner Degree Works
4.0.8
Banner Document Management Suite
8.3 with patches 8.3.0.5 and 8.3.0.8
Banner Employee Self-Service
8.4
Banner Enterprise Identity Services
8.1.3
Banner Faculty and Advisors Self Service
8.5
Banner Finance
8.5
Banner Finance Self Service
8.4
Banner Financial Aid
8.10
Financial Aid Self Service
8.10
Banner Flexible Registration
8.5.1
Banner General
8.4.0.2 with patch 8.4.1.1
Banner HR
8.4
Banner Position Control
8.4
Banner Relationship Management
1.4
Banner Student
8.5
Banner Student Self Service
8.5
Banner Travel and Expense Management
8.4
Banner Web General
8.4
Banner Web Tailor
8.4
Banner Workflow
8.0.1
Institutional Needs Analysis System
8.10
Luminis Channels for Banner
8.3
Luminis Data Integration
8.0.2.1
Luminis Platform
4.3.0.44, build 44 OR 5.0.1.0, build 673
Mass Data Update Utility
8.0.0.1
Australasian Solution Center Localizations
Product
Australian Vocational Education and Training
Management Information Statistical Standard
(AVETMISS)
Department of Education, Employment and Workplace
Relations (DEEWR)
Centrelink Student Concession (CLSC)
Centrelink Concession Card (CLCONC)
Tertiary Admission Centres (TAC)
Commonwealth Higher Education Student Support
Number (CHESSN)
Automated Results Transfer System (ARTS)
Vocational Education and Training (VET)
International Student Tracking (INTTRACKAUS)
Adult Migrant English Program & Language, Literacy
and Numeracy Programme (AMEPLLNP)
XML Import Engine (XIGN)
Version
8.1
8.2.1
8.1
8.0
8.1
8.1
8.0
8.0
8.0
8.0
8.0
Brazilian Solution Center Localizations
Product
Brazilian Ministry of Education Reporting (STUMECR)
Version
8.0
Brazilian Admissions (STUPSEL)
8.1
Brazilian End of Term Procedures (STUFIMP)
8.5
Brazilian Regulatory Procedures (STUREGP)
8.5
Brazilian Accounts Receivable (ARBRA)
8.2
California Solution Center Localizations
Product
California Banner
(CALB) Student
Version
8.5
California Banner (CALB)
HR
8.1.2
Canadian Solution Center Localizations
Product
Banner Student Aid for Canada (BSAC)
Canada Saving Bonds (CSB)
Federal Contract Program (FCP)
Non-Payroll Year End (NPYRE)
Ontario Application Admission Service
(OCAS)
Personal Income Tax Credits Return (TD1)
Postsecondary Student Information System
(PSIS)
Student Educational Tax Credits (T2202A)
Tri-Council Reportings (TRIC)
Year End Reporting T4, T4A (YREND)
Version
8.3.2
8.0
8.0
8.2.0.2
8.5
8.1.1
8.3
8.4.2
8.1
8.2.0.3
European Solution Center Localizations
Product
Higher Education Statistics Agency (HESA)
Version
8.3
Universities and Colleges Admissions System (UCAS)
8.1.1
Student Loan Company (SLC/SAAS)
8.2
Central Applications Office (CAO)
8.1
Graduation Seating Management (GRDS)
8.1
Enhanced Electronic Grade Book (EEGB)
8.0.1
Prospect Self Service (PRPT)
8.0
Programme Catalogue (PROGCAT)
8.1
Attendance Tracking (ATTR)
8.2
Vocational Placements (VOCAP)
8.1
ODS support for UCAS & HESA
8.0
European Credit Transfer System (ECTS)
8.0
International Student Tracking for UKBA (INTTRACK)
8.0.1
European Diploma Supplement (DIPS)
8.0
Bankers Automated Clearing System Direct Debit
(BACS)
Self-Service Engine (SSEN)
8.0
Process Rules Engine (PRGN)
8.0.1
Collaborative Work Module (CWM)
8.0
8.0.2
Latin America & Caribbean Solution Center Localizations
Product
Multi-Currency / Multi-Tax (ARSCMT)
Version
8.2.1
Program Based Registration (BWSBPR)
8.5
General Survey Engine (BWGRSE)
8.5
Teaching Evaluation (BWSTESS)
8.5
Documentos de Venta (Sales Documents) (ARSSDC)
8.2
Chilean RUT (STURUT)
8.5
Accounting by PIDM (FINACP)
8.5
Tax Withhold (FINTXW)
8.5
Inflation Adjustments (FINIAJ)
8.5
Investment Under Budgets (FINIUB)
8.5
Accounting Interface by Program (FINAIP)
8.5
Accounting Books (FINACB)
8.5
Deferred Income and Expenses (FINDIE)
8.5
Middle East Solution Center
Product
Flexible Working Week (FWW)
Version
8.3
Annual leave
8.0
Airline Tickets
8.0
Who should think about applying Database Extension
Utility?
1. Those who plan to implement Multi-Entity Processing
2. Those who would like to be an early adopter of Banner 9/Student Horizon
Why is Database Extension Utility a controlled release?
Database Extension Utility touches every table in the Banner database so we want to make sure
that we are aware of who is attempting to apply it and work closely with you to ensure success.
We did have customers participate in Beta tests with us, but we would still like to work with a
few customers to get them live before we roll it out to all customers.
Update September 30, 2011 - As of September 30, 2011, Database Extension Utility is no
longer a controlled release; it has been made Generally Available via the Customer Support
Center.
How do I obtain Database Extension Utility?
If your institution meets the above requirements and would like to obtain the release, please submit a
Service Request via the Customer Support Center. When submitting your request use Product Line =
Banner; Product = General; Module = Database Extension Utility; Product Version = 8.0.
Update September 30, 2011 - As of September 30, 2011, Database Extension Utility is no longer a
controlled release; it has been made Generally Available via the Customer Support Center.
Which versions of ODS will be compatible with Database
Extension Utility and Banner Student Course Catalog and
Student Class Schedule 9?
ODS 8.1, ODS 8.2.1, and ODS 8.3 are now certified with DBEU, Banner Student Course
Catalog and Student Class Schedule 9, and Banner Faculty Self-Service Faculty Grade Entry 9.0.
For the latest information and additional details on these and upcoming certifications, please see
the BPRA and Banner 9 wiki page on the Business Intelligence Community.