Search Results okc_report_xsl_b




Overview
Explore in AI Chat

Overview

The OKC_REPORT_XSL_B table resides in the OKC schema (Contracts Core) and is a core configuration object for the Contract Printing feature in Oracle E-Business Suite 12.1.1 and 12.2.2. Its purpose is to store the XSLT stylesheets that transform contract data, extracted through a SQL-XML query, into a formatted HTML report. In effect, the table holds the presentation-layer definition that drives the SQL-XML-XSL-HTML rendering pipeline used when users print or preview contract documents such as standard clauses, terms, and agreement layouts.

Under the heuristic Data Vault classification derived from the foreign-key structure, OKC_REPORT_XSL_B is modeled as a standalone object. It carries its own surrogate key and does not serve as a link or dependent satellite; it functions as an independent reference hub of stylesheet definitions. Note that this is a modeling suggestion rather than a formally declared Data Vault construct within the EBS schema.

Key Information Stored

The table comprises 11 documented columns. The following are the most significant:

  • ID — The surrogate primary key, enforced by constraint OKC_REPORT_XSL_B_PK and the unique index OKC_REPORT_XSL_B_U1. This is the internal identifier for each stylesheet record and is the value most commonly referenced by the alias okc_report_xsl_b_pk.
  • AUTHORING_ORG_ID — Identifies the operating unit or authoring organization that owns the stylesheet, enabling multi-org segmentation.
  • START_DATE and END_DATE — Date-effective range controls that determine when a given stylesheet version is active. These fields support versioning of report layouts without overwriting prior definitions.
  • OBJECT_VERSION_NUMBER — The optimistic locking column used by the Oracle Application Framework (OAF) and BC4J to prevent concurrent modification conflicts.
  • SECURITY_GROUP_ID — A foreign key to FND_SECURITY_GROUPS that enforces data security partitioning across the EBS instance.
  • CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard WHO audit columns capturing creation and modification metadata for every record.

The business-key candidate is ID via the unique index OKC_REPORT_XSL_B_U1. While AUTHORING_ORG_ID, START_DATE, and END_DATE together often behave as a natural composite key in practice, no separate unique constraint is documented for that combination.

Common Use Cases and Queries

The primary use case is printing contract documents. When a user invokes the print action, the concurrent program or OAF page queries this table for the currently effective stylesheet, applies it to the XML payload, and renders HTML output. Administrators also use this table to audit which stylesheet versions were active on specific dates.

A typical lookup resolves the active stylesheet for a given organization and date:

  • SELECT id, authoring_org_id, start_date, end_date FROM okc_report_xsl_b WHERE authoring_org_id = :org_id AND TRUNC(SYSDATE) BETWEEN start_date AND NVL(end_date, SYSDATE + 1) AND security_group_id = :sgid;

Version history reporting joins the table to itself to detect superseded layouts, while security auditing filters by SECURITY_GROUP_ID to confirm partitioning. Reporting on CREATED_BY or LAST_UPDATED_BY supports change-tracking for compliance.

Related Objects

  • FND_SECURITY_GROUPS — Referenced through OKC_REPORT_XSL_B.SECURITY_GROUP_ID; join on SECURITY_GROUP_ID to resolve security group names.
  • OKC_REPORT_XSL_TL — The translatable (language) companion table sharing the ID primary key, holding language-specific stylesheet descriptions.
  • OKC_REPORT_XSL_B_PK — The primary key constraint formally declared on the ID column.
  • OKC_REPORT_XSL_B_U1 — The unique index on ID that qualifies it as the business-key candidate.
  • OKC_CONTRACT_TEMPLATES and related OKC contract definition tables — Consume the stylesheet during contract generation and printing workflows.
  • FND_USER — Join on CREATED_BY or LAST_UPDATED_BY to identify the administrator responsible for a stylesheet revision.

Together these relationships position OKC_REPORT_XSL_B as a self-contained configuration reference whose integrity depends on standard EBS audit and security infrastructure rather than on the broader contracts transactional hierarchy.