Results for “okc_report_xsl_v”

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

Overview

OKC_REPORT_XSL_V is a PL/SQL view owned by the APPS schema in Oracle E-Business Suite, belonging to the OKC (Contracts Core) product family. Its documented purpose is to support Contract Printing within the Oracle Contracts module, specifically the SQL-XML-XSL-HTML rendering pipeline used to transform contract data into printable output. The view stores and exposes the stylesheet (XSL) content referenced during that transformation process. In the context of EBS 12.1.1 and 12.2.2, this view functions as the consumer-facing, language-aware interface to the contract report stylesheet repository. When a user initiates contract printing, the reporting engine resolves the appropriate stylesheet through this view rather than querying the underlying tables directly.

The object carries a VALID status in the documented ETRM metadata, confirming it is a supported and currently active database object. Its inclusion in the ETRM repository indicates it is intended for reference and reporting use, though it is an internal implementation component of the contract printing subsystem rather than a general-purpose interface.

Underlying Base Objects

The view is defined over two base objects, both exposed through synonyms in the APPS schema:

• OKC_REPORT_XSL_B — the base table holding non-translatable attributes of each XSL report definition, including the primary key, authoring organization, effective dates, and audit columns.
• OKC_REPORT_XSL_TL — the translation table holding language-specific content: the stylesheet text itself (XSL_TEXT), display name, help text, and the protected flag.
• OKC_CONTEXT — a package, not a table, referenced in the view's WHERE clause through the function OKC_CONTEXT.GET_OKC_ORG_ID. This function resolves the caller's active operating unit context at query time.

The join between the two tables is performed on ID, and the translation table is further filtered by TL.LANGUAGE = USERENV('LANG'), ensuring only the session's current language rows are returned. This design follows the standard EBS MLS (Multi-Lingual Support) pattern, where base and translation tables are combined into a single logical view.

Finally, an organization security predicate filters rows to those where AUTHORING_ORG_ID equals 0 (shared/global definitions) or matches the current OKC operating unit returned by OKC_CONTEXT.GET_OKC_ORG_ID. This guarantees that users see only stylesheets available to their authoring organization.

Key Columns

The view exposes the following columns, combining base and translated attributes:

• ID — primary identifier linking the base and translation records.
• AUTHORING_ORG_ID — the organization that authored the stylesheet; value 0 denotes a global definition available to all operating units.
• NAME — the display name of the stylesheet (translated).
• XSL_TEXT — the full XSL stylesheet content used by the SQL-XML-XSL-HTML print transformation. This is the column most commonly queried by developers and administrators inspecting contract print output.
• HELP_TEXT — descriptive or instructional text associated with the stylesheet.
• PROTECTED_YN — indicates whether the stylesheet is protected from user modification.
• START_DATE / END_DATE — effective date range governing when the stylesheet is active.
• OBJECT_VERSION_NUMBER — optimistic locking column used by the EBS framework.
• Standard audit columns — CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, and LAST_UPDATE_LOGIN.

Common Use Cases and Queries

Typical use cases include auditing active contract print stylesheets, retrieving XSLT content for debugging print rendering issues, and confirming which definitions apply to a given operating unit. A basic query filtering on the stylesheet name and returning the XSL body is shown below:

SELECT id, name, xsl_text FROM okc_report_xsl_v WHERE name LIKE '%CONTRACT%';

To examine the authorization scope and effective dates of all available stylesheets:

SELECT id, authoring_org_id, name, protected_yn, start_date, end_date FROM okc_report_xsl_v ORDER BY authoring_org_id, name;

Because the view enforces language and organization predicates internally, query results automatically reflect the caller's session language and current OKC operating unit. This makes the view suitable for diagnostic reporting without requiring the caller to manually replicate the MLS join or security logic. Production tuning should avoid selecting XSL_TEXT in bulk, as the column can contain large CLOB-style payloads.