Public Profile
  • Counting difference: transfer missing items to MISSING location

    Counting differences can not be transfered to a MISSING location.

    Currently, it is possible to auto acccept a counting difference, or wait until the pending cycle count difference is accepted (or rejected).


    What is preferred in practice:


    If there is any missing quantity detected upon counting, the missing quantity should be transfered to a MISSING location (instead of an adjustment out).

    Then the inventory on the counted location is correct again, and the normal warehouse processes can continue. The MISSING location can be investigated e.g. once a day.


    If there is a surplus found in the location, and the difference can be covered from the MISSING location, this should be an option too.


    Based on the Yammer topic raised by Steve Mulaik

    https://www.yammer.com/dynamicsaxfeedbackprograms/threads/1869742631116800


  • Enable mixed LP receiving and crossdock should generate 1 work per LP (not per item)

    Mixed LP receiving should generate 1 work header per LP in a crossdocking scenario.

    Currently, this is only supported for purchase orders in the location directives.

    But for a mixed LP with 3 items that must be crossdocked, when finishing the mixed LP receipt, 3 different work headers with the same target LP are generated.


    The crossdocked LP should be possible to put to staging or baydoor in 1 step.

    Currently this seems to be impossible because the target LP can not be on the user location and a different location at 1 moment of time.


    Also take into account the ASN + crossdock scenario where I want to get 1 work per SSCC (single SKU or mixed).


    The crossdocking of single SKU LP is working OK

  • Location directive name and location directive action name should be editable

    To give a clear picture without the need to step into the queries, the Location directive name and location directive action name should be editable.


    On the location directive, the name can not be changed. So in case of a typo or a slight change in the query, the only option is to copy the location directive and fill in a different name.

    Poposal: Add a function to change the name of the location directive.


    On the location directive action the name can not be changed either.

    Poposal: Add a function to change the name of the location directive action.



  • Inbound load planning workbench: add filter Vendor

    Inbound load planning workbench: add filter Vendor

    The new feature New load planning workbench pages adds an inbound load planning workbench which is ca 3 times faster than the classic LPWB :-)


    Often there are hundreds of suppliers, so it makes sense to only view the lines for a specific supplier.

    Proposed addition: a filter box for the vendor ID (next to the existing filters for supply & demand filter, site, warehouse, ship and receipt date) would mean a giant step for better useability.

    In this box, optionially enter a vendor account ID, or the first characters of the search key (same as when entering a new purchase order header).

  • License plate confirmation should be enabled for PO put and other type of work

    License plate confirmation (enforce on the mobile device menu item) is currently only supported for sales order pick work in a staging location and apparently also raw material picking.


    Scenario:

    Pallets are received on purchase order, labeled with LP number. Then the fork lift brings and drops the pallet at the start point of the high bay aisle.

    At this point (location type staging, as specified in WHS parameters), the high bay truck should be system-directed to pick up that pallet and validate that he picks up the right LP.


    I use a pick-put-pick-put work template, but there is no way to enforce that the right LP is picked up.


    Similar case was raised for replenishment.

    "Issue 524929 - By design

    License plate confirmation does not work for staged inventory in Replenishment".

    Solution was to change the help text.....





  • Consolidate license plates should be enabled for cross docking LPs on staging location

    Consolidate license plates should be enabled for cross docking LPs on staging location.


    For sales picking work on a staging location, the mobile device menu item Consolidate license plates can be used if these target license plates are for the same shipment.

    For cross docking work with a pick-put-pick-put (via a staging location), this functionality should be possible as well if these target license plates are for the same shipment.

  • Allow split during ship confirm - default parameter

    On the load template, there is a check mark Allow split load during ship confirm. This checkmark is inherited to the load when the load template is set on the load. But when the load is created from wave processing, there is no load template, and thus the checkmark is not set.

    Proposed solution is to create a new Warehouse management parameter for

    default load template inbound and default load template outbound, or

    default parameter for Allow split during ship confirm for initialisation on the load when there is no load template.


  • Work exceptions log - Receiving should log item number and dimensions and load ID

    The work exceptions are evaluated regularly by the warehouse manager. For analyzing, the data should be as complete as possible.


    When the mobile device worker selects a work exception (type Receiving) upon receipt of a load line (or purchase order, transfer receipt), some existing fields in the table WHSWorkExceptionLog are not populated:

    Item number

    Config, Color, Size, Style

    Site, Warehouse

    Batch, serial number

    Load Id.


    The purchase order number and line number are filled, so it should not be difficult to populate the before mentioned fields.



  • Store commerce app - Enable barcode scanning in order fulfillment operations pick and pack

    The barcode scanning experience should be enabled for order fulfillment operations Pick and Pack.


    Scenario:

    Sales order for item A, item B, item C, item D.

    These items should be picked first, but not packing slip updated yet.

     

    In the store commerce app, order fulfillment operation we want to scan all barcodes for the sales order in random sequence. This should change the line state (inventory transaction status) to picked.

     

    Current option is to select the line and mark it for being picked, but the form is not enabled for barcode scanning.

    When you need to scan e.g. 5-20 customized products with unique barcodes per sales order validation through barcode scanning is a must.

  • Mobile packing - scan target LP to find shipment

    In the new mobile packing process, the worker can lookup the shipment in a list through data inquiry.

    This is not workable if dozens of pick bins arrive at the packing station at the same time, and it is also not a secure process.


    It should be possible to scan the target LP (tote, bin etc) instead (just like in the PC packing station).