> 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-version-release-notes/may-2025/order/do-not-allow-entry-without-box-no.-in-delivery-note-against-purchase-order.md).

# “Do Not Allow Entry Without Box No.” in Delivery Note Against Purchase Order

**A new configuration update has been introduced in the “Delivery Note Against Purchase Order” module in Logic ERP.**\
With this update, you can now restrict users from saving the entry unless a **Box Number** is defined, ensuring more accurate and complete data entry.

**Step 1: Let us Enable this configuration in Logic ERP**

Navigate to the Order Processing and then click on **“Delivery Note Against Purchase Orders”**\
Click on **“Configuration”** and then select **“Other Settings”.**\
Locate and enable the option labeled: **“Do Not Allow Entry Without Box No”**

<figure><img src="https://www.logicerp.com/tutorials/wp-content/uploads/2025/05/Do-No-allow-entry-without-box-no.png" alt=""><figcaption></figcaption></figure>

**Step 2: Let us Implement this configuration in Logic ERP**

Now, when you retrieve a Purchase Order and try to scan items without defining a Box Number, the software will prompt you with a message, indicating that you cannot save the entry without specifying the Box Number.

<figure><img src="https://www.logicerp.com/tutorials/wp-content/uploads/2025/05/Error-Prompt.png" alt=""><figcaption></figcaption></figure>


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://kb.logicerp.com/logic-erp-version-release-notes/may-2025/order/do-not-allow-entry-without-box-no.-in-delivery-note-against-purchase-order.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.