Cross Record

R_125

Changes to the latest version will be highlighted

View the validation rules glossary of terms

Name R_125
Version 1
Status Active
Category Cross Record
Severity Error
Error message

T Level and T Level Foundation Year component or core aims must have a corresponding programme aim with the same combination of funding model and programme type

Intent

This rule ensures that a T level programme or T level foundation year programme is recorded correctly with the same programme type as the component aims

Guidance

Ensure that there a programme aim is added with a matching programme type as the component aims to ensure the T level or foundation year is recorded correctly

Description

T Level or T Level Foundation Year component aims or core aims, must have a programme aim with the same programme type and funding model

Detailed error condition
Detailed description

T Level or T Level Foundation Year component aims or core aims ( LearningDelivery.AimType = 3 or 5 and LearningDelivery.ProgType = 31 or 30), must have a programme aim with the same programme type and funding model

(error where there is LearningDelivery.AimType = 3 or 5
and
LearningDelivery.ProgType = 31 or 30
and
there is no record of LearningDelivery.AimType = 1 with the same combination of LearningDelivery.FundModel and LearningDelivery.ProgType )

Flow chart R125

Open flow chart in a new window

Flow chart details

Flowchart for 'R125' rule

1. Has a T level programme or T level foundation year component aim been returned?

  • If 'No' then the rule is not triggered

  • If 'Yes' then:

2. Is there a matching programme aim with the same programme type?

  • If 'Yes' then the rule is not triggered

  • If 'No' then the rule is triggered

Change summary

Version 1

The rule has been rolled over from the previous year

Status summary

Current SLD severity

Error

Current FIS severity

Error

Is this rule in FIS?

Yes

Field values

LearningDelivery.AimType

LearningDelivery.ProgType

LearningDelivery.FundModel

Need help understanding some of these terms?

View the validation rules glossary of terms