My Oracle Support Banner

JDE1: 51: If There Is No “Actual Start Date” In The F51006, The User Cannot Create A New Forecast. (Doc ID 2395163.1)

Last updated on MAY 16, 2018

Applies to:

JD Edwards EnterpriseOne Project Costing - Version 9.1 and later
Information in this document applies to any platform.


On : 9.1 version, Project Costing

If there is no “Actual Start Date” in the F51006, the user cannot create a new Forecast. The documentation says that if there is no “Actual Start Date”, the system will use the “Build Date”. That is not happening.

Being able to enter your own build date and GL date and have a forecast generate.

The issue can be reproduced at will with the following steps:
1. Create a Job Master record.
2. Add accounts and budgets using the P510121
3. Add dates (Planned Start Date & Planned Completion Date) to the Dates/Other tab. (Leaving out the Actual Start Date.)
4. Review dates on the Cost Code Schedule Revision screen.
5. Create a Forecast.
6. Trying to create a forecast using the row exit from the P5111.
7. Note that the results are that the R5111 shows "No Data Selected". (Blank Report)
8. Add the Actual Start Date (to be the same as the Planned Start Date) to the Job Master record.
9. Review the Cost Schedule Revision screen showing the Actual Start Date.
10. Delete then readd the forecast header and run the R5111 (row exit from P5111).
11. Note that the forecast is now created.

The issue has the following business impact:
Due to this issue, users cannot create a forecast leaving the Actual Start Date field blank. The system does not default in the Build Date so the client is forced to create a forecast where the Planned Start Date and Actual Start Date are the same.




To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.