Search Results op_prsl_aud_pk




Overview
Explore in AI Chat

Overview

The OP_PRSL_AUD table is a legacy data object within the Oracle E-Business Suite (EBS) Process Manufacturing Logistics (GML) module. According to the official ETRM documentation, its primary status is that it was not utilized in the 11i release. In the context of later versions like 12.1.1 and 12.2.2, this typically indicates the table is a historical artifact, likely retained for potential data reference or upgrade compatibility but not actively used by core application logic. Its name suggests it was designed as an audit table, potentially intended to track changes to presales order lines, but this functionality was superseded or implemented elsewhere in the application architecture.

Key Information Stored

Based on the provided metadata, the table's structure is defined by its primary key constraints, which reveal its critical columns. The table is designed to uniquely identify audit records through a composite key involving a presales order line identifier and a change identifier. The key columns are:

  • PRESALES_ORDLINE_ID: Likely references a line from a presales order, serving as the parent record being audited.
  • CHANGEPRSL_ID: An identifier for a specific change event or transaction.
  • CHANGEPRSL_LINE_ID: Serves as a unique primary key for each individual audit record in the table.

The existence of multiple primary key constraints (OP_PRSL_AUDI1, OP_PRSL_AUD_PK, OP_PRSL_AUD_UK) suggests a complex historical design for ensuring uniqueness, with OP_PRSL_AUD_UK (on PRESALES_ORDLINE_ID and CHANGEPRSL_ID) being a notable unique constraint.

Common Use Cases and Queries

Given the documented note that this table is not used, there are no active application use cases. Its presence is primarily of interest to database administrators and technical consultants during system analysis, data cleanup initiatives, or when tracing the historical evolution of the schema. Queries would generally be for investigative purposes only. A sample query to examine any existing data would be:

SELECT COUNT(*), 'OP_PRSL_AUD' AS table_name FROM GML.OP_PRSL_AUD;

If data is found, further analysis might involve joining to related presales order tables to understand the context of the audit records, though such joins would be speculative without full column definitions. In standard implementations, this table would not be used for custom reporting or integrations.

Related Objects

While explicit foreign key relationships are not detailed in the metadata, the column names strongly imply relationships to other tables within the GML module, particularly those handling presales order lines. The table likely has a logical, if not enforced, relationship to a base presales order line table. Furthermore, as an audit table, it may have been populated by database triggers or application logic on tables such as OP_PRSL (if it exists), which would be its primary related object. Developers should consult the specific instance's data dictionary for any existing triggers or code references to this table to confirm its historical linkages.