¶ Basic Information
| Key | Value |
|---|---|
| Table | DS04 Schedule |
| Severity | MAJOR |
| Unique ID | 1040180 |
| Summary | Is this hard constraint missing a constraint date? |
| Error message | Hard constraint found (constraint_type = CS_MANDSTART, CS_MSO, CS_MSOB, CS_MANDFIN, CS_MEO, or CS_MEOB) missing a constraint_date. |
¶ 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 Date" is designed to ensure that all hard constraints in the DS04 Schedule table have an associated constraint date.
A hard constraint is a rule that must be strictly adhered to when scheduling tasks. Examples of hard constraints include mandatory start (CS_MANDSTART), mandatory start on or after (CS_MSO), mandatory start on or before (CS_MSOB), mandatory finish (CS_MANDFIN), mandatory end on or after (CS_MEO), and mandatory end on or before (CS_MEOB).
The DIQ check identifies any hard constraints that are missing a constraint date. The constraint date is the date by which the task must start or finish, depending on the type of hard constraint.
If the DIQ check finds a hard constraint without a constraint date, it indicates an error in the data. This could be due to a data entry error, a problem with the data import process, or a system glitch.
To resolve this issue, you should review the hard constraints identified by the DIQ check and ensure that each one has a valid constraint date. If a constraint date is missing, you should add it based on the project schedule and the nature of the hard constraint.
Please note that this DIQ check is designed to ensure the integrity and quality of the project management data. It is important to regularly perform this check to maintain accurate and reliable data.
¶ Why do we check this?
This test is being performed to check for any hard constraints in the DS04 Schedule table that are missing a constraint date. Hard constraints are rules that dictate the start and end dates of tasks in a project schedule. They are crucial in project management as they help in defining the sequence of tasks and their dependencies.
The importance of this check is to ensure that all hard constraints have a corresponding constraint date. If a hard constraint is missing a date, it could lead to inaccuracies in the project schedule, potentially causing delays or mismanagement of tasks. This could further lead to inefficiencies in resource allocation and project execution.
The severity of this check is marked as a MAJOR. This means that while the data can still be reviewed, the issue is likely to cause problems during analysis. It is advisable to fix this issue to ensure accurate project scheduling and efficient project management.
¶ Code
CREATE FUNCTION [dbo].[fnDIQ_DS04_Sched_IsHardConstraintMissingDate] (
@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 constraint_date IS NULL
)