¶ Basic Information
| Key | Value |
|---|---|
| Table | DS04 Schedule |
| Severity | MAJOR |
| Unique ID | 9040151 |
| Summary | Is this BCP missing an entry in the Change Control log? |
| Error message | task with milestone_level = 131 - 135 found without DS09 entry where type = BCP. |
¶ 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 "BCP Missing in Change Control" is designed to ensure that all tasks in the DS04 Schedule table with a milestone level between 131 and 135 have a corresponding entry in the DS09 Change Control log table where the type is 'BCP'.
If this DIQ check fails, it indicates that there is a task in the DS04 Schedule table with a milestone level between 131 and 135 that does not have a corresponding 'BCP' type entry in the DS09 Change Control log table. This could be due to a missing or incorrect entry in the DS09 Change Control log table.
To resolve this issue, ensure that for every task in the DS04 Schedule table with a milestone level between 131 and 135, there is a corresponding entry in the DS09 Change Control log table where the type is 'BCP'.
¶ Why do we check this?
This test is being performed to ensure that all Baseline Change Proposals (BCPs) are properly logged in the Change Control log. The test is checking the 'DS04 Schedule' table for tasks with a milestone level between 131 and 135 that do not have a corresponding entry in the 'DS09' table where the type is 'BCP'.
The importance of this check is to maintain the integrity and traceability of all changes made to the project baseline. BCPs are crucial in project management as they document any proposed changes to the baseline, including the reasons for the change, the impact on the project, and any necessary approvals. If a BCP is missing from the Change Control log, it could lead to confusion, miscommunication, and potential issues in project execution and analysis.
The severity of this check is marked as 'MAJOR', which means that while it may not prevent the data from being reviewed, it is likely to cause problems during analysis. It is therefore important to address this issue to ensure accurate and reliable project management data.
¶ Code
CREATE FUNCTION [dbo].[fnDIQ_DS04_Sched_IsBCPMSMissingDS09Entry] (
@upload_id int = 0
)
RETURNS TABLE
AS RETURN
(
SELECT
*
FROM
DS04_schedule
WHERE
upload_ID = @upload_ID
AND milestone_level BETWEEN 131 AND 135
AND (SELECT COUNT(*) FROM DS09_CC_log WHERE upload_ID = @upload_ID AND type = 'BCP') = 0
)