Sage 100

 View Only
  • 1.  FIFO tiers - anyone else have an issue where an ol

    Posted 05-12-2014 09:41
    FIFO tiers - anyone else have an issue where an older tier is just ignored by the system? It pulls inventory from more recent tiers - this happens on multiple items but not all items - and if I issue the entire quantity on hand - it creates a negative OVERDIST tier and leaves the old tier out there with a positive balance. I compared the tier records in DFDM and don't see anything different about the older one. Sage 100 standard 2013 PU3.


  • 2.  RE: FIFO tiers - anyone else have an issue where an ol

    Posted 05-12-2014 10:20
    It's probably this new file: What is the function of the new data file IM_DataEntryCostCalcCommit.m4t found in MAS90/200 release v4.4x? What programs affect this data file? (Cross Reference by program) Possible Resolution: The cost calc commit logic applies during the register/update programs that w ill be relieving inventory. It applies to LIFO/FIFO & Average cost items. The purpose is to make sure multiple updates don't try to use costs from the same cost tiers, and to make sure w e use every last cent w hen taking the last quantities from a cost tier (or a w rehouse for average cost items). This solves some of our old rounding issues that caused us not to tie to G/L. The common cost calc program is called during the ""populate work tables"" logic and this is w here the commits happen. After the register is printed, the user gets the option to update. If they do update, the commits are cleared as part of the common IM update logic. If they answer NO to the update, the commits are cleared while closing the program. And there are utilities for it:: Values may become stranded in the CostCalcQtyCommitted or CostCalcCostCommitted fields in the IM_ItemCost.M4T and IM_ItemWarehouse.M4T tables or in the IM_DataEntryCostCalcCommit.M4T table during Transaction Register updates or previews.. These values may contribute to discrepancies with Quantity On Hand totals and costing issues. Using these utilities will remove the stranded values and create a comma separated file (.csv) of the committed records removed. Utilities are included in versions 4.40.0.8 and 4.50.2.0 and higher to remove these values. For versions 4.40.0.7 or 4.50.1.0 or lower, contact Customer Support to receive the utilities. Possible Resolution: Note: Use caution when working with Sage MAS 90 and 200 utilities. Always make a backup first. If necessary, seek the assistance of a qualified Sage business partner or Sage Customer Support analyst. These utilities will remove all values in the CostCalcQtyCommitted or CostCalcCostCommitted fields in the IM_ItemCost.M4T and IM_ItemWarehouse.M4T tables and in the IM_DataEntryCostCalcCommit.M4T table. The utilities can only be used when there are no users updating or previewing Transactions Registers. To run the IM_CommitCheckClear utility: Copy the IM_CommitCheckClear_utl and IM_ClearCommitDataEntry_UTL program files from the \MAS90\Utility folder to the \MAS90\IM program file. Go to File / Run and type ""syzcon"" Click OK At the command prompt, type: run ""IM_CommitCheckClear_utl"" and OK. The program will prompt with the following warning: ""Warning: This utility should not be run while registers have not been updated. Do you want to proceed?"" Click Yes to Continue, Click No to quit the program. If any issues are found, the message ""IM Commit Check Clear Utility Check completed. Do you want to clear them?"" will display. Click Yes and the message ""The IM Commit Check Clear Utility for Company xxx has been successfully completed. Results can be viewed in.. HOME/TEXTOUT/IMCommitCheckClear001.csv"" If no issues are found, the message ""The IM Commit Check Clear Utility for Company xxx found no issues to review"" will display. You can then review the report in Excel. The reports are saved by adding a sequence number to the end so comparisons can be made to isolate the cause of the issues. The program will also add an entry to the Activity Log. To run the IM_ClearCommitDataEntry utility: Go to File / Run and type ""syzcon"" Click OK At the command prompt, type: run ""IM_ClearCommitDataEntry_utl"" and OK. The program will prompt with the following warning: ""Warning: This utility should not be run while registers have not been updated. Do you want to proceed?"" Click Yes to Continue, Click No to quit the program. If any issues are found, the message ""IM Commit Check Clear Utility Check completed. Do you want to clear them?"" will display. Click Yes and the message ""The IM Clear Commit Data Entry Utility for Company xxx has been successfully completed. Results can be viewed in.. HOME/TEXTOUT/IMCommitCheckClear001.csv"" If no issues are found, the message ""The IM Clear Commit Data Entry Utility for Company xxx found no issues to review"" will display. You can then review the report in Excel. The reports are saved by adding a sequence number to the end so comparisons can be made to isolate the cause of the issues. The program will also add an entry to the Activity Log.


  • 3.  RE: FIFO tiers - anyone else have an issue where an ol

    Posted 05-12-2014 11:02
    That did the trick, thank you Beth!