Manufacture Stock Entry values do not balance when using the new Scrap Type in the UI

ERPNext
,
1

We are facing an issue with Manufacture Stock Entries when there are multiple items in the target warehouse.

ERPNext requires one item to be marked as the Finished Good, while the remaining items must be marked as Scrap.

Before Version 15, the workflow was:

  • Mark one item as the Finished Good.

  • Save the document.

  • Mark the second target item as Scrap using the “Is Scrap Item” checkbox.

  • Save again.

This resulted in the Incoming Value and Outgoing Value balancing correctly, with Difference = 0.

However, in the current version, the “Is Scrap Item” checkbox has been removed from the UI and replaced with a Type dropdown (Scrap / Co-Product / By-Product / Additional Goods). Selecting Scrap from this dropdown does not result in Difference = 0.

During my bulk import implementation using a Python script, I found that ERPNext still supports the legacy field is_legacy_scrap_item. When I included this field in the API payload, all imported entries automatically had the legacy scrap checkbox enabled instead of using the new dropdown, and the Incoming Value and Outgoing Value balanced correctly with Difference = 0.

However, when creating the same entry manually through the UI, the is_legacy_scrap_item checkbox is not visible, so it cannot be used.

Because of this, our entire production entry process is currently blocked. This appears to be a bug, and we would appreciate your help in resolving it.

2

I am assuming you don’t have a BOM in this case?

3

Yes, we dont have BOM

4

Fixed here

Will be available to use with the next release

5

Okay, so when is this expected to be released? Our production entry process is currently blocked because this is the workflow we use daily through the UI. The API-based bulk import works correctly Difference = 0 is achieved with one Finished Good item and the remaining items marked using the legacy scrap checkbox. For the time being, should we continue using the API for these entries, or would it be acceptable to enable the is_legacy_scrap_item checkbox in the UI through a Client Script for manual entries until the fix is released?

6

It will be released in today’s update.

For the time being you can use the client script.