> 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/move-doc-no-to-lot-number.md).

# Move Doc No to Lot Number

**YouTube:** [How to Transfer the Document Number to the Lot Number in Job Orders?](https://youtu.be/oKRs36aDrGA)

## How to Transfer the Document Number to the Lot Number in Job Orders?

In this tutorial, we will learn how to automatically populate the **Job Order Number** into the **Lot Number** field during Job Order entry using the **Move Doc No to Lot Number** option in Logic ERP. This feature helps maintain consistent lot identification and reduces manual data entry.

***

### Objective of This Feature

* Automatically populate the Job Order Number as the Lot Number
* Reduce manual Lot Number entry
* Maintain consistency between Job Order and Lot Number
* Improve data entry efficiency
* Minimize manual errors

***

### Access to the Job Order Configuration

* Go to the **Configuration** window.
* Navigate to the **Other Settings** section.
* Locate and enable the option labeled as.

> **"Move Doc No to Lot Number"**

<figure><img src="/files/EVpIGKcng46d6NLWoMVX" alt=""><figcaption></figcaption></figure>

* Save the configuration changes.

***

### Create a New Job Order

* Initiate a **New Job Order** entry.
* Observe the Job Order Number generated by the system.

<figure><img src="/files/fUBiE8qEwFVPa1XzxZPY" alt=""><figcaption></figcaption></figure>

For example, the current Job Order Number is **JO3**.

***

### Enter Item Details

* Enter the required **Item Details**.
* Complete the Job Order entry.
* Save the Job Order.

***

### Verify the Lot Number

* Open the same Job Order in **Modify Mode**.
* Navigate to the relevant Lot Number field.

<figure><img src="/files/y0OfD2pcm2G7EM4zNjs7" alt=""><figcaption></figcaption></figure>

**Result**

* The software automatically populates the **Job Order Number** into the **Lot Number** field.
* For Example:&#x20;
  * **Job Order No.: JO10 → Lot Number: JO10**

***

### Key Benefits

* Faster Job Order entry
* Eliminates repetitive Lot Number entry
* Ensures consistent document identification
* Reduces data entry errors
* Improves overall transaction efficiency

***

### Best Practice Tips

* Enable this option when the Job Order Number should be used as the Lot Number.
* Verify the Lot Number after saving the Job Order.
* Use a suitable document numbering format to maintain clear Lot identification.

***

### Final Outcome

After enabling **Move Doc No to Lot Number**, Logic ERP automatically transfers the **Job Order Number** to the **Lot Number** field, making Job Order processing faster, more consistent, and less prone to manual errors.


---

# 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/move-doc-no-to-lot-number.md?ask=<question>&goal=<endgoal>
```

`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.
