About project forecasts [AX 2012]
Updated: October 2, 2014
Applies To: Microsoft Dynamics AX 2012 R3, Microsoft Dynamics AX 2012 R2, Microsoft Dynamics AX 2012 Feature Pack, Microsoft Dynamics AX 2012
Microsoft Dynamics AX provides two methods for projecting and controlling project costs and revenues: project forecasting and project budgeting.
When you use project forecasting, you can enter forecast transactions in forecast forms for each transaction type. Every attribute that is available for an actual transaction can be used for a forecast transaction; for example, line profitability, line attributes, workers, or descriptions. You can also project how long after you incur a cost that you will invoice a customer.
Project forecasting transactions are based on units and amounts.
Each project forecast must be associated with a forecast model. A forecast model, which is created in the Forecast models form, acts as a container for the forecast transactions. Forecast models can be designated as submodels for a model, which allows you to forecast by regions, time periods, or departments.
You can copy the forecast transactions in a model to create a new model, and also transfer the transactions to the general ledger. Because there is a one-to-one relationship between a forecast and a model, each forecast model makes up a separate budget for a project.
Forecast models can use forecast reduction as the control mechanism for projects. With forecast reduction, actual transactions reduce forecast transaction balances. However, because forecast reduction is applied to the highest project in the hierarchy, it provides a limited view of changes in the forecast. For example, if a worker is associated with a subproject, the actual transactions for the worker are posted to the parent project. Therefore, it may be difficult to determine which transaction in which subproject caused a reduction to the forecast amount. Because of this, it can be difficult to track the changes. We recommend that you create a copy of a forecast model specifically for use by forecast reduction so that you can use reports to view what was originally forecasted.
To use forecast reduction, forecast models must first be enabled in the Forecast models form.
For each forecast transaction that is entered, a forecast model is automatically suggested. The default forecast model is set up in the Forecast area in the Project management and accounting parameters form.
Project forecasts can be revised, copied, deleted, or transferred to a general ledger budget.
Revise – You can make revisions to a forecast transaction in the same forms where the original entries were made.
There is no process control. Any worker with permission for a forecast form can make revisions without review.
Copy or delete – When you copy forecast transactions, you copy the transaction lines of one forecast model to another forecast model. When you delete a forecast, you delete the forecast transactions from a forecast model. For more information, see Copy forecast model transactions or Delete forecast model transactions.
To limit the forecast transactions that you want to be copied or deleted, select specific transaction types and dates. This allows you to copy or delete specific parts of a forecast.
Transfer – When you transfer a project forecast to a general ledger budget, you transfer the forecast transactions of a forecast model to a general ledger budget. You can overwrite any previously transferred transactions in the general ledger budget to which you transfer your project forecast. For more information, see Copy a forecast to a ledger.
Announcements: To see known issues and recent fixes, use Issue search in Microsoft Dynamics Lifecycle Services (LCS).