Cannot resolve Planned End date change

From Thursday 10 December, feconnect will be replaced by ESFA Communities.

Feconnect is being replaced by a more robust, accessible service. ESFA Communities is now live and so feconnect will be read only from Thursday 10 December 2020. From this date it will not be possible to create or reply to topics or posts. Feconnect users will need to create a new ESFA communities account to post, reply or subscribe for email alerts.



Home Forums Data issues Cannot resolve Planned End date change

Tagged: , , , , ,

This topic contains 10 replies, has 3 voices, and was last updated by  robS4S 1 year, 1 month ago.

Viewing 11 posts - 1 through 11 (of 11 total)
  • Author
    Posts

  • robS4S
    Participant

    We have identified through FRM05 a Learning Planned End Date administration issue.

    But by following the guidance in the
    Monitoring the funding rules 2018 to 2019: reports user guide

    We end up with a R99 The learner must not have more than one programme aim at the same time
    (from the SLD, FIS 2019/19 returns R99 and R20)

    This seems to be because the guidance requires the existing programme to have an Actual End date of 1 August 2018 and the new programme to have a Start date of 1 August 2018.

    Has anyone had to do this jiggery-pokery and got it to work?

    Or should I just set the start date to 2nd August 2018?

     
    #397641

    robS4S
    Participant

    I have checked again and again can not see any other anomalies

    LearnAimRef 60142327 AimSeqNumber 1
    LearnStartDate 2017-09-18
    LearnPlanEndDate 2018-12-03
    LearnActEndDate 2018-08-01
    
    LearnAimRef 60304650 AimSeqNumber 2
    LearnStartDate 2017-09-18
    LearnPlanEndDate 2018-12-03
    LearnActEndDate 2018-08-01
    
    LearnAimRef ZPROG001 AimSeqNumber 3
    LearnStartDate 2017-09-18
    LearnPlanEndDate 2018-12-03
    LearnActEndDate 2018-08-01
    LearnDelFAMDateFrom 2017-09-18
    LearnDelFAMDateTo 2018-08-01
    AFinDate 2017-09-18
    
    LearnAimRef 60142327 AimSeqNumber 4
    LearnStartDate 2018-08-01
    LearnPlanEndDate 2018-09-18
    PriorLearnFundAdj 8
    LearnActEndDate 2019-05-31
    
    LearnAimRef 60304650 AimSeqNumber 5
    LearnStartDate 2018-08-01
    LearnPlanEndDate 2018-09-18
    PriorLearnFundAdj 8
    LearnActEndDate 2019-05-31
    
    LearnAimRef ZPROG001 AimSeqNumber 6
    LearnStartDate 2018-08-01
    LearnPlanEndDate 2018-09-18
    PriorLearnFundAdj 8
    LearnActEndDate 2019-05-31
    LearnDelFAMDateFrom 2018-08-01
    LearnDelFAMDateTo 2019-05-31
    AFinDate 2018-08-01

    Original start date was 2017-09-18
    Incorrect Learning Planned End date was recorded as 2018-12-03
    Actual planned end date as stated in all supporting documentation is 2018-09-18
    Learner withdrew after continuing until 2019-05-31

     
    #397652

    robS4S
    Participant

    Changed all the 1 August 2018 start dates to 2nd August 2018 and all the errors went away.

    Documentation clearly states;

    If the planned end date has been identified after R14 as being
    significantly incorrect you must:
    Set the Completion status to code 3 ‘withdrawn’ and
    complete the Withdrawal reason using code 40 ‘Learner has
    transferred to a new learning aim with the same provider’.
    Record a Learning actual end date of 1 August 2018.
    Record a new learning aim with the same Learning aim
    reference and a Learning start date of 1 August 2018 and the
    correct Learning planned end date. Record this aim as a
    restart (Learning Delivery Funding and Monitoring Type =
    RES), and complete the Funding adjustment for prior learning
    field with the percentage of learning that is still to be delivered

    any advice?

     
    #397658

    Ben.Feighery
    Participant

    Hi Rob,
    My advice would be to put back ALL the start and planned end dates to exactly what they were on your final 1718 submission, they should not be changed directly in the way you are trying to.
    If you have found that there is a significant issue with the planned end date then the only way you can really change it in the data is to stop the learner and restart them with the correct date in this year, however there are a number of risks with that and in my opinion it is better to accept that the mistake was made in 1718 that can’t be changed rather than try to mess around with the data outside of year and end up with issues such as double counting in your QAR or under/over claiming funding due to OPP value changes.

    Ben F.

     
    #397710

    darrenvidler
    Participant

    For apprenticeships my understanding is that you can set the start date of the new aim to 2nd August and code it as a restart.

     
    #399282

    Ben.Feighery
    Participant

    Hi Darren,
    Do you mean that you would close down the old apprenticeship at the 1st August and put a restarted apprenticeship programme on for the 2nd August?

    If so then that is a possibility but it does lead to a number of issues in the data later. The ESFA have never really addressed this issue in the coding, it wouldn’t be a transfer as they are not moving to a new aim and it couldn’t be coded as a break in learning as there is no break, so you are left with a withdrawal and a restart. I haven’t come across any MIS systems clever enough to recognise this sort of situation in their internal reports so as an example, your internal QAR rates would drift away from the published ones any you end up having to explain the differences again and a gain over the years.

    Ben F.

     
    #399298

    darrenvidler
    Participant

    Hi Ben,

    Not the full apprenticeship, no. The guidance suggests stopping the aim at 1st August and adding a new aim for the same learning aim with a start date of the 1st of August – it then details that, for apprenticeships, a start date of 2nd August for the new aim would be acceptable.

    Darren

     
    #399300

    Ben.Feighery
    Participant

    That doesn’t work with the programme aim, badly written guidance i’m afraid.

     
    #399304

    darrenvidler
    Participant

    Ah, fair point. I can’t say I’ve tried it myself so good to know.

     
    • This reply was modified 1 year, 2 months ago by  darrenvidler.
    #399308

    robS4S
    Participant

    I have requested guidance from service desk. Will update when I get something.

     
    #399320

    robS4S
    Participant

    Official response from the help desk

    You are correct to use the start date of 2 Aug to avoid the R99 error.

     
    #405866
Viewing 11 posts - 1 through 11 (of 11 total)

You must be logged in to reply to this topic.