Search Results op_audt_dtl




Overview
Explore in AI Chat

Overview

The OP_AUDT_DTL table is a core transactional data object within the Process Manufacturing Logistics (GML) module of Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2. It functions as the detailed audit trail repository for sales order lines. Its primary role is to record and persist the historical lineage of changes made to individual sales order lines, providing a granular, auditable record that supports traceability, compliance, and operational analysis within the manufacturing and logistics processes. The table is integral to the change management workflow for sales orders, linking specific line-level modifications back to their originating change orders.

Key Information Stored

The table's structure is defined by its primary and unique keys, which dictate the fundamental data relationships. The primary key, OP_AUDT_DTL_PK, is the CHANGEORDER_LINE_ID, a unique identifier for each audit trail entry at the line level. A unique key, OP_AUDT_DTL_UK, enforces integrity on the combination of CHANGEORDER_ID and LINE_ID. These columns are critical: CHANGEORDER_ID links the detail record to its parent change order header in the OP_AUDT_MST table, while LINE_ID references the specific sales order line (in the OP_ORDR_DTL table) that was modified. While the provided metadata does not list all columns, the table logically stores details about the nature of the change (e.g., quantity, date, status modifications) for the referenced LINE_ID, tied to a specific CHANGEORDER_ID.

Common Use Cases and Queries

This table is central to auditing and reporting on sales order evolution. Common use cases include generating compliance reports that trace all modifications to a specific sales order line over time, analyzing the frequency and type of changes for process improvement, and troubleshooting order fulfillment issues by reviewing the complete change history. A typical query would join OP_AUDT_DTL to both its parent tables to retrieve a comprehensive audit trail. For example, to audit changes for a specific sales order line, one might use a pattern such as:

  • SELECT aud_dtl.*, mst.change_date, ord_dtl.ordered_item FROM gml.op_audt_dtl aud_dtl JOIN gml.op_audt_mst mst ON aud_dtl.changeorder_id = mst.changeorder_id JOIN gml.op_ordr_dtl ord_dtl ON aud_dtl.line_id = ord_dtl.line_id WHERE ord_dtl.line_id = <LINE_ID> ORDER BY mst.change_date;

This retrieves all audit entries for a line, along with header change information and the item details.

Related Objects

OP_AUDT_DTL has defined foreign key relationships with two key tables in the GML schema, forming a critical data chain for sales order auditing.

  • OP_AUDT_MST: This is the master (header) table for change orders. The relationship is defined as OP_AUDT_DTL.CHANGEORDER_ID → OP_AUDT_MST. This links each line-level audit record to its overarching change order transaction.
  • OP_ORDR_DTL: This is the sales order lines table. The relationship is defined as OP_AUDT_DTL.LINE_ID → OP_ORDR_DTL. This connects the audit entry directly to the specific sales order line that was altered, providing the business context for the change.

These relationships ensure referential integrity and enable the construction of complete audit reports by joining detail records to both the change order header and the original sales order line data.