> 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/purchase-order/po-configuration/retrieve-valid-purchase-indent-only.md).

# Retrieve Valid Purchase Indent Only

**YouTube:** [How Enable Retrieval of Valid Purchase Indents by Validity Date in Purchase Orders?](https://youtu.be/898Yb0G7nXE)

## How Enable Retrieval of Valid Purchase Indents by Validity Date in Purchase Orders?

This tutorial explains how to **restrict Purchase Order retrieval to only valid Purchase Indents** in Logic ERP. It demonstrates how enabling this option ensures that only indents within their validity period are available for selection, improving accuracy and control.

***

### **Objective of This Feature**

* Restrict retrieval to **valid Purchase Indents only**
* Avoid selection of **expired indents**
* Improve **accuracy in procurement process**
* Ensure **compliance with validity rules**

***

### **Understanding Default Behavior (Feature Disabled)**

**Retrieve Purchase Indent**

* Click on **Retrieve Button**
* Select **Purchase Indent**

<figure><img src="https://4031188996-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FXMVkjt8zqHBQX1c9QvFS%2Fuploads%2F4VHwUzhtIM1SHvPrvxOw%2FCNF.png?alt=media&amp;token=ee476a3b-17e1-45ff-adcc-528015286085" alt=""><figcaption></figcaption></figure>

**System Behavior**

* Displays **all Pending Indents**
* Includes:
  * Valid Indents
  * Expired Indents

***

### **Enabling Valid Indent Restriction**

* Navigate to **Header Details Section**
* Open **Configuration Window**
* Navigate to **General Options**
* Locate and enable the option labeled as:

> **“Retrieve Valid Purchase Indent Only”**

<figure><img src="https://4031188996-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FXMVkjt8zqHBQX1c9QvFS%2Fuploads%2FDOkUNuV8JUe4DSfDsjgK%2FCNF%20-%202.png?alt=media&amp;token=c88ec278-f34b-4f33-9cd6-a8abf2c36d73" alt=""><figcaption></figcaption></figure>

* Click **Ok.**

***

### Implement **After Enabling Feature**

* Initiate a **New Purchase Order**
* Click **Retrieve → Purchase Indent**

**System Behavior**

* Displays only: **Indents within validity period**

<figure><img src="https://4031188996-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FXMVkjt8zqHBQX1c9QvFS%2Fuploads%2FrCcca1OMuRuGtUmiECqI%2FList.png?alt=media&amp;token=c48a17fc-b771-49cb-9e01-449f08cbabb7" alt=""><figcaption></figcaption></figure>

**Restricted**

* Expired indents are **not shown**

***

### **Key Benefits**

* Prevents **selection of outdated indents**
* Ensures **accurate procurement planning**
* Reduces **manual verification effort**
* Improves **process reliability**

***

### **Best Practice Tips**

* Always define **validity period for indents**
* Enable this feature in **strict procurement environments**
* Regularly review pending indents

***

### **Final Outcome**

* Only **valid Purchase Indents** are available for retrieval
* Procurement process becomes **controlled and accurate**
* Errors due to expired indents are **eliminated**
* Workflow becomes **more efficient and reliable**


---

# 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-learning-hub-tutorials-and-best-practices/order-processing/purchase-order/po-configuration/retrieve-valid-purchase-indent-only.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.
