Results for “print_flag”

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

Overview

EDR_TRANS_QUERY_TEMP is a temporary reporting table owned by the EDR schema within the Oracle E-Business Suite E-Records (EDR) product module. As its description indicates, it functions as an "eRecords Reports Temporary Table," meaning it is populated transiently to stage query criteria and document identifiers used by eRecords reporting programs and concurrent processes during execution. It is not a transactional master table; rather, it is a transient working store whose rows are typically created, consumed, and purged within the lifecycle of a single report run.

The object holds a VALID status in the EDR schema and is documented with eight physical columns. Its primary key is defined by the constraint EDR_TRANS_QUERY_TEMP_P on the QUERY_ID column. From a heuristic Data Vault modeling perspective, the mined relationship data classifies this table as standalone, suggesting it best fits a satellite-like construct — an attribute-bearing, transient record keyed by a surrogate identifier — rather than a hub or link. No foreign key relationships were mined, reinforcing its role as an isolated staging object rather than a participant in the core EDR entity-relationship graph.

Key Information Stored

The table's eight documented columns capture both the surrogate key and the standard EBS audit and operational attributes:

• QUERY_ID — the surrogate primary key (constraint EDR_TRANS_QUERY_TEMP_P), uniquely identifying each staged report query record.
• DOCUMENT_ID — a business-key candidate referencing the eRecords document associated with the query; this is the principal link back to the eRecords document universe.
• CREATION_DATE — timestamp of row insertion, marking when the query staging record was generated.
• CREATED_BY — the user or process that created the staging row.
• LAST_UPDATE_DATE — timestamp of the most recent modification to the row.
• LAST_UPDATED_BY — the user or process responsible for the last update.
• LAST_UPDATE_LOGIN — the login session under which the last update occurred, supporting audit traceability.
• PRINT_FLAG — an operational indicator controlling or recording whether the associated document/query result is flagged for printing by the eRecords report process.

Because only the QUERY_ID primary key is documented as a unique constraint, DOCUMENT_ID remains the primary business-key candidate for joining this staging data to the eRecords document repository. The remaining columns are conventional EBS WHO-column-style audit fields.

Common Use Cases and Queries

This object is encountered primarily when troubleshooting or auditing eRecords reporting behavior. Because it is a temporary table, its contents reflect in-flight or recently completed report executions. Practical scenarios include:

• Verifying which documents were queued for printing during a report run.
• Auditing who initiated a report query and when, using the audit columns.
• Cleaning up orphaned staging rows after failed or interrupted concurrent requests.

Representative SQL patterns include a status-oriented query such as SELECT QUERY_ID, DOCUMENT_ID, PRINT_FLAG FROM EDR.EDR_TRANS_QUERY_TEMP WHERE PRINT_FLAG = 'Y';, an audit query filtering by CREATED_BY and CREATION_DATE, and a join to eRecords document tables on DOCUMENT_ID to resolve staged document identifiers to their report descriptions. Diagnostic scripts commonly join FND_CONCURRENT_REQUESTS indirectly via timing columns to correlate staging rows with specific request runs.

Related Objects

Although the mined relationship data classifies EDR_TRANS_QUERY_TEMP as standalone with no mined foreign keys, its functional dependencies are implicit through shared EDR column semantics rather than enforced constraints. The most significant related objects are:

• EDR_TRANS_QUERY_TEMP_P — the primary key constraint on QUERY_ID, providing the uniqueness guarantee for the staging rows.
• EDR eRecords document tables — joined via DOCUMENT_ID, resolving staged identifiers to their source documents.
• FND_CONCURRENT_REQUESTS / FND_CONCURRENT_PROGRAMS — the concurrent manager tables that drive the report executions populating this temporary table, correlated through timing and user columns.
• FND_USER — resolved against CREATED_BY and LAST_UPDATED_BY to identify acting users.
• FND_LOGINS — correlated with LAST_UPDATE_LOGIN for session-level audit reconstruction.

Because the table is transient and standalone, DBAs generally treat it as a purge target rather than a permanent reporting source, and should confirm row counts before and after report execution when diagnosing eRecords reporting issues.