Campus-Based COD Import
Use the Campus-Based COD Import process to import responses from the Common Origination and Disbursement (COD) system for Federal Work-Study (FWS) earnings into the Anthology Student database. The data is transmitted using the Campus-Based Common Record Response Files (CRCB) message class in Campus-Based XML schema version 1.0a.
-
On the Process tab, specify the data selection criteria and manually queue an import job. The queued job will run in the background.
-
On the History tab, review the results of manually queued jobs and scheduled jobs. You can also view details about the records within the batch and access the student profiles.
For more details about the FWS reporting process at the student level, refer to Campus-Based Programs.
Financial Aid Processes File Management
Use Processes > System Administration > Financial Aid Processes File Management to upload and download files in Azure File Storage. This functionality allows you to place files where financial aid processes, such as Application Data Import/Export, Clearinghouse, and NSLDS Reports, expect them. Refer to Financial Aid Processes File Management.
Prerequisites
Important: It is essential for institutions to accurately configure their Federal Work-Study (FWS) Reporting Entity ID and FWS Attending Entity IDs, with COD's assistance if needed. This step influences the entire FWS reporting process.
-
Go to Settings > System > Campuses > select your campus > Financial Aid.
-
On the COD & Packaging tab, in the COD Entity IDs section, specify the values:
Authorizations:
-
Common - Processes - View
-
Financial Aid - Processes - Financial Aid - Processes - Campus Based Import for COD - FWS
Configure campus-level security for Campus-Based COD Import so users see only records for their assigned campus on the History tab:
-
In Settings > System > Campuses > Campus Groups, create or select a Campus Group containing only the campus that the user can access.
-
In Settings > System > Staff, select the staff member and assign that Campus Group on the General tile.
Access
Processes > Financial Aid > Campus-Based COD Import
Import Campus-Based COD Files
Process Tab
The Selection Criteria section of the Process tab enables you to specify the data set for the Campus-Based COD Import file.
-
Select a Calendar Year or accept the session default.
For the first year of implementation, the default is 2022. As new calendar years are added, the most recent or newly added year will be set as the default.
-
Under Fund Source, the only option available is Federal Work-Study.
-
Under Message Class, select one of the following options:
-
Campus-Based Common Record Response Files (CRCB)
-
Campus-Based Web Activity Response Files (CBWB)
-
-
The Campus EDE Path of the user's default campus is displayed.
-
In the Choose From Campus EDE Path list, select a file.
-
If you selected "Campus-Based Common Record Response Files (CRCB)" in the Message Class field, CRCBMYOP files are listed.
-
If you selected "Campus-Based Web Activity Response Files (CBWB)" in the Message Class field, CBWBYYOP files are listed (where YY indicates the year).
-
-
Select Queue Import.
-
The Submit Batch window displays the default Batch Name. You can edit the Batch Name.
-
Select Submit in the Submit Batch window. This starts the background job to process the data and create a batch based on the selection criteria.
The notification “[Batch Name] [Status]” indicates that the process is finished. The hyperlink on the message points to the Campus-Based COD Import > History tab.
History Tab
The History tab displays the results of manually queued jobs and scheduled jobs.
When Enable Campus Level Security On Batches
is turned on in Settings > System > General, the records on the History tab will be filtered based on the logged-in user and the campus groups associated with the user. Record filtering is based on the SyCampusId. Records with a NULL value in the CampusID field will be visible to all users. CampusID = NULL is assigned to records that are not in Succeeded status (e.g., Completed, Enqueued).
A clean-up script ensures that batches are also filtered if they were created before the implementation of the campus-level security feature. The script runs at the batch level per process and assigns SyCampusId values to the records in the batch.
For Application Data Imports, the clean-up script updates student records with a valid ISIR based on the student’s latest active enrollment campus. When a student has multiple enrollments, the script updates the CampusID to the latest enrollment campus even if the student record was originally imported for a different campus.
For Application Data Exports, the clean-up script retains the Campus Name of the original record.
Unmatched student records, failed batches, and error reports for ISIR imports are visible to all users, including users with limited campus access. For users with limited access, the record numbers in the batches grid (top) and details grid (bottom) may not always match.
If the feature is turned off, the History tab will load the records based on the default campus setting (Session Defaults).
-
Review the grid listing the Campus-Based COD Import batches.
When the number of records exceeds 100, the "items per page" drop-down will include the total number of records gathered. Select this option to view all records in a single view.
-
Select the refresh icon (
) to retrieve the current status of the background jobs. -
To remove a batch, select a batch and select Cancel Batch in the grid toolbar.
-
If the job status is Completed, select Retry Batch in the grid toolbar to resubmit the job.
-
For a job with a status of Succeeded, select the link in the Batch ID column to review the records contained in the batch.
The Import Response Notification section is displayed.
-
Review the following details displayed above the grid:
-
Review the record values.
When the number of records exceeds 100, the "items per page" drop-down will include the total number of records gathered. Select this option to view all records in a single view.
| This feature applies to U.S. compliance only. |