Versions Compared

Key

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

Overview

Once the Purchase Order is created in the the We have made some improvements to the Increff WMS system , the User can now amend the Order line items and lock the PO in CIMSto 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. Inward PO Amendment call comes from ERP

  2. 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)

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

  4. All ASN are moved into the NEW state, for re-validation. and again the validations on ASN happen in CIMSWhen changes are made to the PO in the ERP system, these amendments are sent to Increff system.

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

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

...

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

POs

We have introduced a new state called "LOCKED" for Inward POs in CIMS. On Client Channel Level, a configuration is_po_amend_allowed will be configured for Channel.

  1. For Inward PO with If the is_po_amend_allowed as Enabled, post validation the Inward option is enabled for an Inward PO, the PO will not move to the LOCKED state after validation.

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

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

  2. For Inward PO POs with the is_po_amend_allowed as Disabled

    1. Inward PO gets LOCKED post validation automatically.

    ASN Approval belonging to any Inward PO, not in LOCKED status throws option disabled, the PO will be locked automatically after validation.

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

Syncing of Inward

...

POs with OMS

...

will only occur after they have been locked.

Refer Please refer to the following table which describes what operation is allowed at which 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

CREATED

  1. PO Amendment in CIMS

  2. ASN Creation in CIMS

  1. ASN Approval in CIMS[Synchronous Error]

  2. Inward PO sync to OMS

LOCKED

  1. ASN Creation in CIMS

  2. ASN Approval in CIMS

  3. Inward PO sync to OMS

  1. PO Amendment in CIMS [Synchronous 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