Ashwin,
As you enter time, you see the ETC on the timesheet drop. When you post that timesheet you typically see the assignment s ETC reset.
HOWEVER, with an adjusting timesheet, the rules are different. Because of how timesheets work, when you adjust the time the actual usage is reduced but the ETC IS NOT increased. That s the behavior you re seeing in your case.
I know it doesn t make total sense because technically you lose some usage when you adjust (actuals go down but ETC remains the same) but that s how it works. Basically it s to support external schedulers like Open Workbench or MSP.
Here is a scenario that forces this implementation.
Let s say you open a Clarity project in Open Workbench. While you have it open and are working with it, somebody runs posting and time is posted to one or more task assignments on that project you have open. The ETC on those assignments is reduced. Back in Open Workbench you save the project back to Clarity.
The problem is that the ETC on the assignments from OWB won t be correct anymore because posting reduced it. We need a way to know when this happens.
The decision was to use a date on the assignment called Actuals Thru Date . This date represents the timeperiod FINISH date of the last period posted for that assignment. No remaining work
(ETC) can exist before this date, it s the line between what has been done (actuals) and what s left to do (ETC).
When we reduce ETC, we are basically moving this date forward and adding more time to the total actual work complete.
Okay so now you want to adjust a timesheet. You go into any given timesheet which has already been posted and change the amount of actual work (up or down) and repost. But, the Actuals Thru Date isn t changed, therefore preventing ETC from changing.
This is how it is designed to avoid confusions and to maintain data integrity. Hope this explanation helps you.