> 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-version-release-notes/october-2026/reports-queries/order-reports/item-+-rate-range-wise-po-analysis.md). # Item + Rate Range Wise PO Analysis Logic ERP has corrected several figures and totals in the **Item + Rate Range Wise PO Analysis**. Cancelled purchase orders are now left out, and the report no longer shows an error in some settings. *** ### **Step 1: Open the Report** * Navigate to **Reports/Queries** and select **Order Reports**. * Open the **Item + Rate Range Wise PO Analysis**. *** ### **What's corrected** * Cancelled purchase orders and cancelled order lines are now left out of the report. Quantities, values and totals may fall where orders or lines were cancelled. This is intended. * With **Column As** set to **Pack/Size**, every pack that was ordered now gets its own column. Earlier an order line for a pack could be left out of the row and the totals. Totals may rise where this happened. * With **Column As** set to **Pack/Size**, the report no longer prints empty **Pack Totals** rows when **Pack Totals** is ticked. * Two items with the same name and pack are no longer split into several pieces with item totals in between. * With **Extra Item Groups** selected, the report no longer prints a single **Group Totals** row that only repeated the grand total. * With a **Rate Range Filter**, a rate equal to the upper limit of the chosen band is now left out of that band, the same way the rate range columns treat it. Figures for the filtered band may fall. This is intended. * A rate equal to the last rate range now shows under **Above** that rate, instead of showing no range. * The **Value** figures now show decimals the same way as their totals. * The report no longer shows an error when no rate range has been saved, and the configuration no longer shows an error when a saved rate range has no filter. * The report no longer shows an error for users whose access is limited to certain godowns. Purchase orders are not tied to a godown, so these users now see the same orders as other users of their branches. --- # 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-version-release-notes/october-2026/reports-queries/order-reports/item-+-rate-range-wise-po-analysis.md?ask=&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.