Manufacturing mailing list archives

manufacturing@odoo-community.org

Avatar

Re: ODOO11 MRP multiBom bad production planing

by
faslu
- 17/05/2018 10:33:02
You don't have to complete the MO of B to start MO of B in all cases, You just need the minimum Qty of B to start MO of C.
Also, there are cases we don't need B to 'start' manufacturing of C, we may need C in the last stage. Here also we can start production of Both B and C at the same time.
So it's better we change later.

On Wed, May 16, 2018 at 5:16 AM, jean francois Taille <jf.taille@gmail.com> wrote:
Hi,

I have a problem with mrp that I don't understand...

I have a product A, with a bom containing product B with routing R1

Product B has also a bom containing product C with routing R2.

Product C is a buyable product

if I confirm a Sale Order with product A, I have automatically 2 manufacture orders with R1 and R2.

But the problem is when I planify those MO, they start on the same date....

In reality, product B should be manufactured first and only then product A can be manufactured.

So in the Gantt view, we should have the MO planify with the proper order.

When I launch the planing, all manufacture order start at the same time...

Is there something I missed.

Thanks for your help it is a long time I'm searching ...

reagrds,
Jeff

_______________________________________________
Mailing-List: https://odoo-community.org/groups/manufacturing-6
Post to: mailto:manufacturing@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe




--

Thanks & Regards,


 
Cybrosys
www.cybrosys.com
FASLURAHMAN CA
Python Developer
Project & IT Department
 
faslu@cybrosys.in
+91 494 3015006 / 07
+91 8606827707
cybroopenerp
 
 
Facebook Twitter LinkedIn Google Plus Pinterest Company
 
This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity whom they are addressed.If you have received this email in error please notify the system manager. The company accepts no liability for any damage caused by any virus transmitted by this email.

Reference