Is it possible for a [problem] record to exist where it cannot be traced back to the [task] table?

[SB87]

I'm aware [problem] extends [task] and my understanding is that whenever a [problem] record is created (like [incident] or most records that extend [task]) then the sys_id can be traced back to the parent table, [task] in this case.

There has been an occurrence where we have found [problem] records which do not have a corresponding [task] record, but I'm putting this down to poor data quality (data has been moved around in environments). However, I'm after reassurance my understanding is correct.

Can anyone confirm?

Thanks!

[Saurav11 · Accepted solution]

Hello,

Yes your understanding is correct and every problem should have a task. if you see nay problem not available on task just see If the field task_effective_number is populated on that problem or not. If it is empty then that record will not be seen on task.

Please mark my answer as correct based on impact.

[RaghavSh]

Problem is a child table of task, so it should reflect in task as well. 

If it is not there, its surely a data issue.