We have added the “Create Quote” and “Make SO” buttons on the opportunity object. We have also added the “Make Sales Order” on the Quote object.
New fields added to Work Order Lines
All are formula types (14,4)
Line Extended Cost = Line Quantity * Cost
Line Extended Price = Line Quantity * Price
Actual Extended Cost = Quantity Completed * Cost
Actual Extended Price = Quantity Completed * Price
RMA/Return Issues
The Return Line field originally did not populate on the Serial Number Tracker object to show that it has been returned. We have also added the Return object on the Customer Support object.
Logging email activity history when emailing a Purchase Order
Customers wanted an activity history record when emailing for the purchase order object. This has been updated
Recorded Cost with Lot Average Cost - PWO Archive Lines
Lot average cost is now supported on the production work order build process. If a customer makes a new build it will update the lot average cost and value the finished good lot based aggregate lot cost of the components. It will also update the recorded cost appropriately.
Tax Code with Lines
Tax Code is now working with most of Ascent main objects, both at the header level and at the line level. It works with the following objects: opportunity lines, quote lines, sales order lines, sales invoice lines, purchase order lines, vendor invoice lines, return/RMA lines, credit memo lines, work order lines.
By default, we leave Tax Code on lines blank, and use header Tax Code to show tax% and calculate tax amount on the lines. User can change it to a different tax code at lines, in order to get different tax% and tax amount at some specific lines.
If object B is created from object A - for example, a sales invoice is created from a sales order - tax code at B’s lines will copy tax code from A’s lines. Again, user can change it to a different tax code to get different tax% and tax amount.
Tax Code with Item Master
There is a new way to use tax code. Instead of applying tax code per customer/vendor/order, user can apply tax code per item.
Tax Code lookup field is added to Item Master. If Tax Code on Item Master has a value, when adding this item to any Opportunity lines, Quote lines, Sales Order Lines, Purchase Order Lines, Sales Invoice lines, Vendor invoice lines, Credit Memo lines, Return lines, Work Order lines, Tax Code on the line will populate item's Tax Code.
If Tax Code on Item Master is blank, Tax Code on the above mentioned lines will work the same way as how tax code works with lines: by default, we leave Tax Code on lines blank, and use header Tax Code to calculate taxes on the lines. And we only take Tax Code on the lines to calculate taxes when it has a value.
Ability to Assign RFID EPC to SNT When PWO is Completed
Update RFID Item Query Service to return Lot/Lot Location
SalesOrder API update
Customers that are using our Sales Order API noticed that there was a requirement for a lot for “Service” items. This caused problems for customizations down the line. The requirement has been removed.
New APIs that have been added to AscentERP
REST API Methods for Stage/Unstage SO Lines
REST API Method for Move Item
REST API Methods to support Cancel and Remove Sales Order Lines.
REST API to Query for Sales Orders using custom fields
REST APIs to Support Staging Sales Orders
REST API to Decommission/Replace RFID Tag
Bug Fixes
Item Versioning
Customer that are using item versions may have multiple version of an item. Customers only want active versions to be present when inputting the item on the Sales order line, previously it was showing all versions. This has been corrected.
Custom Setting: Use Advanced Drop Ship
During testing we noticed that Advanced Drop ship was not working correctly. When trying to close out an advanced drop PO, we ran into a soql query error. This was quickly corrected in this release.
Drop Ship in UAT is not closing SO lines
When testing normal Drop Ship, when a user would close a drop ship Purchase Order, the corresponding lines on the Sales Order were not closing. This has been corrected.
Pack Allocated Order doesn't also pack the not counted in inventory lines
Customers that have items that are not “Counted in Inventory” saw that when they allocated their items on the Sales Order, and went to pack it out, it would pack out the “Not counted in inventory” items. An example of a “Not counted in inventory item” would be “Labor” or “Service”.
Lot Average Cost Not Respected for Inventory Adjustments
During testing we noticed that when using the inventory adjustment visualforce page on the item master and using the custom setting called “Use lot average cost for recorded cost” there was a costing error. When adding or subtracting items it would use the “item cost” and adjust the lot average cost, when it should stay the same. This has been corrected during testing.
Allocated Quantity
Certain customers found, based on their customizations, that allocated quantity was not being updated properly, but the allocation grid was. This was corrected and rolled into the main Ascent package.
Cycle Count on mobile menu bringing qty in inventory over to desktop incorrectly
When customers were doing a count journal from the mobile menu, the system would complete the Count journal. However, when looking at the record from the desktop, it did not update the quantity in inventory properly. This may be specifically related to pallets.
Could not print pallet labels after receiving a PO
When using pallets, customer noticed that after receiving a PO on either the mobile menu or desktop version, users were unable to print labels for them. This has been corrected.
Pallet - pack with a different serial number
When using pallets, users noticed that you have the ability to pack a serial number from a different lot than the one that is currently being pointed at. This has been fixed.
Pallets - Reverse packing with serialized items
Customers that use serial numbers noticed that when they reverse pack a serialized item, after the item has been reverse packed, the serial number tracker kept the Sales order and sales order lines id. This has been corrected.
Pallets - Print License plate not working for Returns
Customers using pallets wanted to have the ability to create a new pallet when returning stock. They are able to create a new lot for the pallet, however they are unable to print a license plate for the pallet. This was added.
Pallets - Cycle Count did not ask for serial numbers using mobile menu
When using the the Ascent Mobile menu, users noticed that when trying to use the cycle count function with pallets some information was missing. If the users were trying to cycle count a serialized item, the system wouldnt prompt the user to input serial numbers and would not create the pallet appropriately. This has been corrected
Mobile menu not updating Lot and Inventory records correctly
During testing we noticed that the mobile menu was not updating the lot and inventory records correctly with inventory adjustments. This was found during testing and corrected.
Custom Setting: Use Purchase Price 4 dec on PO Line
Users want to only use the custom setting defined, but only track 4 decimals on the purchase order level and not throughout the rest of the processes of Ascent. We were not capturing the cost properly. This has been corrected.
Calculating tax with discount in a multicurrency org
When the calculate the tax at line items is true, it is taking only standard discount field values. When the calculate the tax at line items is false, it is taking standard discount or discount amount.
Trade agreements on Opportunities
Some users were noticing that they wanted Trade agreement to apply to Opportunities. Ascent allows this functionality, but it was not updating the price correctly. This has been resolved.
Partial Payment Voucher
Customers that use Ascent and Financial Force had an issue with “Partial Payment Voucher”. They were unable to invoice lines. This has been resolved.
Sales invoice line “Final Total Price” rounding issue
With “Use 2 Dec Round Prices on So/Quote/Opp” setting on, sales invoice line “Final Total Price” was not showing the correct rounded 2 decimal value, because it used Total Price from sales order line and this Total Price was not calculated and rounded by final discounted price. This has been resolved.
Known Bugs in this release
Custom Settings: Use User locations
The custom setting is not working in this release. If you have this custom setting on, it will show all available locations instead of the specified locations based on the user
Comments
0 comments
Please sign in to leave a comment.