topic Re: PF Batch w "Hold Excess Quantity" - next Batch Quantity is not recalculated in FlexSim Forum

PF Batch w "Hold Excess Quantity" - next Batch Quantity is not recalculated

clairekruppGhafari — Fri, 17 Feb 2023 22:06:55 GMT

[ FlexSim 23.0.1 ]

I am using the Process Flow Batch activity to pull in multiple tokens and produce 4 outgoing tokens representing pallets, each one with a different density. I have custom code to figure out what the density should be for each batch. Any excess quantity on the last token of a batch is carried over and it becomes the first token of the new batch:

The Batch Quantity for the first batch is calculated correctly, and the excess 200 units are carried forward to the second batch, but the second batch uses the same density as the first batch. I have breakpoints in the code, and they are never triggered, which means the Batch Quantity calculation is not being re-evaluated.

I could do the calculation earlier and put the density I want on a label of the incoming tokens, but if the quantity is not re-evaluated, then that will not work either.

Any suggestions?

The model is confidential, but I can send it to the Dev team if needed.

Thanks

Re: PF Batch w "Hold Excess Quantity" - next Batch Quantity is not recalculated

clairekruppGhafari — Fri, 17 Feb 2023 23:31:22 GMT

Update: If I adjust the batch quantities so that I do not have any overflow, and each batch starts with a new token, then the batch quantities are calculated as expected. It must be a problem with the overflowing token only.

Re: PF Batch w "Hold Excess Quantity" - next Batch Quantity is not recalculated

moehlmann_fe — Mon, 20 Feb 2023 08:17:17 GMT

As you say, it seems that the batch quantity is not re-evaluated when a token for an excess quantity is created by the Batch activity.

As a workaround, you can write the target quantity to a label on the token (either when calculating it in the respective field, or beforehand). Choose the option to always release the excess amount as well. Then check if the batch quantity is larger than the target quantity. If so, create an "excess-token" manually and adjust the batch quantity label of the released token.

The excess token entering the Batch activity will correctly evaluate the quantity anew.

workaround_fm.fsm

Re: PF Batch w "Hold Excess Quantity" - next Batch Quantity is not recalculated

clairekruppGhafari — Mon, 20 Feb 2023 17:30:47 GMT

Thanks @Felix Möhlmann I did already find a simpler workaround by just revising my target quantities to be exact units of the incoming token densities, so that there is never any excess, and a new token starts the new batch. I then adjust the outgoing quantities to what they should be after the batch.

Has the error been reported to the Dev team?

Re: PF Batch w "Hold Excess Quantity" - next Batch Quantity is not recalculated

jason_lightfoot_adsk — Mon, 20 Feb 2023 17:33:59 GMT

I've tagged it as a possible bug for discussion.

Re: PF Batch w "Hold Excess Quantity" - next Batch Quantity is not recalculated

clairekruppGhafari — Mon, 20 Feb 2023 17:35:18 GMT

Temporary workaround: I adjusted the outgoing batch quantity to be an exact multiple of the incoming quantities, so that there is never an "excess" token, and the new batch quantity is always calculated because it's a new token coming in.

In my case I have 800 units each token coming in, and I want 5000, 5000, 4000, 2000 going out, so I changed the outbound quantities to 4800, 4800, 4000, 2400, and then corrected them after they had left the batch activity.

Re: PF Batch w "Hold Excess Quantity" - next Batch Quantity is not recalculated

clairekruppGhafari — Mon, 20 Feb 2023 17:35:53 GMT

Thanks @Jason Lightfoot

Re: PF Batch w "Hold Excess Quantity" - next Batch Quantity is not recalculated

jason_lightfoot_adsk — Mon, 20 Feb 2023 20:49:03 GMT

Thank you Claire. We discussed it in the support group and I sent in the example to dev for consideration. Glad you found a workaround or two.

Re: PF Batch w "Hold Excess Quantity" - next Batch Quantity is not recalculated

andrew_o2 — Thu, 23 Feb 2023 22:12:41 GMT

Hi @Claire Krupp, was Felix Möhlmann's answer helpful? If so, please click the "Accept" button at the bottom of the answer. Or if you still have questions, add a comment and we'll continue the conversation.

If we haven't heard back from you within 3 business days we'll auto-accept an answer, but you can always unaccept and comment back to reopen your question.