Results for “okc_report_xst”

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

Overview

OKC_REPORT_XST is a Contracts Core (OKC) transactional configuration table that drives contract printing in Oracle E-Business Suite Release 12.1.1 and 12.2.2. Its documented purpose is to store combinations of SQL and XSL definitions that together produce a report through an SQL-to-XML-to-XSL-to-HTML transformation chain. In practice, each row represents an executable printing "recipe": a SQL statement that extracts contract data into XML, an XSL stylesheet that transforms that XML into HTML (or another presentation format), and an associated transformation identifier that ties the two together at runtime.

The table is owner-qualified as OKC.OKC_REPORT_XST and holds a VALID status in the ETRM 12.2.2 physical schema, with 12 documented columns. From a Data Vault modeling perspective, the mined FK structure classifies this object as standalone, meaning it does not participate in the classic hub-link-satellite topology. The practical modeling suggestion is to treat it as a reference or configuration entity keyed on a surrogate identifier, rather than as a hub with dependent satellites.

Key Information Stored

The most significant documented columns are:

• ID — the surrogate primary key. It is enforced by the unique index OKC_REPORT_XST_U0 and by the OKC_REPORT_XST_PK constraint, and is the value referenced by downstream child records.
• XSL_ID, SQL_ID, XST_ID — the three business-key components. Together they form the unique constraint OKC_REPORT_XST1_UK and the unique index OKC_REPORT_XST_U1, guaranteeing that a given stylesheet, query, and transformation combination appears only once.
• CACHE_YN — controls whether the compiled or generated report artifact is cached, which directly affects printing performance for high-volume contract generation.
• OBJECT_VERSION_NUMBER — the optimistic locking column used by the Oracle Application Framework (OAF) to detect concurrent updates.
• SECURITY_GROUP_ID — the foreign key into FND_SECURITY_GROUPS, which scopes the row to a specific application security group, typically the standard Oracle Contracts group.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — the standard EBS WHO columns for audit trail and accountability.

Because ID is the surrogate key while (XSL_ID, SQL_ID, XST_ID) is the true business key, joins from other tables referenced by ID should be validated against the unique index on the business key where cross-instance or cross-environment migration is involved.

Common Use Cases and Queries

Report administrators and technical consultants query this table when diagnosing why a contract print program produces blank output, wrong formatting, or a transformation error. A typical verification query resolves the business keys to their definition rows:

• Locate the recipe for a known stylesheet: SELECT id, xsl_id, sql_id, xst_id, cache_yn FROM okc.okc_report_xst WHERE xsl_id = :xsl_id AND sql_id = :sql_id AND xst_id = :xst_id;
• Inventory all printing recipes in a security group: SELECT r.id, r.cache_yn FROM okc.okc_report_xst r WHERE r.security_group_id = :group_id ORDER BY r.id;
• Filter to non-cached, performance-sensitive definitions: SELECT id, xsl_id, sql_id FROM okc.okc_report_xst WHERE cache_yn = 'N';
• Audit recent maintenance against the WHO columns: SELECT id, last_updated_by, last_update_date FROM okc.okc_report_xst WHERE last_update_date > :cutoff;

Reporting use cases include documenting which SQL and XSL assets are active before a patch or clone, confirming row uniqueness before inserting new combinations during a migration, and reconciling the table against the underlying XSL and SQL definition stores to detect orphaned references. Because the table is standalone, queries are generally simple single-table lookups followed by joins to the definition tables that hold the actual XSL text and SQL text.

Related Objects

The documented foreign key and dependency relationships define the following significant related objects:

• FND_SECURITY_GROUPS — referenced through OKC_REPORT_XST.SECURITY_GROUP_ID, scoping each recipe to an application security group.
• OKC_REPORT_XSL — the stylesheet definition table, joined on XSL_ID, holding the XSL text that performs the XML-to-HTML conversion.
• OKC_REPORT_SQL — the query definition table, joined on SQL_ID, holding the SQL text that extracts contract data into XML.
• OKC_REPORT_XST child/transformation definitions — joined on XST_ID, describing the transformation variant applied to the SQL-XML-XSL pipeline.
• OKC_REPORT_XST1_UK and OKC_REPORT_XST_U1 — the unique constraint and index enforcing business-key integrity on (XSL_ID, SQL_ID, XST_ID).
• OKC_REPORT_XST_PK and OKC_REPORT_XST_U0 — the primary key constraint and unique index on ID.
• OKC contract printing concurrent programs — the runtime consumers that read rows from this table to assemble the SQL-XML-XSL-HTML printing chain.

Together these objects form the complete contract printing pipeline, with OKC_REPORT_XST acting as the assembly table that binds query, stylesheet, and transformation into a single executable definition.