Overview:
This article explains what happens when a Superuser deactivates a location that still has Purchase Orders (POs) associated with it in the system.
Scenario 1: RFO Created and Approved, Sitting in Procurement Queue
Action: An attempt to deactivate the location under Settings.
Outcome: An error message will appear, preventing the deactivation of the location. This occurs because there are pending POs in the procurement queue.
Scenario 2: PO Already Created
Action: Deactivate the location under Settings.
Outcome: The location will successfully deactivate. For customers using Auto PO, this should not be an issue as the POs have already been created.
Possible issues with Receiving:
Action: Attempt to receive items against a deactivated location.
Outcome: A "permissions" based error will appear, preventing the receipt of items against the deactivated location. This affects the AP team as they will not be able to create a bill if the items cannot be received.
Recommendation:
Before deactivating a location, ensure that all pending POs are processed and received to avoid any disruptions in the workflow. If you encounter any issues or need further assistance, please contact our support team.