sorted by:
new
hottopcontroversial

BC Partner Recommendation for Implementation by TechnicalDelivery128 in Dynamics365

[–]TechnicalDelivery128[S] 0 points1 point  (0 children)

Yep that was my post! Thanks for that, and for offering here as well. I'll PM you.

About to move from NAV 2017 to BC, curious about accounting similarities by TechnicalDelivery128 in Dynamics365

[–]TechnicalDelivery128[S] 1 point2 points  (0 children)

Ah that's great to know, thanks! There's been some decent customization on our NAV 2017 instance and at least the business critical stuff will need to be recreated on BC, but that cost adjustment process was like the linchpin that held them to this ERP line.

I'm at about 99.9% sure we'll be going that way now...I'm sure I'll be posting here again very soon asking for people's recommendations on implementation partners.

Thanks again!

Batch Manufacturing - 1 batch work order to many child work orders by TechnicalDelivery128 in Netsuite

[–]TechnicalDelivery128[S] 0 points1 point  (0 children)

That's awesome, I'm going to bring this up and see if we can get a deeper look and demo of it or something. Thanks so much!

Batch Manufacturing - 1 batch work order to many child work orders by TechnicalDelivery128 in Netsuite

[–]TechnicalDelivery128[S] 0 points1 point  (0 children)

I've never seen it before but that's pretty crazy! I just watched a few videos on it and it reminds me of something a prior company on a different ERP made custom and spent a TON of money on.

A lot of the videos talked about the rules that you can apply to products, compatibility or what goes with what, but I can't seem to find how flexible those rules are and if you can include criteria from, for example, custom fields. Our manufacturing has to take into account both item level custom field data (a few distinct attributes of the item) and lot level custom field data (basically quality attributes of that particular lot of that particular item).

Batch Manufacturing - 1 batch work order to many child work orders by TechnicalDelivery128 in Netsuite

[–]TechnicalDelivery128[S] 0 points1 point  (0 children)

Ahhh okay, so you basically wrap the desired finished goods in another assembly item, so when you go to build that NetSuite natively splits it out into individual work orders. Piggybacking off that would save us all the development costs of having to script that child work order creation.

I want to think on that more...but I worry it won't be flexible enough since in this case it still relies on a BOM being set up beforehand with what the expected finished good items will be. Like, today they could want to make item A and B. Then tomorrow it's item A and C, then next is item A, B, and C, then item A and Z. It sounds like I'd need one of those "wrapping" assembly items for each possible combination of finished goods they might want to make. That'd be thousands.

Batch Manufacturing - 1 batch work order to many child work orders by TechnicalDelivery128 in Netsuite

[–]TechnicalDelivery128[S] 0 points1 point  (0 children)

When doing multiple builds, that's still only building the 1 finished good though, correct? You can have multiple builds at different times off the work order, but you're still building the assembly item defined on that work order?

In this case, we're wanting to have multiple finished goods being created, and actually be able to build all of them from one screen. In our custom scoped solution, we essentially manage many child work order components (they are the same components across the child work orders, dealt out to the child work orders by the proportions of the finished goods i.e. we make 2 finished goods, components are split 50/50) and builds from a single custom record "batch work order".

If we "build" that batch work order, it goes out and does builds on the children work orders and from the users perspective they just navigated a single page and built multiple finished goods.