> 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/customer-+-item-sale-analysis/item-wise-year+month-wise-sales-cross-tab.md).

# Item Wise Year+Month Wise Sales - Cross Tab

Logic ERP has corrected the **Item Wise Year+Month Wise Sales - Cross Tab** report. **Sale for Last n Months** now fills the earlier months, **STOCK In HAND** and **PREVIOUS To PREVIOUS MONTH SALE** now show, and **LAST YEAR SALE** and the opening stock columns now show the right figure on every row.

***

### **Step 1: Open the Report**

* Navigate to **Reports/Queries** and select **Customer + Item Sale Analysis**.
* Open the **Item Wise Year+Month Wise Sales - Cross Tab** report.

***

### **What's corrected**

**Month and period columns**

* With **Column As** set to **Month**, one financial year selected and **Sale for Last n Months** entered, the months before the report start date are now filled with their sales. Earlier these months were empty.
* When **Sale for Last n Months** goes back over more than one earlier financial year, every year in between is now included. With **Column As** set to **Year**, this adds a column for each year in between.
* With **Column As** set to **Month**, a date range that starts between January and March no longer adds empty April to December columns.
* A start or end date of 29 February no longer gives an error when the report also covers a year without 29 February, such as another selected financial year or **LAST YEAR SALE**.

**STOCK In HAND, PREVIOUS To PREVIOUS MONTH SALE and the six-month columns**

* **STOCK In HAND**, **PREVIOUS To PREVIOUS MONTH SALE** and **AVG PREVIOUS To PREVIOUS MONTH SALE** now show their figures. Earlier these columns were always blank. **STOCK In HAND** shows the stock as on the report end date, without expired and damaged stock, and follows **Godown Selection** and the user's branch rights.
* With **Column As** set to **Year**, **PREVIOUS MONTH SALE**, **PREVIOUS To PREVIOUS MONTH SALE**, **LAST SIX MONTHS SALE** and their average columns now show their full figure on a separate row with a blank **PERIOD**. Earlier the figure was split over the month rows.
* With **Column As** set to **Month** and more than one financial year selected, these columns now show their full figure on the rows of the year that contains the report end date. Earlier the figure was split between the years.

**LAST YEAR SALE and OPENING STOCK**

* **LAST YEAR SALE**, **OPENING STOCK (CURRENT MONTH)** and **OPENING STOCK (PREVIOUS MONTH)** now show each row's own figure when **Extra Item Groups** are selected. Earlier they repeated the whole branch figure on every group row and added it up again in the totals. These totals will **fall** to the correct figure. This is intended.
* With **Item Code** ticked under **Report Consolidation**, these columns now show the figure of each item code.
* With more than one financial year selected and the **PERIOD** column shown, each year's rows now show that year's **LAST YEAR SALE** and opening stock. Earlier every year's rows showed the first year's figure, or **LAST YEAR SALE** was blank.
* **LAST YEAR SALE** now leaves out deleted bills and follows the **Stock Transfer Filter** and the **Party** and **Series** selections, the same way as the current year's sale, so it can **fall**. This is intended. Selecting a **Company** with **LAST YEAR SALE** no longer gives an error.
* Opening stock now leaves out expired and damaged stock and follows **Godown Selection**, the same way as **STOCK In HAND**.
* Running the report again in the same window no longer carries over **LAST YEAR SALE** or opening stock figures from the previous run.

**Item CF and Rate columns**

* **ITEM CF**, **ITEM CF DESCRIPTION**, **RATE 1** and **RATE 2** no longer give an error when none of **Pack / Size**, **Item Name** or **Item Code** is ticked under **Report Consolidation**. They stay blank in that case.

**Groups, targets and totals**

* **Extra Item Groups** now show even when **Group** is not ticked under **Report Consolidation**.
* With **Extra Item Groups** selected and **Group** ticked under **Report Totals**, the **Group** total row, which only repeated the grand total, is no longer shown.
* **Extra Branch Groups** subtotal rows and **Item Code** total rows now carry their values. Earlier they were shown empty.
* Branches are now listed together under their extra branch group.
* **BRANCH TARGET QTY** and **BRANCH TARGET VALUE** now show only the item-wise branch targets. Earlier customer group and agent group targets could be added to an item. These columns can **fall**. This is intended.

**Settings and errors**

* With **Column As** set to **n Days Sale Range** and no **Sale n Days Range** entered, the settings now cannot be saved and show "Sale n Days Range must be entered when Column As is n Days Sale Range." Settings already saved this way show "Sale n Days Range is not configured." when the report is run. Earlier the report opened with no rows.
* Every level of **Item Consolidation Order** is now followed. Earlier, once the settings were saved again, the last level could be ignored.
* The report no longer gives an error for a user who has rights to only some branches when **Branch Consolidation** is **None**. **BRANCH TARGET QTY** and **BRANCH TARGET VALUE** now also follow the user's branch rights.
* The report no longer gives an error with **Branch Consolidation** set to **Branch** when no **Extra Branch Groups** are saved.


---

# 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/customer-+-item-sale-analysis/item-wise-year+month-wise-sales-cross-tab.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.
