Need help on UoM conversion

[Manoj Thandassery]

Hi, 

Can someone help me with this issue:

I buy SawDust in 1kg bags. 

We repack it in small bottles, adding a pinch of this to the bottle. This is then stocked in Stores.

This repacked ' Sawdust in a Bottle' is used as part of a Mfg BoM to make a Science Kit.

Here what I tried:

Set up Sawdust as an item (Raw Material)

Set up Default UoM as KG.

Set up another UoM as 'Pinch' . Conversion factor as 1000. (1000 pinches make up 1 KG).

Set up another item as 'SawDust in a Bottle'

Now when I try to make a BoM for 'SawDust in a bottle'  and add SawDust, it defaults to KG as UoM. I am unable to chose the 'Pinch' UoM. 

Any idea where I am going wrong? I thought I can choose 1 Pinch, and then create a Master Bom for the Science Kit, where 'SawDust in a Bottle' is one of the items.

thanks

Manoj

[Umair Sayyed]

Hi,

You should setup two item codes, with different uom to manage this scenario.

Purchase item:
Sawdust - kg

Repacked item:
Sawdust + pinch - bottle/kg

A repack entry should be made via stock entry using above stated items.

Stock - Stock Entry - new
Purpose - Repack

In bom, repacked item will be used as raw-material.

--
You received this message because you are subscribed to the Google Groups "ERPNext User's Forum" group.
To unsubscribe from this group and stop receiving emails from it, send an email to erpnext-user-fo...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/erpnext-user-forum/874860ff-b9eb-46d6-afcc-7b0b98c9fc37%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Manoj Thandassery]

Thanks Umair

I spent time on this late last night and seemed to arrive at a similar solution except that instead of repack, I did a sub-assembly BoM that adds a small amount of sawdust and a bottle to produce the new item (sawdust in bottle). 

Can't I then use this sub assembly as part of master BoM. Will this approach work as well as the approach you outlined ?

We have about 30-40 of these type of 'repacks' so it's critical that we chose the right approach. So pl educate on pro cons of either approach. One important need is that when we do requirements planning we will need to see the requirement at the level of re packed product and at the basic raw material level. 

Thanks. 

Manoj

You received this message because you are subscribed to a topic in the Google Groups "ERPNext User's Forum" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/erpnext-user-forum/8TFchrecbYY/unsubscribe.
To unsubscribe from this group and all its topics, send an email to erpnext-user-fo...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/erpnext-user-forum/CAJ33fAvSyrHH2LNskBh5%3Dkdu%3DUWhqzXWoQBtk2c4X-5h2KfSQg%40mail.gmail.com.

[Umair Sayyed]

Manoj,

Indeed making sub-assembly BOM for repack item is better and systematic approach, provided raw-material to packed item's conversion is standard. Means same amount of raw-material is consumed each time when repacking.

BOM master should be set in order of production. You should first make BOM for sub-assembly items and then make BOM for finished product. When making BOM for finished product, on selection of sub-assembly item in raw-material table, its BOM will be updated as well.

While doing Production Planning and making Production Order, you will find option to consider or not considering sub-assembly items. Checking a field called "Use Multi-Level BOM" will consider raw-material of sub-assemblies. While unchecking this field will only consider raw-material listed in finished products BOM.

To view this discussion on the web visit https://groups.google.com/d/msgid/erpnext-user-forum/2D2DDB58-C969-45AB-90B9-27014180C4BC%40gmail.com.

For more options, visit https://groups.google.com/d/optout.

--
Thanks and Regards,
Umair Sayyed
www.erpnext.com

[Manoj Thandassery]

Thanks !

Thank you,

Manoj. 

To view this discussion on the web visit https://groups.google.com/d/msgid/erpnext-user-forum/CAJ33fAs2934N-bGBzbUBFXJR-hfAp2xSdwjipi5uoocNmEb3eg%40mail.gmail.com.