...
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.
...
A new configuration is introduced which needs to be Enabled/Disabled by help of Increff Support Team for the configured for Channels in CIMS.
If the configuraton is enabled for an Inward PO, the PO will not move to the LOCKED state after ASN validation.
If ASNs are being sent by the ERP system, the Inward PO will automatically be locked upon approval of the first ASN.
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.
For Inward POs with the is_po_amend_allowed option disabledconfiguration 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.
...
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. |