Search Results output_format_id

Overview

DOM.DOM_DOC_PUBLISH_HIST is a transactional history table in the Oracle E-Business Suite DOM (Documents) schema. It records the audit trail of every publishing event executed against a document managed by Oracle's document management and collaboration framework. Each row captures a discrete publication action: the document, revision, and version involved; the concurrent request that drove the publication; the resulting output file; the date and time of publication; and the user or process that performed it. Because the same document version can be published repeatedly to different repositories or output formats, the table functions as an append-oriented history rather than a current-state register.

In ETRM 12.1.1 the object is documented with 18 columns and a single unique index, DOM_DOC_PUBLISH_HIST_U1. The physical table resides in the APPS_TS_TX_DATA tablespace with a PCT Free of 10, and its unique index is stored separately in APPS_TS_TX_IDX. A heuristic Data Vault classification mined from the foreign-key structure identifies this object as standalone, meaning it behaves as an independent record set with no downstream dependents within the modelled relationship graph. From a modelling perspective, the historical, immutable nature of the rows suggests it can be treated as a satellite-like structure keyed by the document publishing business key, though no formal hub or link classification is asserted by the metadata.

Key Information Stored

The table's business identity is defined by the unique index DOM_DOC_PUBLISH_HIST_U1, a composite business-key candidate over DOCUMENT_ID, REVISION_ID, VERSION_ID, and PUBLISH_ID. This composite key guarantees that a given publish event cannot be recorded twice for the same document revision and version. There is no separate single-column surrogate primary key exposed in the documented schema; the composite unique index serves that role.

• DOCUMENT_ID, REVISION_ID, VERSION_ID — numeric identifiers of the document, its revision, and its version at the time of publication.
• PUBLISH_ID — numeric identifier of the individual publish action, completing the unique business key.
• PUBLISH_LOCATION — the location the document was published from, stored as VARCHAR2(100). This is the column most frequently requested in searches and is central to tracking output destinations.
• PUBLISHED_FILE_NAME — name of the generated output file, VARCHAR2(100).
• PUBLISH_DATE — the date the document was published.
• PUBLISHED_BY — the user who published the document, VARCHAR2(100).
• REPOSITORY_ID — numeric identifier of the repository targeted by the publication.
• CONCURRENT_REQUEST_ID — the concurrent request that executed the publication, enabling traceability back to the concurrent manager.
• TEMPLATE_CODE — template code used for the output, VARCHAR2(100).
• PUBLISH_TEMPLATE_ID — published template identifier, VARCHAR2(100).
• OUTPUT_FORMAT_ID — the output format applied to the publication, VARCHAR2(100).
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard WHO audit columns maintained by EBS.

The table carries a foreign key on VERSION_ID referencing VEA_VERSIONS, tying each history row back to the versioning framework that governs document content.

Common Use Cases and Queries

Typical reporting scenarios include auditing who published a given document and when, tracing a concurrent request to the artifacts it produced, and analysing publication volume by repository, output format, or template. Because PUBLISH_LOCATION is frequently the focus of investigation, a common pattern filters or groups on that column.

To list all publications for a document, including their source location:

• SELECT DOCUMENT_ID, REVISION_ID, VERSION_ID, PUBLISH_ID, PUBLISHED_FILE_NAME, PUBLISH_LOCATION, PUBLISH_DATE, PUBLISHED_BY FROM DOM.DOM_DOC_PUBLISH_HIST WHERE DOCUMENT_ID = :document_id ORDER BY PUBLISH_DATE DESC;

To trace a concurrent request back to its published output:

• SELECT CONCURRENT_REQUEST_ID, DOCUMENT_ID, VERSION_ID, PUBLISHED_FILE_NAME, PUBLISH_LOCATION, OUTPUT_FORMAT_ID FROM DOM.DOM_DOC_PUBLISH_HIST WHERE CONCURRENT_REQUEST_ID = :request_id;

To report publication activity by location and format for a date range:

• SELECT PUBLISH_LOCATION, OUTPUT_FORMAT_ID, COUNT(*) FROM DOM.DOM_DOC_PUBLISH_HIST WHERE PUBLISH_DATE BETWEEN :from_date AND :to_date GROUP BY PUBLISH_LOCATION, OUTPUT_FORMAT_ID ORDER BY 3 DESC;

Joining to VEA_VERSIONS on VERSION_ID enriches these queries with version-level attributes useful in compliance and audit reporting.

Related Objects

• VEA_VERSIONS — referenced by DOM_DOC_PUBLISH_HIST.VERSION_ID; provides version attributes for the published document.
• DOM_DOC_PUBLISH_HIST itself is the documented object of the DOM.DOM_DOC_PUBLISH_HIST FND Design Data entry.
• FND_CONCURRENT_REQUESTS — joins on CONCURRENT_REQUEST_ID to resolve the request name, phase, and status of the publishing concurrent program.
• FND_USER — resolves PUBLISHED_BY and the WHO columns to application user identities.
• DOM_DOCUMENTS, DOM_DOC_REVISIONS, and DOM_DOC_VERSIONS — related document, revision, and version tables referenced through DOCUMENT_ID, REVISION_ID, and VERSION_ID.
• VEA_REPOSITORIES — joins on REPOSITORY_ID to describe the target repository.

Because the table is classified as standalone, no documented objects reference it as a foreign-key parent; it functions as a terminal history record consumed primarily by reporting and audit queries.