COA Guide
Use this workbook to configure Cost of Attendance (COA) items.
Overview
In this workbook, you can define COA items and their attributes.
Workbook Description
The file name for this workbook is COA.csv.
- Field Name.
- Column: Spreadsheet column associated with the field.
- Required?: Denote if you're required to populate the field or not.
- Field Type and Accepted Values:
- String: These are usually alphanumeric.
- Integer: Numeric, a whole number.
- Double: Numeric with places to the right of the decimal.
- Enumeration: List of values.
- Boolean: True or False, Yes or No.
- Groovy script: A logical query using groovy script.
- Date: yyyy-mm-dd format.
- Description.
| Field Name | Column | Required? | Field Type and Accepted Values | Description |
| Item Title | A | Y |
String Alphanumeric ASCII text, up to 255 characters. |
Item Title. Example Values:
Note: You are required to use the same unique Item Titles for
on-campus and off-campus COA items to comply with College
Financing Plan requirements.
|
| Component Title | B | Y |
String Alphanumeric ASCII text, up to 255 characters. |
Component Title. Use freeform text to provide a description for the cost of attendance value. |
| Config Title | C | Y |
String Alphanumeric ASCII text, up to 255 characters. |
Config Title. In the Baseline Configuration, Config_Title is based on multiple values using the CONCATENATE formula in Microsoft Excel. You can use any naming convention you choose, but the Config_Title needs to identify all of the COA Items for a grouping. |
| Enrollment Status | D | Y |
Enumeration List of enumerations:
|
Enrollment Status. To view descriptions, see: Status Definitions and scroll to "Enrollment Statuses". |
| Program Type | E | Y |
Enumeration List of enumerations:
|
Program Type |
| Program Modality | F | Y |
Enumeration List of enumerations:
|
Program Modality |
| Additional COA Components | G | N | Groovy script |
Use this Groovy script to more discretely identity the COA Item. If left blank, the COA values apply to all students with the specified enrollment status, program type, and modality for the given award year. In other words, the absence of a script is synonymous with a "return true". This Groovy script is evaluated whenever Package or Repackage is triggered. For more information, see the Considerations for Configuration section in this topic. DO NOT return a value for both this field and the Cost Value field for the same COA item. |
| COA Component Cost Type | H | Y |
Enumeration List of enumerations:
|
Name of COA Component Item:
|
| COA Item Applicability | I | Y |
Enumeration List of enumerations:
|
Type of Budget Item For purposes of Pell Grant COA calculation, COA Items with a PER_MONTH, PER_CREDIT, PER_COURSE, or PER_TERM Applicability are prorated using the setup in the COA Term Academic Year Guide, and COA Items with a FIXED Applicability are not prorated. |
| Cost Value | J | Y |
Groovy script |
Amount of Budget Item Numeric example values: Do not enter or return a value for both this field
and the Additional COA Components field for the same COA
item.
|
| Aid Year | K | Y |
String Alphanumeric ASCII text, up to 255 characters. Format: CCYY-CCYY Example Values
|
Aid Year associated to Budget Item |
| Prev Item Title | L | N | NA |
Deprecated, used in old version of configuration loader. |
| Prev Component Title | M | N | NA |
Deprecated, used in old version of configuration loader. |
| Prev Config Title | N | N | NA |
Deprecated, used in old version of configuration loader. |
Enable the Configuration in the UI
You do not have to complete any setup in the user interface to enable this configuration.
Required Permissions
You must have a role with the following General Permission(s) through Roles Management in order to view the configuration in the UI.
- Student
Considerations for Configuration
- Regarding Per-term COA versus Academic Year COA, use specific binding in the COA column to make those line items Per-term COA focused.
- Config Title must be unique for each selection group, and a particular
student/package must belong to only one Config Title.
- For example, given any combination of Enrollment Status, Program Type, Program Modality, and Aid Year, if an Additional COA Components (Additional COA Comps) Groovy script is written to capture all students in the School of Nursing, the logical inverse of the script would need to be added to all the other COA rows for that Aid Year to capture all students who do not belong to the School of Nursing.
- This ensures:
- All students being passed to the packaging engine for COA calculation fit in only one selection group.
- Each of the groups must have a unique Config Title so the packaging engine can calculate COA based on a configured set of Cost Values.
Note: If there is no Additional COA Components (Additional COA Comps) Groovy script for any Config Title selection group (combination of Enrollment Status, Program Type, Program Modality, and Aid Year), the corresponding Cost Values apply to all students of that group. If an Additional COA Components (Additional COA Comps) Groovy scripts are introduced for any Config Title selection group, then all COA configuration rows for that Aid Year must have Groovy scripts that include or exclude all students accordingly.
-
Use the Enrollment Status field to configure the Enrollment Status by term based on a student's course load as received from a SAFI integration message. The Enrollment Status calculation is triggered for every repackage, and the Groovy configuration script is run for each individual term to determine the appropriate status.
The Award Packaging process uses the determined term enrollment status when packaging the student for funds. For example, when a student is evaluated the student for Direct Loans, the process ensures that is not less than half time for the term being evaluated.
Here are some examples of Enrollment Status rules you can configure:- When to update the term enrollment status based on the most recent SAFI data for that term.
- When to freeze/not update an individual term enrollment status and ignore the latest SAFI data.
- What the current and future term enrollment statuses should be a term withdrawn student.
- What the current and future term enrollment status should be for a program withdrawn student.
Note: Configuration for Enrollment Status for packaging Pell Grants is done in the FAS Fund Config Configuration Workbook. This supersedes Enrollment Status configuration in the COA Configuration Workbook.
Configuration in the User Interface
The configuration is visible in the Student Financial Planning User Interface if you navigate to the following screens:
The COA is visible in the Packaging Summary and in the COA graphic
Click the icon in the Packaging Summary to view additional Cost of Attendance (COA) and Tuition and Fees information
Understanding How the Baseline Configuration Works
Baseline configuration includes a demonstrable example of how COA configuration workbook will look once completed.
Oracle expects each institution to configure this workbook and not leverage the delivered baseline configuration for any non-testing, non-demonstrable purposes.