======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 [[implementation:wms:history|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** ^ **TABLE NAME** ^
|Audi|PMX_AUDI|
|Can be lined up|PMX_CBLU|
|Document locking|PMX_DOLL|
|History table|PMX_HCOH|
|History column|PMX_HCOL|
|Item shelf life for partner|PMX_ICSL|
|Inventory locking|PMX_INLD|
|Item zone type|PMX_ITZT|
|Current lined up location|PMX_LIUP|
|Logistic unit|PMX_LUID|
|Link zone – zone type|PMX_LZZT|
|Bin|PMX_OSBI|
|Company|PMX_OSCO|
|Dock|PMX_OSDO|
|Ose element|PMX_OSEL|
|Moveable location|PMX_OSML|
|Packing line|PMX_OSPA|
|Production line|PMX_OSPL|
|Printer|PMX_OSPR|
|Ose storage location|PMX_OSSL|
|Silo/Tank|PMX_OSST|
|Thin client|PMX_OSTC|
|Pmx Warehouse|PMX_OSWH|
|Zone|PMX_OSZO|
|Page size|PMX_PGSZ|
|Print report events|PMX_PRRP|
|Production step list|PMX_PSLH|
|Production step list line|PMX_PSLL|
|Quality status transition|PMX_QSTT|
|Quality status|PMX_QYST|
|Reasons|PMX_REAS|
|Report|PMX_RPRT|
|Route template|PMX_RTTH|
|Route template line|PMX_RTTL|
|Fixed item on location|PMX_SLIT|
|SSCC|PMX_SSCC|
|Zone type|PMX_ZOTY|

<WRAP round box>**Limitation:**\\
For some tables to run you will need to adjust additional tables in the [[implementation:wms:history|History config tab]].

The reason for the additional adjustments for specific tables are some of the tables are dependent on one another. If a table is a child table and during the parent adjustment, the //Audit system// checks the parent's settings. If there is no setting for the parent it will not generate the child table.
</WRAP>

**The following list of tables will require extra additional configuration to work:**

^ **Tables** ^ **Additional Configuration** ^ 
| Can be lined up - **PMX_CBLU** | Production line - **PMX_OSPL** | 
| History column - **PMX_HCOL** | History table - **PMX_HCOH** | 
| Link zone – zone type - **PMX_LZZT** | Zone - **PMX_OSZO** | 
| Production step list line - **PMX_PSLL**| Production step list - **PMX_PSLH** | 
| Quality status transition - **PMX_QSTT** | Quality status - **PMX_QYST** | 
| Route template line - **PMX_RTTL** | Route template - **PMX_RTTH** | 


**For the "Fixed item on location" table you will have more options to work with:**

^ **Table** ^ 
| Fixed item on location - **PMX_SLIT** |

^ **PMX_SLIT needs one of the following tables:** ^
| Automated Storage Table - **PMX_OSAS** | 
| Bin - **PMX_OSBI** | 
| Silo/Tank - **PMX_OSST** | 
| Warehouse Automation Table - **PMX_OSWA** | 


<WRAP round box>
EXAMPLE: **Route template lines** \\
In the example we will track the changes in route templates. \\
First we set the **PMX_RTTL** and** PMX_RTTH** tables - as previously explained we need to adjust both the child and parent tables to run the required route templates table - to track on the [[implementation:wms:history|History config]] window.

{{ :implementation:functionalguide:reports:audit:history_config.png.png |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.

{{ :implementation:functionalguide:reports:audit:route_templates.png |Route templates}}
</WRAP>

=====6.5.3.2. Audit trail search=====
To see the change history of the tables you set to track on the [[implementation:wms:history|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.

<WRAP round box>
EXAMPLE: **Route template lines** \\
On the Audit trail search window we select the ‘PMX_RTTL - Route Template Line’ table. 

{{ :implementation:functionalguide:reports:audit:audit_trail_search.png |Audit trail search}}
</WRAP>

=====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.

<WRAP round box>
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. 

{{ :implementation:functionalguide:reports:audit:audit_trail_detail.png |Audit trail detail}}
</WRAP>