The Update Definition window can be used to add or edit your update type and code combinations as defined in the Maintain Table Values window. However, there are a number of update types that J1 Desktop modules depend on for certain processes, which are outlined below.
|
The NSC codes should not be deleted because the system must have them to create the NSC data needed for reporting purposes UNLESS your school does NOT do NSC reporting (the Make Use of NSC Functionality checkbox is cleared in the Registration Configuration window). |
Update Type |
Update Code |
Process |
CL |
User Defined |
Updates Classification on the STUD_TERM_SUM_DIVE table |
HR |
User Defined |
Updates Academic Standing (Honors) on the STUD_TERM_SUM_DIVE table |
NSC |
NS1 |
Updates FICE Code on the NSLC_STUDENT_MAST table |
NSC |
NS2 |
Updates Branch Code on the NSLC_STUDENT_MAST table |
NSC |
NS4 |
Updates Foreign Student column on the NSLC_STUDENT_MAST table |
NSC |
NS5 |
The National Student Clearinghouse no longer uses the Grad Level Indicator. They now use the Clearinghouse Class Code to get this information. |
NSC |
NS6 |
Updates Data Block Indicator on the NSLC_STUDENT_MAST table |
NSC |
NS7 |
Updates FERPA Block Indication on the NSC_DEG_VERIF_DETAIL table |
NSC |
NS8 |
Updates Financial Obligation Block on the NSC_DEG_VERIF_DETAIL table |
NSC |
NS9 |
Used by the Populate Transmittal process to calculate the Clearinghouse Class Code using any available table/column you wish |
NSC |
NS10 |
Used by the Populate Transmittal process for validation of the Good Student flag |
NSC |
NS11 |
Used by NSCL_STUDENT_MAST.NSL_ETHNIC_RACE |
OPE |
OPE ID Assignment |
Used to assign this OPE ID when a new Degree History record is created; also used to update all existing Degree History records |
PB |
User Defined |
Updates Academic Standing (Probation) on the STUD_TERM_SUM_DIVE table |
PCP |
User Defined |
Validates if Non-course Prerequisites, Corequisites, and Prohibited Courses are met |
PFD |
User Defined |
Updates PT/FT Status on Student Term Summary by Division (if you select the Use Rules Based Update for PT/FT Definition checkbox in the Registration Configuration window) |
PFN |
User Defined |
Updates PT/FT Status on NSC Registration Transaction (if you select the Use Rules Based Update for PT/FT Definition checkbox in the Registration Configuration window) |
PFS |
User Defined |
Updates PT/FT Status on Student Term Summary (if you select the Use Rules Based Update for PT/FT Definition checkbox in the Registration Configuration window) |
Jenzabar strongly recommends that an Update Type of SAP be used when developing your Calculate Satisfactory Progress rules. Calculating Satisfactory Progress requires three steps with each step depending on the values determined in the previous steps. Therefore, It is strongly recommended that the following three update codes be defined:
Update Type |
Update Code |
Process |
SAP |
SAP1 |
Rule Assignment on SAP History |
SAP |
SAP2 |
Calculate Current Progress (Pass/Fail) on SAP History |
SAP |
SAP3 |
Update Final Progress on SAP History |
Update Type |
Update Code |
Process |
PMT |
PAYPLANS |
Payment Plans Assignment |
The following columns are available for you to define update types and codes: