> 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/order-processing/delivery-note-against-purchase-orders/dn-against-po-configuration/job-order-selection-required.md).
# Job Order Selection Required
**YouTube:** [How to Configure Mandatory Job Order Selection in Delivery Notes?](https://youtu.be/SrImc5ZOwHo)
## How to Configure Mandatory Job Order Selection in Delivery Notes?
In this tutorial, we will learn how to make **Job Order Selection** mandatory while creating a Delivery Note in Logic ERP. When this feature is enabled, the system restricts item retrieval unless a valid Job Order is selected.
***
### Objective of This Feature
* Make Job Order selection mandatory.
* Prevent Delivery Note creation without a Job Order.
* Ensure accurate Job Order-wise dispatch.
* Improve document traceability.
* Minimize incorrect item retrieval.
***
### Access to the Configuration
* Open the **Delivery Note Configuration** window.
* Navigate to the **Other Settings** section.
* Locate and enable the option labeled as:
> **"Job Order Selection Required"**
**Next:**
* Click **Column Locks**.
* Unlock the **Job Order** field so it is available during voucher entry.
* Save the configuration.
***
### Create a New Delivery Note
* Initiate a **New Delivery Note** entry.
* Select the Supplier.
* Enter the required header details.
* Click **Next**.
**Result**
The **Job Order** field is now available in the Purchase Order retrieval section.
***
### Observe the Functionality
#### **Scenario 1: Job Order Not Selected**
* Select only the **Purchase Order**.
* Leave the **Job Order** field blank.
* Search and select the required Purchase Order.
* Click **Refresh**.
**Result**
The software restricts the transaction and displays an error message indicating that **Job Order selection is mandatory**.
#### Scenario 2: Job Order Selected
* Select the appropriate **Job Order**.
* Click **Refresh** again.
**Result**
The system successfully retrieves the items from the selected Purchase Order and allows you to continue with the Delivery Note entry.
***
### Key Benefits
* Ensures Delivery Notes are linked to the correct Job Order.
* Prevents accidental retrieval without Job Order selection.
* Improves document accuracy and traceability.
* Supports Job Order-based inventory management.
* Reduces manual errors during dispatch.
***
### Best Practice Tips
* Enable the **Job Order** field through **Column Locks** before using this feature.
* Always select the correct Job Order before retrieving a Purchase Order.
* Use this validation in businesses where dispatches are processed against Job Orders.
* Verify the linked Job Order before completing the Delivery Note.
***
### Final Outcome
After enabling **Job Order Selection Required**, Logic ERP ensures that a valid Job Order is selected before items can be retrieved into a Delivery Note. If the Job Order is left blank, the system blocks the transaction, ensuring accurate Job Order-based processing and improved inventory control.
---
# 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/order-processing/delivery-note-against-purchase-orders/dn-against-po-configuration/job-order-selection-required.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.