For more information, see Copy forecast model transactions or Delete forecast model transactions. When you delete a forecast, you delete the forecast transactions from a forecast model. Any worker with permission for a forecast form can make revisions without review.Ĭopy or delete – When you copy forecast transactions, you copy the transaction lines of one forecast model to another forecast model. To use forecast reduction, forecast models must first be enabled in the Forecast models form. 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. Because of this, it can be difficult to track the changes. Therefore, it may be difficult to determine which transaction in which subproject caused a reduction to the forecast amount. For example, if a worker is associated with a subproject, the actual transactions for the worker are posted to the parent project. However, because forecast reduction is applied to the highest project in the hierarchy, it provides a limited view of changes in the forecast. With forecast reduction, actual transactions reduce forecast transaction balances. 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.įorecast models can use forecast reduction as the control mechanism for projects.

You can copy the forecast transactions in a model to create a new model, and also transfer the transactions to the general ledger. Forecast models can be designated as submodels for a model, which allows you to forecast by regions, time periods, or departments. A forecast model, which is created in the Forecast models form, acts as a container for the forecast transactions. Project forecasting transactions are based on units and amounts.Įach project forecast must be associated with a forecast model. You can also project how long after you incur a cost that you will invoice a customer. 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. When you use project forecasting, you can enter forecast transactions in forecast forms for each transaction type. Microsoft Dynamics AX provides two methods for projecting and controlling project costs and revenues: project forecasting and project budgeting. For the latest release plans, see Dynamics 365 and Microsoft Power Platform release plans.Īpplies To: Microsoft Dynamics AX 2012 R3, Microsoft Dynamics AX 2012 R2, Microsoft Dynamics AX 2012 Feature Pack, Microsoft Dynamics AX 2012

For the latest documentation, see Microsoft Dynamics 365 product documentation. This content is archived and is not being updated.

Microsoft dynamics ax training cost