Relationships & Logic
TASKPRED (Activity Relationships)
Relationships: pred_type, lag; live 5670 TASKPRED FS/FF/SS
Columns (Oracle)
| Column | Oracle label |
|---|---|
task_pred_id | Unique ID |
task_id | Successor |
pred_task_id | Predecessor |
proj_id | Successor Project |
pred_proj_id | Predecessor Project |
pred_type | Relationship Type |
lag_hr_cnt | Lag (hours) |
comments | Comments |
Successor is task_id. Predecessor is pred_task_id. Do not flip them.
pred_type values
Oracle's XER map does not list stored strings. MPXJ PrimaveraReader maps:
| Code | Meaning |
|---|---|
PR_FS | Finish-to-Start |
PR_SS | Start-to-Start |
PR_FF | Finish-to-Finish |
PR_SF | Start-to-Finish |
Konnect xD shows an example XER row with "PR_FS". P6 / Primavera Cloud support all four relationship types.
Do not claim SF exists in a given file unless that file was read.
Live file (proved)
XER 23-10-CE-LIVE: 2741 TASK rows, 5670 TASKPRED rows. Types observed: FS / FF / SS. SF is not claimed. See lessons/2026-08-16-xer-23-10-ce-live.md.
Lag
lag_hr_cnt is hours. Which calendar consumes lag is a schedule option (predecessor calendar, successor calendar, 24-hour, or project default). Oracle: lag entered in a unit other than hours is converted to hours using the predecessor activity's calendar.