Skip to content
English
  • There are no suggestions because the search field is empty.

How to view, manage, and edit Stock Item History

The history of any stock items can be viewed by accessing the stock item management page.

This article explains:

Data entered and saved directly into the stock item history screen will propagate forwards in time through future events. There is no "undo" function for these changes.

Accessing stock item histories

The stock item history page can be accessed from any MaiaGrazing page where stock items are visible and displayed in blue. Below are the instructions needed to access stock items from:


How to access the stock item history page from the mob/herd list:

  • Click on the 'Operations' tab

  • Click on 'Livestock > Mob/Herd List'

  • Click on expand all

The stock items will appear in the column under stock item name (1)

  • Click on the name of the stock item to open the stock item history screen.

How to access the stock item history page from the mob/herd management page:

  • Click on the 'Operations' tab

  • Click on 'Livestock'

  • Click on 'Mob List'

  • Click on the name of the mob/herd that contains the stock item you want to see the history for.

This will open the mob/herd management screen.

  • Click on the 3 dots 3 Dotsto the right of the stock item you wish to view the history for.

  • Click on 'View History'


Reading the stock item history screen.

Column 1 - Event names

A new event line is created automatically against each impacted stock item when a:

  • Purchase

  • Sale

  • Merge, or

  • Split

The above types of events will have individual records created in the system.

  • Click on the name of the event in this column to open the event record.

Column 2 - Type

This column displays the type of event that created this data line.

Events in MaiaGrazing include:

  • Purchases

  • Sales

  • Merges

  • Splits, or

  • Manual

A Manual entry indicates that this was an adjustment to the number of stock belonging to this stock item through an event that was not a purchase, sale, merge, or split. These are usually lost, found, deaths, and ration records.

Changes to the weight, price, or feed demand of this stock item will also create a manual entry.

Column 3 - Date

This column displays the date of the event that created this data line.

Clicking on the arrow beside the word date will change the order of the stock item history from oldest-newest to newest-oldest entry.

Column 4 - Head

This column displays the total number of head in this stock item as at the date that the event occurred.

Column 5 - Head Change

This column displays the changes to the number of head in this stock item due to the event that occurred on this date.

Column 6 - Rating

This column displays the changes to the feed demand rating for this stock item due to the event that occurred on this date.

Column 7 - Weight

This column displays the changes to the average weight of the stock in this stock item due to the event that occurred on this date.

Column 8 - Price

This column displays the changes to the price value of this stock item due to the event that occurred on this date.

Column 9 - Reconciliation

This column is where the the reason for a change in head will be displayed.

Reconciliation reasons include:

  • Purchases

  • Deaths

  • Births

  • Losts

  • Founds

  • Rations

Sales do not have a reconciliation entered in this screen.

 


Deleting a line of data

Clicking on the rubbish bin in a line of data will delete that line of data and remove any changes made to head, rating, price, or weight. (10)

Only manual events can be deleted this way.

To delete a line of data associated with any other type of event will require accessing the event that created the line of data.


Editing data directly in the stock item history screen

It is strongly recommended that the stock item history screen is used to check the accuracy of historical data only.

Data entered and saved in this screen can not be undone. Data entered in this screen will propagate forward through future events and can corrupt the rest of your data.

An example of data propagation.