15

The budget and forecast frameworks do not work well together yet and should provide the ability to establish a original budget and then forecast over the lifetime of the project to complete. The fundamentals of a project management is to establish a budget for a project. This budget should never change, it is the baseline. The original budget is then consumed over time. The project manager establishes a forecast to complete each month for the project which should be reviewed and approved. These components should form the same framework including data entry, workflow, version control etc. At present, the initial budget is established via one framework which has most of the functionality you would expect. The forecast to complete is established using the legacy framework which is poor - no workflow, forecasts can be deleted etc. This request is to extend the budget framework to include forecast to complete. The budget framework should also allow budgets to be set at a more gradual level if desired i.e. hours or quantity.

STATUS DETAILS
Under Review
Ideas Administrator

Thank you for the suggestion! This has been added to our roadmap and will be considered for a future release.

Regards,

Kim Nelson

Program Manager, Project management and accounting 

Microsoft 

Comments

R

I agree entirely with this - the method of forecasting in AX goes 80% of the way however falls short with regards to approvals etc. I never quite understood why there needed to be a completely different approach introduced for budgeting when it would have been far easier (and - more importantly - less confusing to the user) just to extend the existing framework and enhance it with new features.

Category: Project Resource Management