Version 2014.1.1.2

This version was released to all customers on March 26, 2014.

The security settings that prevent an user from accessing a screen are now also checked prior to letting that user open the same screen via a link. For example, if the user is prevented from opening the Sales Order, they are now also prevented from using a link to access the Sales Order screen.

3074: Customer

We added a warning to the 'Price Sheet' action to let the user know that it takes several minutes to complete.

2877: Customer Contacts

Added a field to the screen so that the user can track the 'Last Reviewed' date that the contact's information was updated or verified. This field is set automatically by the system when the contact is created, but is manually managed by the user afterwards.

2670: Customer Quote

When releasing a customer quote to a sales order, if the customer is set to require a PO#, the newly created sales order will now show a visual cue and prevent the user from doing anything else with the order until the PO is provided.

2630: Customer Return

Users are now prevented from checking 'Requires Vendor Approval' and leaving 'Return to Vendor' blank. The user will be notified with a visual cue.

2613: Pay A Vendor

When using the 'Save & New' feature, the focus will now be placed in the 'Vendor' field so that the user can continue typing without having to use the mouse.

2995: Price Contracts

Added a new item to the 'Cost Basis' options. This new option, titled 'Vendor Rebate Cost', will calculate a cost that is based on your cost less your vendor rebate. This value would then be used in any of the pricing formulas that use cost as one of the variables.

For example:

Assume you have a formula that will calculate a price with a 25% margin.
Assume your cost is typically $10.
Assume you receive a $1 rebate for selling this item to this selected customer.
Your price, when using 'Vendor Rebate Cost' would be calculated based on a $9 cost instead of a $10 cost.
This would achieve a price of $12.

3150: Replenishment

The 'Use Line Point' flag is now being considered. Since the architecture redesign, this flag has been ignored. It is now being used properly in any type of demand replenishment and ignored during a total review.

2602: Sales Order

Users can now double-click a contact from the list to select the contact's name to populate the 'Ordered By' field.

2785: Sales Order

When the 'Complimentary Items' screen pops up, the focus will now be on the 'Cancel' button so that the user can exit the screen more quickly.

2599: Shipping

The Attached Document functionality has been added to this area. The documents are attached to the sales order, not the shipment itself. This gives the user the opportunity to attach any documents that were generated at the time of the shipment to the sales order for later review.

2878: Vendor Contacts

2614: Vendor Drop Ship Confirmation

When the user adds a new tracking number, the row will automatically be populated with the same carrier service that was selected on the confirmation record.

2994: Vendor Rebates

We've added a feature that allows you to add multiple customers to a vendor rebate. Previously, only a single customer could be associated to a vendor rebate. This was all that was needed for all of our existing user sites. However, some sites do and will need the ability to have a rebate be active for multiple customers.

The feature we've added allows these sites to have a rebate that becomes active for multiple customers. This feature is very similar to the customer groups that are found in Price Contracts and in Promotions.

Bug Fixes

2998: Customer Maintenance

Corrected an issue that prevented the use of the 'Previous' button.

2735: Customer Payment

Corrected an issue that could prevent the user from attaching a document to a posted payment.

3072: Customer Quote

Corrected an unhandled exception that occurred when the system thought that a value at the line level had changed and needed to be written to the database. However, no values that are related to that table had changed.

3204: Customer Quote

Corrected an unhandled exception that could occur when using the 'Move Line' feature.

3026: Customer Statement Printing

Corrected an unhandled exception that occurred if the user tried to print without first retrieving records into the grid.

3067: Date and DateTime Fields

Corrected an unhandled exception that occurred if the user typed in a date that was outside of the range allowed by SQL Server. The user is now given a visual cue that informs them of the error and will prevent them from attempting to save until the date is corrected.

3028: Kit Order

Corrected an unhandled exception that occurred when the user tried to print but had not yet opened an existing (or started a new) kit order.

3024: Manual AR Document

Corrected an unhandled exception that occurred when the user tried to print but had not opened an existing (or started a new) document.

3068: Price Contract

Corrected an unhandled exception that could occur when the user was deleting family, group, or item brackets.

3029: Sales Invoice Printing

Corrected an unhandled exception that occurred when a customer credit was being printed and the system tried to update the credit in the database to show that it had been printed. However, if the credit had been previously printed, the system wouldn't actually have anything to update and an error occurred.

3020: Sales Order

Corrected an unhandled exception that occurred when the user managed to open a sales order that was already locked by another user. This was accomplished by using the scrolling feature. When the user was scrolling to the next record, and that record was the last record, and that record was locked by another user, the system informed the user of the lock but left the order on their screen. If the user then deleted a line, or modified the order, they would receive the unhandled exception.

3069: Sales Order

Corrected an unhandled exception that occurred when the system allowed the user to delete a sales order that had comment lines. The system wasn't accounting for the comments and wasn't deleting them, thus causing an error.

3092: Sales Order

Corrected an unhandled exception that occurred when opening an existing sales order that was tied to a customer that had a mandatory 'Customer Class' message.

3137: Sales Order

Corrected an issue that could cause stock inventory layers to be incorrect. The issue occurred when the item in question 1) was stocked 2) was being special ordered on a sales order line detail 3) the full quantity had been received 4) the user canceled some, but not all, of the commit quantity Under these conditions, the system was creating a new inventory layer for the canceled portion of the line (which is correct), but was creating the layer for the full order quantity (which is incorrect).

3241: Shipping

Corrected an unhandled exception that occurred when the user tried to print a pick ticket, packing slip, or invoice after starting a shipment but prior to specifying the sales order.

3199: Unit Cost Adjustments

Corrected an unhandled exception that occurred when the user did two consecutive adjustments in the stand-alone version of UCA.

3023: Unit of Measure Maintenance

Corrected an unhandled exception that occurred if the user created multiple records with the same unit of measure name.

2961: Usage Adjustments

Corrected an visual cue error that occurred when the user selected a month that is later than the current month, but a year that is prior to the current year. The system mistakenly told the user that the month was in the future, due to not taking the year into consideration.

3035: Vendor

Corrected an unhandled exception that prevented the use of the advanced search.

3030: Vendor Document Inquiry

Corrected an unhandled exception that occurred when the user provided a value for the 'Specific Document' filter.

Wiki