All tables
tables · table

Deletion_Log

The Deletion_Log table serves as an audit trail within the ERP system. Despite its name, the table functions as a general activity log that captures various data manipulation events, including deletions and modifications. It records the "Who, What, Where, and When" for changes made to master records (such as Customer Masters) by logging the ERP user, the physical workstation details (IP, MAC Address, PC Name), the specific form used, and the object (e.g., Customer Code) that was altered.

Row count
1,404
Last entry
2026-01-16
Source
tables

Columns

14
ColumnTypeNullableMeaning
indexintegerNoPrimary Key
CompCodestringYesInternal Company Identifier
EventDatedatetimeYesDate the action occurred
EventTimestringYesTime the action occurred
ObjCodestringYesThe unique code of the record affected
ObjNamestringYesDescriptive name of the record affected
FormNamestringYesThe ERP UI form where the action originated
PC_NamestringYesWorkstation hostname
MAC_IDstringYesPhysical hardware address of the workstation
IPstringYesNetwork IP address of the workstation
PC_UserstringYesOperating System (OS) login name
ERP_UserstringYesERP application login name
RemarksstringYesContextual description of the log entry
ActionTypestringYesThe type of database operation performed

Full documentation

### 1) Overview
 The `Deletion_Log` table serves as an audit trail within the ERP system. Despite its name, the table functions as a general activity log that captures various data manipulation events, including deletions and modifications. It records the "Who, What, Where, and When" for changes made to master records (such as Customer Masters) by logging the ERP user, the physical workstation details (IP, MAC Address, PC Name), the specific form used, and the object (e.g., Customer Code) that was altered.
 
 ### 2) Column dictionary
 
 | Column | Type | Nullable | Meaning | Allowed Values | SQL Usage |
 | :--- | :--- | :--- | :--- | :--- | :--- |
 | **index** | integer | No | Primary Key | | `WHERE index = 45` |
 | **CompCode** | string | Yes | Internal Company Identifier | e.g., "DAS" | `JOIN dbo.company ON ...` |
 | **EventDate** | datetime | Yes | Date the action occurred | | `CAST(EventDate AS DATE)` |
 | **EventTime** | string | Yes | Time the action occurred | HH:MM:SS | |
 | **ObjCode** | string | Yes | The unique code of the record affected | e.g., Customer Code ("PHILLIPS") | `JOIN dbo.cust ON ObjCode = custcode` |
 | **ObjName** | string | Yes | Descriptive name of the record affected | e.g., "PHILLIPS MACHINE TOOLS" | |
 | **FormName** | string | Yes | The ERP UI form where the action originated | e.g., "frmcustmas" | `WHERE FormName = 'frmcustmas'` |
 | **PC_Name** | string | Yes | Workstation hostname | e.g., "JEETU-ACC" | |
 | **MAC_ID** | string | Yes | Physical hardware address of the workstation | | |
 | **IP** | string | Yes | Network IP address of the workstation | | |
 | **PC_User** | string | Yes | Operating System (OS) login name | e.g., "P DASS" | |
 | **ERP_User** | string | Yes | ERP application login name | e.g., "system", "ajay a/c" | `JOIN dbo.pass1 ON ERP_User = username` |
 | **Remarks** | string | Yes | Contextual description of the log entry | e.g., "Customer Master" | |
 | **ActionType** | string | Yes | The type of database operation performed | Modification, Deletion | |
 
 ### 3) Relationships & join map
 
 The `Deletion_Log` table is a standalone audit table but links to various master and security tables based on the context of the logged event.
 
 #### Primary Joins (SCHEMA_MAP Verified):
 * **Company Context:** `Deletion_Log.CompCode` -> `dbo.company.co` (or `compcode` in various headers).
 * **User Auditing:** `Deletion_Log.ERP_User` -> `dbo.pass1.username` or `dbo.UserrightsHdr.usercode`.
 * **Customer Master:** If `FormName` is 'frmcustmas', `Deletion_Log.ObjCode` -> `dbo.cust.custcode`.
 * **Form Security:** `Deletion_Log.FormName` -> `dbo.userrights.formname` or `dbo.CompanyConfig.FormName`.
 
 #### Likely Joins (Inferred):
 * **Station Tracking:** `Deletion_Log.PC_Name` or `IP` may correlate with `dbo.pass1.ComputerName` (Likely).