Lisa Margach

Apprenticeship Units Rule Violations

Created

None

Hi All,

I hope someone can please help, we are trying to process our first cohort of apprenticeship unit learners who are due to start in Sept, but we need them to show in DAS to process their applications (and we cannot add app units manually).

I have spoken to our MIS provider and they have said everything is correct in our system, I have checked the provider support manual and believe everything is coded correctly, and raised a ticket with the helpdesk a few days ago which I am waiting for a response on.  

If anyone is also having issues or can advice on the below I would appreciate any help.  Thanks

We are getting the following rule violations:

AgreemId_01 FundModel=39|AimType=1|DateEmpStatApp=01/07/2025|EmpStat=10|AgreemId=| An Agreement Identifier must be returned for this funding model
LearnAimRef_156 FundModel=39|LearnStartDate=01/09/2026|LearnAimRef=ZPROG001| The Learning aim reference is not valid in the LARS database for this Funding model and this Learning start date
LearnAimRef_160 LearnAimRef=ZPROG001|FundModel=39| The aim must have GROWTH_SKILLS_SHORT_COURSES Validity category in the Validity table in the LARS database.

Replies

No one has replied to this post.


Steve Hewitt

Looks like the problem is that ZPROG001 does not have Growth Skills Short Courses as a validity type...

https://submit-learner-data.service.gov.uk/find-a-learning-aim/LearningAimDetails/Funding/ZPROG001?academicYear=2627

So, you're not doing anything wrong, it's just the set up isn't right at their end. At least 156 is just a warning, but doesn't help when 160 is an error...

Lisa Margach

Thanks for your help with this Steve, makes total sense the errors I was getting, although not great they haven't updated it, but hopefully it will be in the update tomorrow and all will be good again!  Thank you

Steve Hewitt

Hi Lisa

Apparently, you should find these rules have *both* been moved to warnings on SLD for the time being, so you should be able to submit.

Lisa Margach

Thanks for the update on this, I will give it another try and keep everything crossed they clear.  Thanks again Steve

Jo Braithwaite

Did you give it another try? Interested to know if your errors have been removed? I have submitted this morning and still not working!

Lisa Margach

Hi Jo, 

Sorry it isn't working for you, but pleased it isn't just me having this issue.  It is still not working.  I have just had a reply from the DWP helpdesk and they don't know why the error is triggering and have referred it to their ILR technicians to review and come up with a solution.  If I hear anything else on this I will let you know.

Jo Braithwaite

Hi Lisa,

Thank you for the update! I have been staring at my laptop in despair! I will await further comms :)

Lisa Margach

I have just had a reply to say they moved 156 to a warning, which Steve helped with yesterday so we knew that, but they are looking at error 160 now so I am hoping it will be something they can fix, or just tell us what to do if it is us!!   I will let you know when I hear anything else :)

Steve Hewitt

Hmmmm, I thought 156 was *always* a warning? Looks like it from the validation rules spreadsheet...

Definitely no change on ZPROG001 though which would be the "proper" fix...

Lisa Margach

Hi Jo,

I have an update, but I am afraid it is not good news, they have come back and said they are aware it is an issue now, they are investigating a fix, but this might not be done until R02, so said to continue with R01 as normal and they will correct any funding required in R02.  Although not great this would be ok if we didn't need to get the learners fully processed through to show on DAS as we cannot do manual applications on there.  I have asked if they can change this to a warning as well, but presume if they could have done that they would have already :(

Steve Hewitt

I thought we could still do manual additions on AS (they've not implemented the 1 August hard close for Apps), or does that not apply to Units?

Lisa Margach

Unfortunately it is for apps only, there isn't an option for units, they put them on ILR submission only which does not help :( my concerns about not being able to process them have been logged!

Jo Braithwaite

In reply to Lisa Margach · View original comment

Hi Lisa,

Great...but not great! Thank you for coming back to me. I having everything crossed they can fix before close next week.

stephanie.langton

Hi Lisa, 

We are having the same issue, did you get a response on this one:  

AgreemId_01 FundModel=39|AimType=1|DateEmpStatApp=01/07/2025|EmpStat=10|AgreemId=|

An Agreement Identifier must be returned for this funding model

 

156 & 160 have been updated to warnings but we are still getting the above error which is preventing us from updating the ILR.

 

Thanks

Lisa Margach

Hi Stephanie,

It is great 150 & 160 are warnings now, but we are also still having the same issue with the agreement ID.  We have been able to narrow it down that it isn't being included in the xml download from our MIS database, that field is currently blank even though we have data in the ILR.  We are currently talking to our MIS provider about it, hopefully its the same for you and an easy fix!

Thanks

stephanie.langton

In reply to Lisa Margach · View original comment

Hi Lisa,

That is exactly the same as us - we've raised it with our provider too! I'll keep you updated if I hear anything back.

Lisa Margach

Thanks, at least we aren't alone, would you mind saying who your provider is, I am just wondering if it is the same company as us, but no problem if you aren't able to say.  Also if I hear anything I will let you know.