¶ Basic Information
| Key | Value |
|---|---|
| Table | DS04 Schedule |
| Severity | MAJOR |
| Unique ID | 1040181 |
| Summary | Does this task have a hard constraint without a justification? |
| Error message | Task found with a hard constraint (constraint_type = CS_MANDSTART,CS_MSO, CS_MSOB, CS_MANDFIN, CS_MEO, or CS_MEOB) but no justification (justification_constraint_hard is null or empty). |
¶ What causes this error?
The following text was generated by an AI tool and hasn't been reviewed for accuracy by a human! It might be useful, but it also might have errors. Are you a human? You can help by reviewing it for accuracy! Edit it as needed then remove this message.
The Data Integrity and Quality (DIQ) check titled "Hard Constraint Missing Justification" is designed to ensure that every task in the DS04 Schedule table that has a hard constraint also has a corresponding justification.
A hard constraint is a requirement that a task must start or finish no earlier or later than a specific date. In the DS04 Schedule table, these are represented by the constraint types CS_MANDSTART, CS_MSO, CS_MSOB, CS_MANDFIN, CS_MEO, or CS_MEOB.
The DIQ check is flagging an issue when a task has one of these hard constraint types but does not have a corresponding justification. The justification for a hard constraint is expected to be found in the 'justification_constraint_hard' field of the DS04 Schedule table. If this field is null or empty for a task with a hard constraint, the DIQ check will flag it as an error.
The likely cause of this error is that when the task was entered into the system, a hard constraint was set but a justification for that constraint was not provided. To resolve this issue, a justification should be added to the 'justification_constraint_hard' field for any task that has a hard constraint. This will ensure that all hard constraints in the DS04 Schedule table are properly justified, improving the integrity and quality of the project management data.
¶ Why do we check this?
This test is being performed on the 'DS04 Schedule' table to check for tasks that have a hard constraint but lack a justification. Hard constraints in project management are factors that can significantly impact the project schedule, such as mandatory start or finish dates. The test is looking for instances where these constraints are present (constraint_type = CS_MANDSTART,CS_MSO, CS_MSOB, CS_MANDFIN, CS_MEO, or CS_MEOB) but no justification for them is provided (justification_constraint_hard is null or empty).
The importance of this check is to ensure that all hard constraints in the project schedule are properly justified. This is crucial for maintaining data integrity and quality, as unjustified constraints can lead to confusion, misinterpretation of data, and potential issues in project execution. The severity level is set to 'MAJOR', indicating that while this issue may not prevent the data from being reviewed, it is likely to cause problems during analysis if not addressed.
¶ Code
CREATE FUNCTION [dbo].[fnDIQ_DS04_Sched_IsHardConstraintMissingJustification] (
@upload_id int = 0
)
RETURNS TABLE
AS RETURN
(
SELECT
*
FROM
DS04_schedule
WHERE
upload_id = @upload_ID
AND constraint_type in (SELECT type FROM HardConstraints)
AND TRIM(ISNULL(justification_constraint_hard,'')) = ''
)