Using the Mainsaver Transaction Journal


Understanding and using the Mainsaver Transaction Journal


In the Materials Module of Mainsaver there is a submodule named “Transaction Journals”.   This submodule is generally designed for the more advanced Mainsaver user and can requires specific information in order to effectively use the information.   The module essentially records all material transactions to the STXNS table of the Mainsaver database, then allows mining of this table via the application.   The module has 2 methods for mining data as given below:

The first method is straight forward and provides predefined queries for viewing basic material transactions, i.e. part issues, part receipts, part transfers, etc.  These are located under the List Reports of the Module.    Materials > Transactions Journal > Lists

Selecting one of the options under the List Reports will return a pre-defined transaction report against the parts module.  An example of the Inventory Adjustments from Reconciliation Report is given below.

The second method provides more flexibility in defining the search/query on the transactions table, allowing the user to mine the data a bit deeper.  It does, however require specific information about the transaction types/codes in Mainsaver.   This method of recalling transaction data is initiated by clicking on the “Table View” button on the ribbon menu under Transactions Journal, then defining the desired query by then clicking on “Define Query”.  The standard screen for defining queries will be presented, and will allow filtering against the STXNS table.   The user can then query for specific transactions based on transaction date, type, user login, specific part number, and many others.

However, in order to effectively use this option, the user must generally filter the query on a transaction code, of which there are many in Mainsaver.   In order to determine which transaction code(s) to filter on, the user must use the table given below to determine determine which transaction that want to see.  As an example, if the user wanted to filter on Material Transactions Issued to Assets the transaction code would be an MT33.


Proper mastering of the Transaction Journal will allow the user to mine extensive transactional data from the Mainsaver database.