Lock Inward Order API (Beta)
Inbound |PUT|/orders/inward/{orderCode}/{locationCode}
Summary
This API can be used to block any Inward order created in Increff system for any futher updation.
Once the Inward Order is marked as LOCKED, the External System will not be able to update the Inward Order through the Update Inward Order API
Once the Inward Order is marked as Locked , the user is allowed to only start the GRN process.
Description
External systems can use the Update Inward Order API to make updates in an existing Inward order but to block any Inward order for further amendments there is a new state introduced as LOCKED
In Increff System, for every Channel there will be a initial configuration to be enabled on request of Client which will allow the external system to update any Inward Order.
For an Inward PO the PO Amendment configuration Enabled,
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 use the Lock API to make the Inward order as LOCKED for further amendment.
For Inward PO with the PO Amendment configuration Disabled
Inward PO gets LOCked post validation automatically.
Â
Request
Path Parameters
Parameter Name | Data Type | Description | Mandatory |
| String | orderCode of the order in consideration | yes |
| String | locationCode of the warehouse where the order is created | yes |
Response
Â
Empty Body