(1) Explain your problem, don't simply post "This isn't working". What were you doing when you faced the problem? What have you tried to resolve - did you look for a solution using "Search" ? Has it happened just once or several times?
(2) It's also good to get feedback when a solution is found, return to the original post to explain how it was resolved so that more people can also use the results.
Hello,
I have an issue when I update my resources scheduled for resources with an Original lag. If my resource has a 11days lag (original lag column) and if my activity has only started since 5 days then my Actual Units should be 0 and I should have no Actual Start date. But when I update my schedule, P6 put an Actual start date and so Actual units.
I have the same issue when I update a resource who start to work at the beginning of an activity but finish her work before the end of the activity.
I precise that before the update all the columns seem to be correct (planned, actual, remaining, ...)
You'll find below some precisions about my selected options:
- Activity type: Level of effort activity
- Duration type: Fixed duration and Units/Time
- % complete type: Duration
- Fields Calculate costs from Units and Auto compute actuals are thicked
- In Project Window I have selected the following options: Link budget and at completion for not started activities; Reset remaining duration and units to original; When updating actual units or costs Substract actual from at completion; Recalculate actual units and costs when duration % complete changes; Link actual to date and actual this period units and costs.
Below a screenshot before the update (sorry but I'm working in French language):
Below a screenshot after the update:
Can you help me? I have tried to change some options but this wasn't successfull.
Thank you!
Julie
Printer-friendly version
Send to friend
Ok Now I understand your question the answer is that resource lags are ignored on LOE type of activities.
As I mentioned LOE activities get their dates after the schedule runs through the forward and backward pass. Applying a lag to a resource creates the possibility that the resource would extend beyond the dates of the activity which can not happen.
A work around is to assign a resource curve to the LOE activity which will limit the time that the resource is used on the activity.
Zoltan,
I have no issue with the actual start of the LOE activity. My issue is when I update the resources allocated to this LOE activity with a lag (at the beginning of the activity or at the end). I have no issue with ressources with no lag so I don't understand what's the problem.
Julie
its hard to tell not seeing the predecessors but the information for the level of effort activity is automatically derived from the information of its predecessor and successor.
so if the predecessor of the LOE has an actual start then the LOE will inherit this actual start.
Email: PPadmin@planningplanet.com
Replies