User Tools

Site Tools


implementation:wms:audittrail

6.5.3. Audit trail

The “Audit trail” function in the Produmex Office module allows to document the change history of relevant Organizational Structure Elements or relevant aspects or characteristics of items, business partners, etc.

6.5.3.1. Prerequisites

Set the changes to track on the History config tab of the Organizational Structure before starting to use the Audit trail function. Changes made in the following tables can be tracked:

TABLE
AudiPMX_AUDI
Can be lined upPMX_CBLU
Document lockingPMX_DOLL
History tablePMX_HCOH
History columnPMX_HCOL
Item shelf life for partnerPMX_ICSL
Inventory lockingPMX_INLD
Item zone typePMX_ITZT
Current lined up locationPMX_LIUP
Logistic unitPMX_LUID
Link zone – zone typePMX_LZZT
BinPMX_OSBI
CompanyPMX_OSCO
DockPMX_OSDO
Ose elementPMX_OSEL
Moveable locationPMX_OSML
Packing linePMX_OSPA
Production linePMX_OSPL
PrinterPMX_OSPR
Ose storage locationPMX_OSSL
Silo/TankPMX_OSST
Thin clientPMX_OSTC
Pmx WarehousePMX_OSWH
ZonePMX_OSZO
Page sizePMX_PGSZ
Print report eventsPMX_PRRP
Production step listPMX_PSLH
Production step list linePMX_PSLL
Quality status transitionPMX_QSTT
Quality statusPMX_QYST
ReasonsPMX_REAS
ReportPMX_RPRT
Route templatePMX_RTTH
Route template linePMX_RTTL
Fixed item on locationPMX_SLIT
SSCCPMX_SSCC
Zone typePMX_ZOTY

EXAMPLE: Route template lines
In the example we will track the changes in route templates.
First we set the PMX_RTTH table to track on the History config window.

OSE-History config

For the sake of the example, we updated a route template:
We removed the Customer 3 with the ‘Turkey _Istanbul’ shipping code and added Customer 5 instead. We also changed the route sequence.

Route templates

To see the change history of the tables you set to track on the History config tab of the Organizational Structure, open the Audit trail search window via the following path: Produmex > Reports > Audit trail.

On this windows filters for the Audit trail can be added.

  • Table: The filer will get changes only from the selected table. Please note: every table that can be tracked will be listed, not only the ones that are set to track.
  • Column: When a table is selected, it is possible to select a column from a dropdown list. Every column from the table is listed. The filter will get changes only from the selected column(s) of the table.
  • User: The filter will only get changes made by the added user.
  • From: The filter will get changes made from the selected date.
  • Till: The filter will only get changes made until the selected date.

Press the ‘Update’ button to see the details of the Audit trail. The Audit trail details window will open up. In case the user makes no selection, an overview of the complete audit trail will be shown.

EXAMPLE: Route template lines
On the Audit trail search window we select the ‘PMX_RTTL - Route Template Line’ table.

Audit trail search

6.5.3.3. Audit trail details

On the Audit trail details window an overview of the changes is shown. Displayed information:

  • Table: The table where the record was created.
  • Column: The column of the table where the record was created.
  • PK: The primary key value of the record of logged table column.
  • Type: The type of the change. Possible values are: A -Add, U -Update, D -Delete.
  • Old value: The value before the update.
  • New value: The value after the update.
  • User: The user who updated the record.
  • DB User: The database user name.
  • Host: The database server.
  • Date: Date of creation of the record.
  • Time: Time of creation of the record

The list can be filtered further with the standard SBO Filter table function.

EXAMPLE: Route template lines
The overview shows that we deleted ‘Customer 3’ customer from the template, added ‘Customer 5’ to the template then changed the route sequence.

Audit trail detail

implementation/wms/audittrail.txt · Last modified: 2018/04/23 08:34 by csuhaa