- Reported as finished
- Cost accounted
|Original status||Action||Updated status|
|Estimated||run Operations scheduling or Job scheduling||Scheduled|
|Started||run Report as finished||Reported as finished|
|Reported as finished||run Costing||Cost calculated|
|Cost calculated||run Costing and select the End job check box||Ended|
EstimationDuring the "Created" stage, when you create a production order, Microsoft Axapta sets the status of the order to "Created." Run Estimation during this stage. During Estimation, Microsoft Axapta completes the following actions:
- Explodes phantom lines
- Calculates item consumption and creates inventory transactions
- Creates purchases and subproductions
- Calculates route consumption
- Reserves items
- Estimates the cost of subproductions
- Calculates prices
Operations scheduling or Job schedulingDuring the "Estimated" stage, you schedule the order. You can run Operations scheduling or Job scheduling or both, depending on the settings that are configured in the Scheduling method field in the production system's parameters.
- Operations scheduling is the less detailed of the two scheduling types. Use operations scheduling when you want a rough estimate of the duration of the production process.
- Operations scheduling does not split the production route's operations into jobs as job scheduling does. Instead, operations scheduling is limited to scheduling at the operations level.
- When you run operations scheduling, you date-schedule each operation in the production route for the work center that is specified for the operation. Additionally, the duration of each operation is stamped on the production route.
- After operations scheduling is complete, you can date-schedule all operations in the order that the production route specifies. No start times and end times are given for the operations, because the operations are in job scheduling. However, the duration is updated.
- Job scheduling is the more detailed of the two scheduling types. You can use job scheduling together with operations scheduling for more detail. However, you can also run job scheduling by itself.
- Job scheduling generates jobs that are based on operations that you specify for the production route. You can split an operation into the following jobs:
- Queue time before operation
- Setup time
- Process time
- Overlap time
- Transport time
- Queue time after operation
ReleaseDuring the "Scheduled" stage, run Release. When the production order is released, the scheduler indicates that the production order is fully scheduled and is now ready for the actual production process.
If the production has not been cost estimated or scheduled when the production order is released, Microsoft Axapta automatically runs an estimation, and then schedules the production.
After these actions are taken, Microsoft Axapta changes the status to "Released."
StartDuring the "Released" stage, run Start to start the actual production process. You can choose to start all operations or only some operations. You can pick the production order's bill of materials. You can also pick the production order's item consumption and route consumption. You can print a picking list when you run Start.
Note A picking list is a printout of items that are involved in a production.
If production has not been cost estimated, scheduled, or released when you run Start, Microsoft Axapta automatically runs an estimation, schedules the production, and releases the production order for production. However, when you run Start with automatic release, Microsoft Axapta does not automatically print the job, the route card, or the job card. If you want to print these items, you must run the release of production manually.
To cancel a start job that has already been started, reset the production order's status. To do this, click Update, and then click Reset status.
After these actions are taken, Microsoft Axapta changes the status to "Started."
Report as finishedDuring the "Started" stage, run Report as finished to report as finished a quantity of the production order's finished items. When you report a quantity as finished, Microsoft Axapta generates a transaction receipt in the inventory. The status of this receipt is "Received."
When you create a production order, Microsoft Axapta generates an original transaction receipt whose status is "Ordered." This original transaction receipt is recorded or deleted when all the planned production quantity is reported as finished. If you run Report as finished as a final job, Microsoft Axapta gives the production order the status of "Reported as finished."
If the production has not been estimated, scheduled, released, or started when you select Report as finished, Microsoft Axapta automatically runs an estimation, schedules the production, releases the production order, and starts the order. The quantity that is started is the quantity that was reported as finished.
Note By default, the proposed quantity to be reported as finished is the quantity that remains to be reported as finished. If you want to cancel a Report as finished action that you have already requested, reset the production order's status. To do this, click Update, and then click Reset status.
After these actions are taken, Microsoft Axapta changes the status to "Reported as Finished."
CostingDuring the "Reported as finished" stage, run Costing to calculate and to post a production order's costs when the order is reported as finished.
In previous stages, Microsoft Axapta estimates costs by using an estimate of the costs of the time and of the materials. When you run Costing, Microsoft Axapta calculates the production order's actual costs, based on realized material consumption and time consumption. Therefore, you can compare estimated costs and realized costs.
Note For more information, see the "Price calculation" topic in the Microsoft Axapta Help file.
When you run Costing as a final job, Microsoft Axapta performs the following actions:
- Generates a transaction receipt for the production item. The status of this receipt is "Purchased." Microsoft Axapta then deletes the transaction receipts that were generated when you created the production order during the "Ordered" stage.
- Deletes the transaction receipts that were generated when you reported the order as finished during the "Received" stage.
- Automatically reverses previously posted items and works in progress (WIP) in the ledger. All journals that are attached to production are closed, and all journals are posted.
After these actions are taken, Microsoft Axapta changes the status to "Cost accounted."
EndingDuring the "Cost accounted" stage, run Costing again, click to select the End date of job check box, and then finish the production order. After these actions are taken, Microsoft Axapta changes the status to "Ended."
Article ID: 894402 - Last Review: 29 Mar 2017 - Revision: 4