Kits and Credits

midnightmidnight Member Posts: 74
We are using Kitting for our Promotional items, and is working as it should. Not maintaining inventory on the Promo Item, and pulling the three items associated with the Promo Item (kit) from inventory when order is shipped. Works great. Now, comes time to do a credit on an order that has the Promo code on it. What it's doing is putting 1 Promo Item back into stock (which we do not maintain inventory on), and not the three items attached to the Promo Item in a kit.

How I came across this was seeing inventory increase against these Promo codes where there should not be any (because of kitting). Should it not work the same way as when it's shipped just in reverse?

Any thoughts?

Thanks

Comments

  • kinekine Member Posts: 12,562
    than you need to use disassembling or how it is called I think... :-k
    Kamil Sacek
    MVP - Dynamics NAV
    My BLOG
    NAVERTICA a.s.
  • davmac1davmac1 Member Posts: 1,283
    I did a kit credit memo mod.
    Much more complicated than you would think, so try to avoid it.
  • midnightmidnight Member Posts: 74
    I'm sure it would be a complicated mod. The thing is, if there is a kitting module that you purchase which we did, it should be able to handle credits. The shipping side works well. The issue I have with disassembly is that it does a negative adjustment for the kit item. According to the MS docs (Technical Whitepaper) on kitting/disassembly it states "The disassembly is processed as a negative adjustment for the kit, and positive adjustments for the item components". We don't want it to touch the kit item, as we do not maintain inventory on them, just the components. Also, we are not doing BOM journals to build the kits. The components are being pulled at time of shipping, with the "Automatic Build Kit" feature.

    We were looking for NAV to handle this right from the credit memo screen.
  • davmac1davmac1 Member Posts: 1,283
    While I sympathize with you, the NAV team decided not to support this feature, and it is stated in the technical documentation.
    It is always dangerous to assume that features are included which is why requirements should be vetted against the software package's features and the cost of all changes defined and added to the product cost.
    Unfortunately, it is not possible to think of everything.
    I had to make the change because of sales tax issues at the component level.
    If this is not an issue for you, then I suggest you receive back the kit and then run journals to disassemble it - or wait until you upgrade to NAV 2013 and see if it handles it the way you need.
Sign In or Register to comment.