> 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/purchase-reports/purchase-register-detailed-cross-tab.md). # Purchase Register Detailed - Cross Tab Logic ERP has added two new columns, **PARTY USER CODE** and **PO SUPPLIER ORDER NO.**, to the **Purchase Register Detailed - Cross Tab**. This release also corrects **ACCOUNT CODE** and several columns that stayed blank when chosen on their own. *** ### **Step 1: Open the Report** * Navigate to **Reports/Queries** and select **Purchase Reports**. * Open the **Purchase Register Detailed - Cross Tab**. *** ### **Step 2: PARTY USER CODE column** * Add the **PARTY USER CODE** column from the report's column settings, then tick it. * It shows the party's user code beside the party name, the same as in the **Sale Register - Cross Tab**. *** ### **Step 3: PO SUPPLIER ORDER NO. column** * Add the **PO SUPPLIER ORDER NO.** column from the report's column settings, then tick it. * It shows the supplier's order number from the purchase order behind each purchase. * Like **PO ORDER NO.**, it fills only when **Configuration > Report Consolidation > Document No.** is ticked. * When a purchase comes from more than one purchase order, the supplier order numbers are listed in the same order as **PO ORDER NO.**, one for each order, separated by commas. An order without a supplier order number leaves an empty place in the list. The column stays blank when none of the orders has a supplier order number. * The column fills even when it is the only purchase order column chosen. *** ### **What's corrected** * **ACCOUNT CODE** now shows the account code of the party. Before, it showed the party's user code, which is now in the new **PARTY USER CODE** column. On rows with no party, **ACCOUNT CODE** now shows 0 instead of blank, the same as in the **Sale Register - Cross Tab**. This is intended. * With **Document No.** ticked, **TRANSPORT MODE**, **PARTY BILL DATE**, **CHALLAN NO.**, **CHALLAN DATE**, **CASES** and **VEHICLE NO.** no longer stay blank when they are chosen without any of the other goods receipt columns, such as **G.R. NO.** or **TRANSPORT**. --- # 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/purchase-reports/purchase-register-detailed-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.