Results for “edr_prepare_document_temp”

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

Overview

EDR_PREPARE_DOCUMENT_TEMP is a transient staging table within the EDR (E-Records) product module of Oracle E-Business Suite, documented as VALID in the EDR schema for releases 12.1.1 and 12.2.2. Its stated purpose is to store the transient PDF rendering of individual E-Records that a user has selected for printing. When a user initiates a print or batch-print action against one or more E-Records, the concurrent program assembles the selected records into a temporary PDF payload staged in this table, keyed by the request that is executing the print job. Because the content is transient by design, rows are expected to be short-lived and are typically purged once the printing request completes or is recycled by the request-processing framework.

Under the heuristic Data Vault classification mined from the documented foreign-key structure, this object is assessed as standalone. That is a modeling suggestion only: no outbound foreign keys to other EDR or EBS entities are documented, so the table behaves as an isolated transient buffer rather than a hub, link, or satellite in a conventional Data Vault model. Its natural grain is one row per document per concurrent request.

Key Information Stored

The documented physical schema in ETRM 12.2.2 comprises five columns owned by the EDR schema. The most significant are:

• DOCUMENT_ID — identifier of the source E-Record document being prepared for printing; forms the first component of the composite primary key and therefore the leading correlation key back to the parent E-Record.
• REQUEST_ID — the concurrent request identifier under which the transient rendering was generated; forms the second component of the primary key and isolates concurrent print jobs from one another.
• ERECORD_SUMMARY_PDF — PDF payload holding the summary rendering of the E-Record; one of the LOB-backed columns evidenced by the SYS_IL indexed LOB segments.
• ERECORD_PDF — PDF payload holding the full detail rendering of the individual E-Record.
• TRANSIENT_PDF — the transient PDF blob assembled for the print selection, reflecting the table's stated purpose.

The surrogate primary key is EDR_PREPARE_DOCUMENT_TEMP_PK over (DOCUMENT_ID, REQUEST_ID). No separate single-column unique business key is documented; the composite key is the only business-key candidate, and the remaining unique indexes (SYS_IL0000324985C00003$$ through SYS_IL0000324985C00005$$) are internal LOB indexes supporting the PDF columns, not business constraints. Practical joins should therefore always constrain on both key columns to avoid cross-request ambiguity.

Common Use Cases and Queries

Typical usage is diagnostic and operational rather than analytical. Common scenarios include verifying that a print request produced output, retrieving the staged PDF for a specific document, and cleansing orphaned transient rows left behind by failed or cancelled requests.

• Retrieve the staged PDF for a document and request: SELECT TRANSIENT_PDF FROM EDR.EDR_PREPARE_DOCUMENT_TEMP WHERE DOCUMENT_ID = :doc_id AND REQUEST_ID = :req_id;
• Count documents staged per print run: SELECT REQUEST_ID, COUNT(*) FROM EDR.EDR_PREPARE_DOCUMENT_TEMP GROUP BY REQUEST_ID ORDER BY REQUEST_ID DESC;
• Confirm a specific document was included in a batch: SELECT DOCUMENT_ID, LENGTH(TRANSIENT_PDF) FROM EDR.EDR_PREPARE_DOCUMENT_TEMP WHERE REQUEST_ID = :req_id;
• Identify stale transient rows by joining to FND_CONCURRENT_REQUESTS on REQUEST_ID and filtering for completed or errored phases, then scheduling deletion.

Given the transient nature of the data, no operational reporting should depend on this table; it should be treated as a short-lived buffer only.

Related Objects

Because the table is classified as standalone, no foreign keys to peer tables are documented. The most significant associated objects inferred from the metadata and the EDR print workflow are:

• FND_CONCURRENT_REQUESTS — joined on REQUEST_ID to identify the executing print request, its phase, and status.
• FND_CONCURRENT_PROGRAMS — describes the print/prepare-document concurrent program responsible for populating the staged rows.
• The EDR E-Record parent entity referenced through DOCUMENT_ID, which supplies the source content rendered into ERECORD_PDF and ERECORD_SUMMARY_PDF.
• EDR print and batch-print concurrent programs and their EDR Documents output templates, which consume TRANSIENT_PDF for delivery.