Enhancement or Fault Number

Item  Description

Certain fields are not being populated in the label_info_(POS) table if there is a blank line in the item maintenance grid when the label info is generated.

Scenario:
1. In RBO Parameters, Labels Tab, set Label Generation to: Output Label Info to Stylus or to a Database Table.

2.In Item Maintenance, open a new batch in Grid, enter 3 or more items that are on file.

3. Choose 'Insert' to insert another row in the Grid and leave it blank with the cursor and focus on this row.

4. Choose 'Export Tags' and then 'Print' in the Label Printing dialog.

Expected Results: All of the expected fields in the database table: label_info_storeline or label_info_sm are populated with the information in the rows displayed in the Grid

Actual Results: For the first 2 items in the grid, the label_info_storeline or label_info_sm table will contain Null for order_pkg_id, case_pack_ramt, supplier_id, pallet_qty, and auth_ord_flag. And the supplier_desc and sup_cat_desc will be blank.

Certain fields are not being populated in the label_info_(POS) table if there is a blank line in the item maintenance grid when the label info is generated.

Scenario:

1. In RBO Parameters, Labels Tab, set Label Generation to: Output Label Info to Stylus or to a Database Table.

2.In Item Maintenance, open a new batch in Grid, enter 3 or more items that are on file.

3. Choose 'Insert' to insert another row in the Grid and leave it blank with the cursor and focus on this row.

4. Choose 'Export Tags' and then 'Print' in the Label Printing dialog.

Expected Results: All of the expected fields in the database table: label_info_storeline or label_info_sm are populated with the information in the rows displayed in the Grid.

Actual Results: For the first 2 items in the grid, the label_info_storeline or label_info_sm table will contain Null for order_pkg_id, case_pack_ramt, supplier_id, pallet_qty, and auth_ord_flag. And the supplier_desc and sup_cat_desc will be blank.

General Import Formulas don't work on import values that contain an apostrophe

Scenario

1. An Import file contains 1 or more rows to import into RBO with some values that contain an apostrophe (i.e. Nature's Plus)

2. Enter a formula into the Import Template Field Mapping for this file to change the values described in step 1 to Lower Case

For example if the import field name is 'Brand', enter the following Formula for the field mapping lower( field:Brand )

Expected Results:

1. When the formula is entered and 'Verify' is chosen, the message: 'The formula is ok' is returned.

2. When the import file is processed, the values are successfully imported in Lower Case.

Actual Results:

1. When the formula is entered and 'Verify' is chosen, the message: 'The formula cannot be evaluated' is returned if the first row in the file

contains an apostrophe.

2. When the import file is processed, the values containing an apostrophe will have "!" imported instead of the value in the file

An 'Updatedbmt' error is being generated when an import value is mapped to the 'Misc Alpha2' field and it exceeds it maximum length of 10 characters. This causes the whole item record being imported to be rejected and this non-descriptive error message is written to the error file.

Scenario:

1. A value of: "Christopher's" was being mapped to the 'Misc Alpha2' field.

Expected Results: The value should be automatically truncated so that the record is imported successfully with a warning message written to a log to indicate that it was truncated.

Actual Results:

1. the whole item record being imported is rejected and the non-descriptive error message: 'Updatedbmt error' is written to the error file. The syslog does get a 'Bind Parameter' sql error written to it in this situation which can help Support/Development figure out what the problem is but it's not user-friendly.

The 'up_amt' field in the label_info_sm table and equivalent field: 'per_uom_price' in the label extract is zero when an item contains a Split PM/Price and zero Unit Price with RBO/ScanMaster. Additionally, the 4th digit to the right of the decimal in the calculation of this field was not a rounded value.

Scenario:

1. Set the Label Generation parameter to: 'Output Label Info to a Database Table' and save the change.

2. Enter an item into RBO Item Maintenance with a zero Unit Price and Split Price = 2/4.99.

3. Choose 'Export Tags' from the Utilities menu.

4. In the 'Label Printing' dialog, accept the default Quantity of '1' and choose: 'Print' to write this item's info to the label_info_sm database table.

Expected Results: 1. the up_amt field in the label_info_sm table is: 2.4950. Note: without the additional rounding change, this would be 2.49

Actual Results: 1. the up_amt field in the label_info_sm table is: 0

A value imported into a character based field that has an associated Edit List is rejected if it matches a value on file but has Case differences

Scenario:

1. Enter: "Nature's P" (the 1st 10 characters of Nature's Plus) into the Misc Alpha 1 field of an item record.

2. Import a file containing: "nature's plus" in a field that is mapped to the "Misc Alpha 1" field in General Import.

Expected Results:

1. The row in the import file that contains "nature's plus" is imported successfully.

2. "Nature's P" is saved to the "Misc Alpha 1" field in that batch record.

Actual Results: The row in the import file that contains "nature's plus" is rejected and a SQL error: "Violation of PRIMARY KEY constraint..." is written to the error file.

A "Return Only" or "Not Receivable" message needs to be displayed when entering an item in Screen Receiving which does not have its Receivable flag set.

Scenario:

1. In the Item Maintenance Receiving tab, set the Receivable flag for an item to "N"

2. Open an invoice in Screen Receiving and enter that item.

Expected Results:

1. An alert message is raised to inform the user that the item can only be returned.

2. The Return flag is automatically checked on the invoice line item.

Actual Results:

1. The Return flag is automatically checked on the invoice line item but no alert message is raised to inform the user that it can only be a Return.

Powerbuilder error received in Item Maintenance when 'Export Tags' is done if there is a blank line in the batch and the Labels parameter is set to 'output to a text file'

Scenario:

1. In RBO Parameters, Labels Tab, set Label Generation to 'Output Label Info to a text file'

2.In Item Maintenance, open a batch in Grid, enter an item that is on file

3. When the item is displayed, create a blank line by pressing the down arrow key or pressing the Tab Key past the end of the line item that is displayed

4. Click on the 'Export Tags' icon

5. Click 'continue' or 'OK' to the label printing messages

Expected Results: A Label text file is generated

Actual Results: The following Powerbuilder Application Execution Error is displayed:

Application terminated.

Error: Invalid Datawindow row/column specified at line 6 in function getvalue of object u_bass_datastore.

NOTE: if the Label Generation parameter is set to 'Stylus' the PB error is not generated

A 'Fractional Truncation' error occurs when running a Supplier Contribution or Supplier Profitability report on items received as decimal weight values

Scenario:

1. In Receiving, receive one or more items with a decimal weight value and finalize the invoice.

2. Run a Supplier Contribution or Supplier Profitability report with a date range that includes the above invoice.

Expected Results: The Supplier Contribution or Supplier Profitability reports should run successfully

Actual Results: A 'Fractional Truncation' error occurs and the report doesn't display any data for the supplier that had decimal received amounts.