Assembly Scrap
You can scrap unusable, partially completed assemblies from jobs and repetitive schedules by moving them into the Scrap intraoperation step of an operation.
Scrap Transactions
You scrap assemblies by moving them into the Scrap intraoperation step of an operation. You can, if necessary, recover scrapped assemblies by moving them out of the Scrap intraoperation step. You can also move assemblies back to the Scrap intraoperation step of the previous operation from the Queue or Run intraoperation step of the current operation if no work has been completed at the current operation. See: Intraoperation Steps.
The system views assemblies moved into the Scrap intraoperation step from the Queue or Run intraoperation step of the same operation as complete at that operation and updates operation completion information, backflushes pull components, and charges resource and overhead costs accordingly.
Costing Assembly Scrap
You can optionally specify whether Scrap transactions require a scrap account or alias using the WIP Require Scrap Account Parameter. If you enter a scrap account or alias as you move assemblies into Scrap intraoperation steps, the scrap account is debited and the job or repetitive schedule elemental accounts, determined by the accounting class, for the accounting class elemental accounts for the cost of the assembly through the scrap operation are credited. This removes the cost of the scrapped assemblies from the job or repetitive schedule. If you do not provide a scrap account, the cost of the scrap remains in the job or schedule until job or period close. If you recover assemblies from scrap, the scrap account is credited and the job or repetitive schedule elemental accounts for the cost of this assembly through this operation are debited. For more information about how assembly cost transactions are costed see: Work in Process Average Cost Transactions and Work in Process Standard Cost Transactions.
Netting Assembly Scrap
For standard discrete jobs, the MRP planning process does not consider assemblies in Scrap intraoperation steps as scheduled receipts, nor does the planning process use these scrapped assemblies when calculating MPS relief. For standard discrete jobs, the planning process deducts scrapped assemblies from the MRP net quantity to determine the available supply. The planning process does not deduct scrapped assemblies from supply on non-standard discrete jobs or repetitive schedules.
Effect of Scrap on Backflush Components
When you move assemblies into the Scrap intraoperation step, Operation Pull components at subsequent operations that would have been consumed by these assemblies are not backflushed. Also, Assembly Pull components at subsequent operations are not backflushed by assembly completions.
You should not expect later moves or completions to backflush components consumed at operations prior to the one where the assemblies are scrapped if these operations are set to delay backflushing until subsequent operations.
For example, if you scrap assemblies at a non-backflush operation that has Operation Pull components, the system does not backflush these components nor does it backflush Operation Pull components consumed at prior non-backflush operations. If you scrap assemblies at an operation that has Assembly Pull components, the system also does not backflush the components. In both cases, the system alerts you that your scrap transactions may result in unissued pull components.
You can use the WIP Material Transactions window to push (issue) the pull components onto the job or repetitive schedule. You can also update your bills and routings to avoid this problem.
See Also
Intraoperation Steps
Operation Pull Backflush Transactions
Move Transaction Parameters
Scrapping Assemblies
