Results for “okc_report_htm”

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

Overview

OKC_REPORT_HTM is a Contracts Core (OKC) table that stores the rendered HTML output produced during Oracle Contracts printing. When a contract is printed, Oracle EBS executes an SQL-XML-XSL-HTML transformation pipeline: a query extracts contract data into an XML document, a selected XSL stylesheet formats that XML, and the resulting HTML document is persisted in this table. OKC_REPORT_HTM therefore serves as a materialized archive of contract print output, allowing the generated document to be retrieved, reprinted, or audited without re-executing the full transformation chain.

The table resides in the OKC schema and is classified as VALID. It is present in both Oracle EBS 12.1.1 and 12.2.2, and the documented physical schema lists 13 columns. Under the heuristic Data Vault classification mined from its foreign key structure, OKC_REPORT_HTM is modeled as a standalone object rather than a hub, link, or satellite. This suggests the table is treated as an independent content store keyed by contract, version, language, stylesheet, and source document context, rather than participating in a normalized reference or relationship network.

Key Information Stored

The primary key, OKC_REPORT_HTM_PK, is a composite business key defined over five columns: CHR_ID, MAJOR_VERSION, LANGUAGE, XST_ID, and SCN_ID. A matching unique index, OKC_REPORT_HTM_U1, enforces the same five-column combination. The most significant columns include:

• CHR_ID — Contract header identifier; anchors the HTML output to a specific contract.
• MAJOR_VERSION and MINOR_VERSION — Version lineage of the contract at the time of printing.
• LANGUAGE — Language in which the HTML document was generated.
• XST_ID — Identifier of the XSL stylesheet (the selected print template) applied during transformation.
• SCN_ID — Source/scenario identifier associated with the print run, completing the primary key.
• HTM_TEXT — The stored HTML document content produced by the SQL-XML-XSL-HTML transformation; this is the core payload of the table.
• SECURITY_GROUP_ID — Foreign key to FND_SECURITY_GROUPS, providing multi-tenant/security partitioning consistent with the EBS Multi-Org Access Control model.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard EBS WHO columns capturing audit and concurrency metadata.

Common Use Cases and Queries

Typical scenarios include retrieving previously generated contract documents, verifying that printing completed, troubleshooting transformation errors, and reporting on print activity. A representative query retrieves the latest HTML for a contract and stylesheet:

• SELECT htm_text FROM okc_report_htm WHERE chr_id = :chr_id AND major_version = :major_version AND language = :language AND xst_id = :xst_id ORDER BY scn_id DESC;
• Counting print runs per contract: SELECT chr_id, COUNT(*) FROM okc_report_htm GROUP BY chr_id ORDER BY 2 DESC;
• Auditing recent generation activity: SELECT chr_id, major_version, xst_id, creation_date FROM okc_report_htm WHERE creation_date > SYSDATE - 7;
• Security-scoped reporting: join SECURITY_GROUP_ID to FND_SECURITY_GROUPS when operating under Multi-Org security policies.

Because HTM_TEXT can be large, reporting queries should project only the columns required and filter aggressively on the primary key columns.

Related Objects

Documented relationships connect OKC_REPORT_HTM to the following objects:

• FND_SECURITY_GROUPS — referenced via SECURITY_GROUP_ID, governing access partitioning.
• OKC_REPORT_TEMPLATES / OKC_REPORT_TEMPLATES_B / _TL — the stylesheet definitions whose XST_ID values are referenced here.
• OKC_CONTRACTS / OKC_K_HEADERS — contract header records identified by CHR_ID.
• OKC_REPORT_XML / OKC_REPORT_DOCS — upstream XML and document artifacts feeding the transformation.
• OKC_PRINT_QUERIES — print query definitions driving data extraction.
• OKE / OKC print APIs — contract printing concurrent programs that write to this table.

These relationships reflect the print pipeline, with OKC_REPORT_HTM acting as the terminal HTML artifact store.