Processes in request handling
@jalarcon @gcapilit GG allows for recording process steps as *Actions
.
There is no specific status on the order itself, it is considered as closed when the completedDate
is set. Everything else is recorded as order actions.
Considering a generic request for material (think distribution), once the list of accessions and request details are filed in GG, the next steps are:
-
Assign source inventory to each requested item
- If there is no available inventory, what can we do with that order item? Set SYSTEM inventory and
CANCEL
the item?
- If there is no available inventory, what can we do with that order item? Set SYSTEM inventory and
- This leaves us with order items that have valid source inventory and can be packaged for distribution
- Determine if SMTA acceptance is required
- If SMTA required, initiate order item action
SMTAACCEPT
for all remaining items - If other MTA is required, initiate relevant item action.
- If SMTA required, initiate order item action
- Determine if IMPORT PERMIT is required
- Initiate
IMPORT_PER
action on items
- Initiate
For each item in the request:
- Retrieve source inventories from storage
-
Pack take material from source inventory and package for distribution. This updates the available
quantityOnHand
of the source inventory. -
Verify that packets for distribution match (@jalarcon This is your
ORIA_VER_SHIP
action) - Ship the material
Each of these is a task that can be recorded as OrderRequestItemAction
with its own start
and completed
date.
Are any steps missing?
Status
Relationship with order item The status of each order item begins with NEW
and ends in one of: SHIPPED
, CANCEL
or SPLIT
states.
Intermediate states in GG are: HOLD
, PENDING
, INSPECT
and QUALITYTEST
. It is not immediately clear how these relate to the actions listed above.