|
Enhancement or Fault
Number |
Item
Description
|
|
New Feature
|
Add
support to log actions that create or affect a batch at the batch
level.
(CR 303025 / FSD 303025)
|
|
New Feature
|
Add support to display a barcode in the header area of the Invoice
Ticket report to uniquely identify the invoice.
(CR 399301 / FSD 399301)
|
|
New Feature
|
Condense the header of the landscape
Invoice Ticket report in Item Receiving in order to allow more
invoice detail rows to be printed per page.
(CR 420224 / FSD
420224)
|
|
WD 303070
|
SQL Error
received intermittently when quickly scrolling through a group of
item numbers in Form View.
Intermittently
get a SQL Select error: 'An invalid handle was passed in a call to
the database driver...' when quickly moving thru a group of items
using Next or Previous in Form View.
Scenario:
1. Open Form Item Maintenance
2. Retrieve a set of items that have at
least a year of movement saved and that have an Ad Hoc Start and
End Date (on the Movement tab) set which spans that time period.
3. Click on Next or Previous several
times to quickly move thru the items
Expected
Results: No errors occurs while moving thru the items.
Actual Results:
Get a SQL Select error: 'An invalid handle was passed in a call to
the database driver...' while moving thru the items. Note: the
frequency with which the error occurs depends on system
performance.
|
|
WD 303222
|
Immediate Batch
that is left open sometimes stops releasing.
Scenario:
1. Remove the 'Auto Release' field from
the Batch Manager Permanent View
2. Create a Permanent batch with 1 or
more items it and close the batch
3. Open an Immediate batch, change the
price, and save an item
4. In Batch Mgr, change the Start Date
or some other field on the Permanent Batch and choose Save.
5. Change the price of another item in
the Immediate Batch and save.
Expected
Results:
1. The price change is successful and the item is released to the
POS.
2.
The Auto-Release flag is not changed on any batch in the system.
Actual Results:
1. No error is displayed and the 2nd
price change and any subsequent changes are not released to the
POS.
2.
All batches in the system have their Auto-Release flag set to 'N'
|
|
WD 317289
|
Intermittently, when the Batch Manager is
opened, the Permanent or Temporary View has no columns displayed.
|
|
WD 317296
|
Need BackOffice
Task for the Invoice Summary Report.
Scenario:
1. Open BackOffice Task Scheduler.
2. Choose 'File - Open - Build
BackOffice Tasks' in the menu.
3. Choose 'Edit - Add' to add a new
backoffice task and then enter the Task Name: 'Invoice Summary'
4. Choose 'Edit - Add Action'and find or
enter the Action to Run: 'Invoice Summary Rpt' in the drop-down
list.
Expected Results: The 'Invoice Summary
Rpt' is available in the drop-down list and can be used to
schedule a BackOffice task to print this report.
Actual Results:
The 'Invoice Summary Rpt' is NOT available in the drop-down list
and therefore a BackOffice task to print this report cannot be
scheduled.
|
|
WD 398160
|
The RBOBatMgr
(Batch Manager) application intermittently just stops working and
a Windows error message is received indicating the executable is
being ended.
It typically occurs when the window
becomes active after using another application such as Item
Maintenance.
|
|
WD 406479
|
An item's
department-base flags are not always set correctly when an SBE
generated file containing a new item is processed into
RBO/ScanMaster.
Scenario:
On an RBO/ScanMaster system where the
POS and RBO are both set to Follow the Dept Flags:
1. Enter a new item into an Item
Maintenance batch
2. Set the upc, description, price
fields, and then the department to one that has the Food Stamp,
Tax1, and Discount 1 flags set.
3. Export the batch (with the SBE
parameter: "SIL Batch Export Add/Change as Add/Replace" off)
4. Proces the generated file back into
RBO and review it.
Expected
Results: The generated batch is identical to the original batch
Actual Results:
The itemizers show Food Stamp, Tax1, and Discount 1 flags set for
ITEM and DEPT and BLANK for RESULT, with the Override flag turned
on.
|
|
WD 407188
|
Get an
Application error when doing an Invoice Import in a 4.08.02 MU
with 'Accept Imported Invoice Cost' checked in the supplier's
record.
Scenario:
1. Set the field: 'Accept Imported Invoice Cost' in the record for
the supplier that has an XML invoice including costs to be
imported into RBO
2. Import the XML Invoice file
Expected
Results: The XML Invoice file is successfully imported and a batch
is created and staged containing the imported costs
Actual Results:
The following Powerbuilder Application Execution Error is raised:
Bad runtime function reference at line
32 in function of_create_session_batch of object u_bo_import
|
|
WD 409284
|
The weight of an NSC2 item being counted
in FM Stock Count Maintenance is not calculated or recorded
properly if it has a package price of $100 or more.
Scenario:
1. Set the Item Maintenance System Parameter: NSC2
Lookup Format to: 5 Digit Lookup if it is not currently set and
restart the FM Item service.
2. Open an FM Stock Count
Maintenance session
3. Scan an NSC2 item that has a price of
$100 or more that is currently on-file.
Expected Results:
The value displayed on the handheld and recorded in the Location
Count for this item is the calculation of the NSC2 package price
(last 5 digits excluding the check digit ) / the price per pound
recorded in the item record.
Actual Results:
The value
displayed on the handheld and recorded in the Location Count for
this item is incorrect. The application is doing a calculation of
the NSC2 package price without the hundreds digit (last 4 digits
excluding the check digit ) / the price per pound recorded in the
item record. The NSC2 Lookup Format system parameter setting is
ignored.
|
|
WD 409868
|
Some items are getting marked as ‘Return
to Regular’ but are not in an existing or recent batch.
Scenario:
On a RBO system that was originally installed with
release 4.5.3 or earlier and has had the batch_serial reset:
1.
Delete a temporary batch that had one or more items in-effect and
has expired.
2. Run a Full Stage
Expected Results:
The items that were in-effect from being in the above temporary
batch are marked as ‘Return To Regular’.
Actual Results:
Sometimes, other items that were not recently in a batch are
marked as ‘Return To Regular’ in addition to the items that were
in-effect from being in the above temporary batch.
|
|
WD 410079
|
An item doesn’t get marked as ‘Return to
Regular’ if its batch record is changed after the item is released
and then is deleted.
Scenario:
1. Create a temp batch with a
start date = today containing 2 or more item changes.
2. Verify
that the above items are not in any other batches (applied or
unapplied). Permanently delete them if any are found.
3. Run a
Full Stage and Release the temp batch.
4. Open the temp batch
and modify each of the batch records.
5. Clear one of the items
from the batch and close the batch.
6. Run a Full Stage
Expected Results: The item that was
removed from the batch is marked as a ‘Return to Regular',
allowing it to be easily returned to its regular price.
Actual
Results: The item that was removed from the batch is NOT marked as
a ‘Return to Regular' so it will continue to sell at the last
temporary price that was released.
|
|
WD 412246
|
The Pull POS Movement process doesn't
fully complete on systems running Windows 64 bit.
The
ItemUtil.exe *32 process is left open after all of the movement
records have been processed into RBO and the corresponding
ItemUtil.exe application is closed.
Scenario:
1. Ring up
some items on Storeline POS and run an EOD
2. On a Windows 7 or
2008 64bit system, schedule a task to Pull POS Movement
Expected Results: The movement is pulled successfully and the
Itemutil.exe *32 process (viewable in Task Mgr) is closed.
Actual Results: The movement is pulled successfully and the
Itemutil.exe *32 process (viewable in Task Mgr) is still open. As
a result, the next time movement is run at its scheduled time, the
process cannot be started. This is visible in the cs.log as an
error opening the .cs file. If Pull POS Movement is run manually
thru Item Utilities, it runs successfully but leaves an
Itemutil.exe *32 process open even though the application is
closed.
|
|
WD 413541
|
Get error: 'item.exe has stopped working"
and the application closes sometimes when choosing 'Clear Item
from Batch' for a selection of items in the grid.
Scenario:
1. Create a later batch with 5 item changes.
2. Choose the menu
option: 'Review Batch'.
3. In the Grid view, select the 4th and
2nd item in the batch using the ctrl key and mouse click on the 2
item rows.
3. Choose the menu option: 'Clear Item from Batch'.
Expected Results:
1. The 2 item changes are successfully
removed from the batch.
Actual Results:
1. Get error:
'item.exe has stopped working" and the application closes.
2.
The 2 item changes are removed from the batch
|
|
WD 416708
|
Full Stage performance is significantly
affected by large permanent batches even when their Ignore Flag is
set or they're already applied.
Scenario:
1. Run a Full
Stage and record the time needed for this process
2. Run an
Item File Sync on a system that is out-of-sync with the POS to
create a large, Permanent batch that has its Ignore Flag set
3.
Run a Full stage and compare the processing time with the previous
time (step 1)
Expected Results: There should be no
significant difference in processing time since the only new batch
added for the system to consider is set to 'Ignore'.
Actual
Results: The processing time for the 2nd Full Stage is
considerably slower.
|
|
WD 416787
|
The status of a Temporary batch that has
the Batch Ignore Flag set is showing "Current" instead of "Not
Staged" after a Full Stage.
This is misleading especialy since
it is displayed in Green instead of Orange so a user may not
realize that it is currently Ignored'.
Scenario:
1. Create a temporary
batch with current dates
2. Set the Ignore Flag on the batch.
3. Run a Full Stage
Expected Results:
The temporary
batch status is 'Not Staged' and it is displayed in Orange
Actual Results:
The temporary batch status is 'Current' and it
is displayed in Green.
|
|
WD 418105
|
The horizontal scrollbar in the Item
Maintenance Grid View is not in full view on Windows 7 systems.
Scenario:
1. Open Item Maintenance in Grid View
2.
Choose Edit Column Setting to select or build a view that contains
enough fields that will force the horizontal scrollbar to be
displayed
Expected Results:
The horizontal scrollbar is
in full view at the bottom of the screen.
Actual Results:
The horizontal scrollbar is cut-off at the bottom of the screen so
that only half of its width is displayed.
|
|
WD 418721
|
The Screen Receiving fields: Case Cost,
Price, Quantity, and Unit are no longer listed in the Sort and
Filter dialogs when editing an invoice.
Scenario:
1.
Open or create an invoice
2. Add some items to the invoice
3. Choose 'Sort Data' from the View menu
Expected Results:
The Case Cost, Price, Quantity, and Unit fields are listed in the
Sort dialog.
Actual Results: The Case Cost, Price,
Quantity, and Unit fields are NOT listed in the Sort dialog. They
were listed in the 4.7.1 release but not in 4.8.2.
|
|
|
|
|
|
|
