An initial thought would be to have different Routing codes, one using WC K and the other using WC L and program the selection of the Routing code based on the business rules defined.

Frank, it is necessary to maintain plant parameters that will define the min/max kg per component per site and what work center / routing operation is relevant. In my view X3 dont have that. When the sales order is created back to back as a work order is then the rules should be applied.

Braam, I am not suggesting that X3 can do this out of the box.  I am suggesting you can maintain different configurations which X3 does support and create a program that applies the business rules.  The programmer would hopefully find an entry point when the BtB function is called.

Yes. We are aligned. Together with this is the requirement to have a single bill-of-material, where some components is used to make a premix, and the premix is used into the next process to produce the final product. Based on plant configuration the process can differ.

Braam, for this single BOM requirement, use phantoms.  Especially in a premix scenario where you might find yourself unexpectedly having to stock the premix due to a line breakdown, for instance, X3 handles this by allowing you to stock the phantom.  The next work order will first consume the phantom and add components to make the balance.  (It does this in PU8 so check V11/V12 to make sure it still works this way.)

Pierre thanks for the reply. In this scenario the bom is provided by an external specialuzed system used by scientists. This system does not consider plant config and constraints. There could be hundreds of boms and can change weekly. Sending work orders to the plant must also consider specific plant constraints.

I am 100% in agreement with phantoms. Due to the source system providing the boms does not care about the plant config this will have to be handled with integrations of boms.