> 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-duplicate-additional-lot-no.md).
# Do Not Allow Duplicate Additional Lot No
**YouTube:** [How to Prevent Entry of Duplicate Additional Lot Numbers in Job Orders?](https://youtu.be/94WYivMCzI8)
## How to Prevent Entry of Duplicate Additional Lot Numbers in Job Orders?
In this tutorial, we will learn how to prevent the entry of duplicate Additional Lot Numbers in a Job Order using the **"Do Not Allow Duplicate Additional Lot No."** option in Logic ERP. This feature helps maintain unique lot identification and prevents duplicate Job Order entries.
***
### Objective of This Feature
* Prevent duplicate Additional Lot Numbers in Job Orders
* Maintain unique lot identification
* Avoid duplicate Job Order entries
* Improve lot tracking and data accuracy
* Ensure better control over Job Order transactions
***
### 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 Duplicate Additional Lot No."**
* Open **Column Locks**.
* Unlock the **Additional Lot Number** field so that it is available during Job Order entry.
* Save the configuration.
***
### Create a New Job Order
* Initiate a **New Job Order** entry.
* In the **Header Details** section, you will now find the **Additional Lot Number** field.
* Enter an Additional Lot Number.
* Proceed to the **Item Details** section.
* Transact the required item.
* Save the Job Order.
***
### Implement Duplicate Additional Lot Number
* Initiate another **New Job Order** entry.
* Enter the same Additional Lot Number used in the previous Job Order.
* Complete the entry and click **Save**.
**Result**
As observed, the software restricts the transaction and displays an error message indicating that the **Additional Lot Number already exists** and duplicate entries are not allowed.
***
### Enter a Unique Additional Lot Number
* Replace the duplicate Additional Lot Number with a unique value.
* Complete the Job Order entry.
* Click **Save**.
**Result**
The software allows the Job Order to be saved successfully once a unique Additional Lot Number is entered.
***
### Key Benefits
* Prevents duplicate Additional Lot Numbers.
* Improves Job Order tracking.
* Maintains accurate lot-wise records.
* Reduces duplicate transaction entries.
* Ensures better control over Job Order data.
***
### Best Practice Tips
* Always use a unique Additional Lot Number for each Job Order.
* Verify the lot number before saving the transaction.
* Keep the Additional Lot Number field visible for easy verification.
* Enable this restriction when unique lot identification is required.
***
### Final Outcome
After enabling **"Do Not Allow Duplicate Additional Lot No."**, Logic ERP automatically validates the Additional Lot Number during Job Order entry. If the entered number already exists, the software restricts the transaction and prevents the Job Order from being saved. A unique Additional Lot Number must be entered to complete the transaction 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-duplicate-additional-lot-no.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.