Results for “okc_report_xml_v”

26 results




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

Overview

OKC_REPORT_XML_V is a reporting view owned by the APPS schema within the Oracle Contracts Core (OKC) module. It is a language-filtered projection of the contract report XML repository used during Contract Printing. When a contract document is generated for printing, Oracle Contracts uses the XML SQL Utility (XSUtility) supplied by Oracle XML Developer's Kit to serialize contract data into an XML document. The resulting XML payload is persisted in the underlying repository table, and this view exposes that stored content to the application and to external consumers that need a copy of the generated contract XML. The view retains a VALID status in Oracle E-Business Suite 12.1.1 and 12.2.2.

The object is not a stored table and holds no data of its own. It is a thin, read-oriented window that applies a single filtering predicate, restricting rows to the language of the current session. This makes the view behave context-sensitively: the same query returns different rows depending on the value of the session language, aligning printed document content with the user's locale.

Underlying Base Objects

The view is defined over OKC_REPORT_XML (exposed in APPS through a synonym). The view text selects from that base object and applies the predicate WHERE LANGUAGE = USERENV('LANG'). No joins, aggregations, or analytic functions are present, so the view is a simple column projection plus language filter. Every row in OKC_REPORT_XML that matches the session language is visible through the view. Because the base object is referenced as a synonym, the physical implementation remains shielded behind the APPS schema, consistent with standard EBS coding practice.

Key Columns

The view exposes the following columns, each inherited directly from OKC_REPORT_XML:

  • CHR_ID — Identifier of the contract or contract line whose printed XML is stored.
  • MAJOR_VERSION and MINOR_VERSION — Version coordinates that distinguish successive generations of the same contract document, allowing prior and current print versions to be tracked.
  • SQL_ID — Identifier of the SQL statement or extraction definition used to produce the XML payload.
  • XML_TEXT — The XML document itself, produced via XSUtility; this is the column most frequently referenced by consumers searching for "xml_text."
  • CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard EBS audit columns recording who created and last modified each row and when.

The LANGUAGE column present in the base table is consumed by the WHERE clause and is therefore not projected out of the view.

Common Use Cases and Queries

Typical uses include retrieving the stored XML for a specific contract version, auditing the number of XML copies retained per contract, and feeding downstream integration processes that transform or archive printed contract content. Because the view is language-restricted, queries are normally run from within an EBS session where USERENV('LANG') is set appropriately.

Retrieve the XML for a given contract and version:

  • SELECT chr_id, major_version, minor_version, xml_text FROM okc_report_xml_v WHERE chr_id = :p_chr_id AND major_version = :p_major;

Count stored XML copies per contract:

  • SELECT chr_id, COUNT(*) FROM okc_report_xml_v GROUP BY chr_id;

Inspect the most recently updated XML documents:

  • SELECT chr_id, major_version, minor_version, last_update_date FROM okc_report_xml_v ORDER BY last_update_date DESC;

Because XML_TEXT may be a large object, callers should apply restrictive predicates on CHR_ID and version columns before selecting the payload.