Results for “okc_report_xml”

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

Overview

The OKC_REPORT_XML table resides in the OKC schema within Oracle E-Business Suite and is part of the Contracts Core (OKC) module. Its documented purpose is to support contract printing: it stores the XML document generated with Oracle's XSUtility based on a query defined in the contract template or report configuration. During the contract authoring and printing lifecycle, Oracle Contracts produces formatted output by executing a query, converting the result set into an XML document, and persisting that document in OKC_REPORT_XML for retrieval by the printing or document generation process.

From a Data Vault modeling perspective, the ETRM heuristic classifies this object as standalone, meaning it does not participate in the mined foreign-key network as a link or dependent satellite. In practical terms, the table behaves as a persistent repository for generated XML fragments keyed by contract, version, language, and source query, rather than as a transactional hub or relationship link.

Key Information Stored

OKC_REPORT_XML is defined with twelve columns and a composite primary key, OKC_REPORT_XML_PK, spanning CHR_ID, MAJOR_VERSION, LANGUAGE, and SQL_ID. The most significant columns are:

• CHR_ID — Identifier of the contract (or contract header) for which the XML was generated; part of the primary key and the principal business-key candidate.
• MAJOR_VERSION — Major version number of the contract or template, ensuring XML is tied to the correct revision.
• LANGUAGE — Language code of the generated document, supporting multilingual contract output.
• SQL_ID — Identifier of the query used by XSUtility to produce the XML, distinguishing multiple report definitions for the same contract.
• MINOR_VERSION — Minor version indicator complementing MAJOR_VERSION.
• XML_TEXT — The actual XML document generated from the query; the substantive payload of the table.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard EBS audit columns tracking who generated or modified the record and when.
• SECURITY_GROUP_ID — References FND_SECURITY_GROUPS, enforcing multi-org/data-security filtering.

The unique index OKC_REPORT_XML_U1 (CHR_ID, MAJOR_VERSION, LANGUAGE, SQL_ID) mirrors the primary key and confirms the business-key candidate set. A secondary system index (SYS_IL…) is associated with the XML_TEXT LOB storage.

Common Use Cases and Queries

Typical usage centers on contract printing and debugging failed or unexpected print output.

• Retrieving the generated XML for a specific contract and version:

SELECT chr_id, major_version, minor_version, language,
       sql_id, xml_text
FROM   okc.okc_report_xml
WHERE  chr_id = :contract_id
AND    language = USERENV('LANG');

• Identifying which SQL definitions have produced XML for a contract, useful when troubleshooting templates:

SELECT sql_id, COUNT(*), MAX(last_update_date)
FROM   okc.okc_report_xml
WHERE  chr_id = :contract_id
GROUP BY sql_id;

• Auditing document generation activity over a period:

SELECT created_by, creation_date, chr_id, major_version
FROM   okc.okc_report_xml
WHERE  creation_date >= :from_date;

Reporting use cases include validating that print output exists for executed contracts, analyzing template/query performance, and supporting migration or archival of historical contract documents.

Related Objects

The documented foreign-key relationship links SECURITY_GROUP_ID to FND_SECURITY_GROUPS, tying records to the EBS security model. Functionally, OKC_REPORT_XML depends on the contract entity represented by CHR_ID (OKC_K_HEADERS / OKC_K_HEADERS_B and their versions), and on the query definitions identified by SQL_ID. The XSUtility and the Oracle Contracts print/merge programs (such as OKC Contract Print workflows) generate and consume these rows. Reporting joins typically combine OKC_REPORT_XML with OKC_K_HEADERS for contract context and FND_SECURITY_GROUPS for security validation.