> 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/pu-order-report-size-wise-order-level-basis.md). # PU Order Report Size Wise - Order Level Basis Logic ERP has corrected several figures, totals and filters in the **PU Order Report Size Wise - Order Level Basis**. The report is also faster when **Rate From** is set to **Lot Master**. *** ### **Step 1: Open the Report** * Navigate to **Reports/Queries** and select **Order Reports**. * Open the **PU Order Report Size Wise - Order Level Basis**. *** ### **What's corrected** * **PENDING PO QTY** now leaves out cancelled purchase order lines. Pending quantities and their totals may fall. This is intended. * With **Report On** set to **Re-Order Level**, **ORDER QTY** deducts the pending purchase order quantity, so **ORDER QTY** and **AMOUNT** may rise where cancelled lines were deducted before. This is intended. * **Scan Items** now works when **Report On** is set to **Re-Order Level**. The report shows only items whose stock, across all sizes, is at or below the chosen level (**RE-ORDER LEVEL**, **MAX LEVEL** or **MIN LEVEL**). Items with no level set are left out. Saved configurations will show fewer items than before, especially those with **RE-ORDER LEVEL**, the first choice, which earlier showed every item. This is intended. * **Item Totals** now print when **Report On** is set to **Stock=0, Sale For Last ... Days** or **Sale for Last... Days**. * **RATE** now shows on item rows and on total rows when **Report On** is set to **Re-Order Level** or **Formula Basis**. It is the average rate, that is **AMOUNT** divided by **ORDER QTY**. * On the **Amount** row, the **TOTAL** column now shows the sum of the size columns. * On total rows, the **TOTAL** figure of the **Amount** line now shows two decimal places, like its size columns. * The **Min Level** row no longer repeats the **STOCK** to **AMOUNT** figures of the row above it when it is not the first row. * Sizes that belong to a linked size set no longer get an extra, always-empty column of their own beside the linked column. * The report no longer shows an error when **Report On** is set to **Formula Basis**. The formula itself is not yet applied to the figures. * The report no longer shows an error when a saved configuration has no choice in **Rate As** or **Re-Order Level As**. It now uses the first choice of the list. * The report is faster when **Rate From** is set to **Lot Master**. --- # 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/pu-order-report-size-wise-order-level-basis.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.