> 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-entry-w-o-process-+-item-rates.md).
# Do Not allow Entry W/O Process + Item Rates
**YouTube:** [How to Prevent Saving Job Orders Without Process and Item Rates?](https://youtu.be/5jfRWUb7gVk)
## How to Prevent Saving Job Orders Without Process and Item Rates?
In this tutorial, we will learn how to **restrict saving a Job Order when Process + Item Rates are not defined** using the **Do Not allow Entry W/O Process + Item Rates** option in Logic ERP. This feature ensures that the required process-wise and item-wise rates are defined before the Job Order can be saved.
***
### Objective of This Feature
* Ensure Process + Item Rates are defined before saving
* Prevent incomplete Job Order entries
* Maintain accurate process and item costing
* Reduce manual errors
* Improve control over Job Order processing
***
### Access to the Job Order Configuration
* Open the **Configuration** window.
* Navigate to the **Other Settings** section.
* Locate and enable the option labeled as:
> **"Do Not allow Entry W/O Process + Item Rates"**
* Save the configuration changes.
***
### Create a New Job Order
* Initiate a **New Job Order** entry.
* Transact the required item.
* Enter the necessary details.
* Click **Save**.
**Result**
The software restricts the entry from being saved because the required **Process + Item Rates** have not been defined.
***
### Define Process + Item Rates
* From the Job Order entry, click on **Raw Materials**.
* Open the **Process + Item Rates** window.
**Action**
* Define the required **Process-wise Rates**.
* Define the required **Item-wise Rates**.
* Save the rate details.
***
### Save the Job Order Again
* Return to the Job Order entry window.
* Click **Save** again.
**Result**
The software now allows the Job Order to be saved successfully because the required **Process + Item Rates** have been defined.
***
### Key Benefits
* Prevents incomplete Job Order entries
* Ensures required rates are available
* Improves costing accuracy
* Reduces data entry errors
* Provides better control over process-wise costing
***
### Best Practice Tips
* Define Process + Item Rates before saving the Job Order.
* Verify both process-wise and item-wise rates carefully.
* Keep rate configurations updated to ensure accurate Job Order costing.
***
### Final Outcome
After enabling **"Do Not allow Entry W/O Process + Item Rates"**, Logic ERP prevents the Job Order from being saved until the required Process + Item Rates are defined. Once the rates are configured, the Job Order can be saved successfully.
---
# 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-entry-w-o-process-+-item-rates.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.