E1: 51F: Enhancement Request To Store ‘Forecasted Projected Final Amounts’ And ‘Units’ In F51F110
Last updated on MAY 04, 2016
Applies to:JD Edwards EnterpriseOne Advanced Job Forecasting - Version 9.2 and later
Information in this document applies to any platform.
Enhancement request to store ‘Forecasted Projected Final Amounts’ and ‘Units’ in F51F110
This is a request to make an enhancement to the F51F110 table to store the ‘Forecasted Projected Final Amounts’ and ‘Forecasted Projected Final Units’ in the F51F110 table. The current Projected Final (PF) Amounts are displayed in ‘F51FFHA’ and Units in ‘F51FFHU’. These columns are display columns and are not stored. Two large issues with the current structure of calculating the PF ‘on the fly’ that would be mitigated by storing the PF Amounts and Units in the table:
1. Reporting - One of the primary benefits of the Advanced Job Forecasting module is the ability for company management to review and approve the forecast and associated changes to the PF Cost and Revenue prior to committing those costs and revenues to the Job Cost system. Company management will use reports to review and evaluate the PF Cost and Revenue. To obtain the PF Amounts and Units, any report must go to three separate places to determine these values:
a. The existing HA/HU Ledger Type in the F0902 table.
b. The calculations for MOC W, Y and Z need to be performed in the report whenever a report is generated.
c. The calculations for any User Defined MOC must be determined according to the individual MOC.
By storing these values, the system would have one consistent place to locate PF Amounts and Units for reporting.
2. User Defined MOC – User Defined MOC present the unique issue that the value can be determined from multiple places within the system. JDE has previously reviewed this request to display the PF Amounts and Units determined by User Defined MOC and has rejected the request due to the variability of possible calculations of the PF Amounts and Units. There is no way to include the User Defined MOC PF Amounts and Units in a report without calculating that value on every report. It would be much simpler to store the PF Amount and Units which could be retrieved for reporting purposes.
There currently is no way to determine the Projected Final Cost and Revenue on a forecast that includes a User Defined MOC. Additionally, MOC W, Y and Z cannot be included in any reporting without recalculating the Projected Final Amounts and Units relative to those MOC.
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 hundreds of Community platforms