Skip to main content
Question

Title: How to freeze MR/IR/SR once they move to a downstream operation (PO, GRN, Issue, Appointment, Service Order)?

  • Nov 4, 2026 11:05 AM UTC
  • 1 reply
  • 14 views
  • Translate All

RuwanK
Freshman I

Hello Community,

We need to lock request documents (MR, IR, SR) once they progress to a second or later operation such as PO, GRN, Inventory Issue, Appointment or Service Order.

Current behavior: Users can still reopen, cancel or edit quantities after downstream documents exist, and the system sometimes reopens the request automatically after POs are generated or materials are issued.

Required behavior:

  1. Freeze the request completely once it moves to approval, PO, GRN, issue, appointment or service order.
  2. Block reopen, cancel and quantity edits after that point.
  3. Prevent automatic reopening after PO generation or stock issue.

Question: Does Acumatica have any built-in facility (workflow, automation steps, access rights or a setting) to manage this? If not, what is the recommended approach?

1 reply

Steve Milner
Varsity III
Forum|alt.badge.img+6
  • Varsity III
  • Nov 4, 2026 4:17 PM UTC

@RuwanK the workflow is the built-in tool for this. Access rights won't do it on their own, because they're set per role, not per document status. They can hide Cancel from a role in every status, but not only once a PO exists.

If MR, IR and SR are request classes on the Requests screen (RQ301000), one workflow covers all three. The Requests workflow is a single flow for every class, so a condition on the Request Class is how you'd treat one class differently.

The automatic reopen is part of that predefined workflow. From 2025 R1 through 2026 R1, a Closed request moves back to Open by itself whenever its open quantity goes up again. That's a transition in the workflow, not a preference. Purchase Requisitions Preferences (RQ101000) has no setting for it.

The lever is a customization project. Extend the system workflow for Requests, then work state by state. On the Fields tab you can mark a field such as the quantity Disabled, and that setting can come from a condition when the status doesn't change at the PO step. On the Actions tab you switch off Cancel by clearing Active. A canceled request comes back through Put On Hold, so clearing Active on that action in the Canceled state blocks it. System actions can't be deleted, only deactivated. I haven't tested removing the Closed to Open transition, so try that part in a test tenant first.

Translate