> 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/stock-reports/stock-ageing-analysis-cross-tab.md). # Stock Ageing Analysis - Cross Tab Logic ERP has corrected the **Stock Ageing Analysis - Cross Tab** so that **Top N Stock Items(Item + Size)** lists the items with the highest closing stock first, also when the **ITEM IMAGE** column is shown. *** ### **Step 1: Open the Report** * Navigate to **Reports/Queries** and select **Stock Reports**. * Open the **Stock Ageing Analysis - Cross Tab**. *** ### **What's corrected** * The fix applies when **Top N Stock Items(Item + Size)** is set to a number above zero, the **ITEM IMAGE** column is shown, and under **Item Consolidation** either **Item Name** is ticked or **Item Name W/o Shade** and **Shade** are both ticked. * In this setting the items are now listed in order of closing stock, highest first. Earlier the closing stock order was lost and the items came out in their ordinary order. * Earlier the first item break could also start from a different item than the first row shown. --- # 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/stock-reports/stock-ageing-analysis-cross-tab.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.