> 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/do-not-allow-po-creation-without-indent.md).

# Do not allow PO creation without Indent

**YouTube:** [How to Restrict Purchase Order Creation Without a Purchase Indent?](https://youtu.be/5GYYVv9D_Bw)

## How to Restrict Purchase Order Creation Without a Purchase Indent?

 

This tutorial explains how to restrict the creation of a **Purchase Order without a Purchase Indent** in Logic ERP. This feature ensures that every Purchase Order is properly linked with an approved Purchase Indent, improving procurement control and process accuracy.

***

### **Objective of This Feature**

* Prevent manual PO creation without Purchase Indent
* Ensure proper procurement workflow
* Maintain document traceability
* Improve control and approval compliance

***

### **Access to Purchase Order Configuration**

* Open **Configuration Window**
* Navigate to **Default Settings**
* Locate and enable the option labeled as:

> **“Do not allow PO creation without Indent”**

<figure><img src="/files/7J5fDZi03BQieSKCloqS" alt=""><figcaption></figcaption></figure>

* Click **Save**

***

### **Verify in Purchase Order**

**Transaction Process**

* Start a **New Purchase Order Entry**
* Select the **Supplier**
* Proceed to **Item Details Section**
* Click on **Retrieve Option**
* Select the required **Purchase Indent**

<figure><img src="/files/0mgF0GCyJSXkKEYuGwuK" alt=""><figcaption></figcaption></figure>

* Once the Purchase Indent is retrieved, the item details will be fetched automatically.
* Items should be fetched through the approved Purchase Indent.

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

***

### **Attempt Manual Item Entry**

**Test Scenario**

* Try to manually enter an item without retrieving from Purchase Indent

<figure><img src="/files/6kc12SwxXuuLCDBot7Vq" alt=""><figcaption></figcaption></figure>

**System Behavior**

* Software restricts the action
* Displays error message:
  * *“*&#x50;urchase Order Creation without Job Order not allowed........*”*

***

### **Key Benefits**

* Enforces proper procurement workflow
* Prevents unauthorized manual entries
* Improves document linkage and tracking
* Ensures better approval and audit control

***

### **Best Practice Tips**

* Always create and approve Purchase Indents before PO generation
* Train users on retrieval-based PO process
* Use this feature for controlled procurement environments

***

### **Final Outcome**

* Purchase Orders can only be created through Purchase Indents
* Improved procurement discipline and traceability
* Reduced chances of unauthorized purchasing
* Better operational control and compliance


---

# 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/do-not-allow-po-creation-without-indent.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.
