> 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/reports-queries/order-reports/purchase-order-status-report/purchase-order-status-report-configuration.md).

# Purchase Order Status Report - Configuration

The configuration of the [**Purchase Order Status Report**](https://kb.logicerp.com/logic-erp-learning-hub-tutorials-and-best-practices/reports-queries/order-reports/purchase-order-status-report.md) decides which orders appear, how far receipts are split, how quantities and rates are shown, and which totals are printed. You can keep several configurations and pick one when you run the report. A new configuration starts on the first choice of every list, with every tick box unticked.

***

### **Step 1: Open the configuration**

* Navigate to **Reports/Queries\Order Reports** and click on "Purchase Order Status Report".
* Click **Configuration**. The **Purchase Order Status Report Config** window opens.
* Pick a configuration from the list to change it, or type a new name to start one. Names are saved in capital letters.

***

### **Step 2: Report Options — what the report shows**

| Setting                               | What it does                                                                                                                                                                                                                                                                                                                                                                                                                    |
| ------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Report Type**                       | **Lot Wise** (first choice): one row for each lot received, with **LOT NUMBER**, **LOT CODE** and **GODOWN NAME** filled. **Item Wise**: the lots received on the same bill or challan at the same rate are added together into one row for the item, and the lot columns are blank. If **Packs as** is **Lot CF**, lots with different pack sizes stay on separate rows. The ordered quantity and amount are the same in both. |
| **Purchase Order Filter**             | **Billed PO** (first choice): only order items received at least once, on a purchase bill or a purchase challan. **All PO**: also a row for each order item not received at all. **PO Only**: every order item, received or not, with the receipt columns left empty.                                                                                                                                                           |
| **Date Fillter As**                   | Which date of the purchase order the **From** and **To** dates check: **Voucher Date** (first choice) or **Valid Till Date**.                                                                                                                                                                                                                                                                                                   |
| **Party Filter As**                   | Whether the **Supplier** selection, and supplier rights, apply to the order's **Supplier** (first choice) or its **Transfer Party**.                                                                                                                                                                                                                                                                                            |
| **Show Data For Current Branch Only** | Shows only the orders and receipts of the branch you are logged in to; any branches picked under **Branch** are ignored.                                                                                                                                                                                                                                                                                                        |
| **Branch Consolidation**              | **None** (first choice) or **Branch Wise**. **Branch Wise** fills **BRANCH NAME**, lists the orders branch by branch, and is needed for **Branch Totals**.                                                                                                                                                                                                                                                                      |
| **Item Order**                        | How the items of an order are listed: **Item + Size Wise** (first choice) or **Item Wise** (both by item name and pack), **Company Wise**, **Group Wise** or **Shade Wise**. Orders are always listed by order date and number first. With extra item groups chosen, items are listed by those groups first, and **Group Wise** lists by item only.                                                                             |

***

### **Step 3: Report Options — quantities and rates**

| Setting                        | What it does                                                                                                                                                                                                                        |
| ------------------------------ | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Qty CF**                     | The unit in which **ORDER QTY**, **RECEIPT QTY** and **PENDING QUANTITY** are shown: **Unit** (first choice), **Item CF1**, **Item CF2**, **Item CF3** or **Weight/Unit**.                                                          |
| **Weight In**                  | **KGS**, **GMS**, **QTLS** or **TONS** — used when **Qty CF** is **Weight/Unit**.                                                                                                                                                   |
| **Packs as**                   | The pack size used for **ORDERED PACKS** and **RECEIVED PACKS**: **PO CF Quantity** (first choice), **Lot CF**, **Item CF1**, **Item CF2** or **Item CF3**.                                                                         |
| **Qty Decimalization**         | Ticked: packs are shown as decimals. Unticked: packs are shown as packs and loose pieces.                                                                                                                                           |
| **Rate On Basis of**           | **Per Unit** (first choice) or **Per Pack**. **Per Pack** shows **RATE**, **BILLED RATE** and **RATE DIFF** per pack, using the **Packs as** pack size.                                                                             |
| **Rate-2 From**, **Rate-2 As** | Fill the **RATE-2** column: the rate is taken from the **Lot** or the **Item**, as **Basic Rate**, **Pur Rate**, **Sale Rate**, **MRP** or **Sp Rate1** to **Sp Rate5**. Order items not yet received always take it from the item. |

***

### **Step 4: Report Totals**

| Setting           | What it does                                                                           |
| ----------------- | -------------------------------------------------------------------------------------- |
| **PO Wise Total** | Prints a total after each purchase order.                                              |
| **Branch Totals** | Prints a total for each branch. Needs **Branch Consolidation** set to **Branch Wise**. |
| **Grand Totals**  | Prints a total for the whole report.                                                   |

The names of the totals rows appear in the **SUPPLIER NAME** column, so keep that column switched on.

***

### **Step 5: Extra Group Options**

* **Extra Item Groups** — choose the item groups to show, and their order. Each chosen group gets its own column, filled with the item's group, and the items are listed by those groups. With extra item groups chosen, the **GROUP NAME** column is left blank.

***

### **Step 6: Save**

* Click **Save** and answer **Yes**. The window closes, and the configuration is used the next time the report is run with it.
* You need rights to modify configurations. On the web the configuration can be viewed but not saved.

***

### **A good starting set**

> **Example — pending orders to follow up**
>
> Set **Purchase Order Filter** to **All PO** and **Report Type** to **Item Wise**, tick **PO Wise Total** and **Grand Totals**, and save it as **PENDING PO FOLLOW UP**. Switch on **PENDING QUANTITY** and **VALID DATE - RECEIPT DATE** in the column settings. The last row of each item shows how much is still to come, and an item not received at all shows its full ordered quantity. **VALID DATE - RECEIPT DATE** shows how late each receipt arrived. Orders already fully received are listed too, with nothing pending.


---

# 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/reports-queries/order-reports/purchase-order-status-report/purchase-order-status-report-configuration.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.
