Sage 100

 View Only
  • 1.  Anyone found a good work around for this physical

    Posted 09-14-2012 12:30
    Anyone found a good work around for this physical count import issue (see KB article below)? If they'd let us import the same item list to a freeze table (I think that's what we could do prior to 4.4) this wouldn't be an issue. Otherwise it looks like you have to freeze the inventory from the front end - which makes sense, but the client just wants to give me a list and import it. 110-535951 - Physical Count Import Quantity on Hand field is missing.


  • 2.  RE: Anyone found a good work around for this physical

    Posted 09-14-2012 12:32
    Alnoor showed me how to open up that field in the data dictionaries at one time. It is a quick one time fix. But each update / upgrade resets it.


  • 3.  RE: Anyone found a good work around for this physical

    Posted 09-14-2012 12:35
    Can you post that?


  • 4.  RE: Anyone found a good work around for this physical

    Posted 09-14-2012 12:36
    I was just looking at count card entry and the import and it looks like it has the same issue. @AlnoorCassim - if you have a write up on how to add that Qty on hand field to the VI job that would be great! @ClarkWalliser - did you just pull the WH qty's out and put them in your import file - I guess there would be no file assign option?


  • 5.  RE: Anyone found a good work around for this physical

    Posted 09-14-2012 12:41
    These are the only notes I have: How to modify VI Data Dictionaries for 4.x framework DFDM MAS90\providex.ddf Lookup by name to find the VI entity to modify - get the key ID. DFDM MAS90\providex.dde Search by Key. Find the field record you want to modify Edit field 20 (15,1) a zero is importable. a 1 is read only. DFDM VI0XRF.SOA (it's what exposes UDFs to V/I Data tab) (I don't know what came after this - I assume to make sure the field you want exists in this file)


  • 6.  RE: Anyone found a good work around for this physical

    Posted 09-14-2012 14:56
    Not that this would fix your issue but I believe Scanforce will do on the fly freeze when you import physical count. Don't know how often they count inventory but the customers I have on warehouse automation seem to really like the way it speeds physical inventory counting.


  • 7.  RE: Anyone found a good work around for this physical

    Posted 09-14-2012 15:51
    FWIW, after following the first two steps, I was able to create an import with Quantity on Hand in it. Haven't tested it. Thanks, Clark.


  • 8.  RE: Anyone found a good work around for this physical

    Posted 09-14-2012 16:11
    It works! Thanks @ClarkWalliser - if anyone else is reading this and needs a little more info: So the entity in this case (looking in DFDM MAS90\providex.ddf) is: IM_PHYSICAL (if you switch the Key No to By Name and search Physical it will pull up a short list for you. Select IM_Physical and then switch the Key No. back to Primary Key - which is the number you have to look for in DFDM MAS90\providex.dde - find the Key # and there will be a bunch of additional fields tied to that key, find the QuantityonHand field and open and follow Clark's instructions - edit field 20 (15,1) and change to 0. After that you'll see the Qty on Hand field on the IM.Physical import data tab.


  • 9.  RE: Anyone found a good work around for this physical

    Posted 09-14-2012 16:24
    I just love getting credit for following Alnoor's advice :)