Enhancement or Fault Number

Item  Description

New Feature

Add new FM Sound Functionality and Windows CE Device support for playing .wav sound files on the Falcon X3 and Motorola MC-3190.  This includes the ability to play different sounds for "Not on File", �Error�, �Inform/Alert�, �Question�, �Record Not  Found�, and �Deal Days� events.

(CRD 303123 / FSD 303123)

New Feature

Add functionality to General Import and SIL to exclude "on file" items from being imported.

(CRD 303134 / FSD 303134)

New Feature

Add "You Saved" to SIL and General Import support.

(CRD 356276 / FSD 356276)

New Feature

Add FM support for the Motorola MC-3190/Win CE 6.

(CRD 356286 / FSD 356286)

New Feature

Add browse capability to Parameter Maintenance for parameters that require a directory path or a file name to be entered.

(CRD 363452 / FSD 363452)

New Feature

Add RBO/ABO Central Interface. This is an interface to NCR�s ABO (Advanced Back Office) Central product.  It includes an export template for exporting movement and prices to ABO Central, an ABO Host ID record for managing the export and options used when processing ABO generated SIL files, and lastly, improved handling of Allowance and Discount Percent adjustments based upon new Host ID parameters.

(CRD 378735 / FSD 378735)

New Feature

Add capability to export an invoice to a .csv file

(CRD 383412 / FSD 383412)

WD 303009

On-line Help needs updated for FM Flex Data Collect.

In FM Flex Data Collect Parameters, under �Options�, the �Max Qty and �Execute @� boxes were removed in a prior release and help needs to reflect these changes.

WD 303022

On-line Help does not exist for the Misc. Alpha 3 field in Item Maintenance.

WD 303106

The database backup control string log contains an incorrect error message if the user logged into the Retalix Control String service does not exist on the server where the Alternate Location backup is to be copied.

Scenario:

1. The RBO database backup is setup to backup the database files to an alternate location on a different server

2. The login user for the Retalix Control String service does not exist on that server or have appropriate �write� access to the Alternate Location backup directory.

Expected Results: An appropriate error message is written to the control string log to describe the Alternate backup issue.

Actual Results: A message indicating that there is not enough space at the Alternate Location is written to the control string log.

WD 303220

Intermittent issue with movement not pulling from ISS45 V8 on a Windows XP system.

Scenario:

An RBO Backoffice task is scheduled to pull movement from ISS45 V8 on a Windows XP system.

Expected Results: The movement is successfully pulled.

Actual Results: Intermittently, the movement is not being pulled and there is no logging to indicate why it failed.

WD 303224

Unable to launch the Getting Started Wizard from the ISS45 Office menu on a system with Windows 7 or Windows 2008 Server.

Scenario:

Open the Getting Started Wizard in the ISS45 Office menu from an RBO server or client system.

 Expected Results: The Getting Started Wizard opens successfully.

 Actual Results: The error message: �Windows cannot find -USER=ADMIN� is raised and the application is not opened.  

WD 336601

Some RBO applications cannot be launched via the ISS45V8 Office BackOffice menu on Windows 7 RBO client systems

Scenario:

On an RBO Windows 7 client, try to open any of these applications from the ISS45 Office menu: Batch Manager, Release Manager, SIL, or FM Parameter applications.

Expected Results: These applications open successfully.

Actual Results: These applications do not open and an error like the following is received: �RBO Batch Manager has stopped working�

The Event Viewer Application log contains:
ID 1001 - Windows Error Reporting - an APPCRASH on the RBO executable - such as rbobatmgr.exe
ID 1000 - contains the faulting RBO application and the faulting module, which is the same regardless of the RBO application:

WD 337165

The RBO BackOffice Task to backup the RBO database is not shrinking the transaction log on a system running SQL Server 2008.

Scenario:

Schedule a full backup of the RBO database

Expected Results: When the backup completes, the RBO transaction log (RBO.log) file size should be reduced to 1 M.

Actual Results: When the backup completes, the RBO transaction log (RBO.log) file size is unchanged.

WD 353424

RBOFM on a Symbol 9090 handheld with Windows Mobile 5 cannot communicate with the Host system due to a TCP/IP error.

Scenario:

1. Go into RBOFM Diagnostics and try to Connect to Host

Expected Results: Connection should succeed
Actual Results: Connection fails with a TCP/IP error. The error that is recorded in RBOFM.txt is the following:
CRBOSocket::Connect(2): connect() failed.
WinsockErrorNumber=10049 WinsockErrorName=WSAEADDRNOTAVAIL.

WD 354251

Cannot launch applications in the Navigator when the available Windows Display Setting is different than the default: Small 100%Scenario:
1. Set the Window Display Setting to Medium-125% or Large-150%
2. Open the Navigator
3. Open a Folder such as 'Item Maintenance'.

Expected Results: There are icons displayed for the Item Maintenance applications and they can be opened successfully.

Actual Results: There are no icons displayed and when you try to launch an application, nothing happens.

WD 354366

Some Item Parameters should display a message when changed indicating that the FM Item Server service should be restarted for changes to take effect.

Scenario:

Change any of the following Item Parameters and save changes.

- Force POS Description to Upper Case 
- Set Receivable Flag for New Receiving Packages
- Set Orderable Flag for New Receiving Packages
- Default Supplier ID
- Enable Item Group Code Pricing
- Copy Ad-Level in Group Code Pricing - ScanMaster only
- Enable You Saved Maintenance
- You Saved Pricing Method - ScanMaster only
- You Saved Temp Batch Ad Level - ScanMaster only
- Item's Department Flags Follow - ScanMaster only
- Enable Temp Batches
- You Saved Bonus Buy Type - V8 only

Expected Results: When the changes are saved, a message is raised indicating the FM Item Server service should be restarted.

Actual Results: When the changes are saved, no message is raised.

WD 364161

On-line help and the RBO User's Guide are updated for the enhancements made in the 4.08.01-050 release.

WD 364308

Sorting on: 'Batch Change Date and Time' in Item Maintenance does not work which is helpful for printing tags.

Scenario:
1.Open a Permanent or Temporary batch in Item Maintenance on the screen or handheld.

2. Change a few items but not in Item Number order

3. Choose �Review/Edit Batch� from the View menu

4. Choose �Sort Data� from the View menu

5. In the Specify Sort Columns window, change the Sort Column to be on the field: 'Batch Change Date and Time� as the Sort Column.

Expected Results: The items will be listed in the order in which they were changed.

Actual Results: The items are not listed in the order in which they were changed.

WD 371057

The Auto-Apply functionality indicated by the Header (H09) value in the SIL files doesn't get applied to the temporary batches generated from the TPR and Ad prices in these files.

Scenario:

1.   The system parameter: �Process TPR/Ad Fields into Temp Batch(es)� in the Host tab is set.

2.   A SIL file is processed that contains prices in the Sale (F135-F138) or TPR (F181-F184) fields and the H09 header field set so that the generated batches will auto-apply.

Expected Results: All batches generated by the SIL file are applied automatically after processing completes.

Actual Results: The Temporary batches generated by the prices in the Sale (F135-F138) or TPR (F181-F184) fields do not get applied automatically. 

WD 371543

When processing host files that contain split sale prices for ScanMaster, the Item Type in the generated Temp batch is incorrectly set to 'Unit' if the regular price in the file is a unit price or is not included.

Scenario:

1.   The system parameter: �Process TPR/Ad Fields into Temp Batch(es)� in the Host tab is set.

2.   Process a SIL or General Import file containing a Regular Price: 1/0.65 and Sale Price: 2/1.00 for an item.

Expected Results: The Item Type is set to �Split� for the price: 2/1.00 in the generated Temporary batch and to �Unit� for the price: 1/0.65 in the generated Permanent batch.

Actual Results: The Item Type is set to �Unit� and the price becomes: 1/1.00 in the generated Temporary batch to match the Item Type in the generated Permanent batch which has the price: 1/0.65.

WD 372893

The cost and adjustment values display 0.00 and the dates display as blank in FM Item Maintenance when you append/re-open an existing batch.

Scenario:
1. Create a FM Item Maintenance parameter file with Apply Mode = Later and Display Fields that include: 302-Base Cost, 303-Cost DT, 304-Unit Cost, 306-Adj Case Cost, and 307-Adj Unit Cost.
2. Create a permanent or temporary batch in screen or FM Item Maintenance with one or more changes.
3. Open the batch created in step 2 in FM Item Maintenance.
4. Query an item that has current non-zero costs and adjustments.
Expected Results:The fields listed above display the correct values for the item.

Actual Results:The fields listed above display 0.00 for the cost and adjustment values and a blank value for the dates.

WD 373430

A Powerbuilder error occurs in screen Receiving when using the '+' key to enter new line items followed by an invoice adjustment.

Scenario:

1.   Set the system parameter: �Add Mode Key� in the Receiving tab to: �+�.

2.   Create a new invoice in screen Receiving.

3.   Enter an Item Number and Qty into the invoice

4.   Use the �+� key to advance to the next line.

5.   Enter a different Item Number which has an Order Code defined in its item record and then a Qty into the invoice.

6.   Use the �+� key to advance to the next line.

7.   Choose the �Invoice Adjustments� menu option.

Expected Results: The Invoice Adjustments window opens.

Actual Results: A Powerbuilder error is raised.

WD 379148

When multiple Allowances with the same start/end date but different Allowance numbers are imported for an item thru SIL, only one gets saved to the batch

Scenario:
Process a SIL file that contains multiple Allowances with the same start/end date but different Allowance numbers specified in F222 for one or more items
Expected Results: Each Allowance has a unique Allowance number for each item that is written to the batch

Actual Results: Only the last Allowance sent for each item is written to the batch

WD 381467

General Import is creating a duplicate 'Can or Bottle Deposit' when it is being imported for a secondary receiving package and an identical one already exists on the primary receiving package.

Scenario:
1. Create an item with 2 receiving packages:
2. Import a Can or Bottle deposit for the Primary receiving package
3. Apply the batch
4. Import a Can or Bottle deposit for the secondary receiving package
5. Apply the batch

Expected Results: Query the item. Only 1 Can or Bottle deposit should exist for each receiving package

Actual Results: Query the item. 1 Can or Bottle deposit exists for the primary receiving package but the secondary receiving package has 2 which are duplicates

WD 381469

General Import is generating an error when a 'Can or Bottle Deposit' is being imported for a secondary receiving package  and an identical one already exists on the primary and secondary receiving package

Scenario:
1. Create an item with 2 receiving packages:
2. Import a Can or Bottle deposit for the primary receiving package
3. Apply the batch
4. Import a Can or Bottle deposit for the secondary receiving package
5. Apply the batch
6. Query the item and verify that a 'Can or Bottle Deposit' has been added to both receiving packages.
7. Delete the batches generated above.
8. Import a Can or Bottle deposit for the secondary receiving package

Expected Results: General Import does not error when importing the 'Can or Bottle deposit' and when you review the batch only one is present for each receiving package
 

Actual Results: General Import generates an error: "Update failed..." in the error file. And in syslog there are details of a PK violation on order_pkg_adj

WD 383032

When processing a file in General Import with new costs, it sometimes changes an existing receiving package record to have a different Supplier ID instead of creating a new receiving package

WD 383998

RBO is not properly handling maintenance batches that contain a delete of an item and one that re-adds the same item

Scenario:
1. RBO processes a SIL file from host that contains 'REMOVE' maintenance for a set of items followed by 'ADDRPL' maintenance for a subset of the same items because they are corrections (re-adds).
2. One batch is created for the 'REMOVE' maintenance (deletes) and a separate one for the 'ADDRPL maintenance (Add/Replaces)
3. Full Stage is run or the two batches are staged

Expected Results:

1. Only the item Deletes that are not included in the Add/Replace batch should be marked in the Release Manager as "ITEM TO BE DELETED"
2. Those items that are included in the Add/Replace batch will be in the Release Manager as regular maintenance (and not a delete) and their corresponding Delete maintenance record is ignored.

Actual Results:
1. All of the item Deletes are marked in the Release Manager as "ITEM TO BE DELETED", even though some of them are in the newer Add/Replace batch which were sent as corrections for the accidental deletes. As a result, when the items are released, all of them will be deleted including the ones in the Add/Replace batch