Body
Infographic: Configuring eBanner for Distance Education (DE)
Before a student can be associated with a specific program or major across key Banner forms—such as SAAADMS (Admissions), SGASTDN (General Student), and SHADEGR (Degree/Conferral)—the underlying curriculum structure must be configured.
The configuration relies on a strict parent-child relationship between two primary validation pages: SMAPRLE and SOACURR.
Step 1: Program Definition (SMAPRLE)
Before building curriculum rules, you must first establish the parent program code on SMAPRLE (Program Definition Rules).
When configuring a program code on this screen and checking off "Curriculum Rules," fields such as Program Description, Student Level, College Code, and Degree Code are required. The key to this multi-campus approach to identify program delivery (in-person vs. distance) is to leave the Campus Code field Null. Leaving this field null on SMAPRLE prevents the campus code from being hard-coded at the program level, allowing for flexibility downstream.
Image 1: Program Definition Rules SMAPRLE - BA-BACC Example
Step 2: Curriculum Rules (SOACURR)
Once the parent program code is established with a null campus code on SMAPRLE, you can build the specific child curriculum rules on SOACURR (Curriculum Rules).
SOACURR is where you define the detailed curriculum attributes—including the Campus Code, Effective Terms, Majors, Departments, and Active Modules (Admissions, Recruitment, Graduation, etc.). Because the program-level campus code was left null on SMAPRLE, SOACURR can now host two separate curriculum records for a single program code: one assigned to the in-person program delivery (Campus = WOA) and one assigned to the distance program delivery (Campus = DE).
Image 2: Curriculum Rules SOACURR - BA-BACC Configuration
Case Study: UH West Oʻahu Configuration
Images 1 and 2 illustrate how UH West Oʻahu configured their BA-BACC program to support both in-person and distance-delivered pathways:
-
By leaving the Campus Code null on SMAPRLE, SOACURR successfully maintains two distinct curriculum records under the same program code, using WOA (in-person) and DE (distance) to differentiate the delivery methods.
-
Because both curricula are active across Banner modules, staff can seamlessly select and track the correct pathway for students within SAAADMS, SGASTDN, and SHADEGR.
-
Because the Student Level is directly tied to the active student curriculum, this setup can be leveraged to drive accurate reporting, targeted financial aid packaging, and automatic fee assessment rules.
Multi-Institution Implementation: A Roadmap
For other campuses to adopt this approach, they must establish corresponding SOACURR records to map the DE campus code to their existing programs that are approved for distance delivery.
For example, on UH Hilo's SMAPRLE record for the BA-EXHS program, the Campus Code is already configured as null. Therefore, Hilo is fully primed for this setup.
Image 3: Program Definition Rules SMAPRLE - BA-EXHS
To complete the setup, UH Hilo only needs to build a second curriculum record under the BA-EXHS program code on SOACURR and assign the DE campus code to it.
Image 4: Curriculum Rules SOACURR - BA-EXHS
Once this record is established on SOACURR, UH Hilo can immediately process applications (SAAADMS), manage active student records (SGASTDN), and award degrees (SHADEGR) under the dedicated distance pathway.
Mapping Summary of Program & Campus Codes
The table below illustrates how different UH Institutions use distinct campus codes under a single program code to differentiate between in-person and distance delivery models:
| Program Type |
Program Code |
College Code |
Campus Code |
Level |
| In-person |
CSCI-MSC |
14 |
DE |
G0 |
| Distance |
CSCI-MSC |
14 |
DE |
G0 |
| In-person |
BA-EXHS |
A1 |
DE |
U1 |
| Distance |
BA-EXHS |
A1 |
DE |
U1 |
| In-person |
BA-BACC |
PS |
WOA |
U2 |
| Distance |
BA-BACC |
PS |
DE |
U2 |