Wiki

Case Status
Log In

Wiki

 
Release Notes»Version 2013.4.1.2
  • RSS Feed

Last modified on 10/4/2013 10:06 AM by User.

Tags:

Version 2013.4.1.2

This version was released to all customers on September 30, 2013.

 

 

Minor Enhancements

2184: Counter Sale

Users can now use the standard price modifier keys (M10, C25, etc.)

2309: Counter Sale

The user can now select alternate quantity and price units of measure.

2459: Customer Aging

When recalculating past due holds at the end of day, the system will now take the value in "Days Past Due to Allow Before Placing Hold" into account.

2452: Customer History Inquiry

Customers that have their invoices paid for by a Payor will now show payment history in the detail grid under the invoice that was paid.

2169: Customer Quote

Static customer PO numbers are now being captured in customer quotes in the same way that they are currently captured in sales orders.

2211: Document Settings

In Document Control Settings, the user can now specify a standard cover sheet message for faxing. Additionally, just like with the email body, the user can specify placeholder text in this field. Placeholder text is case-sensitive, so I've tried to cover multiple spellings. The placeholder text that is acceptable at this time is:

  • to show the customer's account number [customer] [Customer]
  • to show the customer's name [CustomerName] [customername] [customerName]
  • to show the contact's name (ordered by from sales orders/sales invoices) [Contact] [contact]
  • to show the user's name [User] [user]
  • to show the vendor's account number [Vendor] [vendor]
  • to show the vendor's name [VendorName] [vendorname] [vendorName]

2283: Dynamic Inquiries

We've added a new "Edit" menu to this screen. Within this new menu, you will find three new buttons: "Edit Customer ...", "Edit Item ...", and "Edit Vendor ...". When applicable, these buttons will open the corresponding file maintenance screen.

348: Kit Order

When a virtual stock item is part of a kit order, the user currently has the ability to create a purchase order to fulfill the item's requirement within the kit. We've added new functionality to this feature that allows the user to leave the line within the kit as-is. These lines will now be displayed within replenishment as a special order. The buyer can then purchase the item within replenishment in the same manner as a special order line on a sales order.

2449: Manual AR Document

Closed a loophole in the system that allowed users to edit a posted document. Now, when viewing a posted document, the vertical grid will be read-only.

2307: Merge Items

Merging items will now also attempt to merge the stock usage for both items.

2162: Price Contract

Dynamic Inquiries have now been tied to Price Contracts at the item level. As the user adds items or scrolls through the item grid, the item related inquiries will be updated.

2200: Purchase Order Receiving

When posting a receipt that has been marked with a receipt date that is not today's date, the system will now update the purchase order line with the receipt date instead of today's date.

1058: Sales Order

The "Line" column in the main grid is now free-form editable. The system will not place any restrictions on the number the user assigns, nor will it make any attempt to automatically reorder the unedited lines. The user is in total control over the number should they choose to edit it.

When tabbing through the grid and/or adding new lines, the field will still be skipped over just like it is now. To edit the line number, the user will have to specifically click the field with the mouse or use the arrow keys to navigate to the field, and highlight the number.

We chose this method so that the number of keystrokes needed while adding a line remains unchanged and so that the user is unlikely to accidentally modify the line number when they intended to be entering an item number or quantity.

2201: Sales Order

When changing a committed quantity on a detail, the quantity will now be captured in the "Canceled" column. This will allow any reports or forms that are generated by the system to reflect an accurate order quantity to the customer by subtracting the cancelled quantity from the ordered quantity.

2435: Sales Order

When a user deletes a single line from a sales order, information will be trapped in the tattle-tale table regarding the sales order number, line number, and item number that was deleted.

2472: Sales Order

We've made a change to the way a BTO kit is priced on a sales order line. When the user adds the line to a sales order, and then creates a BTO detail, the price of the kit will be a roll-up of the prices of the components when two conditions are met. First, the line's price source must be 'List Price', meaning that the kit isn't part of a promotion, contract, price bracket, etc. Second, the list price of the kit is $0.00.

This change allows the person setting up the kit to determine how the line will be priced. Assigning a $0 list price and keeping the item out of contract, promotions, etc. will ensure that the BTO kit will be priced based on the components. This change also allows the component prices to be based off of any customer-specific pricing. If a component is part of a customer's price contract, they will then receive that contract price within the BTO, and the overall kit price will reflect that discount.

2464: Shipping

The user can now print shipping labels after the shipment has been posted. There is a new customizable column in the shipping grid titled "Label Count". Users are not required to use this field, but it exists for those sites that wish to print shipping labels.

There is a new row in Document Settings that accommodates this new report and will allow a site to specify a custom report. Your site may need to configure this new setting prior to using it, depending on your needs.

This new functionality performs in exactly the same way that Receiving Labels work in the Purchase Receiving area. The user will only be able to print the labels once the shipment has been posted, and the labels will be forced into a print preview so that the user can direct them to a label printer.

Bug Fixes

2450: Customer Maintenance

Corrected an issue with phone and fax numbers. If the user changed either the phone or fax number while the "Same as Billing" box was checked, the corresponding number was not updated in the shipping fields. The numbers will now be properly updated.

2462: Customer Payment

Corrected a purely cosmetic issue related to customer prepayments. If the user initiated a prepayment from a sales order and the customer had available credit, the payment screen would report twice the available credit in the main screen. However, when viewing the actual credits, the amount shown in that screen was correct and the user could not select more credit than was actually available.

2461: Phone Number Fields

Users are now prevented from entering anything but numbers, parentheses, and dashes in phone/fax numbers throughout the system.

2209: Sales Order

Corrected an issue that led to an erroneous minimum order charge being placed on a sales order. If the customer originally placed an order that qualified for a minimum order charge, but then later increased their order, the system was leaving the original charge in place. The minimum order charge will now be properly re-evaluated.

2456: Sales Order

Corrected an issue tied to BTO kits within sales orders. This issue occurred when the kit had been posted but the sales order had not yet been shipped. The user could then delete the sales order detail tied to the BTO (usually due to the customer canceling the order). When the BTO detail was deleted and the system automatically performed a disassembly, the components where being placed in inventory with a cost of $0. The components are now being placed in inventory with an appropriate cost.

2457: Sales Order

Corrected an issue that caused a hard error when the user tried to delete a sales order detail that was tied to a BTO kit. The error occurred when the kit had been partially completed and posted and the user then tried to delete the detail off of the sales order.

2467: Vendor Item

Corrected an issue that left "Include In Landed Cost" checked by default even if the vendor doesn't participate in the landed cost process. The user could still uncheck the box, but the system should have defaulted the value correctly in the first place.

2458: Vendor Return Shipment

Corrected an issue that could potentially cause the wrong inventory account to be written to when the item involved had an inactive stocking record. The system will now correctly check that the stock record is inactive and write to the non-stock account instead.