> 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-header-details-while-retrieving-purchase-indent-in-po.md).

# Retrieve Header Details while Retrieving Purchase Indent in PO

**YouTube:** [How to Retrieve Header Details from Purchase Indents in Purchase Orders?](https://www.youtube.com/watch?v=0vrdPbK2CMo)

## How to Retrieve Header Details from Purchase Indents in Purchase Orders?

This tutorial explains how to **automatically retrieve header details from a Purchase Indent into a Purchase Order** in Logic ERP. This feature ensures consistency by carrying forward important information like **remarks, payment terms, and other header details**.

***

### **Objective of This Feature**

* Auto-fetch **header details** from Purchase Indent
* Reduce manual data entry
* Maintain **data consistency across documents**
* Improve efficiency in Purchase Order creation

***

### **Access to Configuration**&#x20;

* Open **Configuration Window**
* Go to **General Options**
* Locate and enable the option labeled as:

> **"Retrieve Header Details while Retrieving Purchase Indent in PO"**

<figure><img src="/files/1qrMHQWpZHcspB7AHEa5" alt=""><figcaption></figcaption></figure>

* Click **OK** to apply changes

***

### **Initiate Purchase Order**

* Open **Purchase Order Window**
* Select the **Supplier Name**

**Check Initial Header Details**

* Before retrieving Indent:
  * Open **Header Details / Other Details Section**

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

* Observe:
  * Fields like **Remarks, Payment Terms, etc. are blank**

***

### **Retrieve Purchase Indent**

* Click on **Retrieve Button**

<figure><img src="/files/3wH47pP3CbS7QfO4vozZ" alt=""><figcaption></figcaption></figure>

* Select the required **Purchase Indent**

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

**Verify Retrieved Header Details**

* After retrieval:
  * Go back to **Header Details Section**

***

### **Observation**

* The system automatically fetches:
  * Open **Other Details**
  * **Remarks**
  * **Payment Terms**
  * Other defined header information

<div><figure><img src="/files/fQganY6cGQjE9v5Uxnqz" alt=""><figcaption></figcaption></figure> <figure><img src="/files/7k3uX8PZjAgeyV4uBSVc" alt=""><figcaption></figcaption></figure> <figure><img src="/files/sKYRdSAnfUjD20lc8PmZ" alt=""><figcaption></figcaption></figure></div>

***

### **Key Benefits**

* Eliminates repetitive manual entry
* Ensures **uniform data across documents**
* Reduces chances of missing important details
* Speeds up Purchase Order processing

***

### **Best Practice Tips**

* Always verify Purchase Indent details before retrieval
* Ensure configuration is enabled before starting entry
* Cross-check header details after retrieval

***

### **Final Outcome**

* Header details from Purchase Indent are **automatically populated** in Purchase Order
* Data consistency is **maintained across transactions**
* Purchase workflow becomes **faster and more accurate**


---

# 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/purchase-order/po-configuration/retrieve-header-details-while-retrieving-purchase-indent-in-po.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.
