> 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/allow-retrieval-for-po-from-any-branch.md).
# Allow Retrieval for PO from any Branch
**YouTube:** [How to Allow Purchase Order Retrieval from Any Branch in Delivery Notes?](https://youtu.be/NMwrjpQe7-Q)
## How to Allow Purchase Order Retrieval from Any Branch in Delivery Notes?
In this tutorial, we will learn how to enable the **Allow Retrieval for PO from Any Branch** feature while creating a Delivery Note in Logic ERP. This option allows users to retrieve Purchase Orders created in any branch, instead of being limited to the currently logged-in branch.
***
### Objective of This Feature
* Retrieve Purchase Orders from any branch.
* Simplify inter-branch operations.
* Improve document accessibility.
* Reduce branch-specific retrieval limitations.
* Streamline Delivery Note creation.
***
### Understand the Default Behavior
Before enabling the feature, let's review the default behavior.
* Initiate a **New Delivery Note**.
* Open the **Purchase Order** search window.
**Result**
By default, the software displays only those Purchase Orders that were created in the **currently logged-in branch**.
Purchase Orders from other branches are not available for retrieval.
***
### Enable Retrieval from Any Branch Option
* Open the **Configuration** window.
* Navigate to the **Other Settings** section.
* Locate and enable the option labeled as:
> **"Allow Retrieval for PO from Any Branch"**
* Save the configuration.
***
### Create a New Delivery Note
* Initiate a **New Delivery Note** entry.
* Select the **Supplier**.
* Enter the required header details.
* Click **Next**.
**Retrieve the Purchase Order**
* Click on the **Purchase Order** field.
* Open the **Search** window.
**Result**
The search window now displays **Purchase Orders from all branches**, instead of only those created in the current branch.
You can retrieve a Purchase Order created in **any branch**, regardless of the branch in which you are currently logged in.
***
### Key Benefits
* Enables cross-branch Purchase Order retrieval.
* Simplifies inter-branch procurement workflows.
* Improves operational flexibility.
* Reduces the need to switch branches for document retrieval.
* Speeds up Delivery Note creation.
***
### Best Practice Tips
* Enable this feature only if users are authorized to access Purchase Orders across branches.
* Verify the branch details before retrieving a Purchase Order.
* Ensure branch-level access permissions are configured according to your organization's policies.
* Regularly review cross-branch transactions for accurate inventory and audit control.
***
### Final Outcome
After enabling **Allow Retrieval for PO from Any Branch**, Logic ERP allows users to retrieve Purchase Orders created in any branch while creating a Delivery Note. This improves operational efficiency, supports inter-branch transactions, and provides greater flexibility in document retrieval.
---
# 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/allow-retrieval-for-po-from-any-branch.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.