> For the complete documentation index, see [llms.txt](https://kb.bevica.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://kb.bevica.com/documentation/reporting-and-analytics/reporting_in_bevica_-_overview/item_history_-sales.md).

# Item History (Sales)

Import and maintain historical sales to extend Bevica sales analysis.

{% hint style="info" %}
Bevica Item Sales History is a separate extension. Please contact your system administrator or your TVision contact if you would like further information or would like to install Bevica Item Sales History.
{% endhint %}

Item History functionality allows you to import pre-Bevica item related sales information and have it merged with ongoing Bevica sales information. See sales trends from day one of go-live going back as far as the data you import.

Features:

* **Item History Page** lets you see in one list page all item history. You can filter and sort old and new data. The data can also be used as the basis for external sales analysis reporting, i.e. PowerBI or Jet.
* [**Customer/Item Sales Analysis**](/documentation/reporting-and-analytics/reporting_in_bevica_-_overview/customeritem_sales_analysis.md) accessed from either the item or customer cards this page displays all sales information 'customer by item' or 'item by customer' alongside quantity and values. Filtering the page by date lets you see sales analysis over a selected time period.
* [**Moving Annual Total Sales Analysis (MAT)**](/documentation/reporting-and-analytics/reporting_in_bevica_-_overview/moving_annual_total_sales_analysis_-mat.md) reports show, month on month, 12 month previous sales figures plus other item related information. The page can also be filtered to show buying pattern by customer.

{% hint style="warning" %}
**Prerequisites**

Sales, purchase and items setup.
{% endhint %}

### Item History Page

1. In the search button, find **Item History.**
2. Open the page.

Records in the page are created from Item Ledger Entry (ILE) postings on shipping a Sales Order/Invoice or receipting a Sales Return Order/Credit Memo.

### Populating the Item History

The Item History page is updated in two ways:

* Sales from within Bevica is created and updated via the **Update Item History** report. This can be run manually or via a Job Queue.
* Importing pre-Bevica sales. Item sales information from your previous system can be imported into the page. See [Importing Item Sales History](/documentation/reporting-and-analytics/reporting_in_bevica_-_overview/importing_item_sales_history.md) for information on how to do this.

### Update Item Sales report

The report creates and updates Item History records from ILE records. When the report is run, it creates records for any new ILEs created since the last time it was run and updates existing Item History records with any changes since the last time it was run, i.e. the ILE has been invoiced (sales values) or an ILE has been revalued (cost values).

To run the Update Item History report manually, navigate to the Item History page and select the option from the page's ribbon.

{% hint style="info" %}
Because the report is looking for new, as well as changes to ILEs you should apply a **Date filter** to stop it searching for changes going too far back. We suggest a date filter of **-1M.**
{% endhint %}

### Job Queue

To run the Item History report on a periodic basis create a Job Queue for report 70515 setting it to run overnight.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://kb.bevica.com/documentation/reporting-and-analytics/reporting_in_bevica_-_overview/item_history_-sales.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.