Last active
May 24, 2021 12:20
-
-
Save nhwaani/a216e5d91c48d2b4407edc110642e1ef to your computer and use it in GitHub Desktop.
RMS TOTE SEGREGATION PR
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
TOTE REGEX : | |
TOTE_CODE_TTR = '^TTR[0-9]{5}$' # RMS | |
TOTE_CODE_TT = '^TT[0-9]{3,9}$' # WMS only wms will have TT followed by 3-9 digits | |
TOTE_CODE_TTX = '^TTX[0-9]{5}$' #XMS | |
For the new flow we will hit : | |
1: /{barcode}/mp_resolution which accepts | |
REQUEST: {'barcode' : 'RMD1121' } | |
and it will try to resolve this with MP and provide response back | |
RESPONSE : { | |
'barcode': 'RMD1121', | |
'item_status': 'resolved' | |
'put_away_tote_regex' : TOTE_CODE_TT, # but we dont need to save them on front end , just use what back-end will pass | |
'mp_decision' : 'accepted', | |
'final_destination': 'fbn', | |
'suggested_tote_for_putaway' : '' # this can have None value or tote_code that is active with user and tote regex matches item dest regex tote | |
# ...., and some other keys will be in the response. | |
} | |
This will be the new endpoint for movement_v2, where we will allow validations etc | |
/v2/{barcode}/movement, its same as that before , only there will be validations for item putway | |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment