| Key | Value |
|---|---|
| Table | DS04 Schedule |
| Severity | CRITICAL |
| Unique ID | 1040220 |
| Summary | Is the WBS ID for this task misaligned between the FC & BL schedules? |
| Error message | WBS_ID does not align between the FC & BL schedules for this task_ID (by subproject_id). |
The Data Integrity and Quality (DIQ) check titled "WBS Misaligned Between FC & BL" is designed to identify any discrepancies between the Work Breakdown Structure (WBS) IDs in the Forecast (FC) and Baseline (BL) schedules within the DS04 Schedule table.
The WBS ID is a critical field that should align between the FC and BL schedules for each task. If the WBS ID does not match for a given task, it indicates a potential data integrity issue. This could be due to a data entry error, a change in the WBS structure that was not properly updated in both schedules, or a system error during data import or export.
The DIQ flags any WBS IDs that do not match for tasks found in both the FC and BL schedules by task_id.
To resolve this issue, you should review the flagged tasks and ensure that the WBS IDs are correctly aligned in both the FC and BL schedules. If necessary, correct the WBS IDs in the DS04 Schedule table to ensure data integrity and quality.
This test is being performed to ensure that the Work Breakdown Structure (WBS) ID is consistent between the Forecast (FC) and Baseline (BL) schedules in the DS04 Schedule table. The WBS ID is a critical element in project management that helps in organizing tasks, assigning responsibilities, and tracking project progress.
The severity of this test is marked as 'CRITICAL', which is the highest level of severity. This means that if the WBS ID does not align between the FC and BL schedules for a particular task, it is a critical issue that must be fixed before the data can be reviewed.
The importance of this check lies in its potential to disrupt the entire project management process. Misalignment between the FC and BL schedules could lead to confusion, miscommunication, and errors in project execution and tracking. It could also cause problems during data analysis, as the data from the two schedules would not match.
CREATE FUNCTION [dbo].[fnDIQ_DS04_Sched_IsWBSIdMisalignedBtwFCAndBL] (
@upload_id int = 0
)
RETURNS TABLE
AS RETURN
(
with Tasks as (
SELECT schedule_type, WBS_ID, task_ID, ISNULL(subproject_ID,'') SubP
FROM DS04_schedule
WHERE upload_ID = @upload_ID
), Flags as (
SELECT F.task_ID, F.SubP
FROM Tasks F INNER JOIN Tasks B ON F.task_ID = B.task_ID AND F.SubP = B.SubP AND F.WBS_ID <> B.WBS_ID
WHERE F.schedule_type = 'FC' AND B.schedule_type = 'BL'
)
SELECT S.*
FROM DS04_schedule S INNER JOIN Flags F ON S.task_ID = F.task_ID AND ISNULL(subproject_ID,'') = F.SubP
WHERE upload_id = @upload_ID
)
| Date | Description of Changes |
|---|---|
| 2024-04-30 | Logic adjusted to account for the addition of 'subproject_ID' field. |