Fixed Loading Pattern Not Behaving as Expected
search cancel

Fixed Loading Pattern Not Behaving as Expected


Article ID: 143255


Updated On:


Clarity PPM SaaS


In general, when using the Fixed Loading Pattern, ETC will be dropped from dates before the Actual Thru Date.

However there are some scenarios where you can enter ETC in the previous week and it will stay until the post timesheet job runs again.


This can happen when manual financial transactions are created and then imported back to the assignments.

When timesheets post, the actual thru date becomes the first day of the next timesheet week which causes the ETC from the prior week to drop as expected.  Even if you enter ETC in the prior period, the time slice job will drop it.

However, when a manual transaction is imported back the Actual Thru Date becomes the TRANSDATE which is usually not the same as the time period dates.

When this happens the ETC can get entered in the previous week and it will stay there until timesheets post again.

Here is an example:

Timesheet week is Monday-Sunday - Weekly Timescale shows Monday-Sunday

Resource is not on team and not assignment to task.

Create a financial transaction and post it back.

Transdate was a Friday to make actual thru be 1/4 (Saturday midnight)

Team and Assignment get created

Then go to previous week on TSV and enter hours.  

Slices put the hours split between Saturday and Sunday though those as non-working days.


This is because the actual thru date of 1/4 is not the same as the time period actual thru date which is 1/6 therefore the ETC are still in the same week and get squeezed into the days remaining on that week.

This happens when ETC is entered after the fact.  The ETC will be dropped when the next post timesheet job runs as the actual thru date should update then to 1/6 in this example.






Advise users not to enter ETC in previous week if the actual thru date does not match the time period finish date.