Yes, you can create a work order (not a BoM) with released product = Component. This is meanful for rework as explained in a previous post https://sagecity.na.sage.com/support_communities/sage_erp_x3/f/sage-x3-general-discussion-forum/108213/material-rejection/299755#299755

Cost increase, traceability is updated.

Julien, why not upgrade the BoM and let it have this case reflected??

You can't add the parent product as component. This will lead to infinite loop when running standrad cost calculation of MRP processing. So there is a control that forbid you to do it.

At best you can create a dedicated BoM code with no component to ease the WO modification.

Got that Julien, but SAGE EM could have a special BoM for these cases. Look, this way, a BoM without components means that you will not have the possibility to allocate the component, which is clearly a limitation... One way or the other it will be fun and practical to have this "product as component flag" and update the script to calculate the cost in order to avoid the infinite loop. Just suggesting. Finally, thanks, we are using your suggestion and it works, without allocation, but it works.

You are right.

As mentioned in a previous post: this is a recurring customization we are doing (when controlling the related BoM code cannot be processed for costing or MRP)

Please vote on the related ideas to support it: sagecity.na.sage.com/.../rework_a_product_so_that_it_can_consume_itself

Julien, created a new discussion regarding this discussion, but now https://sagecity.na.sage.com/support_communities/sage_erp_x3/f/sage-x3-general-discussion-forum/122896/production-tracking-message-while-trying-to-validate-the-tracking-this-component-has-already-been-produced-for-this-wo

If we consume and then produce the same product no problem. Now we have a situation where we want to consume, produce and then consume again the same product, the second time we try to consume, when validating it gives us the message the product cannot be consumed in the same wo where it was produced...

I am not familiar with such control. I don't understand the reason to forbid you to do an additional tracking. As a workaround did you try to set component B on another BoM sequence? Or tracking compnent B as an unplanned component?

Hi Julien,

I'm Martins de Almeida 's co-worker and we found a workaround embedded in MFGLIB.src. There's an entry point called CTLMATISS(GPE=1), that allows us to validate the product consumption as we wanted.

Thank you.

Well done!