Enhancements

This section describes the enhancements that are available in this production update.

Each Piece Scan option for Cycle Count

An Each Piece Scan option has been added to the RF Cycle Count menu. You can use this option to perform these tasks.
  • Scan each unit of an item into predefined LPN/Box IDs
  • Scan EAN number for each quantity against a Location and LPN/Box ID
  • Scan one or more items for a scanned LPN/Box ID
  • Receive new inventory into warehouse using blind no ASN option from this menu
  • Trigger a system move if the scanned LPN exists in a different location than what you scanned for the cycle count
  • Click F4 (Complete Scan) to close the location count
  • View the summary of scanned items during the capture of cycle count

You cannot scan each piece for a cycle count of an item if the piece is configured for serials capture, catch weights, or summary weights. If the cycle count discrepancy rule is configured for the item, then the discrepancy rule works as specified.

If the cycle count task exists for location, item and LPN, and LOT, then after each piece scan is performed, the corresponding task is updated.

If you scan an alternate item, the barcode UOM associated to it and the quantity of the article picked increase by master units count configured to the Barcode UOM. For each subsequent scan, the scanned quantity is increased by UOM units. To support this functionality, the Barcode UOM for Each Piece CC scan field has been added to these pages:
  • Item page on the Alternate tab
  • Alternate Item page

EXT UDF fields added to the SPS API Override Strategy page

These extensible (EXT) user defined fields have been added to the Data Field field on the Conditions and API Data Override tabs on the SPS API Override Strategy page:
  • Order
  • Carrier
  • Ship From
  • Ship To
  • Bill To
  • Facility
  • Owner

You can use these fields for reference purposes in the conditions and overrides in the strategy.

Import and Export by format in Form Designer

With this enhancement, you can export or import a single or multiple form designer changes at the form level instead of module level. Modules and forms are no longer displayed separately in the Design List page; instead, a list of the changed forms is displayed. You can export a modified form from the source environment that is in any status, such as Released, Saved, Design, or Publish. When the same form is imported, the form status is imported in the status of Saved or Released in the destination environment based on the existing changes.

Widget properties added to Form Designer list view

With this enhancement, you can change the Form properties of the widget on the list view at the enterprise level. In addition to the List Name field, these property fields are available within the Properties section on the Form Designer page:
  • Hidden

    When set to True, the widget is no longer visible in the list of the screen.

  • Read Only

    When set to True, the application user cannot edit the values of the widget.

  • List Personalization

    When set to False, the widget is no longer visible on the List Personalization page .

These properties are disabled for the widgets that are out-of-the-box mandatory for the list view form, which means fields that are not available in List Personalization page.