Overview
Once the Purchase Order is created in the the Increff WMS system, the User can now amend the Order line items and lock the PO in CIMS.
Inward Order Line Items Update Workflow
Inward PO Amendment call comes from ERP
The new Inward Order Line Items replace the existing Inward Order Line Items after validations(PO Line item can be amended and the whole absolute replacement happens by receiving a new request from ERP)
Inward PO is moved into the NEW state, for re-validation
All ASN are moved into the NEW state, for re-validation. and again the validations on ASN happen in CIMS
PO Amendment For Orders uploaded in OMS will not be allowed.
LOCKED State Introduction in Inward PO
New Inward Order State named LOCKED is introduced in CIMS Inward PO.
On Client Channel Level, a configuration is_po_amend_allowed will be configured for Channel.
For Inward PO with is_po_amend_allowed as Enabled, post validation the Inward PO will not move to LOCKED state
If ASN are being sent by ERP, then Inward PO gets LOCKED on approval of first ASN.
If ERP does not have ASN workflow, then ERP has to explicitly hit Lock API to CIMS.
For Inward PO with is_po_amend_allowed as Disabled
Inward PO gets LOCKED post validation automatically.
ASN Approval belonging to any Inward PO, not in LOCKED status throws an error in CIMS.
Inward PO Syncs with OMS post Locking only.
Refer to the following table which describes what operation is allowed at which PO status in CIMS / OMS.
PO State in CIMS | Allowed | Not Allowed |
---|---|---|
CREATED |
|
|
LOCKED |
|
|
Related APIs
APIs | Description | Reference Links |
---|---|---|
Update Inward Order API |
| |
Lock Inward Order API | This API can be used to lock an Inward order created in Increff Omni. |