Version 2016.1.3.5

Table of Contents

Minor Enhancements
Bug Fixes

This version was released to all customers on February 1, 2017.

Minor Enhancements

7577: Counter Sales

Added Customer PO Release # to the screen as a column chooser option.

7639: Counter Sales

Added a new field for Sales Force. Also reporting changes in its value to the tattle-tale table.

We've added a new button to the Action menu that allows the user to add lines from a sales invoice to the credits grid. This action can be used multiple times to add lines from various invoices as long as all of the invoices are from the same customer.

7640: Customer Returns

The Sales Invoice field has been removed from the header. In its place, we've added a new button to the Action menu that allows the user to add lines from a sales invoice to the return. This action can be used multiple times to add lines from various invoices as long as all of the invoices are from the same customer.

6618: Expedite & Follow Up

Rework Orders are now included in this area.

7321: Foreign Currency

We've completed the functionality to support the use of foreign currency throughout the purchasing and AP processes.

7181: Kit Disassembly

Corrected an issue that prevented non-stocked kits from being disassembled in a quantity greater than one at a time.

7455: Pay Vendors

Added a column chooser option for "Vendor Class". This is to partially compensate for removing vendor class as part of the filter set.

815: Price and Cost Changes

When performing a Price and Cost Change for a specified vendor, the user now has access to a new feature that allows them to upload a vendor cost spreadsheet. The user can start a new worksheet, select a vendor, set an "Effective Date" if desired, and then press the new "Upload ..." button. This will bring them into a new screen that allows them to view the spreadsheet contents, verify data, designate columns, and ultimately update the data in Acclamare.

1973: Purchase Note Maintenance

We've added a file maintenance area for reusable Purchase Order Notes. This is similar to the reusable notes in Expedite & Follow-Up. Once notes have been created in the file maintenance area, they can be accessed in the Purchase Order interface via an action in the main menu. Any note chosen will be added to the header Notes field.

4280: Purchase Order

Added a new column chooser option for Freight Payment Method.

2417: Purchase Order Receiving

Added "Attached Documents" to this area. The documents will not actually be tied to the receipt, but to the purchase order that is being received. As such, this feature is not accessible if there is more than one purchase order in the receipt. Since many of our customer sites do mix multiple purchase orders in one receipt, this action is not available by default. If you would like to access this feature, it must be customized onto your menu.

3274: Replenishment

When an item is included in the worksheet due to being a special order, the associated sales order number is now displayed as part of the "Reason". This will only work on new worksheets. Existing ones will still just show "Special Order".

7605: Replenishment

Users can now change the Unit of Measure on replenishment detail lines.

6378: Sales Order

Added a new Pick Label document that is only available from the Sales Order -> Print menu. The report can be tied in via Document Control and overridden in the Customer, User, and Warehouse areas.

7638: Sales Order

Changes to the Sales Force and Field Sales Force values are now being reported to the tattle-tale table.

4969: Vendor Contact Maintenance

Vendor Contact Maintenance can now be accessed directly from the main menu. It can still also be accessed from within Vendor Maintenance. This direct access allows sites to restrict users from accessing vendor information, but still access and maintain contact information.

2140: Vendor Invoice

Added a feature that allows the user to reverse an invoice as long as it has not been paid and is not associated with a manual payment.

3835: Vendor Invoice

The user can now drill into the associated purchase order by clicking on the PO number in the item grid.

Bug Fixes

7631: Acclamare Command Center

Corrected an issue that prevented failed tasks from displaying properly in the UI. Also added some safeguards to prevent a task from being rescheduled an erroneous number of times.

7442: Bank Register

Corrected an unhandled exception that occurred when a Recurring General Ledger Entry for cash had previously been posted, then deleted.

7388: Customer Credit

Corrected an issue that led to the credit's Original Balance and Current Balance being incorrect. The issue occurred when the credit was created from a Unreturned Merchandise Authorization, the credit had not yet been posted, and the user deleted one or more lines prior to posting.

7488: Customer Credit

Corrected an unhandled exception caused by the typical "where" error.

7259: Customer Payment

Corrected an unhandled exception that occurred under the following conditions: The user is posting a customer payment. The payment is from a payor. The payment has a remaining balance that must be put on account. The user elects to continue with the post and is told they must assign the overpayment to a specific customer.

7505: Customer Quote

Corrected an unhandled exception that happened when the user added a new customer item number, but didn't provide a description. The table actually allows for a null, but the code wasn't properly checking for that condition.

7417: Item Maintenance

Corrected an issue that was caused by allowing a kit item to be a component of its own kit definition. To prevent this issue, that scenario is no longer allowed.

7453: Item Maintenance

Corrected a spelling error in the computed column ControlTypeComputed.

7373: Kit Order

Corrected an unhandled exception that occurred when the user created a kit order, or spawned one from a special order, that resulted in an order quantity of 0.

6541: Landed Cost Allocation

Corrected an issue that led to the GL Inventory balance being out of balance with Inventory Valuation. This occurred when the goods were received and partially shipped prior to the LCA being performed.

7372: Manual AR Document

Corrected an issue that allowed the user to post a document that was in Used or Paid status.

7452: Merge Customers

Corrected an unhandled exception that occurred when the "Remove" customer had credit cards attached.

6638: Merge Vendors

Corrected an issue caused by the user merging two vendors that were already setup with overlapping vendor items. If the user did not cleanup overlaps prior to merging, duplicate vendor item records would result from the merge which could lead to issues throughout purchasing related transactions.

7513: Pay a Vendor

Corrected an unhandled exception that occurred in the search window. This error occurred when the user selected to search on status and picked a single status. If more than one status was selected, the error did not occur.

7322: Physical Count

Corrected an unhandled exception caused by the typical "where" error.

7415: Physical Count

Corrected an unhandled exception that occurred when the user chose to assign workers by SKU Count.

7489: Physical Count

Corrected an unhandled exception that occurred when retrieving an existing count and the item's Description was null.

7328: Purchase Order

Corrected an unhandled exception that occurred if the user tried to print the document prior to providing all required fields.

7381: Replenishment

Corrected an issue that caused a virtual item to be treated as a stocked item on a purchase order. The issue occurred only when the item had previously been stocked, but the stock record had since been set to 'Inactive'. The user would then sell the item as a special order. If the special order generated a purchase order through the use of replenishment, the replenishment post incorrectly identified the item as a stocked item when generating the PO.

7406: Replenishment Filter Maintenance

Corrected an issue that prevented the "Save Changes?" prompt from appearing when the user made edits, but did not manually save prior to exiting the screen.

3575: Sales Order

Corrected an issue that prevented total from being recalculated when the only thing the user changed was the Bottom Line Discount.

3745: Sales Order

Corrected an issue that allowed the user to access Add Items From Customer History prior to selecting a customer and/or warehouse.

6922: Sales Order

Corrected an issue that caused an incorrect value to be recorded in the Virtual Stock Item's On Order field.

7352: Sales Order

Corrected a cosmetic issue that caused the warning (red X) to appear in the quantity fields when a fractional quantity existed. This did not occur during the initial entry of the document, only upon exiting the document and viewing it again later.

7366: Sales Order

Corrected an issue that allowed a locked sales order's Totals screen values to be edited by a user that wasn't the locking user.

7367: Sales Order

Corrected an issue that allowed the user to prematurely print a sales order that they had locked on another screen. This only occurred if the user was entering a new sales order on one screen and also had it open on a second screen. The bug allowed them to print it from the second screen even though the order should have been on hold.

7401: Sales Order

Corrected an inventory synchronization issue that occurred when the item on the line is stocked, some quantity is available but not enough to fulfill the request, the user manually sets the "Quantity Committed" to zero, the user adds a detail for "Kit Order", the kit order is processed and posted, the user reenters the sales order and changes the line level "Pick On" date.

7454: Sales Order

Corrected an issue that prevented new sales order lines from being saved to the database. This issue only occurred in a fresh database created via the "New Company" action, and as such does not affect any currently live sites.

7627: Sales Order

Corrected an issue that caused the stock item values for Quantity Committed and Quantity Being Picked to be incorrect. The issue happened when an order that was in Partially Shipped status was printed and moved to Being Picked status and was then reset back to Partially Shipped using the Reset This Order function.

Wiki

Wiki

Version 2016.1.3.5