Ben James

DLOCK07 data mismatch

Created

None

So we're having a few issues with this again, and I wanted to get some opinions on whether my theory on resolving it is correct. We've got a few learners who were originally recorded as follows;

TNP1 - 18/10/2018 - 16950

TNP2 - 18/10/2018 - 1050

Total = 18,000

They went on a break in learning, and when they came back the EPA price had been renegotiated to the following;

TNP1 - 23/09/2020 - 16950

TNP2 - 23/09/2020 - 1510

Total = 18460

The training costs were then changed again in October (unaware of the specific situation around this at this moment) and was recorded as; 

TNP1 - 07/10/2020 - 16490

TNP2 - 07/10/2020 - 1510

Total = 18,000 (again)

The latest data mismatch report shows this learner as a DLOCK07 error and it seems to be because of the ILR we returned when he came back from his BIL;

My initial thought was that, despite the fact the prices now once again match (DAS is 18000 and the current ILR is 18000), the price when the learner came back from his BIL (18460) was never reflected in DAS, hence the error above. If I click "Request these details are updated to match the ILR" this would presumably fix this DLOCK because DAS would then be changed to 18460, per the ILR dates above.. but then the learner would appear again on the DLOCK report because the DAS price and the current ILR price would be different, meaning I'd have to click "Request these details are updated to match the ILR" once more? Does this make sense to people or am I completely losing the plot?

Replies

No one has replied to this post.


Martin West

You cannot just change the records you should add new or amend records as required.

TNP1 18/10/2018 16950

TNP2 18/10/2018 1050

TNP1 23/09/2020 16950

TNP 2 23/09/2020 1510

If the entries on the 07/10/2020 were to correct the TNP1 entry on 23/09/2020 you should have just changed the TNP1 amount to 16490 and not added the entries on 07/10/2020

Ben James

Apologies, I didn't mean we had amended the original TNPs, we added NEW ones every time the price changed;

Ok so if we clarify that the 07/10/2020 prices were to correct the 23/09/2020 prices, we can simply overwrite? The only issue is, what do you class as a 'correction'? If the price had simply changed because the EPAO decided the cost needed to be revised, that presumably wouldn't be classed as a correction and instead is just a 'change' - at which point we do what? Does what I originally suggested apply in that situation?

(Edited)

Martin West

Only you know the reason for the 07/10/202 entry but I expect it was to correct the TNP 1 of 23/09/2020 that changed the overall negotiated price.

Ben James

Indeed, and I will clarify with the admin team specifically what the reason was. For arguments sake, if it wasn't a correction, do you imagine pushing the change through to DAS trigger another error, and then pushing that change through get rid of the problem altogether? 

Martin West

It must have been due to a change in the EPA costs as why would you increase the negotiated cost to the employer and then reduce it a few days later.

Ben James

Most likely. Just seems slightly odd to go up in price, then down again.

Steve Hewitt

Does this make sense to people or am I completely losing the plot?

why not both :)

But, yes, feels like you're going to have to push it through twice.

Martin West

losing the plot

Ben James

Steve Hewitt

This is why I'm glad we've got a LIKE button on posts now ;)