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

1. Inward PO Amendment call comes from ERP

2. The new Inward Order Line Items replace the existing Inward Order Line Items after validations

3. Inward PO is moved into the NEW state, for re-validation

4. All ASN are moved into the NEW state, for re-validation

LOCKED State Introduction in Inward PO

1. New Inward Order State named LOCKED is introduced in CIMS Inward PO.

2. On Channel Level, a configuration is_po_amend_allowed will be configured for Channel.

3. For Inward PO with is_po_amend_allowed as Enabled

   1. If ASN are being sent by ERP, then Inward PO gets LOCKED on approval of first ASN.

   2. If ERP does not have ASN workflow, then ERP has to explicitly hit Lock API to CIMS.

4. For Inward PO with is_po_amend_allowed as Disabled

   1. Inward PO gets LOCKED post validation automatically.

5. ASN Approval belonging to any Inward PO, not in LOCKED status should throw an error in CIMS.

6. 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.

• IsInwardedPOAmendment Flag is added at the Champ level

  • Client Channel Level property

  • When the value of this property is TRUE, post validation the Inward PO will not move to LOCKED state

  • ERP will have to move the Inward PO to LOCKED state from API endpoint

  • PO Created in CIMS -> Validation Happens in CIMS -> Once the PO is in LOCKED then only it moves to OMS

  • PO Line item can be amended and the whole absolute replacement happens by receiving a new request from ERP

  • Once the Inward PO is amended all the ASNs will again move to NEW state and again the validations on ASN happen in CIMS

• When PO will move to LOCKED state?

  • As soon as the first ASN is approved the PO will be locked.

  • PO Locked API is hit by ERP

Related APIs