Results for “completed_ind”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

OP_AUDT_DTL is a Process Manufacturing Logistics (GML) table that stores the Sales Order Audit Trail at the order line level. It resides in the GML schema and holds a VALID status in both Oracle EBS 12.1.1 and 12.2.2. The table captures a granular, time-stamped record of changes applied to process manufacturing sales order lines, enabling change history reconstruction, pricing audit, and order lifecycle tracking. Each row represents a single audited change event tied to a specific change order header and source order line.

From a Data Vault modeling perspective, the heuristic classification mined from the foreign key structure is link. This reflects the table's role in associating change order headers with the order lines they affect, rather than acting as a pure hub of business keys or a satellite of descriptive attributes. Analysts should treat this as a modeling suggestion only; the table carries both linking foreign keys and a substantial set of descriptive and denormalized attributes.

Key Information Stored

The table contains 56 documented columns. The most operationally significant are listed below.

• CHANGEORDER_LINE_ID — the surrogate primary key defined by the OP_AUDT_DTL_PK index. It uniquely identifies each audit detail row.
• CHANGEORDER_ID and LINE_ID — the two columns forming the OP_AUDT_DTL_UK unique business-key candidate, and both foreign keys. CHANGEORDER_ID references OP_AUDT_MST; LINE_ID references OP_ORDR_DTL.
• DATE_TRACKED — the effective timestamp of the audited change, central to any chronological reporting.
• PRICEREAS_CODE and NET_PRICE — the pricing reason code and net price captured at the time of the change.
• ORDER_QTY1 and ORDER_UM1 — the ordered quantity and unit of measure for the line.
• QC_GRADE_WANTED — the quality grade requested for the line.
• SHIPPER_CODE, SHIPCUST_ID, and SHIPADDR_ID — shipping party, customer, and address identifiers.
• TO_WHSE and FROM_WHSE — destination and source warehouses.
• SCHED_SHIPDATE — the scheduled shipment date.
• HOLDREAS_CODE, LINE_STATUS, and COMPLETED_IND — hold reason, line status, and completion flag.
• CHANGE_COMMENT — free-text commentary on the change.
• Standard audit columns CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, and DELETE_MARK, plus the ATTRIBUTE1–ATTRIBUTE30 and ATTRIBUTE_CATEGORY descriptive flexfield columns.

Common Use Cases and Queries

The primary use case is reconstructing the change history of a sales order line. A typical query joins the audit detail to its master header and the underlying order line:

• Audit by order line: SELECT DATE_TRACKED, PRICEREAS_CODE, NET_PRICE, LINE_STATUS FROM GML.OP_AUDT_DTL WHERE LINE_ID = :line_id ORDER BY DATE_TRACKED;
• Audit by change order: join OP_AUDT_DTL.CHANGEORDER_ID to OP_AUDT_MST to retrieve header context for a batch of line-level changes.
• Pricing analysis: filter on PRICEREAS_CODE and NET_PRICE to quantify repricing events over a period.
• Warehouse and shipping reporting: aggregate on TO_WHSE, FROM_WHSE, SCHED_SHIPDATE, and SHIPPER_CODE to review schedule changes.
• Hold and status trending: group by HOLDREAS_CODE, LINE_STATUS, and COMPLETED_IND for operational dashboards.

Report writers should filter on DELETE_MARK and use CREATION_DATE or DATE_TRACKED ranges to constrain result sets, since the table accumulates one row per audited event.

Related Objects

• OP_AUDT_MST — the audit master (header) table; joined via OP_AUDT_DTL.CHANGEORDER_ID = OP_AUDT_MST.CHANGEORDER_ID. This is the primary parent in the link relationship.
• OP_ORDR_DTL — the process manufacturing sales order line table; joined via OP_AUDT_DTL.LINE_ID = OP_ORDR_DTL.LINE_ID. Supplies the current-state line against which audited values are compared.
• Associated order and header objects that depend on OP_ORDR_DTL (for example order header and customer/ship-to reference tables) are frequently included in audit reports, though the documented foreign keys formally reference only OP_AUDT_MST and OP_ORDR_DTL.
• Concurrent programs and APIs in the GML order management flow that write audit rows into OP_AUDT_DTL during order changes.
• Custom audit, pricing, and shipping reports that consume OP_AUDT_DTL as a change-history fact source.

Because only two foreign keys are documented, the join graph is intentionally narrow: OP_AUDT_MST for header context and OP_ORDR_DTL for line context, with the surrogate OP_AUDT_DTL_PK and the OP_AUDT_DTL_UK business key governing uniqueness.