Share
Report
506We are hitting an issue with importing a Project Budget using the WBS Estimates "Source".
We find this issue on Cost Projects only.
The error occurs when the WBS task has a scheduled end date beyond today's date, as follows:-
"Invoice date is before project date"
By bringing the task's end date to be today, it fixes the issue.
Is there a "functional" type solution to this which avoid having to artificially set the task dates to today? Why can't they be in the future?
I have outlined a possible dev solution below unless there is HotFix I haven't found on this?
Possible dev solution
Follow through from ProjForecastTransferFromWbs, transferToForecast().
I can see that in the ValidateWrite() of ProjForecastEmpl table it calls setSchedFromDateToSourceActivity() which makes SchedFromDate the same as the task's end date.
InvoiceDate is already typically set to today's date (as the first time it calls initFromTransDate() the project id is not yet set and it treats it like a T&M project type without a project contract because the Project Type enum = zero).
It is subesequently ignored when this same method is called later from setSchedFromDateToSourceActivity() because the Cost project type is not coded for in the if/else block that sets InvoiceDate.
Like Fixed price, Inventment & Internal project types, I could set the InvoiceDate to be dateNull() for the Cost project type and this would ignore the later validation completely.
All responses (
Answers (
