Implementing shipment-based backroom pick in Store Inventory Management (SIM)-disabled stores

Configuration

Pick orders portlet

• The portlet displays the total and individual count of shipments with the status of Ready for backroom pick or Backroom pick in progress.
• The getShipmentList API is called and the shipment status, document type, and delivery method is passed to get the shipment count. The delivery method is passed to the API based on the resource permissions.
• The store associate can also scan the order number or shipment number in the portlet. On scanning, the translateBarCode API is called with BarCodeType=”StoreOutboundShipment”.
  • If multiple translations are returned, a list of shipments is displayed.
  • If a single translation is returned and the shipment has the Ready for backroom pick or Backroom pick in progress status, the Pick order page is displayed.
  • If a single translation is returned and the shipment has a status other than than Ready for backroom pick or Backroom pick in progress, a confirmation is shown and the Shipment summary page opens.
  • If bar code input does not match any order number or shipment number, an error message is displayed.

Pick orders list page

• A store associate can click the In progress, Not started, or Shipments counts in the portlet to view the shipment list filtered based on status and delivery method. The Shipments count lists the shipments with the following statuses:
  • Ready for backroom pick. The Pick order button is displayed.
  • Backroom pick in progress. The Continue pick button is displayed
• On clicking Pick order or Continue pick, if the AssignedToUserId is different from the current user, a confirmation message is displayed. The current user can then choose to continue the pick or start over. If the AssignedToUserId is null or the same as the current user, the Pick order page is displayed.

Shipments list

• The shipments list is paginated. When scrolling, the getShipmentList API with pageSize: 10 is called to get the next set of shipments that are appended to the existing shipments list.
• If no shipments are present, a message is displayed.
• The shipments list can be sorted by ExpectedShipmentDate. The default sorting is Oldest to newest.
• The shipments list can be filtered based on the user to whom the pick request is assigned, status, and order type.
  • Assigned to lists all the users of the logged in store by calling the getUserList API. The same user list is used to display the users under Assigned to.
  • Status displays Ready for backroom pick and Backroom pick in progress checkboxes.
  • The option to sort by Order type is displayed only for the Ship delivery method as Ship orders can have different typed such as Sales order and Transfer order.

Pick orders execution flow

• When a store associate clicks Pick or Continue pick in the shipments list page, the assigned to user is validated. This is to ensure that the current user does not start working on any shipment order that is being picked by another user. Once the picking is initiated by a store associate, it is assigned to that associate.
• The assigned to user ID is stamped on the order when the store associate initiates the shipment order by clicking Pick or Continue pick or when the store associate scans the order number or shipment number from the portlet.
• The getShipmentDetails API is called to get the AssignedToUserId, which is then compared to the current user.
  • If AssignedToUserId is null, the changeShipment API is called to update AssignedToUserId and the Pick order page is displayed.
  • If AssignedToUserId is the current user, the Pick order page is displayed.
  • If AssignedToUserId is different from the current user, a message is displayed to confirm if the current user wants to continue the pick or start over.
    • If Start over is selected in the displayed message, the changeShipment API is called to update the shipment with the following information:
      • The AssignedToUserId is updated on the shipment.
      • For serialized item, ShipmentTagSerials is removed from the ShipmentLine.
      • The BackroomPickedQuantity and StagedQuantity is reset to 0.
    • If Continue is selected in the displayed message, the changeShipment API is called to update AssignedToUserId on shipment.
• In the Pick order page, the shipment line is displayed with other details such as item, quantity, and the shorted products.
• The product list is displayed based on the pick location sequence on the shipment line.

  The PickLocation and PickLocationSeq attributes on the ShipmentLine element must be populated by implementing the YDMBeforeCreateShipmentUE user exit.

• The Pick order page lists the shipment lines along with the primary information of the product.

  The getShipmentDetails and getShipmentLineList API is called with ShipmentKey to display the details. The getRuleDetails API is called to know if staging location is required or not.

• For serialized products, the View serials link is displayed to show the list of picked serials.
• To pick a product, the store associate can scan a product or serial number.

  Once the store associate picks a product, the changeShipmentStatus API is called to update the shipment status to Backroom pick in progress.

  On scanning the product, the registerBarcodeForBackroomPick API is called to update the picked quantity.

• The Pick all option is displayed in the Actions menu in the Pick order page. The changeShipment API is called when Pick all is selected and all the non-serialized items are picked.
  Note: The Pick all option is displayed only if the resource permission ISF000053 is enabled.
• The Actions menu also displays the Print option. The action to print the shipment invokes the StorePickTicket_94 service. You can customize the out-of-the-box print capabilities by customizing this service or by using the following sample XMLs:
  • /template/prints/ycd/xsl/StorePickTicket_94_multiApi.xsl.sample
  • /template/prints/ycd/xsl/StorePickTicket_94_output.xsl.sample

Quantity updates

Record shortage

• If the inventory is damaged or short, the store associate can mark it as short.
• The shortage reason that is provided by default is Inventory Shortage. You can also configure custom shortage reasons to specify appropriate reasons while recording shortage. The custom shortage reason is handled the same way as Inventory Shortage. If you want the custom shortage reasons to be handled differently, you must customize to implement your own logic.
• The store associate has to select a reason for marking the pick request as short. Reasons are listed by calling the getCommonCodeList API with CodeType=YCD_PICK_SHORT_RESOL.
• Once the associate selects a reason, the changeShipment API is called on the shipment line with ShortageQty and the shortage quantity on the shipment line is updated. The record shortage mashup internally calls the changeOrder API to add record shortage notes on order line.
• When any product is picked or shorted, a check is performed to know if the shipment is completely picked or has a shortage recorded.

  If it is completely shorted, the shipment is canceled, a warning message is displayed, and the Shipment summary page is displayed.

  If the order is completely picked, but includes some shortages, then if the WSC_BP_STG_REQD rule is set to Y, the staging location window is displayed.

Assign staging location window

• When the Assign staging location window opens, the getRuleDetails API is called to get StagingLocation bar code translation rule details.
• If the WSC_BP_STG_TRAN_REQD rule is set to Y, then, on scan, the translateBarcode API is called with source as HoldLocation.
• When Done is clicked on the Assign staging location window, the changeShipment API is called to update the hold location on Shipment.
• Then getShipmentLineList API is called to validate the shipment for pick complete. This internally calls the changeShipmentStatus to move the shipment to the next status based on the delivery method.
• Once the backroom pick is complete, the Shipment summary screen is displayed.