Please enable JavaScript.

Coggle requires JavaScript to display documents.

Accept or Reject Scrutiny Requests, This should be done with aid of the…

- - - - There may be cases where evidence has not been provided, in which case they can be bulk rejected
      - Cancelled or rejected requests are filtered out in these tables
      - Create a table by running the script in 1_Web_Changes_PupilAdditions_For_DCAMMatching this details website unrecognised students, Send this to DCAM for matching
        
        Two Scenarios occur with these cases
        
        Pupil is matched to an existing student the pupilid of that student is detailed
        
        Student is not matched, a new pupil id is created
        
        Student still requires to meet trigger conditions to be published
        
        Open the 2_Merge_Pupil_Additions script and populate the KS5_MergePupilRequests table with pupils that are required to be merged
        
        ChangeID should be NULL for MergePupilRequests that are required to be processed
        
        Work through 2_Merge_Pupil_Additions script including running SP to merge student additions with existing pupil ids and special cases that can't be handled by the website
        
        If there is more than one record with the same pupil id retain row, this SP will need to be ran in batches
        
        This SP has 3 functions
        
        Pushing exam results to the retained student from the removed
        
        Sets the amendment flags to IN and CL respectively and report year flags
        
        Updating forename, surname, DOB, gender, LAESTAB and SRC_LAESTAB from the remove ID in cases of prev_pub and lack of original data, for each report year
        
        Updates made if the following where criteria is satisfied (((RETAIN.LAESTAB_0 IS null or (RETAIN.LAESTAB_0 = 0000000 and RETAIN.SRC_LAESTAB_0 = 'AO')) AND REMOVE.LAESTAB_0 IS NOT NULL) OR RETAIN.LAESTAB_0 = REMOVE.LAESTAB_0
        
        Review scenarios and requirements and work through/create 3_Non_CE_Manual_Amendments
        
        Changes are typically made to Allocation_Base, this is because when the allocation program is ran it still recalculates Group C Allocation fields (detailed in Allocation_Field_Groups doc)
        
        Remove unwanted 95000000+ Pupil IDs from Allocation file
        
        Run allocations program and output in Portland
        
        1 more item...
        
        Generated through KS5_MergePupilRequests pupilid_remove values