Changing Non Serialized Items to Serialized - What breaks?

Comments

2 comments

  • Aaron Horn

    Hey Marcus,

    You should be fine for quoting purposes as that doesn't care if it's serialized or non-serialized.  Same with the packages (Contents & Suggestions) that you've built.  That should all be unaffected.

    Only thing that comes to mind is jobs that are already scanned out, how the Return would work.  I think it's fine since they were scanned out as non-serialized, but I would certainly recommend testing with a model before applying system wide.  I can do some testing in my system if you want some direct help.  Just reach out.

    Aaron Horn
    Flex Consultant (endorsed by Flex)
    aaronjhorn@gmail.com

    0
    Comment actions Permalink
  • Randy - Flex Staff

    Hi Marcus Corona,

    I can confirm, as Aaron Horn points out, that the only (and primary frustration) is existing "out" quantities. I highly recommend only converting a model from non-serial to serialized when the entirety of your stock for that model is in your warehouse. If you convert the model while quantities are still out, the system will think the remaining quantities are "units," but you won't be able to scan them as units because there are no units on the Manifest.

    If you absolutely must convert a model while it has quantities out, you'll probably have to utilize the "Manually Mark as Returned" option on the Return Screen. Note that after using it, you'll want to confirm that your on-hand and allocated quantities for the model remain as expected.

    Copying quotes will work fine, all of your packages will be fine and any virtual items that point to soon-to-be serialized models will continue to work as expected. The only change moving forward, of course, is that you'll be scanning barcodes instead of punching numbers on the keyboard.

    0
    Comment actions Permalink

Please sign in to leave a comment.