DO Rec Scan Count

This function receives stock by having to scan each SKU – Item barcode and count the receipt this way. It is very useful in fashion where multiple sizes of the same style and multiple styles are sent back from stores and to ensure correct SoH in DC warehouses this can be used

Jira task group:

https://globalomnichannel.atlassian.net/browse/WA2-212

M3 – Settings

 

Setting

Description

MMS005/F – To Location

The to location in MMS005 is used to prepopulate a location.

Note: in earlier versions of M3 the MMS005MI will not return the To Location meaning we will not populate this. The user will have to select a location manually

MMS025 – Popular numbers

The alias number and the qty linked to it will be used in the counting logic

MWS010 – Dispatch policy

Things like use of Shipments and package (advanced packing) is used in this flow since we can received by shipment or package as well as order or delivery

MWS010 – Over receipt

Parameter 600, the function allows over receipt if M3 allows it. Note: in earlier versions of M3 over receipt of DO’s were not allowed and then it will not be allowed in WA2.0 either. Note we rely on the API to check this.

Note: the scan count logic does not allow overreceipt but if the quantity is amended manually you can receive more if the dispatch policy allows.

 

Internal Jira reference

https://globalomnichannel.atlassian.net/browse/WA2-212

Process flows

This function represents MWS442 in M3, DO receipt. 

The difference between DO Receiving and DO Rec Scan Count is that scan count is set up so that we can scan any of the items on the selection (by Package or by Delivery etc (see below) and we will validate that input and accumulate it as a quantity. The quantity is coming from the value in MMS025 or if blank one scan means 1 unit. GS1 AI including quantity: AI 30 and 37 are also considered in this functionality to be able to receive outer boxes based on standard labels.


Scope: 

System directed putaway or other To location logic. 

All different types of item and order configurations: Receipt by

  • Delivery
  • Order
  • Item or Alias
  • Lot
  • Shipment
  • Container (M3 container/Pallet ID)
  • Package (Normal M3 outbound packed packages - advanced packing is a prerequisite and unique package )
  • SSCC package numbers
  • In house packages (Container management 7)


Assumptions:

No overlap between the above different numbers 


Tip: Since we can receive by the DO order number and M3 allows to add this as a user defined number in the API to create DO's If the solution runs external systems for ex POS (Point of sales) (Retail solution) or Service Vans where the external system sends stock back to a M3 Managed DC (Distribution Centre) we don't need M3 paperwork to receive this stock it the external system generated  docket or similar with the order no that was passed into M3 we will be able to find that by using this input 


M3 settings


Setting

Description

MMS005/F – Location

The location in MMS005/F is used to prepopulate a suggested location, that can be overridden.

Note: in earlier versions of M3 the MMS005MI will not return the To Location meaning we will not populate this. The user will have to select a location manually

MWS010 – Over receipt

Parameter 600, the function allows over receipt if M3 allows it. Note: in earlier versions of M3 over receipt of DO’s were not allowed and then it will not be allowed in WA2.0 either. Note we rely on the API to check this.

MWS010 – Dispatch policy

Things like use of Shipments and package (advanced packing) is used in this flow since we can received by shipment or package as well as order or delivery

System Directed PutawaySystem directed putaway is supported in this function if we are putting away only item at the time.
MMS010/F - Location master
Editing character 2: 
this value only comes into play if the location was suggested via directed putaway (if no directed putaway or we receive more than one item at the time the default from MMS005/F will be used and we are always allowed to override this location after a warning.

For the directed putaway location suggestions:
Y means: we CANNOT override must confirm suggested
bLANK OR N means: WE CAN OVERRIDE

MMS025 – Popular numbers


The alias number and the qty linked to it will be used in the counting logic


 

MA settings



This setting is used for both DO Receiving and DO Receiving scan count.
These are the columns shown in the receipt screen.

The ScanCount column is the one that drives the received quantity and will be populated with 0 on initiation of screen and scanning will accumulate values. 

If thee is only one line to receive in the selection that line will have the suggested location retrieved by MMS160MI if this flag is turned on.


If not the location hierarchy is like this:
1. Directed putaway value (MMS160MI) if on
2. MMS005/F location in the receiving warehouse


Instructions



  • Delivery
  • Order
  • Item or Alias
  • Lot
  • Shipment
  • Container (M3 container/Pallet ID)
  • Package (Normal M3 outbound packed packages - advanced packing is a prerequisite and unique package )
  • SSCC package numbers
  • In house packages (Container management 7)


In scan count it is important to have a small amount to validate against so by package, delivery, that this can be checked against


scan in any order
and it will accumulate

same logic as for ScanCount in move.
GS1 AI 30 and 37 alos works so if a bacode looks like this:

02144345670032223724
(02)14434567003222(37)24
(24 in an outer box)
it will scan in at:

to finish scanning and receive press [enter] in the empty to go to to location or tap in the to location field.

Note: we can also manually amend the ScanCount quantity at any point in time if that makes more sense for the receipt. 



 
enter or confirm will receive the stock