> For the complete documentation index, see [llms.txt](https://kb.logicerp.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://kb.logicerp.com/logic-erp-learning-hub-tutorials-and-best-practices/production/production-vouchers/job-order/job-order-configuration/do-not-allow-modification-if-job-order-has-been-used-in-production.md).
# Do not allow modification if Job Order has been used in Production
**YouTube:** [How to Prevent Editing of Job Orders Used in Production?](https://youtu.be/_CBQR7RQyO4)
## How to Prevent Editing of Job Orders Used in Production?
In this tutorial, we will learn how to prevent modifications to a **Job Order** once it has been used in production. This feature ensures that production-linked Job Orders remain unchanged, preserving data integrity and maintaining accurate production records.
***
### Objective of This Feature
* Prevent modification of Job Orders already used in production.
* Maintain production data integrity.
* Protect completed production transactions from unauthorized changes.
* Ensure consistency between Job Orders and production records.
* Improve process control and audit accuracy.
***
### Access to the Job Order Configuration
* Open the **Job Order Configuration** window.
* Navigate to the **Other Settings** section.
* Locate and enable the option labeled as:
> **"Do not allow modification if Job Order has been used in Production".**
* Save the configuration.
***
### Open a Job Order in Modify Mode
* Open an existing **Job Order** that has already been used in a Production transaction.
* Open the document in **Modify Mode**.
**Attempt to Modify the Job Order**
* Try to change the quantity or any other editable details of an item.
**Result**
* The software immediately restricts the modification and displays an error message indicating that the **Job Order has already been used in production and cannot be modified**.
* As a result, no changes can be made to the Job Order after it has been consumed in the production process.
***
### Key Benefits
* Protects production-related Job Orders from modification.
* Maintains consistency between Job Orders and Production records.
* Prevents accidental changes to completed production data.
* Improves data accuracy and traceability.
* Strengthens internal controls and audit compliance.
***
### Best Practice Tips
* Verify all Job Order details before using them in Production.
* Enable this feature to safeguard production data from unauthorized modifications.
* If changes are required after production, follow your organization's revision or correction process instead of modifying the original Job Order.
* Periodically review production records to ensure data consistency.
***
### Final Outcome
After enabling **"Do Not Allow Modification if Job Order Has Been Used in Production"**, Logic ERP prevents users from modifying any Job Order that has already been used in a Production transaction. This ensures data integrity, preserves production history, and maintains accurate manufacturing records.
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://kb.logicerp.com/logic-erp-learning-hub-tutorials-and-best-practices/production/production-vouchers/job-order/job-order-configuration/do-not-allow-modification-if-job-order-has-been-used-in-production.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.