Skip to main content
Solved

Scrap Reporting

  • January 24, 2025
  • 4 replies
  • 79 views

Hello, we are trying to accomplish the following in our system:

  • Track material and product scrap/cycle count adjustment by part number, lot, scrap code/reason, cycle count reason.
  • Track defects (production scrap) in sortable fields and down to material or defect code. Entering scrap (and reporting) allows to report by component, sub-assembly or finished product level.
  • Track scrap per stock item

There are a few methods that we know of, but each has it’s drawbacks from our perspective, summarized below. Does anyone have suggestions for the best approach to overcome the issues noted? There may be some gaps in the procedures outlined as we are new to the system.

 

Method 1: Scrapping Against the Production Order

These are the general steps as we understand them, please confirm or correct as needed:

  1. Scrap action in the BOM must be set to “Write-Off” or “Quarantine”
  2. In the Move transaction within the production order (such as op 010 to 020 in our case), you can enter quantity scrapped, reason, and quantity to proceed.
    1. This is tracked as a WIP adjustment
  3. Production preferences can be set to include scrap in completions, so the production order can be closed as long as scrap + made = planned.

These are the potential issues we see with this method, please let us know if these are not true or there is a work around:

  • Standard cost of the part increases due to the increased scrap. Is this true even if the “Write Off” and “Quarantine” is tied to a different GL account?
  • It may be hard to understand which portion of a stock item lot was accepted and which portion was scrapped.

 

Method 2: Using Materials and Issues Transactions

These are the general steps as we understand them, though we are rusty on this method, please confirm or correct as needed:

  1. A negative materials transaction is made to pull a component off of the production order.
    1. This automatically creates an issues transaction, however there is no way to edit this to specify a reason code.
  2. An issues transaction is made to assign the scrap code. This seems like a duplicated effort to 1a.
    1. This only indicates one location and is reflected accordingly, but it is otherwise unclear where it is going to or coming from.

In line above are the potential issues we see with this method, please let us know if these are not true or there is a work around.

 

Method 3: Create a Scrap Warehouse/Location

These are the general steps as we understand them, please confirm or correct as needed:

  1. Move items to this location, either as part of the negative materials transaction above or with a transfer.

These are the potential issues we see with this method, please let us know if these are not true or there is a work around:

  • These parts sit in the scrap warehouse forever, despite being in a landfill somewhere untracked.
  • This shows a sum of all the materials there, it does not show how much was scrapped and why. For example if 5 parts were scrapped on day 1 for reason X and 5 parts were scrapped on day 2 for reason Y, it just shows 10 parts in the scrap location.

 

Thank you in advance for any insight you can provide!

Best answer by dgodsill97

Quarantine and Write-off subtract the cost of the scrap from the production order totals so those costs are not included in the product cost.  If you want to report on scrap, you can create a GI using the information from AMMTran here: https://help.acumatica.com/Help?ScreenId=ShowWiki&pageid=1ce567e9-7d64-4f0d-aa14-d894a35a8fc3 Note the transaction types of XSQ and XSW.

 

If a material is defective, create the negative Materials issue and specify a non-available location.  Once in the non-available location the item must be dispositions - either returned to the vendor or scrapped out.  You can create a GI to show the items it the non-available location as a tickler for whomever will return or dispose of the items.

View original
Did this topic help you find an answer to your question?

4 replies

Forum|alt.badge.img+3
  • Varsity I
  • 225 replies
  • Answer
  • January 24, 2025

Quarantine and Write-off subtract the cost of the scrap from the production order totals so those costs are not included in the product cost.  If you want to report on scrap, you can create a GI using the information from AMMTran here: https://help.acumatica.com/Help?ScreenId=ShowWiki&pageid=1ce567e9-7d64-4f0d-aa14-d894a35a8fc3 Note the transaction types of XSQ and XSW.

 

If a material is defective, create the negative Materials issue and specify a non-available location.  Once in the non-available location the item must be dispositions - either returned to the vendor or scrapped out.  You can create a GI to show the items it the non-available location as a tickler for whomever will return or dispose of the items.


jdobish
Pro II
Forum|alt.badge.img+2
  • Pro II
  • 232 replies
  • April 8, 2025

There are some strange things that happen with scrap costing based upon the SCRAP ACTION. It is my recommendation that everyone utilizing scrap options and multiple operations review their costing and make sure that the cost of goods is going in to the system as expected. Based upon how you enter these numbers, the costing can be significantly inflated.

There are many times in the real world when someone will identify scrap at a later time, after the completion of an operation, but they don't want to have to go back and remove all pieces just to get that one in the system. The assumption would be that when you scrap the part, you put in the operation, and it would take only the costs associated with that unit, not the combined cost of all units up to that point.

With multiple operations, you have to remove all of the quantity first before applying scrap. The system wants either everything or nothing, it does not pull the costing per piece unless everything is accounted for.

i have attached a workaround for scrap costing on multiple operations. 


Forum|alt.badge.img+3
  • Varsity I
  • 225 replies
  • April 8, 2025

Acumatica does progressive scrap using the added value for each operation - you can see the operation added value on the Production Order Details Total tab.  The cost of operation scrap is the valued added cost of the operation at which the item is scrapped plus any prior operations provided your valuation method is not standard cost.  For example, operation 10 cost (labor, material, overhead, etc.) is $10.00 per unit, operation 20 adds $5.00 of just labor per unit, and operation 30 add another $15.00 of material, labor, and overhead.  If I scrap at:

  • operation 10 my scrap cost is $10.00
  • operation 20 $10 from operation 10 and $5.00 from operation 20 for a total of $15.00
  • Operation 30 $10 + $5 +$15 = $30.00

The scrap also adjusts the qty remaining of the current operation and all prior operations the assumption being you have to go back to the first operation to fulfill the production order.

Progressive scrap is method most used when you what to know what the true cost of scrap is by operation, i.e., the more added value from each operation the more the scrap costs.


jdobish
Pro II
Forum|alt.badge.img+2
  • Pro II
  • 232 replies
  • April 8, 2025

@dgodsill97 While that is true, if you try and post the scrap pieces after you have already done some qty on the operation, there are some strange results. I will send you an email regarding the case that was open regarding that. 


Reply


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings