Kevin M said:

You have to enter quantities for that too (somehow).

The "somehow" is what our Reseller created for us because Sage did not have a way for that to happen.

Just for clarification, there is a Parent that appears in Shipping Data Entry but there is nothing physically to scan as the Parent is comprised of the Children all of which must be scanned individually.

Yes but sage invoices the customer based on the parent's quantity shipped so you still must enter a quantity to ship to bill the customer for it if your intention is to bill the customer for the parent since the customer is not billed for the components.

See this example, shipping only components does not increase the invoice amount. Notice how the component does not have a price and therefore does not have an extension. This is how sage 100 handles exploded kit components.

In order to bill the customer, i must ship the parent.

Parent A = Child B + Child C.

In Shipping Data Entry, we scan Child B and erroneously do not scan/ship Child C.

We then go in a tell Sage that we shipped Part A so it gets invoiced.

Sage then automatically marks as shipped Child B and Child C even though Child C was erroneously not shipped.

This will cause inventory to be off and also the customer to be unhappy when they receive their package that is missing Child C even though they were charged for Parent A.

This is a very simplistic example, but some of our kits are 15-20 Children and some of our Sales Orders contain 10-20 different Parents so it would be really easy to miss a Child which is why we scan everything to always double check ourselves and would not want Sage to mark everything as scanned/shipped simply because we say the Parent is scanned/shipped.

Hopefully that makes sense.

Right, for your exact process, that works and your script made it easier for you to achieve the desired results but that may not be required for every one as i've seen kits used differently where only the parent kit item was shipped during Invoice/Shipping Data Entry and they let standard sage functionality ship the components because their bills were set up for this purpose and if the parent kit item was being shipped, then all of the components had already been physically accounted for outside of sage 100 so there was no need to double check the quantity shipped of the components in Invoice/Shipping Data Entry.

The reason i mention integrations is because i have seen at least one that did not properly handle the parent kit item when processing shipments and this would cause the parent kit item to be backordered and NOT billed to the customer. This was caused by the integration only shipping the components because they did not fully understand how sage 100 handles exploded kits.

BENWKBS, can you share that script?  I am having a similar issue as I look at using barcoding and I think I need to script a change to make this work. 

Thank you
Chris