Ir al contenido principal

Auditing Fields in Sage Enterprise Management (Sage X3)



Have you ever needed to know the previous value of a field or who changed it and when? When people ask us how to do this, we’re often unable to offer answers – unless we’re talking about Sage Enterprise Management (Sage X3), which can be configured to provide this information without any customization.

There are two types of audits in Enterprise Management:

  • A record audit, which tracks the creation, modification, and/or deletion of an entire line in a table
  • A field audit, which tracks the before and after values of a field every time it’s modified

Use the following steps for auditing fields in Sage Enterprise Management:

Identify the table and the fields you want to audit. We recommend tracking only the fields that are critical to your business because this process adds overhead to the normal function processing.

In our scenario, the sales representative field name is REP and is stored on table SORDER.



Add the fields to the Audit tab (located in the Tables function under Development > Data and Parameters).
The field auditing works in conjunction with the record auditing, so check the Creation, Modification, and/or Deletion boxes depending on which you want to track.

When adding the fields, you can specify a condition for the system to log the changes on the field only when the condition is met. To track all the changes, leave the Operator and Value fields empty. After the changes, save and validate the table. For frequently used tables, we recommend making changes when no users are on the system.

auditing fields in Sage Enterprise Management (Sage X3)

Use the Audit Fields inquiry (under Usage > Audit) to check the changes; you can filter the data on this screen by table, field, event, and other criteria to make the information more manageable. Check the “Detail of fields” check box and make sure to click on the Search button again to see the Previous and New value of each field.

auditing fields in Sage Enterprise Management (Sage X3)

There’s also a Tables inquiry (Usage > Audit) that shows logging information at a record level.

Setting up auditing traceability is a fairly simple process in Sage Enterprise Management that offers valuable information you can use anywhere in the system.

If you’d like further help setting up auditing traceability in Sage Enterprise Management or have questions about Sage’s product offerings, please contact us for more information.


Entradas populares de este blog

How to Call an External Program from Sage ERP X3

Origen fuente:   https://www.rklesolutions.com/blog/sage-x3-call-external-program November 20, 2014 By Denise Hartman Leave a Comment It is sometimes useful to be able to access external programs, such as .exe files, from the  Sage ERP X3   menu. Below are instructions for adding a menu item to Sage X3 that references a .Net .exe. COPY THE .EXE FILE TO THE SAGE X3 DIRECTORY The example used here uses the  Callui  function in the Sage X3 code to call OpenFile, and references the .exe program using the parameter UILocalDir. The program being executed must reside in a pre-defined list of directories available to this function. Depending on the parameter used for UILocalDir, the .exe should be copied to one of the 3 directories below. Temp Report RtsTemp Below is an excerpt from the X3 Help, which defines where each of these directories resides within the Sage ERP X3 client installation. In this example, the Temp directory is used. Bel...
Leer más

SAGE X3 SILENT IMPORT (IMPORTSIL) WITH ERROR CATCHING

FUENTE ORIGINAL: https://pluginx3.com/en/blog/post/sage-x3-silent-import-importsil-with-error-catching.html You already know how to manually generate a CSV file in order to import it threw a template in Sage X3. But If you wonder how to catch detailed errors after a silent import here is the solution. Sometimes you need to catch the incoming errors in order to alert the end-user regarding an issue. Closed period, wrong date etc …. Unfortunalty the standard Sage X3 silent import function doesn’t natively show the detailed errors during the import process. Call IMPORTSIL([M:IMP2]MODIMP,[M:IMP2]NOMIMP) From GIMPOBJ And the standard function ERR_IMPORT will only show the overall status of the importation and not the detailed errors. IMPORTSIL function is pushing all the log data into a tracefile in order to avoid any popup on end-user screen. So you have a log file available in order to search for errors in it. Sage X3 runtime is using the same principals standards as any shell for log...
Leer más

How to Delete particular row and reset Grid

Origen: https://www.greytrix.com/blogs/sagex3/2014/06/30/how-to-delete-particular-row-and-reset-grid/ By  Greytrix   |   June 30, 2014 0 Comment We usually come across a scenario when we need to delete row from a grid through coding. Now we can even think of using SQL queries to delete the data, but these changes were reflected at the database level. The screen do not have the changes reflected and this may cause data inconsistency. So for deleting line from grid and then resetting the grid I used ‘DELA’ an existing function of X3. New Stuff :   How to send mail programmatically Dela  is used to delete elements from single-sized tables, from a given index. And also it resets the grid.   Syntax: Dela start [ , number [ , limit ] ] list_nom_var Example: Dela is used to delete elements (default 1) from a set of single-sized tables. In the instruction’s syntax, start establishes the index (shared by all the tables) where the deletion ...
Leer más