Sage 100

Question on Starship and Exploded Kits shipped from Sales Orders: my client does international shipments and has some kits where they need to explode on the Sales Order. As you know MAS has the price on the Kit Parent and the components are all non-chargeable items beneath the kit. They are exploded so that the components rather than the kit parent itself relieve from inventory - all good and fine in the Sage 100 world. However, Starship does not care about kit components - it treats every single line on the sales order as a shipped item and assigns a customs value (Standard Price assigned to the item in Item Maintenance as these items can sometimes ship by themselves) to each component. The sum of the kit component values are greater than the price assigned to the sales kit parent. Starship claims that they can't ignore kit components - they have no facility to do that. Every sales order line is a line that ships in Starship. Yikes - not good for my customer as the declared value only needs to be on the parent item and they do not even want the kit's exploded components to pull into Starship. Anybody ever run into this problem with their Sage client that ships internationally?

How much volume? If it's small can they assemble from the components to a finished good then ship that FG? Yes terrible workaround.

I believe this is a Sage 100 shipping data entry issue. Unfortunately there is no setup option to suppress exploding the kit during shipping data entry. I know, Sage will claim it is because the components relieve inventory during the sales journal update.. I still believe, for many reasons, that there should be an option to suppress the components yet still have the inventory component quantities relieved the same as they do when the components are detailed. Reasons: 1. If it is a kit, why should you have to ""ship"" every component item? .. just ship the parent (kit) item, and, 2. If you have a bar coded pick ticket, the shipper should be able to scan the kit (parent) item only... not have to scan out every component... this is ridiculously inefficient and defeats one of the major advantages of bar coding, and, 3. situations such as @JaneScanlan mentions above.

I like your comments @DougHiggs about the weaknesses of Shipping Data Entry ... all good suggestions on your part. Unfortunately no resolution for my customer.

Am I missing something here or isn't there a way to suppress kits from exploding? The issue is that if you suppress them then people have nothing to pick from? Just trying to read between the lines for the other 138 people who may be reading and scratching their heads.

The issue is that the explode/don't explode is a feature that many people use to build/assemble the parent item using sales order as a work ticket (no WO is required). In those situation, I modify the packing list and invoice to suppress the components from printing. Very handy. Startship does not recognize the component lines and does not suppress.

@WayneSchulz - If you explode the kit on the sales order and pick ticket then it also explodes during shipping data entry. My point is there should be an option to suppress the component detail during shipping data entry and still allow the raw material component backflush when then sales journal is updated.

I think you guys are being soft on V-Technologies. Shipping data entry should display the components, as that's what you're shipping. If the components are packed in separate boxes, the packing list ought to reflect that. The problem is two-fold: users use SO to maintain work orders (instead of WO), and Starship ought to provide the means to not value component items. If V-Tech is maintaining the BOI interface, then they ought to create the logic to interpret the data correctly, so it can be accurate.

Components are not necessarily what you are ""shipping"" - the components are assembled into a finished item, aka the kit parent - it is light assembly that is being done during the picking/packing process. Under customs rules, you cannot have a zero valued line item - each line item has to have a value. Starship should provide an option under their settings to not pull in kit components into Starship. When a line item - which includes kit components - is pulled into Starship it has to have a declared value. Starship does not bring in comment lines or Miscellaneous Charges for obvious reasons as they are not shippable items. There should be an option not to bring in components of an exploded kit into Starship since you are not individually pricing them to the customer; but because Starship is treating them line any other inventory or Miscellaneous item it requires a declared value at the line level. Therefore the customs value does not equal the (Commercial) MAS Invoice value. Very problematic.

I agree Jane. That scenario falls under the ""using SO as WO module"" issue. Starship should either drop the components or the kit item itself. I just started dabbling with the BOI interface and am somewhat disappointed. It's slow and unworkable if you have a couple thousand active SO's.

OK, now I have a little more clarity on this issue. If you use the Starship Link from within Shipping Data Entry, kit components will NOT copy over to the Starship screen. It is only when you use the BOI interface to pull in Sales Orders into Starship that it pulls in all lines - including kit components. V-Tech has confirmed to me that they are working on the enhancement to the BOI so that kit components will not pull in.

LOL... enhancement. Sage speak for bug fix.