TABLE OF CONTENTS

Internal Jira reference

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

Introduction

This function mimics Purchase order receiving in M3 (PPS300).  We have 2 alternative options:


One is called "PO Receiving no ASN" to not mix it up with the ones where we have advanced shipment notifications.


In this function we can receive multiple item at the same time as long as they go to the same location and container. GS1 decode is enabled. Cumulative scanning is supported and if bar codes are set up with quantity in MMS025/E we can scan and count upon receipt. 

This can be done over multiple items at the same time, for example sizes within a fashion style. We can validate input of expiry date and quantity and control if a lot reference is to be entered. 


If we do not want to receive multiple items at the same time we have an alternative function called "PO Receiving" that is better suited for most scenarios. See instructions below




Supported processes

Direct put way to Bin location:

DIR->BIN

DIR->STAGE->BIN

DIR->QAHOLD->STAGE->BIN

GR->PA

GR->INS->PA

GR->PA->INS


Pro tip: Use direct put away and control the stage location and possible Quality inspection location by populating the Inspection field in MMS002/G


Limitations

  • We can only receive to one location and container at the time. 
  • We can only control the printer and number of copies of the put away label (MWS450PF) all other receipt documents are recommended to go to email or being controlled by custom logic in CMS005 and XML out.   
  • Attribute update on PO receipt is not implemented yet (roadmap)
  • Inspection (INS)  M3 at this state (roadmap)
  • Sublot scanning is not implemented yet (roadmap)


M3 settings


ProgramField/FlagComment
MMS002/GInspection locationUse this to control receipt staging area for each item or group of items 
MMS002/GLocationUse this to direct a product directly to a bin location upon PO receipt
PPS345/EGoods rec methodDirect put away or Staged put away
MMS010/FEdit position 2Use this to control if the location must be scan validated (Y), Populated but optional validation (blank) (location can be overridden), or Populated and locked for input (N). Pro tip: use N if a staging area for receiving is to be used. 
MMS025/EQuantityUse this to link a barcode to a quantity for cumulative scan receipt. 
MMS002/IShelflifeIf the item is expiry date controlled this will be used to validate the dates entered as expiry date for based on the current date, the expiry date and shelf life considering tolerance limits set up in below settings in MA.


M3 – Fixes if on 13.4 or less

 

JT-1406706 Additional output fields in PPS001MI - Receipt transaction

 


Mobile Action settings



User settings

Data grid config



No ASNPO Rec
Settings\System\Receiving\XX
Lot ref and and/or 2 required etc.

Print putaway Label (MWS450PF)

Expiry date tolerance based on no of days in MMS002/I
so say 100 days there and a tolerance of -10% and +20%
means a date for the expiry date can be between 90 days from now and 120 days anything else is out of tolerance.

Quantity tolerance is the same - is how much less than the PO quantity can be received without a warning.
Note if many part receipts are done: the recommendation is to set this to -100% - any short receipt is allowed.
and maybe a +10 % saying it will only look at over receipt after 10% over receipt.

These settings are not used by PO Receiving only PO Receiving no ASN.

X

X


X


X




X





X

X		X

X









Po rec in short:
Prompt:

Warning:

PO Receiving in short: 
This flag is only used in PO Receiving not the PO Receiving no ASN function.
It controls what should happen in the step view when we receive less than the PO line was for: ex 200 out of 2000

Stay on the lines means we go back to the quantity input and assume we will receive another X qty onto another pallet/container or location etc, essentially batching in the receipts.

Auto lot number input option:
If the lot number method in M3 is >0 (auto of some sort)
M3 will generate a lot no for each receipt.
If this flag is set to disable. If it is optional or mandatory we ignore this and ask the user to put in a lot number anyway

Show both expi date and manuf date makes it possible to enter both pack/manuf date and expiry date on a product at receipt. We update the lot master with the manuf date entered here.

Input option:
This flag is valid when short receive and stay on the line:
Blank means: We need to repeat all values Item/quantity/to location/container
Memory means: It remembers last value and user can override
Skip means: The item is assumed the same so skip, quantity is memory, to location is skipped, container is blank. (Note Skip only work if the item is container managed)

 










X





X






X





X







X




X
From and to Planning date:
This is the overall date range we use to search for PO lines to receive.
It is possible to override in PO Receiving no ASN.
but just defaulted behind the scenes in the other PO Receiving function

Delivery note: If entered it will be added into SUDO in PPS330		XX







X



Process flows:




Instructions PO receiving no ASN - general filter, settings and search


The dates are defaulted based on settings (above)
the To lowest status is hard coded to be initiated to 75.
if we want the fully received lines to drop off we can set this to 74 (one off) or save the filter (this will save these settings on your user and be remembered next time.
Note: the dates selections are not saved since they are dynamically calculated all the time

Settings:
The printer is coming from the User settings (Putaway printer) but the number of copies is editable and can be changed here and saved depending on the type of receipt.



Note: We do validate the no of copies settings if Print put-away Lbl is = 1.
(it is ok to have blank printer - email)



If the print labels is on and we have no copies it will complain.
Set a value and save (will save to your user)

Note: The print flag is not correct here: it is the general settings that rules and this flag is not in play.

All filters will enable the user to search on a specific entry data.
Combined Filter will test the input data through all of the individual options and return the lines based on this.
So if we have no overlaps in the data and use a combination of Supplier, PO no, item no etc to find lines to receive this is probably a more efficient way to find the PO lines.




Instructions PO receiving No ASN - receive lines Expiry dates - lot control GS1


The input field takes Item, Alias, GS1
it decodes as per the items GS1 Decode override rules (see separate instruction)

Example manual entry
Fill in the values 
the reason for the production date is since the item got expiry date methog 2 or 4

If the system had asked for both dates we would have had to input both Manuf date and expiry date
GS1 option:
02144345670018291123021210LCS14022023|3724
(02)14434567001829(11)230212(10)LCS14022023(37)24


Note: even though we have the AI 10 in the barcode we have a Mobile Action logic here:
1. Only show lot if manual lot number or if set to be open anyway in settings.

2 Don't pass in the lot no from AI 10 or 21 (regardless of config) the supplier inconsistencies in australia are too big so we demand a lot no manually entered
the lot no entered will then count for all other scans.

Quantity logic: if AI 30 or 37 exists use that else use what is stored in MMS002/E as quantity if nothing use 1.

if AI 310x and the basic UoM is KG then that will be used.
if AI 310x and catch weight item that will be used as catch weight.
See general GS1 decode section.
It auto calculates the expiry dates based on shelf life
(note when manually entered only the Prod date or Expiry date is requested (unless config to open both) and the other date is calculated by M3
subsequent scans will accumulate directly assuming same lot.


The date will be overridden if a carton with less date is scanned.
Example of KG item (expiry date managed)
011443456700180531020017281523092510LOT998
(01)14434567001805(3102)001728(15)230925(10)LOT998

Each scan accumulates with the individual cartons weight.
Note: if AI 21 is part of the barcode it will be accumulated as a serail count and we will validate duplicate scans of the same serial no even if no sublot controlled items. 
To putaway just press enter in the empty scan filed
(or tap)

To location logic:
if all selected lines have the same location
(Hierarchy: if direct putaway:
1. MMS002/G inspection location (does not need to be sts 1)
2. System Directed putaway rules
See flowchart explaining this above (if QI then the locs are taken from PPS345)

It will show:
Deepening on the MMS010/F (editing position 2) settings it will be mandatory to scan and cannot be overridden (Y) it or it will be defaulted (N) and cannot be overridden
or it BLANK: it is not defaulted and any other location can be used instead.

Y:

N:

Blank:
And allowed
If at least one item (and location combination) is container managed the container will be requested.

Note: no package mask validation here

Validation on the receipt quantity tolerance

If items on the PO has different receipt locations
we must receive them separately
Example of tolerance check on date

Note: We do not validate the dates when scanned in (the check is meant to be to pick up key errors)

If  

(Remaining qty - Quantity) = Ordered (no colour - not started)

(Remaining qty - Quantity) < Ordered (orange) Partly received)

(Remaining qty - Quantity) = 0 (green) Received in full

(Remaining qty-Quantity)<0 (negative value) Red - over received 




Instructions PO Receiving no ASN - Fashion items




Scan garments barcodes in any random order
As long as a quantity is linked in MMS025 for the alias number or GS1 AI 30 or 37 are included in the barcode it will accumulate the counts.

else this will pop up:
Validates wrong item
[enter] or confirm to receive

Instructions PO Receiving