Today when we run Update worker periods with start date = employment start date, if the employement start date is not the start date of a period the system will generate periods after the employement start date. The consequence is the employee has no period for his first few days.
This doesn't prevent timesheet posting but the times entered for these days aren't stored in « ProjPeriodEmpl » table, and of course they can't be seen from the Period status screen of the employee.
Instead this function should generate periods starting with the last period BEFORE the employment start date.
Example: employment start date is November 18th but periods start on 16th and 23rd. Current behaviour is to start with period on 23rd, but it should include the period starting on 16th so that times entered between the 18th and 22nd of November are correctly recorded.