RBO Version 4.08.00-050 Release Table

Enhancement or Fault Number	Item Description
New Feature	Support RBO installations on Windows 7 and Windows 2008 Server 64 bit versions.
New Feature	Add the ability to open the Ad Markdown report directly from the batch manager window so that it can be easily accessed for a specific batch. (CRD 317297 / FSD 317297)
New Feature	For ISS45 V8 add PLU Maintenance > Parameter 1 > Exclude From Promotions flag field to RBO. (CRD 338759 / FSD 338759)
New Feature	For ISS45 V8 add PLU Maintenance: 'Linked Items' field to RBO Item Maintenance. (CRD 344631 / FSD 344631)
Updated Feature	Need option to keep MRD logs so that they are not overwritten when service is restarted. (CRD 303214 / FSD 303214)
WD 303012	File Sync - Trailing blank on Bonus Buy Pricing Description field cause out-of-sync condition.
WD 303069	Lowest Price Wins parameter is overridden by Priority Level in Batch Manager. ALL POS' If Lowest Price Wins parameter is checked, and the Priority Level is changed to something other then 0-REGULAR PRICE in batch manager the Hierarchical Pricing will be considered for those items in that batch instead of the "Lowest Price Wins" . Example: 1. I have batch A with item 1 in it at $.99 and batch B with item 1 in it at $1.99. 2. The Lowest price wins parameter is checked in parameters. 3. I change the Priority Level for batch B to 2 -TPR. 4. Stage and release both of the batches and batch B will be in effect at $1.99 instead of batch A with the lowest price.
WD 303085	When doing inventory management , the case cost field is showing zero on certain items even though costs does exist on the item, within parameters, the default is set to Selling Cost, if this parameter is changed to Current cost thru the parameters then the cost does display thru the inventory management screen. The case cost should display with the default parameter of Selling Cost in effect.
WD 303143	Price changes made via item group code functionality are not auto-populating the base price values of the "linked" items. The base price is only being populated on the item which was actually changed, not the linked items, which had a price change. Base price values can not be manually entered, are only populated via a price change.
WD 303148	RBO - batches with a batch_serial > 65535 cannot be applied. ALL POS' - Batches with a batch_serial value greater than 65535 cannot be applied, edited, or copied - no errors are received. Possibly related to the maximum small integer value of 32767? The value doubled is 65534, although the problem occurs only with 65535 and greater.
WD 303189	RBO - SIL - SBE creates a "bad" SIL file if the batch description contains a comma. ALL POS' If a batch, containing a comma in the batch description, is exported to SIL a "bad" SIL file is created. The SILprocess.log file contains the following error message, but no pop-up error is received, so the end user is unaware there is an issue with the generated SIL file: 05/09/11 03:48:50 PM silOutInsertRow() failed 05/09/11 03:48:50 PM KEY COLUMN 1.0 NOT PROVIDED
WD 303199	Cannot export a batch that contains changes to the field: '# of Facings' (F191) having 4 digits. ALL POS' Cannot export a batch that contains changes to the field: '# of Facings' (F191) having 4 digits. We can enter a 4 digit number in the #of facings field in RBO (value range is 1 - 9999) but when we export the batch to SIL, items with a 4 digit facings number do not get put in the batch. The RBO 4.7.1 SIL Programmer's Guide says the max length for F191 (Facings) is 4.0. I tested on a 4.7.1 lab - pulled up an item in immediate maint, changed the price and assigned a 4 digit # of Facings field value (form item maint > shelf/label scales tab > shelf management section), and then exported the batch to SIL.Bill was correct; the item number was not inserted into the SIL file. The SILprocess.log file contained the following: 07/05/11 01:26:58 PM silOutInsertRow() failed 07/05/11 01:26:58 PM BAD NUMBER VALUE (TOO MANY DIGITS NN [IN NN.DD] FOR THIS COLUMN, MUST BE <= 3) IN COLUMN F191
WD 303228	SBE Maint generates field 11 in header with value 9999366, this cannot be processed when sent to Scanmaster.Take a RBO batch, run Sil Batch Export Maint against it look in default directory Retalix/Common/Communications/Host/Outbox for SBEStoreX.SIL file field H11 is Purge Date - per SIL Specifications doc
WD 315527	When doing Store transfers in Inventory Management with the system parameter set to use 'Current Cost', adjustments should be included if applicable in the cost of the transferred items.
WD 317289	Intermittently, when the Batch Manager is opened, the Permanent or Temporary View has no columns displayed. Batch_mgr_reset.sql is being run to fix the issue when it occurs as a workaround.
WD 317351	FM services are intermittently dropping and scheduled tasks sometimes don't run. These issues seem to be occurring when there is an MRD error being reported in the Event Viewer as the following: - 1000 - "Faulting application MRD.exe, version 0.0.0.0, faulting module msgrtdll.dll".
WD 317354	RBO is still using the last applicable "Received" cost when it is calculating and recording the "Selling" cost into Movement History and the item is no longer being received via DSD. The cost in this case, will become out of date as new costs are entered into the system and the item is not being received via DSD. This issue is reflected in the "Cost" field of a Host Export and in several Item/Movement reports since it is a calculation of cost of goods sold: movement * cost (where cost is either a "Received" or "Current" cost). Scenario: 1. system Inventory parameters: 'Keep DSD Inventory' is checked and 'Inventory Method' = 'FIFOor 'LIFO' 2. an item is being received via DSD and sold for some time period so the cost that is being recorded in Mvmt History is the "Received Cost" from the DSD buckets 3. the store stops receiving the item via DSD 4. a new "Current" cost for the item is entered into Item Maintenance 5. The item is sold and movement is processed causing the existing inventory bucket(s) to be depleted Expected Results: the "Current Cost" should be used in the calculated "Selling" cost that is recorded into Movement History once the inventory buckets are depleted Actual Results: The last applicable "Received" cost continues to be used in the calculated "Selling" cost that is recorded into Movement History even though the inventory buckets are depleted and the "Current Cost" of the item has changed
WD 319030	RBO Price Management doesn't automatically handle the case where a Host sends down a temporary price change which is an increase over a temporary price that it previously sent. The Problem : A Host sends down a temporary price change which is an increase over a temporary price that it previously sent. The lower price will "win" assuming that both batches have the same priority which would be typical. Retailers lose in this case because the increased price that was sent by Host is usually associated with an increased cost which the retailer would absorb unless they manually end the lower price that was originally sent. Scenario: 1. Process a SIL file from a host that contains temporary price changes 2. Process a 2nd SIL file from host that contains temporary price changes some of which are higher in price than in the first file but the priority assigned to the batch(es) is the same as the first Expected Results: The temporary price that should take effect, is the one sent in the 2nd file because the host system intended for it to replace the one previously sent. Actual Results: The lowest temporary price is the one that takes effect based upon RBO's current Price Management rules
WD 320411	An Item's Net Adjustment value is doubled and Adjusted Cost values are incorrect in FM Item Maintenance and FDC when the same item is queried in a separate session. Scenario1 - FM Item Maintenance: 1. Create an FM Item Parameter that has 305 - Net Adj, 306 - Adj Case Cost, and 307 - Adj Unit Cost in it. 2. Put a cost and adjustment on an item in screen Item Maintenance, noting the above values 3. Open FM Item Maintenance using the parameter defined above and query that item 4. Open a separate FM Item Maintenance session using the parameter defined above and query the same item Expected Results: The values for fields: 305- Net Adj, 306 - Adj Case Cost, and 307 - Adj Unit Cost are correct Actual Results: In the 2nd FM session, the value for field: 305- Net Adj is doubled and the values for 306 - Adj Case Cost, and 307 - Adj Unit Cost are incorrect since they are based upon the Net Adj Scenario2 - Flex Data Collect: 1. Create an FM Flex Data Collect Parameter that has 305 - Net Adj, 306 - Adj Case Cost, and 307 - Adj Unit Cost in it. 2. Open FM Flex Data Collect using the parameter defined above and query the item defined above that has a cost and adjustment 3. Enter the values for the fields being collected and then Quit the session 4. Open a new FM Flex Data Collect session using the parameter defined above and query the same item Expected Results: The values for fields: 305- Net Adj, 306 - Adj Case Cost, and 307 - Adj Unit Cost are correct. Actual Results: In the 2nd FM session, the value for field: 305- Net Adj is doubled and the values for 306 - Adj Case Cost, and 307 - Adj Unit Cost are incorrect since they are based upon the Net Adj.
WD 320573	When using Flex Data Collect for Inventory Management, the cost values displayed in fields 796 and 799 should be consistent with what is recorded for the Item cost in the inventory transaction. Specifically, they should be based upon the corresponding Inventory cost parameter setting. Currently, they display the following: 796 - always displays a base case cost (no adjustments) 799 - always displays a base unit cost (no adjustments) These values are inconsistent with the cost that is recorded in the inventory transaction except in case where the corresponding Inventory cost parameter setting is: 'Current Base Cost' Scenario: 1. Setup an item with a cost and allowance 2. Set the Inventory parameter: 'Store Transfer Out Cost' to: 'Current Cost' 3. Open a Flex Data Collect session and use Parameter 90 to create a Store Transfer 4. Query the item above Expected Results: The cost value displayed for field 796 should be the adjusted case cost (including the allowance) in this case, because the parameter is set to "Current Cost". Actual Results: The cost value displayed for field 796 is always the base case cost. This is inconsistent with what is expected with the parameter setting and what is recorded in the transfer which is correct. The results are similar for a parameter that includes field: 799 - Current Cost.
WD 321295	Some batches are opening very slowly. Scenario: 1. This is occurring occassionally on some batches at a customer site which have 500+ items in the batch. Their item file is large (115K+ items). 2. When double-clicking on one of these batches in the Batch Manager, it takes several minutes to open the batch and pull up the items that are in the batch. 3. Opening the same batch in Query Mode open normally. But, when "Review Items" is chosen the slowness occurs 4. Performance is normal though when we restored the same database on a different system
WD 326889	Need to improve the RBO User's Guide to provide more details on Invoice Import. We need to improve the RBO User's Guide to provide more details on Invoice Import.have had inquiries from dealers on this and more recently, a wholesaler: SuperValu. The main areas that are lacking detail are: - The Invoice Import XML format and details on the fields included - The option to "Accept Imported Invoice Cost" - The rules that are used by the import process to match to an existing Receiving package in RBO or create a new one (when "Accept Imported Invoice Cost" is being used)
WD 331635	Send to POS does not work on a new install of RBO running with Storeline 8.4.7.4000 Scenario: 1. In Item Utilities, choose Send to POS Expected Results: - An export file should be created successfully and automatically moved to the \import directory of the POS (as determined by RBO Host parameter: FastPLUExtractPath) where it is picked up and used by the POS import process Actual Results: - Progess window comes up but process never completes - The following error is in C:\Retalix\BackOffice\InStore\Utilities\export_itemPLU.log: SQLState = S1000, NativeError = 0 Error = [Microsoft][SQL Server Native Client 10.0]Unable to open BCP host data-file
WD 334776	If 'Current Cost' is selected as the Method, the cost recorded into movement history is supposed to be the current cost instead of a DSD bucket cost. The customer noticed this issue when they did a Host Export which included the "Cost" field. This field maps to mvmt_cost_amt which is a summary of the item_cost_amt value in mvmt_history. Specifically: mvmt_cost_amt = isnull(fn_mvmt_date_range.item_cost_amt, 0) which is: SUM(mvmt_history.item_cost_amt) Scenario: 1. Inventory parameter Keep DSD Inventory = Y 2. Inventory parameter Inventory Method = Current 3. Receive a couple items that have a current cost and finalize the invoice 4. Add a new current cost in Immediate maintenance for each of the items 5. Ring up each of the items and one item that was not received 6. Pull Movement Expected Results: - The cost recorded in the mvmt_history table for those items should be the current cost instead of the received cost Actual Results: - The only cost in the mvmt_history table for those items that is a current cost is on the item that was not received
WD 335765	Getting the message: "Error converting data type varchar to bigint" when running Synchronize POS Vendor Cost Fields when an item's Order Code field contains non-numeric characters Scenario: 1. An item record in RBO has non-numeric characters in the Order Code field 2. Run Item Utilities: "Synchronize POS Vendor Cost Fields" Expected Results: A batch is created with items that have out of sync cost fields and batch records that have values that don't pass validation should have their Ignore Flag set. In this case, the batch record with the non-numeric Order Code should have the Ignore Flag set because the value which has been copied to the POS Vendor Item# must be changed to a numeric value before it can be sent to the POS. Actual Results: A batch is created with items that have out of sync cost fields BUT the error described is raised and the batch records that have values that don't pass validation don't have the Ignore Flag set.
WD 338012	The RBO client install will prompt for the location of the SQL Server installation if it can't find it on the system. This is unnecessary and confusing because an RBO client only needs the SQL Server ODBC driver to run and it is present on all Windows XP and Windows 7 systems. To get around this, a user will install SQL Server tools on the client or will browse to manually enter the path to the SQL directory on the RBO server. Scenario: 1. Run the RBO install on a system where SQL Server or SQL Server tools are not installed 2. Choose 'Client' for the install type 3. Choose the system that is the RBO Server Expected Results: the install should proceed to the next step which is to choose the POS Server Actual Results: the install prompts for the location of SQL Server


	Name of Link:	CD Only
	Code Distribution:	N/A
	Posting Date:	Customer Trial January 16, 2013 General Release February 2013
RBO Version 4.08.01-050 Release Table Last updated January 18, 2013 See the table below for a description of the new features provided and faults addressed in this release. Information in this table prior to release is provided in order to assist dealers in their planning, and while they are not commitments, this list represents StoreNext's best view at time of posting regarding highly likely new feature content and faults most likely to be addressed.
Printing Instructions: many browsers do not support correct color and format printing directly from the Web. For best results, with your cursor highlight the section of the table you wish to print and copy to the clipboard. Then paste from the clipboard into a blank Word document and print the Word document to a color printer.