This option will allow the user to
submit NSFAS
data to NSFAS in batch. The program will generate a .csv file to be
send to NSFAS, including all students who were awarded money against a
NSFAS bursary and not yet submitted to NSFAS.
The program generates two separate reports, one indicating students
that were validated and
that will be submitted and a second indicating students with
validation errors that will not be submitted.
The
following information for a student must exist on the ITS system and
will be validated:
Biographical information {FBNO-2} / {SREGB-1}
The following address and communication types must exist for the student
The
following
detail will be validated in addition to the biographical data and the
validation we already do on the biographical and address detail.
NSFAS agreed to the following fields being optional for the time being,
but it will be good practice if the users to identify fields that are
currently not used by the institution and ensure that they will be
captured in future.
The
student must have a NSFAS bursary award for the year
The family structure of the student must exist and the NSFAS means test
done
The bursary code must be linked to a NSFAS donor code
The student must be registered for the year
Connectivity between the institution and NSFAS must be established
The
program also uses the SOD Defined in {FCSM-1b2}.
The SOD is defined for
system BL and the code is FW - Report fatal error if bursary
allocation amount not within Donor Min/Max Range.
The program uses the mnemonic field on {GOPS-21} to determine the qualification type linked to a national level {GOPS-21} External Body NSF External Code Type NLC.
All students that pass validation and are included in the file that is submitted to NSFAS will be updated and the status of the NSFAS application set to‘Data Submitted’
User Selection | Prompt Text * an item between square brackets [ ] is the default answer |
Type & Length |
Comments |
---|---|---|---|
Choose the Report Choice: 1. Only Validation Report. 2. Validation File for NSFAS 3. Final File to be send to NSFAS |
N1 |
|
|
Enter the Year this Report must be generated for | N4 | |
|
|
Enter Start Student Number | N9 | |
|
Enter End Student Number | N9 | |
|
Enter Donor Code or ALL | A8 | |
|
Enter Bursary Code or ALL | A7 | |
Enter Block Code or ALL | A3 | ||
Use User Email Address (Y)es/(N)o | A1 | Whenever a file is created and send to NSFAS for processing, a response eMail is send back from NSFAS. The response eMail address is part of the file that is send to NSFAS and can either be the eMail address of the originating user or an eMail address set up in {GCS2-18} for NSFAS. Which eMail address is used is a user choice according to this input parameter. The SOD’s MU, MV and MX for subsystem BL as set up in {FCSM-1} indicates the eMail Address Type that will be used for the user eMail address from the applicable biographical record. If the address type linked to the SOD does not exist for the user, the program will select the primary eMail address of the user (contact sequence zero). |
Sort Order | Per | Comments |
---|---|---|
Student Number |
System Select | |
---|---|
No special system selection |
|
Processing Rules |
|
---|---|
No special processing rules |
Date | System Version | By Whom | Job | Description |
---|---|---|---|---|
05-Feb-2012 | v01.0.0.0 | Mac Thipe | t179299 | New Menu Option FBNO-4 |
04-Dec-2012 | v01.0.0.1 | Jabu Mokonene | t184600 | Add prompt Users e-mail address. |
20-Dec-2012 | v02.0.0.0 | Jabu Mokonene | t187503 | Add manual on integrator 2 |
10-Apr-2013 | v02.0.0.1 | Jabu Mokonene | t189551 | Manual update add notes on operation in relation to SOD FW on BL |
02-Sep-2013 |
v03.0.0.0 |
Christel van Staden |
t188734 |
Add description for eMail address prompt |