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

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

Valores de fstat

Fstat fstat  is a numeric status that is returned upon execution of a database operation, a sequential file operation, or a lock instruction. Syntax fstat Examples # MYTABLE is a table with a key called KEY1, that has a unique component called KEYVAL # Create a record in the table MYTABLE with they key value 1 if it doesn't exist Local File MYTABLE [MYT] Read [MYT]KEY1=1 If fstat [MYT]KEYVAL=1 : Write [MYT] If fstat MSG="The key was created in the mean time" Else MSG="Key created" Endif Else MSG="Key already exists" Endif Details fstat  is always set to '0' if the operation is successfully completed, and has a non-null value if there is an error: In a sequential read ( Getseq  and  Rdseq ),  fstat  is set to '1' at the end of the file. On  Lock ,  fstat  is set to '1' if the lock could not be performed. For a database operation ( Read ,  Look ,  Readlock ,  For ,  Write ,  ...
Leer más

How To Add a Custom Selector for the Screen Field

Fuente original del artículo:   https://www.rklesolutions.com/blog/how-to-add-a-custom-selector-for-the-screen-field January 5, 2022 By RKL Team Leave a Comment There may be times when you want to add a pop-up window to select a field for a screen. Sometimes this can be handled automatically if the field is a standard X3 object field (i.e. when selecting a product with a type of ITM from the ITMMASTER table). There may be other times where a standard look-up is not available, and some custom code is required to do the selection window. We'll show you how to add a custom selector of your choosing to the screen field. ADD SELECT ON SCREEN FIELD The first step is to add the appropriate code to the field on the screen in Sage X3: Go to  Development > Script Dictionary > Screens Select Your Screen Select the field to have the lookup for  by moving your cursor to it on the screen. The field should show with a blue background. Select a type of "Selection" , and an  ac...
Leer más