Versions Compared

Version Old Version 3 New Version Current
Changes made by

Rahul Singh

Rahul Singh

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Overview

Once the Purchase Order is created in We have made some improvements to the Increff WMS system , User can now amend the Order line items and can lock the PO in CIMS

  • IsInwardedPOAmendment Flag is added at 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

Raghav Mehta Rahul Singh to enhance the Purchase Order (PO) management process. Now, users can easily make changes to the line items of a PO and lock it in CIMS (our system).

Inward Order Line Items Update Workflow

  1. When changes are made to the PO in the ERP system, these amendments are sent to Increff system.

  2. The new line items provided by the ERP system will replace the existing ones after going through necessary validations. This means that the entire line item information is updated based on the new request from the ERP system.

  3. The PO will be moved to a NEW state for re-validation, along with all associated Advance Shipping Notices (ASN). The validations on the ASN will also be performed in CIMS.

Info

PO Amendment For Orders uploaded in OMS will not be allowed.

Introducing the LOCKED State for Inward POs

We have introduced a new state called LOCKED for Inward POs in CIMS.

A new configuration is introduced which needs to be Enabled/Disabled by help of Increff Support Team for the configured for Channels in CIMS.

  1. If the configuraton is enabled for an Inward PO, the PO will not move to the LOCKED state after ASN validation.

    1. If ASNs are being sent by the ERP system, the Inward PO will automatically be locked upon approval of the first ASN.

    2. If the ERP system does not follow an ASN workflow, it needs to explicitly use the Lock API in CIMS to lock the Inward PO.

  2. For Inward POs with the configuration set as Disabled, the PO will be locked automatically after validation.

Note:

  • Any ASN approval related to an Inward PO that is not in the LOCKED status will result in an error in CIMS User Interface.

  • Syncing of Inward POs with OMS will only occur after they have been locked.

Please refer to the table below for a summary of what operations are allowed for each PO status in CIMS and OMS.

PO State in CIMS

Allowed

Not Allowed

VALIDATED

  1. PO Amendment in CIMS

  2. ASN Creation in CIMS

  3. ASN Approval in CIMS(PO is Locked on first ASN approval of the PO)

  1. Inward PO sync to OMS

LOCKED

  1. ASN Creation

  2. ASN Approval

  3. Inward PO sync to OMS

  1. PO Amendment in CIMS [Error]

Related APIs

APIs

Description

Reference Links

Update Inward Order API

  • This API can be used by an ERP to update a certain inward order created in CIMS.

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

Update Inward Order API

Lock Inward Order API

This API can be used to lock an Inward order created in Increff Omni.

Lock Inward Order API