Possible issue when the Planned End Date stored for Post-16 Programme of Study is written to the return file
When a school clicks on 'Calculate Programmes of Study' in the Post-16 Programme of Study application (Tools | Academic Management | Course Manager | Post-16 Programme of Study) the Planned End Date for the programme will reflect the latest planned end date for the pupils membership of their courses in Maintain Course. The planned end date stored in the Post-16 Programme of Study is then written directly to the return file when the school clicks on Create & Validate in the census application.
CAPITA have said that on the face of it, writing of planned end dates directly from the Post-16 Programme of Study application seems to be justified in all circumstances, but this has turned out not to be case as this can trigger validation error 2905. This validation is triggered when a pupil has a learning aim with a planned end data that is after the planned end date of the programme to which it 'belongs'.
There are two main ways in which this can occur. Firstly, when calculating the learning aims panel of the census application the school may have opted to use the planned end date reported to the DfE in the previous year's census.
Secondly, once the learning aims panel has been calculated the school may have decided to correct one or more of the planned end dates in the learning aims panel.
Schools can already solve this problem by using the bulk update facilities of the Post-16 Programme of Study application to change the programme planned end date in line with the learning aims planned end date in the Learning Aims panel of the census application.
However, some schools may find this confusing so CAPITA are looking into providing a patch to deal with this issue. The patch would change Create & Validate in the census application so the programme planned end dates are moved forward as necessary to be in line with the learning aim planned end date in the census application's learning aims panel.
The patch will only by absolutely necessary where the issue is triggering validation error 2905.