One Step Retail Solutions Community Forums
Home      Members   Calendar   Who's On
Welcome Guest ( Login | Register )
      

Home » One Step Data » General discusion » Retail News » October Updates 8.51/8.4/SRO


October Updates 8.51/8.4/SROExpand / Collapse
Author
Message
Posted 10/27/2004 10:55:24 AM


Forum Member

Forum MemberForum MemberForum MemberForum MemberForum MemberForum MemberForum MemberForum Member

Group: Forum Members
Last Login: 5/27/2005 1:56:00 PM
Posts: 103, Visits: 1

 

 

         Retail Pro BTF-Series 8.4/8.5

Update Release Cycle

RPro v8.51 Core  

Updated executables Contained in the October RPro v8.51 Core update:

Core Files:

Rpro8.exe, Rpro_Api.bpl, RDA2.dll, ms_ie_d5.bpl, RPRO_API.bpl, vcl50.bpl, vclie50.bpl, SRO.exe, Custexport.exe, cprocin.exe, mprocin.exe, rprocin.exe, Rpro8.sec,

TS23_Pulse.pdf, Pulse.hlp, V8_3_DeptVend.pdf, V8_9_Customers.pdf, Rpro8.cnt, Rpro8.hlp

 

Tools:

 SRO.exe

 

 

Issue ID: 

13219

WebTAC ID:

19563

Area:

General System

Severity:

3 - Moderate

Title: 

Random order of values for AUX fields displayed in Filter view

Description: 

The values displayed for the AUX fields in a Filter design are not displayed in either the order entered or in alphabetical order.  They appear to have no pattern, which makes it difficult to find the item you which to use as the criteria.

 

For example, added the following values to AUX1 - c,a,b,d.  In Inventory > Filtered View, the AUX1 field shows the following order - a,b,d,c.  I then added a value of "e" to the list.  They're now ordered as - a,d,b,c,e.

 

When creating an item in Inventory, the order is shown as alphabetical.  When returning to Preferences, the order is alphabetical.  Filter View should display them as alphabetical as well.

Resolution:

In Inventory filter view, AUX fields' values are sorted in alphabetical order.

 

Issue ID: 

13569

WebTAC ID:

 

Area:

Receipts

Severity:

2 - Serious

Title: 

Customer Defined Price Levels defaults to Active price level if no value is set, and it should default to the price level on the document.

Description: 

If you are using Customer defined price levels and priced based stores then if you list a customer on the receipt it will change your price level to whatever the active price level is in inventory instead of using the level defined for the price based stores.

 

If you are using price based stores, and customer defined price levels, then if the customer does not have a level defined it should default to the price based store level, and not the active price level.

 

Resolution:

If System Preferences are set up to use price based stores and customer defined price levels, then if the customer does not have a level defined , the price on a receipt defaults to the Active price level as set in inventory, not to the price based store level.  With this fix, the receipt price now defaults to the price-based store level instead.

 

 

 

Issue ID: 

13688

WebTAC ID:

 

Area:

Tools - Other

Severity:

2 - Serious

Title: 

SRO.exe: Does not calculate On Order Qty for Marked-For POs.

Description: 

SRO.exe: Does not calculate On Order Qty for Marked-For POs.

 

 

Resolution:

SRO.exe now takes "Marked For" PO into consideration when calculating for Cmp On Order Qty and Store On Order Qty.

 

Issue ID: 

13741

WebTAC ID:

 

Area:

Tools - Pulse

Severity:

4 - Low

Title: 

Documentation specifies the wrong location for "Location of the pulse data base"

Description: 

"Path to the RPRO folder containing the pulse database" should be the Retail\RPro folder. not the

Retail\Rpro\pulse\data folder as specified in the documentation on page 12 section 5.1 step 3

Resolution:

The following files have been updated in the Pulse documentation:

TS23_Pulse.doc

TS23_Pulse.pdf

The following files have been updated in Retail Pro help:

Pulse.hlp

 

Issue ID: 

13807

WebTAC ID:

 

Area:

Vendors

Severity:

4 - Low

Title: 

Vendor notes field is limited to 243 characters.

Description: 

Documentation for the vendor notes field says this fields cap is 310. I was only able to enter 243 characters in 8.5 and 8.4.

 

Resolution:

The documentation has been updated.

 

Corrected the Vendor Note field and Customer Note field descriptions to state that the field holds 243 characters. The following E-Manual contents have been updated:

V8_3_DeptVend.doc

V8_3_DeptVend.pdf

V8_9_Customers.doc

V8_9_Customers.pdf

The following Help Files have been updated:

RPRO8.cnt

RPRO8.hlp

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Issue ID: 

14156

WebTAC ID:

25738

Area:

Customers

Severity:

5 - Change Request

Title: 

Request Customer Export Tool have functionality to export inactvie customers.

Description: 

Request Customer Export Tool have functionality to export inactive customers.

 

 

 

Resolution:

There is now an option in the Customer Export dialog "Export inactive customers".When selected, inactive customers will be included with the Customer Export.

 

Issue ID: 

14198

WebTAC ID:

 

Area:

Security Manager

Severity:

5 - Change Request

Title: 

Request to be able to restrict users making Out Slips to the available quantity.

Description: 

Currently if you are set to Check Availability for Out Slips you can make an Out Slip and place an item on it with a quantity greater then the Available qty.  You receive a message but you can still select to transfer more then you have.  Can we add a setting in SecAdmin to restrict OutSlips to the quantity on hand only?

 

 

Resolution:

An option was added to enforce Checking Availability, Outslips cannot be created if the quantity listed was over the On Hand Quantity.

 

Issue ID: 

14242

WebTAC ID:

26577, 26665

Area:

Receipts

Severity:

3 - Moderate

Title: 

Quantity based pricing is not updating the price when price level 1 is first applied to the receipt

Description: 

Quantity based pricing is not updating the price when price level 1 is first applied to the receipt

 

 

 

Resolution:

The customer price level was being applied to items first and then to the document.  This caused quantity discounts to be recalculated based on the old price level. Now  the document global price level is changed first, and then and only then to all items.

 

Issue ID: 

14372

WebTAC ID:

 

Area:

Sales Orders

Severity:

2 - Serious

Title: 

Deleting an SO with items with serial numbers, these serial numbers do not get available again. After poling they are still marked as "SO - reserved"

Description: 

When we delete a SO with items with serial numbers, these serial numbers do not get available again. After poling they are still marked as “SO - reserved”

 

            I make at a POS station a SO - layaway with full serial items on. I put the serial numbers on every serial number item.

      &nb