Hello All,
I have had this issue on multiple projects and was wondering if this was a flaw in P6.
Whenever I apply the SF link, the link pulls the successor into non-working period. Here is how the 3 activties are linked.
Activity A <---- Milestone B ----> Activity C
Miilestone B is the main driving milestone. Activity A needs to finish the day before this milestone constraint date. However, even though the same calendar is applied to all 3 activities, Activity A seems to be pulled into non-working time period by Milestone B, which should not be allowed by P6 calendars at all costs. Does anyone know the reason behind this?
I know I will get quite a few here suggesting not to use SF links. I need to create a backward pass schedule based on Activity B milestones which are driven by a client. If you are going to suggest not using a SF link, please also suggest a working alternative to an SF link in this scenario.
Thanks all