Sage 100

Any enhancements?  I think multi-bin might change the physical count object behavior, adding bin to the primary key.

Any enhancements?  I think multi-bin might change the physical count object behavior, adding bin to the primary key.

Any enhancements?  I think multi-bin might change the physical count object behavior, adding bin to the primary key.

I have had success with physical count imports only if I add the Lot/Serial field.  It can point to a column with blank values, if your items are not lot/serial valuation.  I don't know if this will solve your issue, but you may need this component in your import regardless.

Any enhancements?  I think multi-bin might change the physical count object behavior, adding bin to the primary key.

Which Sage Version?

I have had success with physical count imports only if I add the Lot/Serial field.  It can point to a column with blank values, if your items are not lot/serial valuation.  I don't know if this will solve your issue, but you may need this component in your import regardless.

Any enhancements?  I think multi-bin might change the physical count object behavior, adding bin to the primary key.

Thanks everyone! Sorry I went radio silent for a bit; I got sucked into one meeting after another this afternoon.

@Jeff Schwenk This is Sage 100 version 2022 PU 5 (Upgrading might solve this, but who knows)

@Susan Pawlowic Good idea but still getting the same results after adding the lot serial and pointing to a blank column

@Brett Zimmerman interesting thought, but there is a warehouse record for the items I am testing, but the items are all average cost so there would not be any records in IM_ItemCost table. I may explore looking for or making an item with FIFO cost and see if that produces any results. but that will have to be tomorrow's task. 

Which Sage Version?

I have had success with physical count imports only if I add the Lot/Serial field.  It can point to a column with blank values, if your items are not lot/serial valuation.  I don't know if this will solve your issue, but you may need this component in your import regardless.

Any enhancements?  I think multi-bin might change the physical count object behavior, adding bin to the primary key.

This can be taken out of urgent. We have not found a resolution, but we do have a workaround for this client. 

Here is their count prosses:

They generate count sheets from IM_ItemWarehouse -> then count inventory -> fix count issues -> Freeze Inventory -> Import using the VI Job -> Update Variance in Sage -> Post transaction register -> fix any other issues via Item Adjustments.

Since they don't freeze until just before they import, they will import the problematic items into the IM_Physical table before they freeze -> then freeze ->then import the rest of the inventory counts. 

That is considerably faster than manually updating the problematic items after the Inventory freeze. It's an extra step but it's not that time consuming to create an import that only has the 0 on hand quantity items. They will try it this weekend with the next couple of inventories and let me know how that goes.

Thanks everyone! Sorry I went radio silent for a bit; I got sucked into one meeting after another this afternoon.

@Jeff Schwenk This is Sage 100 version 2022 PU 5 (Upgrading might solve this, but who knows)

@Susan Pawlowic Good idea but still getting the same results after adding the lot serial and pointing to a blank column

@Brett Zimmerman interesting thought, but there is a warehouse record for the items I am testing, but the items are all average cost so there would not be any records in IM_ItemCost table. I may explore looking for or making an item with FIFO cost and see if that produces any results. but that will have to be tomorrow's task. 

Which Sage Version?

I have had success with physical count imports only if I add the Lot/Serial field.  It can point to a column with blank values, if your items are not lot/serial valuation.  I don't know if this will solve your issue, but you may need this component in your import regardless.

Any enhancements?  I think multi-bin might change the physical count object behavior, adding bin to the primary key.

Good to hear.

So are you saying, VI will not ADD the item to the frozen table?  I am foggy on the processing details.

This can be taken out of urgent. We have not found a resolution, but we do have a workaround for this client. 

Here is their count prosses:

They generate count sheets from IM_ItemWarehouse -> then count inventory -> fix count issues -> Freeze Inventory -> Import using the VI Job -> Update Variance in Sage -> Post transaction register -> fix any other issues via Item Adjustments.

Since they don't freeze until just before they import, they will import the problematic items into the IM_Physical table before they freeze -> then freeze ->then import the rest of the inventory counts. 

That is considerably faster than manually updating the problematic items after the Inventory freeze. It's an extra step but it's not that time consuming to create an import that only has the 0 on hand quantity items. They will try it this weekend with the next couple of inventories and let me know how that goes.

Thanks everyone! Sorry I went radio silent for a bit; I got sucked into one meeting after another this afternoon.

@Jeff Schwenk This is Sage 100 version 2022 PU 5 (Upgrading might solve this, but who knows)

@Susan Pawlowic Good idea but still getting the same results after adding the lot serial and pointing to a blank column

@Brett Zimmerman interesting thought, but there is a warehouse record for the items I am testing, but the items are all average cost so there would not be any records in IM_ItemCost table. I may explore looking for or making an item with FIFO cost and see if that produces any results. but that will have to be tomorrow's task. 

Which Sage Version?

I have had success with physical count imports only if I add the Lot/Serial field.  It can point to a column with blank values, if your items are not lot/serial valuation.  I don't know if this will solve your issue, but you may need this component in your import regardless.

Good to hear.

So are you saying, VI will not ADD the item to the frozen table?  I am foggy on the processing details.

This can be taken out of urgent. We have not found a resolution, but we do have a workaround for this client. 

Here is their count prosses:

They generate count sheets from IM_ItemWarehouse -> then count inventory -> fix count issues -> Freeze Inventory -> Import using the VI Job -> Update Variance in Sage -> Post transaction register -> fix any other issues via Item Adjustments.

Since they don't freeze until just before they import, they will import the problematic items into the IM_Physical table before they freeze -> then freeze ->then import the rest of the inventory counts. 

That is considerably faster than manually updating the problematic items after the Inventory freeze. It's an extra step but it's not that time consuming to create an import that only has the 0 on hand quantity items. They will try it this weekend with the next couple of inventories and let me know how that goes.

Thanks everyone! Sorry I went radio silent for a bit; I got sucked into one meeting after another this afternoon.

@Jeff Schwenk This is Sage 100 version 2022 PU 5 (Upgrading might solve this, but who knows)

@Susan Pawlowic Good idea but still getting the same results after adding the lot serial and pointing to a blank column

@Brett Zimmerman interesting thought, but there is a warehouse record for the items I am testing, but the items are all average cost so there would not be any records in IM_ItemCost table. I may explore looking for or making an item with FIFO cost and see if that produces any results. but that will have to be tomorrow's task. 

Which Sage Version?

I have had success with physical count imports only if I add the Lot/Serial field.  It can point to a column with blank values, if your items are not lot/serial valuation.  I don't know if this will solve your issue, but you may need this component in your import regardless.

Any enhancements?  I think multi-bin might change the physical count object behavior, adding bin to the primary key.

This is a perfect defect to submit.  If they don't fix it, I would like to hear the WAD reason.  This could go on the thread for quick fixes.

Good to hear.

So are you saying, VI will not ADD the item to the frozen table?  I am foggy on the processing details.

This can be taken out of urgent. We have not found a resolution, but we do have a workaround for this client. 

Here is their count prosses:

They generate count sheets from IM_ItemWarehouse -> then count inventory -> fix count issues -> Freeze Inventory -> Import using the VI Job -> Update Variance in Sage -> Post transaction register -> fix any other issues via Item Adjustments.

Since they don't freeze until just before they import, they will import the problematic items into the IM_Physical table before they freeze -> then freeze ->then import the rest of the inventory counts. 

That is considerably faster than manually updating the problematic items after the Inventory freeze. It's an extra step but it's not that time consuming to create an import that only has the 0 on hand quantity items. They will try it this weekend with the next couple of inventories and let me know how that goes.

Thanks everyone! Sorry I went radio silent for a bit; I got sucked into one meeting after another this afternoon.

@Jeff Schwenk This is Sage 100 version 2022 PU 5 (Upgrading might solve this, but who knows)

@Susan Pawlowic Good idea but still getting the same results after adding the lot serial and pointing to a blank column

@Brett Zimmerman interesting thought, but there is a warehouse record for the items I am testing, but the items are all average cost so there would not be any records in IM_ItemCost table. I may explore looking for or making an item with FIFO cost and see if that produces any results. but that will have to be tomorrow's task. 

Which Sage Version?

I have had success with physical count imports only if I add the Lot/Serial field.  It can point to a column with blank values, if your items are not lot/serial valuation.  I don't know if this will solve your issue, but you may need this component in your import regardless.

Any enhancements?  I think multi-bin might change the physical count object behavior, adding bin to the primary key.

This can be removed from urgent. 

I went up 3 rungs in the Sage support queue and have figured out how to resolve my issue. We removed the standard perform logic that is included in the physical count VI job and that fixed the issue. I don't have an explanation of WHY the perform logic caused the VI to not update the items, but I have a fix and wanted to post it here in case anyone else sees this happening.  If I get down time, I will look at the providex code in that perform logic and see if I can provide more information.. 

Both clients where I saw this happen had Avalara. I can't imagine Avalara causing issues with a physical count import job. 

This is a perfect defect to submit.  If they don't fix it, I would like to hear the WAD reason.  This could go on the thread for quick fixes.

Good to hear.

So are you saying, VI will not ADD the item to the frozen table?  I am foggy on the processing details.

This can be taken out of urgent. We have not found a resolution, but we do have a workaround for this client. 

Here is their count prosses:

They generate count sheets from IM_ItemWarehouse -> then count inventory -> fix count issues -> Freeze Inventory -> Import using the VI Job -> Update Variance in Sage -> Post transaction register -> fix any other issues via Item Adjustments.

Since they don't freeze until just before they import, they will import the problematic items into the IM_Physical table before they freeze -> then freeze ->then import the rest of the inventory counts. 

That is considerably faster than manually updating the problematic items after the Inventory freeze. It's an extra step but it's not that time consuming to create an import that only has the 0 on hand quantity items. They will try it this weekend with the next couple of inventories and let me know how that goes.

Thanks everyone! Sorry I went radio silent for a bit; I got sucked into one meeting after another this afternoon.

@Jeff Schwenk This is Sage 100 version 2022 PU 5 (Upgrading might solve this, but who knows)

@Susan Pawlowic Good idea but still getting the same results after adding the lot serial and pointing to a blank column

@Brett Zimmerman interesting thought, but there is a warehouse record for the items I am testing, but the items are all average cost so there would not be any records in IM_ItemCost table. I may explore looking for or making an item with FIFO cost and see if that produces any results. but that will have to be tomorrow's task. 

Which Sage Version?

I have had success with physical count imports only if I add the Lot/Serial field.  It can point to a column with blank values, if your items are not lot/serial valuation.  I don't know if this will solve your issue, but you may need this component in your import regardless.

Any enhancements?  I think multi-bin might change the physical count object behavior, adding bin to the primary key.