Articles in this section

Release Notes 3.51

AscentERP
  • Updated
Follow

 

Enhancements:

  1. On the mobile menu, we have added a confirmation statement after item movement is done successfully
    • The message will display as “The movement for item XXX is done successfully!”
  2. We designed a new way to show Master Planner data and actions using Planner Data
    • It is a new tab where you can see the same lines as shown on Master Planner after clicking “Generate MP Data”, and by clicking the Do Action button, you can create PO or PWO as you usually do on Master Planner. This is helpful for customers with larger volumes of Master Planner data that may have hit Salesforce.com limitations with the standard Master Planner. Please note that standard Master Planner is still available for customers who wish to continue to use it as before.
  3. We now support the Sales Order Re-Staging function in the Ascent Mobile Menu.
  4. We have added a new serial number search function on the Pack SO VisualForce page
    • A user can now click on this search icon, and it will open a new window where the user can search for serial numbers or it can just display all the serial numbers for that item in the selected location. The user can then click on the serial numbers and add them to the Pack Out process.
  5. We added a Location filter on CMPO complete page
    • In the Complete process for CMPO, only the lots (or locations if lot is not used) that match with the PO Lines Location will be shown as available for issuing components.
  6. We added the ability in Master Planner page to sort the results by Vendor, by clicking on the Vendor label in the header row.  
  7. We added two custom settings to avoid duplicate lots and inventory records
    • There were duplicate lots and inventory records generated by some users who used a data loader tool to add cycle count lines if they do not otherwise use lots. To avoid this happening, we added two new custom settings in this release: “Don’t Allow Duplicate Lots Creation” and “Don’t Create Default Lots on New Items“. Users who don’t need lots and are also adding cycle counts lines by a data loader tool should turn on the two custom settings.
  8. We modified the default Picking List for a Sales Order 
    • It can show the Default Location for each Sales Order Line based on the Location that is put on the sales order line.
  9. We made it possible to set a Default Expiration Days greater than 5,000 days for Items.
  10. With "Default to CM PO" Item setting turned on, Master Planner will now show suggestions for BOM-Non Phantoms as “Create CMPO”.
  11. We added a new Apex Class in our package to update BOM component exchange rate
    • The Apex Class is "ScheduleBomCompExchangeRateRecalculation". Users can schedule it to run and it will update BOM components exchange rates based on the current Dated Exchange Rates.
  12. We added the maximum available fields for several fieldsets that support Ascent VisualForce components. This gives users more flexibility in defining the fields to be used in these VisualForce pages following field sets"
    • Quote_Lines_Field_Set
    • Sales_Order_Lines_Field_Set
    • Sales_Order_Lines_Field_Set2
    • viewSOSimply
    • Clone_SO_Sales_Order_Lines_2
    • Clone_SO_Sales_Order_Lines_4
  13. The Returns from PO process has been improved
    • We added a new “Has Return?” field on the received PO Line to indicate if the line has any return lines created from. We also made sure Cost on the return from PO will be from the Recorded Cost on the Received PO line.
  14. We added a rule that when running Historical Inventory Object, a future date should not be allowed to be chosen.
    • If a user selects a date in the future and tries to add items, an error message will appear on this page saying “Ascent can do a lot but we can’t predict the future yet.  Please select a date in the past.”
  15. On the Historical Inventory Object page, we added the standard Salesforce header
    • The header will include all of the objects, so the user can navigate away from the page easily.
  16. We added an error message on the Historical Inventory page when there was no item selected
    • It will show when a user clicks on “Add Items” button. It will show “Please choose one of the following: all items, items, or item group”.
  17. We made a new custom setting “Mobile - Show Item Description on Table”
    • It will overrule all places that Item usually shows in the mobile menu to be Item Description instead.
  18. We added a Cancel option for Bulk Item Movement
    • When a line is in pending status, the user can cancel it. We also made sure the page will refresh itself after the user saves the line.
  19. We added a new custom setting called “Disable TA for Quote lines”
    • Which will disable the trade agreements functionality for quote lines when “Disable Trade Agreements” checkbox on the quote header is true.

 

Bug Fixes:

  1. "Invalid Date" error for expiration dates
    • If the user has a non-US locale on the user table, there was a problem on the receive purchase order visualforce page when a user tried to create a new lot, as the expiration date field did not allow the user to change it or it showed “Invalid Date” error. This issue is now fixed.
  2. "Use Inventory Cost for Recorded Cost" not working properly
    • When the “Use Inventory Cost for Recorded Cost” custom setting is turned on, and if users tried to process a return to a new location where the item's inventory record did not exist, the return lines, credit packed sales order lines, inventory cost, lot average cost, and movement lines transaction cost were all showing a zero recorded cost. This issue is fixed and they will show recorded cost same as “Recorded Cost” on packed sales order lines.
  3. Success message after packing a sales order for a drop-ship sales order line is not exactly correct
    • The success message says:  "line was successfully drop shipped". Now, this is changed to: "line was successfully created on a drop ship PO" since it hasn't been drop shipped yet, and it will only happen when a user performs a Receive PO or Compete PO (depending on if advanced drop ship is used or not).
  4. Master Planner not showing correct qty for items with Min/Max and on Drop-ship Sales orders. This issue is now fixed.
  5. Tax Code on Returns
    • When the return was created from a sales order and sales order tax code was different than tax code of the account, return displayed account’s tax code instead of sales order header tax code. This is fixed and now the tax code on the return should always show the same as sales order header tax code.
  6. Merge Inventory function was not working correctly for serial numbers
    • After performing a merge the inventory lot field on the serial number tracker updated to blank. This is now fixed and the lot on the serial number tracker will always show the merged location lot.
  7. Error message for Receive PO function on the Mobile Menu
    • After scanning the item, it showed the error message "Page xxxxxxxx(SalesforceID) does not exist " which is now fixed in this release.
  8. Cycle count on the Mobile Menu asking serial numbers for non-serialized items
    • When the admin setting for lots is disabled and cycle count by serial number is enabled in admin settings, Mobile Menu Cycle Count asked to scan a serial number for a non-serialized item. This is now fixed and it will only ask for serial numbers for serialized items.
  9. Mobile Menu allowed cycle counting to scan and count a serial number that belongs to a different item than what was selected in a previous step, which led to serial number to be switched between items. We fixed it in this release.
  10. While receiving transfer orders, lots were not showing up to receive the items while non-expired lots did exist. This is fixed in this release.
  11. When multi-currency is turned on, transfer order line currency was not showing to be the same as the transfer order header currency, which it should be. This is fixed in this release.
  12. Not showing calendar for Mobile Menu Inventory Adjustment
    • On Mobile Menu, while doing inventory adjustment and creating a lot, calendar was not displaying for the user to select the expiration date of the lot. This is fixed in this release.
  13. While in the Lightning UI, the Bulk Item Movement page had a display issue where the input fields are too narrow. This is fixed in this release.
  14. Pallet Content Report
    • There was a problem with the Pallet Content Report such that when you reference a container in two different sales orders, it shows container items from other sales orders. We fixed it in this release.
  15. Price field on purchase order lines
    • When adding a new purchase order line to a purchase order, the “Price” field didn’t show the price as set at Item Master. If Item Master cost type is Standard, it should show Item Cost, and if cost type is Last Price, it should show Last Purchase Price. We fixed this in this release.
  16. In release 3.30, ATP by location doesn't work as expected
    • we have found some issues with Available to Promise (ATP) by Location in that the ATP field on Item Grid and Sales Order Lines were not updating properly when the “Use ATP by Location” custom setting is turned on. We fixed this in this release.
  17. Allocation Quantity was incorrect for Contract Manufacturing Purchase Order (CMPO) BOM depletion lines
    • Meaning that having a BOM allocation line on a CMPO is treating the BOM component as if it is being purchased on order rather than being allocated for depletion on the completion of the CMPO. This created the wrong demand profile for the item, it is fixed in this release.
  18. Drop Ship PO's were consolidating the Sales Order Lines to a single purchase order line, when the item number is the same
    • This issue caused some sales orders to be left open due to the receiving PO process only packing out a single line of the sales order. We fixed this in this release.
  19. There was no reference for Bill of Materials (BOM) Production Work Order (PWO) archive line on its components’ PWO archive lines. We added it in this release.
  20. Trade Agreement Order level was not respecting the multi-currency order’s currency
    • In that it still applied when the sales order was in a different currency than the currency on the trade agreement. It should not apply when currency is different. We fixed it in this release.
  21. Pack SO page display issue
    • When not using Lots, the Location field and create a new Lot section were both a bit narrow on Receive PO page, and the Description field was not wrapped on Pack SO page. We made both pages neater and more user-friendly in this release.
  22. Error when performing Credit function on a purchase order line
    • It showed error on “viewpowithfieldset” visualforce page. We fixed it in this release.
  23. The Discount % field on the Quote Lines View with field set was too skinny
    • It is too narrow to show 2 decimal discounts. We made it wider to allow the display of 2 decimal discounts.
  24. When there was a BOM-Phantom on a purchase order line with huge quantity (i.e. 4,000) and one or more of the components are serialized, the system aborted with the Error message: Collection size 1,001 Exceeds maximum size of 1,000. We fixed it in this release.
  25. Incorrect movement line type for CMPO
    • The movement lines created for a completed CMPO showed the wrong type “Receipt from PO” for the components of a Bill of Materials (BOM). We correct it to “Goods Issued for Purchase Order” in this release.
  26. When trying to perform Allocate Order, any BOM-Phantom components were not properly allocated. We fixed it in this release.
  27. The Credit function on RMA lines did not convert the unit of measure properly. We fixed it in this release.
  28. When adding a PO line, the number entered into the tax field was divided by 100 (e.g. $26.00 became $0.26.) We fixed it in this release.
  29. Serial number prefix not functioning perfectly when generating a great amount of it
    • When generating an index was used for Items and the serial number prefix was set, if you received an item with a large quantity (i.e. 95), serial numbers were generated but the prefix was not consistently used. We fixed this in this release.
  30. Some users were unable to complete Ascent Work Orders (WO)
    • When they don’t have the field Create Inventory exposed in the field set called Part Type Complete WO. We fixed this and users now do not have to add this field in order to be able to complete Work Orders.
  31. In release 3.30, issue when staging SO with same item into same location
    • Each time a user staged a Sales Order line it created a new Lot with the same name and the Lot from which the item was staged. This was changed to put the quantity into one single staged lot for that item.
  32. The system showed an error message when trying to process an RMA for an RMA line that had an Item that was not from the original sales order. We fixed this in this release.
  33. A user could not use a location that was set up as not counted in inventory as the From Location on a transfer order. We fixed this in this release.
  34. Tax not being calculated for Discount% on Quote lines
    • When using a discount by a percentage on a Quote Line, the Tax was calculated for the total price without the discount being applied. It is fixed in this release.
  35. Tax on Shipping was not being calculated on Quote
    • On an Ascent Quote when there is a Shipping Cost on the quote header and header level tax code, Tax on Shipping was not being calculated. This is now fixed and the Quote will calculate the tax for the shipping cost.
  36. Item Description was not wrapping on the following VisualForce pages and they were fixed now.
    • SO Lines View
    • PO Lines View
    • Quote Lines View
    • RMA Lines View
    • Process RMA lines View
    • Pack SO
    • Picking List 
    • Receive PO
  37. Lot Average Cost not being converted properly after PO receiving when Purchase order and lot had different currencies
    • When receiving the Purchase Order into the Lot, purchase price and lot average cost were not converting the values to the correct lot currency. This issue is fixed in this release. Now the PO lines, Receive Po lines and movement lines will show the PO currencies and lot average cost will be converted into the location currency.
  38. Movement journal and movement lines currency issue with PWO
    • When a PWO was created with different currency from Org currency, the movement journal and movement lines related to this PWO were created with Org currency instead of PWO’s currency. It is fixed in this release.
  39. The Item Description on a SO Line not being updated automatically 
    • It was not changed to the new description when the SO Line Item is updated. It is fixed in this release.
  40. When creating a Purchase Order from Master Planner and with the custom setting “Edit PO/PWOs before creation on MP"enabled, an error occurred. We fixed this in this release.    
  41. There was an error message when trying to delete a Quote Line from an Ascent Quote. We fixed it in this release.
  42. For some users, Historical Inventory Report showed negative inventory numbers 
    • It was caused by Purchase Order reversal movement lines filling the To Location, instead of From Location, which added inventory when it should be reduced. We fixed this in this release.

 

Known Issues:

  • In 3.51, there is one known issue that when custom setting "Edit Po/Pwos before creation on MP" is enabled, it will show an error when clicking on "Create PO" link on Master Planner or clicking on "Do Action" button on Planner Data page. We will fix it in the next release.
  • In 3.51, Process return lines with "Replacement" type can only process half of the quantity user claims on the line. We will fix it in a future release.
  • When custom setting "Use Returns And Cases for RMA" is enabled and user processes an RMA line that there are lines not belong to the original sales order, the RMA line will still show Status = open with 0 qty processed. The workaround for this issue is to not enable the custom setting “Use Return And Cases for RMA” when you need to add additional items to RMA. We will fix it in a future release.

Related articles

Comments

0 comments

Please sign in to leave a comment.