Results for “xst_id”

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

Overview

OKC_REPORT_XST_V is a reporting view owned by the APPS schema within the OKC (Contracts Core) product module of Oracle E-Business Suite. It is a thin projection view defined over the OKC_REPORT_XST table and serves as the metadata repository for contract printing in Oracle Contracts. Specifically, the view exposes the set of (query, stylesheet) pairings that drive the generation of printed contract documents. The "XST" component of the name reflects the coupling of an XSL stylesheet with a SQL query: each record links a stored query that gathers contract data to the stylesheet that transforms that data into formatted output.

In Oracle EBS 12.1.1 and 12.2.2, contract printing relies on a template engine that retrieves a saved SQL statement and an associated XSL-FO or XSLT stylesheet, then renders the merged output as a printable document. OKC_REPORT_XST_V provides the lookup surface through which the printing framework resolves which stylesheet applies to which query. Because it is a view rather than a table, it imposes no additional storage and inherits the column set of its base object directly. Its status is documented as VALID in the ETRM metadata, confirming that the underlying definition compiles successfully against the APPS schema.

Underlying Base Objects

The view is defined over a single referenced base object, OKC_REPORT_XST, which is documented as a synonym in the metadata. The view text is a straightforward column projection from that object:

• SELECT ID, XSL_ID, SQL_ID, XST_ID, CACHE_YN, OBJECT_VERSION_NUMBER, CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN FROM OKC_REPORT_XST

No joins, filters, or aggregation are applied. This means the view behaves as a pass-through alias to the base table, offering a stable, queryable name in the OKC reporting layer while the physical persistence and constraints remain on OKC_REPORT_XST. Because the mapping is one-to-one and unfiltered, every row and column visible on the base object is likewise visible through the view.

Key Columns

The columns exposed mirror the base table and encode the printing configuration:

• ID — Primary identifier for the query/stylesheet combination record.
• XSL_ID — Identifier of the XSL stylesheet used to transform the query output; this is the column most frequently targeted when users search for "xsl_id," since it ties a printing template to its transformation logic.
• SQL_ID — Identifier of the SQL query that supplies the source data for the print job.
• XST_ID — Identifier linking the stylesheet and query pairing as a composite configuration record.
• CACHE_YN — Flag indicating whether the generated output or template should be cached, which affects printing performance.
• OBJECT_VERSION_NUMBER — Optimistic locking column used to detect concurrent updates.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard Oracle EBS audit columns capturing who created and last modified each row, and when.

Common Use Cases and Queries

Developers and functional consultants query this view to inspect, troubleshoot, or extend contract printing configurations. Typical scenarios include identifying which stylesheet is bound to a given query, verifying caching behavior, and auditing recent changes to printing templates.

To retrieve all printing combinations:

• SELECT id, xsl_id, sql_id, xst_id, cache_yn FROM okc_report_xst_v;

To locate the stylesheet binding for a specific query:

• SELECT id, xsl_id, xst_id FROM okc_report_xst_v WHERE sql_id = :p_sql_id;

To review recently modified configurations, using the audit columns:

• SELECT id, xsl_id, sql_id, last_updated_by, last_update_date FROM okc_report_xst_v ORDER BY last_update_date DESC;

Because the view is unfiltered, care should be taken when joining it to other OKC objects to avoid accidental row multiplication. All queries should be executed in the APPS schema or through a synonym appropriately granted to the requesting user.