Is this in company config or something you set per job?
Iâd have to find it, but I believe is resource group or operation? Itâs a check box called âSplit Burdenâ I believe.
Thanks, I think I recall that having some scheduling implications too maybe??
Either way thanks a ton man. we donât use scheduling right now either so Iâll cross that bridge when I get there.
Ah yes, itâs the split operations I was thinking of.
Thanks man, I will. thank you @Beth as well for spurring the conversation/
I think youâll have to change how the issuing for the raw materials is done. So youâll have to issue less than it calls for on each one (or return to stock). Not a huge deal, but if you are backflushing, it could get a little confusing.
Yes man thatâs what I am trying to avoid as well, but if thatâs the only way to get the variances to come out then okay, weâll weigh that option.
We are all lot tracked so we donât backflush.
Thanks a ton for thinking so critically about this for me.
@Banderson is correct. You will need to figure out how much material to issue to each job and return what you donât use.
Thatâs why I liked co-parts but co-parts has some short comings that need to be corrected.
Thanks everyone. I will try and figure out which practice people want to try out.
You know⌠I wonder what operation batching could do for this⌠I think it might just turn them into co-parts though⌠but maybe the variance posts back to the original operation? Probably not. But may be worth a FAFO if someone else doesnât already know the outcome.
They do turn them into co-parts- I did the batching, the variance results in the same thing⌠all variance going to the part on the jobheader, not each one individually like it should.
Might I respectfully suggest
If only I could record scrap for that co-part youâre throwing away there
Thatâs the thing, the co-part never existed
It existed the moment I received it to inventory at its standard cost. Furthermore, the variances donât get factored till you complete and close the job so I donât see any reason we couldnât count that as âexisting.â I think you were joking, but Iâm still a little hurt by how weird this was programmed
I was just reminded that scrapping of co-parts and nonconforming them has been fixed in the new version. They have added scrapping of coparts to the grid as well as nonconforming them.
Well, I can add that to the list of reasons we should go to kinetic.
thank you!
I was going to look and see if variances were booking the way I want too. I gotta hop in my kinetic environment.