Lynnette,
I have looked at these two students and 109847 has 3
student_programmes with an enrolment on sequence no 2 while student 112364
has 2 student_programmes with an enrolment against sequence no 3.
If you add the line
AND sba_spr_sequence_no = spr_sequence_no
the duplicates should disappear.
This looks as if it will be a problem for 99/00 programmes as previously we
have mainly had only one student programme.
The above line will probably need adding to many of the scribe reports.
Lena
p.s. did we have problems with sequence numbers being wrong and if so was it
corrected?
The following is my sql
SPR_CA SPR_S_RE SPR_SEQUENCE_NO
------ -------- ---------------
98/99 109847 1
99/00 109847 1
99/00 109847 2
99/00 109847 3
99/00 112364 1
99/00 112364 2
6 rows selected.
SQL> select sba_s_ref,sba_sb_ref,sba_calp_period_code,sba_status,
2 sba_type,sba_spr_sequence_no
3 from study_block_associations
4 where sba_s_ref in ('109847','112364')
5 and sba_type = 'E'
6 and sba_status = 'L';
SBA_S_RE SBA_SB_REF SBA_CA S S SBA_SPR_SEQUENCE_NO
-------- ----------- ------ - - -------------------
112364 M9S3 99/00 L E 2
112364 15PDSC001 99/00 L E 2
112364 15PDSC002 99/00 L E 2
112364 15PDSC999 99/00 L E 2
109847 Y4GF 98/99 L E 1
109847 Y4S6 99/00 L E 3
109847 15PPOC020 99/00 L E 3
109847 15PNMC213 99/00 L E 3
109847 15PPOC999 99/00 L E 3
9 rows selected.
Lena Dunn
MIS
Tel: 0171-691-3455
e-mail [log in to unmask]
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
