Skip to main content

Transaction Log Guide

Lynne Whitmore
  • Updated

Transaction Logs allow the user to see detailed information regarding changes made to FeneVision data.  Any screen which has this icon   in the top ribbon has the ability to show transaction logs, provided you have the logging enabled via the Database Maintenance Utility (see Advanced).

Example Scenarios

Determine who changed the price of a line item  

  1. Within Order Entry, open the order in question and select the icon.  The Transaction Log dialog automatically opens to the order you have open.
  2. Find the first record for your line item number and double-click on it to see more detail.  
  3. Use the arrows to move to other records until you find the price change.  

The user involved is shown near the top of the screen in the User field.  In the Transaction Log Details screen below, the price of lineitem 1 was changed from the Old Value of $45 to the New Value of $55 by user l.whitmore.

 

Determine who deleted an order 

  1. Within Order Entry, select the icon.  
  2. Enter the order number you are looking for in the Order Number field and press the Search button.  
  3. Double-click on the first record of Type Order to open the Transaction Log Details screen.  

If the order was deleted, then the Delete column will be present.  The user involved is shown near the top of the screen in the User field.   In the Transaction Log Details screen below the Deleted column is displayed and the user is l.whitmore.

Tips

  • Transaction Log Details:  Double click on a row in the Transaction Log screen to see more detail.
  • Up / Down Arrows:  Use the arrow keys to move to older or newer records.  Newest records appear at the top of the screen.
  • Refine Results:  Use the Refine Results button to filter out records that are duplicates and where there was no physical change in data.
  • CSR Transactions in Web:  Customer Service Representatives have the ability to create and modify quotes for customers in Web.  CSR changes can be tracked and viewed by selecting this icon .   At this time, Web transaction logging is limited to CSR logins.

 

  • Remote User:  Web orders that are show in Core as Entered By and Uploaded By Remote User, , likely means that the Web login does not have a first and last name entered in the user setup in Web. 
  • SA, IIS, and other users:  User actions can trigger the software to make additional updates.  When transaction logs do not have the exact user listed, there may or may not be other ways to determine the exact user.  These situations are explained in sections below.

IIS User

User actions can trigger the software to make additional updates.  These examples are typically from the IIS user, but might be listed for SA instead.

Order is Closed by IIS:  Occurs when the system automatically closes an order due to being fully shipped and fully invoiced.

Order is Acknowledged by IIS:  The Upload Action in Customer Setup is set to Acknowledge and Auto, you will see IIS as the acknowledge user because FeneVision Web is handling the acknowledgement.

The Upload Action setting from the General tab in Customer Setup

Order price changed on upload by IIS:  The price was changed during upload due to a difference in price in Core vs cost in Web.  Keep in mind the "price" on a Core order is the "cost" on a Web quote.  When a quote is uploaded from Web to Core, Core will calculate the manufacturer's price at upload time and then override the price on the uploaded order in Core to match the quote cost in Web. This way, the Web quote costing is honored.

Purchase Order or Purchase Order Line Item was Closed by IIS:  There are system settings in Core - Security - Defaults that can allow the software to auto close a PO or a PO line item during Receipt Entry when the full amount is received or close to it.  This can result in the IIS or SA user being listed as closing the PO or PO line item.  Looking for a transaction log entry stating who received the item, near the time of the close, will indicate who really initiated the close.  There are also prompts that ask the user if they want to close the PO or PO line item during Receipt Entry, which have the same result when the user says yes to the prompt.

SA User

User actions can trigger the software to make additional updates.  These examples are typically from the SA user, but might be listed for IIS instead.

Change in inventory quantity:  This is the type of update that can be made by one of the FeneVision APIs.  The exact user might be found by querying the APIRequestResponseLog table in the FVPerformance database near the date/time of the transaction log date.  

SELECT DateTime, EmployeeID, *
FROM FVPerformance.dbo.APIRequestResponseLog
WHERE DateTime BETWEEN '2024-02-28 10:49' AND '2024-02-28 10:51'
ORDER BY ID DESC

The BOM Cost and Cost fields were updated by SA:  Posting a PO Invoice can cause the system to update costing on an associated sales order lineitem.  The FVPerformance.dbo.APIRequestResponseLog may have more information.

Print Date is updated by user SA:  This can occur due to SSRS (SQL Server Reporting Services) facilitating the printing of the report.  Advanced users can run this query against database ReportServer in SQL Server Management Studio. The resultset includes the UserName field.  Assume the Print Date is 7/10/25 3:47:00 pm and the order’s okey is 381914:

SELECT * FROM ExecutionLog2 WHERE TimeStart >= ‘07-10-2025 15:46:00’ AND TimeStart <= ‘07-10-2025 15:47:00’ and Parameters like ‘%okey=381914%’

NTSERVICE/SQLSERVERAGENT User

There are several FeneVision SQL Agent Jobs that can update the database, and these actions can be logged as NTSERVICE/SQLSERVERAGENT in transaction logging.  For example, the FeneVision Completion Poller, goes through and updates some transactions within the system, such as complete Quantity values for the orders and when an order is shipped or has no workcell.  For general information on SQL Agent Jobs, see SQL Agent & FeneVision Agent Jobs

Unknown Windows User

To track the unknown user down, attempt to find out which machine name is associated with that account.  Request your IT team try the following steps.  Once you have the station name, you can determine how users are logging in to FeneVision on that station.

  • Use Active Directory Audit Logs
  • Open Event Viewer on the domain controller.
  • Navigate to: Windows Logs > Security
  • Filter for Event ID 4624 (successful logon).
  • Search for username in the event details.
  • The log will include the computer name under “Workstation Name.”

Advanced

  • Show All Fields: Use this checkbox at the bottom of the Transaction Log Details screen to show all fields, instead of just the fields that have changed.  For a line item, this will show information about overrides in effect, pricing info, backorder info, etc., plus internal information such as the item type number, oKey and odKey.  
  • Enable/disable logging:  The Database Maintenance Utility resides only on the database server.  Use the Logs tab to see what types of logs are enabled and to enable/disable logging.   For example, to enable the CategoryDiscountTables logging below, check the box next to it and press the Enable Logging button.  To disable logging, use the Disable Logging button.
  • How to query the FVTransLog database:  In SQL Server Management Studio, select the FVTransLog database. Expand FVTransLog's Tables node in SSMS to see what transaction log tables are available.  Typically, table names are the same as in FVMaster but with a "_Translog" suffix. To determine who made a price change on a given order and line item, first you need to know the oKey for the order.  Using Show All Fields in the Transactions Log Details screen is one way to find the oKey (described above).   Then enter your query in SSMS.  The query below shows the price changed from $45 to $55 in row 13, and the user on that row was l.whitmore.

 

Related articles